[Bug 2083310] [NEW] GDM doesn't start Xorg with `-listen tcp` when DisallowTCP=false is set in custom.conf

[Thomas Debesse]

Public bug reported:

GDM doesn't start Xorg with `-listen tcp` when DisallowTCP=false is set
in /etc/gdm3/custom.conf

Nine years ago with xorg-server 1.17 ago the `-nolisten tcp` option was
reversed as a `-listen tcp`.

Before, the behavior was to always enable tcp unless `-nolisten tcp` was
set, now the behavior is to always disable tcp unless `-listen tcp` is
set.

To reverse the behaviour, GDM should be built with
`HAVE_XSERVER_WITH_LISTEN` being defined, typically by passing
`-DHAVE_XSERVER_WITH_LISTEN=1` to the compiler, as seen in the source:

https://gitlab.gnome.org/GNOME/gdm/-/blob/08aea8002a2725f07a0889f52584d284648b2e82/daemon/gdm-
server.c#L329

GDM modified its behaviour 8 years ago:

https://gitlab.gnome.org/GNOME/gdm/-/commit/3f59fa0da5168451898db63e51e312ce894af0c1

and two years ago it was modified again:

https://gitlab.gnome.org/GNOME/gdm/-/commit/bc16c9898012e463bc6b79c3faa8f81ed54527f7

Maybe this define was never added to the GDM build script?

The web is full of forum threads of people trying to make GDM works with
TCP listening, fail to get it working, and give up and use lightdm
instead, this is probably because GDM was built without the expected
define.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdm3 46.0-2ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-44.44-generic 6.8.12
Uname: Linux 6.8.0-44-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Oct  1 10:43:26 2024
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
mtime.conffile..etc.gdm3.custom.conf: 2024-10-01T10:43:20.322306

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


** Tags: amd64 apport-bug noble third-party-packages

** Description changed:

  GDM doesn't start Xorg with `-listen tcp` when DisallowTCP=false is set
  in /etc/gdm3/custom.conf
  
  Nine years ago with xorg-server 1.17 ago the `-nolisten tcp` option was
  reversed as a `-listen tcp`.
  
  Before, the behavior was to always enable tcp unless `-nolisten tcp` was
  set, now the behavior is to always disable tcp unless `-listen tcp` is
  set.
  
  To reverse the behaviour, GDM should be built with
  `HAVE_XSERVER_WITH_LISTEN` being defined, typically by passing
  `-DHAVE_XSERVER_WITH_LISTEN=1` to the compiler, as seen in the source:
  
  
https://gitlab.gnome.org/GNOME/gdm/-/blob/08aea8002a2725f07a0889f52584d284648b2e82/daemon/gdm-
  server.c#L329
  
- GDM modified its default behaviour 8 years ago:
+ GDM modified its behaviour 8 years ago:
  
  
https://gitlab.gnome.org/GNOME/gdm/-/commit/3f59fa0da5168451898db63e51e312ce894af0c1
  
  and two years ago it was modified again:
  
  
https://gitlab.gnome.org/GNOME/gdm/-/commit/bc16c9898012e463bc6b79c3faa8f81ed54527f7
  
- Maybe this define was never added to GDM the build script?
+ Maybe this define was never added to the GDM build script?
  
  The web is full of forum threads of people trying to make GDM works with
  TCP listening, fail to get it working, and give up and use lightdm
  instead, this is probably because GDM was built without the expected
  define.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: gdm3 46.0-2ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-44.44-generic 6.8.12
  Uname: Linux 6.8.0-44-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Oct  1 10:43:26 2024
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
  mtime.conffile..etc.gdm3.custom.conf: 2024-10-01T10:43:20.322306

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

Title:
  GDM doesn't start Xorg with `-listen tcp` when DisallowTCP=false is
  set in custom.conf

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


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

[Bug 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions

[Austin Thomas]

Is there a known workaround for this bug? I've found that holding an
additional finger on the screen before pressing an element will
sometimes work.

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

Title:
  Some shell elements don't respond to touchscreen in Xorg sessions

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


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

[Bug 2067260] Re: Mouse mapping randomly temporarily changes after Ubuntu 24.04 upgrade

[Thomas Mortagne]

I finally noticed that this seems to happen shortly after switching from
one workspace to another. My understanding is that it's what is
described in https://github.com/mzur/gnome-shell-wsmatrix/issues/279.

Not sure if it is worth keeping this launchpad issue (considering it as
a regression in Gnome 46) or if it's just an expected breakage and the
Workspace Matrix extension need to be updated to be compatible with it.

** Bug watch added: github.com/mzur/gnome-shell-wsmatrix/issues #279
   https://github.com/mzur/gnome-shell-wsmatrix/issues/279

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

Title:
  Mouse mapping randomly temporarily changes after Ubuntu 24.04 upgrade

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


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

[Bug 2067260] Re: Mouse mapping randomly temporarily changes after Ubuntu 24.04 upgrade

[Thomas Mortagne]

Attached is a session (I rebooted to be sure) with a very basic USB
cable mouse without any of the Logitech fancy features or buttons (an
Amazon basics to be precise).

** Attachment added: "log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2067260/+attachment/5783849/+files/log.txt

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

Title:
  Mouse mapping randomly temporarily changes after Ubuntu 24.04 upgrade

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


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

[Bug 2067260] Re: Mouse mapping randomly temporarily changes after Ubuntu 24.04 upgrade

[Thomas Mortagne]

Thanks for the analysis!

>   * A hardware-specific mode within the mouse itself.

It would be strange that this happens only after upgrading to 24.04.
Also, I tried with a simple USB cable mouse without any fancy side button and 
had similar problems. I will try to get some log of that as soon as I get back 
my computer.

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

Title:
  Mouse mapping randomly temporarily changes after Ubuntu 24.04 upgrade

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


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

Re: [Bug 2066203] [NEW] Libraries compiled without Shadow Stack support

[Thomas Orgis]

Am Mon, 20 May 2024 23:51:15 -
schrieb Marcos Alano <2066...@bugs.launchpad.net>: 

> [6399376a4e90] main audio output warning: cannot load module
`/usr/lib/x86_64-linux-gnu/vlc/plugins/audio_output/libpulse_plugin.so'
(/lib/x86_64-linux-gnu/libmpg123.so.0: rebuild shared object with SHSTK
support enabled)

Regarding libmpg123, you either need to disable assembly optimizations
(build with generic decoders only), I presume, or someone provide a
patch that adds SHSTK to them. I don't know which implementation of
shadow stacks glibc/gcc is using in that setup. I've read up on the
concept and so far only figured that this is part of a spiral that
complicates ABI and makes providing assembly-optimized functions ever
harder. This would be fine if compilers finally would be smart enough
to evade the need to do so. Last time I checked, hand-tuned AVX
decoding was still a lot more efficient.

We already handle IBT, I think, with indirect jumps landing only in C
wrapper functions. I wonder if we could also limit the shadow stack
impact to those with some compiler/linker flags. The assembly routines
are rather strict math, many years old now without much of attack
surface. All parsing of input is before them in C. They just do lots of
multiplication/addition.

One might try to write a set of optimizations using intrinsics for
modern CPUs that then also get the treatment of shadow stacks or the
next shiny security measure. Porting the AVX code to GCC (and/or other)
inline ASM might also work for some platforms.

(Still, I am wondering why pulseaudio output should need MPEG decoding.)


Alrighty then,

Thomas

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

Title:
  Libraries compiled without Shadow Stack support

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


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

[Bug 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04

[Thomas Burger]

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

Is there any estimate when this is being solved? This is really annoying.
We upgraded the family to 22.04 LTS (using Firefox) and are now affected by 
this.
Everything is updated to the most current level.
Thank 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/1968887

Title:
  Save As Dialog Box does not get focus in Ubuntu 22.04

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


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

[Bug 2042857] Re: Cannot handle HEIC images

[Thomas Morin]

I observe this issue on Ubuntu 23.10, even after installing heif-gdk-
pixbuf, heif-thumbnailer and libheif-* .

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

Title:
  Cannot handle HEIC images

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


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

[Bug 2040155] [NEW] gimp crashes when using simple color filter

[Thomas-Thomas]

Public bug reported:




```
GNU Image Manipulation Program version 2.10.34
git-describe: GIMP_2_10_34
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/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 
12.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-12 
--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-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-12-TwSidC/gcc-12-12.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-TwSidC/gcc-12-12.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 12.2.0 (Ubuntu 12.2.0-16ubuntu1) 

# Libraries #
using babl version 0.1.98 (compiled against version 0.1.98)
using GEGL version 0.4.44 (compiled against version 0.4.42)
using GLib version 2.76.1 (compiled against version 2.75.3)
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.50.12 (compiled against version 1.50.12)
using Fontconfig version 2.14.1 (compiled against version 2.14.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Speicherzugriffsfehler

Stack trace:
```

# Stack traces obtained from PID 1688892 - Thread 1688898 #


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 1688893]
[New LWP 1688894]
[New LWP 1688895]
[New LWP 1688896]
[New LWP 1688897]
[New LWP 1688898]
[New LWP 1688899]
[New LWP 1688900]
[New LWP 1688901]
[New LWP 1688902]
[New LWP 1688903]
[New LWP 1688904]
[New LWP 1688905]
[New LWP 1688906]
[New LWP 1688907]
[New LWP 1688908]
[New LWP 1688909]
[New LWP 1688910]
[New LWP 1688911]
[New LWP 1688914]
[New LWP 1688915]
[New LWP 1688994]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  Id   Target Id  Frame 
* 1Thread 0x7fd33d286e40 (LWP 1688892) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  2Thread 0x7fd33c9fd6c0 (LWP 1688893) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7fd33c1fc6c0 (LWP 1688894) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7fd333fff6c0 (LWP 1688895) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7fd33b9fb6c0 (LWP 1688896) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7fd33b1fa6c0 (LWP 1688897) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7fd33a9f96c0 (LWP 1688898) "worker"   __GI___libc_read 
(nbytes=256, buf=0x7fd33a9f78c0, fd=19) at ../sysdeps/unix/sysv/linux/read.c:26
  8Thread 0x7fd33a1f86c0 (LWP 1688899) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7fd3399f76c0 (LWP 1688900) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7fd3391f66c0 (LWP 1688901) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7fd3389f56c0 (LWP 1688902) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7fd3337fe6c0 (LWP 1688903) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7fd332ffd6c0 (LWP 1688904) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  14   Thread 0x7fd3327fc6c0 (LWP 1688905) "worker"   sy

[Bug 2018555] Re: Nautilus rendering is broken if GTK_THEME env variable exists

[Thomas Debesse]

To be even more precise: you activated a countdown that would
automatically close this issue if no answer would be given to the only
question that was not answerable because of the very nature of this bug.

The Launchpad software is just obeying to human decisions, there.

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

Title:
  Nautilus rendering is broken if GTK_THEME env variable exists

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


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

[Bug 2018555] Re: Nautilus rendering is broken if GTK_THEME env variable exists

[Thomas Debesse]

I may update that sentence:

> You're just saying no one tried to reproduce the bug, this is
different.

You're just saying no one tried to reproduce the bug _and it was just
decided to let it expire with the distribution version itself_, this is
different.

Launchpad can't be taken responsible for, it's a machine.

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

Title:
  Nautilus rendering is broken if GTK_THEME env variable exists

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


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

[Bug 2018555] Re: Nautilus rendering is broken if GTK_THEME env variable exists

[Thomas Debesse]

There was enough information to be actionable:

1. Get Ubuntu with the version the bug is reported for.
2. Apply the reproduction steps given in the very first message reporting the 
bug:

```
killall nautilus
GTK_THEME=
nautilus
```

The bug was said to be a rendering bug, any human with functional eyes
following the reproduction steps could see the rendering bug described
in the very first message:

> Then try to select some icons, selected icons will not be displayed as
selected.

There was no need for any screenshot: the described bug is that
rendering of nautilus would not change between selected and unselected
icon. Those words are more meaningful than a screenshot.

Screenshot may even add more ambiguities to the description, since the
bug is that no change were rendered, nothing happens between before and
after the action that should lead to a change being rendered.

The bug was that the render did not update when you selected something.
There was no way a screenshot could describe the bug as the bug was
there was no rendering change.

The bug was that something was not rendered. The bug could not be
captured by a screenshot. The bug was that the render was not responding
to an event.

The issue was complete from the start.

You're just saying no one tried to reproduce the bug, this is different.

Don't let to machines what machines can't do. This issue was written for
humans. That's why there was reproduction steps given, and that's why
what should be expected and what was given instead was described.

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

Title:
  Nautilus rendering is broken if GTK_THEME env variable exists

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


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

[Bug 2038967] [NEW] selective gaussian plugin crashes upon with large size image

[Thomas-Thomas]

Public bug reported:

had a large image, about ~6000x6000.
executed gaussian blur filter
changed radius slider.

This happens reproducibly, over and over.





```
GNU Image Manipulation Program version 2.10.34
git-describe: GIMP_2_10_34
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/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 
12.2.0-16ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-12 
--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-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-12-TwSidC/gcc-12-12.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-TwSidC/gcc-12-12.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 12.2.0 (Ubuntu 12.2.0-16ubuntu1) 

# Libraries #
using babl version 0.1.98 (compiled against version 0.1.98)
using GEGL version 0.4.44 (compiled against version 0.4.42)
using GLib version 2.76.1 (compiled against version 2.75.3)
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.50.12 (compiled against version 1.50.12)
using Fontconfig version 2.14.1 (compiled against version 2.14.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Speicherzugriffsfehler

Stack trace:
```

# Stack traces obtained from PID 627067 - Thread 627068 #


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 627068]
[New LWP 627069]
[New LWP 627070]
[New LWP 627071]
[New LWP 627072]
[New LWP 627073]
[New LWP 627074]
[New LWP 627075]
[New LWP 627076]
[New LWP 627077]
[New LWP 627078]
[New LWP 627079]
[New LWP 627080]
[New LWP 627081]
[New LWP 627082]
[New LWP 627083]
[New LWP 627084]
[New LWP 627085]
[New LWP 627087]
[New LWP 627090]
[New LWP 627097]
[New LWP 627310]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  Id   Target Id Frame 
* 1Thread 0x7f8f5ee6fe40 (LWP 627067) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  2Thread 0x7f8f5e54f6c0 (LWP 627068) "worker"   __GI___libc_read 
(nbytes=256, buf=0x7f8f5e54d8c0, fd=21) at ../sysdeps/unix/sysv/linux/read.c:26
  3Thread 0x7f8f5dd4e6c0 (LWP 627069) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f8f5d54d6c0 (LWP 627070) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f8f5cd4c6c0 (LWP 627071) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f8f57fff6c0 (LWP 627072) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7f8f577fe6c0 (LWP 627073) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f8f56ffd6c0 (LWP 627074) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7f8f567fc6c0 (LWP 627075) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7f8f55ffb6c0 (LWP 627076) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7f8f557fa6c0 (LWP 627077) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7f8f54ff96c0 (LWP 627078) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7f8f26c0 (LWP 627079) "worker"   syscall () at 
../sysdeps

[Bug 2018555] Re: Nautilus rendering is broken if GTK_THEME env variable exists

[Thomas Debesse]

This looks fixed in Ubuntu 23.04 and this was reported against Ubuntu 22.10.
So, now that Ubuntu 22.10 is not supported, this can be considered fixed.

That said, I don't understand why this bug was closed because “there has
been no activity for 60 days”.

The bug was still reproducible on Ubuntu 22.10 and reproduction
instructions properly described.

Bugs don't disappear by magic because there is no comment to add.

I noticed that setting GTK_THEME to empty string (you also have to
export the variable) still changes the way nautilus look in Ubuntu
23.04, but the different look doesn't make nautilus unusable (unlike
what happened on Ubuntu 22.10).

```
killall nautilus
export GTK_THEME=
nautilus
```

I'm not sure what happens on Ubuntu 23.04 is a bug, though.

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

Title:
  Nautilus rendering is broken if GTK_THEME env variable exists

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


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

[Bug 2036528] Re: Can't turn on bluetooth

[Thomas Bechtold]

works now. closing.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  Can't turn on bluetooth

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


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

[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[Thomas Bechtold]

And it happened again after I unplugged and plugged my usb-c->display
port cable . looks like this time there's more useful information in the
logs.

** Attachment added: "journal.txt after unplug/plug the display port cable with 
mutter (45.0-1ubuntu1)"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702554/+files/journal.txt

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

Title:
  one of 3 monitors "frozen" when a window moves there

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


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

[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[Thomas Bechtold]

with latest mutter+gnome-shell (single GPU), this still happens. log
attached.

** Attachment added: "journal.txt from current boot 2 seconds after the problem 
occured with mutter (45.0-1ubuntu1)"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702553/+files/journal.txt

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

Title:
  one of 3 monitors "frozen" when a window moves there

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


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

[Bug 2036528] [NEW] Can't turn on bluetooth

[Thomas Bechtold]

Public bug reported:

When I try to click (enable) the toggle switch in the bluetooth panel in
gnome-control-center, nothing happens. Bluetooth is always disabled.
This happens since roughly 2 days on mantic.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-control-center 1:45.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 19 10:27:46 2023
InstallationDate: Installed on 2023-05-10 (132 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to mantic on 2023-07-19 (61 days ago)

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


** Tags: amd64 apport-bug mantic third-party-packages wayland-session

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

Title:
  Can't turn on bluetooth

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


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

[Bug 2035114] [NEW] zenity 3.24.1 --question argument does not return a value in ubuntu 22.04

[Thomas Sauve]

Public bug reported:

'--question' attribute in zenity is not returning a value after the user 
interacts with the message box.  It should be returning a 0, 1, or 5 depending 
on what the user selects.  Other forms that zenity produces do return the 
appropriate values.
tom@BossUbuntui9:~$ zenity --version
3.42.1
tom@BossUbuntui9:~$ zenity --calendar
09/12/2024
tom@BossUbuntui9:~$ zenity --question --title="Answer the question." 
--text="Yes or No?"
tom@BossUbuntui9:~$
This is a paste from my terminal.  As you can see the --version and --calendar 
arguments return the appropriate values.  When I use the --question argument, 
it does not matter whether I press yes or no, I get nothing.

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

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

Title:
  zenity 3.24.1 --question argument does not return a value in ubuntu
  22.04

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


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

[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[Thomas Bechtold]

> Please try adding this to /etc/environment as a workaround:

>  MUTTER_DEBUG_FORCE_KMS_MODE=simple

this seem to help. and it also helps for having the mouse pointer in
firefox working again (I filled
https://bugzilla.mozilla.org/show_bug.cgi?id=1852519 for that)

Does that have any negative impact (on performance)?

** Bug watch added: Mozilla Bugzilla #1852519
   https://bugzilla.mozilla.org/show_bug.cgi?id=1852519

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

Title:
  one of 3 monitors "frozen" when a window moves there

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


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

[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[Thomas Bechtold]

** Attachment added: "journal.txt from current boot 2 seconds after the problem 
occured"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035016/+attachment/5699911/+files/journal.txt

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

Title:
  one of 3 monitors "frozen" when a window moves there

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


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

[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there

[Thomas Bechtold]

@Daniel, what exactly do you need from the journal? I don't want to post
the full output here. it contains some private user sessions services
output which I don't want to share.

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

Title:
  one of 3 monitors "frozen" when a window moves there

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


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

[Bug 2035054] [NEW] Reset keyboard shortcuts gets overwritten and modifications show up again

[Thomas Bechtold]

Public bug reported:

I did reset all keyboard shortcuts (Settings->Keyboard->View and customize 
Shortcuts) via the "Reset All ..." button.
But now (after a reboot and apt update && apt dist-upgrade) I have some 
modfications back. Those modifications are:

- Windows->Maximize Window
- Windows->Restore Window
- Windows->View split on left
- Windows->View split on right


Note that I have disabled all extensions (via the Extensions App and then the 
top toggle) but the "Ubuntu Tilling Assistant" toggle was still active. 
Deactivating that one does reset the Shortcuts again (and eg. Super+Left does 
work again)

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-settings-daemon 45~rc-1ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 11 06:48:03 2023
InstallationDate: Installed on 2023-05-10 (124 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/usr/bin/zsh
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to mantic on 2023-07-19 (53 days ago)

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


** Tags: amd64 apport-bug mantic wayland-session

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

Title:
  Reset keyboard shortcuts gets overwritten and modifications show up
  again

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


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

[Bug 2035016] [NEW] one of 3 monitors "frozen" when a window moves there

[Thomas Bechtold]

Public bug reported:

When I move a window to one of my 3 monitors (not the main display), the
monitor freezes. That means that moving the mouse there doesn't work and
the picture is frozen on that monitor (including the mouse pointer which
is visible there).

The journal has those logs:

Sep 10 07:21:49 clown-t14 gnome-shell[5640]: 
meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' 
failed
Sep 10 07:21:49 clown-t14 systemd[5341]: Started 
vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 
launched by kgx process 7379.
Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use 
Mtk.Rectangle instead
Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use 
Mtk.Rectangle instead
Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use 
Mtk.Rectangle instead
Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use 
Mtk.Rectangle instead
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already 
disposed — impossible to get any property from it. This might be caused by the 
object having been destroyed from C code using something such as destroy(), 
dispose(), or remove() vfuncs.
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d5260 b   
resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 
0x55b0777837f0 ==
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0   7ffe4d1d53b0 b   
resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1   55b07789ddb8 i   
resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2   55b07789dd30 i   
resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3   55b07789dc98 i   
resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4   55b07789dc08 i   
resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5   55b07789db80 i   
resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6   55b07789daf0 i   
resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7   55b07789da70 i   
resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8   55b07789d9f0 i   
resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9   7ffe4d1dc560 b   
resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10   55b07789d968 i   
resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11   55b07789d8d8 i   
resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48)
Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object 
.Gjs_ui_workspaceThu

[Bug 1648534] Re: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_internal from g_dbus_

[Thomas]

Facing the same issue with one of my client's site. Related to https://capapkcut.com/story-keren-capcut-template/";>Story
Keren.

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

Title:
  gnome-software crashed with SIGTRAP in g_wakeup_new from
  g_main_context_new from g_dbus_connection_send_message_with_reply_sync
  from g_dbus_connection_call_sync_internal from
  g_dbus_connection_call_sync

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

[thomas]

Is there any progress on this issue? (Progress as in: works for end-
users as it did the last 20 years…)

-- 
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 2023491] [NEW] Deleting files causes folders in the directory to disappear and reappear after a refresh

[Thomas Perl]

Public bug reported:

I'm experiencing some inconsistencies when using Nautilus and deleting
files.

I've found a bug report upstream that describes the same behavior:

https://gitlab.gnome.org/GNOME/nautilus/-/issues/2941

Reproduced here for completeness:

Steps to reproduce

- Open a directory.
- Delete some files, either permanently or move to wastebasket.
- Refresh the current view.

Current behavior

- Folders that were not selected to be deleted disappear.

Expected behavior

- Only the selected files are deleted and removed from the file view.


This bug (which affects me on Ubuntu 23.04) has apparently been fixed in 
upstream Gtk:

https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5873

Please pull the fixes into Ubuntu 23.04.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: nautilus 1:44.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 11 19:06:01 2023
GsettingsChanges:
 b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'"
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'"
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true'
 b'org.gnome.nautilus.window-state' b'initial-size' b'(1607, 1234)'
InstallationDate: Installed on 2021-11-12 (575 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: nautilus
UpgradeStatus: Upgraded to lunar on 2023-04-12 (60 days ago)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1

** Affects: nautilus
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug lunar

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

** Also affects: nautilus via
   https://gitlab.gnome.org/GNOME/nautilus/-/issues/2941
   Importance: Unknown
   Status: Unknown

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

Title:
  Deleting files causes folders in the directory to disappear and
  reappear after a refresh

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/2023491/+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

[thomas]

Is there any progress on this one? It completely disrupts workflows and
is the single most annoying bug in the Gnome shell since a few years.

-- 
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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[thomas]

Why is this bug a duplicate of
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968887 ?

It should definitely be the other way around, since it does not only
affect chromium but all programs using the Gnome shell file-save dialog.

-- 
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 2018555] [NEW] Nautilus rendering is broken if GTK_THEME env variable exists

[Thomas Debesse]

Public bug reported:

In Ubuntu 22.10, nautilus rendering is broken as soon as GTK_THEME
environment exists, and there are some other components of GNOME that
sets it at desktop launch (for example the Desktop may set it as
GTK_THEME=Adwaita:dark).

I have found no GTK_THEME value to make nautilus render properly, even
the empty string breaks nautilus.

How to reproduce:

```
killall nautilus
GTK_THEME=
nautilus
```

Then try to select some icons, selected icons will not be displayed as
selected.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri May  5 06:49:41 2023
GsettingsChanges:
 
ProcEnviron:
 LANGUAGE=fr_FR:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1
 nautilus-image-converter  0.4.0-2
 python3-nautilus  4.0-1

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


** Tags: amd64 apport-bug kinetic third-party-packages

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

Title:
  Nautilus rendering is broken if GTK_THEME env variable exists

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


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

[Bug 2011751] Re: openbox crashed with SIGABRT

[Thomas Ward]

After discussion with the Security Team, we do not believe this is a
Security bug and that there currently is no need to keep it private as
there is other public discourse via other related bugs on other trackers
and here in Launchpad with other bugs (marked as dupes of this or such).

** Information type changed from Private Security to Public

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

Title:
  openbox crashed with SIGABRT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions


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

[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

[Thomas Ward]

Regarding NGINX, PCRE2 support is now available in NGINX nginx 1.21.5+
so there was support as of December 24th 2021 and later.

Which means that NGINX 1.22+ supports PCRE2.  This could be marked as
Triaged *for 23.04 and later* once NGINX is merged in from Debian
upstream, if someone can put a few cycles to build/test.

Refer to
https://trac.nginx.org/nginx/changeset/0b5f12d5c531be630a4aae644686be83cfed3267/nginx
and the "fixed" Trac bug https://trac.nginx.org/nginx/ticket/720

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

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

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

[Thomas Løcke]

This annoying bug rears its ugly head since I upgraded my own and my
wifes computer to Ubuntu 22.04. This does not happen on my 18.04 laptop
or 20.04 workbox.

When using the Save As dialog, focus switches to the filter/search field
in the dialog when we start typing a name for the file. The focus change
happens after each character, so it's practically unusable.

Confirmed with Firefox (snap), Google Chrome (PPA) and Brave (snap).

-- 
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 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04

[Thomas Løcke]

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

This annoying bug rears its ugly head since I upgraded my own and my
wifes computer to Ubuntu 22.04. This does not happen on my 18.04 laptop
or 20.04 workbox.

When using the Save As dialog, focus switches to the filter/search field
in the dialog when we start typing a name for the file. The focus change
happens after each character, so it's practically unusable.

Confirmed with Firefox (snap), Google Chrome (PPA) and Brave (snap).

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

Title:
  Save As Dialog Box does not get focus in Ubuntu 22.04

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


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

[Bug 1993594] Re: Scrolling in a view with many files is broken

[Thomas M Steenholdt]

Possibly related to https://gitlab.gnome.org/GNOME/gtk/-/issues/2971

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

Title:
  Scrolling in a view with many files is broken

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


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

[Bug 1993594] Re: Scrolling in a view with many files is broken

[Thomas M Steenholdt]

** Attachment added: "Video showing problem. Using mouse wheel to ONLY scroll 
up."
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993594/+attachment/5625351/+files/Screencast%20from%202022-10-19%2021-52-35.webm

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #2971
   https://gitlab.gnome.org/GNOME/gtk/-/issues/2971

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

Title:
  Scrolling in a view with many files is broken

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


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

[Bug 1993594] [NEW] Scrolling in a view with many files is broken

[Thomas M Steenholdt]

Public bug reported:

Scrolling up and down in a Files window, in a directory with many files,
the scrolling is erratic and seems to often jump to the bottom of the
view.

It happens only when scrolling while hovering the actual files (eg.
using the mouse wheel). If hovering the scrollbar instead, there are no
problems.

The problem is bad enough, it's basically useless to get things done.

Problem happens both in List View and Grid View

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: nautilus 1:43.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Wed Oct 19 21:42:25 2022
GsettingsChanges:
 b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'"
 b'org.gnome.nautilus.window-state' b'initial-size' b'(2179, 1167)'
InstallationDate: Installed on 2022-05-20 (152 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: nautilus
UpgradeStatus: Upgraded to kinetic on 2022-10-01 (18 days ago)
usr_lib_nautilus:
 file-roller   43.0-1
 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1

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


** Tags: amd64 apport-bug kinetic wayland-session

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

Title:
  Scrolling in a view with many files is broken

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


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

[Bug 1990521] Re: Open gnome-terminal window not shown in favorite list

[Thomas Bechtold]

This is solved with gnome-shell 43.0-1ubuntu2 from kinetic. Feel free to
close the bug.

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

Title:
  Open gnome-terminal window not shown in favorite list

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


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

[Bug 1990521] [NEW] Open gnome-terminal window not shown in favorite list

[Thomas Bechtold]

Public bug reported:

I have gnome-terminal pinned as favorite . But when I open a window,
gnome-terminal is shown at the bottom instead of adding a red dot to the
pinned icon. That only happens with gnome-terminal. Other applications
(eg. Thunderbird, hexchat, emacs) do have the dot beside the pinned
icon.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell-extension-ubuntu-dock 72ubuntu6
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 22 13:41:38 2022
InstallationDate: Installed on 2022-03-21 (184 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to kinetic on 2022-09-18 (3 days ago)

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


** Tags: amd64 apport-bug kinetic third-party-packages wayland-session

** Attachment added: "gnome-terminal open application not showing in pinned 
icon"
   
https://bugs.launchpad.net/bugs/1990521/+attachment/5618043/+files/gnome-terminal-pin.png

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

Title:
  Open gnome-terminal window not shown in favorite list

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


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

[Bug 1987076] Re: Mouse cannot control windows after suspend and display change

[Thomas M Steenholdt]

lspci -k

** Attachment added: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+attachment/5610691/+files/lspci.txt

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

Title:
  Mouse cannot control windows after suspend and display change

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


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

[Bug 1987076] Re: Mouse cannot control windows after suspend and display change

[Thomas M Steenholdt]

journalctl -b0

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+attachment/5610690/+files/journal.txt

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

Title:
  Mouse cannot control windows after suspend and display change

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


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

[Bug 1987076] Re: Mouse cannot control windows after suspend and display change

[Thomas M Steenholdt]

Thanks for the directions...

It's not that hard to reproduce here, I just have to move between places
(or I could bring my other monitor closer, for more intense
troubleshooting if need be). But it just happened...

There are no recent crashes and nothing reported by whoopsie. The
requested files are attached.

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

Title:
  Mouse cannot control windows after suspend and display change

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


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

[Bug 1987076] [NEW] Mouse cannot control windows after suspend and display change

[Thomas M Steenholdt]

Public bug reported:

My setup is this:

Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland)
Laptop: Lenovo ThinkPad P14s Gen 2a (AMD).
Display: Lenovo T34w-20, connected via USB-C

The problem started with upgrade to 22.04
I have had the same exact problem with my previous laptop, a ThinkPad T14s. 
Both of these are AMD laptops, but I had no problem on 21.10.

Way I can usually reproduce (always?)

1. Suspend my laptop by yanking out the USB-C cable.
2. Resume the laptop by connecting a different monitor (same make and model, 
but not the same physical one) and hit the keyboard a few times.

Note: Resuming on the same physical display does not seem to result in
the same problem.

After this, I can no longer control the Windows on my desktop. The mouse
cursor is active, but moves behind the open windows, and mouse click is
not registered (at least not in a way that is useful).

I can navigate the windows and use the applications, using the keyboard.

Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the real
session, mouse is still "broken".

Ctrl+Alt+F2 to get to a TTY, and going back to the original session,
mouse is still "broken".

Only way I have found to reliably restore functionality is a reboot
(which I have been doing a lot of the last few months).

Please let me know what else I can provide you with, in order to get
this fixed. :)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter 42.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Fri Aug 19 10:32:48 2022
InstallationDate: Installed on 2022-05-20 (91 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Mouse cannot control windows after suspend and display change

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


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

[Bug 1948881] Re: XSane plugin not available in GIMP File menu

[Thomas Stieler]

I would also like to wait until fixed packages reach the users.

Is is feasible to update the packages for 22.04 or do we have to wait
for 22.10?

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

Title:
  XSane plugin not available in GIMP File menu

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


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

[Bug 1948881] Re: XSane plugin not available in GIMP File menu

[Thomas Stieler]

Of course it would be much better, if the root cause of this issue would
be fixed.

An update of Gimp or xsane will most probably overwrite the manual
changes.

You can trigger a pluginrc rewrite by touching the xsane plugin binary.

But for me the hack works good enough to use xsane again...

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

Title:
  XSane plugin not available in GIMP File menu

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


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

[Bug 1948881] Re: XSane plugin not available in GIMP File menu

[Thomas Stieler]

I think that there's a mechanism to update the pluginrc, when a plugin
was updated.

The number at the end of the first line of the diff looks like a
timestamp: Can you delete the pluginrc and let Gimp rebuild it.

Then keep the generated line with the "plug-in-def" and replace the
other lines according to the diff.

This works for me...

If it doesn't work for you, make a backup of the generated pluginrc and
post the difference between the backup and your modified version, maybe
there is another issue...

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

Title:
  XSane plugin not available in GIMP File menu

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


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

[Bug 1948881] Re: XSane plugin not available in GIMP File menu

[Thomas Stieler]

** Attachment added: "Pluginrc from focal fossa"
   
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1948881/+attachment/5598408/+files/pluginrc_focal

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

Title:
  XSane plugin not available in GIMP File menu

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


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

[Bug 1948881] Re: XSane plugin not available in GIMP File menu

[Thomas Stieler]

** Attachment added: "Pluginrc from jammy jellyfish"
   
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1948881/+attachment/5598409/+files/pluginrc_jammy

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

Title:
  XSane plugin not available in GIMP File menu

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


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

[Bug 1948881] Re: XSane plugin not available in GIMP File menu

[Thomas Stieler]

I will attach the xsane-relevant part from the automatically generated
pluginrc file, first version from focal fossa and second from jammy
jellyfish.

Here are the diffs:

stieler@mercury:~/Desktop$ diff  pluginrc_jammy pluginrc_focal
1c1
< (plug-in-def "${gimp_plug_in_dir}/plug-ins/xsane/xsane" 1651153157
---
> (plug-in-def "${gimp_plug_in_dir}/plug-ins/xsane" 1614568029
8,9c8,10
<  "/File/Acquire/XSane/Device dialog..."
<  0
---
>  ""
>  1
> (menu-path "/File/Create/Acquire/XSane/Device dialog...")
13a15
>

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

Title:
  XSane plugin not available in GIMP File menu

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


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

[Bug 1948881] Re: XSane plugin not available in GIMP File menu

[Thomas Stieler]

Stupid enough that this issue ist still not fixed.

I booted an old Ubuntu version in virtualbox and installed Gimp and
xsane. Then I just compared the working plugin configuration and
manually aligned the autogenerated configuration.

So I got a working xsane plugin.

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

Title:
  XSane plugin not available in GIMP File menu

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


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

[Bug 1948881] Re: XSane plugin not available in GIMP File menu

[Thomas Wolf]

I'm affected by this bug, too.
I'm on Ubuntu 22.04. Is there anything new?
What can I do as a workaround?

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

Title:
  XSane plugin not available in GIMP File menu

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


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

[Bug 1978340] [NEW] "flatpak run ..." fails with "bwrap: Can't get type of source /mnt: Permission denied"

[Thomas Bechtold]

Public bug reported:

When I try to start a flatpak app, I get:

$ flatpak run org.gnome.gitg 
bwrap: Can't get type of source /mnt: Permission denied
error: Failed to sync with dbus proxy
$ echo $?
1

I have:
$ flatpak list
Name  Application ID
 Version BranchInstallation
Freedesktop Platform  org.freedesktop.Platform  
 21.08.1421.08 system
Mesa  
org.freedesktop.Platform.GL.default21.3.8  21.08 system
openh264  org.freedesktop.Platform.openh264 
 2.1.0   2.0   system
GNOME Application Platform version 41 org.gnome.Platform
 41system
gitg  org.gnome.gitg
 41  stablesystem
Yaru Gtk Themeorg.gtk.Gtk3theme.Yaru
 3.22  system

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: flatpak 1.12.7-1
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
Uname: Linux 5.15.0-35-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 10 20:08:35 2022
InstallationDate: Installed on 2022-03-21 (80 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: flatpak
UpgradeStatus: Upgraded to jammy on 2022-03-21 (80 days ago)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  "flatpak run ..." fails with "bwrap: Can't get type of source /mnt:
  Permission denied"

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


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

[Bug 1967235] Re: Can not trash files in other partitions

[Thomas]

There are rumors that a Trash existent directory like .Trash-th might
help in this specific partition/mount but it does not help.

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

Title:
  Can not trash files in other partitions

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


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

[Bug 1967235] [NEW] Can not trash files in other partitions

[Thomas]

Public bug reported:

I know this is an old one, but this is still present, either it is a
regression or not. Files in another partition than home can only be
deleted but not moved to Trash, even if the whole partition has writing
allowed for the current user.

How to reproduce:

USER=th

mkdir /home/th/shim
sudo mkdir /mnt/shim
sudo mount -o bind /home/th/shim
cd /mnt/shim
touch ttt
nautilus /mnt/shim

Now trashing ttt fails. However trashing when in /home/th/shim it works.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-lowlatency 5.8.18
Uname: Linux 5.8.0-55-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Thu Mar 31 09:27:36 2022
InstallationDate: Installed on 2019-12-19 (832 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
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 third-party-packages

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

Title:
  Can not trash files in other partitions

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


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

[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"

[Thomas Schmitt]

Hi,

> > *Do you experience the problem with CD-R or CD-RW media ?*

> Yes. The exact same error message as when I tried to make a DVD.

Then it is not exactly the same problem as with the DRW-24D5MT of
Mauro Sacchetto and my BW-16D1HT as of Debian bug 998718.

Your Brasero version 3.12.1-4ubuntu2 seems slightly younger than
the 3.12.3-1 of Mauro and the 3.12.2-5 which i tested. But there was
no visible development in Brasero since quite a while. So i would not
blame the difference on the versions ... for now.


> > Does it help to blank the CD medium before using it with Brasero:
> > xorriso -outdev /dev/sr0 -blank as_needed*

> Unfortunately No.

What about other burn programs (with a power-cycle between the last
Brasero run and the the new experiment) ?

Like:

ISO="...path.to.your.iso.image.file..."
xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed "$ISO"


Have a nice day :)

Thomas

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

Title:
  Brasero does not burn ISO IMAGE. Error message;  "SCSI error on
  write(0,16): See MMC specs: Sense Key 5 "Illegal request"

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


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

[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"

[Thomas Schmitt]

Hi,

C. Clear wrote:
> What does doing a power off/on cycle entail ???

Just a shutdown so that the burner drive has no electrical power.
If in doubt whether the power is really off, press the drive's eject 
button. The drive should not react.


Have a nice day :)

Thomas

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

Title:
  Brasero does not burn ISO IMAGE. Error message;  "SCSI error on
  write(0,16): See MMC specs: Sense Key 5 "Illegal request"

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


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

[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"

[Thomas Schmitt]

Hi,

C. Clear wrote:
> Drive type   : vendor 'ASUS' product 'BW-16D1HT' revision '3.10'

That would match the Debian bug of last year.


>  Did try Nero for Linux and had the same
> result as I did with Brasero.

Keep in mind that in the Debian bug scenario Brasero's bad read attempt
spoiled the two ASUS drives until they got a power-off-on cycle. If the
drive is built into the computer this means a power-off-on cycle of the
computer, i fear. (I have mine in a USB box. That eases the problem.)

It was enough to show Brasero a CD burnt with wite type TAO to let the
drive go mad. It was not necessary to make a burn attempt.
The only workaround was to blank CD-RW by other programs before giving
them to Brasero for being re-written.

Unfortunately TAO is the write type used by Brasero itself. Other programs
may choose SAO with the consequence that those CDs don't let the drive go
mad, even when they get shown to Brasero.


Have a nice day :)

Thomas

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

Title:
  Brasero does not burn ISO IMAGE. Error message;  "SCSI error on
  write(0,16): See MMC specs: Sense Key 5 "Illegal request"

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


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

[Bug 1964554] Re: Brasero does not burn ISO IMAGE. Error message; "SCSI error on write(0,16): See MMC specs: Sense Key 5 "Illegal request"

[Thomas Schmitt]

Hi,

the error message stems from the burner drive and was forwarded by libburn
to Brasero. Strangely the code ASC=21 , ASCQ=04 is not specified in in
the SCSI specs for optical drives (MMC).
In the overall error code list
  https://www.t10.org/lists/asc-num.htm
it is listed for other device classes as
  21h/04h  DZ UNALIGNED WRITE COMMAND

I know this error code from
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998718
with
  Drive type   : vendor 'ASUS' product 'DRW-24D5MT' revision '2.00'
Brasero crashed at that occasion before it could start to write.
The indirect reason seems to be a bad READ CD command which Brasero
emitted on its own (i.e. not via libburn). It brings the firmware of
two ASUS drives to a state from where it throws that error code.
(Mine is a BW-16D1HT with firmware 1.01.)
It happens only with CD media which were written by write type TAO.

So (assuming that the drive has address /dev/sr0):

- What is the vendor, model, revision of your drive.
  You may obtain it from the empty drive by

xorriso -outdev /dev/sr0 -toc | grep 'Drive type'

- Do you experience the problem with CD-R or CD-RW media ?
  If so:

  - What happens if you use a writable DVD medium instead ?

  - Does it help to blank the CD medium before using it with Brasero:

  xorriso -outdev /dev/sr0 -blank as_needed

- Do you experience the problem with other GUI programs like K3B or
  Xfburn ?

- Do you experience the problem with a run of xorriso ?

ISO="...path.to.your.iso.image.file..."
xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed "$ISO"


Have a nice day :)

Thomas


** Bug watch added: Debian Bug tracker #998718
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998718

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

Title:
  Brasero does not burn ISO IMAGE. Error message;  "SCSI error on
  write(0,16): See MMC specs: Sense Key 5 "Illegal request"

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


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

[Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"

[Thomas Bechtold]

** Changed in: launchpad-buildd
   Status: New => Invalid

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

Title:
  CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions


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

[Bug 1948521] [NEW] SMTP: does not wait for the "real" response

[Thomas]

Public bug reported:

evolution goes on with "mail from" though the "real" response to AUTH PALIN has 
not received
here a debug protocol

[SMTP] Connecting to server securesmtp.t-online.de:465 ...
[SMTP] received: 220-fwd86.t-online.de T-Online ESMTP receiver fmsad ready.
[SMTP] received: 220 T-Online ESMTP receiver securesmtp.t-online.de ready.
[SMTP] sending: EHLO apt.cache
[SMTP] received: 250-fwd86.t-online.de ready.
[SMTP] received: 250-SIZE 52428800
[SMTP] received: 250-8BITMIME
[SMTP] received: 250-AUTH=LOGIN PLAIN
[SMTP] received: 250-AUTH LOGIN PLAIN
[SMTP] received: 250-ENHANCEDSTATUSCODES
[SMTP] received: 250 HELP
[SMTP] sending: AUTH PLAIN ...
[SMTP] received: 235-2.5.0 Authentication successful.

// 235-2.5.0 this is not the end of the response, but evolution goes on
with MAIL FROM

[SMTP] Sending with server securesmtp.t-online.de:465 ...
[SMTP] sending: MAIL FROM: ...

// and now the real 235 came in and evolution reports an error because
it wants a 250

[SMTP] received: 235 2.5.0 Authentifizierung erfolgreich.

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

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

Title:
  SMTP: does not wait for the "real" response

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


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

[Bug 1944084] [NEW] file roller crashed by file.zip 20 GB

[Thomas Peirick]

Public bug reported:

First, my English is very bad! Sorry! File roller crashed by files at 20
GB. First I have tried "b1freearchiver": no problems, but not translated
in german, than I tried "Ark": perfect, no problems and translated in
german, and, surprise, nautilus works with Ark! Could you solve the
problem in Gnome: Thanks!

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  file roller crashed by file.zip 20 GB

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


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

[Bug 1939318] [NEW] package gir1.2-gdm-1.0:amd64 3.36.3-0ubuntu0.20.04.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuratio

[Thomas Nguyen]

Public bug reported:

i was trying to install docker and this happend

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: gir1.2-gdm-1.0:amd64 3.36.3-0ubuntu0.20.04.4
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Aug  9 17:35:08 2021
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2021-08-09 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: gdm3
Title: package gir1.2-gdm-1.0:amd64 3.36.3-0ubuntu0.20.04.4 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package gir1.2-gdm-1.0:amd64 3.36.3-0ubuntu0.20.04.4 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

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


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

[Bug 254171] Re: Nautilus can't properly unmount FUSE file systems

[Thomas Uhle]

** Package changed: fuse (Debian) => fuse

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

Title:
  Nautilus can't properly unmount FUSE file systems

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

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

[Bug 254171] Re: Nautilus can't properly unmount FUSE file systems

[Thomas Uhle]

According to https://github.com/karelzak/util-linux/pull/705, this issue
seems to have been fixed natively in mount/libmount1 from util-linux
(since version 2.34). So it should work with Ubuntu 20.04 LTS (focal
fossal) and newer.

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

Title:
  Nautilus can't properly unmount FUSE file systems

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

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

[Bug 254171] Re: Nautilus can't properly unmount FUSE file systems

[Thomas Uhle]

** Bug watch added: github.com/libfuse/libfuse/issues #246
   https://github.com/libfuse/libfuse/issues/246

** Also affects: fuse (Debian) via
   https://github.com/libfuse/libfuse/issues/246
   Importance: Unknown
   Status: Unknown

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

Title:
  Nautilus can't properly unmount FUSE file systems

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

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

[Bug 254171] Re: Nautilus can't properly unmount FUSE file systems

[Thomas Uhle]

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

** Changed in: nautilus
   Importance: Medium => Unknown

** Changed in: nautilus
   Status: Confirmed => Unknown

** Changed in: nautilus
 Remote watch: GNOME Bug Tracker #607706 => 
gitlab.gnome.org/GNOME/gvfs/-/issues #133

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

Title:
  Nautilus can't properly unmount FUSE file systems

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

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

[Bug 1926402] Re: Gdm offers different login methods randomly

[Thomas]

journalctl --unit=gdm.service

There is following strange line:

Apr 30 19:07:27 seal gdm-fingerprint][8190]: gkr-pam: no password is
available for user

** Attachment added: "gdm-service.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1926402/+attachment/5493936/+files/gdm-service.txt

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

Title:
  Gdm offers different login methods randomly

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

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

[Bug 1926402] Re: Gdm offers different login methods randomly

[Thomas]

Added two files as wished.

Further observation: sometimes it is switching between both methods when
re-selecting the login user from the list.

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

Title:
  Gdm offers different login methods randomly

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

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

[Bug 1926402] Re: Gdm offers different login methods randomly

[Thomas]

** Attachment added: "gdm-finger.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1926402/+attachment/5493934/+files/gdm-finger.txt

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

Title:
  Gdm offers different login methods randomly

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

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

[Bug 1926402] Re: Gdm offers different login methods randomly

[Thomas]

** Attachment added: "gdm-hybrid.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1926402/+attachment/5493935/+files/gdm-hybrid.txt

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

Title:
  Gdm offers different login methods randomly

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

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

[Bug 1926402] [NEW] Gdm offers different login methods randomly

[Thomas]

Public bug reported:

I have enabled fingerprint login for my device. GDM is offering
sometimes hybrid authentication like: password or swipe finger. But
sometimes it offers only fingerprint. This is very strange and I like
the hybrid variant. So it changes its behaviour between several reboots.
I can not relate this this to any special event or anything.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.36.3-0ubuntu0.20.04.3
ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Apr 28 08:49:00 2021
InstallationDate: Installed on 2019-12-19 (495 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2021-04-23T01:47:10.096850

** Affects: gdm3 (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 gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1926402

Title:
  Gdm offers different login methods randomly

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

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

[Bug 1918033] Re: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor))

[Thomas M Steenholdt]

I am no longer able to reproduce the crash after installing the proposed
fix! Looks good to me! :)

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

Title:
  gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-
  stage.c:3785:on_device_actor_reactive_changed: assertion failed:
  (!clutter_actor_get_reactive (actor))

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

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

[Bug 1918412] [NEW] gnome-shell crashed

[Thomas Bechtold]

Public bug reported:

Not sure what I actually did.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.3-3ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 10 09:03:49 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-12-08 (91 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
RelatedPackageVersions: mutter-common 3.38.3-3ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to hirsute on 2020-12-09 (90 days ago)

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


** Tags: amd64 apport-bug hirsute wayland-session

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

Title:
  gnome-shell crashed

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

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

[Bug 1918127] [NEW] gnome-shell crash when using panel

[Thomas M Steenholdt]

Public bug reported:

Whenever I perform an action in the Gnome Panel (Activate a VPN has 100%
failure-rate, but I have seen it when clearing notifications and other
things too), the entire session crashes and I'm back at login.

I'm running gnome-session on Hirsute.

journalctl /usr/bin/gnome-shell shows the following just before the
crash:

Mar 08 07:02:40 localhost gnome-shell[67382]: **
Mar 08 07:02:40 localhost gnome-shell[67382]: 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))
Mar 08 07:02:40 localhost gnome-shell[67382]: Bail out! 
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
 assertion failed: (!clutter_actor_get_reactive (actor))

The problem is 100% reproducible.

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


** Tags: hirsute

** Tags added: hirsute

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

Title:
  gnome-shell crash when using panel

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

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

[Bug 1918127] Re: gnome-shell crash when using panel

[Thomas M Steenholdt]

Problem occurs on Wayland as well as Xorg.

Please let me know what kind of info you need.

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

Title:
  gnome-shell crash when using panel

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

[Thomas Kirby]

This is a problem regardless whether Pointer location is on or off.
The only difference is that when pointer location is on, you can't see the 
LEFT-CTRL key light up it corresponding element on the keyboard map,
i.e. Language & Region > Input Sources and then click on the eyeball button 
for the keyboard in use.

The LEFT-CTRL key is effectively dead.

How do we revitalise it since we need it for convenient command
shortcuts.

-- 
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 when using pointer location

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

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

[Bug 1900063] Re: Sync flatpak 1.8.2-3 (universe) from Debian sid (main)

[Thomas Ward]

Hello.

According to the tool to indicate whether a package is seeded or not,
Flatpak is currently seeded in Ubuntu Budgie and Xubuntu:

$ seeded-in-ubuntu flatpak
flatpak (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported
gir1.2-flatpak-1.0 (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported
libflatpak-dev (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported
libflatpak0 (from flatpak) is seeded in:
  ubuntu-budgie: supported
  xubuntu: supported

Ubuntu is now in Final Freeze - per the Final Freeze announcement [1],
packages need to fit one of these two categories:


1) Release critical bugs that affect ISOs, installers, or otherwise
   can't be fixed easily post-release.

2) Bug fixes that would be suitable for post-release SRUs, which we may
   choose to accept, reject, or shunt to -updates for 0-day SRUs on a
   case-by-case basis.  This second case should have SRU-style bugs filed
   with the appropriate template, referenced in changelog.


I don't see a justification included on the sync request that would put this 
request into either of the categories as this does not have any SRU template.

The only new changes I can see here are that it has a dependency on
DBus, but that you fix an issue with Parental Control checks.  That's
likely SRUable post-release.

However, I don't see justification to sync this at this time given we
are in Final Freeze.

** Changed in: flatpak (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Sync flatpak 1.8.2-3 (universe) from Debian sid (main)

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

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

[Bug 1897460] Re: VLC Snap Incompatible With Thunderbird

[Matthew Paul Thomas]

Andrew, I suggest deciding what you want this bug report to be about.

If it’s about the VLC snap, then in this case Sebastien suggests it’s a
bug in snapd.

If it’s about Ubuntu Software, then you should change the steps to
reproduce to focus on Ubuntu Software.

Either way, it should not be filed on software-center, which is a
separate app altogether.

** Package changed: software-center (Ubuntu) => gnome-software (Ubuntu)

** Changed in: gnome-software (Ubuntu)
   Status: New => Incomplete

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

Title:
  VLC Snap Incompatible With Thunderbird

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

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

[Bug 1896804] Re: CD/DVD drive detected as read only, command line and GUI programs

[Thomas Schmitt]

Hi,

sorry for your drive.

But good for Linux burn programs that MS-Windows does not know something
essential about drive error messages which we Linuxers don't know.

> the srange this is that if you use the Disks program in utilities.

That's probably a message from the kernel via systemd and lsblk.
Although the Linux kernel is willing to apply disk write commands to
overwritable media in optical drives, it mostly treats them as CD-ROM.

That's why there are burn programs in userspace which send SCSI commands
directly to the drive, circumventing the buffered block device layers of
the kernel.

And that's why much of the kernel's cdrom and sr driver code had few
motivation to follow the technical evolution from CD to DVD and BD.
(The relation of cdrom and sr is funny enough. cdrom was meant as
 abstraction of the various hunchbacked CD drives of the mid 1990s with
 proprietary controllers and command sets. sr represents for cdrom the 
 then rare SCSI drives which are now the only survivors at PATA, SATA 
 and USB. Meanwhile code execution hops forth and back between both
 drivers which are actually only one.)

Well, now i have to think what to do with my code change to tolerate all
6,28,XX error codes ...

Have a nice day :)

Thomas

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

Title:
  CD/DVD drive detected as read only, command line and GUI programs

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

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

[Bug 1896804] Re: CD/DVD drive detected as read only, command line and GUI programs

[Thomas Schmitt]

Hi,

well, at least we got over the strange error code.

> libburn : SORRY : Timeout exceed (3 ms). Retry canceled.
> libburn : SORRY : Command: READ DISC INFORMATION #63,[2 04 00] : 51 00
> 00 00 00 00 00 00 22 00  : dxfer_len= 34

The command READ DISC INFORMATION was retried 63 times. The last failure
was because of a timeout of 30 seconds.
The failed command does not cause much effort in the drive. It is just an
inquiry about the overall state of the loaded medium. Normally it is done
within less than a millisecond.

The drive seems to have announced that there is a medium loaded.
Else libburn would not have had interest in the medium state.

As it seems now, this drive is quite unusable. See below for a deeper
inspection of what is going on between it and libburn.

> Drive type   : vendor 'HL-DT-ST' product 'DVDRAM GH20NS10' revision
'EL00'

Googling "GH20NS10" "EL00" shows that this drive is around since 2007.
How old is yours ? When was last it was re-cabled or moved to another box ?

Do you have an opportunity to test it with MS-Windows without touching the
hardware ? It would be quite astonishing if it worked right now with the
same medium loaded as with your above xorriso run.

--

Let's break out the big gear and add command -scsi_log "on" to the xorriso
run. Because the output on standard error channel will be very verbous,
we catch it in a file in /tmp while still showing it on terminal:

  ./xorriso/xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 \
  | tee -i /tmp/xorriso.log

(I write this as two lines with a "\" at the end of the first, because the
 bug tracker breaks up oversized lines. You may write it in one line without
 that "\":

  ./xorriso/xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 | tee -i
/tmp/xorriso.log

)

This will log the SCSI commands and their replies as they go forth and back
between libburn and the drive.
Add the emerging file
  /tmp/xorriso.log
as attachment to your next comment.

If the attachment is rejected for any reason, send the file to
  scdbac...@gmx.net
as mail body or as attachment.

It will be interesting to see all error replies and the timing of command
execution.

--

Have a nice day :)

Thomas

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

Title:
  CD/DVD drive detected as read only, command line and GUI programs

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

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

[Bug 1896804] Re: CD/DVD drive detected as read only, command line and GUI programs

[Thomas Schmitt]

Correction:
The single command READ DISC INFORMATION probably did not timeout, but was 
repeated
with intermediate waiting until 30 seconds had elapsed. So the drive probably 
reacts swiftly but
always says that it is not yet ready.

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

Title:
  CD/DVD drive detected as read only, command line and GUI programs

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

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

[Bug 1896804] Re: CD/DVD drive detected as read only, command line and GUI programs

[Thomas Schmitt]

Hi,

> libburn : SORRY : Asynchronous SCSI error on waiting after START UNIT
> (+ LOAD) [6 28 81] Drive event. Unknown ASCQ with drive event ASC 28.

Grr. A higher level intervened.

In line 198 of file

  ~/xorriso/xorriso-1.5.3/libburn/spc.c

there is

if (key == 0x6 && asc == 0x28 && ascq == 0x00)

which should be shortened to

if (key == 0x6 && asc == 0x28)

Do you feel apt to make this code change and then run

  make

again ?
(Else i would upload a new tarball.)

This time i simulated the drive reply 0x6, 0x28, 0x81 in the waiting loop
from where the message stems. Without " && ascq == 0x00" in line 198 it
works for me. So now it is up to your drive to tell me where else this
unexpected error code creates mistrust, or what other interesting replies
it has to offer.

Have a nice day :)

Thomas

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

Title:
  CD/DVD drive detected as read only, command line and GUI programs

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

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

[Bug 1896804] Re: CD/DVD drive detected as read only, command line and GUI programs

[Thomas Schmitt]

The line with the absolute address was meant to be:

  /home/chris/xorriso/xorriso-1.5.3/xorriso/xorriso -outdev /dev/sr0
-toc

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

Title:
  CD/DVD drive detected as read only, command line and GUI programs

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

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

[Bug 1896804] Re: CD/DVD drive detected as read only, command line and GUI programs

[Thomas Schmitt]

Hi,

> Sense Key 6 "Drive event", ASC 28 ASCQ 81.

This SCSI error reply is not listed in SCSI specs SPC or MMC or in the
summary of T10 committee
  https://www.t10.org/lists/asc-num.htm#ASC_28

So the drive's firmware programmers were overly creative.

If it was ASCQ 0 or 2, then libburn would tolerate it:
  6 28 00 NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED
  6 28 02 FORMAT-LAYER MAY HAVE CHANGED
but the other ASCQs of ASC 28 were too obscure to me to be tolerable.

I now made a GNU xorriso tarball with a libburn which tolerates any Drive
event error with ASC 28 so that you can drill deeper into the drive behavior.

(I have to think whether this change is good as permanent solution. The list
 of key 6 errors looks in part fatal like
   6 29 00 POWER ON, RESET, OR BUS DEVICE RESET OCCURRED
   6 3B 0F END OF MEDIUM REACHED
 but in part retryable. My program change relies on the hope that all ASC 28
 codes are harmless.)



You will need the dependency packages of pseudo-package "build-essential"
  https://packages.ubuntu.com/xenial/build-essential
then download

  https://www.gnu.org/software/xorriso/xorriso-1.5.3.tar.gz

and copy it to a directory of your choice, e.g. to
  /home/chris/xorriso

Then build it by

  cd /home/chris/xorriso
  tar xzf xorriso-1.5.3.tar.gz
  cd xorriso-1.5.3
  ./configure --prefix=/usr && make

On a modern machine the "make" part should be done in half a minute.
Afterwards there should be an executable program
  ./xorriso/xorriso

You may use it in place by its relative address

  ./xorriso/xorriso -outdev /dev/sr0 -toc

or by its absolute address

  /home/chris/xorriso/xorriso-1.5.3/xorriso/xorriso

Your Ubuntu xorriso will stay installed and your package manager cannot
get confused by the newly made xorriso. (It is quite large because it contains
own copies of libburn, libisofs, libisoburn, and libjte.)

----

Have a nice day :)

Thomas

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

Title:
  CD/DVD drive detected as read only, command line and GUI programs

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

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

[Bug 1896804] Re: CD/DVD drive detected as read only, command line and GUI programs

[Thomas Schmitt]

I forgot to ask for putting in the desired medium before performing

  xorriso -outdev /dev/sr0 -toc

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

Title:
  CD/DVD drive detected as read only, command line and GUI programs

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

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

[Bug 1896804] Re: CD/DVD drive detected as read only, command line and GUI programs

[Thomas Schmitt]

Hi,

i understand from the category "brasero package" that you inspect the drive
by Brasero.

Which burn backend is it using (cdrecord, wodim, libburn ) ?
What kind of medium did you try (CD-R, DVD+R, DVD-R, DVD+RW, BD-R, ...) ?
Which task of Brasero do you want to perform (Audio project, Data project,
Burn image, ...) ?
What kind of files shall be used as input ?
By what message does Brasero tell you that the medium is read-only ?

What do you get from

  xorriso -devices

and if the desired target drive is listed (as e.g. /dev/sr0)

  xorriso -outdev /dev/sr0 -toc

Have a nice day :)

Thomas

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

Title:
  CD/DVD drive detected as read only, command line and GUI programs

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

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

[Bug 1894327] [NEW] package gnome-control-center 1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] failed to install/upgrade: trying to overwrite '/usr/share/applicatio

[Thomas Docherty]

Public bug reported:

Reading database ... 337678 files and directories currently installed.)
Preparing to unpack .../gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb ...
Unpacking gnome-control-center (1:3.37.90-1ubuntu2) over (1:3.36.2-1ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb 
(--unpack):
 trying to overwrite 
'/usr/share/applications/gnome-control-center.desktop', which is the 
diverted version of '/tmp/fallback-settings.tmp'
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: gnome-control-center 1:3.36.2-1ubuntu1 [modified: 
usr/share/applications/gnome-control-center.desktop]
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Sep  4 18:54:19 2020
DuplicateSignature:
 package:gnome-control-center:1:3.36.2-1ubuntu1 [modified: 
usr/share/applications/gnome-control-center.desktop]
 Unpacking gnome-control-center (1:3.37.90-1ubuntu2) over (1:3.36.2-1ubuntu1) 
...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-YeLaCI/189-gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb
 (--unpack):
  trying to overwrite '/usr/share/applications/gnome-control-center.desktop', 
which is the diverted version of '/tmp/fallback-settings.tmp'
ErrorMessage: trying to overwrite 
'/usr/share/applications/gnome-control-center.desktop', which is the diverted 
version of '/tmp/fallback-settings.tmp'
InstallationDate: Installed on 2020-08-13 (22 days ago)
InstallationMedia: Ubuntu Unity 20.10 "Groovy Gorilla" (20200610)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10
SourcePackage: gnome-control-center
Title: package gnome-control-center 1:3.36.2-1ubuntu1 [modified: 
usr/share/applications/gnome-control-center.desktop] failed to install/upgrade: 
trying to overwrite '/usr/share/applications/gnome-control-center.desktop', 
which is the diverted version of '/tmp/fallback-settings.tmp'
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package groovy package-conflict

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

Title:
  package gnome-control-center 1:3.36.2-1ubuntu1 [modified:
  usr/share/applications/gnome-control-center.desktop] failed to
  install/upgrade: trying to overwrite '/usr/share/applications/gnome-
  control-center.desktop', which is the diverted version of '/tmp
  /fallback-settings.tmp'

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

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

[Bug 1886728] [NEW] OpenVPN OTP replaces the ordinary password

[Thomas Bjørnson Larsen]

Public bug reported:

When OpenVPN has One-time password (OTP) enabled, and the user connects,
a dialog asks the user to enter the One-time password (OTP) and press
ok. This action replaces the ordinary "long term" password with the OTP.
This causes annoyance as the next login will fail because the password
is wrong and the user has to enter both the password and the OTP the
next time they log in.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-keyring 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul  8 01:07:18 2020
InstallationDate: Installed on 2020-03-23 (106 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gnome-keyring
UpgradeStatus: Upgraded to focal on 2020-05-11 (57 days ago)

** Affects: gnome-keyring (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-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1886728

Title:
  OpenVPN OTP replaces the ordinary password

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

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

[Bug 1882394] [NEW] xrdp configured, connects successful then terminates

[Thomas Schweikle]

Public bug reported:

xrdp is setup, connections to client work: mstsc connects to client,
authentication is successful, then starts x11, starts session,
terminates session, terminates x11, closes connection. All without any
visible error. Any idea why?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xrdp 0.9.12-1
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jun  6 23:33:49 2020
InstallationDate: Installed on 2019-09-09 (271 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=screen
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: xrdp
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xrdp (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 xrdp in Ubuntu.
https://bugs.launchpad.net/bugs/1882394

Title:
  xrdp configured, connects successful then terminates

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

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

[Bug 1880492] Re: nautilus takes a long time to shut down

[Thomas]

** Tags added: focal

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

Title:
  nautilus takes a long time to shut down

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

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

[Bug 1880492] Re: nautilus takes a long time to shut down

[Thomas]

Thanks for the bug report.

I was able to reproduce this on Focal with Nautilus version 3.36.2.

** Changed in: nautilus (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  nautilus takes a long time to shut down

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

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

[Bug 1880492] Re: nautilus takes a long time to shut down

[Thomas]

Appears to already be reported upstream here:
https://gitlab.gnome.org/GNOME/nautilus/-/issues/423

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

Title:
  nautilus takes a long time to shut down

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

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

[Bug 1879122] Re: Cannot enable wifi hotspot on the first attempt

[Thomas]

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  Cannot enable wifi hotspot on the first attempt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1879122/+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 when using pointer location

[Thomas]

It seems to work on a fresh install of 20.04. Is it likely to be fixed
on a running system or is it recommended to re-install 20.04? Thanks.

-- 
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 when using pointer location

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

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

[Bug 1878912] [NEW] Gimp Crashed

[Thomas Krcal]

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: Abgebrochen

Stack trace:
```
/lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x397)[0x7fed836ed8c7]
gimp-2.10(+0xd14a0)[0x56221a0334a0]
gimp-2.10(+0xd18d8)[0x56221a0338d8]
gimp-2.10(+0xd2037)[0x56221a034037]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x15540)[0x7fed82bfb540]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7fed82a393eb]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7fed82a18899]
/lib/x86_64-linux-gnu/libc.so.6(+0x25769)[0x7fed82a18769]
/lib/x86_64-linux-gnu/libc.so.6(+0x37006)[0x7fed82a2a006]
/lib/x86_64-linux-gnu/libX11.so.6(+0x3f493)[0x7fed828ee493]
/lib/x86_64-linux-gnu/libX11.so.6(+0x3f53d)[0x7fed828ee53d]
/lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x5a)[0x7fed828ee83a]
/lib/x86_64-linux-gnu/libX11.so.6(XPending+0x61)[0x7fed828e0171]
/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x5c3ef)[0x7fed837ae3ef]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1d1)[0x7fed82daf4e1]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x51a52)[0x7fed82dafa52]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x83)[0x7fed82dafe33]
gimp-2.10(app_run+0x357)[0x56221a032cb7]
gimp-2.10(main+0x395)[0x56221a0325b5]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7fed82a1a1e3]
gimp-2.10(_start+0x2a)[0x56221a03273a]

```

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

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

Title:
  Gimp Crashed

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

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

[Bug 1875733] [NEW] GNOME Software Installed List Missing Apps

[Adam Thomas]

Public bug reported:

Installed Ubuntu Studio 20.04LTS 4 days ago. GNOME Software's installed list is 
missing a lot of programs that I have installed.
For example, I have installed Clementine but it is missing from the installed 
list. However, when I search for Clementine in Software it does identify it as 
being installed, but it (as well as a lot of other programs) are missing from 
the installed list in GNOME Software.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-software 3.36.0-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-26.30-lowlatency 5.4.30
Uname: Linux 5.4.0-26-lowlatency x86_64
NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice 
talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Tue Apr 28 20:14:43 2020
InstallationDate: Installed on 2020-04-24 (4 days ago)
InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
InstalledPlugins:
 gnome-software-plugin-flatpak 3.36.0-0ubuntu3
 gnome-software-plugin-snap3.36.0-0ubuntu3
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  GNOME Software Installed List Missing Apps

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

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

[Bug 1875056] Re: locate-pointer (w/ ctrl key) not working

[Thomas]

It works on first attempt, then OFF and ON and it stops:

Mon 27 Apr 15:29:58 CEST 2020


** Attachment added: "locate-pointer-journalctl.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1875056/+attachment/5361658/+files/locate-pointer-journalctl.txt

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

Title:
  locate-pointer (w/ ctrl key) not working

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

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

[Bug 1857383] Re: Fractional scaling does not work anymore

[Thomas Clark]

Hi Simone

I have also suffered from the bug that you mention in the past before
suffering from this bug, bug 1870736 and bug 1873403 currently. I might
be wrong, but I think that the bug that you mention might be covered by
bug 1874559.

Kind Regards

Thomas

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

Title:
  Fractional scaling does not work anymore

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

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

[Bug 1875056] Re: locate-pointer (w/ ctrl key) not working

[Thomas]

It then stops and cannot be re-activated after reboot.

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

Title:
  locate-pointer (w/ ctrl key) not working

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

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

[Bug 1875056] Re: locate-pointer (w/ ctrl key) not working

[Thomas]

The setting, see attached, has not effect.

** Description changed:

- It was working for an hour and the stopped.
+ It was working for an hour and then stopped.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.36.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 25 19:09:37 2020
  InstallationDate: Installed on 2020-03-31 (25 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  locate-pointer (w/ ctrl key) not working

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

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