Summary: | sys-apps/qingy-0.9.8 log off user from X on keyboard input | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Marcus Becker <marcus.disi> |
Component: | Current packages | Assignee: | Michele Noberasco (RETIRED) <s4t4n> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | base-system, f.bondoux, marcus.disi |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
qingy.log
revert change in session.c ebuild with patch |
Description
Marcus Becker
2009-04-27 21:31:51 UTC
Even if I login to console and startx from there via Qingy X crashes. Here are the USE flags, Qingy is with X and DirectFB without: [ebuild R ] dev-libs/DirectFB-1.2.7 USE="fbcon fusion gif jpeg mmx png sdl sse sysfs truetype zlib -X -debug -v4l -v4l2" 2,707 kB [ebuild R ] sys-apps/qingy-0.9.8 USE="X crypt directfb gpm pam -emacs -opensslcrypt -static" 0 kB here is the end of Xorg.1.log: (II) config/hal: Adding input device Microsoft Comfort Optical Mouse 1000 (II) LoadModule: "evdev" (II) Loading /usr/lib64/xorg/modules/input//evdev_drv.so (II) Module evdev: vendor="X.Org Foundation" compiled for 1.5.3, module version = 2.2.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 2.1 (**) Microsoft Comfort Optical Mouse 1000: always reports core events (**) Microsoft Comfort Optical Mouse 1000: Device: "/dev/input/event3" (II) Microsoft Comfort Optical Mouse 1000: Found 3 mouse buttons (II) Microsoft Comfort Optical Mouse 1000: Found x and y relative axes (II) Microsoft Comfort Optical Mouse 1000: Found scroll wheel(s) (II) Microsoft Comfort Optical Mouse 1000: Configuring as mouse (**) Microsoft Comfort Optical Mouse 1000: YAxisMapping: buttons 4 and 5 (**) Microsoft Comfort Optical Mouse 1000: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device "Microsoft Comfort Optical Mouse 1000" (type: MOUSE) (II) config/hal: Adding input device AT Translated Set 2 keyboard (**) AT Translated Set 2 keyboard: always reports core events (**) AT Translated Set 2 keyboard: Device: "/dev/input/event2" (II) AT Translated Set 2 keyboard: Found keys (II) AT Translated Set 2 keyboard: Configuring as keyboard (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD) (**) Option "xkb_rules" "evdev" (**) Option "xkb_model" "evdev" (**) Option "xkb_layout" "us" (II) Microsoft Comfort Optical Mouse 1000: Close (II) UnloadModule: "evdev" (II) AT Translated Set 2 keyboard: Close (II) UnloadModule: "evdev" It did work if I logged on to console via Qingy and ran startx now I downgraded to DirectFB-1.2.6 and Qingy 0.9.7 and no problems anymore Could you maybe elaborate if this is either a problem with qingy or DirectFB? How about only downgrading one package at a time and test again? Created attachment 189775 [details]
qingy.log
I am back on Qingy 0.9.8 with DirectFB-1.2.6 and the same happens again
so this is a problem with Qingy
I attched the debug log
Unfortunately here in those 20sec it happens: Apr 28 23:24:22, qingy-DirectFB on tty1, [DEBUG] stderr logger process shutting down... Apr 28 23:24:43, qingy on tty1, [DEBUG] You chose a screen saver timeout of 5 minutes. and there seems to be no log in qingy nor messages nor Xorg.log :( no problems Qingy 0.9.7 and DirectFB-1.2.7 Qingy 0.9.8 DirectFB 1.2.7 created a fresh test user and same thing happens (i use different keys like a,d,b,i,o,e): Apr 29 00:06:26 disi-desktop qingy: pam_unix(qingy:session): session opened for user pimpf by (uid=0) Apr 29 00:06:26 disi-desktop qingy: pam_unix(qingy:session): session opened for user pimpf by (uid=0) Apr 29 00:06:28 disi-desktop IRQ 16/nvidia: IRQF_DISABLED is not guaranteed on shared IRQs Apr 29 00:06:29 disi-desktop IRQ 16/nvidia: IRQF_DISABLED is not guaranteed on shared IRQs Apr 29 00:06:32 disi-desktop JBD: barrier-based sync failed on dm-0:8 - disabling barriers Apr 29 00:06:46 disi-desktop qingy: pam_unix(qingy:session): session closed for user pimpf Apr 29 00:06:46 disi-desktop qingy: pam_unix(qingy:session): session closed for user pimpf recompiled x11-base/xorg-server-1.5.3-r5 without hal USE flag same problem... can anybody run Qingy 0.9.8 to login to X? There is probably a get function or something that waits for input while it goes on to start X. As soon as it gets something from the keyboard, it continous in the Qingy script and kills X in the meantime? I am no C expert and currently try to follow the session.c if there are any brackets missing or something... (In reply to comment #10) > can anybody run Qingy 0.9.8 to login to X? Actually, I can, and I cannot reproduce your issues. But I'm investigating... more testing: removed xorg-x11 installed openbox for testing, works fine installed windowmaker for testing, works fine Uhm... I might install xfce4 and see if qingy issues are somehow related with it... I'm not using xfce but I'm having a related bug with Qingy 0.9.8. The DBus session instance started by /etc/X11/xinit/xinitrc.d/30-dbus dies on keyboard input. Xfce is maybe dying along with the dbus daemon. This is due to a change in session.c which messes up the standard I/O. The attached patch reverts this change and restores the std IO streams. Created attachment 190684 [details, diff]
revert change in session.c
Created attachment 190721 [details]
ebuild with patch
works perfect now here with xfce4, thanks a lot :)
(In reply to comment #16) > Created an attachment (id=190721) [edit] > ebuild with patch It works for me! Before that patch I have to login to console then launch Xfce via startx, if I login to my Xsession directly d-bus doesn't starts correctly and gconf-enabled sowftwares (firefox, gedit...) shows me errors and annoying issues. Thanks! Just added version 0.9.9 to Portage, which adds the patch proposed here. Thanks, Florent! |