180.35 was released last night along with legacy updates. 180.35 (current) http://www.nvnews.net/vbulletin/showthread.php?t=128939 96.43.11 (legacy) http://www.nvnews.net/vbulletin/showthread.php?t=128942 173.14.17 (legacy, BETA) http://www.nvnews.net/vbulletin/showthread.php?t=128941 Reproducible: Always
Reassigning to/CCing maintainers.
180.35 is already in the tree. The legacy ones will come shortly
I just did an update on my amd64 box, including a number of packages such as qt-4.5, kdelibs-4.2, glibc, and nvidia-drivers-180.35. After rebooting, I noticed something odd: ctrl-c no longer worked in konsole. I began noticing other problems, such as un-closable tabs in konsole (I could type "exit" and the shell would quit, but the tab would stay open) and I could no longer logout from the kde-4.2 desktop (ctrl-backspace killed it, however). After looking at the package list I had emerged recently, I honestly had no idea what could be causing the problem, so I started downgrading packages (kdelibs-4.2.0-r3 to kdelibs-4.2.0-r2, for example). Still broken. In desperation, I downgraded nvidia-drivers-180.35 to 180.29, and suddenly everything started working again. I thought that was odd, so I visited the forums at nvnews.net, and other people are reporting the same problems. For reference, you may want to look at the following threads: http://www.nvnews.net/vbulletin/showthread.php?t=128959 http://www.nvnews.net/vbulletin/showthread.php?t=128992 If you feel this is more appropriate in a new bug, I can open one.
I got some severe problems after that one too. But with Gnome (~x86). Should be mask for the time I think... Greetings
Ditto comment #3 - ctrl-c didn't work in any terminal emulator (locally), but did on remote systems SSHed into in the same terminal. It's not KDE-specific, I use xterm, uxterm, and XFterm. Seemed like several other signals were being trapped as well: screen wouldn't exit properly, SSH tunnels refused to tear down, ctrl-z wouldn't suspend, and so on. Oddly enough, ctrl-d and ctrl-v were still working well.
Neil, someone beat you to it. 5:) The new bug to follow is bug 260441.
Actually, that one was the "dupe" - posted at 21:09, whereas Neil's info was posted at 06:56. ;)
It doesn't matter to me which is the dupe, I just knew that I spent HOURS troubleshooting those issues. I just wanted to pass along the info to hopefully save someone else the trouble.
180.37 is released, fixing the issues with 180.35 among others: http://www.nvnews.net/vbulletin/showpost.php?p=1951107&postcount=1
(In reply to comment #9) > 180.37 is released, fixing the issues with 180.35 among others: > http://www.nvnews.net/vbulletin/showpost.php?p=1951107&postcount=1 > 180.37 builds fine with a simple version bump, at least here. do this in portage?
It built with no problems with a rename of the 180.29 ebuild from portage. I've been running it with no apparent issues since it came out.
All bumped.
