[Bug 123696] Re: dependency problem on Kubuntu
Just applied Bård's patch here, and it works great. Thanks! Bård - any chance at re-submitting this upsteam? -- dependency problem on Kubuntu https://bugs.launchpad.net/bugs/123696 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 299270] [NEW] Can't build KDE apps due to incorrect cmake file
Public bug reported:
I'm trying to build the kopete tree from the SVN tree, to do some
general kopete development work.
However due to an incorrect dependency in the cmake files from the
kdelibs5 package, the build fails:
make[2]: *** No rule to make target
`/build/buildd/kde4libs-4.1.2/obj-i486-linux-gnu/lib/libkdecore.so',
needed by `lib/libkopete.so.4.1.0'. Stop.
It looks like this dependency is caused by the following lines in
/usr/share/kde4/apps/cmake/modules/KDELibsDependenciesInternal.cmake:
SET("solid_LIB_DEPENDS"
"general;/usr/lib/libQtCore.so;general;/usr/lib/libQtDBus.so;general;/usr/lib/libQtXml.so;general;/usr/lib/libQtGui.so;general;/build/buildd/kde4libs-4.1.2/obj-i486
-linux-gnu/lib/libkdecore.so;")
SET("solid_LIB_DEPENDS"
"/usr/lib/libQtCore.so;/usr/lib/libQtDBus.so;/usr/lib/libQtXml.so;/usr/lib/libQtGui.so;/build/buildd/kde4libs-4.1.2/obj-i486
-linux-gnu/lib/libkdecore.so;")
The reference to the /build/buildd path looks like a left-over from the
package build system. These paths should instead reference /usr/lib.
Changing these paths to /usr/lib/libkdecore.so fixes the problem for me.
** Affects: kde4libs (Ubuntu)
Importance: Undecided
Status: New
** Tags: buildd cmake kde
--
Can't build KDE apps due to incorrect cmake file
https://bugs.launchpad.net/bugs/299270
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kde4libs in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 295329] Re: konqueror looses connection to klauncher
Same problem here. Another sympton is that konqueror keeps prompting to restore a crash session. These problems have been reported in kde bugs 167667 and 164307. Looks like this has been fixed in KDE SVN, commit r870787. Could the kubuntu team backport this change to the kdebase package? Thanks, Jeremy -- konqueror looses connection to klauncher https://bugs.launchpad.net/bugs/295329 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 251218] Re: Kopete KDE4 doesn't support sametime (meanwhile) protocol
I have a series of patches to update the kopete meanwhile plugin in KDE4, which will be committed to KDE svn soon. Once these are in, the kubuntu folks will need to enable the meanwhile plugin for this to work. In the meantime, I've ported these over to the intrepid kopete source: http://ozlabs.org/~jk/tmp/intrepid-kopete-meanwhile/ To build a kopte-meanwhile package: sudo apt-get build-dep kopete sudo apt-get install libmeanwhile-dev sudo apt-get source kopete cd kdenetwork-4.1.2 wget http://ozlabs.org/~jk/tmp/intrepid-kopete-meanwhile/intrepid-kopete-meanwhile.tar.gz tar -zxvf intreprid-kopete-meanwhile.tar.gz dpkg-buildpackage -rfakeroot sudo dpkg -i ../kopete-meanwhile_4.1.2-0ubuntu4-jk2_i386.deb -- Kopete KDE4 doesn't support sametime (meanwhile) protocol https://bugs.launchpad.net/bugs/251218 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdenetwork in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 251218] Re: Kopete KDE4 doesn't support sametime (meanwhile) protocol
OK, all committed now, so kdenetwork SVN should have meanwhile support. Revisions r885903 to r885908 contain the meanwhile updates. Ubuntu packaging folks: feel free to get in touch if you need a hand with this. -- Kopete KDE4 doesn't support sametime (meanwhile) protocol https://bugs.launchpad.net/bugs/251218 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 283100] Re: powertop shows kwin generating lots of wakeups (intrepid, kde4)
I just did some experimentation to reduce kwin-induced wakeups. Initially, I was seeing around 50-60 wakeups per sec due to kwin. By turning off the 'Track Mouse' effect, I now see around 11 per sec. Using jaunty here, with uxa accelleration. -- powertop shows kwin generating lots of wakeups (intrepid, kde4) https://bugs.launchpad.net/bugs/283100 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 340265] Re: pthread manpages missing
Makes sense, closing. ** Changed in: glibc (Ubuntu) Status: New => Invalid -- pthread manpages missing https://bugs.launchpad.net/bugs/340265 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 367689] [NEW] Python reference doesn't include standard library
Public bug reported: The python2.6-doc package seems to have not generated the "standard library" reference. This is the section of the doc that I tend to refer to the most. Compare: /usr/share/doc/python2.6/html/library/index.html with: http://docs.python.org/library/ Both have the text: "Python’s standard library is very extensive, offering a wide range of facilities as indicated by the long table of contents listed below" but there is no "long table of contents" in the packaged version of the docs. ** Affects: python2.6 (Ubuntu) Importance: Undecided Status: New -- Python reference doesn't include standard library https://bugs.launchpad.net/bugs/367689 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 340265] [NEW] pthread manpages missing
Public bug reported: Using jaunty alpha packages (version shown below), the pthread_create manpage appears to be missing: [...@pingu ~]$ man pthread_create No manual entry for pthread_create The glibc-doc package still contains some pthread manpages, but not all. The list of manpages that seem to have been dropped since intrepid: pthread_attr_destroy pthread_attr_getdetachstate pthread_attr_getinheritsched pthread_attr_getschedparam pthread_attr_getschedpolicy pthread_attr_getscope pthread_attr_init pthread_attr_setdetachstate pthread_attr_setinheritsched pthread_attr_setschedparam pthread_attr_setschedpolicy pthread_attr_setscope pthread_cancel pthread_cleanup_pop pthread_cleanup_pop_restore_np pthread_cleanup_push pthread_cleanup_push_defer_np pthread_create pthread_detach pthread_equal pthread_exit pthread_getschedparam pthread_join pthread_self pthread_setcancelstate pthread_setcanceltype pthread_setschedparam pthread_testcancel 'apt-cache search pthread' doesn't suggest any alternative package that these manpages may have moved to. [...@pingu ~]$ apt-cache policy glibc-doc glibc-doc: Installed: 2.9-4ubuntu2 Candidate: 2.9-4ubuntu2 Version table: *** 2.9-4ubuntu2 0 500 http://mirror.internode.on.net jaunty/main Packages 100 /var/lib/dpkg/status ** Affects: glibc (Ubuntu) Importance: Undecided Status: New -- pthread manpages missing https://bugs.launchpad.net/bugs/340265 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 340280] [NEW] Agenda views are completely blank
Public bug reported: Binary package hint: korganizer Using jaunty packages here (version listed below) When I open an 'agenda view' in korganizer (ie, day view or week view), the area where the calendar should be is completely blank. Screenshot attached (however, there seems to be an additional black area in the screenshot. This is not present on the actual UI) This problem also occurs with a completely new user with no existing KDE settings. [...@pingu ~]$ apt-cache policy korganizer korganizer: Installed: 4:4.2.1-0ubuntu1 Candidate: 4:4.2.1-0ubuntu1 Version table: *** 4:4.2.1-0ubuntu1 0 500 http://mirror.internode.on.net jaunty/main Packages 100 /var/lib/dpkg/status ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New -- Agenda views are completely blank https://bugs.launchpad.net/bugs/340280 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 340280] Re: Agenda views are completely blank
** Attachment added: "blank agenda view screenshot" http://launchpadlibrarian.net/23685656/korganizer-screenshot.png -- Agenda views are completely blank https://bugs.launchpad.net/bugs/340280 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 338628] Re: corrupted graphics, choppy scrolling
I'm seeing the same corrupted graphics and gui slowness, but am using the intel video driver. Perhaps this is a general kdeui or qt bug? [...@pingu ~]$ apt-cache policy xserver-xorg-video-intel kdelibs5 libqt4-core xorg xserver-xorg-video-intel: Installed: 2:2.6.1-1ubuntu4 Candidate: 2:2.6.1-1ubuntu4 Version table: *** 2:2.6.1-1ubuntu4 0 500 http://mirror.internode.on.net jaunty/main Packages 100 /var/lib/dpkg/status kdelibs5: Installed: 4:4.2.1a-0ubuntu2 Candidate: 4:4.2.1a-0ubuntu2 Version table: *** 4:4.2.1a-0ubuntu2 0 500 http://mirror.internode.on.net jaunty/main Packages 100 /var/lib/dpkg/status libqt4-core: Installed: 4.5.0-0ubuntu1 Candidate: 4.5.0-0ubuntu1 Version table: *** 4.5.0-0ubuntu1 0 500 http://mirror.internode.on.net jaunty/main Packages 100 /var/lib/dpkg/status xorg: Installed: 1:7.4~5ubuntu13 Candidate: 1:7.4~5ubuntu13 Version table: *** 1:7.4~5ubuntu13 0 500 http://mirror.internode.on.net jaunty/main Packages 100 /var/lib/dpkg/status -- corrupted graphics, choppy scrolling https://bugs.launchpad.net/bugs/338628 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 338205] Re: [jaunty] plasma crashes on start with SIGSEGV
Is the status for this bug really fix commited/fix released? The fix may have been comitted/released upstream, but (from the above comments) it sounds like it's not going to be included in jaunty. Given that the kde 4.2.2 release is scheduled for after the jaunty release, we won't see the fix in kubuntu until jaunty+1. Is this correct? -- [jaunty] plasma crashes on start with SIGSEGV https://bugs.launchpad.net/bugs/338205 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 338205] Re: [jaunty] plasma crashes on start with SIGSEGV
Running krandrtray doesn't work for me - just tried this, and plasma still crashes. I still need to edit the geometry settings manually. I've shortened the process by keeping a 'clean' plasma-appletsrc file for each possible monitor configuration (3: work, home, and laptop-only modes). When the configuration changes, I just copy in the right file. Kinda hacky, but sucks less than not having plasma working. -- [jaunty] plasma crashes on start with SIGSEGV https://bugs.launchpad.net/bugs/338205 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 340280] Re: Agenda views are completely blank
OK, Interesting. I had "0,0" as the config parameter for "Separator AgendaView", so looks like this change won't affect my setup here - sizes.count() would return 2, so we'd get the unpatched behaviour regardless. Workaround is simple though, I just put sensible values in there instead (in my case, "400,600"). -- Agenda views are completely blank https://bugs.launchpad.net/bugs/340280 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 251593] Re: unknown filesytem type: spufs
> But I couldn't create directories below it (as described in Arnd's > arcticle [1]) even as root. However I need to go back and revisit > this later as I may have made an error somewhere. You won't be able to mkdir in the spufs mount point - only the spu_create system call will be able to create entries in spufs (the article is a little old). If you'd like to test that spufs is working, the spufs testsuite might be handy: http://git.kernel.org/?p=linux/kernel/git/jk/spufs-testsuite.git -- unknown filesytem type: spufs https://bugs.launchpad.net/bugs/251593 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 295329] Re: konqueror looses connection to klauncher
Looks to be fixed in 4:4.1.3-0ubuntu1~intrepid1 due to the new upstream version. -- konqueror looses connection to klauncher https://bugs.launchpad.net/bugs/295329 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 308473] [NEW] konsole doesn't respect 'show menubar' setting
Public bug reported: After doing an upgrade today (bringing konsole to 4:4.1.3-0ubuntu1~intrepid1), my konsole sessions no longer respect the 'Show Menubar' setting on start. I have konsole configured to hide the menubar by default. When I start a new konsole session, the menubar is always shown. Also, the 'Show Menubar' menu item (in the View menu) is deselected, indicating that the menubar should be disabled. To re-hide the menubar, I need to enable it (ie, select 'Show Menubar' in the View menu), then re-disable it (ie, unselect 'Show Menubar' in the View menu). ** Affects: kdebase (Ubuntu) Importance: Undecided Status: New -- konsole doesn't respect 'show menubar' setting https://bugs.launchpad.net/bugs/308473 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 308473] Re: konsole doesn't respect 'show menubar' setting
Upstream KDE bug 172142, looks like a stale settings problem. Opening the profile settings, enabling and disabling the 'Show menu bar on new windows' option, and hitting 'Apply' Fixed the problem for me. -- konsole doesn't respect 'show menubar' setting https://bugs.launchpad.net/bugs/308473 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 336057] [NEW] Konqueror crashes on startup (when loading about page)
Public bug reported: Using konqueror 4:4.2.0-0ubuntu3 from the jaunty beta here. When I start konqueror from the KDE menu, a key shortcut, or form the command line, nothing happens. Running under gdb reports a SIGSEGV: (gdb) run Starting program: /usr/bin/konqueror (no debugging symbols found) [lines omitted] [Thread debugging using libthread_db enabled] [New Thread 0xb5e9cb40 (LWP 23593)] konqueror(23593) KServiceFactory::findServiceByDesktopPath: "findServiceByDesktopPath: searchproviders/.desktop not found" Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb5e9cb40 (LWP 23593)] 0xb764c46d in KSycocaEntry::property () from /usr/lib/libkdecore.so.5 (gdb) bt #0 0xb764c46d in KSycocaEntry::property () from /usr/lib/libkdecore.so.5 #1 0xb441b0ed in ?? () from /usr/lib/kde4/konq_aboutpage.so #2 0xb44222e0 in ?? () from /usr/lib/kde4/konq_aboutpage.so #3 0xb7f43096 in ?? () from /usr/lib/libkdeinit4_konqueror.so #4 0xb7f944f9 in ?? () from /usr/lib/libkdeinit4_konqueror.so #5 0xb7f4a429 in ?? () from /usr/lib/libkdeinit4_konqueror.so #6 0xb7f4a5a1 in ?? () from /usr/lib/libkdeinit4_konqueror.so #7 0xb7f4b07a in ?? () from /usr/lib/libkdeinit4_konqueror.so #8 0xb7f4bc19 in ?? () from /usr/lib/libkdeinit4_konqueror.so #9 0xb7f50b02 in ?? () from /usr/lib/libkdeinit4_konqueror.so #10 0xb7fca11e in kdemain () from /usr/lib/libkdeinit4_konqueror.so #11 0x080486f2 in _start () (gdb) info frame Stack level 0, frame at 0xbfe20a70: eip = 0xb764c46d in KSycocaEntry::property(QString const&) const; saved eip 0xb441b0ed called by frame at 0xbfe20ca0 Arglist at 0xbfe20a68, args: Locals at 0xbfe20a68, Previous frame's sp is 0xbfe20a70 Saved registers: ebp at 0xbfe20a68, esi at 0xbfe20a64, eip at 0xbfe20a6c (gdb) info registers eax0x0 0 ecx0xbfe20b30 -1075705040 edx0x0 0 ebx0xb4426ff4 -1270714380 esp0xbfe20a50 0xbfe20a50 ebp0xbfe20a68 0xbfe20a68 esi0xbfe20b30 -1075705040 edi0xbfe20bf4 -1075704844 eip0xb764c46d 0xb764c46d eflags 0x210286 [ PF SF IF RF ID ] cs 0x73 115 ss 0x7b 123 ds 0x7b 123 es 0x7b 123 fs 0x0 0 gs 0x33 51 (gdb) Given that the segv is caused in the konq_aboutpage library, the workaround is to start konqueror at a specific URL. However, this requires command-line interaction. ** Affects: kdebase (Ubuntu) Importance: Undecided Status: New -- Konqueror crashes on startup (when loading about page) https://bugs.launchpad.net/bugs/336057 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 270972] Re: gvim hangs on start with gtk-qt-engine-kde4 and qt4 style
Looks to be fixed in jaunty, gvim starts fine. vim-gtk: 2:7.2.079-1ubuntu1 gtk-qt-engine: 1:1.1+svn20080816-0ubuntu6 -- gvim hangs on start with gtk-qt-engine-kde4 and qt4 style https://bugs.launchpad.net/bugs/270972 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to gtk-qt-engine in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338205] [NEW] [jaunty] plasma crashes on start with SIGSEGV
Public bug reported: Binary package hint: kdebase-plasma When I log in via kdm, my KDE session does not have a panel or background. This has started happening since today's upgrades. Versions are listed below. If I try to manually run plasma from the shell, I get a lot of print output from plasma, including the following: plasma(576) InterfaceItem::setEnabled: true plasma(576) NetworkManagerApplet::showVpn: SHOWING (617)/ checkComposite: Plasma has an argb visual 0x9514a10 79691777 (617)/ checkComposite: Plasma can use COMPOSITE for effects on 0x9514360 plasma(575): Communication problem with "plasma" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " KCrash: Application 'plasma' crashing... Running under 'strace -e trace=process -f' gives: plasma(19255) NetworkManagerApplet::showVpn: SHOWING [pid 19255] --- SIGSEGV (Segmentation fault) @ 0 (0) --- Process 19255 detached [pid 19286] +++ killed by SIGSEGV (core dumped) +++ So looks like we have a SIGSEGV. Valgrind shows a breakage in libqtcore4: plasma(3710) NetworkManagerApplet::showVpn: SHOWING ==3710== ==3710== Invalid read of size 4 ==3710==at 0x5A6DEBA: QTimer::stop() (in /usr/lib/libQtCore.so.4.5.0) ==3710==by 0x408387F: (within /usr/lib/libkdeinit4_plasma.so) ==3710==by 0x40884AA: (within /usr/lib/libkdeinit4_plasma.so) ==3710==by 0x5A68CB7: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/libQtCore.so.4.5.0) ==3710==by 0x5A69941: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (in /usr/lib/libQtCore.so.4.5.0) ==3710==by 0x41BD546: Plasma::View::sceneRectAboutToChange() (in /usr/lib/libplasma.so.3.0.0) ==3710==by 0x41BE7AE: (within /usr/lib/libplasma.so.3.0.0) ==3710==by 0x41BDCAA: Plasma::View::qt_metacall(QMetaObject::Call, int, void**) (in /usr/lib/libplasma.so.3.0.0) ==3710==by 0x4088469: (within /usr/lib/libkdeinit4_plasma.so) ==3710==by 0x5A68CB7: QMetaObject::activate(QObject*, int, int, void**) (in /usr/lib/libQtCore.so.4.5.0) ==3710==by 0x5A69941: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (in /usr/lib/libQtCore.so.4.5.0) ==3710==by 0x413E126: Plasma::Applet::geometryChanged() (in /usr/lib/libplasma.so.3.0.0) ==3710== Address 0x8 is not stack'd, malloc'd or (recently) free'd KCrash: Application 'plasma' crashing... Package versions: [...@pingu ~]$ apt-cache policy kdebase-plasma libqtcore4 kdebase-plasma: Installed: 4:4.2.1-0ubuntu1 Candidate: 4:4.2.1-0ubuntu1 Version table: *** 4:4.2.1-0ubuntu1 0 500 http://mirror.internode.on.net jaunty/main Packages 100 /var/lib/dpkg/status libqtcore4: Installed: 4.5.0-0ubuntu1 Candidate: 4.5.0-0ubuntu1 Version table: *** 4.5.0-0ubuntu1 0 500 http://mirror.internode.on.net jaunty/main Packages 100 /var/lib/dpkg/status ** Affects: kdebase (Ubuntu) Importance: Undecided Status: New -- [jaunty] plasma crashes on start with SIGSEGV https://bugs.launchpad.net/bugs/338205 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338205] Re: [jaunty] plasma crashes on start with SIGSEGV
Running under gdb doesn't seem to catch the SEGV, perhaps because plasma forks and detaches from the parent process and/or kcrash is catching the signal? (gdb) run [ lines omitted ] plasma(30010) NetworkManagerApplet::showVpn: SHOWING KCrash: Application 'plasma' crashing... plasma(29977): Communication problem with "plasma" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " Program exited with code 0377. (gdb) (30044)/ checkComposite: Plasma has an argb visual 0x915aa10 81788929 (30044)/ checkComposite: Plasma can use COMPOSITE for effects on 0x915a360 QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout plasma(30046) Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: "NetworkManager 0.7" [ output continues ] I'll see if I can coerce gdb into attaching to the forked processes. -- [jaunty] plasma crashes on start with SIGSEGV https://bugs.launchpad.net/bugs/338205 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 338205] Re: [jaunty] plasma crashes on start with SIGSEGV
OK, got a backtrace: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb4c79710 (LWP 14855)] 0xb663ceba in QTimer::stop () from /usr/lib/libQtCore.so.4 (gdb) bt #0 0xb663ceba in QTimer::stop () from /usr/lib/libQtCore.so.4 #1 0xb7f9f880 in PanelView::updatePanelGeometry (this=0x989f510) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/panelview.cpp:543 #2 0xb7fa44ab in PanelView::qt_metacall (this=0x989f510, _c=QMetaObject::InvokeMetaMethod, _id=16, _a=0xbfa109d8) at /build/buildd/kdebase-workspace-4.2.1a/obj-i486-linux-gnu/plasma/shells/desktop/panelview.moc:112 #3 0xb6637cb8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #4 0xb6638942 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #5 0xb7e9b547 in Plasma::View::sceneRectAboutToChange () from /usr/lib/libplasma.so.3 #6 0xb7e9c7af in ?? () from /usr/lib/libplasma.so.3 #7 0xb7e9bcab in Plasma::View::qt_metacall () from /usr/lib/libplasma.so.3 #8 0xb7fa446a in PanelView::qt_metacall (this=0x989f510, _c=QMetaObject::InvokeMetaMethod, _id=43, _a=0xbfa10c18) at /build/buildd/kdebase-workspace-4.2.1a/obj-i486-linux-gnu/plasma/shells/desktop/panelview.moc:91 #9 0xb6637cb8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #10 0xb6638942 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #11 0xb7e1c127 in Plasma::Applet::geometryChanged () from /usr/lib/libplasma.so.3 #12 0xb7e22930 in Plasma::Applet::itemChange () from /usr/lib/libplasma.so.3 #13 0xb7e3a2bf in Plasma::Containment::itemChange () from /usr/lib/libplasma.so.3 #14 0xb6f07e27 in ?? () from /usr/lib/libQtGui.so.4 #15 0xb6f08053 in QGraphicsItem::setPos () from /usr/lib/libQtGui.so.4 #16 0xb7e38cca in ?? () from /usr/lib/libplasma.so.3 #17 0xb7e3a3c8 in Plasma::Containment::resizeEvent () from /usr/lib/libplasma.so.3 #18 0xb6f520ba in QGraphicsWidget::event () from /usr/lib/libQtGui.so.4 #19 0xb68cef5c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #20 0xb68d723e in QApplication::notify () from /usr/lib/libQtGui.so.4 #21 0xb772471d in KApplication::notify () from /usr/lib/libkdeui.so.5 #22 0xb6621a4b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #23 0xb68da0de in QCoreApplication::sendEvent () from /usr/lib/libQtGui.so.4 #24 0xb6f53185 in QGraphicsWidget::setGeometry () from /usr/lib/libQtGui.so.4 #25 0xb6f50771 in QGraphicsWidget::resize () from /usr/lib/libQtGui.so.4 #26 0xb7fa1103 in PanelView::pinchContainment (this=0x989f510, screenge...@0xbfa11a00) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/panelview.cpp:618 #27 0xb7fa2658 in PanelView (this=0x989f510, panel=0x95b5b78, id=1, parent=0x0) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/panelview.cpp:243 #28 0xb7fac246 in PlasmaApp::createView (this=0x949a998, containment=0x95b5b78) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/plasmaapp.cpp:619 #29 0xb7fac966 in PlasmaApp::containmentAdded (this=0x949a998, containment=0x95b5b78) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/plasmaapp.cpp:663 #30 0xb7facbdc in PlasmaApp::qt_metacall (this=0x949a998, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfa11d0c) at /build/buildd/kdebase-workspace-4.2.1a/obj-i486-linux-gnu/plasma/shells/desktop/plasmaapp.moc:97 #31 0xb6637cb8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #32 0xb6638942 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #33 0xb7e3e2d3 in Plasma::Corona::containmentAdded () from /usr/lib/libplasma.so.3 #34 0xb7e3f8d8 in Plasma::Corona::loadLayout () from /usr/lib/libplasma.so.3 #35 0xb7e40ff1 in Plasma::Corona::initializeLayout () from /usr/lib/libplasma.so.3 #36 0xb7fa958d in PlasmaApp::corona (this=0x949a998) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/plasmaapp.cpp:517 #37 0xb7fa9ba5 in PlasmaApp::setupDesktop (this=0x949a998) at /build/buildd/kdebase-workspace-4.2.1a/plasma/shells/desktop/plasmaapp.cpp:255 #38 0xb7facc0b in PlasmaApp::q
[Bug 338205] Re: [jaunty] plasma crashes on start with SIGSEGV
If I remove the plasma-appletsrc file, the crash still occurs - no widgets added. -- [jaunty] plasma crashes on start with SIGSEGV https://bugs.launchpad.net/bugs/338205 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338205] Re: [jaunty] plasma crashes on start with SIGSEGV
Will this fix be ported to jaunty? KDE is pretty much unusable without plasma (no system tray = no network manager = no network). -- [jaunty] plasma crashes on start with SIGSEGV https://bugs.launchpad.net/bugs/338205 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 336057] Re: Konqueror crashes on startup (when loading about page)
Looks good, all working here. Thanks! -- Konqueror crashes on startup (when loading about page) https://bugs.launchpad.net/bugs/336057 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338205] Re: [jaunty] plasma crashes on start with SIGSEGV
The workaround mentioned in the linked KDE bug does not work, even after removing ~/.kde/share/config/plasma-appletsrc, plasma still crashes. This is due to the global plasma-appletsrc file /usr/share/kubuntu- default-settings/kde4-profile/default/share/config/plasma-appletsrc, from the kubuntu-default-setting package. It contains a number of geometry settings that aren't suitable for this display, resulting in a crash. Workaround is to remove all 'geometry=' lines from /usr/share/kubuntu- default-settings/kde4-profile/default/share/config/plasma-appletsrc, and ~/.kde/share/config/plasma-appletsrc if present. -- [jaunty] plasma crashes on start with SIGSEGV https://bugs.launchpad.net/bugs/338205 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 338205] Re: [jaunty] plasma crashes on start with SIGSEGV
> Workaround is to remove all 'geometry=' lines from /usr/share/kubuntu- > default-settings/kde4-profile/default/share/config/plasma-appletsrc, and > ~/.kde/share/config/plasma-appletsrc if present. Nope, doesn't work either. will try messing around with geometry settings until something works... -- [jaunty] plasma crashes on start with SIGSEGV https://bugs.launchpad.net/bugs/338205 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 338205] Re: [jaunty] plasma crashes on start with SIGSEGV
ok, to work around this, I needed to find each geometry setting in my plasma-appletsrc, and manually clip each value to within the screen size. Hopefully hotplugging a larger screen then removing it doesn't write any larger values to this file, otherwise it'll keep crashing... -- [jaunty] plasma crashes on start with SIGSEGV https://bugs.launchpad.net/bugs/338205 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 338205] Re: [jaunty] plasma crashes on start with SIGSEGV
> Hopefully hotplugging a larger screen then removing it doesn't write > any larger values to this file, otherwise it'll keep crashing... Unfortunately, after adding an external monitor then removing it, the geometry settings in plasma-appletsrc are changed back to a crashing state. This means that the plasma-appletsrc needs to be hand-edited after any decrease in screen resolution. -- [jaunty] plasma crashes on start with SIGSEGV https://bugs.launchpad.net/bugs/338205 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 333041] [NEW] Kopete package is missing .desktop file for meanwhile protocol
Public bug reported: Binary package hint: kopete The kopete package in the Jaunty alpha is missing the following file: /usr/share/kde4/services/kopete_meanwhile.desktop This package is included in the upstream kopete install, but it looks like the deb build is missing the file. Without this .desktop file, kopete does not provide the meanwhile (Sametime) instant messaging support. This bug also applies to the KDE 4.2.0 backport for Intrepid, in the kubuntu-experimental PPA. ** Affects: kopete (Ubuntu) Importance: Undecided Status: New -- Kopete package is missing .desktop file for meanwhile protocol https://bugs.launchpad.net/bugs/333041 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 333041] Re: Kopete package is missing .desktop file for meanwhile protocol
OK, looks like I had the wrong package - this bug is only applicable to the kbuntu-experimental PPA, and not the main Januty repo. Feel free to close. Also, where is this embedded readme? Those instructions are way out of date (the icons and desktop file are installed during 'make install'), and Sivaram has not been the maintainer of the kopete meanwhile protocol for some time now. -- Kopete package is missing .desktop file for meanwhile protocol https://bugs.launchpad.net/bugs/333041 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kopete in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 333041] Re: Kopete package is missing .desktop file for meanwhile protocol
Found it at kopete/protocols/meanwhile/README. I'll update the info accordingly. -- Kopete package is missing .desktop file for meanwhile protocol https://bugs.launchpad.net/bugs/333041 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kopete in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 338205] Re: [jaunty] plasma crashes on start with SIGSEGV
After the updates to jaunty, all looks good here - no more crashing plasma. Thanks for all the work, you guys rock. -- [jaunty] plasma crashes on start with SIGSEGV https://bugs.launchpad.net/bugs/338205 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 330797] Re: [Jaunty] Amarok 2.0.1 will not resume playback after paused
Same behaviour here - Amarok will not resume after pausing, and occasionally stops playing when changing to the next track. The UI indicates that Amarok is still in 'play' mode, but the track position bar does not progress. In this state, Amarok can not be quit, and needs to be manually killed. -- [Jaunty] Amarok 2.0.1 will not resume playback after paused https://bugs.launchpad.net/bugs/330797 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 330797] Re: [Jaunty] Amarok 2.0.1 will not resume playback after paused
Potential upstream bug no: 179388 -- [Jaunty] Amarok 2.0.1 will not resume playback after paused https://bugs.launchpad.net/bugs/330797 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 330797] Re: [Jaunty] Amarok 2.0.1 will not resume playback after paused
OK, I've gone through the same tests here: * Just commenting-out "autospawn = yes" is not enough, as it seems this is the default. I need to change it to " = no" for autospawn to actually be disabled. * After killing the pulseaudio daemon, Amarok is opening the sound device directly: [...@pingu ~]$ sudo fuser -v /dev/dsp* /dev/snd/* USERPID ACCESS COMMAND /dev/snd/controlC0: jk21391 F kmix jk28680 F amarok /dev/snd/pcmC0D0p: jk28680 F...m amarok /dev/snd/timer: jk28680 f amarok - and pause/resume is working fine. -- [Jaunty] Amarok 2.0.1 will not resume playback after paused https://bugs.launchpad.net/bugs/330797 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 330797] Re: [Jaunty] Amarok 2.0.1 will not resume playback after paused
I'm not too familiar with the phonon/pulseaudio infrastructure, but
happy to help out with chasing this down. Catch me on IRC ('jk-' on
freenode or oftc) if you need any tracing done.
--
[Jaunty] Amarok 2.0.1 will not resume playback after paused
https://bugs.launchpad.net/bugs/330797
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to amarok in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 239889] Re: [needs-packaging] petitboot (for PS3)
Happy to help out from the petitboot side where possible here. One of the main issues with building petitboot is that it requires a minimal linux ramdisk for the first-stage boot, which isn't trivial to compile from scratch (we actually use openWRT as a base for the current builds on the PB site). Not sure what the ubuntu standard initramfs provides, but I assume that this will be sufficient with a few additions (eg libtwin, libjpeg, libpng). libtwin is from http://cgit.freedesktop.org/twin/ Cheers, Jeremy -- [needs-packaging] petitboot (for PS3) https://bugs.launchpad.net/bugs/239889 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 52365] Re: Amarok xine backend can't play FLAC files (1.4.1).
The source package that I posted *is* a backport to dapper. Building the x86 binaries shouldn't be hard at all. Just extract the tar file, cd to the new directory, apply the (gzipped) diff and run 'dpkg- buildpackage -rfakeroot'. If it's really necessary, I can find an x86 box to build this on for you. -- Amarok xine backend can't play FLAC files (1.4.1). https://launchpad.net/bugs/52365 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 52365] Re: Amarok xine backend can't play FLAC files (1.4.1).
It's an update to libxine. -- Amarok xine backend can't play FLAC files (1.4.1). https://launchpad.net/bugs/52365 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 52365] Re: Amarok xine backend can't play FLAC files (1.4.1).
Having the same problem here after upgrading to 1.4.1 from 1.4.0, using the kubuntu.org packages on Dapper. flac packages (libflac++5c2, libflac7, liboggflac3 and flac) are all at version 1.1.2-3ubuntu1. -- Amarok xine backend can't play FLAC files (1.4.1). https://launchpad.net/bugs/52365 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 52365] Re: Amarok xine backend can't play FLAC files (1.4.1).
OK, the patch fixes the problem here. I've done a simple backport to the current libxine (ie, just adding the patch to the ubuntu diff), and amarok 1.4.1 will play flacs with no problem. Source packages are here: http://ozlabs.org/~jk/libxine-bugfix.tmp (there are some powerpc binaries too, if anyone's interested) Note this only a temporary site, it won't stay up for too long! Someone may want to do a proper package (bump the version, sign, and it should be done). Maybe a contender to go in the kubuntu.org/packages/amarok-141 tree ? Cheers. -- Amarok xine backend can't play FLAC files (1.4.1). https://launchpad.net/bugs/52365 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71609] Can't unmount UUID= volume as a user
Public bug reported:
I have the following entry in /etc/fstab:
UUID=00a1665a-f7f1-48c6-8dff-65e77c98bd2f /media/extdisk ext3
user,noauto,exec0 0
- to allow a nonprivileged user (ie, me) to mount a firewire disk with
the specified UUID.
mounting works fine, but unmounting (as the same user) doesn't:
[EMAIL PROTECTED] ~]$ umount /media/extdisk
umount: /media/extdisk mount disagrees with the fstab
When this disk is mounted, /proc/mounts shows:
/dev/disk/by-uuid/00a1665a-f7f1-48c6-8dff-65e77c98bd2f /media/extdisk ext3
rw,nosuid,nodev,data=ordered 0 0
however, /etc/mtab shows:
/dev/sda1 /media/extdisk ext3 rw,nosuid,nodev,user=jk 0 0
If I strace the umount:
[EMAIL PROTECTED] ~]$ sudo strace -etrace=file -u jk umount /media/extdisk/
execve("/bin/umount", ["umount", "/media/extdisk/"], [/* 31 vars */]) = 0
access("/etc/suid-debug", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libc.so.6", O_RDONLY)= 3
readlink("/media", 0x7fa625fb, 4096)= -1 EINVAL (Invalid argument)
readlink("/media/extdisk", 0x7fa625fb, 4096) = -1 EINVAL (Invalid argument)
open("/etc/mtab", O_RDONLY|O_LARGEFILE) = 3
open("/etc/fstab", O_RDONLY|O_LARGEFILE) = 3
readlink("/dev", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/sda1", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/proc", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/home", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/media", 0x7fa625cb, 4096)= -1 EINVAL (Invalid argument)
readlink("/media/cdrom0", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
getcwd("/home/jk", 4095)= 9
readlink("/home/jk/UUID=00a1665a-f7f1-48c6-8dff-65e77c98bd2f", 0x7fa625cb,
4096) = -1 ENOENT (No such file or directory)
readlink("/media", 0x7fa625cb, 4096)= -1 EINVAL (Invalid argument)
readlink("/media/ipod", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/home", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/media", 0x7fa625cb, 4096)= -1 EINVAL (Invalid argument)
readlink("/media/ipod", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk/by-uuid", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk/by-uuid/00bcb37c-0d82-4fc4-9515-9c7daa72ffaf",
"../../hda5", 4096) = 10
readlink("/dev/hda5", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk/by-uuid", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk/by-uuid/27a00a33-2101-44b2-b29f-0be7258b70e7",
"../../hda6", 4096) = 10
readlink("/dev/hda6", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk/by-uuid", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk/by-uuid/883a4c5f-3d9b-4ce4-bf3d-c2d187870e76",
"../../hda4", 4096) = 10
readlink("/dev/hda4", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/hdc", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk/by-uuid", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk/by-uuid/00a1665a-f7f1-48c6-8dff-65e77c98bd2f",
"../../sda1", 4096) = 10
readlink("/dev/sda1", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk/by-label", 0x7fa625cb, 4096) = -1 EINVAL (Invalid argument)
readlink("/dev/disk/by-label/IPOD", 0x7fa625cb, 4096) = -1 ENOENT (No such file
or directory)
umount: /media/extdisk mount disagrees with the fstab
Process 10417 detached
- umount has managed to resolve the symlink from /dev/disk/by-uuid/00...
to /dev/sda1, but hasn't recognised that it's the same device ?
** Affects: util-linux (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Can't unmount UUID= volume as a user
https://launchpad.net/bugs/71609
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40359] Re: libgpod causes segfault on startup
Works fine on edgy - amarok can sync just fine now. -- libgpod causes segfault on startup https://launchpad.net/bugs/40359 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77649] Re: kernel-package doesn't work if CONFIG_LOCALVERSION_AUTO is set
Confirmed on Hardy too. The problem is in /usr/share/kernel- package/ruleset/misc/version_vars.mk - we construct a version variable as follows: version = $(VERSION).$(PATCHLEVEL) $(SUBLEVEL)$(EXTRAVERSION)$(iatv)$(LOCALVERSION)$(GIT_VERSION) However, $(LOCALVERSION) already includes the contents of $(GITVERSION) Perhaps conditionally setting $(GITVERSION) based on the value of CONFIG_LOCALVERSION_AUTO would be the solution? -- kernel-package doesn't work if CONFIG_LOCALVERSION_AUTO is set https://bugs.launchpad.net/bugs/77649 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 117736] Re: pam_mount unable to unmount needs root priv
Also present in hardy. pam_mount can't unmount on logout: pam_mount(misc.c:285) command: /sbin/umount.crypt [/home/crypt/] pam_mount(misc.c:56) set_myuid: (uid=1001, euid=1001, gid=1001, egid=1001) pam_mount(misc.c:358) error setting uid to 0 pam_mount(mount.c:104) umount errors: pam_mount(mount.c:107) You have to be root to use cryptsetup! pam_mount(mount.c:107) umount: only root can unmount UUID=3d6517a4-b0b1-4e74-8b29-47853e187a13 from /home/crypt pam_mount(mount.c:107) umount.crypt: error unmounting /home/crypt/ pam_mount(mount.c:596) waiting for umount pam_mount(pam_mount.c:624) unmount of /dev/sda6 failed pam_mount(pam_mount.c:635) pam_mount execution complete This leaves the encrypted volume mounted, and attached to the device mapper (/dev/mapper/_dev_sda6 allows access to the unencrypted data). This allows access to the volume in plaintext after the user has logged out. -- pam_mount unable to unmount needs root priv https://bugs.launchpad.net/bugs/117736 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 117736] Re: pam_mount unable to unmount needs root priv
The login-count bug mentioned in comment 1 is also a symptom of the early-priv-dropping problem. When pam_mount decreases the login count to 0, it tries to remove the /var/run/pam_mount/$USER file, but can't as it doesn't have the privileges to do so. This results in a stale login count file. -- pam_mount unable to unmount needs root priv https://bugs.launchpad.net/bugs/117736 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 210048] [NEW] mt-daapd server crashes when requesting a scan
Public bug reported: Binary package hint: mt-daapd By requesting a metadata scan through mt-daapd's web interface, I can crash the mt-daapd process. I see the following in the log output (using 'sudo mt-daapd -D webserver -d -f'): Thread 12: Request: POST /xml-rpc HTTP/1.1 Thread 12: Read: User-Agent: Mozilla/5.0 (compatible; Konqueror/3.5; Linux 2.6.25-rc7-p2; X11; ppc) KHTML/3.5.9 (like Gecko) (Kubuntu package 4:3.5.9-0ubuntu5) Thread 12: Adding header *User-Agent=Mozilla/5.0 (compatible; Konqueror/3.5; Linux 2.6.25-rc7-p2; X11; ppc) KHTML/3.5.9 (like Gecko) (Kubuntu package 4:3.5.9-0ubuntu5)* Added *User-Agent=Mozilla/5.0 (compatible; Konqueror/3.5; Linux 2.6.25-rc7-p2; X11; ppc) KHTML/3.5.9 (like Gecko) (Kubuntu package 4:3.5.9-0ubuntu5)* Thread 12: Read: Referer: http://pokey:3689/index.html Thread 12: Adding header *Referer=http://pokey:3689/index.html* Added *Referer=http://pokey:3689/index.html* Thread 12: Read: Pragma: no-cache Thread 12: Adding header *Pragma=no-cache* Added *Pragma=no-cache* Thread 12: Read: Cache-control: no-cache Thread 12: Adding header *Cache-control=no-cache* Added *Cache-control=no-cache* Thread 12: Read: Accept: text/html, image/jpeg, image/png, text/*, image/*, */* Thread 12: Adding header *Accept=text/html, image/jpeg, image/png, text/*, image/*, */** Added *Accept=text/html, image/jpeg, image/png, text/*, image/*, */** Thread 12: Read: Accept-Encoding: x-gzip, x-deflate, gzip, deflate Thread 12: Adding header *Accept-Encoding=x-gzip, x-deflate, gzip, deflate* Added *Accept-Encoding=x-gzip, x-deflate, gzip, deflate* Thread 12: Read: Accept-Charset: utf-8, utf-8;q=0.5, *;q=0.5 Thread 12: Adding header *Accept-Charset=utf-8, utf-8;q=0.5, *;q=0.5* Added *Accept-Charset=utf-8, utf-8;q=0.5, *;q=0.5* Thread 12: Read: Accept-Language: en Thread 12: Adding header *Accept-Language=en* Added *Accept-Language=en* Thread 12: Read: Host: pokey:3689 Thread 12: Adding header *Host=pokey:3689* Added *Host=pokey:3689* Thread 12: Read: connection: close Thread 12: Adding header *connection=close* Added *connection=close* Thread 12: Read: x-prototype-version: 1.4.0 Thread 12: Adding header *x-prototype-version=1.4.0* Added *x-prototype-version=1.4.0* Thread 12: Read: x-requested-with: XMLHttpRequest Thread 12: Adding header *x-requested-with=XMLHttpRequest* Added *x-requested-with=XMLHttpRequest* Thread 12: Read: Content-type: application/x-www-form-urlencoded Thread 12: Adding header *Content-type=application/x-www-form-urlencoded* Added *Content-type=application/x-www-form-urlencoded* Thread 12: Read: Authorization: Basic YWRtaW46ZGVhbDlwcmljeQ== Thread 12: Adding header *Authorization=Basic YWRtaW46ZGVhbDlwcmljeQ==* Added *Authorization=Basic YWRtaW46ZGVhbDlwcmljeQ==* Thread 12: Read: Connection: Keep-Alive Thread 12: Adding header *Connection=Keep-Alive* Updating Connection from close to Keep-Alive Thread 12: Out of memory Aborting Rendezvous socket closed (daap server crashed?) Aborting. Aborting Fix: It looks like the browser is sending two 'Connection:' headers (one in lowercase). This is triggerring a bug where the ws_addarg() updates (rather than inserts) a new header. This condition includes an incorrect return value. The caller assumes that the ws_addarg failed, so exits with the out of memory message. Patch attached, also sent upstream. ** Affects: mt-daapd (Ubuntu) Importance: Undecided Status: New -- mt-daapd server crashes when requesting a scan https://bugs.launchpad.net/bugs/210048 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 210048] Re: mt-daapd server crashes when requesting a scan
** Attachment added: "Patch to fix return value in ws_addarg" http://launchpadlibrarian.net/13010565/fix-crash-on-scan.patch -- mt-daapd server crashes when requesting a scan https://bugs.launchpad.net/bugs/210048 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 196600] Re: powerpc ibm pseries 620 stopping after kernel load
Hi Ulrich, How is your console connected on this machine? Are you using a management center console or a serial cable? Also, try adding 'debug' to the kernel command line, to override the default 'quiet' option. Let us know what output you get with that. -- powerpc ibm pseries 620 stopping after kernel load https://bugs.launchpad.net/bugs/196600 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 69643] no wireless networks after upgrade to 0.1-0ubuntu1
Public bug reported:
After upgrading from 0.1~svn-r533312-0ubuntu1 to 0.1-0ubuntu1, I can no
longer access any wireless networks.
0.1~svn-r533312-0ubuntu1 works fine, and lists wireless networks in the
context menu. The gnome network manager applet also works fine.
Selecting the 'Enable Wireless' option makes no difference.
I see the following in /var/log/daemon.log when knetworkmanager starts:
Nov 1 18:33:14 localhost NetworkManager: ^IUpdating allowed
wireless network lists.
Nov 1 18:33:14 localhost NetworkManager: ^I nm_dbus_get_networks_cb
(): error received: org.freedesktop.NetworkManagerInfo.NoNetworks -
org.freedesktop.NetworkManagerInfo.NoNetworks.
>From reading various reports on these error messages, I get the
impression that this is due to knetworkmanager not finding any suitable
wireless devices. lshal shows the following for my wireless device:
udi = '/org/freedesktop/Hal/devices/net_00_11_24_90_6b_dc'
info.udi = '/org/freedesktop/Hal/devices/net_00_11_24_90_6b_dc' (string)
linux.subsystem = 'net' (string)
linux.hotplug_type = 2 (0x2) (int)
net.80211.mac_address = 73627888604 (0x1124906bdc) (uint64)
info.product = 'WLAN Interface' (string)
net.interface_up = false (bool)
net.arp_proto_hw_id = 1 (0x1) (int)
net.linux.ifindex = 3 (0x3) (int)
net.address = '00:11:24:90:6b:dc' (string)
net.interface = 'eth1' (string)
net.physical_device = '/org/freedesktop/Hal/devices/pci_14e4_4320' (string)
info.capabilities = {'net', 'net.80211'} (string list)
info.category = 'net.80211' (string)
info.parent = '/org/freedesktop/Hal/devices/pci_14e4_4320' (string)
linux.sysfs_path = '/sys/class/net/eth1' (string)
** Affects: knetworkmanager (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
no wireless networks after upgrade to 0.1-0ubuntu1
https://launchpad.net/bugs/69643
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 69173] Re: rpm -t* don't work
Also occurs in edgy. When trying to build a RPM: [EMAIL PROTECTED] ~]$ rpmbuild -v -ta (package).tar.gz error: Name field must be present in package: (main package) error: Version field must be present in package: (main package) error: Release field must be present in package: (main package) error: Summary field must be present in package: (main package) error: Group field must be present in package: (main package) error: License field must be present in package: (main package) This is due to rpmbuild using the following method to find the .spec file in the tarball: gunzip < $tarball | tar xOvf - '*.spec' however, the installed version of tar dies with this error: tar: Pattern matching characters used in file names. Please, tar: use --wildcards to enable pattern matching, or --no-wildcards to tar: suppress this warning. tar: *.spec: Not found in archive tar: Error exit delayed from previous errors - it just needs the --wildcards option to be able to extract the .spec -- rpm -t* don't work https://launchpad.net/bugs/69173 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69173] Re: rpm -t* don't work
Looks like it's fixed upstream, but here's a patch in the interim. ** Attachment added: "Add --wildcard to tarball build options" http://librarian.launchpad.net/5093654/fix-tarball-build.patch -- rpm -t* don't work https://launchpad.net/bugs/69173 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72832] no console started on cell machine
Public bug reported: The default setup of the system-services package doesn't start a login on an IBM cell machine. This is after doing a minimal netinstall with the edgy server initrd. Looking in /etc/event.d/, I see there are several files (tty[1-6]) to start consoles on the tty devices, but these aren't present on the cell (or most powerpc machines). To enable a login process running on the only console available (the hvc console), I've created /etc/event.d/console with the following configuration: start on runlevel-2 start on runlevel-3 start on runlevel-4 start on runlevel-5 stop on shutdown respawn /sbin/getty 38400 console Is the use of /dev/console a suitable fallback for machines that don't have the /dev/tty[0-6] devices available? This is a little tricky to work around (especially if there's no other method of login available - eg, after a minimal install): - hard-reset the machine - when rebooting, append init=/bin/sh to the kernel command line - remount root as read-only: mount / -o remount,rw - create /etc/event.d/console with the above content - sync; exit ** Affects: upstart (Ubuntu) Importance: Undecided Status: Unconfirmed -- no console started on cell machine https://launchpad.net/bugs/72832 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72832] Re: no console started on cell machine
Correct. There is no VT, only the console on /dev/hvc0 (in fact, my previous /etc/event.d/ example should do a getty on /dev/hvc0, not /dev/console). Rather than having to worry about every possible console configuration, can the installer set up a /etc/event.d/ file to point to the console where the installer was running? Something like 'readlink /proc/self/fd/0' would work nicely. -- no console started on cell machine https://launchpad.net/bugs/72832 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72832] Re: no console started on cell machine
$ stty --file /dev/hvc0 speed 38400 However, the hvc devices ignore the speed parameter - no handler for ioctl() is registered. -- no console started on cell machine https://launchpad.net/bugs/72832 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387073] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000228
I get the same oops here, usually triggered by plasma-desktop (causes KDE4 desktop, panel & widgets to disappear). Workaround is to restart plasma desktop. Linux pororo 2.6.31-9-generic #29-Ubuntu SMP Sun Aug 30 17:39:26 UTC 2009 x86_64 GNU/Linux I have a dmesg log saved, happy to attach if it'll help. -- BUG: unable to handle kernel NULL pointer dereference at 0228 https://bugs.launchpad.net/bugs/387073 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 387073] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000228
Had a bit of time to look into this, hope this helps:
BUG: unable to handle kernel NULL pointer dereference at 0220
IP: [] touch_atime+0x20/0x150
8102efb0 :
8112efb0: 55 push %rbp
8112efb1: 48 89 e5mov%rsp,%rbp
8112efb4: 48 83 ec 30 sub$0x30,%rsp
8112efb8: 48 89 5d f0 mov%rbx,-0x10(%rbp)
8112efbc: 4c 89 65 f8 mov%r12,-0x8(%rbp)
8112efc0: 48 89 fbmov%rdi,%rbx
8112efc3: 4c 8b 66 10 mov0x10(%rsi),%r12
8112efc7: e8 94 36 00 00 callq 0x81132660
8112efcc: 85 c0 test %eax,%eax
8112efce: 75 13 jne0x8112efe3
8112efd0: 41 f6 84 24 20 02 00testb $0x2,0x220(%r12)
>From looking at the oops log, r12 is indeed 0. Referring to source of
touch_atime:
void touch_atime(struct vfsmount *mnt, struct dentry *dentry)
{
struct inode *inode = dentry->d_inode;
struct timespec now;
if (mnt_want_write(mnt))
return;
if (inode->i_flags & S_NOATIME)
goto out;
We're oopsing on the ionode->i_flags dereference, so dentry->d_inode is NULL. I
think it's safe to assume that this function should not be called on a negative
dentry.
>From a brief look at ecryptfs_read_update_atime, it seems that there is
no reference on the "lower" dentry when it's added to d_fsdata, so
perhaps we need a check for lower_dentry != NULL around that call to
touch_atime. I'm not entirely sure that this is the correct solution,
but we shouldn't be updating dentries for files that have been removed.
--
BUG: unable to handle kernel NULL pointer dereference at 0228
https://bugs.launchpad.net/bugs/387073
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 422457] Re: plasma-desktop crashes sometimes using ecryptfs home directory
*** This bug is a duplicate of bug 387073 *** https://bugs.launchpad.net/bugs/387073 ** This bug has been marked a duplicate of bug 387073 BUG: unable to handle kernel NULL pointer dereference at 0228 -- plasma-desktop crashes sometimes using ecryptfs home directory https://bugs.launchpad.net/bugs/422457 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 430483] Re: Display turned off during boot.
Does this problem still occur if you add 'nomodeset' to the kernel boot arguments? Could be related to #425165. -- Display turned off during boot. https://bugs.launchpad.net/bugs/430483 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 319729] Re: ARM architecture lacks support for pselect() and ppoll()
Just tried the attached build, and the childspin example still hangs. However, it looks like it's waiting somewhere in do_exit, rather than the previous deadlock, which seems to be waiting in poll_schedule_timeout Will see if I can find more about what's happening here. -- ARM architecture lacks support for pselect() and ppoll() https://bugs.launchpad.net/bugs/319729 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 303755] Re: Web cam won't work in Intrepid, worked in previous Ubuntu versions
pixolex: how about the output of 'id'? are you in the 'video' group? Cheers, Jeremy -- Web cam won't work in Intrepid, worked in previous Ubuntu versions https://bugs.launchpad.net/bugs/303755 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 588549] [NEW] [gm45] Xorg crash when idle: Failed to map batchbuffer: Cannot allocate memory
Public bug reported: Binary package hint: xserver-xorg-video-intel I have had Xorg crash several times while not at the computer, and I return to find a KDM login prompt. Before the crash, the screen has been locked, with no screensaver running. There may have been notifications appearing in the background; I generally have IRC (Quassel) and IM (kopete) clients running while the system is idle. The crash may be related to an event (notifcation) occuring at the time, but I can't tell. Xorg.0.log.old reports around 2.5k lines of: (WW) intel(0): i830_uxa_prepare_access: bo map failed At the end of the log: Fatal server error: Failed to map batchbuffer: Cannot allocate memory May be a dup of Bug #539938, but reporting separately as it looks like we have a different errno here. Running lucid, xserver-xorg-video-intel version is 2:2.9.1-3ubuntu5, kernel version 2.6.32-22.33. Happy to provide more info if required. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-video-intel 2:2.9.1-3ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 Date: Wed Jun 2 08:23:04 2010 DkmsStatus: EcryptfsInUse: Yes MachineType: LENOVO 2777CTO ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=66f31270-8b1f-4e8b-b057-0dbb76dc5c81 ro crashkernel=384M-2G:64M,2G-:128M quiet splash ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-intel dmi.bios.date: 05/15/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 6EET41WW (3.01 ) dmi.board.name: 2777CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6EET41WW(3.01):bd05/15/2009:svnLENOVO:pn2777CTO:pvrThinkPadX301:rvnLENOVO:rn2777CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2777CTO dmi.product.version: ThinkPad X301 dmi.sys.vendor: LENOVO system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-22-generic ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash lucid -- [gm45] Xorg crash when idle: Failed to map batchbuffer: Cannot allocate memory https://bugs.launchpad.net/bugs/588549 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 588549] Re: [gm45] Xorg crash when idle: Failed to map batchbuffer: Cannot allocate memory
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/49528472/BootDmesg.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/49528473/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/49528474/Dependencies.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/49528475/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/49528476/Lsusb.txt ** Attachment added: "PciDisplay.txt" http://launchpadlibrarian.net/49528477/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/49528478/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/49528479/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/49528480/ProcModules.txt ** Attachment added: "RelatedPackageVersions.txt" http://launchpadlibrarian.net/49528481/RelatedPackageVersions.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/49528482/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/49528484/UdevLog.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/49528486/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/49528487/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/49528490/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/49528492/glxinfo.txt ** Attachment added: "monitors.xml.txt" http://launchpadlibrarian.net/49528493/monitors.xml.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/49528495/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/49528496/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/49528497/xkbcomp.txt -- [gm45] Xorg crash when idle: Failed to map batchbuffer: Cannot allocate memory https://bugs.launchpad.net/bugs/588549 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 557742] Re: Lenovo Thinkpad X201 & T410 & W510 not autoswitching to input mic jack in 10.04
Jerone: just to clarify: we can't update l-b-m to use ALSA 1.0.23, because that will break thinkpad-acpi ? -- Lenovo Thinkpad X201 & T410 & W510 not autoswitching to input mic jack in 10.04 https://bugs.launchpad.net/bugs/557742 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 557742] Re: Lenovo Thinkpad X201 & T410 & W510 not autoswitching to input mic jack in 10.04
This looks like what we're after: http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=commitdiff;h=7b2bfdbc0dee5a321b5c02febe157adebd33ab3a Perhaps we can SRU this and avoid the l-b-m/thinkpad_acpi issue. -- Lenovo Thinkpad X201 & T410 & W510 not autoswitching to input mic jack in 10.04 https://bugs.launchpad.net/bugs/557742 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 557742] Re: Lenovo Thinkpad X201 & T410 & W510 not autoswitching to input mic jack in 10.04
Spoke to Jerone off-line, it sounds like the thinkpad_acpi symbol issue may have been particular to the build (symbol versioning), so l-b-m *should* be compatible with thinkpad_acpi once it comes out. Spoke to Stefan, he has an update pending for linux-backports-modules, which includes ALSA v1.0.23. So, this bug should be fixed (without thinkpad_acpi breakage) in the next l-b-m update, which should be coming soon. -- Lenovo Thinkpad X201 & T410 & W510 not autoswitching to input mic jack in 10.04 https://bugs.launchpad.net/bugs/557742 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 557742] Re: Lenovo Thinkpad X201 & T410 & W510 not autoswitching to input mic jack in 10.04
@Jerone: it hasn't hit -proposed yet, but it's in the linux-backports- modules repo (git://kernel.ubuntu.com/ubuntu/ubuntu-lucid-lbm.git) if you want to build & test early. -- Lenovo Thinkpad X201 & T410 & W510 not autoswitching to input mic jack in 10.04 https://bugs.launchpad.net/bugs/557742 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 588549] Re: [gm45] Xorg crash when idle: Failed to map batchbuffer: Cannot allocate memory
Just happened again, except this time the machine wasn't idle; I was editing a file with gvim. Xorg had been running for about two days. Same message in the Xorg log: Fatal server error: Failed to map batchbuffer: Cannot allocate memory -- [gm45] Xorg crash when idle: Failed to map batchbuffer: Cannot allocate memory https://bugs.launchpad.net/bugs/588549 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 531696] [NEW] mc13892 LED driver oopses on trigger action
Public bug reported: Setting a LED trigger event on a babbage board will cause an oops when that trigger occurs: echo mmc0 | sudo dd of=/sys/class/leds/pmic_ledsb/trigger sudo dd if=/dev/mmcblk0 of=/dev/null The led_classdev's brightness_set function is called from an atomic context, but the mc13892 LED driver's brightness_set callback may sleep, resulting in the recursive oops. Patch attached. ** Affects: linux-fsl-imx51 (Ubuntu) Importance: Undecided Assignee: Bryan Wu (cooloney) Status: New -- mc13892 LED driver oopses on trigger action https://bugs.launchpad.net/bugs/531696 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 531696] Re: mc13892 LED driver oopses on trigger action
** Patch added: "Patch to use a workqueue for setting LED brightness" http://launchpadlibrarian.net/40124884/0001-leds-mc13892-Use-workqueue-for-setting-LED-brightnes.patch ** Changed in: linux-fsl-imx51 (Ubuntu) Assignee: (unassigned) => Bryan Wu (cooloney) -- mc13892 LED driver oopses on trigger action https://bugs.launchpad.net/bugs/531696 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 531696] Re: mc13892 LED driver oopses on trigger action
The attached patch does a bit of rework to enable the driver to use a workqueue. If we need a less intrusive (but more hacky) patch, let me know. -- mc13892 LED driver oopses on trigger action https://bugs.launchpad.net/bugs/531696 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 541029] Re: netboot image fails to connect to the network
Tobin - how are you booting this image? directly from redboot via a HTTP load? -- netboot image fails to connect to the network https://bugs.launchpad.net/bugs/541029 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 548513] Re: Firewire disks not working under 10.04
Looks like this may not be all controllers/disks; seems to work here with a generic SBP2 disk interface. I've tested with both a OHCI and PCILynx firewire controller. Jerone - could you try with a different FW disk, and see if the problem still occurs? May help to isolate the root cause. -- Firewire disks not working under 10.04 https://bugs.launchpad.net/bugs/548513 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 541029] Re: netboot image fails to connect to the network
So just to make sure I'm understanding this correctly - you're not netbooting, right? -- netboot image fails to connect to the network https://bugs.launchpad.net/bugs/541029 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 541029] Re: netinstall image fails to connect to the network
OK, we should check to see if a netinstall build with the fix from #457878 addresses this issue, otherwise I'll look into this further. -- netinstall image fails to connect to the network https://bugs.launchpad.net/bugs/541029 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 548513] Re: Firewire disks not working under 10.04
Just a stab in the dark, but can you try this with the disk plugged in to an external power source (if you're not doing that already?) it looks like the FW bus is being reset, and so the SCSI layer is creating multiple devices when the requests time out. -- Firewire disks not working under 10.04 https://bugs.launchpad.net/bugs/548513 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 537083] Re: Suspend no longer works after updating to 2.6.31-605.9 kernel
** Changed in: linux-fsl-imx51 (Ubuntu Lucid) Assignee: Bryan Wu (cooloney) => Jeremy Kerr (jk-ozlabs) -- Suspend no longer works after updating to 2.6.31-605.9 kernel https://bugs.launchpad.net/bugs/537083 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 537083] Re: Suspend no longer works after updating to 2.6.31-605.9 kernel
Working on a fix for the update leds driver. -- Suspend no longer works after updating to 2.6.31-605.9 kernel https://bugs.launchpad.net/bugs/537083 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 537083] Re: Suspend no longer works after updating to 2.6.31-605.9 kernel
This patch fixes the problem for me. Please test & let me know the results. >From the patch comments: [PATCH] leds-mc13892: fix suspend/resume The workqueue update for the leds-mc13892 driver introduced a regression where machine would no longer suspend and resume, as the wrong type was being retrieved from the platform drvdata. This change updates the suspend and resume functions to use the struct mc13892_led type. Signed-off-by: Jeremy Kerr ** Patch added: "Fix for suspend & resume with imx51 mc13892 leds driver" http://launchpadlibrarian.net/41195366/0001-leds-mc13892-fix-suspend-resume.patch ** Changed in: linux-fsl-imx51 (Ubuntu Lucid) Status: Triaged => Fix Released -- Suspend no longer works after updating to 2.6.31-605.9 kernel https://bugs.launchpad.net/bugs/537083 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 537083] Re: Suspend no longer works after updating to 2.6.31-605.9 kernel
** Changed in: linux-fsl-imx51 (Ubuntu Lucid) Status: Fix Released => In Progress -- Suspend no longer works after updating to 2.6.31-605.9 kernel https://bugs.launchpad.net/bugs/537083 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 438687] Re: FEC driver does not set "DRIVER" property in udev which makes network-manager fail
>From looking at the udev code, it would seem that this is due to a missing driver symlink in the sysfs directory for this device. Could you confirm by pasting the output of: ls -l /sys/class/net/eth0/device/ ? -- FEC driver does not set "DRIVER" property in udev which makes network-manager fail https://bugs.launchpad.net/bugs/438687 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 438687] Re: FEC driver does not set "DRIVER" property in udev which makes network-manager fail
Looks like the struct netdevice for the fec interfaces don't have a "parent", and hence no driver. I'm currently building a test kernel to add a parent device for the interface, will let you know how that goes. ** Changed in: linux-fsl-imx51 (Ubuntu Karmic) Status: Triaged => Won't Fix ** Changed in: linux-fsl-imx51 (Ubuntu Karmic) Status: Won't Fix => In Progress -- FEC driver does not set "DRIVER" property in udev which makes network-manager fail https://bugs.launchpad.net/bugs/438687 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 427127] [NEW] broken symlink in qemu-kvm package
Public bug reported: Binary package hint: qemu-kvm The qemu-kvm pacakge contains a broken symlink: [...@b1 ~]$ ls -l /usr/share/kvm lrwxrwxrwx 1 root root 8 2009-09-10 10:49 /usr/share/kvm -> qemu-kvm The /usr/share/qemu-kvm directory does not exist. This means that packages that use the /usr/share/kvm directory will fail to install: [...@b1 ~]$ sudo apt-get install kvm-pxe Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: kvm-pxe 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/156kB of archives. After this operation, 250kB of additional disk space will be used. (Reading database ... 105789 files and directories currently installed.) Unpacking kvm-pxe (from .../kvm-pxe_5.4.3+dfsg-0.2ubuntu1_all.deb) ... dpkg: error processing /var/cache/apt/archives/kvm-pxe_5.4.3+dfsg-0.2ubuntu1_all.deb (--unpack): trying to overwrite `/usr/share/kvm', which is also in package qemu-kvm dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/kvm-pxe_5.4.3+dfsg-0.2ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Workaround is to change this symlink to point to /usr/share/qemu instead. [...@b1 ~]$ apt-cache policy qemu-kvm qemu-kvm: Installed: 0.11.0~rc2-0ubuntu2 Candidate: 0.11.0~rc2-0ubuntu2 Version table: *** 0.11.0~rc2-0ubuntu2 0 500 http://mirror.internode.on.net karmic/main Packages 100 /var/lib/dpkg/status ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- broken symlink in qemu-kvm package https://bugs.launchpad.net/bugs/427127 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 438687] Re: FEC driver does not set "DRIVER" property in udev which makes network-manager fail
I'm in the process of adding some minimal platform_driver infrastructure to the fec code; this should give the appropriate entries in sysfs. Will report back with a patch tomorrow. -- FEC driver does not set "DRIVER" property in udev which makes network-manager fail https://bugs.launchpad.net/bugs/438687 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 438687] Re: FEC driver does not set "DRIVER" property in udev which makes network-manager fail
New test kernel up at http://kernel.ubuntu.com/~jk/bugs/438687/ - the jk2 version is my most recent build. This has a minimal platform_device for the FEC driver. We may need to provide more details to the core driver code, but try this one to see how it goes. Loïc: try this and let me know how it goes. dmesg from a boot would be handy if you could attach it here. -- FEC driver does not set "DRIVER" property in udev which makes network-manager fail https://bugs.launchpad.net/bugs/438687 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 438687] Re: FEC driver does not set "DRIVER" property in udev which makes network-manager fail
New kernel is up (jk3). Let me know how that goes, and thanks for the continued testing. -- FEC driver does not set "DRIVER" property in udev which makes network-manager fail https://bugs.launchpad.net/bugs/438687 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 438687] Re: FEC driver does not set "DRIVER" property in udev which makes network-manager fail
Loïc: the updated driver uses the 'platform' bus rather than 'virtual', so the device has moved in sysfs. Is this going to be a problem? Also, could you see if NM works as it does for Paul? It's possible that the DRIVER property is being exposed through a different node in sysfs. Try a recursive query: udevadm info --query=all --path=/class/net/eth0 --attribute-walk Paul; IIRC, ifup will only work if you have an entry in /etc/network/interfaces, which would preclude NM from managing the device. If you want to try ifup/ifdown, you may need to add the following to /etc/network/interfaces: auto eth0 iface eth0 inet dhcp If all is OK with the updated driver, I will remove debug code and send a patch. -- FEC driver does not set "DRIVER" property in udev which makes network-manager fail https://bugs.launchpad.net/bugs/438687 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 438687] Re: FEC driver does not set "DRIVER" property in udev which makes network-manager fail
Oliver: My changes should only affect the probe code, so I'd be surprised if we seen any difference with the rx/tx paths. However, I've been surprised before, so I've done a "baseline" build, version jk0: http://kernel.ubuntu.com/~jk/bugs/438687/linux- image-2.6.31-102-imx51_2.6.31-102.10.jk0_armel.deb - this is the fsl-imx51 branch, built without my changes. Could you test this to see if you still have the same errors in dmesg? Of course, the interface will need to be brought up manually, as NM won't work. -- FEC driver does not set "DRIVER" property in udev which makes network-manager fail https://bugs.launchpad.net/bugs/438687 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 438687] Re: FEC driver does not set "DRIVER" property in udev which makes network-manager fail
OK, thanks for the testing. Patch coming. -- FEC driver does not set "DRIVER" property in udev which makes network-manager fail https://bugs.launchpad.net/bugs/438687 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 438687] Re: FEC driver does not set "DRIVER" property in udev which makes network-manager fail
Patch to convert fec to a platform device. I've sent to k...@u.c. Suggest we track the dmesg errors in a separate bug, as they seem to be independent of this. >From the patch comments: [PATCH] drivers/net/fec: Convert to a platform bus driver BugLink: https://bugs.launchpad.net/bugs/438687 Currently, the FEC device is placed on the 'virtual' bus, and so has no driver symlink in sysfs. This symlink is required for network manager to handle the device properly, so FEC devices are currently ignored. This change converts the FEC driver to use the platform bus, so we get the proper symlinks set up in sysfs. With this change, NM will bring up the network as expected. We're doing the platform_device_register in the driver itself, rather than in machine-specific code. This is a bit of a hack: the driver will always attempt to initialise a FEC even if one isn't present in the system. However, this is no different from the existing driver. Signed-off-by: Jeremy Kerr ** Attachment added: "Patch to convert fec to a platform bus driver" http://launchpadlibrarian.net/33294649/0001-drivers-net-fec-Convert-to-a-platform-bus-driver.patch -- FEC driver does not set "DRIVER" property in udev which makes network-manager fail https://bugs.launchpad.net/bugs/438687 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 438687] Re: FEC driver does not set "DRIVER" property in udev which makes network-manager fail
** Changed in: linux-fsl-imx51 (Ubuntu Karmic) Status: In Progress => Won't Fix ** Changed in: linux-fsl-imx51 (Ubuntu Karmic) Status: Won't Fix => In Progress -- FEC driver does not set "DRIVER" property in udev which makes network-manager fail https://bugs.launchpad.net/bugs/438687 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 407428] Re: sshd zombie processes and strange behavior after karmic upgrade
The attached patch fixes the problem for me. From the patch comments: External programs triggered by events (via RUN=) will inherit udev's signal mask, which is set to block all but SIGALRM. For most utilities, this is OK, but if we start daemons from RUN=, we run into trouble (especially as SIGCHLD is blocked). This change saves the original sigmask when udev starts, and restores it just before we exec() the external command. Signed-off-by: Jeremy Kerr I'm not a udev hacker, so not sure if this is the proper fix. I've sent it to linux-hotplug for comment. ** Attachment added: "Patch to restore signal mask before execing external processes" http://launchpadlibrarian.net/31357893/0001-Restore-signal-mask-before-executing-event-RUN-comma.patch -- sshd zombie processes and strange behavior after karmic upgrade https://bugs.launchpad.net/bugs/407428 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 407428] Re: sshd zombie processes and strange behavior after karmic upgrade
Looks like this patch has been accepted to udev: http://www.spinics.net/lists/hotplug/msg02675.html The udev.git tree doesn't look like it has been updated though, I assume Kay hasn't pushed recent changes yet. -- sshd zombie processes and strange behavior after karmic upgrade https://bugs.launchpad.net/bugs/407428 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 407428] Re: sshd zombie processes and strange behavior after karmic upgrade
Patch is now in udev: http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=d412a685736e3b3350b555f4d7d8ebfc80aa54c9 -- sshd zombie processes and strange behavior after karmic upgrade https://bugs.launchpad.net/bugs/407428 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 456398] Re: plasma clock does not update with system timezone
Jonathan: just to clarify, you're not using launchpad to track any non- packaging bugs? ** Bug watch added: KDE Bug Tracking System #213962 http://bugs.kde.org/show_bug.cgi?id=213962 ** Also affects: kdebase via http://bugs.kde.org/show_bug.cgi?id=213962 Importance: Unknown Status: Unknown -- plasma clock does not update with system timezone https://bugs.launchpad.net/bugs/456398 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 319729] Re: ARM architecture lacks support for pselect() and ppoll()
Attached a new testcase. Rather than use the libc pselect() wrapper, the new testcase has its own wrapper for pselect. Compile with: gcc -o childspin -DUSE_PSELECT_WRAPPER -Wall childspin.c Running this on a patched kernel (from Amit's comment 16), the program does not show the blocking behaviour. So, looks like the patch works as expected. Since the eglibc sources will Do The Right Thing when __NR_pselect6 is #defined, a rebuild of the eglibc package against the new kernel headers should provide the correct libc wrapper. ** Attachment added: "Testcase with internal pselect wrapper" http://launchpadlibrarian.net/34502840/childspin.c -- ARM architecture lacks support for pselect() and ppoll() https://bugs.launchpad.net/bugs/319729 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 303755] Re: Web cam won't work in Intrepid, worked in previous Ubuntu versions
picolex: looks like you do have permissions to access the device. Are you seeing the exact same output as Craig Gilding (from comment #6) when you run gstreamer-properties? Craig: could you post your output from 'id' and 'ls -l /dev/video0' too? -- Web cam won't work in Intrepid, worked in previous Ubuntu versions https://bugs.launchpad.net/bugs/303755 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
