Hi all,
I just dup'ed my machine today as well and ran into an issue I believe a bunch of users ran into already.
GDM fails to show the greeter with the all famous 'oh no! something has gone wrong' error message.
I could track it down to /dev/nvidiactl: the gdm greeter seems not to have sufficient permissions to access this device, causing the error.
/dev/nvidiactl is created as crw-rw---- root:video; which obviously is not matching the gdm user's permission.
As a quick workaround I just added user 'gdm' to the group 'video', which helped over the problem, but I'm wondering why this would have started to happen now?
Dominique
PS: No, no bugreport created yet.
On Sat, 2011-10-22 at 23:42 +0200, Dimstar / Dominique Leuenberger wrote:
Hi all,
I just dup'ed my machine today as well and ran into an issue I believe a bunch of users ran into already.
GDM fails to show the greeter with the all famous 'oh no! something has gone wrong' error message.
I could track it down to /dev/nvidiactl: the gdm greeter seems not to have sufficient permissions to access this device, causing the error.
/dev/nvidiactl is created as crw-rw---- root:video; which obviously is not matching the gdm user's permission.
As a quick workaround I just added user 'gdm' to the group 'video', which helped over the problem, but I'm wondering why this would have started to happen now?
Dominique
PS: No, no bugreport created yet.
in /etc/modprobe.d/50-nvidia.conf change options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660
to options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0666
On Sun, 23 Oct 2011 15:10:48 +0200 Juergen Orschiedt jorschiedt@web.de wrote:
On Sat, 2011-10-22 at 23:42 +0200, Dimstar / Dominique Leuenberger wrote:
Hi all,
I just dup'ed my machine today as well and ran into an issue I believe a bunch of users ran into already.
GDM fails to show the greeter with the all famous 'oh no! something has gone wrong' error message.
I could track it down to /dev/nvidiactl: the gdm greeter seems not to have sufficient permissions to access this device, causing the error.
/dev/nvidiactl is created as crw-rw---- root:video; which obviously is not matching the gdm user's permission.
As a quick workaround I just added user 'gdm' to the group 'video', which helped over the problem, but I'm wondering why this would have started to happen now?
Dominique
PS: No, no bugreport created yet.
in /etc/modprobe.d/50-nvidia.conf change options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660
to options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0666
Hi But this still doesn't account for the change. I had 11.4 with 3.0.2 and all was fine logging in/out. I've now updated the same system running the same nvidia with the original conf file to gnome-shell 3.2.0 and now I have the 'oh no' screen when trying to login/logout.
Il giorno dom, 23/10/2011 alle 10.18 -0500, Malcolm ha scritto:
On Sun, 23 Oct 2011 15:10:48 +0200 Juergen Orschiedt jorschiedt@web.de wrote:
On Sat, 2011-10-22 at 23:42 +0200, Dimstar / Dominique Leuenberger wrote:
Hi all,
I just dup'ed my machine today as well and ran into an issue I believe a bunch of users ran into already.
GDM fails to show the greeter with the all famous 'oh no! something has gone wrong' error message.
I could track it down to /dev/nvidiactl: the gdm greeter seems not to have sufficient permissions to access this device, causing the error.
/dev/nvidiactl is created as crw-rw---- root:video; which obviously is not matching the gdm user's permission.
As a quick workaround I just added user 'gdm' to the group 'video', which helped over the problem, but I'm wondering why this would have started to happen now?
Dominique
PS: No, no bugreport created yet.
in /etc/modprobe.d/50-nvidia.conf change options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660
to options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0666
Hi But this still doesn't account for the change. I had 11.4 with 3.0.2 and all was fine logging in/out. I've now updated the same system running the same nvidia with the original conf file to gnome-shell 3.2.0 and now I have the 'oh no' screen when trying to login/logout.
-- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 11.4 (x86_64) Kernel 2.6.37.6-0.7-desktop up 15:31, 4 users, load average: 0.09, 0.09, 0.19 GPU GeForce 8600 GTS Silent - Driver Version: 285.05.09
Hello,
Just to add a personal feedback on the issue.
I'm using 12.1 RC1 64 bits, derived by various Milestones upgrades, obtained by "zypper dup" which I installed as virtual machine (VirtualBox 4.1.4).
Previously all the attempts to boot always failed due the fact 12.1 boot default was systemd so I switched to sysv and finally system booted ok, but only to console login, no graphical.
Then I edited /etc/permission.local and uncomment the line
"/usr/bin/Xorg" obtaining X finally starting but only if I login as root or by using "sudo startx".
Currently I edited /etc/sysconfig/windowmanager to use "kde" and /etc/sysconfig/displaymanager to use "gdm"
Now I can login both into GNOME or KDE, without problems.
Cheers,
On Sat, 2011-10-22 at 23:42 +0200, Dimstar / Dominique Leuenberger wrote:
Hi all,
I just dup'ed my machine today as well and ran into an issue I believe a bunch of users ran into already.
GDM fails to show the greeter with the all famous 'oh no! something has gone wrong' error message.
I could track it down to /dev/nvidiactl: the gdm greeter seems not to have sufficient permissions to access this device, causing the error.
/dev/nvidiactl is created as crw-rw---- root:video; which obviously is not matching the gdm user's permission.
As a quick workaround I just added user 'gdm' to the group 'video', which helped over the problem, but I'm wondering why this would have started to happen now?
Dominique
Apparently more users start seeing this now as well, see https://bugzilla.novell.com/show_bug.cgi?id=728259
How was the permission on that device handled in the past? What changed and why did we loose it?
I'm very tempted of flagging that issue as a blocker, as a big part of nvidia users will be affected by this.
Dominique
Le vendredi 04 novembre 2011 à 10:53 +0100, Dimstar / Dominique Leuenberger a écrit :
On Sat, 2011-10-22 at 23:42 +0200, Dimstar / Dominique Leuenberger wrote:
Hi all,
I just dup'ed my machine today as well and ran into an issue I believe a bunch of users ran into already.
GDM fails to show the greeter with the all famous 'oh no! something has gone wrong' error message.
I could track it down to /dev/nvidiactl: the gdm greeter seems not to have sufficient permissions to access this device, causing the error.
/dev/nvidiactl is created as crw-rw---- root:video; which obviously is not matching the gdm user's permission.
As a quick workaround I just added user 'gdm' to the group 'video', which helped over the problem, but I'm wondering why this would have started to happen now?
Dominique
Apparently more users start seeing this now as well, see https://bugzilla.novell.com/show_bug.cgi?id=728259
How was the permission on that device handled in the past? What changed and why did we loose it?
I'm very tempted of flagging that issue as a blocker, as a big part of nvidia users will be affected by this.
Looks like ACL aren't set to nvidia devices, unlike drm "classic" device :
70-uaccess.rules:SUBSYSTEM=="drm", KERNEL=="card*", TAG+="uaccess" 70-udev-acl.rules:SUBSYSTEM=="drm", KERNEL=="card*", TAG+="udev-acl"
there is no similar rule for nvidia.
On Fri, Nov 04, 2011 at 10:59:23AM +0100, Frederic Crozat wrote:
Le vendredi 04 novembre 2011 à 10:53 +0100, Dimstar / Dominique Leuenberger a écrit :
On Sat, 2011-10-22 at 23:42 +0200, Dimstar / Dominique Leuenberger wrote:
Hi all,
I just dup'ed my machine today as well and ran into an issue I believe a bunch of users ran into already.
GDM fails to show the greeter with the all famous 'oh no! something has gone wrong' error message.
I could track it down to /dev/nvidiactl: the gdm greeter seems not to have sufficient permissions to access this device, causing the error.
/dev/nvidiactl is created as crw-rw---- root:video; which obviously is not matching the gdm user's permission.
/etc/modprobe.d/50-nvidia.conf: options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660
Add gdm to video group. ;-) I didn't see such an issue with KDE/kdm. What has changed in kdm?
As a quick workaround I just added user 'gdm' to the group 'video', which helped over the problem, but I'm wondering why this would have started to happen now?
Dominique
Apparently more users start seeing this now as well, see https://bugzilla.novell.com/show_bug.cgi?id=728259
How was the permission on that device handled in the past? What changed and why did we loose it?
I'm very tempted of flagging that issue as a blocker, as a big part of nvidia users will be affected by this.
Looks like ACL aren't set to nvidia devices, unlike drm "classic" device :
70-uaccess.rules:SUBSYSTEM=="drm", KERNEL=="card*", TAG+="uaccess" 70-udev-acl.rules:SUBSYSTEM=="drm", KERNEL=="card*", TAG+="udev-acl"
there is no similar rule for nvidia.
No idea, what would be required. And if it's possible with NVIDIA at all. But NVIDIA/fglrx RPMs won't work anyway with RC2 becoming the final release due to bnc #619218 ...
Thanks, Stefan
Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) --------------------------------------------------------------
On Friday 04 November 2011 11:35:14 Stefan Dirsch wrote:
Add gdm to video group. ;-) I didn't see such an issue with KDE/kdm. What has changed in kdm?
kdm runs as root, doesn't it?
Anders
On Fri, 2011-11-04 at 11:40 +0100, Anders Johansson wrote:
On Friday 04 November 2011 11:35:14 Stefan Dirsch wrote:
Add gdm to video group. ;-) I didn't see such an issue with KDE/kdm. What has changed in kdm?
kdm runs as root, doesn't it?
Still? We even got X no longer running as root... that would sound rather strange to have kdm suid in this case then (but it would explain why this is no issue).
Dominique
On 11/04/2011 11:52 AM, Dimstar / Dominique Leuenberger wrote:
On Fri, 2011-11-04 at 11:40 +0100, Anders Johansson wrote:
On Friday 04 November 2011 11:35:14 Stefan Dirsch wrote:
Add gdm to video group. ;-) I didn't see such an issue with KDE/kdm. What has changed in kdm?
kdm runs as root, doesn't it?
Still? We even got X no longer running as root... that would sound rather strange to have kdm suid in this case then (but it would explain why this is no issue).
root 3134 0.0 0.0 28844 816 ? Ss 11:08 0:00 /usr/bin/kdm
so its still running as root.
On Fri, Nov 04, 2011 at 11:40:39AM +0100, Anders Johansson wrote:
On Friday 04 November 2011 11:35:14 Stefan Dirsch wrote:
Add gdm to video group. ;-) I didn't see such an issue with KDE/kdm. What has changed in kdm?
That should read: "What has changed in *g*dm?"
kdm runs as root, doesn't it?
Yes.
Thanks, Stefan
Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) --------------------------------------------------------------
Le vendredi 04 novembre 2011 à 11:57 +0100, Stefan Dirsch a écrit :
On Fri, Nov 04, 2011 at 11:40:39AM +0100, Anders Johansson wrote:
On Friday 04 November 2011 11:35:14 Stefan Dirsch wrote:
Add gdm to video group. ;-) I didn't see such an issue with KDE/kdm. What has changed in kdm?
That should read: "What has changed in *g*dm?"
gdm is now trying to use gl acceleration (if available), from GNOME Shell.
On Fri, Nov 04, 2011 at 12:33:08PM +0100, Frederic Crozat wrote:
Le vendredi 04 novembre 2011 à 11:57 +0100, Stefan Dirsch a écrit :
On Fri, Nov 04, 2011 at 11:40:39AM +0100, Anders Johansson wrote:
On Friday 04 November 2011 11:35:14 Stefan Dirsch wrote:
Add gdm to video group. ;-) I didn't see such an issue with KDE/kdm. What has changed in kdm?
That should read: "What has changed in *g*dm?"
gdm is now trying to use gl acceleration (if available), from GNOME Shell.
Thanks. This explains the changed behaviour in gdm.
Best regards, Stefan
Public Key available ------------------------------------------------------ Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0 Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.de Germany -------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) --------------------------------------------------------------
Le vendredi 04 novembre 2011, à 11:35 +0100, Stefan Dirsch a écrit :
On Fri, Nov 04, 2011 at 10:59:23AM +0100, Frederic Crozat wrote:
Le vendredi 04 novembre 2011 à 10:53 +0100, Dimstar / Dominique Leuenberger a écrit :
On Sat, 2011-10-22 at 23:42 +0200, Dimstar / Dominique Leuenberger wrote:
I could track it down to /dev/nvidiactl: the gdm greeter seems not to have sufficient permissions to access this device, causing the error.
/dev/nvidiactl is created as crw-rw---- root:video; which obviously is not matching the gdm user's permission.
/etc/modprobe.d/50-nvidia.conf: options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660
Add gdm to video group. ;-) I didn't see such an issue with KDE/kdm. What has changed in kdm?
I thought we wanted to avoid adding users to specific groups like this? We can do this, of course; I just want to be sure that it's the right way forward, or if it's just a temporary workaround (for 12.1).
Vincent
Le vendredi 04 novembre 2011, à 12:07 +0100, Vincent Untz a écrit :
Le vendredi 04 novembre 2011, à 11:35 +0100, Stefan Dirsch a écrit :
On Fri, Nov 04, 2011 at 10:59:23AM +0100, Frederic Crozat wrote:
Le vendredi 04 novembre 2011 à 10:53 +0100, Dimstar / Dominique Leuenberger a écrit :
On Sat, 2011-10-22 at 23:42 +0200, Dimstar / Dominique Leuenberger wrote:
I could track it down to /dev/nvidiactl: the gdm greeter seems not to have sufficient permissions to access this device, causing the error.
/dev/nvidiactl is created as crw-rw---- root:video; which obviously is not matching the gdm user's permission.
/etc/modprobe.d/50-nvidia.conf: options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660
Add gdm to video group. ;-) I didn't see such an issue with KDE/kdm. What has changed in kdm?
I thought we wanted to avoid adding users to specific groups like this? We can do this, of course; I just want to be sure that it's the right way forward, or if it's just a temporary workaround (for 12.1).
Ping? Should we go this way, and just for 12.1 or forever? There's a submit request from Dominique that does this, and we just need confirmation...
Vincent
Vincent Untz wrote:
Le vendredi 04 novembre 2011, à 12:07 +0100, Vincent Untz a écrit :
Le vendredi 04 novembre 2011, à 11:35 +0100, Stefan Dirsch a écrit :
On Fri, Nov 04, 2011 at 10:59:23AM +0100, Frederic Crozat wrote:
Le vendredi 04 novembre 2011 à 10:53 +0100, Dimstar / Dominique Leuenberger a écrit :
On Sat, 2011-10-22 at 23:42 +0200, Dimstar / Dominique Leuenberger wrote:
I could track it down to /dev/nvidiactl: the gdm greeter seems not to have sufficient permissions to access this device, causing the error.
/dev/nvidiactl is created as crw-rw---- root:video; which obviously is not matching the gdm user's permission.
/etc/modprobe.d/50-nvidia.conf: options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=33 NVreg_DeviceFileMode=0660
Add gdm to video group. ;-) I didn't see such an issue with KDE/kdm. What has changed in kdm?
I thought we wanted to avoid adding users to specific groups like this? We can do this, of course; I just want to be sure that it's the right way forward, or if it's just a temporary workaround (for 12.1).
Ping? Should we go this way, and just for 12.1 or forever? There's a submit request from Dominique that does this, and we just need confirmation...
It would be a workaround forever I guess. AFAIK /dev/nvidia* is not created via udev, therefore not known to udev, therefore no ACLs so no access for the desktop. That's the only reason why we still add users to the video group. So you need to do that for gdm too then.
Shouldn't there be a fallback in case GL doesn't work though?
cu Ludwig
Le mardi 08 novembre 2011, à 08:49 +0100, Ludwig Nussel a écrit :
Vincent Untz wrote:
Le vendredi 04 novembre 2011, à 12:07 +0100, Vincent Untz a écrit :
Le vendredi 04 novembre 2011, à 11:35 +0100, Stefan Dirsch a écrit :
Add gdm to video group. ;-) I didn't see such an issue with KDE/kdm. What has changed in kdm?
I thought we wanted to avoid adding users to specific groups like this? We can do this, of course; I just want to be sure that it's the right way forward, or if it's just a temporary workaround (for 12.1).
Ping? Should we go this way, and just for 12.1 or forever? There's a submit request from Dominique that does this, and we just need confirmation...
It would be a workaround forever I guess. AFAIK /dev/nvidia* is not created via udev, therefore not known to udev, therefore no ACLs so no access for the desktop. That's the only reason why we still add users to the video group. So you need to do that for gdm too then.
Ok, thanks.
Shouldn't there be a fallback in case GL doesn't work though?
There is a fallback mode, but the "GL doesn't work" detection code apparently detects things are fine in that case -- no idea why. It'd be weird to have gnome-shell for users and fallback in gdm, though.
Vincent
-
Anders Johansson -
Dimstar / Dominique Leuenberger -
Frederic Crozat -
Ismail Donmez -
Juergen Orschiedt -
Ludwig Nussel -
Malcolm -
Marco Calistri -
Stefan Dirsch -
Vincent Untz