[Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Ok, I guess this is embarrassing, but as I was trying James' workaround in #92 , I started thinking that somehow the signal was weak or intermittent. A few minutes later, Solaar (the GUI that displays status of Logitech wireless devices) tells me that the battery level in the mouse was down to 5%. I replaced the only battery it takes (I have the M215), and the middle button started working just fine. It's been rock solid for a few days.Running Bionic now. (as an aside, it seems like the battery reporting capabilities are not too good: new batteries show 90% charge, and this one "dropped" from 90% to 5% instantly. But the battery was very likely almost empty for quite some time) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Same as Kristin #85 : Disconnecting the USB receiver in a port, and connecting it in the USB port just besides it, has been working for some time now. Middle click is now recognized in System Settings. Ubuntu 16.04, NVIDIA drivers. xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Mouseemu virtual mouseid=13 [slave pointer (2)] ⎜ ↳ Logitech K330 id=8[slave pointer (2)] ⎜ ↳ Logitech M215 2nd Gen id=11 [slave pointer (2)] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495276] Re: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion `*_head == _item' failed.
I guess this is obvious. But this bug still happens in Xenial. lmilano@grisell:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" lmilano@grisell:~$ dpkg -l |grep cups-client ii cups-client 2.1.3-4 amd64Common UNIX Printing System(tm) - client programs (SysV) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495276 Title: cupsd assert failure: cupsd: entrygroup.c:245: avahi_entry_group_free: Assertion `*_head == _item' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1495276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504698] Re: NetworkManager crashes after reboot
Just a quick note.This problem persists after the official release of 15.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504698 Title: NetworkManager crashes after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1504698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504698] [NEW] NetworkManager crashes after reboot
*** This bug is a duplicate of bug 1500399 *** https://bugs.launchpad.net/bugs/1500399 Public bug reported: I upgraded my HP Chromebook 14 from 15.04 to 15.10 beta. After cold boot, NetworkManager crashes and I get the popup to send a bug report for a NM crash. There is no network, either. Restarting the NetworkManager service from a terminal fixes the issue ... until next reboot :) ~$ sudo service NetworkManager restart ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Fri Oct 9 16:39:39 2015 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 600 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.38 metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTIONCON-UUID CON-PATH wlan0wifi connected /org/freedesktop/NetworkManager/Devices/2 MilanoFamily fbced2d1-aa52-4d01-81dd-9f56594e0911 /org/freedesktop/NetworkManager/ActiveConnection/0 ttyUSB0 gsm disconnected /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash wily ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504698 Title: NetworkManager crashes after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1504698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504698] Re: NetworkManager crashes after reboot
*** This bug is a duplicate of bug 1500399 *** https://bugs.launchpad.net/bugs/1500399 An automatic comment stating that this bug is a duplicate has been added, but the allegedely original bug doesn't seem to exist. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504698 Title: NetworkManager crashes after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1504698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504698] Re: NetworkManager crashes after reboot
** This bug is no longer a duplicate of private bug 1500399 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504698 Title: NetworkManager crashes after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1504698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422004] Re: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop'
Thank you, Till, I was looking for the proper place to change the tag :) Cheers, Leo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422004 Title: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop' To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1422004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422004] Re: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop'
Hi I enabled 'proposed' vivid updates, installed hplip 3.15.2-0ubuntu4.1 , and I could successfully run the hp-plugin component. As far as my local machine goes, the package fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422004 Title: pkservice.py crashed with AttributeError in __init__(): 'module' object has no attribute 'MainLoop' To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1422004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448794] [NEW] hp-plugin needs /usr/bin/python to point to python3*
Public bug reported: After upgrading to Vivid, my HP LaserJet M1212nf MFP would not work anymore, and trying to install the binary driver, as prompted by the HPLIP utility would fail. After fiddling for a good hour, I realized that the utility was failing to load the python modules for hplip: $ gksu hp-plugin [ ... ] Uncompressing HPLIP 3.15.2 Plugin Self Extracting Archive... Error importing HPLIP modules. Is HPLIP installed? I changed to /usr/bin, and noticed that python was a symlink to python2.7; I temporarily made it be a symlink to python3.4, and I managed to install the proprietary plugin for my printer. However, other software would crash, so I reverted to have the symlink pointing to the old python2.7 location. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: hplip 3.15.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-15.15-lowlatency 3.19.3 Uname: Linux 3.19.0-15-lowlatency x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 26 16:13:19 2015 Lpstat: device for HP_COLOR_LaserJet: hp:/net/HP_LaserJet_200_color_M251nw?zc=NPI6A3827 device for HP_LaserJet_Professional_M1212nf_MFP: hp:/usb/HP_LaserJet_Professional_M1212nf_MFP?serial=0QJ4316YPR1a MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP Papersize: letter PpdFiles: HP_COLOR_LaserJet: HP LaserJet 200 color M251 Postscript (recommended) HP_LaserJet_Professional_M1212nf_MFP: HP LaserJet Professional m1212nf MFP, hpcups 3.15.2, requires proprietary plugin ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-lowlatency root=UUID=edc6b677-0e99-4da6-83b8-12f019053f9f ro quiet splash vt.handoff=7 SourcePackage: hplip UpgradeStatus: Upgraded to vivid on 2014-04-12 (378 days ago) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/12/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448794 Title: hp-plugin needs /usr/bin/python to point to python3* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1448794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1437692] Re: cups-browsed crashed with SIGABRT in __GI_____strtof_l_internal()
Yes, indeed, the crashes are not happening anymore, sorry, I should have updated this. On Apr 13, 2015 9:11 AM, Till Kamppeter 1437...@bugs.launchpad.net wrote: Most probably fixed in cups-browsed 1.0.67-0ubuntu2. Please update and re-open this bug if you still have problems. ** Information type changed from Private to Public ** Changed in: cups-filters (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1437692 Title: cups-browsed crashed with SIGABRT in __GI_strtof_l_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1437692/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437692 Title: cups-browsed crashed with SIGABRT in __GI_strtof_l_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1437692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308264] Re: Ubuntu 14.04 Beta 2 stuck at Switched to clocksource tsc when booting up, then resumes booting to the login screen, after 1 minute
Same here, I am running the current version of Xubuntu 15.04 on an HP Chromebook 14 Falco, and the (50s) delay disappears when using the tpm_tis.force=1 option in grub. I wonder if this has to do with loading Ubuntu from coreboot, since the setting is related to Trusted Platform management between the kernel and the Bios [1]. I am attaching some relevant dmesg output [2]. Cheers! Leo [1] http://resources.infosecinstitute.com/linux-tpm-encryption/ [2] Dmesg output: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.18.0-9-generic root=UUID=e59338a7-cc1f-4053-9a89-82ee7d3dd0db ro quiet splash tpm_tis.force=1 vt.handoff=7 [0.00] DMI: Hewlett-Packard Falco, BIOS 08/13/2014 [0.671007] tpm_tis tpm_tis: 1.2 TPM (device-id 0xB, rev-id 16) [8.608433] tpm_inf_pnp 00:08: Found TPM with ID IFX0102 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308264 Title: Ubuntu 14.04 Beta 2 stuck at Switched to clocksource tsc when booting up, then resumes booting to the login screen, after 1 minute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1308264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
Ok, before rebooting, I just removed the offending file. It is growing at a rate of 1Gb every 10s or so. I will try logging out and in, and see if the log is still growing continuously ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
It just happened here. I will need to clean up and reboot. This is how it looks like lmilano@grisell:upstart$ ls -lh unity7.log -rw-r- 1 lmilano users 53G Nov 12 16:03 unity7.log lmilano@grisell:upstart$ tail unity7.log _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 1lmilano@grisell:upstart$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
To be clear: I removed the file before rebooting, but it got regenerated and refilled at a furious pace, with the same message: _xgeWireToEvent: Unknown extension 148, this should never happen. At that time, top was reporting upstart as the most process, obviously caught in an infinite loop throwing this erroor about the extension 148. It seems like this is the bug: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1369113 And it seems that the spamming, at least, would be removed with an upgrade of libXext to 1.3.3. Or at least, it would be nice to backport the relevant patch http://patchwork.freedesktop.org/patch/22124/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353940] Re: webgl no longer works
Same here, Ubuntu 14.10, Intel Haswell i5 graphics. The following workaround (suggested in the chromium issue shown above) works for me: google-chrome -disable-gpu-sandbox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353940 Title: webgl no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1353940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386077] Re: [Dell XPS 13 9333] Touchpad not detected on Ubuntu 14.10
Christopher, I am not sure what you mean. I experienced exactly the same bug as described here (Touchpad not detected on Ubuntu 14.10) on exactly the same hardware (Dell XPS 13), under the exact same conditions (upgrade from 14.10). I am providing information in the interest of helping handle the issue. Opening a duplicate as you suggest would certainly not help. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386077 Title: [Dell XPS 13 9333] Touchpad not detected on Ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1386077] Re: [Dell XPS 13 9333] Touchpad not detected on Ubuntu 14.10
Same here. I have an xps 13 running ubuntu 14.10. When I upgraded from 12.04 (as installed by dell) into 14.04, I had to blacklist i2c_hid. After upgrading to 14.10, i needed to remove the blacklisting, as others reported. Here is the interesting thing: I needed to blacklist two different i2c modules (but see my first note below). me@myxps:~$ grep i2c /etc/modprobe.d/blacklist.conf # blacklist i2c_hid # blacklist i2c_i801 A few notes: * when dealing kernel settings in laptops, I find that it's often the case that it's better to shut down and power cycle, instead of restarting. It seems like the BIOS doesn't quite get the hardware reset on a restart. * Joseph: when testing upstream, what's the expected/desired behavior? It seems like 14.10 is already working ok for most users. It seems to me that the blacklisting was a workaround in 14.04, not needed anymore. Or are you asking those who still have issues after de-blacklisting i2c_hic ? To those folks, I suggest trying a full shutdown and remove the power chord, and perhaps also removing the blacklist for i2c_i801 and see if that helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386077 Title: [Dell XPS 13 9333] Touchpad not detected on Ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
Same here. My 120Gb SSD just filled up. Good thing I'm an advanced user and I could manage to find the offending folder. A newbie would just need to give up. The harddrive analyzer would not give any info (maybe because the disk was full). In my case, it was unity7.log, which was about 50Gb. Is there any way to completely stop the upstart logging? Shouldn't that be the default for regular users? This seems like a real bug. Logrotate is installed here, and I'm running Ubuntu-14.10 (upgraded from older version for, well, close to 10 years now :-) ). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307746] Re: [SRU] pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock()
Hi Chris Thank you for uploading the package. Unfortunately, I already upgraded the machine where I had the crash to Utopic. I tried on another machine running trusty, and both before and after enabling proposed (and therefore upgrading to 0.93-3ubuntu0.1 ), pitivi loads just fine. So, all I can say on my end is that I don't see any obvious regression. I hope others can test this fix! Cheers Leo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307746 Title: [SRU] pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/pitivi/+bug/1307746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307746] Re: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock()
Another update. As of today, pitivi is not crashing anymore. I've been running updates daily, though I didn't see remember having seen any pitivi update. The changelog doesn't show any recent changes, either: http://changelogs.ubuntu.com/changelogs/pool/universe/p/pitivi/ I guess some unnderlying library must have been updated (or uninstalling gnome-shell and unity, something I did yesterday after testing with them, removed a conflicting binary?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307746 Title: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/pitivi/+bug/1307746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307746] Re: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock()
Ouch, it might be the same issue. I don't have gnome-shell installed, and installing the metapackage didn't enable a session in lightdm. The Ubuntu (Unity) shell prouces the same crash. But sudo pitivi works fine. I'll look around to enable a gnome-shell session and try from there. Thanks for the suggestion, Lubosz! (in the meantime, for anyone having the same issue, you can download a self contained pitivi bundle, see here for more info: http://www.pitivi.org/?go=download) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307746 Title: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/pitivi/+bug/1307746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307746] Re: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock()
Ok. It looks like running from the gnome-shell doesn't help. This is what I added to my Kubuntu install: * gnome-shell * ubuntu-gnome-desktop Now I can login to Ubuntu (unity), Gnome (gnome-shell, I believe), Gnome Classic, KDE Plasma and others. Pitivi crashes in all of them, whether from the menu or the command line. Only root can run it without segfaulting. Hope this helps! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307746 Title: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/pitivi/+bug/1307746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307746] Re: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock()
I just tested installing the Unity package to see if a more typical Ubuntu installation would not crash, but I had not luck. I'll gladly help with testing if anyone has any ideas of what to try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307746 Title: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/pitivi/+bug/1307746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307746] [NEW] pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock()
Public bug reported: I just upgraded to Kubuntu 14.04 (Trusty) yesterday, and pitivi stopped working. It segfaults immediately, with the following stdout error: lmilano@grisell:crash$ pitivi Missing soft dependency: - pycanberra not found on the system - enables sound notifications when rendering is complete Segmentation fault (core dumped) Apport is not popping up, even if I launch pitivi from the main menu in KDE. But it did, just once, and it dumped a report in /var/crash - I will try to upload that file manually. ** Affects: pitivi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307746 Title: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1307746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307746] Re: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock()
** Attachment added: Apport crash report from /var/crash https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1307746/+attachment/4083897/+files/_usr_bin_pitivi.1002.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307746 Title: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1307746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307746] Re: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock()
** Description changed: - I just upgraded to Kubuntu 12.04 yesterday, and pitivi stopped working. - It segfaults immediately, with the following stdout error: + I just upgraded to Kubuntu 14.04 (Trusty) yesterday, and pitivi stopped + working. It segfaults immediately, with the following stdout error: lmilano@grisell:crash$ pitivi Missing soft dependency: - pycanberra not found on the system - - enables sound notifications when rendering is complete + - enables sound notifications when rendering is complete Segmentation fault (core dumped) Apport is not popping up, even if I launch pitivi from the main menu in - KDE. But it did, just once, and it dumped a report in /var/crash - - I will try to upload that file manually. + KDE. But it did, just once, and it dumped a report in /var/crash - I + will try to upload that file manually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307746 Title: pitivi crashed with SIGSEGV in __GI___pthread_mutex_lock() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1307746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1119209] Re: Lightdm does not start on a netboot of Kubuntu 13.04
Same here. I have a Dell Vostro A90 with a Minimal KDE install, and lightdm as the DM, running 13.04 daily updates . It is set up to autologin. In thefin last couple days, upon reboot, the computer comes to a command line login. You can login, and then run sudo lightdm, or sudo service lightdm start. In both cases it works just fine. I suspect upstart is not running lightdm anymore, and this seems a regression. I'll play with BUM if I have some time, to confirm. Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1119209 Title: Lightdm does not start on a netboot of Kubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1119209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1119209] Re: Lightdm does not start on a netboot of Kubuntu 13.04
Confirmed! I launched BUM, and lightdm was not selected. I activated it, rebooted, and everything is back to normal (the graphical login goes on normally). Hope this helps! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1119209 Title: Lightdm does not start on a netboot of Kubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1119209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986374] Re: oneiric-precise upgrade failed: E:Internal Error, Could not early remove python-minimal
Same here. Patrick's workaround (thanks) wasn't quite enough. I needed to run it on the python program sudo apt-get install -o APT::Force-LoopBreak=1 python -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986374 Title: oneiric-precise upgrade failed: E:Internal Error, Could not early remove python-minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/986374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496435] Re: upgrades of the grub-pc package can overwrite wrong MBR
This is still an issue in Oneiric. Here is my case: * a computer with two hard-drives. One of the MBR of these is used to bottup normally * I introduced a USB stick with Kubuntu 11.04, booted from USB, and upgraded to Oneiric (11.10) After the upgrade, the MBR in the HD of the desktop computer was now damaged, it would no longer boot from HD The fix was, as usual, to boot the HD partition from the USB's Grub, and then run grub-install /dev/sdX , where X was the appropriate value (either a or b). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/496435 Title: upgrades of the grub-pc package can overwrite wrong MBR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857828] Re: kontact migration to 11.10 fails
I just had another crash. Even though I had some success with the migration, KMail sometimes freezes, folders take a long time to refresh and show the contents of the emails, and this is the most recent crash (I will install the debug symbols). Soprano is disabled right now, as it tends to crash or apparently leak memory , and takes over my 3 cpus, although it's been indexing for days now). Application: KMail (kmail), signal: Segmentation fault [Current thread is 1 (Thread 0x7f878f9787a0 (LWP 3309))] Thread 4 (Thread 0x7f8770147700 (LWP 3358)): #0 0x7f878a8a004c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7f8781c52c2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f8781c52d59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f878a89befc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7f878ccf589d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x in ?? () Thread 3 (Thread 0x7f876f846700 (LWP 3360)): #0 0x7f878cce9773 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f8785740f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8785741429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f878d667f3e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f878d63bcf2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f878d63bef7 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f878d55327f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f878d555d05 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f878a89befc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f878ccf589d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x in ?? () Thread 2 (Thread 0x7f876c814700 (LWP 3476)): #0 0x7f878cce9773 in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f8785740f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8785741429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f878d667f3e in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #4 0x7f878d63bcf2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #5 0x7f878d63bef7 in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #6 0x7f878d55327f in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #7 0x7f878d61ecbf in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f878d555d05 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f878a89befc in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f878ccf589d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x in ?? () Thread 1 (Thread 0x7f878f9787a0 (LWP 3309)): [KCrash Handler] #6 0x7f878ee1abbf in ?? () from /usr/lib/libkdecore.so.5 #7 0x7f878d554107 in QThreadStorageData::set(void*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #8 0x7f878ee198a2 in ?? () from /usr/lib/libkdecore.so.5 #9 0x7f878ee18e12 in KServiceTypeTrader::applyConstraints(QListKSharedPtrKService , QString const) () from /usr/lib/libkdecore.so.5 #10 0x7f878ee18ffe in KServiceTypeTrader::defaultOffers(QString const, QString const) const () from /usr/lib/libkdecore.so.5 #11 0x7f878ee19751 in KServiceTypeTrader::query(QString const, QString const) const () from /usr/lib/libkdecore.so.5 #12 0x7f877f7fb33e in ?? () from /usr/lib/libkemoticons.so.4 #13 0x7f877f7fb49a in KEmoticons::KEmoticons() () from /usr/lib/libkemoticons.so.4 #14 0x7f8786c15128 in KPIMUtils::LinkLocator::convertToHtml(QString const, int, int, int) () from /usr/lib/libkpimutils.so.4 #15 0x7f8786738d54 in ?? () from /usr/lib/libmessageviewer.so.4 #16 0x7f8786742d9c in ?? () from /usr/lib/libmessageviewer.so.4 #17 0x7f878679408f in ?? () from /usr/lib/libmessageviewer.so.4 #18 0x7f87867a283d in ?? () from /usr/lib/libmessageviewer.so.4 #19 0x7f87867a5434 in ?? () from /usr/lib/libmessageviewer.so.4 #20 0x7f87867a5ce2 in ?? () from /usr/lib/libmessageviewer.so.4 #21 0x7f87867a918d in ?? () from /usr/lib/libmessageviewer.so.4 #22 0x7f878d64feba in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #23 0x7f878d653789 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #24 0x7f878db6d424 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
[Bug 857828] Re: kontact migration to 11.10 fails
And this is the standard output of the previous crash
lmilano@grisell:~$ kmail
[1] 3308
lmilano@grisell:~$ /usr/bin/kmail(3309) Soprano:
org.freedesktop.DBus.Error.NoReply - Did not receive a reply. Possible causes
include: the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network connection
was broken.
/usr/bin/kmail(3309) Soprano: QLocalSocket::connectToServer: Connection
refused
/usr/bin/kmail(3309) Soprano: org.freedesktop.DBus.Error.UnknownObject - No
such object path '/org/soprano/Server'
Object::connect: No such slot KMMainWidget::slotItemNotMovedByFilters(
Akonadi::Item )
/usr/bin/kmail(3309) Soprano: SQLExecDirect failed on query 'sparql select *
where { graph ?g { ?s http://www.w3.org/1999/02/22-rdf-syntax-ns#type
http://www.semanticdesktop.org/ontologies/2007/08/15/nao#Tag . } . FILTER(?g
!= http://www.openlinksw.com/schemas/virtrdf#) . }' (iODBC Error:
[OpenLink][Virtuoso iODBC Driver]CL064: Lost connection to server)
/usr/bin/kmail(3309) Soprano: SQLExecDirect failed on query 'sparql select *
where { graph ?g { ?s http://www.w3.org/1999/02/22-rdf-syntax-ns#type
http://www.semanticdesktop.org/ontologies/2007/08/15/nao#Tag . } . FILTER(?g
!= http://www.openlinksw.com/schemas/virtrdf#) . }' (iODBC Error:
[OpenLink][Virtuoso iODBC Driver]CL064: Lost connection to server)
/usr/bin/kmail(3309) Soprano: SQLExecDirect failed on query 'sparql select *
where { graph ?g { ?s http://www.w3.org/1999/02/22-rdf-syntax-ns#type
http://www.semanticdesktop.org/ontologies/2007/08/15/nao#Tag . } . FILTER(?g
!= http://www.openlinksw.com/schemas/virtrdf#) . }' (iODBC Error:
[OpenLink][Virtuoso iODBC Driver]CL064: Lost connection to server)
/usr/bin/kmail(3309) Soprano: SQLExecDirect failed on query 'sparql select *
where { graph ?g { ?s http://www.w3.org/1999/02/22-rdf-syntax-ns#type
http://www.semanticdesktop.org/ontologies/2007/08/15/nao#Tag . } . FILTER(?g
!= http://www.openlinksw.com/schemas/virtrdf#) . }' (iODBC Error:
[OpenLink][Virtuoso iODBC Driver]CL064: Lost connection to server)
/usr/bin/kmail(3309) Soprano: Invalid iterator.
local socket error: QLocalSocket::PeerClosedError
kmail2(3309): Error while fetching items. 103 Unknown error. (Unable to fetch
item from backend)
kmail2(3309): Error while fetching items. 103 Unknown error. (Unable to fetch
item from backend)
kmail2(3309): Error while fetching items. 103 Unknown error. (Unable to fetch
item from backend)
/usr/bin/kmail(3309) Soprano: QLocalSocket::connectToServer: Connection
refused
/usr/bin/kmail(3309) Soprano: org.freedesktop.DBus.Error.ServiceUnknown -
The name org.kde.nepomuk.services.nepomukstorage was not provided by any
.service files
/usr/bin/kmail(3309) Soprano: QLocalSocket::connectToServer: Connection
refused
/usr/bin/kmail(3309) Soprano: QLocalSocket::connectToServer: Connection
refused
/usr/bin/kmail(3309) Soprano: QLocalSocket::connectToServer: Connection
refused
/usr/bin/kmail(3309) Soprano: org.freedesktop.DBus.Error.ServiceUnknown -
The name org.kde.nepomuk.services.nepomukstorage was not provided by any
.service files
/usr/bin/kmail(3309) Soprano: Unsupported operation (2): Invalid model
/usr/bin/kmail(3309) Soprano: org.freedesktop.DBus.Error.ServiceUnknown -
The name org.kde.nepomuk.services.nepomukstorage was not provided by any
.service files
/usr/bin/kmail(3309) Soprano: Unsupported operation (2): Invalid model
/usr/bin/kmail(3309) Soprano: Unsupported operation (2): Invalid model
/usr/bin/kmail(3309) Soprano: Invalid iterator.
/usr/bin/kmail(3309) Soprano: org.freedesktop.DBus.Error.ServiceUnknown -
The name org.kde.nepomuk.services.nepomukstorage was not provided by any
.service files
/usr/bin/kmail(3309) Soprano: QLocalSocket::connectToServer: Connection
refused
/usr/bin/kmail(3309) Soprano: org.freedesktop.DBus.Error.ServiceUnknown -
The name org.kde.nepomuk.services.nepomukstorage was not provided by any
.service files
/usr/bin/kmail(3309) Soprano: Unsupported operation (2): Invalid model
/usr/bin/kmail(3309) Soprano: org.freedesktop.DBus.Error.ServiceUnknown -
The name org.kde.nepomuk.services.nepomukstorage was not provided by any
.service files
/usr/bin/kmail(3309) Soprano: Unsupported operation (2): Invalid model
/usr/bin/kmail(3309) Soprano: Unsupported operation (2): Invalid model
/usr/bin/kmail(3309) Soprano: Invalid iterator.
/usr/bin/kmail(3309) Soprano: org.freedesktop.DBus.Error.ServiceUnknown -
The name org.kde.nepomuk.services.nepomukstorage was not provided by any
.service files
/usr/bin/kmail(3309) Soprano: QLocalSocket::connectToServer: Connection
refused
/usr/bin/kmail(3309) Soprano: org.freedesktop.DBus.Error.ServiceUnknown -
The name org.kde.nepomuk.services.nepomukstorage was not provided by any
.service files
/usr/bin/kmail(3309) Soprano: Unsupported operation (2): Invalid model
/usr/bin/kmail(3309) Soprano: org.freedesktop.DBus.Error.ServiceUnknown -
The name
[Bug 857828] Re: kontact migration to 11.10 fails
And this is a new stack trace, now that I installed the debug symbols. By the way, folks, help here is appreciated, but venting is inappropriate. This is not a forum, but a bug tracker. Thread 1 (Thread 0x7f878f9787a0 (LWP 3309)): [KCrash Handler] #6 deref (this=0x7f877f3c2bd8) at /usr/include/qt4/QtCore/qatomic_x86_64.h:133 #7 ~KSharedPtr (this=0x1a3a0c0, __in_chrg=optimized out) at ../../kdecore/util/ksharedptr.h:90 #8 ~ParsingData (this=0x1a3a0c0, __in_chrg=optimized out) at ../../kdecore/services/ktraderparse.cpp:40 #9 QThreadStorageKTraderParse::ParsingData*::deleteData (x=0x1a3a0c0) at /usr/include/qt4/QtCore/qthreadstorage.h:133 #10 0x7f878d554107 in QThreadStorageData::set (this=0x4f55bb0, p=0x52369f0) at thread/qthreadstorage.cpp:165 #11 0x7f878ee198a2 in qThreadStorage_setLocalDataKTraderParse::ParsingData (d=optimized out, t=optimized out) at /usr/include/qt4/QtCore/qthreadstorage.h:92 #12 setLocalData (t=0x52369f0, this=optimized out) at /usr/include/qt4/QtCore/qthreadstorage.h:148 #13 KTraderParse::parseConstraints (_constr=...) at ../../kdecore/services/ktraderparse.cpp:55 #14 0x7f878ee18e12 in applyConstraints (constraint=optimized out, lst=...) at ../../kdecore/services/kservicetypetrader.cpp:59 #15 KServiceTypeTrader::applyConstraints (lst=..., constraint=optimized out) at ../../kdecore/services/kservicetypetrader.cpp:53 #16 0x7f878ee18ffe in KServiceTypeTrader::defaultOffers (this=optimized out, serviceType=optimized out, constraint=...) at ../../kdecore/services/kservicetypetrader.cpp:127 #17 0x7f878ee19751 in KServiceTypeTrader::query (this=0x19888b0, serviceType=..., constraint=...) at ../../kdecore/services/kservicetypetrader.cpp:141 #18 0x7f877f7fb33e in KEmoticonsPrivate::loadServiceList (this=0x5220b30) at ../../kutils/kemoticons/kemoticons.cpp:71 #19 0x7f877f7fb49a in KEmoticons::KEmoticons (this=0x5220c90) at ../../kutils/kemoticons/kemoticons.cpp:121 #20 0x7f8786c15128 in operator- (this=optimized out) at ../../kpimutils/linklocator.cpp:56 #21 KPIMUtils::LinkLocator::convertToHtml (plainText=optimized out, flags=optimized out, maxUrlLen=optimized out, maxAddressLen=optimized out) at ../../kpimutils/linklocator.cpp:426 #22 0x7f8786738d54 in MessageViewer::strToHtml (str=optimized out, flags=optimized out) at ../../messageviewer/headerstyle.cpp:85 #23 0x7f8786742d9c in MessageViewer::FancyHeaderStyle::format (this=0x1d3fe10, message=0x1a5cd90) at ../../messageviewer/headerstyle.cpp:598 #24 0x7f878679408f in MessageViewer::ViewerPrivate::writeMsgHeader (this=0x1cd9fb0, aMsg=0x1a5cd90, vCardNode=optimized out, topLevel=true) at ../../messageviewer/viewer_p.cpp:907 #25 0x7f87867a283d in MessageViewer::ViewerPrivate::parseContent (this=0x1cd9fb0, content=0x1a5cd90) at ../../messageviewer/viewer_p.cpp:846 #26 0x7f87867a5434 in MessageViewer::ViewerPrivate::displayMessage (this=0x1cd9fb0) at ../../messageviewer/viewer_p.cpp:729 #27 0x7f87867a5ce2 in MessageViewer::ViewerPrivate::updateReaderWin (this=0x1cd9fb0) at ../../messageviewer/viewer_p.cpp:1946 #28 0x7f87867a918d in MessageViewer::ViewerPrivate::qt_metacall (this=0x1cd9fb0, _c=QMetaObject::InvokeMetaMethod, _id=27, _a=0x7fff2ecdf980) at ./viewer_p.moc:220 #29 0x7f878d64feba in QMetaObject::activate (sender=0x1cda038, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3278 #30 0x7f878d653789 in QObject::event (this=0x1cda038, e=optimized out) at kernel/qobject.cpp:1181 #31 0x7f878db6d424 in notify_helper (e=0x7fff2ecdfee0, receiver=0x1cda038, this=0x1633760) at kernel/qapplication.cpp:4486 #32 QApplicationPrivate::notify_helper (this=0x1633760, receiver=0x1cda038, e=0x7fff2ecdfee0) at kernel/qapplication.cpp:4458 #33 0x7f878db72291 in QApplication::notify (this=0x7fff2ece02a0, receiver=0x1cda038, e=0x7fff2ecdfee0) at kernel/qapplication.cpp:4365 #34 0x7f878f38e1e6 in KApplication::notify (this=0x7fff2ece02a0, receiver=0x1cda038, event=0x7fff2ecdfee0) at ../../kdeui/kernel/kapplication.cpp:311 #35 0x7f878d63cafc in QCoreApplication::notifyInternal (this=0x7fff2ece02a0, receiver=0x1cda038, event=0x7fff2ecdfee0) at kernel/qcoreapplication.cpp:787 #36 0x7f878d669d62 in sendEvent (event=0x7fff2ecdfee0, receiver=optimized out) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #37 QTimerInfoList::activateTimers (this=0x16356d0) at kernel/qeventdispatcher_unix.cpp:603 #38 0x7f878d667514 in timerSourceDispatch (source=optimized out) at kernel/qeventdispatcher_glib.cpp:184 #39 0x7f8785740a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #40 0x7f8785741258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #41 0x7f8785741429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #42 0x7f878d667ed6 in QEventDispatcherGlib::processEvents (this=0x15e6f70, flags=optimized out) at
[Bug 857828] Re: kontact migration to 11.10 fails
So, here is a summary of the migration (see comment #18 above): • it completed successfully after a long time (more than one hour for about 20k emails on a 3core fast desktop) • it added a new IMAP Google account/folder I didn’t have and seemed to slow things down significantly • it created some Local Folders (besides KMail folders) and placed a few of my “Inbox” emails in the Local Folders’ Inbox. The rest stayed in the right Inbox within “KMail Folders”. This is probably a result of the first failed migration • I used to have Kontact to autostart on login. I wonder if, after distro upgrade, Kontact started before akonadi and the original migration failed because of that • KWallet was disabled and that created also lots of errors/grief. I ran KWallet from the menu and activated it for use with KDE. After that, password management got smoother (without that, the second migration worked, but I would have to retype each account’s password after each login to KDE) Hope this helps! Leo -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdepim in Ubuntu. https://bugs.launchpad.net/bugs/857828 Title: kontact migration to 11.10 fails To manage notifications about this bug go to: https://bugs.launchpad.net/kdepim/+bug/857828/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 857828] Re: kontact migration to 11.10 fails
Thanks, Clay! I removed ~/.kde/share/config/kmail-migratorrc and re- ran kmail-migrator --interactive. This time I got a the migration tool to complete and show a succeeded check mark at the end. The command line showed some errors or warnings. The message notification widget showed a bunch of errors about the different email folders I have, and the 3 cores in the desktop have been churning for 10 minutes, apparently importing my emails (I have email back to 1995 in this machine) into the different email folders I used to have. I will report again when it finishes up. Below are some typical errors shown in the terminal. Thanks! -- Leo /usr/bin/kmail-migrator(22850) Soprano: Unsupported operation (2): Invalid model /usr/bin/kmail-migrator(22850) Soprano: org.freedesktop.DBus.Error.ServiceUnknown - The name org.kde.nepomuk.services.nepomukstorage was not provided by any .service files /usr/bin/kmail-migrator(22850) Soprano: Unsupported operation (2): Invalid model /usr/bin/kmail-migrator(22850) Soprano: Unsupported operation (2): Invalid model kmail-migrator(22850)/kdeui (Wallet): The kwalletd service has been disabled kmail-migrator(22850)/kdeui (Wallet): The kwalletd service has been disabled kmail-migrator(22850)/kdeui (Wallet): The kwalletd service has been disabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857828 Title: kontact migration to 11.10 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/857828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 857828] Re: kontact migration to 11.10 fails
Same here. I lost all my email settings. The migration failed in the first login after the upgrade. I got a pop up asking me to run kmail- migrator --interactive manually. But if I do, I get the following error: lmilano@grisell:config$ kmail-migrator --interactive kmail-migrator(9148) main: Migration of kmailrc has already run, not running it again removing kmail2rc doesn't help. Quite a showstopper for new users! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/857828 Title: kontact migration to 11.10 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/857828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847782] Re: installer writes a permanent ethernet entry in interfaces file
Hi Clint Thanks for the changes in failsafe.conf, neat work! A ten second countdown would probably give slightly better feedback to the user (but it isn't essential or anything): $PLYMOUTH message --text=Waiting up to 60 more seconds for network configuration... || : sleep 10 $PLYMOUTH message --text=Waiting up to 50 more seconds for network configuration... || : sleep 10 $PLYMOUTH message --text=Waiting up to 40 more seconds for network configuration... || : sleep 10 [etc] I also tested removing the iface eth0 and there is no delay, so the fix to bug #838968 seems to be working ok, which will alleviate the situation here I'm not convinced that normal installs lead to 'auto ethX' in /etc/network/interfaces. Only installs that started life without network-manager will have it, which is certainly not the norm. Yes, that was the initial understanding. However, comment #5 by Robert Hooker seemed to indicate that this is not the case (wouldn't the normal live CD always initiate NetworkManager). But I downloaded the Beta 1 live CD, burned a USB image and I still couldn't reproduce Robert's observation. I was using a DHCP connection. @Robert: could you please give a little more details on how to reproduce what you see? Maybe show your interfaces file? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847782 Title: installer writes a permanent ethernet entry in interfaces file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/847782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847782] Re: installer writes a permanent ethernet entry in interfaces file
Yes, Damian, this is the same bug. To double check, you can temporarily edit that file (using sudo), and add a # character in from of the ppp0 related lines. This should bring your boot time back to normal. So, a couple questions, mostly because it's not clear who is affected: 1) have you ever used an alternative network manager? (such as wicd, etc) 2) what installation procedure have you used, originally? (regular cd, alternate cd, etc) Thanks for reporting! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847782 Title: installer writes a permanent ethernet entry in interfaces file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/847782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847782] Re: installer writes a permanent ethernet entry in interfaces file
Clint: something to consider. How would people (except for advanced users) fix their interfaces files? Can we provide a bash script installed by default, that will allow people to quickly install a vanilla interfaces files? It could also save a backup, and optionally restore it with another script. Or a simple debian package that can be installed, etc. One way or the other, I think we need to provide an easy fix for the average user hit by this (and having the typical home networking connection, which doesn't need any customization of the interfaces file). Otherwise, we'll be one step further from fixing bug #1 :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847782 Title: installer writes a permanent ethernet entry in interfaces file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcfg/+bug/847782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Jeremy: Could either a new bug for this issue be opened or [...] Done! https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847782] Re: Ubiquity writes a permanent ethernet entry in interfaces file
** Description changed: In certain situations, ubiquity writes an auto ethN line /etc/network/interfaces. This means that the boot up process, including - bringing up the X system by upstart, will be delayed for whatever grace - period is defined in /etc/init/failsafe.conf . This is currently 120 + bringing up the X system by upstart, will be delayed for whatever + timeout is defined in /etc/init/failsafe.conf . This is currently 120 seconds This seems to affect mostly (if not only) people who use either the - netinstall, or the alternate CD, while using a whired connection. + netinstall, or the alternate CD, while using a whired connection. Note + that a line stating auto eth0 will prevent the network from being + considered up, unless the ethernet card is connected to the internet. + Adding this line by hand might be a good idea for certain servers, but + for most practical use it is not needed, since network manager will + always bring up an ethernet connection via DHCP. Please see bug #839595 for more information -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847782 Title: Ubiquity writes a permanent ethernet entry in interfaces file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/847782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Sorry for the typo in my last statement, the new bug report is bug #847782 https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/847782 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845914] Re: Failsafe boot delay causes a real delay on every boot
I think this is mostly a duplicate of bug # 839595 . And the short of it, is that upstart seems to be doing the right thing, but ubiquity seems to be the problem. A new bug report has been reported for ubiquity, bug #847782 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845914 Title: Failsafe boot delay causes a real delay on every boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/845914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847782] Re: Ubiquity writes a permanent ethernet entry in interfaces file
Scott: it seems clear that a permanent connection in a machine needs to be there, yes. However, it is assuming that any user who has ethernet plugged in needs that. This seems dangerous, particularly because it makes people have subsequent 3 minute boot up times. Why not just ask the user? (and want the user about possible large delays in boot up if they choose permanent for something that isn't) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847782 Title: Ubiquity writes a permanent ethernet entry in interfaces file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/847782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847782] [NEW] Ubiquity writes a permanent ethernet entry in interfaces file
Public bug reported: In certain situations, ubiquity writes an auto ethN line /etc/network/interfaces. This means that the boot up process, including bringing up the X system by upstart, will be delayed for whatever grace period is defined in /etc/init/failsafe.conf . This is currently 120 seconds This seems to affect mostly (if not only) people who use either the netinstall, or the alternate CD, while using a whired connection. Please see bug #839595 for more information ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847782 Title: Ubiquity writes a permanent ethernet entry in interfaces file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/847782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847782] Re: installer writes a permanent ethernet entry in interfaces file
Clint: good point about annoying vs safer. Overall, I don't think we know, at installation time, what the user intends to do. In my case, for instance, I never intended to create any static connection. Actually, I configured a DHCP ethernet connection. I really had no intention of persisting the connection, and such is the case of other folks commenting in the related bug reports. Of course, other people will be setting up servers in some large institutions/corporation, and they deserve to be So, yes, I think the best way to handle this is by explicitly asking the user before leaving the installation. The simpler installer doesn't hardcode ethernet connections, so the bulk of the users are not a concern. And the folks doing a custom install won't mind an extra question. Should I update the bug description along these? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847782 Title: installer writes a permanent ethernet entry in interfaces file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/847782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847782] Re: installer writes a permanent ethernet entry in interfaces file
** Description changed: - In certain situations, ubiquity writes an auto ethN line + In certain situations, ubiquity writes an auto ethX line in /etc/network/interfaces. This means that the boot up process, including bringing up the X system by upstart, will be delayed for whatever timeout is defined in /etc/init/failsafe.conf (see bug 839595). This is - currently 120 seconds + currently 120 seconds. - This seems to affect mostly (if not only) people who use either the - netinstall, or the alternate CD, while using a whired connection. Note - that a line stating auto eth0 will prevent the network from being - considered up, unless the ethernet card is connected to the internet. - Adding this line by hand might be a good idea for certain servers, but - for most practical use it is not needed, since network manager will - always bring up an ethernet connection via DHCP. + This only affects users who customized the interfaces file by hand, as + well as people who used either the netinstall, or the alternate + installation CD, on a wired connection. + + So far, it seems like the best solution would be for the custom (net or + alternative) installer to give the user the option to choose what to do + with the interfaces file after finishing installation Please see bug #839595 for more information -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847782 Title: installer writes a permanent ethernet entry in interfaces file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/847782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847782] Re: installer writes a permanent ethernet entry in interfaces file
Thanks, Robert! I will update the description, since this is very relevant. Basically, the installer is always adding auto ethX to the interfaces file, provided there is an ethernet connection at install time. This means the problem will be much more widespread than we had thought. I think the severity of this bug is higher than Medium, but I can't change that. So, all the installers should address this. And I think the upgrade tool should address this, as well. Many people who have never used the command line but had an ethernet connection in their first install, will have 3 minutes boot delays until/unless they learn how to modify a text file in sudo mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847782 Title: installer writes a permanent ethernet entry in interfaces file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/847782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 847782] Re: installer writes a permanent ethernet entry in interfaces file
** Description changed: - In certain situations, ubiquity writes an auto ethX line in - /etc/network/interfaces. This means that the boot up process, including - bringing up the X system by upstart, will be delayed for whatever - timeout is defined in /etc/init/failsafe.conf (see bug 839595). This is - currently 120 seconds. + If Ubiquity (the installer) is ran while connected to the internet via + ethernet, writes an auto ethX line in /etc/network/interfaces. This + means that the boot up process, including bringing up the X system by + upstart, will be delayed for whatever timeout is defined in + /etc/init/failsafe.conf (see bug 839595). This is currently 120 seconds. - This only affects users who customized the interfaces file by hand, as - well as people who used either the netinstall, or the alternate - installation CD, on a wired connection. - - So far, it seems like the best solution would be for the custom (net or - alternative) installer to give the user the option to choose what to do - with the interfaces file after finishing installation + So far, it seems like the best solution would be for the installer to + give the user the option to choose what to do with the interfaces file + after finishing installation. This will also be an issue with upgrades + to Oneiric, so the upgrade tool should probably offer the user to fix + the interfaces file. In all cases, the user should be offered a sane + default behavior. Please see bug #839595 for more information -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/847782 Title: installer writes a permanent ethernet entry in interfaces file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/847782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Clint, I'll give it a swirl. Where exactly do you add --verbose? Do you mean to remove the quiet linux boot parameter? Or add splash=verbose ? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Will do. I assume you mean to run a grep on syslog right after I login (or pls let me know otherwise). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Robert, Chris, I think you are both hitting also the other problem I encountered, namely the fact that X is not starting until failsafe is up (even though theoretically this should not be the case). Could you please look at comment #21 by Clint and post the info he is asking for as well? I will, later today, but I am guessing the more the merrier, since this looks like it would become a high impact issue (I am glad we found it) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Clint. The biggest issues it that we are not sure, but it is plausible that a large proportion of the existing systems will suffer a 2 minute delay after the upgrade. How about we test this: * remove the offending ethN line from /etc/networking/interfaces * reboot * connect the laptop/desktop to an ethernet device at some point, to see if network manager is actually adding that entry again, which is what Robert suggested in #22 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Three is a crowd! I have 4 machines running kubuntu. Two started out with regular CD/USB live image installed to disk. The other two were installed from the netinstall mini-iso, connected to ethernet. These two are the only ones where I see an auto ethN. I also played in one of my machines extensively with the network management plasma widget and the ethernet config (as I suggested in post #26). I could never, ever get it to save anything to the /etc/network/interfaces files. It seems pretty conclusive that some of the ubuntu official installers are adding these auto ethN entries, which don't seem to make sense. Should we open a bug report for that? What's the proper place? In addition, I agree with Clint that the more e can do to help users hitting this the better. It will be a minority, but definitely a lot of people. Is it possible to have the update manager to actually correct this, save a back up of the offending interfaces files, and people the info on how to restore it if needed? Sames as happens when you upgrade KDM or GDM and it gives you the option to keep the custom config file or use a new one (with additional info pointing at the issue at hand) Cheers! Leo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Yes, that's correct. Is that something that should not be there? Thanks! santisofi@minime:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Scott, is this how things are intended to work? My current understanding is: * pre-start exec sleep N means wait up to N seconds for the preconditions to be satisfied. In this case, these are a network up and a fs up. I thought it meant Wait at least N seconds, but I guess I was wrong. * The current change makes the system to wait up to 120 seconds if the network is not brought up according to /etc/network/interfaces I think the latter is something that is not unlikely to happen for people who have been using different network managers and upgrading to new releases. Why would we do this? Isn't it better to proceed with the boot up even if the network is not fully up? Why is a network fully up a requirement to run rc-sysinit.conf? I would expect a flood of my boot up takes 3 minutes bug reports if this released with a potential two minute lag. Thanks! Leo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
@ Scott: thanks for the detailed response. It all makes sense now. I am guessing perhaps wicd wrote that entry in my interfaces file. I haven't edited this file by hand. @ Clint: yes, I think it makes sense to add this to the release notes. Thanks for updating the description. It seems like this is a reasonable approach for now. Longer term, I think the start system needs more granularity. Ideally, if the network is still not up, most services (except for things like ntp, firewalls, etc) should start anyway. The user should still be able to get X up and running, and be able to login. But the current structure of one upstart hook to all sysvinit services won't allow for that. Thank you for the great work, and I hope this little extra bit of info benefits other users. Best! -- Leo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
I will try to dig in a bit. My X clearly doesn't start until the penalty
120 secs expire, so I'd like to understand why, since for what you are
saying this shouldn't be the case (and there is, indeed, a kdm.conf in
/etc/init).
In the meantime: I use KDE, with KDM set to autologin to a user account.
In that user account, I run the script I show below (in
.kde/Autostart/). It basically runs an xterm, and then records the time
since boot started. It gives me a measure of the time from cold boot
into a usable desktop.
I will play a bit with lightdm, and will also try disabling autologin in
KDM.
Cheers
-- Leo
#!/bin/bash
#
# 2009, Leo Milano
#
# Credits: http://www.perlmonks.org/?node_id=11582
#
http://www.linuxscrew.com/2007/09/04/two-way-conversion-of-unix-time-seconds-since-1970-and-regular-time/
#
# Customize this if needed
log_file=~/boot_time.log
# A trick to make sure the script doesn't run this xterm in the background,
# we want the window to popup before we go on with the script
# Choose one of the dummy commands below
dummy=`xterm -e echo hi`
boot_time=`perl -ne 'print scalar $1 if /^btime (\d+)/' /proc/stat`
this_time=`date +%s`
let elapsed_time=this_time-boot_time
echo `date`. Boot Time [s]: ${elapsed_time} ${log_file}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/839595
Title:
failsafe.conf's 30 second time out is too low
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Hi, Just an update: Lightdm also gets penalized and waits the sleep time declared in failsafe.conf before loading -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Hi After installing this version of upstart is making, my netbook takes extra 100 seconds to boot. CTRL-ALT-F1 shows me that that the network security us being brought up. Any thoughts? Could this be a coincidence? Boot time (as measured with a script) has regressed incredibly over the last few days Sun Aug 28 21:26:50 PDT 2011. Boot Time [s]: 43 Tue Aug 30 20:44:08 PDT 2011. Boot Time [s]: 40 Thu Sep 1 19:59:34 PDT 2011. Boot Time [s]: 39 Thu Sep 1 21:19:29 PDT 2011. Boot Time [s]: 38 Fri Sep 2 19:33:38 PDT 2011. Boot Time [s]: 39 Sat Sep 3 23:24:53 PDT 2011. Boot Time [s]: 76 Sat Sep 3 23:26:57 PDT 2011. Boot Time [s]: 68 Sat Sep 3 23:29:49 PDT 2011. Boot Time [s]: 67 Sun Sep 4 17:52:59 PDT 2011. Boot Time [s]: 162 Sun Sep 4 21:29:33 PDT 2011. Boot Time [s]: 156 Thanks Leo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
Oh yes, changing that value in failsafe.conf brings back the old boot times: tried setting to 12 and then 1, and it definitely fixed things: ( I added the //comments ) Wed Sep 7 17:13:34 PDT 2011. Boot Time [s]: 156 // Sleep 120 Wed Sep 7 18:59:59 PDT 2011. Boot Time [s]: 51 // Sleep 12 Wed Sep 7 19:04:28 PDT 2011. Boot Time [s]: 48 // Sleep 12 Wed Sep 7 19:10:36 PDT 2011. Boot Time [s]: 37 // Sleep 1 This is how it looks now: # santisofi@minime:~$ cat /etc/init/failsafe.conf # failsafe description Failsafe Boot Delay author Clint Byrum cl...@ubuntu.com start on filesystem and net-device-up IFACE=lo stop on runlevel pre-start exec sleep 1 # So, it looks like, around Sept 3, something changed with an update, and I started going to sleep for 30 secs (so boot times went around 30 sec longer). Then, this recent change to 120 added extra 90 secs. I looked around in dmesg and didn't find anything obvious. I will attach it shortly, regardless. Thanks! Leo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
** Attachment added: dmesg for a boot with sleep = 1 https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595/+attachment/2370271/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 839595] Re: failsafe.conf's 30 second time out is too low
One more thought, just by looking at the script and the behaviour on my system. The bug description states as far as I can understand, the 30 second sleep in failsafe.conf means that /etc/init/rc-sysinit.conf will start within AT MOST 30 seconds of 'filesystem' and 'ifup lo' having occurred. It seems to me that the sleep statement means that the bootup will take AT LEAST 30 seconds, and a 120 sleep statement will ensure at least 120 seconds to boot up. I am not an expert, so sorry if this silly, but isn't upstart all about dependency based start up? It seems as if using sleep statements defeats the whole purpose of the system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/839595 Title: failsafe.conf's 30 second time out is too low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/839595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496435] Re: upgrades of the grub-pc package can overwrite wrong MBR
Colin: do my logs shed any light? Let me point out that updates to grub during the life of the distro did not ruin the MBR. It has only (and consistently) happened when upgrading to a newer distro version. With that in mind. Why don't we ask the user for confirmation before writing to the MBR? Would that be feasible? It seems to me like such a critical step would merit an extra click Thanks Leo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/496435 Title: upgrades of the grub-pc package can overwrite wrong MBR -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496435] Re: upgrades of the grub-pc package can overwrite wrong MBR
Hi Colin, I am attaching the required info. Apparently I can only add one at a time. Thank you so much for looking into this. Cheers! Leo ** Attachment added: sudo debconf-show grub-pc grub-pc.txt https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110796/+files/grub-pc.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/496435 Title: upgrades of the grub-pc package can overwrite wrong MBR -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496435] Re: upgrades of the grub-pc package can overwrite wrong MBR
** Attachment added: sudo cat /var/log/installer/partman partman.txt https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110797/+files/partman.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/496435 Title: upgrades of the grub-pc package can overwrite wrong MBR -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496435] Re: upgrades of the grub-pc package can overwrite wrong MBR
** Attachment added: sudo cat /var/log/installer/syslog syslog.txt https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110798/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/496435 Title: upgrades of the grub-pc package can overwrite wrong MBR -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496435] Re: upgrades of the grub-pc package can overwrite wrong MBR
** Attachment added: df -h df-h.txt https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110800/+files/df-h.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/496435 Title: upgrades of the grub-pc package can overwrite wrong MBR -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496435] Re: upgrades of the grub-pc package can overwrite wrong MBR
** Attachment added: sudo blkid blkid.txt https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+attachment/2110801/+files/blkid.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/496435 Title: upgrades of the grub-pc package can overwrite wrong MBR -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496435] Re: upgrades of the grub-pc package can overwrite wrong MBR
Ok, I added all the info, I hope it helps. I took the liberty to add a couple more useful outputs. My computer boots from /dev/sdb , but I always keep a grub in /dev/sda just in case. Both of them failed to load grub after the upgrade (I only run grub-install /dev/sda every once in a while, I only do it since I started hitting this bug). I have been running Kubuntu for ... 2 years now on this computer? So there are several layers of upgrades, and there is certainly the possibility that an old setting is bothering things, as Colin stated. @ Frank: I showed the commands I ran on the command line to generate teh attachments, in case it helps. @seasoned_geek: please note that this is not a forum where users exchange _opinions_, but rather a bug tracker. Even when you are trying to help, you are introducing noise, which actually hurts the chances of getting things fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/496435 Title: upgrades of the grub-pc package can overwrite wrong MBR -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496435] Re: upgrades of the grub-pc package can overwrite wrong MBR
I noticed a reference to a third partition in the grub-pc output: grub-pc/install_devices: /dev/disk/by-id/ata-WDC_WD1001FALS-00J7B1_WD- WMATV1484210-part3 Does this mean that the upgrade is trying to install grub on a partition instead of the MBR? But, assuming that's the case, why does the old grub in the MBR stop working? (I have an older version of Kubuntu in another partition, and grub doesn't even show me that) Oh well, I hope I gave enough info to shed some light. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/496435 Title: upgrades of the grub-pc package can overwrite wrong MBR -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 496435] Re: upgrades of the grub-pc package can overwrite wrong MBR
Same here. My desktop system with 2 sata hard drives just rendered itself unbootable after upgrading Kubuntu 10.10 - 11.04 As far as I can tell, Fix Released is not a proper characterization for this bug's status, and this is a CRITICAL bug. I really don't mean to flame, but we can't afford having people click on the A new distribution version is available button, only to get a black screen after booting, not to mention losing access to poprietary operating systems already installed Cheers! Leo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/496435 Title: upgrades of the grub-pc package can overwrite wrong MBR -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 646862] Re: skype crashes after signing in
Hi Jacob, All, I restored (+r) to both binaries and Skype is still working fine. It really seems to have been a regression introduced by ia32-libs (and now fixed). Good work everyone! -- skype crashes after signing in https://bugs.launchpad.net/bugs/646862 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 646862] Re: skype crashes after signing in
Here the workaround was enough to let me start skype but I had no audio (mic/speakers) in skype. The new ia32libs restored audio, good enough to complete a call (however I never undid the workaround, that is I didn't restore the original file permissions) -- skype crashes after signing in https://bugs.launchpad.net/bugs/646862 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 641297] Re: kded crashes at login
I had the same crash, Kubuntu 64 bit, after upgrading from 10.04 to 10.10 beta. Removing all the obex related packages did the trick, many thanks to Erdewit. This is a really problematic bug. It would prevent networkmanagement from working at all (the computer would not connect to the wireless AP). After removing the bluetooth packages everything went back to normal. Is this a packaging issue? -- kded crashes at login https://bugs.launchpad.net/bugs/641297 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 496435] Re: upgrades of the grub-pc package can overwrite wrong MBR
Same here, it hit me when upgrading from Kubuntu 10.04 to 10.10beta, on an amd64 system with multiple sata drives. I had to boot from the live image and chroot. Shouldn't that part of a grub/system upgrade ask for user input, since this is SO critical? This is a killer for non-experts! -- upgrades of the grub-pc package can overwrite wrong MBR https://bugs.launchpad.net/bugs/496435 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 609280] Re: Grub error : symbol grub_xputs not found
*** This bug is a duplicate of bug 496435 *** https://bugs.launchpad.net/bugs/496435 Hi This is a duplicate of bug # 496435 https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435 Cheers Leo ** This bug has been marked a duplicate of bug 496435 upgrades of the grub-pc package can overwrite wrong MBR * You can subscribe to bug 496435 by following this link: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/496435/+subscribe -- Grub error : symbol grub_xputs not found https://bugs.launchpad.net/bugs/609280 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 546578] Re: [RS480] black screen after a few user switches
Here is something encouraging. This morning (May 9) I tried the xorg-edgers ppa again, and now the crash on logout is gone. No workarounds, no mess. This is, again, in Kubuntu/KDM. If anyone wants to try, here are the instructions. From the command line: To install: sudo add-apt-repository ppa:xorg-edgers/ppa Then refresh your packages and upgrade. To uninstall: sudo ppa-purge xorg-edgers For more, please see here: https://launchpad.net/~xorg-edgers/+archive/ppa I had tried this before with no luck. If we can confirm that this has been fixed upstream, then there is hope we can get a fix backported. -- [RS480] black screen after a few user switches https://bugs.launchpad.net/bugs/546578 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 539708] Re: /usr/lib/cups/filter/pdftoraster failed
Hi all I just tested the hpcups driver from the proposed repository in my system (Kubuntu Lucid, HP Deskjet F380), and the bug is fixed. I no longer get the black background. Great work everyone involved! Cheers, -- Leo -- /usr/lib/cups/filter/pdftoraster failed https://bugs.launchpad.net/bugs/539708 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 553573] Re: Printing on hp printer has black background
Hi Till I just tested the hpcups driver from the proposed repository in my system (Kubuntu Lucid, HP Deskjet F380), and the bug is fixed. I no longer get the black background. I will also post the good news in bug 539708. Great work everyone involved! Cheers, -- Leo -- Printing on hp printer has black background https://bugs.launchpad.net/bugs/553573 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 553573] Re: Printing on hp printer has black background
** Attachment added: Screenshot of my printer config http://launchpadlibrarian.net/47699568/printer-hpcups.png -- Printing on hp printer has black background https://bugs.launchpad.net/bugs/553573 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 546578] Re: [RS480] black screen after a few user switches
With my hardware (ATI HD 3500), I get the black screen in Kubuntu with the open source stack (radeon, etc). If I enable fglrx in the Hardware Drivers section, the issue is gone. The latest packages from the xorg- edgers ppa also produce the crash. -- [RS480] black screen after a few user switches https://bugs.launchpad.net/bugs/546578 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 529882] Re: black screen when switching between multiple X session
Same behavior here, ATI open source driver, current Lucid, but this is with KDM and Kubuntu. I'll probably try with a more current mainline kernel. -- black screen when switching between multiple X session https://bugs.launchpad.net/bugs/529882 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 464712] Re: Black screen + freeze when suspending or hibernating with mounted SD Card
Just to confirm, this is still happening in Lucid, Dell Mini 9 (Vostro A90). -- Black screen + freeze when suspending or hibernating with mounted SD Card https://bugs.launchpad.net/bugs/464712 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 535108] Re: Hide console messages while Plymouth is running
Same here, I needed the FRAMEBUFFER=y workaround. Not that kubuntu-desktop _is_ installed here, but cryptsetup is not. Meaning: if you don't know about the workaround, you won't get the splash screen. Is this a packaging issue? Thanks! -- Hide console messages while Plymouth is running https://bugs.launchpad.net/bugs/535108 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 538031] Re: hp printer prints totally wrong - non-text lines are black rather than white
I just printed an email from gmail, using Chrome, and I got a full page in black. Solid black. This is using an HP F380 AIO. I tried again from Adobe (a previously saved PDF), same problem. This is in Lucid. The same printer works fine in Karmic. -- hp printer prints totally wrong - non-text lines are black rather than white https://bugs.launchpad.net/bugs/538031 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 538031] Re: hp printer prints totally wrong - non-text lines are black rather than white
Ouch. Too bad. I was going to ask what driver you were using :-). My machine was using hpijs in karmic, and when I upgraded to Lucid it was picked up as hpcups, which was not working fine. From the KDE System Settings I reconfigured the printer to use hpijs (instead of the _recommended_ hpcups), and everything is fine. Is this the default really? To use hpcups? Here, at least, it prints a full black block, which would empty an inkjet cartridge in just about a few pages (if the user doesn't realize). And those are expensive! -- hp printer prints totally wrong - non-text lines are black rather than white https://bugs.launchpad.net/bugs/538031 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 538524] Re: boot hangs on splash screen, doesn't switch to KDM
I can confirm the fix here, too (Radeon HD3450, Kubuntu Lucid, KMS). Great work! I'll follow up in the smooth transition bug 540177 -- boot hangs on splash screen, doesn't switch to KDM https://bugs.launchpad.net/bugs/538524 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 540177] Re: KDM needs plymouth transition patch
I'll provide feedbback for this, I am running Kubuntu Lucid + KMS with a Radeon HD3450. Right now, plymouth shows perfectly at shutdown. On boot up, though, it only pops up _very_ late (about a second before KDM loads), and it's only displayed for a fraction of a second. Cheers! -- KDM needs plymouth transition patch https://bugs.launchpad.net/bugs/540177 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 353278] Re: [jaunty] kpackagekit doesn't prompt for user password
@nerdy_kid: I believe this bug HAS been fixed, and I marked it as such above. However, Lynx marked this as NEW again, and undid this. I think the confusion has to do with what this bug is about, although it was explained above by Jonathan in post #64. We need a new bug report for the missing policykit-kde, and close this one. If anyone has the time please go ahead and link from here (I'll do the same if I get a little time to do it) -- [jaunty] kpackagekit doesn't prompt for user password https://bugs.launchpad.net/bugs/353278 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 527083] Re: plymouth broken on radeon 7500
I am not sure if I am in the right bug report, I found several similar reports when trying to file a gub with ubuntu-bug. I have an R600 card (Radeon HD3450). KMS has been working fine in Lucid, but the latest update to plymouth killed it (boot up hangs at the plymouth screen). This is Kubuntu lucid: l...@grisell:~$ dpkg -l |grep plym ii libplymouth2 0.8.0~-14 graphical boot animation and logger - shared librar ii plymouth 0.8.0~-14 graphical boot animation and logger - main package ii plymouth-x11 0.8.0~-14 graphical boot animation and logger - X11 interface Disabling KMS (in grub) works fine with plymouth, and so does of course removing the splash boot option. I can provide any extra information as needed. Best of all Leo -- plymouth broken on radeon 7500 https://bugs.launchpad.net/bugs/527083 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 527083] Re: plymouth broken on radeon 7500
Thanks Scott, and sorry for the misreport. -- plymouth broken on radeon 7500 https://bugs.launchpad.net/bugs/527083 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 538097] Re: Apport cannot connect to crash database
Same here, I am trying to report a critical bung in plymouth. This is the console output: l...@grisell:~$ apport-bug plymouth QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /home/leo/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon -- Apport cannot connect to crash database https://bugs.launchpad.net/bugs/538097 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 353278] Re: [jaunty] kpackagekit doesn't prompt for user password
Wow! I am running latest Lucid and I just realized that policykit-kde is not available for Lucid, either! This is the behavior: * policykit-1-gnome is installed * If I open KPackageKit and select updates, I can install them with NO authentication! (Is this expected?) * If I install new packages I do get a prompt (I guess the gnome version), which actually asks me what user to use for sudo'ing (that's nice). Should we file a packaging bug for the missing policykit-kde? -- [jaunty] kpackagekit doesn't prompt for user password https://bugs.launchpad.net/bugs/353278 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to policykit-kde in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 418246] Re: it87 (sensors) module broken, needs automatic adding of a kernel line during installation
Has anyone tried in Lucid? The worlaround (acpi_enforce_resources=lax) works here in Karmic, but it doesn't in current Lucid. l...@grisell:~$ dmesg |grep lax [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-15-server root=UUID=e1c15c83-23cf-4bfb-a043-ba9469332293 ro quiet splash acpi_enforce_resource=lax l...@grisell:~$ sudo lshw |grep -i a7 product: A7GM-S 2.0 l...@grisell:~$ sudo modprobe it87 FATAL: Error inserting it87 (/lib/modules/2.6.32-15-server/kernel/drivers/hwmon/it87.ko): Device or resource busy -- it87 (sensors) module broken, needs automatic adding of a kernel line during installation https://bugs.launchpad.net/bugs/418246 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 418246] Re: it87 (sensors) module broken, needs automatic adding of a kernel line during installation
Ouch! Thanks Hernando!!! Yes, I can confirm that the workaround still works (and it's still needed, unfortunately) -- it87 (sensors) module broken, needs automatic adding of a kernel line during installation https://bugs.launchpad.net/bugs/418246 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 527482] Re: unable to make /etc/lxdm/default.conf.dpkg-tmp a symlink to /etc/alternatives/lxdm.conf
I just tested in latest Lucid, same issue. Is this a local problem in my computer or a packaging issue? I don't really use Lubuntu, but I am trying to help because I came across this bug and it seems like a biggie. -- unable to make /etc/lxdm/default.conf.dpkg-tmp a symlink to /etc/alternatives/lxdm.conf https://bugs.launchpad.net/bugs/527482 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 527482] Re: unable to make /etc/lxdm/default.conf.dpkg-tmp a symlink to /etc/alternatives/lxdm.conf
Hi Julien, Yes, that certainly works, the install script is missing the check for /etc/lxdm l...@grisell:~$ sudo mkdir /etc/lxdm [sudo] password for leo: l...@grisell:~$ sudo apt-get install lubuntu-default-settings Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: lubuntu-default-settings 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0B/11.4kB of archives. After this operation, 238kB of additional disk space will be used. Selecting previously deselected package lubuntu-default-settings. (Reading database ... 210713 files and directories currently installed.) Unpacking lubuntu-default-settings (from .../lubuntu-default-settings_0.5_all.deb) ... Processing triggers for desktop-file-utils ... Setting up lubuntu-default-settings (0.5) ... update-alternatives: using /etc/xdg/lubuntu/lxdm/lxdm.conf to provide /etc/lxdm/default.conf (lxdm.conf) in auto mode. -- unable to make /etc/lxdm/default.conf.dpkg-tmp a symlink to /etc/alternatives/lxdm.conf https://bugs.launchpad.net/bugs/527482 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 527482] [NEW] unable to make /etc/lxdm/default.conf.dpkg-tmp a symlink to /etc/alternatives/lxdm.conf
Public bug reported: Binary package hint: lubuntu-default-settings In the latest upgrade of lubuntu-default-settings for Lucid (version 0.5), I got the error described in the bug report summary. Uninstalling and re-installing didn't help. It seems to be a missing target for a symlink. Here is a log of an installation after removal: l...@grisell:~$ sudo apt-get install lubuntu-default-settings Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libqscintilla2-5 libwebkit-1.0-common libpolkit-qt0 libqtscript4-network vcdimager libsmokeqt4-3 libqtscript4-gui libtag-extras1 libqtscript4-sql devicekit-disks libqtscript4-xml gnome-brave-icon-theme libindicate3 ruby1.8 libsmokekde4-3 ruby amarok-utils libqtruby4shared2 gnome-colors-common libkde4-ruby1.8 libqt4-ruby1.8 libwebkit-1.0-2 libkde4-ruby libqtscript4-uitools libruby1.8 liblastfm0 libqtscript4-core libsmokesoprano3 Use 'apt-get autoremove' to remove them. The following NEW packages will be installed: lubuntu-default-settings 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 11.4kB of archives. After this operation, 238kB of additional disk space will be used. Get:1 http://us.archive.ubuntu.com lucid/universe lubuntu-default-settings 0.5 [11.4kB] Fetched 11.4kB in 0s (12.7kB/s) Selecting previously deselected package lubuntu-default-settings. (Reading database ... 253554 files and directories currently installed.) Unpacking lubuntu-default-settings (from .../lubuntu-default-settings_0.5_all.deb) ... Processing triggers for desktop-file-utils ... Setting up lubuntu-default-settings (0.5) ... update-alternatives: using /etc/xdg/lubuntu/lxdm/lxdm.conf to provide /etc/lxdm/default.conf (lxdm.conf) in auto mode. update-alternatives: error: unable to make /etc/lxdm/default.conf.dpkg-tmp a symlink to /etc/alternatives/lxdm.conf: No such file or directory dpkg: error processing lubuntu-default-settings (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: lubuntu-default-settings E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug Architecture: amd64 Date: Wed Feb 24 19:14:04 2010 DistroRelease: Ubuntu 10.04 Package: lubuntu-default-settings 0.5 PackageArchitecture: all ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-14.20-server SourcePackage: lubuntu-default-settings Uname: Linux 2.6.32-14-server x86_64 ** Affects: lubuntu-default-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- unable to make /etc/lxdm/default.conf.dpkg-tmp a symlink to /etc/alternatives/lxdm.conf https://bugs.launchpad.net/bugs/527482 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
