[Bug 1315817] Re: totem shows error Invalid commandline while running all media files
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- 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/1315817 Title: totem shows error Invalid commandline while running all media files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1315817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
** Changed in: mutter (Ubuntu) Assignee: Nour Belguith (master-nour) => (unassigned) -- 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/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722256] Re: Wifi connection status icon shows a "?" question mark when connected
Sounds related, and maybe that's where the bug is. Although it's not an Ubuntu-specific issue... https://bugzilla.gnome.org/show_bug.cgi?id=750260 That said, I haven't seen this bug in a long time. If you do see it, what release are you using? -- 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/1722256 Title: Wifi connection status icon shows a "?" question mark when connected To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836124] Re: I couldn't interact with the screenlock
Hmm. The process I killed was most definitely gnome-screensaver. It might have been running in an LXD instance. This is strange. -- 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/1836124 Title: I couldn't interact with the screenlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1836124/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836124] [NEW] I couldn't interact with the screenlock
Public bug reported: Hello, I use i3lock to lock my screen. systemd starts gnome-screensaver when I suspend my laptop because I haven't figured out how to turn that off yet. Most of the time this is no big deal, I just have to unlock twice the five or six times a year I suspend my laptop. Today, however, I couldn't actually interact with the gnome-screensaver lock screen: - I resumed my laptop - I unlocked the already-running i3lock - The gnome-screensaver was running, showed the correct time in the center of the 'titlebar', showed my user name in the right side of the titlebar, and the mouse moved around fine. - I blindly typed my password and hit enter - The mouse pointer turned to a spinner for 20~40 seconds - The mouse pointer could move around, but couldn't interact with any screen elements - ctrl+alt+f1 etc worked fine to change virtual consoles I was only able to use my X11 session after manually killing the gnome- screensaver process from a shell. Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Wed Jul 10 15:05:31 2019 InstallationDate: Installed on 2012-10-18 (2456 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to bionic on 2018-05-02 (435 days ago) ** Affects: gnome-screensaver (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 gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1836124 Title: I couldn't interact with the screenlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1836124/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835956] Re: Deleting "Input Sources" not in use, affects the ones in use.
I'm sorry, but I'm not sure if I understand what you mean by "not only after adding but continuing after a session restart using the indicator/keybindings and not the settings?" Now I'm thinking maybe this is somehow related to the problem mentioned before, that sometimes the "Input Source in use" indicator changes, but the keyboard keeps behaving the same way. I'll check the gnome-shell list to see if I can add any information to a related bug, or maybe opening a new one. Thanks. -- 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/1835956 Title: Deleting "Input Sources" not in use, affects the ones in use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1835956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 622542] Re: Search box should obtain focus at start up
** Changed in: rhythmbox Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/622542 Title: Search box should obtain focus at start up To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/622542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors
This bug was fixed in the package gnome-desktop3 - 3.32.1-1ubuntu1.2 --- gnome-desktop3 (3.32.1-1ubuntu1.2) disco; urgency=medium * Cherry-pick patch from upstream to use mutter's connector-type to detect output connector type. This fixes suspend on some systems (primarily ones using the NVIDIA binary driver). (LP: #1731318) * libgnome-desktop-3-17.symbols: Update. The patch add two symbols and drops one. These symbols are defined in "gnome-rr-private.h", which is not shipped in the -dev package, so they can't be used in practice. This is a technical ABI break but one which it's OK to overlook. There's probably a better way to handle the visibility of these symbols, though. * debian/control*, gbp.conf: Update for ubuntu/bionic -- Iain Lane Fri, 28 Jun 2019 13:34:02 +0100 ** Changed in: gnome-desktop3 (Ubuntu Disco) 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/1731318 Title: NVIDIA systems will not suspend with lid close and no external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1731318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors
This bug was fixed in the package gnome-desktop3 - 3.28.2-0ubuntu1.5 --- gnome-desktop3 (3.28.2-0ubuntu1.5) bionic; urgency=medium * Revert "libgnome-desktop-3-17.symbols: Update". I overzealously cherry-picked this from disco. This is in fact not a problem with the autotools build (in disco meson is used and the _-prefixed symbols are leaked). It is not needed here. gnome-desktop3 (3.28.2-0ubuntu1.4) bionic; urgency=medium * Cherry-pick patch from upstream to use mutter's connector-type to detect output connector type. This fixes suspend on some systems (primarily ones using the NVIDIA binary driver). (LP: #1731318) * libgnome-desktop-3-17.symbols: Update. The patch add two symbols and drops one. These symbols are defined in "gnome-rr-private.h", which is not shipped in the -dev package, so they can't be used in practice. This is a technical ABI break but one which it's OK to overlook. There's probably a better way to handle the visibility of these symbols, though. -- Iain Lane Wed, 03 Jul 2019 09:53:10 +0100 ** Changed in: gnome-desktop3 (Ubuntu Bionic) 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/1731318 Title: NVIDIA systems will not suspend with lid close and no external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1731318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836113] [NEW] Gimp crashed while using the paint tool
Public bug reported: ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1) using GEGL version 0.4.14 (compiled against version 0.4.12) using GLib version 2.60.4 (compiled against version 2.58.1) using GdkPixbuf version 2.38.1 (compiled against version 2.38.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.0) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Aborted Stack trace: ``` # Stack traces obtained from PID 14328 - Thread 14328 # [New LWP 14330] [New LWP 14331] [New LWP 14332] [New LWP 14333] [New LWP 14334] [New LWP 14335] [New LWP 14336] [New LWP 14337] [New LWP 14338] [New LWP 14396] [New LWP 32762] [New LWP 32763] [New LWP 32764] [New LWP 32765] [New LWP 632] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __libc_read (nbytes=256, buf=0x7ffeed325290, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7f055791ae00 (LWP 14328) "gimp-2.10" __libc_read (nbytes=256, buf=0x7ffeed325290, fd=18) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7f05571cb700 (LWP 14330) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7f05569ca700 (LWP 14331) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7f05561c9700 (LWP 14332) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7f0547dfb700 (LWP 14333) "gmain" 0x7f0559605729 in __GI___poll (fds=0x5649298a5cf0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 6Thread 0x7f05475fa700 (LWP 14334) "gdbus" 0x7f0559605729 in __GI___poll (fds=0x56492995d670, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 7Thread 0x7f05388f8700 (LWP 14335) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7f0533fff700 (LWP 14336) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7f05337fe700 (LWP 14337) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 10 Thread 0x7f0532ffd700 (LWP 14338) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 11 Thread 0x7f05127fc700 (LWP 14396) "swap writer" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7f05037fe700 (LWP 32762) "gimp-2.10" futex_wait_cancelable (private=, expected=0, futex_word=0x564932b1f298) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 13 Thread 0x7f0502ffd700 (LWP 32763) "gimp-2.10" futex_wait_cancelable (private=, expected=0, futex_word=0x564932b1f298) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 14 Thread 0x7f05027fc700 (LWP 32764) "gimp-2.10" futex_wait_cancelable (private=, expected=0, futex_word=0x564932b1f298) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 15 Thread 0x7f0510ff9700 (LWP 32765) "gimp-2.10" futex_wait_cancelable (private=, expected=0, futex_word=0x564932b1f298) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 16 Thread 0x7f0512ffd700 (LWP 632) "paint" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Thread 16 (Thread 0x7f0512ffd700 (LWP 632)): #0 0x7f055960b2e9 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f05598ef93f in g_cond_wait () at
[Bug 1836100] Re: Was able to migrate out of proposed despite breaking dkms
Deleting the glib2.0 task; it's not appropriate to hijack this bug report for a request on an unrelated package. ** No longer affects: glib2.0 (Ubuntu) ** Package changed: gcc-9 (Ubuntu) => auto-package-testing ** Changed in: auto-package-testing Status: Incomplete => Triaged -- 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/1836100 Title: Was able to migrate out of proposed despite breaking dkms To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1836100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836100] Re: Was able to migrate out of proposed despite breaking dkms
> No, this is not a gcc thing. But the kernel 5.2 now finally > getting built in eoan, and not binary copied from disco as > done for 5.0. Matthias, I agree with Seb's analysis here. The actual sequence of events is: - linux 5.0 in eoan was fixed to pass its build tests with the gcc in eoan, as seen in the history at http://autopkgtest.ubuntu.com/packages/l/linux/eoan/amd64 et al. - a new gcc-9 was uploaded (https://lists.ubuntu.com/archives/eoan-changes/2019-July/002800.html) which triggered a linux autopkgtest which rebuilt the kernel; however, because gcc-defaults still pointed at gcc-8, this did not actually test that the kernel was buildable with gcc-9. (e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/l/linux/20190705_005255_eec9e@/log.gz) - a new gcc-defaults was uploaded (https://lists.ubuntu.com/archives/eoan-changes/2019-July/002843.html) which switched the default gcc from gcc-8 to gcc-9, but this did *not* trigger an autopkgtest of the kernel, so the fact that the kernel regressed in buildability went unobserved and did not block the new gcc-defaults from reaching the release pocket. - reports began to come in about failing autopkgtests on a variety of dkms packages whose modules would no longer build using the gcc and linux-headers in the release pocket. - Dimitri (NOT the kernel team, though they would have been in their rights to have also done so) forward-copied https://launchpad.net/ubuntu/+source/linux/5.0.0-21.22 from disco to eoan-proposed. Because this was a binary copy, it did not trigger any build failures that would have notified the kernel team that there was a regression, nor did this trigger any autopkgtest rebuild tests (intentionally!) that would have identified the regression. However, the regression in the release pocket had already happened 2 steps above, because of the lack of gating of gcc-defaults; it was not caused by the sync of linux 5.0.0-21.22. - the kernel team uploads https://launchpad.net/ubuntu/+source/linux/5.2.0-8.9 which is compatible with gcc-9, fixing this problem in eoan-proposed - we are now waiting for linux to migrate in order for everything to return to normal. This does not mean that it is the responsibility of the gcc-9 package to fix this lack of gating. By design, autopkgtest gating works the other way around: the package which depends on your package, and which could regress, should declare its tests and catch any regressions. So this was definitely not a bug in gcc-9. It is *actually* a bug in the proposed-migration infrastructure, because the kernel and gcc are both special-cased there, and the special-case in question explicitly fails to include gcc-defaults in the set of packages triggering linux rebuild tests. -- 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/1836100 Title: Was able to migrate out of proposed despite breaking dkms To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1836100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836100] Re: Was able to migrate out of proposed despite breaking dkms
** Summary changed: - Was able to migrate out of proposed despite breaking dmks + Was able to migrate out of proposed despite breaking dkms -- 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/1836100 Title: Was able to migrate out of proposed despite breaking dkms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1836100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1691357] Re: User switch not possible, login screen black
** Changed in: gdm3 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => pawel (boreslaw5) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1691357 Title: User switch not possible, login screen black To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1691357/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1558337] Re: [AMD] Unable to Display on 16.04 Xenial Beta
** Changed in: gdm3 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => pawel (boreslaw5) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1558337 Title: [AMD] Unable to Display on 16.04 Xenial Beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1558337/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836100] Re: Was able to migrate out of proposed despite breaking dmks
so how should we glib2.0 stop migrating to the release pocket, when synced from experimental, and breaking builds? No, this is not a gcc thing. But the kernel 5.2 now finally getting built in eoan, and not binary copied from disco as done for 5.0. Blocking packages for having some build failures is not the thing we are currently doing. ** Changed in: gcc-9 (Ubuntu) Status: New => Incomplete ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- 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/1836100 Title: Was able to migrate out of proposed despite breaking dmks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1836100/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836026] Re: There is no the screen rotation option in Settings with sensor LNG2DM
The upstream bug is a kernel one so reassigning to that component ** Package changed: iio-sensor-proxy (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1836026 Title: There is no the screen rotation option in Settings with sensor LNG2DM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836026/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836019] Re: shotwell hangs with high cpu usage when dir contains many image
Thanks Jens for the upstream bug reference! ** Changed in: shotwell (Ubuntu) Importance: Undecided => High ** Changed in: shotwell (Ubuntu) Status: New => Triaged ** Also affects: ubuntuone-shotwell-plugin via https://bugzilla.gnome.org/show_bug.cgi?id=794678 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1836019 Title: shotwell hangs with high cpu usage when dir contains many image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuone-shotwell-plugin/+bug/1836019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836090] Re: From about a week, when I turn on the PC and open the application called file I have to try to open it at least 5 times before it really opens.
Thank you for your bug report. You are speaking about the 'Files' GNOME file manager right? (the package name is 'nautilus'). Could you add your 'journalctl -b 0' log after getting the issue? Also having a screencast/video from the problem would help to understand what you describe exactly ** Package changed: file (Ubuntu) => nautilus (Ubuntu) ** 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/1836090 Title: From about a week, when I turn on the PC and open the application called file I have to try to open it at least 5 times before it really opens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1836090/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836091] Re: Nautilus does not allow thumbnail for image size above 4096 KiB
Thank you for your bug report, could you also report that upstream on https://gitlab.gnome.org/GNOME/nautilus/issues ? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1836091 Title: Nautilus does not allow thumbnail for image size above 4096 KiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1836091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836090] [NEW] From about a week, when I turn on the PC and open the application called file I have to try to open it at least 5 times before it really opens.
You have been subscribed to a public bug: when I turn on the computer not only the file application I have to select it several times before accessing it but also firefox ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: file 1:5.35-4 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 10 18:16:31 2019 InstallationDate: Installed on 2019-07-02 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug disco -- >From about a week, when I turn on the PC and open the application called file >I have to try to open it at least 5 times before it really opens. https://bugs.launchpad.net/bugs/1836090 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 991002] Re: Use the modern English name Bangla instead of Bengali for the language code bn
Thanks Gunnar, I sponsored the change but renamed the patch to be prefixed with git- rather than ubuntu- and moved it in the serie before the ubuntu section since the change is not ubuntu specific ** Changed in: ibus (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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/991002 Title: Use the modern English name Bangla instead of Bengali for the language code bn To manage notifications about this bug go to: https://bugs.launchpad.net/cldr/+bug/991002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835956] Re: Deleting "Input Sources" not in use, affects the ones in use.
Thanks for the info, it's a bit puzzling still. I guess the behaviour was not only after adding but continuing after a session restart using the indicator/keybindings and not the settings? (in which case it's probably more a bug on the shell/server side). Also it would be good to report it upstream since they are likely to have a better understanding of those details (e.g on https://gitlab.gnome.org/GNOME/gnome-shell/) -- 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/1835956 Title: Deleting "Input Sources" not in use, affects the ones in use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1835956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 991002] Re: Use the modern English name Bangla instead of Bengali for the language code bn
The attached ibus debdiff is possibly the last piece in the puzzle to fix this Bengali -> Bangla transition in Ubuntu. ** Patch added: "ibus-lp991002.debdiff" https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/991002/+attachment/5276152/+files/ibus-lp991002.debdiff ** Tags added: patch ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New ** Changed in: ibus (Ubuntu) Importance: Undecided => Medium ** Changed in: ibus (Ubuntu) Status: New => In Progress ** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- 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/991002 Title: Use the modern English name Bangla instead of Bengali for the language code bn To manage notifications about this bug go to: https://bugs.launchpad.net/cldr/+bug/991002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835956] Re: Deleting "Input Sources" not in use, affects the ones in use.
So I tried something I hadn't tried before, and it worked I installed "Spanish" as input source, and deleted all the others, including English (which I never tried deleting before). With only this layout available, I checked, and it works just as I expect it to. After that, I added "English (US, intl., with dead keys) back again, and now both of the layouts work OK, the spanish one didn't get affected this time. So now, I have just the two layouts that I'll be using. Before this, I had 3 or 4 spanish layouts installed, but would use only one of them. Nevertheless, couldn't erase the ones I wouldn't use, because that would change the behaviour of the useful one, so I had to stick with all of them. Nevertheless, don't hesitate to ask for more information if it is needed to solve the bug I reported in the first place. Thank you! -- 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/1835956 Title: Deleting "Input Sources" not in use, affects the ones in use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1835956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 622542] Re: Search box should obtain focus at start up
** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #991 https://gitlab.gnome.org/GNOME/rhythmbox/issues/991 ** Changed in: rhythmbox Importance: Wishlist => Unknown ** Changed in: rhythmbox Status: Expired => Unknown ** Changed in: rhythmbox Remote watch: GNOME Bug Tracker #632013 => gitlab.gnome.org/GNOME/rhythmbox/issues #991 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/622542 Title: Search box should obtain focus at start up To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/622542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835928] Re: ``` GNU Image Manipulation Program version 2.10.12 git-describe: GIMP_2_10_10-209-g3d8535b55f C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-
¿Solucion? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1835928 Title: ``` GNU Image Manipulation Program version 2.10.12 git-describe: GIMP_2_10_10-209-g3d8535b55f C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux- gnu/7/lto-wrapper Target: i686-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable- languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program- prefix=i686-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable- threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx- time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable- default-pie --with-system-zlib --with-target-system-zlib --enable- objc-gc=auto --enable-targets=all --enable-multiarch --disable-werror --with-arch-32=i686 --with-multilib-list=m32,m64,mx32 --enable- multilib --with-tune=generic --enable-checking=release --build=i686 -linux-gnu --host=i686-linux-gnu --target=i686-linux-gnuThread model: posix gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) using GEGL version 0.4.16 (compiled against version 0.4.16) using GLib version 2.56.4 (compiled against version 2.56.4) using GdkPixbuf version 2.36.11 (compiled against version 2.36.11) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.40.14 (compiled against version 1.40.14) using Fontconfig version 2.12.6 (compiled against version 2.12.6) using Cairo version 1.15.10 (compiled against version 1.15.10) ``` > fatal error: Abortado Stack trace: ``` /usr/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x353)[0xb78633c3] gimp-2.10(+0x91ab0)[0x4acab0] gimp-2.10(+0x92111)[0x4ad111] gimp-2.10(+0x927ec)[0x4ad7ec] linux- gate.so.1(__kernel_sigreturn+0x0)[0xb7f40d14] linux- gate.so.1(__kernel_vsyscall+0x9)[0xb7f40d09] /lib/i386-linux- gnu/libc.so.6(gsignal+0xc2)[0xb6bf5832] /lib/i386-linux- gnu/libc.so.6(abort+0x121)[0xb6bf6cc1] /lib/i386-linux- gnu/libc.so.6(+0x257bb)[0xb6bed7bb] /lib/i386-linux- gnu/libc.so.6(+0x25819)[0xb6bed819] /usr/lib/i386-linux- gnu/libX11.so.6(+0x36e17)[0xb6aade17] /usr/lib/i386-linux- gnu/libX11.so.6(+0x36f1a)[0xb6aadf1a] /usr/lib/i386-linux- gnu/libX11.so.6(_XEventsQueued+0x72)[0xb6aae312] /usr/lib/i386-linux- gnu/libX11.so.6(XPending+0x6b)[0xb6a9f95b] /usr/lib/i386-linux- gnu/libgdk-x11-2.0.so.0(+0x51778)[0xb7917778] /usr/lib/i386-linux- gnu/libglib-2.0.so.0(g_main_context_check+0x1a2)[0xb6f12be2] /usr/lib/i386-linux-gnu/libglib-2.0.so.0(+0x49201)[0xb6f13201] /usr/lib/i386-linux- gnu/libglib-2.0.so.0(g_main_loop_run+0xf9)[0xb6f136b9] gimp-2.10(app_run+0x36d)[0x4ac46d] gimp-2.10(main+0x374)[0x4abc44] /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0xb6be0e81] gimp-2.10(+0x90e31)[0x4abe31] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1835928/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836091] [NEW] Nautilus does not allow thumbnail for image size above 4096 KiB
Public bug reported: In Ubuntu 18.10, Nautilus doesn't allow thumbnail size for image above 4096KiB. In preference pane, it is not possible to increase value above 4096. This is a regression, because it was possible before. By the way, whatever the value of dconf property org/gnome/nautilus/preferences /thumbnail-limit, if it is above 4096, Nautilus will not observe it (Setting the max image size for thumbnail generation in Nautilus preference pane is correctly changing org/gnome/nautilus/preferences /thumbnail-limit) Other funny things : the default value for org/gnome/nautilus/preferences/thumbnail-limit is 10MiB, so if it is at default value, Nautilus is showing (and observing) its hard-coded max of "4096" (4MiB) ! No workaround found as there is no anwser to this question: https://askubuntu.com/questions/1140576/nautilus-doesn-allow-thumbnail-for-image-size-above-4096-kib ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1836091 Title: Nautilus does not allow thumbnail for image size above 4096 KiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1836091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834583] Re: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus()
@fasaxc Thank you that is a handy workaround. -- 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/1834583 Title: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1834583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1826266] Re: Nautilus no longer copies file path when a file is marked then copied
Same thing here, it is really useful feature lost! It is really frustrating. -- 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/1826266 Title: Nautilus no longer copies file path when a file is marked then copied To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1826266/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1326817] Re: No multi-arch information in libgtksourceview2.0 control files
Fixed in 2.10.5-3 ** Changed in: gtksourceview2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtksourceview2 in Ubuntu. https://bugs.launchpad.net/bugs/1326817 Title: No multi-arch information in libgtksourceview2.0 control files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtksourceview2/+bug/1326817/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836051] Re: autamatic sleep notification cannot close
Thank you for your bug report. What desktop environment do you use? Can you make a screenshot of the issue? ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1836051 Title: autamatic sleep notification cannot close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1836051/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836051] Re: autamatic sleep notification cannot close
** Package changed: ubuntu-docs (Ubuntu) => gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Status: Invalid => 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/1836051 Title: autamatic sleep notification cannot close To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1836051/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768597] Re: [needs-packaging] package filemanager-actions missing
Great that it's in 19.04. Would be good to have available in current LTS release: 18.04 -- 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/1768597 Title: [needs-packaging] package filemanager-actions missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/filemanager-actions/+bug/1768597/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836051] [NEW] autamatic sleep notification cannot close
You have been subscribed to a public bug: I put my computer to sleep mode. 4 hours set afer no use. Vhen notification appeared, I put comp to sleep. After woke up, notification is still and can not close thru X. ubuntu-bug 18.04.2 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- autamatic sleep notification cannot close https://bugs.launchpad.net/bugs/1836051 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Nour Belguith (master-nour) -- 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/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836070] Re: seahorse crashed with signal 5
** 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 seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1836070 Title: seahorse crashed with signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1836070/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771880] Re: Seahorse unable to import pkcs12 certificates
You can ignore that upstream bug triager comment, Andre tends to dismiss reports based on first reporting version without checking if that's still an issue which is often the wrong thing to do, https://gitlab.gnome.org/GNOME/seahorse/issues/205 has a one week old comment stating that it's still a problem in 3.32 which is their current and supported version. -- 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/1771880 Title: Seahorse unable to import pkcs12 certificates To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1834583] Re: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus()
I was hitting this on disco-proposed. I found that it was resolved by setting an APT priority of -1 for disco-proposed and doing a dist- upgrade (i.e. downgrading all packages to disco-updates). I found that downgrading mutter and gnome-shell was insufficient (I guess there are lots of related libraries). -- 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/1834583 Title: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1834583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1771880] Re: Seahorse unable to import pkcs12 certificates
Well, after filling the report on GitLab, as suggested in comment #15, I receive the following statement from there: Andre Klapper @aklapper · 14 hours ago Developer You are using a version that is too old and not supported anymore by GNOME developers. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes by GNOME developers for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug report if the problem still occurs with a recent version of GNOME (3.32), or feel free to report this bug in the bug tracking system of your Linux distribution if your distribution still supports the version that you are using. --- I may well be wrong (I'm a lawyer, not a developer) but I understand that this issue is an "Ubuntu bug" not a "GNOME bug", as it apparently just happens in Ubuntu 18.04 LTS, which is supposed to be supported for 5 years until April 2023. Nevertheless, the solution was marked herea mere "wishlist". I assume no one will spend time trying to fix it, despite de lifespan support of Ubuntu 18.04 LTS is supposed to last 4 years more. That's sad! -- 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/1771880 Title: Seahorse unable to import pkcs12 certificates To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
It could be that Debian won't need this change. Looks like all the triggers are now processed near the end of upgrade, due to changes in dpkg itself. Possibly related entry from dpkg 1.19.3 changelog: * dpkg: Introduce a new dependency try level for trigger processing. This completely defers trigger processing until after the dependency cycle breaking level, so to avoid generating artificial trigger cycles, when we end up trying to process triggers with yet unsatisifiable dependencies. Closes: #810724, #854478, #911620 https://bugs.debian.org/810724 And from dpkg 1.19.7 changelog: * dpkg: Split the trigger dependtry into two, the second of which will be the one checking trigger cycles when deferring trigger processing due to unsatisfiable dependencies. Closes: #928429 https://bugs.debian.org/928429 ** Bug watch added: Debian Bug tracker #810724 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810724 ** Bug watch added: Debian Bug tracker #928429 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928429 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835625] Re: Shows old snap edge version of thunderbird
Re-opening per https://forum.snapcraft.io/t/future-maintaining- thunderbird/10845/5 ** Changed in: gnome-software (Ubuntu) Status: Invalid => New -- 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/1835625 Title: Shows old snap edge version of thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1835625/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722256] Re: Wifi connection status icon shows a "?" question mark when connected
Is this related ? "...a Connectivity Checking feature was introduced. Ubuntu 17.10 and onwards, you are presented with a question mark in network status whenever a Captive Portal is detected. This new feature works by pinging the http://connectivity-check.ubuntu.com URL, time to time, in order to detect a captive portal." https://vitux.com/disable-connectivity-checking-on-ubuntu-for-public-wifi-captive-portals/ -- 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/1722256 Title: Wifi connection status icon shows a "?" question mark when connected To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798790] Re: Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it)
I see 'Started bpfilter' at shutdown or restart and it hangs when closing down. I can just power off holding the power button but I know may be causing OS/ HDD issues in not closing down correctly. -- 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/1798790 Title: Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system (and setting WaylandEnable=false fixes it) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1798790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835969] Re: Categories expander is constantly broken
** Changed in: gnome-software Status: Unknown => Fix Released -- 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/1835969 Title: Categories expander is constantly broken To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1835969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836019] Re: shotwell hangs with high cpu usage when dir contains many image
Probably related: https://bugzilla.gnome.org/show_bug.cgi?id=794678 ** Bug watch added: bugzilla.gnome.org/ #794678 https://bugzilla.gnome.org/show_bug.cgi?id=794678 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1836019 Title: shotwell hangs with high cpu usage when dir contains many image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1836019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836026] [NEW] There is no the screen rotation option in Settings with sensor LNG2DM
Public bug reported: If a machine has a accelerometer, the screen rotation option won't be drawn in Settings. But, we cannot read the accelerometer raw data from the sensor LNG2DM. The value always is 0 in in_accel_x_raw, in_accel_y_raw and in_accel_y_raw. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=200775 ** Affects: iio-sensor-proxy (Ubuntu) Importance: Undecided Status: New ** Description changed: - If a machine has a g-sensor, the screen rotation option won't be drawn - in Settings. + If a machine has a accelerometer, the screen rotation option won't be + drawn in Settings. But, we cannot read the accelerometer raw data from the sensor LNG2DM. The value always is 0 in in_accel_x_raw, in_accel_y_raw and in_accel_y_raw. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=200775 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1836026 Title: There is no the screen rotation option in Settings with sensor LNG2DM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1836026/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1836019] [NEW] shotwell hangs with high cpu usage when dir contains many image
Public bug reported: After close shotwell >$ pgrep shotwell |wc -l >4 shotwell still run backgroud. with high cpu usage,. Load average: 5.95 5.02 3.80 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: shotwell 0.30.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 10 16:19:32 2019 InstallationDate: Installed on 2019-06-02 (37 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1836019 Title: shotwell hangs with high cpu usage when dir contains many image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1836019/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835969] Re: Categories expander is constantly broken
** Changed in: gnome-software (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu) Status: New => Fix Committed ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/issues #607 https://gitlab.gnome.org/GNOME/gnome-software/issues/607 ** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/issues/607 Importance: Unknown Status: Unknown -- 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/1835969 Title: Categories expander is constantly broken To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1835969/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1835956] Re: Deleting "Input Sources" not in use, affects the ones in use.
** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => 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/1835956 Title: Deleting "Input Sources" not in use, affects the ones in use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1835956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
