[Bug 1905400] Re: nautilus segfault libgio-2.0.so.0.6600.1
*** This bug is a duplicate of bug 1820859 *** https://bugs.launchpad.net/bugs/1820859 Thanks and no I don't need the id, the report information indicates it's bug #1820859 ** This bug has been marked a duplicate of bug 1820859 nautilus --version segfaults in g_application_impl_get_dbus_object_path -- 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/1905400 Title: nautilus segfault libgio-2.0.so.0.6600.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905400] Re: nautilus segfault libgio-2.0.so.0.6600.1
*** This bug is a duplicate of bug 1820859 *** https://bugs.launchpad.net/bugs/1820859 Could you perhaps describe what you did to trigger the segfault and if you are able to trigger the problem again following some steps? -- 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/1905400 Title: nautilus segfault libgio-2.0.so.0.6600.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905842] Re: Bluetooth once turned off then it does'nt start agin
The Bluetooth menu item is *designed* to hide if turned off and you hadn't paired anything yet https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1426#note_912033 I'm not sure I agree with that design but it does mean it's not a bug. You will need to either: * Re-enable Bluetooth via Settings; or * Pair a Bluetooth device. ** Package changed: bluez (Ubuntu) => gnome-shell (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #1426 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1426 ** Changed in: gnome-shell (Ubuntu) Status: New => Won't 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/1905842 Title: Bluetooth once turned off then it does'nt start agin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905842/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905842] [NEW] Bluetooth once turned off then it does'nt start agin
You have been subscribed to a public bug: Bluetooth does'nt start once turned off. It only starts when I restart my system. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 27 12:43:08 2020 InstallationDate: Installed on 2020-10-29 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic root=UUID=cd634a09-ce20-463b-aa0a-8d92be8e0864 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2013 dmi.bios.release: 15.101 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.44 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 33.68 dmi.modalias: dmi:bvnInsyde:bvrF.65:bd02/05/2013:br15.101:efr33.68:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.44:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0: Type: Primary Bus: USB BD Address: 2C:D0:5A:58:29:47 ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:1289 acl:0 sco:0 events:108 errors:0 TX bytes:5027 acl:0 sco:0 commands:87 errors:0 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- Bluetooth once turned off then it does'nt start agin https://bugs.launchpad.net/bugs/1905842 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898910] Re: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgrou
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/1898910 Title: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898910/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
** Tags added: hirsute -- 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/1897765 Title: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
The fix is also in debian/3.38.1-3 from commit 72370b880c ** Also affects: gnome-shell (Debian) Importance: Undecided Status: New ** No longer affects: gnome-shell (Debian) -- 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/1897765 Title: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905825] Re: [SRU] Disable CRTCs when system becomes headless
** Tags added: focal groovy hirsute -- 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/1905825 Title: [SRU] Disable CRTCs when system becomes headless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905825] [NEW] [SRU] Disable CRTCs when system becomes headless
Public bug reported: [Impact] On new Intel SoCs, after all connectors are unplugged and the system becomes headless, it cannot detect monitor hotplug event from type-c port. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561 Based on "drm/i915 Intel GFX Driver, Hotplug" [1]: "Finally, the userspace is responsible for triggering a modeset upon receiving the hotplug uevent, disabling or enabling the crtc as needed." [Test] Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor back, monitor is blank. With the fix applied, the system can detect monitor again. [Where problems could occur] This fix disables CRTCs when there's no monitor, if driver has trouble dealing with it, we may see something break. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Affects: mutter (Ubuntu Groovy) Importance: Undecided Status: New ** Affects: mutter (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Focal) 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/1905825 Title: [SRU] Disable CRTCs when system becomes headless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723835] Re: Dock - Clicking icon doesn't minimize
** Bug watch added: github.com/micheleg/dash-to-dock/issues #365 https://github.com/micheleg/dash-to-dock/issues/365 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/365 Importance: Unknown Status: Unknown ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Triaged -- 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/1723835 Title: Dock - Clicking icon doesn't minimize To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1723835/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-40 fixed-upstream ** Tags removed: fixed-in-40 ** Tags added: fixed-in-gnome-shell-40 -- 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/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905759] Re: gnome-shell crashed with SIGABRT in GI_raise()
*** This bug is a duplicate of bug 1886059 *** https://bugs.launchpad.net/bugs/1886059 Thanks. At least two of those are bug 1886059. So please help us to debug that one if you can. ** This bug has been marked a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] -- 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/1905759 Title: gnome-shell crashed with SIGABRT in GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1905759] Re: gnome-shell crashed with SIGABRT in GI_raise()
Hello, Thank you very much! My apologies for attaching the crash file - I hadn't realized this might be problematic. I followed what you indicated (particularly #2) and found the following links: https://errors.ubuntu.com/oops/2f0e2248-3008-11eb-8c9b-fa163e983629 https://errors.ubuntu.com/oops/21ec9802-3008-11eb-b997-fa163e102db1 https://errors.ubuntu.com/oops/5fdb36f4-2f3c-11eb-8677-fa163ee63de6 I think I may have erroneously send multiple of the same crash reports - my apologies if this was the case. Please let me know if there is anything else I might provide. Thanks, Daniel On Thu, Nov 26, 2020 at 9:15 PM Daniel van Vugt <1905...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. > > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a security > risk for yourself. > > > ** Tags added: groovy > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1905759 > > Title: > gnome-shell crashed with SIGABRT in GI_raise() > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Description: Ubuntu 20.10 > Release: 20.10 > > In the middle of work screen will randomly glitch green then revert to > the login screen - behaviour with both Wayland and not Wayland. > Apport.log shows: > > ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: called for pid 2318, > signal 6, core limit 0, dump mode 1 > ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: executable: > /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") > ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: debug: session gdbus > call: (true,) > > ERROR: apport (pid 11042) Thu Nov 26 11:51:51 2020: wrote report > /var/crash/_usr_bin_gnome-shell.1000.crash > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905759/+subscriptions > -- Candidate for Bachelors of Science University of Waterloo -- 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/1905759 Title: gnome-shell crashed with SIGABRT in GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905774] Re: gnome shell logout/crash
*** This bug is a duplicate of bug 1898005 *** https://bugs.launchpad.net/bugs/1898005 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1898005, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- desktop-icons (Ubuntu) ** This bug has been marked a duplicate of bug 1898005 gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() -- 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/1905774 Title: gnome shell logout/crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1905774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905759] Re: gnome-shell crashed with SIGABRT in GI_raise()
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: groovy ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1905759 Title: gnome-shell crashed with SIGABRT in GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905400] Re: nautilus segfault libgio-2.0.so.0.6600.1
Hi Sebastien, As requested, you can find the apport report here "https://errors.ubuntu.com/oops/0f82c2e1-3053-11eb-b9cb-fa163e102db1; Do you also need my Whoopsie-id ? Best regards, -- 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/1905400 Title: nautilus segfault libgio-2.0.so.0.6600.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905400/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1830422] Re: Shell boxpointer menus don't have scroll buttons when they exceed the screen height
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: diodon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1830422 Title: Shell boxpointer menus don't have scroll buttons when they exceed the screen height To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diodon/+bug/1830422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1830422] Re: Shell boxpointer menus don't have scroll buttons when they exceed the screen height
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1830422 Title: Shell boxpointer menus don't have scroll buttons when they exceed the screen height To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diodon/+bug/1830422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905754] Re: When gnome-shell shows a long error, it doesn't scroll and show the whole error
*** This bug is a duplicate of bug 1830422 *** https://bugs.launchpad.net/bugs/1830422 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1830422, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- appindicator (Ubuntu) ** This bug has been marked a duplicate of bug 1830422 Shell boxpointer menus don't have scroll buttons when they exceed the screen height -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1905754 Title: When gnome-shell shows a long error, it doesn't scroll and show the whole error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1905754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905802] Re: gnome-shell crashed with SIGSEGV in _clutter_actor_stop_transitions() from clutter_actor_remove_child_internal() from clutter_actor_dispose() from g_object_run_dispose() from clutter
Just noticed this crash is super-prolific on bionic right now. Over 150K instances just in the past month!? ** Summary changed: - /usr/bin/gnome-shell:11:_clutter_actor_stop_transitions:clutter_actor_remove_child_internal:clutter_actor_dispose:g_object_run_dispose:clutter_actor_destroy + gnome-shell crashed with SIGSEGV in _clutter_actor_stop_transitions() from clutter_actor_remove_child_internal() from clutter_actor_dispose() from g_object_run_dispose() from clutter_actor_destroy() ** Tags removed: artful cosmic trusty ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Tags added: rls-bb-incoming -- 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/1905802 Title: gnome-shell crashed with SIGSEGV in _clutter_actor_stop_transitions() from clutter_actor_remove_child_internal() from clutter_actor_dispose() from g_object_run_dispose() from clutter_actor_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905802] [NEW] gnome-shell crashed with SIGSEGV in _clutter_actor_stop_transitions() from clutter_actor_remove_child_internal() from clutter_actor_dispose() from g_object_run_dispose() from clutt
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.1-2ubuntu1.18.10.2, the problem page at https://errors.ubuntu.com/problem/eca8edabb5e911fca46723ac0925e7e374a4cc12 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: High Status: Fix Released ** Tags: bionic rls-bb-incoming xenial -- 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/1905802 Title: gnome-shell crashed with SIGSEGV in _clutter_actor_stop_transitions() from clutter_actor_remove_child_internal() from clutter_actor_dispose() from g_object_run_dispose() from clutter_actor_destroy() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905802/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1905209] Re: gnome-screensaver is blocked by an application to lock screen
Hi Sebastian, thanks for your email. 1. specific actions: superkey +L > nothing happens. ctrl + alt + L > nothing happens. using terminal to lock screen as follow: gnome-screensaver-command -l ** (gnome-screensaver-command:34478): WARNING **: 11:56:50.135: unable to send message: Timeout was reached ** Message: 11:56:50.135: Did not receive a reply from the screensaver. 2. I expect the screen to lock and only to unlock with password. It used to do that before but not any longer. 3. The behaviour I encountered as above. I think it is an application that is blocking screenlock from doing it. I do not know how to identify which app is it and how to fix it. Thanks Sokol On 26/11/2020 19:59, Sebastien Bacher wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Unfortunately, we cannot work on this bug because your > description didn't include enough information. You may find it helpful > to read "How to report bugs effectively" > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem. > > We have instructions on debugging some types of problems at > http://wiki.ubuntu.com/DebuggingProcedures. > > At a minimum, we need: > > 1. The specific steps or actions you took that caused you to encounter the > problem. > 2. The behavior you expected. > 3. The behavior you actually encountered (in as much detail as possible). > > Please also ensure that you include the release and flavour of Ubuntu > that you are using. > > Thank you! > > ** Changed in: gnome-screensaver (Ubuntu) > Importance: Undecided => Low > > ** Changed in: gnome-screensaver (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1905209 Title: gnome-screensaver is blocked by an application to lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1905209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905209] Re: gnome-screensaver is blocked by an application to lock screen
Hi Sebastian, thanks for your email. 1. specific actions: superkey +L > nothing happens. ctrl + alt + L > nothing happens. using terminal to lock screen as follow: gnome-screensaver-command -l ** (gnome-screensaver-command:34478): WARNING **: 11:56:50.135: unable to send message: Timeout was reached ** Message: 11:56:50.135: Did not receive a reply from the screensaver. 2. I expect the screen to lock and only to unlock with password. It used to do that before but not any longer. 3. The behaviour I encountered as above. I think it is an application that is blocking screenlock from doing it. I do not know how to identify which app is it and how to fix it. Thanks sn0m -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1905209 Title: gnome-screensaver is blocked by an application to lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1905209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905741] Re: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output
@mdelsaur Thanks for the prompt fixes. I confirm they fix the issues I had observed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905741 Title: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905793] [NEW] latest poppler xenial update breaks xpdf
Public bug reported: There were three updates over the last two days. with poppler (0.41.0-0ubuntu1.16) I find xpdf (3.04-1-ubuntu1.1) crashes on startup, on any file, every time. The version 0.41.0-0ubuntu1.13 worked correctly. I'm not sure about the ones in between. Perhaps this is a classic bug, back again. See, e.g., https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/669211 Description:Ubuntu 16.04.7 LTS Release:16.04 ** Affects: poppler (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905793 Title: latest poppler xenial update breaks xpdf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905793/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892276] Re: thumbnails stretched on desktop 20.04 after previous bug fix release
Minor additional information: - Also affects Ubuntu 20.10 - Stretching does not occur in the File Explorer Nautilus window, just the desktop preview. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1892276 Title: thumbnails stretched on desktop 20.04 after previous bug fix release To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1892276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892276] Re: pdf images stretched on desktop 20.04 after previous bug fix release
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low ** Summary changed: - pdf images stretched on desktop 20.04 after previous bug fix release + thumbnails stretched on desktop 20.04 after previous bug fix release -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1892276 Title: thumbnails stretched on desktop 20.04 after previous bug fix release To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1892276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905784] Re: Incorrect preview image aspect ratio in the desktop display
*** This bug is a duplicate of bug 1892276 *** https://bugs.launchpad.net/bugs/1892276 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1892276, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1892276 thumbnails stretched on desktop 20.04 after previous bug fix release -- 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/1905784 Title: Incorrect preview image aspect ratio in the desktop display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905784/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905784] [NEW] Incorrect preview image aspect ratio in the desktop display
Public bug reported: Relevant askubuntu post: https://askubuntu.com/questions/1293101/how- do-i-correct-the-preview-image-aspect-ratio-in-the-desktop-display See the included images. On Ubuntu 20.04 LTS and 20.10, images shown on the desktop are horizontally stretched. I am using a 4k built-in screen scaled to 200% with no external monitors. On the desktop: Image 1 In the file explorer (note the aspect ratio is correct here): Image 2 Unfortunately I don't know enough about Nautilus / Ubuntu to search for the right keywords, since I haven't found links to this issue elsewhere. To my knowledge, this is unreported. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 26 15:01:41 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2020-10-16 (40 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: nautilus UpgradeStatus: Upgraded to groovy on 2020-11-26 (0 days ago) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "Comparison of incorrect and correct image aspect ratios for desktop preview vs. Nautilus file display" https://bugs.launchpad.net/bugs/1905784/+attachment/5438445/+files/Screenshot%20from%202020-11-26%2015-09-41.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1905784 Title: Incorrect preview image aspect ratio in the desktop display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905784/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905774] [NEW] gnome shell logout/crash
Public bug reported: Recently it is happening a lot that gnome shell suddenly logs me out. I've just checked and saw some errors in syslog, e.g.: Nov 26 19:39:28 hp gnome-shell[11142]: St:ERROR:../src/st/st- bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL) I have the feeling it is related to mounting stuff. E.g., I am now avoiding to use sshfs, because i have the impression that this makes it more likely. just now (for the 19:39 line above) I tried logging in with a Nexus 7 tablet plugged in which I guess would also result in some mounting/filesystem action. However, as I am typing this, I am logged in and the tablet is still connected, so, maybe it's unrelated ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 26 19:43:15 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-13 (43 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session -- 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/1905774 Title: gnome shell logout/crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905774] Re: gnome shell logout/crash
syslog attached ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905774/+attachment/5438399/+files/syslog -- 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/1905774 Title: gnome shell logout/crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905741] Re: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output
This bug was fixed in the package poppler - 0.62.0-2ubuntu2.12 --- poppler (0.62.0-2ubuntu2.12) bionic-security; urgency=medium * SECURITY REGRESSION: broken Splash output (LP: #1905741) - debian/rules: don't build with SPLASH_CMYK=ON as this causes a regression with xpdf and gdal. This reverts the fix for CVE-2019-10871. -- Marc Deslauriers Thu, 26 Nov 2020 10:55:59 -0500 ** Changed in: poppler (Ubuntu Bionic) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-10871 ** Changed in: poppler (Ubuntu Xenial) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905741 Title: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905741] Re: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output
This bug was fixed in the package poppler - 0.41.0-0ubuntu1.16 --- poppler (0.41.0-0ubuntu1.16) xenial-security; urgency=medium * SECURITY REGRESSION: broken Splash output (LP: #1905741) - debian/rules: don't build with --enable-cmyk as this causes a regression with xpdf and gdal. This reverts the fix for CVE-2019-10871. -- Marc Deslauriers Thu, 26 Nov 2020 10:59:16 -0500 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905741 Title: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905759] [NEW] gnome-shell crashed with SIGABRT in GI_raise()
Public bug reported: Description:Ubuntu 20.10 Release:20.10 In the middle of work screen will randomly glitch green then revert to the login screen - behaviour with both Wayland and not Wayland. Apport.log shows: ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: called for pid 2318, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: executable: /usr/bin/gnome-shell (command line "/usr/bin/gnome-shell") ERROR: apport (pid 11042) Thu Nov 26 11:51:41 2020: debug: session gdbus call: (true,) ERROR: apport (pid 11042) Thu Nov 26 11:51:51 2020: wrote report /var/crash/_usr_bin_gnome-shell.1000.crash ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/bugs/1905759/+attachment/5438304/+files/_usr_bin_gnome-shell.1000.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/1905759 Title: gnome-shell crashed with SIGABRT in GI_raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905759/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter
** Changed in: mutter (Ubuntu) Status: Incomplete => Confirmed -- 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/1905637 Title: Games don't go full screen correctly with newer version of libmutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905756] [NEW] SRU the current 3.36.8 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some translation updates https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that a GNOME session still works correctly, including changing the background image, locale and screen settings. The GNOME version in setting should also be 3.36.8 * Regression potential The update has some test and translations fixes and a change to the thumbnailing, check that nautilus still previews images correctly ** Affects: gnome-desktop3 (Ubuntu) Importance: Low Status: Fix Released ** Changed in: gnome-desktop3 (Ubuntu) Status: New => Fix Released ** Changed in: gnome-desktop3 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1905756 Title: SRU the current 3.36.8 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1905756/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1900263] Re: In Hebrew environment, clock is reversed: minutes are shown before hours
** Changed in: gnome-desktop3 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1900263 Title: In Hebrew environment, clock is reversed: minutes are shown before hours To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1900263/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905741] Re: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output
Thanks for reporting this, I'll back out the fix and will release updates shortly. ** Also affects: poppler (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: poppler (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: poppler (Ubuntu) Status: New => Invalid ** Changed in: poppler (Ubuntu Xenial) Status: New => In Progress ** Changed in: poppler (Ubuntu Bionic) Status: New => In Progress ** Changed in: poppler (Ubuntu Xenial) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: poppler (Ubuntu Bionic) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905741 Title: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905754] [NEW] When gnome-shell shows a long error, it doesn't scroll and show the whole error
Public bug reported: I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-54.60-lowlatency 5.4.65 Uname: Linux 5.4.0-54-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 26 17:59:04 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2020-02-08 (292 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-10-23 (34 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1905754 Title: When gnome-shell shows a long error, it doesn't scroll and show the whole error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905754] Re: When gnome-shell shows a long error, it doesn't scroll and show the whole error
** Attachment added: "Screenshot from 2020-11-26 17-13-26.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905754/+attachment/5438272/+files/Screenshot%20from%202020-11-26%2017-13-26.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/1905754 Title: When gnome-shell shows a long error, it doesn't scroll and show the whole error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905741] Re: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output
** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905741 Title: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re:[Bug 1905727] Re: the nautilus will be freezen when open a folder which contains a big file (>3GB)
-- 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/1905727 Title: the nautilus will be freezen when open a folder which contains a big file (>3GB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905727/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905727] Re: the nautilus will be freezen when open a folder which contains a big file (>3GB)
Thank you for your reply。I have just run the 'htop',But There are no high CPU consuming programs.After I run the file browser,opening the problematic folder,the cpu will get highly using.a folder contains a iso file about 3gb,another include a subdirectory which is Android source code about 16gb -- 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/1905727 Title: the nautilus will be freezen when open a folder which contains a big file (>3GB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905727/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905637] Re: Games don't go full screen correctly with newer version of libmutter
** Summary changed: - Games don't go full screen correctly with new version of libmutter + Games don't go full screen correctly with newer version of libmutter -- 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/1905637 Title: Games don't go full screen correctly with newer version of libmutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905740] Re: SRU the current 3.36.5 stable update
Ubuntu 20.10 has 3.38 and the fixes are the current package ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released ** 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/1905740 Title: SRU the current 3.36.5 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1905740/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905741] Re: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905741 Title: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905740] [NEW] SRU the current 3.36.5 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-control-center/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the GNOME settings still work correctly * Regression potential Review the fixes in the update the things to try should include - replacing a keybinding - checking that connectivy changes are correctly reflected in settings and that informations are correctly displayed in the details screen - opening the printer panel to verify that ink levels are still correctly displayed - using the privacy screen to enable or disable screen sharing - going to the sound panel and change devices configurations ** 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/1905740 Title: SRU the current 3.36.5 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1905740/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905741] [NEW] poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output
Public bug reported: The security updates 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 break the Splash output rendering, for example if using the xpdf utility that relies on Poppler splash output, or as used by the GDAL library (the issue was detected due to breakage in GDAL continuous integration tests) I've traced the root cause to those security updates enabling in 'rules' CMYK (--enable-cmyk for 0.41.0-0ubuntu1.15 and -DSPLASH_CMYK=ON for 0.62.0-2ubuntu2.11) Building without CMYK restore poppler in a working state. It should be noted that even on the upstream 0.41.0 version, enabling CMYK result in a non-functional build, so it is not related to the patches applied on top of it, but really on enabling CMYK The issue can be verified with "xpdf test_ogc_bp.pdf" with the attached test_ogc_bp.pdf file. With the new packages, xpdf crashes, whereas with older ones it displays a 20x20 greyscale image. Or with "gdal_translate test_ogc_bp.pdf out.png -of PNG" when installing the "gdal-bin" package, that currently errors out with a message like "ERROR 1: Bitmap decoded size (18623872x0) doesn't match raster size (20x20)" ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Sample file that make xpdf crash currently" https://bugs.launchpad.net/bugs/1905741/+attachment/5438256/+files/test_ogc_bp.pdf -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905741 Title: poppler 0.62.0-2ubuntu2.11 and 0.41.0-0ubuntu1.15 security updates break Splash output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905741/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905704] Re: xpdf segmentation fault
I can confirm that rolling back to libpoppler73_0.62.0-2ubuntu2.10_amd64.deb makes xpdf work again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905704 Title: xpdf segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
@nightwing666: Thank you so much for this! It worked! -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905727] Re: the nautilus will be freezen when open a folder which contains a big file (>3GB)
Thank you for your bug report, could you check in 'top' if anything is using cpu when you open the folder? which format is the file using, could be a thumbnail process having issue ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1905727 Title: the nautilus will be freezen when open a folder which contains a big file (>3GB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905727/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905729] [NEW] power button conifiguration broken
Public bug reported: I'm not able to suspend the machine anymore by pressing the power button, instead a popup saying the machine will be shut down in 60s appears. The settings for configuring the behaviour is no longer visible in control center. And selecting suspend from the menu now asks for my password. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-settings-daemon 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 24 16:35:55 2020 InstallationDate: Installed on 2019-10-14 (406 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/zsh RebootRequiredPkgs: gnome-shell linux-image-5.8.0-29-generic linux-base SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to groovy on 2020-09-29 (56 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- 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/1905729 Title: power button conifiguration broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1905729/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905704] Re: xpdf segmentation fault
# lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 I have an Epson TM BA Thermal network printer, configured in CUPS After today's unattended upgrade it stopped working Logs found on server [540009.389033] pdftoraster[63919]: segfault at d0400 ip 557a50f569a8 sp 7ffd5ca826d8 error 6 in pdftoraster[557a50f52000+8000] Thu Nov 26 14:14:19 2020: apport: report /var/crash/_usr_lib_cups_filter_pdftoraster.7.crash already exists and unseen, doing nothing to avoid disk usage DoS # dpkg -S /usr/lib/cups/filter/pdftoraster cups-filters-core-drivers: /usr/lib/cups/filter/pdftoraster Start-Date: 2019-11-25 17:01:06 Install cups-filters-core-drivers:amd64 # dpkg -l|grep cups-filters-core-drivers ii cups-filters-core-drivers 1.20.2-0ubuntu3.1 I checked what was updated with unattended upgrade Start-Date: 2020-11-24 06:20:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpulse0:amd64 (1:11.1-1ubuntu7.10, 1:11.1-1ubuntu7.11) End-Date: 2020-11-24 06:20:10 and I rolled back # wget https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/17383699/+files/poppler-utils_0.62.0-2ubuntu2.10_amd64.deb # wget https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+build/17383699/+files/libpoppler73_0.62.0-2ubuntu2.10_amd64.deb # ls apt/ libpoppler73_0.62.0-2ubuntu2.10_amd64.deb poppler-utils_0.62.0-2ubuntu2.10_amd64.deb #dpkg -R --install apt/ and started to work again and of course apt-mark hold libpoppler73 poppler-utils # apt-cache policy poppler-utils libpoppler73 poppler-utils: Installed: 0.62.0-2ubuntu2.10 Candidate: 0.62.0-2ubuntu2.11 Version table: 0.62.0-2ubuntu2.11 500 500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 0.62.0-2ubuntu2.10 100 100 /var/lib/dpkg/status 0.62.0-2ubuntu2 500 500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages libpoppler73: Installed: 0.62.0-2ubuntu2.10 Candidate: 0.62.0-2ubuntu2.11 Version table: 0.62.0-2ubuntu2.11 500 500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://gr.archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages *** 0.62.0-2ubuntu2.10 100 100 /var/lib/dpkg/status 0.62.0-2ubuntu2 500 500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Attachment added: "_usr_lib_cups_filter_pdftoraster.7.crash" https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905704/+attachment/5438244/+files/_usr_lib_cups_filter_pdftoraster.7.crash -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905704 Title: xpdf segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905727] [NEW] the nautilus will be freezen when open a folder which contains a big file (>3GB)
Public bug reported: ubuntu version:20.04 can't open the big size folder by click the file browser.but can open by the cmdline ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 26 19:55:59 2020 GsettingsChanges: InstallationDate: Installed on 2020-11-21 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=zh_CN:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/usr/bin/zsh SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1905727 Title: the nautilus will be freezen when open a folder which contains a big file (>3GB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905727/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in
** Also affects: plasma-desktop (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/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905637] Re: Games don't go full screen correctly with new version of libmutter
I kept the mentioned packages on hold so I can play games, but if you need I update them or test another package please let me know. I would like to bisect the patches of the newer version but I have no clue about how. -- 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/1905637 Title: Games don't go full screen correctly with new version of libmutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803321] Re: gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_update_pad_state()
I don't have the tablet anymore and I'm still on 18.04. -- 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/1803321 Title: gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_update_pad_state() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803321/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905637] Re: Games don't go full screen correctly with new version of libmutter
I tried to execute the apport-collect command but always happens this: mhalano@glados:~$ apport-collect 1905637 Package mutter not installed and no hook available, ignoring mhalano@glados:~$ So I executed: apport-collect -p libmutter-7-0 1905637 -- 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/1905637 Title: Games don't go full screen correctly with new version of libmutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905637] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1905637/+attachment/5438224/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905637 Title: Games don't go full screen correctly with new version of libmutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905637] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1905637/+attachment/5438223/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905637 Title: Games don't go full screen correctly with new version of libmutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905637] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1905637/+attachment/5438222/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1905637 Title: Games don't go full screen correctly with new version of libmutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905637] Re: Games don't go full screen correctly with new version of libmutter
** Attachment added: "monitors.xml" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+attachment/5438221/+files/monitors.xml ** Tags added: apport-collected third-party-packages ** Description changed: Some games (I tried using Portal and Tomb Raider 2013, both native games) don't go full screen correctly (even configured for it). I tracked down the problem to a regression on package libmutter-7-0. The problem occurs with latest version, 3.38.1-2ubuntu1, but when I downgrade the package (and also the package gir1.2-mutter-7) to 3.38.1-1ubuntu1 the gomes went full screen normally. I'm using Ubuntu 20.10. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.2 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2020-10-23 (33 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + NonfreeKernelModules: nvidia_modeset nvidia + Package: libmutter-7-0 3.38.1-1ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17 + Tags: groovy third-party-packages + Uname: Linux 5.8.0-30-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- 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/1905637 Title: Games don't go full screen correctly with new version of libmutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1905637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905704] [NEW] xpdf segmentation fault
Public bug reported: When I installed the latest updates this morning, xpdf started crashing with all pdf files. xpdf uses libpoppler73:amd64 and this library was updated from version 0.62.0-2ubuntu2.10 to 0.62.0-2ubuntu2.11. xpdf itself was not updated. $ xpdf foo.pdf Segmentation fault (core dumped) (gdb) run Starting program: /usr/bin/xpdf.real [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Program received signal SIGSEGV, Segmentation fault. 0x55569173 in ?? () (gdb) bt #0 0x55569173 in ?? () #1 0x55565123 in ?? () #2 0x5556521c in ?? () #3 0x55561616 in ?? () #4 0x7737ddb9 in Gfx::go(bool) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.73 #5 0x7737de8b in Gfx::display(Object*, bool) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.73 #6 0x773c9e31 in Page::displaySlice(OutputDev*, double, double, int, bool, bool, int, int, int, int, bool, bool (*)(void*), void*, bool (*)(Annot*, void*), void*, bool) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.73 #7 0x55563af6 in ?? () #8 0x55566aa0 in ?? () #9 0x5556ca31 in ?? () #10 0x555619c6 in ?? () #11 0x55572e57 in ?? () #12 0x779b7a78 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #13 0x779ee9e1 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #14 0x779eef65 in ?? () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #15 0x779c0bd3 in _XmDispatchGadgetInput () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #16 0x77a6dae2 in _XmGadgetActivate () from /usr/lib/x86_64-linux-gnu/libXm.so.4 #17 0x77050a0d in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #18 0x77051937 in _XtTranslateEvent () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #19 0x77029e52 in XtDispatchEventToWidget () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #20 0x7702a83d in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #21 0x7702a919 in XtDispatchEvent () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #22 0x770365cf in XtAppProcessEvent () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #23 0x7702ad2d in XtAppMainLoop () from /usr/lib/x86_64-linux-gnu/libXt.so.6 #24 0x55561115 in ?? () #25 0x76140bf7 in __libc_start_main (main=0x55560b30, argc=1, argv=0x7fffde78, init=, fini=, rtld_fini=, stack_end=0x7fffde68) at ../csu/libc-start.c:310 #26 0x5556146a in ?? () $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ dpkg -l|grep xpdf ii xpdf 3.04-7 amd64Portable Document Format (PDF) reader ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpoppler73:amd64 0.62.0-2ubuntu2.11 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 Date: Thu Nov 26 11:57:55 2020 SourcePackage: poppler UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1905704 Title: xpdf segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1905704/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1904709] Re: Nautilus crash on filtering files over samba mount points
*** This bug is a duplicate of bug 1869404 *** https://bugs.launchpad.net/bugs/1869404 Thanks, sounds like the issue you hit there is bug #1869404 so I'm marking it duplicate One other error in the reports was bug #1905697 ** This bug has been marked a duplicate of bug 1869404 nautilus crashed with SIGABRT -- 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/1904709 Title: Nautilus crash on filtering files over samba mount points To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1904709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905697] [NEW] /usr/bin/nautilus:11:g_file_has_prefix:check_select_old_location_containing_folder:begin_location_change:nautilus_window_slot_open_location_full:ffi_call_unix64
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.38.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/90aafe5f99f343c6b8ce7a0d8beddda64d822a1f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: nautilus (Ubuntu) Importance: Low Status: Confirmed ** Tags: disco eoan focal groovy -- 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/1905697 Title: /usr/bin/nautilus:11:g_file_has_prefix:check_select_old_location_containing_folder:begin_location_change:nautilus_window_slot_open_location_full:ffi_call_unix64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905697] Re: /usr/bin/nautilus:11:g_file_has_prefix:check_select_old_location_containing_folder:begin_location_change:nautilus_window_slot_open_location_full:ffi_call_unix64
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1905697 Title: /usr/bin/nautilus:11:g_file_has_prefix:check_select_old_location_containing_folder:begin_location_change:nautilus_window_slot_open_location_full:ffi_call_unix64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905697/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905209] Re: gnome-screensaver is blocked by an application to lock screen
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: gnome-screensaver (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-screensaver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1905209 Title: gnome-screensaver is blocked by an application to lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1905209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1905576] Re: I cannot drag icons above to a particular region of my desktop
Thank you for your bug report, as Daniel said the nautilus desktop rendering got deprecated in newer versions. The issue also sounds like a duplicate of bug #360970 ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/1905576 Title: I cannot drag icons above to a particular region of my desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905576/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1904709] Re: Nautilus crash on filtering files over samba mount points
Hi, I have made step 1 with the file "_usr_bin_nautilus.1151801627.crash" found in /var/crash The command "ubuntu-bug " has sent a report but i don't know where to find the ID of the newly created bug. The system hasn't tell me anything. On the other hand, as you instructed in step 2, the links of the nautilus reports are: https://errors.ubuntu.com/oops/f58ac652-2fc2-11eb-8c7d-fa163e983629 https://errors.ubuntu.com/oops/daa39c7a-2e51-11eb-8be3-fa163e983629 https://errors.ubuntu.com/oops/f53bc03e-2e50-11eb-82f1-fa163e6cac46 https://errors.ubuntu.com/oops/ce79ed26-2b27-11eb-b7ac-fa163e102db1 https://errors.ubuntu.com/oops/e6cc764e-28cc-11eb-899e-fa163e983629 https://errors.ubuntu.com/oops/9af44cfc-27f6-11eb-b62f-fa163e102db1 https://errors.ubuntu.com/oops/a9b08fc7-25b2-11eb-8857-fa163e983629 https://errors.ubuntu.com/oops/753baa02-1ea6-11eb-b2a0-fa163e102db1 https://errors.ubuntu.com/oops/bda174d3-1a97-11eb-8422-fa163e983629 El mar., 24 nov. 2020 a las 14:30, Sebastien Bacher (< 1904...@bugs.launchpad.net>) escribió: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. It sounds like some part of the system has crashed. To > help us find the cause of the crash please follow these steps: > > 1. Look in /var/crash for crash files and if found run: > ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. > > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where > ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. > Do you find any links to recent problems on that page? If so then please > send the links to us. > > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. > > Please take care to avoid attaching .crash files to bugs as we are > unable to process them as file attachments. It would also be a security > risk for yourself. > > ** Changed in: nautilus (Ubuntu) >Importance: Undecided => Low > > ** Changed in: nautilus (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1904709 > > Title: > Nautilus crash on filtering files over samba mount points > > Status in nautilus package in Ubuntu: > Invalid > > Bug description: > When I open Nautilus and navigate over a samba mount point and do this, > nautilus crashes: > 1. Go to a samba mount point > 2. Start typing something to filter results > 3. Drag mouse to select all the text you have typed > 4. Start typing again to change filter and nautillus crash > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: nautilus 1:3.36.3-0ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 > Uname: Linux 5.4.0-54-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.12 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Wed Nov 18 09:47:35 2020 > GsettingsChanges: >b'org.gnome.nautilus.window-state' b'sidebar-width' b'206' >b'org.gnome.nautilus.window-state' b'initial-size' b'(1133, 727)' >b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', > 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', > 'date_modified_with_time', 'date_accessed', 'recency', 'starred', > 'detailed_type']" > InstallationDate: Installed on 2020-10-29 (19 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=es_ES.UTF-8 >SHELL=/bin/bash > SourcePackage: nautilus > UpgradeStatus: No upgrade log present (probably fresh install) > usr_lib_nautilus: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1904709/+subscriptions > -- 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/1904709 Title: Nautilus crash on filtering files over samba mount points To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1904709/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
This is also affecting me on Ubuntu 20.04 (started to happen from the very beginning with a standard fresh installation). * keyboard mapping for compose key set from gnome-tweaks is frequently gone again * sound setting seems to switch whenever I open the settings menu, also switches when I go to the sound tab in the settings -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs