[Touch-packages] [Bug 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
Still happening in May 2022 on xubuntu 22.04 with xfce -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Status in at-spi: Invalid Status in at-spi2-core package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: Invalid Status in at-spi2-core package in Debian: Invalid Bug description: Since a few days, xsession-errors is fullfilled by that kind of errors: ** (nautilus:22621): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused Similar errors are reported all over the net, but Debian have tried to fix it already: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517 But some other devs seems to blame an atk-bridge: https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA And some others suggest a dbus/gdbus race; the good thing is that seems not disturbing that much the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Fri Jun 21 08:35:40 2013 MarkForUpload: True SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/1193236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1976119] [NEW] Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
Public bug reported: Every time 'evince' runs it prints this on the terminal: dbind-WARNING **: ... Couldn't connect to accessibility bus: Failed to connect to socket /run/user//at-spi/bus_0: Permission denied AFAICT this is the same as a very-old bug 1193236, but that bug was closed with a comment "If you are affected, open your own bug" (https://bugs.launchpad.net/ubuntu/+source/at- spi2-core/+bug/1193236/comments/20). So I am. Xubuntu (xfce) 22.04 evince version 42.0 at-spi2-core Ubuntu package version 2.44.0-3 STEPS TO REPRODUCE: 1. In a terminal, run /usr/bin/evince RESULTS: Error glop appears on terminal EXPECTED RESULTS: Silence unless there is a real error the user can respond to. ** Affects: at-spi2-core (Ubuntu) Importance: Undecided Status: New ** Description changed: Every time 'evince' runs it prints this on the terminal: dbind-WARNING **: ... Couldn't connect to accessibility bus: Failed to connect to socket /run/user//at-spi/bus_0: Permission denied AFAICT this is the same as a very-old bug 1193236, but that bug was closed with a comment "If you are affected, open your own bug" (https://bugs.launchpad.net/ubuntu/+source/at- spi2-core/+bug/1193236/comments/20). So I am. + + Xubuntu (xfce) 22.04 STEPS TO REPRODUCE: 1. In a terminal, run /usr/bin/evince RESULTS: Error glop appears on terminal EXPECTED RESULTS: Silence unless there is a real error the user can respond to. ** Description changed: Every time 'evince' runs it prints this on the terminal: dbind-WARNING **: ... Couldn't connect to accessibility bus: Failed to connect to socket /run/user//at-spi/bus_0: Permission denied AFAICT this is the same as a very-old bug 1193236, but that bug was closed with a comment "If you are affected, open your own bug" (https://bugs.launchpad.net/ubuntu/+source/at- spi2-core/+bug/1193236/comments/20). So I am. Xubuntu (xfce) 22.04 + evince version 42.0 + + at-spi2-core Ubuntu package version 2.44.0-3 + STEPS TO REPRODUCE: 1. In a terminal, run /usr/bin/evince RESULTS: Error glop appears on terminal EXPECTED RESULTS: Silence unless there is a real error the user can respond to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1976119 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Status in at-spi2-core package in Ubuntu: New Bug description: Every time 'evince' runs it prints this on the terminal: dbind-WARNING **: ... Couldn't connect to accessibility bus: Failed to connect to socket /run/user//at-spi/bus_0: Permission denied AFAICT this is the same as a very-old bug 1193236, but that bug was closed with a comment "If you are affected, open your own bug" (https://bugs.launchpad.net/ubuntu/+source/at- spi2-core/+bug/1193236/comments/20). So I am. Xubuntu (xfce) 22.04 evince version 42.0 at-spi2-core Ubuntu package version 2.44.0-3 STEPS TO REPRODUCE: 1. In a terminal, run /usr/bin/evince RESULTS: Error glop appears on terminal EXPECTED RESULTS: Silence unless there is a real error the user can respond to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1976119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937119] [NEW] apt-add-repository --remove -S ... also deletes other components
Public bug reported: apt-add-repository --remove -S deb http://us.archive.ubuntu.com/ubuntu hirsute xyzzx wrongly disables *every* component, not just xyzzx. This happens because the entire existing line is commented out in /etc/apt/sources.list rather than just editing out the deleted component. When *adding* a component, and existing line is edited IN to an existing line for that repository; the reverse should probably be done when removing a component if there are other components which should remain enabled. In other words, commenting out the whole line should be done only if the LINE specified in the remove command specifies all the currently-enabled components. STEPS TO REPRODUCE: 1. sudo cp /etc/apt /tmp/apt.BAK 2. Remove all references to "multiverse" in /etc/apt/sources.list 3. sudo apt-add-repository -y --no-update -S deb http://us.archive.ubuntu.com/ubuntu hirsute multiverse 4. diff -r /etc/apt.BAK /etc/apt (Should show 'multiverse' added to an existing line in /etc/apt/sources.list) diff -r /tmp/apt.BAK/sources.list /etc/apt/sources.list 4,5c4,5 < deb http://us.archive.ubuntu.com/ubuntu hirsute main restricted < # deb-src http://us.archive.ubuntu.com/ubuntu hirsute main restricted --- > deb http://us.archive.ubuntu.com/ubuntu hirsute restricted main multiverse > # deb-src http://us.archive.ubuntu.com/ubuntu hirsute restricted main multiverse 5. sudo apt-add-repository --remove -y --no-update -S deb http://us.archive.ubuntu.com/ubuntu hirsute multiverse 6. diff -r /etc/apt.BAK /etc/apt (Should show 'multiverse' removed from existing line in /etc/apt/sources.list, but...) diff -r /tmp/apt.BAK/sources.list /etc/apt/sources.list 4,5c4,5 < deb http://us.archive.ubuntu.com/ubuntu hirsute main restricted < # deb-src http://us.archive.ubuntu.com/ubuntu hirsute main restricted --- > # deb http://us.archive.ubuntu.com/ubuntu hirsute multiverse restricted main > # deb-src http://us.archive.ubuntu.com/ubuntu hirsute restricted main multiverse (7. sudo rm -rf /etc/apt; sudo cp -a /tmp/apt.BAK /etc/apt) # restore RESULTS: *every* component (including 'main') is disabled EXPECTED RESULTS: Only the specified component is disabled. In other words, --remove should un-do whatever the effect of an 'add' with the same LINE argument ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: software-properties-common 0.99.10 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Jul 21 18:02:20 2021 InstallationDate: Installed on 2021-07-20 (0 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute uec-images -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1937119 Title: apt-add-repository --remove -S ... also deletes other components Status in software-properties package in Ubuntu: New Bug description: apt-add-repository --remove -S deb http://us.archive.ubuntu.com/ubuntu hirsute xyzzx wrongly disables *every* component, not just xyzzx. This happens because the entire existing line is commented out in /etc/apt/sources.list rather than just editing out the deleted component. When *adding* a component, and existing line is edited IN to an existing line for that repository; the reverse should probably be done when removing a component if there are other components which should remain enabled. In other words, commenting out the whole line should be done only if the LINE specified in the remove command specifies all the currently- enabled components. STEPS TO REPRODUCE: 1. sudo cp /etc/apt /tmp/apt.BAK 2. Remove all references to "multiverse" in /etc/apt/sources.list 3. sudo apt-add-repository -y --no-update -S deb http://us.archive.ubuntu.com/ubuntu hirsute multiverse 4. diff -r /etc/apt.BAK /etc/apt (Should show 'multiverse' added to an existing line in /etc/apt/sources.list) diff -r /tmp/apt.BAK/sources.list /etc/apt/sources.list 4,5c4,5 < deb http://us.archive.ubuntu.com/ubuntu hirsute main restricted < # deb-src http://us.archive.ubuntu.com/ubuntu hirsute main restricted --- > deb http://us.archive.ubuntu.com/ubuntu hirsute restricted main multiverse > # deb-src http://us.archive.ubuntu.com/ubuntu hirsute restricted main multiverse 5. sudo apt-add-repository --remove -y --no-update -S deb http://us.archive.ubuntu.com/ubuntu hirsute multiverse 6. diff -r /etc/apt.BAK /etc/apt (Should show 'multiverse' rem
[Touch-packages] [Bug 1814611] Re: ubuntu-bug never (any longer) opens browser window
In privacy settings, it says I am enabling "Send error reports to Canonical... Send report *automatically*". This does not have anything to do with NON-automatic error reporting. This worked before, what changed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814611] Re: ubuntu-bug never (any longer) opens browser window
Well if "automatic" sending is enabled in Settings->Privacy->Problem Reporting, then is-enabled is "enabled" and is-active is "active". But if "automatic" sending is disabled in Settings, then is-enabled is "disabled" and is-active is "inactive" Again, I don't think running ubuntu-bug explicitly has anything to do with "automatically" sending error reports! As others have said, ubuntu-bug should ignore those settings or, at least, tell the user it won't do anything useful unless those settings are changed. Currently it silently fails (no message, zero exit status). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814611] Re: ubuntu-bug never (any longer) opens browser window
Clarification: By "settings" I meant the single setting (as seen by users) controlled by the "Send error reports to Canonical" switch in Settings->Privacy->problem -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838180] [NEW] apps use speakers when bluetooth headset is active (REGRESSION)
Public bug reported: Bluetooth headset stopped working after upgrading to 19.04. Worked perfectly with 18.10. Now, when a BT headset is connected the volume-control widget (seen via the speaker icon in the upper-right corner) displays a headset icon and a volume slider, but the slider has NO EFRFECT on volume and sound still comes out of the speakers. It seems like the BT headset is active as far as the volume-control GUI knows, BUT sound from apps still goes to the speakers (which were active before the BT headset connected). syslog shows: bluetoothd[1423]: connect error: Device or resource busy (16) I will attach the full syslog The problem does not occur with a wired headset. STEPS TO REPRODUCE: 1. Reboot Turn Bluetooth OFF (speakericon->BTicon->Turn Off) 2. Start Rhythmbox or other sound source; play something, set the volume low but audible (should be heard on speakers) 3. Turn on a Bluetoogh headset 4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On) If necessary, do other stuff to get the BT headset connected A "headset icon" should appear next the volume slider (click speaker icon to see it) RESULTS: Sound continues to come out of speakers; nothing from BT headset Moving the volume slider has no effect EXPECTED RESULTS: Switch sound to the BT headset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 22:59:01 2019 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-21-generic root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0: Type: Primary Bus: USB BD Address: 48:89:E7:CF:4F:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:14153 acl:154 sco:0 events:971 errors:0 TX bytes:429273 acl:643 sco:0 commands:229 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1838180/+attachment/5279675/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838180 Title: apps use speakers when bluetooth headset is active (REGRESSION) Status in bluez package in Ubuntu: New Bug description: Bluetooth headset stopped working after upgrading to 19.04. Worked perfectly with 18.10. Now, when a BT headset is connected the volume-control widget (seen via the speaker icon in the upper-right corner) displays a headset icon and a volume slider, but the slider has NO EFRFECT on volume and sound still comes out of the speakers. It seems like the BT headset is active as far as the volume-control GUI knows, BUT sound from apps still goes to the speakers (which were active before the BT headset connected). syslog shows: bluetoothd[1423]: connect error: Device or resource busy (16) I will attach the full syslog The problem does not occur with a wired headset. STEPS TO REPRODUCE: 1. Reboot Turn Bluetooth OFF (speakericon->BTicon->Turn Off) 2. Start Rhythmbox or other sound source; play something, set the volume low but audible (should be heard on speakers) 3. Turn on a Bluetoogh headset 4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On) If necessary, do other stuff to get the BT headset connected A "headset icon" should appear next the volume slider (click speaker icon to see it) RESULTS: Sound continues to come out of speakers; nothing from BT headset Moving the volume slider has no effect EXPECTED RESULTS: Switch sound to the BT headset ProblemType: Bug DistroRelease: Ubuntu 19.04 Pac
[Touch-packages] [Bug 1838180] Re: apps use speakers when bluetooth headset is active (REGRESSION)
Ok, the mis-directed output seems to be fixed with a kernel 5.2. With the stock 5.0.0-21-generic, disconnecting BT in the Ubuntu gui does not actually disconnect immediately. Instead, the disconnect happens when BT is turned ON again in the gui! (based on my BT headset's synthesized status-change messages, which say nothing when BT is turned OFF in the gui, but say "disconnected" when BT is turned ON in the gui). Thereafter, sound goes to the speakers even though the gui shows the BT headset is connected. I found that power-cycling the headset clears the problem, presumably because of the extraneous connection messages when the headset comes back on. These problem COMPLETELY GO AWAY with kernel 5.2 installed. Now, when I disconnect the headset in the Ubuntu gui, the headset instantly reports being disconnected, and it re-connects propertly when the headset is turned on again in the Ubuntu gui. There are some remaining gui issues where the switch in the gui snaps back by itself to "off" on the first few tries, but after a while the headset connects correctly. I will file a different bugrep about that with a video. In conclusion, it sounds like some kernel bug or api mis-match will be resolved with kernel 5.2, but that won't be shipped for while in Ubuntu. ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838180 Title: apps use speakers when bluetooth headset is active (REGRESSION) Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Bluetooth headset stopped working after upgrading to 19.04. Worked perfectly with 18.10. Now, when a BT headset is connected the volume-control widget (seen via the speaker icon in the upper-right corner) displays a headset icon and a volume slider, but the slider has NO EFRFECT on volume and sound still comes out of the speakers. It seems like the BT headset is active as far as the volume-control GUI knows, BUT sound from apps still goes to the speakers (which were active before the BT headset connected). syslog shows: bluetoothd[1423]: connect error: Device or resource busy (16) I will attach the full syslog The problem does not occur with a wired headset. STEPS TO REPRODUCE: 1. Reboot Turn Bluetooth OFF (speakericon->BTicon->Turn Off) 2. Start Rhythmbox or other sound source; play something, set the volume low but audible (should be heard on speakers) 3. Turn on a Bluetoogh headset 4. Turn on Bluetooth in the computer (Speakericon->BTicon->Turn On) If necessary, do other stuff to get the BT headset connected A "headset icon" should appear next the volume slider (click speaker icon to see it) RESULTS: Sound continues to come out of speakers; nothing from BT headset Moving the volume slider has no effect EXPECTED RESULTS: Switch sound to the BT headset ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 22:59:01 2019 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-21-generic root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0:Type: Primary Bus: USB BD Address: 48:89:E7:CF:4F:FD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:14153 acl:154 sco:0 events:971 errors:0 TX bytes:429273 acl:643 sco:0 commands:229 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838180/+subscriptions
[Touch-packages] [Bug 1838227] [NEW] Bluetooth "Connection switch" snaps back by itself until after many tries
Public bug reported: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Video demonstrating the problem (view with vlc)" https://bugs.launchpad.net/bugs/1838227/+attachment/5279774/+files/btdemo.mp4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: New Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:r
[Touch-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
I rebooted before submitting this bug report using ubuntu-bug, so syslog is probably the wrong one. I'll attach the previous one (syslog.1) which I think covers the test demonstrated in the video (and several earlier attempts). ** Attachment added: "syslog.1" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+attachment/5279785/+files/syslog.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: New Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
@Daniel Here you go (newlog_2019_07_29.txt). The log covers only the time while I tried to connect to the headset (took several tries before the switch switched; there are maybe a dozen mouse actions during that time). There are many message like this: org.gnome.Shell.desktop[1585]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (k eycode 12). ** Attachment added: "newlog_2019_07_29.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+attachment/5279854/+files/newlog_2019_07_29.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Incomplete Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
...and here is a smaller log covering only a single attempt to slide the connection switch to the right (the switch snapped back immediately by itself) ** Attachment added: "newlog_SingleTry_2019_07_29.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+attachment/5279857/+files/newlog_SingleTry_2019_07_29.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Incomplete Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
Well, I see the problem also on real hardware, but it's harder to reproduce. In any case, I don't want to install a non-standard kernel there, so it is mixed up with the other problems with the 5.0 kernel. However, the VM *does* indeed have bluetooth. Virtualbox allows VMs to access any USB device on the host (when enabled). My BT controller is a usb device. For testing I disable BT on the host and later enable the VM to access the BT usb device; it works fine, ie. connects and disconnects as expected (and, yes, even plays music!). All from the VM. However the GUI problem is most apparent in the VM, running 5.2 kernel. I don't think using a VM is relevant, except that hardware timing will be different due to i/o instructions being trapped and re-executed on the host. If timing causes a problem, then it probably points to a race condition or similar bug. Anyway, as I mentioned the same symptom appears less frequently on bare hardware with the 5.0 kernel. I will attached output from journalctl -f for just one "snapback", and for a complete sequence eventually succeeding. Again, tjese were made with the older kernel. ** Attachment added: "newlog_kernel5.0.0-21-generic_onlyfirstsnapback.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+attachment/5279954/+files/newlog_kernel5.0.0-21-generic_onlyfirstsnapback.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Invalid Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
** Attachment added: "newlog_kernel5.0.0-21-generic_repeateduntilitworks.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+attachment/5279955/+files/newlog_kernel5.0.0-21-generic_repeateduntilitworks.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Invalid Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814609] [NEW] ubuntu-bug / appport never opens browser window
Public bug reported: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. I don't know whether the bug data was sent but browser not opened, or if apport silently croaked (yet exited with zero status) before sending anything. Firefox is my default browser, confirmed just now in Settings->Default Applications->Web. Anyway this worked fine before, but it has been many months since I tried to submit a bug. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814609 Title: ubuntu-bug / appport never opens browser window Status in apport package in Ubuntu: New Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. I don't know whether the bug data was sent but browser not opened, or if apport silently croaked (yet exited with zero status) before sending anything. Firefox is my default browser, confirmed just now in Settings->Default Applications->Web. Anyway this worked fine before, but it has been many months since I tried to submit a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814611] [NEW] ubuntu-bug never (any longer) opens browser window
Public bug reported: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Output from strace -f ubuntu-bug apport" https://bugs.launchpad.net/bugs/1814611/+attachment/5236038/+files/strace.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: New Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814613] [NEW] qmlscene -style material file.qml says "QApplication: invalid style override passed"
Public bug reported: qmlscene -qt=5 -style material file.qml prints QApplication: invalid style override passed, ignoring it. on the terminal. This does not happen when using the environment variable method, e.g. QT_QUICK_CONTROLS_STYLE=material qmlscene -qt=5 file.qml The documentation for how this is supposed to work is at https://doc.qt.io/qt-5/qtquickcontrols2-styles.html#using-styles-in-qt-quick-controls-2 I'm reporting this to ubuntu because it might be due to packaging or patching done for Ubuntu. I can not conveniently try a pristine upstream version of Qt, so hoping the Qt Ubuntu maintainer can quickly determine if this is an upstream bug or not. I'll attach a trivial test file which demonstrates the problem STEPS TO REPRODUCE: qmlscene -style material test.qml # test.qml attached ACTUAL RESULTS: Prints warning about invalid style on the terminal EXPECTED RESULTS: Silent obedience ** Affects: qtchooser (Ubuntu) Importance: Undecided Status: New ** Attachment added: "file.qml" https://bugs.launchpad.net/bugs/1814613/+attachment/5236039/+files/file.qml -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtchooser in Ubuntu. https://bugs.launchpad.net/bugs/1814613 Title: qmlscene -style material file.qml says "QApplication: invalid style override passed" Status in qtchooser package in Ubuntu: New Bug description: qmlscene -qt=5 -style material file.qml prints QApplication: invalid style override passed, ignoring it. on the terminal. This does not happen when using the environment variable method, e.g. QT_QUICK_CONTROLS_STYLE=material qmlscene -qt=5 file.qml The documentation for how this is supposed to work is at https://doc.qt.io/qt-5/qtquickcontrols2-styles.html#using-styles-in-qt-quick-controls-2 I'm reporting this to ubuntu because it might be due to packaging or patching done for Ubuntu. I can not conveniently try a pristine upstream version of Qt, so hoping the Qt Ubuntu maintainer can quickly determine if this is an upstream bug or not. I'll attach a trivial test file which demonstrates the problem STEPS TO REPRODUCE: qmlscene -style material test.qml # test.qml attached ACTUAL RESULTS: Prints warning about invalid style on the terminal EXPECTED RESULTS: Silent obedience To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1814613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814613] Re: qmlscene -style material file.qml says "QApplication: invalid style override passed"
Ok, thanks. FYI the underlying qmlscene executable (/usr/lib/qt5/bin/qmlscene) is provided by the "qmlscene" package in Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1814613 Title: qmlscene -style material file.qml says "QApplication: invalid style override passed" Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: qmlscene -qt=5 -style material file.qml prints QApplication: invalid style override passed, ignoring it. on the terminal. This does not happen when using the environment variable method, e.g. QT_QUICK_CONTROLS_STYLE=material qmlscene -qt=5 file.qml The documentation for how this is supposed to work is at https://doc.qt.io/qt-5/qtquickcontrols2-styles.html#using-styles-in-qt-quick-controls-2 I'm reporting this to ubuntu because it might be due to packaging or patching done for Ubuntu. I can not conveniently try a pristine upstream version of Qt, so hoping the Qt Ubuntu maintainer can quickly determine if this is an upstream bug or not. I'll attach a trivial test file which demonstrates the problem STEPS TO REPRODUCE: qmlscene -style material test.qml # test.qml attached ACTUAL RESULTS: Prints warning about invalid style on the terminal EXPECTED RESULTS: Silent obedience To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1814613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814839] [NEW] keystrokes go to wrong window immediately after moving mouse to change window focus
Public bug reported: Ubuntu 18.04. Gnome X11 session. When window focus policy is set to follow the mouse, then if the mouse is moved into a new window and keystrokes typed immediately afterwards, the keystrokes go to the old window (invariably causing application errors). This is extremely annoying for rapid-fire developers, who for example run vim in one window to edit a script and bash in another to test the script; the sequence 1) save changes in vim; 2) move mouse to the bash window; 3) type the command to run the script results in the shell command (or part of it) being received by vim in the old window (with occasionally-entertaining effects). It seems like mouse-movement events are not kept in-order with respect to keyboard events. I can see the mouse pointer move to the new window before I type on the keyboard, so I know the mouse-move events have been received before the keystrokes. Speculations: This might be a window-manager bug: Although the mouse cursor has moved before I type, the window borders may not yet have changed to indicate a changed focus (not certain because the sequence is so quick). Therefore the window manager might be (erroneously) continuing to pass keystrokes to the "current" (i.e. old) window after the mouse moves into the new window. I'm assuming here that the window manager is able to receive mouse-move and keyboard events in a single stream, or timestamped, or otherwise marked so they can be processed in the order they originally occurred. Or maybe Xorg does not keep them in order or doesn't allow the window- manager to know their relative order. Or maybe keystrokes are going directly to the old window without filtering for the current mouse position (if this is the case, then IMO xorg should be told to stop delivering keystrokes if the mouse is outside a specified region until the window-manager tells it to resume delivery; or some similar way to allow the focus-change to occur first). STEPS TO REPRODUCE: 1. Run gnome-tweaks, set Windows->Window Focus to "Sloppy" 2. Open two vertically-adjacent gnome-terminal windows 3. Put cursor in the top window. Wait 2 seconds. 4. Move mouse (with one hand) rapidly into the other window, then (immediately) type a character into the other window (with the other hand) ACTUAL RESULTS: The keystroke appears in the old window EXPECTED RESULTS: Keystroke appears in the new window (i.e. the keystroke is not processed at all until the window manager completes the focus change). In other words, "typeahead" should encompass both keystrokes and mouse movements. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814839 Title: keystrokes go to wrong window immediately after moving mouse to change window focus Status in xorg package in Ubuntu: New Bug description: Ubuntu 18.04. Gnome X11 session. When window focus policy is set to follow the mouse, then if the mouse is moved into a new window and keystrokes typed immediately afterwards, the keystrokes go to the old window (invariably causing application errors). This is extremely annoying for rapid-fire developers, who for example run vim in one window to edit a script and bash in another to test the script; the sequence 1) save changes in vim; 2) move mouse to the bash window; 3) type the command to run the script results in the shell command (or part of it) being received by vim in the old window (with occasionally-entertaining effects). It seems like mouse-movement events are not kept in-order with respect to keyboard events. I can see the mouse pointer move to the new window before I type on the keyboard, so I know the mouse-move events have been received before the keystrokes. Speculations: This might be a window-manager bug: Although the mouse cursor has moved before I type, the window borders may not yet have changed to indicate a changed focus (not certain because the sequence is so quick). Therefore the window manager might be (erroneously) continuing to pass keystrokes to the "current" (i.e. old) window after the mouse moves into the new window. I'm assuming here that the window manager is able to receive mouse-move and keyboard events in a single stream, or timestamped, or otherwise marked so they can be processed in the order they originally occurred. Or maybe Xorg does not keep them in order or doesn't allow the window- manager to know their relative order. Or maybe keystrokes are going directly to the old window without filtering for the current mouse position (if this is the case, then IMO xorg should be told to stop delivering keystrokes if the mouse is outside a specified region until the window-manager tells it to resume delivery; or some similar way to allow the focus-change to occur firs
[Touch-packages] [Bug 1814839] Re: keystrokes go to wrong window immediately after moving mouse to change window focus
** Description changed: Ubuntu 18.04. Gnome X11 session. When window focus policy is set to follow the mouse, then if the mouse is moved into a new window and keystrokes typed immediately afterwards, the keystrokes go to the old window (invariably causing application errors). This is extremely annoying for rapid-fire developers, who for example run vim in one window to edit a script and bash in another to test the script; the sequence 1) save changes in vim; 2) move mouse to the bash window; 3) type the command to run the script results in the shell command (or part of it) being received by vim in the old window (with occasionally-entertaining effects). It seems like mouse-movement events are not kept in-order with respect to keyboard events. I can see the mouse pointer move to the new window before I type on the keyboard, so I know the mouse-move events have been received before the keystrokes. Speculations: This might be a window-manager bug: Although the mouse cursor has moved before I type, the window borders may not yet have changed to indicate a changed focus (not certain because the sequence is so quick). Therefore the window manager might be (erroneously) continuing to pass keystrokes to the "current" (i.e. old) window after the mouse moves into the new window. I'm assuming here that the window manager is able to receive mouse-move and keyboard events in a single stream, or timestamped, or otherwise marked so they can be processed in the order they originally occurred. Or maybe Xorg does not keep them in order or doesn't allow the window- - manager to know their relative order. Or something. + manager to know their relative order. Or maybe keystrokes are going + directly to the old window without filtering for the current mouse + position (if this is the case, then IMO xorg should be told to stop + delivering keystrokes if the mouse is outside a specified region until + the window-manager tells it to resume delivery; or some similar way to + allow the focus-change to occur first). STEPS TO REPRODUCE: 1. Run gnome-tweaks, set Windows->Window Focus to "Sloppy" 2. Open two vertically-adjacent gnome-terminal windows 3. Put cursor in the top window. Wait 2 seconds. 4. Move mouse (with one hand) rapidly into the other window, then (immediately) type a character into the other window (with the other hand) ACTUAL RESULTS: The keystroke appears in the old window EXPECTED RESULTS: Keystroke appears in the new window (i.e. the keystroke is not processed at all until the window manager completes the - focus change). + focus change). In other words, "typeahead" should encompass both + keystrokes and mouse movements. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814839 Title: keystrokes go to wrong window immediately after moving mouse to change window focus Status in xorg package in Ubuntu: New Bug description: Ubuntu 18.04. Gnome X11 session. When window focus policy is set to follow the mouse, then if the mouse is moved into a new window and keystrokes typed immediately afterwards, the keystrokes go to the old window (invariably causing application errors). This is extremely annoying for rapid-fire developers, who for example run vim in one window to edit a script and bash in another to test the script; the sequence 1) save changes in vim; 2) move mouse to the bash window; 3) type the command to run the script results in the shell command (or part of it) being received by vim in the old window (with occasionally-entertaining effects). It seems like mouse-movement events are not kept in-order with respect to keyboard events. I can see the mouse pointer move to the new window before I type on the keyboard, so I know the mouse-move events have been received before the keystrokes. Speculations: This might be a window-manager bug: Although the mouse cursor has moved before I type, the window borders may not yet have changed to indicate a changed focus (not certain because the sequence is so quick). Therefore the window manager might be (erroneously) continuing to pass keystrokes to the "current" (i.e. old) window after the mouse moves into the new window. I'm assuming here that the window manager is able to receive mouse-move and keyboard events in a single stream, or timestamped, or otherwise marked so they can be processed in the order they originally occurred. Or maybe Xorg does not keep them in order or doesn't allow the window- manager to know their relative order. Or maybe keystrokes are going directly to the old window without filtering for the current mouse position (if this is the case, then IMO xorg should be told to stop delivering keystrokes if the mouse is outside a specified region until the w
[Touch-packages] [Bug 1814611] Re: ubuntu-bug never (any longer) opens browser window
x not z -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814611] Re: ubuntu-bug never (any longer) opens browser window
xdg-open http://bugs.launchpad.net opens the page in Firefox. I use zdg-open routinely. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window Status in apport package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.1 LTS, X11 gnome session. For some reason ubuntu-bug no longer opens a browser window, so it is not possible to enter useful bug detauls, or even know the bug number. After prompting whether or not to Send the report, clicking "Send" just closes appport and nothing else ever happens. The exit status of "ubuntu-bug" is zero. This worked fine before, but it has been many months since I tried to submit a bug. strace shows many stat calls on plausible browser paths, including the one that is correct (/usr/bin/firefox, which returned a successful stat call). I'll attach the trace output from strace -f -o /tmp/strace.log ubuntu-bug apport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814613] Re: qmlscene -style material file.qml says "QApplication: invalid style override passed"
Upstream bug: https://bugreports.qt.io/browse/QTBUG-73818 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1814613 Title: qmlscene -style material file.qml says "QApplication: invalid style override passed" Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: qmlscene -qt=5 -style material file.qml prints QApplication: invalid style override passed, ignoring it. on the terminal. This does not happen when using the environment variable method, e.g. QT_QUICK_CONTROLS_STYLE=material qmlscene -qt=5 file.qml The documentation for how this is supposed to work is at https://doc.qt.io/qt-5/qtquickcontrols2-styles.html#using-styles-in-qt-quick-controls-2 I'm reporting this to ubuntu because it might be due to packaging or patching done for Ubuntu. I can not conveniently try a pristine upstream version of Qt, so hoping the Qt Ubuntu maintainer can quickly determine if this is an upstream bug or not. I'll attach a trivial test file which demonstrates the problem STEPS TO REPRODUCE: qmlscene -style material test.qml # test.qml attached ACTUAL RESULTS: Prints warning about invalid style on the terminal EXPECTED RESULTS: Silent obedience To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1814613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738144] [NEW] Monitor locked to low-res when using EFI/Secure Boot on Coffee Lake
Public bug reported: Booting with EFI, as opposed to legacy BIOS booting, somehow prevents detecting the resolutions supported by a VESA-compliant monitor; instead a single low resolution mode is used, and no other choices are available in the "Displays" setting dialog. At least that's what happens using built-in Intel graphics on a i7-8700K / Z370 (Coffee Lake), with a 1920x1200 DVI monitor. This effectively prevents enabling Secure Boot with Ubuntu on this platform. I don't know if older hardware has the same problem (this is the first UEFI-capable system I've owned) The problem is visible when booting from the installer DVD in "try Ubuntu" mode (the install DVDs are set up to boot either way). If you boot in EFI mode, the desktop comes up at 1024x768. But if you boot in legacy BIOS mode, it comes up normally (1920x1200 in my case). Ditto for installed systems. STEPS TO REPRODUCE: 1. Go out and buy a new Coffee Lake system with ASUS Z370-A PRIME motherboard and i7-8700K cpu 2. Enable Secure Boot in the "bios" (disable legacy booting) 3. Boot the 17.10 or 16.04 Ubuntu Desktop DVD in "try Ubuntu" mode RESULTS: Resolution abnormally low, and can not be changed 4. Turn off Secure Boot and enable legacy or "Compatibility" support (CSM in ASUS-speak). 5. Boot the same Desktop installer DVD RESULTS: Normal resolution Installing in legacy BIOS mode is a work-around, but preventing use of Secure Boot is a security problem (the system is potentially vulnerable to bootstrap malware) ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1738144 Title: Monitor locked to low-res when using EFI/Secure Boot on Coffee Lake Status in upstart package in Ubuntu: New Bug description: Booting with EFI, as opposed to legacy BIOS booting, somehow prevents detecting the resolutions supported by a VESA-compliant monitor; instead a single low resolution mode is used, and no other choices are available in the "Displays" setting dialog. At least that's what happens using built-in Intel graphics on a i7-8700K / Z370 (Coffee Lake), with a 1920x1200 DVI monitor. This effectively prevents enabling Secure Boot with Ubuntu on this platform. I don't know if older hardware has the same problem (this is the first UEFI-capable system I've owned) The problem is visible when booting from the installer DVD in "try Ubuntu" mode (the install DVDs are set up to boot either way). If you boot in EFI mode, the desktop comes up at 1024x768. But if you boot in legacy BIOS mode, it comes up normally (1920x1200 in my case). Ditto for installed systems. STEPS TO REPRODUCE: 1. Go out and buy a new Coffee Lake system with ASUS Z370-A PRIME motherboard and i7-8700K cpu 2. Enable Secure Boot in the "bios" (disable legacy booting) 3. Boot the 17.10 or 16.04 Ubuntu Desktop DVD in "try Ubuntu" mode RESULTS: Resolution abnormally low, and can not be changed 4. Turn off Secure Boot and enable legacy or "Compatibility" support (CSM in ASUS-speak). 5. Boot the same Desktop installer DVD RESULTS: Normal resolution Installing in legacy BIOS mode is a work-around, but preventing use of Secure Boot is a security problem (the system is potentially vulnerable to bootstrap malware) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1738144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738307] [NEW] Can not move icons in dash
Public bug reported: The icons in the new 17.10 dash side-bar can not be re-arranged. You can left-click and drag them sideways and then vertically to a new position, but when you un-click the icon snaps back to it's original position. In Ubuntu 11.10 this apparently worked in gnome-shell: There are instructions and a short video animation here: https://askubuntu.com/questions/87629/how-to-drag-and-move-icons-in- the-gnome-shell-favourites-bar That animation shows the other icons moving out of the way so that the one being dragged has a place to land. But in Ubuntu 17.10 the other icons don't move at all. Even dragging to empty space below all existing icons does not work (the dragged icon still snaps back). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dash 0.5.8-2.3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 17:02:39 2017 InstallationDate: Installed on 2017-12-13 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dash (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug artful ** Description changed: - The icons in the dash side-bar can not be re-arranged. You can left- - click and drag them sideways and then vertically to a new position, but - when you un-click the icon snaps back to it's original position. + The icons in the new 17.10 dash side-bar can not be re-arranged. You + can left-click and drag them sideways and then vertically to a new + position, but when you un-click the icon snaps back to it's original + position. In Ubuntu 11.10 this apparently worked in gnome-shell: There are instructions and a short video animation here: - https://askubuntu.com/questions/87629/how-to-drag-and-move-icons-in- + https://askubuntu.com/questions/87629/how-to-drag-and-move-icons-in- the-gnome-shell-favourites-bar That animation shows the other icons moving out of the way so that the one being dragged has a place to land. But in Ubuntu 17.10 the other icons don't move at all. Even dragging to empty space below all existing icons does not work (the dragged icon still snaps back). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dash 0.5.8-2.3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 17:02:39 2017 InstallationDate: Installed on 2017-12-13 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: dash (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1738307 Title: Can not move icons in dash Status in dash package in Ubuntu: Invalid Bug description: The icons in the new 17.10 dash side-bar can not be re-arranged. You can left-click and drag them sideways and then vertically to a new position, but when you un-click the icon snaps back to it's original position. In Ubuntu 11.10 this apparently worked in gnome-shell: There are instructions and a short video animation here: https://askubuntu.com/questions/87629/how-to-drag-and-move-icons-in- the-gnome-shell-favourites-bar That animation shows the other icons moving out of the way so that the one being dragged has a place to land. But in Ubuntu 17.10 the other icons don't move at all. Even dragging to empty space below all existing icons does not work (the dragged icon still snaps back). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dash 0.5.8-2.3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 17:02:39 2017 InstallationDate: Installed on 2017-12-13 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1738307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738307] Re: Can not move icons in dash
Now this is strange. I used Settings->Dock to fiddle with the doc, changing it's size and moving it to the bottom and back to the left side (no net change). Lo and behold, miving the icons now works! So maybe this is a one-time glitch. I upgraded, so there is Unity cruft in my environment. -> If anyone else observes the problem, please click the "affects me" button at top left. Let's see if I'm the only one. For now, setting Status to Invalid. P.S. I do live in California but have not been smoking anything anything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dash in Ubuntu. https://bugs.launchpad.net/bugs/1738307 Title: Can not move icons in dash Status in dash package in Ubuntu: Invalid Bug description: The icons in the new 17.10 dash side-bar can not be re-arranged. You can left-click and drag them sideways and then vertically to a new position, but when you un-click the icon snaps back to it's original position. In Ubuntu 11.10 this apparently worked in gnome-shell: There are instructions and a short video animation here: https://askubuntu.com/questions/87629/how-to-drag-and-move-icons-in- the-gnome-shell-favourites-bar That animation shows the other icons moving out of the way so that the one being dragged has a place to land. But in Ubuntu 17.10 the other icons don't move at all. Even dragging to empty space below all existing icons does not work (the dragged icon still snaps back). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: dash 0.5.8-2.3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 14 17:02:39 2017 InstallationDate: Installed on 2017-12-13 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1738307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738673] [NEW] deluser --backup fails because tar --no-unquote option should be used
Public bug reported: deluser --backup --remove-home (or --remove-all-files) USER aborts if it encounters certain file names, for example the ubiquitous 'C:\nppdf32Log\debuglog.txt' left in Linux home directories by Firefox. The root cause is that 'tar' helpfully "interprets escape sequences" in its filename arguments, so file names containing a backslash followed by 'n' are changed to contain a newline character, and other similar cases. The tar --no-unquote option prevents this. So 'deluser' should pass --no-unquote to 'tar' when creating the backup archive. I'll attach a demo/regression-test script, but in brief: STEPS TO REPRODUCE: 1. touch '/home/testuser/C:\nppdf32Log\debuglog.txt' 2. deluser --backup --remove-home testuser RESULTS: /bin/tar: /home/.../C\:\nppdf32Log\\debuglog.txt: Cannot stat: No such file or directory (deluser aborts without doing anything except creating an empty archive file) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: adduser 3.113+nmu3ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 17 15:20:16 2017 InstallationDate: Installed on 2017-12-13 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: adduser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: adduser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1738673 Title: deluser --backup fails because tar --no-unquote option should be used Status in adduser package in Ubuntu: New Bug description: deluser --backup --remove-home (or --remove-all-files) USER aborts if it encounters certain file names, for example the ubiquitous 'C:\nppdf32Log\debuglog.txt' left in Linux home directories by Firefox. The root cause is that 'tar' helpfully "interprets escape sequences" in its filename arguments, so file names containing a backslash followed by 'n' are changed to contain a newline character, and other similar cases. The tar --no-unquote option prevents this. So 'deluser' should pass --no-unquote to 'tar' when creating the backup archive. I'll attach a demo/regression-test script, but in brief: STEPS TO REPRODUCE: 1. touch '/home/testuser/C:\nppdf32Log\debuglog.txt' 2. deluser --backup --remove-home testuser RESULTS: /bin/tar: /home/.../C\:\nppdf32Log\\debuglog.txt: Cannot stat: No such file or directory (deluser aborts without doing anything except creating an empty archive file) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: adduser 3.113+nmu3ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 17 15:20:16 2017 InstallationDate: Installed on 2017-12-13 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: adduser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1738673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738673] Re: deluser --backup fails because tar --no-unquote option should be used
** Attachment added: "Demo/regression-test script" https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1738673/+attachment/5023900/+files/deluser_backup_test.sh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1738673 Title: deluser --backup fails because tar --no-unquote option should be used Status in adduser package in Ubuntu: New Bug description: deluser --backup --remove-home (or --remove-all-files) USER aborts if it encounters certain file names, for example the ubiquitous 'C:\nppdf32Log\debuglog.txt' left in Linux home directories by Firefox. The root cause is that 'tar' helpfully "interprets escape sequences" in its filename arguments, so file names containing a backslash followed by 'n' are changed to contain a newline character, and other similar cases. The tar --no-unquote option prevents this. So 'deluser' should pass --no-unquote to 'tar' when creating the backup archive. I'll attach a demo/regression-test script, but in brief: STEPS TO REPRODUCE: 1. touch '/home/testuser/C:\nppdf32Log\debuglog.txt' 2. deluser --backup --remove-home testuser RESULTS: /bin/tar: /home/.../C\:\nppdf32Log\\debuglog.txt: Cannot stat: No such file or directory (deluser aborts without doing anything except creating an empty archive file) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: adduser 3.113+nmu3ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 17 15:20:16 2017 InstallationDate: Installed on 2017-12-13 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: adduser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1738673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1740214] [NEW] Ubuntu patch to perl causes problem
Public bug reported:
Ubuntu patched perl to work around a libc compatibility issue, but there
is a problem.
Please see the perl bug report at
https://rt.perl.org/Public/Bug/Display.html?id=132631
Here is an excerpt from the linked-to perl bug:
...the relevant Ubuntu change:
http://deriv.debian.net/patches/p/perl/Debian_perl_5.26.0-8_Ubuntu_perl_5.26.0-8ubuntu1.debian.patch
Ubuntu's adding zero to SIG_NUM looks wrong and the probable cause of this bug
to me.
SIGUNUSED is 31 (alias for SIGSYS) on at least all the Debian architectures
where it exists
in the first place, and Perl_magic_setsig() gives the warning reported here
('No such signal')
when the signal number is zero or negative. So I think this can only be fixed
in Ubuntu,
and presumably somebody needs to file a Ubuntu bug for that to happen.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: perl 5.26.0-8ubuntu1 [modified: usr/bin/perldoc]
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 26 19:34:01 2017
InstallationDate: Installed on 2017-12-13 (13 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: perl
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: perl (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1740214
Title:
Ubuntu patch to perl causes problem
Status in perl package in Ubuntu:
New
Bug description:
Ubuntu patched perl to work around a libc compatibility issue, but
there is a problem.
Please see the perl bug report at
https://rt.perl.org/Public/Bug/Display.html?id=132631
Here is an excerpt from the linked-to perl bug:
...the relevant Ubuntu change:
http://deriv.debian.net/patches/p/perl/Debian_perl_5.26.0-8_Ubuntu_perl_5.26.0-8ubuntu1.debian.patch
Ubuntu's adding zero to SIG_NUM looks wrong and the probable cause of this
bug to me.
SIGUNUSED is 31 (alias for SIGSYS) on at least all the Debian architectures
where it exists
in the first place, and Perl_magic_setsig() gives the warning reported here
('No such signal')
when the signal number is zero or negative. So I think this can only be fixed
in Ubuntu,
and presumably somebody needs to file a Ubuntu bug for that to happen.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: perl 5.26.0-8ubuntu1 [modified: usr/bin/perldoc]
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 26 19:34:01 2017
InstallationDate: Installed on 2017-12-13 (13 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: perl
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1740214/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1102282] Re: Image OMITTED from pdf printed with lpr (works with acroread)
I no longer have a postscript printer, so don't know if this is still a problem. Since nobody else reported this, I guess it's best to close as invalid. ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1102282 Title: Image OMITTED from pdf printed with lpr (works with acroread) Status in cups package in Ubuntu: Invalid Bug description: Images in certain PDF files are missing when printed using "lpr test.pdf" to a postscript level 2 printer (hp3030). The image is not missing when printed through acroread to the same printer. I'll attach a test pdf. The "circle of hands" image is missing when printed using lpr ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups-bsd 1.5.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu15.1 Architecture: amd64 Date: Sun Jan 20 20:11:38 2013 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for hp-LaserJet-3030: hp:/usb/hp_LaserJet_3030?serial=00CNBM066305 device for hp-LaserJet-3030-Fax: hpfax:/usb/hp_LaserJet_3030?serial=00CNBM066305 device for PDF: cups-pdf:/ MachineType: System manufacturer System Product Name MarkForUpload: True Papersize: letter PpdFiles: hp-LaserJet-3030: HP LaserJet 3020 3030 Postscript (recommended) PDF: Generic CUPS-PDF Printer hp-LaserJet-3030-Fax: HP Fax hpcups ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=8aaca318-f079-4a4f-95c0-735aa54bed2d ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to precise on 2012-08-10 (163 days ago) dmi.bios.date: 09/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1408:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1102282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1486445] Re: Lots of zeitgeist errors
Also happening in 17.04 zeitgeist-datahub.vala:210: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required etc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1486445 Title: Lots of zeitgeist errors Status in Zeitgeist Datahub: Confirmed Status in zeitgeist package in Ubuntu: Confirmed Bug description: $ cat /var/log/syslog shows me lots of zeitgeist-related errors. My system is behaving weird lately since the upgrade from Ubuntu 14.10 to 15.04 so I am guessing this might be related. Alright, here the relevant log entries: Aug 19 19:31:49 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: zeitgeist-datahub.vala:212: Error during inserting events: GDBus.Error:org.gnome.zeitgeist.EngineError.InvalidArgument: Incomplete event: interpretation, manifestation and actor are required ... Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/.config/sublime-text-3/Projects/seeflow_live.sublime-project" was not found, exec: sublime_text, mime_type: application/octet-stream Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/binarykitchen/code/videomail.io/etc/ssl-certs/local/fake.crt" was not found, exec: google-chrome-stable, mime_type: application/pkix-cert Aug 19 20:25:14 M1 org.gnome.zeitgeist.Engine[25838]: ** (zeitgeist-datahub:26262): WARNING **: recent-manager-provider.vala:132: Desktop file for "file:///home/michael-heuberger/binarykitchen/code/webcamjs/demos/flash.html" was not found, exec: google-chrome-stable, mime_type: application/x-extension-html ... Aug 19 20:34:30 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop Aug 19 20:37:47 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: message repeated 2 times: [ ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop] ... Aug 19 20:38:52 M1 org.gnome.zeitgeist.SimpleIndexer[25838]: ** (zeitgeist-fts:26260): WARNING **: Unable to get info on application://gnome-terminal-server.desktop Any clues how to fix all that? To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist-datahub/+bug/1486445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1504688] Re: fsck runs on every boot (clean install, single ext4 filesystem)
Hello "A" (for Anonymous...?), I did not debug the problem, only filed the bug report. Are you a developer? On 10/31/2015 11:27 PM, A. wrote: > Any ideas why this happening? > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1504688 Title: fsck runs on every boot (clean install, single ext4 filesystem) Status in upstart package in Ubuntu: Confirmed Bug description: fsck runs early on *every* boot (and always says "/dev/sda1: clean ...") The system was always shut down using the regular Unity mechanism (Gear->Shut Down...) Strangely, the "Last checked" time shown by "sudo dumpe2fs /dev/sda1" shows the date of installation and never changes. This system is a brand new, clean install from the 15.10 beta2 iso, with subsequent updates. I took all the installer defaults, which created a single ext4 file system. Please see attached: bootscreen.png - screen shot of fsck output at start of bootup (from VM window) dumpe2fs_out.txt - output from "sudo dumpe2fs /dev/sda1" ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: upstart 1.13.2-0ubuntu16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 15:10:05 2015 InstallationDate: Installed on 2015-10-07 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=5944d29d-f058-4836-a160-4da2d77554e3 ro quiet splash SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemJobs: Error: command ['initctl', '--system', 'list'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1504688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504688] [NEW] fsck runs on every boot (clean install, single ext4 filesystem)
Public bug reported: fsck runs early on *every* boot (and always says "/dev/sda1: clean ...") The system was always shut down using the regular Unity mechanism (Gear->Shut Down...) Strangely, the "Last checked" time shown by "sudo dumpe2fs /dev/sda1" shows the date of installation and never changes. This system is a brand new, clean install from the 15.10 beta2 iso, with subsequent updates. I took all the installer defaults, which created a single ext4 file system. Please see attached: bootscreen.png - screen shot of fsck output at start of bootup (from VM window) dumpe2fs_out.txt - output from "sudo dumpe2fs /dev/sda1" ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: upstart 1.13.2-0ubuntu16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 15:10:05 2015 InstallationDate: Installed on 2015-10-07 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=5944d29d-f058-4836-a160-4da2d77554e3 ro quiet splash SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemJobs: Error: command ['initctl', '--system', 'list'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "dumpe2fs_out.txt" https://bugs.launchpad.net/bugs/1504688/+attachment/4490204/+files/dumpe2fs_out.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1504688 Title: fsck runs on every boot (clean install, single ext4 filesystem) Status in upstart package in Ubuntu: New Bug description: fsck runs early on *every* boot (and always says "/dev/sda1: clean ...") The system was always shut down using the regular Unity mechanism (Gear->Shut Down...) Strangely, the "Last checked" time shown by "sudo dumpe2fs /dev/sda1" shows the date of installation and never changes. This system is a brand new, clean install from the 15.10 beta2 iso, with subsequent updates. I took all the installer defaults, which created a single ext4 file system. Please see attached: bootscreen.png - screen shot of fsck output at start of bootup (from VM window) dumpe2fs_out.txt - output from "sudo dumpe2fs /dev/sda1" ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: upstart 1.13.2-0ubuntu16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 15:10:05 2015 InstallationDate: Installed on 2015-10-07 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=5944d29d-f058-4836-a160-4da2d77554e3 ro quiet splash SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemJobs: Error: command ['initctl', '--system', 'list'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1504688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504688] Re: fsck runs on every boot (clean install, single ext4 filesystem)
** Attachment added: "Screenshot of boot screen (in Virtual Machine)" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1504688/+attachment/4490209/+files/bootscreen.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1504688 Title: fsck runs on every boot (clean install, single ext4 filesystem) Status in upstart package in Ubuntu: New Bug description: fsck runs early on *every* boot (and always says "/dev/sda1: clean ...") The system was always shut down using the regular Unity mechanism (Gear->Shut Down...) Strangely, the "Last checked" time shown by "sudo dumpe2fs /dev/sda1" shows the date of installation and never changes. This system is a brand new, clean install from the 15.10 beta2 iso, with subsequent updates. I took all the installer defaults, which created a single ext4 file system. Please see attached: bootscreen.png - screen shot of fsck output at start of bootup (from VM window) dumpe2fs_out.txt - output from "sudo dumpe2fs /dev/sda1" ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: upstart 1.13.2-0ubuntu16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 9 15:10:05 2015 InstallationDate: Installed on 2015-10-07 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=5944d29d-f058-4836-a160-4da2d77554e3 ro quiet splash SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemJobs: Error: command ['initctl', '--system', 'list'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist UpstartRunningSystemVersion: Error: command ['initctl', '--system', 'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1504688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720019] [NEW] org.PulseAudio1 was not provided by any .service files
Public bug reported: Whenever a program starts which uses audio many errors appear in syslog like these: indicator-sound[1922]: message repeated 15 times: [ volume-control- pulse.vala:735: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files] unity-panel-ser[2249]: track_menus: assertion 'IS_WINDOW_MENU(menus)' failed Sep 27 14:46:23 lxjima indicator-sound[1922]: volume-control-pulse.vala:735: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files STEPS TO REPRODUCE: 1. tail -f /var/log/syslog (in another terminal). 2. Start firefox, chromium, or audacity ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Wed Sep 27 14:48:15 2017 InstallationDate: Installed on 2017-01-19 (251 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to zesty on 2017-07-26 (63 days ago) dmi.bios.date: 09/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1408:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720019 Title: org.PulseAudio1 was not provided by any .service files Status in pulseaudio package in Ubuntu: New Bug description: Whenever a program starts which uses audio many errors appear in syslog like these: indicator-sound[1922]: message repeated 15 times: [ volume-control- pulse.vala:735: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files] unity-panel-ser[2249]: track_menus: assertion 'IS_WINDOW_MENU(menus)' failed Sep 27 14:46:23 lxjima indicator-sound[1922]: volume-control-pulse.vala:735: unable to get pulse unix socket: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.PulseAudio1 was not provided by any .service files STEPS TO REPRODUCE: 1. tail -f /var/log/syslog (in another terminal). 2. Start firefox, chromium, or audacity ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7 Date: Wed Sep 27 14:48:15 2017 InstallationDate: Installed on 2017-01-19 (251 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to zesty on 2017-07-26 (63 days ago) dmi.bios.date: 09/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T dmi.board.vendor: ASUSTeK Computer INC. dmi
[Touch-packages] [Bug 1679789] [NEW] Trailing slash missing from Dir::Cache in apt configuration
Public bug reported:
The apt configuration database has some incompatible changes which break
existing scripts. It is not obvious that this was deliberate (I hope
not).
Prior to 16.10, the configured cache directory path(s) included a
trailing slash. Now they do not include the trailing slash. This
breaks existing scripts which combine bits from the configuration
database.
In 16.04:
$ apt-config shell D Dir C Dir::Cache F Dir::Cache::pkgcache
D='/'
C='var/cache/apt/'
F='pkgcache.bin'
So if this output is eval'd in the shell, then
path=${D}${C}${F} produces "/var/cache/apt/pkgcache.bin"
However in 16.10:
$ apt-config shell D Dir C Dir::Cache F Dir::Cache::pkgcache
D='/'
C='var/cache/apt'
F='pkgcache.bin'
So existing shell code now breaks
path=${D}${C}${F} produces "/var/cache/aptpkgcache.bin"
If this was a mistake, please fix ASAP.
If it was on purpose, please post (a link to) an explanation.
Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apt 1.3.4
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 4 10:33:13 2017
InstallationDate: Installed on 2016-05-06 (332 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160506)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug yakkety
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1679789
Title:
Trailing slash missing from Dir::Cache in apt configuration
Status in apt package in Ubuntu:
New
Bug description:
The apt configuration database has some incompatible changes which
break existing scripts. It is not obvious that this was deliberate (I
hope not).
Prior to 16.10, the configured cache directory path(s) included a
trailing slash. Now they do not include the trailing slash. This
breaks existing scripts which combine bits from the configuration
database.
In 16.04:
$ apt-config shell D Dir C Dir::Cache F Dir::Cache::pkgcache
D='/'
C='var/cache/apt/'
F='pkgcache.bin'
So if this output is eval'd in the shell, then
path=${D}${C}${F} produces "/var/cache/apt/pkgcache.bin"
However in 16.10:
$ apt-config shell D Dir C Dir::Cache F Dir::Cache::pkgcache
D='/'
C='var/cache/apt'
F='pkgcache.bin'
So existing shell code now breaks
path=${D}${C}${F} produces "/var/cache/aptpkgcache.bin"
If this was a mistake, please fix ASAP.
If it was on purpose, please post (a link to) an explanation.
Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apt 1.3.4
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 4 10:33:13 2017
InstallationDate: Installed on 2016-05-06 (332 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160506)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1679789/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1679789] Re: Trailing slash missing from Dir::Cache in apt configuration
Thanks for the clarification. I had completely missed the /d and /f
functionality.
Sorry for the bogus bugrep.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1679789
Title:
Trailing slash missing from Dir::Cache in apt configuration
Status in apt package in Ubuntu:
Invalid
Bug description:
The apt configuration database has some incompatible changes which
break existing scripts. It is not obvious that this was deliberate (I
hope not).
Prior to 16.10, the configured cache directory path(s) included a
trailing slash. Now they do not include the trailing slash. This
breaks existing scripts which combine bits from the configuration
database.
In 16.04:
$ apt-config shell D Dir C Dir::Cache F Dir::Cache::pkgcache
D='/'
C='var/cache/apt/'
F='pkgcache.bin'
So if this output is eval'd in the shell, then
path=${D}${C}${F} produces "/var/cache/apt/pkgcache.bin"
However in 16.10:
$ apt-config shell D Dir C Dir::Cache F Dir::Cache::pkgcache
D='/'
C='var/cache/apt'
F='pkgcache.bin'
So existing shell code now breaks
path=${D}${C}${F} produces "/var/cache/aptpkgcache.bin"
If this was a mistake, please fix ASAP.
If it was on purpose, please post (a link to) an explanation.
Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apt 1.3.4
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 4 10:33:13 2017
InstallationDate: Installed on 2016-05-06 (332 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160506)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1679789/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1658556] [NEW] watch -c --differences=permanent misbehaves (highlights everything)
Public bug reported:
If the watch -c and --differences=permanent options are combined, then
upon the first update _every_ character is highlighted even if nothing
has ever changed.
It appears that -c ("Interpret ANSI color and style sequences") tickles
a bug in the persistence logic. Regular non-permanent highlighting
(with option -d) works okay with -c.
STEPS TO REPRODUCE:
1. /usr/bin/watch -c --differences=permanent -n 1 echo This never
changes
RESULTS: After one second all output is highlighted
EXPECTED RESULTS: No highlighting until something changes
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: procps 2:3.3.10-4ubuntu2.3
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jan 22 17:35:09 2017
InstallationDate: Installed on 2013-08-06 (1266 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: procps
UpgradeStatus: Upgraded to xenial on 2016-05-11 (257 days ago)
** Affects: procps (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug third-party-packages xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1658556
Title:
watch -c --differences=permanent misbehaves (highlights everything)
Status in procps package in Ubuntu:
New
Bug description:
If the watch -c and --differences=permanent options are combined, then
upon the first update _every_ character is highlighted even if nothing
has ever changed.
It appears that -c ("Interpret ANSI color and style sequences")
tickles a bug in the persistence logic. Regular non-permanent
highlighting (with option -d) works okay with -c.
STEPS TO REPRODUCE:
1. /usr/bin/watch -c --differences=permanent -n 1 echo This never
changes
RESULTS: After one second all output is highlighted
EXPECTED RESULTS: No highlighting until something changes
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: procps 2:3.3.10-4ubuntu2.3
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
Uname: Linux 4.4.0-62-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jan 22 17:35:09 2017
InstallationDate: Installed on 2013-08-06 (1266 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: procps
UpgradeStatus: Upgraded to xenial on 2016-05-11 (257 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1658556/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671977] [NEW] Inconsistent splitting of results of $(Command Substitution)
Public bug reported:
The man page says, under "Word Expansions", that output from Command
Substitution will be later split into fields (unless IFS is null).
Therefore the statement
foo=$(echo xxx bar=yyy)
should expand to
foo=xxx bar=yyy
and when executed, set two variables foo and bar.
However dash does not do this. Instead, the Command Substitution output
is not split, and the result is the same as
foo="xxx bar=yyy"
which sets a single variable.
HOWEVER, inside a function, dash *does* split the result of Command
Substitution if it is part of a 'local' variable declaration.
This seems inconsistent: One or the other case must be a bug.
Comment: Despite what the man says, splitting Command Substitution
results is probably not desirable and would be incompatible with bash
(which AFAIK never splits Command Subst output). I can't say what POSIX
mandates about this.
#!/usr/bin/env dash
func() {
echo "IFS='$IFS'"
gvar=$(echo "11 y=22")
local lvar=$(echo "33 z=44")
echo "gvar=$gvar"
echo "y=$y"
echo "lvar=$lvar"
echo "z=$z"
}
func
# RESULTS:
#
# IFS='
# '
# gvar=11 y=22
# y=
# lvar=33
# z=44
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dash 0.5.8-2.1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 10 16:33:07 2017
InstallationDate: Installed on 2017-01-19 (50 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: dash
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: dash (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1671977
Title:
Inconsistent splitting of results of $(Command Substitution)
Status in dash package in Ubuntu:
New
Bug description:
The man page says, under "Word Expansions", that output from Command
Substitution will be later split into fields (unless IFS is null).
Therefore the statement
foo=$(echo xxx bar=yyy)
should expand to
foo=xxx bar=yyy
and when executed, set two variables foo and bar.
However dash does not do this. Instead, the Command Substitution
output is not split, and the result is the same as
foo="xxx bar=yyy"
which sets a single variable.
HOWEVER, inside a function, dash *does* split the result of Command
Substitution if it is part of a 'local' variable declaration.
This seems inconsistent: One or the other case must be a bug.
Comment: Despite what the man says, splitting Command Substitution
results is probably not desirable and would be incompatible with bash
(which AFAIK never splits Command Subst output). I can't say what
POSIX mandates about this.
#!/usr/bin/env dash
func() {
echo "IFS='$IFS'"
gvar=$(echo "11 y=22")
local lvar=$(echo "33 z=44")
echo "gvar=$gvar"
echo "y=$y"
echo "lvar=$lvar"
echo "z=$z"
}
func
# RESULTS:
#
# IFS='
# '
# gvar=11 y=22
# y=
# lvar=33
# z=44
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dash 0.5.8-2.1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Mar 10 16:33:07 2017
InstallationDate: Installed on 2017-01-19 (50 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: dash
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1671977/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871260] [NEW] update-initramfs Error 24 (EMFILE? == Too many open files?)
Public bug reported: $ sudo apt-get dist-upgrade Fails with: Setting up linux-image-5.3.0-46-generic (5.3.0-46.38) ... Processing triggers for linux-image-5.3.0-46-generic (5.3.0-46.38) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.3.0-46-generic ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.3.0-46-generic I: The initramfs will attempt to resume from /dev/nvme1n1p3 I: (UUID=03bd380f-5d5c-433d-9047-0ca550fef461) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 If "Error 24" means errno==24 then it is EMFILE (Too many open files). Re-running produces an identical failure. There is nothing unusual going on in the machine. Just rebooted, actually. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jima 6601 F pulseaudio tu2 10212 F pulseaudio Date: Mon Apr 6 16:48:05 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-03-24 (13 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-45-generic root=UUID=7c21c040-30e8-456e-bcd9-5f4bcfc2fc92 ro toram priority=low quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-5.3.0-46-generic 5.3.0-46.38 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/01/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1871260 Title: update-initramfs Error 24 (EMFILE? == Too many open files?) Status in initramfs-tools package in Ubuntu: New Bug description: $ sudo apt-get dist-upgrade Fails with: Setting up linux-image-5.3.0-46-generic (5.3.0-46.38) ... Processing triggers for linux-image-5.3.0-46-generic (5.3.0-46.38) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.3.0-46-generic ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.3.0-46-generic I: The initramfs will attempt to resume from /dev/nvme1n1p3 I: (UUID=03bd380f-5d5c-433d-9047-0ca550fef461) I: Set the RESUME variable to override this. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 If "Error 24" means errno==24 then it is EMFILE (Too many open files). Re-running produces an identical failure. There is nothing unusual going on in the machine. Just rebooted, actually. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jima 6601 F pulseaudio tu2 10212 F pulseaudio Date: Mon Apr 6 16:48:05 2020 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-03-24 (13 days
[Touch-packages] [Bug 1415256] Re: Errors entering single-user mode; hang going back to multiuser
** Attachment added: "Screenshot showing exiting single-user, until hang" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1415256/+attachment/4306890/+files/exiting_singleuser_screen.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1415256 Title: Errors entering single-user mode; hang going back to multiuser Status in upstart package in Ubuntu: New Bug description: Several wrong-looking messages appear when entering single-user mode, and when ^D is typed to exit the single-user shell, the system hangs trying to resume multi-user mode (the graphical login never apperas, nor does the virtual-terminal login prompt). I observed this testing with virtualbox. Haven't tried bare metal. I will attach two screenshots, one showing the entry into single-user mode, the second showing the attempted exit. But the bits which seemed relevant are reproduced below; STEPS TO REPRODUCE: 1. Log in as root from a virtual console (in virtualbox: -F1 and log in) 2. $ shutdown now # documented to enter single-user mode /lib/init/init-d-script: 2: /etc/default/whoopsie: [General]: not found ... ModemManager ... Caught signal, shutting down... ModemManager ... Could not acquire the 'org.freedesktop.Modemmanger1' service name 3. When prompted, enter root password ... 4. ^D (or type 'exit') ... /lib/init/init-d-script: 2: /etc/default/shoopsie: [General]: not found systemd-logind: Failed to start user service: Unknown unit: user@108.service systemd-logind: Failed to start user service: Unknown unit: user@0.service systemd-logind: Failed to start user service: Unknown unit: user@1000.service * Starting shoopsie shoopsie[fail] (HANGS) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu7 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 27 15:46:46 2015 InstallationDate: Installed on 2015-01-02 (25 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150102) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic root=UUID=96d674cd-12fb-4ad1-8d76-cffb545e6256 ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1415256/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415256] Re: Errors entering single-user mode; hang going back to multiuser
** Attachment added: "Screenshot showing warnings/errors entering single-user mode" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1415256/+attachment/4306889/+files/entering_singluser_screen.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1415256 Title: Errors entering single-user mode; hang going back to multiuser Status in upstart package in Ubuntu: New Bug description: Several wrong-looking messages appear when entering single-user mode, and when ^D is typed to exit the single-user shell, the system hangs trying to resume multi-user mode (the graphical login never apperas, nor does the virtual-terminal login prompt). I observed this testing with virtualbox. Haven't tried bare metal. I will attach two screenshots, one showing the entry into single-user mode, the second showing the attempted exit. But the bits which seemed relevant are reproduced below; STEPS TO REPRODUCE: 1. Log in as root from a virtual console (in virtualbox: -F1 and log in) 2. $ shutdown now # documented to enter single-user mode /lib/init/init-d-script: 2: /etc/default/whoopsie: [General]: not found ... ModemManager ... Caught signal, shutting down... ModemManager ... Could not acquire the 'org.freedesktop.Modemmanger1' service name 3. When prompted, enter root password ... 4. ^D (or type 'exit') ... /lib/init/init-d-script: 2: /etc/default/shoopsie: [General]: not found systemd-logind: Failed to start user service: Unknown unit: user@108.service systemd-logind: Failed to start user service: Unknown unit: user@0.service systemd-logind: Failed to start user service: Unknown unit: user@1000.service * Starting shoopsie shoopsie[fail] (HANGS) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu7 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 27 15:46:46 2015 InstallationDate: Installed on 2015-01-02 (25 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150102) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic root=UUID=96d674cd-12fb-4ad1-8d76-cffb545e6256 ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1415256/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415256] [NEW] Errors entering single-user mode; hang going back to multiuser
Public bug reported: Several wrong-looking messages appear when entering single-user mode, and when ^D is typed to exit the single-user shell, the system hangs trying to resume multi-user mode (the graphical login never apperas, nor does the virtual-terminal login prompt). I observed this testing with virtualbox. Haven't tried bare metal. I will attach two screenshots, one showing the entry into single-user mode, the second showing the attempted exit. But the bits which seemed relevant are reproduced below; STEPS TO REPRODUCE: 1. Log in as root from a virtual console (in virtualbox: -F1 and log in) 2. $ shutdown now # documented to enter single-user mode /lib/init/init-d-script: 2: /etc/default/whoopsie: [General]: not found ... ModemManager ... Caught signal, shutting down... ModemManager ... Could not acquire the 'org.freedesktop.Modemmanger1' service name 3. When prompted, enter root password ... 4. ^D (or type 'exit') ... /lib/init/init-d-script: 2: /etc/default/shoopsie: [General]: not found systemd-logind: Failed to start user service: Unknown unit: user@108.service systemd-logind: Failed to start user service: Unknown unit: user@0.service systemd-logind: Failed to start user service: Unknown unit: user@1000.service * Starting shoopsie shoopsie[fail] (HANGS) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu7 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 27 15:46:46 2015 InstallationDate: Installed on 2015-01-02 (25 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150102) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic root=UUID=96d674cd-12fb-4ad1-8d76-cffb545e6256 ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) ** Affects: upstart (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1415256 Title: Errors entering single-user mode; hang going back to multiuser Status in upstart package in Ubuntu: New Bug description: Several wrong-looking messages appear when entering single-user mode, and when ^D is typed to exit the single-user shell, the system hangs trying to resume multi-user mode (the graphical login never apperas, nor does the virtual-terminal login prompt). I observed this testing with virtualbox. Haven't tried bare metal. I will attach two screenshots, one showing the entry into single-user mode, the second showing the attempted exit. But the bits which seemed relevant are reproduced below; STEPS TO REPRODUCE: 1. Log in as root from a virtual console (in virtualbox: -F1 and log in) 2. $ shutdown now # documented to enter single-user mode /lib/init/init-d-script: 2: /etc/default/whoopsie: [General]: not found ... ModemManager ... Caught signal, shutting down... ModemManager ... Could not acquire the 'org.freedesktop.Modemmanger1' service name 3. When prompted, enter root password ... 4. ^D (or type 'exit') ... /lib/init/init-d-script: 2: /etc/default/shoopsie: [General]: not found systemd-logind: Failed to start user service: Unknown unit: user@108.service systemd-logind: Failed to start user service: Unknown unit: user@0.service systemd-logind: Failed to start user service: Unknown unit: user@1000.service * Starting shoopsie shoopsie[fail] (HANGS) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu7 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 27 15:46:46 2015 InstallationDate: Installed on 2015-01-02 (25 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150102) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic root=UUID=96d674cd-12fb-4ad1-8d76-cffb545e6256 ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1415256/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1035431] Re: bluetooth-wizard failed to connect to a keyboard(logitech)
Does not work for me. Running 14.10 with utopic-proposed enabled; an update installed gnome-bluetooth 3.8.2.1-0ubuntu9 amd64 Several errors were logged. It looks like an error occurs when starting discovery, before even attempting to pair with a device. And after attempting to pair, the usual "Invalid Parameters" error occurs AND a dbus error about a rejected message: 1. Clicked "Set up new device" in the bt applet syslog: bluetoothd[637]: Discovery session 0x7f9eb2d982c0 with :1.70 activated syslog: bluetoothd[637]: Unknown command complete for opcode 37 3. Selected a device in the list and clicked Next (the device was my Android 4.4 cellphone, which was set to be visible) syslog: bluetoothd[637]: Stopping discovery syslog: bluetoothd[637]: hci0: Cancel Pair Device (0x001a) failed: Invalid Parameters (0x0d) auth.log: dbus[601]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.73" (uid=2000 pid=5662 comm="bluetooth- wizard ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=637 comm="/usr/sbin/bluetoothd ") I'm using a usb bluetooth dongle. I've _never_ been able to use it with Ubuntu, so I suppose it could be a hardware problem. Even if that is so, the above errors looks like bugs to me, not legitimate diagnostics. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1035431 Title: bluetooth-wizard failed to connect to a keyboard(logitech) Status in GNOME Bluetooth: New Status in OEM Priority Project: In Progress Status in OEM Priority Project trusty series: New Status in bluez package in Ubuntu: Fix Released Status in gnome-bluetooth package in Ubuntu: Fix Released Status in bluez source package in Precise: Triaged Status in gnome-bluetooth source package in Precise: Triaged Status in bluez source package in Trusty: Fix Committed Status in gnome-bluetooth source package in Trusty: Fix Committed Bug description: [Impact] * Fixes issues connecting bluetooth devices using SSP (Simple Secure Pairing); which does include many newer bluetooth devices, especially keyboards. [Test Case] * Try to connect a bluetooth keyboard using the wizard; especially one of the following models: Logitech Bluetooth Keyboard K760 Logitech Bluetooth Keyboard K810 HP Bluetooth Keyboard K4000 [Regression Potential] * It must be ensured that keyboards that could already be paired successfully still work properly; specifically, especially for keyboards but for any other devices, that pairing still works despite changes to the SSP code. [Other Info] --- When I try to connect my bluetooth keyboard using bluetooth-wizard, it ever fails: ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760' failed: Authentication Failed This keyboard works fine with another computer under ubuntu 11.04. This keyboard works fine with this computer and Windows 7 (arghhh). This computer ubuntu 12.04 works fine with my bluetooth mouse. I can attach manually this keyboard to this computer using : sudo hidd --search My computer is a Samsung 305U1A My bluetooth interface is : Bus 003 Device 002: ID 0a5c:219c Broadcom Corp. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1035431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1228567] Re: at-spi2 daemon error messages in .xsession-errors
Still present in 14.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1228567 Title: at-spi2 daemon error messages in .xsession-errors Status in at-spi2-core package in Ubuntu: Confirmed Bug description: Sometimes I get the following messages in .xsession-errors init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd main process ended, respawning init: at-spi2-registryd respawning too fast, stopped I use a Lenovo Thinkpad Twist convertible with touch screen, using Onboard in tablet mode. Can perhaps have a relation with bug 1227173. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1228567/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 872483] Re: laser printer only prints first job correct
Is there a mechanism in place which will cause this "fix" to be removed when the underlying kernel issue is repaired? Resetting the usb port between jobs is an undesirable hack (e.g. slows down printing) so should go away as soon as possible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/872483 Title: laser printer only prints first job correct Status in cups package in Ubuntu: Fix Released Status in cups source package in Oneiric: Won't Fix Status in cups source package in Precise: Fix Released Bug description: please also refer to this bug - this seems to be exactly my issue and does not seem to be solved. https://bugs.launchpad.net/ubuntu/+source/foomatic-db/+bug/855412 ProblemType: Bug DistroRelease: Ubuntu 11.10 - all updates as of today applied. I followed https://wiki.ubuntu.com/DebuggingPrintingProblems according to https://bugs.launchpad.net/ubuntu/+source/foomatic- db/+bug/855412/comments/20 I printed two copies of the same document, since this forces the error easily. The content under /var/spool/cups/d... look fine - see attached files. after cupsenable the first copy comes out fine - the second as random character - I stopped after some pages. The test is with Samsung ML-2250 Series (SPL II) - which worked fine under all previous versions of Ubuntu Samsung ML-2250 Foomatic/pxlmono (recommended) generates basically the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/872483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374500] [NEW] F1 displays help for Gnome Terminal, not alsamixer
Public bug reported: alsamixer's display says F1 provided help. However, putting the cursor in the window and pressingt F1 pops up the Gnome Terminal manual. It appears that the terminal is grabbing F1 for it's own purposes. Either it shouldn't do that, or else alsamixer should somehow disable that or use a different key for it's help function. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-utils 1.0.27.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Sep 26 08:19:39 2014 InstallationDate: Installed on 2013-08-06 (416 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: alsa-utils UpgradeStatus: Upgraded to saucy on 2013-10-24 (336 days ago) ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1374500 Title: F1 displays help for Gnome Terminal, not alsamixer Status in “alsa-utils” package in Ubuntu: New Bug description: alsamixer's display says F1 provided help. However, putting the cursor in the window and pressingt F1 pops up the Gnome Terminal manual. It appears that the terminal is grabbing F1 for it's own purposes. Either it shouldn't do that, or else alsamixer should somehow disable that or use a different key for it's help function. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-utils 1.0.27.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Sep 26 08:19:39 2014 InstallationDate: Installed on 2013-08-06 (416 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: alsa-utils UpgradeStatus: Upgraded to saucy on 2013-10-24 (336 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1374500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1059872] Re: Error formatting disk using disk utility
Same story using the version in Ubuntu 14.10 (the package says it is
version 0.2.62 but usb-creator-gtk --version says it is 0.2.23):
Attempting to erase a USB which has no valid partition table gets "Timed
out waiting for object".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1059872
Title:
Error formatting disk using disk utility
Status in “udisks2” package in Ubuntu:
Invalid
Status in “util-linux” package in Ubuntu:
Fix Released
Status in “udisks2” source package in Trusty:
Invalid
Status in “util-linux” source package in Trusty:
Triaged
Status in “util-linux” package in Debian:
Fix Released
Bug description:
Formatting a SD card using the disk utility fails with an error
message
"Error formatting disk - Error synchronizing after initial wipe: Timed
out waiting for object (udisks-error-quark, 0)"
Steps to repro:
Launch the disk utility
Plug a SD card into the computer
Select the SD card and click on the gears icon at the top right of the
application
From the drop down menu, select "Format Disk"
maintain the default setting and select Format
Acknowledge warnings
After format process has been going for a while, the error message shown
above pops up
Workaround:
After selecting the SD card, instead of clicking the gear icon to format,
click the partition in the "Volumes" section.
Delete the partition ("minus" icon)
Create a new partition
-
The underlying problem is that the "wipefs" tool from util-linux does
not work any more.
=== TEST CASE ===
$ sudo modprobe scsi_debug dev_size_mb=200
# this creates a new /dev/sdX, usually /dev/sdb; check dmesg!
# now create a partition table
$ cat
[Touch-packages] [Bug 1059872] Re: Error formatting disk using disk utility
Furthermore:
If gparted is used to create an msdos partition table, but NO
partitions, then 'Erase Disk' in usb-creator-gtk fails with the timeout
error.
If gparted is used to create an (empty) FAT32 partition, then 'Erase
Disk' in usb-creator-gtk seems to succeed, but the "Make Startup Disk"
button remains grayed out so you can't do anything with it.
I ran usb-creator-gtk -i file.iso because the interactive iso picker
does not work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1059872
Title:
Error formatting disk using disk utility
Status in “udisks2” package in Ubuntu:
Invalid
Status in “util-linux” package in Ubuntu:
Fix Released
Status in “udisks2” source package in Trusty:
Invalid
Status in “util-linux” source package in Trusty:
Triaged
Status in “util-linux” package in Debian:
Fix Released
Bug description:
Formatting a SD card using the disk utility fails with an error
message
"Error formatting disk - Error synchronizing after initial wipe: Timed
out waiting for object (udisks-error-quark, 0)"
Steps to repro:
Launch the disk utility
Plug a SD card into the computer
Select the SD card and click on the gears icon at the top right of the
application
From the drop down menu, select "Format Disk"
maintain the default setting and select Format
Acknowledge warnings
After format process has been going for a while, the error message shown
above pops up
Workaround:
After selecting the SD card, instead of clicking the gear icon to format,
click the partition in the "Volumes" section.
Delete the partition ("minus" icon)
Create a new partition
-
The underlying problem is that the "wipefs" tool from util-linux does
not work any more.
=== TEST CASE ===
$ sudo modprobe scsi_debug dev_size_mb=200
# this creates a new /dev/sdX, usually /dev/sdb; check dmesg!
# now create a partition table
$ cat
[Touch-packages] [Bug 1244285] Re: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04)
Still happening in 13.10 after updating system on 9/1/2014. Reboot does NOT fix problem, but 'killall unity-panel-service' does. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1244285 Title: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04) Status in One Hundred Papercuts: Triaged Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: it does not happen often, and when it happens, just a log out and re- log in is enough to restore it. http://askubuntu.com/questions/357266/how-to-show-time-in- ubuntu-13-10/357280 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1244285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
