[Desktop-packages] [Bug 977069] Re: After installaing and removing lightdm-gtk-greeter lightdm is left in a not working state
** Changed in: lightdm-gtk-greeter (Ubuntu) Status: Incomplete => Invalid ** Changed in: unity-greeter (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/977069 Title: After installaing and removing lightdm-gtk-greeter lightdm is left in a not working state Status in lightdm-gtk-greeter package in Ubuntu: Invalid Status in unity-greeter package in Ubuntu: Invalid Bug description: expected behaviour: unity greeter is used again actual behaviour lightdm wont start, falling back to console ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Mon Apr 9 10:56:19 2012 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/977069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930355] Re: gnome-calendar crashes disabling/enabling or removing/readding calendar (Signal 6)
I solved the problem for myself by commenting out the offending line (212) from gcal-timeline.c and building and installing my own package. I don't know whether this could count as a real solution, but one doesn't lose anything except crashes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1930355 Title: gnome-calendar crashes disabling/enabling or removing/readding calendar (Signal 6) Status in gnome-calendar package in Ubuntu: New Bug description: Gnome-calendar crashes reliably under two conditions. First 1. Open GNOME Calendar 2. Goto Manage your calendars 3. Disable the display one of the calendars 4. Renenable it Second 1. Open GNOME Calendar 2. Goto Manage your calendars 3. Goto Manage Calendars ... 4. Select one calendar 5. Remove calendar 6. Close Window "Manage Calendars" 7. Goto Manage your calendars 8. Goto Manage Calendars ... 9. Choose "Add Calendar..." 10. Selected calendar file removed in step 5 via file selection dialog This is gnome-calendar 3.36.2 under up to date ubuntu 20.04 If I start gnome-calendar from a terminal I get as error messages: GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Aborted (core dumped) These are the same in both cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1930355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)
This bug was fixed in the package gnome-shell - 3.38.4-1ubuntu3 --- gnome-shell (3.38.4-1ubuntu3) impish; urgency=medium [ Daniel van Vugt ] * Add workspacesView-Only-use-valid-allocations-when-avail.patch. To stop bogus values being used in _updateWorkspacesActualGeometry(), which would cause the overview to fail to toggle. (LP: #1922353) [ Marco Trevisan (Treviño) ] * debian/patches: Refresh * debian/patches: Cherry-pick upstream calendar-server crash fix (LP: #1915929) -- Marco Trevisan (Treviño) Mon, 31 May 2021 18:51:34 +0200 ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1915929 Title: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in gnome-shell source package in Hirsute: Fix Committed Bug description: [ Impact ] gnome-shell-calendar-server crashes (and it seems to happen more in aarch64). https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1 [ Test case ] There's not a clear test case, but this is relevant: - Configure a supported calendar in your online accounts - GNOME shell should show your events in the calendar (under notifications panel) [ Regression potential ] gnome-shell-calendar-server may leak memory. --- M1 Mac mini Parallels Ubuntu VM ProblemType: CrashDistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic aarch64 ApportVersion: 2.20.11-0ubuntu58 Architecture: arm64 AssertionMessage: double free or corruption (fasttop) CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 17 04:34:36 2021 DisplayManager: gdm3 ExecutablePath: /usr/libexec/gnome-shell-calendar-server GsettingsChanges: b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']" b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true' InstallationDate: Installed on 2021-02-17 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217) ProcCmdline: /usr/libexec/gnome-shell-calendar-server ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x81245180 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x81240c08 "double free or corruption (fasttop)") at malloc.c:5389 _int_free (av=, p=0xe9eee300, have_lock=0) at malloc.c:4298 g_variant_builder_clear () from /lib/aarch64-linux-gnu/libglib-2.0.so.0 ?? () Title: gnome-shell-calendar-server assert failure: double free or corruption (fasttop) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
This bug was fixed in the package gnome-shell - 3.38.4-1ubuntu3 --- gnome-shell (3.38.4-1ubuntu3) impish; urgency=medium [ Daniel van Vugt ] * Add workspacesView-Only-use-valid-allocations-when-avail.patch. To stop bogus values being used in _updateWorkspacesActualGeometry(), which would cause the overview to fail to toggle. (LP: #1922353) [ Marco Trevisan (Treviño) ] * debian/patches: Refresh * debian/patches: Cherry-pick upstream calendar-server crash fix (LP: #1915929) -- Marco Trevisan (Treviño) Mon, 31 May 2021 18:51:34 +0200 ** Changed in: gnome-shell (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Hirsute: Fix Committed Status in gnome-shell source package in Impish: Fix Released Bug description: [Impact] Shell overview gets stuck where it's permanently toggled but not visible. Only app windows appear in their overview state. Can't interact with applications anymore. [Test Plan] 1. Log into GNOME. 2. Press Super+A 3. Click on 'Files' and wait till it has launched. 4. Press the Super key. Expect: Can interact with the application window. [Where problems could occur] Since the patch affects some of the core gnome-shell layout logic, anything is possible. Risk has been mitigated by the patch being small. [Original description] When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930485] Re: Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4.
Launchpad has imported 2 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1713986. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2021-06-02T01:29:27+00:00 Jameson Williams wrote: User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36 Steps to reproduce: I run the following on my Ubuntu 18.04 system: ```bash export XDG_RUNTIME_DIR=/run/weston export GDK_BACKEND=wayland export MOX_ENABLE_WAYLAND=1 export DISPLAY=wayland-0 export LD_LIBRARY_PATH=/usr/lib:/usr/lib/aarch64-linux-gnu/ export WAYLAND_DEBUG=1 export WAYLAND_DISPLAY=wayland-0 firefox \ --g-fatal-warnings \ --kiosk \ --private-window \ https://bing.com ``` Actual results: Firefox does not start. Instead, I get this output, only: ``` [1446891.592] -> wl_display@1.get_registry(new id wl_registry@2) [1446891.702] -> wl_disp...@1.sync(new id wl_callback@3) [1446893.656] wl_display@1.delete_id(3) [1446893.737] wl_registry@2.global(1, "wl_compositor", 4) [1446893.781] -> wl_regis...@2.bind(1, "wl_compositor", 3, new id [unknown]@4) [1446893.852] wl_registry@2.global(2, "wl_subcompositor", 1) [1446893.889] -> wl_regis...@2.bind(2, "wl_subcompositor", 1, new id [unknown]@5) [1446893.938] wl_registry@2.global(3, "wp_viewporter", 1) [1446893.973] wl_registry@2.global(4, "wp_presentation", 1) [1446894.007] wl_registry@2.global(5, "zwp_relative_pointer_manager_v1", 1) [1446894.041] wl_registry@2.global(6, "zwp_pointer_constraints_v1", 1) [1446894.075] wl_registry@2.global(7, "wl_data_device_manager", 3) [1446894.109] -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id [unknown]@6) [1446894.156] wl_registry@2.global(8, "wl_shm", 1) [1446894.190] -> wl_regis...@2.bind(8, "wl_shm", 1, new id [unknown]@7) [1446894.429] -> wl_shm@7.create_pool(new id wl_shm_pool@8, fd 9, 2304) [1446894.974] -> wl_shm_pool@8.resize(5568) [1446895.214] -> wl_shm_pool@8.resize(12096) [1446895.273] wl_registry@2.global(9, "wayland_buffer_backend", 4) [1446895.315] wl_registry@2.global(10, "wl_seat", 5) [1446895.353] -> wl_regis...@2.bind(10, "wl_seat", 5, new id [unknown]@9) [1446925.977] -> wl_compositor@4.create_surface(new id wl_surface@10) [1446926.203] -> wl_data_device_manager@6.get_data_device(new id wl_data_device@11, wl_seat@9) [1446926.370] -> wl_compositor@4.create_surface(new id wl_surface@12) [1446926.636] -> wl_disp...@1.sync(new id wl_callback@13) [1446926.765] wl_registry@2.global(11, "zwp_linux_dmabuf_v1", 3) [1446926.845] wl_registry@2.global(12, "gbm_buffer_backend", 1) [1446926.906] wl_registry@2.global(13, "wl_output", 3) [1446926.965] -> wl_regis...@2.bind(13, "wl_output", 2, new id [unknown]@14) [1446927.172] -> wl_disp...@1.sync(new id wl_callback@15) [1446927.246] wl_registry@2.global(14, "zwp_input_panel_v1", 1) [1446927.319] wl_registry@2.global(15, "zwp_input_method_v1", 1) [1446927.378] wl_registry@2.global(16, "zwp_text_input_manager_v1", 1) [1446927.436] wl_registry@2.global(17, "zxdg_shell_v6", 1) [1446927.494] wl_registry@2.global(18, "xdg_shell", 1) [1446927.585] wl_registry@2.global(19, "wl_shell", 1) [1446927.643] wl_registry@2.global(20, "weston_desktop_shell", 1) [1446927.716] wl_registry@2.global(21, "weston_screenshooter", 1) [1446927.777] wl_callb...@3.done(1) [1446929.537] wl_display@1.delete_id(13) [1446929.624] wl_display@1.delete_id(15) [1446929.656] wl_shm@7.format(0) [1446929.684] wl_shm@7.format(1) [1446929.709] wl_shm@7.format(909199186) [1446929.733] wl_shm@7.format(842093913) [1446929.758] wl_shm@7.format(842094158) [1446929.783] wl_shm@7.format(1448695129) [1446929.807] wl_seat@9.capabilities(2) [1446929.834] -> wl_seat@9.get_keyboard(new id wl_keyboard@3) [1446929.903] wl_s...@9.name("default") [1446929.931] wl_callb...@13.done(1) [1446929.958] wl_output@14.geometry(0, 0, 0, 0, 0, "QCM", "unknown", 0) [1446930.094] wl_output@14.scale(1) [1446930.123] wl_out...@14.mode(3, 1920, 1080, 6) [1446930.193] wl_out...@14.done() [1446930.245] wl_callb...@15.done(1) [1446930.278] -> wl_regis...@2.bind(17, "zxdg_shell_v6", 1, new id [unknown]@15) Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI returned an error (t=0.548409) [GFX1-]: glxtest: eglBindAPI returned an error Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed (t=0.548476) [GFX1-]: glxtest: EGL test failed Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed (t=0.548476) |[2][GFX1-]: No GPUs detected via PCI (t=0.548504) [GFX1-]: No GPUs detected via
[Desktop-packages] [Bug 1930485] Re: Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4.
** Summary changed: - Can't Start Firefox 88 on Ubuntu 18.0.4. + Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930485 Title: Can't Start Firefox 88 on Weston/Wayland, Ubuntu 18.0.4. Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: New Bug description: I am running Weston/Wayland on Ubuntu 18.0.4. I am able to successfully start the display server: ``` export XDG_RUNTIME_DIR=/run/weston weston --tty 1 & ``` Next, I try to run firefox on it: ``` export XDG_RUNTIME_DIR=/run/weston export GDK_BACKEND=wayland export MOZ_ENABLE_WAYLAND=1 export DISPLAY=wayland-0 export LD_LIBRARY_PATH=/usr/lib:/usr/lib/aarch64-linux-gnu/ export WAYLAND_DEBUG=1 export WAYLAND_DISPLAY=wayland-0 firefox \ --g-fatal-warnings \ --kiosk \ --private-window \ https://bing.com ``` This outputs: ``` [1446891.592] -> wl_display@1.get_registry(new id wl_registry@2) [1446891.702] -> wl_disp...@1.sync(new id wl_callback@3) [1446893.656] wl_display@1.delete_id(3) [1446893.737] wl_registry@2.global(1, "wl_compositor", 4) [1446893.781] -> wl_regis...@2.bind(1, "wl_compositor", 3, new id [unknown]@4) [1446893.852] wl_registry@2.global(2, "wl_subcompositor", 1) [1446893.889] -> wl_regis...@2.bind(2, "wl_subcompositor", 1, new id [unknown]@5) [1446893.938] wl_registry@2.global(3, "wp_viewporter", 1) [1446893.973] wl_registry@2.global(4, "wp_presentation", 1) [1446894.007] wl_registry@2.global(5, "zwp_relative_pointer_manager_v1", 1) [1446894.041] wl_registry@2.global(6, "zwp_pointer_constraints_v1", 1) [1446894.075] wl_registry@2.global(7, "wl_data_device_manager", 3) [1446894.109] -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id [unknown]@6) [1446894.156] wl_registry@2.global(8, "wl_shm", 1) [1446894.190] -> wl_regis...@2.bind(8, "wl_shm", 1, new id [unknown]@7) [1446894.429] -> wl_shm@7.create_pool(new id wl_shm_pool@8, fd 9, 2304) [1446894.974] -> wl_shm_pool@8.resize(5568) [1446895.214] -> wl_shm_pool@8.resize(12096) [1446895.273] wl_registry@2.global(9, "wayland_buffer_backend", 4) [1446895.315] wl_registry@2.global(10, "wl_seat", 5) [1446895.353] -> wl_regis...@2.bind(10, "wl_seat", 5, new id [unknown]@9) [1446925.977] -> wl_compositor@4.create_surface(new id wl_surface@10) [1446926.203] -> wl_data_device_manager@6.get_data_device(new id wl_data_device@11, wl_seat@9) [1446926.370] -> wl_compositor@4.create_surface(new id wl_surface@12) [1446926.636] -> wl_disp...@1.sync(new id wl_callback@13) [1446926.765] wl_registry@2.global(11, "zwp_linux_dmabuf_v1", 3) [1446926.845] wl_registry@2.global(12, "gbm_buffer_backend", 1) [1446926.906] wl_registry@2.global(13, "wl_output", 3) [1446926.965] -> wl_regis...@2.bind(13, "wl_output", 2, new id [unknown]@14) [1446927.172] -> wl_disp...@1.sync(new id wl_callback@15) [1446927.246] wl_registry@2.global(14, "zwp_input_panel_v1", 1) [1446927.319] wl_registry@2.global(15, "zwp_input_method_v1", 1) [1446927.378] wl_registry@2.global(16, "zwp_text_input_manager_v1", 1) [1446927.436] wl_registry@2.global(17, "zxdg_shell_v6", 1) [1446927.494] wl_registry@2.global(18, "xdg_shell", 1) [1446927.585] wl_registry@2.global(19, "wl_shell", 1) [1446927.643] wl_registry@2.global(20, "weston_desktop_shell", 1) [1446927.716] wl_registry@2.global(21, "weston_screenshooter", 1) [1446927.777] wl_callb...@3.done(1) [1446929.537] wl_display@1.delete_id(13) [1446929.624] wl_display@1.delete_id(15) [1446929.656] wl_shm@7.format(0) [1446929.684] wl_shm@7.format(1) [1446929.709] wl_shm@7.format(909199186) [1446929.733] wl_shm@7.format(842093913) [1446929.758] wl_shm@7.format(842094158) [1446929.783] wl_shm@7.format(1448695129) [1446929.807] wl_seat@9.capabilities(2) [1446929.834] -> wl_seat@9.get_keyboard(new id wl_keyboard@3) [1446929.903] wl_s...@9.name("default") [1446929.931] wl_callb...@13.done(1) [1446929.958] wl_output@14.geometry(0, 0, 0, 0, 0, "QCM", "unknown", 0) [1446930.094] wl_output@14.scale(1) [1446930.123] wl_out...@14.mode(3, 1920, 1080, 6) [1446930.193] wl_out...@14.done() [1446930.245] wl_callb...@15.done(1) [1446930.278] -> wl_regis...@2.bind(17, "zxdg_shell_v6", 1, new id [unknown]@15) Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI returned an error (t=0.548409) [GFX1-]: glxtest: eglBindAPI returned an error Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed (t=0.548476) [GFX1-]: glxtest: EGL test failed Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed (t=0.548476) |[2
[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1926062 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930460] Re: HP Probook 470 G5 does not wake from sleep (just a black screen)
Thanks for the bug report. Next time the problem happens and you get the black screen, please: 1. Wait 10 seconds. 2. Reboot. 3. Open a Terminal and run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Summary changed: - i have blank screen after some time on sleep mode, or just restart while in sleep mode + HP Probook 470 G5 does not wake from sleep (just a black screen) ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1930460 Title: HP Probook 470 G5 does not wake from sleep (just a black screen) Status in linux package in Ubuntu: Incomplete Bug description: I have HP Probook 470 G5, first I installed Ubuntu 18.04 and then upgraded to 20.04, in both cases the same problem arrived. I have disabled sleep mode, but also, if I intensionally put laptop in sleep mode the same thing happened. Sometimes when I try to wake him up, its just black screen and I cant do anything, I have to do hard restart (on button) Or when I try to wake him from sleep, i can do that, but i see that laptop has been restarted. Please exuce my bad English, I hope you understand me. I am beginner with Linux , and I dont have any idea how to solve this problem on my own Thank you very much on your help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 21:25:03 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-09-03 (271 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-15 (229 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930485] [NEW] Can't Start Firefox 88 on Ubuntu 18.0.4.
Public bug reported: I am running Weston/Wayland on Ubuntu 18.0.4. I am able to successfully start the display server: ``` export XDG_RUNTIME_DIR=/run/weston weston --tty 1 & ``` Next, I try to run firefox on it: ``` export XDG_RUNTIME_DIR=/run/weston export GDK_BACKEND=wayland export MOZ_ENABLE_WAYLAND=1 export DISPLAY=wayland-0 export LD_LIBRARY_PATH=/usr/lib:/usr/lib/aarch64-linux-gnu/ export WAYLAND_DEBUG=1 export WAYLAND_DISPLAY=wayland-0 firefox \ --g-fatal-warnings \ --kiosk \ --private-window \ https://bing.com ``` This outputs: ``` [1446891.592] -> wl_display@1.get_registry(new id wl_registry@2) [1446891.702] -> wl_disp...@1.sync(new id wl_callback@3) [1446893.656] wl_display@1.delete_id(3) [1446893.737] wl_registry@2.global(1, "wl_compositor", 4) [1446893.781] -> wl_regis...@2.bind(1, "wl_compositor", 3, new id [unknown]@4) [1446893.852] wl_registry@2.global(2, "wl_subcompositor", 1) [1446893.889] -> wl_regis...@2.bind(2, "wl_subcompositor", 1, new id [unknown]@5) [1446893.938] wl_registry@2.global(3, "wp_viewporter", 1) [1446893.973] wl_registry@2.global(4, "wp_presentation", 1) [1446894.007] wl_registry@2.global(5, "zwp_relative_pointer_manager_v1", 1) [1446894.041] wl_registry@2.global(6, "zwp_pointer_constraints_v1", 1) [1446894.075] wl_registry@2.global(7, "wl_data_device_manager", 3) [1446894.109] -> wl_regis...@2.bind(7, "wl_data_device_manager", 3, new id [unknown]@6) [1446894.156] wl_registry@2.global(8, "wl_shm", 1) [1446894.190] -> wl_regis...@2.bind(8, "wl_shm", 1, new id [unknown]@7) [1446894.429] -> wl_shm@7.create_pool(new id wl_shm_pool@8, fd 9, 2304) [1446894.974] -> wl_shm_pool@8.resize(5568) [1446895.214] -> wl_shm_pool@8.resize(12096) [1446895.273] wl_registry@2.global(9, "wayland_buffer_backend", 4) [1446895.315] wl_registry@2.global(10, "wl_seat", 5) [1446895.353] -> wl_regis...@2.bind(10, "wl_seat", 5, new id [unknown]@9) [1446925.977] -> wl_compositor@4.create_surface(new id wl_surface@10) [1446926.203] -> wl_data_device_manager@6.get_data_device(new id wl_data_device@11, wl_seat@9) [1446926.370] -> wl_compositor@4.create_surface(new id wl_surface@12) [1446926.636] -> wl_disp...@1.sync(new id wl_callback@13) [1446926.765] wl_registry@2.global(11, "zwp_linux_dmabuf_v1", 3) [1446926.845] wl_registry@2.global(12, "gbm_buffer_backend", 1) [1446926.906] wl_registry@2.global(13, "wl_output", 3) [1446926.965] -> wl_regis...@2.bind(13, "wl_output", 2, new id [unknown]@14) [1446927.172] -> wl_disp...@1.sync(new id wl_callback@15) [1446927.246] wl_registry@2.global(14, "zwp_input_panel_v1", 1) [1446927.319] wl_registry@2.global(15, "zwp_input_method_v1", 1) [1446927.378] wl_registry@2.global(16, "zwp_text_input_manager_v1", 1) [1446927.436] wl_registry@2.global(17, "zxdg_shell_v6", 1) [1446927.494] wl_registry@2.global(18, "xdg_shell", 1) [1446927.585] wl_registry@2.global(19, "wl_shell", 1) [1446927.643] wl_registry@2.global(20, "weston_desktop_shell", 1) [1446927.716] wl_registry@2.global(21, "weston_screenshooter", 1) [1446927.777] wl_callb...@3.done(1) [1446929.537] wl_display@1.delete_id(13) [1446929.624] wl_display@1.delete_id(15) [1446929.656] wl_shm@7.format(0) [1446929.684] wl_shm@7.format(1) [1446929.709] wl_shm@7.format(909199186) [1446929.733] wl_shm@7.format(842093913) [1446929.758] wl_shm@7.format(842094158) [1446929.783] wl_shm@7.format(1448695129) [1446929.807] wl_seat@9.capabilities(2) [1446929.834] -> wl_seat@9.get_keyboard(new id wl_keyboard@3) [1446929.903] wl_s...@9.name("default") [1446929.931] wl_callb...@13.done(1) [1446929.958] wl_output@14.geometry(0, 0, 0, 0, 0, "QCM", "unknown", 0) [1446930.094] wl_output@14.scale(1) [1446930.123] wl_out...@14.mode(3, 1920, 1080, 6) [1446930.193] wl_out...@14.done() [1446930.245] wl_callb...@15.done(1) [1446930.278] -> wl_regis...@2.bind(17, "zxdg_shell_v6", 1, new id [unknown]@15) Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI returned an error (t=0.548409) [GFX1-]: glxtest: eglBindAPI returned an error Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed (t=0.548476) [GFX1-]: glxtest: EGL test failed Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: eglBindAPI returned an error (t=0.548409) |[1][GFX1-]: glxtest: EGL test failed (t=0.548476) |[2][GFX1-]: No GPUs detected via PCI (t=0.548504) [GFX1-]: No GPUs detected via PCI [1447360.209] -> wl_display@1.get_registry(new id wl_registry@13) [1447360.288] -> wl_disp...@1.sync(new id wl_callback@16) [1447362.605] wl_display@1.delete_id(16) [1447362.653] wl_keyboard@3.repeat_info(40, 400) [1447362.676] wl_keyboard@3.keymap(1, fd 3, 48257) [1447365.368] wl_registry@13.global(1, "wl_compositor", 4) [1447365.420] -> wl_regis...@13.bind(1, "wl_compositor", 4, new id [unknown]@17) [1447365.483] wl_registry@13.global(2, "wl_subcompositor", 1) [1447365.512] -> wl_regis...@13.bind(2,
[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Summary changed: - [hirsute] Can't turn bluetooth on again after turning it off + [hirsute/impish] Can't turn bluetooth on again after turning it off -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930409] Re: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...
> It gives me a popup "error occured" every time I reboot.. Error popups mean something has crashed, whereas the error message here doesn't look like a crash. If you would like to report the popup/crash then please follow these instructions: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930409 Title: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ... Status in pulseaudio package in Ubuntu: Incomplete Bug description: Not sure if the bluez error is related, perhaps not (this is a desktop without Wifi/Bluetooth). jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired,> Intel i3-9100, C246 chipset, 32GB ram. Ubuntu Budgie 21.04 installed via usb boot disk. It gives me a popup "error occured" every time I reboot.. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asterix1749 F pulseaudio CasperMD5CheckResult: pass Date: Tue Jun 1 12:48:36 2021 InstallationDate: Installed on 2021-05-11 (21 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.release: 1.6 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x dmi.board.name: D3644-B1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3644-B1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr: dmi.product.family: OEM-FTS dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930409] Re: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ...
> It gives me a popup "error occured" every time I reboot.. Error popups mean something has crashed, whereas the error message here doesn't look like a crash. If you would like this bug to be about the popup/crash then please follow these instructions for reporting a crash: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. ** Summary changed: - Pulseaudio org.freedesktop.dbus error on boot after clean 21.04 install + Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930409 Title: Pulseaudio 14.2 says: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. ... Status in pulseaudio package in Ubuntu: Incomplete Bug description: Not sure if the bluez error is related, perhaps not (this is a desktop without Wifi/Bluetooth). jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired,> Intel i3-9100, C246 chipset, 32GB ram. Ubuntu Budgie 21.04 installed via usb boot disk. It gives me a popup "error occured" every time I reboot.. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asterix1749 F pulseaudio CasperMD5CheckResult: pass Date: Tue Jun 1 12:48:36 2021 InstallationDate: Installed on 2021-05-11 (21 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.release: 1.6 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x dmi.board.name: D3644-B1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3644-B1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr: dmi.product.family: OEM-FTS dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930371] Re: top bar displayed on top of a fullscreen window that gets moved from one monitor to another
** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4351 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1930371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874578] Re: Dock has very long load time when show-mounts is enabled
Petr, in that case this is the wrong bug for you and you should open a new bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1874578 Title: Dock has very long load time when show-mounts is enabled Status in Dash to dock: New Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930305] Re: [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all
If you choose Headphone or Headset, the headphone should work; if you choose Microphone, the headphone will not output sound anymore. When you have chance, please verify it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1930305 Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello, So I use Ubuntu 20.04 LTS for a month. Firstly thank you for such a good and progressive operating system. Here is the problem: Normally, sound works perfectly when the output device is speakers. It is also works when I plugged in the headphone on PC when the system is on. However whenever I try to plug in the headphone when the system is locked (on locked screen) the headphone does not work anymore even I restart. But it works when I try to plug in it when the lock screen is not active on next day. It is not working right now. The list of Output Devices in the Settings: - Speakers - Built-in Audio - Headphones - Built-in Audio When I select headphones, the sound is gone at all. Also yes, I tried to use headphone on another devices and they work perfectly. I will put all informations that you might want. Please let me know if you need more information. I am also not sure if I chose the right output device. Thank you. Release: Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:29:49 2021 InstallationDate: Installed on 2021-05-26 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 05VVC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/27/2019:efr1.1:svnDellInc.:pnInspiron5537:pvrA12:rvnDellInc.:rn05VVC5:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 00 dmi.product.name: Inspiron 5537 dmi.product.sku: Inspiron 5537 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1930305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930476] Re: my internal Bluetooth device is off and i can turn it ON but the settings still show it to be OFF
The attachment "Bluetooth is active in setting but its off in menu" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1930476 Title: my internal Bluetooth device is off and i can turn it ON but the settings still show it to be OFF Status in alsa-driver package in Ubuntu: New Bug description: i update grub after that Bluetooth device is deactive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mehdi 2237 F pulseaudio /dev/snd/controlC1: mehdi 2237 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 2 03:04:07 2021 InstallationDate: Installed on 2021-05-22 (10 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 3.43 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: NO DPK dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.ec.firmware.release: 3.43 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:br3.43:efr3.43:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.sku: LENOVO_MT_20378_BU_idea_FM_Lenovo Y50-70 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1930476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930305] Re: [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all
Hello, thanks for your response. I am not on PC now. I can upload log.txt tomorrow I guess. For the first question I tried both inputs and they do not work. The PC's and also the headphone's. Well, for the second question actually I do not choose any of them. Because the sound also gone if I choose any of them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1930305 Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello, So I use Ubuntu 20.04 LTS for a month. Firstly thank you for such a good and progressive operating system. Here is the problem: Normally, sound works perfectly when the output device is speakers. It is also works when I plugged in the headphone on PC when the system is on. However whenever I try to plug in the headphone when the system is locked (on locked screen) the headphone does not work anymore even I restart. But it works when I try to plug in it when the lock screen is not active on next day. It is not working right now. The list of Output Devices in the Settings: - Speakers - Built-in Audio - Headphones - Built-in Audio When I select headphones, the sound is gone at all. Also yes, I tried to use headphone on another devices and they work perfectly. I will put all informations that you might want. Please let me know if you need more information. I am also not sure if I chose the right output device. Thank you. Release: Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:29:49 2021 InstallationDate: Installed on 2021-05-26 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 05VVC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/27/2019:efr1.1:svnDellInc.:pnInspiron5537:pvrA12:rvnDellInc.:rn05VVC5:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 00 dmi.product.name: Inspiron 5537 dmi.product.sku: Inspiron 5537 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1930305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926989] Re: lpoptions command won't create a new printer instance
*** This bug is a duplicate of bug 1930477 *** https://bugs.launchpad.net/bugs/1930477 ** This bug has been marked a duplicate of bug 1930477 cups 2.3.1 does not enumerate printer instances that are set up with lpoptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1926989 Title: lpoptions command won't create a new printer instance Status in cups package in Ubuntu: New Bug description: Running the following command : sudo lpoptions -p Letters/test -o InputSlot=Tray5 returns without error sudo lpoptions -p Letters/test -l Shows that the the above command had no effect InputSlot=Auto After running the commands, there is no file /etc/cups/lpoptions Even if an lpoptions file is created manually, it has no effect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-Gray..\' already exists W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-RGB..\' already exists W [03/May/2021:11:20:51 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-Gray..\' already exists W [03/May/2021:11:20:51 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-DeviceN..\' already exists Date: Mon May 3 11:39:40 2021 InstallationDate: Installed on 2021-04-27 (5 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lpstat: device for Letters: dnssd://HP%20LaserJet%20600%20M602%20%5B66D356%5D._ipp._tcp.local/?uuid=a9f85a02-21b1-11e3-9d3a-1556bd6228ad MachineType: LENOVO 10ST00A6US Papersize: letter PpdFiles: Letters: HP LaserJet 600 M602, driverless, cups-filters 1.27.4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=abf53fc0-1910-4d2d-b58d-2e356575d519 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.release: 1.80 dmi.bios.vendor: LENOVO dmi.bios.version: M1UKT50A dmi.board.name: 312A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305279232807 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrM1UKT50A:bd02/17/2020:br1.80:efr1.24:svnLENOVO:pn10ST00A6US:pvrThinkCentreM720s:rvnLENOVO:rn312A:rvrSDK0J40697WIN3305279232807:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M720s dmi.product.name: 10ST00A6US dmi.product.sku: LENOVO_MT_10ST_BU_Think_FM_ThinkCentre M720s dmi.product.version: ThinkCentre M720s dmi.sys.vendor: LENOVO modified.conffile..etc.cups.snmp.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1926989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930477] [NEW] cups 2.3.1 does not enumerate printer instances that are set up with lpoptions
Public bug reported: We use printer instances (PRINTER/instance) that are defined in /etc/cups/lpoptions Printer instances don't work properly with Ubuntu 20.04 and cups 2.3.1. We have used the same lpoptions file with earlier versions of cups. With 2.3.1, the command: lp PRINTER/instance FILENAME works But the printer instances are not visible as printers in the libreoffice print dialog, or by using lpstat -e or lpstat -a. There is a recent fix in the uplevel cups code for printer instances. We did our own make and install of the uplevel master branch 2.3.5 and printer instances are working now. We hope that ubuntu 20.04 can soon include the 2.3.5 cups code. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups (not installed) ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jun 1 16:37:10 2021 InstallationDate: Installed on 2021-03-08 (85 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1930477 Title: cups 2.3.1 does not enumerate printer instances that are set up with lpoptions Status in cups package in Ubuntu: New Bug description: We use printer instances (PRINTER/instance) that are defined in /etc/cups/lpoptions Printer instances don't work properly with Ubuntu 20.04 and cups 2.3.1. We have used the same lpoptions file with earlier versions of cups. With 2.3.1, the command: lp PRINTER/instance FILENAME works But the printer instances are not visible as printers in the libreoffice print dialog, or by using lpstat -e or lpstat -a. There is a recent fix in the uplevel cups code for printer instances. We did our own make and install of the uplevel master branch 2.3.5 and printer instances are working now. We hope that ubuntu 20.04 can soon include the 2.3.5 cups code. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups (not installed) ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jun 1 16:37:10 2021 InstallationDate: Installed on 2021-03-08 (85 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1930477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930476] [NEW] my internal Bluetooth device is off and i can turn it ON but the settings still show it to be OFF
Public bug reported: i update grub after that Bluetooth device is deactive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mehdi 2237 F pulseaudio /dev/snd/controlC1: mehdi 2237 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 2 03:04:07 2021 InstallationDate: Installed on 2021-05-22 (10 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 3.43 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: NO DPK dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.ec.firmware.release: 3.43 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:br3.43:efr3.43:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.sku: LENOVO_MT_20378_BU_idea_FM_Lenovo Y50-70 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Patch added: "Bluetooth is active in setting but its off in menu" https://bugs.launchpad.net/bugs/1930476/+attachment/5501755/+files/Screenshot%20from%202021-06-02%2003-09-38.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1930476 Title: my internal Bluetooth device is off and i can turn it ON but the settings still show it to be OFF Status in alsa-driver package in Ubuntu: New Bug description: i update grub after that Bluetooth device is deactive. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mehdi 2237 F pulseaudio /dev/snd/controlC1: mehdi 2237 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 2 03:04:07 2021 InstallationDate: Installed on 2021-05-22 (10 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 3.43 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.asset.tag: NO DPK dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO DPK dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.ec.firmware.release: 3.43 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:br3.43:efr3.43:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNODPK:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.sku: LENOVO_MT_20378_BU_idea_FM_Lenovo Y50-70 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1930476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
Hello jeremyszu, or anyone else affected, Accepted pulseaudio into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: Triaged Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Committed Bug description: [Impact] In Lenovo P520, which using a codec for front panel, the other codec for rear panel and both are on a same card. In this case, the rear Mic will present on input devices of "Sound Settings" even if attaching nothing to rear mic jack. [Fix] For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl because of ``` control.18 { iface CARD name 'Rear Mic Jack' value true comment { access read type BOOLEAN count 1 } } ``` After applying "Rear Mic Jack", the rear Mic will not always there anymore but it's not there as well if hot-plugging audio device on rear mic. Thus, it needs to change pulseaudio to handle if all devices are off cases. For pulseaudio, if there is no any audio devices attached, then attaching an input device on rear mic jack. The port will not be selected automatically because the profiles is off. It needs patch pulseaudio to check off profiles (for dual codec case). [Test] After applying these patches, the rear mic jack works good in all cases (boot without mic and then attach mic, boot with mic and then hotplug it) and other functions (line-in / line-out) work pretty well. [Where problems could occur] This change only apply the bonus on below cases: ``` if ((has_input_port && found_available_input_port && !has_output_port) || (has_output_port && found_available_output_port && !has_input_port) || (has_input_port && found_available_input_port && has_output_port && found_available_output_port)) ``` and these cases have been tested. If there are some complex codec design then it might cause problem but so far we didn't see that. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929817] Re: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only)
Hello Hui, or anyone else affected, Accepted pulseaudio into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929817 Title: [SRU] pulseaudio: let a single alsa mixer support up to 8 channels (focal only) Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Bug description: [Impact] Many Lenovo laptops have up to 4 microphones (microphone array), before the linux kernel 5.11, the alsa mixer for digital microphone is 2 channels, and the PA in the focal also supports up to 2 chanels for a single alsa mixer, so the PA in the focal works well with linux kernel 5.10 and lower on those Lenovo laptops. But we are going to install hirsute kernel (5.11) to the focal, the PA in the focal can't handle 4 channels of the digital mic, it will use pure software volume for digital mic, user can't adjust hardware volume of the digital mic anymore. [Fix] Backport 2 patches from PA-14.2, the PA in the hirsute (21.04) already have these 2 patches, so this SRU is for focal only. After applying these 2 patches, the PA could handle up to 8 channels for a single alsa mixer. [Test] Install patched PA on Lenovo laptops with 4 digital microphone, I could change the hardware input volume of digital mic through pulseaudio. I also installed patched PA to some old lenovo and Dell machines, all output and input devices worked as well as before, there is no regression observed. [Where problems could occur] This could introduce a regression on the output/input volume control, for example, the output or input volume only supports software volume in the PA, users can't adjust the hardware volume through pulseaudio anymore. But this regression possibility is very low, first the hirsute already has these 2 patches, second I already tested these 2 patches on different machines, all worked as well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1929817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930167] Re: New Firefox 88 freezes on Wayland then system crash
So, I've questions about this bug if it comes from firefox, or mutter, or wayland because every time I try use Firefox 88 the Wayland session freezes and nothing else works besides Magic Key to restart my machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1930167 Title: New Firefox 88 freezes on Wayland then system crash Status in firefox package in Ubuntu: Incomplete Bug description: After updating firefox deb to version 88, every time I play YouTube videos, some times in several tabs, then Wayland crashes and the system freezes. For try workaround this crash, I've to use the magic key SysRq (Alt + SysReq) with "REISUB" characters to safely reboot my Ubuntu though. Every time I open Firefox 88 deb via console, the message below appears even though these modules are installed: Gtk-Message: 14:01:56.615: Failed to load module "appmenu-gtk-module" Gtk-Message: 14:01:56.662: Failed to load module "canberra-gtk-module" Gtk-Message: 14:01:56.664: Failed to load module "canberra-gtk-module" /usr/share/libdrm/amdgpu.ids: No such file or directory I'm currently using Firefox 78 ESR snap because the main installation is unusable, unfortunately ... Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 88.0.1+build1-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: douglas 15771 F pulseaudio /dev/snd/controlC2: douglas 15771 F pulseaudio /dev/snd/controlC0: douglas 15771 F pulseaudio BuildID: 20210504152106 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 30 13:54:03 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-11-12 (198 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.2 metric 100 MostRecentCrashID: bp-09389e82-1bfb-43fe-bd10-2b8940210408 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=84.0.2/20210105180113 (Out of date) Profile0 - LastVersion=88.0.1/20210504152106 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-09389e82-1bfb-43fe-bd10-2b8940210408 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50d dmi.board.asset.tag: Default string dmi.board.name: AB350M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50d:bd07/02/2020:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B350 MB dmi.product.name: AB350M-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
Hello jeremyszu, or anyone else affected, Accepted pulseaudio into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:14.2-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: Triaged Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: Fix Committed Bug description: [Impact] In Lenovo P520, which using a codec for front panel, the other codec for rear panel and both are on a same card. In this case, the rear Mic will present on input devices of "Sound Settings" even if attaching nothing to rear mic jack. [Fix] For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl because of ``` control.18 { iface CARD name 'Rear Mic Jack' value true comment { access read type BOOLEAN count 1 } } ``` After applying "Rear Mic Jack", the rear Mic will not always there anymore but it's not there as well if hot-plugging audio device on rear mic. Thus, it needs to change pulseaudio to handle if all devices are off cases. For pulseaudio, if there is no any audio devices attached, then attaching an input device on rear mic jack. The port will not be selected automatically because the profiles is off. It needs patch pulseaudio to check off profiles (for dual codec case). [Test] After applying these patches, the rear mic jack works good in all cases (boot without mic and then attach mic, boot with mic and then hotplug it) and other functions (line-in / line-out) work pretty well. [Where problems could occur] This change only apply the bonus on below cases: ``` if ((has_input_port && found_available_input_port && !has_output_port) || (has_output_port && found_available_output_port && !has_input_port) || (has_input_port && found_available_input_port && has_output_port && found_available_output_port)) ``` and these cases have been tested. If there are some complex codec design then it might cause problem but so far we didn't see that. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295247] Re: [Logitech C170] Cheese says "There was an error playing video from webcam"
Same issue here after upgrading to 21.04. Never had any issues before. cam is microsoft hd-3000 sudo apt install guvcview and switch back to default resolution (in my case 720) did the trick for me as stated before. thanks btw. after that cheese and other voip program work well -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1295247 Title: [Logitech C170] Cheese says "There was an error playing video from webcam" Status in cheese package in Ubuntu: Incomplete Bug description: Whenever I open Cheese in Ubuntu 14.04 beta 1 (Unity), my external Logitech C170 webcam's light turns on once, then it turns off and Cheese turns black, written "There was an error playing video from webcam". This never happened in any previous versions of Ubuntu. The problem is reproducible. WORKAROUND: In Cheese preferences lower image resolution to 640x480. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cheese 3.10.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CurrentDesktop: Unity Date: Thu Mar 20 22:29:57 2014 InstallationDate: Installed on 2014-03-20 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140225) SourcePackage: cheese UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1295247/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886161] Re: Unattended upgrades should work on roaming laptops
@Julian Thanks for the explanation and the tip. Auto-retries would be a really beneficial feature but I get that you have a lot on your plate. Thanks for your work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: Unattended upgrades should work on roaming laptops Status in apt package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866059] Re: firefox-locale-* packages do not enable localization => post-install localization is not complete
This bug was fixed in the package thunderbird - 1:78.8.1+build1-0ubuntu0.18.04.1 --- thunderbird (1:78.8.1+build1-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream stable release (78.8.1build1) (LP: #1895643) - debian/config/branch.mk * Bump build dependency on rustc >= 1.41.0 and cargo >= 0.42 - debian/control{,.in} * Bump build dependency on nodejs-mozilla >= 10.21 - debian/control{,.in} * Bump build dependency on nasm-mozilla >= 2.14.02 - debian/control{,.in} * Bump build dependency on debhelper >= 9 - debian/compat - debian/control{,.in} * Port packaging to python3 - debian/build/Expression.py - debian/build/Preprocessor.py - debian/build/create-tarball.py - debian/build/fix-mozinfo-appname.py - debian/build/keepalive-wrapper.py - debian/build/rules.mk - debian/build/xpi-id.py - debian/control{,.in} * Clean up unused code paths in packaging rules - debian/rules - debian/build/config.mk - debian/config/mozconfig.in * Update cbindgen to 0.17.0 - debian/build/create-tarball.py * Work around clang hanging forever when trying to optimize the build of the embedded copy of sqlite3 (LP: #1878292) - debian/patches/s390x-workaround-sqlite3-clang-optimization-hang.patch * Remove obsolete config options - debian/config/mozconfig.in * Allow sideloading langpacks (LP: #1866059) - debian/config/mozconfig.in * Make xul-ext-lightning a transitional empty package, now that calendar functionality is part of the Thunderbird core - debian/build/rules.mk - debian/control{,.in} - debian/rules * Separately installed blocklist.xml was removed - debian/thunderbird.install.in * Install WeTransfer extension to the features directory - debian/thunderbird.install.in * Add the following locales: af, en-CA, fa, ja-JP-mac, pa-IN, th - update debian/config/locales.{all,shipped} * Remove upstreamed patch - debian/patches/nss_disable_fips_enabled_flag.patch * Update and rename patch to selectively reduce debug info level - debian/patches/reduce-rust-debuginfo-on-selected-architectures.patch * Refresh patches - debian/patches/rust-drop-dll-checksums.patch - debian/patches/support-coinstallable-trunk-build.patch * Updates patches - debian/patches/unity-menubar.patch * Cherry-pick 3 upstream commits to fix building ICU on big-endian architectures (e.g. s390x) - debian/patches/upstream-icu-fixes.patch * Add a missing linker flag to build icupkg on s390x - debian/patches/s390x-fix-icupkg-build.patch * Drop armel arch references - debian/control{,.in} - debian/build/rules.mk * Add generic logic to target different LLVM toolchains - debian/config/mozconfig.in - debian/control{,.in} - debian/build/rules.mk * Make thunderbird suggest libotr5 - debian/control{,.in} * Add versioned breaks on enigmail and jsunit - debian/control{,.in} * Allow the use of external GPG keyrings by default - debian/vendor.js -- Olivier Tilloy Wed, 17 Mar 2021 15:37:52 +0100 ** Changed in: thunderbird (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1866059 Title: firefox-locale-* packages do not enable localization => post-install localization is not complete Status in firefox package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Fix Released Bug description: On 2020-03-03 I installed a Focal system from the latest ISO image and chose the Italian localization at install time. The localization setting worked as expected, but not for Firefox: its interface is still in English. No "Italian" option shows up in the 'Preferences -> Language' menu (the menu is empty). The firefox-locale-it package is correctly installed. I tried installing firefox-locale-fr and restart Firefox, but I still got no French option in the Language menu. On the other hand letting Firefox download the language pack itself *does* work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1866059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
This bug was fixed in the package enigmail - 2:2.2.4-0ubuntu0.18.04.1 --- enigmail (2:2.2.4-0ubuntu0.18.04.1) bionic; urgency=medium * new upstream release for Thunderbird 78 (LP: #1895643) * drop a number of obsolete patches * remove obsolete autopkgtests * depend on thunderbird >= 78.0 -- Olivier Tilloy Fri, 12 Mar 2021 16:27:25 +0100 ** Changed in: jsunit (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in enigmail package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in enigmail source package in Bionic: Fix Released Status in jsunit source package in Bionic: Fix Released Status in thunderbird source package in Bionic: Fix Released Status in enigmail source package in Focal: Fix Released Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878292] Re: firefox FTBFS on s390x
This bug was fixed in the package thunderbird - 1:78.8.1+build1-0ubuntu0.18.04.1 --- thunderbird (1:78.8.1+build1-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream stable release (78.8.1build1) (LP: #1895643) - debian/config/branch.mk * Bump build dependency on rustc >= 1.41.0 and cargo >= 0.42 - debian/control{,.in} * Bump build dependency on nodejs-mozilla >= 10.21 - debian/control{,.in} * Bump build dependency on nasm-mozilla >= 2.14.02 - debian/control{,.in} * Bump build dependency on debhelper >= 9 - debian/compat - debian/control{,.in} * Port packaging to python3 - debian/build/Expression.py - debian/build/Preprocessor.py - debian/build/create-tarball.py - debian/build/fix-mozinfo-appname.py - debian/build/keepalive-wrapper.py - debian/build/rules.mk - debian/build/xpi-id.py - debian/control{,.in} * Clean up unused code paths in packaging rules - debian/rules - debian/build/config.mk - debian/config/mozconfig.in * Update cbindgen to 0.17.0 - debian/build/create-tarball.py * Work around clang hanging forever when trying to optimize the build of the embedded copy of sqlite3 (LP: #1878292) - debian/patches/s390x-workaround-sqlite3-clang-optimization-hang.patch * Remove obsolete config options - debian/config/mozconfig.in * Allow sideloading langpacks (LP: #1866059) - debian/config/mozconfig.in * Make xul-ext-lightning a transitional empty package, now that calendar functionality is part of the Thunderbird core - debian/build/rules.mk - debian/control{,.in} - debian/rules * Separately installed blocklist.xml was removed - debian/thunderbird.install.in * Install WeTransfer extension to the features directory - debian/thunderbird.install.in * Add the following locales: af, en-CA, fa, ja-JP-mac, pa-IN, th - update debian/config/locales.{all,shipped} * Remove upstreamed patch - debian/patches/nss_disable_fips_enabled_flag.patch * Update and rename patch to selectively reduce debug info level - debian/patches/reduce-rust-debuginfo-on-selected-architectures.patch * Refresh patches - debian/patches/rust-drop-dll-checksums.patch - debian/patches/support-coinstallable-trunk-build.patch * Updates patches - debian/patches/unity-menubar.patch * Cherry-pick 3 upstream commits to fix building ICU on big-endian architectures (e.g. s390x) - debian/patches/upstream-icu-fixes.patch * Add a missing linker flag to build icupkg on s390x - debian/patches/s390x-fix-icupkg-build.patch * Drop armel arch references - debian/control{,.in} - debian/build/rules.mk * Add generic logic to target different LLVM toolchains - debian/config/mozconfig.in - debian/control{,.in} - debian/build/rules.mk * Make thunderbird suggest libotr5 - debian/control{,.in} * Add versioned breaks on enigmail and jsunit - debian/control{,.in} * Allow the use of external GPG keyrings by default - debian/vendor.js -- Olivier Tilloy Wed, 17 Mar 2021 15:37:52 +0100 ** Changed in: thunderbird (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1878292 Title: firefox FTBFS on s390x Status in firefox package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Fix Released Bug description: Builds hang when trying to compile the third-party sqlite3 copy, during 7+ hours, before being killed. See e.g. https://launchpad.net/ubuntu/+source/firefox/76.0.1+build1-0ubuntu1/+build/19276095: 436:55.58 make[6]: *** [/<>/firefox-76.0.1+build1/config/rules.mk:673: sqlite3.o] Killed 436:55.59 make[6]: Leaving directory '/<>/firefox-76.0.1+build1/obj-s390x-linux-gnu/third_party/sqlite3/src' 436:55.59 make[5]: *** [/<>/firefox-76.0.1+build1/config/recurse.mk:74: third_party/sqlite3/src/target-objects] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1878292/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
This bug was fixed in the package jsunit - 0.2.2-1~ubuntu0.18.04.2 --- jsunit (0.2.2-1~ubuntu0.18.04.2) bionic; urgency=medium * jsunit is unmaintained and hasn't been ported to thunderdird series 78 (https://www.mail-archive.com/enigmail-users@enigmail.net/msg05251.html), so it is being removed from the bionic archive to allow thunderbird to be updated (LP: #1895643) -- Olivier Tilloy Fri, 12 Mar 2021 15:30:55 +0100 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in enigmail package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in enigmail source package in Bionic: Fix Released Status in jsunit source package in Bionic: Fix Released Status in thunderbird source package in Bionic: Fix Released Status in enigmail source package in Focal: Fix Released Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
This bug was fixed in the package thunderbird - 1:78.8.1+build1-0ubuntu0.18.04.1 --- thunderbird (1:78.8.1+build1-0ubuntu0.18.04.1) bionic; urgency=medium * New upstream stable release (78.8.1build1) (LP: #1895643) - debian/config/branch.mk * Bump build dependency on rustc >= 1.41.0 and cargo >= 0.42 - debian/control{,.in} * Bump build dependency on nodejs-mozilla >= 10.21 - debian/control{,.in} * Bump build dependency on nasm-mozilla >= 2.14.02 - debian/control{,.in} * Bump build dependency on debhelper >= 9 - debian/compat - debian/control{,.in} * Port packaging to python3 - debian/build/Expression.py - debian/build/Preprocessor.py - debian/build/create-tarball.py - debian/build/fix-mozinfo-appname.py - debian/build/keepalive-wrapper.py - debian/build/rules.mk - debian/build/xpi-id.py - debian/control{,.in} * Clean up unused code paths in packaging rules - debian/rules - debian/build/config.mk - debian/config/mozconfig.in * Update cbindgen to 0.17.0 - debian/build/create-tarball.py * Work around clang hanging forever when trying to optimize the build of the embedded copy of sqlite3 (LP: #1878292) - debian/patches/s390x-workaround-sqlite3-clang-optimization-hang.patch * Remove obsolete config options - debian/config/mozconfig.in * Allow sideloading langpacks (LP: #1866059) - debian/config/mozconfig.in * Make xul-ext-lightning a transitional empty package, now that calendar functionality is part of the Thunderbird core - debian/build/rules.mk - debian/control{,.in} - debian/rules * Separately installed blocklist.xml was removed - debian/thunderbird.install.in * Install WeTransfer extension to the features directory - debian/thunderbird.install.in * Add the following locales: af, en-CA, fa, ja-JP-mac, pa-IN, th - update debian/config/locales.{all,shipped} * Remove upstreamed patch - debian/patches/nss_disable_fips_enabled_flag.patch * Update and rename patch to selectively reduce debug info level - debian/patches/reduce-rust-debuginfo-on-selected-architectures.patch * Refresh patches - debian/patches/rust-drop-dll-checksums.patch - debian/patches/support-coinstallable-trunk-build.patch * Updates patches - debian/patches/unity-menubar.patch * Cherry-pick 3 upstream commits to fix building ICU on big-endian architectures (e.g. s390x) - debian/patches/upstream-icu-fixes.patch * Add a missing linker flag to build icupkg on s390x - debian/patches/s390x-fix-icupkg-build.patch * Drop armel arch references - debian/control{,.in} - debian/build/rules.mk * Add generic logic to target different LLVM toolchains - debian/config/mozconfig.in - debian/control{,.in} - debian/build/rules.mk * Make thunderbird suggest libotr5 - debian/control{,.in} * Add versioned breaks on enigmail and jsunit - debian/control{,.in} * Allow the use of external GPG keyrings by default - debian/vendor.js -- Olivier Tilloy Wed, 17 Mar 2021 15:37:52 +0100 ** Changed in: thunderbird (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: enigmail (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in enigmail package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in enigmail source package in Bionic: Fix Released Status in jsunit source package in Bionic: Fix Released Status in thunderbird source package in Bionic: Fix Released Status in enigmail source package in Focal: Fix Released Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930460] [NEW] i have blank screen after some time on sleep mode, or just restart while in sleep mode
Public bug reported: I have HP Probook 470 G5, first I installed Ubuntu 18.04 and then upgraded to 20.04, in both cases the same problem arrived. I have disabled sleep mode, but also, if I intensionally put laptop in sleep mode the same thing happened. Sometimes when I try to wake him up, its just black screen and I cant do anything, I have to do hard restart (on button) Or when I try to wake him from sleep, i can do that, but i see that laptop has been restarted. Please exuce my bad English, I hope you understand me. I am beginner with Linux , and I dont have any idea how to solve this problem on my own Thank you very much on your help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 21:25:03 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-09-03 (271 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-15 (229 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1930460 Title: i have blank screen after some time on sleep mode, or just restart while in sleep mode Status in gnome-shell package in Ubuntu: New Bug description: I have HP Probook 470 G5, first I installed Ubuntu 18.04 and then upgraded to 20.04, in both cases the same problem arrived. I have disabled sleep mode, but also, if I intensionally put laptop in sleep mode the same thing happened. Sometimes when I try to wake him up, its just black screen and I cant do anything, I have to do hard restart (on button) Or when I try to wake him from sleep, i can do that, but i see that laptop has been restarted. Please exuce my bad English, I hope you understand me. I am beginner with Linux , and I dont have any idea how to solve this problem on my own Thank you very much on your help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 21:25:03 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-09-03 (271 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-15 (229 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1388491]
I've submitted a patch: https://gerrit.libreoffice.org/c/core/+/116501 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1388491 Title: [upstream] calc: "Cut" and "Paste special" -> "Transpose" affects other cells Status in LibreOffice: In Progress Status in libreoffice package in Ubuntu: Fix Committed Bug description: Step to reproduce: 1. Open the attached ods file. 2. Select I12 to L16 and cut this region (Ctrl+X). (This bug doesn't occur with copy) 3. Select I5 and open Paste Special dialog (Shift+Ctrl+V). 4. Enable "Transpose" option and Click "OK" Then, values of some cells in C9 to E10, which are not related to blank cells are changed: C9: =C3/SUM(C$3:C$6) -> K7/SUM(C$3:C$6) D9: =D3/SUM(D$3:D$6) -> L7/SUM(D$3:D6) E9: =E3/SUM(E$3:E$6) -> M7/SUM(E$3:E$6) C10: =C4/SUM(C$3:C$6) -> K8/SUM(C$3:C$6) D10: =D4/SUM(D$3:D$6) -> L8/SUM(D$3:D6) E10: =E4/SUM(E$3:E$6) -> M8/SUM(E$3:E$6) My environment is Ubuntu 14.04 LibreOffice 4.2.6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1388491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926843] Update Released
The verification of the Stable Release Update for gnome-online-accounts has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Focal: Fix Committed Status in gnome-online-accounts source package in Hirsute: Fix Released Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926843] Re: online accounts integration with fb isn't working
This bug was fixed in the package gnome-online-accounts - 3.38.1-1ubuntu1.1 --- gnome-online-accounts (3.38.1-1ubuntu1.1) hirsute; urgency=medium * debian/rules: - disable the facebook provider since it's current not working (lp: #1926843) -- Sebastien Bacher Fri, 07 May 2021 17:16:05 +0200 ** Changed in: gnome-online-accounts (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Focal: Fix Committed Status in gnome-online-accounts source package in Hirsute: Fix Released Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer
Oh, didn't see that. Sorry! But yes I had this issue sometimes in the past but now was the time to report it finally. :) It's a bit annoying to get this freeze sometimes. But I don't know in what connection with what App it was. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1930192 Title: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter- offscreen-effect.c:213: Unable to create an Offscreen buffer Status in mutter package in Ubuntu: New Bug description: Addition for bug report 1930128 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Sat May 29 12:20:21 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1608008084 GsettingsChanges: b'org.gnome.desktop.background' b'show-desktop-icons' b'true' b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true' b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false' b'org.gnome.desktop.session' b'idle-delay' b'uint32 0' InstallationDate: Installed on 2019-11-10 (566 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /var/lib/gdm3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1258367] Re: Atom feed is not readable in Rhythmbox
** Changed in: rhythmbox Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1258367 Title: Atom feed is not readable in Rhythmbox Status in Rhythmbox: Fix Released Status in rhythmbox package in Ubuntu: Triaged Bug description: The following feed either crashes or doesn't work in Rhythmbox: http://gdata.youtube.com/feeds/api/users/TimesSquareChurch/uploads As you can see, it's valid: http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fgdata.youtube.com%2Ffeeds%2Fapi%2Fusers%2FTimesSquareChurch%2Fuploads ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 5 18:21:09 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-23 (12 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1258367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930447] [NEW] Unable to turn on bluetooth
Public bug reported: Testing Ubuntu Impish daily ISO 01-06-2021 0n QA tracking site - After successful install go to settings "Bluetooth" and select the on tab in upper right hand corner and nothing happens. This maybe related to bug # 1928924 https://bugs.launchpad.net/ubuntu/+source/bluedevil/+bug/1928924 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.58-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 16:30:07 2021 InstallationDate: Installed on 2021-06-01 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210601) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 82C4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=efd131f1-9709-400b-9f5d-d72be1df3885 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 28:39:26:D5:7D:8E ACL MTU: 1021:6 SCO MTU: 255:12 DOWN RX bytes:1682 acl:0 sco:0 events:183 errors:0 TX bytes:36490 acl:0 sco:0 commands:183 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1930447 Title: Unable to turn on bluetooth Status in bluez package in Ubuntu: New Bug description: Testing Ubuntu Impish daily ISO 01-06-2021 0n QA tracking site - After successful install go to settings "Bluetooth" and select the on tab in upper right hand corner and nothing happens. This maybe related to bug # 1928924 https://bugs.launchpad.net/ubuntu/+source/bluedevil/+bug/1928924 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.58-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 16:30:07 2021 InstallationDate: Installed on 2021-06-01 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210601) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 82C4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=efd131f1-9709-400b-9f5d-d72be1df3885 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 28:39:26:D5:7D:8E ACL MTU: 1021:6 SCO MTU: 255:12 DOWN RX bytes:1682 acl:0 sco:0 events:183 errors:0 TX bytes:36490 acl:0 sco:0 commands:183 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1930447/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
ack. Is yours the "ubuntu" session? i.e. auto-detection, the default, not "ubuntu-xorg" which is manually selecting "Ubuntu on Xorg" from gdm. Check $DESKTOP_SESSION. I can confirm that if I pick ubuntu-xorg then nvidia-smi looks like yours. I see from `lsmod` that nvidia is loaded - apparently that's not enough to get it to be used though. I would have expected the udev rule (61-gdm.rules) to have fired here and caused gdm-disable-wayland to run, so that I got Xorg and things running on the nvidia GPU; is that a valid expectation? On Tue, Jun 01, 2021 at 02:22:34PM -, Alberto Milone wrote: > I don't get that at all (see the attached screenshot). > > Detection seems to work well here: > > giu 01 16:05:52 dell-g7 systemd[1725]: Starting GNOME Shell on Wayland... > giu 01 16:05:52 dell-g7 systemd[1725]: Starting GNOME Shell on X11... > giu 01 16:05:52 dell-g7 systemd[1725]: > app-gnome-gnome\x2dkeyring\x2dpkcs11-2001.scope: Succeeded. > giu 01 16:05:52 dell-g7 systemd[1725]: org.gnome.Shell@wayland.service: > Control process exited, code=exited, status=2/INVALIDARGUMENT > giu 01 16:05:52 dell-g7 systemd[1725]: org.gnome.Shell@wayland.service: > Skipped due to 'exec-condition'. > giu 01 16:05:52 dell-g7 systemd[1725]: Condition check resulted in GNOME > Shell on Wayland being skipped. > > ** Attachment added: "Screenshot from 2021-06-01 16-08-04.png" > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5501675/+files/Screenshot%20from%202021-06-01%2016-08-04.png > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1925238 > > Title: > [nvidia-prime] switches between xorg and wayland session > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 643440] Re: show addon homepage fails with "Secure Connection Failed"
** Changed in: thunderbird Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/643440 Title: show addon homepage fails with "Secure Connection Failed" Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Invalid Bug description: Binary package hint: thunderbird When an add-on's homepage uses an invalid certificate the connection fails with "Secure Connection Failed". There is no option to accept the certificate, so no way to visit the homepage. Steps to reproduce: 1. Install removedupes.mozdev.org 2. Click Tools->Add-ons->Remove Duplicates->Visit homepage Expected: a. A dialog to accept the security certificate b. A dialog to attempt an insecure connection c. Delegate all this to the web-browser ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.8+build2+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-25.43-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 NonfreeKernelModules: nvidia wl Architecture: i386 Date: Mon Sep 20 13:21:23 2010 InstallationMedia: Kubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/643440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 643440]
We open the add-on homepage in the default system browser now, not within Thunderbird. So this bug is no longer valid. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/643440 Title: show addon homepage fails with "Secure Connection Failed" Status in Mozilla Thunderbird: Invalid Status in thunderbird package in Ubuntu: Invalid Bug description: Binary package hint: thunderbird When an add-on's homepage uses an invalid certificate the connection fails with "Secure Connection Failed". There is no option to accept the certificate, so no way to visit the homepage. Steps to reproduce: 1. Install removedupes.mozdev.org 2. Click Tools->Add-ons->Remove Duplicates->Visit homepage Expected: a. A dialog to accept the security certificate b. A dialog to attempt an insecure connection c. Delegate all this to the web-browser ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: thunderbird 3.0.8+build2+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-25.43-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 NonfreeKernelModules: nvidia wl Architecture: i386 Date: Mon Sep 20 13:21:23 2010 InstallationMedia: Kubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/643440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930199] Re: Thunderbird attachments, if they are from LibreOffice 7.1, are not opened directly
** Package changed: ubuntu => thunderbird (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1930199 Title: Thunderbird attachments, if they are from LibreOffice 7.1, are not opened directly Status in thunderbird package in Ubuntu: New Bug description: Environment: - Ubuntu 20.04 LTS - Thunderbird 7.8.1 (64Bit) - LibreOffice 7.1.3.2. Trying to open any applications LibreOffice 7.1 directly from Thnderbird mail attachments, happens that LibreOffice starts immediately and goes into error with the following box error: /temp/mozilla_user0/filename.doc does not exist In this example I used the .doc extension but this happens only with all extensions of LibreOffice 7.1. As a result, I am uncomfortably forced to download attachments first and then open them with LibreOffice 7.1 Thanks in advance for any help To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1930199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930199] [NEW] Thunderbird attachments, if they are from LibreOffice 7.1, are not opened directly
You have been subscribed to a public bug: Environment: - Ubuntu 20.04 LTS - Thunderbird 7.8.1 (64Bit) - LibreOffice 7.1.3.2. Trying to open any applications LibreOffice 7.1 directly from Thnderbird mail attachments, happens that LibreOffice starts immediately and goes into error with the following box error: /temp/mozilla_user0/filename.doc does not exist In this example I used the .doc extension but this happens only with all extensions of LibreOffice 7.1. As a result, I am uncomfortably forced to download attachments first and then open them with LibreOffice 7.1 Thanks in advance for any help ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Thunderbird attachments, if they are from LibreOffice 7.1, are not opened directly https://bugs.launchpad.net/bugs/1930199 You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
I don't get that at all (see the attached screenshot). Detection seems to work well here: giu 01 16:05:52 dell-g7 systemd[1725]: Starting GNOME Shell on Wayland... giu 01 16:05:52 dell-g7 systemd[1725]: Starting GNOME Shell on X11... giu 01 16:05:52 dell-g7 systemd[1725]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2001.scope: Succeeded. giu 01 16:05:52 dell-g7 systemd[1725]: org.gnome.Shell@wayland.service: Control process exited, code=exited, status=2/INVALIDARGUMENT giu 01 16:05:52 dell-g7 systemd[1725]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'. giu 01 16:05:52 dell-g7 systemd[1725]: Condition check resulted in GNOME Shell on Wayland being skipped. ** Attachment added: "Screenshot from 2021-06-01 16-08-04.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5501675/+files/Screenshot%20from%202021-06-01%2016-08-04.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874578] Re: Dock has very long load time when show-mounts is enabled
Worth to say that in my case, even 'gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false' doesn't fix it. Also clicking on dotted button "Show aplications" doesn't do anything until I click on Activities in top bar once. Ubuntu 20.04 LTS (no custom extensions, kernel 5.11) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1874578 Title: Dock has very long load time when show-mounts is enabled Status in Dash to dock: New Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I just upgraded from Ubuntu 18.04 to 20.04. When I boot my system I have to wait at least 10 to 15 seconds for the application icons to load on dock. Meanwhile everything else seems to be working properly. I didn't experience this behavior in Ubuntu 18.04. Also the dock doesn't trigger when I move my cursor to the left of the screen. (I have set the docker to Auto-Hide mode and it's position is on the left of my screen). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2016-08-03 (1359 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Tags: focal third-party-packages wayland-session Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-23 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1874578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 269441] Re: Trash always full
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: caja (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/269441 Title: Trash always full Status in Ubuntu MATE: Confirmed Status in caja package in Ubuntu: Confirmed Status in glib2.0 package in Ubuntu: Confirmed Bug description: I've seen other users having problems with that the trash appears empty even though it isn't. I have the opposite problem: my trash icon on the desktop always appears full, even if empty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/269441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
No, they should be on "ubuntu" and that is Wayland if wayland works and Xorg if it doesn't. The problem is that changing the setting doesn't appear to have any effect at least from what I can see. For example look at the screenshot attached here. Do you see this kind of thing on a hybrid machine with hirsute or is it all OK for you? ** Attachment added: "Screenshot from 2021-06-01 13-01-36.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5501666/+files/Screenshot%20from%202021-06-01%2013-01-36.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
If you use intel mode, then GDM will default to Wayland, since no NVIDIA driver is detected. Would you rather have users rely on X11 even in intel mode? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930409] [NEW] Pulseaudio org.freedesktop.dbus error on boot after clean 21.04 install
Public bug reported: Not sure if the bluez error is related, perhaps not (this is a desktop without Wifi/Bluetooth). jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired,> Intel i3-9100, C246 chipset, 32GB ram. Ubuntu Budgie 21.04 installed via usb boot disk. It gives me a popup "error occured" every time I reboot.. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asterix1749 F pulseaudio CasperMD5CheckResult: pass Date: Tue Jun 1 12:48:36 2021 InstallationDate: Installed on 2021-05-11 (21 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.release: 1.6 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x dmi.board.name: D3644-B1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3644-B1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr: dmi.product.family: OEM-FTS dmi.sys.vendor: FUJITSU ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930409 Title: Pulseaudio org.freedesktop.dbus error on boot after clean 21.04 install Status in pulseaudio package in Ubuntu: New Bug description: Not sure if the bluez error is related, perhaps not (this is a desktop without Wifi/Bluetooth). jun 01 12:46:30 Obelix dbus-daemon[1070]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) jun 01 12:46:30 Obelix pulseaudio[1749]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired,> Intel i3-9100, C246 chipset, 32GB ram. Ubuntu Budgie 21.04 installed via usb boot disk. It gives me a popup "error occured" every time I reboot.. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: pulseaudio 1:14.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asterix1749 F pulseaudio CasperMD5CheckResult: pass Date: Tue Jun 1 12:48:36 2021 InstallationDate: Installed on 2021-05-11 (21 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.release: 1.6 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.13 R1.6.0 for D3644-B1x dmi.board.name: D3644-B1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3644-B1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.13R1.6.0forD3644-B1x:bd05/15/2019:br1.6:svnFUJITSU:pn:pvr:rvnFUJITSU:rnD3644-B1:rvrS26361-D3644-B1:cvnFUJITSU:ct3:cvr: dmi.product.family: OEM-FTS dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1930409/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930371] Re: top bar displayed on top of a fullscreen window that gets moved from one monitor to another
Filed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4351 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4351 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4351 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another Status in gnome-shell package in Ubuntu: New Bug description: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930387] [NEW] The system voice doesn't change after disable "Over-Amplification"
Public bug reported: [Summary] The system voice doesn't change after disable "Over-Amplification" [Reproduce] 1. Boot into the system. 2. Launch Settings > Sound 3. Enable "Over-Amplification" 4. Maximize the system Volume 5. Disable "Over-Amplification" [Expected result] The system voice can become lower. [Actual result] The system volume showed as 100 but the voice doesn't become lower. [Fail Rate] 100% [Additional information] Ubuntu Version: 20.04.2 LTS Image: sutton-newell-focal-amd64-20210414-220 gnome-control-center: 1:3.36.5-0ubuntu1 ** Affects: oem-priority Importance: Medium Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1930206 sutton ** Tags added: oem-priority originate-from-1930206 sutton ** Changed in: oem-priority Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1930387 Title: The system voice doesn't change after disable "Over-Amplification" Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: [Summary] The system voice doesn't change after disable "Over-Amplification" [Reproduce] 1. Boot into the system. 2. Launch Settings > Sound 3. Enable "Over-Amplification" 4. Maximize the system Volume 5. Disable "Over-Amplification" [Expected result] The system voice can become lower. [Actual result] The system volume showed as 100 but the voice doesn't become lower. [Fail Rate] 100% [Additional information] Ubuntu Version: 20.04.2 LTS Image: sutton-newell-focal-amd64-20210414-220 gnome-control-center: 1:3.36.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930371] Re: top bar displayed on top of a fullscreen window that gets moved from one monitor to another
Thanks for the bug report. First, please try removing these extensions: 'fullscreen-hot-cor...@sorrow.about.alice.pm.me', 'transparentosd@ipaq3870' then log in again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another Status in gnome-shell package in Ubuntu: New Bug description: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930371] [NEW] top bar displayed on top of a fullscreen window that gets moved from one monitor to another
Public bug reported: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another Status in gnome-shell package in Ubuntu: New Bug description: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930312] Re: USB disks and SD cards mount for wrong user
** Also affects: caja (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1930312 Title: USB disks and SD cards mount for wrong user Status in Ubuntu MATE: New Status in caja package in Ubuntu: New Status in gvfs package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: I have MATE 20.04 LTS installed on a laptop with 4 users. Plugging in SD cards and USB sticks works perfectly, unless there is someone else logged in on the machine. eg: 1- user A logs in, then walks away and screen locks 2- user B switches to the login screen and logs in as user B 3- user B plugs in a USB stick, but it doesn't mount for user B 4- (hidden from sight) user A gets an "authentication is required to mount... /dev/sdb1" error and the window is asking for admin password - details of this are: polkit.subject-pid: 102318 polkit.caller-pid: 806 Action: org.freedesktop.udisks2.filesystem-mount-other-seat Vendor: The Udisks Project user B has no indication on why it didn't mount. If they click on the USB stick in the Caja side bar, they get an "Unable to mount USB Disk - an operation is already pending" So it seems that automount is trying to show the USB stick to the inactive user A, totally blocking user B. (user B doesn't even get the chance to enter an admin password to override) the only solution is basically to "switch account", log in as user A and log them out. (this clearly doesn't work if user B doesn't know their password!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1930312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp