[Bug 882214] Re: Evolution throws up various GConf error dialogs
I can confirm getting the same errors. In my case there was no sleep involved, these errors occurred after having let evolution sit idling for a few hours. Once one error dialogue appeared it seems like that more appear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882214 Title: Evolution throws up various GConf error dialogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/882214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776487] [NEW] too difficult to select scroll bar handle
Public bug reported: Binary package hint: overlay-scrollbar For some reason scrolling is much more difficult with the new overlay scrollbars. This is what I do: - hover over the scrollbar that opens the scrollbar handle - click drag, usually doing something I don't want, for instance in evolution starts a drag operation on a folder or something - realize that in order to scroll I need to first hover over the scroll bar then move the mouse to the left Now I realize that I'm probably not familiar yet with the user interface but something like scrolling shouldn't be something you have to re-train yourself to do. Perhaps a clickdrag on the scrollbar area should scroll the page as if the mouse is directly over the handle, this would solve the problem for me. ** Affects: overlay-scrollbar (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/776487 Title: too difficult to select scroll bar handle -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776487] Re: too difficult to select scroll bar handle
I meant right instead of left oops -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776487 Title: too difficult to select scroll bar handle -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776487] Re: too difficult to select scroll bar handle
Also I just realized that you have to hover over the orange part of the scrollbar, and this sometimes gets extremely small, making it even harder to scroll. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776487 Title: too difficult to select scroll bar handle -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776487] Re: too difficult to select scroll bar handle
Of course, I'm using a desktop with mouse, I guess this scrollbar was designed with mobile users in mind, I think it needs a few tweaks for us mousers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776487 Title: too difficult to select scroll bar handle -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 732653] Re: Menus are hidden by default
I agree, this is a major usability regression IMHO from previous versions of Ubuntu, I spent ages trying to find the menu before I thought of mousing over the title at the top of the screen. Can we at least have an option to turn it off!! I'm a Mac OS X user so menus at the top of the screen are not unfamiliar to me, but hiding it by default is a design flaw, it detracts significantly from the usability compared to a traditional desktop machine, IMHO it would be better to obscure the window title than to hide the menu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/732653 Title: Menus are hidden by default -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 732653] Re: Menus are hidden by default
Perhaps more constructive in most of the apps I use there is ample space for the menu to sit beside the window title, why not simply make the menu permanently visible but sit next to the window title. If either gets too large then add a ... indicator and then a mouse over can reveal the complete menu. (or or whatever to indicate there are more options). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/732653 Title: Menus are hidden by default -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792344] [NEW] Screen corruption with virtual desktop greater than 2048 pixels
Public bug reported: Binary package hint: compiz When using an ATI Radeon X800XT (R423) 5d57(PCIE) and a dual monitor setup I get screen corruption when running compiz. To reproduce: 1. Log in using Ubuntu Classic 2. Open a terminal window. 3. Drag window around At this point a trail of windows are left behind as the backdrop is updated. ** Affects: compiz (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/792344 Title: Screen corruption with virtual desktop greater than 2048 pixels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792344] Re: Screen corruption with virtual desktop greater than 2048 pixels
After researching this I disovered the enabling the Copy to texture should work around the 2048 pixel limit for compiz. It would be good if this was enabled by default. However, after installing CompizConfig Settings Manager and enabling the copytex plugin a different behaviour is observed: the backgournd is filled with random junk. After spend some hours stepping through the copytex.cpp code I've managed to put together a patch that fixes this problem. Really there are two things that need to be done: 1. Enable the Copy to texture plugin by default 2. Apply the patch to the copytex.cpp plugin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792344 Title: Screen corruption with virtual desktop greater than 2048 pixels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792344] Re: Screen corruption with virtual desktop greater than 2048 pixels
This is the patch to the Copy to Texture plugin I am currently using. It appears to fix this issue. ** Patch added: Fixes premature delete that causes heap corruption https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/792344/+attachment/2153368/+files/fix_screen_corruptions.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792344 Title: Screen corruption with virtual desktop greater than 2048 pixels -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 782261] [NEW] Menus items disappearing in some applications
Public bug reported: Binary package hint: unity I noticed this whilst using SpringSource Tools downloaded from here: http://www.springsource.com/developer/sts (version 2.6.1 installed from the prepackage Linux 32-bit install) A number of the menu options that would normally be in the menu seem to be missing or broken. Under “Ubuntu Classic” when a have a Java source file open I get the following options: File, Edit, Source, Refactor, Navigate, Search, Project, Run, Window, Help Viewing exactly the same file under a “Ubuntu” desktop session I get: Edit, Source, Refactor, Navigate, Window Also the Window menu is supposed to have sub menus for the Open Perspective and Show View options, but instead there is no sub-menu and these options do nothing when selected. As you can imagine this using this app quite difficult under Unity. msharman@desktop:~$ lsb_release -rd Description:Ubuntu 11.04 Release:11.04 msharman@desktop:~$ apt-cache policy unity unity: Installed: 3.8.12-0ubuntu1 Candidate: 3.8.12-0ubuntu1 Version table: *** 3.8.12-0ubuntu1 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 3.8.10-0ubuntu2 0 500 http://mirror.internode.on.net/pub/ubuntu/ubuntu/ natty/main i386 Packages ** Affects: unity (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/782261 Title: Menus items disappearing in some applications -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 782261] Re: Menus items disappearing in some applications
Odd. It's now working fine, I have no idea what was causing the problem but all my Menus are displaying fine now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/782261 Title: Menus items disappearing in some applications -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 782261] Re: Menus items disappearing in some applications
Spoke too soon, rebooted and the same behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/782261 Title: Menus items disappearing in some applications -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776565] Re: compiz no longer able to drive my external monitor on upgrade to 11.04; does not recover
Yep, having the same problems here also, with a dual monitor set up. Works fine without compiz, but with compiz the screen gets corrupts. Symptoms including random garbage over monitors, to just a black screen where the background should be, and dragging windows leaves a trail of artifacts as if the background is not being rendered at all. My graphics card chipset is ATI Radeon X800XT. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776565 Title: compiz no longer able to drive my external monitor on upgrade to 11.04; does not recover -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1182007] Re: Failed to SUID root
I'm having trouble trouble connecting to Google Talk get am getting the following in my syslog: Mar 27 11:28:59 office-desktop signond[9112]: ../../../../src/signond/signondaemon.cpp 388 init Failed to SUID root. Secure storage will not be available. Mar 27 11:28:59 office-desktop signond[9112]: ../../../../src/signond/credentialsaccessmanager.cpp 211 init Couldn't load AccessControlManager: apparmor-ac Running 13.10 (64-bit) ** Description changed: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1182007 Title: Failed to SUID root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1182007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
I noticed today that I had a partialy configured nvidia-331 package (I'm using nvidia-331-updates). I purged the package, and now the dpkg reconfigure nvidia-331-updates commands succeed. I wonder if this was the cause of 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/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464968] [NEW] Unable to import photos from Samsung Galaxy Note 3
Public bug reported: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a Could not claim USB device (-53) error, which when dismissed just displays a Starting import please wait message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp- detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect, device number 2 [ 28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 28.375249] usb 1-2: Product: SAMSUNG_Android [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 2. Kill any gvfs processes that might interfere with with mtp-detect msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 3. Make sure phone is unlocked and run mtp-detect: msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 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 4 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. 4. Check dmesg output: msharman@laptop-msharman:~$ dmesg | tail [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 [ 88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 88.681995] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 88.681999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 88.682000] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 [ 217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 217.885218] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 217.885227] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 217.885230] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 It looks like there could be an xhci related kernel bug? So I tried using a newer mainline kernel: http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.0-vivid/linux- image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb With this kernel I get different dmesg output but the mtp-detect still fails (following the exact same procedure as above but I'm just showing the differences here) (running kernel 4.0.0) msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 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 4 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): No such device outep: usb_get_endpoint_status(): No such device libusb_open() failed!: No such device LIBMTP PANIC: Could not init USB on second attempt Unable to open raw device 0 OK. msharman@laptop-msharman:~$ dmesg | tail [ 212.229605] usb 2-2: Product: SAMSUNG_Android [ 212.229608] usb 2-2: Manufacturer: SAMSUNG [ 212.229610] usb 2-2: SerialNumber: 2410ba56 [ 215.164011] usb 2-2: USB disconnect, device number 2 [ 215.503911] usb 1-2: new high-speed USB device number 5 using xhci_hcd [ 215.634182] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 215.634189] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 215.634193] usb 1-2: Product: SAMSUNG_Android [ 215.634196] usb 1-2: Manufacturer: SAMSUNG [ 215.634198] usb 1-2: SerialNumber: 2410ba56 So upgrading to kernel 4.0 has done something it's fixed the xhci_hcd related errors but the mtp-detect is still failing (I've tried gphoto2 -L as well and got similar results). But issue still remains. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mtp-tools 1.1.8-1ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jun 14 16:49:17 2015 InstallationDate: Installed on 2012-10-21 (966 days ago)
[Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
sorry this is the same as https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1464968 I just wantes to make sure the correct kernel related information was submitted since I think this is likely a kernel issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464968] Re: Unable to import photos from Samsung Galaxy Note 3
*** This bug is a duplicate of bug 1464969 *** https://bugs.launchpad.net/bugs/1464969 ** This bug has been marked a duplicate of bug 1464969 Unable to import photos from Samsung Galaxy Note 3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464968 Title: Unable to import photos from Samsung Galaxy Note 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1464968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
Also tried kernel 3.12.43-031243-generic still failed, dmesg output now: [ 18.855676] usb 3-2: USB disconnect, device number 2 [ 64.721133] usb 3-2: new high-speed USB device number 4 using xhci_hcd [ 64.739469] usb 3-2: New USB device found, idVendor=04e8, idProduct=6860 [ 64.739474] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 64.739476] usb 3-2: Product: SAMSUNG_Android [ 64.739477] usb 3-2: Manufacturer: SAMSUNG [ 64.739479] usb 3-2: SerialNumber: 2410ba56 [ 132.665779] usb 3-2: usbfs: process 2073 (pool) did not claim interface 0 before use [ 132.831567] usb 3-2: reset high-speed USB device number 4 using xhci_hcd [ 132.848744] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad1c0 [ 132.848749] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad180 [ 132.848752] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad200 [ 132.849369] usb 3-2: usbfs: process 2073 (pool) did not claim interface 0 before use [ 133.015400] usb 3-2: reset high-speed USB device number 4 using xhci_hcd [ 133.032709] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad1c0 [ 133.032715] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad180 [ 133.032717] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800368ad200 [ 133.033430] usb 3-2: usbfs: process 2073 (pool) did not claim interface 0 before use [ 133.033564] usb 3-2: usbfs: process 2073 (pool) did not claim interface 0 before use -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464969] [NEW] Unable to import photos from Samsung Galaxy Note 3
Public bug reported: I'm having trouble accessing photos or files on my Samsung Galaxy Note 3 phone. Plugging in phone and using Shotwell, then clikcing on the SMASUNG_Android camera cause a Could not claim USB device (-53) error, which when dismissed just displays a Starting import please wait message indefinitely. In an attempt to figure out what is going wrong I've been using the mtp- detect command as per https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556 So this is a log of what I've done: (running kernel is 3.19.0-20-generic) 1. Unplug and plug in Samsung Galaxy Note 3 and get dmesg output: [ 25.386168] usb 1-2: USB disconnect, device number 2 [ 28.245983] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 28.375245] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 28.375247] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 28.375249] usb 1-2: Product: SAMSUNG_Android [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 2. Kill any gvfs processes that might interfere with with mtp-detect msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 3. Make sure phone is unlocked and run mtp-detect: msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 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 4 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. 4. Check dmesg output: msharman@laptop-msharman:~$ dmesg | tail [ 28.375250] usb 1-2: Manufacturer: SAMSUNG [ 28.375251] usb 1-2: SerialNumber: 2410ba56 [ 88.552728] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 88.681995] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 88.681999] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 88.682000] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 [ 217.756010] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 217.885218] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731348 [ 217.885227] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731300 [ 217.885230] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 8800b8731390 It looks like there could be an xhci related kernel bug? So I tried using a newer mainline kernel: http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.0-vivid/linux- image-4.0.0-04-generic_4.0.0-04.201504121935_amd64.deb With this kernel I get different dmesg output but the mtp-detect still fails (following the exact same procedure as above but I'm just showing the differences here) (running kernel 4.0.0) msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 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 4 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): No such device outep: usb_get_endpoint_status(): No such device libusb_open() failed!: No such device LIBMTP PANIC: Could not init USB on second attempt Unable to open raw device 0 OK. msharman@laptop-msharman:~$ dmesg | tail [ 212.229605] usb 2-2: Product: SAMSUNG_Android [ 212.229608] usb 2-2: Manufacturer: SAMSUNG [ 212.229610] usb 2-2: SerialNumber: 2410ba56 [ 215.164011] usb 2-2: USB disconnect, device number 2 [ 215.503911] usb 1-2: new high-speed USB device number 5 using xhci_hcd [ 215.634182] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 215.634189] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 215.634193] usb 1-2: Product: SAMSUNG_Android [ 215.634196] usb 1-2: Manufacturer: SAMSUNG [ 215.634198] usb 1-2: SerialNumber: 2410ba56 So upgrading to kernel 4.0 hasdone something it's fixed the xhci_hcd related errors but the mtp-detect is still failing (I've tried gphoto2 -L as well and got similar results). So I'm not which package the bug is in: could kernel, libmtp, libusb or somethings else ? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-generic 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID
[Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
I just tried with the latest mainline kernel: 4.1.0-040100rc7-generic Got the same result but different dmesg output: [ 29.767220] usb 1-2: USB disconnect, device number 2 [ 32.307137] usb 1-2: new high-speed USB device number 4 using xhci_hcd [ 32.436267] usb 1-2: New USB device found, idVendor=04e8, idProduct=6860 [ 32.436272] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 32.436274] usb 1-2: Product: SAMSUNG_Android [ 32.436276] usb 1-2: Manufacturer: SAMSUNG [ 32.436278] usb 1-2: SerialNumber: 2410ba56 [ 52.986605] usb 1-2: usbfs: process 2070 (mtp-detect) did not claim interface 0 before use [ 53.098907] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 53.227897] usb 1-2: usbfs: process 2070 (mtp-detect) did not claim interface 0 before use [ 53.395019] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 53.525020] usb 1-2: usbfs: process 2070 (mtp-detect) did not claim interface 0 before use [ 53.525248] usb 1-2: usbfs: process 2070 (mtp-detect) did not claim interface 0 before use [ 133.385180] usb 1-2: usbfs: process 2147 (pool) did not claim interface 0 before use [ 133.497291] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 133.627167] usb 1-2: usbfs: process 2147 (pool) did not claim interface 0 before use [ 133.793254] usb 1-2: reset high-speed USB device number 4 using xhci_hcd [ 133.922914] usb 1-2: usbfs: process 2147 (pool) did not claim interface 0 before use [ 133.923082] usb 1-2: usbfs: process 2147 (pool) did not claim interface 0 before use -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
** Attachment added: dmesg output kernel 4.1rc7 for comparison https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+attachment/4415377/+files/dmesg-out-4.1rc7.txt ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
msharman@laptop-msharman:~$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date N56VM.214 08/28/2012 Thanks, for some reason it didn't occur to me to check for out dated BIOS. I've updated the BIOS to the 214 version which indeed has made a significant change. Ubuntu now attachs to the phone with the file manager when it is plugged in. Add if I eject the phone (to avoid the device can not be claimed error in Shotwell) then Shotwell is now able to read the previews of the photos and import the photos - which is much better. However, it isn't stable, I gave the mtp-detect process above a go after a reboot and the result is better but there were some errors I've attached the output as the file mtp-detect-out.txt and also there are still errors in the dmesg I've attached the complete dmesg output as dmesg-out.txt Interestingly after repeating the above mtp-detect hangs as it attempts to reset the device: msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ mtp-detect (output attached as mtp-detect-out.txt) dmesg output: [ 51.197549] usb 1-4: USB disconnect, device number 3 [ 54.520400] usb 1-4: new high-speed USB device number 4 using xhci_hcd [ 54.649665] usb 1-4: New USB device found, idVendor=04e8, idProduct=6860 [ 54.649672] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 54.649676] usb 1-4: Product: SAMSUNG_Android [ 54.649679] usb 1-4: Manufacturer: SAMSUNG [ 54.649682] usb 1-4: SerialNumber: 2410ba56 [ 131.389969] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use [ 131.501544] usb 1-4: reset high-speed USB device number 4 using xhci_hcd [ 131.630174] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88022409da48 [ 131.630180] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88022409da00 [ 131.630184] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with disabled ep 88022409da90 [ 131.630628] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use [ 131.630712] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630828] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630841] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630856] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630872] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.630900] usb 1-4: usbfs: process 2209 (mtp-detect) did not claim interface 0 before use [ 131.631012] usb 1-4: usbfs: process 2263 (pool) did not claim interface 0 before use msharman@laptop-msharman:~$ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled. libmtp version: 1.1.8 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) Seems to hang here. For reference my list of steps is now: 1. Plug in device 2. Click Eject when notification about device attached appears (otherwise will get an error about device being claimed). 3. Kill gvfs processes because they stop mtp-detect from working. msharman@laptop-msharman:~$ killall gvfs-gphoto2-volume-monitor msharman@laptop-msharman:~$ killall gvfs-mtp-volume-monitor 5. Make sure phone is unlocked and then run mtp-detect Works but has errors. 5. Make sure phone is unlocked and then run mtp-detect a second time. This time it hangs. As before I tried updating to the most recent mainline kernel 4.1rc7 but the same symptoms were present the dmesg output was different again (I've attached this as dmesg-out-41.rc7.txt) ** Attachment added: dmesg output kernel 3.19.0-20 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+attachment/4415376/+files/dmesg-out.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464969] Re: Unable to import photos from Samsung Galaxy Note 3
** Attachment added: output when mtp-detect works after resetting device https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+attachment/4415375/+files/mtp-detect-out.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1464969 Title: Unable to import photos from Samsung Galaxy Note 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1472487] [NEW] Remmina fullscreen broken and unusable
Public bug reported: Steps: 1. Open VNC connection from connection window. (server is at 1080p, as is both monitors on Ubuntu system) 2. Click fullscreen button. Results: Window has black borders and is off centre overlapping two monitors on my dual monitor setup. It is also impossible to get the window out of full screen using the toolbar as it moves rapidly up and down whenever the mouse pointer is positioned on it. Expected results: Fullscreen should bring the window to cover the entire screen and the toolbar to control remmina should be clickable and slide down from the top of the screen. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: remmina 1.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jul 8 15:19:44 2015 InstallationDate: Installed on 2013-03-04 (855 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Release amd64(20121023) SourcePackage: remmina UpgradeStatus: Upgraded to vivid on 2015-06-06 (32 days ago) ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: dual monitor screenshot the VNC window is in full screen mode https://bugs.launchpad.net/bugs/1472487/+attachment/4426128/+files/Screenshot%20from%202015-07-08%2015%3A13%3A33.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472487 Title: Remmina fullscreen broken and unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1472487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611243] Re: lxc-attach "lxc-attach: attach.c: lxc_attach: 730 failed to get the init pid"
ah so you do! apologies for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611243 Title: lxc-attach "lxc-attach: attach.c: lxc_attach: 730 failed to get the init pid" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1611243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611243] [NEW] lxc-attach "lxc-attach: attach.c: lxc_attach: 730 failed to get the init pid"
Public bug reported: This is what I did: 1. sudo lxc-create -t download -n itsnotfine -- --dist ubuntu --release xenial --arch amd64 2. sudo lxc-attach -n itsnotfine lxc-attach: attach.c: lxc_attach: 730 failed to get the init pid 3. Returns to command line prompt. I expected to be attached to the newly created container. dist version: Ubuntu 16.04.1 LTS package version: 2.0.3-0ubuntu1~ubuntu16.04.1 ** Affects: lxc (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/1611243 Title: lxc-attach "lxc-attach: attach.c: lxc_attach: 730 failed to get the init pid" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1611243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 768791] Re: isoinfo: Unable to find Joliet SVD (USB creator won't select ISO for creating boot USB)
Still a problem on 16.04 LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/768791 Title: isoinfo: Unable to find Joliet SVD (USB creator won't select ISO for creating boot USB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cdrkit/+bug/768791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802208] [NEW] Reports won't open
Public bug reported: Reports that were working as of June this year (I haven't opened them since then) now are failing with the following error: Can not activate the factory for org.libreoffice.report.pentaho.SOReportJobFactory$_SOReportJobFactory I tried creating a fresh report to see if its some kind of out of date file format but I get the same error: 1. select "Create Report in Design View..." 2. select "Save" 3. Double click report 4. Same error as above Of course I'm expecting the report to open without an error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-report-builder 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 8 12:16:08 2018 InstallationDate: Installed on 2018-02-17 (263 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-01 (190 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802208 Title: Reports won't open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1802208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966143] [NEW] Periodic glitch in LogiTech H390 headphone audio
Public bug reported: When running kernel version 5.13.0-37-generic the audio output through my Logitech H390 headphones has a periodic "glitch" every few seconds - noticable in Google Meetings and Youtube - its very distracting, its not exactly a scratch or pop; it's more like a really bad reception mobile phone call "robot voice" noise but lasts only for a moment, then maybe 30 seconds later occurs again, seems to be regularly periodic. The problem isn't present on 5.13.0-35-generic and doesn't effect my external speaker audio output just the headphones so it's not a network issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Mar 24 10:26:12 2022 InstallationDate: Installed on 2018-02-17 (1495 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-05-08 (684 days ago) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: When running kernel version 5.13.0-37-generic the audio output through my Logitech H390 headphones has a periodic "glitch" every few seconds - noticable in Google Meetings and Youtube - its very distracting, its not - exactly a scratch or pop, not sure how to describe it. + exactly a scratch or pop; it's more like a really bad reception mobile + phone call "robot voice" noise but lasts only for a moment, then maybe + 30 seconds later occurs again, seems to be regularly peridoic. The problem isn't present on 5.13.0-35-generic and doesn't effect my sound card audio output just the headphones. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Mar 24 10:26:12 2022 InstallationDate: Installed on 2018-02-17 (1495 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-05-08 (684 days ago) ** Description changed: When running kernel version 5.13.0-37-generic the audio output through my Logitech H390 headphones has a periodic "glitch" every few seconds - noticable in Google Meetings and Youtube - its very distracting, its not exactly a scratch or pop; it's more like a really bad reception mobile phone call "robot voice" noise but lasts only for a moment, then maybe - 30 seconds later occurs again, seems to be regularly peridoic. + 30 seconds later occurs again, seems to be regularly periodic. The problem isn't present on 5.13.0-35-generic and doesn't effect my - sound card audio output just the headphones. + external speaker audio output just the headphones so it's not a network + issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Mar 24 10:26:12 2022 InstallationDate: Installed on 2018-02-17 (1495 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: Upgraded to focal on 2020-05-08 (684 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966143 Title: Periodic glitch in LogiTech H390 headphone audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
