[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
Everyone please also try this in /etc/environment by itself: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
Although I might be assuming too much because if the bug happened 2 seconds before the log in comment #26 then there's nothing about it being logged. That's normal for freezes. In that case we need to enable full debug mode in /etc/environment: MUTTER_DEBUG=kms reboot and then next time a freeze happens run: journalctl -b0 > journal.txt and compress the resulting text file before attaching it here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
Both of those logs contain the same warning from the kernel graphics code: WARNING: CPU: 12 PID: 148 at drivers/gpu/drm/drm_mode_object.c:45 drm_mode_object_add+0x99/0xa0 [drm] whose call trace seems to be related to DisplayPort, MST (multi-stream transport) and hotplugging. We should assume until proven otherwise that Thomas' issue is originating in the kernel. Everyone else please report new bugs of your own so they can be investigated without confusion. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
And it happened again after I unplugged and plugged my usb-c->display port cable . looks like this time there's more useful information in the logs. ** Attachment added: "journal.txt after unplug/plug the display port cable with mutter (45.0-1ubuntu1)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702554/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
with latest mutter+gnome-shell (single GPU), this still happens. log attached. ** Attachment added: "journal.txt from current boot 2 seconds after the problem occured with mutter (45.0-1ubuntu1)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702553/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036746] Re: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard
gnome-shell (44.3-0ubuntu2) lunar-security; urgency=medium * SECURITY UPDATE: Avoid exposing window previews on lock screen via keyboard shortcuts (CVE-2023-43090, LP: #2036746, gnome-shell#6990) -- Jeremy Bícha Wed, 20 Sep 2023 08:32:31 -0400 ** Tags added: fixed-in-gnome-shell-43.9 fixed-in-gnome-shell-44.5 fixed-upstream ** Also affects: gnome-shell (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Changed in: gnome-shell (Ubuntu Mantic) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Lunar) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Lunar) Status: Confirmed => Fix Committed ** Changed in: gnome-shell (Ubuntu Lunar) Assignee: Marc Deslauriers (mdeslaur) => Jeremy Bícha (jbicha) ** Also affects: gnome-shell (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2036746 Title: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2036746/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1970921] Re: Drag and drop does not work
Second post, as I can only upload one file per comment. A quick screen recording to further demonstrate the reproducible issues. Worth noting that beyond the appended/suffixed text issue, drag and drop seems to struggle with location context too. Drag and drop fails multiple times through standard user permissions, but succeeds 100% of the time through root permissions. ** Attachment added: "Nautilus_Bug_Video.mp4" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970921/+attachment/5702483/+files/Nautilus_Bug_Video.mp4 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1970921 Title: Drag and drop does not work To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1970921/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033688] Re: [mantic] gnome-shell fails to follow accent colours
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: https://iso.qa.ubuntu.com/qatracker/reports/bugs/2033688 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2033688 Title: [mantic] gnome-shell fails to follow accent colours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033688/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1970921] Re: Drag and drop does not work
As no fix has been released yet... Echoing Alejandro's #10 comment, when attempting to drag and drop images from "Files" to Google Chrome or Slack, the following (seemingly random) garbage text is appended / suffixed to the file extension: .jpg0:~28:478:44 .png0:~22:478:44 .png0:~7:460:44 As a result of the appended text, the destination app returns an error indicating the file path/type is invalid: Google Chrome: Your file couldn't be accessed It may have been moved, edited, or deleted. ERR_FILE_NOT_FOUND Slack: File unsupported Sorry, is a type of file not supported by Slack Try uploading a .zip version of this file instead. [OK] In the case of Google Chrome, where the file path can be edited in the address bar, removing the characters improperly suffixed onto the file extension and attempting the navigation again by hitting Enter, the file renders as expected. A fresh installation of Ubuntu on a beefy Dell Precision 5680 laptop: OS Name: Ubuntu 22.04.3 LTS OS Type: 64-bit GNOME Version: 42.9 Windows System: Wayland Standard app installs, two different methods: Google Chrome: $ sudo apt install ./google-chrome-stable_current_amd64.deb Google Chrome Version 117.0.5938.88 (Official Build) (64-bit) Slack: $ sudo snap install slack Snap 4.34.115 64-bit StackExchange got me over to this bug filing: https://unix.stackexchange.com/questions/714305/unable-to-drag-and-drop-files-into-other-applications-on-ubuntu-22-04 And as "0xheartcode" posted there, it does seem to be a permissions issue: "It is a permission issue/feature with Ubuntu 22.04. Opening folders with sudo nautilus /home/user/ or sudo xdg-open /home/user/ fixes this." When executing "$ sudo nautilus /home/" from Terminal, supplying my password, and using the newly launched "Files" window to perform drag and drop into Slack, I can no longer reproduce the issue. With standard permissions, I encounter the improperly suffixed characters and upload error within one to three drag and drop attempts. As root, I can drag and drop upload 25+ images to Slack (10 at a time, per Slack's file upload limitations) without encountering the bug/permissions issue once. ** Attachment added: "Screenshot_References.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970921/+attachment/5702482/+files/Screenshot_References.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1970921 Title: Drag and drop does not work To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1970921/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033688] Re: [mantic] gnome-shell fails to follow accent colours
Hi Aptivi, the screenshot was just an example, I'm seeing the same. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2033688 Title: [mantic] gnome-shell fails to follow accent colours To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2033688/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036746] Re: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard
** Changed in: gnome-shell (Ubuntu Lunar) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2036746 Title: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2036746/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036764] Re: indicator keyboard crashes when upgrading from lunar->mantic on ubuntu cinnamon
Upon investigation, we have determined the rdepends in question: cinnamon-core +-- Depends: lightdm ..+-- Depends: unity-greeter +-- Depends: indicator-applet ..+-- Recommends: indicator-keyboard Unfortunately, this means it cannot be removed from the seed/meta, and therefore, the meta is not a factor. The problem lies in the indicator, which appears abandoned upstream and needs to be patched for this to work without crashing. This is, of course, assuming the autopkgtests are correct because, as you said, Tim, you couldn't reproduce in a lxd vm. ** Changed in: ubuntucinnamon-meta (Ubuntu) Status: New => Invalid ** Changed in: ubuntucinnamon-meta (Ubuntu) Assignee: Joshua Peisach (itzswirlz) => (unassigned) ** Changed in: indicator-keyboard (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/2036764 Title: indicator keyboard crashes when upgrading from lunar->mantic on ubuntu cinnamon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/2036764/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036764] Re: indicator keyboard crashes when upgrading from lunar->mantic on ubuntu cinnamon
** Also affects: ubuntucinnamon-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/2036764 Title: indicator keyboard crashes when upgrading from lunar->mantic on ubuntu cinnamon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/2036764/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036764] [NEW] indicator keyboard crashes when upgrading from lunar->mantic on ubuntu cinnamon
Public bug reported: Log snippet: JournalErrors: Sep 20 14:52:28 autopkgtest kernel: kauditd_printk_skb: 164 callbacks suppressed Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in message bus configuration file Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in message bus configuration file Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file Sep 20 14:52:32 autopkgtest systemd[1]: multipathd.socket: Socket service multipathd.service already active, refusing. Sep 20 14:52:32 autopkgtest systemd[1]: Failed to listen on multipathd.socket - multipathd control socket. Sep 20 14:52:34 autopkgtest kernel: kauditd_printk_skb: 205 callbacks suppressed Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file Sep 20 14:52:35 autopkgtest indicator-keybo[747]: g_variant_ref: assertion 'value != NULL' failed Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv4: There appears to be another mDNS responder running, or previously systemd-resolved crashed with some outstanding transfers. Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv6: There appears to be another mDNS responder running, or previously systemd-resolved crashed with some outstanding transfers. Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Main process exited, code=dumped, status=11/SEGV Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Failed with result 'core-dump'. Sep 20 14:52:38 autopkgtest indicator-keybo[27565]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Sep 20 14:52:42 autopkgtest kernel: kauditd_printk_skb: 193 callbacks suppressed Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file Sep 20 14:52:42 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file Package: indicator-keyboard 0.0.0+19.10.20220803-0ubuntu1 I'll attach the full upgrade log. This bug was discovered by using autopkgtest. You can reproduce by installing autopkgtest, auto-upgrade-testing and cloning auto-upgrade- testing-specifications and running this from the parent directory: sudo --preserve-env=AUTOPKGTEST_APT_SOURCES_FILE python3 -m upgrade_testing.command_line -c auto-upgrade-testing- specifications/profiles/ubuntu-lunar-mantic-ubuntucinnamon- amd64_qemu.yaml --provision --results-dir /home/$USER/upgrade_cinnamon --adt-args=--timeout-factor=10 I'll attach the full logs below. I'm also trying to recreate using an lxd container ** Affects: indicator-keyboard (Ubuntu) Importance: Undecided Status: New ** Description changed: Log snippet: JournalErrors: - Sep 20 14:52:28 autopkgtest kernel: kauditd_printk_skb: 164 callbacks suppressed - Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file - Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in message bus configuration file - Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown username "polkitd" in message bus configuration file - Sep 20 14:52:32 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file - Sep 20 14:52:32 autopkgtest systemd[1]: multipathd.socket: Socket service multipathd.service already active, refusing. - Sep 20 14:52:32 autopkgtest systemd[1]: Failed to listen on multipathd.socket - multipathd control socket. - Sep 20 14:52:34 autopkgtest kernel: kauditd_printk_skb: 205 callbacks suppressed - Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file - Sep 20 14:52:34 autopkgtest dbus-daemon[415]: Unknown group "power" in message bus configuration file - Sep 20 14:52:35 autopkgtest indicator-keybo[747]: g_variant_ref: assertion 'value != NULL' failed - Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv4: There appears to be another mDNS responder running, or previously systemd-resolved crashed with some outstanding transfers. - Sep 20 14:52:36 autopkgtest systemd-resolved[27430]: mDNS-IPv6: There appears to be another mDNS responder running, or previously systemd-resolved crashed with some outstanding transfers. - Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Main process exited, code=dumped, status=11/SEGV - Sep 20 14:52:38 autopkgtest systemd[653]: indicator-keyboard.service: Failed with result 'core-dump'. - Sep
[Bug 2036746] Re: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6990 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6990 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6990 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2036746 Title: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2036746/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036746] [NEW] CVE-2023-43090: avoid exposing window previews on lock screen via keyboard
*** This bug is a security vulnerability *** Public security bug reported: Security Impact --- Open windows can be viewed from the lock screen without unlocking the screen. Test Case - From upstream This is the broken case and should not happen: - Lock screen (e.g. Super+L) - Press PrtScn to open screenshot tool - Press V twice to toggle the screenshot tool from picture mode to video mode and then back to picture mode. (First bug: it should not be possible to enter video mode when the UI element is insensitive.) - Enter the window selection mode by clicking or pressing W - Now all of the user's windows may be viewed despite the session being locked. Initial Testing Done I built the package locally. I installed the updated packages on Ubuntu 23.04 and was no longer able to reproduce the failure case. Other Info -- I was unable to duplicate the failure with Ubuntu 22.04 LTS. GNOME Shell 42 (included in 22.04 LTS) was the first GNOME release with an embedded screenshot tool; previously it used gnome-screenshot. So older versions are definitely not affected. GNOME Shell 42 reached End of Life earlier this year, but it does not appear to be affected by this issue. This issue has been fixed for Ubuntu 23.10 with GNOME Shell 45.0 ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: gnome-shell (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Tags: lunar ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released ** Also affects: gnome-shell (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Lunar) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2036746 Title: CVE-2023-43090: avoid exposing window previews on lock screen via keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2036746/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036749] [NEW] Sudo gnome-terminal fails
Public bug reported: Can't launch a sudo version of gnome-terminal sudo gnome-terminal # Error constructing proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Failed to execute child process “dbus-launch” (No such file or directory) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-terminal 3.44.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Sep 20 08:48:31 2023 InstallationDate: Installed on 2023-09-01 (19 days ago) InstallationMedia: Ubuntu-Budgie 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-09-02T06:36:32.926571 ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2036749 Title: Sudo gnome-terminal fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2036749/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036751] [NEW] file-roller's show files doesn't go to file directory
Public bug reported: Clicking show files doesn't pull up the directory the files were extracted to. It opens home. ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2036751 Title: file-roller's show files doesn't go to file directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2036751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1574586] Re: Not able to rate/review snaps
** Project changed: snappy => snapd -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1574586 Title: Not able to rate/review snaps To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1574586/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1598667] Re: No snapd API for account registration / password reset
** Project changed: snappy => snapd -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1598667 Title: No snapd API for account registration / password reset To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1598667/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Changed in: linux Status: Unknown => New ** Changed in: xorg-server Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1555567] Re: [snaps] License information from the store not available
** Project changed: snappy => snapd -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/167 Title: [snaps] License information from the store not available To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/167/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036597] Re: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos))
No, the laptop had been up and running for some time there. Here's journalctl from 11:32: Sep 20 11:31:49 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:31:49 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:31:51 ThinkPad-P14s-Gen-3 kernel: audit: type=1400 audit(1695202311.035:244): apparmor="DENIED" operation="open" class="file" profile="snap.firefox.firefox" name="/etc/fstab" pid=6542 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 20 11:31:51 ThinkPad-P14s-Gen-3 dbus-daemon[1487]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.172' (uid=1000 pid=6542 comm="/snap/firefox/3145/usr/lib/firefox/firefox" label="snap.firefox.firefox (enforce)") Sep 20 11:31:51 ThinkPad-P14s-Gen-3 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Sep 20 11:31:51 ThinkPad-P14s-Gen-3 dbus-daemon[1487]: [system] Successfully activated service 'org.freedesktop.hostname1' Sep 20 11:31:51 ThinkPad-P14s-Gen-3 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Sep 20 11:31:51 ThinkPad-P14s-Gen-3 kernel: audit: type=1107 audit(1695202311.383:245): pid=1487 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.173" pid=6542 label="snap.firefox.firefox" peer_pid=7747 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=101 hostname=? addr=? terminal=?' Sep 20 11:31:51 ThinkPad-P14s-Gen-3 kernel: audit: type=1107 audit(1695202311.383:246): pid=1487 uid=101 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.173" pid=6542 label="snap.firefox.firefox" peer_pid=7747 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=101 hostname=? addr=? terminal=?' Sep 20 11:31:51 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:31:58 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:31:58 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:32:07 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:32:07 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:32:07 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:32:07 ThinkPad-P14s-Gen-3 gnome-shell[3636]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 20 11:32:08 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:32:08 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:32:15 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:32:15 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:32:15 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:32:15 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:32:15 ThinkPad-P14s-Gen-3 gnome-shell[3636]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 20 11:32:21 ThinkPad-P14s-Gen-3 dbus-daemon[3346]: [session uid=1000 pid=3346] Activating service name='org.gnome.Nautilus' requested by ':1.90' (uid=1000 pid=4310 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" label="unconfined") Sep 20 11:32:21 ThinkPad-P14s-Gen-3 systemd[1]: anacron.service - Run anacron jobs was skipped because of an unmet condition check (ConditionACPower=true). Sep 20 11:32:21 ThinkPad-P14s-Gen-3 nautilus[7855]: Connecting to org.freedesktop.Tracker3.Miner.Files Sep 20 11:32:21 ThinkPad-P14s-Gen-3 dbus-daemon[3346]: [session uid=1000 pid=3346] Successfully activated service 'org.gnome.Nautilus' Sep 20 11:32:21 ThinkPad-P14s-Gen-3 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Sep 20 11:32:21 ThinkPad-P14s-Gen-3 org.gnome.Nautilus[7855]: Initializing nautilus-dropbox 2019.02.14 Sep 20 11:32:21 ThinkPad-P14s-Gen-3 dbus-daemon[1487]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.175' (uid=1000 pid=7855 comm="/usr/bin/nautilus
[Bug 2036597] Re: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos))
The timestamp indicates those were created at 11:32, do you know what you did on the system around that time? is that when you turned the computer on/started the session? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/2036597 Title: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/2036597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036597] Re: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos))
It happened again: martin@ThinkPad-P14s-Gen-3:~$ ls -l total 2992 drwxrwxr-x 3 martin martin4096 Sep 18 12:44 bin drwxr-xr-x 2 martin martin4096 Sep 19 13:48 Desktop drwxr-xr-x 19 martin martin4096 Sep 18 12:42 Documents drwxr-xr-x 4 martin martin4096 Sep 20 11:31 Downloads drwx-- 5 martin martin4096 Sep 19 14:56 Dropbox lrwxrwxrwx 1 martin martin 18 Sep 20 11:32 Music -> /home/martin/Music drwxrwxr-x 3 martin martin4096 Sep 19 15:10 Pictures lrwxrwxrwx 1 martin martin 19 Sep 20 11:32 Public -> /home/martin/Public drwxrwxr-x 3 martin martin4096 Sep 18 16:25 R -rw--- 1 martin martin 3027062 Sep 19 14:37 references.bib drwx-- 13 martin martin4096 Sep 19 13:56 snap lrwxrwxrwx 1 martin martin 22 Sep 20 11:32 Templates -> /home/martin/Templates lrwxrwxrwx 1 martin martin 19 Sep 20 11:32 Videos -> /home/martin/Videos but this time, .config/user-dirs.dirs is not changed, or the changes to correct I made before are still there, e.g., XDG_VIDEOS_DIR="$HOME/Videos". In fact, even though I changed the locale to en_DK, Settings still show the default en_US and locale seems to be a mix? martin@ThinkPad-P14s-Gen-3:~$ locale LANG=en_US.UTF-8 LANGUAGE=en_US:en LC_CTYPE="en_US.UTF-8" LC_NUMERIC=en_DK.UTF-8 LC_TIME=en_DK.UTF-8 LC_COLLATE="en_US.UTF-8" LC_MONETARY=en_DK.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=en_DK.UTF-8 LC_NAME=en_DK.UTF-8 LC_ADDRESS=en_DK.UTF-8 LC_TELEPHONE=en_DK.UTF-8 LC_MEASUREMENT=en_DK.UTF-8 LC_IDENTIFICATION=en_DK.UTF-8 LC_ALL= ** Attachment added: "Screenshot from 2023-09-20 12-11-42.png" https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/2036597/+attachment/5702323/+files/Screenshot%20from%202023-09-20%2012-11-42.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/2036597 Title: Strange permissions and/or links to default directories in home folder (Music, Pictures, Public, Templates and Videos)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/2036597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1429584] Re: gnome-terminal doesn't set $COLORTERM from 3.14 onwards
I've just found a link to this ancient bugreport in https://en.wikipedia.org/wiki/ANSI_escape_code. Unfortunately this discussion here contains two confusing mistakes. I'd like to correct them for future reference purposes. No action necessary, other than perhaps closing this bug, and fixing the Wiki page (I might do the latter). In comment #1 I was mistakenly talking about the COLOR*FGBG* variable, not about COLOR*TERM*. This can be seen by the link pointing to an issue that actually (correctly) talks about COLORFGBG, and from my words over here not making any sense. I probably made the same mistake in #4 too (but I'm not sure). I must have had that other environment variable in mind and talked about that, incorrectly typing the name of the one this bugreport was talking about, not realizing the difference. My bad, apologies for this mistake. (I'm not editing the earlier posts here because then the thread will make even less sense.) COLORTERM used to be set to the terminal emulator's name, "gnome- terminal" in our case. This was removed from GNOME Terminal version 3.14, released in 2014, the commit is linked from comment #2 here. This version of GNOME Terminal (or rather, the corresponding VTE version) also implemented truecolor support. Around this time the de facto use of this environment variable across various terminal emulators shifted for it to contain the "truecolor" string if the emulator supported this feature. So VTE 0.44, corresponding to GNOME Terminal 3.20, released in 2016 brought back this environment variable with the new value in https://github.com/GNOME/vte/commit/1dea919b9aa4b55e2c5c07bf2022769cbac365b5. Since the setting now occurs in VTE rather than GNOME Terminal, it is set in all VTE-based emulators. It has stayed ever since and is likely to stay as long as this variable is in widespread use. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1429584 Title: gnome-terminal doesn't set $COLORTERM from 3.14 onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1429584/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2861 https://gitlab.freedesktop.org/drm/amd/-/issues/2861 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/2861 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
I have more questions than answers now... * It looks like source_gnome-shell.py already attaches journalctl output, so why didn't it here? * data/general-hooks/generic.py also attaches journal errors, so why didn't it here? * Do we really want all Ubuntu bug reports to have journal data that might be sensitive? * Can we compress system logs before attaching them? * Why is ubuntu.py source maintained in debian/patches/Add-general- hooks.patch instead of a standalone file? * What's the criteria for going in ubuntu.py vs upstream https://github.com/canonical/apport ? It all seems a little too hard right now. I have other things I need to be doing instead of learning apport and Python. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
