[Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
I meant to say that last year an update killed my middle mouse pasting, which had worked before. This install is a completely clean install of Lubuntu 16.10 after reformatting the hard drive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
I followed John's instructions and am attaching the terminal output (from the script command) because it does show emulation set to zero as well as my type of mouse. My scrolling has always worked, just not the middle mouse paste. Performing the steps john suggested did not make the pasting work. I'm on Lubuntu 16.10 using lxde. The problem also was happening to me last year under the previous LTS (I think xubuntu 14.04) using xfce. ** Attachment added: "fixmouse-whatidid-05082017.out" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581088/+attachment/4873468/+files/fixmouse-whatidid-05082017.out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 914889] Re: F1 - Help / yelp / ghelp is looping, Ubuntu 11.10
This problem exists in 12.04 Precise as well. And no matter how much you kill it, it keeps coming back. The process shows init as its parent: rifter5626 1 14 15:05 ?00:00:48 yelp ghelp:///usr/share/gnome/help/gnome-terminal/C/gnome-terminal.xml The only way to stop it seems to be to kill the terminal, for some reason. highly frustrating. I'm using the 64 bit AMD version of Precise, btw. dpkg -l | grep yelp ii libyelp03.4.1-0ubuntu1 Library for the GNOME help browser ii yelp3.4.1-0ubuntu1 Help browser for GNOME ii yelp-xsl3.4.1-1 XSL stylesheets for the yelp help browser uname -a Linux leviathan 3.2.0-37-generic #58-Ubuntu SMP Thu Jan 24 15:28:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/914889 Title: F1 - Help / yelp / ghelp is looping, Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/914889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 914889] Re: F1 - Help / yelp / ghelp is looping, Ubuntu 11.10
Also note that there is an upstream bug for this in Debian.: http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1088861.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/914889 Title: F1 - Help / yelp / ghelp is looping, Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/914889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 914889] Re: F1 - Help / yelp / ghelp is looping, Ubuntu 11.10
I stand corrected. It seems that I can't get rid of yelp by killing the terminal after all. If I could figure out what is respawing it I would kill that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/914889 Title: F1 - Help / yelp / ghelp is looping, Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/914889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 914889] Re: F1 - Help / yelp / ghelp is looping, Ubuntu 11.10
Kill -9 does the trick. I had been using xkill and I guess it does not do that. Destroying or closing the window, or using xkill, results in a respawn, but kill -9 from the terminal gets rid of it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/914889 Title: F1 - Help / yelp / ghelp is looping, Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/914889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 456637] Re: Please consider turning powermizer OFF
The issue exists for *all* cards, including the newest, and in the newest drivers from nvidia. It doesn't remember the setting between reboots, either, which is very frustrating. And the only reason we did not report it to nvidia as I recall is we could find no means to do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/456637 Title: Please consider turning powermizer OFF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/456637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 456637] Re: Please consider turning powermizer OFF
Oh and just in case ?I was not clear this affects the latest Ubuntu and the latest drivers. I don't see a way to indicate that but I believe we're still where we were before on this. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Expired = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/456637 Title: Please consider turning powermizer OFF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/456637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562414] Re: gpointing-device-settings crashed with SIGSEGV in gpds_xinput_utils_get_device_info()
I am on Ubuntu 12.04 LTS (AMD64) and this is still a problem. The command just flat does not work. If I use gksudo I get the above result, like the OP. If I try as a normal user I get: ... a different error. (apport would not let me copy and paste, and would not come up again so I could even see the error to show you. This is with a freshly installed package, version 1.5.1-6 I will try and get some better info. When I initially ran the program I did not have debug symbols installed, because there is no package named after this one that has those symbols. (turns out it is in libgpds-dbg - a very nonintuitive name indeed). With this bug not fixed I don't get why we are even using this. It doesn't work. It crashes on launch. Why would we leave this unfixed for years if we're distributing it? It's kind of annoying too because there is now no longer a way to emulate middle mouse buttons since that is not an option in the current preferences program. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/562414 Title: gpointing-device-settings crashed with SIGSEGV in gpds_xinput_utils_get_device_info() To manage notifications about this bug go to: https://bugs.launchpad.net/gpointing-device-settings/+bug/562414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562414] Re: gpointing-device-settings crashed with SIGSEGV in gpds_xinput_utils_get_device_info()
** Attachment added: gpointing-device-settings.bug.apport https://bugs.launchpad.net/ubuntu/+source/gpointing-device-settings/+bug/562414/+attachment/3329913/+files/gpointing-device-settings.bug.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/562414 Title: gpointing-device-settings crashed with SIGSEGV in gpds_xinput_utils_get_device_info() To manage notifications about this bug go to: https://bugs.launchpad.net/gpointing-device-settings/+bug/562414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 456637] Re: Please consider turning powermizer OFF
@#25 Maximum performance is not an overclocked setting. I would expect overheating when overclocking. Not to say that Nvidia cards don't do that under normal speed, because the ones that don't do powermizer have for me in the past. However that only happens if you have insufficient cooling. Older cards basically require a slot fan because generally there is not enough airflow over them otherwise. I learned that the hard way long ago. I have a newer card now and it comes with a builtin slot fan, probably for this reason. Essentially what I am getting at is if you are having that kind of issue when under maximum performance, not overclocking the card, the problem is in your case setup/cooling solution, not in the powermizer setting, in which case you need to address that anyway. I would prefer that powrmizer remember the setting you put in, then people in your situation could have it set to something else. I would notify Nvidia upstream but I never was able to discover a way to do so. Very frustrating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/456637 Title: Please consider turning powermizer OFF To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/456637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 456637] Re: Please consider turning powermizer OFF
The people who claim only some people are affected by this bug are completely off base. This is a bug that affects everyone. It is ridiculous that the setting for the nvidia powermizer is not saved when you change it unless you do so by manually editing xorg.conf. It's also pretty annoying that it defaults to the lowest performance setting even on a desktop. On my system this results in what is a pretty decent nvidia card using performance that would have been considered weak something like 10 years ago. I'm talking about clocks going down to 1/12 speed. And it should not affect desktop performance, but it does. It especially seems to affect video. And like pretty much all adaptive cpu technologies to date it is not very adaptive in that it does not change performance levels quickly enough if at all. I read something online that suggested that powermizer waits 15 seconds after detecting a performance change to change performance. There are settings available to make powermizer default to a different performance mode and even set it to be smart enough to use a different setting when on ac power versus battery power. Of course right now the change in performance mode is not saved when done through the gui and there is no gui way to change the other stuff, but the capability exists. There's really no excuse for this bug having persisted for years without relief. The problem I see with editing xorg.conf manually, besides the fact there is a lot of misinformation and bad instructions out there for how to set powermizer therein which have led people to a bad pass at times and besides the aforementioned problem that this is a high bar for the target Ubuntu user, is that what you put in there is likely to get blown away unless there is some awareness in the tools involved and installers that also edit xorg.conf on a regular basis. All that aside, quite apart from the fact that EVERYONE will suffer from bad performance and settings not being saved, there are clearly a significant set of cards, etc, that actually have flickering and freezing problems from powermizer. That would be solved if it defaulted to off and could be changed later somehow. In any case, absent that it will be difficult for most people to fix once they are in that state where they can't even see or log in, and I would imagine there are not many who would even figure out that powermizer was the problem in the first place. The nvidia-settings app is nvidia's, as is powermizer itself, so I see some of the passing of the buck there. However, there's no reason we can't do something about xorg.conf within Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/456637 Title: Please consider turning powermizer OFF -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591388] Re: marking libsdl1.2debian-all for install marks ubuntu-desktop for removal
This problem continues in Maverick Meerkat (10.10) it was not an issue in Karmic. I needed to install the all package to support esd .. I guess i can't now. I say the option that -all satisfies all dependencies for the others makes more sense. I am pretty sure that is how it is handled before; it is sad it has appeared now. ** Tags added: maverick -- marking libsdl1.2debian-all for install marks ubuntu-desktop for removal https://bugs.launchpad.net/bugs/591388 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 433146] Re: xfstt assert failure: *** buffer overflow detected ***: /usr/bin/xfstt terminated
Okay it says the fix is released, but in what version? I have the latest package and this still continuously happens. Further, the bug continues to exist in Lucid https://bugs.launchpad.net/ubuntu/+source/xfstt/+bug/575026 I see the patch in here, but is it going to get included in a package? I though that was what fix released meant. -- xfstt assert failure: *** buffer overflow detected ***: /usr/bin/xfstt terminated https://bugs.launchpad.net/bugs/433146 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 648436] [NEW] package ecm 1.00-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/bin/ecm', which is also in package gmp-ecm 0:6.2-1
Public bug reported: Binary package hint: ecm gmp-ecm and ecm are both packages in Universe. The first is a math program and the second one deals with a format for cdrom images. Apparently they both call their command ecm. These are the involved versions: $ apt-cache policy gmp-ecm gmp-ecm: Installed: 6.2-1 Candidate: 6.2-1 Version table: *** 6.2-1 0 500 http://us.archive.ubuntu.com karmic/universe Packages 100 /var/lib/dpkg/status That is what I had installed when I tried to install ecm (and it failed). This is the ecm package: $ apt-cache policy ecm ecm: Installed: 1.00-0ubuntu2 Candidate: 1.00-0ubuntu2 Version table: *** 1.00-0ubuntu2 0 500 http://us.archive.ubuntu.com karmic/universe Packages 100 /var/lib/dpkg/status $ If I had had ecm installed and tried to install gmp-ecm it would have been the same problem, obviously so the problem really affects both packages. ProblemType: Package AptOrdering: ecm: Install ecm: Configure Architecture: amd64 Date: Sun Sep 26 17:33:28 2010 DistroRelease: Ubuntu 9.10 ErrorMessage: trying to overwrite '/usr/bin/ecm', which is also in package gmp-ecm 0:6.2-1 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) NonfreeKernelModules: nvidia Package: ecm 1.00-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.31-22.65-server SourcePackage: ecm Title: package ecm 1.00-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/bin/ecm', which is also in package gmp-ecm 0:6.2-1 Uname: Linux 2.6.31-22-server x86_64 ** Affects: ecm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package -- package ecm 1.00-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/bin/ecm', which is also in package gmp-ecm 0:6.2-1 https://bugs.launchpad.net/bugs/648436 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 648436] Re: package ecm 1.00-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/bin/ecm', which is also in package gmp-ecm 0:6.2-1
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/648436/+attachment/1641161/+files/Dependencies.txt ** Attachment added: Dmesg.txt https://bugs.launchpad.net/bugs/648436/+attachment/1641162/+files/Dmesg.txt ** Attachment added: DpkgTerminalLog.gz https://bugs.launchpad.net/bugs/648436/+attachment/1641163/+files/DpkgTerminalLog.gz ** Attachment added: XsessionErrors.txt https://bugs.launchpad.net/bugs/648436/+attachment/1641164/+files/XsessionErrors.txt -- package ecm 1.00-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/bin/ecm', which is also in package gmp-ecm 0:6.2-1 https://bugs.launchpad.net/bugs/648436 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 648436] Re: package ecm 1.00-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/bin/ecm', which is also in package gmp-ecm 0:6.2-1
This was in Karmic -- package ecm 1.00-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/bin/ecm', which is also in package gmp-ecm 0:6.2-1 https://bugs.launchpad.net/bugs/648436 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 466701] Re: package xscreensaver-data-extra (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man6/pacman.6.gz', which is also in package pacman 0:10-17ubuntu1
except that it hasn't been fixed. or at least it hasn't been fixed for karmic. I haven't made the jump to lucid yet. -- package xscreensaver-data-extra (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man6/pacman.6.gz', which is also in package pacman 0:10-17ubuntu1 https://bugs.launchpad.net/bugs/466701 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 466701] Re: package xscreensaver-data-extra (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man6/pacman.6.gz', which is also in package pacman 0:10-17ubuntu1
it seems silly that such a simple patch could not be applied to karmic packages, especially since it looks like it is Ubuntu's fault and it would only require adding ONE CHARACTER (an x) to the package instructions. -- package xscreensaver-data-extra (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man6/pacman.6.gz', which is also in package pacman 0:10-17ubuntu1 https://bugs.launchpad.net/bugs/466701 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 359517] Re: kstars does not support indi
I'm on karmic, and the kstars package still causes this error. So is it really fixed? -- kstars does not support indi https://bugs.launchpad.net/bugs/359517 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdeedu in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 359517] Re: kstars does not support indi
OK, it looks like I had indi on my system. Getting rid of it was pretty ugly. apt-get remove wouldn't work because the kstars package and others were broken, fix didn't work because libindi0 gave the error trying to overwrite '/usr/bin/indiserver' as above. In the end I was able to do dpkg -r indi and get rid of indi, then these things installed properly. I would say the fact we still have packages stomping on each other (because I am pretty sure I checked indi along with the others in synaptic and that is what brought this on) is kind of a problem. -- kstars does not support indi https://bugs.launchpad.net/bugs/359517 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 563486] Re: 9.10 (Karmic): gnome-volume-control segmentation fault on startup (crashed with SIGSEGV in _int_free())
** Attachment added: trace-bugreport.tar.gz http://launchpadlibrarian.net/44206093/trace-bugreport.tar.gz ** Attachment added: CoreDump.gz http://launchpadlibrarian.net/44204934/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/44204938/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/44204939/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/44204941/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/44204943/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/44204944/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/44204946/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/44204947/ThreadStacktrace.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/44204949/XsessionErrors.txt ** Visibility changed to: Public -- 9.10 (Karmic): gnome-volume-control segmentation fault on startup (crashed with SIGSEGV in _int_free()) https://bugs.launchpad.net/bugs/563486 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 563486] Re: 9.10 (Karmic): gnome-volume-control segmentation fault on startup (crashed with SIGSEGV in _int_free())
One other thing ... I know that I have installed several updates from update manager since the font problem. It could just as well be that one of these broke gnome-volume-control. -- 9.10 (Karmic): gnome-volume-control segmentation fault on startup (crashed with SIGSEGV in _int_free()) https://bugs.launchpad.net/bugs/563486 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 563486] Re: 9.10 (Karmic): gnome-volume-control segmentation fault on startup (crashed with SIGSEGV in _int_free())
This turns out to be a duplicate of the following bug because it was caused by pango-graphite https://bugs.launchpad.net/ubuntu/+source/pango-graphite/+bug/404681 pango-graphite broke my gnome-volume-control as well as gnome-appearance-properties by causing segfaults. It also caused xchat to break as far as how it renders fonts (the end of the line would get cut off and some words would be mashed together ... highlighting the line revealed the beginning and end that were cut off) , and, I am sure, caused instability in Firefox (constant crashes just from running it). Uninstalling pango-graphite fixed the appearance as well as the volume control problem. -- 9.10 (Karmic): gnome-volume-control segmentation fault on startup (crashed with SIGSEGV in _int_free()) https://bugs.launchpad.net/bugs/563486 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 404681] Re: gnome-appearance-properties crashed with SIGSEGV in free()
pango-graphite broke my gnome-volume-control as well as gnome- appearance-properties by causing segfaults. It also caused xchat to break as far as how it renders fonts (the end of the line would get cut off and some words would be mashed together ... highlighting the line revealed the beginning and end that were cut off) , and, I am sure, caused instability in Firefox (constant crashes just from running it). Uninstalling pango-graphite fixed the appearance as well as the volume control problem. -- gnome-appearance-properties crashed with SIGSEGV in free() https://bugs.launchpad.net/bugs/404681 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 404681] Re: gnome-appearance-properties crashed with SIGSEGV in free()
Uninstalling also fixed a problem where the following programs crashed when trying to open or save files (which had started after pango-graphite was installed): gnumeric, openoffice (calc), gimp, kspread All of those started working again when I uninstalled pango-graphite. -- gnome-appearance-properties crashed with SIGSEGV in free() https://bugs.launchpad.net/bugs/404681 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 148454] Re: console-kit-daemon spawns too many threads
I am running Ubuntu 9.10 on AMD 64-bit and I have this bug. I disagree with those who say the resource waste from this bug is negligible because at least in my case I have 64 instances of this process, each of which are using over 122MB of RAM, 117MB of which is virtual. That's a total of over 7.6GB for a set of processes that have no discernable purpose. If it's supposed to be monitoring terminals including pseudoterminals, it t seems strange that it would be starting so many instances. It's even more egregious if it is supposed to be monitoring real ttys. Even if you wanted to monitor a bunch of terms, wouldn't it make more sense to spawn a more conservative, perhaps configurable, number of processes at the outset and spawn more as needed? That's basically the model for programs like Apache and, if memory serves, sshd. If it's good enough there it would seem it should be good enough here. At the very least we should have a better explanation of why this daemon is deemed necessary so we can seek alternatives, or have some workaround. I'll try killing the processes, but it seems to me that just killing off all the processes for a program that is poorly understood, at the very least killing all instead of some, is a poor administrative solution. I've been having performance problems as well, and I have to wonder if at least part of the problem is not due to this. At the very least that much memory being used is a problem, and I originally sought out answers when I needed to free up some memory. -- console-kit-daemon spawns too many threads https://bugs.launchpad.net/bugs/148454 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 400485] Re: Empathy sounds not in default ubuntu theme
I have no sounds, either (in Karmic). I installed the freedesktop theme as above but that did not make the sounds work. Is there some workaround to get sounds in Empathy? -- Empathy sounds not in default ubuntu theme https://bugs.launchpad.net/bugs/400485 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 486154] Re: System beep broken in Karmic despite heroic efforts to fix it
Thank you thank you thank you Grondr and Robert for giving some respite to people who are suffering from this horrible bug. This problem is highly annoying to me. The initial reason for neutering the pc speaker was that besides it being outdated you had to grovel through 8 miles of innards to get it to be turned off. Unfortunately the solution resulted in no beep at all (so much for the outdated idea -- if it was outdated to have the pc speaker beep why didn't they make a configurable alert sound take over for it?). It also means you have to grovel through 8 miles of innards to get it back on again, and even then it's actually a sad string of hacks designed to turn it back on after the bits put in by the bell-killers turn it off. When I first ran into this, I thought it was a resurrection of an xterm bug (in version 242, here: http://invisible-island.net/xterm/xterm.log.html#xterm_243 )that had plagued me in cygwin (which required me to recompile xterm for that platform), but no such luck. By the way, two whole other sets of directions regarding the bell in ubuntu are here http://ubuntuforums.org/showthread.php?t=1377990 and here http://ubuntuforums.org/showthread.php?t=1377990 I've done everything in the Grondr's comment except for patching metacity, and everything in those two forum threads except for the bit about changing the bell sound. What I don't like is that I have to remember to do xset b 100 every time I boot up because even though it's in my .xinitrc it doesn't happen. I've put it in my .profile, but that is a hack, and I still haven't rebooted yet to see if that will be sufficient. I should be able to configure the x bell with respect to x, using its init files. What I have not explored yet, is the probability that the bell is still neutered with respect to the computer's state before X is launched, and regular consoles. Console beeps should work, or at least be configurable in some way. What would be nice is if you could easily set this without having to grovel through all these places, and whatever you did to do it would undo the things that were done to neuter the bell rather than reacting to them. What would be even nicer is if you could set the bell sound, too. It appears that you can, if you dig deep enough, but at this stage I'm still trying to make sure I have the bell turned on in enough places, and I find more places that it is not and more places where my settings are ignored every day. Applications that don't speak to sound mixers should be allowed to produce pc speaker beeps, as should the kernel itself. If we are going to try to intercept that, it should be in a way that ensures it will still work, and make both the interception and what we do with it configurable. Likewise, errors made in gui apps and other apps that can speak to the sound mixer should have a configurable sound. I hope that anyone who is affected by this finds a solution that works for them. Expect to have to wrestle it awhile, and to have a frustrating time going through all these places. I did get my beep to work, I just have to keep turning it back on, and I still worry that there are situations in which the beep is still not happening when it should. If we could find all the places where the bell was neutered and how, maybe we could make a better solution for undoing it or produce patches that either make it configurable or turn it on again. Ubuntu being what it is, maybe gui configuration is the way to go. But whatever we do needs to be compatible with legacy applications. -- System beep broken in Karmic despite heroic efforts to fix it https://bugs.launchpad.net/bugs/486154 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
