[Desktop-packages] [Bug 1955087] [NEW] bluetooth cannot transfer files to phone although connected
Public bug reported: Ubuntu version: 20.4 Not sure of package (bluez)? (Whatever handles Bluetooth) What I expected: File is transferred. What happened: transfer fails with mysterious error code (0x53) which sometimes shows up on phone and sometimes doesn't. In any case the transfer fails. Additional notes: Error was observed before, see https://bbs.archlinux.org/viewtopic.php?id=202815, however suggested solution on that page doesn't work for me so I assume there is some difference. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 18:50:38 2021 InstallationDate: Installed on 2021-01-27 (323 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP Pavilion Desktop TP01-0xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=d2279364-889e-4dd0-9766-948e06f4ab3d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.release: 15.35 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.41 dmi.modalias: dmi:bvnAMI:bvrF.23:bd07/07/2020:br15.35:efr52.41:svnHP:pnHPPavilionDesktopTP01-0xxx:pvr:sku3UQ92AA#ABA:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Desktop TP01-0xxx dmi.product.sku: 3UQ92AA#ABA dmi.sys.vendor: HP hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:15:83:4E:03:27 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5837051 acl:16480 sco:0 events:6085 errors:0 TX bytes:44273 acl:1706 sco:0 commands:1272 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bluetooth focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1955087 Title: bluetooth cannot transfer files to phone although connected Status in bluez package in Ubuntu: New Bug description: Ubuntu version: 20.4 Not sure of package (bluez)? (Whatever handles Bluetooth) What I expected: File is transferred. What happened: transfer fails with mysterious error code (0x53) which sometimes shows up on phone and sometimes doesn't. In any case the transfer fails. Additional notes: Error was observed before, see https://bbs.archlinux.org/viewtopic.php?id=202815, however suggested solution on that page doesn't work for me so I assume there is some difference. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 18:50:38 2021 InstallationDate: Installed on 2021-01-27 (323 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP Pavilion Desktop TP01-0xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=d2279364-889e-4dd0-9766-948e06f4ab3d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.release: 15.35 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.41 dmi.modalias: dmi:bvnAMI:bvrF.23:bd07/07/2020:br15.35:efr52.41:svnHP:pnHPPavilionDesktopTP01-0xxx:pvr:sku3UQ92AA#ABA:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Desktop TP01-0xxx dmi.product.sku: 3UQ92AA#ABA dmi.sys.vendor: HP hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:15:83:4E:03:27 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5837051 acl:16480 sco:0 events:6085 errors:0 TX bytes:44273 acl:1706 sco:0 commands:1272 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1955087/+subscriptions -- Mailing
[Desktop-packages] [Bug 1536409] Re: gimp move by holding space bar does not terminate
Same version, same problem, not running fullscreen mode. Cannot escape hangup because the mouse and graphics tablet inputs continue to be captured (I assume). When I signed on from another computer via ssh and killed the Gimp process, everything else appeared to resume running normally. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1536409 Title: gimp move by holding space bar does not terminate Status in gimp package in Ubuntu: New Bug description: package: gimp 2.8.14 release: Ubuntu 14.04.3 LTS circumstance: Running gimp in full screen mode, moving image around by depressing space bar and using mouse. Cursor changes to fist. Note that image was larger by a good bit than window / view of image. expected behavior: On releasing space bar, cursor should resume previous mode and moving mouse should not move image. observed behavior: On releasing space bar, gimp remains in same state (moving image). Moving the cursor outside the window does not release the move either. Clicking mouse (either side) has no effect in window or out. Nor does ESC, space, break, or any other keyboard action. In full screen mode, it is necessary to reboot or restart the desktop to get out of the situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1536409/+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 1536409] Re: gimp move by holding space bar does not terminate
I should add that the problem is intermittent -- not seen often. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1536409 Title: gimp move by holding space bar does not terminate Status in gimp package in Ubuntu: New Bug description: package: gimp 2.8.14 release: Ubuntu 14.04.3 LTS circumstance: Running gimp in full screen mode, moving image around by depressing space bar and using mouse. Cursor changes to fist. Note that image was larger by a good bit than window / view of image. expected behavior: On releasing space bar, cursor should resume previous mode and moving mouse should not move image. observed behavior: On releasing space bar, gimp remains in same state (moving image). Moving the cursor outside the window does not release the move either. Clicking mouse (either side) has no effect in window or out. Nor does ESC, space, break, or any other keyboard action. In full screen mode, it is necessary to reboot or restart the desktop to get out of the situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1536409/+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 1536409] [NEW] gimp move by holding space bar does not terminate
Public bug reported: package: gimp 2.8.14 release: Ubuntu 14.04.3 LTS circumstance: Running gimp in full screen mode, moving image around by depressing space bar and using mouse. Cursor changes to fist. Note that image was larger by a good bit than window / view of image. expected behavior: On releasing space bar, cursor should resume previous mode and moving mouse should not move image. observed behavior: On releasing space bar, gimp remains in same state (moving image). Moving the cursor outside the window does not release the move either. Clicking mouse (either side) has no effect in window or out. Nor does ESC, space, break, or any other keyboard action. In full screen mode, it is necessary to reboot or restart the desktop to get out of the situation. ** Affects: gimp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1536409 Title: gimp move by holding space bar does not terminate Status in gimp package in Ubuntu: New Bug description: package: gimp 2.8.14 release: Ubuntu 14.04.3 LTS circumstance: Running gimp in full screen mode, moving image around by depressing space bar and using mouse. Cursor changes to fist. Note that image was larger by a good bit than window / view of image. expected behavior: On releasing space bar, cursor should resume previous mode and moving mouse should not move image. observed behavior: On releasing space bar, gimp remains in same state (moving image). Moving the cursor outside the window does not release the move either. Clicking mouse (either side) has no effect in window or out. Nor does ESC, space, break, or any other keyboard action. In full screen mode, it is necessary to reboot or restart the desktop to get out of the situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1536409/+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 311297] Re: growisofs unable to burn dual layer DVD-R
I have experienced this problem with Ubuntu 14.04. Until a few months ago the problem did not occur, but then I started to observe inevitable failures when the target was a DL DVD-R. I have a machine still running 12.04 which does not exhibit the problem; it has no trouble writing the DVDs. I conclude the change made to 14.04 is the current problem. The error messages I get are similar to those already posted here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to dvd+rw-tools in Ubuntu. https://bugs.launchpad.net/bugs/311297 Title: growisofs unable to burn dual layer DVD-R Status in dvd+rw-tools package in Ubuntu: Confirmed Status in dvd+rw-tools package in Debian: New Bug description: Using kubuntu hardy heron (LTS) up to date. I have tried to burn a Verbatim 4x DVD-R DL in my LG GSA-H10N dvd writer with k3b... and no way! The problem is related to growisofs. I have no problem burning CD-R, CR-RW and DVD-R (the only media I used). Of course, the writer supports dual layer DVD-R and firmware is updated to the last version. You can see the output from k3b in the attached file. I have also tried from the shell: jcamen@vicma:~$ growisofs -dvd-compat -speed=2 -Z /dev/dvd1=Almacen/ssbb.iso Executing 'builtin_dd if=Almacen/ssbb.iso of=/dev/dvd1 obs=32k seek=0' :-[ READ DVD STRUCTURE #10h failed with SK=8h/ASC=ABh/ACQ=80h]: Input/output error It seems that growisofs don't like DVD-R DL media. I have made tons of google searches and it looks like there is a serious problem with growisofs and DVD-R DL. See for instance the thread at http://bugs.kde.org/show_bug.cgi?id=138641 . Words from Sebastian Trueg, developer of the wonderful k3b: "I am closing this as invalid then because it is not a k3b bug and I will introduce cdrecord DVD writing support post-1.0 which will hopefully fix this problem. " Any ideas to fix this? Even Windows XP is capable of burning DVD-R DL with this writer! :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dvd+rw-tools/+bug/311297/+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 1249940] Re: Thunderbird picks incorrect mime type for inline picture when drag-and-dropping
I experienced the same problem dragging jpgs to message I was composing.
The resultant attachment is characterized as something.txt, which
confuses many mail readers. It may also be incorrectly encoded. I am
running Thunderbird 24.5.0 on Ubuntu 12.4 on a Dell Vostro (32-bit
Intel) machine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1249940
Title:
Thunderbird picks incorrect mime type for inline picture when drag-
and-dropping
Status in “thunderbird” package in Ubuntu:
Confirmed
Bug description:
When I attach png images by dragging from the file browser to the
header region of the compose window, they are attached with correct
mimetype.
Content-Type: image/png;
name=foo.png
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename=foo.png
Similarly, *inline* png images attach fine when using Thunderbird's
native file picker.
Content-Type: image/png;
name=foo.png
Content-Transfer-Encoding: base64
Content-ID: part1.random_numb...@foobar.com
Content-Disposition: inline;
filename=foo.png
However, when I attach them inline by *dragging* from the file browser
into the body, they are attached with the incorrect mime type as
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: base64
Content-ID: part1.00030206.09040...@foobar.com
The latter displays fine for the recipient if they are using
Thunderbird, or via the gmail web interface. However, OSX Mail.app
users only see a text file Mail Attachment.txt full of nonsense.
Kmail also fails to display the image correctly.
It seems that Thunderbird is using the wrong mime type when png images
are attached inline. (I also see a similar problem with .jpg files.)
I see the same problem whether dragging from Dolphin file browser,
Konqueror, Krusader, Firefox (via the browser window itself), and
Kate's file picker. With Firefox, I entered the file path into the url
bar, and dragged from the main browser window. I also attempted to
install Nautilus, but I can't even drag from it (with KDE). I've also
tried dragging from Firefox's browser window in Xubuntu, which had the
same problem.
I tried safe mode, and this didn't fix it. Finally, installing
Thunderbird directly from the website *does* fix the problem so it's a
problem introduced in the Ubuntu package.
TB 24.1.0
Kubuntu 13.10
KDE 4.11.2
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: thunderbird 1:24.1.0+build1-0ubuntu0.13.10.1
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lee2253 F pulseaudio
BuildID: 20131028125905
CRDA:
country AU:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (3, 23)
(5250 - 5330 @ 40), (3, 23), DFS
(5735 - 5835 @ 40), (3, 30)
Channel: Unavailable
Date: Mon Nov 11 15:18:44 2013
DefaultProfilePrefSources:
prefs.js
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/000system.js
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
[Profile]/extensions/{9533f794-00b4-4354-aa15-c2bbda6989f8}/defaults/preferences/prefs.js
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2012-12-16 (329 days ago)
InstallationMedia: Kubuntu 12.10 Quantal Quetzal - Release amd64
(20121017.1)
IpRoute:
default via 192.168.1.254 dev wlan0 proto static
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.4 metric 9
MarkForUpload: True
MostRecentCrashID: bp-8716a067-8317-4ad0-808a-2254e2120524
Profile1PrefSources:
prefs.js
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
/usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/000system.js
Profile1Prefs:
extensions.lastAppVersion: 24.0 (prefs.js)
network.cookie.prefsMigrated: true (prefs.js)
Profiles:
Profile0 (Default) - LastVersion=24.1.0/20131028125905 (In use)
Profile1 - LastVersion=24.0/20130917155107 (Out of date)
RelatedPackageVersions:
kopete4:4.11.2-0ubuntu1
google-talkplugin 4.7.0.0-1
rhythmbox-mozilla 2.99.1-0ubuntu1
RunningIncompatibleAddons:
