[Desktop-packages] [Bug 1170217] Re: Path entry of desktop file not work when autostart
** Changed in: gnome-session (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1170217 Title: Path entry of desktop file not work when autostart Status in gnome-session package in Ubuntu: Incomplete Bug description: #precise #Ubuntu12.04.2 LTS This is about .desktop file in ~/.config/autostart In "[Desktop Entry]" section, "Path" is shouled to the workdir. Double click the .desktop file, it can run ok. But when it autostart after login, the workdir is not set to the "Path" value, still be ~ . The same .desktop file can work well in mint14. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1170217/+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 70585] Re: doesn't recognise "~/" shortcut for /home/user/
** Changed in: gnome-session (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/70585 Title: doesn't recognise "~/" shortcut for /home/user/ Status in gnome-control-center: Invalid Status in gnome-session: Expired Status in gnome-session package in Ubuntu: Opinion Bug description: I installed the MoinMoin wiki (Desktop Edition) for my personal use. It is written in python, and in the terminal, the command to run it is: python ~/moin-desktop/moin.py However, when entered into the "Additional startup programs", this doesn't work. It does work when rewritten as: python /home/user/moin-desktop/moin.py To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/70585/+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 1969305] Re: Export XDG_CONFIG_HOME and XDG_DATA_HOME as well
It's one of the shell scripts in https://git.launchpad.net/ubuntu/+source/xorg/tree/debian/local/Xsession.d, which is then installed to /etc/X11/Xsession.d The most appropriate would be 60x11-common_xdg_path, where CONFIG and DATA dirs are exported from. I'm on Xubuntu 20.04 but I checked the devel branch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1969305 Title: Export XDG_CONFIG_HOME and XDG_DATA_HOME as well Status in xorg package in Ubuntu: Incomplete Bug description: These base directories should also be included to make scripting easier. Their default values should be set as per XDG base-dir spec, i.e.: XDG_CONFIG_HOME="$HOME/.config" XDG_DATA_HOME="$HOME/.local/share" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969305/+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 1969305] [NEW] Export XDG_CONFIG_HOME and XDG_DATA_HOME as well
Public bug reported: These base directories should also be included to make scripting easier. Their default values should be set as per XDG base-dir spec, i.e.: XDG_CONFIG_HOME="$HOME/.config" XDG_DATA_HOME="$HOME/.local/share" ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1969305 Title: Export XDG_CONFIG_HOME and XDG_DATA_HOME as well Status in xorg package in Ubuntu: New Bug description: These base directories should also be included to make scripting easier. Their default values should be set as per XDG base-dir spec, i.e.: XDG_CONFIG_HOME="$HOME/.config" XDG_DATA_HOME="$HOME/.local/share" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969305/+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 1958856] [NEW] gnome-software continues running in the background even after its window is closed
Public bug reported: 1) Ubuntu 20.04.3 LTS 2) gnome-software 3.36.1-0ubuntu0.20.04.0 3) Closing the window should kill the process altogether 4) The process remains in the background instead [ STEPS TO REPRODUCE ] This becomes obvious when launched from the shell: ~ gnome-software & [1] 7972 ~ 11:25:23:0836 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, modalias, odrs, packagekit-refine, rewrite-resource, snap, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata 11:25:23:0836 Gs disabled plugins: dpkg, dummy, repos 11:25:26:0660 Gs Only 0 apps for recent list, hiding 11:25:31:0006 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.bare-EISPgh06mRh1vordZY9OZ34QHdd7OrdR/latest/stable from runtime to unknown! 11:25:31:0817 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.core20-DLqre5XGLbDqg9jPtiAhRRjDuPVa5X1q/latest/stable from runtime to unknown! 11:25:32:0448 Gs automatically prevented from changing kind on system/snap/*/desktop/io.snapcraft.snapd-PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4/latest/stable from desktop to unknown! 11:25:32:0721 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.core18-CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6/latest/stable from runtime to unknown! here, the window is closed but the process is still running as shown below ~ jobs [1]+ Running gnome-software & Launching Software, window appears ~ wmctrl -lpG | grep 'Software$' 0x0267 0 7972 29 -8 1274 916 hp Software Closing Software, window disappears, yet the process is still running as shown above ~ wmctrl -lpG | grep 'Software$' ~ [ WORKAROUND ] The workaround here is to kill the process manually, e.g. `pkill gnome-software`. [ SUGGESTION ] Is it designed so to prevent interruptions (accidental or not) during updates? If it is, perhaps a more elegant way would be to display a confirmation dialog/prompt/popup in the case of an ongoing update process, gracefully quit the program otherwise (the process is killed for good). END OF REPORT ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.1-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jan 24 16:19:33 2022 InstallationDate: Installed on 2021-05-17 (252 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.1-0ubuntu0.20.04.0 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.cron.daily.apport: [modified] mtime.conffile..etc.cron.daily.apport: 2022-01-10T23:09:37.086519 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: 1) Ubuntu 20.04.3 LTS 2) gnome-software 3.36.1-0ubuntu0.20.04.0 3) Closing the window should kill the process altogether 4) The process remains in the background instead + + [ STEPS TO REPRODUCE ] This becomes obvious when launched from the shell: ~ gnome-software & [1] 7972 ~ 11:25:23:0836 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, appstream, desktop-menu-path, hardcoded-blacklist, modalias, odrs, packagekit-refine, rewrite-resource, snap, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata 11:25:23:0836 Gs disabled plugins: dpkg, dummy, repos 11:25:26:0660 Gs Only 0 apps for recent list, hiding 11:25:31:0006 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.bare-EISPgh06mRh1vordZY9OZ34QHdd7OrdR/latest/stable from runtime to unknown! 11:25:31:0817 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.core20-DLqre5XGLbDqg9jPtiAhRRjDuPVa5X1q/latest/stable from runtime to unknown! 11:25:32:0448 Gs automatically prevented from changing kind on system/snap/*/desktop/io.snapcraft.snapd-PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4/latest/stable from desktop to unknown! 11:25:32:0721 Gs automatically prevented from changing kind on system/snap/*/runtime/io.snapcraft.core18-CSO04Jhav2yK0uz97cr0ipQRyqg0qQL6/latest/stable from runtime to unknown! here, the
[Desktop-packages] [Bug 1954429] Re: The required package for GNOME Classic not mentioned in docs
My apologies, Gunnar. I stand corrected. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1954429 Title: The required package for GNOME Classic not mentioned in docs Status in Gnome Documentation: Unknown Status in gnome-user-docs package in Ubuntu: Confirmed Bug description: On this page https://help.ubuntu.com/stable/ubuntu-help/gnome- classic.html.en is described how to switch between user interfaces, but instead of "Switch to and from GNOME Classic" I can choose to switch between Ubuntu and Ubuntu Xorg, that actually doesn't make any changes at my system's interface. I'm using Ubuntu 21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-user-docs/+bug/1954429/+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 1952083] Re: Add support for Beige Goby
@tjaalton, I always use the main official server (archive.ubuntu.com). Anyway, there were no errors today and the update went smoothly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952083 Title: Add support for Beige Goby Status in amd: New Status in OEM Priority Project: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Released Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+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 1952083] Re: Add support for Beige Goby
This version wants to break dependencies and introduces a conflict between packages. Xubuntu 20.04.3 LTS ** Attachment added: "Screenshot_2021-12-02_13-21-29.png" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1952083/+attachment/5544859/+files/Screenshot_2021-12-02_13-21-29.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952083 Title: Add support for Beige Goby Status in amd: New Status in OEM Priority Project: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Released Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+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 1934185] Re: Ubuntu Dock popup menu in top left corner of the screen and won't go away
Here is a short screencast: https://launchpadlibrarian.net/566466758/Screencast%20from%2010-31-2021%2001%3A55%3A32%20PM.webm -- 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/1934185 Title: Ubuntu Dock popup menu in top left corner of the screen and won't go away Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Every so often, typically when I'm using Thunderbird, I attempt to use the dock context menu to create a new window or something like that, and the "New Window" popup comes up, but does not work. Attempts to click on it have no effect. I cannot make the popup go away, other than by logging out and logging back in again (or rebooting). I did not observe this problem until I installed Ubuntu 21.04, so I expect it's a glitch that is new to this release. See attached screenshot for an example of the popup that won't go away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 30 10:57:22 2021 InstallationDate: Installed on 2018-08-03 (1062 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-06-03 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1934185/+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 1950075] Re: nautilus crashes when 1 window is open and open new window directly to folder
syslog, dmesg and strace for bug #1950075 ** Attachment added: "1950075.tar.xz" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1950075/+attachment/5538650/+files/1950075.tar.xz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1950075 Title: nautilus crashes when 1 window is open and open new window directly to folder Status in nautilus package in Ubuntu: Confirmed Bug description: Description: Ubuntu 21.10 Release: 21.10 GNOME nautilus 40.2 When I have 1 window or more opened from nautilus and right click on bar icon and then click a folder like Downloads ord Desktop all windows are suddenly closed. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 10:17:06 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 548)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2021-11-06 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1950075/+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 1950075] Re: nautilus crashes when 1 window is open and open new window directly to folder
From bug #1950083 1) Ubuntu Jammy Jellyfish (development branch) 20211107 daily-live 2) nautilus (1:40.2-1ubuntu1) 3) A new window should open 4) Files crashes altogether ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 16:16:50 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2021-11-07 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211107) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f846593510f: mov 0x8(%rbp),%rax PC (0x7f846593510f) ok source "0x8(%rbp)" (0x5570009c) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_display_error_trap_push () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_screen_supports_net_wm_hint () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf separator: usr_lib_nautilus: evince 41.2-1 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share 0.7.3-2ubuntu4 ** Attachment added: "Screencast from 11-07-2021 04:24:47 PM.webm" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1950075/+attachment/5538649/+files/Screencast%20from%2011-07-2021%2004%3A24%3A47%20PM.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1950075 Title: nautilus crashes when 1 window is open and open new window directly to folder Status in nautilus package in Ubuntu: Confirmed Bug description: Description: Ubuntu 21.10 Release: 21.10 GNOME nautilus 40.2 When I have 1 window or more opened from nautilus and right click on bar icon and then click a folder like Downloads ord Desktop all windows are suddenly closed. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 10:17:06 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 548)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2021-11-06 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1950075/+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 1949845] Re: Toggle enable/disable dock autohide gives glitches
There are two glitches here: 1. Selecting the Appearance tab for the first time causes the Dock to disappear briefly. 2. Toggling the "Auto-hide the Dock" setting causes the Dock (plus the Settings icon) and the Application menu to flash and re-render. Screencasts are attached below. Pay attention to the Dock (plus the Settings icon) and the Application menu. ** Attachment added: "bug_1949845.tar" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1949845/+attachment/5538338/+files/bug_1949845.tar -- 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/1949845 Title: Toggle enable/disable dock autohide gives glitches Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 development branch @ 4/11/2021 with kernel 5.13.0-19-generic (wayland) When opening gnome-control-center and toggle enable/disable the dock to autohide a few times, the gnome-control-center window gives glitches/flashes this is not on random, it can be reproduced ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 16:47:34 2021 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1949845/+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 1845362] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
I know that it was set to rls-ii-notfixing but I just want to tell that it appears in Jammy as well (build 20211104). I'm including this bug in my test result with the "Passed" flag. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1845362 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() Status in gnome-font-viewer package in Ubuntu: Confirmed Status in gnome-font-viewer package in Debian: New Bug description: Reproducible crash (tested on Ubuntu and Xubuntu) or freezing of application during ISO testing of a live-session. Application will crash if there is an attempt to close it or scroll through fonts. On one occasion my laptop was rendered unusable when Firefox was launched while trying to report the crash to Launchpad. After the bug report has been sent gnome-font-viewer will freeze when automatically restarted. No fonts are displayed. Work around --- gnome-font-viewer appears to start correctly when started from the command line of my Ubuntu 20.04 installation. Then subsequent attempts to start the program succeed when started from the dock or the Application Overview. I have found that this work around wasn't necessary when using Xubuntu 20.04. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-font-viewer 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.416 CurrentDesktop: XFCE Date: Wed Sep 25 17:34:17 2019 ExecutablePath: /usr/bin/gnome-font-viewer LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) ProcCmdline: gnome-font-viewer ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-font-viewer StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6 XPending () from /lib/x86_64-linux-gnu/libX11.so.6 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1845362/+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 1949293] Re: Context menu of an empty Trash is spawned at +0+0 and has no action items
@lotuspsychje You're absolutely correct! I did not check that. After the context menu disappears, Trash becomes un-right-clickable. Whether it needs to produce some sort of a feedback or offer at least a single action, i.e. Open/View Trash, is a valid question. The bug is present on Ubuntu 22.04 20211031 daily build. -- 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/1949293 Title: Context menu of an empty Trash is spawned at +0+0 and has no action items Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Right-clicking an empty Trash icon in the Ubuntu dock causes the context menu to spawn in the upper left-hand corner. Additionally, the context menu contains no action items. The latter is merely an observation and perhaps isn't related to the bug itself. 1) Ubuntu 21.10 2) gnome-shell-extension-ubuntu-dock (70~ubuntu3) 3) Context menu is shown next to Trash icon with a list of possible actions (Open/View Trash is my only suggestion) 4) Context menu is spawned at +0+0 with no action items A short screencast is attached. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 31 13:58:13 2021 InstallationDate: Installed on 2021-10-16 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1949293/+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 1949294] Re: Right-clicking Terminal in the Ubuntu dock and selecting “Preferences” opens a new instance of Terminal instead
Testing on Ubuntu 22.04 20211031 daily build, the bug doesn't appear, so I guess it got fixed. Hence, I'm changing the status to "Incomplete" until someone else encounters it and reports that here. ** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1949294 Title: Right-clicking Terminal in the Ubuntu dock and selecting “Preferences” opens a new instance of Terminal instead Status in gnome-terminal package in Ubuntu: Incomplete Bug description: 1) Ubuntu 21.10 2) gnome-terminal (3.38.1-1ubuntu2) 3) The Preferences window should pop up 4) A new instance of Terminal is opened. The reason is in the desktop entry for Terminal, the last line (23) to be precise: [Desktop Action preferences] Name=Preferences Exec=gnome-terminal However, manually appending the --preferences option changes absolutely nothing, even if running instances of Terminal are present. In addition, the --zoom=ZOOM option is not recognized either. Other applications, such as Firefox, are working as intended and offer appropriate windows/actions. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-terminal 3.38.1-1ubuntu2 [modified: usr/share/applications/org.gnome.Terminal.desktop] ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 31 14:21:05 2021 InstallationDate: Installed on 2021-10-16 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1949294/+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 1949294] [NEW] Right-clicking Terminal in the Ubuntu dock and selecting “Preferences” opens a new instance of Terminal instead
Public bug reported: 1) Ubuntu 21.10 2) gnome-terminal (3.38.1-1ubuntu2) 3) The Preferences window should pop up 4) A new instance of Terminal is opened. The reason is in the desktop entry for Terminal, the last line (23) to be precise: [Desktop Action preferences] Name=Preferences Exec=gnome-terminal However, manually appending the --preferences option changes absolutely nothing, even if running instances of Terminal are present. In addition, the --zoom=ZOOM option is not recognized either. Other applications, such as Firefox, are working as intended and offer appropriate windows/actions. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-terminal 3.38.1-1ubuntu2 [modified: usr/share/applications/org.gnome.Terminal.desktop] ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 31 14:21:05 2021 InstallationDate: Installed on 2021-10-16 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Description changed: 1) Ubuntu 21.10 2) gnome-terminal (3.38.1-1ubuntu2) 3) The Preferences window should pop up - 4) A new instance of Terminal is opened. + 4) A new instance of Terminal is opened. - The reason is the desktop entry of Terminal, the last line (23) to be + The reason is in the desktop entry of Terminal, the last line (23) to be precise: [Desktop Action preferences] Name=Preferences Exec=gnome-terminal However, manually appending the --preferences option changes absolutely nothing, even if running instances of Terminal are present. In addition, the --zoom=ZOOM option is not recognized either. Other applications, such as Firefox, are working as intended and offer appropriate windows/actions. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-terminal 3.38.1-1ubuntu2 [modified: usr/share/applications/org.gnome.Terminal.desktop] ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 31 14:21:05 2021 InstallationDate: Installed on 2021-10-16 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: 1) Ubuntu 21.10 2) gnome-terminal (3.38.1-1ubuntu2) 3) The Preferences window should pop up 4) A new instance of Terminal is opened. - The reason is in the desktop entry of Terminal, the last line (23) to be - precise: + The reason is in the desktop entry for Terminal, the last line (23) to + be precise: [Desktop Action preferences] Name=Preferences Exec=gnome-terminal However, manually appending the --preferences option changes absolutely nothing, even if running instances of Terminal are present. In addition, the --zoom=ZOOM option is not recognized either. Other applications, such as Firefox, are working as intended and offer appropriate windows/actions. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-terminal 3.38.1-1ubuntu2 [modified: usr/share/applications/org.gnome.Terminal.desktop] ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 31 14:21:05 2021 InstallationDate: Installed on 2021-10-16 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1949294 Title: Right-clicking Terminal in the Ubuntu dock and selecting “Preferences” opens a new instance of Terminal instead Status in gnome-terminal package in Ubuntu: New Bug description: 1) Ubuntu 21.10 2) gnome-terminal (3.38.1-1ubuntu2) 3) The Preferences window should pop up 4) A new instance of Terminal is opened. The reason is in the desktop entry for Terminal, the last line (23) to be precise: [Desktop Action preferences] Name=Preferences Exec=gnome-terminal However, manually appending the --preferences option changes absolutely nothing, even if running instances of Terminal are present. In addition, the --zoom=ZOOM option is not recognized either. Other
[Desktop-packages] [Bug 1949293] [NEW] Context menu of an empty Trash is spawned at +0+0 and has no action items
Public bug reported: Right-clicking an empty Trash icon in the Ubuntu dock causes the context menu to spawn in the upper left-hand corner. Additionally, the context menu contains no action items. The latter is merely an observation and perhaps isn't related to the bug itself. 1) Ubuntu 21.10 2) gnome-shell-extension-ubuntu-dock (70~ubuntu3) 3) Context menu is shown next to Trash icon with a list of possible actions (Open/View Trash is my only suggestion) 4) Context menu is spawned at +0+0 with no action items A short screencast is attached. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 31 13:58:13 2021 InstallationDate: Installed on 2021-10-16 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "Screencast from 10-31-2021 01:55:32 PM.webm" https://bugs.launchpad.net/bugs/1949293/+attachment/5537271/+files/Screencast%20from%2010-31-2021%2001%3A55%3A32%20PM.webm ** Description changed: Right-clicking an empty Trash icon in the Ubuntu dock causes the context menu to spawn in the upper left-hand corner. Additionally, the context - menu contains no action items. + menu contains no action items. The latter is merely an observation and + perhaps isn't related to the bug itself. 1) Ubuntu 21.10 2) gnome-shell-extension-ubuntu-dock (70~ubuntu3) 3) Context menu is shown next to Trash icon with a list of possible actions (Open/View Trash is my only suggestion) 4) Context menu is spawned at +0+0 with no action items A short screencast is attached. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 31 13:58:13 2021 InstallationDate: Installed on 2021-10-16 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1949293 Title: Context menu of an empty Trash is spawned at +0+0 and has no action items Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Right-clicking an empty Trash icon in the Ubuntu dock causes the context menu to spawn in the upper left-hand corner. Additionally, the context menu contains no action items. The latter is merely an observation and perhaps isn't related to the bug itself. 1) Ubuntu 21.10 2) gnome-shell-extension-ubuntu-dock (70~ubuntu3) 3) Context menu is shown next to Trash icon with a list of possible actions (Open/View Trash is my only suggestion) 4) Context menu is spawned at +0+0 with no action items A short screencast is attached. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 31 13:58:13 2021 InstallationDate: Installed on 2021-10-16 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1949293/+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 1946525] Re: Removable media are not mounted automatically
@bjorn-hutmacher, thank you for the thorough description! Do removable media show up in the Files at least? In my case, I could see them being recognized and I could click on them, which would then mount them successfully. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1946525 Title: Removable media are not mounted automatically Status in udisks2 package in Ubuntu: Confirmed Bug description: 1) Ubuntu Desktop amd 64 20211008.1 daily build 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+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 1946525] Re: Removable media are not mounted automatically
** Summary changed: - Disks are not being mounted automatically + Removable media are not mounted automatically -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1946525 Title: Removable media are not mounted automatically Status in udisks2 package in Ubuntu: Confirmed Bug description: 1) Ubuntu Desktop amd 64 20211008.1 daily build 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+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 1946525] Re: Disks are not being mounted automatically
I have tried to reproduce this bug numerous times, but to no avail. Further testing is required. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1946525 Title: Disks are not being mounted automatically Status in udisks2 package in Ubuntu: Confirmed Bug description: 1) Ubuntu Desktop amd 64 20211008.1 daily build 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+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 1946525] Re: Disks are not being mounted automatically
** Changed in: udisks2 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1946525 Title: Disks are not being mounted automatically Status in udisks2 package in Ubuntu: Confirmed Bug description: 1) Ubuntu Desktop amd 64 20211008.1 daily build 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+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 1946525] Re: Disks are not being mounted automatically
Yes. This behavior is observed in a VirtualBox virtual machine. It doesn't occur every time. I'll try reproducing it on a hardware in a live session environment and see if I can get relevant journal entries and outputs. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1946525 Title: Disks are not being mounted automatically Status in udisks2 package in Ubuntu: Incomplete Bug description: 1) Ubuntu Desktop amd 64 20211008.1 daily build 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+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 1946525] [NEW] Disks are not being mounted automatically
Public bug reported: 1) Ubuntu Desktop amd 64 20211008.1 daily build 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: udisks2 (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 udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1946525 Title: Disks are not being mounted automatically Status in udisks2 package in Ubuntu: New Bug description: 1) Ubuntu Desktop amd 64 20211008.1 daily build 2) udisks 2.9.4-1 3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions disk images, should be mounted automatically 4) the automount feature seems to be gone or non-functional in the last couple of days ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 60-vboxadd.rules 70-snap.snap-store.rules Date: Sat Oct 9 01:37:13 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1946525/+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 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscre
** Attachment added: "_usr_bin_gnome-shell.999.crash" https://bugs.launchpad.net/mutter/+bug/1942031/+attachment/5531059/+files/_usr_bin_gnome-shell.999.crash -- 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/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() from g_object_unref() from clutter_stage_view_finalize() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1942031/+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 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscre
Ubuntu Desktop amd64 daily-live 20211006 gnome-shell 40.5-1ubuntu2 gnome-shell --sm-disable --mode=ubiquity crash with signal 11 Shall I include more logs? -- 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/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() from g_object_unref() from clutter_stage_view_finalize() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1942031/+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 1893439] Re: Adjusting the 'Pointer speed' mouse setting in Unity has no effect
Testing Ubuntu Unity Impish ISO, I've just realized that touchpad click doesn't work either, although installing xserver-xorg-input-synaptics helped with that. Touchpad can be configured as expected (additional checkboxes appeared), the mouse cannot, though. Installing x-x-i-mouse did not help either. Regardless, I think x-x-i-synaptics has to be included in the ISO. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1893439 Title: Adjusting the 'Pointer speed' mouse setting in Unity has no effect Status in unity-control-center package in Ubuntu: Confirmed Bug description: - What is expected to happen: Pointer speed (mouse sensitivity) adjusts according to the slider's position. - What happens instead: The setting has no effect on mouse, though the slider can be moved freely. - How it happens: 1) Log in into a Unity session; 2) Go to System Settings > Mouse & Touchpad > Try moving the slider to either side; 3) The new values are not applied, pointer speed is not updated. Whenever the slider's position is moved, the "speed" key in "org.gnome.desktop.peripherals.mouse" gsettings schema updates accordingly, however the "libinput Accel Speed (290)" property does not. It stays at 0. Manually setting a value to this property (xinput --set-prop device property value) has an immediate effect. This setting works as expected during a GNOME session. Both the "speed" key and the "Accel Speed" property update as the slider is adjusted. Ubuntu 18.04.5 LTS; unity 7.5.0 (=7.5.0+18.04.20190304-0ubuntu1); lightdm 1.26.0 (=1.26.0-0ubuntu1). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Aug 28 18:34:50 2020 InstallationDate: Installed on 2016-11-03 (1393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: unity-control-center UpgradeStatus: Upgraded to bionic on 2020-08-17 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1893439/+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 1945658] Re: Link to release notes on Ubiquity language plugin page is opened with gedit
** Description changed:
Reproducible only during Live session. See comment #2.
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
/etc/mailcap still points to text/html; /usr/bin/sensible-browser
- I will attach relevant files here in a moment and will also look through
- the code.
-
For now, I propose to revert the last commit, at least until the bug is
fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1945658
Title:
Link to release notes on Ubiquity language plugin page is opened with
gedit
Status in xdg-utils package in Ubuntu:
Triaged
Bug description:
Reproducible only during Live session. See comment #2.
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
/etc/mailcap still points to text/html; /usr/bin/sensible-browser
For now, I propose to revert the last commit, at least until the bug
is fixed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1945658/+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 1945658] Re: Link to release notes on Ubiquity language plugin page is opened with gedit
** Description changed:
+ Reproducible only during Live session. See comment #2.
+
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
/etc/mailcap still points to text/html; /usr/bin/sensible-browser
I will attach relevant files here in a moment and will also look through
the code.
For now, I propose to revert the last commit, at least until the bug is
fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1945658
Title:
Link to release notes on Ubiquity language plugin page is opened with
gedit
Status in xdg-utils package in Ubuntu:
Triaged
Bug description:
Reproducible only during Live session. See comment #2.
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
/etc/mailcap still points to text/html; /usr/bin/sensible-browser
I will attach relevant files here in a moment and will also look
through the code.
For now, I propose to revert the last commit, at least until the bug
is fixed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1945658/+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 1945658] Re: Link to release notes on Ubiquity language plugin page is opened with gedit
** Description changed:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
/etc/mailcap still points to text/html; /usr/bin/sensible-browser
I will attach relevant files here in a moment and will also look through
the code.
+
+ For now, I propose to revert the last commit, at least until it's fixed.
** Description changed:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
/etc/mailcap still points to text/html; /usr/bin/sensible-browser
I will attach relevant files here in a moment and will also look through
the code.
- For now, I propose to revert the last commit, at least until it's fixed.
+ For now, I propose to revert the last commit, at least until the bug is
+ fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1945658
Title:
Link to release notes on Ubiquity language plugin page is opened with
gedit
Status in xdg-utils package in Ubuntu:
Triaged
Bug description:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
/etc/mailcap still points to text/html; /usr/bin/sensible-browser
I will attach relevant files here in a moment and will also look
through the code.
For now, I propose to revert the last commit, at least until the bug
is fixed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1945658/+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 1945658] Re: Link to release notes on Ubiquity language plugin page is opened with gedit
** Summary changed:
- The link to the release notes is opened with gedit
+ Link to release notes on Ubiquity language plugin page is opened with gedit
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1945658
Title:
Link to release notes on Ubiquity language plugin page is opened with
gedit
Status in xdg-utils package in Ubuntu:
Triaged
Bug description:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
/etc/mailcap still points to text/html; /usr/bin/sensible-browser
I will attach relevant files here in a moment and will also look
through the code.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1945658/+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 1945658] Re: The link to the release notes is opened with gedit
** Description changed:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
/etc/mailcap still points to text/html; /usr/bin/sensible-browser
I will attach relevant files here in a moment and will also look through
- its code.
+ the code.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1945658
Title:
The link to the release notes is opened with gedit
Status in xdg-utils package in Ubuntu:
Triaged
Bug description:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
/etc/mailcap still points to text/html; /usr/bin/sensible-browser
I will attach relevant files here in a moment and will also look
through the code.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1945658/+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 1945658] Re: The link to the release notes is opened with gedit
** Description changed:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
- is opened with gedit. Both org.gnome.gedit.desktop and
- firefox_firefox.desktop show correct values for MimeType, however, xdg-
- mime query default text/xml outputs org.gnome.gedit.desktop
+ is opened with gedit. Desktop files for both gedit and firefox show
+ correct values for MimeType, however, xdg-mime query default text/xml
+ outputs org.gnome.gedit.desktop
+
+ /etc/mailcap still points to text/html; /usr/bin/sensible-browser
I will attach relevant files here in a moment and will also look through
- the code.
+ its code.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1945658
Title:
The link to the release notes is opened with gedit
Status in xdg-utils package in Ubuntu:
Confirmed
Bug description:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
/etc/mailcap still points to text/html; /usr/bin/sensible-browser
I will attach relevant files here in a moment and will also look
through its code.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1945658/+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 1945658] Re: The link to the release notes is opened with gedit
** Description changed:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
- is opened with gedit. Desktop files for both gedit and firefox show
- correct values for MimeType, however, xdg-mime query default text/xml
- outputs org.gnome.gedit.desktop
+ is opened with gedit. Both org.gnome.gedit.desktop and
+ firefox_firefox.desktop show correct values for MimeType, however, xdg-
+ mime query default text/xml outputs org.gnome.gedit.desktop
I will attach relevant files here in a moment and will also look through
- its code.
+ the code.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1945658
Title:
The link to the release notes is opened with gedit
Status in xdg-utils package in Ubuntu:
Confirmed
Bug description:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Both org.gnome.gedit.desktop and
firefox_firefox.desktop show correct values for MimeType, however,
xdg-mime query default text/xml outputs org.gnome.gedit.desktop
I will attach relevant files here in a moment and will also look
through the code.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1945658/+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 1945658] Re: The link to the release notes is opened with gedit
** Tags added: ubiquity xdg-open xdg-utils
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1945658
Title:
The link to the release notes is opened with gedit
Status in xdg-utils package in Ubuntu:
Confirmed
Bug description:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Both org.gnome.gedit.desktop and
firefox_firefox.desktop show correct values for MimeType, however,
xdg-mime query default text/xml outputs org.gnome.gedit.desktop
I will attach relevant files here in a moment and will also look
through the code.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1945658/+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 1945658] Re: The link to the release notes is opened with gedit
journalctl entry. nothing too fancy, just confirming that it is indeed
opened with gedit
** Attachment added: "ubiquity-journalctl"
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1945658/+attachment/5529525/+files/ubiquity-journalctl
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1945658
Title:
The link to the release notes is opened with gedit
Status in xdg-utils package in Ubuntu:
Confirmed
Bug description:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
I will attach relevant files here in a moment and will also look
through its code.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1945658/+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 1945658] [NEW] The link to the release notes is opened with gedit
Public bug reported:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
I will attach relevant files here in a moment and will also look through
its code.
** Affects: xdg-utils (Ubuntu)
Importance: Undecided
Status: Confirmed
** Changed in: xdg-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1945658
Title:
The link to the release notes is opened with gedit
Status in xdg-utils package in Ubuntu:
Confirmed
Bug description:
Ubuntu Impish daily-live 20210930
ubiquity 21.10.6
xdg-utils 1.1.3-2ubuntu2
Commit 33e306c9d77c6688e02d0cbae9a1d86f404272d3 to ubiquity changed
sensible-browser to xdg-open to open hyperlinks.
Now, for some reason the link to the release notes
http://www.ubuntu.com/getubuntu/releasenotes?os=ubuntu=21.10=${LANG}
is opened with gedit. Desktop files for both gedit and firefox show
correct values for MimeType, however, xdg-mime query default text/xml
outputs org.gnome.gedit.desktop
I will attach relevant files here in a moment and will also look
through its code.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1945658/+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 1945198] Re: Ubuntu Software first startup stuck at “Downloading application ratings…”
*** This bug is a duplicate of bug 1944768 *** https://bugs.launchpad.net/bugs/1944768 ** This bug has been marked a duplicate of bug 1944768 snap-store hangs building catalog on first run (impish) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1945198 Title: Ubuntu Software first startup stuck at “Downloading application ratings…” Status in gnome-software package in Ubuntu: New Bug description: Ubuntu Impish 20210926 daily build fresh install on VirtualBox VM ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-software (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 27 08:25:15 2021 InstallationDate: Installed on 2021-09-27 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210926) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1945198/+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 1945198] Re: Ubuntu Software first startup stuck at “Downloading application ratings…”
Attaching relevant log entries. ** Attachment added: "snap" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1945198/+attachment/5529417/+files/snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1945198 Title: Ubuntu Software first startup stuck at “Downloading application ratings…” Status in gnome-software package in Ubuntu: New Bug description: Ubuntu Impish 20210926 daily build fresh install on VirtualBox VM ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-software (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 27 08:25:15 2021 InstallationDate: Installed on 2021-09-27 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210926) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1945198/+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 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscre
Still affects libX11 in Live session (build 20210929), which I am currently testing. Same thing: segfault at 0 ip 7f---77f sp 7ff0 error 4 in libX11.so.6.4.0[7f---000+8c000] Can attach detailed logs if required. -- 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/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() from cogl_onscreen_glx_dispose() from g_object_unref() from clutter_stage_view_finalize() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1942031/+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 1893439] Re: Adjusting the 'Pointer speed' mouse setting in Unity has no effect
** Summary changed: - Adjusting the 'Pointer speed' setting in Bionic running on Unity has no effect + Adjusting the 'Pointer speed' mouse setting in Unity has no effect -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1893439 Title: Adjusting the 'Pointer speed' mouse setting in Unity has no effect Status in unity-control-center package in Ubuntu: Confirmed Bug description: - What is expected to happen: Pointer speed (mouse sensitivity) adjusts according to the slider's position. - What happens instead: The setting has no effect on mouse, though the slider can be moved freely. - How it happens: 1) Log in into a Unity session; 2) Go to System Settings > Mouse & Touchpad > Try moving the slider to either side; 3) The new values are not applied, pointer speed is not updated. Whenever the slider's position is moved, the "speed" key in "org.gnome.desktop.peripherals.mouse" gsettings schema updates accordingly, however the "libinput Accel Speed (290)" property does not. It stays at 0. Manually setting a value to this property (xinput --set-prop device property value) has an immediate effect. This setting works as expected during a GNOME session. Both the "speed" key and the "Accel Speed" property update as the slider is adjusted. Ubuntu 18.04.5 LTS; unity 7.5.0 (=7.5.0+18.04.20190304-0ubuntu1); lightdm 1.26.0 (=1.26.0-0ubuntu1). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Aug 28 18:34:50 2020 InstallationDate: Installed on 2016-11-03 (1393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: unity-control-center UpgradeStatus: Upgraded to bionic on 2020-08-17 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1893439/+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 1945198] [NEW] Ubuntu Software first startup stuck at “Downloading application ratings…”
Public bug reported: Ubuntu Impish 20210926 daily build fresh install on VirtualBox VM ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-software (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 27 08:25:15 2021 InstallationDate: Installed on 2021-09-27 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210926) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "gnome-software.png" https://bugs.launchpad.net/bugs/1945198/+attachment/5528380/+files/gnome-software.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1945198 Title: Ubuntu Software first startup stuck at “Downloading application ratings…” Status in gnome-software package in Ubuntu: New Bug description: Ubuntu Impish 20210926 daily build fresh install on VirtualBox VM ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-software (not installed) ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 27 08:25:15 2021 InstallationDate: Installed on 2021-09-27 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210926) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1945198/+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 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent()
I believe this bug needs to be mentioned here: https://discourse.ubuntu.com/t/impish-indri-release-notes/21951 in the "Ubuntu Desktop" category. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1942031 Title: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent() Status in gnome-shell package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942031/+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 1942706] [NEW] gnome-shell crashed right after Live session started. Won't allow to send the report because of "some obsolete packages"
Public bug reported:
Live session started with a crash.
ProblemType: Crash
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 5 14:48:10 2021
DistroRelease: Ubuntu 21.10
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1630503878
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcCwd: /home/ubuntu
ProcEnviron:
PATH=(custom, no user)
LANG=C.UTF-8
XDG_RUNTIME_DIR=
ProcMaps:
"Send" was clicked on the crash dialog. After a few moments, it returned
the following:
Package: gnome-shell 40.2-1ubuntu6
PackageArchitecture: amd64
SourcePackage: gnome-shell
UnreportableReason:
You have some obsolete package versions installed. Please upgrade the
following packages and check if the problem still occurs:
gir1.2-ibus-1.0, ibus, ibus-data, ibus-gtk, ibus-gtk3, ibus-gtk4,
libibus-1.0-5, libjack-jackd2-0, python3-ibus-1.0
_MarkForUpload: True
Crash log is attached.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu6
ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
Uname: Linux 5.13.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu68
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 5 14:54:00 2021
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 'au'),
('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210905)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug impish
** Attachment added: "_usr_bin_gnome-shell.999.crash"
https://bugs.launchpad.net/bugs/1942706/+attachment/5523035/+files/_usr_bin_gnome-shell.999.crash
--
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/1942706
Title:
gnome-shell crashed right after Live session started. Won't allow to
send the report because of "some obsolete packages"
Status in gnome-shell package in Ubuntu:
New
Bug description:
Live session started with a crash.
ProblemType: Crash
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 5 14:48:10 2021
DistroRelease: Ubuntu 21.10
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1630503878
ProcCmdline: gnome-shell --sm-disable --mode=ubiquity
ProcCwd: /home/ubuntu
ProcEnviron:
PATH=(custom, no user)
LANG=C.UTF-8
XDG_RUNTIME_DIR=
ProcMaps:
"Send" was clicked on the crash dialog. After a few moments, it
returned the following:
Package: gnome-shell 40.2-1ubuntu6
PackageArchitecture: amd64
SourcePackage: gnome-shell
UnreportableReason:
You have some obsolete package versions installed. Please upgrade the
following packages and check if the problem still occurs:
gir1.2-ibus-1.0, ibus, ibus-data, ibus-gtk, ibus-gtk3, ibus-gtk4,
libibus-1.0-5, libjack-jackd2-0, python3-ibus-1.0
_MarkForUpload: True
Crash log is attached.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu6
ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
Uname: Linux 5.13.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu68
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 5 14:54:00 2021
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
'au'), ('xkb', 'cm'), ('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210905)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942706/+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 1940707] Re: Maximized window becomes a mess at next startup after manually choosing to restore previous session
I assume that privacy.resistFingerprinting preference is somehow being enabled before sessionstore-backups are loaded which is why the window state appears unmaximized and distorted. -- 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/1940707 Title: Maximized window becomes a mess at next startup after manually choosing to restore previous session Status in firefox package in Ubuntu: New Bug description: Checked on both current and new user. This behavior is observed only if "Restore previous session" is not enabled to occur automatically at startup. 1) Ubuntu 20.04.2 LTS 2) 91.0+build2-0ubuntu0.20.04.1 3) "Restore previous session" should not change window settings and appearance 4) "Restore previous session" drastically changes window settings and appearance in a very unpleasant way Steps to reproduce: 1) Don't have "Restore previous session" enabled in Settings > General > Startup 2) Browse some sites 3) Close the window and confirm your desire to close it 4) Reopen Firefox 5) Go to History and select "Restore previous session" 6) The window will break apart as a result Screenshot below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 91.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kbar 1005 F pulseaudio /dev/snd/controlC1: kbar 1005 F pulseaudio BuildID: 20210804193234 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Fri Aug 20 23:27:25 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 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-05-17 (95 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.102 metric 600 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=None/None (Out of date) Profile0 - LastVersion=91.0/20210804193234 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2014 dmi.bios.release: 15.54 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 220D dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.49 dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:br15.54:efr86.49:svnHewlett-Packard:pnHP14NotebookPC:pvr097512405F0610180:rvnHewlett-Packard:rn220D:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 14 Notebook PC dmi.product.sku: L8N69PA#UUF dmi.product.version: 097512405F0610180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1940707/+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 1940707] Re: Maximized window becomes a mess at next start-up after manually choosing to restore previous session
** Description changed: - Checked on both current and new user. + Checked on both current and new user. This behavior is observed only if + "Restore previous session" is not enabled to occur automatically at + startup. 1) Ubuntu 20.04.2 LTS 2) 91.0+build2-0ubuntu0.20.04.1 3) "Restore previous session" should not change window settings and appearance 4) "Restore previous session" drastically changes window settings and appearance in a very unpleasant way Steps to reproduce: 1) Don't have "Restore previous session" enabled in Settings > General > Startup 2) Browse some sites 3) Close the window and confirm your desire to close it 4) Reopen Firefox 5) Go to History and select "Restore previous session" 6) The window will break apart as a result Screenshot below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 91.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: kbar 1005 F pulseaudio - /dev/snd/controlC1: kbar 1005 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: kbar 1005 F pulseaudio + /dev/snd/controlC1: kbar 1005 F pulseaudio BuildID: 20210804193234 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Fri Aug 20 23:27:25 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 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-05-17 (95 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: - default via 192.168.1.1 dev wlo1 proto dhcp metric 600 - 169.254.0.0/16 dev wlo1 scope link metric 1000 - 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.102 metric 600 + default via 192.168.1.1 dev wlo1 proto dhcp metric 600 + 169.254.0.0/16 dev wlo1 scope link metric 1000 + 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.102 metric 600 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=None/None (Out of date) - Profile0 - LastVersion=91.0/20210804193234 + Profile1 (Default) - LastVersion=None/None (Out of date) + Profile0 - LastVersion=91.0/20210804193234 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2014 dmi.bios.release: 15.54 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 220D dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.49 dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:br15.54:efr86.49:svnHewlett-Packard:pnHP14NotebookPC:pvr097512405F0610180:rvnHewlett-Packard:rn220D:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 14 Notebook PC dmi.product.sku: L8N69PA#UUF dmi.product.version: 097512405F0610180 dmi.sys.vendor: Hewlett-Packard ** Summary changed: - Maximized window becomes a mess at next start-up after manually choosing to restore previous session + Maximized window becomes a mess at next startup after manually choosing to restore previous session -- 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/1940707 Title: Maximized window becomes a mess at next startup after manually choosing to restore previous session Status in firefox package in Ubuntu: New Bug description: Checked on both current and new user. This behavior is observed only if "Restore previous session" is not enabled to occur automatically at startup. 1) Ubuntu 20.04.2 LTS 2) 91.0+build2-0ubuntu0.20.04.1 3) "Restore previous session" should not change
[Desktop-packages] [Bug 1940707] [NEW] Maximized window becomes a mess at next start-up after manually choosing to restore previous session
Public bug reported: Checked on both current and new user. 1) Ubuntu 20.04.2 LTS 2) 91.0+build2-0ubuntu0.20.04.1 3) "Restore previous session" should not change window settings and appearance 4) "Restore previous session" drastically changes window settings and appearance in a very unpleasant way Steps to reproduce: 1) Don't have "Restore previous session" enabled in Settings > General > Startup 2) Browse some sites 3) Close the window and confirm your desire to close it 4) Reopen Firefox 5) Go to History and select "Restore previous session" 6) The window will break apart as a result Screenshot below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 91.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kbar 1005 F pulseaudio /dev/snd/controlC1: kbar 1005 F pulseaudio BuildID: 20210804193234 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Fri Aug 20 23:27:25 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 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-05-17 (95 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: default via 192.168.1.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.102 metric 600 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=None/None (Out of date) Profile0 - LastVersion=91.0/20210804193234 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2014 dmi.bios.release: 15.54 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 220D dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.49 dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:br15.54:efr86.49:svnHewlett-Packard:pnHP14NotebookPC:pvr097512405F0610180:rvnHewlett-Packard:rn220D:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 14 Notebook PC dmi.product.sku: L8N69PA#UUF dmi.product.version: 097512405F0610180 dmi.sys.vendor: Hewlett-Packard ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "firefox.png" https://bugs.launchpad.net/bugs/1940707/+attachment/5519486/+files/firefox.png -- 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/1940707 Title: Maximized window becomes a mess at next start-up after manually choosing to restore previous session Status in firefox package in Ubuntu: New Bug description: Checked on both current and new user. 1) Ubuntu 20.04.2 LTS 2) 91.0+build2-0ubuntu0.20.04.1 3) "Restore previous session" should not change window settings and appearance 4) "Restore previous session" drastically changes window settings and appearance in a very unpleasant way Steps to reproduce: 1) Don't have "Restore previous session" enabled in Settings > General > Startup 2) Browse some sites 3) Close the window and confirm your desire to close it 4) Reopen Firefox 5) Go to History and select "Restore previous session" 6) The window will break apart as a result Screenshot below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 91.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kbar 1005
[Desktop-packages] [Bug 1889102] Re: [ubuntu-dock] App grid has too many page dots on right
Here is that short screencast showcasing the bug: https://launchpadlibrarian.net/502131812/show-all-apps.webm ** Attachment added: "show-all-apps.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889102/+attachment/5422847/+files/show-all-apps.webm -- 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/1889102 Title: [ubuntu-dock] App grid has too many page dots on right Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-dashtodock package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have noticed a bug with the applications menu. I am having a weird issue with adding apps into folders on the menu. If I try opening a folder, the entire screen glitches out and the bar on the right-hand size showing how many pages are on the menu show more pages than there actually is. Occasionally if I try adding or removing an app to a folder, the entire system freezes. The only way I am able to get things back to normal is a forced restart by holding down the power button. The only way I have been able to not come across this issue is to have no folders in my menu at all, which took a while as the system kept crashing during the process. However, I am no longer experiencing the issue with no folders, but it returns when I try creating a folder. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 27 16:31:56 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Iris Plus Graphics G7 [17aa:3f1a] InstallationDate: Installed on 2020-07-22 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:56b2 IMC Networks Integrated Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 004: ID 1ea7:0066 SHARKOON Technologies GmbH [Mediatrack Edge Mini Keyboard] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81VV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1664842e-9af5-44b6-a3c8-f9235f094044 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2020 dmi.bios.vendor: LENOVO dmi.bios.version: CUCN21WW(V1.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32776 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S340-14IIL dmi.modalias: dmi:bvnLENOVO:bvrCUCN21WW(V1.10):bd05/27/2020:svnLENOVO:pn81VV:pvrLenovoIdeaPadS340-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32776WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IIL: dmi.product.family: IdeaPad S340-14IIL dmi.product.name: 81VV dmi.product.sku: LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL dmi.product.version: Lenovo IdeaPad S340-14IIL dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889102/+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 1899956] [NEW] Opening the Utilities folder and trying to scroll through it will expand and multiply the pages on the Show all applications panel
Public bug reported: What's expected to happen: Retracting or closing the Utilities folder should not affect the amount of pages displayed on the Show all applications panel. What happens instead: Retracting or closing the Utilities folder increases the amount of dots that represent the pages displayed on the Show all applications panel. A short screencast showcasing the bug is attached to the bug report below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 15:47:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-11-03 (1441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-03 (11 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal gnome-shell ** Attachment added: "A short screencast showcasing the bug" https://bugs.launchpad.net/bugs/1899956/+attachment/5422563/+files/show-all-apps.webm ** Description changed: - What's expected to happen: + What's expected to happen: Retracting or closing the Utilities folder should not affect the amount of pages on the Show all applications panel. - What happens instead: + What happens instead: Retracting or closing the Utilities folder increases the amount of dots that represent the pages on the Show all applications panel. + + A short screencast showcasing the bug is attached to the bug report + below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 15:47:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-11-03 (1441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-03 (11 days ago) ** Description changed: - What's expected to happen: - Retracting or closing the Utilities folder should not affect the amount of pages on the Show all applications panel. + What's expected to happen: + Retracting or closing the Utilities folder should not affect the amount of pages displayed on the Show all applications panel. What happens instead: Retracting or closing the Utilities folder increases the amount of dots that represent the pages on the Show all applications panel. A short screencast showcasing the bug is attached to the bug report below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 15:47:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-11-03 (1441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-03 (11 days ago) ** Description changed: - What's expected to happen: + What's expected to happen: Retracting or closing the Utilities folder should not affect the amount of pages displayed on the Show all applications panel. What happens instead: - Retracting or closing the Utilities folder increases the amount of dots that represent the pages on the Show all applications panel. + Retracting or closing the Utilities folder increases the amount of dots that represent the pages shown on the Show all applications panel. A short screencast showcasing the bug is attached to the bug report below. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 15 15:47:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-11-03 (1441 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-03 (11 days ago)
[Desktop-packages] [Bug 1893439] Re: Adjusting the 'Pointer speed' setting in Bionic running on Unity has no effect
This behavior can be observed from an Ubuntu Live USB session as well. Booting up a live Ubuntu 18.04.5 session, installing Unity and trying to adjust the Pointer speed slider yields the same result, or no result, shall I say. Hence, I set the status to "Confirmed". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1893439 Title: Adjusting the 'Pointer speed' setting in Bionic running on Unity has no effect Status in unity-control-center package in Ubuntu: Confirmed Bug description: - What is expected to happen: Pointer speed (mouse sensitivity) adjusts according to the slider's position. - What happens instead: The setting has no effect on mouse, though the slider can be moved freely. - How it happens: 1) Log in into a Unity session; 2) Go to System Settings > Mouse & Touchpad > Try moving the slider to either side; 3) The new values are not applied, pointer speed is not updated. Whenever the slider's position is moved, the "speed" key in "org.gnome.desktop.peripherals.mouse" gsettings schema updates accordingly, however the "libinput Accel Speed (290)" property does not. It stays at 0. Manually setting a value to this property (xinput --set-prop device property value) has an immediate effect. This setting works as expected during a GNOME session. Both the "speed" key and the "Accel Speed" property update as the slider is adjusted. Ubuntu 18.04.5 LTS; unity 7.5.0 (=7.5.0+18.04.20190304-0ubuntu1); lightdm 1.26.0 (=1.26.0-0ubuntu1). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Aug 28 18:34:50 2020 InstallationDate: Installed on 2016-11-03 (1393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: unity-control-center UpgradeStatus: Upgraded to bionic on 2020-08-17 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1893439/+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 1893439] Re: Adjusting the 'Pointer speed' setting in Bionic running on Unity has no effect
** Changed in: unity-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1893439 Title: Adjusting the 'Pointer speed' setting in Bionic running on Unity has no effect Status in unity-control-center package in Ubuntu: Confirmed Bug description: - What is expected to happen: Pointer speed (mouse sensitivity) adjusts according to the slider's position. - What happens instead: The setting has no effect on mouse, though the slider can be moved freely. - How it happens: 1) Log in into a Unity session; 2) Go to System Settings > Mouse & Touchpad > Try moving the slider to either side; 3) The new values are not applied, pointer speed is not updated. Whenever the slider's position is moved, the "speed" key in "org.gnome.desktop.peripherals.mouse" gsettings schema updates accordingly, however the "libinput Accel Speed (290)" property does not. It stays at 0. Manually setting a value to this property (xinput --set-prop device property value) has an immediate effect. This setting works as expected during a GNOME session. Both the "speed" key and the "Accel Speed" property update as the slider is adjusted. Ubuntu 18.04.5 LTS; unity 7.5.0 (=7.5.0+18.04.20190304-0ubuntu1); lightdm 1.26.0 (=1.26.0-0ubuntu1). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Aug 28 18:34:50 2020 InstallationDate: Installed on 2016-11-03 (1393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: unity-control-center UpgradeStatus: Upgraded to bionic on 2020-08-17 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1893439/+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 1893439] [NEW] Adjusting the 'Pointer speed' setting in Bionic running on Unity has no effect
Public bug reported: - What is expected to happen: Pointer speed (mouse sensitivity) adjusts according to the slider's position. - What happens instead: The setting has no effect on mouse, though the slider can be moved freely. - How it happens: 1) Log in into a Unity session; 2) Go to System Settings > Mouse & Touchpad > Try moving the slider to either side; 3) The new values are not applied, pointer speed is not updated. Whenever the slider's position is moved, the "speed" key in "org.gnome.desktop.peripherals.mouse" gsettings schema updates accordingly, however the "libinput Accel Speed (290)" property does not. It stays at 0. Manually setting a value to this property (xinput --set- prop device property value) has an immediate effect. This setting works as expected during a GNOME session. Both the "speed" key and the "Accel Speed" property update as the slider is adjusted. Ubuntu 18.04.5 LTS; unity 7.5.0 (=7.5.0+18.04.20190304-0ubuntu1); lightdm 1.26.0 (=1.26.0-0ubuntu1). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Aug 28 18:34:50 2020 InstallationDate: Installed on 2016-11-03 (1393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: unity-control-center UpgradeStatus: Upgraded to bionic on 2020-08-17 (11 days ago) ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: bionic mouse unity-control-center ** Attachment added: "graphical representation" https://bugs.launchpad.net/bugs/1893439/+attachment/5405447/+files/mouse.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1893439 Title: Adjusting the 'Pointer speed' setting in Bionic running on Unity has no effect Status in unity-control-center package in Ubuntu: New Bug description: - What is expected to happen: Pointer speed (mouse sensitivity) adjusts according to the slider's position. - What happens instead: The setting has no effect on mouse, though the slider can be moved freely. - How it happens: 1) Log in into a Unity session; 2) Go to System Settings > Mouse & Touchpad > Try moving the slider to either side; 3) The new values are not applied, pointer speed is not updated. Whenever the slider's position is moved, the "speed" key in "org.gnome.desktop.peripherals.mouse" gsettings schema updates accordingly, however the "libinput Accel Speed (290)" property does not. It stays at 0. Manually setting a value to this property (xinput --set-prop device property value) has an immediate effect. This setting works as expected during a GNOME session. Both the "speed" key and the "Accel Speed" property update as the slider is adjusted. Ubuntu 18.04.5 LTS; unity 7.5.0 (=7.5.0+18.04.20190304-0ubuntu1); lightdm 1.26.0 (=1.26.0-0ubuntu1). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Aug 28 18:34:50 2020 InstallationDate: Installed on 2016-11-03 (1393 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: unity-control-center UpgradeStatus: Upgraded to bionic on 2020-08-17 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1893439/+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 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged
Proposed package (https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome- shell/+packages) on https://launchpad.net/~gunnarhj/+archive/ubuntu /gnome-shell fixes the bug. -- 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/1890875 Title: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Bug description: [Impact] What should happen: Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order, or reboot. [Test Case] Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) or 5. Reboot or re-login (restarting gnome-shell works as well: killall -3 gnome-shell or Alt+F2 > r > Enter) Then install gnome-shell from bionic-proposed, reboot, and find that an added input source now is effective instantly without any of the mentioned workarounds. [Regression Potential] Minimal. The fix consists of a simple upstream commit which has been in use as from GNOME 3.32. [Other info] Screenshots are attached. The bug is easily reproduced as many times as possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1890875/+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 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged
bug-exists Ubuntu 18.04.5 LTS bionic GNOME Shell 3.28.4 (=3.28.4-0ubuntu18.04.3) gnome-control-center 3.28.2 (=1:3.28.2-0ubuntu0.18.04.6) bug-exists Ubuntu 18.10 cosmic GNOME Shell 3.30.1 (=3.30.1-2ubuntu1) gnome-control-center 3.30.1 (=1:3.30.1-1ubuntu2) no-bug Ubuntu 19.04 disco GNOME Shell 3.32.0 (=3.32.0+git20190410-1ubuntu1) gnome-control-center 3.32.1 (=1:3.32.1-1ubuntu4) Tested on various versions of Ubuntu running on a virtual machine. -- 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/1890875 Title: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged Status in GNOME Shell: Unknown Status in gnome-control-center package in Ubuntu: Fix Released Bug description: What should happen: Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order, or reboot. Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) or 5. Reboot or re-login (restarting gnome-shell works as well: killall -3 gnome-shell or Alt+F2 > r > Enter) Screenshots are attached. The bug is easily reproduced as many times as possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1890875/+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 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged
Maybe the reconfiguration process is delayed as waiting for 20-30 minutes sometimes works, but it's unreliable and I can't seem to reproduce it. -- 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/1890875 Title: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged Status in GNOME Shell: Unknown Status in gnome-control-center package in Ubuntu: Fix Released Bug description: What should happen: Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order, or reboot. Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) or 5. Reboot or re-login (restarting gnome-shell works as well: killall -3 gnome-shell or Alt+F2 > r > Enter) Screenshots are attached. The bug is easily reproduced as many times as possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1890875/+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 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged
I have tried to add an input source through gsettings
gsettings set org.gnome.desktop.input-sources sources "[('xkb', 'us'), ('xkb',
'ru')]"
but it still produced the same result: text input remains at default layout.
Restarting the GNOME Shell fixes the issue and the 'ru' layout gets
added in /etc/default/keyboard configuration file: XKBLAYOUT=us,ru
This may explain why rearranging the order of input sources magically
fixes the bug: newly added input sources probably need to be put into
defaults once to be recognized later.
However, manually editing the keyboard configuration file does nothing.
What probably happens is that gnome-shell recognizes the added input
sources but 'forgets' 1) to send the appropriate command to XKB
(setxkbmap ru) whenever the switch shortcut is invoked; or 2) to
reconfigure the keyboard settings.
--
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/1890875
Title:
Keyboard won't switch its layout to a newly added second input source
unless their order is rearranged
Status in GNOME Shell:
Unknown
Status in gnome-control-center package in Ubuntu:
Fix Released
Bug description:
What should happen:
Adding a second input source (Russian, in my case) should result in being
able to switch to it and use it immediately.
What happens now:
It is not recognized until you rearrange its order, or reboot.
Steps to reproduce this bug:
1. Have English set as primary language.
2. Go to Settings > Region & Language > Input Sources and add Russian.
3. Russian layout is added to Input Sources and the indicator becomes visible
in the Top Bar.
4. You can switch between languages with the assigned keyboard shortcut but
the text input won't change.
5. Rearrange their order in Input Sources: make Russian primary, English
secondary.
6. You can now enter text in Russian.
7. You can now put Russian back to being second in the list (so it does not
cause problems at logic screen, opening up new browser window, etc.)
or 5. Reboot or re-login (restarting gnome-shell works as well:
killall -3 gnome-shell or Alt+F2 > r > Enter)
Screenshots are attached. The bug is easily reproduced as many times as
possible.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18
Uname: Linux 4.15.0-112-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 8 13:39:01 2020
InstallationDate: Installed on 2016-11-03 (1373 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1890875/+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 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3061 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3061 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3061 Importance: Unknown Status: Unknown ** Description changed: What should happen: Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order, or reboot. Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) - or 5. Reboot. + or 5. Reboot or re-login (restarting gnome-shell works as well: killall + -3 gnome-shell or Alt+F2 > r > Enter) - Screenshots are attached. The bug is easily reproduced as many times as - possible. + + Screenshots are attached. The bug is easily reproduced as many times as possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) -- 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/1890875 Title: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged Status in GNOME Shell: Unknown Status in gnome-control-center package in Ubuntu: Fix Released Bug description: What should happen: Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order, or reboot. Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) or 5. Reboot or re-login (restarting gnome-shell works as well: killall -3 gnome-shell or Alt+F2 > r > Enter) Screenshots are attached. The bug is easily reproduced as many times as possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1890875/+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 1890875] Re: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged
I've looked through a lot of various bug trackers and other projects and could not find the exact fix. It may be an ibus problem. -- 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/1890875 Title: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged Status in gnome-control-center package in Ubuntu: Fix Released Bug description: What should happen: Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order, or reboot. Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) or 5. Reboot. Screenshots are attached. The bug is easily reproduced as many times as possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1890875/+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 1890875] Re: Keyboard won't switch its layout to the newly added second input source unless their order is rearranged
Rebooting also solves this issue and can be considered as a work-around. ** Summary changed: - Keyboard won't switch its layout to the newly added second input source unless their order is rearranged + Keyboard won't switch its layout to a newly added second input source unless their order is rearranged ** Description changed: - What should happen: - Adding a second input source (Russian, in my example) should result in being able to switch to it and use it immediately. + What should happen: + Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: - It is not recognized until you rearrange its order. + It is not recognized until you rearrange its order, or reboot. Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. - 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. + 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. - 5. Rearrange their order in Input Sources: make Russian primary, English secondary. + + 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) + + or 5. Reboot. Screenshots are attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) ** Description changed: What should happen: Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order, or reboot. Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) or 5. Reboot. - Screenshots are attached. + Screenshots are attached. The bug is easily reproduced as many times as + possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) -- 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/1890875 Title: Keyboard won't switch its layout to a newly added second input source unless their order is rearranged Status in gnome-control-center package in Ubuntu: New Bug description: What should happen: Adding a second input source (Russian, in my case) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order, or reboot. Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause
[Desktop-packages] [Bug 1890875] Re: Keyboard won't switch its layout to the newly added second input source unless their order is rearranged
** Attachment added: "Another example of this bug, now in gedit" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1890875/+attachment/5399804/+files/gedit.png -- 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/1890875 Title: Keyboard won't switch its layout to the newly added second input source unless their order is rearranged Status in gnome-control-center package in Ubuntu: New Bug description: What should happen: Adding a second input source (Russian, in my example) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order. Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) Screenshots are attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1890875/+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 1890875] [NEW] Keyboard won't switch its layout to the newly added second input source unless their order is rearranged
Public bug reported: What should happen: Adding a second input source (Russian, in my example) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order. Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) Screenshots are attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic input keyboard ** Attachment added: "You can see that Russian (ru) layout is set but the input itself hasn't switched from English" https://bugs.launchpad.net/bugs/1890875/+attachment/5399800/+files/firefox.png -- 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/1890875 Title: Keyboard won't switch its layout to the newly added second input source unless their order is rearranged Status in gnome-control-center package in Ubuntu: New Bug description: What should happen: Adding a second input source (Russian, in my example) should result in being able to switch to it and use it immediately. What happens now: It is not recognized until you rearrange its order. Steps to reproduce this bug: 1. Have English set as primary language. 2. Go to Settings > Region & Language > Input Sources and add Russian. 3. Russian layout is added to Input Sources and the indicator becomes visible in the Top Bar. 4. You can switch between languages with the assigned keyboard shortcut but the text input won't change. 5. Rearrange their order in Input Sources: make Russian primary, English secondary. 6. You can now enter text in Russian. 7. You can now put Russian back to being second in the list (so it does not cause problems at logic screen, opening up new browser window, etc.) Screenshots are attached. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 13:39:01 2020 InstallationDate: Installed on 2016-11-03 (1373 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2020-07-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1890875/+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 1732245] Re: Fullscreen game windows vertically offset after returning from Alt-Tab
I found a work-around: disabling animations in GNOME Tweaks solves the issue and the whole Top Bar (not a ghost of it) and the Dock are visible for a very short time until the window becomes fullscreen. I suggest to include an option to disable these animations when fullscreen windows are present because they also cause frame drops. As for upgrading I'm patiently waiting for the dot release. Fingers crossed tomorrow is the day. :) -- 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/1732245 Title: Fullscreen game windows vertically offset after returning from Alt-Tab Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: Impact == Using Alt-Tab to leave a fullscreen game and then return breaks the game by offsetting the display by the size of the GNOME Shell top bar (and the Ubuntu Dock if running). Test Case = 1. Log into the default Ubuntu session. (Make sure that Wayland is running by running this command. If you have output, you are running Wayland. env | grep -i wayland 2. Run a game full screen. I installed Steam and used Team Fortress 2 because it's free (but a very large download) 3. Press Alt-Tab to switch to another window and then press Alt-Tab to switch back to the game. The game should display and function normally. Workaround == Open the Activities Overview and click the game window instead of using Alt-Tab to switch back to the game. Other Info == This bug is split from LP: #1725649 where the problem was seen and fixed for the Xorg session. This bug is for the Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+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 1732245] Re: Fullscreen game windows vertically offset after returning from Alt-Tab
Thanks for the quick response! Another detail I want to add is that it only happens after invoking the switcher. I can control volume or screen brightness all good without any problems but as soon as I switch windows and go back to my game the top bar keeps appearing whenever the volume or screen brightness controls are accessed. The switcher is definitely the culprit here. It happens on X, it happens on Wayland. On X, the bar usually disappears as soon as the switching animation stops or volume and screen brightness control pop-ups fade away. On Wayland, the bug persists until I re-open the affected window through Activities, not the Switcher. GNOME Shell 3.28.4-0ubuntu18.04.3 Mutter 3.28.4-0ubuntu18.04.2 -- 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/1732245 Title: Fullscreen game windows vertically offset after returning from Alt-Tab Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: Impact == Using Alt-Tab to leave a fullscreen game and then return breaks the game by offsetting the display by the size of the GNOME Shell top bar (and the Ubuntu Dock if running). Test Case = 1. Log into the default Ubuntu session. (Make sure that Wayland is running by running this command. If you have output, you are running Wayland. env | grep -i wayland 2. Run a game full screen. I installed Steam and used Team Fortress 2 because it's free (but a very large download) 3. Press Alt-Tab to switch to another window and then press Alt-Tab to switch back to the game. The game should display and function normally. Workaround == Open the Activities Overview and click the game window instead of using Alt-Tab to switch back to the game. Other Info == This bug is split from LP: #1725649 where the problem was seen and fixed for the Xorg session. This bug is for the Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+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 1732245] Re: Fullscreen game windows vertically offset after returning from Alt-Tab
Hey, Daniel! You sent me here from #1890281 #1725649 is said to be fixed but the bug is still present on Ubuntu 18.04.4 running X. I've recently upgraded to Bionic and noticed this bug immediately as I often play games. Shall I file a new bug report? Thanks in advance. -- 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/1732245 Title: Fullscreen game windows vertically offset after returning from Alt-Tab Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: Impact == Using Alt-Tab to leave a fullscreen game and then return breaks the game by offsetting the display by the size of the GNOME Shell top bar (and the Ubuntu Dock if running). Test Case = 1. Log into the default Ubuntu session. (Make sure that Wayland is running by running this command. If you have output, you are running Wayland. env | grep -i wayland 2. Run a game full screen. I installed Steam and used Team Fortress 2 because it's free (but a very large download) 3. Press Alt-Tab to switch to another window and then press Alt-Tab to switch back to the game. The game should display and function normally. Workaround == Open the Activities Overview and click the game window instead of using Alt-Tab to switch back to the game. Other Info == This bug is split from LP: #1725649 where the problem was seen and fixed for the Xorg session. This bug is for the Wayland sessions. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+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 1890281] [NEW] Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit
Public bug reported: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit by the height of the Top Bar and the desktop background to show up. Controlling the audio volume or screen brightness, or using keyboard shortcuts should not bring up the GNOME desktop and misplace the window in fullscreen games. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 17:33:35 2020 DistUpgraded: 2020-07-24 11:33:50,776 DEBUG running apport_crash() DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:220d] InstallationDate: Installed on 2016-11-03 (1369 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=fff07cd8-771d-418e-a056-c094fe8e3a55 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2020-07-24 (11 days ago) dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 220D dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP14NotebookPC:pvr097512405F0610180:rvnHewlett-Packard:rn220D:rvr86.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 14 Notebook PC dmi.product.version: 097512405F0610180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jul 24 10:49:18 2020 xserver.configfile: default xserver.errors: Failed to load module "vesa" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 831 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1890281 Title: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit Status in xorg package in Ubuntu: New Bug description: Switching windows, regulating audio volume or screen brightness in fullscreen games causes the window to move down a bit by the height of the Top Bar and the desktop background to show up. Controlling the audio volume or screen brightness, or using keyboard shortcuts should not bring up the GNOME desktop and misplace the window in fullscreen games. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Aug 4 17:33:35 2020 DistUpgraded: 2020-07-24 11:33:50,776 DEBUG running apport_crash() DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller
[Desktop-packages] [Bug 1646547] Re: nvidia-367.57 with kernel 4.4.0-51-generic won't boot
There is a fix. Press and hold 'Shift' while booting. It should bring up the login screen. You won't need to do this every single time, just once after failing to boot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1646547 Title: nvidia-367.57 with kernel 4.4.0-51-generic won't boot Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Bug description: Pretty much identical to bug 1642400 and bug 1638990 except that this behavior also happens with the most recent Xenial kernel, 4.4.0-51-generic. If I boot into recovery mode on 4.4.0-51-generic, mount the filesystem as read/write, start networking, the resume normal boot, I can finally get into my window manager. But if I reboot and let GRUB handle boot normally, it doesn't even let me enter my encryption passphrase. Just sits at a blinking cursor. Switching back to nouveau works, but after reinstalling 367.57, the behavior returns and the aforementioned steps have to be followed. Ubuntu 4.4.0-51.72-generic 4.4.30 :~$ lsb_release -rd Description: Ubuntu 16.04.1 LTS Release: 16.04 :~$ apt-cache policy linux-image-4.4.0-51-generic linux-image-4.4.0-51-generic: Installed: 4.4.0-51.72 Candidate: 4.4.0-51.72 Version table: *** 4.4.0-51.72 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status I expect that I should be able to boot normally with nvidia drivers, without any special steps to boot. But instead, I just get a blinking cursor before I can even unlock my encrypted drive. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-51-generic 4.4.0-51.72 ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30 Uname: Linux 4.4.0-51-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lost 4789 F pulseaudio /dev/snd/controlC0: lost 4789 F pulseaudio /dev/snd/controlC2: lost 4789 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 1 10:48:04 2016 HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6 InstallationDate: Installed on 2016-11-01 (29 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 11361Q0 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-51-generic root=/dev/mapper/xubuntu--vg-root ro recovery nomodeset RelatedPackageVersions: linux-restricted-modules-4.4.0-51-generic N/A linux-backports-modules-4.4.0-51-generic N/A linux-firmware1.157.5 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2016 dmi.bios.vendor: LENOVO dmi.bios.version: A3KT57AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: 573921 dmi.chassis.type: 7 dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE: dmi.product.name: 11361Q0 dmi.product.version: ThinkStation C30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1646547/+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 1639599] [NEW] Huawei E173 won't be switched to 'USB Modem' mode (1436).
Public bug reported: Huawei E173 won't be switched automatically. The package is not consistent. The modem has successfully been switched the first time I plugged it in (as you can see here: https://paste.ubuntu.com/23437650/). Subsequent plug-ins of the modem won't result in a successful mode- switch (https://paste.ubuntu.com/23437624/). The only fix, which is inconsistent as well, is to completely remove the packages, reboot, reinstall them and plug the device back in. However, this is pretty inconvenient. USB mode-switch log: https://pastebin.ubuntu.com/23437487/ ** Affects: usb-modeswitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1639599 Title: Huawei E173 won't be switched to 'USB Modem' mode (1436). Status in usb-modeswitch package in Ubuntu: New Bug description: Huawei E173 won't be switched automatically. The package is not consistent. The modem has successfully been switched the first time I plugged it in (as you can see here: https://paste.ubuntu.com/23437650/). Subsequent plug-ins of the modem won't result in a successful mode-switch (https://paste.ubuntu.com/23437624/). The only fix, which is inconsistent as well, is to completely remove the packages, reboot, reinstall them and plug the device back in. However, this is pretty inconvenient. USB mode-switch log: https://pastebin.ubuntu.com/23437487/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1639599/+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
