[Desktop-packages] [Bug 1314556] Re: Unable to mount Android MTP device
I'm now on Kubuntu 15.04, and the problem still exist. In my case turning on USB debug in advanced options helped... but it shouldn't be that way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1314556 Title: Unable to mount Android MTP device Status in gvfs package in Ubuntu: Confirmed Bug description: I have the same problem on 3 computers with 14.04: So I tried, mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): Resource temporarily unavailable outep: usb_get_endpoint_status(): Device or resource busy ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs-backends 1.20.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 30 11:18:12 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor InstallationDate: Installed on 2013-02-12 (441 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gvfs UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+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 1289047] Re: [Trusty] hostapd package is broken
Is there any mode to disable upgrading this package from 13.10 (which works for me too)? I mean when i use sudo apt-get upgrade it upgrades this package to 1:2.1 version, which doesn't work (surely bugged). I get the same result on new version from hostapd: nl80211: Could not configure driver mode nl80211 driver initialization failed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1289047 Title: [Trusty] hostapd package is broken Status in “wpa” package in Ubuntu: Confirmed Bug description: When trying to create an access point, I am met with a fatal error with hostapd: nl80211: Could not configure driver mode nl80211 driver initialization failed. hostapd_free_hapd_data: Interface wlan0 wasn't started What worked before no longer works today after a package upgrade. After installing hostapd deb from Ubuntu 13.10, it works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hostapd 1:2.1-0ubuntu1 Uname: Linux 3.14.0-031400rc5-lowlatency x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Thu Mar 6 16:57:20 2014 InstallationDate: Installed on 2014-02-01 (33 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 LANGUAGE=en_CA:en SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1289047/+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 1289047] Re: [Trusty] hostapd package is broken
Ok, I've found it. If anyone need stop upgrading by apt, you must use sudo apt-mark hold hostapd. ( For other update managers etc, see here: http://askubuntu.com/questions/18654/how-to-prevent-updating-of-a -specific-package ) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1289047 Title: [Trusty] hostapd package is broken Status in “wpa” package in Ubuntu: Confirmed Bug description: When trying to create an access point, I am met with a fatal error with hostapd: nl80211: Could not configure driver mode nl80211 driver initialization failed. hostapd_free_hapd_data: Interface wlan0 wasn't started What worked before no longer works today after a package upgrade. After installing hostapd deb from Ubuntu 13.10, it works. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hostapd 1:2.1-0ubuntu1 Uname: Linux 3.14.0-031400rc5-lowlatency x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Thu Mar 6 16:57:20 2014 InstallationDate: Installed on 2014-02-01 (33 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140121.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 LANGUAGE=en_CA:en SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1289047/+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 833849] Re: cheese crashed with SIGSEGV in g_slice_alloc()
It affects also me on Ubuntu 13.10. I think it may be connected with x64 build, because I also use amd64 version of Ubuntu. In my case crash appear not on start, but after random time of using application. I haven't found any reason or reproduce, just random time of using app. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/833849 Title: cheese crashed with SIGSEGV in g_slice_alloc() Status in “cheese” package in Ubuntu: Confirmed Bug description: cheese crashes on start. lsb_release -rd Description: Ubuntu oneiric (development branch) Release: 11.10 apt-cache policy cheese cheese: Installed: 3.0.1-2ubuntu2 Candidate: 3.0.1-2ubuntu2 Version table: *** 3.0.1-2ubuntu2 0 500 http://in.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: cheese 3.0.1-2ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CrashCounter: 1 Date: Thu Aug 25 20:58:33 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/cheese InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) MachineType: Dell Inc. Dell System XPS L702X ProcCmdline: cheese RelatedPackageVersions: cheese3.0.1-2ubuntu2 cheese-common 3.0.1-2ubuntu2 SegvAnalysis: Segfault happened at: 0x7f28255c9598 g_slice_alloc+280:mov 0x8(%rax),%rbx PC (0x7f28255c9598) ok source 0x8(%rax) (0x10007) not located in a known VMA region (needed readable region)! destination %rbx ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: cheese StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_new_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: cheese crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: Upgraded to oneiric on 2011-08-23 (1 days ago) UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare video dmi.bios.date: 06/01/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 0XN71K dmi.board.vendor: Dell Inc. dmi.board.version: FAB1 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd06/01/2011:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L702X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/833849/+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 1236774] [NEW] gnome-settings-daemon crashed with signal 5
Public bug reported: Just installed latest update of gnome-settings-daemon and restarted my computer. After logging in window appeared with this bug. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Oct 8 11:57:32 2013 Disassembly: = 0x7f4034d313c9: Cannot access memory at address 0x7f4034d313c9 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationDate: Installed on 2013-09-05 (32 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130905) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () ?? () ?? () ?? () Title: gnome-settings-daemon crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1236774 Title: gnome-settings-daemon crashed with signal 5 Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: Just installed latest update of gnome-settings-daemon and restarted my computer. After logging in window appeared with this bug. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Tue Oct 8 11:57:32 2013 Disassembly: = 0x7f4034d313c9: Cannot access memory at address 0x7f4034d313c9 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationDate: Installed on 2013-09-05 (32 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130905) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () ?? () ?? () ?? () Title: gnome-settings-daemon crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1236774/+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 1235851] Re: gnome-settings-daemon crashed with signal 5
** Information type changed from Private to Public ** Description changed: - I think it's somehow connected with Nvidia drivers. I have optimus + This bug appears every time i reboot my computer. + + I think may be somehow connected with Nvidia drivers. I have optimus technology on notebook and used newest Nvidia drivers from official Ubuntu repositories. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Oct 6 06:04:56 2013 Disassembly: = 0x7f2d2a8a33c9: Cannot access memory at address 0x7f2d2a8a33c9 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationDate: Installed on 2013-09-05 (30 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130905) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: - PATH=(custom, no user) - LANGUAGE=pl - XDG_RUNTIME_DIR=set - LANG=pl_PL.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + LANGUAGE=pl + XDG_RUNTIME_DIR=set + LANG=pl_PL.UTF-8 + SHELL=/bin/bash Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: - ?? () - ?? () - ?? () - ?? () + ?? () + ?? () + ?? () + ?? () Title: gnome-settings-daemon crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1235851 Title: gnome-settings-daemon crashed with signal 5 Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: This bug appears every time i reboot my computer. I think may be somehow connected with Nvidia drivers. I have optimus technology on notebook and used newest Nvidia drivers from official Ubuntu repositories. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Sun Oct 6 06:04:56 2013 Disassembly: = 0x7f2d2a8a33c9: Cannot access memory at address 0x7f2d2a8a33c9 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationDate: Installed on 2013-09-05 (30 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130905) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, no user) LANGUAGE=pl XDG_RUNTIME_DIR=set LANG=pl_PL.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () ?? () ?? () ?? () Title: gnome-settings-daemon crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1235851/+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
