installed curl into a working LXQT session. Now X will not boot

installed curl into a working LXQT session. Now X will not boot

I was trying to install the Brave.com browser.
https://brave.com/linux/#linux

OpenSUSE 15+

sudo zypper install curl

sudo rpm --import https://brave-browser-rpm-release.s3.brave.com/brave-core.asc

sudo zypper addrepo https://brave-browser-rpm-release.s3.brave.com/x86_64/ brave-browser

sudo zypper install brave-browser

The first step is to install curl. zypper curl
It called for a reboot.
It reboots but will not load X.

Here is the last few lines of the /var/log/Xorg.0.log

   243.066] (II) NOUVEAU(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
   243.066] (II) NOUVEAU(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
   243.147] (--) NOUVEAU(G0): HDMI max TMDS frequency 225000KHz
   269.310] (EE) event3  - PixArt USB Optical Mouse: client bug: event processing lagging behind by 12ms, your system is too slow
   269.310] (EE) event3  - PixArt USB Optical Mouse: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.
  1463.172] (II) event2  - Power Button: device removed
  1463.185] (II) event1  - Power Button: device removed
  1463.213] (II) event3  - PixArt USB Optical Mouse: device removed
  1463.246] (II) event0  - AT Translated Set 2 keyboard: device removed
  1463.273] (II) event5  - HP WMI hotkeys: device removed
  1463.352] failed to get BO with handle -1
  1463.354] (II) UnloadModule: "libinput"
  1463.354] (II) UnloadModule: "libinput"
  1463.354] (II) UnloadModule: "libinput"
  1463.354] (II) UnloadModule: "libinput"
  1463.354] (II) UnloadModule: "libinput"
  1463.377] (II) NOUVEAU(G0): NVLeaveVT is called.
  1463.437] (II) NOUVEAU(0): NVLeaveVT is called.
  1463.490] (II) Server terminated successfully (0). Closing log file.

Any and all help is appreciated.

Random portions of Xorg.0.log are rarely helpful. Instead, upload the whole log and give us the resulting URL:

cat /var/log/Xorg.0.log | susepaste

It’s very surprising to see curl was not already installed. Vast portions of YaST require curl, and most openSUSE installations include most if not all of YaST.

Knowing your NVidia configuration could be helpful as well:

inxi -Gay

Above is best run from running X, when possible, a bit of a chicken and egg problem when X won’t start, because inxi has no access to some configuration bits when doesn’t come from running X. It also depends on xdpyinfo (running in X) for certain bits, which on an installation without YaST & curl might not (yet) be installed.

Thank you and here it is.

https://susepaste.org/44827048

I have a couple of partians, one as a backup.
Below is the one I am running now, but this is not the correct one with the curl issue.
This one has a few other nvidia problems from the latest zypper dup. I’ll get to those after this is fixed,

The real one should be under /LXQT-root/
What would that command be to pull the correct information for you?

> inxi -Gay
Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: eVga.com. driver: nvidia
v: 470.86 alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:128b
class-ID: 0300
Device-2: NVIDIA GF119 [GeForce GT 610] vendor: eVga.com. driver: N/A
alternate: nouveau, nvidia_drm, nvidia bus-ID: 20:00.0 chip-ID: 10de:104a
class-ID: 0300
Display: x11 server: X.org 1.21.1.1 driver: loaded: modesetting
unloaded: fbdev,vesa alternate: vboxvideo,vmware
resolution: <missing: xdpyinfo>
OpenGL: renderer: llvmpipe (LLVM 13.0.0 128 bits) v: 4.5 Mesa 21.3.0
direct render: Yes

OK,
I rebooted to that install and ran the inxi -Gay from the console mode

Graphics:
Device-1: NVIDIA GK208B [GeForce GT 710] vendor: eVga.com. driver: nouveau v: kernel bus-ID 01:00.0 chip-ID: 10de:128b class-ID: 0300
Device-2: NVIDIA GF119 (GeForce GT 610] vendor: eVga.com. driver: nouveau v: kernel bus-ID 20:00.0 chip-ID: 10de:104a class-ID: 0300
Display: server: X.org 1.20.11 driver: loaded: nouveau unloaded: fbdev,modesetting,vesa alternative: nv,nvidia tty: 160x64
Message: Advanced graphics data unavailable in console for root.

I have not updated (zypper dup) that for a while.
With the other problems I was having in this side from the nvidia issues, I didn’t want to chance trashing it also.

Guess; your out of date TW install pulled in some new files when Brave was installed and now you don’t have all your necessary files in sync.

rpm -qa --last | head -n 50

Might be revealing.

The only things obvious to me from your log is it comes from using a ~6 month old kernel and an old Xorg version, which suggests you tried to “install” curl on an installation that was in need of getting properly-up-to-date, or you provided a log from running a different OS than the one with the subject problem.

The original inxi report presented suffices for now.

If you have an /etc/X11/xorg.conf or equivalent files in /etc/X11/xorg.conf.d/, or an xrandr startup script to configure your dual graphics cards, you should show them to us.

Would a zipper dup clean it all up?

Normally one should expect so, but when you let TW get that far behind, the odds of something going wrong get farther from zero.

Here are what I could type. It is all of the installs from the other night, and down to the first of the 6 month back.

:~ # rpm -qa --last | head -n 50
glibc-devel-2.34-3.1.x86_64 Sun 28 Nov 2021 08:50:35 PM CST
curl-7.80.0-1.1.x86-64 Sun 28 Nov 2021 08:50:35 PM CST
libcurl4-7.80.0-1.1.x86-64 Sun 28 Nov 2021 08:50:34 PM CST
glibc-extra-2.34-3.1.x86-64 Sun 28 Nov 2021 08:50:34 PM CST
glibc-locale-2.34-3.1.x86-64 Sun 28 Nov 2021 08:50:33 PM CST
nscd-2.34-3.1.x86-64 Sun 28 Nov 2021 08:50:28 PM CST
glibc-localepbasep2.34-3.1.x86-64 Sun 28 Nov 2021 08:50:27 PM CST
glibc-2.34-3.1.x86-64 Sun 28 Nov 2021 08:50:27 PM CST
filesystem-84.87-3.1.x86-64 Sun 28 Nov 2021 08:50:25 PM CST
compat-usrmerge-tools-84.87-5.1.x86_64 Sun 28 Nov 2021 08:50:20 PM CST
cinnamon-screensaver-lang4.8.0-1.2.noarch Sun 30 May 2021 04:25:44 PM CST

I am trying to superpaste the system.journal to show the errors, but it will not.
I cannot cut and paste.
What is the best way to get that info to you?

What exactly happens when you try?

I cannot cut and paste.
Why not?

What is the best way to get that info to you?
Command output can be redirected to a file, and the file copied someplace from where you can copy and paste, or use susepaste to upload.

If it helps

Xorg.0.log
https://susepaste.org/8268025

snapper.log
https://susepaste.org/39825919

boot.log
https://susepaste.org/13543742

zypper.log

won’t susepaste, Paste failed :frowning:
saved it as a .txt file and it does the same.

zypper.log tends to be gargantuan, rarely small enough to be accepted by susepaste. Besides, /var/log/zypp/history is much easier to work with trying to discern what got installed or removed when.

The snapper log seems to be indicating you last did a full upgrade in May, 6 months ago, not a good schedule for reliable TW use.

Xorg.0.log seems fine until at some point

(EE) dbus-core: error connecting to system bus: org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory)

starts repeating. I suspect your system was last fully upgraded prior to the /usr/merge (which I think happened right after your last zypper dup in May), and the packages added since then are assuming a seriously altered filesystem that isn’t yet present, which makes your installation corrupt. I doubt this installation is fixable by any method other than zypper dup, and possibly not at all. I suppose you may have a good snapshot to go back to, in which case enabling it, followed by zypper dup, would be your best way forward.

Additional info
It will log into emergency mode.
journalctl -There is a long list of errors, below are those in yellow or red.

Nov 29 15:42:08 localhost kernel: Linux version 5.15.3-1-default (geeko@buildhost) (gcc (SUSE Linux) 11.2.1 20210816 [revision 0>
Nov 29 15:42:08 localhost kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Address but zero Length>
Nov 29 15:42:08 localhost kernel: ACPI BIOS Warning (bug): Invalid length for FADT/Pm2ControlBlock: 0, using default 8 (20210730>
Nov 29 15:42:08 localhost kernel: pmd_set_huge: Cannot satisfy [mem 0xf4000000-0xf4200000] with a huge-page mapping due to MTRR override.
Nov 29 15:42:08 localhost kernel: acpi LNXCPU:00: Invalid PBLK length [7]
Nov 29 15:42:08 localhost kernel: acpi LNXCPU:01: Invalid PBLK length [7]
Nov 29 15:42:08 localhost kernel: acpi LNXCPU:02: Invalid PBLK length [7]
Nov 29 15:42:08 localhost kernel: acpi LNXCPU:03: Invalid PBLK length [7]
Nov 29 15:42:08 localhost kernel: ACPI BIOS Error (bug): \_SB.PCI0._OSC: Excess arguments - ASL declared 5, ACPI requires 4 (20210730/nsarguments-162)
Nov 29 15:42:08 localhost kernel: ACPI BIOS Error (bug): Failure creating named object \_SB.PCI0._OSC.CAPD], AE_ALREADY_EXISTS (20210730/dsfield-184)
Nov 29 15:42:08 localhost kernel: ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20210730/dswload2-477)
Nov 29 15:42:08 localhost kernel: ACPI Error: Aborting method \_SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (20210730/psparse-529)
Nov 29 15:42:08 localhost kernel: ima: Error Communicating to TPM chip
Nov 29 15:42:08 localhost kernel: ima: Error Communicating to TPM chip
Nov 29 15:42:08 localhost kernel: ima: Error Communicating to TPM chip
Nov 29 15:42:08 localhost kernel: ima: Error Communicating to TPM chip
Nov 29 15:42:08 localhost kernel: ima: Error Communicating to TPM chip
Nov 29 15:42:08 localhost kernel: ima: Error Communicating to TPM chip
Nov 29 15:42:08 localhost kernel: ima: Error Communicating to TPM chip
Nov 29 15:42:08 localhost kernel: ima: Error Communicating to TPM chip
Nov 29 15:42:08 localhost systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Nov 29 15:42:08 localhost kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
Nov 29 15:42:10 localhost kernel: ata3.01: supports DRM functions and may not be fully accessible
Nov 29 15:42:10 localhost kernel: ata3.01: supports DRM functions and may not be fully accessible
Nov 29 15:42:12 localhost systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a>
Nov 29 21:42:13 localhost systemd[1]: /usr/lib/systemd/system/plymouth-start.service:15: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
Nov 29 21:42:13 localhost kernel: FAT-fs (sdc2): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Nov 29 21:42:14 localhost kernel: nvidia: loading out-of-tree module taints kernel.
Nov 29 21:42:14 localhost kernel: nvidia: module license 'NVIDIA' taints kernel.
Nov 29 21:42:14 localhost kernel: Disabling lock debugging due to kernel taint
Nov 29 21:42:14 localhost systemd[1]: plymouth-start.service: Found left-over process 320 (plymouthd) in control group while starting unit. Ignoring.
Nov 29 21:42:14 localhost systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Nov 29 21:42:14 localhost kernel: NVRM: The NVIDIA GeForce GT 610 GPU installed in this system is
                                  NVRM:  supported through the NVIDIA 390.xx Legacy drivers. Please
                                  NVRM:  visit http://www.nvidia.com/object/unix.html for more
                                  NVRM:  information.  The 470.86 NVIDIA driver will ignore
                                  NVRM:  this GPU.  Continuing probe...
Nov 29 21:42:14 localhost kernel: NVRM: ignoring the legacy GPU 0000:20:00.0
Nov 29 21:42:14 localhost kernel: nvidia: probe of 0000:20:00.0 failed with error -1
Nov 29 21:42:14 localhost kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  470.86  Tue Oct 26 21:55:45 UTC 2021
Nov 29 21:42:14 localhost kernel: nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint.
Nov 29 21:42:15 localhost kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than pnp 00:0a [mem 0x000d0a00-0x000e3fff]
Nov 29 21:42:15 localhost kernel: caller _nv000722rm+0x1ad/0x200 [nvidia] mapping multiple BARs
Nov 29 21:42:18 localhost accounts-daemon[1299]: g_dbus_interface_skeleton_get_object_path: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Nov 29 21:42:19 localhost systemd-xdg-autostart-generator[1336]: Not generating service for XDG autostart app-xapp\x2dsn\x2dwatcher@autostart.service, error parsing Exec= line: No such file or directory
Nov 29 21:42:27 localhost lightdm[1378]: gkr-pam: unable to locate daemon control file
Nov 29 21:42:27 localhost systemd-xdg-autostart-generator[1408]: Not generating service for XDG autostart app-xapp\x2dsn\x2dwatcher@autostart.service, error parsing Exec= line: No such file or directory
Nov 29 21:42:29 localhost udisksd[1665]: Can't load configuration file /etc/udisks2/udisks2.conf
Nov 29 21:42:30 localhost /hp-upgrade[1679]: hp-upgrade[1679]: error: HPLIP upgrade is disabled by openSUSE for security reasons, see https://bugzilla.suse.com/show_bug.cgi?id=853405 - if you like to upgrade HPLIP, use an openSUSE software package manager like YaST or zypper.
Nov 29 21:42:30 localhost lxqt-panel[1579]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.46'
Nov 29 21:42:30 localhost pcmanfm-qt[1573]: libpng warning: iCCP: known incorrect sRGB profile
Nov 29 21:42:54 localhost.localdomain pulseaudio[1608]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Nov 29 21:43:14 localhost.localdomain systemd-udevd[601]: 3-3: Spawned process '/usr/bin/hp-firmware -s 003:002' [617] is taking longer than 59s to complete
Nov 29 21:43:14 localhost.localdomain systemd-udevd[498]: 3-3: Worker [601] processing SEQNUM=2245 is taking a long time
Nov 29 21:43:15 localhost.localdomain /hp-firmware[617]: hp-firmware[617]: error: Device hp:/usb/HP_LaserJet_3390?serial=00CNRJR03861 does not support or require firmware download.
Nov 29 21:43:15 localhost.localdomain systemd-udevd[601]: 3-3: Process '/usr/bin/hp-firmware -s 003:002' failed with exit code 1.
Nov 29 21:43:15 localhost.localdomain colord[1149]: CdMain: failed to emit DeviceAdded: failed to register object: An object is already exported for the interface org.freedesktop.ColorManager.Device at /org/freedesktop/ColorManager/devices/sysfs_Hewlett_Packard_HP_LaserJet_3390
Nov 29 21:48:31 localhost.localdomain sudo[2144]: gkr-pam: unable to locate daemon control file

plus 40 lines of:
9.700437] nouveau 0000:20.00.0: bus: MMIO write of 00000000 FAULT at 103ff4 PRIVRING ]
All the same except the first bracketed numbers

Again, random portions of Xorg.0.log are rarely helpful, as with this latest comment #13 excerpt. One of the first several lines in Xorg.0.log is routinely crucial.

Thanks,
I was doing that last dig before I saw your note. That really stinks. It was running perfect then crash after that install. It was my backup safety installation is why it hadn’t been updated in a while. I will try to get to a zypper, but in emergency mode it doesn’t want to let me connect to the internet. May have to reinstall.

For the primary installation partitian, I have a couple of questions all having to do with a crappy nvidia update from the last zypper dup couple of weeks ago.

The browsers no longer show any graphics, just and error message saying it could not display the web page.
The only one that works is Falkon or Firefox.

I also have two video cards. One is running three monitors, the other is running the tv as an entertainment monitor.
After that nvidia crud the card to the tv is no longer being seen. Before the backup installation shot craps, it was working there, so the card and cables are physically working.

this is in running cinnamon as well as in lxqt.

I am tired of messing with the nvidia, is there a decent option these days when using nvidia display cards? If so, how would I make that change?

Should this be a new post, or can it continue here?

thanks.

Have you ever tried not using NVidia’s drivers on this hardware configuration?

I have several NVidia cards roughly similar in age to yours, but only ever one at a time, and only ever with at most two displays at a time. All work just fine automagically on the upstream default FOSS display driver, named modesetting. Without xf86-video-nouveau or NVidia’s proprietary drivers installed, it should be used automatically. I do find three displays at a time working just fine on the very same modesetting display driver on 3 PCs with Intel IGP graphics. Switching to the modesetting should be a simple matter of fully eradicating the NVidia drivers and all its consequential remnants. If you find yourself doing a fresh installation, why not try not installing NVidia’s drivers and see how it works for you?

I am interested in the modesetting option you mention. I see on the Software search, the unofficial versions available are for 13.3 and lower. Is there a 15.x version available? Is it an option in the 15.3 installation?

You cannot not have the modesetting DIX display driver installed, unless you don’t have X installed. You can only use it or not, as it’s provided by/with the Xorg server. This primer explains.

I got a pair of old NVidia cards both working at the same time using only default X settings:

# inxi -Sy
System:
  Host: ga970 Kernel: 5.3.18-59.34-default x86_64 bits: 64
  Desktop: Trinity R14.0.11 Distro: **openSUSE Leap 15.3**
# inxi -Gayz
Graphics:
  Device-1: NVIDIA GF108 [GeForce GT 630] vendor: Gigabyte driver: nouveau
  v: kernel bus-ID: 01:00.0 chip-ID: 10de:0f00 class-ID: 0300
  Device-2: NVIDIA G84 [GeForce 8600 GT] vendor: XFX Pine driver: nouveau
  v: kernel bus-ID: 05:00.0 chip-ID: 10de:0402 class-ID: 0300
  Display: x11 server: X.Org 1.20.3 driver: loaded: modesetting
  unloaded: fbdev,vesa alternate: nouveau,nv,nvidia display-ID: :0 screens: 1
  **Screen**-1: 0 s-res: **6400x1200** s-dpi: 120 s-size: 1354x254mm (53.3x10.0")
  s-diag: 1378mm (54.2")
  Monitor-1: DVI-I-2 res: 1920x1200 hz: 60 dpi: 94
  size: 519x324mm (20.4x12.8") diag: 612mm (24.1")
  Monitor-2: DVI-I-3 res: 2560x1080 hz: 60 dpi: 97
  size: 673x284mm (26.5x11.2") diag: 730mm (28.8")
  Monitor-3: **HDMI**-1-1 res: **1920x1080** hz: 60 dpi: 70
  size: 700x390mm (27.6x15.4") diag: 801mm (31.5")
  OpenGL: renderer: NV84 v: 3.3 Mesa 20.2.4 direct render: Yes
# xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
**Screen** 0: minimum 320 x 200, current **6400 x 1200**, maximum 8192 x 8192
HDMI-1-1 connected 1920x1080+4480+0 (normal left inverted right x axis y axis) 700mm x 390mm
DVI-I-3 connected 2560x1080+1920+0 (normal left inverted right x axis y axis) 673mm x 284mm
DVI-I-2 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 519mm x 324mm
   2560x1080     60.00*+
   1920x1200     59.95*+
   1920x1080     60.00*+  60.00    50.00    59.94    59.93
#

I didn’t actually have to do anything to make this work. All I had to do was plug the cards in the right slots, and not have any optional display drivers installed. This is the resulting Xorg.0.log.

It’s not so simple in TW on same PC using otherwise same settings (e.g.: only defaults). So far I have yet to determine how to get the #2 GPU to show up as a usable provider in TW:

## TW 20211128
# xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x42; cap: 0x2 (Sink Output); crtcs: 2; outputs: 2; associated providers: 0; name: modesetting
    output DVI-I-2
    output DVI-I-3
Provider 1: id: 0xdb; cap: 0x2 (Sink Output); crtcs: 2; outputs: 3; associated providers: 0; name: modesetting
    output 0xd8
    output 0xd9
    output 0xda
## 15.3
# xrandr --listproviders
Providers: number : 2
Provider 0: id: 0xec; cap: 0xf (Source Output, Sink Output, Source Offload, Sink Offload); crtcs: 2; outputs: 2; associated providers: 1; name: modesetting
    output DVI-I-2
    output DVI-I-3
Provider 1: id: 0x44; cap: 0xf (Source Output, Sink Output, Source Offload, Sink Offload); crtcs: 2; outputs: 3; associated providers: 1; name: modesetting
    output DVI-I-1-1
    output HDMI-1-1
    output VGA-1-1