[Desktop-packages] [Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
Hi Marco, I didn't get any error on an old but up-to-date installation of 22.04 with LightDM, but got a login error from gnome-session when using a fresh Ubuntu 22.04 daily-live ISO and installing Unity7 on top of it (with both gdm and lightdm). Apparently, it works after installing the old version of gnome-session and then going back to the latest version with both GDM and lightdm (and doesn't work on both GDM and lightdm without doing so). This might be why it works on old up-to-date installs of 22.04 but not on fresh installs (which have the latest version of gnome-session installed). -- 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/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version Status in gnome-session package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Unity7 seems to crash on 22.04 when logging in after installing Ubuntu (it works fine in the live session). I then tried installing the 21.10 gnome-session package on 22.04 and Unity7 then worked perfectly fine. Also, XDG_CURRENT_DESKTOP is set to GNOME instead of "Unity:7;Unity:ubuntu" with the Jammy version, which is really unexpected and might be causing these issues. seb128 and 3vin1o: Neither I nor Khurshid are sure about what has changed between the two packages, and I think this is a critical bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1969558] Re: Dragging one edge of a modal dialog moves the opposite edge
Thanks Daniel, this fixed the odd preference window behaviour. Glad to see it's a feature and not a bug. I would still question why we want this active by default though considering the lack of consistency with other windows and Xorg. -- 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/1969558 Title: Dragging one edge of a modal dialog moves the opposite edge Status in gnome-shell package in Ubuntu: Invalid Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+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 1969558] Re: Dragging one edge of a modal dialog moves the opposite edge
If you want different behaviour then you can run: gsettings set org.gnome.shell.overrides attach-modal-dialogs false gsettings set org.gnome.mutter attach-modal-dialogs false and log in again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1969558 Title: Dragging one edge of a modal dialog moves the opposite edge Status in gnome-shell package in Ubuntu: Invalid Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
verify #21, the result is good. The kernel log for reference.
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967274/+attachment/5581937/+files/kernel.log
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1969558] Re: Dragging one edge of a modal dialog moves the opposite edge
Yes, I updated the title as it appears that this behaviour applies to all Preferences/Settings dialogs. This behaviour looks extremely odd and is inconsistent with the resizing mechanism for other windows (and inconsistent with the same windows in Xorg). If I grab the bottom corner, I want to move the bottom corner, not the top. -- 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/1969558 Title: Dragging one edge of a modal dialog moves the opposite edge Status in gnome-shell package in Ubuntu: Invalid Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Yeah a kernel fix is more useful because you won't get Night Light or
colour profile support without a kernel fix.
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1969558] Re: Incorrect Window Resizing for Preference Dialogs
Oh preference dialogs of gnome-extensions-app, that's different. They are meant to remain perfectly centred so yes dragging the bottom edge will also move the top edge. ** Summary changed: - Incorrect Window Resizing for Preference Dialogs + Dragging one edge of a modal dialog moves the opposite edge ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- 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/1969558 Title: Dragging one edge of a modal dialog moves the opposite edge Status in gnome-shell package in Ubuntu: Invalid Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Thanks Timo, this series of patches seems fix this issue
https://www.spinics.net/lists/intel-gfx/msg284609.html
Here is the test kernel, I can't reproduce the issue with this kernel.
https://people.canonical.com/~acelan/bugs/lp1967274/
I'll submit SRU soon.
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1969709] Re: libreoffice font selection unusably slow
** Description changed: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to - perform individidual scrolling gestures to move through the list. + perform individidual scrolling gestures. The CPU jumps to 100% and the + whole system becomes unresponsive. I have tried deb, snap and even the packages offered on the site of the - LibreOffice project. They all manifest the same behaviour. I have had to - downgrade to 7.2, which appears to be unaffected. + LibreOffice project. They all manifest the same behaviour. The only + thing that works is disabling font previews. I have downgraded to 7.2 + for now, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice 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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1969709 Title: libreoffice font selection unusably slow Status in libreoffice package in Ubuntu: New Bug description: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to perform individidual scrolling gestures. The CPU jumps to 100% and the whole system becomes unresponsive. I have tried deb, snap and even the packages offered on the site of the LibreOffice project. They all manifest the same behaviour. The only thing that works is disabling font previews. I have downgraded to 7.2 for now, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969709/+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 1969558] Re: Incorrect Window Resizing for Preference Dialogs
** Summary changed: - Incorrect Window Resizing for Extension Settings + Incorrect Window Resizing for Preference Dialogs -- 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/1969558 Title: Incorrect Window Resizing for Preference Dialogs Status in gnome-shell package in Ubuntu: New Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+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 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
There may be no need if 42.1 is tagged in the next week or so. It's
scheduled for 23 April (roughly):
https://wiki.gnome.org/FortyTwo
I imagine we will SRU 42.1 quickly. Also I don't have any sponsorship
powers myself.
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1969709] [NEW] libreoffice font selection unusably slow
Public bug reported: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to perform individidual scrolling gestures to move through the list. I have tried deb, snap and even the packages offered on the site of the LibreOffice project. They all manifest the same behaviour. I have had to downgrade to 7.2, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Description changed: - Trying to scroll the font list from the menu bar of writer, I experience - an unacceptable degree of lagging. Just popping up the dropdown list - takes 7-10 seconds and the system takes the same amount of time to - respond to perform single scrolling gestures moving through the list. + Trying to scroll through the font list in the menu bar, I experience an + unacceptable degree of lagging. Just popping up the dropdown list takes + 7-10 seconds and the system takes the same amount of time to respond to + perform individidual scrolling gestures to move through the list. - I have tried deb, snap and even the packages as offered on the site of - the LibreOffice project. The all manifest the same behaviour. I have had - to downgrade to 7.2. + I have tried deb, snap and even the packages offered on the site of the + LibreOffice project. They all manifest the same behaviour. I have had to + downgrade to 7.2, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should - be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is using 2.13. + be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping + 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice 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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1969709 Title: libreoffice font selection unusably slow Status in libreoffice package in Ubuntu: New Bug description: Trying to scroll through the font list in the menu bar, I experience an unacceptable degree of lagging. Just popping up the dropdown list takes 7-10 seconds and the system takes the same amount of time to respond to perform individidual scrolling gestures to move through the list. I have tried deb, snap and even the packages offered on the site of the LibreOffice project. They all manifest the same behaviour. I have had to downgrade to 7.2, which appears to be unaffected. I have contacted the LibreOffice team and they tell me that this should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is shipping 2.13... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libreoffice-core 1:7.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 05:01:24 2022 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2022-03-27 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1967274] Re: Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
@vanvugt
Hello,
Will you help to SRU it for jammy?
Thanks,
--
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/1967274
Title:
Screen sometimes can't update on Intel Alder Lake GPUs [Failed to post
KMS update: CRTC property (GAMMA_LUT) not found]
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Triaged
Status in mutter package in Ubuntu:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1969707] Re: DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM).
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969707 Title: DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Status in OEM Priority Project: New Status in network-manager-openvpn package in Ubuntu: New Bug description: Try to enable vpn, but the vpn is not able to enable. The config file under /etc/NetworkManager input a deprecated option. Try to change cipher to data-cipher, the network can be enabled successfully. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 10:19:15 2022 InstallationDate: Installed on 2022-04-21 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969707/+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 1924859] Re: VMware not grabbing Alt+Tab input in Wayland sessions
** Tags added: jammy -- 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/1924859 Title: VMware not grabbing Alt+Tab input in Wayland sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: I am currently running VMware workstation pro 16.1. When pressing alt+tab to toggle the windows in the guest OS, the input is instead applied to the host OS and not the guest. When switching from Wayland to Xorg the problem is resolved. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Sat Apr 17 15:48:45 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0112] NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GM206 [GeForce GTX 960] [1462:3202] InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=739968f7-1aa4-47f1-8d68-55af0ffb428d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 07/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: Z77 OC Formula dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/11/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77OCFormula:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924859/+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 1969707] [NEW] DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM).
Public bug reported: Try to enable vpn, but the vpn is not able to enable. The config file under /etc/NetworkManager input a deprecated option. Try to change cipher to data-cipher, the network can be enabled successfully. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 10:19:15 2022 InstallationDate: Installed on 2022-04-21 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy oem-priority wayland-session ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969707 Title: DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Status in network-manager-openvpn package in Ubuntu: New Bug description: Try to enable vpn, but the vpn is not able to enable. The config file under /etc/NetworkManager input a deprecated option. Try to change cipher to data-cipher, the network can be enabled successfully. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 10:19:15 2022 InstallationDate: Installed on 2022-04-21 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1969707/+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 1924859] Re: VMware not grabbing Alt+Tab input in Wayland sessions
Reproduced in jammy. -- 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/1924859 Title: VMware not grabbing Alt+Tab input in Wayland sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: I am currently running VMware workstation pro 16.1. When pressing alt+tab to toggle the windows in the guest OS, the input is instead applied to the host OS and not the guest. When switching from Wayland to Xorg the problem is resolved. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Sat Apr 17 15:48:45 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0112] NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GM206 [GeForce GTX 960] [1462:3202] InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=739968f7-1aa4-47f1-8d68-55af0ffb428d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 07/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: Z77 OC Formula dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/11/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77OCFormula:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924859/+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 1969633] Re: Bluetooth not connecting
Thanks for the bug report. Your kernel log seems to show Bluetooth commands repeatedly failing to transmit: [337184.522407] Bluetooth: hci0: command 0x0406 tx timeout [337887.553831] Bluetooth: hci0: command 0x0c1a tx timeout [337889.565670] Bluetooth: hci0: command 0x0c3a tx timeout [337891.581728] Bluetooth: hci0: command 0x0c1a tx timeout [337913.213192] Bluetooth: hci0: command 0x1405 tx timeout [337915.229228] Bluetooth: hci0: command 0x1403 tx timeout So that's either a kernel bug or a hardware fault. BlueZ is not really relevant here. ** Summary changed: - Bluetooth not connecting + Continuous Bluetooth timeouts [Broadcom BCM20702A] ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Package changed: linux (Ubuntu) => linux-hwe-5.13 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1969633 Title: Continuous Bluetooth timeouts [Broadcom BCM20702A] Status in linux-hwe-5.13 package in Ubuntu: New Bug description: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1969633/+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 1969651] Re: Dock auto-hides too quickly when interacting with an app's right-click menu
*** This bug is a duplicate of bug 1967121 *** https://bugs.launchpad.net/bugs/1967121 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1967121, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- ubuntu-dock (Ubuntu) ** This bug has been marked a duplicate of bug 1967121 Contextual menus are glitching when auto-hide is enabled (right click + windows selector) -- 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/1969651 Title: Dock auto-hides too quickly when interacting with an app's right-click menu Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Whenever I try to select a different window from the dock (or add to favourites/any other option in that menu), as soon as my mouse leaves the dock for that menu, the dock hides, which makes the menu drop down. This is very frustrating because at best I have to try again, and at worst I have to undo whatever wrong action the menu drop made me click. It's worse when the menu is not on my primary display, as on top of dropping down, it gets sent to the primary display. This is quite a frustrating bug that has been present the whole time I've been using the 22.04 beta. My gnome-shell-extension-ubuntu-dock version is 72-ubuntu5, and I am using Wayland. My dock settings are set to show on all displays, at the bottom. Although the behaviour is wonky when set to display on the left too. Let me know if there is any more information you would like me to provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1969651/+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 1969688] Re: possible hardware incompatibility
What package is failing to install? What is the problem exactly? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1969688 Title: possible hardware incompatibility Status in Ubuntu: Incomplete Bug description: Update repeatedly fails to install some package. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Apr 20 17:16:16 2022 DistUpgraded: 2020-10-07 14:17:40,302 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3525] InstallationDate: Installed on 2015-03-16 (2592 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic root=UUID=f382b311-5a9b-4768-bb28-40f911cc2040 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-07 (560 days ago) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A58M-HD2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd03/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A58M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Aug 21 10:57:10 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputComposite USB PS2 Converter USB to PS2 Adaptor v1.09 KEYBOARD, id 9 inputComposite USB PS2 Converter USB to PS2 Adaptor v1.09 KEYBOARD, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1969688/+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 1969558] Re: Incorrect Window Resizing for Extension Settings
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1969558 Title: Incorrect Window Resizing for Extension Settings Status in gnome-shell package in Ubuntu: New Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+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 1969602] Re: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1969602 Title: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 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/1969602/+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 1964442] Re: Key repeats forever if a shell popover steals focus during a keypress
** Tags added: fixed-in-42.1 fixed-upstream -- 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/1964442 Title: Key repeats forever if a shell popover steals focus during a keypress Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Released Bug description: This is a regression not seen until this week (not seen until March 4 at least). Calling debsign from a terminal pops up the window to enter the key, but the terminal is sent continuous keys and the terminal scrolls down with empty input lines. You can still sign the file, however you end up with an empty scroll buffer if the signing takes too long time. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1964442/+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 1969637] Re: lookup table appears bottom left of application
Yes, it's a locale issue somehow. Good catch! When I first tested I didn't even have the Japanese locale generated. But after doing: sudo locale-gen ja_JP.UTF-8 sudo update-locale LC_CTYPE=ja_JP.UTF-8 I can reproduce the issue in a Xorg session. But it's not specific to ja_JP.UTF-8 (it hasn't been changed since 2019). I see the issue also if I set LC_CTYPE=zh_CN.UTF-8. And it does not only affect ibus-mozc. The candidate window is misplaced also when I use ibus-libpinyin in a Xorg session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application Status in ibus: Fix Released Status in im-config package in Ubuntu: New Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+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 1969637] Re: lookup table appears bottom left of application
Is it a locale issue? When my environment changed to C.UTF-8 locale, worked great for me. > Well, your proposed fix is not possible to implement. OK, I will propose an another fix. ** Attachment added: "Screenshot from 2022-04-21 08-12-48.png" https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1969637/+attachment/5581909/+files/Screenshot%20from%202022-04-21%2008-12-48.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application Status in ibus: Fix Released Status in im-config package in Ubuntu: New Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+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 27867]
Thank you for useful information. That can make me use the information to work in order to continue working effectively. [ok](https://okcasino.vip/) Thank you. -- 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/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+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 1969593] Re: rules to prevent non-root users from rebooting not taken into account
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1969593 Title: rules to prevent non-root users from rebooting not taken into account Status in policykit-1 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: On fresh Ubuntu Jammy installation, I add a "/etc/polkit-1/localauthority/90-mandatory.d/restriction.pkla" file with the following contents : [Disable power-off] Identity=unix-user:* Action=org.freedesktop.login1.power-off ResultActive=no ResultInactive=no ResultAny=no [Disable power-off when others are logged in] Identity=unix-user:* Action=org.freedesktop.login1.power-off-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot] Identity=unix-user:* Action=org.freedesktop.login1.reboot ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot_when_others_are_logged_in] Identity=unix-user:* Action=org.freedesktop.login1.reboot-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no It must prevent non-root users from shutdowning and rebooting the system. But it only prevent shutdowning. Rebooting is still possible for a non-root user. We can see it using pkcheck command (as a non-root user) : $ pkcheck --action-id org.freedesktop.login1.power-off --process $PPID ; echo $? Not authorized. 1 $ pkcheck --action-id org.freedesktop.login1.reboot --process $PPID ; echo $? 0 As this problem can lead to unexpected reboot on multi-users systems (a disponibilty concern), I checked the "This bug is a security vulnerability" box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: policykit-1 0.105-33 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 10:53:27 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1969593/+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 1969688] [NEW] possible hardware incompatibility
Public bug reported: Update repeatedly fails to install some package. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Apr 20 17:16:16 2022 DistUpgraded: 2020-10-07 14:17:40,302 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3525] InstallationDate: Installed on 2015-03-16 (2592 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic root=UUID=f382b311-5a9b-4768-bb28-40f911cc2040 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-07 (560 days ago) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A58M-HD2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd03/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A58M-HD2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Aug 21 10:57:10 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputComposite USB PS2 Converter USB to PS2 Adaptor v1.09 KEYBOARD, id 9 inputComposite USB PS2 Converter USB to PS2 Adaptor v1.09 KEYBOARD, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1969688 Title: possible hardware incompatibility Status in xorg package in Ubuntu: New Bug description: Update repeatedly fails to install some package. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Apr 20 17:16:16 2022 DistUpgraded: 2020-10-07 14:17:40,302 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GT218 [GeForce 210] [1458:3525] InstallationDate: Installed on 2015-03-16 (2592 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic root=UUID=f382b311-5a9b-4768-bb28-40f911cc2040 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-07 (560 days ago) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American
[Desktop-packages] [Bug 1969593] Re: rules to prevent non-root users from rebooting not taken into account
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1969593 Title: rules to prevent non-root users from rebooting not taken into account Status in policykit-1 package in Ubuntu: New Bug description: On fresh Ubuntu Jammy installation, I add a "/etc/polkit-1/localauthority/90-mandatory.d/restriction.pkla" file with the following contents : [Disable power-off] Identity=unix-user:* Action=org.freedesktop.login1.power-off ResultActive=no ResultInactive=no ResultAny=no [Disable power-off when others are logged in] Identity=unix-user:* Action=org.freedesktop.login1.power-off-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot] Identity=unix-user:* Action=org.freedesktop.login1.reboot ResultActive=no ResultInactive=no ResultAny=no [Disable_reboot_when_others_are_logged_in] Identity=unix-user:* Action=org.freedesktop.login1.reboot-multiple-sessions ResultActive=no ResultInactive=no ResultAny=no It must prevent non-root users from shutdowning and rebooting the system. But it only prevent shutdowning. Rebooting is still possible for a non-root user. We can see it using pkcheck command (as a non-root user) : $ pkcheck --action-id org.freedesktop.login1.power-off --process $PPID ; echo $? Not authorized. 1 $ pkcheck --action-id org.freedesktop.login1.reboot --process $PPID ; echo $? 0 As this problem can lead to unexpected reboot on multi-users systems (a disponibilty concern), I checked the "This bug is a security vulnerability" box. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: policykit-1 0.105-33 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 10:53:27 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1969593/+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 1969637] Re: lookup table appears bottom left of application
Thanks for your report. Hmm.. First I thought of bug #1966552, but that one was only about some specific non-standard applications. It was not about e.g. gedit. And I can't reproduce it. For me, the candidate window shows up close to the cursor as expected. (Tried with ibus-mozc; assuming that's what you used too.) Not sure what else to say at this stage.. Well, your proposed fix is not possible to implement. It would result in GTK_IM_MODULE=ibus being set for all GNOME users in both wayland and xorg sessions, and as regards wayland sessions it would result in adverse side effects. For instance it would break the Screen Keyboard feature. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application Status in ibus: Fix Released Status in im-config package in Ubuntu: New Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+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 1968425] Re: Workspace switching interruptible with trackpad overview gesture
I think it's similar to a degree, the other bug starts in the overview and similarly attempting to interrupt the transition, I can confirm the behaviour of seeing "a part of the previous workspace for a second or two" on GNOME 42. My issue is slightly different as it starts from the desktop and interrupts the transition by going to the overview (as demonstrated in the screen recording). I think both bugs speak to additional polish needed for the workspace transitions namely preventing an in progress transition from being interrupted regardless of being on the desktop or the overview. Fixing this may help to improve some of the unintended transitions I see when using rapid trackpad gestures, and the transitions sometimes feeling like they go somewhere different than intended (3 swipe down to desktop sometimes lands me on an adjacent desktop, but don't know how to reliably reproduce hence haven't created a bug for this). -- 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/1968425 Title: Workspace switching interruptible with trackpad overview gesture Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 gnome-shell: Installed: 42.0-1ubuntu1 Candidate: 42.0-1ubuntu1 Version table: *** 42.0-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status What happened: On the desktop when using a trackpad 3 finger swipe to switch to an adjacent workspace, if a 3 finger swipe up gesture to go to the activities overview is invoked during the transition animation it will abruptly cancel the transition and go to the overview at the original workspace. The abrupt cancellation can make the workspace/overview experience feel a bit jerky. What I expected: The transition to be non interruptible with the activities overview gesture only being able to used when the transition has concluded. This is the behaviour I observe when using workspaces on macOS. screen recording demonstrating this with libinput debug-gui to show trackpad gestures is attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 9 15:08:52 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 42.0-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/1968425/+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 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
Ah, Rudra: All my tests have been done *with lightDM*, not gdm. I assume there's some bit lightdm is not doing, but in my test environment it was perfectly able to start the session as underlined in the comments below. -- 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/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version Status in gnome-session package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Unity7 seems to crash on 22.04 when logging in after installing Ubuntu (it works fine in the live session). I then tried installing the 21.10 gnome-session package on 22.04 and Unity7 then worked perfectly fine. Also, XDG_CURRENT_DESKTOP is set to GNOME instead of "Unity:7;Unity:ubuntu" with the Jammy version, which is really unexpected and might be causing these issues. seb128 and 3vin1o: Neither I nor Khurshid are sure about what has changed between the two packages, and I think this is a critical bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1969619] Re: RDP Sharing appears on by default in jammy
Łukasz, Yes, just opening the Sharing panel with gnome-control-center 1:41.4-1ubuntu12 is enough to attempt to start the RDP service. systemctl --user status gnome-remote-desktop reports this error: RDP TLS certificate and key not configured properly I didn't check open ports but it makes sense that it would open the RDP port even though the RDP service isn't completely working. ** Description changed: - Summary - === - 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. - 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. + Impact + == + 1. It looks like RDP Sharing is turned on but it is not. + 2. To actually turn on RDP Sharing, you would need to turn it off then turn it on. - On further investigation, it is not actually on. + This bugfix fixes it so that it correctly shown as off by default and + turning it on works. - More details + Test Case + = + 0. Start with a clean Ubuntu 22.04 install. + Or you can create a new user and log in as the new user. + 1. Open the Settings app. + 2. In the left sidebar, click Sharing. The switch at the top of the page needs to be off. + 3. Turn the switch on. Then click Remote Desktop and turn it on. + 4. Close the Settings app. + 5. Open the Settings app and verify that Sharing is on and Remote Desktop is on. + 6. Close the Settings app. + 7. From a terminal, run + systemctl --user status gnome-remote-sharing.service + + It should show the service as active (running) and + a line at the bottom should say RDP server started + 8. Then run + systemctl --user stop gnome-remote-sharing.service + 9. Open the Settings app. It should show that Remote Desktop sharing is off. + 10. Turn on Sharing and turn on Remote Desktop sharing. + 11. Run + systemctl --user status gnome-remote-sharing.service + + It should show the service as active (running) and + a line at the bottom should say RDP server started + + What Could Go Wrong + === + This is a minimal fix proposed upstream. + The original implementation was insufficient. + The bugfix will allow Remote Desktop to be turned on and work correctly from the beginning. + + More Details - This issue affects both the live session and the initial install. (Probably would show up for any new user.) - - 1. Before opening the Settings app, the gnome-remote-desktop service is - running. I think this is expected. - - $ systemctl status --user gnome-remote-desktop.service - \u25cf gnome-remote-desktop.service - GNOME Remote Desktop - Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> - Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago - Main PID: 1611 (gnome-remote-de) - Tasks: 4 (limit: 4603) - Memory: 13.8M - CPU: 66ms - CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> - \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon - - Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... - Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) - Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. - - Also, the RDP enable gsettings key is turned off. - - $ gsettings get org.gnome.desktop.remote-desktop.rdp enable - false - - 2. When I open the Sharing page, the gsettings key turns to true - - and systemctl shows me an error where it tried to enable RDP: - Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly - - 3. So then I open Remote Desktop Sharing and turn it off then on and - then systemctl shows me that is working correctly. - - Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... - Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> - Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. - Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started - - Note in particular the final line: "RDP server started". That tells us - whether RDP is running or not. There would be a similar line for VNC. - This line didn't show in the initial state in step 1. - - What should happen - == - Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. - - There is no gsettings for the Sharing master on/off switch (in the - headerbar). It shows as On if any of the services are On. None of the - services should be On by default so this should show Off by default. - - A Bug Trigger - = - It looks like this bug was triggered by - https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 - - I have reported this issue to GNOME. That patch fixes an important issue - so maybe we need to keep that patch but fix the logic in gnome-control- - center. + To simplify this bug report, I
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "apparmor_3.0.3-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581882/+files/apparmor_3.0.3-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
@Sebastien, yes, just did. Thank you! I also attached the debdiffs for evince and apparmor for bionic, focal, impish and jammy. They were also uploaded into the Security Proposed PPA: https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages?field.name_filter=apparmor https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages?field.name_filter=evince -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "apparmor_2.12-4ubuntu5.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581885/+files/apparmor_2.12-4ubuntu5.2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "apparmor_2.13.3-7ubuntu5.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581884/+files/apparmor_2.13.3-7ubuntu5.2.debdiff ** Patch removed: "apparmor_3.0.3-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581883/+files/apparmor_3.0.3-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "apparmor_3.0.3-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581883/+files/apparmor_3.0.3-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "evince_40.4-2ubuntu0.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581878/+files/evince_40.4-2ubuntu0.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "apparmor_3.0.4-2ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581881/+files/apparmor_3.0.4-2ubuntu3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "evince_3.28.4-0ubuntu1.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581880/+files/evince_3.28.4-0ubuntu1.3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "evince_3.36.10-0ubuntu1.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581879/+files/evince_3.36.10-0ubuntu1.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1969314] Re: xdg-user-dirs-gtk-update not display panel
Hi, First I install Japanese environment from jammy-desktop-amd64.iso 2022-04-16 and 2022-04-19. and I want to change home directory name from Japanese to English to use command LANG=C xdg-user-dirs-gtk-update but not success Second I install English environment from jammy-desktop-amd64.iso 2022-04-19. and I added Japanese environment. Reboot system, panel displayed that do you want to use home directory Japanese or English, it is same LANG=C xdg-user-dirs-gtk-update command. and it work fine. however I install only one time, something may have failed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1969314 Title: xdg-user-dirs-gtk-update not display panel Status in xdg-user-dirs-gtk package in Ubuntu: Incomplete Bug description: Hi, I installed jammy-desktop-amd64.iso 2022-04-16 version by selecting Japanese. ubuntu-20.04, after installing the English version, I added a Japanese environment, but it has easier. However, the setting panel does not appear even if I execute the command to change the Japanese directory name of the HOME directory. LANG=C xdg-user-dirs-gtk-update As for the execution result, both Japanese and English direcotres remained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs-gtk/+bug/1969314/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Patch added: "evince_42.1-3ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1794064/+attachment/5581877/+files/evince_42.1-3ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
Also systemd units seems green: ● ubuntu-vmware State: running Jobs: 0 queued Failed: 0 units Since: Wed 2022-04-20 20:28:39 CEST; 40min ago CGroup: /user.slice/user-1001.slice/user@1001.service ├─session.slice │ ├─xdg-document-portal.service │ │ ├─50709 /usr/libexec/xdg-document-portal │ │ └─50721 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /run/user/1001/doc │ ├─xdg-desktop-portal.service │ │ ├─50701 /usr/libexec/xdg-desktop-portal │ │ ├─50804 sh -c /usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings org.gnome.system.proxy org.gnome.system.proxy.http org.gnome.system.proxy.https org.gnome.system.proxy.ftp org.gnome.system.proxy.socks │ │ └─50805 /usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings org.gnome.system.proxy org.gnome.system.proxy.http org.gnome.system.proxy.https org.gnome.system.proxy.ftp org.gnome.system.proxy.socks │ ├─pipewire-media-session.service │ │ └─34144 /usr/bin/pipewire-media-session │ ├─pulseaudio.service │ │ └─51099 /usr/bin/pulseaudio --daemonize=no --log-target=journal │ └─pipewire.service │ └─34143 /usr/bin/pipewire ├─app.slice │ ├─app-gnome-nemo\x2dunity\x2dautostart-51480.scope │ │ └─51480 nemo-desktop │ ├─indicator-datetime.service │ │ └─51025 /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service │ ├─app-gnome-geoclue\x2ddemo\x2dagent-34917.scope │ │ └─34917 /usr/libexec/geoclue-2.0/demos/agent │ ├─gvfs-goa-volume-monitor.service │ │ └─51650 /usr/libexec/gvfs-goa-volume-monitor │ ├─app-gnome-zeitgeist\x2ddatahub-51568.scope │ │ └─51568 zeitgeist-datahub │ ├─indicator-printers.service │ │ └─51034 /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service │ ├─xdg-permission-store.service │ │ └─50713 /usr/libexec/xdg-permission-store │ ├─indicator-keyboard.service │ │ └─51027 /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service --use-gtk │ ├─app-gnome-gnome\x2dinitial\x2dsetup\x2dfirst\x2dlogin-51376.scope │ │ ├─51376 /usr/libexec/gnome-initial-setup --existing-user │ │ ├─51824 sh -c /usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings org.gnome.system.proxy org.gnome.system.proxy.http org.gnome.system.proxy.https org.gnome.system.proxy.ftp org.gnome.system.proxy.socks │ │ └─51825 /usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings org.gnome.system.proxy org.gnome.system.proxy.http org.gnome.system.proxy.https org.gnome.system.proxy.ftp org.gnome.system.proxy.socks │ ├─zeitgeist.service │ │ └─51649 /usr/bin/zeitgeist-daemon │ ├─app-gnome-nm\x2dapplet-51354.scope │ │ └─51354 nm-applet │ ├─unity7.service │ │ └─51244 /usr/bin/compiz │ ├─app-gnome-caffeine-51365.scope │ │ └─51365 /usr/bin/python3 /usr/bin/caffeine │ ├─indicator-bluetooth.service │ │ └─51022 /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service │ ├─unity-panel-service.service │ │ └─51258 /usr/lib/x86_64-linux-gnu/unity/unity-panel-service │ ├─app-gnome-gnome\x2dsoftware\x2dservice-51331.scope │ │ ├─51331 /usr/bin/gnome-software --gapplication-service │ │ ├─51439 sh -c /usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings org.gnome.system.proxy org.gnome.system.proxy.http org.gnome.system.proxy.https org.gnome.system.proxy.ftp org.gnome.system.proxy.socks │ │ └─51440 /usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings org.gnome.system.proxy org.gnome.system.proxy.http org.gnome.system.proxy.https org.gnome.system.proxy.ftp org.gnome.system.proxy.socks │ ├─evolution-calendar-factory.service │ │ └─51130 /usr/libexec/evolution-calendar-factory │ ├─app-gnome-org.gnome.Evolution\x2dalarm\x2dnotify-51337.scope │ │ └─51337 /usr/libexec/evolution-data-server/evolution-alarm-notify │ ├─app-gnome-update\x2dnotifier-52025.scope │ │ └─52025 update-notifier │ ├─app-gnome-unity\x2dfallback\x2dmount\x2dhelper-51328.scope │ │ └─51328 /usr/lib/unity-settings-daemon/unity-fallback-mount-helper │ ├─app-gnome-polkit\x2dgnome\x2dauthentication\x2dagent\x2d1-51375.scope │ │ └─51375 /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 │ ├─app-gnome-tracker\x2dminer\x2dfs\x2d3-51380.scope │ │ └─51380 /usr/libexec/tracker-miner-fs-3 │ ├─xdg-desktop-portal-gnome.service │ │ └─50726 /usr/libexec/xdg-desktop-portal-gnome │
[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Description changed: - This is related to bug #1792648. After fixing that one (see discussion - at https://salsa.debian.org/gnome-team/evince/merge_requests/1), - clicking a hyperlink in a PDF opens it correctly if the default browser - is a well-known application (such as /usr/bin/firefox), but it fails to - do so if the default browser is a snap (e.g. the chromium snap). + [Impact] - This is not a recent regression, it's not working on bionic either. + * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. + * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. - ProblemType: Bug - DistroRelease: Ubuntu 18.10 - Package: evince 3.30.0-2 - ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 - Uname: Linux 4.18.0-7-generic x86_64 - NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair - ApportVersion: 2.20.10-0ubuntu11 - Architecture: amd64 - CurrentDesktop: ubuntu:GNOME - Date: Mon Sep 24 12:28:06 2018 - EcryptfsInUse: Yes - InstallationDate: Installed on 2016-07-02 (813 days ago) - InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) - SourcePackage: evince - UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) - modified.conffile..etc.apparmor.d.abstractions.evince: [modified] - mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 + [Test Plan] + + * Make sure the default browser is provided through the snap store. + * Open a PDF that contains a hyperlink using evince and click on the URL. + * The browser should open the requested URL. + + [Where problems could occur] + + * If the browser or snap core update to have new requirements for + opening a browser, then the current policy could become obsolete and + will need to be updated again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1969619] Re: RDP Sharing appears on by default in jammy
** Changed in: gnome-control-center (Ubuntu Jammy) Status: Triaged => In Progress -- 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/1969619 Title: RDP Sharing appears on by default in jammy Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Jammy: In Progress Bug description: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Also, the RDP enable gsettings key is turned off. $ gsettings get org.gnome.desktop.remote-desktop.rdp enable false 2. When I open the Sharing page, the gsettings key turns to true and systemctl shows me an error where it tried to enable RDP: Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly 3. So then I open Remote Desktop Sharing and turn it off then on and then systemctl shows me that is working correctly. Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started Note in particular the final line: "RDP server started". That tells us whether RDP is running or not. There would be a similar line for VNC. This line didn't show in the initial state in step 1. What should happen == Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. There is no gsettings for the Sharing master on/off switch (in the headerbar). It shows as On if any of the services are On. None of the services should be On by default so this should show Off by default. A Bug Trigger = It looks like this bug was triggered by https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 I have reported this issue to GNOME. That patch fixes an important issue so maybe we need to keep that patch but fix the logic in gnome- control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Georgia Garcia (georgiag) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
I've tested current Jammy in a VM (old one, but with a barely used user) and it seems to work properly: https://imgur.com/19SdylW.png Can you provide further logs of the error you're getting? -- 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/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version Status in gnome-session package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Unity7 seems to crash on 22.04 when logging in after installing Ubuntu (it works fine in the live session). I then tried installing the 21.10 gnome-session package on 22.04 and Unity7 then worked perfectly fine. Also, XDG_CURRENT_DESKTOP is set to GNOME instead of "Unity:7;Unity:ubuntu" with the Jammy version, which is really unexpected and might be causing these issues. seb128 and 3vin1o: Neither I nor Khurshid are sure about what has changed between the two packages, and I think this is a critical bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1965439] Re: software-properties-qt can no longer launch when called by pkexec
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1965439 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: software-properties-qt can no longer launch when called by pkexec Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Confirmed Status in software-properties source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1965439/+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 1966905] Re: Valgrind memory errors in gnome-shell 42 from accountsservice
I think this is triggered by valgrind because it leads to slowdowns, but the bug is indeed there. We can handle it in a later upload I think, but due to gslice and the randomness of these memory errors, I wouldn't be shocked if this is actually presenting right now in the wild with a different stack trace. -- 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/1966905 Title: Valgrind memory errors in gnome-shell 42 from accountsservice Status in accountsservice: Unknown Status in accountsservice package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in
[Desktop-packages] [Bug 1969651] [NEW] Dock auto-hides too quickly when interacting with an app's right-click menu
Public bug reported: Whenever I try to select a different window from the dock (or add to favourites/any other option in that menu), as soon as my mouse leaves the dock for that menu, the dock hides, which makes the menu drop down. This is very frustrating because at best I have to try again, and at worst I have to undo whatever wrong action the menu drop made me click. It's worse when the menu is not on my primary display, as on top of dropping down, it gets sent to the primary display. This is quite a frustrating bug that has been present the whole time I've been using the 22.04 beta. My gnome-shell-extension-ubuntu-dock version is 72-ubuntu5, and I am using Wayland. My dock settings are set to show on all displays, at the bottom. Although the behaviour is wonky when set to display on the left too. Let me know if there is any more information you would like me to provide. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: Whenever I try to select a different window from the dock (or add to favourites/any other option in that menu), as soon as my mouse leaves the dock for that menu, the dock hides, which makes the menu drop down. This is very frustrating because at best I have to try again, and at worst I have to undo whatever wrong action the menu drop made me click. It's worse when the menu is not on my primary display, as on top of dropping down, it gets sent to the primary display. This is quite a frustrating bug that has been present the whole time I've been using the 22.04 beta. My gnome-shell-extension-ubuntu-dock version is 72-ubuntu5, and I am using Wayland. + My dock settings are set to show on all displays, at the bottom. + Although the behaviour is wonky when set to display on the left too. + Let me know if there is any more information you would like me to provide. -- 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/1969651 Title: Dock auto-hides too quickly when interacting with an app's right-click menu Status in gnome-shell package in Ubuntu: New Bug description: Whenever I try to select a different window from the dock (or add to favourites/any other option in that menu), as soon as my mouse leaves the dock for that menu, the dock hides, which makes the menu drop down. This is very frustrating because at best I have to try again, and at worst I have to undo whatever wrong action the menu drop made me click. It's worse when the menu is not on my primary display, as on top of dropping down, it gets sent to the primary display. This is quite a frustrating bug that has been present the whole time I've been using the 22.04 beta. My gnome-shell-extension-ubuntu-dock version is 72-ubuntu5, and I am using Wayland. My dock settings are set to show on all displays, at the bottom. Although the behaviour is wonky when set to display on the left too. Let me know if there is any more information you would like me to provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969651/+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 1969619] Re: RDP Sharing appears on by default in jammy
I think this is a bit more nefarious. On an installed system, all you have to do to have port 3389/tcp suddenly open is to *visit* the "share" tab in the settings. No need to change a thing, just visit it, then close the window. Boom, you have rdp desktop sharing running. At least it's a random password (I think: it's not the local account password). -- 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/1969619 Title: RDP Sharing appears on by default in jammy Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center source package in Jammy: Triaged Bug description: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Also, the RDP enable gsettings key is turned off. $ gsettings get org.gnome.desktop.remote-desktop.rdp enable false 2. When I open the Sharing page, the gsettings key turns to true and systemctl shows me an error where it tried to enable RDP: Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly 3. So then I open Remote Desktop Sharing and turn it off then on and then systemctl shows me that is working correctly. Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started Note in particular the final line: "RDP server started". That tells us whether RDP is running or not. There would be a similar line for VNC. This line didn't show in the initial state in step 1. What should happen == Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. There is no gsettings for the Sharing master on/off switch (in the headerbar). It shows as On if any of the services are On. None of the services should be On by default so this should show Off by default. A Bug Trigger = It looks like this bug was triggered by https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 I have reported this issue to GNOME. That patch fixes an important issue so maybe we need to keep that patch but fix the logic in gnome- control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+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 1965439] Re: software-properties-qt can no longer launch when called by pkexec
software-properties-qt simply does not launch when run from the live session except when using the workaround mentioned by Paul above in comment 6 or when run by the Driver Manager link in System Settings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: software-properties-qt can no longer launch when called by pkexec Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Confirmed Status in software-properties source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1965439/+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 1969266] Re: application windows frozen after screen blanking
The bug appears to be a theming issue. I have not seen it since I replaced the third party theme I was using with the default. -- 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/1969266 Title: application windows frozen after screen blanking Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I want to use my computer after the screen has blanked, I often (about half of the time) find that the open applications are frozen. I can bring them back to life by restarting X or by cycling through the windows (ALT + TAB). Not a major bug certainly annoying as it is happening time and again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 09:53:51 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-27 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969266/+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 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
I tried using GDM3 as suggested by Khurshid, and it works perfectly fine with GDM3 and the latest version of gnome-session. Guess I'll release Ubuntu Unity 22.04 with GDM instead of lightdm since it's too late to release an update to fix this for lightdm users before the release. -- 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/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version Status in gnome-session package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Unity7 seems to crash on 22.04 when logging in after installing Ubuntu (it works fine in the live session). I then tried installing the 21.10 gnome-session package on 22.04 and Unity7 then worked perfectly fine. Also, XDG_CURRENT_DESKTOP is set to GNOME instead of "Unity:7;Unity:ubuntu" with the Jammy version, which is really unexpected and might be causing these issues. seb128 and 3vin1o: Neither I nor Khurshid are sure about what has changed between the two packages, and I think this is a critical bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1969632] Re: demote ntfs-3g
** Description changed: demote ntfs-3g Kernel now ships ntfs3 kernel module which is preferred over fuse/ntfs-3g way of mounting ntfs3 filesystems. At the moment we do ship ntfs-3g in standard, live, desktop, server. udisks2 still recommends ntfs-3g. ubiquity uses ntfsresize binary shipped by ntfs-3g. curtin installs and uses ntfs-3g as well, still it seems. but there is still a lot of useful ntfs-3g tooling in the ntfs-3g package. For example, maybe we should drop the ntfs-3g initramfs hooks and drop mount.ntfs-3g utilities, in favor of using ntfs3 kernel module. But otherwise keep all other ntfs-3g package utils in place? + + or forexample maybe we should drop fuse portions of ntfs-3g, and keep + tooling + mounting using ntfs3 kernel module only. -- 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/1969632 Title: demote ntfs-3g Status in curtin: New Status in udisks2 package in Ubuntu: New Bug description: demote ntfs-3g Kernel now ships ntfs3 kernel module which is preferred over fuse/ntfs-3g way of mounting ntfs3 filesystems. At the moment we do ship ntfs-3g in standard, live, desktop, server. udisks2 still recommends ntfs-3g. ubiquity uses ntfsresize binary shipped by ntfs-3g. curtin installs and uses ntfs-3g as well, still it seems. but there is still a lot of useful ntfs-3g tooling in the ntfs-3g package. For example, maybe we should drop the ntfs-3g initramfs hooks and drop mount.ntfs-3g utilities, in favor of using ntfs3 kernel module. But otherwise keep all other ntfs-3g package utils in place? or forexample maybe we should drop fuse portions of ntfs-3g, and keep tooling + mounting using ntfs3 kernel module only. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1969632/+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 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04
** Package changed: ubuntu-release-upgrader (Ubuntu) => gnome-shell (Ubuntu) -- 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/1968887 Title: Save As Dialog Box does not get focus in Ubuntu 22.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: When using a browser to right click a file and save as, the save as window does not get focus, which means you can't just type the name of the file you want, you have to force focus onto the window to use it by clicking it. This defeats the entire purpose of 2 built in features, 1 being the pre-selected original file name (since you can't rename until you re- aquire focus for that window, thereby undoing the pre-selection programmed in) and 2, the ability to quickly save the file with a keystroke. A side note to this, ubuntu-bug should have an option to report bugs with other WITHOUT having to specify a package. This is a bug in ubuntu-bug. Not a feature. Because we don't always know what package(s) are involved. This needs to be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 13 07:55:24 2022 InstallationDate: Installed on 2022-03-31 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade 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/1968887/+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 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
@adrian-wilkins Unity always use lightdm. Will try using gdm. Yes. The current_desktop_name is being set from data/unity.desktop.in.in file. Please look at the patch in debian/patches/ubuntu/ubuntu-session.patch. As for changes between impish and jammy, It seems now the object path has changed in gsm-manager.c ? From org.gnome.Shell to org.gnome.Shell.desktop? Though not sure that would affect this. Here is the changelog of 41.3-1ubuntu1. https://launchpad.net/ubuntu/+source/gnome-session/41.3-1ubuntu1 -- 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/1969357 Title: Unity7 crashes on Jammy with 22.04's gnome-session version Status in gnome-session package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Unity7 seems to crash on 22.04 when logging in after installing Ubuntu (it works fine in the live session). I then tried installing the 21.10 gnome-session package on 22.04 and Unity7 then worked perfectly fine. Also, XDG_CURRENT_DESKTOP is set to GNOME instead of "Unity:7;Unity:ubuntu" with the Jammy version, which is really unexpected and might be causing these issues. seb128 and 3vin1o: Neither I nor Khurshid are sure about what has changed between the two packages, and I think this is a critical bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1968887] [NEW] Save As Dialog Box does not get focus in Ubuntu 22.04
You have been subscribed to a public bug: When using a browser to right click a file and save as, the save as window does not get focus, which means you can't just type the name of the file you want, you have to force focus onto the window to use it by clicking it. This defeats the entire purpose of 2 built in features, 1 being the pre- selected original file name (since you can't rename until you re-aquire focus for that window, thereby undoing the pre-selection programmed in) and 2, the ability to quickly save the file with a keystroke. A side note to this, ubuntu-bug should have an option to report bugs with other WITHOUT having to specify a package. This is a bug in ubuntu- bug. Not a feature. Because we don't always know what package(s) are involved. This needs to be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 13 07:55:24 2022 InstallationDate: Installed on 2022-03-31 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug dist-upgrade jammy -- Save As Dialog Box does not get focus in Ubuntu 22.04 https://bugs.launchpad.net/bugs/1968887 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965505] Re: Changing the position of the dock moves applications to first workspace
Changing status to "Incomplete" as I can't currently reproduce this issue which was so easy to do so before when using two displays. Edit: sorry for the noise, This is still an issue. -- 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/1965505 Title: Changing the position of the dock moves applications to first workspace Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I have a two monitor set-up with four workspaces on the primary display and an additional workspace on the secondary display. I normally have an application running in each workspace. If I open Settings | Dock | Position on screen and change the setting from 'Left' to 'Bottom' I find that the applications on workspaces 3 and 4 move to workspace 1. The applications in workspaces 1 and 2 remain running in those workspaces. Reverting to the change doesn't move the applications back to their former workspace. There have been other occasions when I have seen this behaviour but am I unable to reproduce at this time. Primary monitor: External - four workspaces Secondary monitor: Laptop internal - single workspace ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter-common 42~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 18 08:03:00 2022 InstallationDate: Installed on 2021-11-11 (126 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2021-11-11 (126 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965505/+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 1969637] Re: lookup table appears bottom left of application
** Changed in: ibus Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application Status in ibus: Fix Released Status in im-config package in Ubuntu: New Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+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 1969632] Re: demote ntfs-3g
** Description changed: demote ntfs-3g Kernel now ships ntfs3 kernel module which is preferred over fuse/ntfs-3g way of mounting ntfs3 filesystems. At the moment we do ship ntfs-3g in standard, live, desktop, server. udisks2 still recommends ntfs-3g. ubiquity uses ntfsresize binary shipped by ntfs-3g. curtin installs and uses ntfs-3g as well, still it seems. + + but there is still a lot of useful ntfs-3g tooling in the ntfs-3g + package. + + For example, maybe we should drop the ntfs-3g initramfs hooks and drop + mount.ntfs-3g utilities, in favor of using ntfs3 kernel module. But + otherwise keep all other ntfs-3g package utils in place? -- 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/1969632 Title: demote ntfs-3g Status in curtin: New Status in udisks2 package in Ubuntu: New Bug description: demote ntfs-3g Kernel now ships ntfs3 kernel module which is preferred over fuse/ntfs-3g way of mounting ntfs3 filesystems. At the moment we do ship ntfs-3g in standard, live, desktop, server. udisks2 still recommends ntfs-3g. ubiquity uses ntfsresize binary shipped by ntfs-3g. curtin installs and uses ntfs-3g as well, still it seems. but there is still a lot of useful ntfs-3g tooling in the ntfs-3g package. For example, maybe we should drop the ntfs-3g initramfs hooks and drop mount.ntfs-3g utilities, in favor of using ntfs3 kernel module. But otherwise keep all other ntfs-3g package utils in place? To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1969632/+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 1969632] Re: demote ntfs-3g
** Also affects: curtin Importance: Undecided Status: New -- 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/1969632 Title: demote ntfs-3g Status in curtin: New Status in udisks2 package in Ubuntu: New Bug description: demote ntfs-3g Kernel now ships ntfs3 kernel module which is preferred over fuse/ntfs-3g way of mounting ntfs3 filesystems. At the moment we do ship ntfs-3g in standard, live, desktop, server. udisks2 still recommends ntfs-3g. ubiquity uses ntfsresize binary shipped by ntfs-3g. curtin installs and uses ntfs-3g as well, still it seems. but there is still a lot of useful ntfs-3g tooling in the ntfs-3g package. For example, maybe we should drop the ntfs-3g initramfs hooks and drop mount.ntfs-3g utilities, in favor of using ntfs3 kernel module. But otherwise keep all other ntfs-3g package utils in place? To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1969632/+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 1966786] Re: login screen shown twice with VirtualBox Guest Additions
It's fixed as far as I can see. Changed the status to 'Fix Released'. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions Status in gdm3 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: The login screen is shown twice and I have to supply the password twice. The system works normally afterwards. When I select auto-login in the settings still one login screen is shown. gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static) Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1915 (gdm3) Tasks: 3 (limit: 2291) Memory: 5.0M CPU: 125ms CGroup: /system.slice/gdm.service └─1915 /usr/sbin/gdm3 mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager... mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager. mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate daemon control file mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password to try later in open session mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was already dead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 11:48:17 2022 InstallationDate: Installed on 2020-01-25 (793 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+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 1969637] Re: lookup table appears bottom left of application
** Bug watch added: github.com/ibus/ibus/issues #2401 https://github.com/ibus/ibus/issues/2401 ** Also affects: ibus via https://github.com/ibus/ibus/issues/2401 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application Status in ibus: Unknown Status in im-config package in Ubuntu: New Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+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 1969632] Re: demote ntfs-3g
** Merge proposal linked: https://code.launchpad.net/~xnox/ubuntu/+source/udisks2/+git/udisks2/+merge/419970 -- 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/1969632 Title: demote ntfs-3g Status in curtin: New Status in udisks2 package in Ubuntu: New Bug description: demote ntfs-3g Kernel now ships ntfs3 kernel module which is preferred over fuse/ntfs-3g way of mounting ntfs3 filesystems. At the moment we do ship ntfs-3g in standard, live, desktop, server. udisks2 still recommends ntfs-3g. ubiquity uses ntfsresize binary shipped by ntfs-3g. curtin installs and uses ntfs-3g as well, still it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1969632/+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 1969637] [NEW] lookup table appears bottom left of application
Public bug reported: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus Importance: Unknown Status: Unknown ** Affects: im-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy uec-images ** Attachment added: "Screenshot from 2022-04-21 00-17-56.png" https://bugs.launchpad.net/bugs/1969637/+attachment/5581853/+files/Screenshot%20from%202022-04-21%2000-17-56.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1969637 Title: lookup table appears bottom left of application Status in ibus: Unknown Status in im-config package in Ubuntu: New Bug description: I know it is not im-config issue. I don't know what is root cause. how to reproduce: 1. Install Ubuntu 22.04 LTS or apply newest update 2. boot 3. select a user 4. select Ubuntu on Xorg 5. input password 6. login 7. run gedit 8. push Hankaku/Zenkaku key 9. input any keys 10. lookup table appears bottom left of application proposed fix: edit DESKTOP_SETUP_IBUS="GNOME" to DESKTOP_SETUP_IBUS="" on /etc/default/im-config ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: im-config 0.50-2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 00:13:10 2022 InstallationDate: Installed on 2022-04-20 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1969637/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Quoting upstream systemd developers (https://github.com/systemd/systemd/issues/22737#issuecomment-1077682307): "We essentially traded one problem (lockup when starting services) for another (the failure described in this commit). I actually think that the lockup is worse. Here there is a simple solution: switch from dbus-daemon to dbus-broker. [...] A proper fix will most likely be to make all dbus calls asynchronous in systemd, but that is a lot of work and it's unclear when/if it'll happen. The regression is unfortunate, but I don't think we can fix it in reasonable time." So I wonder what's the best path forward in Ubuntu... if we revert, we'll re-introduce the lockup/timeout problem with dbus-daemon. If we keep the current version, fwupd-refresh.service is broken. The comment at https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992 suggests that disabling the DynamicUser= setting makes the service work again. Maybe that's worth a try, in order to get both problems solved? (i.e. shipping an override config for fwupd) $cat /etc/systemd/system/fwupd-refresh.service.d/override.conf [Service] DynamicUser=no -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Released Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling.
[Desktop-packages] [Bug 1948498] Re: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU
Seems to be fixed with linux-image-5.13.0-39-generic ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1948498 Title: Bluetooth Headset not working when Lenovo P14s AMD Gen1 is connected to Lenovo USB Dock 40AY0090EU Status in pulseaudio package in Ubuntu: Fix Released Bug description: When the Laptop is not connected to it's dock, the bluethooth headset works. As soon as it is connected to a Lenovo 40AY0090EU Dock, sound stops on the headsets and plays via the display connected via DisplayPort. The headset is still available in sound settings, but even if selected, no sound plays on the headset. If I change the configuration (HSP/A2DP), a short "click" sound can be heard on the headset, so apparently there's still something going on between the laptop and the headsets. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 22 22:04:27 2021 InstallationDate: Installed on 2021-09-29 (23 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.35 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET66W(1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y1000MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrR1BET66W(1.35):bd07/30/2021:br1.35:efr1.35:svnLENOVO:pn20Y1000MGE:pvrThinkPadP14sGen1:skuLENOVO_MT_20Y1_BU_Think_FM_ThinkPadP14sGen1:rvnLENOVO:rn20Y1000MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P14s Gen 1 dmi.product.name: 20Y1000MGE dmi.product.sku: LENOVO_MT_20Y1_BU_Think_FM_ThinkPad P14s Gen 1 dmi.product.version: ThinkPad P14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1948498/+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 1969633] [NEW] Bluetooth not connecting
Public bug reported: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1969633 Title: Bluetooth not connecting Status in bluez package in Ubuntu: New Bug description: My computer is an ASUS A88XM-A with AMD A8-7600 Radeon R7. Pluggable USB 2 Bluetooth dongle. Logitech K480 Bluetooth keyboard and Keychron K7 Bluetooth "keyboard". The Bluetooth manager finds the K480 but pairing always fails. The keyboard flashes blue but dongle steady blue. The K7 does not even show up. (But then the "keyboard" does not even work using a USB cable.) Bought dongle and K480 4 years ago, never got them to work at all, gave up as a bad investment. I ordered a K7 wireless keyboard. What I received was a Bluetooth keyboard. Bluetooth does not work. Plugging it in with a USB cable partially works (function keys and End key do not work). Got the K480 working with my Samsung Galaxy 5 Android tablet, but not with my computer. I want Bluetooth but do not know how to get it to work. It still does not work after 4 years of cold boots and the replacement of the power supply. I went to the Keychron Facebook Linux group. They were complaining that Ubuntu does not support Bluetooth and that the Keychron function keys do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 20 10:45:57 2022 InstallationDate: Installed on 2022-03-05 (46 days ago) InstallationMedia: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=0fc4c88c-4da7-4b59-afcc-1de5d036e6ba ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh
[Desktop-packages] [Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
could someone use --g-fatal-warning and try to get a https://wiki.ubuntu.com/Backtrace of the warning? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1969632] [NEW] demote ntfs-3g
Public bug reported: demote ntfs-3g Kernel now ships ntfs3 kernel module which is preferred over fuse/ntfs-3g way of mounting ntfs3 filesystems. At the moment we do ship ntfs-3g in standard, live, desktop, server. udisks2 still recommends ntfs-3g. ubiquity uses ntfsresize binary shipped by ntfs-3g. curtin installs and uses ntfs-3g as well, still it seems. ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Merge proposal linked: https://code.launchpad.net/~xnox/ubuntu-seeds/+git/platform/+merge/419962 ** Merge proposal linked: https://code.launchpad.net/~xnox/ubuntu-seeds/+git/ubuntu-seeds/+merge/419961 -- 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/1969632 Title: demote ntfs-3g Status in udisks2 package in Ubuntu: New Bug description: demote ntfs-3g Kernel now ships ntfs3 kernel module which is preferred over fuse/ntfs-3g way of mounting ntfs3 filesystems. At the moment we do ship ntfs-3g in standard, live, desktop, server. udisks2 still recommends ntfs-3g. ubiquity uses ntfsresize binary shipped by ntfs-3g. curtin installs and uses ntfs-3g as well, still it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1969632/+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 1965439] Re: software-properties-qt can no longer launch when called by pkexec
** Description changed: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma-discover's "Software Sources" link. + Steps to recrate: + + 1) Open Plasma-discover + 2) Go to Settings + 3) Under click on "Software Sources" + 4) Attempt to enter password + + Expected: Software properties opens + + Actual: Pkexec keeps asking for password. + + -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage: ubuntustudio-default-settings UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago) modified.conffile..etc.skel..local.share.konsole.Profile: [deleted] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1965439 Title: software-properties-qt can no longer launch when called by pkexec Status in kubuntu-settings package in Ubuntu: In Progress Status in policykit-1 package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in ubuntustudio-default-settings package in Ubuntu: In Progress Status in kubuntu-settings source package in Jammy: In Progress Status in policykit-1 source package in Jammy: Confirmed Status in software-properties source package in Jammy: Confirmed Status in ubuntustudio-default-settings source package in Jammy: In Progress Bug description: See description below. As the driver manager is done inside software- properties-qt, it's basically the same bug, but now it's affected by something we can't exactly get into the mechanism of: plasma- discover's "Software Sources" link. Steps to recrate: 1) Open Plasma-discover 2) Go to Settings 3) Under click on "Software Sources" 4) Attempt to enter password Expected: Software properties opens Actual: Pkexec keeps asking for password. -- Earlier description: The driver manager for both Ubuntu Studio and Kubuntu can no longer launch due to some updated security measures in PolicyKit. The original behavior was that systemsettings would open /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver- manger) via pkexec, which would then open software-settings-qt. Unfortunately, the new behavior does not act correctly to pkexec and pkexec does not see the user as available in the sudoers file. The only way around this was to pass "export DISPLAY=:0" inside the appropriate driver manager executable with the command "sudo software- properties-qt". The KCM itself needs to execute the driver-manager via xterm, which then prompts for a password. It's ugly, but it works. I will attach a debdiff for the kubuntu-settings package. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntustudio-default-settings 22.04.19 [modified: usr/share/sddm/themes/ubuntustudio/theme.conf] ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19 Uname: Linux 5.15.0-22-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Mar 17 12:19:44 2022 InstallationDate: Installed on 2021-03-20 (361 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) PackageArchitecture: all SourcePackage:
[Desktop-packages] [Bug 1969619] Re: RDP Sharing appears on by default in jammy
** Changed in: gnome-control-center (Ubuntu Jammy) Milestone: None => ubuntu-22.04.1 -- 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/1969619 Title: RDP Sharing appears on by default in jammy Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center source package in Jammy: Triaged Bug description: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Also, the RDP enable gsettings key is turned off. $ gsettings get org.gnome.desktop.remote-desktop.rdp enable false 2. When I open the Sharing page, the gsettings key turns to true and systemctl shows me an error where it tried to enable RDP: Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly 3. So then I open Remote Desktop Sharing and turn it off then on and then systemctl shows me that is working correctly. Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started Note in particular the final line: "RDP server started". That tells us whether RDP is running or not. There would be a similar line for VNC. This line didn't show in the initial state in step 1. What should happen == Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. There is no gsettings for the Sharing master on/off switch (in the headerbar). It shows as On if any of the services are On. None of the services should be On by default so this should show Off by default. A Bug Trigger = It looks like this bug was triggered by https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 I have reported this issue to GNOME. That patch fixes an important issue so maybe we need to keep that patch but fix the logic in gnome- control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+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 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session
fwiw I've checked Ubuntu 21.10/22.04, Fedora 35/36 and Arch. This only happens in Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1951878 Title: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session Status in gtk+3.0 package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 on Wayland session mutter 40.5-1ubuntu3~21.10.1 My apologies if this does not belong in mutter but because it happens in multiple applications, it's my best guess. This is a weird bug because I don't know what causes it but it happens consistently after normal usage which for me means several times leaving the laptop idle and unlocking. If I leave gnome-terminal and/or evince open, eventually any UI action like switching from multiple tabs, opening context menu etc will output the following to journal gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window I suspect this may happen with other gtk apps as well. This persists until each individual app is restarted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+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 1969619] Re: RDP Sharing appears on by default in jammy
Thank you for filling in the bug! So from what I understand here, this means that sharing is disabled until someone opens the sharing screen in the gnome-control-center, right? I agree with the 'High' priority here in that case, but it's certainly not a 22.04 release blocker - however, the fix for that should be prepared ASAP and uploaded as a 0-day SRU, if possible. Actually, I even think maybe it should go through the security pocket, as at least to me this seems like a violation of our security policies by enabling RDP without the users knowledge. This way all the users would get this update as well via unattended updates. Could we get some input from the security team? What do you think? -- 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/1969619 Title: RDP Sharing appears on by default in jammy Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center source package in Jammy: Triaged Bug description: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Also, the RDP enable gsettings key is turned off. $ gsettings get org.gnome.desktop.remote-desktop.rdp enable false 2. When I open the Sharing page, the gsettings key turns to true and systemctl shows me an error where it tried to enable RDP: Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly 3. So then I open Remote Desktop Sharing and turn it off then on and then systemctl shows me that is working correctly. Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started Note in particular the final line: "RDP server started". That tells us whether RDP is running or not. There would be a similar line for VNC. This line didn't show in the initial state in step 1. What should happen == Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. There is no gsettings for the Sharing master on/off switch (in the headerbar). It shows as On if any of the services are On. None of the services should be On by default so this should show Off by default. A Bug Trigger = It looks like this bug was triggered by https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 I have reported this issue to GNOME. That patch fixes an important issue so maybe we need to keep that patch but fix the logic in gnome- control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+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 1969558] Re: Incorrect Window Resizing for Extension Settings
alright, even better, I just downloaded a pre-release of 22.04 and installed it into gnome box to check if it's my session or not. I litterally just installed as a virtual machine, didn't change any setting and the issue is there too (using Wayland). -- 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/1969558 Title: Incorrect Window Resizing for Extension Settings Status in gnome-shell package in Ubuntu: Incomplete Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+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 1969628] [NEW] Used memory indication is not really useful
Public bug reported: The values shown as "memory used" are not really informative. Roughly speaking "used" memory (indicated in the tool) = "really used" memory (NOT indicated in the tool) + "cache" (indicated in the tool) + "available" (NOT indicated in the tool) The tool shows the LHS "used memory" and "cache", but does not show the "available memory". With modern kernels the tendency is to "use" memory as much as possible in various buffers, so the value indicated in that tool has no practical value. For a user I would presume that "memory" should be indication of "really used" memory, because only that tells him how many application will he be able to run. Currently my Machine tells me it is using 61 GB of memory, with 20.5 GB in Cache. While all I have open are some basic simple tools like skype, Gnome-Terminal and a few Google Chrome windows. Thing is I have 33GB in "available" (according to TOP), which tells me that I am "really using" around 7GB of memory, which sounds about right. There is no way to get the 7GB value from gnome-system-monitor. The gnome-system-monitor should show "really used memory" or at the very least show also "available" memory just below "cache". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-system-monitor 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 16:07:09 2022 SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to jammy on 2022-03-19 (32 days ago) mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot from 2022-04-20 16-07-21.png" https://bugs.launchpad.net/bugs/1969628/+attachment/5581831/+files/Screenshot%20from%202022-04-20%2016-07-21.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1969628 Title: Used memory indication is not really useful Status in gnome-system-monitor package in Ubuntu: New Bug description: The values shown as "memory used" are not really informative. Roughly speaking "used" memory (indicated in the tool) = "really used" memory (NOT indicated in the tool) + "cache" (indicated in the tool) + "available" (NOT indicated in the tool) The tool shows the LHS "used memory" and "cache", but does not show the "available memory". With modern kernels the tendency is to "use" memory as much as possible in various buffers, so the value indicated in that tool has no practical value. For a user I would presume that "memory" should be indication of "really used" memory, because only that tells him how many application will he be able to run. Currently my Machine tells me it is using 61 GB of memory, with 20.5 GB in Cache. While all I have open are some basic simple tools like skype, Gnome-Terminal and a few Google Chrome windows. Thing is I have 33GB in "available" (according to TOP), which tells me that I am "really using" around 7GB of memory, which sounds about right. There is no way to get the 7GB value from gnome-system-monitor. The gnome-system-monitor should show "really used memory" or at the very least show also "available" memory just below "cache". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-system-monitor 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 16:07:09 2022 SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to jammy on 2022-03-19 (32 days ago) mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1969628/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
> https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907 This appears to have caused a regression in fwupd in Ubuntu 20.04 with details at https://github.com/fwupd/fwupd/issues/3037 fwupd-refresh.service uses DynamicUser and now hits this upstream bug: https://github.com/systemd/systemd/issues/22737 ** Bug watch added: github.com/fwupd/fwupd/issues #3037 https://github.com/fwupd/fwupd/issues/3037 ** Bug watch added: github.com/systemd/systemd/issues #22737 https://github.com/systemd/systemd/issues/22737 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Released Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped
[Desktop-packages] [Bug 1969619] Re: RDP Sharing appears on by default in jammy
** No longer affects: gnome-remote-desktop (Ubuntu) ** Project changed: gnome-remote-desktop => gnome-control-center ** No longer affects: gnome-remote-desktop (Ubuntu Jammy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1969619 Title: RDP Sharing appears on by default in jammy Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center source package in Jammy: Triaged Bug description: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Also, the RDP enable gsettings key is turned off. $ gsettings get org.gnome.desktop.remote-desktop.rdp enable false 2. When I open the Sharing page, the gsettings key turns to true and systemctl shows me an error where it tried to enable RDP: Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly 3. So then I open Remote Desktop Sharing and turn it off then on and then systemctl shows me that is working correctly. Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started Note in particular the final line: "RDP server started". That tells us whether RDP is running or not. There would be a similar line for VNC. This line didn't show in the initial state in step 1. What should happen == Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. There is no gsettings for the Sharing master on/off switch (in the headerbar). It shows as On if any of the services are On. None of the services should be On by default so this should show Off by default. A Bug Trigger = It looks like this bug was triggered by https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 I have reported this issue to GNOME. That patch fixes an important issue so maybe we need to keep that patch but fix the logic in gnome- control-center. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1969619/+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 1966945] Re: xdg-desktop-portal crashed with SIGSEGV in magazine_chain_pop_head()
I can confirm that this is fixed with 1.14.3-0ubuntu2 - I could not reproduce the issue anymore after updating to that version. Thanks a lot for you effort! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1966945 Title: xdg-desktop-portal crashed with SIGSEGV in magazine_chain_pop_head() Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Jammy: Fix Released Bug description: Impact -- xdg-desktop-portal 1.14.3 has a single change fixing a consistent crash when using the experimental Wayland feature in TeamViewer. Original Bug Report --- Crash happened a short time after starting a screen cast / remote desktop session using the Freedesktop portal API in a Wayland session with mouse and keyboard input. Screen cast continues to run (i.e., PipeWire stream), but input stops. Can be reproduced by using the experimental Wayland support of TeamViewer (https://community.teamviewer.com/English/discussion/122410/teamviewer- support-on-wayland-experimental-state-%F0%9F%A7%AA) Reported upstream as well: https://github.com/flatpak/xdg-desktop- portal/issues/771 lsb_release -rd: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 29 14:04:48 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal InstallationDate: Installed on 2022-03-25 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220325) ProcCmdline: /usr/libexec/xdg-desktop-portal SegvAnalysis: Segfault happened at: 0x7fcf54779d7b:mov0x8(%rax),%rcx PC (0x7fcf54779d7b) ok source "0x8(%rax)" (0x7fcf0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: xdg-desktop-portal StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 __GI___nptl_deallocate_tsd () at ./nptl/nptl_deallocate_tsd.c:73 __GI___nptl_deallocate_tsd () at ./nptl/nptl_deallocate_tsd.c:22 start_thread (arg=) at ./nptl/pthread_create.c:453 Title: xdg-desktop-portal crashed with SIGSEGV in __GI___nptl_deallocate_tsd() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966945/+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 1969622] [NEW] save file dialog doesn't allow saving to a directory without files
Public bug reported: Impact -- Ubuntu uses xdg-desktop-portal-gnome for the save dialog for snaps (like Firefox or Chromium). xdg-desktop-portal-gnome in Ubuntu 22.04 uses gtk4 This issue also affects gnome-text-editor which uses gtk4 directly. Attempting to save a file to an empty folder won't work in many cases because the Save button is insensitive (unable to be clicked). Test Case - View this page with the Firefox or Chromium snaps. Press Ctrl+S to try to save this page. Navigate to a folder without any files in it. (It can have other folders in it.) The Save button should stay lit up. Save the file. Note that I wasn't able to reproduce the bug for bookmarked folders in the left sidebar so just navigate using the main view area. What Could Go Wrong This is a one-line bug fix from the stable gtk-4-6 branch targeted to directly fix this issue. Other Notes --- I do not believe we need to respin the Ubuntu 22.04 ISOs for this issue. I do request a 0-day SRU since this is a small high impact fix that affects the usability of the Firefox snap. ** Affects: gtk Importance: Unknown Status: Unknown ** Affects: gtk4 (Ubuntu) Importance: High Assignee: Jeremy Bicha (jbicha) Status: In Progress ** Tags: jammy ** Summary changed: - save file dialog doesn't allow saving to empty directory + save file dialog doesn't allow saving to a directory without files ** Description changed: Impact -- Ubuntu uses xdg-desktop-portal-gnome for the save dialog for snaps (like Firefox or Chromium). xdg-desktop-portal-gnome in Ubuntu 22.04 uses gtk4 This issue also affects gnome-text-editor which uses gtk4 directly. Attempting to save a file to an empty folder won't work in many cases because the Save button is insensitive (unable to be clicked). Test Case - View this page with the Firefox or Chromium snaps. Press Ctrl+S to try to save this page. - Navigate to an empty folder. + Navigate to a folder without any files in it. (It can have other folders in it.) The Save button should stay lit up. Save the file. Note that I wasn't able to reproduce the bug for bookmarked folders in the left sidebar so just navigate using the main view area. What Could Go Wrong This is a one-line bug fix from the stable gtk-4-6 branch targeted to directly fix this issue. Other Notes --- I do not believe we need to respin the Ubuntu 22.04 ISOs for this issue. I do request a 0-day SRU since this is a small high impact fix that affects the usability of the Firefox snap. ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4851 https://gitlab.gnome.org/GNOME/gtk/-/issues/4851 ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/-/issues/4851 Importance: Unknown Status: Unknown ** Changed in: gtk4 (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1969622 Title: save file dialog doesn't allow saving to a directory without files Status in GTK+: Unknown Status in gtk4 package in Ubuntu: In Progress Bug description: Impact -- Ubuntu uses xdg-desktop-portal-gnome for the save dialog for snaps (like Firefox or Chromium). xdg-desktop-portal-gnome in Ubuntu 22.04 uses gtk4 This issue also affects gnome-text-editor which uses gtk4 directly. Attempting to save a file to an empty folder won't work in many cases because the Save button is insensitive (unable to be clicked). Test Case - View this page with the Firefox or Chromium snaps. Press Ctrl+S to try to save this page. Navigate to a folder without any files in it. (It can have other folders in it.) The Save button should stay lit up. Save the file. Note that I wasn't able to reproduce the bug for bookmarked folders in the left sidebar so just navigate using the main view area. What Could Go Wrong This is a one-line bug fix from the stable gtk-4-6 branch targeted to directly fix this issue. Other Notes --- I do not believe we need to respin the Ubuntu 22.04 ISOs for this issue. I do request a 0-day SRU since this is a small high impact fix that affects the usability of the Firefox snap. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1969622/+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 1969558] Re: Incorrect Window Resizing for Extension Settings
ok, I just created a new user to see if this could have something to do with settings I might have changed or extensions but the brand new profile has the same issue. This looks somewhat similar to this issue which was also Wayland specific: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1922034 -- 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/1969558 Title: Incorrect Window Resizing for Extension Settings Status in gnome-shell package in Ubuntu: Incomplete Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+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 1969619] Re: RDP Sharing appears on by default in jammy
** Bug watch added: gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues #94 https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/94 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/issues/94 Importance: Unknown Status: Unknown ** Also affects: gnome-remote-desktop (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: New => Triaged ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Importance: Undecided => High ** Project changed: gnome-control-center => gnome-remote-desktop ** Description changed: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Also, the RDP enable gsettings key is turned off. $ gsettings get org.gnome.desktop.remote-desktop.rdp enable false 2. When I open the Sharing page, the gsettings key turns to true and systemctl shows me an error where it tried to enable RDP: Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly 3. So then I open Remote Desktop Sharing and turn it off then on and then systemctl shows me that is working correctly. Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started Note in particular the final line: "RDP server started". That tells us whether RDP is running or not. There would be a similar line for VNC. This line didn't show in the initial state in step 1. What should happen == Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. There is no gsettings for the Sharing master on/off switch (in the headerbar). It shows as On if any of the services are On. None of the services should be On by default so this should show Off by default. - Guesses and Further Investigation Needed - == - I think there may have been a logic bug when the RDP sharings were backported from gnome-control-center 42. This code was originally in gtk4 so some rewriting was necessary. + A Bug Trigger + = + It looks like this bug was triggered by + https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 - I didn't see this issue in a Fedora 36 Beta instance. Sharing showed off - by default. - - Also, we did add this patch: - https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 - I think that patch is necessary but maybe that changed what gnome-control-center was expecting to see. + I have reported this issue to GNOME. That patch fixes an important issue + so maybe we need to keep that patch but fix the logic in gnome-control- + center. -- 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/1969619 Title: RDP Sharing appears on by default in jammy Status in GNOME Remote Desktop: Unknown Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-remote-desktop package in Ubuntu: Triaged Status in gnome-control-center source package in Jammy: Triaged Status in gnome-remote-desktop source package in Jammy: Triaged Bug description: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it
[Desktop-packages] [Bug 1969620] [NEW] /usr/bin/software-properties-gtk:TypeError:on_driver_selection_changed
*** This bug is a duplicate of bug 1969460 *** https://bugs.launchpad.net/bugs/1969460 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22, the problem page at https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57 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/. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: impish jammy kylin-22.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969620 Title: /usr/bin/software-properties-gtk:TypeError:on_driver_selection_changed Status in software-properties package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding software-properties. This problem was most recently seen with package version 0.99.22, the problem page at https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57 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/software-properties/+bug/1969620/+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 1969621] [NEW] /usr/libexec/xdg-desktop-portal-gnome:11:gtk_tree_view_update_rubber_band_selection_range:gtk_tree_view_update_rubber_band_selection:gtk_tree_view_update_rubber_
*** This bug is a duplicate of bug 1966529 *** https://bugs.launchpad.net/bugs/1966529 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xdg-desktop-portal-gnome. This problem was most recently seen with package version 42.0.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/44bd0ca893055a3c496a03038023a8d0d4860802 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/. ** Affects: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided Status: New ** Tags: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1969621 Title: /usr/libexec/xdg-desktop-portal- gnome:11:gtk_tree_view_update_rubber_band_selection_range:gtk_tree_view_update_rubber_band_selection:gtk_tree_view_update_rubber_band:gtk_tree_view_drag_gesture_update:_gtk_marshal_VOID__DOUBLE_DOUBLEv Status in xdg-desktop-portal-gnome package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xdg-desktop-portal-gnome. This problem was most recently seen with package version 42.0.1-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/44bd0ca893055a3c496a03038023a8d0d4860802 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/xdg-desktop-portal-gnome/+bug/1969621/+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 1969619] Re: RDP Sharing appears on by default in jammy
** Description changed: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Also, the RDP enable gsettings key is turned off. $ gsettings get org.gnome.desktop.remote-desktop.rdp enable false 2. When I open the Sharing page, the gsettings key turns to true and systemctl shows me an error where it tried to enable RDP: Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly 3. So then I open Remote Desktop Sharing and turn it off then on and then systemctl shows me that is working correctly. Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started Note in particular the final line: "RDP server started". That tells us whether RDP is running or not. There would be a similar line for VNC. This line didn't show in the initial state in step 1. What should happen == - The Sharing master witch should be off by default. + Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. - Remote Desktop should show off by default and should not attempt to turn - on just by opening the Sharing page. + There is no gsettings for the Sharing master on/off switch (in the + headerbar). It shows as On if any of the services are On. None of the + services should be On by default so this should show Off by default. Guesses and Further Investigation Needed == - Is there a gsettings key for the master sharing on/off switch? - - I think there may have been a logic bug when the RDP sharings were - backported from gnome-control-center 42. This code was originally in - gtk4 so some rewriting was necessary. + I think there may have been a logic bug when the RDP sharings were backported from gnome-control-center 42. This code was originally in gtk4 so some rewriting was necessary. I didn't see this issue in a Fedora 36 Beta instance. Sharing showed off by default. Also, we did add this patch: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 I think that patch is necessary but maybe that changed what gnome-control-center was expecting to see. -- 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/1969619 Title: RDP Sharing appears on by default in jammy Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-control-center source package in Jammy: Triaged Bug description: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup:
[Desktop-packages] [Bug 1969619] [NEW] RDP Sharing appears on by default in jammy
Public bug reported: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago Main PID: 1611 (gnome-remote-de) Tasks: 4 (limit: 4603) Memory: 13.8M CPU: 66ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:07:44 ubuntu2204 gnome-remote-desktop-daemon[1611]: libEGL warning: pci id for fd 9: 1b36:0100, driver (null) Apr 20 08:07:44 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Also, the RDP enable gsettings key is turned off. $ gsettings get org.gnome.desktop.remote-desktop.rdp enable false 2. When I open the Sharing page, the gsettings key turns to true and systemctl shows me an error where it tried to enable RDP: Apr 20 08:12:50 ubuntu2204 gnome-remote-de[1611]: RDP TLS certificate and key not configured properly 3. So then I open Remote Desktop Sharing and turn it off then on and then systemctl shows me that is working correctly. Apr 20 08:14:32 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop... Apr 20 08:14:32 ubuntu2204 gnome-remote-desktop-daemon[2801]: libEGL warning: p> Apr 20 08:14:32 ubuntu2204 systemd[1483]: Started GNOME Remote Desktop. Apr 20 08:14:32 ubuntu2204 gnome-remote-de[2801]: RDP server started Note in particular the final line: "RDP server started". That tells us whether RDP is running or not. There would be a similar line for VNC. This line didn't show in the initial state in step 1. What should happen == The Sharing master witch should be off by default. Remote Desktop should show off by default and should not attempt to turn on just by opening the Sharing page. Guesses and Further Investigation Needed == Is there a gsettings key for the master sharing on/off switch? I think there may have been a logic bug when the RDP sharings were backported from gnome-control-center 42. This code was originally in gtk4 so some rewriting was necessary. I didn't see this issue in a Fedora 36 Beta instance. Sharing showed off by default. Also, we did add this patch: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/commit/7f4ef31fd3 I think that patch is necessary but maybe that changed what gnome-control-center was expecting to see. ** Affects: gnome-control-center (Ubuntu) Importance: High Status: Triaged ** Affects: gnome-control-center (Ubuntu Jammy) Importance: High Status: Triaged ** Tags: jammy ** Also affects: gnome-control-center (Ubuntu Jammy) Importance: High Status: Triaged ** Description changed: Summary === 1. From the Ubuntu 22.04 live session (or a clean install), Open the Settings app. 2. Open the Sharing page. It looks like Remote Desktop sharing is turned on. On further investigation, it is not actually on. More details This issue affects both the live session and the initial install. (Probably would show up for any new user.) 1. Before opening the Settings app, the gnome-remote-desktop service is running. I think this is expected. - $ systemctl status --user gnome-remote-desktop.service + $ systemctl status --user gnome-remote-desktop.service \u25cf gnome-remote-desktop.service - GNOME Remote Desktop - Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> - Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago -Main PID: 1611 (gnome-remote-de) - Tasks: 4 (limit: 4603) - Memory: 13.8M - CPU: 66ms - CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> - \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon + Loaded: loaded (/usr/lib/systemd/user/gnome-remote-desktop.service; enable> + Active: active (running) since Wed 2022-04-20 08:07:44 EDT; 17s ago + Main PID: 1611 (gnome-remote-de) + Tasks: 4 (limit: 4603) + Memory: 13.8M + CPU: 66ms + CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/gnome-remo> + \u2514\u25001611 /usr/libexec/gnome-remote-desktop-daemon Apr 20 08:07:44 ubuntu2204 systemd[1483]: Starting GNOME Remote Desktop...
[Desktop-packages] [Bug 1968195] Re: websocket transport is never enabled
closed in tandem with #1968577. This was also backported to stable-2.0 branch ** Changed in: freerdp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1968195 Title: websocket transport is never enabled Status in freerdp package in Ubuntu: Fix Released Bug description: freerdp supports an rdp gateway with websocket transport since 2.3.0. There was however a backport bug that never enabled this feature since the introduction to disable this feature (by /gt:auto,no-websockets) the relevant stable push is https://github.com/FreeRDP/FreeRDP/pull/7786 Note that the upstream master branch had never this problem, so that feature should be tested by many people. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1968195/+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 1969558] Re: Incorrect Window Resizing for Extension Settings
actually, I am seing this on all dialogs, including nautilus preference window, DejaDup preferences, etc.. -- 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/1969558 Title: Incorrect Window Resizing for Extension Settings Status in gnome-shell package in Ubuntu: Incomplete Bug description: Issue with gnome-extensions-app While the main Extensions windows behaves normally when being resizes, for Extension Settings, when dragging the bottom corner up, the top of the window also goes down. If I drag the bottom corner down, the top edge goes up... See screenshots attached. I each case, I only adjusted the bottom corner, yet, the top edge moved which is not consistent with the normal window resizing behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:41:18 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-06 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1969558/+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 1960614] Re: Add mid: scheme handler to thunderbird.desktop
Thank you, Olivier. I am happy to see that it works out of the box in 20.04 focal LTS. The fix was released a month ago, but since I anyway had custom association configured in ~/.config/mimeapps.list, I forgot to check it earlier. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1960614 Title: Add mid: scheme handler to thunderbird.desktop Status in thunderbird package in Ubuntu: Fix Released Bug description: Since thunderbird-91 version (actually even earlier, but only ESR releases are packaged in Ubuntu) it is possible to open particular messages from command line using Message-ID: thunderbird mid:a...@example.com See e.g. https://bugzilla.mozilla.org/264270 However to open links from other application "mid:" scheme should be advertised in the thunderbird.desktop file: MimeType=x-scheme-handler/mailto;application/x-xpinstall;x-scheme- handler/mid; Please, adjust this field in the desktop file. To check that the change has effect the following command may be used: xdg-open mid:a...@example.com Notice that it is not upstream issue. Thunderbird developers left desktop integration up to maintainers of Linux distributions. Long time ago it was possible to create such links to particular messages using thunderlink extension but migration from XUL to WebExtension add-ons broke it. Support of mid: scheme restores linking of mail messages from other applications. There is a related issue: request to add message/rfc822 MIME type in lp:1861262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1960614/+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 1969314] Re: xdg-user-dirs-gtk-update not display panel
The initial description stated that you installed in japanese and now you say english, could you describe exact steps of what you are doing to get the dialog? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1969314 Title: xdg-user-dirs-gtk-update not display panel Status in xdg-user-dirs-gtk package in Ubuntu: Incomplete Bug description: Hi, I installed jammy-desktop-amd64.iso 2022-04-16 version by selecting Japanese. ubuntu-20.04, after installing the English version, I added a Japanese environment, but it has easier. However, the setting panel does not appear even if I execute the command to change the Japanese directory name of the HOME directory. LANG=C xdg-user-dirs-gtk-update As for the execution result, both Japanese and English direcotres remained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs-gtk/+bug/1969314/+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 1969314] Re: xdg-user-dirs-gtk-update not display panel
Hi, jammy-desktop-amd64.iso 2022-04-19 version, I installed English environment, then added Japanese. LANG=C xdg-user-dirs-gtk-update work fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1969314 Title: xdg-user-dirs-gtk-update not display panel Status in xdg-user-dirs-gtk package in Ubuntu: Incomplete Bug description: Hi, I installed jammy-desktop-amd64.iso 2022-04-16 version by selecting Japanese. ubuntu-20.04, after installing the English version, I added a Japanese environment, but it has easier. However, the setting panel does not appear even if I execute the command to change the Japanese directory name of the HOME directory. LANG=C xdg-user-dirs-gtk-update As for the execution result, both Japanese and English direcotres remained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs-gtk/+bug/1969314/+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 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version
Is this a `gnome-session` issue? The source sayeth (@ gnome-
session/main.c:422)
/* From 3.14 GDM sets XDG_CURRENT_DESKTOP. For compatibility with
* older versions of GDM, other display managers, and startx,
* set a fallback value if we don't find it set.
*/
There doesn't seem to be any other location in the code that sets
`XDG_CURRENT_DESKTOP` and this code hasn't changed between the two
versions listed above.
Is this because of a change to `gdm` ? Does it work if you switch to
lightdm?
`gdm` sets this from the session definition, which is patched into
gnome-session by
debian/patches/ubuntu/ubuntu-sessions.patch
(the patch file has changed between revisions but mostly to remove a
community session)
gdm fetches this @ daemon/gdm-session.c:2612 get_session_desktop_names()
filename = g_strdup_printf ("%s.desktop", get_session_name (self));
g_debug ("GdmSession: getting desktop names for file '%s'", filename);
keyfile = load_key_file_for_file (self, filename, NULL, NULL);
if (keyfile != NULL) {
gchar **names;
names = g_key_file_get_string_list (keyfile,
G_KEY_FILE_DESKTOP_GROUP,
"DesktopNames", NULL, NULL);
Can't see any obvious changes in GDM between Impish and Jammy that would
cause this just from looking at the diffs though.
--
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/1969357
Title:
Unity7 crashes on Jammy with 22.04's gnome-session version
Status in gnome-session package in Ubuntu:
Confirmed
Status in unity package in Ubuntu:
Confirmed
Bug description:
Unity7 seems to crash on 22.04 when logging in after installing Ubuntu
(it works fine in the live session). I then tried installing the 21.10
gnome-session package on 22.04 and Unity7 then worked perfectly fine.
Also, XDG_CURRENT_DESKTOP is set to GNOME instead of
"Unity:7;Unity:ubuntu" with the Jammy version, which is really
unexpected and might be causing these issues.
seb128 and 3vin1o: Neither I nor Khurshid are sure about what has
changed between the two packages, and I think this is a critical bug.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+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 1969314] Re: xdg-user-dirs-gtk-update not display panel
Today, I download jammy-desktop-amd64.iso 2022-04-19 version, and install it. this version display panel, but not work. ** Attachment added: "Screenshot from 2022-04-20 18-40-25.png" https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs-gtk/+bug/1969314/+attachment/5581695/+files/Screenshot%20from%202022-04-20%2018-40-25.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1969314 Title: xdg-user-dirs-gtk-update not display panel Status in xdg-user-dirs-gtk package in Ubuntu: Incomplete Bug description: Hi, I installed jammy-desktop-amd64.iso 2022-04-16 version by selecting Japanese. ubuntu-20.04, after installing the English version, I added a Japanese environment, but it has easier. However, the setting panel does not appear even if I execute the command to change the Japanese directory name of the HOME directory. LANG=C xdg-user-dirs-gtk-update As for the execution result, both Japanese and English direcotres remained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs-gtk/+bug/1969314/+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 1969598] Re: no auto-focus application after workspace switch
This might have the same root cause as bug 1928317. -- 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/1969598 Title: no auto-focus application after workspace switch Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: 1) Setup at least two workspaces. 2) open at least one GUI application on one of them. Another one is focused and no application opened. 3) switch workspaces from 'empty' to 'with application' Expected result: last focused GUI application from the new focused workspace will be auto-focused again. And all shortcuts right after the switch will be applicable to a given application. Actual result: application is not focused, all shortcuts are applicable to desktop only. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 12:17:48 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 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/1969598/+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 1964120] Re: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack])
Looks like I hit this today in a Xorg session when testing Nvidia. The log provides no details of what caused the crash other than the system was shutting down/logging out at the time. -- 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/1964120 Title: gnome-shell crashed with SIGSEGV at ?+a7c called from (Cannot access memory at address [in stack]) Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Desktop has some issues but it was not showable ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu1 Uname: Linux 5.16.12-051612-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 12:12:08 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-03-04 (4 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 42~beta-1ubuntu1 Signal: 11 SourcePackage: gnome-shell Stacktrace: #0 0x7f0d7aec5a7c in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7ffce8d834a0 StacktraceTop: ?? () Title: gnome-shell crashed with SIGSEGV UpgradeStatus: Upgraded to jammy on 2022-03-04 (4 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964120/+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 1969602] [NEW] gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing
Public bug reported: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1969602 Title: gnome-shell with "Focus on hover" behaves wrongly when alt-tabbing Status in gnome-shell package in Ubuntu: New Bug description: I have set gnome to "focus on hover", i.e. focus follows mouse. If I alt-tab to bring a window to the front but the mouse is over another window, then the hovered-over window will reclaim focus and the window I raised will typically get covered up again. In previous gnome versions, if I explicitly focussed a window via keyboard shortcuts, it remained focussed and I think this is the preferred behaviour. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:35:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-17 (33 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 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/1969602/+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 1969601] [NEW] context menu cut, after screen resolution is changed
Public bug reported: I have a 4K monitor. If I open Nautilus window when display is in 1920x1080 resolution, then change the resolution to 3840x2160 AND change "scaling" to 200% then the context menu appears cut. Changing the resolution and leaving "scaling" at 100% does not trigger the bug. That is the content is scaled by 200% correctly, but the bounds of the context menu window seems not transformed and is twice too small to fit the content. When I open a new window (I do not need to kill already opened window). Then the right-click context menu is fine, in the new window. In the "old" window it remains cut. No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04 LTS Release:22.04 Codename: jammy nautilus: Installed: 1:42.0-1ubuntu2 Candidate: 1:42.0-1ubuntu2 Version table: *** 1:42.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:17:59 2022 SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-19 (32 days ago) mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "Screenshot from 2022-04-20 11-16-58.png" https://bugs.launchpad.net/bugs/1969601/+attachment/5581674/+files/Screenshot%20from%202022-04-20%2011-16-58.png -- 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/1969601 Title: context menu cut, after screen resolution is changed Status in nautilus package in Ubuntu: New Bug description: I have a 4K monitor. If I open Nautilus window when display is in 1920x1080 resolution, then change the resolution to 3840x2160 AND change "scaling" to 200% then the context menu appears cut. Changing the resolution and leaving "scaling" at 100% does not trigger the bug. That is the content is scaled by 200% correctly, but the bounds of the context menu window seems not transformed and is twice too small to fit the content. When I open a new window (I do not need to kill already opened window). Then the right-click context menu is fine, in the new window. In the "old" window it remains cut. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04 LTS Release: 22.04 Codename: jammy nautilus: Installed: 1:42.0-1ubuntu2 Candidate: 1:42.0-1ubuntu2 Version table: *** 1:42.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:17:59 2022 SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-19 (32 days ago) mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1969601/+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
