Ctrl+C/Ctrl+Z/exit/etc. broken in GNOME, other WMs [solved]

[Avuton Olrich]

Hello,

I know this isn't bugzilla, please forgive me, I don't want to file a bug when I'm not sure if it's my fault or something.


In the last day I can't suspend /anything/ using CTRL-Z as I'm used to. CTRL-C seems to be a problem to, but if I figure the suspend problem I think I'll figure both out.

Here's where it works and where it doesn't:

Works at:
the linux console.
a basic startx in the xterm

Fails:
a basic startxfce4 with any term including xterm
kde-4.2 with any term including xterm
Tried starting as a test user with either of the above fails as well.
Tried booting a known working kernel continued to fail in the above situations.
Tried downgrading both coreutils and readline as I saw those were updated here lately.

I'm out of ideas for figuring this problem out. Please throw ideas out, I need help here and I'm so frusterated and out of ideas.


Turns out this is a new bug from nvidia-drivers? So strange.

[poly_poly-man]

does kill -SIGSTOP pid work? pid must be of a program running in terminal - will act as a ^z, hopefully.

[Avuton Olrich]

does kill -SIGSTOP pid work? pid must be of a program running in terminal - will act as a ^z, hopefully.

That does work.

[poly_poly-man]

do you see any on-screen indication of those combinations being pressed? such as, "^C" or "^Z" being printed?

[jburns]

Are you using x11-drivers/nvidia-drivers-180.35

[Avuton Olrich]

Are you using x11-drivers/nvidia-drivers-180.35

Well, holy cow are you right?!?! That makes no sense. No wonder I didn't find it. Thank you so much, I was really going out of my mind.

[Avuton Olrich]

do you see any on-screen indication of those combinations being pressed? such as, "^C" or "^Z" being printed?

BTW- they did appear. Thanks for your attempt to help someone when they were down. I thought I'd never track down what the issue was.

[poly_poly-man]

Are you using x11-drivers/nvidia-drivers-180.35

you want to explain this issue to me? I *thought* I was using that version, but my update script has been deadlocked for so long.... should I avoid that version?

[Avuton Olrich]

Are you using x11-drivers/nvidia-drivers-180.35

you want to explain this issue to me? I *thought* I was using that version, but my update script has been deadlocked for so long.... should I avoid that version?

The issue is just like I said above, it seriously, I have no idea how blocks you from using CTRL-C and CTRL-Z in any terminal, not in the console, and only if you use a WM. I don't get it and that's why I had to post here. It makes no sense to me :/

[jburns]

See http://bugs.gentoo.org/show_bug.cgi?id=260441. The driver works for some people and causes problems for other people. For me it would not close a terminal window after typing exit, I could not exit from my KDE sesson, etc. But I have a program that always crashed when I exited it that terminates normally with the new driver.

[Crono81]

I don't know what happened, but now i can't use ctrl-c, ctrl-z key combinations anymore when i'm on a terminal under Gnome (either on gnome-terminal or xterm). If i run a bare X desktop environment with only an xterm, then i can ctrl-c, but if i run a gnome-terminal there it doesn't work.
(e.g. this script doesn't print the "*** Trapped CTRL-C" message)

Code: Select all

#!/bin/bash

trap ctrl_c INT

function ctrl_c() {
        echo "** Trapped CTRL-C"
}

for i in `seq 1 5`; do
        sleep 1
        echo -n "."
done

I can actually ctrl-r, ctrl-p etc. I tried to create a new user from scratch and to reset the gnome keyboard configurations to default, but it didn't help. Hints?


--update:
"exit" doesn't work also. If i type exit and press enter, the terminal prints "exit" but the window doesn't close.

[poly_poly-man]

are you using nvidia-drivers-180.35?

[jcat]

I have an almost identical problem after an update yesterday.
Gnome Terminal is as you describe, however xterm running under gnome works for me.

I also can't recover from "locked" screen, I get stuck in the screensaver, only way is to kill X.

The packages installed yesterday were:

Code: Select all

     Sat Feb 28 12:50:53 2009 >>> sys-apps/texinfo-4.13
     Sat Feb 28 12:51:16 2009 >>> dev-util/dialog-1.1.20080819
     Sat Feb 28 12:52:29 2009 >>> app-text/poppler-0.10.4
     Sat Feb 28 12:52:56 2009 >>> x11-libs/libXi-1.2.1
     Sat Feb 28 12:53:38 2009 >>> x11-libs/pixman-0.14.0
     Sat Feb 28 12:54:02 2009 >>> x11-libs/libdrm-2.4.5
     Sat Feb 28 12:54:20 2009 >>> x11-drivers/xf86-video-vesa-2.2.0
     Sat Feb 28 12:54:40 2009 >>> x11-drivers/xf86-input-evdev-2.1.3
     Sat Feb 28 12:56:30 2009 >>> x11-drivers/nvidia-drivers-180.35
     Sat Feb 28 12:57:40 2009 >>> net-www/netscape-flash-10.0.22.87
     Sat Feb 28 12:59:44 2009 >>> app-mobilephone/gnokii-0.6.27-r2
     Sat Feb 28 13:00:16 2009 >>> gnome-extra/gucharmap-2.24.3
     Sat Feb 28 13:04:41 2009 >>> media-libs/xine-lib-1.1.16.2
     Sat Feb 28 13:11:19 2009 >>> gnome-extra/evolution-data-server-2.24.5
     Sat Feb 28 13:13:04 2009 >>> gnome-extra/gtkhtml-3.24.5
     Sat Feb 28 13:42:04 2009 >>> mail-client/evolution-2.24.5
     Sat Feb 28 13:43:45 2009 >>> app-text/poppler-bindings-0.10.4
     Sat Feb 28 13:51:38 2009 >>> media-gfx/imagemagick-6.4.8.3
     Sat Feb 28 13:54:04 2009 >>> gnome-base/gnome-panel-2.24.3-r1

I've re-emerge the contents of

Code: Select all

qlist -I |grep x11-drivers

plus

Code: Select all

gnome-terminal

and

Code: Select all

gnome-screensaver

I tried running

Code: Select all

revdev-rebuild

and

Code: Select all

emerge -av @preserved-rebuld

..nothing helps.


Cheers,
jcat

[poly_poly-man]

mask the latest nvidia-drivers.

[Crono81]

These things drive me mad.
Thank you poly_poly-man, emerge =nvidia-drivers-180.29 solved the problem, and i really don't want to know why.

[HotBBQ]

Awesome find. Thanks for the tip.

[jcat]

I should have guessed

..but unlike Crono81, I would like to know why. This is touted as a stable release by nVidia.......


Cheers,
jcat

[alienvenom]

kde users are having issues too with 180.35

http://bbs.archlinux.org/viewtopic.php?pid=505620

also

http://www.nvnews.net/vbulletin/showthr ... ost1945779

[mlinden]

Thanks a lot! I searched the last 1 1/2 hours about this problem and came here to ask you guys and the first thread I see has the solution. Thanks a lot!

[muffy]

My thanks also, this was driving me nuts.

Gnome-do also seems to have major problems with the later drivers, downgrading fixed that too.

[bdx]

The new nvidia drivers appear to be causing some init scripts to fail unexpectedly, in particular

Code: Select all

 /etc/init.d/mythbackend stop
 * Stopping MythTV Backend ...  [ !! ]
  /etc/init.d/mtd stop
 * Stopping MythTV Transcoding Daemon ... [ !! ]

After reverting to the previous nvidia-drivers the problem goes away

[SDNick484]

I'm so glad I found this thread (fortunately Gentoo Forums is always my first place to look). Yeah, I'm definitely very curious what they did to cause this and am glad there's a fix. This issue would drive me insane.

[timeBandit]

Merged from [post=5521967]Crono81's post[/post] onward here, and retitled the thread since this is now [bug=260441]recognized[/bug] as a more general problem with nvidia-drivers-180.35.

Also, moved from Other Things Gentoo to Desktop Environments. Fits better here.

[energyman76b]

do you guys have consolekit running? if no - does the problem gets away if you start consolekit before starting X?

[poly_poly-man]

I should have guessed

..but unlike Crono81, I would like to know why. This is touted as a stable release by nVidia.......


Cheers,
jcat

actually, it's a beta release, isn't it?

within a few days of this popping up, they had 180.37 which fixed all problems - turns out it was blocking signals from hitting apps...