Description of problem: Install M4 from any Live disk and afterwards gdm/kdm have the login menu option 'drak3d'. But logging into such session, one gets thrown out again right away. From tty may be seen that the file .xsession-errors (or gdm entries in journal) show: Failed to connect to VirtualBox kernel service localhost being added to access control list Failed to connect to VirtualBox kernel service Failed to connect to VirtualBox kernel service Failed to connect to VirtualBox kernel service Failed to connect to VirtualBox kernel service Error creating textual authentication agent: Errror opening current controlling terminal for the process ('/dev/tty'): No such device or address Nothing else is reported. It should be able to do something with this choice, or the menu option should not be created. Reproducible: Steps to Reproduce:
Blocks: (none) => 11704Whiteboard: (none) => 4RC
CC: (none) => eeeemail, thierry.vignaud, tmb
I still don't understand why this option even exists (i.e., why drak3d provides a wmsession.d file).
(In reply to David Walser from comment #1) > I still don't understand why this option even exists (i.e., why drak3d > provides a wmsession.d file). Thierry, maybe we could remove it ? as drak3d still works in console if needed (and it will also remove 1 or 2 other bugs) or it's only a polkit agent not running
Component: Installer => RPM PackagesAssignee: bugsquad => thierry.vignaud
I can nuke the wmsession file during live build if that is wanted / all that is needed
well there is a real use of it ? we could remove it for everywhere
With 3rd round Live isos and new drak3d package the login option is still there and still does nothing.
Source RPM: drak3d-2.0-4.mga4 => drak3d-2.1-1.mga4Whiteboard: 4RC => 4final
So the path seems to be wrong. In the past it would run /usr/sbin directly, but now it runs /usr/bin version... in our case it shouldn't matter actually as we're already root at this stage (at least I think we are... kinda hard to tell actually). But even correcting things seems to fail. Not really sure why, but perhaps gtk3 doesn't like being run without a real window manager? I'm tempted to just nuke it until we can figure out if it should return. Most 3D bits these days is automatically configured and I'd be tempted to kill drak3d completely for mga5. Anyway, nuked the wmsession file for now.
Status: NEW => RESOLVEDCC: (none) => mageiaResolution: (none) => FIXED
Sorry, when I do an uograde, drak3d login option is gone. But just did a fresh install with 64 bits classical iso, GNOME only and upgrade all packages before the end and before reboot: drak3d is still there.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
$ rpm -q drak3d $ ls -l /etc/X11/wmsessions.d/ $ rpm -qf /etc/X11/wmsessions.d/*
(sorry, it's wmsession.d (no plural))
@coling re #c8 These are questions I suppose? rpm -q drak3d drak3d-2.1-1.mga4 This is from update during installation today at 13:40 h UTC; obviously 2.1-2 was not found although it should have been. Bah :(( ls -l /etc/wmsession.d/ ... 02GNOME ... 03GNOME_CLASSIC ... 07IceWM -rw-r--r-- l root root 116 Jan 25 16:56 20drak3d rpm -qf /etc/X11/wmsessions.d/* ... ... ... drak3d-2.1-1.mga4
At this hour I updated again the same install, now the wmsession file is removed. So obviously this was due to a lagging mirror. Sorry for the noise.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED