[Testing Update] 2016-10-02 - Kernels, Manjaro Tools, Deepin, NM, LibreOffice, Steam

update
testing

#7

I had the same issue and the only package the file belonged to was cuda. First I uninstalled cuda, but couldn’t reinstall it with the newer version as the file still existed, for whatever reason. After deleting it manually, the update went fine.


#8

Good to know I can find it out that way. It was just a link that pointed to a file in the same location and the CUDA update remade the entire folder also.


#9

why do we have so many steam options? its confusing. What’s the difference between steam-manjaro and steam-native?


#10

Sorry to interrupt the discussion:

Kernel 4.8 rc8 up and running without crash the last 8 hours.
Seems the problem with libsata (or whatever) has been solved.


#11

I posted about an issue with the Nvidia legacy drivers-304.132-1 a week ago in an old testing thread, because there is no current unstable thread. I don’t know if you read it or not, but I’ll repeat here for the same reason. After installing them X won’t start properly. After booting plymouth finishes, but X fails to initialize, leaving only a blank screen on TTY1. The only way for me to recover is to switch to a VT on another TTY and downgrade back to the last release. I’ve checked the configuration files and they appear to be OK. Any help I can give in solving I’ll be happy to provide. TIA


#12

@Odysseus: Try to install dbus-x11 and check if that fixes your issue …


#13

Here some info about the Steam-Clients:

  • steam-manjaro: is our definition of the steam client. It uses patches our community defined. Latest patch included is this one FS#45.
  • steam-native: is our definition addon for the steam client, which uses the native libs provided by Manjaro. Not all games work with that option
  • steam: is Arch’s definition of the steam client
  • steam-native-runtime: is Arch’s definition and addon on how the provided libs should be used. Both versions got heavy updates lately. A new set of updates can be expected soon with linux48 final

#14

Thanks for your response, but this can’t be the issue. I installed dbus-x11 when you first introduced it into the unstable repo a few weeks ago, so it must be something else.


#15

@Odysseus: do you have any metamodes activated in your nvidia.conf? If so, please comment them and check if that fixes it. Maybe the ForceFullCompositionPipeline issue got backported to that legacy driver. From the changelog however I can’t see no indication for this …


#16

Thanks again for your quick response. I did have a metmodes line in my nvidia.conf which reads: Option “metamodes” “1440x900_60 +0+0” so I commented out then installed the latest drivers you just introduced today. No luck, still a black screen on tty1.

I do know some of X is functional because keyboard hot keys I’ve configured to kill the X server are working. If I Ctrl+Alt+Backspace I can see the X server killed then attempting to restart back to the black screen.

I’ve examined the Xorg0.log from the older drivers which successfully load and the Xorg0.log.old from when they didn’t load and everything seems normal and the same until the last few lines.

With the older drivers from line 270 onward it looks like this:

[    20.523] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 11)
[    20.523] (**) Option "xkb_rules" "evdev"
[    20.523] (**) Option "xkb_model" "precision_m"
[    20.523] (**) Option "xkb_layout" "us"
[    20.523] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[    51.592] (II) NVIDIA(GPU-0): Display (Seiko/Epson (DFP-0)) does not support NVIDIA 3D
[    51.592] (II) NVIDIA(GPU-0):     Vision stereo.
[    51.592] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    51.592] (**) NVIDIA(0):     device Seiko/Epson (DFP-0) (Using EDID frequencies has
[    51.592] (**) NVIDIA(0):     been enabled on all display devices.)
[    61.064] (II) NVIDIA(GPU-0): Display (Seiko/Epson (DFP-0)) does not support NVIDIA 3D
[    61.064] (II) NVIDIA(GPU-0):     Vision stereo.
[    61.064] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[    61.064] (**) NVIDIA(0):     device Seiko/Epson (DFP-0) (Using EDID frequencies has
[    61.064] (**) NVIDIA(0):     been enabled on all display devices.)

With the newer drivers which are failing to load that section looks like this:
[    20.573] (**) Option "config_info" "udev:/sys/devices/virtual/input/input9/event8"
[    20.573] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 11)
[    20.573] (**) Option "xkb_rules" "evdev"
[    20.573] (**) Option "xkb_model" "precision_m"
[    20.573] (**) Option "xkb_layout" "us"
[    20.573] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
[   143.339] (II) evdev: Dell WMI hotkeys: Close
[   143.339] (II) UnloadModule: "evdev"
[   143.339] (II) UnloadModule: "synaptics"
[   143.339] (II) evdev: AT Translated Set 2 keyboard: Close
[   143.339] (II) UnloadModule: "evdev"
[   143.339] (II) evdev: Sleep Button: Close
[   143.339] (II) UnloadModule: "evdev"
[   143.339] (II) evdev: Power Button: Close
[   143.340] (II) UnloadModule: "evdev"
[   143.340] (II) evdev: Video Bus: Close
[   143.340] (II) UnloadModule: "evdev"
[   143.417] (II) Server terminated successfully (0). Closing log file.

My interpretation is the older drivers are successfully loading and detecting the EDID of my screen then configuring it properly, where the newer ones aren’t, hence the black screen.

Is there any other log file I should be checking, so we can try to find a resolution? TIA

Edit: To further confirm that some parts of X are loading, I renamed and moved my nvidia.conf file in /etc/X11/mhwd.d then created an xorg.conf file with the nvidia-config tool. Upon X attempting to restart I now see the Nvidia splash screen before the screen goes black.

So then I again reinstalled the older properly working drivers, then restored the configuration I had backed-up. So I’m back on the older drivers now, but have a properly working system again. So something is definitely amiss with these latest drivers too.


#17

Phil I searched around the net and found a few pages which may explain what is going on, but I don’t have the time to look into myself. So unfortunately, I’m still stuck on the older 304.131 legacy drivers.

A couple of things to look into. Over at the Puppy linux forums they pointed out that the driver needs to have an mtrr patch run to get this older driver to load on newer kernels (This is only required for legacy drivers). http://murga-linux.com/puppy/viewtopic.php?p=890560#890560 and http://www.murga-linux.com/puppy/viewtopic.php?p=925871&sid=6178240d5fce217060b54bb53c7d4204

Over at the nvidia forums I found these threads that may help https://devtalk.nvidia.com/default/topic/968448/linux/304-132-does-not-load-on-kernel-4-7-5-mttr-patch-has-not-been-applied-/ and https://devtalk.nvidia.com/default/topic/968892/linux/geforce-7300le-with-304-132-glxinfo-fails-now-with-quot-x-error-of-failed-request-badvalue-quot-/

Finally, it may not be a driver issue at all. I found this bug over at kde bugzilla: https://www.mail-archive.com/kde-bugs-dist@kde.org/msg81284.html

And I found mentioned over at the nvidia forums that the newer Nvidia drivers have issues with newer versions of X, if X is compiled with the glamour option enabled.

I hope this helps.

Whatever log files that will help to troubleshoot I’ll be happy to provide, just tell me which ones. TIA


#18

Hmm, seems to be indeed a regression …


#19

@Odysseus: what is the output of mhwd? Also the output of hwinfo --gfx might help. Does any other nvidia driver work for your hardware? Regarding mtrr. We export that symbol with one of our kernel patches. The given Debian Patch disables mtrr usage completely. Does the driver work with linux41?


#20

I’ll have to install and check the 41 kernel. I currently use 47 and 44. I’ll try then post back with results.


#21

OK, I tried the 41 kernel, but had the same results only this time plymouth cut off before X loaded so I could see the startup error message. It says Failed kernel module failed to load (I’m assuming thats the Nvidia kernel blob).

Edit: After reading the systemd journal log it seems it was the Dell module controlling my fan, not the nvidia blob.

Output from mhwd from my functioning desktop:
mhwd

0000:01:00.0 (0300:10de:0297) Display controller nVidia Corporation:


              NAME               VERSION          FREEDRIVER           TYPE

video-nvidia-304xx            2016.04.25               false            PCI
     video-nouveau            2016.01.28                true            PCI
          video-nv            2012.09.18                true            PCI
        video-vesa            2012.09.18                true            PCI

Output from hwinfo --gfx (again from my functioning desktop):

hwinfo --gfx
22: PCI 100.0: 0300 VGA compatible controller (VGA)             
  [Created at pci.366]
  Unique ID: VCu0.RGPi+2EIaLB
  Parent ID: vSkL.7WEN2dcNUbD
  SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0
  SysFS BusID: 0000:01:00.0
  Hardware Class: graphics card
  Model: "nVidia G71M [GeForce Go 7950 GTX]"
  Vendor: pci 0x10de "nVidia Corporation"
  Device: pci 0x0297 "G71M [GeForce Go 7950 GTX]"
  SubVendor: pci 0x1028 "Dell"
  SubDevice: pci 0x019b 
  Revision: 0xa1
  Driver: "nvidia"
  Driver Modules: "nvidia"
  Memory Range: 0xed000000-0xedffffff (rw,non-prefetchable)
  Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
  Memory Range: 0xee000000-0xeeffffff (rw,non-prefetchable)
  I/O Ports: 0xef00-0xef7f (rw)
  Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
  IRQ: 16 (4291 events)
  I/O Port: 0x00 (rw)
  Module Alias: "pci:v000010DEd00000297sv00001028sd0000019Bbc03sc00i00"
  Driver Info #0:
    Driver Status: nouveau is not active
    Driver Activation Cmd: "modprobe nouveau"
  Driver Info #1:
    Driver Status: nvidia is active
    Driver Activation Cmd: "modprobe nvidia"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #7 (PCI bridge)

Primary display adapter: #22

I hope this helps


#22

Here is the boot log of the previous failed boot, maybe it’s an issue with plasma or sddm?

journalctl --boot=-1
-- Logs begin at Wed 2016-09-14 03:50:50 EDT, end at Tue 2016-10-04 17:37:53 EDT. --
Oct 04 17:33:43 Precision-M90 systemd-journald[155]: Runtime journal (/run/log/journal/) is 8.0M, max 163.1M, 155.1M free.
Oct 04 17:33:43 Precision-M90 systemd-journald[155]: System journal (/var/log/journal/) is 232.3M, max 3.1G, 2.9G free.
Oct 04 17:33:46 Precision-M90 systemd-journald[155]: Time spent on flushing to /var is 2.626117s for 2 entries.
Oct 04 17:33:46 Precision-M90 kernel: ACPI: RSDP 0x00000000000FC0E0 000014 (v00 DELL  )
Oct 04 17:33:46 Precision-M90 kernel: ACPI: RSDT 0x00000000CFE8818A 000048 (v01 DELL   M07      27D80A10 ASL  00000061)
Oct 04 17:33:46 Precision-M90 kernel: ACPI: FACP 0x00000000CFE89000 000074 (v01 DELL   M07      27D80A10 ASL  00000061)
Oct 04 17:33:46 Precision-M90 kernel: ACPI: DSDT 0x00000000CFE89C00 0051B9 (v01 INT430 SYSFexxx 00001001 INTL 20050624)
Oct 04 17:33:46 Precision-M90 kernel: ACPI: FACS 0x00000000CFE98400 000040
Oct 04 17:33:46 Precision-M90 kernel: ACPI: HPET 0x00000000CFE89700 000038 (v01 DELL   M07      00000001 ASL  00000061)
Oct 04 17:33:46 Precision-M90 kernel: ACPI: APIC 0x00000000CFE89800 000068 (v01 DELL   M07      27D80A10 ASL  00000047)
Oct 04 17:33:46 Precision-M90 kernel: ACPI: ASF! 0x00000000CFE89400 00005B (v16 DELL   M07      27D80A10 ASL  00000061)
Oct 04 17:33:46 Precision-M90 kernel: ACPI: MCFG 0x00000000CFE897C0 00003E (v16 DELL   M07      27D80A10 ASL  00000061)
Oct 04 17:33:46 Precision-M90 kernel: ACPI: SLIC 0x00000000CFE8989C 000176 (v01 DELL   M07      27D80A10 ASL  00000061)
Oct 04 17:33:46 Precision-M90 kernel: ACPI: TCPA 0x00000000CFE89B00 000032 (v01 DELL   M07      27D80A10 ASL  00000061)
Oct 04 17:33:46 Precision-M90 kernel: ACPI: BOOT 0x00000000CFE893C0 000028 (v01 DELL   M07      27D80A10 ASL  00000061)
Oct 04 17:33:46 Precision-M90 kernel: ACPI: SSDT 0x00000000CFE88215 0004DC (v01 PmRef  CpuPm    00003000 INTL 20050624)
Oct 04 17:33:46 Precision-M90 kernel: ACPI: 2 ACPI AML tables successfully acquired and loaded
Oct 04 17:33:46 Precision-M90 kernel: 
Oct 04 17:33:46 Precision-M90 kernel: core: PEBS disabled due to CPU errata
Oct 04 17:33:46 Precision-M90 kernel: TSC synchronization [CPU#0 -> CPU#1]:
Oct 04 17:33:46 Precision-M90 kernel: Measured 11629421412 cycles TSC warp between CPUs, turning off TSC clock.
Oct 04 17:33:46 Precision-M90 kernel: mtrr: your CPUs had inconsistent variable MTRR settings
Oct 04 17:33:46 Precision-M90 kernel: ACPI: Dynamic OEM Table Load:
Oct 04 17:33:46 Precision-M90 kernel: ACPI: SSDT 0xFFFF8800CF48A9C0 000043 (v01 LMPWR  DELLLOM  00001001 INTL 20050624)
Oct 04 17:33:47 Precision-M90 kernel: ACPI: Dynamic OEM Table Load:
Oct 04 17:33:47 Precision-M90 kernel: ACPI: SSDT 0xFFFF8800CF48EC00 000244 (v01 PmRef  Cpu0Ist  00003000 INTL 20050624)
Oct 04 17:33:47 Precision-M90 kernel: ACPI: Dynamic OEM Table Load:
Oct 04 17:33:47 Precision-M90 kernel: ACPI: SSDT 0xFFFF8800CB4FAC00 0001C6 (v01 PmRef  Cpu0Cst  00003001 INTL 20050624)
Oct 04 17:33:47 Precision-M90 kernel: ACPI: Dynamic OEM Table Load:
Oct 04 17:33:47 Precision-M90 kernel: ACPI: SSDT 0xFFFF8800CBB94B00 0000C4 (v01 PmRef  Cpu1Ist  00003000 INTL 20050624)
Oct 04 17:33:47 Precision-M90 kernel: ACPI: Dynamic OEM Table Load:
Oct 04 17:33:47 Precision-M90 kernel: ACPI: SSDT 0xFFFF8800CBB92F00 000085 (v01 PmRef  Cpu1Cst  00003000 INTL 20050624)
Oct 04 17:33:47 Precision-M90 kernel: ACPI: Enabled 3 GPEs in block 00 to 1F
Oct 04 17:33:47 Precision-M90 kernel: pnp 00:01: disabling [io  0x1000-0x1005] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct 04 17:33:47 Precision-M90 kernel: pnp 00:01: disabling [io  0x1008-0x100f] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct 04 17:33:47 Precision-M90 kernel: pnp 00:02: disabling [io  0x1006-0x1007] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct 04 17:33:48 Precision-M90 kernel: pnp 00:02: disabling [io  0x100a-0x1059] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct 04 17:33:48 Precision-M90 kernel: pnp 00:02: disabling [io  0x1060-0x107f] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct 04 17:33:48 Precision-M90 kernel: pnp 00:02: disabling [io  0x1010-0x102f] because it overlaps 0000:00:1f.0 BAR 13 [io  0x1000-0x107f]
Oct 04 17:33:48 Precision-M90 kernel: nvidia: module license 'NVIDIA' taints kernel.                                                 
Oct 04 17:33:48 Precision-M90 kernel: Disabling lock debugging due to kernel taint                                                   
Oct 04 17:33:48 Precision-M90 kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  304.132  Fri Sep 16 11:02:09 PDT 2016          
Oct 04 17:33:48 Precision-M90 kernel: iwl4965 0000:0c:00.0: can't disable ASPM; OS doesn't have ASPM control                         
Oct 04 17:33:50 Precision-M90 systemd-journald[155]: Journal started                                                                 
Oct 04 17:33:48 Precision-M90 systemd-udevd[270]: Process '/usr/bin/set-wireless-regdom' failed with exit code 1.                    
Oct 04 17:33:49 Precision-M90 systemd-udevd[275]: Process '/usr/bin/alsactl restore 0' failed with exit code 99.                     
Oct 04 17:33:49 Precision-M90 systemd-udevd[272]: Process '/usr/bin/tlp auto' failed with exit code 4.                               
Oct 04 17:33:49 Precision-M90 systemd-udevd[268]: Error calling EVIOCSKEYCODE on device node '/dev/input/event8' (scan code 0x150, key code 190): Invalid argument
Oct 04 17:33:53 Precision-M90 bluetoothd[572]: Failed to obtain handles for "Service Changed" characteristic                                                                                              
Oct 04 17:33:53 Precision-M90 bluetoothd[572]: Sap driver initialization failed.                                                                                                                          
Oct 04 17:33:53 Precision-M90 bluetoothd[572]: sap-server: Operation not permitted (1)                                                                                                                    
Oct 04 17:33:57 Precision-M90 kernel: NVRM: Your system is not currently configured to drive a VGA console                                                                                                
Oct 04 17:33:57 Precision-M90 kernel: NVRM: on the primary VGA device. The NVIDIA Linux graphics driver                                                                                                   
Oct 04 17:33:57 Precision-M90 kernel: NVRM: requires the use of a text-mode VGA console. Use of other console                                                                                             
Oct 04 17:33:57 Precision-M90 kernel: NVRM: drivers including, but not limited to, vesafb, may result in                                                                                                  
Oct 04 17:33:57 Precision-M90 kernel: NVRM: corruption and stability problems, and is not supported.                                                                                                      
Oct 04 17:34:01 Precision-M90 sddm-greeter[1445]: inotify_add_watch("/usr/share/wayland-sessions") failed: "No such file or directory"                                                                    
Oct 04 17:34:03 Precision-M90 sddm-greeter[1445]: QObject: Cannot create children for a parent that is in a different thread.                                                                             
                                                  (Parent is SDDM::GreeterApp(0x7ffccaadf250), parent's thread is QThread(0x93de50), current thread is QThread(0xa3e410)
Oct 04 17:34:03 Precision-M90 sddm-greeter[1445]: QObject: Cannot create children for a parent that is in a different thread.
                                                  (Parent is SDDM::GreeterApp(0x7ffccaadf250), parent's thread is QThread(0x93de50), current thread is QThread(0xa3e410)
Oct 04 17:34:03 Precision-M90 sddm-greeter[1445]: QObject: Cannot create children for a parent that is in a different thread.
                                                  (Parent is SDDM::GreeterApp(0x7ffccaadf250), parent's thread is QThread(0x93de50), current thread is QThread(0xa3e410)
Oct 04 17:34:03 Precision-M90 sddm-greeter[1445]: QObject: Cannot create children for a parent that is in a different thread.
                                                  (Parent is SDDM::GreeterApp(0x7ffccaadf250), parent's thread is QThread(0x93de50), current thread is QThread(0xa3e410)
Oct 04 17:34:03 Precision-M90 sddm-greeter[1445]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Oct 04 17:34:03 Precision-M90 sddm-greeter[1445]: QObject: Cannot create children for a parent that is in a different thread.
                                                  (Parent is SDDM::GreeterApp(0x7ffccaadf250), parent's thread is QThread(0x93de50), current thread is QThread(0xa3e410)
Oct 04 17:34:05 Precision-M90 sddm-greeter[1445]: QObject: Cannot create children for a parent that is in a different thread.
                                                  (Parent is SDDM::GreeterApp(0x7ffccaadf250), parent's thread is QThread(0x93de50), current thread is QThread(0xa3e410)
Oct 04 17:34:05 Precision-M90 sddm-greeter[1445]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Oct 04 17:34:07 Precision-M90 sddm-greeter[1445]: QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.15'
Oct 04 17:34:07 Precision-M90 sddm-greeter[1445]: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueB
Oct 04 17:34:08 Precision-M90 sddm[780]: Auth: sddm-helper exited with 6
Oct 04 17:34:08 Precision-M90 systemd-coredump[1491]: Process 1445 (sddm-greeter) of user 995 dumped core.
                                                      
                                                      Stack trace of thread 1445:
                                                      #0  0x00007f5e4422f04f raise (libc.so.6)
                                                      #1  0x00007f5e4423047a abort (libc.so.6)
                                                      #2  0x00007f5e44bcc4a1 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
                                                      #3  0x00007f5e4685cef3 _ZN13QSGRenderLoop28handleContextCreationFailureEP12QQuickWindowb (libQt5Quick.so.5)
                                                      #4  0x00007f5e46864a22 n/a (libQt5Quick.so.5)
                                                      #4  0x00007f5e46864a22 n/a (libQt5Quick.so.5)
                                                      #5  0x00007f5e46864e03 n/a (libQt5Quick.so.5)
                                                      #6  0x00007f5e45319e15 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5)
                                                      #7  0x00007f5e4689a883 _ZN12QQuickWindow5eventEP6QEvent (libQt5Quick.so.5)
                                                      #8  0x00007f5e44dbfc7a _ZN16QCoreApplication6notifyEP7QObjectP6QEvent (libQt5Core.so.5)
                                                      #9  0x00007f5e44dbfde0 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
                                                      #10 0x00007f5e4530f2ed _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5)
                                                      #11 0x00007f5e4530fefd _ZN22QGuiApplicationPrivate24processWindowSystemEventEPN29QWindowSystemInterfacePrivate17WindowSystemEventE (libQt5Gui.so.5)
                                                      #12 0x00007f5e452edcab _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5)
                                                      #13 0x00007f5e3af302f0 n/a (libQt5XcbQpa.so.5)
                                                      #14 0x00007f5e40728e67 g_main_context_dispatch (libglib-2.0.so.0)
                                                      #15 0x00007f5e407290d0 n/a (libglib-2.0.so.0)
                                                      #16 0x00007f5e4072917c g_main_context_iteration (libglib-2.0.so.0)
                                                      #17 0x00007f5e44e1470f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
                                                      #18 0x00007f5e44dbe23a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
                                                      #19 0x00007f5e44dc673c _ZN16QCoreApplication4execEv (libQt5Core.so.5)
                                                      #20 0x000000000041629f main (sddm-greeter)
                                                      #21 0x00007f5e4421c291 __libc_start_main (libc.so.6)
                                                      #22 0x00000000004163ca _start (sddm-greeter)
                                                      
                                                      Stack trace of thread 1447:
                                                      #0  0x00007f5e442db48d poll (libc.so.6)
                                                      #1  0x00007f5e40729066 n/a (libglib-2.0.so.0)
                                                      #2  0x00007f5e4072917c g_main_context_iteration (libglib-2.0.so.0)
                                                      #3  0x00007f5e44e1470f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
                                                      #4  0x00007f5e44dbe23a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
                                                      #5  0x00007f5e44be10f3 _ZN7QThread4execEv (libQt5Core.so.5)
                                                      #6  0x00007f5e45f822d5 n/a (libQt5Qml.so.5)
                                                      #7  0x00007f5e44be5d78 n/a (libQt5Core.so.5)
                                                      #8  0x00007f5e41727754 n/a (libGL.so.1)
                                                      #9  0x00007f5e4295a454 start_thread (libpthread.so.0)
                                                      #10 0x00007f5e442e47df __clone (libc.so.6)
                                                      
                                                      Stack trace of thread 1446:
                                                      #0  0x00007f5e442db48d poll (libc.so.6)
                                                      #1  0x00007f5e464d58e0 n/a (libxcb.so.1)
                                                      #2  0x00007f5e464d7679 xcb_wait_for_event (libxcb.so.1)
                                                      #3  0x00007f5e3aefa449 n/a (libQt5XcbQpa.so.5)
                                                      #4  0x00007f5e44be5d78 n/a (libQt5Core.so.5)
                                                      #5  0x00007f5e41727754 n/a (libGL.so.1)
                                                      #6  0x00007f5e4295a454 start_thread (libpthread.so.0)
                                                      #7  0x00007f5e442e47df __clone (libc.so.6)
                                                      
                                                      Stack trace of thread 1448:
                                                      #0  0x00007f5e442db48d poll (libc.so.6)
                                                      #1  0x00007f5e40729066 n/a (libglib-2.0.so.0)
                                                      #2  0x00007f5e4072917c g_main_context_iteration (libglib-2.0.so.0)
                                                      #3  0x00007f5e44e1470f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5)
                                                      #4  0x00007f5e44dbe23a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
                                                      #5  0x00007f5e44be10f3 _ZN7QThread4execEv (libQt5Core.so.5)
                                                      #6  0x00007f5e38b50e55 n/a (libQt5DBus.so.5)
                                                      #7  0x00007f5e44be5d78 n/a (libQt5Core.so.5)
                                                      #8  0x00007f5e41727754 n/a (libGL.so.1)
                                                      #9  0x00007f5e4295a454 start_thread (libpthread.so.0)
                                                      #10 0x00007f5e442e47df __clone (libc.so.6)
Oct 04 17:34:24 Precision-M90 NetworkManager[571]: <warn>  [1475616864.8490] device (wlp12s0): No agents were available for this request.
Oct 04 17:34:24 Precision-M90 NetworkManager[571]: <warn>  [1475616864.8495] device (wlp12s0): Activation: failed for connection 'HOME-0242_EXT'
Oct 04 17:35:32 Precision-M90 sddm[780]: Signal received: SIGTERM
Oct 04 17:35:35 Precision-M90 kernel: watchdog: watchdog0: watchdog did not stop!
Oct 04 17:35:35 Precision-M90 systemd-journald[155]: Journal stopped

#23

Please download the XFCE development build and simply boot it up. It includes the current Nvidia 304.xx driver. Maybe that will exclude the issue you currently face with KDE and might narrow it down. linux44 is used with this ISO.


#24

@philm Thanks again for responding. I downloaded, burned, and tried out the new ISO, but unfortunately, with the same results. I can get to the desktop with the free nouveau drivers, but with the non-free nvidia-drivers it’s the same as with my current system. A blank screen on tty1, when plymouth finishes. So this is definitely not KDE/Plasma related, it’s some kind of regression with the new 304.xxx drivers and my Nvidia 7950GTX Go GPU. :sob: :sob: :sob:


#25

I think it can be the same problem than me. steam alone (not steam-manjaro) must work also, if yes.


#26