[Bug 2063445] [NEW] GIMP crashes on close in noble arm64
Public bug reported: On the Ubuntu Desktop for Raspberry Pi (arm64) under noble, GIMP is reliably crashing when closing the application with unsaved changes, and selecting "Discard Changes". Steps to reproduce: * sudo apt install gimp * Open GIMP with an image (right click image in Files, Open With..., select GIMP) * Make some changes to the image (scribble over it) * Close the application * Select Discard Changes * GIMP Crash Debug appears I'll attach the bug information from crash debug window ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gimp-crash.txt" https://bugs.launchpad.net/bugs/2063445/+attachment/5770223/+files/gimp-crash.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/2063445 Title: GIMP crashes on close in noble arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2063445/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060730] Re: totem cannot install codecs via packagekit
Sorry, I should give a bit more context on this issue to clarify things. The test for this issue comes from the ISO tests for the Ubuntu Desktop for Raspberry Pi images. The test intends to check whether a fresh install can play a video "out of the box". The video used in the test is https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 which is downloaded and opened normally. The video deliberately uses a codec that isn't seeded and installed by default (but is a commonly used format) in the expectation that totem will guide the user through installing the necessary bits (which it used to back in groovy, but doesn't since -- incidentally the reason this wasn't noticed in jammy is because it failed to even open the video at that point, but that's now been fixed). Seeding gstreamer1.0-packagekit is probably fine (the whole of gstreamer's in main). Seeding gnome-software is likely not (given we're using snap-store for software delivery currently). Is app-center intended to fill that gap in future? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2060730 Title: totem cannot install codecs via packagekit To manage notifications about this bug go to: https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037017] Re: Sharing tab hangs gnome-control-center
Failed to reproduce on noble beta images; marking invalid as that's two failures now. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037017 Title: Sharing tab hangs gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060730] Re: totem cannot install codecs via packagekit
Adding affects packagekit as I've no idea if this is totem's fault or packagekit's. ** Also affects: packagekit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2060730 Title: totem cannot install codecs via packagekit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2060730/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060730] [NEW] totem cannot install codecs via packagekit
Public bug reported: While attempting to play a video on Ubuntu noble desktop for raspberry pi, totem attempts to locate a package for the H.264 codec but cannot find a service providing org.freedesktop.PackageKit. This is strange given that packagekit is installed, provides packagekit.service, which declares that it provides that name over DBus. Specifically, the following is output by totem: ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder) ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main (H.264 (Main Profile) decoder) ** Message: 21:13:39.414: PackageKit: xid = 0 ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit) ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main Profile) decoder ** Message: 21:13:39.414: PackageKit: ignoring field named level ** Message: 21:13:39.414: PackageKit: ignoring field named profile ** Message: 21:13:39.414: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit) ** Message: 21:13:39.434: PackageKit: Did not install codec: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PackageKit was not provided by any .service files ** Message: 21:13:39.441: No installation candidate for missing plugins found. The packagekit.service is defined as: $ systemctl cat packagekit.service # /usr/lib/systemd/system/packagekit.service [Unit] Description=PackageKit Daemon # PK doesn't know how to do anything on ostree-managed systems; # currently the design is to have dedicated daemons like # eos-updater and rpm-ostree, and gnome-software talks to those. ConditionPathExists=!/run/ostree-booted Wants=network-online.target [Service] Type=dbus BusName=org.freedesktop.PackageKit User=root ExecStart=/usr/libexec/packagekitd And just to demonstrate packagekit is actually running: $ systemctl status packagekit.service ● packagekit.service - PackageKit Daemon Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static) Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s ago Main PID: 1565 (packagekitd) Tasks: 4 (limit: 3864) Memory: 6.2M (peak: 6.7M) CPU: 180ms CGroup: /system.slice/packagekit.service └─1565 /usr/libexec/packagekitd Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - PackageKit Daemon... Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - PackageKit Daemon. ** Affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2060730 Title: totem cannot install codecs via packagekit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2060730/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2060679] [NEW] No icons for gtk4 applications under noble
Public bug reported: While testing the Ubuntu noble (24.04) desktop for Raspberry Pi beta, I noticed that all GTK4 applications appear to be missing various icons. All lack the minimize / maximize / close icons (which are left as three empty circles on the window), and others lack icons within the windows, e.g. on various controls like radio buttons, or folder icons in nautilus. GTK3 applications appear unaffected. I'll attach some screenshots demonstrating the issue. ** Affects: gtk4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2060679 Title: No icons for gtk4 applications under noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2060679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037017] Re: Sharing tab hangs gnome-control-center
Failed to reproduce this on the jammy .4 images during ISO testing. Possibility it's either fixed or only occurs on later versions. Will attempt to reproduce on mantic later, if I've got the time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037017 Title: Sharing tab hangs gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2044382] [NEW] Quassel opens "another" icon under Gnome
Public bug reported: I'm unsure if this is a bug in quassel, or in the gnome dock itself. Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the left bar results in the pinned icon appearing "idle" (not running), and a second icon appearing below those that are pinned which apparently represents the running quassel instance. Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) runs *another* instance of quassel rather than switching to the running instance. The "extra" icon also cannot be pinned (and occasionally strange "copies" of it are left lying around if one tries to drag it to the pinned icon locations). This may be because quassel is a Qt based application, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), hence why I'm unsure this is an issue in quassel or in the gnome dock. I'll attach a screenshot demonstrating the issue. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Affects: quassel (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2023-11-23 13-42-51.png" https://bugs.launchpad.net/bugs/2044382/+attachment/5722734/+files/Screenshot%20from%202023-11-23%2013-42-51.png ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Description changed: - I'm unsure if this is a bug in quassel, or in gnome itself. Under Ubuntu - 23.10 (mantic), running Quassel from a pinned icon on the left bar - results in the pinned icon appearing "idle" (not running), and a second - icon appearing below those that are pinned which apparently represents - the running quassel instance. + I'm unsure if this is a bug in quassel, or in the gnome dock itself. + Under Ubuntu 23.10 (mantic), running Quassel from a pinned icon on the + left bar results in the pinned icon appearing "idle" (not running), and + a second icon appearing below those that are pinned which apparently + represents the running quassel instance. Pressing the idle quassel icon (or pressing the Super+4 shortcut for it) runs *another* instance of quassel rather than switching to the running instance. The "extra" icon also cannot be pinned (and occasionally strange "copies" of it are left lying around if one tries to drag it to the pinned icon locations). This may be because quassel is a Qt based application, but I also run KeepassXC (another Qt application) without such issues (other than unusual window borders and icons which appear on both applications), - hence why I'm unsure this is an issue in quassel or in gnome. I'll - attach a screenshot demonstrating the issue. + hence why I'm unsure this is an issue in quassel or in the gnome dock. + I'll attach a screenshot demonstrating the issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2044382 Title: Quassel opens "another" icon under Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2044382/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
This has been fixed for a couple of releases now (since lunar I believe), and if I recall correctly the issue was indeed the wpe backend mentioned in comment 17. That would suggest this should be "invalid" for gtk and yelp, and "fix released" for webkit2gtk. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879137] Re: The snap-store is using hundreds of MiBs of RAM.
This appears to be partially fixed under Ubuntu 23.10. While the application (when running) still eats a few hundred meg of RAM, it does release that when closed, as opposed to hanging around persistently. Given apt usually eats over a hundred meg when processing the archive index, it's probably reasonable for a a graphical application processing a similar archive and including all the icons and pretty graphics to gobble a few hundred meg. However, it should definitely relinquish that memory when not in operation, which now appears to be the case. In other words, my major objection (that it grabbed this RAM even when not in use), appears to be addressed. However, that's not the subject line of the bug; should this be closed / revised? Are others still encountering issues with the store on mantic? -- 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/1879137 Title: The snap-store is using hundreds of MiBs of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1879137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2007160] Re: Image properties does nothing in lunar
This looks to be working under mantic now; image properties pane appears with resolution and (if present) EXIF details. -- 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/2007160 Title: Image properties does nothing in lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2007160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037017] Re: Sharing tab hangs gnome-control-center
Argh! During ISO testing I thought I'd just quickly check this still didn't occur on a Pi 5... only to find it did, this time. I've still not encountered a Pi 4 where it *didn't* occur, but I wonder if this is a race-condition somewhere and just more prone to occurring on the slower 4. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037017 Title: Sharing tab hangs gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037017] Re: Sharing tab hangs gnome-control-center
Oh, one other note: no output in the journal during the hang; I'm afraid the only info is from the backtrace. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037017 Title: Sharing tab hangs gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037017] Re: Sharing tab hangs gnome-control-center
Additional observation: I re-tested this on the Pi 4 and 5. The hang only occurs on the Pi 4 and 400, but does *not* occur on the 5 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037017 Title: Sharing tab hangs gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037017] Re: Sharing tab hangs gnome-control-center
Attaching backtrace from gdb with debug symbols ** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+attachment/5708243/+files/gdb.txt ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037017 Title: Sharing tab hangs gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998782] Re: Totem unable to play video on Raspberry Pi: "could not initialize OpenGL support"
With the correct video codecs installed (for the particular test video I was using, I needed gstreamer1.0-plugins-bad which pulls in libav), this now works on the mantic final images, under both the Pi 4 and 5. ** Changed in: totem (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1998782 Title: Totem unable to play video on Raspberry Pi: "could not initialize OpenGL support" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1998782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037017] [NEW] Sharing tab hangs gnome-control-center
Public bug reported: On the Ubuntu Desktop for Raspberry Pi current Mantic beta images (with gnome-control-center version 1.45.0-1ubuntu1), on a Raspberry Pi 4B, switching to the "Sharing" tab hangs the application (presenting the Force Quit / Wait overlay prompt). Worse, re-launching the application simply re-opens the "Sharing" tab resulting in another hang. A workaround for now is to launch the application from the command-line, forcing initial selection of a different tab, e.g. "gnome-control-center info-overview". Launching the application from the command line with "gnome-control- center sharing" also causes the hang, but unfortunately there's no additional console output to shed any light on the situation. I'm not sure if this is Pi specific (haven't attempted it on any other platforms yet). ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: raspi-image rls-mm-incoming ** Tags added: raspi-image rls-mm-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037017 Title: Sharing tab hangs gnome-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037017/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037016] [NEW] Firefox redundantly appears twice in Default Apps
Public bug reported: Under the current Mantic beta, Firefox redundantly appears twice in the Web and Photos drop-downs under the "Default Apps" tab of gnome-control- center. ** Affects: gnome-control-center (Ubuntu) Importance: Low Status: New ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037016 Title: Firefox redundantly appears twice in Default Apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2025308] [NEW] package appstream 0.15.2-2 failed to install/upgrade: installed appstream package post-installation script subprocess returned error exit status 1
Public bug reported: unknown ProblemType: Package DistroRelease: Ubuntu 22.04 Package: appstream 0.15.2-2 Uname: Linux 5.10.104-tegra aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Jun 28 21:47:23 2023 ErrorMessage: installed appstream package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: appstream Title: package appstream 0.15.2-2 failed to install/upgrade: installed appstream package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-06-29 (0 days ago) ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/2025308 Title: package appstream 0.15.2-2 failed to install/upgrade: installed appstream package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/2025308/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2001904] Re: URLs fail to launch in Firefox
*** This bug is a duplicate of bug 1794064 *** https://bugs.launchpad.net/bugs/1794064 ** This bug has been marked a duplicate of bug 1794064 Clicking a hyperlink in a PDF fails to open it if the default browser is a snap -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2001904 Title: URLs fail to launch in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2017097] Re: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed
Also verified on a Pi 4 (mutter 44.1-0ubuntu1); video playback is smooth again! -- 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/2017097 Title: [raspi] GNOME Shell 44.0 runs at 30 FPS unless the CPU is being stressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2017097/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
I'd say this is effectively "Fix Released" at this point in that on lunar (and kinetic? Sorry, I forgot to re-test this before upgrading the old drive), Totem now fails to play the video with "could not initialize OpenGL support" which is the "fix" implemented upstream (and reflected by the upstream tracker). LP: #1998782 has been filed with this new message so I'll point to that one in the ISO tracker for the current lunar beta. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 861493] Re: evince doesn't print duplex on duplex-able printers
Still an issue on the current LTS (jammy, 22.04), and the current devel series (lunar, 23.04) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/861493 Title: evince doesn't print duplex on duplex-able printers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/861493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
FYI, in case anyone wants to add their monitor (and whether it succeeds or fails at suspending with the Ubuntu raspi kernel) to this ticket: $ cp /sys/devices/platform/gpu/drm/card1/card1-HDMI-A-1/edid hdmi0-monitor.edid $ cp /sys/devices/platform/gpu/drm/card1/card1-HDMI-A-2/edid hdmi1-monitor.edid As you may guess, hdmi0-monitor.edid is the EDID for the monitor plugged into HDMI0 (the socket closest to the USB-C power port on the Pi4, and the socket closest to the uSD slot on the Pi400), whilst hdmi1-monitor.edid is the EDID for the monitor plugged into HDMI1. If you have no monitor connected to a socket, you'll still get an EDID file but it'll be 0 bytes. A valid EDID file should be 256 bytes (or more? I forget the details of EDID, but there's some extended blocks I vaguely recall). Upload valid EDID files to https://www.edid.tv/edid/upload/binary/ if you wish (bear in mind this will share the serial # of your monitor but I don't think there's any particular security risk in that), and add the link here along with whether or not this particular monitor suspends successfully or not. -- 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/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
Fails with this monitor: https://www.edid.tv/edid/2267/ -- 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/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
I'm still seeing this behaviour (precisely as described at the top: fades to black, switches off, then switches on to black a second or two later) with the lunar daily image and the bootstrap 6.2 kernel, so it'll likely be an issue in lunar. I'll flash a jammy and kinetic image to a card in a bit and try and re- confirm them there but kinetic certainly exhibited the issue last week before I upgraded my devel system. In case this is monitor specific, the monitor I'm using is a Benq GW2270H running at 1080p. -- 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/1998716 Title: [raspi] Ubuntu 22.10 does not turn off monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2007160] [NEW] Image properties does nothing in lunar
Public bug reported: When testing the current lunar (23.04) pre-installed desktop image for the Raspberry Pi, I attempted to retrieve the properties of a captured JPEG from nautilus: * Right click on a JPEG image * Select "Properties" item at the bottom * Click on the "Image Properties" link at the bottom of the dialog that opens However, nothing happens when clicking on the link. I presume this is meant to go to a page listing the details that nautilus used to display (resolution, etc). I tested with a couple of different JPEGs that display their properties correctly under jammy and kinetic. I'm happy to provide test images if required, but I don't think it's specific to the JPEGs I'm using. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/2007160 Title: Image properties does nothing in lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2007160/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825593] Re: Display scale not remembered when X11 Fractional Scaling is enabled
I can confirm this bug remains even without Fractional Scaling is enabled, and also while using Wayland not X11 In my case I set monitor 1 as primary monitor (primary display port), monitor 3 (secondary display port) with orientation "Portrait Left", after reboot/logout/system update that required reboot, login window appears on monitor 3 in landscape mode, likewise after login monitor 3 is in landscape mode and the primary monitor (has the dock) |--|--| | OS Name | Ubuntu 22.04.1 LTS | | OS Type | 64-bit | | Gnome Version | 42.5 | | Windowing System | Wayland | | Graphics | Mesa Intel® HD Graphics 530 (SKL GT2) | | Processor | Intel® Core™ i5-6500 CPU @ 3.20GHz × 4 | | Hardware Model | HP HP EliteDesk 800 G3 DM 65W | -- 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/1825593 Title: Display scale not remembered when X11 Fractional Scaling is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1852860] Re: Display settings not saved across sessions if fractional scaling is used
*** This bug is a duplicate of bug 1825593 *** https://bugs.launchpad.net/bugs/1825593 I disagree that this is a Duplicate of bug #1825593, because this happens for me without Fractional Scaling is enabled, and while using Wayland not X11 In my case I set monitor 1 as primary monitor (primary display port), monitor 3 (secondary display port) with orientation "Portrait Left", after reboot/logout/system update that required reboot, login window appears on monitor 3 in landscape mode, likewise after login monitor 3 is in landscape mode and the primary monitor (has the dock) |--|--| | OS Name | Ubuntu 22.04.1 LTS | | OS Type | 64-bit | | Gnome Version | 42.5 | | Windowing System | Wayland | | Graphics | Mesa Intel® HD Graphics 530 (SKL GT2) | | Processor | Intel® Core™ i5-6500 CPU @ 3.20GHz × 4 | | Hardware Model | HP HP EliteDesk 800 G3 DM 65W | -- 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/1852860 Title: Display settings not saved across sessions if fractional scaling is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2001904] Re: URLs fail to launch in Firefox
Adding a trivial test PDF ** Attachment added: "test_pdf.pdf" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+attachment/5639334/+files/test_pdf.pdf -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2001904 Title: URLs fail to launch in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2001904] [NEW] URLs fail to launch in Firefox
Public bug reported: Opening a PDF under evince, then clicking an https: link within the PDF fails to open the link in Firefox. On the command line, evince reports: $ evince test.pdf env: ‘/snap/bin/firefox’: Permission denied In dmesg, the following message appears each time the link is clicked: [ 1366.891145] audit: type=1400 audit(1672910889.559:286): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/bin/snap" pid=14698 comm="env" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 This may be related to (or a regression of?) LP: #964510 as it's clearly aa related, but I don't think it's a direct duplicate given the audit log is rather different. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2001904 Title: URLs fail to launch in Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2001904/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 195798] Re: Nautilus: Impossible to change case of filename/extension in Windows Share
I am running into something similar. I changing case in a filename doesn't accept changes. ie: renaming "text.txt" to "Test.txt" doesn't work. The only thing I can do is rename "text.txt" to "test2.txt" then rename "test2.txt" to "Test.txt" -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/195798 Title: Nautilus: Impossible to change case of filename/extension in Windows Share To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/195798/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1993174] [NEW] disabling fractional-scaling picks wrong screen size
Public bug reported: During testing of the kinetic desktop on a Raspberry Pi, I came across an odd behaviour with the fractional scaling settings. I also replicated the issue on the PC image (so it's not Pi specific), and on the jammy desktop (so it's a fairly long-standing bug). Reproduction steps: 1. Open Gnome control center 2. Under Screen Display: enable Fractional Scaling, then select 125% as the Scale, then click Apply 3. Accept the changes 4. Under Screen Display: select 100% as the Scale, disable Fractional Scaling, then click Apply (please note both changes must be done in one "Apply" step; if done separately the bug does not manifest) 5. Accept the changes At this point the screen should be partially filled in the top left, as if the correct resolution is picked, but the wrong screen size. On the Pi the remaining screen area was blank, on the PC it was filled with random garbage. Interestingly, if you select "Revert" in the final step things *don't* revert and instead I wound up with a 100% scale, full-screen desktop (on both the Pi and the PC). That may be a separate bug but either way it appears there's some broken interaction between fractional scaling, the selection of the scale, and the application (and reversion) of settings. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1993174 Title: disabling fractional-scaling picks wrong screen size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1993174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989615] Re: gnome-shell crashed with SIGABRT in assertion [libmutter:ERROR:../src/backends/meta-monitor-manager.c:1690:get_connector_type_name: code should not be reached]
** Information type changed from Private to Public -- 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/1989615 Title: gnome-shell crashed with SIGABRT in assertion [libmutter:ERROR:../src/backends/meta-monitor- manager.c:1690:get_connector_type_name: code should not be reached] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1989615/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
** Description changed: - On the hirsute Pi desktop, under a wayland session with the "full" KMS - overlay enabled, and "kms-modifiers" present in the - org.gnome.mutter/experimental-features, the body of a window containing - an HTML renderer (e.g. help text or a login page) displays corruption. + On the jammy Pi desktop, under a wayland session, the body of a window + containing an HTML renderer (e.g. help text or a login page) displays + corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
@seb128 yes, the following command line plays (for at least 20 seconds -- I didn't watch the whole thing) happily under totem: MESA_GL_VERSION_OVERRIDE=3.3 totem big_buck_bunny_720p_surround.mp4 So the issue is simply that the pi's GL driver only goes up to 2.1, and/or that GTK doesn't accept GL<3.0 (my vague understanding of the graphics situation on the pi is that the GLES driver has (had?) rather better support than GL, but that Vulkan was the real focus of development efforts -- https://www.raspberrypi.com/news/vulkan-update- version-1-1-conformance-for-raspberry-pi-4/ has some more info on that). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964601] Re: I have no processor!
Sorry, hadn't refreshed this page and didn't notice your comment 9 before posting mine! With the override in place it looks like things work properly: $ MESA_GL_VERSION_OVERRIDE=3.3 /usr/libexec/gnome-control-center-print-renderer V3D 4.2 And looking at the upstream ticket you linked makes a lot of sense: the Pi's GL driver only goes up to 2.1: $ glxinfo | grep "GL version string" OpenGL version string: 2.1 Mesa 22.0.1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1964601 Title: I have no processor! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964601] Re: I have no processor!
I've done a bit of debugging on this; wound up tweaking the code
mentioned in comment 8 above to return g_strdup("NULL context") instead
of return NULL and with this in place, gnome-control-center-print-
renderer (and indeed the "Graphics" field of the control center) both
return "NULL context" so at least we know that's what's going on.
I also hacked up an openGL demo to print the result of
glGetString(GL_RENDERER) and apparently we should be getting "V3D 4.2"
when everything's working correctly. Unfortunately I've no idea why
gdk_window_create_gl_context isn't working on the pi desktop.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1964601
Title:
I have no processor!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964601] Re: I have no processor!
gnome-control-center-printer-renderer produces no output on the raspi. The debug output from gnome-control-center is: (gnome-control-center:3171): GLib-GIO-DEBUG: 14:47:50.015: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ (gnome-control-center:3171): dconf-DEBUG: 14:47:50.015: watch_fast: "/org/gnome/desktop/interface/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.016: watch_fast: "/org/gnome/desktop/peripherals/mouse/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.016: watch_fast: "/org/gnome/desktop/sound/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.016: watch_fast: "/org/gnome/desktop/privacy/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.016: watch_fast: "/org/gnome/desktop/wm/preferences/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.017: watch_fast: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.017: watch_fast: "/org/gnome/desktop/a11y/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.017: watch_fast: "/org/gnome/desktop/a11y/interface/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.019: watch_established: "/org/gnome/desktop/interface/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.019: watch_established: "/org/gnome/desktop/peripherals/mouse/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.019: watch_established: "/org/gnome/desktop/sound/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.020: watch_established: "/org/gnome/desktop/privacy/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.020: watch_established: "/org/gnome/desktop/wm/preferences/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.020: watch_established: "/org/gnome/settings-daemon/plugins/xsettings/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.020: watch_established: "/org/gnome/desktop/a11y/" (establishing: 1) (gnome-control-center:3171): dconf-DEBUG: 14:47:50.020: watch_established: "/org/gnome/desktop/a11y/interface/" (establishing: 1) (gnome-control-center:3171): GLib-DEBUG: 14:47:50.141: unsetenv() is not thread-safe and should not be used after threads are created (gnome-control-center:3171): GLib-GIO-DEBUG: 14:47:50.162: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’ (gnome-control-center:3171): cc-object-storage-DEBUG: 14:47:51.608: Initializing object storage (gnome-control-center:3171): GLib-DEBUG: 14:47:51.611: unsetenv() is not thread-safe and should not be used after threads are created (gnome-control-center:3171): Gtk-DEBUG: 14:47:51.612: Connecting to session manager (gnome-control-center:3171): dconf-DEBUG: 14:47:51.714: watch_fast: "/org/gnome/control-center/" (establishing: 0, active: 0) (gnome-control-center:3171): dconf-DEBUG: 14:47:52.664: watch_established: "/org/gnome/control-center/" (establishing: 1) (gnome-control-center:3171): network-cc-panel-DEBUG: 14:47:52.694: Monitoring NetworkManager for Wi-Fi devices (gnome-control-center:3171): cc-object-storage-DEBUG: 14:47:52.723: Adding object NMClient (CcObjectStorage::nm-client → 0xffaee090) to the storage (gnome-control-center:3171): network-cc-panel-DEBUG: 14:47:52.723: Wi-Fi panel visible: yes (gnome-control-center:3171): wacom-cc-panel-DEBUG: 14:47:52.751: Wacom panel visible: no (gnome-control-center:3171): cc-object-storage-DEBUG: 14:47:52.758: Adding object MMManager (CcObjectStorage::mm-manager → 0xffb298c0) to the storage (gnome-control-center:3171): cc-wwan-panel-DEBUG: 14:47:52.758: Monitoring ModemManager for WWAN devices (gnome-control-center:3171): cc-wwan-panel-DEBUG: 14:47:52.758: WWAN panel visible: no (gnome-control-center:3171): dconf-DEBUG: 14:47:52.778: change_fast (gnome-control-center:3171): info-overview-cc-panel-DEBUG: 14:47:57.744: Getting renderer from helper for GPU 'Unknown Graphics Controller' (gnome-control-center:3171): info-overview-cc-panel-DEBUG: 14:47:57.796: About to launch '/usr/libexec/gnome-control-center-print-renderer' (gnome-control-center:3171): info-overview-cc-panel-DEBUG: 14:47:57.796: With environment: (gnome-control-center:3171): info-overview-cc-panel-DEBUG: 14:47:57.797: DRI_PRIME = platform-fec0_v3d (gnome-control-center:3171): cc-window-DEBUG: 14:47:58.842: Time to open panel 'About': 6.063688s ** (gnome-control-center:3171): DEBUG: 14:47:59.261: No extra argument (gnome-control-center:3171): diagnostics-cc-panel-DEBUG: 14:47:59.284: ABRT vanished (gnome-control-center:3171): dconf-DEBUG: 14:48:02.202: unwatch_fast: "/org/gnome/control-center/" (active: 1, establishing: 0) (gnome-control-center:3171):
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
Reported issue with flatpak (under arm64) upstream: https://gitlab.gnome.org/GNOME/totem/-/issues/509#note_1468424 (after re-testing just to confirm that the issue still occurred). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964601] Re: I have no processor!
I'm attaching the full outputs as a tarball (just in case they're useful) but here's the pertinent bits too: $ tail -n 13 /proc/cpuinfo processor : 3 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 Hardware: BCM2835 Revision: c03131 Serial : 1000acbea889 Model : Raspberry Pi 400 Rev 1.1 It looks like "Model" would be the most appropriate field to report here. Looking at the upstream bug it's querying a "Model name" field (which appears per-CPU on my PC) but not a "Model" field in the final section (though on my PC there is no final section, just the per-CPU sections). On glxinfo: $ glxinfo | grep 'OpenGL renderer' OpenGL renderer string: V3D 4.2 I'm attaching two cases of the udisksctl output. The first (udisk_sd.log) is from a "typical" installation of Ubuntu Desktop for Pi on an SD card. The second (udisk_usb.log) is from the same Pi booting from a USB-attached SSD (which is a fairly common configuration for booting the desktop). Should I post these bits upstream too? ** Attachment added: "1964601.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+attachment/5593907/+files/1964601.tar.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1964601 Title: I have no processor! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
@Samuel that fix is for PCs which is a different bug (LP: #1971463); this bug is about totem on the Pi desktop images (or, I'm beginning to suspect, arm64 more generally). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
An additional data point; I noted in the linked gitlab bug a couple of messages noting that "it works with the flatpak". Out of curiosity (as to whether this might be a well and truly arm64 specific problem), I tried the flatpak on the pi desktop and: it's got exactly the same problem (same behaviour, same message, etc). So I'm currently thinking this is *not* distro-specific to Ubuntu, but I'm certainly considering that this is possibly arch-specific to arm64 (or possibly just non- amd64? Not sure). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
Unfortunately we've tried "G_DEBUG=fatal_warnings" before (you suggested it back in comment:4) but I did manage to figure out a couple of things since last time: The crash I originally observed (back in comment:6) only occurs on the very first run of totem. All subsequent runs (even after a reboot) fail to crash (which makes me suspect the crash is a result of something that's missing on that first run ... maybe something that gets written to the user's home-dir or cache or something? I should try deleting ~/.cache and see what happens). All subsequent runs still display the issue described in the bug (that the video won't play with "the specified movie could not be found" error) but don't actually crash. That also makes me suspect that the crash might not be related to the issue of the movie not playing. Nonetheless, once I had the ability to reliably reproduce the crash (albeit with the annoyance of having to re-flash the card each time), I did manage to get totem to crash with the totem-dbgsym (and libtotem0-dbgsym, and libgstreamer1.0-0-dbgsym, and basically any other vaguely related -dbgsym I could think of) installed. Unfortunately the results were ... not exactly useful: https://errors.ubuntu.com/oops/7cd5149e-d1db-11ec-9a6d-fa163e55efd0 Here's another OOPS report which *did* get a partial stacktrace, but unfortunately I'd forgotten to install the -dbgsym package on this one (was kicking myself after realizing I had to re-flash the card *again*!): https://errors.ubuntu.com/oops/58aa5662-d1cf-11ec-8c2d-fa163e993415 Sorry these probably aren't much use in shedding any further light on the problem! On the other hand, the fact the crash doesn't occur after the first run makes me think that perhaps I'm barking up the wrong tree here (that the crash is distinct from the failure to play the video file). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879137] Re: The snap-store is using hundreds of MiBs of RAM.
It appears to take 250MB resident (according to top) on my Raspberry Pi 400 even when the software is "closed". On a machine with 4GB, this is pretty significant. Even more so considering we now support the desktop on Pis with as little as 2GB of RAM. -- 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/1879137 Title: The snap-store is using hundreds of MiBs of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1879137/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
I've now installed the -dbg packages in an attempt to get a proper stacktrace (as requested by seb128); unfortunately try as I might I've been unable to re-create the crash I experienced a couple of weeks ago. Totem still fails to play anything (same message, same debug output as previously reported), but no crashes. One thing I have noted, after retrying on a freshly flashed card is that using gst-launch directly fails initially, complaining that it's lacking the AAC codec (perhaps I should amend the ISO test case to use an OGG instead -- though I have a feeling this *used* to work, maybe it prompted to install the necessary codec). Still, installing gstreamer1.0-libav fixes this and gst-launch then happily plays the video (and audio), whilst totem still fails with the aforementioned message. I'll keep trying to get a proper stacktrace, but at this point I'd say it's likely unrelated to totem's failure to play the video (given there's evidently no issue with gstreamer itself playing the video otherwise, and totem still fails to play the video even when no crash occurs). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: Totem unable to play video: "The specified movie could not be found"
@floe -- thanks for the extra info! Unfortunately I'm not sure this is a gstreamer issue (or more precisely, there may well be a gstreamer issue on amd64, but it doesn't appear to be the case on arm64 with the Pi Desktop image). gstreamer1.0-vaapi isn't seeded on the Pi Desktop images, and indeed running your gst-launch reproducer plays the video happily with no mention of gstvaapi in the console output. Just in case it's useful, here's the output I saw: GST_DEBUG=3 gst-launch-1.0 playbin uri=file:///$HOME/big_buck_bunny_720p_surround.mp4 Setting pipeline to PAUSED ... 0:00:00.045303856 31845 0xf25f9240 WARN basesrc gstbasesrc.c:3688:gst_base_src_start_complete: pad not activated yet 0:00:00.046280739 31845 0xf25f9240 WARN basesrc gstbasesrc.c:3688:gst_base_src_start_complete: pad not activated yet Pipeline is PREROLLING ... 0:00:00.096946452 31845 0xf260eb60 WARN qtdemux qtdemux.c:3121:qtdemux_parse_trex: failed to find fragment defaults for stream 1 0:00:00.097408468 31845 0xf260eb60 WARN qtdemux qtdemux.c:3121:qtdemux_parse_trex: failed to find fragment defaults for stream 2 Redistribute latency... Redistribute latency... Redistribute latency... Redistribute latency... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstPulseSinkClock Redistribute latency... About 9 seconds in I closed the window (which was correctly playing the video, and audio), which produced the output: 0:00:09.474384373 31845 0x902bc120 WARN xvimagesink xvimagesink.c:568:gst_xv_image_sink_handle_xevents: error: Output window was closed ERROR: from element /GstPlayBin:playbin0/GstPlaySink:playsink/GstBin:vbin/GstXvImageSink:xvimagesink0: Output window was closed Additional debug info: ../sys/xvimage/xvimagesink.c(568): gst_xv_image_sink_handle_xevents (): /GstPlayBin:playbin0/GstPlaySink:playsink/GstBin:vbin/GstXvImageSink:xvimagesink0 Execution ended after 0:00:09.137470426 Setting pipeline to NULL ... 0:00:09.477803649 31845 0x800609e0 WARN xvimagesink xvimagesink.c:1045:gst_xv_image_sink_show_frame: could not output image - no window 0:00:09.478389497 31845 0xf260eb60 WARN qtdemux qtdemux.c:6747:gst_qtdemux_loop: error: Internal data stream error. 0:00:09.478468497 31845 0xf260eb60 WARN qtdemux qtdemux.c:6747:gst_qtdemux_loop: error: streaming stopped, reason error (-5) ERROR: from element /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0/GstQTDemux:qtdemux0: Internal data stream error. Additional debug info: ../gst/isomp4/qtdemux.c(6747): gst_qtdemux_loop (): /GstPlayBin:playbin0/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0/GstQTDemux:qtdemux0: streaming stopped, reason error (-5) Freeing pipeline ... Admittedly, this was on my usual Pi desktop; I'll try it on an entirely fresh card in a bit (as I need to do that to respond to seb128's request for a proper stacktrace), but I suspect the result will be similar. Still, it may be worth opening a separate bug for the gstvaapi case? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: Totem unable to play video: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: totem unable to play bbb mp4: "The specified movie could not be found"
** Changed in: totem (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: totem unable to play bbb mp4: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: totem unable to play bbb mp4: "The specified movie could not be found"
ylist_add_one_mrl ():
big_buck_bunny_720p_surround.mp4 (null) (null) (null) 0 false
(totem:38425): Totem-DEBUG: 11:13:08.719: Adding popup busy for reason opening
file
(totem:38425): Totem-DEBUG: 11:13:08.721: emitting PlaybackStatus change
(totem:38425): Totem-DEBUG: 11:13:08.721: Not enabling offline save, as
'file:///home/dave/big_buck_bunny_720p_surround.mp4' already in $HOME, and
native
(totem:38425): Totem-DEBUG: 11:13:08.723: TotemGrilo: Pausing videos
thumbnailing
(totem:38425): Totem-DEBUG: 11:13:08.727: Removing popup busy for reason
opening file
(totem:38425): Totem-DEBUG: 11:13:08.727: Will hide popup soon
(totem:38425): Totem-DEBUG: 11:13:08.728: emitting PlaybackStatus change
(totem:38425): Totem-DEBUG: 11:13:08.735: Removing popup busy for reason paused
(totem:38425): Totem-DEBUG: 11:13:08.735: Will hide popup soon
(totem:38425): Totem-DEBUG: 11:13:08.735: successfully acquired dbus name
org.mpris.MediaPlayer2.totem
(totem:38425): Totem-DEBUG: 11:13:08.753: emitting PlaybackStatus change
(totem:38425): dconf-DEBUG: 11:13:11.427: unwatch_fast: "/org/gnome/Totem/"
(active: 4, establishing: 0)
(totem:38425): dconf-DEBUG: 11:13:11.430: unwatch_fast:
"/org/gnome/desktop/lockdown/" (active: 2, establishing: 0)
(totem:38425): dconf-DEBUG: 11:13:11.437: unwatch_fast: "/org/gnome/Totem/"
(active: 3, establishing: 0)
(totem:38425): Totem-DEBUG: 11:13:11.482: Removing popup busy for reason
buffering
(totem:38425): Totem-DEBUG: 11:13:11.482: Will hide popup soon
(totem:38425): dconf-DEBUG: 11:13:11.599: unwatch_fast:
"/org/gnome/desktop/thumbnailers/" (active: 1, establishing: 0)
Secondly, the *first* time I ran totem, it additionally reported:
double free or corruption (out)
Aborted (core dumped)
Unfortunately, I wasn't capturing stderr at that point and no subsequent
run reported the same crash. apport obviously popped up on that core
dump and I opted to report the error, which can found under the
following OOPS:
https://errors.ubuntu.com/oops/927e463e-c15b-11ec-8afa-fa163e993415
I should also note (anecdotally) that the source_totem.py hook in apport
also reported an error in syslog:
Apr 21 11:12:33 miss-piggy update-notifier-crash[37540]: ERROR: hook
/usr/share/apport/package-hooks/source_totem.py crashed:
Apr 21 11:12:33 miss-piggy update-notifier-crash[37540]: Traceback (most recent
call last):
Apr 21 11:12:33 miss-piggy update-notifier-crash[37540]: File
"/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook
Apr 21 11:12:33 miss-piggy update-notifier-crash[37540]:
symb['add_info'](report, ui)
Apr 21 11:12:33 miss-piggy update-notifier-crash[37540]: File
"/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
Apr 21 11:12:33 miss-piggy update-notifier-crash[37540]: response =
ui.choice("How would you describe the issue?", ["The totem interface
is not working correctly", "No sound is being played", "Some audio files or
videos are not being played correctly"], False)
Apr 21 11:12:33 miss-piggy update-notifier-crash[37540]: AttributeError:
'NoneType' object has no attribute 'choice'
Running with "G_DEBUG=fatal_warnings" produced no differences to the
prior runs (no additional messages, no crash, etc.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1969512
Title:
totem unable to play bbb mp4: "The specified movie could not be found"
To manage notifications about this bug go to:
https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] Re: totem unable to play bbb mp4: "The specified movie could not be found"
We download and try to play locally (see item 12 in http://iso.qa.ubuntu.com/qatracker/milestones/432/builds/247134/testcases/1747/results for an example). I'll try and get some DEBUG output this morning (I can state it's definitely not crashing though; the error message simply appears and totem remains open, without playing anything, until closed). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: totem unable to play bbb mp4: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969512] [NEW] totem unable to play bbb mp4: "The specified movie could not be found"
Public bug reported: As part of our ISO testing for the Pi desktop, we attempt to play https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4 with the shipped totem video player. Unfortunately, on the current Jammy image, totem simply reports "The specified movie could not be found" when attempting to play the file (the exit code is 0, no other errors are reported at the command line). I've attempted to install a few gstreamer codecs, in case that might've been the issue (this was necessary on some older versions), but neither gstreamer1.0-plugins-ugly, nor gstreamer1.0-libav made any difference. Just to ensure the video file was intact and playable, I then installed vlc from the archive, which played the video happily. ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1969512 Title: totem unable to play bbb mp4: "The specified movie could not be found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1969512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
Another quick update: in recent days we've gone from "blank white space" back to "incorrect stride corruption" in all documented cases (embedded browsers, help windows, MiniBrowser, etc). I note in the dpkg logs, libglx-mesa0 got updated a few days ago, but unfortunately I'm unsure exactly when the change occurred so this is speculation on my part. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
@seb128 interesting, I've just tried this on a fully updated jammy image on a Pi 400 and /usr/lib/aarch64-linux-gnu/webkit2gtk-4.0/MiniBrowser starts quite happily; browser window opens and ... nothing but blank white space within the body of the window. All the controls in the toolbar are fine and it's definitely able to navigate to pages, and after a bit of experimentation I'm reasonably convinced it's all "working correctly" with the one exception that nothing actually shows up (but the mouse cursor changes shape in all the right places, etc). @vanvugt: in case it's of any use, MiniBrowser produced the following console output: ** (MiniBrowser:149058): WARNING **: 21:30:51.512: GDK is not able to create a GL context, falling back to glReadPixels (slow!): Unable to create a GL context Cannot create EGL context: invalid display (last error: EGL_SUCCESS) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
This still seems to be an issue on the current Ubuntu Pi Jammy images although it presents in a different manner: instead of an incorrect- stride corruption, the embedded browser (in the same places: help windows, or the login entries for online accounts) simply appears blank white. However, if the mouse cursor is moved across the blank white content of the window, the cursor shape changes to indicate text entry fields or clickable links indicating that the browser is likely operating correctly but failing to render correctly. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964601] [NEW] I have no processor!
Public bug reported: At least according to gnome-control-center anyway. Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi 4B), selecting Settings, then the "About" page shows that gnome-control- center thinks the processor is "", the graphics are "unknown", and apparently so is the disk capacity! I admit it's a trivial thing, but it's been this way since at least hirsute, and it'd be nice to see something vaguely sane in there at some point :) ** Affects: gnome-control-center (Ubuntu) Importance: Low Status: New ** Tags: raspi-image ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1964601/+attachment/5567967/+files/gnome-contol-center.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1964601 Title: I have no processor! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922353] Re: Overview sometimes fails to appear or disappear fully when Ubuntu Dock is loaded
I am impacted by this bug. Ubuntu 21.04/Wayland. Only the Dash to Panel desktop extension is enabled. Problem started after upgrading from 20.10 to 21.04. -- 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/1922353 Title: Overview sometimes fails to appear or disappear fully when Ubuntu Dock is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1924251] [NEW] Embedded browser display corruption under Wayland on Pi desktop
Public bug reported: On the hirsute Pi desktop, under a wayland session with the "full" KMS overlay enabled, and "kms-modifiers" present in the org.gnome.mutter /experimental-features, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. ** Affects: mutter (Ubuntu) Importance: Undecided Assignee: Daniel van Vugt (vanvugt) Status: New ** Tags: hirsute raspi raspi-gfx ** Attachment added: "Screenshot from 2021-04-15 10-07-46.png" https://bugs.launchpad.net/bugs/1924251/+attachment/5488263/+files/Screenshot%20from%202021-04-15%2010-07-46.png -- 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/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1924251/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913742] Re: Fractional scaling: bottom half of screen black on external monitor disconnect
Apologies: I never saw this response asking for more information. I did solve the problem, as it turns out; it was Gromit-MPX, a tool I use allow me to draw on the screen. The problem disappears when I restarted Gromit-MPX. -- 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/1913742 Title: Fractional scaling: bottom half of screen black on external monitor disconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1913742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922298] [NEW] Activities panel on wrong display
Public bug reported: The activities panel is showing up on the wrong display. Selecting the "primary display" as 3 in the display settings puts the top bar on display 3 , but the activities bar on screen 2. Screenshot attached Similarly, selecting primary display = 2 then activities bar ends up on 1 primary display = 1 then activities bar ends up on 3 I'm hoping this is just an off by one error somewhere. I think gnome-shell is the correct package. Feel free to move to the correct package ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 1 17:16:30 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-12 (293 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2021-04-01 17-05-08.png" https://bugs.launchpad.net/bugs/1922298/+attachment/5483269/+files/Screenshot%20from%202021-04-01%2017-05-08.png -- 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/1922298 Title: Activities panel on wrong display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922298/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913742] [NEW] Fractional scaling: bottom half of screen black on external monitor disconnect
Public bug reported: I'm using Ubuntu 20.04.1, on a Lenovo Thinkpad T14s. I've got fractional scaling enabled (125%) with Gnome. I regularly plug into an external monitor with an HDMI connection, and run both screens (the external monitor and the built-in laptop one) side-by-side. With that setup, I don't use fractional scaling, because my main external monitor is easier to read. When I unplug the HDMI cord from my external monitor to go back to working on the laptop, sometimes the bottom half of the laptop screen goes black. The mouse cursor is still visible if I move it to that region, but nothing is visible in the entire lower portion of my screen. I've been running 20.04 on this laptop since last August, and it didn't used to be a problem. The problem first occurred perhaps a month or two ago, but was rare and sporadic. It has been happening more and more frequently, and is now at the point that most of the time this problem occurs. Once I have unplugged the cable and I'm stuck with a black bottom half of the screen, I can resolve it by disabling fractional scaling, but of course, that disables fractional scaling. At that point, any attempts to reenable fractional scaling either bring the black region back again, or start causing all kinds of other instabilities. Restarting Gnome at this point contributes to the mess. The only stable workaround I've found (apart from rebooting) is to plug the laptop back into the external monitor again, switch the configuration to single display mode, and then unplug. This works but is of course cumbersome. Is there more information I can supply that would be useful? ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1913742 Title: Fractional scaling: bottom half of screen black on external monitor disconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1913742/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
I already did:- https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897632 but it has been marked as a duplicate of https://bugs.launchpad.net/bugs/1883886 Also there is a Libre Office relevant bug https://bugs.documentfoundation.org/show_bug.cgi?id=127782 ** Bug watch added: Document Foundation Bugzilla #127782 https://bugs.documentfoundation.org/show_bug.cgi?id=127782 -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Just reporting this fix has NOT fixed the Libre Office Print Dialoge Box issue mentioned in comment #86 -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
I have raised a bug with LibreOffice which I believe may be related. https://bugs.documentfoundation.org/show_bug.cgi?id=137142 To summarise, with a scaling factor of 1.25 and GNOME Desktop Environment Universal Access accessibility Large Print set to on I am unable to see fully the LibreOffice Print dialogue. Setting Large Print to off cures the problem BUT my low vision means I really need to squint. Setting the scaling factor to 1.0 also succeeds but rather bizarrely also automatically switches off GNOME Desktop Environment Universal Access accessibility Large Print. Is all this related? And will the forthcoming fix correct everything including the LibreOffice and Universal Access accessibility Large Print? ** Bug watch added: Document Foundation Bugzilla #137142 https://bugs.documentfoundation.org/show_bug.cgi?id=137142 -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1891815] Re: Multi-seat stopped working in Ubuntu 20.04
We've confirmed the same issue. The issue wasn't present in Bionic, and isn't present in GDM 3.36.3 on Fedora 32. Does anyone know if this fix would appear in 20.04 LTS or only in 20.10? We're currently rebuilding our computing labs for remote access (Apache Guacamole -> tigervnc -> XDMCP) and are eager to upgrade from 18.04 to 20.04 (LTS to LTS). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1891815 Title: Multi-seat stopped working in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1891815/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards
I have low vision and I thought my vision was just deteriorating! I happened to boot into 18.04 and even after updating it I noticed my fonts in 18.04 were much better on the same hardware. It is most noticeable in the pull-down panels. In 20.04, sure enough if I change the scaling factor from 1.25 to 1.30 the font size is increased and if I then decrease back to 1.25 the font size remains at the higher setting. This high setting does not withstand a re-boot. I am left to conclude, reducing the scaling factor no longer works and at boot, no notice is taken of the setting in place at the last power off. I am using Dash-to-Panel Gnome Extension, Intel HD Graphics, Gnome 3.36.3 X11 Windowing System 20.04.1 LTS -- 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/1892440 Title: [focal] [nvidia] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04 with nvidia cards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1734541] Re: encrypted home-directory is not unmounted on logout
Note this was also reported in bug 1637710 back in 2016 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1734541 Title: encrypted home-directory is not unmounted on logout To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1734541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890613] [NEW] Gnome unresponsive JS ERROR: TypeError: windowActor is null
Public bug reported: gnome-shell becomes unresponsive after about 1 day. I'm able to interact with the window that had focus when the problem appears (in this case it was Chrome), but I'm unable to select or otherwise interact with other windows, the shell, dock, or indicators. The logs are spammed with gnome-shell[2916]: JS ERROR: TypeError: windowActor is null#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 This looks similar to but different enough from https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774 I was using the i915 driver when this happened if that makes any difference ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 09:08:32 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-12 (54 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed -- 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/1890613 Title: Gnome unresponsive JS ERROR: TypeError: windowActor is null To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1890613/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793007] Re: gnome-disk-image-mounter creates loopback device but it is not mounted automatically
This bug is still valid in Ubuntu 20.04. The utility creates the loopback device OK, but the mount sometimes works and sometimes silently fails. This utility has no debug or verbosity option, so there's no way for the end user to give useful information about the failure. That's something that could be remedied first if the devs have no idea why it fails. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1793007 Title: gnome-disk-image-mounter creates loopback device but it is not mounted automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1793007/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873403] Re: [nvidia] Screen turns off when trying to set some fractional scaling values
I have a possible related problem with Ubuntu-mate 20.04. I adjusted my mouse pointer size (Dell Inspiron 7995 with Nvidia GTX 960M graphics) the screen went black mouse pointer frozen, 10 seconds later the login screen appears. If I log back in again the screen is black and I'm stuck in an endless loop. -- 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/1873403 Title: [nvidia] Screen turns off when trying to set some fractional scaling values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876681] Re: gnome-shell crashes when extension bingwallpa...@ineffable-gmail.com is loaded
Bug reported as advised https://github.com/neffo/bing-wallpaper-gnome-extension/issues/70#issuecomment-624599291 ** Bug watch added: github.com/neffo/bing-wallpaper-gnome-extension/issues #70 https://github.com/neffo/bing-wallpaper-gnome-extension/issues/70 -- 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/1876681 Title: gnome-shell crashes when extension bingwallpa...@ineffable-gmail.com is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876681] Re: gnome-shell crashes when extension bingwallpa...@ineffable-gmail.com is loaded
Reinstalled 'bingwallpa...@ineffable-gmail.com' and as expected on a reboot an "Ubuntu has experienced an internal error" box was once more generated. Ran ubuntu-bug _usr_bin_gnome-shell.1000.crash obtained from /var/crash and all it did was produce another/same(?) "Ubuntu has experienced an internal error" box. The terminal screen is frozen at this point and a Ctrl-C produces this:- ^CTraceback (most recent call last): File "/usr/share/apport/apport-gtk", line 597, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 719, in run_argv self.run_crash(self.options.crash_file, False) File "/usr/lib/python3/dist-packages/apport/ui.py", line 313, in run_crash response = self.ui_present_report_details(allowed_to_report) File "/usr/share/apport/apport-gtk", line 380, in ui_present_report_details Gtk.main() File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 1632, in main return _Gtk_main(*args, **kwargs) File "/usr/lib/python3.8/contextlib.py", line 120, in __exit__ next(self.gen) File "/usr/lib/python3/dist-packages/gi/_ossighelper.py", line 251, in register_sigint_fallback signal.default_int_handler(signal.SIGINT, None) KeyboardInterrupt Tried . https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id but all I get is I do not have permission to see. I have looked briefly at https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 and I am now at a loss as to exactly what to do. -- 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/1876681 Title: gnome-shell crashes when extension bingwallpa...@ineffable-gmail.com is loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876681] Re: gnome-shell crashes on boot
As requested, all extensions quoted uninstalled and all fine. Still fine after a number of reboots. Decided to re-install each extension one by one. Tried 'bingwallpa...@ineffable-gmail.com' first and once more a similar crash and as before system was still usable. Uninstalled once more and system was fine once more. I then proceeded to reinstall these extensions in this sequence, each time followed by shutdown and reboot. All, no problems. 'dash-to-pa...@jderose9.github.com', 'clipboard-indica...@tudmotu.com', 'applications-overview-tooltip@RaphaelRochet' I have decided I can Live without the others and could even live without the successful ones if necessary. If I should be reporting these extension bugs elsewhere, particularly the BingWallpaper one then please advise. Happy for this reported bug to be zapped! -- 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/1876681 Title: gnome-shell crashes on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876681] [NEW] gnome-shell crashes on boot
Public bug reported: Had a few gnome-shell problems since 20.04 install. Usually, just did the auto send thing, but this time thought it best to do a manual report. Not much I can add though. I do see things like these in the reports from time to time Invalid core dump: BFD: warning:/tmp/apport_core_7buvs9st is truncated:expected core file size >=582705152, found:11411 $ /tmp$ ls -alt app* -rw--- 1 dave dave 1114112 May 4 09:32 apport_core_7buvs9st $ file apport_core_7buvs9st apport_core_7buvs9st: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/gnome-shell', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000 $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 4 09:35:03 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-27 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "apport_core_7buvs9st" https://bugs.launchpad.net/bugs/1876681/+attachment/5366041/+files/apport_core_7buvs9st -- 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/1876681 Title: gnome-shell crashes on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863400] Re: gnome-shell reports problem on boot
Happened again. Bug did not seem to submit report once more. Screenshot as per comment #2 Report was produced which I managed to see the details but sending report did not return a bug ID. See this from terminal where I carried out action 1a in comment #3. Still no bug ID. dave@dave-ThinkPad-T410:~$ ls -alt /var/crash total 21384 -rw-r- 1 gdm whoopsie 21887221 Mar 2 23:32 _usr_bin_gnome-shell.121.crash drwxrwsrwt 2 root whoopsie 4096 Mar 2 23:32 . drwxr-xr-x 14 root root 4096 Jul 25 2018 .. dave@dave-ThinkPad-T410:~$ sudo ubuntu-bug /var/crash/_usr_bin_gnome-shell.121.crash [sudo] password for dave: dave@dave-ThinkPad-T410:~$ ls -alt /var/crash total 21596 drwxrwsrwt 2 root whoopsie 4096 Mar 3 07:22 . -rw--- 1 whoopsie whoopsie0 Mar 3 07:22 _usr_bin_gnome-shell.121.uploaded -rw-r--r-- 1 root whoopsie0 Mar 3 07:22 _usr_bin_gnome-shell.121.upload -rw-r- 1 gdm whoopsie 22105281 Mar 3 07:18 _usr_bin_gnome-shell.121.crash drwxr-xr-x 14 root root 4096 Jul 25 2018 .. dave@dave-ThinkPad-T410:~$ See this from terminal where I carried out action 1b in comment #3. No form was automatically opened in web browser (I use Firefox) dave@dave-ThinkPad-T410:~$ sudo apport-cli /var/crash/_usr_bin_gnome-shell.121.crash [sudo] password for dave: *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (22.1 MB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): S dave@dave-ThinkPad-T410:~$ Carried out Step 2 in comment #3 but it was only showing the same one from 14th Feb 2020 as per comment #9 Although I carry out full updates and upgrades regularly I will once more carry out the instructions in comment #10. I will retain the contents of /var/crash for now and only report back here if necessary. -- 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/1863400 Title: gnome-shell reports problem on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863400] Re: gnome-shell reports problem on boot
Moeez In future, whenever you get a bug and you know the name of package causing the problem use this command inside a terminal session making sure you first have an internet conection:- ubuntu-bug "packagename" So in my case I ran "ubuntu-bug gnome-shell" and it then does the business, goes into your default browser opening a launchpad window/tab (you may need to login). You can then provide some narrative as to what happened which becomes the bug description that you can see at the top of the page of this bug, for example. For now though, given the updates/upgrade you have performed there is no need just yet for further action. If a bug hunter like Daniel comes in he will advise anything different. You might find /var/crash still contains some files in which case it would be safe to delete them - see comment#12 above. No disrespect, but please keep correspondence on bug reports to a minimum - this is not a forum as such. You should be able to correspond direct to me without adding to this bug report and maybe I could direct you to a few places where you can chat and ask questions to your hearts content. -- 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/1863400 Title: gnome-shell reports problem on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863400] Re: gnome-shell reports problem on boot
Moeez I am sure it would help the bug hunters if you cross-referenced your reported bug ID in here. The more data they have the better. So far,I have hadno related issues and no replication since performing sudo apt update sudo apt full-upgrade Shutdown Rebooted But I suppose it might happen again any time. -- 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/1863400 Title: gnome-shell reports problem on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863400] Re: gnome-shell reports problem on boot
/var/crash has now been emptied device shutdown and rebooted no problems reported at boot /var/crash remains empty -- 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/1863400 Title: gnome-shell reports problem on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863400] Re: gnome-shell reports problem on boot
Performed sudo apt update sudo apt full-upgrade Shutdown Rebooted Performed sudo ubuntu-bug /var/crash/_usr_bin_gnome-shell.121.crash Report produced and sent. Went to https://errors.ubuntu.com/user/ID where the ID was the one obtained from sudo more /var/lib/whoopsie/whoopsie-id Then same as comment #7 and the same link produced as per comment #9 -- 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/1863400 Title: gnome-shell reports problem on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863400] Re: gnome-shell reports problem on boot
Here you go https://errors.ubuntu.com/oops/14394820-5158-11ea-a66d-fa163ee63de6 Thank You. -- 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/1863400 Title: gnome-shell reports problem on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863400] Re: gnome-shell reports problem on boot
Complied with comment #6 and step 2 in comment #3. A web page is produced with all the bugs I have raised from this device, and yes the latest gnome one is there. But clicking on it takes me to webpage which says I have not got permission to see it and asks me to complete a form, which I have done. The form asks me for my email address etc and once completed it says they will be in touch. That was over 1 hour ago - not heard a thing. I do have the URL of the bug I could click on. Would that be secure to paste here? -- 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/1863400 Title: gnome-shell reports problem on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863400] Re: gnome-shell reports problem on boot
Cant find bug id - but was uploade 07:35 UTC according to /var/crash -- 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/1863400 Title: gnome-shell reports problem on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863400] Re: gnome-shell reports problem on boot
Step 1 worked " sudo ubuntu-bug /var/crash/_usr_bin_gnome-shell.121.crash" and report sent - trying to find bug id. -- 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/1863400 Title: gnome-shell reports problem on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863400] Re: gnome-shell reports problem on boot
** Description changed: Problem reported at boot but does not seem to collect data and send, just does nothing. + See attached screenshot of window. Still able to use laptop. This file exists in /var/crash -rw-r- 1 gdm whoopsie 21900809 Feb 14 22:01 _usr_bin_gnome-shell.121.crash The time of this file must have been at last shutdown which did take a little longer than usual. Description: Ubuntu 18.04.4 LTS Release: 18.04 gnome-shell: - Installed: 3.28.4-0ubuntu18.04.3 - Candidate: 3.28.4-0ubuntu18.04.3 - Version table: - *** 3.28.4-0ubuntu18.04.3 500 - 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages - 100 /var/lib/dpkg/status - 3.28.3+git20190124-0ubuntu18.04.2 500 - 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages - 3.28.1-0ubuntu2 500 - 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + Installed: 3.28.4-0ubuntu18.04.3 + Candidate: 3.28.4-0ubuntu18.04.3 + Version table: + *** 3.28.4-0ubuntu18.04.3 500 + 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages + 100 /var/lib/dpkg/status + 3.28.3+git20190124-0ubuntu18.04.2 500 + 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages + 3.28.1-0ubuntu2 500 + 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 15 06:21:53 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-17 (454 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Attachment added: "Screenshot of window on boot" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+attachment/5328366/+files/Screenshot%20from%202020-02-15%2010-06-14.png -- 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/1863400 Title: gnome-shell reports problem on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863400] [NEW] gnome-shell reports problem on boot
Public bug reported: Problem reported at boot but does not seem to collect data and send, just does nothing. Still able to use laptop. This file exists in /var/crash -rw-r- 1 gdm whoopsie 21900809 Feb 14 22:01 _usr_bin_gnome-shell.121.crash The time of this file must have been at last shutdown which did take a little longer than usual. Description:Ubuntu 18.04.4 LTS Release:18.04 gnome-shell: Installed: 3.28.4-0ubuntu18.04.3 Candidate: 3.28.4-0ubuntu18.04.3 Version table: *** 3.28.4-0ubuntu18.04.3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.3+git20190124-0ubuntu18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.1-0ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 15 06:21:53 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-17 (454 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1863400 Title: gnome-shell reports problem on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 387957] Re: Improve Save As Dialog Box (focus issues)
Agreed. yaztromo identified the frustration well. I've been living with this in Mint Cinnamon for years, and still can't seem to get used to it. Thanks for the Alt+N shortcut (works in English/US version). Maybe that'll help me stop cursing at my computer every time I save a file. Returning the focus to the filename after using the mouse (or touchpad) to navigate into a folder would be ideal. The only reason to use the find is when input is solely from keyboard. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/387957 Title: Improve Save As Dialog Box (focus issues) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/387957/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1841646] Re: White text on white background for HTML e-mail
The short term fix can be to downgrade the two required libraries. sudo apt install libjavascriptcoregtk-4.0-18=2.20.1-1 libwebkit2gtk-4.0-37=2.20.1-1 Evolution works again and I have blocked updating of those two for now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1841646 Title: White text on white background for HTML e-mail To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1841646/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853753] Re: The toolbar can not be edited
I am not able to see where I would change -ui to give an "edit" icon to the existing toolbar. Code: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1853753 Title: The toolbar can not be edited To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1853753/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853753] Re: Top Bar can't be changed
Here is a screen shot of the top of Evolution in full screen mode. Notice that there are no icons or the ability to right-click the mouse to reveal a "menu change,add or remove" capability like Thunderbird. ** Attachment added: "Screenshot from 2019-11-26 16-01-57.png" https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1853753/+attachment/5308027/+files/Screenshot%20from%202019-11-26%2016-01-57.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1853753 Title: Top Bar can't be changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1853753/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1853753] [NEW] Top Bar can't be changed
Public bug reported: After install and establishing email accounts, the top bar can't be changed. There is no "edit" function to add, delete or move the various icons. Kernel: 4.15.0-69-generic x86_64 bits: 64 Desktop: Gnome 3.28.4 Distro: Ubuntu 18.04.3 LTS ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1853753 Title: Top Bar can't be changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1853753/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
Enabling this plugin is the easiest way to work around this issue in bionic. https://extensions.gnome.org/extension/1328/disable-workspace-switch-animation/ That being said what is the status of a real fix? -- 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/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1812527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]
** Tags added: indeed -- 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/1812527 Title: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1812527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
I'm struggling with 18.10: Lots of bad things happen but this is worst: This
happens every time more than 2 applications are open.
{code}
Unrecoverable failure in required component org.gnome.Shell.desktop
{code}
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1764417
Title:
Unrecoverable failure in required component
org.gnome.SettingsDaemon.Color.desktop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1736011] Re: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Pr
+1 MacbookAir 6,2 Issue is present with all extensions disabled (minus user themes). In addition to the delay after login, there's this weird behaviour: after waking from sleep induced by closing the lid, the desktop shows for a while before going back to the greeter screen. Not sure if this is related (maybe others can corroborate?), but it's there more often than not. I recently switched from laptop-mode-tools to TLP which seems to exacerbate this behaviour. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1736011 Title: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1736011/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1770502] Re: Brasero hangs when burning cds
Affected me, clean install of Ubuntu-mate 18.04.1 LTS. Brasero would fail to burn Audio CD's. Thanks @Ronald, work around worked fine. ** Attachment added: "Brasero-session log for Audio CD burn failure" https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1770502/+attachment/5200208/+files/brasero-session.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1770502 Title: Brasero hangs when burning cds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1770502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784065] Re: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger
This workaround doesn't work for me... I have i386 architecture, so I changed the commands as follows: wget https://launchpad.net/ubuntu/+source/glib2.0/2.48.2-0ubuntu3/+build/15131276/+files/libglib2.0-0_2.48.2-0ubuntu3_i386.deb wget http://mirrors.kernel.org/ubuntu/pool/main/d/dpkg/dpkg_1.18.4ubuntu1_i386.deb ar -x dpkg_1.18.4ubuntu1_i386.deb tar -xzf data.tar.gz sudo ./usr/bin/dpkg -i libglib2.0-0_2.48.2-0ubuntu3_i386.deb everything appeared to process correctly, but when I run sudo apt-get -f install it fails with the same "interest-await" error as before. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784065 Title: upgrade from 14.04 to 16.04 fails due to `interest-await' in trigger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1784065/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1774932] Re: nautilus assert failure: malloc(): memory corruption (fast)
This is happening to me several times now on a daily basis. Each time I submit the crash report and each time within the report it says a duplicate of this bug report. How can I help resolve it. New install of 18.04 from about a month ago - all updates and upgrades installed. -- 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/1774932 Title: nautilus assert failure: malloc(): memory corruption (fast) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774932/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1662617] Re: gnome-calculator with transparent formula entry box
Calculator display showing bionic desktop capture in display area (no longer transparent) with overtyping and gridding in the number display. ** Attachment added: "calculator1.png" https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1662617/+attachment/5165425/+files/calculator1.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1662617 Title: gnome-calculator with transparent formula entry box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1662617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1662617] Re: gnome-calculator with transparent formula entry box
Calculator worked flawlessly in Advanced mode in 16.04 (and before). Upgrade to 18.04 and this bug appeared (the bionic desktop visible in the display window). Using the calculator produced overtyped characters and weird gridding between the numbers displayed (see attached). Switching from xim to ibus seems to have solved it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1662617 Title: gnome-calculator with transparent formula entry box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1662617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1680438] Re: gnome-calculator comes up with totally wrong answer
gnome has moved to gitlab. Corresponding bug is now https://gitlab.gnome.org/GNOME/gnome-calculator/issues/59 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1680438 Title: gnome-calculator comes up with totally wrong answer To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calculator/+bug/1680438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1565489] Re: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()
*** This bug is a duplicate of bug 927340 *** https://bugs.launchpad.net/bugs/927340 Any chance of a fix or workaround Yes, this IS a duplicate however every search result for this error lands on a DUPLICATE bug which references a PRIVATE bug which I cannot read. SO HOW am I supposed to "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"? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1565489 Title: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1565489/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
