[Desktop-packages] [Bug 1396226] [NEW] nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build
Public bug reported: Nvidia kernel module failed to build when updating to the 3.16.0-25-generic kernel. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Tue Nov 25 17:53:04 2014 InstallationDate: Installed on 2014-11-02 (23 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1396226 Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: Nvidia kernel module failed to build when updating to the 3.16.0-25-generic kernel. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Tue Nov 25 17:53:04 2014 InstallationDate: Installed on 2014-11-02 (23 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1396226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1348193] [NEW] Duplicity fails during backup in with_tempdir()
Public bug reported: Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 duplicity: Installed: 0.6.23-1ubuntu5 Candidate: 0.6.23-1ubuntu5 Version table: *** 0.6.23-1ubuntu5 0 500 http://au.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status During a full system backup, using the deja-dup, the process gets about half-way through and then stops with the following error: Backup Failed Failed with an unknown error. Traceback (most recent call last): File "/usr/bin/duplicity", line 1494, in with_tempdir(main) File "/usr/bin/duplicity", line 1488, in with_tempdir fn() File "/usr/bin/duplicity", line 1337, in main do_backup(action) File "/usr/bin/duplicity", line 1458, in do_backup full_backup(col_stats) File "/usr/bin/duplicity", line 542, in full_backup globals.backend) File "/usr/bin/duplicity", line 403, in write_multivol globals.gpg_profile, globals.volsize) File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 324, in GPGWriteFile file = GPGFile(True, path.Path(filename), profile) File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 105, in __init__ self.logger_fp = tempfile.TemporaryFile( dir=tempdir.default().dir() ) File "/usr/lib/python2.7/tempfile.py", line 497, in TemporaryFile (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags) File "/usr/lib/python2.7/tempfile.py", line 239, in _mkstemp_inner fd = _os.open(file, flags, 0600) OSError: [Errno 2] No such file or directory: '/tmp/duplicity-DEgmK7-tempdir/tmplcuF1s' The referred to directory does not exist, however, the following one does exist: /tmp/duplicity-l4bYos-tempdir/ ** Affects: duplicity (Ubuntu) Importance: Undecided Status: New ** Description changed: Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 duplicity: - Installed: 0.6.23-1ubuntu5 - Candidate: 0.6.23-1ubuntu5 - Version table: - *** 0.6.23-1ubuntu5 0 - 500 http://au.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 0.6.23-1ubuntu5 + Candidate: 0.6.23-1ubuntu5 + Version table: + *** 0.6.23-1ubuntu5 0 + 500 http://au.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages + 100 /var/lib/dpkg/status - During a full system backup, using the backup tool, the process gets about half-way through and then stops with the following error: + During a full system backup, using the deja-dup, the process gets about half-way through and then stops with the following error: Backup Failed Failed with an unknown error. Traceback (most recent call last): - File "/usr/bin/duplicity", line 1494, in - with_tempdir(main) - File "/usr/bin/duplicity", line 1488, in with_tempdir - fn() - File "/usr/bin/duplicity", line 1337, in main - do_backup(action) - File "/usr/bin/duplicity", line 1458, in do_backup - full_backup(col_stats) - File "/usr/bin/duplicity", line 542, in full_backup - globals.backend) - File "/usr/bin/duplicity", line 403, in write_multivol - globals.gpg_profile, globals.volsize) - File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 324, in GPGWriteFile - file = GPGFile(True, path.Path(filename), profile) - File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 105, in __init__ - self.logger_fp = tempfile.TemporaryFile( dir=tempdir.default().dir() ) - File "/usr/lib/python2.7/tempfile.py", line 497, in TemporaryFile - (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags) - File "/usr/lib/python2.7/tempfile.py", line 239, in _mkstemp_inner - fd = _os.open(file, flags, 0600) + File "/usr/bin/duplicity", line 1494, in + with_tempdir(main) + File "/usr/bin/duplicity", line 1488, in with_tempdir + fn() + File "/usr/bin/duplicity", line 1337, in main + do_backup(action) + File "/usr/bin/duplicity", line 1458, in do_backup + full_backup(col_stats) + File "/usr/bin/duplicity", line 542, in full_backup + globals.backend) + File "/usr/bin/duplicity", line 403, in write_multivol + globals.gpg_profile, globals.volsize) + File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 324, in GPGWriteFile + file = GPGFile(True, path.Path(filename), profile) + File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 105, in __init__ + self.logger_fp = tempfile.TemporaryFile( dir=tempdir.default().dir() ) + File "/usr/lib/python2.7/tempfile.py", line 497, in TemporaryFile + (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags) + File "/usr/lib/python2.7/tempfile.py", line 239, in _mkstemp_inner + fd = _os.open(file, flags, 0600) OSError: [Errno 2] No such file or directory: '/tmp/duplicity-DEgmK7-tempdir/tmplcuF1s' - The referred to directory does not exist, however, the following one does exist: /tmp/duplicity-l4bYos-tempdir
[Desktop-packages] [Bug 1184262] Re: network-manager has decided that networking is disabled, cannot be re-enabled from lightdm
A work around that works for me is killing the NetworkManager process using "sudo killall NetworkManager". The daemon re-starts and the network is restored. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: network-manager has decided that networking is disabled, cannot be re- enabled from lightdm Status in “network-manager” package in Ubuntu: Confirmed Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 959068] Re: unity-gwibber-daemon crashed with SIGABRT in g_assertion_message()
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/959068 Title: unity-gwibber-daemon crashed with SIGABRT in g_assertion_message() Status in “gwibber” package in Ubuntu: New Bug description: This crash occurred when logging into the unity desktop session. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-lens-gwibber 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 19 17:52:18 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gwibber/unity-gwibber-daemon InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcCmdline: /usr/lib/gwibber/unity-gwibber-daemon ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANGUAGE=en_AU:en LANG=en_AU.UTF-8 Signal: 6 SourcePackage: gwibber StacktraceTop: g_assertion_message (domain=, file=, line=, func=0x7ff9ebb43aa0 "gee_hash_map_node_iterator_next", message=0x30a1630 "assertion failed: (_tmp0_ == _tmp2_)") at /build/buildd/glib2.0-2.31.20/./glib/gtestutils.c:1860 g_assertion_message_expr (domain=0x0, file=0x7ff9ebb43449 "hashmap.c", line=2621, func=0x7ff9ebb43aa0 "gee_hash_map_node_iterator_next", expr=) at /build/buildd/glib2.0-2.31.20/./glib/gtestutils.c:1871 ?? () from /usr/lib/x86_64-linux-gnu/libgee.so.2 ?? () from /usr/lib/libgwibber.so.2 g_closure_invoke (closure=0x21afc20, return_value=0x0, n_param_values=2, param_values=0x2ad4400, invocation_hint=) at /build/buildd/glib2.0-2.31.20/./gobject/gclosure.c:777 Title: unity-gwibber-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to precise on 2012-01-15 (64 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/959068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 795475] Re: [iOS5 devices do not work] Unhandled lockdown error (-4)
@Richard and Andrew - bug 877440 has been opened for the "Unhandled Lockdown error (-15)" issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/795475 Title: [iOS5 devices do not work] Unhandled lockdown error (-4) Status in “libimobiledevice” package in Ubuntu: Fix Released Status in “libimobiledevice” source package in Lucid: Fix Committed Status in “libimobiledevice” source package in Maverick: Confirmed Status in “libimobiledevice” source package in Natty: Fix Released Status in “libimobiledevice” source package in Oneiric: Fix Released Status in “libimobiledevice” source package in Precise: Fix Released Bug description: Binary package hint: nautilus TEST CASE: 1. attach an iphone with iOS5 2. see you get the error on mount "Unhandled lockdown error (-4)" 3. now install libimobiledevice from natty-proposed 4. see the iphone successfully makes a USB connection. ==Original Report== Plugged an iphone 4 running beta of iOS 5 into my Ubuntu Natty desktop and got a dialog:- "Unable to mount Alan Pope's iPhone" "Unhandled lockdown error (-4)" ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Jun 10 11:49:15 2011 ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/795475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 795475] Re: [iOS5 devices do not work] Unhandled lockdown error (-4)
Alan, I cannot access bug 870592 - I keep getting a message saying that the bug cannot be found. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/795475 Title: [iOS5 devices do not work] Unhandled lockdown error (-4) Status in “libimobiledevice” package in Ubuntu: Fix Committed Status in “libimobiledevice” source package in Lucid: Fix Committed Status in “libimobiledevice” source package in Maverick: Confirmed Status in “libimobiledevice” source package in Natty: Fix Committed Status in “libimobiledevice” source package in Oneiric: Fix Committed Status in “libimobiledevice” source package in Precise: Fix Committed Bug description: Binary package hint: nautilus TEST CASE: 1. attach an iphone with iOS5 2. see you get the error on mount "Unhandled lockdown error (-4)" 3. now install libimobiledevice from natty-proposed 4. see the iphone successfully makes a USB connection. ==Original Report== Plugged an iphone 4 running beta of iOS 5 into my Ubuntu Natty desktop and got a dialog:- "Unable to mount Alan Pope's iPhone" "Unhandled lockdown error (-4)" ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Jun 10 11:49:15 2011 ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/795475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 795475] Re: [iOS5 devices do not work] Unhandled lockdown error (-4)
Herewith further info from the syslog: Oct 13 22:24:00 localhost kernel: [ 1445.565743] ADDRCONF(NETDEV_UP): eth1: link is not ready Oct 13 22:24:01 localhost kernel: [ 1447.161868] show_signal_msg: 18 callbacks suppressed Oct 13 22:24:01 localhost kernel: [ 1447.161881] iphone-set-info[4033]: segfault at 8 ip 003a7706 sp bf8ee984 error 4 in libc-2.13.so[32d000+15a000] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/795475 Title: [iOS5 devices do not work] Unhandled lockdown error (-4) Status in “libimobiledevice” package in Ubuntu: Fix Committed Status in “libimobiledevice” source package in Lucid: Fix Committed Status in “libimobiledevice” source package in Maverick: Confirmed Status in “libimobiledevice” source package in Natty: Fix Committed Status in “libimobiledevice” source package in Oneiric: Fix Committed Status in “libimobiledevice” source package in Precise: Fix Committed Bug description: Binary package hint: nautilus TEST CASE: 1. attach an iphone with iOS5 2. see you get the error on mount "Unhandled lockdown error (-4)" 3. now install libimobiledevice from natty-proposed 4. see the iphone successfully makes a USB connection. ==Original Report== Plugged an iphone 4 running beta of iOS 5 into my Ubuntu Natty desktop and got a dialog:- "Unable to mount Alan Pope's iPhone" "Unhandled lockdown error (-4)" ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Jun 10 11:49:15 2011 ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/795475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 795475] Re: [iOS5 devices do not work] Unhandled lockdown error (-4)
I have just installed libimobiledevice 1.1.0-3ubuntu1 from natty- proposed, and I am still getting the "Unhandled lockdown error" message. I have tested this after rebooting, and I have upgraded my iphone to iOS 5 released yesterday. I suggest that verification gets done on the actual iOS release, instead of the iOS 5 GM release. ** Tags removed: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/795475 Title: [iOS5 devices do not work] Unhandled lockdown error (-4) Status in “libimobiledevice” package in Ubuntu: Fix Committed Status in “libimobiledevice” source package in Lucid: Fix Committed Status in “libimobiledevice” source package in Maverick: Confirmed Status in “libimobiledevice” source package in Natty: Fix Committed Status in “libimobiledevice” source package in Oneiric: Fix Committed Status in “libimobiledevice” source package in Precise: Fix Committed Bug description: Binary package hint: nautilus TEST CASE: 1. attach an iphone with iOS5 2. see you get the error on mount "Unhandled lockdown error (-4)" 3. now install libimobiledevice from natty-proposed 4. see the iphone successfully makes a USB connection. ==Original Report== Plugged an iphone 4 running beta of iOS 5 into my Ubuntu Natty desktop and got a dialog:- "Unable to mount Alan Pope's iPhone" "Unhandled lockdown error (-4)" ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nautilus 1:2.32.2.1-0ubuntu13 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Jun 10 11:49:15 2011 ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/795475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
