[Bug 1889252] Re: [amdgpu] app blinking
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Invalid => Fix Released -- 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/1889252 Title: [amdgpu] app blinking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1889252] Re: [amdgpu] app blinking
now its over, 20.04 install and proper work thanks a lot sir... -- 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/1889252 Title: [amdgpu] app blinking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1889252/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1430068] Re: Unable to launch gnome-system-monitor
I tried what Alan said, but I get Permission denied even when doing sudo: ~$ sudo echo 512 > /proc/sys/fs/inotify/max_user_instances bash: /proc/sys/fs/inotify/max_user_instances: Permission denied It did not work for me. Any ideas? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1430068 Title: Unable to launch gnome-system-monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1430068/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895837] Re: [groovy] totem crashed with SIGSEGV in g_main_context_dispatch()
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Summary changed: - totem crashed with SIGSEGV in g_main_context_dispatch() + [groovy] totem crashed with SIGSEGV in g_main_context_dispatch() -- 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/1895837 Title: [groovy] totem crashed with SIGSEGV in g_main_context_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1895837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895837] Re: [groovy] totem crashed with SIGSEGV in g_main_context_dispatch()
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: totem (Ubuntu) Status: Confirmed => Incomplete -- 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/1895837 Title: [groovy] totem crashed with SIGSEGV in g_main_context_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1895837/+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; erratic behaviour when user logged in.
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => 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/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when 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 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in.
Here is sit, in 2020, Nvidia, Ubuntu 20.04, SAME issue... as a desktop, full keyboard I have no Fn'b button (lol pun intended). Kernel, 5.4.0-47-generic, Nvidia Driver 450.66 (Game Driver) -- 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; erratic behaviour when 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 1895837] Re: totem crashed with SIGSEGV in g_main_context_dispatch()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: totem (Ubuntu) Status: New => 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/1895837 Title: totem crashed with SIGSEGV in g_main_context_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1895837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892643] Re: [SRU] Update libgweather to 3.36.1
Please sponsor libgweather 3.36.1 in my PPA to Focal: https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter= -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1892643 Title: [SRU] Update libgweather to 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1892643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892643] Re: [SRU] Update libgweather to 3.36.1
** Description changed: - Please update libgweather to 3.36.1 to fix the unavailability of current - temperature in some locations. + [Impact] + + libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36. https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS - == - Version 3.36.1 - == + This version works around the unavailability of the NOAA weather + services by using very short-term forecasts as current weather + conditions. - This version works around the unavailability of the NOAA weather services - by using very short-term forecasts as current weather conditions. + Sometimes the current weather is not available because the NOAA weather + servers aren't working correctly. Version 3.36.1 fixes the + unavailability of current temperature in some locations. + + + [Test case] + + Make sure that gnome-weather is still working properly and the weather + in gnome-shell is shown when gnome-weather is installed. + + + [Regression potential] + + The regression potential is low since the changes in version 3.36.1 are + small. + + + [Other] + + libgweather 3.36.1 has been successfully built as a no-change backport + from Groovy to Focal in my PPA and runs fine: + + https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter= + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 19:05:21 2020 InstallationDate: Installed on 2020-04-26 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1892643 Title: [SRU] Update libgweather to 3.36.1 To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1892643/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895872] [NEW] Please delete the patch "Sort snaps before other apps" in Ubuntu 20.04
Public bug reported: Since the focus is now on the snap-store, and this revert has already been implemented there, I'm asking please to remove the patch that sorts snaps before other apps in Ubuntu 20.04. The revert in the snap-store: https://gitlab.gnome.org/Community/Ubuntu/gnome-software/-/merge_requests/21 Sorting snaps before other apps sometimes gives unrelated search results. That can be shown when you have both the snap and flatpak plugins installed beside debs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.1-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 16 18:54:01 2020 InstallationDate: Installed on 2020-04-26 (143 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snapN/A ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- 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/1895872 Title: Please delete the patch "Sort snaps before other apps" in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1895872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884746] Re: Wacom stylus not identified/available (ACER SPIN 5)
Hi, just to say that for me adding i8042.nopnp=1 pci=nocrs works very fine : I had back : - touchpad - touch screen with automated rotation (usefull in tablet configuration) - stylus recognition with buttons and intensity sensor (tested on xournal++) and appearing in the wacom parameters Thanks a lot. Config : spin 5, sp513 54N - with 1TB ssd, 16GB RAM, - dual boot using BIOS option AHCI - Linux Mint 20 Cinnamon - a NTFS partition to share docs between Linux and Win -- 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/1884746 Title: Wacom stylus not identified/available (ACER SPIN 5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1884746/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884746] Re: Wacom stylus not identified/available (ACER SPIN 5)
Oooups : I just checked that the rotation of the screen works, but not the rotation of the "touch" part of the screen (so there is no coherence between touch and orientation when the screen rotate) -- 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/1884746 Title: Wacom stylus not identified/available (ACER SPIN 5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1884746/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875845] Re: keyring cannot be unlocked if used fingerprint to login gnome session
I was about to submit this same bug... I can confirm that every time you login to your gnome session with a fingerprint you can't unlock your login keyring. It seems that the prompt asking for the password fails to appear. For example, opening seahorse and clicking "unlock" has no effect (the button becomes gray but no prompt is shown). When other software tries to access the keyring (which is still locked) no prompt is shown and the software (e.g. the browser) either gets stuck, hangs or crashes. The only workaround I found so far is to lock the session and then unlock it with the password. After that, clicking on "unlock" in seahorse will work. I guess that the password you just used to unlock the session is cached for a while. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1875845 Title: keyring cannot be unlocked if used fingerprint to login gnome session To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1875845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Thank you @christian. I marked the Xenial test cases under this same bug, though can open a new bug and update the hint bug references if needed. I'll check back to see when/if ddstreet/rbalint have a chance to review. For the test results you're posting, I was wondering where you're getting those results from and an explanation of the results? xenial amd64 boot-and-services (F 45% f 0% S 0% B 5% => P 50%/) .FF...BFF.F. boot-smoke (F 80% f 0% S 0% B 5% => P 15%/) F.FF..BF systemd-fsckd (F 65% f 0% S 0% B 5% => P 30%/) FF.FFF.F..B.FF.F ppc64el no failures s390x no failures In the above, what does the F, f, B, & . stand for? Am I correct to assume the P *% is the pass rate? F for fail? Thank you! -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1286430] Re: Suspend option when lid closed "greyed out" in Power Settings
Closing this ancient bug (which I filed) since it's against a long-since EOL version, and I haven't seen this problem in any recent versions. ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1286430 Title: Suspend option when lid closed "greyed out" in Power Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1286430/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1825224] Re: gnome-calendar cannot add credentialed web ics calendars
Closing as fix released since this was fixed around the time of Gnome 3.34. ** Changed in: gnome-calendar (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1825224 Title: gnome-calendar cannot add credentialed web ics calendars To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-calendar/+bug/1825224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Hi, how can I install the fix upstream please? Thank-you Le mer. 16 sept. 2020, à 08 h 20, Marco Trevisan (Treviño) < 1892...@bugs.launchpad.net> a écrit : > Sorry for the delay here, but unfortunately the work to be done in > groovy updates lead to having less time to study this issue. > > However, it looks like the problem is present upstream, but our patch is > triggering it more. > > So I've proposed a fix upstream > (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1444) while the > ubuntu package is in progress as well. > > ** Changed in: mutter (Ubuntu) >Status: Confirmed => In Progress > > ** Changed in: mutter (Ubuntu Focal) >Status: Confirmed => In Progress > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1893792). > https://bugs.launchpad.net/bugs/1892440 > > Title: > Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on > Nvidia) > > Status in mutter package in Ubuntu: > In Progress > Status in mutter source package in Focal: > In Progress > > Bug description: > See also bug 1892521. > > The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 > causes small text in GNOME Shell menu with NVIDIA cards. > > With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The > problem is after update to the (3.36.4-0ubuntu0.20.04.2). > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu27.8 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 20.04 > InstallationDate: Installed on 2020-08-18 (2 days ago) > InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" > (20200815) > NonfreeKernelModules: nvidia_modeset nvidia > Package: mutter 3.36.4-0ubuntu0.20.04.2 > PackageArchitecture: amd64 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Tags: focal > Uname: Linux 5.4.0-42-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo > _MarkForUpload: True > modified.conffile..etc.default.apport: ># set this to 0 to disable apport, or to 1 to enable it ># you can temporarily override this with ># sudo service apport start force_start=1 >enabled=0 > mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions > -- 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 is too small 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 1895837] Re: totem crashed with SIGSEGV in g_main_context_dispatch()
** 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 totem in Ubuntu. https://bugs.launchpad.net/bugs/1895837 Title: totem crashed with SIGSEGV in g_main_context_dispatch() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1895837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895664] Re: evince can't start local installation of vivaldi browser
** Summary changed: - problem in apparmor configuration of evince + evince can't start local installation of vivaldi browser ** Changed in: evince (Ubuntu) Status: New => Invalid -- 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/1895664 Title: evince can't start local installation of vivaldi browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895664/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895664] Re: problem in apparmor configuration of evince
Thank you for your bug report, vivaldi isn't a known webbrowser though and is a locally installed software in /opt so probably something you need to handle locally -- 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/1895664 Title: problem in apparmor configuration of evince To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895664/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Sorry for the delay here, but unfortunately the work to be done in groovy updates lead to having less time to study this issue. However, it looks like the problem is present upstream, but our patch is triggering it more. So I've proposed a fix upstream (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1444) while the ubuntu package is in progress as well. ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress ** Changed in: mutter (Ubuntu Focal) Status: Confirmed => In Progress -- 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 is too small 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 1895664] Re: problem in apparmor configuration of evince
** Changed in: evince (Ubuntu) Importance: Undecided => Low -- 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/1895664 Title: problem in apparmor configuration of evince To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1895664/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881896] Re: "Sign In…" string not available for translation
My proposed fix was rejected with this comment: "Going to reject now since gnome-software got unpatched, snap-store has the Ubuntu improvements and gnome-software is back to be what upstream provides" Closing. ** Changed in: gnome-software (Ubuntu) Status: In Progress => Won't Fix ** Changed in: ubuntu-translations Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1881896 Title: "Sign In…" string not available for translation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1881896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895781] Re: ~/.gnomerc is not loaded anymore at startup
I think we should not post this bug report to the upstream's BTS because this bug only occus on Ubuntu. Here are some background info. '55gnome-session_gnomerc' is created by Debian and not included in the original tarball of gnome-session, and it perfectly works on Debian. So why it fails on Ubuntu? Ubuntu's 'ubuntu-session' package provides '/usr/share/xsessions/ubuntu.desktop' file that executes gnome-session by the following command line: env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --systemd --session=ubuntu For comparison, on Debian, '/usr/share/xsessions/gnome.desktop' simply calls '/usr/bin/gnome-session'. In conclusion, 1) Ubuntu activates /usr/bin/gnome-session in a non- standard way, and 2) 55gnome-session_gnomerc does not expect it. -- 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/1895781 Title: ~/.gnomerc is not loaded anymore at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1895781/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1318327] Re: Can't open .webp files
These are the upstream: https://bugzilla.gnome.org/show_bug.cgi?id=700751 | https://gitlab.gnome.org/GNOME/eog/-/issues/45 ** Bug watch added: bugzilla.gnome.org/ #700751 https://bugzilla.gnome.org/show_bug.cgi?id=700751 ** Bug watch added: gitlab.gnome.org/GNOME/eog/-/issues #45 https://gitlab.gnome.org/GNOME/eog/-/issues/45 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1318327 Title: Can't open .webp files To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1318327/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1895781] Re: ~/.gnomerc is not loaded anymore at startup
Thanks for the bug report. Please also report it to the developers at: https://gitlab.gnome.org/GNOME/gnome-session/-/issues and then tell us the new issue ID. ** Tags added: focal -- 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/1895781 Title: ~/.gnomerc is not loaded anymore at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1895781/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
And on Bionic we only need to do so for amd64 Here is a new MP for Bionic: https://code.launchpad.net/~paelzer/britney/hints-ubuntu-bionic-disable-systemd-v2/+merge/390793 ** Branch linked: lp:~paelzer/britney/hints-ubuntu-bionic-disable- systemd-v2 -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
The problem with Xenial is that there it isn't just flaky "systemd- fsckd" much more seems to be broken. I'll revise my Bionic MP, but for Xenial I'd like to hear from ddstreet/rbalint how they think we should go on there ... -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Focal test hint was accepted tonight and things moved there. @Kelsey - Steve denied the hint as a reset since recently a few results were good. Maybe you want to submit the same as force-badtest and bring it up like that for X? The results for xenial really look similarly bad ... xenial amd64 boot-and-services (F 45% f 0% S 0% B 5% => P 50%/) .FF...BFF.F. boot-smoke (F 80% f 0% S 0% B 5% => P 15%/) F.FF..BF systemd-fsckd (F 65% f 0% S 0% B 5% => P 30%/) FF.FFF.F..B.FF.F ppc64el no failures s390x no failures I know that ddstreet is considering the SRU updates for systemd to also mark those flaky. I'm still +1 to mark them force-badtest until then but I'm not the one to decide. -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
