[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Peter Ryan]

Thanks - this fix appears to have resolved my lag issues.

OS: Ubuntu 22.04.04 LTS
$XDG_SESSION_TYPE: x11
nVidia: 535.171.04

Mobo/CPU: MSI MAG B550M BAZOOKA / AMD Ryzen 5 5600X
Video card: MSI GeForce GT1030 2GB PCI Express

Mostly this was affecting Gnome terminal for me, but just prior to
applying this patch (thanks again!!) I used GnuCash and that lagged too.

-- 
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/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

[Peter Sabaini]

Just as a datapoint, the PPA has resolved my lag issues on my
Nvidia/xorg setup.

Thanks!


Details:

Ubuntu 22.04.4 LTS

modinfo nvidia
...
version:535.171.04


I had those `MetaSyncRing: Sync object is not ready -- were events handled 
properly?` journal entries as well, and did not reappear after PPA upgrade

-- 
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/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2055044] Re: GIMP crash at closure

[Peter Freeth]

The crash only occurs when closing GIMP with an open unsaved image and
selecting 'Discard'. If all images are closed first, GIMP can be closed
normally.

-- 
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/2055044

Title:
  GIMP crash at closure

To manage notifications about this bug go to:
https://bugs.launchpad.net/gimp/+bug/2055044/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2061980] ProcEnviron.txt

[Peter Freeth]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/2061980/+attachment/5766749/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/2061980

Title:
  GIMP crashes instead of closing normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2061980/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2061980] Re: GIMP crashes instead of closing normally

[Peter Freeth]

apport information

** Tags added: apport-collected noble wayland-session

** Description changed:

  Whenever I close GIMP, instead of closing normally it crashes.
  
  This happens only when I close GIMP with an image open. I click Discard
  because I don't want to save the image and GIMP crashes instead of
  closing. If I close and discard the image first, GIMP closes normally.
  
  This happened on both Ubuntu 23.10 and 24.04 beta
  
  
  
  ```
  GNU Image Manipulation Program version 2.10.36
  git-describe: GIMP_2_10_36
  Build: unknown rev 0 for linux
  # C compiler #
   Using built-in specs.
   COLLECT_GCC=gcc
   COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
   OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
   OFFLOAD_TARGET_DEFAULT=1
   Target: x86_64-linux-gnu
   Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --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-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
   Thread model: posix
   Supported LTO compression algorithms: zlib zstd
   gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3)
  
  # Libraries #
  using babl version 0.1.108 (compiled against version 0.1.108)
  using GEGL version 0.4.48 (compiled against version 0.4.48)
  using GLib version 2.80.0 (compiled against version 2.80.0)
  using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
  using GTK+ version 2.24.33 (compiled against version 2.24.33)
  using Pango version 1.52.1 (compiled against version 1.52.1)
  using Fontconfig version 2.15.0 (compiled against version 2.15.0)
  using Cairo version 1.18.0 (compiled against version 1.18.0)
  
  ```
  > fatal error: Segmentation fault
  
  Stack trace:
  ```
  
  # Stack traces obtained from PID 459153 - Thread 459153 #
  
  This GDB supports auto-downloading debuginfo from the following URLs:
    
  Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
  Debuginfod has been disabled.
  To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
  [New LWP 459629]
  [New LWP 459230]
  [New LWP 459202]
  [New LWP 459193]
  [New LWP 459180]
  [New LWP 459179]
  [New LWP 459178]
  [New LWP 459166]
  [New LWP 459165]
  [New LWP 459164]
  [New LWP 459163]
  [New LWP 459162]
  [New LWP 459161]
  [New LWP 459160]
  [New LWP 459159]
  [New LWP 459158]
  [New LWP 459157]
  [New LWP 459156]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fa475ca9c00 in malloc_consolidate (av=av@entry=0x7fa475e03ac0 
) at ./malloc/malloc.c:4878
    Id   Target Id Frame
  * 1Thread 0x7fa4756f2640 (LWP 459153) "gimp-2.10"0x7fa475ca9c00 
in malloc_consolidate (av=av@entry=0x7fa475e03ac0 ) at 
./malloc/malloc.c:4878
    2Thread 0x7fa42fe006c0 (LWP 459629) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
    3Thread 0x7fa42da006c0 (LWP 459230) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
    4Thread 0x7fa42f4006c0 (LWP 459202) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
    5Thread 0x7fa43cc006c0 (LWP 459193) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
    6Thread 0x7fa44be006c0 (LWP 459180) "gdbus"0x7fa475d1b4cd 
in __GI___poll (fds=0x7fa41c000b90, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
    7Thread 0x7fa44b4006c0 (LWP 459179) "gmain"0x7fa475d1b4cd 
in __GI___poll (fds=0x5ac102ca5050, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
    8Thread 0x7fa44aa006c0 (LWP 459178) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
    9Thread 0x7fa469e006c0 (LWP 459166) "worker"   syscall () at 

[Bug 2061980] ProcCpuinfoMinimal.txt

[Peter Freeth]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2061980/+attachment/5766748/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/2061980

Title:
  GIMP crashes instead of closing normally

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/2061980/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2061980] Re: GIMP crashes instead of closing normally

[Peter Freeth]

** Description changed:

  Whenever I close GIMP, instead of closing normally it crashes.
  
+ This happens only when I close GIMP with an image open. I click Discard
+ because I don't want to save the image and GIMP crashes instead of
+ closing. If I close and discard the image first, GIMP closes normally.
+ 
  This happened on both Ubuntu 23.10 and 24.04 beta
  
- 
  
- 
  
  ```
  GNU Image Manipulation Program version 2.10.36
  git-describe: GIMP_2_10_36
  Build: unknown rev 0 for linux
  # C compiler #
-   Using built-in specs.
-   COLLECT_GCC=gcc
-   COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
-   OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
-   OFFLOAD_TARGET_DEFAULT=1
-   Target: x86_64-linux-gnu
-   Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --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-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
-   Thread model: posix
-   Supported LTO compression algorithms: zlib zstd
-   gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) 
+  Using built-in specs.
+  COLLECT_GCC=gcc
+  COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
+  OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
+  OFFLOAD_TARGET_DEFAULT=1
+  Target: x86_64-linux-gnu
+  Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --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-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
+  Thread model: posix
+  Supported LTO compression algorithms: zlib zstd
+  gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3)
  
  # Libraries #
  using babl version 0.1.108 (compiled against version 0.1.108)
  using GEGL version 0.4.48 (compiled against version 0.4.48)
  using GLib version 2.80.0 (compiled against version 2.80.0)
  using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
  using GTK+ version 2.24.33 (compiled against version 2.24.33)
  using Pango version 1.52.1 (compiled against version 1.52.1)
  using Fontconfig version 2.15.0 (compiled against version 2.15.0)
  using Cairo version 1.18.0 (compiled against version 1.18.0)
  
  ```
  > fatal error: Segmentation fault
  
  Stack trace:
  ```
  
  # Stack traces obtained from PID 459153 - Thread 459153 #
  
- 
  This GDB supports auto-downloading debuginfo from the following URLs:
-   
+   
  Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
  Debuginfod has been disabled.
  To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
  [New LWP 459629]
  [New LWP 459230]
  [New LWP 459202]
  [New LWP 459193]
  [New LWP 459180]
  [New LWP 459179]
  [New LWP 459178]
  [New LWP 459166]
  [New LWP 459165]
  [New LWP 459164]
  [New LWP 459163]
  

[Bug 2061980] [NEW] GIMP crashes instead of closing normally

[Peter Freeth]

Public bug reported:

Whenever I close GIMP, instead of closing normally it crashes.

This happened on both Ubuntu 23.10 and 24.04 beta





```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --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-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 459153 - Thread 459153 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 459629]
[New LWP 459230]
[New LWP 459202]
[New LWP 459193]
[New LWP 459180]
[New LWP 459179]
[New LWP 459178]
[New LWP 459166]
[New LWP 459165]
[New LWP 459164]
[New LWP 459163]
[New LWP 459162]
[New LWP 459161]
[New LWP 459160]
[New LWP 459159]
[New LWP 459158]
[New LWP 459157]
[New LWP 459156]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fa475ca9c00 in malloc_consolidate (av=av@entry=0x7fa475e03ac0 
) at ./malloc/malloc.c:4878
  Id   Target Id Frame 
* 1Thread 0x7fa4756f2640 (LWP 459153) "gimp-2.10"0x7fa475ca9c00 in 
malloc_consolidate (av=av@entry=0x7fa475e03ac0 ) at 
./malloc/malloc.c:4878
  2Thread 0x7fa42fe006c0 (LWP 459629) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7fa42da006c0 (LWP 459230) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7fa42f4006c0 (LWP 459202) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7fa43cc006c0 (LWP 459193) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7fa44be006c0 (LWP 459180) "gdbus"0x7fa475d1b4cd in 
__GI___poll (fds=0x7fa41c000b90, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7fa44b4006c0 (LWP 459179) "gmain"0x7fa475d1b4cd in 
__GI___poll (fds=0x5ac102ca5050, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7fa44aa006c0 (LWP 459178) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7fa469e006c0 (LWP 459166) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7fa46a8006c0 (LWP 459165) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7fa46be006c0 (LWP 459164) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7fa470a006c0 (LWP 459163) "worker"   syscall () at 

[Bug 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed

[Peter Goodall]

I have it in ubuntu 22.04

Feb 21 13:59:49 <> gnome-session[3662]: gnome-session-binary[3662]:
GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error ==
NULL' failed

-- 
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/1968907

Title:
  GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error
  == NULL' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1968907/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2048892] [NEW] Newer minor version release available

[Peter Eisenmann]

Public bug reported:

Hi, I wanted to point out that a newer version of nautilus 45 available.
The release candidate shipped in Ubuntu is not meant to be packaged by
distributions, as it is pre-release software and does potentially not
include fixes made before release.

See e.g. https://gitlab.gnome.org/GNOME/nautilus/-/tags/45.2.1 or .
https://gitlab.gnome.org/GNOME/nautilus/-/tags/45.1 which is available
in Debian unstable.

Thank you for your consideration.

** 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/2048892

Title:
  Newer minor version release available

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2048892/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Peter]

Also FWIW, I don't think this issue is due to external/3rd-party packages, I 
have never used PPAs and have no third-party packages at all:
 
> pro security-status --thirdparty
1794 packages installed:
 0 packages from third parties

You have no packages installed from a third party.

-- 
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/2043395

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Peter]

@razielanarki
If you `apt-get remove gnome-remote-desktop`, does the upgrade work then?

-- 
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/2043395

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Peter]

** Attachment added: "apt.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+attachment/5719403/+files/apt.log

-- 
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/2043395

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Peter]

@jbicha 
Which files are those are those in? /var/log/dist-upgrade/apt.log for apt logs 
I assume but where can I find full upgrader logs?


I worked around this issue by removing gnome-remote-desktop, and installing 
ubuntu-desktop in addition to ubuntu-desktop-minimal, and then the upgrade 
worked (somewhat - see 
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/2043394 ) so I 
can't reproduce now as I'm on 23.10

-- 
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/2043395

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2043395] Re: Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Peter]

** Description changed:

- Running do-release-upgrade on a 23.04 (lunar), **ubuntu-desktop-minimal
+ Running do-release-upgrade on 23.04 (lunar), **ubuntu-desktop-minimal
  based** install:
  
  2023-11-10 07:03:16,578 DEBUG nvidiaUpdate()
  2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new
  2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache
  2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35
  2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36
  2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
  2023-11-10 07:03:20,564 DEBUG abort called

-- 
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/2043395

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2043395] [NEW] Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop & gnome-shell packages are broken

[Peter]

Public bug reported:

Running do-release-upgrade on a 23.04 (lunar), **ubuntu-desktop-minimal
based** install:

2023-11-10 07:03:16,578 DEBUG nvidiaUpdate()
2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new
2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache
2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache
2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with
2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35
2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36
2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
2023-11-10 07:03:20,564 DEBUG abort called

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: gnome-remote-desktop (Ubuntu) => gnome-shell
(Ubuntu)

** Description changed:

- Running do-release-upgrade on 23.04 (lunar), an ubuntu-desktop-minimal
- based install:
+ Running do-release-upgrade on a 23.04 (lunar), **ubuntu-desktop-minimal
+ based** install:
  
  2023-11-10 07:03:16,578 DEBUG nvidiaUpdate()
  2023-11-10 07:03:20,125 INFO no old nvidia driver installed, installing no new
  2023-11-10 07:03:20,125 DEBUG quirks: running PostDistUpgradeCache
  2023-11-10 07:03:20,125 DEBUG running Quirks.PostDistUpgradeCache
- 2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with 
+ 2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-35 with
  2023-11-10 07:03:20,237 DEBUG Comparing 6.2.0-36 with 6.2.0-35
  2023-11-10 07:03:20,238 DEBUG Comparing 6.5.0-10 with 6.2.0-36
  2023-11-10 07:03:20,554 ERROR Dist-upgrade failed: 'Broken packages after 
upgrade: gnome-remote-desktop, gnome-shell'
  2023-11-10 07:03:20,564 DEBUG abort called

-- 
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/2043395

Title:
  Updating to Ubuntu 23.10 (mantic) fails as the gnome-remote-desktop &
  gnome-shell packages are broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2043395/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1970921] Re: Drag and drop does not work

[Peter Freeth]

23.10, yes the problem is still there. I had switched to X11 to solve
this, but Wacom tablet is now broken under X11 so I have moved back to
Wayland. Drag and drop to Chrome to upload a file to a website doesn't
work, the web page responds as if it knows a file is being dropped onto
it, but the upload doesn't happen.

Oddly, if I select the file manually (which doesn't work for the
multiple files that I usually upload) then that works, and after that,
drag and drop then works again.

-- 
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/1970921

Title:
  Drag and drop does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1970921/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2037151] Re: Chromium glitches, Brave too, might be GPU

[Peter Fisera]

note:  i wrote "chromium-browser"as SourcePackage, not gnome-panel (as
it says above), that's the default value for that text box.  problem in
the form?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/2037151

Title:
  Chromium glitches, Brave too, might be GPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/2037151/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2037151] [NEW] Chromium glitches, Brave too, might be GPU

[Peter Fisera]

Public bug reported:

Hi there! I have a theory what this problem is, and i am going to post
it in detail here https://bugs.launchpad.net/ubuntu/+source/chromium-
browser/+bug/2037093

This was not supposed to be a "new" bug report, I wanted to use Apport
and somehow attach my Apport output to an *existing* bug thread in
bugs.launchpad.net   Is there a way to do that?

short version:  i think its very similar to this:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2035360
also, Brave has already fixed the issue, i got a snap update from them
about 8 hours ago and YES it fixed it.  know anyone on their tech team
who can tell you how they fixed it? ;-);-)

cheers
Peter Fisera 
https://earthangelconsulting.com

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-panel 1:3.44.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Flashback:GNOME
Date: Fri Sep 22 20:25:51 2023
ExecutablePath: /usr/bin/gnome-panel
GsettingsChanges:
 b'org.gnome.gnome-panel.layout' b'object-id-list' b"['menu-bar', 'indicators', 
'show-desktop', 'window-list', 'workspace-switcher', 'launcher', 'launcher-0', 
'launcher-1', 'launcher-2', 'launcher-3', 'launcher-4', 'launcher-5', 
'launcher-6', 'launcher-7', 'launcher-8', 'launcher-9', 'launcher-10', 
'launcher-11', 'launcher-12', 'launcher-13', 'launcher-14', 'launcher-15', 
'launcher-16', 'launcher-17', 'launcher-18', 'launcher-19', 'launcher-20', 
'launcher-21', 'launcher-22', 'launcher-23', 'launcher-24', 'launcher-25', 
'launcher-26', 'launcher-27', 'launcher-28', 'launcher-29']"
 b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['top-panel', 
'bottom-panel']"
InstallationDate: Installed on 2021-11-17 (675 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
UpgradeStatus: Upgraded to jammy on 2023-02-20 (215 days ago)

** Affects: gnome-panel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bug-id-2037093 chromium.gpu.glitch jammy 
third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/2037151

Title:
  Chromium glitches, Brave too, might be GPU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/2037151/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2025308] [NEW] package appstream 0.15.2-2 failed to install/upgrade: installed appstream package post-installation script subprocess returned error exit status 1

[dave peter]

Public bug reported:

unknown

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: appstream 0.15.2-2
Uname: Linux 5.10.104-tegra aarch64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: arm64
CasperMD5CheckResult: unknown
Date: Wed Jun 28 21:47:23 2023
ErrorMessage: installed appstream package post-installation script subprocess 
returned error exit status 1
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.9
SourcePackage: appstream
Title: package appstream 0.15.2-2 failed to install/upgrade: installed 
appstream package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to jammy on 2023-06-29 (0 days ago)

** Affects: appstream (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 jammy

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/2025308

Title:
  package appstream 0.15.2-2 failed to install/upgrade: installed
  appstream package post-installation script subprocess returned error
  exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/2025308/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

[Peter Havekes]

I enabled the -proposed repository and lowered the priority, then i
updated mutter and gnome shell:

sudo apt-get install mutter/lunar-proposed gnome-shell/lunar-proposed

This fixed the raise issue for me. I do not use SNAP applications, so I
can't test that

-- 
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/2013216

Title:
  Single click on title bar does not transfer focus to target window
  (server side decorations in Xorg sessions)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2018731] Re: Graphics memory (VRAM) leak in mutter-x11-frames

[Peter de Kraker]

I have 3GB of GPU RAM usage by mutter-x11-frames (and my gpu only has 8GB total)
nvidia-smi:
```
 /usr/libexec/mutter-x11-frames 3348MiB
```
Ubuntu 23.04
Kernel 6.2.0-20-generic
Nvidia 530.41.03  
GTX 3070 Ti
Desktop with one 4K screen, 200% scaling.

-- 
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/2018731

Title:
  Graphics memory (VRAM) leak in mutter-x11-frames

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2018731/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2013216] Re: Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions)

[Peter Freeth]

Same problem as soon as I upgraded to 23.04. Gnome 44.0 Linux
6.2.0-20-generic.

If I move a lower window by its title bar then it raises to the top, but
if I just click on it then stays below. This is a problem because
clicking in a window's active area to raise it is likely to change
something in that window. For example if the lower window is a graphics
program then clicking in the active area could change the image I'm
working on without me realising. I need to click on the titlebar as it
is a 'neutral' area.

-- 
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/2013216

Title:
  Single click on title bar does not transfer focus to target window
  (server side decorations in Xorg sessions)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2013216/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Peter Klausner]

Recent Ubuntu 22.04.2 LTS, libgtk-4-common 4.6.6+ds-0ubuntu1,
libgtk-3-common 3.24.33-1ubuntu2,vivaldi-stable 5.7.2921.65-1

'Save as' dialog now works as expected: focus is on filename keyboard
entry,  immediately closes dialog.

BAD regression:  
Vivaldi window is frozen after that. Does not happen with other distros, cf 
https://forum.vivaldi.net/topic/85488/bug-saving-a-web-page-freezes-browser-window

This is since about 1 week now. As I got used to mousing my way around
the previous bug, I did not immediately notice the changed behaviour.
Except the browser hang, of course.

-- 
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/1949340

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2015347] Re: Regression: GTK statusbars look very weird on 200% scaling

[Peter de Kraker]

With latest apt-get update it is now solved.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2015347

Title:
  Regression: GTK statusbars look very weird on 200% scaling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2015347/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2015347] [NEW] Regression: GTK statusbars look very weird on 200% scaling

[Peter de Kraker]

Public bug reported:

I don't know where I need to report this bug, but it's quite a serious
one.

On both livecd and installed version of Ubuntu 23.04 the statusbars of
some applications (for example libreoffice, Visual Studio Code, the
keychain dialog when logging in and more) are really small and weird
looking when using Gnome with 200% scaling.

https://pasteboard.co/S0idNZig1HEV.png

It looks like the legacy compatibility mode of GTK for these apps
doesn't take into account scaling. This worked properly on 22.10 and
earlier.

System:
Ubuntu 23.04 beta
NVIDIA RTX 3070Ti (nvidia drivers on install, nouveau I guess on livecd)

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Schermafdruk van 2023-04-02 17-20-37.png"
   
https://bugs.launchpad.net/bugs/2015347/+attachment/5661187/+files/Schermafdruk%20van%202023-04-02%2017-20-37.png

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2015347

Title:
  Regression: GTK statusbars look very weird on 200% scaling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2015347/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2009893] Re: gnome-control-center online-accounts nextcloud handling crashes when changing options

[Peter Rhone]

It wasn't a crash. The nextcloud options dialog locks up when changing
options, and the wrong server accounts are added when using multiple
nextcloud accounts for browsing remote files.

-- 
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/2009893

Title:
  gnome-control-center online-accounts nextcloud handling crashes when
  changing options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2009893/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2009893] Re: gnome-control-center online-accounts nextcloud handling crashes when changing options

[Peter Rhone]

Actually this might be a gnome-online-accounts bug

-- 
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/2009893

Title:
  gnome-control-center online-accounts nextcloud handling crashes when
  changing options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2009893/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2009893] [NEW] gnome-control-center online-accounts nextcloud handling crashes when changing options

[Peter Rhone]

Public bug reported:

I added 3 nextcloud accounts via the "online accounts" option in gnome-
control-center.

If you click on any of the added nextcloud accounts and attempt to
change any of the three options [Calendar, Contacts, Files] in the pop-
up dialog window, the dialog becomes unresponsive and must be force-
closed with xkill.

Furthermore, if I select the 'files' option on the three different
nextcloud accounts, gnome-files duly adds three remote drives, but
unfortunately it adds the first account from 'online accounts' three
times. The expected behaviour is to be able to mount and browse the
files in each of the nextcloud accounts, not have three identical mount
points repeated.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-control-center 1:44~alpha-0ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  9 22:33:16 2023
InstallationDate: Installed on 2020-06-20 (992 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to lunar on 2022-12-21 (78 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug lunar

-- 
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/2009893

Title:
  gnome-control-center online-accounts nextcloud handling crashes when
  changing options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2009893/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1796649] Re: gjs-console crashed with SIGABRT in g_assertion_message()

[Peter]

Any update on this? Still experiencing this issue on Ubuntu 22.10

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1796649

Title:
  gjs-console crashed with SIGABRT in g_assertion_message()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1796649/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Peter Klausner]

This bug is mighty annoying. E.g. you can't simply type  to get out
of the save dialog, if you wrongly typed . You first need to
mouse the pointer to the text field.

-- 
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/1949340

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1872230] Re: The left Ctrl key does not work with key combos when using pointer location in Xorg sessions

[Peter Englmaier]

I can also confirm this bug in ubuntu 20.04.5 / gnome version 3.36.8 / X11.
Turning the pointer location feature off (gnome-tweaks), the left control key 
is working again.

It happens in remote sessions only, in particular with the citrix
workspace app.

-- 
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/1872230

Title:
  The left Ctrl key does not work with key combos when using pointer
  location in Xorg sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1872230/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Peter Klausner]

For 22.04, I can additionally confirm the problem for Vivaldi's save dialog.
Whereas the seemingly identical dialog in LibreOffice works as intended.

-- 
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/1949340

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height

[Peter Ryan]

@martin-weinberg-5 I tried the dconf write as you suggested, and I did
alt-F2 and "r" to restart Gnome, but it doesn't seem to have changed
anything.

***As I wrote the above, I remembered that I'd left some terminal
windows open during the process. I've re-tested but closed all windows
before restarting Gnome and it *does* resolve the problem. However, I
now have a menu bar on all my terminal windows. (screen grab attached
for the benefit of others).

For the moment, I'll reset that entry:
dconf reset /org/gnome/terminal/legacy/headerbar

..but hopefully that will help a little in figuring out where the
underlying bug is.


** Attachment added: "Screenshot of gnome terminal with headerbar set to @mb 
false via dconf"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+attachment/5618395/+files/Screenshot%20from%202022-09-23%2012-21-45.png

-- 
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/1288655

Title:
  Terminal height shrinks - repeatedly restored shorter than the
  previous height

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1288655] Re: Terminal height shrinks - repeatedly restored shorter than the previous height

[Peter Ryan]

@prohlep
I fresh installed Ubuntu 22.04 (64-bit) on 27th April 2022 and this is still 
occurring for me.
(Hopefully) video attached of me opening three terminal windows, and then 
pressing F11 to toggle one of them to/from full screen.

** Attachment added: "Video of terminal window with effect of F11 / full screen 
toggling"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1288655/+attachment/5618087/+files/Screencast%20from%2022-09-22%2015%3A16%3A06.webm

-- 
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/1288655

Title:
  Terminal height shrinks - repeatedly restored shorter than the
  previous height

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1288655/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [Bug 1986510] Re: No settings options for "Dock" under setting>>appearance

[Mbwabwa ivan peter]

This solved the problem. Thank you

On Thu, Aug 18, 2022 at 4:11 PM Jeremy Bicha <1986...@bugs.launchpad.net>
wrote:

> Please run this command in a terminal:
>
> sudo apt install ubuntu-desktop
>
> Then log out and log back in.
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1986510
>
> Title:
>   No settings options for "Dock" under setting>>appearance
>
> Status in gnome-control-center package in Ubuntu:
>   Incomplete
>
> Bug description:
>   There are no options for customizing the Dock under
>   settings>>appearance.
>
>   Even withe gnome-tweaks installed, the options don't show up.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: ubuntu-release-upgrader-core 1:22.04.13
>   ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
>   Uname: Linux 5.15.0-46-generic x86_64
>   NonfreeKernelModules: wl nvidia_modeset nvidia
>   ApportVersion: 2.20.11-0ubuntu82.1
>   Architecture: amd64
>   CasperMD5CheckResult: unknown
>   CrashDB: ubuntu
>   CurrentDesktop: ubuntu:GNOME
>   Date: Mon Aug 15 11:01:15 2022
>   InstallationDate: Installed on 2020-02-03 (924 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
>   PackageArchitecture: all
>   SourcePackage: ubuntu-release-upgrader
>   Symptom: release-upgrade
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   VarLogDistupgradeTermlog:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986510/+subscriptions
>
>

-- 
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/1986510

Title:
  No settings options for "Dock" under setting>>appearance

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1986510/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1875285] Re: Fractional scaling zooms to 200% and crops half the screen

[Peter Roelants]

Same Issue here on Lenovo P1 with Nvidia Quadro T1000 (see attached
screenshot which is a picture of my secondary monitor).

I cannot use fractional scaling with a secondary monitor, the scaling
zooms to 200% and crops part the screen on the secondary monitor.

I have had this issue with both 20.04 and 22.04 X-Window manager
(Wayland doesn't even work on my Lenovo...)

** Attachment added: "Desktop Fraction Scaling Issue"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+attachment/5598757/+files/IMG_20220621_223853.jpg

-- 
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/1875285

Title:
  Fractional scaling zooms to 200% and crops half the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1875285] Re: Fractional scaling zooms to 200% and crops half the screen

[Peter Roelants]

Same Issue here on Lenovo P1 with Nvidia Quadro T1000 (see attached
screenshot which is a picture of my secondary monitor).

I cannot use fractional scaling with a secondary monitor, the scaling
zooms to 200% and crops part the screen on the secondary monitor.

I have had this issue with both 20.04 and 22.04 X-Window manager
(Wayland doesn't even work on my Lenovo...)

** Attachment added: "Desktop Fraction Scaling Issue"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+attachment/5598756/+files/IMG_20220621_223853.jpg

-- 
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/1875285

Title:
  Fractional scaling zooms to 200% and crops half the screen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1875285/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1971752] [NEW] Toggling F11 for fullscreen reduces the restored window size

[Peter Ryan]

Public bug reported:

When I open a Gnome Terminal window at a given size (say 80 columns x 24
rows), press F11 to go full-screen, and then press F11 to restore the
window to it's original size, it will be a bit smaller! It will lose
both height and width.

If I keep toggling with F11, the window will reduce to 3 lines and...
I'm not sure exactly how many columns, but it's less than it had.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-terminal 3.44.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May  5 18:03:50 2022
InstallationDate: Installed on 2022-04-26 (8 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
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/1971752

Title:
  Toggling F11 for fullscreen reduces the restored window size

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1971752/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1968026] [NEW] right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo does work. All works with a PS2 keyboard

[Peter Burnett]

Public bug reported:

Left-Alt always works.
This has been the case with Ubuntu, Kubuntu, and Lubuntu for years.
r-e-i-s-u-b, printscrn, print scrn, printscreen, print screen, SysRq, SysReq

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  6 09:45:00 2022
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb', 'au'), 
('xkb', 'cm'), ('xkb', 'gb')]"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
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/1968026

Title:
  right-Alt + PrtScn + reisub does not work with USB keyboard and reisuo
  does work. All works with a PS2 keyboard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968026/+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

[Peter Sagerson]

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 1958658] [NEW] GTK File Chooser file type filter too restrictive

[Peter Freeth]

Public bug reported:

Description:Ubuntu 21.10
Release:21.10
xdg-desktop-portal-gtk:
Installed: 1.8.0-1build1


When calling the GTK File Chooser from inside another program such as Google 
Chrome, the files displayed are filtered according to a file extension filter. 
The bottom right of the chooser window shows a button "customised files".

This creates a problem in that file extensions are an unreliable
indication of file type.

For example, when uploading an image to a website, Google Chrome filters
for image files by lower case extensions. Any images with upper case
file extensions are filtered out. The user has to select "all files" to
see the files with upper case file names/extensions.

Google Chrome is to blame for sending incomplete file filter information
to the file chooser, however the file chooser could also match both
upper and lower case extensions so that the calling program doesn't need
to take this into account.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xdg-desktop-portal-gtk 1.8.0-1build1
ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 21 15:20:00 2022
ExecutablePath: /usr/libexec/xdg-desktop-portal-gtk
InstallationDate: Installed on 2019-10-11 (832 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010)
ProcEnviron:
 LANG=en_GB.UTF-8
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: xdg-desktop-portal-gtk
UpgradeStatus: Upgraded to impish on 2021-10-20 (93 days ago)

** Affects: xdg-desktop-portal-gtk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xdg-desktop-portal-gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1958658

Title:
  GTK File Chooser file type filter too restrictive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1958658/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1944453] Re: PDF documents signed with DocuSign show the error message "The document contains no pages"

[Peter]

@seb128 I am aware that this has been fixed in hirsuite, but it remains
unfixed in focal. I am committed to staying on an LTS release.

If this is not the right place to report this bug, could you please
point me to how I can navigate the relevant backporting request process?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1944453

Title:
  PDF documents signed with DocuSign show the error message "The
  document contains no pages"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1944453/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1944453] [NEW] PDF documents signed with DocuSign show the error message "The document contains no pages"

[Peter]

Public bug reported:

Steps to reproduce:
---

1. Open a document signed with DocuSign

Expected behaviour:
---

Document opens fine

Actual behaviour:
---

Evince refuses to display the document, with the error message "The
document contains no pages".

If document is opened with `pdftotext`, the output is:

```
Syntax Error: Gen inside xref table too large (bigger than INT_MAX)
Syntax Error: Invalid XRef entry 3
Syntax Error: Top-level pages object is wrong type (null)
Command Line Error: Wrong page range given: the first page (1) can not be after 
the last page (0).
```

Other information
---

This appears to be a bug in libpoppler, described at
https://stackoverflow.com/questions/66636441/pdf2image-library-failing-
to-read-pdf-signed-using-docusign and
https://gitlab.freedesktop.org/poppler/poppler/-/issues/1014 . I believe
that bumping the version of Poppler and/or Evince will solve the issue,
though I have no way to test this as compiling from source is a
significant undertaking.

I do not have a public sample document that I could share, but examples
of DocuSigned documents should be available online.

Ubuntu version: 20.04 LTS (up to date)
Evince version: 3.36.10 (official package)
Poppler version: 0.86.1-0ubuntu1 (official package)

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1944453

Title:
  PDF documents signed with DocuSign show the error message "The
  document contains no pages"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1944453/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1929011] Re: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

[Peter Burnett]

I pursued this further and found that on multiple computers and
keyboards including using both USB and PS2 keyboards.

Right-Alt + PrintScrn + REISUB works only while using PS2 keyboards, and
it is consistent with multiple computers. The computer I reported this
bug on does not have any PS2 ports.

Furthermore REISUB works only with PS2 keyboards with LIVE openSUSE-
Leap-15.3-DVD-x86_64-Build151.1-Media.iso and not USB keyboards on any
computer I tried with it.

Thus I take it that this is a kernel problem, and it is not mapping the
Right-Alt key.

-- 
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/1929011

Title:
  Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1929011/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1929011] Re: Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

[Peter Burnett]

REISUO R-E-I-S-U-O as well.

-- 
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/1929011

Title:
  Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1929011/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1929011] [NEW] Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

[Peter Burnett]

Public bug reported:

Left-Alt is always operational & Right-Alt is not at any time & not specific to 
this report's subject category.
True on both desktop & Live ubuntu-20.04.2.0-desktop-amd64.iso.
It is natural to use Right-Alt due to a closer distance to the SysRq key.
This might help explain why some say REISUB does not work.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-screensaver (not installed)
ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-53-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 20 00:27:12 2021
InstallationDate: Installed on 2020-07-14 (309 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen locking issue
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-screensaver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1929011

Title:
  Alt + SysRq/ PrintScrn + REISUB R-E-I-S-U-B for emergency reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1929011/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1918066] [NEW] following recent automatic update on 20.04.2lts I now have no sound on my system

[Peter Jordan]

Public bug reported:

System sound no longer working. Checked my hardware by loading TAILS on a USB 
stick. Sound works perfectly. So nothing wrong with my hardware. System 
20.04.2LTS was working perfectly until latest automatic update. Noticed that in 
settings the sound screen has changed in layout. Tried various settings options 
but unable to recover sound.
settings=  output device = Line Out Built-in Audio
configuration  = Analogue Surround 5.1 Output
Used to have 7.1 but this now gone.
system pretty unusable without any sound.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar  7 16:46:34 2021
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-11-16 (110 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1918066

Title:
  following recent automatic update on 20.04.2lts I now have no sound on
  my system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1918066/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1422136] Re: Can't change grid spacing in GIMP

[Peter]

Image > Grid settings

-- 
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/1422136

Title:
  Can't change grid spacing in GIMP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1422136/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)

[Peter L Jones]

Hi,

I'm running focal (20.04.1 LTS) -- and hit this only just now when
upgrading to the new LTS.

So this is to confirm this affects the LTS release and I'd like to ask
for it back-ported. :)

Thanks,

-- Peter

-- 
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/1897224

Title:
  Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
  display)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

[Peter Goodall]

I have reported a new bug:
https://bugs.launchpad.net/bugs/1899089

Thanks for your help...

-- 
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/1691908

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1691908/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1899089] [NEW] Ubuntu 20.04 file browser showing all zfs mounts explicitly in side-panel

[Peter Goodall]

Public bug reported:

I have installed Ubuntu 20.04 on zfs. I had previously had zfs datasets
mounted into my 18.04 system. Those mounts are all working in the new
system, but they are displaying as mounts in my file browser with
unmount buttons next to them. I certainly don't want this function. it
is also cluttering my display. It appears similar to Bug 1691908.

My zfs mounts are not removable volumes, they are not in fstab.

I was advised to report the output of `gio mount -li`:

```
Volume(0): efi
  Type: GUnixVolume
  ids:
   uuid: '8799-8F8E'
  themed icons:  [drive-removable-media]
  symbolic themed icons:  [drive-removable-media-symbolic]
  can_mount=1
  can_eject=0
  should_automount=1
  Mount(0): efi -> file:///boot/efi
Type: GUnixMount
default_location=file:///boot/efi
themed icons:  [drive-harddisk]
symbolic themed icons:  [drive-harddisk-symbolic]
can_unmount=1
can_eject=0
is_shadowed=0
Mount(1): SPACE -> file:///media/peterg/SPACE
  Type: GUnixMount
  default_location=file:///media/peterg/SPACE
  themed icons:  [drive-harddisk]
  symbolic themed icons:  [drive-harddisk-symbolic]
  can_unmount=1
  can_eject=0
  is_shadowed=0
```

I tried Ask-Ubuntu. No answers at this time:
https://askubuntu.com/questions/1280941/ubuntu-20-04-file-browser-showing-all-zfs-mounts-explicitly-in-side-panel

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
Uname: Linux 5.4.0-49-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Oct  9 08:41:22 2020
GsettingsChanges:
 
InstallationDate: Installed on 2020-10-01 (6 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20201001)
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal zfs

** Attachment added: "screen-grab of nautilus showing zfs filesystem 
mount-points"
   
https://bugs.launchpad.net/bugs/1899089/+attachment/5419777/+files/Screenshot%20from%202020-10-09%2008-54-46.png

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1899089

Title:
  Ubuntu 20.04 file browser showing all zfs mounts explicitly in side-
  panel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1899089/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

[Peter Goodall]

@Sebastien,

Thanks, but I am struggling to find a PID to report this against. So I
had to find related subject-matter - Bug 1691908 was the most relevant I
could locate. So what do I report this against? I don't really do Ubuntu
internals, so my knowledge of relevant subsystems is limited. It isn't
like Smalltalk where I can click on the offending item and drop into an
inspector.

`ubuntu-bug` requires a PID. '

`sudo gio mount -li ` output doesn't seem to help... The zfs mount-
points are not removable drives...

Volume(0): efi
  Type: GUnixVolume
  ids:
   uuid: '8799-8F8E'
  themed icons:  [drive-removable-media]
  symbolic themed icons:  [drive-removable-media-symbolic]
  can_mount=1
  can_eject=0
  should_automount=1
  Mount(0): efi -> file:///boot/efi
Type: GUnixMount
default_location=file:///boot/efi
themed icons:  [drive-harddisk]
symbolic themed icons:  [drive-harddisk-symbolic]
can_unmount=1
can_eject=0
is_shadowed=0
Mount(1): SPACE -> file:///media/peterg/SPACE
  Type: GUnixMount
  default_location=file:///media/peterg/SPACE
  themed icons:  [drive-harddisk]
  symbolic themed icons:  [drive-harddisk-symbolic]
  can_unmount=1
  can_eject=0
  is_shadowed=0

-- 
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/1691908

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1691908/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1691908] Re: fstab binds appear as mounts (x-gvfs-hide is being ignored)

[Peter Goodall]

This is occurring in Ubuntu 20.04. All my zfs mounts are appearing in my
desktop file-manager. Screenshot attached. A total nuisance.


** Attachment added: "Screenshot from 2020-10-08 09-41-42.png"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1691908/+attachment/5419210/+files/Screenshot%20from%202020-10-08%2009-41-42.png

-- 
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/1691908

Title:
  fstab binds appear as mounts (x-gvfs-hide is being ignored)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1691908/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1874217] Re: [nvidia] Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors

[Peter Klaesson]

@Daniel: Sounds like something you should be able to have access too if
you are assigned to test this.

Do you have any thought about how it could be solved? I mean, you need a
new card or an adapter(?) for your current card?

I have no idea how this works for you financially. Can you get what you
need and get the expenses covered by Canonical?

-- 
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/1874217

Title:
  [nvidia] Dual monitor setup with secondary monitor in portrait-right
  mode cause tiled windows to occupy 1.5 monitors

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1877155] [NEW] gimp crashes on first login ang starts on second login

[Peter]

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.62.4 (compiled against version 2.58.1)
using GdkPixbuf version 2.40.0 (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: Speicherzugriffsfehler

Stack trace:
```

# Stack traces obtained from PID 3658 - Thread 3658 #

[New LWP 3660]
[New LWP 3661]
[New LWP 3662]
[New LWP 3663]
[New LWP 3664]
[New LWP 3665]
[New LWP 3666]
[New LWP 3667]
[New LWP 3668]
[New LWP 3669]
[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=0x7fff79ae8c90, fd=13) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id Frame 
* 1Thread 0x7f2785e75e00 (LWP 3658) "gimp-2.10"  __libc_read 
(nbytes=256, buf=0x7fff79ae8c90, fd=13) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7f27855ee700 (LWP 3660) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f2784ded700 (LWP 3661) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f277c5ec700 (LWP 3662) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f277f28e700 (LWP 3663) "gmain"  0x7f2786e17c2f in 
__GI___poll (fds=0x55b8763e7a60, nfds=1, timeout=4704) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7f277e654700 (LWP 3664) "gdbus"  0x7f2786e17c2f in 
__GI___poll (fds=0x55b8763fe380, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7f2763fff700 (LWP 3665) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f27637fe700 (LWP 3666) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7f2762ffd700 (LWP 3667) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7f275bfff700 (LWP 3668) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7f27627fc700 (LWP 3669) "pool-gimp-2.10" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 11 (Thread 0x7f27627fc700 (LWP 3669)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f278710aea6 in g_cond_wait_until () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7f278708f3e1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3  0x7f278708fa06 in g_async_queue_timeout_pop () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7f27870e8969 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5  0x7f27870e8181 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6  0x7f2786efe669 in start_thread (arg=) at 
pthread_create.c:479
ret = 
pd = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139807132993280, 
-776773280171938494, 140735234873502, 140735234873503, 140735234873648, 
139807132989696, 826019304206380354, 826222579432041794}, mask_was_saved = 0}}, 
priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 

[Bug 1876445] Re: Cut or copy & paste problems

[Michael Peter Nolan]

Its intermittent but about 50 times a day between web and terminal, or
any different software the copy just doesn't take until i do it a second
time. It is so ridiculous that you can't just test it and figure out ...
like maybe you could patch that copy is double processed until you
figure out why its fucked up so at least we can copy ... reliably.

-- 
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/1876445

Title:
  Cut or copy & paste problems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1876445/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1876141] Re: before login screen the setup forces a new login name

[Peter Sluka]

the offending program is gnome-initial-setup.  I can exit [via a timeout] but 
that give a black screen which I break out of with Ctrl-Alt-Del, but that
just puts me back at the same gnome-initial-setup.  The only way forward seems 
to let it add a new user.  At the login screen of that new user, I then click 
on "login as another user" which then gets me to my "real" user and all is fine 
after that.

-- 
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/1876141

Title:
  before login screen the setup forces a new login name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1876141/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1874217] Re: Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors

[Peter Klaesson]

I also experience this issue. Was not there in 19.10 for me either. It's
ONLY when setting one of the monitors to portrait mode.

Currently I have to use a workaround, running ARandR or "nvidia x server
settings" after login to set the displays. But I can't save the settings
to make them persistent.

It would be nice to be able to use the monitor.xml to make the settings
persistent.

-- 
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/1874217

Title:
  Dual monitor setup with secondary monitor in portrait-right mode cause
  tiled windows to occupy 1.5 monitors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874217/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1873658] Re: Deb Files are not associated with an application that manages packages

[Peter Jones]

Just to confirm, I'm using pure Ubuntu 20.04 and not any of the
flavours.  I'm happy to assist in any testing of the flavours if you
would like me to. Just let me know.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1873658

Title:
  Deb Files are not associated with an application that manages packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1873658] Re: Deb Files are not associated with an application that manages packages

[Peter Jones]

Seems to have been fixed with an update this evening?


** Attachment added: "Screen Grab"
   
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1873658/+attachment/5357719/+files/Capture.PNG

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1873658

Title:
  Deb Files are not associated with an application that manages packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1873658] Re: Deb Files are not associated with an application that manages packages

[Peter Jones]

Please ignore last comment. Now brings up software centre and says
Failed to install File - Not Supported.

** Attachment added: "Screen Grab"
   
https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1873658/+attachment/5357720/+files/Capture2.PNG

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1873658

Title:
  Deb Files are not associated with an application that manages packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Peter Müller]

Same issue here (NVIDIA GTX1060) and related bug 1869565; solved by
20.04 daily w/o propriety driver during install for now.

-- 
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/1845801

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1869565] Re: Login loop with fresh 19.10 install

[Peter Müller]

I decided to go upstream and replace 19.10 by 20.04. I also slected 3rd
party options to exclude the NVIDIA driver during install. I currently
have no issues but know now how to report a bug when it appears. I may
have a problem due to gdm "or" NVIDIA.

Thanks for all the prompt help and support!

-- 
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/1869565

Title:
  Login loop with fresh 19.10 install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869565/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1869565] Re: Login loop with fresh 19.10 install

[Peter Müller]

I took a photo and typed it in on another computer which is tedious.

https://launchpad.net/+authorize-
token?oauth_token=FvWwRf72mCVNWPdsr1TP_permission=DESKTOP-
INTEGRATION

I then get this error:

Not allowed here
Sorry, you don't have permission to access this page or the information in this 
page is not shared with you.

You are logged in as Peter Müller.

The reporting of bugs is taking up a lot of time.

-- 
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/1869565

Title:
  Login loop with fresh 19.10 install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869565/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1869565] Re: Login loop with fresh 19.10 install

[Peter Müller]

The prompt is the same as above. That may be another bug because -cli
should not issue it.

-- 
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/1869565

Title:
  Login loop with fresh 19.10 install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869565/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1869565] Re: Login loop with fresh 19.10 install

[Peter Müller]

apport-collect 1869565

is stuck on trying to open a page in a browser which is not available
after dropping into a shell ctrl-alt-f2. Any plans to improve the tool?

-- 
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/1869565

Title:
  Login loop with fresh 19.10 install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869565/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1869565] Re: Login loop with fresh 19.10 install

[Peter Müller]

** Description changed:

  On a fresh clean 19.10 install, a login loop evolves after a couple of
  reboots.
  
- The gdm package is likely the culprit. None of the recommendations in
- https://askubuntu.com/questions/1182506/login-loop-with-
- fresh-19-10-install fix it.
+ The gdm package is likely the culprit. None of the recommendations in 
https://askubuntu.com/questions/1182506/login-loop-with-fresh-19-10-install
+ fix it.

-- 
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/1869565

Title:
  Login loop with fresh 19.10 install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869565/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1869565] [NEW] Login loop with fresh 19.10 install

[Peter Müller]

Public bug reported:

On a fresh clean 19.10 install, a login loop evolves after a couple of
reboots.

The gdm package is likely the culprit. None of the recommendations in
https://askubuntu.com/questions/1182506/login-loop-with-
fresh-19-10-install fix it.

** Affects: gdm (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1869565

Title:
  Login loop with fresh 19.10 install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1869565/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1865272] [NEW] ``` GNU Image Manipulation Program version 2.10.14 git-describe: GIMP_2_10_12-511-ga4f55d6c7e C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86

[Peter]

Public bug reported:

```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:hsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
9.2.1-17ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-9 
--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-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib=auto --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,hsa --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 9.2.1 20191102 (Ubuntu 9.2.1-17ubuntu1) 

using babl version 0.1.74 (compiled against version 0.1.72)
using GEGL version 0.4.18 (compiled against version 0.4.18)
using GLib version 2.63.5 (compiled against version 2.62.1)
using GdkPixbuf version 2.40.0 (compiled against version 2.40.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.44.7 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Speicherzugriffsfehler

Stack trace:
```

# Stack traces obtained from PID 52883 - Thread 52883 #

[New LWP 52884]
[New LWP 52885]
[New LWP 52886]
[New LWP 52887]
[New LWP 52888]
[New LWP 52889]
[New LWP 52890]
[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=0x7ffe6480cd10, fd=16) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id  Frame 
* 1Thread 0x7ff974a17e00 (LWP 52883) "gimp-2.10"  __libc_read 
(nbytes=256, buf=0x7ffe6480cd10, fd=16) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7ff971ce3700 (LWP 52884) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7ff9714e2700 (LWP 52885) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7ff970ce1700 (LWP 52886) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7ff963dfb700 (LWP 52887) "gmain"  0x7ff975a0fc3f in 
__GI___poll (fds=0x558250d06cf0, nfds=1, timeout=3501) at 
../sysdeps/unix/sysv/linux/poll.c:29
  6Thread 0x7ff9635fa700 (LWP 52888) "gdbus"  0x7ff975a0fc3f in 
__GI___poll (fds=0x558250d12f00, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7ff954db3700 (LWP 52889) "async"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7ff94bfff700 (LWP 52890) "pool-gimp-2.10" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 8 (Thread 0x7ff94bfff700 (LWP 52890)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7ff975d044e6 in g_cond_wait_until () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7ff975c87511 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3  0x7ff975c87b36 in g_async_queue_timeout_pop () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#4  0x7ff975ce1219 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#5  0x7ff975ce08d1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#6  0x7ff975af6669 in start_thread (arg=) at 
pthread_create.c:479
ret = 
pd = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140708698650368, 
-4907943033698399510, 140730584586446, 140730584586447, 140730584586592, 
140708698646784, 4904961158509611754, 4904860411942128362}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 0
#7  0x7ff975a1c333 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
No locals.

Thread 7 (Thread 0x7ff954db3700 (LWP 52889)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No 

[Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

[Michael Peter Nolan]

I can't do screen capture - sometimes when i roll over a field in Chrome its 
like there is a list there of clipboard items. I have to copy 2 times to get 
text but other types of clipboard like captured images aren't working.
I'd fix this if I was up to speed with developing on this platform because it's 
driving me nuts.

-- 
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/1852183

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1251281] Re: gnome-session-flashback/Unity fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)

[Peter Bennett]

Xubuntu should be OK. I have no problems with it. Try this -
https://catch22cats.blogspot.com/2018/05/xrdp-blank-screen-with-
ubuntu-1804.html

-- 
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/1251281

Title:
  gnome-session-flashback/Unity fails to start without hardware
  acceleration in cloud/remote environments
  (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1251281/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)

[Peter May]

I have this problem as well.

Virgin/Clean install of Eoan Desktop install in a KVM virtual machine.
Install package cqrlog, which has a long startup time and usually causes the 
"not responding" dialog to raise, but can be dismissed.

Under Eoan, the "CQRLOG is not responding" dialog cannot be dismissed -
both "Force Quit" and "Wait" are greyed out and cannot be selected.

gnome-shell then runs to 100% cpu utilisation (one thread/core) and
repeatedly logs:

gnome-shell[4157]: JS ERROR: TypeError: null has no
properties#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9

in syslog.
Killing gnome-shell clears the "not responding" dialog.

Not this is a virgin install to debug this problem, no extensions or
anything else installed (except mariadb-server and cqrlog).

-- 
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/1841774

Title:
  gnome-shell freezes and continuously logs "JS ERROR: TypeError: null
  has no properties" in _addWindowEffect from vfunc_show (both in
  closeDialog.js)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications

[Peter S]

I have the same problem with eboard 1.1.3 on Debian Buster. The program
build is quite old (2016), hence it seems that the problem is with some
high-level library.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1808710

Title:
  !xcb_xlib_threads_sequence_lost error with GTK2 applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1834568] Re: gdm fails to start on nvidia based systems on cosmic

[Peter De Sousa]

*** This bug is a duplicate of bug 1798790 ***
https://bugs.launchpad.net/bugs/1798790

Found this bug to be a copy of
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790.



** This bug has been marked a duplicate of bug 1798790
   Ubuntu login screen sometimes doesn't appear on a single GPU Nvidia system 
(and setting WaylandEnable=false fixes it)

-- 
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/1834568

Title:
  gdm fails to start on nvidia based systems on  cosmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1834568/+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)

[Peter De Sousa]

I also have this issue, but I discovered if I pressed Alt+F{N>2} then
Alt+F1 gdm boots immediatly.

I opemed a bug here,
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1834568 but I will
close it now that I found this one.

-- 
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 1834568] [NEW] gdm fails to start on nvidia based systems on cosmic

[Peter De Sousa]

Public bug reported:

Hello,

After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
seemingly was unable to start. There was not much in the logs, and after
much tinkering I discovered that after the Ubuntu splash screen if I
pressed Alt + F{N>1} then pressed Alt+F1 gdm would immediatly start up.

But if I left it to load as normal, it would fall into a stalled state
where I am forced to reboot.

If you need any diagnostics please don't hisitate to ask.

Prior to discovering this work around I checked the logs using
`journalctl -xb` but was unable to see anything related to GDM, so it
may not be that but this is the configuration I have:

- Nvidia RTX 2080Ti
- Nvidia 430 drivers from nvidia ppa
- Wayland enabled
- Cosmic Cuttlefish 18.10

This bug is not present when I disable wayland.

** Affects: gdm3 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Hello,
  
  After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
  seemingly was unable to start. There was not much in the logs, and after
  much tinkering I discovered that after the Ubuntu splash screen if I
- pressed Alt + F{N<1} then pressed F1 gdm would immediatly start up.
+ pressed Alt + F{N>1} then pressed F1 gdm would immediatly start up.
  
  But if I left it to load as normal, it would fall into a stalled state
  where I am forced to reboot.
  
  If you need any diagnostics please don't hisitate to ask.
  
  Prior to discovering this work around I checked the logs using
  `journalctl -xe` but was unable to see anything related to GDM, so it
  may not be that but this is the configuration I have:
  
  - Nvidia RTX 2080Ti
  - Nvidia 430 drivers from nvidia ppa
  - Wayland enabled
  - Cosmic Cuttlefish 18.10
  
  This bug is not present when I disable wayland.

** Description changed:

  Hello,
  
  After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
  seemingly was unable to start. There was not much in the logs, and after
  much tinkering I discovered that after the Ubuntu splash screen if I
- pressed Alt + F{N>1} then pressed F1 gdm would immediatly start up.
+ pressed Alt + F{N>1} then pressed Alt+F1 gdm would immediatly start up.
  
  But if I left it to load as normal, it would fall into a stalled state
  where I am forced to reboot.
  
  If you need any diagnostics please don't hisitate to ask.
  
  Prior to discovering this work around I checked the logs using
  `journalctl -xe` but was unable to see anything related to GDM, so it
  may not be that but this is the configuration I have:
  
  - Nvidia RTX 2080Ti
  - Nvidia 430 drivers from nvidia ppa
  - Wayland enabled
  - Cosmic Cuttlefish 18.10
  
  This bug is not present when I disable wayland.

** Description changed:

  Hello,
  
  After upgrading to Cosmic Cuttlefish yesterday when I came to reboot gdm
  seemingly was unable to start. There was not much in the logs, and after
  much tinkering I discovered that after the Ubuntu splash screen if I
  pressed Alt + F{N>1} then pressed Alt+F1 gdm would immediatly start up.
  
  But if I left it to load as normal, it would fall into a stalled state
  where I am forced to reboot.
  
  If you need any diagnostics please don't hisitate to ask.
  
  Prior to discovering this work around I checked the logs using
- `journalctl -xe` but was unable to see anything related to GDM, so it
+ `journalctl -xb` but was unable to see anything related to GDM, so it
  may not be that but this is the configuration I have:
  
  - Nvidia RTX 2080Ti
  - Nvidia 430 drivers from nvidia ppa
  - Wayland enabled
  - Cosmic Cuttlefish 18.10
  
  This bug is not present when I disable wayland.

-- 
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/1834568

Title:
  gdm fails to start on nvidia based systems on  cosmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1834568/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1824157] Re: Regression: Can not copy/paste files from nautilus to terminal (19.04)

[Peter Würtz]

*** This bug is a duplicate of bug 1826266 ***
https://bugs.launchpad.net/bugs/1826266

Seems to be a design choice, known for at least 8 months.

https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826266

https://gitlab.gnome.org/GNOME/nautilus/issues/634

** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #634
   https://gitlab.gnome.org/GNOME/nautilus/issues/634

-- 
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/1824157

Title:
  Regression: Can not copy/paste files from nautilus to terminal (19.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1824157/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1829111] [NEW] Openvpn connection icons missing from display

[Peter Nunn]

Public bug reported:

Having upgraded to the unstable packages I no longer see an indication
on the vpn dropdown to show what vpn's are connected and which are not.

The last one active is shown at the top of the dropdown list, but others
in the list are missing the indication that they used to have to say
they are connected.

The following appears in the log at the same time so I think its
related.

May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #6   
7ffcd0736aa0 b   resource:///org/gnome/gjs/modules/signals.js:128 (7fc4db3cb820 
@ 386)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #7   
7ffcd0736b50 b   resource:///org/gnome/shell/ui/tweener.js:238 (7fc4db3cb3a0 @ 
159)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #8   
7ffcd0736bf0 b   resource:///org/gnome/shell/ui/tweener.js:209 (7fc4db3cb280 @ 
15)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: == Stack trace 
for context 0x55f2c9f241e0 ==
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #0   
55f2d255fca8 i   resource:///org/gnome/shell/ui/background.js:722 (7fc4daf08430 
@ 22)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #1   
55f2d255fc20 i   resource:///org/gnome/shell/ui/tweener.js:106 (7fc4db3c8940 @ 
37)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #2   
7ffcd0736720 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 
(7fc4db3d0670 @ 54)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #3   
7ffcd0736870 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:342 
(7fc4db3d0700 @ 1742)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #4   
7ffcd0736920 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:355 
(7fc4db3d0790 @ 100)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #5   
7ffcd07369b0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:370 
(7fc4db3d0820 @ 10)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #6   
7ffcd0736aa0 b   resource:///org/gnome/gjs/modules/signals.js:128 (7fc4db3cb820 
@ 386)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #7   
7ffcd0736b50 b   resource:///org/gnome/shell/ui/tweener.js:238 (7fc4db3cb3a0 @ 
159)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #8   
7ffcd0736bf0 b   resource:///org/gnome/shell/ui/tweener.js:209 (7fc4db3cb280 @ 
15)
May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: g_object_run_dispose: 
assertion 'G_IS_OBJECT (object)' failed
May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: Object Meta.Background 
(0x55f2cdc6f230), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: g_object_run_dispose: 
assertion 'G_IS_OBJECT (object)' failed
May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: Object Meta.Background 
(0x55f2cdc6f230), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: == Stack trace 
for context 0x55f2c9f241e0 ==
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #0   
55f2d255fca8 i   resource:///org/gnome/shell/ui/background.js:722 (7fc4daf08430 
@ 22)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #1   
55f2d255fc20 i   resource:///org/gnome/shell/ui/tweener.js:106 (7fc4db3c8940 @ 
37)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #2   
7ffcd0736720 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 
(7fc4db3d0670 @ 54)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #3   
7ffcd0736870 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:342 
(7fc4db3d0700 @ 1742)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #4   
7ffcd0736920 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:355 
(7fc4db3d0790 @ 100)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #5   
7ffcd07369b0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:370 
(7fc4db3d0820 @ 10)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #6   
7ffcd0736aa0 b   resource:///org/gnome/gjs/modules/signals.js:128 (7fc4db3cb820 
@ 386)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #7   
7ffcd0736b50 b   resource:///org/gnome/shell/ui/tweener.js:238 (7fc4db3cb3a0 @ 
159)
May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #8   
7ffcd0736bf0 b   resource:///org/gnome/shell/ui/tweener.js:209 (7fc4db3cb280 @ 
15)
May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: g_object_run_dispose: 
assertion 'G_IS_OBJECT (object)' failed
May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: Object Meta.Background 

[Bug 688436] Re: gvfs-open and gnome-open can't handle URLs containing "%2F"

[Peter Oliver]

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #54
   https://gitlab.gnome.org/GNOME/gvfs/issues/54

** Also affects: gvfs via
   https://gitlab.gnome.org/GNOME/gvfs/issues/54
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libgnome in Ubuntu.
https://bugs.launchpad.net/bugs/688436

Title:
  gvfs-open and gnome-open can't handle URLs containing "%2F"

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/688436/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1819263] [NEW] GNOME Shell applet can't open System Monitor installed as Snap

[Peter Bittner]

Public bug reported:

It looks like the `gnome-system-monitor` package is installed as a snap
package since Ubuntu 18.04 Bionic by default [1]. Unfortunately, this
affects some GNOME Shell extensions.

The popular "system-monitor" extension [3][4] fails to locate the system
monitor executable to call and open it from the context menu.

A related bug report on GitHub [5] (issue #474) explains the problem and
documents that several users solve the issue by uninstalling the snap
and installing the gnome-system-monitor .deb package [2] instead.

Do we have to fix the GNOME Shell extension (if yes, how?), can this
issue be resolved in the snap package, or is that a permanent
restriction of the snap package? (i.e. wontfix)


[1] 
https://www.reddit.com/r/Ubuntu/comments/8krkam/system_monitor_on_1804_is_a_snap_by_default/
[2] https://packages.ubuntu.com/cosmic/gnome/gnome-system-monitor
[3] https://extensions.gnome.org/extension/120/system-monitor/
[4] https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet
[5] 
https://github.com/paradoxxxzero/gnome-shell-system-monitor-applet/issues/474

** Affects: gnome-system-monitor (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1819263

Title:
  GNOME Shell applet can't open System Monitor installed as Snap

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1819263/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817546] Re: Changing the volume (with the mouse wheel over icon) locks up gnome-shell

[Peter Rhone]

Seems to be fixed with mutter 3.31.92-1~fakesync

Thanks for fixing this so quickly.

-- 
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/1817546

Title:
  Changing the volume (with the mouse wheel over icon) locks up gnome-
  shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1817546/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817546] Re: Changing the volume (with the mouse wheel over icon) locks up gnome-shell

[Peter Rhone]

@3v1n0 Where can I find the journal for gnome-shell?

-- 
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/1817546

Title:
  Changing the volume (with the mouse wheel over icon) locks up gnome-
  shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1817546] [NEW] Changing the volume (with the mouse wheel over icon) locks up gnome-shell

[Peter Rhone]

Public bug reported:

If I change the volume, the display freezes right after the volume
display floating indictor appears in the middle of the screen. I have to
either reboot or switch to virtual terminal and killall -3 gnome-shell
to restart the session.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.31.90-1ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 25 13:20:49 2019
DisplayManager: gdm3
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-06-19 (615 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170617)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-01-31 (24 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2019-02-23T10:27:39.206420

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco package-from-proposed third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1817546

Title:
  Changing the volume (with the mouse wheel over icon) locks up gnome-
  shell

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1817546/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813738] Re: laptop doesnt wake up

[Peter Hall]

Problem disappears for me after revertering FROM linux-
image-4.15.0-44-generic TO linux-image-4.15.0-43-generic

Seems to be other issues with linux-image-4.15.0-44-generic, I get
lockups simply by disconnecting the USB-C cable to my monitor
("undocking", if you will).

-- 
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/1813738

Title:
  laptop doesnt wake up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813738/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1813738] Re: laptop doesnt wake up

[Peter Hall]

Same problem for me.
Full freeze after entering sleep mode or if I just lock my gnome-session while 
an external monitor is attached.
If laptop is standalone it does not freeze.

There is nothing in /var/crash
There is no match on https://errors.ubuntu.com/user/

-- 
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/1813738

Title:
  laptop doesnt wake up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813738/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1576977] Re: Lots of GEGL-gegl-operation.c-WARNING on starting gimp

[Peter Flynn]

I have the identical issue under Mint 18. Google works fine, but they
just fill up my console :-) They're only warnings, but it would be nice
if someone could clean up the code.

-- 
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/1576977

Title:
  Lots of GEGL-gegl-operation.c-WARNING on starting gimp

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1576977/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 353554] Re: error on deleting image file "Couldn't access trash."

[Peter White]

*** This bug is a duplicate of bug 192629 ***
https://bugs.launchpad.net/bugs/192629

Really this is an annoying situation. last month I faced that kind of
problem. But LongPath Tool helped me to delete fixed/error file.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/353554

Title:
  error on deleting image file "Couldn't access trash."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/353554/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1588009]

[Peter Hutterer]

Please see https://wayland.freedesktop.org/libinput/doc/latest/faqs.html
#what-causes-the-timer-offset-negative-warning, this is almost never a
libinput bug.

fwiw, libinput has moved to gitlab, any future issues should be filed at
https://gitlab.freedesktop.org/libinput/libinput

-- 
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/1588009

Title:
  "libinput bug: timer offset negative" keeps coming up in syslog

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1588009/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1800043] Re: nautilus cannot write on nfs file share

[Peter Neugebauer]

Do we work on the same problem? My nfs share is exported by an external file 
server (i.e. a synology disc station) and imported by Ubuntu 18.04. 
Thus, the line in my /etc/fstab on my Ubuntu system reads
xxx.yyy.zzz:/volume1/homes/peter /media/peter/MyStorage nfs defaults,intr 0 0
This links the external disc to my Ubuntu system. The option "intr" seemed to 
be important for the synology station when I still was using 16.04. Now, the 
behaviour doesn't change if I omit it.
Once again: using nautilus I can only read from "/media/peter/MyStorage". Using 
command line tools I can read and write to the share.
Also, using nautilus I can read _and_ write to every subfolder of 
"/media/peter/MyStorage".

-- 
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/1800043

Title:
  nautilus cannot write on nfs file share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800043/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1800043] Re: nautilus cannot write on nfs file share

[Peter Neugebauer]

As for the command line: copying and deleting works with the usual cp/rm 
commands and also with the gio tool (gio copy/gio remove). However, it doesn't 
work with nautilus. 
The nautilus UI simply doesn't let me place the icon of the desired file into 
the root window. It "flies" back to where it came from. Thus, it behaves 
exactly as you would expect from a read-only file system. BTW: copying _from_ 
the root system with nautilus also works correctly. And, again, once I go into 
one of my folders - everything works as usual. 
For now I decided to mount my share with CIFS - which also works as desired.

Best regards
Peter

-- 
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/1800043

Title:
  nautilus cannot write on nfs file share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800043/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 574342] Re: GIMP set as default pdf viewer

[Peter Paul]

This bug is still present in Arch Linux. Since Gimp has been installed, both 
Firefox and Thunderbird open PDFs with Gimp instead of Okular.
Furthermore, editing /usr/share/applications/mimeinfo.cache only helped 
temporarily.

-- 
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/574342

Title:
  GIMP set as default pdf viewer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/574342/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1800043] [NEW] nautilus cannot write on nfs file share

[Peter Neugebauer]

Public bug reported:

I installed Ubuntu 18.04LTS comming from 16.04LTS where I did not have this 
weird problem: If I mount a NFS share from a file server (i.e. Synology DS 418) 
Nautilus is not able to perform any write access to it (write, delete, make new 
directory,...). I can do all of this operations by using shell commands (touch, 
cp, mkdir...) in a terminal window. Also, nautilus can perform these actions if 
I start it with root privileges.
Even stranger is the following: even though nautilus cannot write into the 
mounted shares it is able to write into its subfolders. This bug seems to 
affect others as well: 
https://askubuntu.com/questions/1000973/nautilus-cannot-write-into-1st-directory-of-a-nfs-share

Ubuntu version: 18.04.1 LTS - amd64
Nautilus version: 1:3.26.4-0~ubuntu18.04.1

** 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/1800043

Title:
  nautilus cannot write on nfs file share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1800043/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1792807] Re: Login screen freeze

[Peter Bosch]

I've solved it for me now with a new graphics card. Couldn't bare the
nomodeset anymore knowing there was an alternative solution. Imagine how
much I am attached to Ubuntu to rather buy a new graphics card then to
switch to another OS ;-).

We can keep it open if you want further investigation and it might help
with others. For me personally it is solved with the new graph card, so
it can be closed as well. Up to you :-)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1792807

Title:
  Login screen freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1792807] Re: Login screen freeze

[Peter Bosch]

I've just borrowed an external graphics card (ATI) from the office and
plugged it, and then it boots without a problem.

So it definitely has to do with the GPU I mentioned. It would be too
much of a coincidence if this was a hardware problem I think, since the
problem appeared immediately since the upgrade to 18.04..

Anymore thoughts? Or is the only solution here buying an external
graphics card?

-- 
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/1792807

Title:
  Login screen freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1792807] Re: Login screen freeze

[Peter Bosch]

Do you have any other possible solution or attempt I could do to get
this solved? It's pretty annoying to have to run in nomodeset all the
time. Screen res is making my eyes weird o.0 ;-)

-- 
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/1792807

Title:
  Login screen freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1792807] Re: Login screen freeze

[Peter Bosch]

I noticed that I have installed (and could only find) the amd64 image. I
have a 64-bit Intel (https://ark.intel.com/products/52209/Intel-
Core-i5-2500-Processor-6M-Cache-up-to-3_70-GHz) processor. Would that
matter at all? (Maybe a dumb question, but throwing it out there anyway
;-))

-- 
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/1792807

Title:
  Login screen freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1792807] Re: Login screen freeze

[Peter Bosch]

** Attachment added: "nosplash_2.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+attachment/5190305/+files/nosplash_2.jpg

-- 
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/1792807

Title:
  Login screen freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1792807] Re: Login screen freeze

[Peter Bosch]

** Attachment added: "nosplash_3.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+attachment/5190314/+files/nosplash_3.jpg

-- 
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/1792807

Title:
  Login screen freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1792807] Re: Login screen freeze

[Peter Bosch]

I've done that now:

1. $ sudo vim /etc/default/grub
2. changed "splash" to "nosplash"
3. $ sudo update-initramfs -u
4. $ sudo update-grub
5. $ sudo reboot

Note:
* I've added the "-u" option to the update-initramfs as well (it tells me "You 
must specify at least one of -c, -u, or -d", so I did "-u" to update existing).
* I did a "sudo update-grub", because otherwise the changes do not have any 
effect when I restart.

I took some photos during start-up. I got some errors before the disk
unlock (nosplash_1) and some after (nosplash_2). After that, the login
page shows, and the screen is frozen again (nosplash_3).

** Attachment added: "nosplash_1.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+attachment/5190304/+files/nosplash_1.jpg

-- 
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/1792807

Title:
  Login screen freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792807/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs