|
Bugzilla – Full Text Bug Listing |
| Summary: | nvidia: xorg stuck after shortcut is typed | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Pavel Nemec <pnemec> |
| Component: | X11 3rd Party Driver | Assignee: | Roland Hui <rohui> |
| Status: | RESOLVED NORESPONSE | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | andreas.pfaller |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | 64bit | ||
| OS: | openSUSE 10.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
xorg.conf, with nvidia binary driver
screenshot of ill klipper log gathered using nvidia bug report script .xsessions errors file |
||
Any hints how I can define these shortcuts in which desktop? Which application? So I can try to reproduce. My configuration: kernel: 2.6.18.8-0.3-default KDE: kdebase3-3.5.7-31.2 Xorg: xorg-x11-7.2-26 nvidia drivers: NVIDIA-Linux-x86-1.0-9755-pkg1.run I am using KDE as WM. How to set shortcut for klipper: 1) start klipper (if it is not all ready started) 2) click with right mouse button on klipper icon in task bar 3) select "Klipper settings" 4) select "ShortCuts" 5) AFAIK Ctrl+Alt+V is default shortcut for klipper. How to set shortcut for switching keyboard layout 1) run kde control centre (kcontrol) 2) select "Regional and Accessibility" (in EN language, DE will have different label) 3) select "Keyboard Layout" 4) select "Enable Keyboard Layout" 5) select some additional keyboard layout ###shortcut### 6) in kcontrol select "Regional and Accessibility" and then "Keyboard shortcuts" 7) in my case i have set "Switch to next Keyboard Layout" -> Scroll Lock Try switch keyboard layout when writing address in Konqueror "URL input box", for example. BTW: i am not sure if you will be able to reproduce it. It sometimes took days when it happen at my computer, sometimes 5 times per day :( I created this bug report manly for tracking if someone will also meet this problem. Ok. Thanks for detailed explanation. Since you said that it's not easily reproducable I'm setting the severity to NORMAL. Indeed I can't reproduce this issue with openSUSE 10.3 Alpha5plus. Since I can't reproduce it, I set this one to LATER for now. Reopen. Any improvements with openSUSE 10.3 Beta1? Sorry i do not have time to test it as my workload in POS is quite high. Only information i have is that problem is problably not in Xorg but in klipper. I had 10 accidents in this week, all related to klipper invocation. Reassign to me, till usefull informations are gathered This is probably a duplicate of Bug #245711. I have couple of information for this one. First I can reproduce it on different hw with 10.2. And I install 10.3 on my work computer and I can reproduce it here also. I also find problematic spot. It is klipper!!!. I realize that when I copy some text (typycaly url or email adress) klipper get stucked for while (10-40 seconds). After that there are double squares in clipboard memory and not text I select to paste. When I call Ctr+Alt+V in this time where, which should show klipper popup my X get killed. Everytime. When I open popup menu by mouse, klipper show it after it is released from his stuck time and show it normally. If I am right, klipper is part of kicker. So how can I debug it? Created attachment 181023 [details]
screenshot of ill klipper
After copy some text from jedit (java) using selection (select some part of text using mouse, not ctrl+c) i get klipper hung and it return crippled text. If i type ctrl+shift v in this 30 seconds interval X get killed.
Changing product to openSUSE10.3 which I am using know. This error kill X so I am rising priority. Looks like Lubos know klipper. If X gets killed, then it should be X bug, albeit triggered by Klipper. Please check if this also happens with nv driver. For this uninstall the nvidia driver properly and run "sax2 -r" to create a nvidia driver based configuration. > ... and run "sax2 -r" to create a nvidia driver
Of course I've meant "nv"-driver ...
Any news on this one. Does this mean that it didn't happen since you switched to nv driver? Sorry for long delay, I was/am wery bussy about releasing SLEPOS. I will test it ASAP. Could you verify, if this issue is still reproducable with release 169.07? Driver download: http://www.nvidia.com/object/linux_display_ia32_169.07.html http://www.nvidia.com/object/linux_display_amd64_169.07.html Installation instructions: http://www.suse.de/~sndirsch/nvidia-installer-HOWTO.html I am now trying reproduce this problem only with nv driver. Problem here is that it take some time this bug occure. After that I will test new drivers. Anyway, what kinds of logs will be usefull? AFAIK there is no error message in /var/log/messeges or /var/log/ /var/log/Xorg.0.log Ok. If there are no related error messages in Xorg.0.log and messages I think we don't need any logs. I see. So you just need information that bug occure with nv or not. Exactly. I can confirm this one with nv video driver. BTW I just found that I report similar bug on ati machine bug #197527. Duplicate. See comment #8. *** This bug has been marked as a duplicate of bug 245711 *** I had to reopen bug. Because X still do not behave correctly. Same environment (10.3 x86-64, KDE) Due to bug #245711 I updated Xorg from stable (xorg-x11-7.2-135.4) Same shortcut ctrl+alt+v to show klipper. Now x do not get stuck but they crash and restart immediately (If you think this is different problem I can create another bug?). I found this in .xsession-errors /etc/X11/xim: Checking whether an input method should be started. /etc/X11/xim: user environment variable LANG=cs_CZ.UTF-8 sourcing /etc/sysconfig/language to get the value of INPUT_METHOD INPUT_METHOD is not set or empty (no user selected input method). Trying to start a default input method for the locale cs_CZ.UTF-8 ... There is no default input method for the current locale. startkde: Starting up... kbuildsycoca running... JACK tmpdir identified as [/dev/shm] KMenuBase::setProperty( "frameShadow", value ) failed: property invalid, read-only or does not exist KMenuBase::setProperty( "frameShape", value ) failed: property invalid, read-only or does not exist QObject::connect: No such signal Kicker::settingsChanged(SettingsCategory) QObject::connect: (sender name: 'kicker') QObject::connect: (receiver name: 'animtt') ASSERT: "!name.isEmpty()" in ./kio/kio/kdirlister.cpp (969) ASSERT: "!m_self" in ./kicker/kicker/buttons/knewbutton.cpp (58) [...] JACK tmpdir identified as [/dev/shm] akode: Cannot detect mimetype KNotify::playTimeout Klipper is already running! *** WARNING *** The programme 'kdeinit' uses the Apple Bonjour compatiblity layer of Avahi. *** WARNING *** Please fix your application to use the native API of Avahi! *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=kdeinit> není souborem ani adresářem SOAP FAULT: SOAP-ENV:Client "Operation interrupted or timed out" Operace probíhá SOAP FAULT: SOAP-ENV:Client "Operation interrupted or timed out" QLayout "unnamed" added to QVBox "unnamed", which already has a layout QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow NVIDIA: could not open the device file /dev/nvidiactl (Přístup odmítnut). NVIDIA: Direct rendering failed; attempting indirect rendering. QObject::connect: Incompatible sender/receiver arguments [...] >NVIDIA: could not open the device file /dev/nvidiactl (Přístup odmítnut).
>NVIDIA: Direct rendering failed; attempting indirect rendering.
Reassigning to NVIDIA.
If this problem persists with 169.09, please generate and provide an nvidia-bug-report.log. Pavel, is there any update? If this problem persists with 169.12, please generate and provide an nvidia-bug-report.log. Sorry for long delay, I missed Stefans comment. Currently I am running nvidia 169.09 and xorg 7.2.0 (standard 10.3 with updates) I did not encounter any problems for quite some time (10+ days). But behaviour of this bug is quite unpredictable. As I state in comment #23 I was able to reproduce this bug without nvidia drivers loaded. I am decreasing severity and leave need info on me till I will be able to provide requested crash log. Created attachment 202576 [details]
log gathered using nvidia bug report script
I got error after pressing Ctr+Alt+V. I did not run KDE or klipper at that time.
Created attachment 202578 [details]
.xsessions errors file
And last log found in /var/log/messeges (sorry for czech) Mar 17 15:31:00 wintermute gconfd (pavel-31575): startuji (verze 2.20.0), pid 31575, uživatel 'pavel' Mar 17 15:31:00 wintermute gconfd (pavel-31575): Zjištěna adresa "xml:readonly:/etc/gconf/gconf.xml.mandatory" je zdroj nastavení pouze pro čtení na pozici 0 Mar 17 15:31:00 wintermute gconfd (pavel-31575): Zjištěna adresa "xml:readwrite:/home/pavel/.gconf" je přepisovatelný zdroj nastavení na pozici 1 Mar 17 15:31:00 wintermute gconfd (pavel-31575): Zjištěna adresa "xml:readonly:/etc/gconf/gconf.xml.defaults" je zdroj nastavení pouze pro čtení na pozici 2 Mar 17 15:31:00 wintermute gconfd (pavel-31575): Zjištěna adresa "xml:readonly:/etc/gconf/gconf.xml.schemas" je zdroj nastavení pouze pro čtení na pozici 3 Mar 17 15:31:30 wintermute gconfd (pavel-31575): Server GConf se nepoužívá, končím. Mar 17 15:31:30 wintermute gconfd (pavel-31575): Končím Mar 17 15:32:31 wintermute syslog-ng[2347]: STATS: dropped 0 Mar 17 15:35:14 wintermute kernel: klauncher[19723]: segfault at 0000000000000021 rip 00002af63f549066 rsp 00007fff6ce4f400 error 4 Mar 17 15:35:15 wintermute kdm[17618]: X server for display :0 terminated unexpectedly Could you verify, if this issue is still reproducable with release 169.12? Driver download: http://www.nvidia.com/object/linux_display_ia32_169.12.html http://www.nvidia.com/object/linux_display_amd64_169.12.html Installation instructions: http://www.suse.de/~sndirsch/nvidia-installer-HOWTO.html Still no feedback after a week. Please reopen once you can provide the requested feedback. Thanks. |
Created attachment 151614 [details] xorg.conf, with nvidia binary driver I have very weird behaviour of xorg. Sometimes after shortcut is pressed xorg get stucked. X do not crash, but run at 99% cpu. I am able to log to my machine (over ssh) and kill them, but i can`t do anything else (like switch to konsole). rcxdm restart do not kill X, same with kill Only kill -9 work. No message in /var/log/messages. I have reproduce it with binary nvidia drivers and without it (with nv). Stucking is more often when i type shortcut in some inputBoxWidget (any type, QT, java, GTK) I was told that this behaviour could be caused by MozillaFirefox or OpenOffice.org. But i reproduce it without those applications. It mostly happened with two kind of shortcut. (because i use this shortcut a lot) Ctr+Alt+v - show up window with klipper content ScrLk - change keyboard layout. Finaly i have very simmilar setup (SL version, KDE version, shortcuts) at my home computer, with different graphic card and i never meet this problem. I know this is very inaccurate report, but i do not know what i should look for (logs or whatever)