[Bug 435831] [NEW] unclutter shouldn't be enabled by default
Public bug reported: Binary package hint: unclutter When you install unclutter it starts automatically every time you boot your computer. This is set in '/etc/default/unclutter'. It can be confusing for many users (it was for me). I believe the default should be changed so that the user has to enable it. Thanks. ** Affects: unclutter (Ubuntu) Importance: Undecided Status: New -- unclutter shouldn't be enabled by default https://bugs.launchpad.net/bugs/435831 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 352517] [NEW] plasmoid-memusage should be replaced with dummy package
Public bug reported: Binary package hint: plasmoid-memusage Since the upstream naming conventions changed for plasmoids and there exists a version of memusage (plasma-widget-memusage), the old one should be replaced with a dummy package, like the rest of the plasmoids. Currently both versions exist adding to confusion. PS. that is under Ubuntu 9.04 beta ** Affects: plasmoid-memusage (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: plasmoid-memusage Since the upstream naming conventions changed for plasmoids and there exists a version of memusage (plasma-widget-memusage), the old one should be replaced with a dummy package, like the rest of the plasmoids. Currently both versions exist adding to confusion. + + PS. that is under Ubuntu 9.04 beta -- plasmoid-memusage should be replaced with dummy package https://bugs.launchpad.net/bugs/352517 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 352508] [NEW] system status widget does not work correctly
Public bug reported: Binary package hint: plasma-widget-system-status Using plasma-widget-system-status 0.5-0ubuntu6 under Kubuntu 9.04 (beta): * the widget is listed as System Monitor under Add Widgets dialog while it should be called System Status or System Load Monitor to avoid confusion with another widget sharing the same name. It seams to me that the name has changed according to the kde-apps page * after adding the widget to the panel it doesn't work (the bars remain empty no matter the actual load) * there is no custom icon in the Add Widgets dialog and the default one is used, which I understand might not be 'buntu's responsibility Finally there is a new version available (0.6) ** Affects: plasma-widget-system-status (Ubuntu) Importance: Undecided Status: New -- system status widget does not work correctly https://bugs.launchpad.net/bugs/352508 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 352508] Re: system status widget does not work correctly
** Attachment added: "not working system status widget" http://launchpadlibrarian.net/24581679/snapshot1.png -- system status widget does not work correctly https://bugs.launchpad.net/bugs/352508 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 156172] Re: computer freezes randomly when running Kopete
I no longer have this problem thus I'm closing this report as invalid. ** Changed in: kopete (Ubuntu) Status: New => Invalid -- computer freezes randomly when running Kopete https://bugs.launchpad.net/bugs/156172 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kopete in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 153500] Re: Kopete crashes on startup
To enable debugging support you have to install the -dbg packages. For Kopete that's kdenetwork-dbg It's not installed by default because it slows down the computer performance. -- Kopete crashes on startup https://bugs.launchpad.net/bugs/153500 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdelibs in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 156172] Re: computer freezes randomly when running Kopete
I forgot to mention that I'm using an up to date Gutsy installation. -- computer freezes randomly when running Kopete https://bugs.launchpad.net/bugs/156172 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kopete in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 156172] computer freezes randomly when running Kopete
Public bug reported: Binary package hint: kopete I have noticed that my computer freezes when I have an open chat window. It seems random to me. I can't install the -dbg packages to get a debug report or something cause the kdelibs package on official repos won't let me connect to msn (known problem) and there is no -dev or -dbg packages for the patched deb. It might have something to do with msn contacts but I have very few jabber contacts to test it with other protocols. Each time it crashed my pc, I was talking with a different contact, if that helps. What's the best way to debug this problem? My pc freezes completely and only a hard reset will do any good (tower button reset). ** Affects: kopete (Ubuntu) Importance: Undecided Status: New -- computer freezes randomly when running Kopete https://bugs.launchpad.net/bugs/156172 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kopete in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 153500] Re: Kopete crashes on startup
It also worked for me. Any chance we would see updated -dev and -dbg debs before official repo updates? -- Kopete crashes on startup https://bugs.launchpad.net/bugs/153500 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdelibs in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 153500] Re: Kopete crashes on startup
I have the same problem. Console output: QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key kopete: ERROR: : couldn't create slave : Unable to create io-slave: klauncher said: Unknown protocol ''. kopete: KCrash: Application 'kopete' crashing... KDE Crash Handler with dbg: Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1241896464 (LWP 30109)] [KCrash handler] #6 MSNAccount::slotNotifySocketClosed (this=0x82d57a8) at /build/buildd/kdenetwork-3.5.8/./kopete/protocols/msn/msnnotifysocket.h:72 #7 0xb5901668 in MSNAccount::qt_invoke (this=0x82d57a8, _id=33, _o=0xbfbbc65c) at ./msnaccount.moc:227 #8 0xb6842893 in QObject::activate_signal (this=0x8467ba8, clist=0x84684d8, o=0xbfbbc65c) at kernel/qobject.cpp:2356 #9 0xb6843338 in QObject::activate_signal (this=0x8467ba8, signal=5) at kernel/qobject.cpp:2325 #10 0xb590a8dc in MSNSocket::socketClosed (this=0x8467ba8) at ./msnsocket.moc:204 #11 0xb591e4cd in MSNNotifySocket::disconnect (this=0x8467ba8) at /build/buildd/kdenetwork-3.5.8/./kopete/protocols/msn/msnnotifysocket.cpp:101 #12 0xb591af3b in MSNNotifySocket::sslLoginFailed (this=0x8467ba8) at /build/buildd/kdenetwork-3.5.8/./kopete/protocols/msn/msnnotifysocket.cpp:673 #13 0xb59210f5 in MSNNotifySocket::qt_invoke (this=0x8467ba8, _id=22, _o=0xbfbbc7ac) at ./msnnotifysocket.moc:387 #14 0xb6842893 in QObject::activate_signal (this=0x8472bb0, clist=0x8465e90, o=0xbfbbc7ac) at kernel/qobject.cpp:2356 #15 0xb6843338 in QObject::activate_signal (this=0x8472bb0, signal=4) at kernel/qobject.cpp:2325 #16 0xb593b16c in MSNSecureLoginHandler::loginFailed (this=0x8472bb0) at ./msnsecureloginhandler.moc:113 #17 0xb593b40f in MSNSecureLoginHandler::slotTweenerReceived (this=0x8472bb0, authJob=0x847ee38) at /build/buildd/kdenetwork-3.5.8/./kopete/protocols/msn/msnsecureloginhandler.cpp:128 #18 0xb593c5a6 in MSNSecureLoginHandler::qt_invoke (this=0x8472bb0, _id=3, _o=0xbfbbc8d4) at ./msnsecureloginhandler.moc:120 #19 0xb6842893 in QObject::activate_signal (this=0x847ee38, clist=0x8472cd8, o=0xbfbbc8d4) at kernel/qobject.cpp:2356 #20 0xb747d021 in KIO::Job::result (this=0x847ee38, t0=0x847ee38) at ./jobclasses.moc:162 #21 0xb74d58cd in KIO::Job::emitResult (this=0x847ee38) at /build/buildd/kdelibs-3.5.8/./kio/kio/job.cpp:235 #22 0xb74d5d2e in KIO::SimpleJob::slotFinished (this=0x847ee38) at /build/buildd/kdelibs-3.5.8/./kio/kio/job.cpp:601 #23 0xb74d643d in KIO::TransferJob::slotFinished (this=0x847ee38) at /build/buildd/kdelibs-3.5.8/./kio/kio/job.cpp:971 #24 0xb74d5301 in KIO::SimpleJob::qt_invoke (this=0x847ee38, _id=7, _o=0xbfbbcc38) at ./jobclasses.moc:417 #25 0xb74d5363 in KIO::TransferJob::qt_invoke (this=0x847ee38, _id=7, _o=0xbfbbcc38) at ./jobclasses.moc:1082 #26 0xb6842893 in QObject::activate_signal (this=0x82033c8, clist=0x84426f8, o=0xbfbbcc38) at kernel/qobject.cpp:2356 #27 0xb6bce8ec in QSignal::signal (this=0x82033c8, [EMAIL PROTECTED]) at .moc/debug-shared-mt/moc_qsignal.cpp:100 #28 0xb6862842 in QSignal::activate (this=0x82033c8) at kernel/qsignal.cpp:212 #29 0xb686a258 in QSingleShotTimer::event (this=0x82033a0) at kernel/qtimer.cpp:286 #30 0xb67d9af0 in QApplication::internalNotify (this=0xbfbbd264, receiver=0x82033a0, e=0xbfbbcf88) at kernel/qapplication.cpp:2635 #31 0xb67db91f in QApplication::notify (this=0xbfbbd264, receiver=0x82033a0, e=0xbfbbcf88) at kernel/qapplication.cpp:2358 #32 0xb6f9fca2 in KApplication::notify (this=0xbfbbd264, receiver=0x82033a0, event=0xbfbbcf88) at /build/buildd/kdelibs-3.5.8/./kdecore/kapplication.cpp:550 #33 0xb676c209 in QApplication::sendEvent (receiver=0x82033a0, event=0xbfbbcf88) at ../include/qapplication.h:520 #34 0xb67cc53b in QEventLoop::activateTimers (this=0x815e220) at kernel/qeventloop_unix.cpp:556 #35 0xb6780d49 in QEventLoop::processEvents (this=0x815e220, flags=4) at kernel/qeventloop_x11.cpp:389 #36 0xb67f41ce in QEventLoop::enterLoop (this=0x815e220) at kernel/qeventloop.cpp:198 #37 0xb67f3fde in QEventLoop::exec (this=0x815e220) at kernel/qeventloop.cpp:145 #38 0xb67db699 in QApplication::exec (this=0xbfbbd264) at kernel/qapplication.cpp:2758 #39 0x0807f95c in main (argc=8372248, argv=0xb6d93a80) at /build/buildd/kdenetwork-3.5.8/./kopete/kopete/main.cpp:107 #40 0xb5fe9050 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6 #41 0x0806f071 in _start () -- Kopete crashes on startup https://bugs.launchpad.net/bugs/153500 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdenetwork in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 113972] wrong link in .deb summary
Public bug reported: Binary package hint: ktorrent The homepage link in ktorrent's deb is http:/i/ktorrent.org Please remove the bogus 'i'. ** Affects: ktorrent (Ubuntu) Importance: Undecided Status: Confirmed -- wrong link in .deb summary https://bugs.launchpad.net/bugs/113972 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for ktorrent in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 113972] Re: wrong link in .deb summary
That's on feisty... ** Changed in: ktorrent (Ubuntu) Status: Unconfirmed => Confirmed -- wrong link in .deb summary https://bugs.launchpad.net/bugs/113972 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for ktorrent in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 97555] Re: direct rendering no longer works
I removed the restricted modules and nvidia-glx stuff and installed driver from nvidia's site. That fixed the problem. I attach my new X log as I didn't change anything other than the driver, so you can see any differences. If you need me to test anything, I can reinstall the ubuntu driver. ** Attachment added: "Xorg.0.log" http://librarian.launchpad.net/7468758/Xorg.0.log -- direct rendering no longer works https://bugs.launchpad.net/bugs/97555 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97555] Re: direct rendering no longer works
** Attachment added: "Xorg.0.log" http://librarian.launchpad.net/7411615/Xorg.0.log -- direct rendering no longer works https://bugs.launchpad.net/bugs/97555 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97555] Re: direct rendering no longer works
Just another output: glxinfo -v ** Attachment added: "glxinfo.output" http://librarian.launchpad.net/7410840/glxinfo.output -- direct rendering no longer works https://bugs.launchpad.net/bugs/97555 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 97555] Re: direct rendering no longer works
I seem to have the same problem. I use nvidia-glx-new. My card is GeForce 7600 GS 256MB AGP. I upgraded from edgy to feisty final. ** Attachment added: "xorg.conf" http://librarian.launchpad.net/7410832/xorg.conf -- direct rendering no longer works https://bugs.launchpad.net/bugs/97555 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106732] Re: bogus splashimage line in menu.lst after installation
Oops just noticed a mistake in my first report. The correct line should be "splashimage=(hd0,2)/boot/grub/splashimages/KUBUNTU_splashscreen_blue_neon_logo_03.xpm.gz" -- bogus splashimage line in menu.lst after installation https://bugs.launchpad.net/bugs/106732 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kubuntu-grub-splashimages in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 106732] bogus splashimage line in menu.lst after installation
Public bug reported: Binary package hint: kubuntu-grub-splashimages While upgrading from edgy to feisty I installed kubuntu-grub-splashimages. After the first reboot, grub informed me of being unable to find the selected splashimage. The problem was the splashimage line in menu.lst, which was "splashimage=,2)/boot/grub/splashimages/KUBUNTU_splashscreen_blue_neon_logo_03.xpm.gz", while it should read "splashimage=(0,2)/boot/..." ** Affects: kubuntu-grub-splashimages (Ubuntu) Importance: Undecided Status: Unconfirmed -- bogus splashimage line in menu.lst after installation https://bugs.launchpad.net/bugs/106732 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64531] Re: apt-index-watcher uses way too much system ressources
It is still bugged for me too. version 0.3.9ubuntu5 Actually a better command to close it, is: sudo /etc/init.d/apt-index-watcher stop -- apt-index-watcher uses way too much system ressources https://launchpad.net/bugs/64531 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs