[Bug 1917926] Re: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1
The problem is still (or maybe regressed again?) there in Ubuntu 23.10, xorg session, with libmutter-13-0:amd64 Major non-gnome desktop apps, such as LibreOffice and Firefox to not raise when clicking in their titlebar, however gnome-terminal, gnome- settings and maybe other gnome-* raise as expected. --> Was the root cause masked by some work-around now built into gnome apps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917926 Title: Window focus/clicking/moving failures for Xorg sessions in 3.38.3-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1917926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976119 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1976119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/1193236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946792] [NEW] Can not install build-essential (missing repo or packaging problem?)
Public bug reported: Immediately after a clean install, sudo apt-get install build-essential fails as follows: Err:1 http://us.archive.ubuntu.com/ubuntu impish/main amd64 libc-dev-bin amd64 2.34-0ubuntu2 404 Not Found [IP: 91.189.91.38 80] Err:2 http://us.archive.ubuntu.com/ubuntu impish/main amd64 linux-libc-dev amd64 5.13.0-16.16 404 Not Found [IP: 91.189.91.38 80] Err:3 http://us.archive.ubuntu.com/ubuntu impish/main amd64 libnsl-dev amd64 1.3.0-2 404 Not Found [IP: 91.189.91.38 80] Err:4 http://us.archive.ubuntu.com/ubuntu impish/main amd64 libc6-dev amd64 2.34-0ubuntu2 404 Not Found [IP: 91.189.91.38 80] Err:5 http://us.archive.ubuntu.com/ubuntu impish/main amd64 build-essential amd64 12.9ubuntu1 404 Not Found [IP: 91.189.91.38 80] Err:6 http://us.archive.ubuntu.com/ubuntu impish/main amd64 libc-devtools amd64 2.34-0ubuntu2 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/g/glibc/libc-dev-bin_2.34-0ubuntu2_amd64.deb 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-libc-dev_5.13.0-16.16_amd64.deb 404 Not Found [IP: 91.189.91.38 80] E: Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/libn/libnsl/libnsl-dev_1.3.0-2_amd64.deb 404 Not Found [IP: 91.189.91.38 80] ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 12 13:28:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-10-07 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubiquity-21.10.5 wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946792 Title: Can not install build-essential (missing repo or packaging problem?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1946792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937958] Re: gnome-shell gdb instructions cause immediate "Oh no" crash
Upstream bug is https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4597 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4597 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4597 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937958 Title: gnome-shell gdb instructions cause immediate "Oh no" crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937958] Re: gnome-shell gdb instructions cause immediate "Oh no" crash
@vanvugt - No recent crash file was created in /var/crash, and neither at https://errors.ubuntu.com/user/ I re-ran the test using ssh and this time many "St-CRITICAL" warnings were written to the terminal, including this one surely indicates something bad: Object Gio.DBusProxy (0x57d0fa70), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. These were all captured in a typescript, which I will upload now: PLEASE SEE "typescript.3-processed" LMK if there is something else I could do to help track this down. -Jim ** Attachment added: "typescript.3-processed" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+attachment/5514109/+files/typescript.3-processed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937958 Title: gnome-shell gdb instructions cause immediate "Oh no" crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937958] Re: gnome-shell gdb instructions cause immediate "Oh no" crash
** Attachment added: "typescript-processed_v2" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+attachment/5513620/+files/typescript-processed_v2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937958 Title: gnome-shell gdb instructions cause immediate "Oh no" crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937958] Re: gnome-shell gdb instructions cause immediate "Oh no" crash
** Attachment added: "Extrqact from /var/log/syslog" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+attachment/5513619/+files/ex_syslog.txt ** Attachment removed: "typescript-processed" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+attachment/5513572/+files/typescript-processed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937958 Title: gnome-shell gdb instructions cause immediate "Oh no" crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937958] Re: gnome-shell gdb instructions cause immediate "Oh no" crash
** Description changed: I wanted to report a gnome-shell bug with a backtrace, so tried to use the instructions in https://wiki.gnome.org/Projects/GnomeShell/Debugging - which say to do the following in a separate VT: + which say to do the following in an ssh login or separate VT: gnome_session=$(pgrep -u $USER gnome-session) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS) gdb ...etc... However three problems came up, two minor (wrong instructions), the other major: (1) There is more than one gnome-session process, and so the shell variable $gnome_session gets set to a list of several PIDs, which in turn causes syntax errors when using the expression "/proc/$gnome_session/environ". In Ubuntu 21.04 I have three gnome-session processes immediately after rebooting and logging in (I have auto-login enabled, so the login happens by itself, in case that matters): $ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/') UID PIDPPID CSZ RSS PSR STIME TTY TIME CMD jima97439725 0 55216 16084 2 13:41 tty3 00:00:00 /usr/libexec/gnome-session-binary --systemd --session=ubuntu jima98288066 0 24031 6148 8 13:41 ?00:00:00 /usr/libexec/gnome-session-ctl --monitor jima98388066 0 129272 18176 7 13:41 ?00:00:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu (2) The instructions specify this gdb command: call gjs_dumpstack () However that results in an error and the call is not made: 'gjs_dumpstack' has unknown return type; cast the call to its declared return type - (3) Most importantly, a crash: After after starting gdb in an - independent VT to replace the running gnome-session process (or possibly - at the moment I switched VTs back to where I could observe the gnome - session), the session had immediately gotten a white screen with "Oh + (3) Most importantly, a crash: Immediately upon starting the new gnome- + shell process (with option --replace) a white screen appears with "Oh No... something went wrong..." forcing me log out. - I swtiched back to the independent VT, typed Control-C to get control in - gdb, and produced the backtraces (see attached typescript file). + The crash happens whether using an independent VT or an ssh login. + + Afterwards I typed Control-C to get control in gdb, and produced the + attached backtraces but they don't seem useful (see attached typescript + file). + + /var/syslog might be useful. I will attach the portion beginning just + before starting the new gnome-shell The attached typescript file shows what I did to circumvent the buggy instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging P.S. The original crash I wanted to report was that opening any .jpg in gimp and selecting part of the image and then doing Select->Invert instantly freezes the system. The only recovery is to use a separate VT to kill the gimp process, after which gnome-shell restarts. A system error dialog appears saying gnome-session [correction: gnome-shell] got a segfault somewhere; thus the desire to get a backtrace. But this bug - report is _not_ about that bug, at least not explicitly; it is about how - using the debug instructions in the wiki seem to cause a crash on their - own. + report is _not_ about that bug, but is about how using the debug + instructions in the wiki are incorrect and when fixed seem to cause a + crash on their own. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 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: Sun Jul 25 13:41:54 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-20 (5 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937958 Title: gnome-shell gdb instructions cause immediate "Oh no" crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937958] Re: gnome-shell gdb instructions cause immediate "Oh no" crash
Correction in the last paragraph: The segfault was in gnome-shell, not gnome-session, IIRC ** Description changed: I wanted to report a gnome-shell bug with a backtrace, so tried to use the instructions in -https://wiki.gnome.org/Projects/GnomeShell/Debugging + https://wiki.gnome.org/Projects/GnomeShell/Debugging which say to do the following in a separate VT: - gnome_session=$(pgrep -u $USER gnome-session) - eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY) - eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY) - eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS) - gdb - ...etc... + gnome_session=$(pgrep -u $USER gnome-session) + eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY) + eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY) + eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS) + gdb + ...etc... However three problems came up, two minor (wrong instructions), the other major: (1) There is more than one gnome-session process, and so the shell variable $gnome_session gets set to a list of several PIDs, which in turn causes syntax errors when using the expression "/proc/$gnome_session/environ". In Ubuntu 21.04 I have three gnome-session processes immediately after rebooting and logging in (I have auto-login enabled, so the login happens by itself, in case that matters): $ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/') UID PIDPPID CSZ RSS PSR STIME TTY TIME CMD jima97439725 0 55216 16084 2 13:41 tty3 00:00:00 /usr/libexec/gnome-session-binary --systemd --session=ubuntu jima98288066 0 24031 6148 8 13:41 ?00:00:00 /usr/libexec/gnome-session-ctl --monitor jima98388066 0 129272 18176 7 13:41 ?00:00:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu - gnome_session=$(pgrep -u $USER gnome-session|head -1) - eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY) - eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORI - TY) - eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SES - SION_BUS_ADDRESS) (2) The instructions specify this gdb command: - call gjs_dumpstack () + call gjs_dumpstack () However that results in an error and the call is not made: 'gjs_dumpstack' has unknown return type; cast the call to its declared return type - - (3) Most importantly, a crash: After after starting gdb in an independent VT to replace the running gnome-session process (or possibly at the moment I switched VTs back to where I could observe the gnome session), the session had immediately gotten a white screen with "Oh No... something went wrong..." forcing me log out. + (3) Most importantly, a crash: After after starting gdb in an + independent VT to replace the running gnome-session process (or possibly + at the moment I switched VTs back to where I could observe the gnome + session), the session had immediately gotten a white screen with "Oh + No... something went wrong..." forcing me log out. I swtiched back to the independent VT, typed Control-C to get control in gdb, and produced the backtraces (see attached typescript file). The attached typescript file shows what I did to circumvent the buggy instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging P.S. The original crash I wanted to report was that opening any .jpg in gimp and selecting part of the image and then doing Select->Invert instantly freezes the system. The only recovery is to use a separate VT to kill the gimp process, after which gnome-shell restarts. A system error dialog appears saying gnome-session got a segfault somewhere; thus the desire to get a backtrace. But this bug report is _not_ about that bug, at least not explicitly; it is about how using the debug instructions in the wiki seem to cause a crash on their own. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 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: Sun Jul 25 13:41:54 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-20 (5 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: I wanted to report a gnome-shell bug with a backtrace, so
[Bug 1937958] [NEW] gnome-shell gdb instructions cause immediate "Oh no" crash
Public bug reported: I wanted to report a gnome-shell bug with a backtrace, so tried to use the instructions in https://wiki.gnome.org/Projects/GnomeShell/Debugging which say to do the following in a separate VT: gnome_session=$(pgrep -u $USER gnome-session) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS) gdb ...etc... However three problems came up, two minor (wrong instructions), the other major: (1) There is more than one gnome-session process, and so the shell variable $gnome_session gets set to a list of several PIDs, which in turn causes syntax errors when using the expression "/proc/$gnome_session/environ". In Ubuntu 21.04 I have three gnome-session processes immediately after rebooting and logging in (I have auto-login enabled, so the login happens by itself, in case that matters): $ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/') UID PIDPPID CSZ RSS PSR STIME TTY TIME CMD jima97439725 0 55216 16084 2 13:41 tty3 00:00:00 /usr/libexec/gnome-session-binary --systemd --session=ubuntu jima98288066 0 24031 6148 8 13:41 ?00:00:00 /usr/libexec/gnome-session-ctl --monitor jima98388066 0 129272 18176 7 13:41 ?00:00:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu (2) The instructions specify this gdb command: call gjs_dumpstack () However that results in an error and the call is not made: 'gjs_dumpstack' has unknown return type; cast the call to its declared return type (3) Most importantly, a crash: After after starting gdb in an independent VT to replace the running gnome-session process (or possibly at the moment I switched VTs back to where I could observe the gnome session), the session had immediately gotten a white screen with "Oh No... something went wrong..." forcing me log out. I swtiched back to the independent VT, typed Control-C to get control in gdb, and produced the backtraces (see attached typescript file). The attached typescript file shows what I did to circumvent the buggy instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging P.S. The original crash I wanted to report was that opening any .jpg in gimp and selecting part of the image and then doing Select->Invert instantly freezes the system. The only recovery is to use a separate VT to kill the gimp process, after which gnome-shell restarts. A system error dialog appears saying gnome-session [correction: gnome-shell] got a segfault somewhere; thus the desire to get a backtrace. But this bug report is _not_ about that bug, at least not explicitly; it is about how using the debug instructions in the wiki seem to cause a crash on their own. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 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: Sun Jul 25 13:41:54 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-20 (5 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages uec-images ** Attachment added: "typescript-processed" https://bugs.launchpad.net/bugs/1937958/+attachment/5513572/+files/typescript-processed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937958 Title: gnome-shell gdb instructions cause immediate "Oh no" crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1937958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937119 Title: apt-add-repository --remove -S ... also deletes other components To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1937119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915362] Re: unoconv aborts if output file is in /tmp and named "out.xlsx"
** Description changed:
This is hard to believe, so I'm reluctant to submit this. But here it
is:
- If the effective output file path is "/tmp/out.xlsx" then unoconv aborts
- with an exception, but no abort occurs if a different file name or
- different directory is used (and yes, I checked that the file did not
- already exist). Something about the specific file name "out.xlsx" when
- stored in /tmp provokes this exception:
+ If the effective output file path is a certain filename, then unoconv
+ aborts with an exception, but no abort occurs if a different file name
+ or directory is used (and yes, I checked that the file did not already
+ exist). For a while, outputting to "out.xlsx" aborted but not if using
+ any other output filename; later, output to "xout.xlsx" started aborting
+ but using "out.xlsx" no longer aborted.
+
+ So there is some kind of state which remembers past file names (or
+ something) and causes havoc.
+
+ I tried temporarily removing $HOME/.config/libreoffice* but that did not
+ help (also tried setting the UserInstallation environment variable).
+
+ The exception is:
document.storeToURL(outputurl, tuple(outputprops) )
uno.IOException: SfxBaseModel::impl_store failed:
0x11b(Error Area:Io Class:Abort Code:27)
- I wonder if something about the permissions of /tmp, or the fact that is
- is a tmpfs file system, tickles some bug:
$ ls -ld /tmp
drwxrwxrwt 31 root root 980 Feb 10 18:46 /tmp/
$ mount | grep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=52428800k)
$ df -h /tmp
Filesystem Size Used Avail Use% Mounted on
tmpfs50G 572K 50G 1% /tmp
$ unoconv --version
unoconv 0.7
platform posix/linux
python 3.8.5 (default, Jul 28 2020, 12:59:40)
[GCC 9.3.0]
LibreOffice 6.4.6.2
I tried a new, clean user-config directory, thinking there might be
something corrupted in mine; but it makes no difference (export
UserInstallation... in the script below)
*** STEPS TO REPRODUCE ***
1. cd /tmp
2. echo "foo,bar" >demo.csv
- # OPTIONAL: use new, pristine user config
- 3. mkdir /tmp/userconfig ; export UserInstallation="file:///tmp/userconfig"
- 4. unoconv -d spreadsheet -f xlsx -o out.xlsx demo.csv
+ 3. unoconv -d spreadsheet -f xlsx -o out.xlsx demo.csv
+(or try xout.xlsx, alternating between tries)
RESULTS:
Traceback (most recent call last):
File "/usr/bin/unoconv", line 1037, in convert
document.storeToURL(outputurl, tuple(outputprops) )
uno.IOException: SfxBaseModel::impl_store failed:
0x11b(Error Area:Io Class:Abort Code:27)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/unoconv", line 1282, in
main()
File "/usr/bin/unoconv", line 1198, in main
convertor.convert(inputfn)
File "/usr/bin/unoconv", line 1039, in convert
raise UnoException("Unable to store document to %s (ErrCode
%d)\n\nProperties: %s" % (outputurl, e.ErrCode, outputprops), None)
File "/usr/lib/python3/dist-packages/uno.py", line 516, in
_uno_struct__getattr__
return getattr(self.__dict__["value"], name)
AttributeError: ErrCode
NOTE: Change "out.xlsx" to "xout.xlsx" and no error occurs!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: unoconv 0.7-2
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 10 18:39:17 2021
InstallationDate: Installed on 2020-03-24 (323 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: unoconv
UpgradeStatus: Upgraded to focal on 2020-05-16 (270 days ago)
** Description changed:
This is hard to believe, so I'm reluctant to submit this. But here it
is:
- If the effective output file path is a certain filename, then unoconv
- aborts with an exception, but no abort occurs if a different file name
- or directory is used (and yes, I checked that the file did not already
- exist). For a while, outputting to "out.xlsx" aborted but not if using
- any other output filename; later, output to "xout.xlsx" started aborting
- but using "out.xlsx" no longer aborted.
+ If the effective output file path specified -o is a certain
+ filename, then unoconv aborts with an exception, but no abort occurs if
+ a different file name or directory is used (and yes, I checked that the
+ file did not already exist). For me, outputting to "out.xlsx" when in
+ /tmp aborted but not if using any other output filename; however when in
+ some other directory (/home/myuser/ptmp/J), output to "xout.xlsx"
+ started aborting but using "out.xlsx" worked without error.
So there is some kind of state which remembers past file names (or
something) and causes havoc.
I tried
[Bug 1915362] [NEW] unoconv aborts if output file is in /tmp and named "out.xlsx"
Public bug reported:
This is hard to believe, so I'm reluctant to submit this. But here it
is:
If the effective output file path is "/tmp/out.xlsx" then unoconv aborts
with an exception, but no abort occurs if a different file name or
different directory is used (and yes, I checked that the file did not
already exist). Something about the specific file name "out.xlsx" when
stored in /tmp provokes this exception:
document.storeToURL(outputurl, tuple(outputprops) )
uno.IOException: SfxBaseModel::impl_store failed:
0x11b(Error Area:Io Class:Abort Code:27)
I wonder if something about the permissions of /tmp, or the fact that is
is a tmpfs file system, tickles some bug:
$ ls -ld /tmp
drwxrwxrwt 31 root root 980 Feb 10 18:46 /tmp/
$ mount | grep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=52428800k)
$ df -h /tmp
Filesystem Size Used Avail Use% Mounted on
tmpfs50G 572K 50G 1% /tmp
$ unoconv --version
unoconv 0.7
platform posix/linux
python 3.8.5 (default, Jul 28 2020, 12:59:40)
[GCC 9.3.0]
LibreOffice 6.4.6.2
I tried a new, clean user-config directory, thinking there might be
something corrupted in mine; but it makes no difference (export
UserInstallation... in the script below)
*** STEPS TO REPRODUCE ***
1. cd /tmp
2. echo "foo,bar" >demo.csv
# OPTIONAL: use new, pristine user config
3. mkdir /tmp/userconfig ; export UserInstallation="file:///tmp/userconfig"
4. unoconv -d spreadsheet -f xlsx -o out.xlsx demo.csv
RESULTS:
Traceback (most recent call last):
File "/usr/bin/unoconv", line 1037, in convert
document.storeToURL(outputurl, tuple(outputprops) )
uno.IOException: SfxBaseModel::impl_store failed:
0x11b(Error Area:Io Class:Abort Code:27)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/unoconv", line 1282, in
main()
File "/usr/bin/unoconv", line 1198, in main
convertor.convert(inputfn)
File "/usr/bin/unoconv", line 1039, in convert
raise UnoException("Unable to store document to %s (ErrCode
%d)\n\nProperties: %s" % (outputurl, e.ErrCode, outputprops), None)
File "/usr/lib/python3/dist-packages/uno.py", line 516, in
_uno_struct__getattr__
return getattr(self.__dict__["value"], name)
AttributeError: ErrCode
NOTE: Change "out.xlsx" to "xout.xlsx" and no error occurs!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: unoconv 0.7-2
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 10 18:39:17 2021
InstallationDate: Installed on 2020-03-24 (323 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: unoconv
UpgradeStatus: Upgraded to focal on 2020-05-16 (270 days ago)
** Affects: unoconv (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal third-party-packages
** Description changed:
This is hard to believe, so I'm reluctant to submit this. But here it
is:
If the effective output file path is "/tmp/out.xlsx" then unoconv aborts
with an exception, but no abort occurs if a different file name or
- different directory is used. Something about the specific file name
- "out.xlsx" when stored in /tmp provokes this exception:
+ different directory is used (and yes, I checked that the file did not
+ already exist). Something about the specific file name "out.xlsx" when
+ stored in /tmp provokes this exception:
document.storeToURL(outputurl, tuple(outputprops) )
uno.IOException: SfxBaseModel::impl_store failed:
0x11b(Error Area:Io Class:Abort Code:27)
I wonder if something about the permissions of /tmp, or the fact that is
is a tmpfs file system, tickles some bug:
$ ls -ld /tmp
drwxrwxrwt 31 root root 980 Feb 10 18:46 /tmp/
$ mount | grep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=52428800k)
$ df -h /tmp
Filesystem Size Used Avail Use% Mounted on
tmpfs50G 572K 50G 1% /tmp
$ unoconv --version
unoconv 0.7
platform posix/linux
- python 3.8.5 (default, Jul 28 2020, 12:59:40)
+ python 3.8.5 (default, Jul 28 2020, 12:59:40)
[GCC 9.3.0]
LibreOffice 6.4.6.2
I tried a new, clean user-config directory, thinking there might be
something corrupted in mine; but it makes no difference (export
UserInstallation... in the script below)
*** STEPS TO REPRODUCE ***
1. cd /tmp
2. echo "foo,bar" >demo.csv
-# OPTIONAL: use new, pristine user config
+ # OPTIONAL: use new, pristine user config
3. mkdir /tmp/userconfig ; export UserInstallation="file:///tmp/userconfig"
4. unoconv -d spreadsheet -f xlsx -o out.xlsx demo.csv
RESULTS:
Traceback (most recent call last):
- File "/usr/bin/unoconv", line 1037, in convert
- document.storeToURL(outputurl,
[Bug 1908333] Re: Ubuntu's groff ignores TZ (but upstream works)
Debian's choice to permanently make groff ignore TZ is obviously wrong (and unnecessary bc builds could set TZ=UTC if desired). What is the best way to get Debian to look at this? I guess I mean file a bug with Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908333 Title: Ubuntu's groff ignores TZ (but upstream works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groff/+bug/1908333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908333] Re: Ubuntu's groff ignores TZ (but upstream works)
> Subject: Always use UTC times for display @Jouni - do you have a link to the bug or discussion which made this change? It preposterous to break applications so they ignore TZ as a solution for a problematic build system. A build system could simply run everything with TZ=UTC, which would make apps display in UTC regardless of where the build executes. ** What would people think if the "date" command were changed to ignore the locale? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908333 Title: Ubuntu's groff ignores TZ (but upstream works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groff/+bug/1908333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908333] Re: Ubuntu's groff ignores TZ (but upstream works)
** Attachment added: "Demo script as a separate attachment" https://bugs.launchpad.net/ubuntu/+source/groff/+bug/1908333/+attachment/5444013/+files/groff_date_test.sh ** Attachment removed: "Demo script as a separate attachment" https://bugs.launchpad.net/ubuntu/+source/groff/+bug/1908333/+attachment/5444012/+files/groff_date_test.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908333 Title: Ubuntu's groff ignores TZ (but upstream works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groff/+bug/1908333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908333] [NEW] Ubuntu's groff ignores TZ (but upstream works)
Public bug reported: Ubuntu 20.04.1 LTS groff's date & time (visible in variable \n[hours] for example) are always in UTC, not the local time. The TZ environment variable is ignored. The upstream version doesn't have this bug; it honors TZ as it should. I downloaded and built from upstream source the exact same version of groff that the Ubuntu package claims to contain, and it works. But the Ubuntu binary does not work in this respect. dpkg-query -l groff says: 1.22.4-4build1 amd64 Upstream source code is at http://ftp.gnu.org/gnu/groff/groff-1.22.4.tar.gz STEPS TO REPRODUCE: 1. Run the following script #!/bin/sh #GROFF=/home/jima/src/groff-1.22.4/inst/bin/groff GROFF=/usr/bin/groff echo "Using $GROFF" for varlist in \ 'PATH=/bin:/usr/bin' \ 'PATH=/bin:/usr/bin TZ=UTC' \ 'PATH=/bin:/usr/bin TZ=America/New_York' \ 'PATH=/bin:/usr/bin TZ=America/Los_Angeles' \ ; do echo "--" eval "env -i $varlist /bin/sh" <&1 >/dev/null .tm groff says: \n[year]-\n[mo]-\n[dy] \n[hours]:\n[minutes]:\n[seconds] GEND SHELLEOF done *** Here is output on my system (notice that \n[hours] is always in UTC regardless of TZ): Using /usr/bin/groff -- TZ is (unset) date says: 2020-12-15 16:54:38 groff says: 2020-12-16 0:54:38 -- TZ is UTC date says: 2020-12-16 00:54:38 groff says: 2020-12-16 0:54:38 -- TZ is America/New_York date says: 2020-12-15 19:54:38 groff says: 2020-12-16 0:54:38 -- TZ is America/Los_Angeles date says: 2020-12-15 16:54:38 groff says: 2020-12-16 0:54:38 *** Here is output using groff built from upstream source: Using /home/jima/src/groff-1.22.4/inst/bin/groff -- TZ is (unset) date says: 2020-12-15 16:55:05 groff says: 2020-12-15 16:55:5 -- TZ is UTC date says: 2020-12-16 00:55:05 groff says: 2020-12-16 0:55:5 -- TZ is America/New_York date says: 2020-12-15 19:55:05 groff says: 2020-12-15 19:55:5 -- TZ is America/Los_Angeles date says: 2020-12-15 16:55:05 groff says: 2020-12-15 16:55:5 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: groff 1.22.4-4build1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 16:40:41 2020 InstallationDate: Installed on 2020-03-24 (266 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: groff UpgradeStatus: Upgraded to focal on 2020-05-16 (213 days ago) ** Affects: groff (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908333 Title: Ubuntu's groff ignores TZ (but upstream works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groff/+bug/1908333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908333] Re: Ubuntu's groff ignores TZ (but upstream works)
** Attachment added: "Demo script as a separate attachment" https://bugs.launchpad.net/ubuntu/+source/groff/+bug/1908333/+attachment/5444012/+files/groff_date_test.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908333 Title: Ubuntu's groff ignores TZ (but upstream works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/groff/+bug/1908333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881423] Re: error channel closing too late to send/recv
This is a problem because the errors also spew to the terminal -- corrupting whatever the user is doing now in the terminal. Firefox is started with a terminal if the user runs (possibly indirectly through a script) something which uses xdg-open, for example, on a file when firefox is the handler for it. ###!!! [Child][MessageChannel] Error: (msgtype=0x3A0146,name=PContent::Msg_ScriptError) Channel closing: too late to send/recv, messages will be lost -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881423 Title: error channel closing too late to send/recv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1881423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837974] Re: Toggle-maximize-vertically/horiz fully maximzes (REGRESSION)
*** This bug is a duplicate of bug 1698083 *** https://bugs.launchpad.net/bugs/1698083 Something is strange here: That upstream bug is 5+ years old, yet this problem appeared in Ubuntu at most 3 years ago (vertical resize worked in Ubuntu 18.10) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837974 Title: Toggle-maximize-vertically/horiz fully maximzes (REGRESSION) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1837974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886354] Re: Software app (gnome-software) Explore always hangs
I tried "sudo apt-get install --reinstall gnome-software" in case something was lost when upgrading to Ubuntu 20.04. Afterwards when I ran gnome-software, it said '"GNOME Software" needs to be restarted to use new plugins' but when I clicked "Restart Now", it hung. This time syslog had these lines: Jul 5 18:01:21 lxjima systemd[1989]: tracker-store.service: Succeeded. Jul 5 18:01:27 lxjima dbus-daemon[2153]: [session uid=2000 pid=2153] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.1' (uid=2000 pid=2140 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Jul 5 18:01:27 lxjima systemd[1989]: Starting Tracker metadata database store and lookup manager... Jul 5 18:01:27 lxjima dbus-daemon[2153]: [session uid=2000 pid=2153] Successfully activated service 'org.freedesktop.Tracker1' Jul 5 18:01:27 lxjima systemd[1989]: Started Tracker metadata database store and lookup manager. Jul 5 18:01:38 lxjima gnome-software-[217747]: Failed to quit service: Failed to see org.gnome.Software vanish: Waited for 3ms Jul 5 18:01:58 lxjima tracker-store[217754]: OK Jul 5 18:01:58 lxjima systemd[1989]: tracker-store.service: Succeeded. (but it's still hung) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886354 Title: Software app (gnome-software) Explore always hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1886354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886354] Re: Software app (gnome-software) Explore always hangs
** Attachment added: "syslog.txt -- logged during gnome-software" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1886354/+attachment/5390007/+files/syslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886354 Title: Software app (gnome-software) Explore always hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1886354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886354] [NEW] Software app (gnome-software) Explore always hangs
Public bug reported: The Explore tab of the "Software" app seems to be completely non- functional. It shows an initial screen with "Editors Picks", etc. but if you do any search or click one of the Categories, a blank screen appears with a forever-spinning indicator. The following error is written to syslog: ... dbus-daemon... Successfully activated service 'org.gnome.seahorse.Application' gnome-shell[]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.1376 was not provided by any .service files gnome-shell[]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 4 but got 0 (complete syslog from during the run is attached as syslog.txt) STEPS TO REPRODUCE: 1. Run gnome-software (or run "Software" through the app-finder mechanism) 2. Click the "Explore" (leftmost) tab at the top 3. Scroll down and click "Audio & Video" under Categories RESULTS: White screen with forever-spinning indicator ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 17:40:51 2020 InstallationDate: Installed on 2020-03-24 (103 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-05-16 (50 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886354 Title: Software app (gnome-software) Explore always hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1886354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871260 Title: update-initramfs Error 24 (EMFILE? == Too many open files?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851551] [NEW] man page does not mention that -e is deprecated
Public bug reported: gnome-terminal -e 'command...' emits a warning: # Option “-e” is deprecated and might be removed in a later version of gnome-terminal. # Use “-- ” to terminate the options and put the command line to execute after it. However this is contrary to the man page, which says nothing about -e being deprecated, and does not mention anything about the new method being possible (-- followed by command and options). Please update the documentation STEPS TO REPRODUCE: 1. man gnome-terminal 2. gnome-terminal -e "sh -c 'ls -l; sleep 3'" RESULTS: The documented method of specifying a command causes a deprecation warning. EXPECTED RESULTS: Documentation should say how to do the right thing. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 10:20:44 2019 InstallationDate: Installed on 2019-02-06 (273 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-10-25 (11 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851551 Title: man page does not mention that -e is deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1851551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851546] [NEW] Debug spew to stderr at startup
Public bug reported: gnome-terminal writes debug messages to stderr every time it starts up: # _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) This pollutes the terminal when a script explicitly invokes gnome- terminal to open another window. STEPS TO REPRODUCE: 1. Open a terminal and type "gnome-terminal" RESULTS: Debug messages appear on the first terminal EXPECTED RESULTS: Nothing should appear on stderr or stdout of gnome- terminal itself, unless there is an actual error. P.S. Presumably a debug build escaped and was released. To prevent this from happening, it would be a good idea to add a test which checks that gnome-terminal writes nothing to std* in normal (non-error) cases. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-terminal 3.34.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 10:03:24 2019 InstallationDate: Installed on 2019-02-06 (273 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to eoan on 2019-10-25 (11 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851546 Title: Debug spew to stderr at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1851546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838180 Title: apps use speakers when bluetooth headset is active (REGRESSION) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838177] Re: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs
@Daniel Ach! Sorry, I posted to the wrong bug report. Please disregard comments #2 through #5 (when processing this bug report). ** Description changed: Whenever the "bluetooth settings" screen is opened, an assertion failure is logged from gnome-shell, followed by many video-related lines from gdm-x-session (syslog extract attached). The first part looks like this: gnome-shell[2872]: g_environ_setenv: assertion 'value != NULL' failed /usr/lib/gdm3/gdm-x-session[2251]: (II) modeset(0): EDID vendor "NEC", prod id 26342 ... - STEPS TO REPRODUCE: 1. tail -f /var/log/syslog #in a terminal 2. In the upper-right top of the screen: - Speakericon->Bluetoothicon->Gluetooth settings + Speakericon->Bluetoothicon->Gluetooth settings RESULTS: BT settings window openens, and many messages logged to syslog EXPECTED RESULTS: No assertion errors logged (unclear why anything should be logged due to simply opening a window). + + NOTE: Please disregard comments #2 through #5 below, they were intended + for a differenb bugrep. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 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:37:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838177 Title: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838177] Re: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs
Still a problem: When BT is turned "Off" in Ubuntu (using the speaker- icon thingie), the BT does not immediately report disconnection; but when BT it turned ON again in Ubuntu, *then* the headset says it lost the connection. (and at that point the original problem is present, where Ubuntu says it is connected to the headset but sounds go to the speakers instead). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838177 Title: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838177] Re: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs
I found that removing the following "fixed" the problem: $HOME/.cache $HOME/.config/pulse $HOME/.config/sound-juicer $HOME/.gconf Don't know what exactly is(was) the problem. However I backed up my homedir first, so I can attach any of the deleted files here if that would be helpful. @devs Please let me know if you want that. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838177 Title: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838180 Title: apps use speakers when bluetooth headset is active (REGRESSION) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838177] [NEW] bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs
Public bug reported: Whenever the "bluetooth settings" screen is opened, an assertion failure is logged from gnome-shell, followed by many video-related lines from gdm-x-session (syslog extract attached). The first part looks like this: gnome-shell[2872]: g_environ_setenv: assertion 'value != NULL' failed /usr/lib/gdm3/gdm-x-session[2251]: (II) modeset(0): EDID vendor "NEC", prod id 26342 ... STEPS TO REPRODUCE: 1. tail -f /var/log/syslog #in a terminal 2. In the upper-right top of the screen: Speakericon->Bluetoothicon->Gluetooth settings RESULTS: BT settings window openens, and many messages logged to syslog EXPECTED RESULTS: No assertion errors logged (unclear why anything should be logged due to simply opening a window). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 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:37:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-05 (479 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-07-26 (2 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1838177/+attachment/5279670/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838177 Title: bluetooth->settings causes gnome-shell assertion failure, then many video-releated msgs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837974] [NEW] Toggle-maximize-vertically/horiz fully maximzes (REGRESSION)
Public bug reported: Double-clicking a window title-bar now fully-maximizes the window, even though the action is set to "Toggle Maximize Vertically" or "Toggle Maximize Horizontally". In other words, those options now behave just like "Toggle Maximize". This problem started after I upgraded from Ubuntu 18.10 (gnome-shell 3.30?) to Ubuntu 19.04 (gnome-shell 3.32.1). STEPS TO REPRODUCE: 1. Run gnome-tweaks 2. Click "Window Titlebars" in left menu panel 3. Set "Titlebar Actions ... Double-Click" to "Toggle Maximize Vertically" 4. Double-click a gnome-terminal titlebar RESULTS: WIndow maximizes fully (fills entire screen) EXPECTED RESULTS: Maximize in vertical direction only. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 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: Thu Jul 25 22:53:16 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-04-05 (477 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-07-26 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837974 Title: Toggle-maximize-vertically/horiz fully maximzes (REGRESSION) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1837974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834981] [NEW] scan area does not match preview selection
Public bug reported: Using Brother MFC-9340CDW to scan. After selecting a region in the Preview window, "Scan" scans the wrong area. The scanned area is "kind of" related to the selcted area, but off significantly. The scan includes extra area to the upper left, and truncates ares from the lower right. Please see attached screen shot, which shows the preview window and scan results. Note that the dashed line selected in the preview does not correspond to the area actually scanned. ** Affects: xsane (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot showing preview selection problem" https://bugs.launchpad.net/bugs/1834981/+attachment/5274546/+files/xsanebug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834981 Title: scan area does not match preview selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/1834981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834981] Re: scan area does not match preview selection
STEPS TO REPRODUCE: 1. Install brother MFC-9340CDW :-) 2. Put newsprint or similar on flat bed. 3. Start xsane. In preview window, select +zoom and click somewhere to zoom in. Then right-click to stop zoom function, and left-click-drag to select a small scan area (about 1x1 inches) 4. Click Scan button in the main window. RESULTS: The scan contains the wrong part of the image EXPECTED RESULT: Scan should contain the area shown in the dotted box in the Preview window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1834981 Title: scan area does not match preview selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xsane/+bug/1834981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818573] [NEW] sound-juicer can not read 2nd CD: device_changed_cb: code should not be reached
Public bug reported: After successfully Extracting tracks from a music CD with auto-eject, this appears: ** (sound-juicer:19604): WARNING **: 14:15:59.588: (src/sj- prefs.c:299):device_changed_cb: code should not be reached Thereafter, sound-juicer can not read another CD. It is necessary to quit sound-juicer and restart. If another audio CD is inserted, sound-juicer briefly flashes a message "Extracting track info..." but then a big pop-up appears with: Could not read the CD... Reason: Cannot access CD: The name:1.176 was not provided by any .service file There is no recovery (except quit & restart sound-juicer) Ubuntu 18.10 (Not using ubuntu-bug because it no longer opens a browser after sending bug data!) ** Affects: sound-juicer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818573 Title: sound-juicer can not read 2nd CD: device_changed_cb: code should not be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sound-juicer/+bug/1818573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814839] Re: "Sloppy" or "Focus on Hover" window focus is slow to respond, some keystrokes go to the wrong (old) window
Okay. Upstream bug is https://gitlab.gnome.org/GNOME/mutter/issues/469 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814839 Title: "Sloppy" or "Focus on Hover" window focus is slow to respond, some keystrokes go to the wrong (old) window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1814839] Re: keystrokes go to wrong window immediately after moving mouse to change window focus
Daniel van Vugt wrote:
> Are you able to try Ubuntu 19.04 and tell us if the same problem happens
> there?
Yes I can download and install Ubuntu 19.04 in a virtual machine. But
before you ask me to go to all that work, have you tried the test
yourself given in the bug ("STEPS TO REPRODUCE")?
Do you see the symptom? If yes, on what OS version?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814839
Title:
keystrokes go to wrong window immediately after moving mouse to change
window focus
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1814839/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816255] [NEW] Default sidebar icon screws up size of all icons
Public bug reported:
Ubuntu 18.04.1, gnome/X11 session.
All the icons in the activities panel (the left side-bar) are shrunk if
an app is run which does not specify an icon. Perhaps the default icon
is too large, or otherwise lacking in a way which causes the entire
side-bar to be re-scaled, shrinking the existing icons.
The example below usses qmlscene (a tool to run Qt-based apps), but I've
seen this with other apps which don't have a proper icon, such as the
citrix receiver.
Please see attached screenshots (before and after running a qmlscene
program)
STEPS TO REPRODUCE:
1. # Install Qt with qmlscene.
# I think this is enough:
sudo apt-get install qmlchooser qmlscene
# But if not, then:
sudo apt-get install qtcreator qtbase5-dev
2. # create a trivial qml program
echo 'import QtQuick 2.9' >t.qml
echo 'import QtQuick.Controls 2.2' >>t.qml
echo 'ApplicationWindow { id: top; visible:true }' >>t.qml
3. qmlscene t.qml
RESULTS: The icons in the left sidebar contract to about half their
previous size.
** Affects: gnome-panel (Ubuntu)
Importance: Undecided
Status: Invalid
** Attachment added: "after.png (showing shrunken icons in task bar)"
https://bugs.launchpad.net/bugs/1816255/+attachment/5239165/+files/after.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816255
Title:
Default sidebar icon screws up size of all icons
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1816255/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816255] Re: Default sidebar icon screws up size of all icons
** Attachment added: "before.png (showing icons as they were before)" https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1816255/+attachment/5239166/+files/before.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816255 Title: Default sidebar icon screws up size of all icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1816255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816255] Re: Default sidebar icon screws up size of all icons
Oh, nevermind. The problem is too many icons to fit vertically; I was expecting the task bar to scroll/overlap like it used to do in Unity. Now it just shrinks everything ** Changed in: gnome-panel (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816255 Title: Default sidebar icon screws up size of all icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1816255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814613 Title: qmlscene -style material file.qml says "QApplication: invalid style override passed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1814613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1459359] Re: Gtk & Glib CRITICAL messages at startup (regression)
The GTK warning no longer happes for me on Ubuntu 18.04.01. However a different message is written to the terminal at startup: Initializing nautilus-image-converter extension (unrelated) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1459359 Title: Gtk & Glib CRITICAL messages at startup (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1459359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814839 Title: keystrokes go to wrong window immediately after moving mouse to change window focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814839 Title: keystrokes go to wrong window immediately after moving mouse to change window focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814613 Title: qmlscene -style material file.qml says "QApplication: invalid style override passed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1814613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814613 Title: qmlscene -style material file.qml says "QApplication: invalid style override passed" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1814613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: ubuntu-bug never (any longer) opens browser window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814609 Title: ubuntu-bug / appport never opens browser window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248328] Re: Printing emails shows no body text; works only printing to .ps file
This is no longer a problem using TB 57.0b2 (64-bit) and Ubuntu 18.04 ** Changed in: thunderbird (Ubuntu) Status: Expired => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248328 Title: Printing emails shows no body text; works only printing to .ps file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1248328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098358] Re: Close-Other-Tabs warns even if "warning if closing multiple tabs" is disabled
The problem no longer exists (checked with Firefox 61.0.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098358 Title: Close-Other-Tabs warns even if "warning if closing multiple tabs" is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1098358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1102282 Title: Image OMITTED from pdf printed with lpr (works with acroread) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1102282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1306288] Re: Ubuntu Firefox does not allow using system default email program
Problem is gone now (Firefox 61.0). ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1306288 Title: Ubuntu Firefox does not allow using system default email program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1306288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771466] Re: Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state
Upstream bug is https://gitlab.gnome.org/GNOME/gnome-shell/issues/282 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771466 Title: Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771466] [NEW] Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state
Public bug reported: Toggling Super+D hides or un-hides all windows so you can access icons on the desktop. But this breaks if a new window appears while the windows are hidden: They become PERMANENTLY hidden, i.e. Super+D does not restore them. They seem to be "minimized" -- you have to individually un-minimize each window to get your session back. This is very annoying, and is common: The only reason for using Super+D is to see something on the desktop; probably you then need to do something with it, i.e. click it. If that action opens a new window, which is almost certain, you're hosed. STEPS TO REPRODUCE: 1. Open a bunch of windows and artfully arrange them. 2. Type Super+D (they all become hidden) 3. Double-click the "Trash" desktop icon and wait for a file browser to open. RESULTS: Once the file-viewer opens, Super+D will not restore the previously-hidden windows. Instead, it seems to forget about them and instead hide the new window (and un-hide it if pressed a second time --before yet another window is opened, of course). EXPECTED RESULTS: The state should be well-defined: Either normal or windows-hidden. Once in the windows-hidden state, Super-D should un-hide the hidden windows e ven if new windows have been created in the interim. SUGGESTED FIX: 1. (preferred): On the first Super+D, hide all windows and remember their IDs. On the next Super+D, un-hide just those windows, if they still exist, and do nothing at all with any other windows which might be present (i.e. new ones). Then return to the initial state, where Super+D hides all visible windows. 2. (if the above is too hard to implement): If a new window appears while in the "hiding" state, make the new window immediately become hidden also; only on the second Super+D would the new window become visible along with the old ones. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 15 16:40:22 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['keepaw...@jepfa.de', 'rece...@leonardo.bartoli.gmail.com', 'drive-m...@gnome-shell-extensions.gcampax.github.com', 'sound-output-device-choo...@kgshank.net', 'suspend-button@laserb', 'systemmoni...@gnome-shell-extensions.gcampax.github.com', 'workspaces-to-d...@passingthru67.gmail.com']" b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-04-05 (40 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771466 Title: Super+D wrongly leaves windows minimized if a new window appears while in "hiding" state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1771466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771434] [NEW] Log Out/login does not recognize new supplementary group; Hangs after repeated Log Out/login cycles
Public bug reported: If a supplementary group is added to a user who is currently logged in to a graphical session, then strange breakage occurs: Problem #1: If the changed user logs out and then logs in again, their processes still do not have the new group membership. It seems necessary to reboot for the group add to take effect in graphically logins. However "su - " in a terminal does get a process with tne new group. Problem #2: If the changed user repeatedly does "Log Out" and then logs in again via gdm, eventually "Log Out" stops working completely (invoking it has no discernible effect). STEPS TO REPRODUCE: 1. Log in graphically as any existing user (might not be relevant). 2. Control-Alt-F3 to get a vt login; log in as root. In the root shell: adduser testuser (enter a password) (hit ENTER to take defaults for all other prompts) 3. Alt-Ctrl-F1 to get to the grpahical login Log in as "testuser" 4. Control-Alt-F3 to return to the root shell. usermod -a -G sudo testuser # group 'sudo' is an example 5. Alt-Ctrl-F1 to get to the grpahical login Return to session of user "testuser" Upper-right-corner-menu->testuser->Log Out (returns to graphical login selector) 6. Log in as "testuser" again Start a gnome-terminal and type "id" RESULTS: "id" shows that the process does NOT have "sudo" as a supplementary group. EXPECTED RESULTS: New graphical logins should see credential changes. 7. Repeatedly do Upper-right-corner-menu->testuser->Log Out Log in again as "testuser" RESULTS: After 3 or 4 iterations, "Log Out" stops working altogether. (When finished "deluser --remove-home testuser" to clean up) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 15 14:17:25 2018 InstallationDate: Installed on 2018-04-05 (40 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180403.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Summary changed: - Log Out/login does not recognize new supplementary group; Lot Out hangs eventually + Log Out/login does not recognize new supplementary group; Hangs after repeated Log Out/login cycles ** Description changed: If a supplementary group is added to a user who is currently logged in to a graphical session, then strange breakage occurs: Problem #1: If the changed user logs out and then logs in again, - their processes still do not have the new group membership. + their processes still do not have the new group membership. - It seems necessary to reboot for the group add to take effect in - in graphically logins. + It seems necessary to reboot for the group add to take effect in + graphically logins. However "su - " in a terminal does get a + process with tne new group. Problem #2: If the changed user repeatedly does "Log Out" and then - logs in again via gdm, eventually "Log Out" stops working - completely (invoking it has no discernible effect). + logs in again via gdm, eventually "Log Out" stops working + completely (invoking it has no discernible effect). STEPS TO REPRODUCE: 1. Log in graphically as any existing user (might not be relevant). 2. Control-Alt-F3 to get a vt login; log in as root. -In the root shell: - adduser testuser - (enter a password) - (hit ENTER to take defaults for all other prompts) + In the root shell: + adduser testuser + (enter a password) + (hit ENTER to take defaults for all other prompts) - 3. Alt-Ctrl-F1 to get to the grpahical login -Log in as "testuser" + 3. Alt-Ctrl-F1 to get to the grpahical login + Log in as "testuser" 4. Control-Alt-F3 to return to the root shell. - usermod -a -G sudo testuser # group 'sudo' is an example + usermod -a -G sudo testuser # group 'sudo' is an example 5. Alt-Ctrl-F1 to get to the grpahical login -Return to session of user "testuser" + Return to session of user "testuser" -Upper-right-corner-menu->testuser->Log Out -(returns to graphical login selector) + Upper-right-corner-menu->testuser->Log Out + (returns to graphical login selector) 6. Log in as "testuser" again -Start a gnome-terminal and type "id" + Start a gnome-terminal and type "id" RESULTS: "id" shows that the process does NOT - have "sudo" as a supplementary group. + have "sudo" as a supplementary group. EXPECTED RESULTS: New graphical logins should see credential changes. 7. Repeatedly do - Upper-right-corner-menu->testuser->Log Out - Log in again as "testuser" +
[Bug 1756147] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1756147/+attachment/5080890/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756147 Title: Error/warning on terminal when clicking "Privacy" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1756147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756147] Re: Error/warning on terminal when clicking "Privacy" tab
apport information ** Tags added: apport-collected artful third-party-packages ** Description changed: Many error/warning messages are written to the terminal (stdout and/or stderr) when operating gnome-control-center. For example, clicking the "Privacy" category tab produces this: - (gnome-control-center:11277): privacy-cc-panel-WARNING **: 10:27:13.217: - Failed fetch permissions from flatpak permission store: - GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name - org.freedesktop.impl.portal.PermissionStore was not provided by any - .service files + (gnome-control-center:11277): privacy-cc-panel-WARNING **: 10:27:13.217: Failed fetch permissions from flatpak permission store: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files + --- + ApportVersion: 2.20.7-0ubuntu3.7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 17.10 + Package: gnome-control-center 1:3.26.2-0ubuntu0.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 + Tags: artful third-party-packages + Uname: Linux 4.13.0-36-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1756147/+attachment/5080888/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756147 Title: Error/warning on terminal when clicking "Privacy" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1756147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756147] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1756147/+attachment/5080889/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756147 Title: Error/warning on terminal when clicking "Privacy" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1756147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756147] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1756147/+attachment/5080891/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756147 Title: Error/warning on terminal when clicking "Privacy" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1756147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756147] [NEW] Error/warning on terminal when clicking "Privacy" tab
Public bug reported: Many error/warning messages are written to the terminal (stdout and/or stderr) when operating gnome-control-center. For example, clicking the "Privacy" category tab produces this: (gnome-control-center:11277): privacy-cc-panel-WARNING **: 10:27:13.217: Failed fetch permissions from flatpak permission store: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.impl.portal.PermissionStore was not provided by any .service files ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756147 Title: Error/warning on terminal when clicking "Privacy" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1756147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258597] Re: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
I fixed the problem, but every time I do an update (and grub is updated), it asks me if it can install the "package maintainer's version". If I say yes, then this warning occurs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258597 Title: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1258597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743154] [NEW] sane-dll (5) man page missing
Public bug reported: In Ubuntu 17.10, with packages "sane" and "libsane1" installed, man sane-dll man 5 sane-dll say "No manual entry for sane-dll". This man page is the SEE ALSO list in the sane(7) man page and mentioned on the Internet. Note: When trying to install libsane, apt-get substitutes "libsane1" for some reason: # apt-get install libsane Note, selecting 'libsane1' instead of 'libsane' libsane1 is already the newest version (1.0.27-1~experimental2ubuntu2.1). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: sane 1.0.14-12build1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 13 12:35:48 2018 InstallationDate: Installed on 2017-12-13 (31 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: sane-frontends UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-frontends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743154 Title: sane-dll (5) man page missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-frontends/+bug/1743154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740214
Title:
Ubuntu patch to perl causes problem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1740214/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739468] [NEW] Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered
Public bug reported: The following message is continuously logged to /var/log/syslog (every few seconds): Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Attempting to re-register :1.51/org/ayatana/NotificationItem/multiload; resetting instead Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered It's hard to find anything in syslog because thousands of these messages intermingle with everything else ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 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: Wed Dec 20 10:28:49 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-13 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739468 Title: Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738889] Re: Hang with >1 CPU after "Restart now" button pressed
** Summary changed: - Hang after "Restart now" button pressed + Hang with >1 CPU after "Restart now" button pressed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738889 Title: Hang with >1 CPU after "Restart now" button pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738889] Re: Hang after "Reboot now" button pressed
It's MULTI-PROCESSOR related. I realized that I had always had multiple CPUs (doing a bare-metal install or in a VM with multiple CPUs enabled). I tried again with a completely-defaulted Virtualbox VM -- only one CPU and 1GB of ram: and the bug DID NOT HAPPEN. REVISED STEPS TO REPRODUCE: 1. Create a new Virtualbox VM, initially taking all defaults. Then change Settings->System->Processor to 4 CPUs, and 4GB of ram (if your machine has < 6GB of actual ram, specify 1GB less than your physical ram size) Attach the 17.10 Desktop iso image to the virtual optical drive (Settings->Storage-> click the DVD image; then click the "Optical Drive" drop-down and Choose the path to the .iso file) 2. Start the VM. Click "Install Ubuntu" at the first screen, take all defaults 3. At the last screen, click "Restart Now" (hangs) ** Summary changed: - Hang after "Reboot now" button pressed + Hang after "Restart now" button pressed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738889 Title: Hang after "Restart now" button pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738889] [NEW] Hang after "Reboot now" button pressed
Public bug reported: The install system hangs after every install, after the user clicks the "Reboot Now" button. The desktop disappears and "Ubuntu 17.10" in white typeface appears, but then nothing. The system must be reset to regain control (the installed system then works). I'll attach a screenshot of a VM in the hung state, and also an archive of files left in /var/log/installer/ STEPS TO REPRODUCE (using Virtualbox): 1. Download the 17.10 Desktop iso image from https://www.ubuntu.com/download/desktop/thank-you?version=16.04.3=amd64 2. In virtualbox, create a new VM with a newly-created virtual disk; attach the iso image to the virtual optical drive, and start the VM. 3. Select "Install" when prompted, then take all the defaults (no download in background, no extra codecs, etc.) 4. When finished, click the "Reboot Now" button RESULTS: hangs ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity (not installed) 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: Mon Dec 18 09:49:44 2017 InstallationDate: Installed on 2017-12-13 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "tar archive of /var/log/installer/ in the installed (guest) system" https://bugs.launchpad.net/bugs/1738889/+attachment/5024334/+files/var_log_installer.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738889 Title: Hang after "Reboot now" button pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738889] Re: Hang after "Reboot now" button pressed
** Attachment added: "screen-shot at the hang" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738889/+attachment/5024340/+files/hangscreen.png ** Attachment removed: "UbiquitySyslog.txt" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738889/+attachment/5024339/+files/UbiquitySyslog.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738889/+attachment/5024338/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738889/+attachment/5024337/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738889/+attachment/5024336/+files/JournalErrors.txt ** Attachment removed: "HookError_source_ubiquity.txt" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738889/+attachment/5024335/+files/HookError_source_ubiquity.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738889 Title: Hang after "Reboot now" button pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1738889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738673 Title: deluser --backup fails because tar --no-unquote option should be used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1738673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738673 Title: deluser --backup fails because tar --no-unquote option should be used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1738673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738307 Title: Can not move icons in dash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1738307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738307 Title: Can not move icons in dash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1738307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738144 Title: Monitor locked to low-res when using EFI/Secure Boot on Coffee Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1738144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1486445 Title: Lots of zeitgeist errors To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist-datahub/+bug/1486445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720019 Title: org.PulseAudio1 was not provided by any .service files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710751] Re: bamfdaemon polling every 3 ms
Oh never mind. Some process is sending it a continuous stream of messages, so of course it is waking up all the time... ** Changed in: bamf (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710751 Title: bamfdaemon polling every 3 ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1710751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710751] [NEW] bamfdaemon polling every 3 ms
Public bug reported:
bamfdaemon has some odd behavior (possibly indicating a design bug)
which causes it to wake up every 3 milliseconds and attempt four non-
blocking reads on the same socket. This occurs in an otherwise idle
system.
Most likely the code uses a short-cut or work-around for a design
problem somewhere.
Ideally bamfdaemon would call poll() or select() and block
_indefinitely_ (no timeout) until an event of possible interest occurs,
and only then attempt the recvmsg() calls. That would avoid loading
the cpu and forcing the bamf memory pages to stay resident, etc.
Can someone who knows what bamfdaemon is trying to do comment on why it is
waking up every 3 ms. to repeat the exact same recvmsg() calls?
Strangely, it seems to call recvmsg() several times on the same file
descriptor, with a different buffer address each time (no kernel calls
inbetween).
STEPS TO REPRODUCE:
sudo strace -p `pidof bamfdaemon`
RESULTS:
recvmsg(3, {msg_name(0)=NULL,
msg_iov(1)=[{"\34\0\0\375\20\0\200\3\253\1\0\0\263\214[\26\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(3, 0x7ffe096ef630, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, 0x7ffe096ef4e0, 0) = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(3, 0x7ffe096ef610, 0) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}], 3,
-1) = 1 ([{fd=3, revents=POLLIN}])
(repeats forever)
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: bamfdaemon 0.5.3+17.04.20170406-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-30.34-generic 4.10.17
Uname: Linux 4.10.0-30-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon Aug 14 18:09:28 2017
InstallationDate: Installed on 2017-01-19 (207 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: bamf
UpgradeStatus: Upgraded to zesty on 2017-07-26 (19 days ago)
** Affects: bamf (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710751
Title:
bamfdaemon polling every 3 ms
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1710751/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707977] Re: SHLVL=2 in outermost shell in unity terminals (REGRESSION)
Oh joy, a bug in the work-around (and no way to edit the post).
Please add "-a" to the egrep command line to avoid a warning due to the nul
terminator in cmdline.
CORRECTED work-around for .bashrc :
i_am_toplevel() {
case "$SHLVL" in
1) return 0 ;;
3) return 1 ;;
2) # HACK FOR Ubuntu 16.10, 17.04 ... where SHLVL=2 at top
if egrep -as '(terminal-server|^xterm)' /proc/$PPID/cmdline ; then
return 0
fi
;;
esac
return 1
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707977
Title:
SHLVL=2 in outermost shell in unity terminals (REGRESSION)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1707977/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707977] Re: SHLVL=2 in outermost shell in unity terminals (REGRESSION)
I hope this bug will be fixed before the next release. But meanwhile,
here is a nasty workaround which can be used in bash startup scripts:
i_am_toplevel() {
case "$SHLVL" in
1) return 0 ;;
3) return 1 ;; # (optimize this case)
2) # HACK FOR Ubuntu 16.10, 17.04 ... where SHLVL=2 at top
if egrep -s '(terminal-server|^xterm)' /proc/$PPID/cmdline ; then
return 0
fi
;;
esac
return 1
}
Then say "if i_am_toplevel ; then ... "
instead of "if [ $SHLVL -eq 1 ] ..."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707977
Title:
SHLVL=2 in outermost shell in unity terminals (REGRESSION)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1707977/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707977] [NEW] SHLVL=2 in outermost shell in unity terminals (REGRESSION)
Public bug reported: The bash variable SHLVL is 2, rather than 1, in the outermost shell process in terminal emulators (gnome-terminal, xterm, etc. -- it doesn't matter). This makes SHLVL useless, and breaks many scripts (run from .bashrc etc.) which look for SHLVL=1 to save/restore state of some kind. This is a painful REGRESSION since 16.04. SHLVL=1 in pty terminals (Ctrl-Alt-F1 etc.) so the problem is not in bash. The parent of the "outer most" shell (which has SHLVL=2) is not another bash instance, but the terminal emulator (gnome-terminal-server, xterm, etc.). This is expected. Since the problem exists with various terminal emulators, the bug must be in generic gui initialization or gui-app startup code (not in gnome-terminal or xterm). => Speculation: Somewhere in the initial GUI startup code there is a script executed by bash which starts long-running processes (systemd?) and then exits. SHLVL=1 is inherited in the environment by the child, and so any shell the child later spawns set SHLVL=2. If that's the case, then it might suffice to "unset SHLVL" before starting the child(ren). Again, this is just speculation. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: unity 7.5.0+17.04.20170407.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 BootLog: WDStockRoot: clean, 408304/4890624 files, 6257387/19531008 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Tue Aug 1 10:07:13 2017 DistUpgraded: 2017-07-26 09:01:41,817 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-87-generic, x86_64: installed nvidia-375, 375.66, 4.10.0-28-generic, x86_64: installed DpkgLog: GconfCompiz: /apps/compiz-1/plugins: /apps/compiz-1/plugins/grid: /apps/compiz-1/plugins/grid/screen0: /apps/compiz-1/plugins/grid/screen0/options: top_edge_action = 0 GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] [10de:1284] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GK208 [GeForce GT 630 Rev. 2] [19da:1308] InstallationDate: Installed on 2017-01-19 (194 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-28-generic root=UUID=cc35a925-d0d6-4331-b791-4d52605d5a8d ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to zesty on 2017-07-26 (6 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 version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel
[Bug 270479] Re: Debian/Ubuntu netpbm is many years out-of-date with upstream
Thanks to whoever did the fix. But can we please have a bit more (i.e. any at all) communication in the future? There is nary a word from any dev in this bug report about what the problem was or how it was resolved, or even what was done in the "fix". Questions: What _is_ the current status of netpbm now? How does Ubuntu's netpbm compare, now, with upstream? Is it the same? If different, please give brief overview of why. Are there any remaining issues (such as licensing) which will impede routine updates in the future (that is, can we expect future upstream changes to appear in Ubuntu)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/270479 Title: Debian/Ubuntu netpbm is many years out-of-date with upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/270479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401207] Re: No 'Select-by-word characters' property
Ok, I'll say it very explicitly: Please bring back explicit setting WITH GUI SUPPORT. Users should not have to hack around with dcomf for something like this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401207 Title: No 'Select-by-word characters' property To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1401207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679789 Title: Trailing slash missing from Dir::Cache in apt configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1679789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679789
Title:
Trailing slash missing from Dir::Cache in apt configuration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1679789/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1671977
Title:
Inconsistent splitting of results of $(Command Substitution)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1671977/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1658556
Title:
watch -c --differences=permanent misbehaves (highlights everything)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1658556/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658001] [NEW] (brasero:11454): CRITICAL **: gst_ffmpeg_cfg_set_property: assertion 'qdata->size == sizeof (gint64)' failed
Public bug reported: brasero /path/to/dvdimage.iso ...burns the disk okay but emits the following on the terminal: ** (brasero:11454): CRITICAL **: gst_ffmpeg_cfg_set_property: assertion 'qdata->size == sizeof (gint64)' failed Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: brasero 3.12.1-1ubuntu3~16.04 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: Thu Jan 19 23:48:55 2017 InstallationDate: Installed on 2013-08-06 (1263 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: brasero UpgradeStatus: Upgraded to xenial on 2016-05-11 (254 days ago) ** Affects: brasero (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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658001 Title: (brasero:11454): CRITICAL **: gst_ffmpeg_cfg_set_property: assertion 'qdata->size == sizeof (gint64)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1658001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
