danny_met's questions

EDIT: see updates at the end for solution, title changed to reflect better the problem.

I have Ubuntu 22.04 LTS on a system with a Geforce RTX 2060 card. I have recently done some small changes in hardware (changing the graphics card from one PCI slot to another, and days after that installing some case fan), and after the latest change I am finding that the graphic output of the system randomly dies, not much time after booting. Booting is apparently fine, I can log in, start opening my browser, terminals etc as usual, and then the screen turns blue just like when there is no signal. Any attempt to open a terminal (Ctrl+Alt+F3, Ctrl+Alt+F1...) is useless, and I can only do a Alt+SysRq+REISUB to reboot the system.

Looking at the system/kernel logs, it seems that the problems start with this:

kernel: [ 1531.539086] xhci_hcd 0000:0c:00.2: Unable to change power state from D3hot to D0, device inaccessible 
kernel: [ 1531.539241] nouveau 0000:0c:00.0: timer: stalled at ffffffffffffffff
kernel: [ 1531.539244] ------------[ cut here ]------------
kernel: [ 1531.539245] nouveau 0000:0c:00.0: timeout

And later some lines like

kernel: [ 1531.599952] xhci_hcd 0000:0c:00.2: Unable to change power state from D3cold to D0, device inaccessible
kernel: [ 1531.599959] xhci_hcd 0000:0c:00.2: Controller not ready at resume -19
kernel: [ 1531.599961] xhci_hcd 0000:0c:00.2: PCI post-resume error -19!
kernel: [ 1531.599962] xhci_hcd 0000:0c:00.2: HC died; cleaning up

I have tried browsing for those messages and read that some people gets some issues after changing the card from one PCI slot to another (which I find surprising), but the funny thing is that I did change the graphics card of PCI slot about one week ago, and during this week everything was fine, and it has been only today after powering off to add a case fan and rebooting (fan was an Arctic P14 slim PWM PST, connected to an Arctic P12 PWM PST that was already installed, and that to CHA_FAN1 on the mobo which is an Asus ROG Strix X570-e) that I am having these issues.

So, I do not know if the issue is the changes in the hardware that are creating conflicts, or else whether there has been some update of the nouveau drivers that has kicked in after the last boot (I take lots of time from one boot to another, so I would have detected that only now).

Someone has some idea of what is the issue, or what should I look for in the logs to better pinpoint the problem? Thanks a lot!

** UPDATE: just tried putting back the graphics card to the previous PCI slot, and the problem appears again. So I guess that it must be something related with some recent drivers update or something like that. Anyone has some idea?

** UPDATE 2: As said in the comment to the answer by kanehekili, I think I know now the origin of the problem. The card was originally in a x16 slot, and then I changed it to another slot that is admits a x16 card but actually is a x8 slot. The documentation of the mobo very misleadingly labels the slots as PCIEX16_1 and PCIEX16_2, omitting the fact that the second slot is actually only x8. Then, surely this change triggered some issue with the drivers that persisted even after putting back the card to the x16. The problem was finally solved by installing the Nvidia "driver metapackage from nvidia-driver-530 (proprietary)" with the GUI "additional drivers" menu. I note that trying the first driver option in the menu, which is the "-open" version of 530, still gave some issues as the system would not fully recognize the card (e.g. output of nvidia-smi in terminal would give "no devices were found"). Now, apparently everything is fine again. I mark the issue as solved.

I must transfer several huge files from a remote machine A to my local computer. The problem is that I can not access A directly, but instead I must access via another remote machine B. Unfortunately, machine B has a very limited amount of space, so I can not copy the files from A to B and then from B to local. Instead, I would need to use B as a kind of proxy.

I was thinking in something as simple as possible that does not need to install or configure anything, hopefully simply using sftp, scp o ssh.

Does anyone know how to do that?

As explained in the title, I can edit the css file /usr/share/Yaru-dark/gnome-shell/gnome-shell.css and write:

stage {
  font-family: Ubuntu, Sans-Serif;
  font-size: 12pt;
  font-weight: bold;
}

But for some reason the font-weight specification has no effect, however changing the font-size works fine.

Is it something I am missing in specifying the font?

I just upgraded to Ubuntu 20.04 and I am unable to toggle between the tabs in the terminal with the mouse wheel, which was fine in 18.04. I can't find where this feature is enabled. Is it possible that this feature has been removed?

After trying to fix my graphics drivers I have finally come to a point where I get a black screen on boot, even though "nomodeset" is set in /etc/default/grub.

The system is a Thinkpad X1 carbon with an Intel HD 620 graphics card.

The full previous story is here, but to be short the thing is that Ubuntu was no longer loading the intel drivers but the system would boot and see fine but with some issues (brightness controls broken, not suspend on closing lid), and in my attempt to fix things I did this:

sudo add-apt repository -y ppa:oibaf/graphics-drivers
sudo apt update
sudo apt upgrade

After that I would see this:

Then I tried to force the intel drivers doing:

sudo apt install xserver-xorg-core-hwe-18.04
sudo apt install xserver-xorg-video-intel-hwe-18.04

After this, I get a black screen on boot. I tried to undo it by

sudo apt-get remove xserver-xorg-core-hwe-18.04
sudo apt-get remove xserver-xorg-video-intel-hwe-18.04

But I still get the black screen (again, I have "nomodeset" in the grub file).

Some help for fixing this enormous mess would be greatly appreciated!

EDIT: It keeps getting better. Now I saw that all the xserver-xorg-video-* packages are gone, by doing dpkg --get-selections | grep xserver-xorg-video I only see xserver-xorg-video-intel and xserver-xorg-video-intel-hwe-18.04, both marked as rc.

EDIT2: Well, I managed to fix the black screen by doing sudo apt-get install --reinstall xserver-xorg However, still I get the 'llvmpipe' as the graphics in the Details window...

EDIT3:

IT IS FINALLY FIXED!!!!

After the last edit, I removed the 'nomodeset' from the GRUB file and it is finally working! All the apparent issues are gone (brightness and suspend working again), lshw -C video shows configuration: driver=i915 and in the Settings window I see "Mesa Intel HD Graphics 620 (KBL GT2)"

I'm having a puzzling issue with X11.

I am running Ubuntu 19.10 on a desktop, from which I can ssh to Server A where X11 forwarding works nicely (i.e. X11 on my client side works), but on the other hand if I try to use X11 to another Server B then it does not work.

But it happens that X11 on Server B is fine because it works when I connect to it via my laptop (with Ubuntu 18.04)!

This is what I get from ssh -v -X :

debug1: Requesting X11 forwarding with authentication spoofing.
debug1: Sending environment.
.... 
debug1: client_input_channel_open: ctype x11 rchan 2 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 49834
debug1: channel 1: new [x11]
debug1: confirm x11
debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 49860
debug1: channel 2: new [x11]
debug1: confirm x11
debug1: client_input_channel_open: ctype x11 rchan 4 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 49878
debug1: channel 3: new [x11]
debug1: confirm x11
debug1: channel 1: FORCE input drain

This is very strange, because the usual solutions (edit /etc/ssh/ssh_config) do not work. And with Ubuntu 18.04 everything works out of the box!

I compared the outputs of both the successful case w/Ubuntu18.04@laptop and the unsuccessful case w/Ubuntu19.10@desktop and the only significant difference is the message FORCE input drain.

A more complete output with ssh -vvv -X gives me this (note that I am trying to open a gnuplot window to test the X11):

gnuplot> p x w l
debug3: receive packet: type 90
debug1: client_input_channel_open: ctype x11 rchan 2 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 52382
debug2: fd 7 setting O_NONBLOCK
debug3: fd 7 is O_NONBLOCK
debug1: channel 1: new [x11]
debug1: confirm x11
debug3: send packet: type 91
debug2: channel 1: rcvd adjust 34784
debug3: receive packet: type 90
debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 52394
debug2: fd 8 setting O_NONBLOCK
debug3: fd 8 is O_NONBLOCK
debug1: channel 2: new [x11]
debug1: confirm x11
debug3: send packet: type 91
debug3: receive packet: type 90
debug1: client_input_channel_open: ctype x11 rchan 4 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 52398
debug2: fd 9 setting O_NONBLOCK
debug3: fd 9 is O_NONBLOCK
debug1: channel 3: new [x11]
debug1: confirm x11
debug3: send packet: type 91
debug2: channel 1: rcvd adjust 33588
debug2: channel 1: rcvd adjust 46612
debug2: channel 1: rcvd adjust 37976
debug2: channel 1: rcvd adjust 45940
debug2: channel 1: rcvd adjust 33144
debug3: receive packet: type 96
debug2: channel 1: rcvd eof
debug2: channel 1: output open -> drain
debug2: channel 1: obuf empty
debug2: channel 1: chan_shutdown_write (i0 o1 sock 7 wfd 7 efd -1 [closed])
debug2: channel 1: output drain -> closed
debug1: channel 1: FORCE input drain
debug2: channel 1: ibuf empty
debug2: channel 1: send eof
debug3: send packet: type 96
debug2: channel 1: input drain -> closed
debug2: channel 1: send close
debug3: send packet: type 97
debug3: channel 1: will not send data after close
debug3: channel 1: will not send data after close
Warning: slow font initialization
debug3: channel 1: will not send data after close
debug3: channel 1: will not send data after close
gnuplot> 
debug3: channel 1: will not send data after close

Does anyone have any idea of what is this? Maybe some bug in Ubuntu 19.10?

I want to reinstall Linux 18.04 on my laptop after I screwed up several things (see this question, also help is welcome with that), but when I boot with the USB live I don't see the option for keeping the files (I don't want to format again). I am not sure if this has something to do with the fact that the system in the laptop is version 18.04.4 and the one in USB is 18.04.3. Can anyone confirm if this is the issue and if so whether it can be solved with an iso of version 18.04.4, and where could I find it?

[edited for claryfing some details]

I installed Lutris (utility for running games designed for windows) and Winehq (required for it) and after reboot the system got stuck in "record successful boot for GRUB" (see image)

When I boot, I see the GRUB menu for choosing Ubuntu / Ubuntu recovery mode / Windows / etc. Then if leave the normal startup begin, the system gets stuck as above, but if I enter in the recovery mode and request to keep normal startup (without actually doing anything else) then the system boots apparently fine, apart from some details that do not work properly (I had to change the scale of the display, and the laptop does no longer suspend when closing the lid, in addition some of the Fn keys like brightness do not work anymore -- BTW it is a Thinkpad X1 carbon 5th gen). I tried to fix packages via dpkg in the recovery mode it but does not help.

Now the question is what did I broke when installing winehq/wine/lutris. I had to enable i386 architecture and add several repositories, which I already deleted (anything related with i386/wine/winehq/lutris...)

It seems that Lutris/wine has messed up some graphics driver or power manager or whatever, but I do not find similar problems reported. Has anyone any idea of what has been broken and how can I fix it?