[Bug 432882] Re: Python binding for gnomekeyring prevents password prompt on unlock
Still a problem in 10.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/432882 Title: Python binding for gnomekeyring prevents password prompt on unlock -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368659] Re: Display flickering then system crash
This is from lspci -v: 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GT (rev a1) Subsystem: ASUSTeK Computer Inc. Device 1632 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at fc00 (32-bit, non-prefetchable) [size=16M] Memory at e000 (64-bit, prefetchable) [size=256M] Memory at fa00 (64-bit, non-prefetchable) [size=32M] I/O ports at 9c00 [disabled] [size=128] [virtual] Expansion ROM at fdee [disabled] [size=128K] Capabilities: Kernel driver in use: nvidia Kernel modules: nvidia, nvidiafb -- Display flickering then system crash https://bugs.launchpad.net/bugs/368659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368659] Re: Display flickering then system crash
I have also had this bug for some time. I have the 180 nvidia driver and compiz running on Ubuntu 9.04. Dual monitors too. Symptoms are, screens flicker then go black. Keyboard is unresponsive but sometimes mouse will still move. The latest time this happened I was able to login from another machine. Everything was still running. Initially the 'Xorg' process was taking up 100% CPU then it calmed down to about 5%. I was able to switch to text mode and back once with Ctrl-Alt-F1. Then both monitors lost their signal all together. Personally, I think it is buggy Nvidia drivers. They don't have a good track record. I've heard rumor that Nvidia's main reason for having their binary only HAL driver is to hide the fact that it tries to work around a number of hardware bugs. Just Open-Source the whole driver and fix the bugs. This happens on my system a couple of times a week with regular use. Very annoying. -- Display flickering then system crash https://bugs.launchpad.net/bugs/368659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 368659] Re: Display flickering then system crash
This is my nvida-bug-report-log ** Attachment added: "nvidia-bug-report.log" http://launchpadlibrarian.net/34384251/nvidia-bug-report.log -- Display flickering then system crash https://bugs.launchpad.net/bugs/368659 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421048] Re: Black dots appear on screen
This bug also showed up recently on my Intrepid desktop install with nvidia-glx-180. I would also like to note that if I mouse click on the dots they blink. This may be due to a screen redraw at the X layer. Moving a window over the dots will also make them blink. It seems that X firsts draws the correct content then a moment later the dots reappear, thereby causing the blinking. -- Black dots appear on screen https://bugs.launchpad.net/bugs/421048 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282068] Re: ctrl-alt-f1..f6 drops to blinking cursor; no 'console' login possible
I can confirm that the above fix worked for me too: Ubuntu 9.04 Intel T7500 NVidia driver versions 172, 180 and 185 To make things a little clearer you run: sudo apt-get install startupmanager sudo startupmanager Then change the display resolution to 1024x768 with a 24bit depth as mentioned above. Then of course you need to reboot. -- ctrl-alt-f1..f6 drops to blinking cursor; no 'console' login possible https://bugs.launchpad.net/bugs/282068 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282068] Re: ctrl-alt-f1..f6 drops to blinking cursor; no 'console' login possible
I believe your boot command line addition of: vga=791 fixes an unrelated problem. I have used the same fix on other systems to fix the console display during boot up. I am also running the NVIDIA restricted driver which seems to be the source of the "borked" console problem. I've tried several versions of the driver and haven't yet found one that doesn't have this problem. Somehow the NVIDIA driver is killing the text mode settings. -- ctrl-alt-f1..f6 drops to blinking cursor; no 'console' login possible https://bugs.launchpad.net/bugs/282068 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282068] Re: ctrl-alt-f1..f6 drops to blinking cursor; no 'console' login possible
I still have this problem after an upgrade to Jaunty. -- ctrl-alt-f1..f6 drops to blinking cursor; no 'console' login possible https://bugs.launchpad.net/bugs/282068 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 287577] Re: emacs22-gtk freezes gnome when using Alt-tab and Assistive Technologies are enabled
Please keep in mind that the title of this bug does not fully describe what is going on. Bug #294211 was marked as duplicate. It's symptoms must also be captured! >From what I can tell it is not just an Alt-Tab issue but involves moving away from the emacs window. For example this same bug will also cause firefox to lock up if you move from emacs22-gtk to firefox on another screen. No Alt-Tab involved. Taking focus away from emacs22-gtk releases firefox. I have seen this happen with other applications too. At least on Intrepid, disabling Assistive Technologies only changes the bug behavior. -- emacs22-gtk freezes gnome when using Alt-tab and Assistive Technologies are enabled https://bugs.launchpad.net/bugs/287577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 322563] Re: Intrepid random (but frequent) system freeze
Update: This fix really works I'm now at 17 days uptime on both machines. -- Intrepid random (but frequent) system freeze https://bugs.launchpad.net/bugs/322563 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 299019] Re: GTK Emacs and Metacity lockup
*** This bug is a duplicate of bug 231034 *** https://bugs.launchpad.net/bugs/231034 I don't think this is exactly a duplicate of bug #231034 which is about dragging emacs from one screen to another. It is probably related. This error is in regards to switching focus from emacs to another app. I have this problem all the time when going from emacs to firefox on a dual monitor setup. In this case taking focus away from emacs on screen one will keep firefox from freezing on screen two. Otherwise, firefox will lockup temporarily until I move the mouse back to screen one. This is new for me in Ubuntu 8.10 with gtk-emacs but reports indicate it is not limited to the gtk version. -- GTK Emacs and Metacity lockup https://bugs.launchpad.net/bugs/299019 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 289241] Re: Gnome-panel freezes when starting an application on the secondary display
I have the same problem since upgrading to intrepid from hardy. Ubuntu: 8.10 Metacity: 1:2.24.0-0ubuntu1 gnome-panel: 1:2.24.1-0ubuntu2.1 Dual Monitors An interesting side note is that if you enable assistive technologies gnome-panel restarts instead of locking up. This behavior I find easier to deal with. Clicking on launch buttons in the second display sometimes works. This is really annoying. (Sorry for the double post, but I got the wrong bug the first time.) -- Gnome-panel freezes when starting an application on the secondary display https://bugs.launchpad.net/bugs/289241 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 322563] Re: Intrepid random (but frequent) system freeze
As I mentioned above, I was plagued by this problem but I've found a
solution that has worked on two different machines with very different
usage patterns. Both started having this problem after upgrade to
Intrepid.
A solution occurred to me while watching a process through top that I
knew was getting out of control and using up too much memory. I decided
to see what would happen when it ran out rather than stop it. Once it
hit about 2GiB the system froze hard. The kernel should have killed the
process at some point or at least behaved in a graceful manner but
instead I got the familiar lockup. I have 3GiB installed so including
other processes that was probably the exact point when all my system
memory ran out.
One of the two machines that had this problem had swap enabled the other
did not so swap space does not seem to matter. One ran firefox all the
time. The other never. and so on.
So the solution or work around. I've added two lines to the end of
/etc/security/limits.conf:
* hard nproc 1000
* soft as 150 # 1.5GiB (depends on your total RAM)
After adding these lines you should reboot to get the change propagated
to all running processes.
The first line limits the number of processes that can be created by a
single user. This protects you against fork-bombs which I think do
occur in some applications. Without this line your system will totally
lock up if fork-bombed. Try running this example fork-bomb in your
shell: ':(){ :|:& };:' without the quotes. WARNING: be prepared for a
reboot if you don't have nproc limited in limits.conf. I believe some
applications accidentally cause fork bombs and the OS should be able to
handle them.
The second line limits the maximum amount of memory any single process
can use. The number is in KiB and will depend no how much memory you
have installed in your system. I would recommend setting it to about
75% of your total system memory.
I was getting crashes all the time on both machines. Since I added
these lines both machines have been up for 9 days with no problems.
I suspect that firefox 3.0, pulseaudio, possibly gnome-panel and others
have problems that trigger this but the OS has to be able to handle
poorly behaved processes without crashing. I would be very interested
to know what change caused this to start occurring. I suspect it is
kernel related but xorg could also be involved.
FYI, when the crash did occur there was no relevant info in
/var/log/syslog.
--
Intrepid random (but frequent) system freeze
https://bugs.launchpad.net/bugs/322563
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 322563] Re: Intrepid random (but frequent) system freeze
I also have the same problem. uname -a Linux kenny 2.6.27.7-custom-grsec #14 SMP PREEMPT Fri Mar 6 06:16:17 PST 2009 i686 GNU/Linux I compiled a new kernel but I had the problem with the sock ubuntu kernel and my custom kernel was compiled from ubnutu sources + grsec anyway. Ever since an upgrade to Intrepid in January. I've been updating my packages regularly too. I have dual monitors and an Nvida card. I was using the 180 nvidia driver but am trying 173 to see if that helps. This is a huge problem for me. I am a heavy user and I get this at least once or twice a day lately. I've been evaluating other Distros but don't want to switch because Ubuntu has been so good up until now. -- Intrepid random (but frequent) system freeze https://bugs.launchpad.net/bugs/322563 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282068] Re: ctrl-alt-f1..f6 drops to blinking cursor; no 'console' login possible
Having exactly the same problem describe in the initial post ever since I upgraded from hardy to Intrepid with gnome and an nvidia card. I also have dual monitors. I doubt it is kernel related. -- ctrl-alt-f1..f6 drops to blinking cursor; no 'console' login possible https://bugs.launchpad.net/bugs/282068 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 284861] Re: Intrepid: gnome-panel hangs in dual monitor setup
*** This bug is a duplicate of bug 235944 *** https://bugs.launchpad.net/bugs/235944 ** This bug has been marked a duplicate of bug 235944 Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu -- Intrepid: gnome-panel hangs in dual monitor setup https://bugs.launchpad.net/bugs/284861 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235944] Re: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu
I have the same problem since upgrading to intrepid from hardy. Ubuntu: 8.10 Metacity: 1:2.24.0-0ubuntu1 gnome-panel: 1:2.24.1-0ubuntu2.1 Dual Monitors An interesting side note is that if you enable assistive technologies gnome-panel restarts instead of locking up. This behavior I find easier to deal with. Clicking on launch buttons in the second display sometimes works. This is really annoying. -- Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu https://bugs.launchpad.net/bugs/235944 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 231034] Re: desktop freeze when moving emacs in workspace switcher
I have the same problem: Ubuntu: 8.10 Emacs: emacs22-gtk 22.2-0ubuntu2 Metacity: 1:2.24.0-0ubuntu1 Dual Monitors Assistive Technologies enabled Symptoms: Cursor turns to window resize pointer and stays that way. Mouse will move around on the current screen but will not move to second screen and clicks do nothing. Switching to text terminal and back "fixes" the problem. Pressing Caps lock sometimes turns the direction of the resize pointer and eventually frees up the mouse. Note also that the window does not actually resize until the mouse is released then it moves to wherever the mouse is at the time. This happens at random but is pretty easy to reproduce by making attempts to resize gtk-emacs screen. This may not be related but I also have a bug where gnome-panel crashes when I try to use a launch button on the second display. The gnome- panel used to lock up and use 100% CPU until I enabled assisitive technologies now it crashes and restarts instead. Since both problems involve metacity and assisitive technologies it could be related. -- desktop freeze when moving emacs in workspace switcher https://bugs.launchpad.net/bugs/231034 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
