[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2133 https://gitlab.gnome.org/GNOME/mutter/-/issues/2133 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2133 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1532508 Title: Screen contents revealed briefly on resume, before even unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960383] [NEW] package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: While installing 21.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Feb 9 13:04:28 2022 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2022-02-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: i386 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.1 apt 2.0.6 SourcePackage: glib2.0 Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package focal i386 need-duplicate-check third-party-packages -- 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/1960383 Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1960383/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960379] [NEW] Gimp closes
Public bug reported:
```
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/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-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=x86_64-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-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 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:
```
# Stack traces obtained from PID 5362 - Thread 5362 #
[Nuevo LWP 5364]
[Nuevo LWP 5365]
[Nuevo LWP 5366]
[Nuevo LWP 5367]
[Nuevo LWP 5368]
[Nuevo LWP 5369]
[Nuevo LWP 5395]
[Depuración de hilo usando libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fb41128a384 in __libc_read (fd=20, buf=0x7ffd008c5250, nbytes=256) at
../sysdeps/unix/sysv/linux/read.c:27
Id Target Id Frame
* 1Thread 0x7fb4160a8e00 (LWP 5362) "gimp-2.10" 0x7fb41128a384 in
__libc_read (fd=20, buf=0x7ffd008c5250, nbytes=256) at
../sysdeps/unix/sysv/linux/read.c:27
2Thread 0x7fb408063700 (LWP 5364) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
3Thread 0x7fb407862700 (LWP 5365) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
4Thread 0x7fb407061700 (LWP 5366) "worker" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
5Thread 0x7fb3fe905700 (LWP 5367) "gmain" 0x7fb410f9cbf9 in
__GI___poll (fds=0x56225865eac0, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
6Thread 0x7fb3fe104700 (LWP 5368) "gdbus" 0x7fb410f9cbf9 in
__GI___poll (fds=0x562258670690, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
7Thread 0x7fb3d6497700 (LWP 5369) "async" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
8Thread 0x7fb3d508c700 (LWP 5395) "swap writer" syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
Thread 8 (Thread 0x7fb3d508c700 (LWP 5395)):
#0 0x7fb410fa3839 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7fb411acc77f in g_cond_wait () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7fb41312b931 in () at /usr/lib/x86_64-linux-gnu/libgegl-0.4.so.0
#3 0x7fb411aae195 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fb4112806db in start_thread (arg=0x7fb3d508c700) at
pthread_create.c:463
pd = 0x7fb3d508c700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140410349995776,
-5367516780689550350, 140410349992192, 0, 9470181968, 140724612643536,
5396743901917549554, 5398300539174327282}, mask_was_saved = 0}}, priv = {pad =
{0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call =
#5 0x7fb410fa988f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 7 (Thread 0x7fb3d6497700 (LWP 5369)):
#0 0x7fb410fa3839 in syscall () at
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1 0x7fb411acc77f in g_cond_wait () at
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x56225741bf0c in ()
#3 0x7fb411aae195 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x7fb4112806db in start_thread (arg=0x7fb3d6497700) at
pthread_create.c:463
pd = 0x7fb3d6497700
now =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140410371012352,
-5367516780689550350, 140410371008768, 0,
[Bug 1960336] Re: No login screen after recent update
To avoid confusion we should also not mention DisplayLink here. That's a separate issue so if you have problems with DisplayLink then please open a new bug about that. -- 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/1960336 Title: No login screen after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960336] Re: no login screen on Wayland with gdm3 after recent update
The login screen is provided by 'gnome-shell' so reassigning there. Also please run these commands to gather more information from the machine: apport-collect 1960336 lspci -k > lspci.txt journalctl -b-1 > prevboot.txt and attach the resulting text files here. In future please be sure to report bugs using the 'ubuntu-bug' command which will collect the required information automatically. ** Tags added: jammy ** Summary changed: - no login screen on Wayland with gdm3 after recent update + No login screen after recent update ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** 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 gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-42 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1738838 Title: Bluetooth icon shows "Off" and the only option given below it is "Turn Off" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: readline (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960339] [NEW] Problems setting Monday as first day of week
Public bug reported: I came across an interesting issue on my Ubuntu 21.10 machine. Originally I wanted to make the calendar applet in the shell menu to start the week on monday so I set up my language section according to the attached picture. Then I logged out from Gnome and nothing had changed when I logged back in. Pursuing this issue a bit further I thought of using gnome-calendar to isolate the problem but when I started the program from the application launcher, I noticed that gnome-calendar also had sunday as first day of the week. Digging a little deeper among the tips found through Google, I came across a post suggesting to set up my locale to deal with this situation: > locale LANG=sv_SE.UTF-8 LANGUAGE=en LC_CTYPE=sv_SE.UTF-8 LC_NUMERIC=sv_SE.UTF-8 LC_TIME=sv_SE.UTF-8 LC_COLLATE=sv_SE.UTF-8 LC_MONETARY=sv_SE.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=sv_SE.UTF-8 LC_NAME=sv_SE.UTF-8 LC_ADDRESS=sv_SE.UTF-8 LC_TELEPHONE=sv_SE.UTF-8 LC_MEASUREMENT=sv_SE.UTF-8 LC_IDENTIFICATION=sv_SE.UTF-8 LC_ALL= > grep first_weekday /usr/share/i18n/locales/sv_SE first_weekday 2 So, I tried starting gnome-calendar from my gnome-terminal, where I knew the regional settings were correct, and I still got the issue with sunday being the first day of the week. For no real reason I restarted the application just to make sure I hadn't committed a user error but the problem still persisted. Being a bit frustrated at the point I rage- quit the program and just as I did that I realised I had to check an appointment so I quickly started gnome-calendar from the same terminal again and got an error message GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying When I re-tried starting gnome-calendar from the same terminal again, the application launched and this time with monday as first day of the week. Steps to reproduce 1. Start gnome-terminal 2. In terminal, issue command gnome-calendar 3. Quit Calendar and issue command gnome-calendar again in the same terminal two more times until error message appears as described above 4. Issue command gnome-calendar 5. Observe start of week is monday (as expected) This problem only seems to occur when I start the X11 session. I logged into the Wayland session to look at another problem and noticed that the calendar applet in the shell had monday as first day of the week. Starting gnome-calendar (from the shell menu) also presented me with a calendar where monday was the first day of the week. Logging out and into the X11 session again made the problem, as originally described above, re-appear. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-calendar 41.0-1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Feb 8 17:01:43 2022 InstallationDate: Installed on 2021-10-20 (111 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome-calendar impish ** Attachment added: "Language settings" https://bugs.launchpad.net/bugs/1960339/+attachment/5559743/+files/Screenshot%20from%202021-12-10%2018-04-17.png -- 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/1960339 Title: Problems setting Monday as first day of week To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1960339/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
I can confirm the same intermittent issue and I also have Keybase installed. I don't recall having the issue prior to installing it. -- 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/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1951075] Re: Nautilus doesn't load and gives GVFS-WARNING
I've been experiencing the same (intermittent) symptom on a relatively new install. It's hard to be sure, but I think I've resolved it by disabling keybase. -- 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/1951075 Title: Nautilus doesn't load and gives GVFS-WARNING To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1951075/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960336] [NEW] no login screen on Wayland with gdm3 after recent update
Public bug reported: After a recent update, when using gdm3 as login manager, there is no account visible and it is not possible to login. When switching to lightdm I can login but sleep is broken and some notifications do not work. Running the latest 22.04 dev branch with Wayland and Nvidia driver. Had to select kernel 5.12 to have display link working. This issue occurs with and without external displays attached. A recent attempt to switch back to gdm3 gave me just a black screen. I tried to reinstall gdm3 to no avail. This seems like a quite serious issue, hence this report for the dev version. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- 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/1960336 Title: no login screen on Wayland with gdm3 after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866999] Re: gnome-calendar does not sync with Google Calendar
I'm on Ubuntu 20.04 with gnome-calendar 3.36.2 and have the same problem: Google calendar did not sync. Then I removed the cache in "~/.cache/evolution/calendar/", and gnome calendar showed no appointments at all (as expected). Clicking the "sync now" menu item changed the calendar icon briefly to a checkmark, but "journalctrl -f" said: > Feb 08 13:28:20 sybo gnome-calendar[17021]: Error synchronizing client > Feb 08 13:28:20 sybo gnome-calendar[17021]: Error synchronizing client > Feb 08 13:28:20 sybo gnome-calendar[17021]: Error synchronizing client for every calendar, enabled or not. -- 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/1866999 Title: gnome-calendar does not sync with Google Calendar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
@Paride Thanks for your help and explanations. Yeah I know what multi- arch does although I didn't know about 'Multi-Arch: foreign' - so thank you very much for the pointers. @Christian I have uploaded the updated package to mentors on Sunday. It was prepared on Ubuntu, though, I guess it is better when to redo the steps through a debian chroot - I hope I come to that in the evening. https://mentors.debian.net/package/unionfs-fuse/ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
FYI the re-upload of a fuse3 open-vm-tools happened yesterday and it migrated to jammy-release. Any issues with the images? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
