from:"christian"

Found the cause:

gsd-rfkill[2049]: Could not open rfkill device: Could not open RFKILL
control device, please verify your installation

GNOME's BT GUI needs access to /dev/rfkill to work. It's tagged
"uaccess" in udev, so in theory all logged-in users should get access
via an ACL, but in practice this doesn't seem to work for seats other
than seat0 in a multiseat scenario.

Removing the "seat" tag and re-adding the "shared" tag via custom udev
rule doesn't help--the acl doesn't get added if you don't login on
seat0.

Of course simply changing the permissions to 666 does the trick until
the next reboot, but ...

So, not a gnome-bluetooth* bug, nor a gnome-control-center one, but
whose is it? Logind? /dev/rfkill should be available to all users logged
in locally, IMHO.

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

Title:
  no adapter found on second seat [loginctl multiseat]

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


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

[Bug 2033324] [NEW] no adapter found on second seat [loginctl multiseat]

Public bug reported:

I've set up a second seat via loginctl --attach, resulting in the
following udev rules:

TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_6e_00_0", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="input-pci-_6c_00_0-usb-0_11_1_0", 
ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="sound-pci-_6e_00_1", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="usb-pci-_6e_00_3-usb-0_1", 
ENV{ID_SEAT}="seat1"

(Since loginctl doesn't consider BT adapters per-seat--they don't show
up in loginctl seat-status at all--adding an extra one and assigning it
to seat1 does accomplish nothing.)

However, when logged in on seat1 the GNOME BT settings panel insists
there's no BT adapter attached.

Funnily enough
- the top-right drop-down menu shows (some?) connected devices
- opening the BT settings panel triggers something alright (as seen in 
bluetoothctl)

If a BT adapter is not a per-seat resource then I'd expect it to be
configurable by (authorised) users no matter what seat they log in on.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-bluetooth 3.34.5-8
Uname: Linux 6.4.12-060412-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Aug 29 00:22:00 2023
InstallationDate: Installed on 2023-08-25 (3 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
SourcePackage: gnome-bluetooth
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  no adapter found on second seat [loginctl multiseat]

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


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

[Bug 2033323] [NEW] will only come up on second seat once [loginctl multiseat]

Public bug reported:

I've set up a second seat via loginctl --attach, resulting in the
following udev rules:

TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_6e_00_0", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="input-pci-_6c_00_0-usb-0_11_1_0", 
ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="sound-pci-_6e_00_1", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="usb-pci-_6e_00_3-usb-0_1", 
ENV{ID_SEAT}="seat1"

Because of #2033322, WaylandEnable=false is set in
/etc/gdm3/custom.conf.

It works great--except it does so only once. I can login on seat1 just fine, 
except when I log out, the greeter doesn't come back up again, it just leaves 
me with a black screen. 
Can be recovered from by restarting gdm (via ssh from another box or from 
seat0), but obviously that isn't ideal.

I've attached a pstree for the working case (no GUI logins, both
greeters up) and the non-working post-logout one (no GUI logins, only
seat0 hat a greeter up); please advise re. what logs to provide.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu7.22.04.3
Uname: Linux 6.4.12-060412-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Aug 29 00:02:03 2023
InstallationDate: Installed on 2023-08-25 (3 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2023-08-28T23:54:05.623349

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


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

** Attachment added: "output of pstree for the working and nonworking case"
   https://bugs.launchpad.net/bugs/2033323/+attachment/5695783/+files/pstree.tgz

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

Title:
  will only come up on second seat once [loginctl multiseat]

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


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

[Bug 2033322] [NEW] multiseat (via loginctl) will not work unless Wayland is disabled

Public bug reported:

When a second seat is set up via loginctl --attach, the greeter will not
come up on the second screen unless WaylandEnable=false is set in
/etc/gdm3/custom.conf (and gdm restarted).

For completeness' sake, the udev rules set up by loginctl are:

TAG=="seat", ENV{ID_FOR_SEAT}=="drm-pci-_6e_00_0", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="input-pci-_6c_00_0-usb-0_11_1_0", 
ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="sound-pci-_6e_00_1", ENV{ID_SEAT}="seat1"
TAG=="seat", ENV{ID_FOR_SEAT}=="usb-pci-_6e_00_3-usb-0_1", 
ENV{ID_SEAT}="seat1"

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu7.22.04.3
Uname: Linux 6.4.12-060412-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Aug 28 23:54:57 2023
InstallationDate: Installed on 2023-08-25 (3 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2023-08-28T23:54:05.623349

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


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

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

Title:
  multiseat (via loginctl) will not work unless Wayland is disabled

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


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

[Bug 2030963] [NEW] default theme highlights hard to see

2023-08-10 Thread Christian Pernegger

Public bug reported:

In 22.04's default theme, it's almost impossible for me to make out
which app or window is the currently selected one in the window switcher
(alt-tab) or the application switcher (super-tab). The "highlighted"
item is just a slightly different shade of grey. I mean, I can make it
out if I squint at it, but ... that just isn't a *highlight*. This is a
use where Ubuntu Orange shines, too. :-(

Similarly, the active workspace in the workspace overview (?) does get
an orange frame, but it's very thin, much too thin to see unless you
look closely. Again, that's not a highlight. A highlight is supposed to
pop out.

In comparison, the highlighting for the current tab in Terminal is ok-
ish. I'd *prefer* for the entire tab to become orange, or to become a
lighter colour in addition to the orange bar, but it's usable.

"Ok, boomer, you're blind. I can see that just fine". Fair enough. Are
you under thirty and (thus still) have 20:20 vision, by any chance? The
point is, it isn't good UI design either way. What's worse, the high
contrast accessibility setting doesn't touch any of it, and that is
definitely a bug.

(I could go on. For example, windows' title bars are now white vs the iconic 
Ubuntu Brown, which makes it hard to tell where the title bar is vs the window 
contents. Many applications also have buttons in the title bar now. It's no 
longer possible to just grab a window and move it on auto-pilot ... If the 
title bar can't be a different colour any more, at least separate it with a 
thick line or something.
In any case, 22.04 is a massive regression in terms of visual UI design vs 
18.04. Form should follow function, not the other way around.)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.9-0ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-1009.9~22.04.1-lowlatency 6.2.13
Uname: Linux 6.2.0-1009-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 10 12:58:31 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-08-02 (7 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
RelatedPackageVersions: mutter-common 42.9-0ubuntu4
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  default theme highlights hard to see

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


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

[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

If it would be an MP I'd set it to needs-information, but this is a debdiff in 
a bug.
I hope my questions and confusion was clear so that you can iterate and clarify.

I'll remove ubuntu-sponsors which I'll ask you to add back once this is
ready for review again.

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

Title:
  gvfsd process does not have the KRB5CCNAME environment set

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


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

[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

Then the most recent applied patch says:
...
Since this is a helper service that is meant to be controlled by
"tracker-miner-fs", the install section shouldn't exist, as it allows
the service to enabled, meaning that its execution would be
controlled by systemd.

But I can't see where/how:

root@m:~# grep -Hn -- tracker-extract $(dpkg -L tracker-miner-fs| xargs)
2>/dev/null | grep -v copyright

Would you mind clarifying that interaction on your update.
Because without I'm afraid more will be confused :-/

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

Title:
  gvfsd process does not have the KRB5CCNAME environment set

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


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

[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

Some things just do not fit together.
You write
"... to update from default.target.wants to gnome-session.target.wants. ..."
But while 3.4.3-1ubuntu1 does:
+ [Install]
+-WantedBy=default.target
++WantedBy=gnome-session.target

Then later 3.4.3-1ubuntu2 does
+-[Install]
+-WantedBy=default.target
++# This is a helper service that is controlled by "tracker-miner-fs-3.service".
++# It's not supposed to be enabled or started manually.

So the changelog and intent doesn't match.
Is it just the changelog that got confused or is there more that needs to be 
clarified and corrected?

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

Title:
  gvfsd process does not have the KRB5CCNAME environment set

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


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

[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

This is now the third revision of the change (3.4.3-1ubuntu1 + 3.4.3-1ubuntu2 + 
this) and by identifying that this also needs to go to -devel I wonder if you 
should not also use the chance to submit the outstanding Delta to Debian. That 
will help them directly and mid-term ease maintenance.
3.4.3-1ubuntu2 said "Cherry-pick patch ..." but didn't mention from where - 
will this be in next upstream and that way come to Debian?
If so, you might still help by reminding them to use the purge mechanism to get 
rid of the old on-disk config.

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

Title:
  gvfsd process does not have the KRB5CCNAME environment set

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


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

[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

I can see why you do the purge forgetting the old state to enable them as if 
they were freshly installed.
I'm not sure how SRUable that will be afterwards as it is affecting behavior if 
someone has set something else than the default. But for now, going forward to 
mantic I agree that it will help to get an upgrading system out of the old 
wrong dependencies.

Given that this isn't meant to be enabled automatically (thanks for the
explanation in the last patch) that should be ok'ish.

You do this change even to people which installed 3.4.3-1ubuntu2 as the
first (which was correct). But I think adding more code to detect that
rare case won't help many real cases.

Since this is juts for mantic for now, that is fine.
But double think about it on SRU time.

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

Title:
  gvfsd process does not have the KRB5CCNAME environment set

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


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

[Bug 1779890] Re: gvfsd process does not have the KRB5CCNAME environment set

Thanks for the clarification Matthew and Heitor - first I'll re-set the state 
of the devel release then.
As it isn't completely fixed there.

** Changed in: tracker-miners (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: tracker-miners (Ubuntu Lunar)
   Status: Fix Released => Confirmed

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

Title:
  gvfsd process does not have the KRB5CCNAME environment set

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


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

[Bug 1812456] Re: [MIR] libflatpak0

2023-06-13 Thread Christian Ehrhardt 

There has been not further update for too long, for now we consider it invalid.
Feel free to re-open if there is effort backing it up and motivation to bring 
it to main.

** Changed in: flatpak (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [MIR] libflatpak0

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


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

[Bug 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.

2023-03-20 Thread Christian Ehrhardt 

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

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

Title:
  Window actions (like maximize) no more work in wayland for QEMU using
  GTK backend once the guest UI is intialized.

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


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

[Bug 1982584] Re: wacom invisible cursor on startup, xorg 22.04

2022-10-30 Thread Christian

I have the same problem - any ongoing solutions ?

You can override the problem with a second plugged mouse too, if you
move it only one pixel at after startup the mousepointer appears and
stay until shutdown.

Maybe the problem is to initialise the pointer when using wacom ?

The Wacom pointer is working but you can't see it, unless you bring the
pointer to be visible by override it by another device.

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

Title:
  wacom invisible cursor on startup, xorg 22.04

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


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

[Bug 422012] Re: Emptying the trash can lead to have files still on disk in expunged

2022-10-23 Thread Christian Lampe

Same behaviour on Ubuntu 22.04.1 LTS with nemo 5.2.4-1 ... 
The files seem to be moved there if you delete a directory of yours with files 
from other users in it from the trash. 

Proposal for behaviour changes:
1. Not create and use the "expunged" folder at all and just fail to delete 
other users' files from your own trash.
2. Continue to use the "expunged" folder but warn the user when and why and 
which files are being moved there (and maybe even continuing to show them in 
"trash:///").

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

Title:
  Emptying the trash can lead to have files still on disk in expunged

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


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

[Bug 1991474] [NEW] GIMP 2.99 crashes on file load

2022-10-02 Thread Christian Brickhouse

Public bug reported:




```
GNU Image Manipulation Program version 2.99.12
git-describe: GIMP_2_99_12
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=/usr/bin/cc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/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 
11.3.0-1ubuntu1~22.04' --with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-11 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--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-11-xKiWfi/gcc-11-11.3.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-xKiWfi/gcc-11-11.3.0/debian/tmp-gcn/usr
 --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu 
--with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04) 

# Libraries #
using babl version 0.1.96 (compiled against version 0.1.96)
using GEGL version 0.4.38 (compiled against version 0.4.38)
using GLib version 2.72.1 (compiled against version 2.72.1)
using GdkPixbuf version 2.42.8 (compiled against version 2.42.8)
using GTK+ version 3.24.33 (compiled against version 3.24.33)
using Pango version 1.50.6 (compiled against version 1.50.6)
using Fontconfig version 2.13.1 (compiled against version 2.13.1)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Aborted

Stack trace:
```

# Stack traces obtained from PID 16762 - Thread 16762 #

[New LWP 16763]
[New LWP 16764]
[New LWP 16765]
[New LWP 16766]
[New LWP 16767]
[New LWP 16768]
[New LWP 16769]
[New LWP 16770]
[New LWP 16771]
[New LWP 16772]
[New LWP 16773]
[New LWP 16774]
[New LWP 16775]
[New LWP 16776]
[New LWP 16777]
[New LWP 16778]
[New LWP 16779]
[New LWP 16781]
[New LWP 16785]
[New LWP 16786]
[New LWP 16787]
[New LWP 16788]
[New LWP 16789]
[New LWP 16790]
[New LWP 16791]
[New LWP 16792]
[New LWP 16793]
[New LWP 16794]
[New LWP 16795]
[New LWP 16796]
[New LWP 16797]
[New LWP 16798]
[New LWP 16799]
[New LWP 16800]
[New LWP 16801]
[New LWP 30730]
[New LWP 30736]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7ff24be549cc in read () from /lib/x86_64-linux-gnu/libc.so.6
  Id   Target IdFrame 
* 1Thread 0x7ff248503f40 (LWP 16762) "gimp" 0x7ff24be549cc in 
read () from /lib/x86_64-linux-gnu/libc.so.6
  2Thread 0x7ff247f15640 (LWP 16763) "gmain"0x7ff24be58d7f in 
poll () from /lib/x86_64-linux-gnu/libc.so.6
  3Thread 0x7ff247714640 (LWP 16764) "gdbus"0x7ff24be58d7f in 
poll () from /lib/x86_64-linux-gnu/libc.so.6
  4Thread 0x7ff246bd9640 (LWP 16765) "worker"   0x7ff24be5ea3d in 
syscall () from /lib/x86_64-linux-gnu/libc.so.6
  5Thread 0x7ff2463d8640 (LWP 16766) "worker"   0x7ff24be5ea3d in 
syscall () from /lib/x86_64-linux-gnu/libc.so.6
  6Thread 0x7ff245bd7640 (LWP 16767) "worker"   0x7ff24be5ea3d in 
syscall () from /lib/x86_64-linux-gnu/libc.so.6
  7Thread 0x7ff2453d6640 (LWP 16768) "worker"   0x7ff24be5ea3d in 
syscall () from /lib/x86_64-linux-gnu/libc.so.6
  8Thread 0x7ff244bd5640 (LWP 16769) "worker"   0x7ff24be5ea3d in 
syscall () from /lib/x86_64-linux-gnu/libc.so.6
  9Thread 0x7ff237fff640 (LWP 16770) "worker"   0x7ff24be5ea3d in 
syscall () from /lib/x86_64-linux-gnu/libc.so.6
  10   Thread 0x7ff2377fe640 (LWP 16771) "worker"   0x7ff24be5ea3d in 
syscall () from /lib/x86_64-linux-gnu/libc.so.6
  11   Thread 0x7ff236ffd640 (LWP 16772) "worker"   0x7ff24be5ea3d in 
syscall () from /lib/x86_64-linux-gnu/libc.so.6
  12   Thread 0x7ff2367fc640 (LWP 16773) "worker"   0x7ff24be5ea3d in 
syscall () from /lib/x86_64-linux-gnu/libc.so.6
  13   Thread 0x7ff235ffb640 (LWP 16774) "worker"   0x7ff24be5ea3d in 
syscall () from /lib/x86_64-linux-gnu/libc.so.6
  14   Thread 0x7ff2357fa640 (LWP 16775) "worker"   0x7ff24be5ea3d in 
syscall () from /lib/x86_64-linux-gnu/libc.so.6

[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched

2022-06-14 Thread Christian Sarrasin

@ausbin: `aa-complain` is hardly a "fix": it bypasses AppArmor, which is
not optimal, knowing how PDF documents are often used as a malware
vector.  Admittedly, malware is less likely to be targeted at Linux
desktops but still...

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

Title:
  Evince Document Viewer(42.0) does not remember last page in 22.04 and
  opens in a tiny window when launched

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


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

[Bug 1892456] Re: [MIR] malcontent

2022-06-07 Thread Christian Ehrhardt 

AFAIU https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1812456
needs to be completed to unblock this one here as well.

There is a discussion between Security and others - but that seems stalled for 
almost a year now.
Maybe worth to ping there (or the involved people) to get it back on track?

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

Title:
  [MIR] malcontent

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


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

[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04

2022-05-08 Thread Christian Sarrasin

Running APT evince 42.1-3 on stock Ubuntu 22.04/GNOME 42.0/Wayland.

My issue is Evince opening in a tiny window every time it's fired off;
this deployment was upgraded from 21.10, which didn't suffer from such
issue.

I attach below the output from `journalctl -f` while starting up Evince,
which clearly shows AppArmor violations.

I thus attempted the approach from https://askubuntu.com/a/886011/145568
.  When running with `aa-complain evince`, Evince behaves properly; I
accepted `aa-logprof`'s suggestion to grant /usr/bin/evince [owner
/run/user/1000/at-spi/bus rw,].  Unfortunately as soon as I reinstate
`aa-enforce evince`, the tiny window issue re-appears.

(Note: at first I Ignored /usr/sbin/cups-browsed [capability sys_nice,]
because I thought it was unrelated; I tried to grant it but this still
doesn't solve the issue).

** Attachment added: "Evince 42.1-3 AppArmor debugging.txt"
   
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+attachment/5587685/+files/Evince%2042.1-3%20AppArmor%20debugging.txt

** Summary changed:

- Evince Document Viewer(42.0) does not remember last page in 22.04
+ Evince Document Viewer(42.0) does not remember last page in 22.04 and opens 
in a tiny window when launched

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

Title:
  Evince Document Viewer(42.0) does not remember last page in 22.04 and
  opens in a tiny window when launched

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


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

[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04

2022-05-08 Thread Christian Sarrasin

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

Title:
  Evince Document Viewer(42.0) does not remember last page in 22.04 and
  opens in a tiny window when launched

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


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

[Bug 1972004] [NEW] Dock follows primary display scaling for all displays

2022-05-06 Thread Christian

Public bug reported:

This bug seems like #1826543, but I fled a new one because it is a
regression from 21.10.

While writing this, I also noticed that other elements only follow the
primary display scaling, like the numbers on the top left that say which
display is which, and the pop-up that asks whether I want to keep the
new display settings, so I might have filed this bug in the wrong
package.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5
ProcVersionSignature: Ubuntu 5.15.0-29.30-generic 5.15.35
Uname: Linux 5.15.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri May  6 13:21:52 2022
InstallationDate: Installed on 2021-09-13 (235 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210912)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-shell-extension-ubuntu-dock
UpgradeStatus: Upgraded to jammy on 2022-03-31 (35 days ago)

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


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

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

Title:
  Dock follows primary display scaling for all displays

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


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

[Bug 1969651] [NEW] Dock auto-hides too quickly when interacting with an app's right-click menu

2022-04-20 Thread Christian

Public bug reported:

Whenever I try to select a different window from the dock (or add to
favourites/any other option in that menu), as soon as my mouse leaves
the dock for that menu, the dock hides, which makes the menu drop down.
This is very frustrating because at best I have to try again, and at
worst I have to undo whatever wrong action the menu drop made me click.

It's worse when the menu is not on my primary display, as on top of
dropping down, it gets sent to the primary display.

This is quite a frustrating bug that has been present the whole time
I've been using the 22.04 beta.

My gnome-shell-extension-ubuntu-dock version is 72-ubuntu5, and I am
using Wayland.

My dock settings are set to show on all displays, at the bottom.
Although the behaviour is wonky when set to display on the left too.

Let me know if there is any more information you would like me to
provide.

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

** Description changed:

  Whenever I try to select a different window from the dock (or add to
  favourites/any other option in that menu), as soon as my mouse leaves
  the dock for that menu, the dock hides, which makes the menu drop down.
  This is very frustrating because at best I have to try again, and at
  worst I have to undo whatever wrong action the menu drop made me click.
  
  It's worse when the menu is not on my primary display, as on top of
  dropping down, it gets sent to the primary display.
  
  This is quite a frustrating bug that has been present the whole time
  I've been using the 22.04 beta.
  
  My gnome-shell-extension-ubuntu-dock version is 72-ubuntu5, and I am
  using Wayland.
  
+ My dock settings are set to show on all displays, at the bottom.
+ Although the behaviour is wonky when set to display on the left too.
+ 
  Let me know if there is any more information you would like me to
  provide.

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

Title:
  Dock auto-hides too quickly when interacting with an app's right-click
  menu

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


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

[Bug 1964600] Re: [MIR] gnome-bluetooth3

2022-04-13 Thread Christian Ehrhardt 

Ok, it is there now:
https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html


gnome-bluetooth3: gir1.2-gnomebluetooth-3.0 gnome-bluetooth-3-common 
libgnome-bluetooth-3.0-13 libgnome-bluetooth-3.0-dev libgnome-bluetooth-doc 
libgnome-bluetooth-ui-3.0-13 libgnome-bluetooth-ui-3.0-dev

[Reverse-Depends: Rescued from gnome-bluetooth3 (Uploader: jbicha),
gir1.2-gnomebluetooth-3.0, gnome-shell (Uploader: 3v1n0) (MAIN),
libgnome-bluetooth-3.0-13, libgnome-bluetooth-ui-3.0-dev]

All Acks are present, no further dependencies, subscription present.
Resolving this to get migrations done and have less noise left towards the 
release week.

Override component to main
gnome-bluetooth3 42.0-5 in jammy: universe/misc -> main
gir1.2-gnomebluetooth-3.0 42.0-5 in jammy amd64: 
universe/introspection/optional/100% -> main
gir1.2-gnomebluetooth-3.0 42.0-5 in jammy arm64: 
universe/introspection/optional/100% -> main
gir1.2-gnomebluetooth-3.0 42.0-5 in jammy armhf: 
universe/introspection/optional/100% -> main
gir1.2-gnomebluetooth-3.0 42.0-5 in jammy ppc64el: 
universe/introspection/optional/100% -> main
gir1.2-gnomebluetooth-3.0 42.0-5 in jammy riscv64: 
universe/introspection/optional/100% -> main
gir1.2-gnomebluetooth-3.0 42.0-5 in jammy s390x: 
universe/introspection/optional/100% -> main
gnome-bluetooth-3-common 42.0-5 in jammy amd64: universe/gnome/optional/100% -> 
main
gnome-bluetooth-3-common 42.0-5 in jammy arm64: universe/gnome/optional/100% -> 
main
gnome-bluetooth-3-common 42.0-5 in jammy armhf: universe/gnome/optional/100% -> 
main
gnome-bluetooth-3-common 42.0-5 in jammy i386: universe/gnome/optional/100% -> 
main
gnome-bluetooth-3-common 42.0-5 in jammy ppc64el: universe/gnome/optional/100% 
-> main
gnome-bluetooth-3-common 42.0-5 in jammy riscv64: universe/gnome/optional/100% 
-> main
gnome-bluetooth-3-common 42.0-5 in jammy s390x: universe/gnome/optional/100% -> 
main
libgnome-bluetooth-3.0-13 42.0-5 in jammy amd64: universe/libs/optional/100% -> 
main
libgnome-bluetooth-3.0-13 42.0-5 in jammy arm64: universe/libs/optional/100% -> 
main
libgnome-bluetooth-3.0-13 42.0-5 in jammy armhf: universe/libs/optional/100% -> 
main
libgnome-bluetooth-3.0-13 42.0-5 in jammy ppc64el: universe/libs/optional/100% 
-> main
libgnome-bluetooth-3.0-13 42.0-5 in jammy riscv64: universe/libs/optional/100% 
-> main
libgnome-bluetooth-3.0-13 42.0-5 in jammy s390x: universe/libs/optional/100% -> 
main
libgnome-bluetooth-3.0-dev 42.0-5 in jammy amd64: 
universe/libdevel/optional/100% -> main
libgnome-bluetooth-3.0-dev 42.0-5 in jammy arm64: 
universe/libdevel/optional/100% -> main
libgnome-bluetooth-3.0-dev 42.0-5 in jammy armhf: 
universe/libdevel/optional/100% -> main
libgnome-bluetooth-3.0-dev 42.0-5 in jammy ppc64el: 
universe/libdevel/optional/100% -> main
libgnome-bluetooth-3.0-dev 42.0-5 in jammy riscv64: 
universe/libdevel/optional/100% -> main
libgnome-bluetooth-3.0-dev 42.0-5 in jammy s390x: 
universe/libdevel/optional/100% -> main
libgnome-bluetooth-doc 42.0-5 in jammy amd64: universe/doc/optional/100% -> main
libgnome-bluetooth-doc 42.0-5 in jammy arm64: universe/doc/optional/100% -> main
libgnome-bluetooth-doc 42.0-5 in jammy armhf: universe/doc/optional/100% -> main
libgnome-bluetooth-doc 42.0-5 in jammy i386: universe/doc/optional/100% -> main
libgnome-bluetooth-doc 42.0-5 in jammy ppc64el: universe/doc/optional/100% -> 
main
libgnome-bluetooth-doc 42.0-5 in jammy riscv64: universe/doc/optional/100% -> 
main
libgnome-bluetooth-doc 42.0-5 in jammy s390x: universe/doc/optional/100% -> main
libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy amd64: universe/libs/optional/100% 
-> main
libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy arm64: universe/libs/optional/100% 
-> main
libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy armhf: universe/libs/optional/100% 
-> main
libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy ppc64el: 
universe/libs/optional/100% -> main
libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy riscv64: 
universe/libs/optional/100% -> main
libgnome-bluetooth-ui-3.0-13 42.0-5 in jammy s390x: universe/libs/optional/100% 
-> main
libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy amd64: 
universe/libdevel/optional/100% -> main
libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy arm64: 
universe/libdevel/optional/100% -> main
libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy armhf: 
universe/libdevel/optional/100% -> main
libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy ppc64el: 
universe/libdevel/optional/100% -> main
libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy riscv64: 
universe/libdevel/optional/100% -> main
libgnome-bluetooth-ui-3.0-dev 42.0-5 in jammy s390x: 
universe/libdevel/optional/100% -> main
Override [y|N]? y
45 publications overridden.

** Changed in: gnome-bluetooth3 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:

[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2022-03-29 Thread Christian Ehrhardt 

I can't test this reliably (as stated in the SRU description), but at
least I can say I haven't seen it in the last 24h :-) I think this is on
@gjolly to try to reproduce it in the mentioned azure test environment.

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

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


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

[Bug 1866999] Re: gnome-calendar does not sync with Google Calendar

2022-02-08 Thread Christian Weiske

I'm on Ubuntu 20.04 with gnome-calendar 3.36.2 and have the same problem: 
Google calendar did not sync.
Then I removed the cache in "~/.cache/evolution/calendar/", and gnome calendar 
showed no appointments at all (as expected).

Clicking the "sync now" menu item changed the calendar icon briefly to a
checkmark, but "journalctrl -f" said:

> Feb 08 13:28:20 sybo gnome-calendar[17021]: Error synchronizing client
> Feb 08 13:28:20 sybo gnome-calendar[17021]: Error synchronizing client
> Feb 08 13:28:20 sybo gnome-calendar[17021]: Error synchronizing client

for every calendar, enabled or not.

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

Title:
  gnome-calendar does not sync with Google Calendar

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


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

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

2022-02-08 Thread Christian Ehrhardt 

FYI the re-upload of a fuse3 open-vm-tools happened yesterday and it migrated 
to jammy-release.
Any issues with the images?

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

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

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


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

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

2022-02-01 Thread Christian Ehrhardt 

@aakef - while I said unionfs-fuse might not be a blocker I'd still
recommend to upload the change switching to fuse3. On comment #12 it
seemed you are close. Any chance to get this done or did unexpected
blockers show up while trying?

The unionfs-fuse task here is assigned to Graham; @ginggs - did you make
any progress on that yourself or together with Bernd?

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

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

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


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

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

2022-02-01 Thread Christian Ehrhardt 

FYI according to
https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/ALL/fuse
https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.jammy/rdepends/ALL/fuse3

This should no more be an issue now, so open-vm-tools will switch to
fuse3 again in the next few days. This is a heads up in case it breaks
again some way.

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

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

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


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

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

Hi Bernd,
I'm glad to heard that as we were not sure it would work well with fuse3.
As a reminder, the libs are co-installable it is "bin:fuse" vs "bin:fuse3" that 
are conflicting.
So when you change that remember to also change fuse->fuse3.

In the meantime it was found that unionfs-fuse isn't seeded (anymore) -
it is only a comment in the Ubuntu seeds nowadays. So it will be great
to move it to fuse3, but not resolve the issue discussed here. That must
have been due to one of the other dependencies in the image.

Anyone looking at this - please coordinate with ginggs, trevinho, paride
on #ubuntu-devel for the timing of related Ubuntu uploads if they are
seeded (or even in general).

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

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

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


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

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

FYI - I uploaded a revert to the open-vm-tools change to un-block image builds 
for now.
But maybe this was a good wake-up call.
Please have a look at gvfs, union-fuse (here) and grub2, s390-tools, snapd, 
xdg-desktop-portal in bug 1934510.

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

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

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


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

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

@Marco Trevisan - I subscribed you in case you want to steal the Desktop
POV to this from Didier.

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

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

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


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

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

Also see
https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/1934510/comments/24

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

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

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


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

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

#1 - Package: gvfs-fuse
This build for Desktop already switched to the version3 as you see in 
"libfuse3-3 (>= 3.2.3)".
But it still depends on the v2 user-tools. That mismatch needs to be resolved 
for 22.04 and it will need to switch to fuse3.
I'm adding a src:gvfs task for that to switch to fuse3 (assigning to Didier, 
please reassign in *Desktop accordingly)

#2
Package: unionfs-fuse
This wasn't yet tried with fuse3 AFAIC as it was missed on the initial analysis 
for bug 1934510.
I'll add a bug task for it here and ping bug 1934510 about it.
We will have to move this to fuse3 as well, and the others of the formerly 
identified packages.
I'll assign that to Ginggs as he has taken the initial archive wide check, 
maybe Foundations has this and more prepared to have all of them move at once.


If it turns out that not all are ready yet, then we need to tune back 
open-vm-tools "for now" until they are ready. Therefore I'll add an 
open-vm-tools tasks assigned to myself, but set to incomplete until we know 
from the others if everything could move now or if we have to wait.


P.S. There might be others like grub, s390x-tools, ... (see initial mail I 
linked above) which might trigger the same issue for this or other images, see 
bug 1934510 and the links from there.

** Also affects: gvfs (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: unionfs-fuse (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: open-vm-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: open-vm-tools (Ubuntu)
   Status: New => Incomplete

** Changed in: gvfs (Ubuntu)
 Assignee: (unassigned) => Didier Roche (didrocks)

** Changed in: unionfs-fuse (Ubuntu)
 Assignee: (unassigned) => Graham Inggs (ginggs)

** Changed in: open-vm-tools (Ubuntu)
 Assignee: (unassigned) => Christian Ehrhardt  (paelzer)

-- 
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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2021-11-17 Thread Christian Ehrhardt 

FYI triggered again for me due to unattended upgrades.
The time in the journal when things go down matches the 
unpack/configuee/install phase of
- accountsservice:amd64 0.6.55-0ubuntu12~20.04.5
- libaccountsservice0:amd64 0.6.55-0ubuntu12~20.04.5
- dbus:amd64 1.12.16-2ubuntu2.1

I - again - had the usual suspect entries:

systemd[1]: Starting Daily apt upgrade and clean activities...
dbus-daemon[2266]: [system] Reloaded configuration
dbus-daemon[2266]: Unknown group "power" in message bus configuration file
systemd[1]: Reloading.
systemd[1]: NetworkManager.service: Unexpected error response from 
GetNameOwner(): Connection terminated

I didn't see anything in the log we didn't have before, but for
completeness I'm attaching journal of the issue and a few hours before
it

** Attachment added: "journal entries around the issues happening on 
unattended-upgrades"
   
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+attachment/5541619/+files/fail-18Nov-6-24-07.log

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

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


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

[Bug 1947706] [NEW] gnome crash after power save and display turn on

2021-10-19 Thread christian

Public bug reported:

Hi

My desktop crashed and sent me back to login page. After input my
password display switched black again and then showed login screen. Just
reboot fixed my problem.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 19 11:46:44 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-11-27 (325 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  gnome crash after power save and display turn on

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


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

[Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)

2021-10-13 Thread Christian Ehrhardt 

As outlined in #55 unless we identify a smaller set of fixes I'm unsure
what we could do for Focal.

I'm out of ideas, the only one good thing is that it seems better in
later versions and got more rare. But I hate when I do not understand
all of a problem, here I might need help from Desktop-oriented thinking
- hence I'll subscribe the desktop team if they might know better.

** Changed in: spice-protocol (Ubuntu Focal)
   Status: Triaged => Won't Fix

** Changed in: spice-gtk (Ubuntu Focal)
   Status: Triaged => Won't Fix

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

Title:
  Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM
  guests)

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


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

[Bug 1931225] Re: 0.9.15 is FTFBS on ppc64el and s390x

2021-10-04 Thread Christian Ehrhardt 

Mitigated in impish Steve via
https://launchpad.net/ubuntu/+source/xrdp/0.9.15-1ubuntu1

** Changed in: xrdp (Ubuntu)
   Status: New => Fix Released

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

Title:
  0.9.15 is FTFBS on ppc64el and s390x

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


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

[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

2021-06-08 Thread Christian Ehrhardt 

Also blocking isc-dhcp now, added a task

** Also affects: isc-dhcp (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Incomplete

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

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

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

[Bug 1931225] [NEW] 0.9.15 is FTFBS on ppc64el and s390x

2021-06-08 Thread Christian Ehrhardt 

Public bug reported:

Hi,
as seen in
https://launchpadlibrarian.net/536144995/buildlog_ubuntu-impish-ppc64el.xrdp_0.9.15-1_BUILDING.txt.gz
https://launchpadlibrarian.net/536175263/buildlog_ubuntu-impish-s390x.xrdp_0.9.15-1_BUILDING.txt.gz

This currently fails to build on ppc64el and s390x.

Upstream explcitly checks supported architectures now and only with the more 
recent 0.9.16 version
it got that support.

s390x:
https://github.com/neutrinolabs/xrdp/commit/1d1ec9614f84243e4a08256f82994278d082b592
ppc64el:
https://github.com/neutrinolabs/xrdp/commit/3b81df3f9e894dd164f86d8cf87c3a171ced6d08

IMHO we can just wait for 0.9.16, but this bug provides the start of any action 
if someone disagrees.
Further via update-excuse it makes it easily discovered from there avoiding to 
re-debugg it.

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

** Affects: xrdp (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: update-excuse

** Tags added: update-excuse

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

** Also affects: xrdp (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983843
   Importance: Unknown
   Status: Unknown

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

Title:
  0.9.15 is FTFBS on ppc64el and s390x

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

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

[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

2021-06-07 Thread Christian Ehrhardt 

As I said I tried to recreate this, but it worked.
It was fine under Focal/5.4.0-53-generic Host with the Impish-armhf container.
Upgrading the host to impish it Impish/5.11.0-16-generic still works fine.

It seems it only fails in autopkgtest infrastructure, not sure why yet
:-/

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

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

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

[Bug 1931088] [NEW] boot-and-services tests fails in impish on armhf (248.3)

2021-06-07 Thread Christian Ehrhardt 

Public bug reported:

Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
before now slipping into a bad mode.

Now it seems all tests failed in boot-and-services by hanging until killed by
VirtSubproc.Timeout of autokgtest.

The last [1] test log has a bit more, it shows a python stack overflow
```
   VirtSubproc.Timeout
   Fatal Python error: Cannot recover from stack overflow.
   Python runtime state: initialized

   Current thread 0x7f108e840740 (most recent call first):
 File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log
 File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug
 File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send
 File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command
```

I have seen a bunch of packages including even gdm3 and glibc being blocked by
that so I wanted to at least track down the issue until we can put it on
someones task list to resolve.
No one replied to my pings yet, but maybe that means someone is already
debugging this and had enabled some debugging?

By running the same in armhf container on arm64 VM on canonistack I've seen
no issues. The test worked fine and had no hang/issues.

root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services
lxc
1
test_profile (__main__.AppArmorTest)
AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352'
test_help (__main__.CLITest)
--help works and succeeds ... ok
test_invalid_option (__main__.CLITest)
Calling with invalid option fails ... ok
test_version (__main__.CLITest)
--version works and succeeds ... ok
test_cpushares (__main__.CgroupsTest)
service with CPUShares ... ok
test_simple (__main__.CgroupsTest)
simple service ... ok
test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does not 
work in containers'
test_log_for_service (__main__.JournalTest) ... ok
test_no_options (__main__.JournalTest) ... ok
test_boot (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
test_service (__main__.NspawnTest) ... skipped 'nspawn does not work in most 
containers'
test_failing (__main__.SeccompTest) ... ok
test_0_init (__main__.ServicesTest)
Verify that init is systemd ... ok
test_cron (__main__.ServicesTest) ... ok
test_dbus (__main__.ServicesTest) ... ok
test_gdm3 (__main__.ServicesTest) ... skipped 'gdm3 not found'
test_logind (__main__.ServicesTest) ... ok
test_network_manager (__main__.ServicesTest) ... ok
test_no_failed (__main__.ServicesTest)
No failed units ... ok
test_rsyslog (__main__.ServicesTest) ... ok
test_tmp_cleanup (__main__.ServicesTest) ... ok
test_tmp_mount (__main__.ServicesTest) ... ok
test_udev (__main__.ServicesTest) ... skipped 'udev does not work in containers'
--
Ran 23 tests in 5.589s
OK (skipped=6)

So I can not reproduce this on canonistack, but it blocks autopkgtests of
various packages pretty reproducibly :-/

[1]: https://autopkgtest.ubuntu.com/results/autopkgtest-
impish/impish/armhf/s/systemd/20210604_081326_d4319@/log.gz

** Affects: dnsmasq (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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

** Affects: glibc (Ubuntu)
 Importance: Undecided
 Status: Incomplete

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


** Tags: update-excuse

** Tags added: update-excuse

** Also affects: gdm3 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: glibc (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: dnsmasq (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: dnsmasq (Ubuntu)
   Status: New => Incomplete

** Changed in: gdm3 (Ubuntu)
   Status: New => Incomplete

** Changed in: glibc (Ubuntu)
   Status: New => Incomplete

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

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

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

[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

2021-06-07 Thread Christian Ehrhardt 

I was adding a few of the blocked packages as incomplete tasks to have
this bug update-excuse show up in excuses. Right now until we know
better I'd consider this a systemd issue.

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

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

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

[Bug 1926364] Re: interactive resizes window jumps out of screen

2021-05-04 Thread Christian Rauch

bug 1922034 is gnome-terminal specific. The upstream issue was
https://gitlab.gnome.org/GNOME/mutter/-/issues/1723.

But this bug is generic for any Wayland client. And it also has been
fixed in the 3.38 release.

Now, this very issue is tagged "fixed-in-3.36.8" which is not correct I think. 
At least for me, I still see this issue on the latest 3.36 release in the 
upstream branch "gnome-3-36".
Can someone confirm that this is resolved in 3.36.9? Otherwise, this issue 
should stay open.

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1723
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1723

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

Title:
  interactive resizes window jumps out of screen

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

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

[Bug 1888399] Re: After Update->20.04, Empathy/Salut stops working

2021-04-29 Thread Christian González

I don't know why exactly, but I t seems to work again after I installed
telepathy-salut_0.8.1-5ubuntu1_amd64.deb from xenial. This package does
not exist in 20.04?

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

Title:
  After Update->20.04, Empathy/Salut stops working

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

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

[Bug 1926088] Re: Appearance: Window colors selection does not work

2021-04-28 Thread Christian Weiske

Thank you for your help!

ubuntu-desktop was indeed not installed, probably because I removed one
of the dependent packages at one time because I did not want it.

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

Title:
  Appearance: Window colors selection does not work

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

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

[Bug 1926088] Re: Appearance: Window colors selection does not work

2021-04-28 Thread Christian Weiske

It does indeed!
I wonder why this was not installed automatically.

Also, the title bars of Firefox , Thunderbird and Slack (Electron
Desktop) are white when using the "Standard" colors, but text editor,
control center + terminal have dark title bars. But this is probably a
different issue.

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

Title:
  Appearance: Window colors selection does not work

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

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

[Bug 1926088] Re: Appearance: Window colors selection does not work

2021-04-28 Thread Christian Weiske

Clicking the themes in control center does change the gtk-theme setting.
It only does not modify anything layout-wise :)

$ dpkg -l | grep yaru
ii  yaru-theme-gnome-shell  20.04.10.1  all  Yaru GNOME Shell desktop theme 
from the Ubuntu Community


Original setting:
$ gsettings get org.gnome.desktop.interface gtk-theme
'Ambiance'

After clicking on light layout:
$ gsettings get org.gnome.desktop.interface gtk-theme
'Yaru-light'

After clicking on standard layout:
$ gsettings get org.gnome.desktop.interface gtk-theme
'Yaru'

After clicking on dark layout:
$ gsettings get org.gnome.desktop.interface gtk-theme
'Yaru-dark'

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

Title:
  Appearance: Window colors selection does not work

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

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

[Bug 1926364] [NEW] interactive resizes window jumps out of screen

2021-04-27 Thread Christian Rauch

Public bug reported:

Interactively resizing a Wayland window while it resizes itself results
in the window jumping out of the screen. This happens on GNOME Shell and
pure mutter on the 3.36 branch but has been resolved on newer versions
(3.37.1 onwards).

See https://gitlab.gnome.org/GNOME/mutter/-/issues/1700 for the mutter
upstream bug report.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libmutter-6-0 3.36.9-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-51.57~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 27 21:58:40 2021
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal package-from-proposed 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/1926364

Title:
  interactive resizes window jumps out of screen

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

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

[Bug 1926088] Re: Appearance: Window colors selection does not work

2021-04-27 Thread Christian Weiske

I did install Ubuntu 10.04 over ten years ago from a CD-Rom.
Maybe I once uninstalled the permanent dock, maybe it never was the in 16.04 or 
18.04.

I did install the dock, but that changes nothing in regard to my
problem.

Attached is the log file.

** Attachment added: "jourctrl -b 0 > log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1926088/+attachment/5492668/+files/log

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

Title:
  Appearance: Window colors selection does not work

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

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

[Bug 1919143] Re: SRU mutter to 3.36.9

2021-04-26 Thread Christian Rauch

I updated via focal-proposed to mutter and gnome-shell version 3.36.9
(3.36.9-0ubuntu0.20.04.1) but unfortunately my original issue reported
at https://gitlab.gnome.org/GNOME/mutter/-/issues/1700 still persists.

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1700
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1700

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

Title:
  SRU mutter to 3.36.9

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

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

[Bug 1926088] Re: Appearance: Window colors selection does not work

2021-04-26 Thread Christian Weiske

I'm using the official Gnome Shell packages. I don't know if it has a
dock; but the left-side menu with the favorite applications is visible
when clicking the top left "application" button.

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

Title:
  Appearance: Window colors selection does not work

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

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

[Bug 1926088] Re: Appearance: Window colors selection does not work

2021-04-26 Thread Christian Weiske

Apart from one line there seem to be no relevant log lines:

> No Ubuntu Dock is installed here. Panel disabled. Please fix your
installation.

** Attachment added: "journalctl-appearance.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1926088/+attachment/5492474/+files/journalctl-appearance.log

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

Title:
  Appearance: Window colors selection does not work

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

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

[Bug 1888399] Re: After Update->20.04, Empathy/Salut stops working

2021-04-26 Thread Christian González

Ping - how can I help track down this problem? I need telepathy-salut to
work. This package seems to have been removed - but is replaced with
what?

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

Title:
  After Update->20.04, Empathy/Salut stops working

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

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

[Bug 1926088] [NEW] Appearance: Window colors selection does not work

2021-04-25 Thread Christian Weiske

Public bug reported:

When clicking on one of the "window colors" (Light, Standard, Dark) in
the Appearance section of gnome control center, nothing changes.

The window background stays light, the top window bar stays light.

Using gnome tweaks tool to change the appearance works, and then
changing the "window colors" once works (sets colors back to default).
All further color changes do not work.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 25 18:17:33 2021
InstallationDate: Installed on 2013-11-29 (2703 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to focal on 2021-04-25 (0 days ago)

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


** Tags: amd64 apport-bug focal

** Attachment added: "screenshot"
   
https://bugs.launchpad.net/bugs/1926088/+attachment/5492192/+files/2021-04-25.png

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

Title:
  Appearance: Window colors selection does not work

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

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

[Bug 1923311] Re: nautilus crash when creating symlink

2021-04-24 Thread Christian Rauch

A bit unrelated, but the reason that there is no "nautilus-dbgsym" for
the updated nautilus package (version 1:3.36.3-0ubuntu from "focal-
updates") is that the dbgsym index for the released version ("focal")
at:

http://ddebs.ubuntu.com/dists/focal/main/binary-amd64/Packages

shows the "nautilus-dbgsym" at version "1:3.36.1.1-1ubuntu2", but the
updated index ("focal-updates") at:

http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages

does not contain any "nautilus-dbgsym".

I am mentioning this because I have a couple of other packages that have
been updated but now do not have a corresponding "-dbgsym" package.

@seb128 Do you have an idea where I can report this issue?

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

Title:
  nautilus crash when creating symlink

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

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

[Bug 1923311] Re: nautilus crash when creating symlink

2021-04-16 Thread Christian Rauch

After installing that dbgsym package, I still do not get a backtrace. It
just exits with "[Inferior 1 (process 116937) exited with code 01]" so
maybe it does not crash but the failed assertion makes it just quit?
Also, there is nothing in "/var/crash" which is another indicator that
the process just exits, but does not crash.

I found the upstream issue at
https://gitlab.gnome.org/GNOME/nautilus/-/issues/1303. There it is
reported that this is a Wayland-only issue and I can indeed verify that
this does not happen on X11.

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

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

Title:
  nautilus crash when creating symlink

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

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

[Bug 1923311] Re: nautilus crash when creating symlink

2021-04-16 Thread Christian Rauch

I have the ddebs sources added:
deb http://ddebs.ubuntu.com focal main restricted universe multiverse
deb http://ddebs.ubuntu.com focal-updates main restricted universe multiverse
deb http://ddebs.ubuntu.com focal-proposed main restricted universe multiverse

But the dbgsym version does not match the package version:

$ apt list nautilus -a
nautilus/focal-updates,now 1:3.36.3-0ubuntu1 amd64  [installiert]
nautilus/focal 1:3.36.1.1-1ubuntu2 amd64

$ apt list nautilus-dbgsym -a
nautilus-dbgsym/focal 1:3.36.1.1-1ubuntu2 amd64

After nautilus has been updated to version "1:3.36.3-0ubuntu1" the
-dbgsym package stayed at version "1:3.36.1.1-1ubuntu2". So I cannot
install "nautilus-dbgsym" and run gdb with the debug symbols to check
where it crashes.

Anyway, this issue is pretty easy reproducible on my side and occurs
every time.

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

Title:
  nautilus crash when creating symlink

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

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

[Bug 1923311] [NEW] nautilus crash when creating symlink

2021-04-10 Thread Christian Rauch

Public bug reported:

nautilus crashes when I try to create a symbolic link via drag and drop:

1. open an arbitrary folder in nautlus
2. hold 'Alt' and drag and drop a file
3. a context dialog will open with options to move, copy or link the file
4. chose any option

Choosing any option (even abort) or just changing to another window will
crash nautilus with:

gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed


Since the "nautilus-dbgsym" package hasn't been updated, it cannot be installed 
and I cannot collect a meaningful backtrace.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 10 16:01:41 2021
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 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/1923311

Title:
  nautilus crash when creating symlink

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

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

[Bug 1912833] Re: Gnome shell crashes when using wl-copy or wl-paste (SIGFPE in wl_shell_surface_role_configure from meta_window_wayland_configure)

2021-04-06 Thread Christian Rauch

I believe that this is the same issue that causes crashes for me in some
situations where a Wayland surface is committed without a window
geometry.

The upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/1739
includes a backtrace of the crash on the "gnome-3-36" branch. So this
issue will not be fixed with the 3.36.9 release.

Upstream has no interest in maintaining 3.36 anymore (see comments)
because there are not enough volunteers. For long-term maintenance of
GNOME 3.36, it would maybe make sense if someone from the
Ubuntu/Canonical team would step up to backport fixes into the
"gnome-3-36" branch (or a fork) and do further releases.

Alternatively, you could also release newer GNOME Shell versions with
the LTS point releases. I think Red Hat used to do this with RHEL7.

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1739
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1739

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

Title:
  Gnome shell crashes when using wl-copy or wl-paste (SIGFPE in
  wl_shell_surface_role_configure from meta_window_wayland_configure)

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

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

[Bug 1919143] Re: SRU mutter to 3.36.9

2021-04-05 Thread Christian Rauch

It would be helpful to also update the packages "mutter-dbgsym" and
"libmutter-6-0-dbgsym" to the corresponding point/patch versions.

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

Title:
  SRU mutter to 3.36.9

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

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

[Bug 1888399] Re: After Update->20.04, Empathy/Salut stops working

2021-03-29 Thread Christian González

BTW, I purged/reinstalled empathy. Did not help.

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

Title:
  After Update->20.04, Empathy/Salut stops working

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

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

[Bug 1888399] Re: After Update->20.04, Empathy/Salut stops working

2021-03-29 Thread Christian González

Is there anything I can post here to fix this bug? What else information
do you need?

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

Title:
  After Update->20.04, Empathy/Salut stops working

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

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

[Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-22 Thread Christian Ehrhardt 

** Merge proposal unlinked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/399966

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

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

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

[Bug 1919143] Re: Update mutter to 3.36.9

2021-03-20 Thread Christian Rauch

I am a bit confused about the version scheme here. My "About" page in
the settings says I am already on GNOME Version 3.36.8, but the mutter
version is 3.36.7 and the gnome-shell version is 3.36.4.

How is this "GNOME Version" determined? Shouldn't all the GNOME packages
be on the same version 3.36.8
(https://gitlab.gnome.org/GNOME/mutter/-/tree/3.36.8,
https://gitlab.gnome.org/GNOME/gnome-shell/-/tree/3.36.8, ...)?

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

Title:
  Update mutter to 3.36.9

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

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

[Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-17 Thread Christian Ehrhardt 

open-vm-tools fixed in

open-vm-tools (2:11.2.5-2ubuntu1) hirsute; urgency=medium   
 

  
   * d/p/fix-FTFBS-glib2.0-2.66.3.patch: fix FTBFS with glib2.0 >=2.66.3 

-- Christian Ehrhardt   Mon, 08 Mar
2021 12:12:35 +0100


** Changed in: open-vm-tools (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

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

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

[Bug 1919143] [NEW] update mutter to 3.36.8

2021-03-15 Thread Christian Rauch

Public bug reported:

This is a request to update mutter to version 3.36.8 to fix various
issues that have been fixed upstream.

See https://gitlab.gnome.org/GNOME/mutter/-/issues/1700#note_1058654 for
the original mutter issue report that will be fixed by 3.36.8.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libmutter-6-0 3.36.7+git20201123-0.20.04.1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 15 10:40:58 2021
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  update mutter to 3.36.8

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

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

[Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-08 Thread Christian Ehrhardt 

Forwarded to upstream open-vm-tools as 
https://github.com/vmware/open-vm-tools/issues/500
Uploaded a fix for Ubuntu in 
https://launchpad.net/ubuntu/+source/open-vm-tools/2:11.2.5-2ubuntu1

** Bug watch added: github.com/vmware/open-vm-tools/issues #500
   https://github.com/vmware/open-vm-tools/issues/500

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

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

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

[Bug 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-07 Thread Christian Ehrhardt 

Thanks Iain for the Fixes in glib.
I need to sort out how to adopt that in qemu for now ...


Also open-vm-tools is also FTBFS by this, so I need to add a task and work on 
that as well.

** Also affects: open-vm-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  glib2.0 >=2.67.3 breaks include from an extern C context

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

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

[Bug 1917812] Re: extracting archives from within nautilus omits subfolders

2021-03-04 Thread Christian Rauch

I am experiencing this issue on two laptops with 20.04.2. But I just
verified that it indeed works as expected with a Live ISO inside a VM.

Is there a way to debug this?

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

Title:
  extracting archives from within nautilus omits subfolders

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

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

[Bug 1917812] [NEW] extracting archives from within nautilus omits subfolders

2021-03-04 Thread Christian Rauch

Public bug reported:

When extracting ZIP archives from within nautilus (e.g. right-click ->
"Extract Here") the extracted file structure is missing subfolders.

Reproduce:
1. download a ZIP archive that includes files and folders in the root (e.g. 
https://github.com/electron/electron/releases/download/v12.0.0/electron-v12.0.0-linux-x64.zip)
2. within nautilus right-click on the archive and select "Extract Here"
3. check the extracted folder, you will see that only the files have been 
extracted, the folders are missing

This is an issue that was recently introduced, as this used to work a
while ago on Ubuntu 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  4 22:09:52 2021
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 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/1917812

Title:
  extracting archives from within nautilus omits subfolders

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

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

[Bug 1916705] [NEW] glib2.0 >=2.67.3 breaks include from an extern C context

2021-02-23 Thread Christian Ehrhardt 

Public bug reported:

qemu now breaks in Hirsute (it didn't 23h ago)
Broken:
https://launchpadlibrarian.net/524654684/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-6ubuntu1_BUILDING.txt.gz

Good before:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4471/+packages

Error:

../../disas/arm-a64.cc
In file included from /usr/include/glib-2.0/glib/gmacros.h:241,
 from /usr/lib/x86_64-linux-gnu/glib-2.0/include/glibconfig.h:9,
 from /usr/include/glib-2.0/glib/gtypes.h:32,
 from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /<>/qemu-5.2+dfsg/include/glib-compat.h:32,
 from /<>/qemu-5.2+dfsg/include/qemu/osdep.h:126,
 from ../../disas/arm-a64.cc:21:
/usr/include/c++/10/type_traits:56:3: error: template with C linkage
   56 |   template
  |   ^~~~
../../disas/arm-a64.cc:20:1: note: ‘extern "C"’ linkage started here
   20 | extern "C" {
  | ^~

Also in disas/nanomips.cpp, ...

And indeed disas/arm-a64.cc has:
 20 extern "C" {
 21 #include "qemu/osdep.h"
 22 #include "disas/dis-asm.h"
 23 }

Through the chain of headers as reported above this gets to the templates
in /usr/include/c++/10/type_traits which fails due to that.

So C++ constructs within a C scope which is this bug.

Upstream qemu has not recently changed yet for this.
The code is the same since 2016 via commit e78490c44: "disas/arm-a64.cc:
Include osdep.h first" by Peter Maydell.

But what was different before to break it now?
To find that I was comparing Hirsute vs Hirsute-proposed ...

It is indeed failing in -proposed but working in hirsute-release.

10.2.1-20ubuntu1 : bad

repro in broken build:
$ cd /root/qemu-5.2+dfsg/b/qemu
$ c++ -Ilibcommon.fa.p -I. -I../.. -Iqapi -Itrace -Iui -Iui/shader 
-I/usr/include/pixman-1 -I/usr/include/virgl -I/usr/include/libpng16 
-I/usr/include/spice-server -I/usr/include/spice-1 -I/usr/include/libusb-1.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cacard -I/usr/include/nss -I/usr/include/nspr 
-I/usr/include/PCSC -I/usr/include/slirp -fdiagnostics-color=auto -pipe -Wall 
-Winvalid-pch -Wnon-virtual-dtor -std=gnu++11 -O2 -g -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -U_FORTIFY_SOURCE -m64 -mcx16 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wundef 
-Wwrite-strings -fno-strict-aliasing -fno-common -fwrapv -g -O2 
-ffile-prefix-map=/root/qemu-5.2+dfsg=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wempty-body 
-Wendif-labels -Wexpansion-to-defined -Wno-missing-include-dirs 
-Wno-shift-negative-value -Wno-psabi -fstack-protector-strong -isystem 
/root/qemu-5.2+dfsg/linux-headers -isystem linux-headers -iquote 
/root/qemu-5.2+dfsg/tcg/i386 -iquote . -iquote /root/qemu-5.2+dfsg -iquote 
/root/qemu-5.2+dfsg/accel/tcg -iquote /root/qemu-5.2+dfsg/include -iquote 
/root/qemu-5.2+dfsg/disas/libvixl -pthread -fPIE -DSTRUCT_IOVEC_DEFINED 
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNCURSES_WIDECHAR -MD -MQ 
libcommon.fa.p/disas_nanomips.cpp.o -MF libcommon.fa.p/disas_nanomips.cpp.o.d 
-o libcommon.fa.p/disas_nanomips.cpp.o -c ../../disas/nanomips.cpp

With that I have a test env...

Doko asked me to test
https://launchpad.net/ubuntu/+source/gcc-10/10.2.1-19ubuntu1/+build/20995220/+files/g++-10_10.2.1-19ubuntu1_amd64.deb
That fails as well, but also good as well as bad case have 10.10.2.1-20ubuntu1
It must be something else.

The difference were ~340 packages I was upgrading them to spot what broke it.
I eventually found glib 2.66 -> 2.67 to break it.

libglib2.0-0/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-data/hirsute-proposed 2.67.4-1 all [upgradable from: 2.66.4-1]
libglib2.0-dev-bin/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]
libglib2.0-dev/hirsute-proposed 2.67.4-1 amd64 [upgradable from: 2.66.4-1]

Old:
/*
 * We can only use __typeof__ on GCC >= 4.8, and not when compiling C++. Since
 * __typeof__ is used in a few places in GLib, provide a pre-processor symbol
 * to factor the check out from callers.
 *
 * This symbol is private.
 */
#undef g_has_typeof
#if defined(__GNUC__) && (__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__ >= 
8)) && !defined(__cplusplus)
#define g_has_typeof
#endif

New:
/*
 * We can only use __typeof__ on GCC >= 4.8, and not when compiling C++. Since
 * __typeof__ is used in a few places in GLib, provide a pre-processor symbol
 * to factor the check out from callers.
 *
 * This symbol is private.
 */
#undef glib_typeof
#if !defined(__cplusplus) && \
 ((defined(__GNUC__) && (__GNUC__ > 4 || (__GNUC__ == 4 && __GNUC_MINOR__

[Bug 49579] Re: screen doesn't lock when some menu is open

2020-11-29 Thread Christian Hubmann

This bug is still present in Ubuntu 20.10 / Gnome 3.38. This is a huge
issue especially in corporate environments.

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

Title:
  screen doesn't lock when some menu is open

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

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

[Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)

2020-11-09 Thread Christian Ehrhardt 

Interesting thanks Jakub, 0.38 is in groovy and later
 spice-gtk | 0.37-2fakesync1 | focal/universe   | source
 spice-gtk | 0.38-2ubuntu1   | groovy/universe  | source
 spice-gtk | 0.38-2ubuntu1   | hirsute/universe | source

But being a protocol change [1] I'm unsure we can SRU this to Focal easily.
I wonder that you say only the host needs to change as the discussion on [2] 
says you'll need the new protocol on the guest as well.

I'm glad we have it fixed going forward, but as I said I'm rather unsure
about SRUing this change without a much deeper evaluation.

[1]: https://gitlab.freedesktop.org/spice/spice-gtk/-/merge_requests/25/commits
[2]: https://gitlab.freedesktop.org/spice/spice-gtk/-/issues/82

** Changed in: spice-vdagent (Ubuntu Focal)
   Status: Incomplete => Invalid

** Changed in: spice-protocol (Ubuntu Focal)
   Status: Incomplete => Triaged

** Changed in: spice-protocol (Ubuntu Focal)
   Importance: Undecided => Wishlist

** Also affects: spice-gtk (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: spice-gtk (Ubuntu Focal)
   Status: New => Triaged

** Changed in: spice-gtk (Ubuntu Focal)
   Importance: Undecided => Wishlist

** Changed in: spice-gtk (Ubuntu)
   Status: New => Fix Released

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

Title:
  Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM
  guests)

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

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

[Bug 1900009] Re: Window tiled to monitor where most of the window is in instead of where the mouse is.

2020-10-28 Thread Christian

This seems to be fixed!

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

Title:
  Window tiled to monitor where most of the window is in instead of
  where the mouse is.

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

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

[Bug 1730612] Re: Enable Remote desktop feature during build

2020-10-23 Thread Christian Rauch

This is still an issue on Ubuntu 20.10, while the GNOME Shell remote-
desktop / screencast support on Wayland has been enabled for Fedora and
other distributions for some time now.

What is Ubuntu holding back from enabling Wayland remote-desktop support
(and consecutively a Wayland-by-default 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/1730612

Title:
  Enable Remote desktop feature during build

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+subscriptions

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

[Bug 1900009] Re: Window tiled to monitor where most of the window is in instead of where the mouse is.

2020-10-16 Thread Christian

Issue id is 3290.
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3290

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3290
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3290

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

Title:
  Window tiled to monitor where most of the window is in instead of
  where the mouse is.

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

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

[Bug 1900009] [NEW] Window tiled to monitor where most of the window is in instead of where the mouse is.

2020-10-15 Thread Christian

Public bug reported:

Release: Ubuntu Groovy Gorilla (development branch) 20.10
Package version: 3.38.1-1ubuntu1

When I tile windows using edge tiling, I want the window to tile on the
same edge that I brought it to, however, if the window is mostly in
monitor 1 when I try to tile it to the left (or right) edge of monitor
2, the window will tile to the left (or right) edge of monitor 2.

This happens on both my computer with an Nvidia GPU on x11 and my laptop
using Intel integrated graphics on Wayland.

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

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

Title:
  Window tiled to monitor where most of the window is in instead of
  where the mouse is.

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

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

[Bug 1857655] Re: gdkselection-wayland.c:275: error reading selection buffer

2020-09-30 Thread Christian Kujau

** Bug watch added: Red Hat Bugzilla #1413858
   https://bugzilla.redhat.com/show_bug.cgi?id=1413858

** Also affects: wayland-protocols (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1413858
   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/1857655

Title:
  gdkselection-wayland.c:275: error reading selection buffer

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

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

[Bug 857651] Re: Unable to hide users from login screen / user switcher

2020-09-28 Thread Christian Ehrhardt 

Since so many components are involved a fix/change might have been missed.
And since I recently didn't hear anything about this otherwise rather hot bug I 
was giving focal a try.

It turns out that this was indeed improved. Only the user of pkg:ifmail user 
fdt name "Fidonet" is still visible. All other formerly affected packages are 
good in Focal.
I can't (without digging through history a lot) say what fixed that but I'll 
update the bug tasks accordingly. Setting Focal fixed and marking Bionic/Xenial 
as still affected releases.
The backport tasks for those packages are incomplete thou as it is unclear 
which change in which package fixed it for Focal.

Note: This is only speaking for the "default config" of Ubuntu Desktop
as in 20.04 we know that certain environments will behave differently
(e.g. KDE never was affected).

** Also affects: ifmail (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: libvirt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ceph (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: accountsservice (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: netqmail (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: sddm (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: ifmail (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: libvirt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ceph (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: accountsservice (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: netqmail (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: sddm (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: accountsservice (Ubuntu Xenial)

** No longer affects: accountsservice (Ubuntu Bionic)

** Changed in: ceph (Ubuntu Xenial)
   Status: New => Incomplete

** Changed in: ceph (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: ceph (Ubuntu)
   Status: Triaged => Fix Released

** No longer affects: ifmail (Ubuntu Xenial)

** No longer affects: ifmail (Ubuntu Bionic)

** No longer affects: lightdm (Ubuntu Xenial)

** No longer affects: lightdm (Ubuntu Bionic)

** Changed in: libvirt (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: libvirt (Ubuntu Xenial)
   Status: New => Incomplete

** Changed in: libvirt (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: netqmail (Ubuntu Xenial)
   Status: New => Incomplete

** Changed in: netqmail (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: netqmail (Ubuntu)
   Status: Triaged => Fix Released

** No longer affects: sddm (Ubuntu Xenial)

** No longer affects: sddm (Ubuntu Bionic)

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

Title:
  Unable to hide users from login screen / user switcher

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

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

[Bug 1896188] Re: Activities Overview does not exit anymore getting the desktop stuck

There were no extensions in:
'/home/paelzer/.local/share/gnome-shell/extensions': No such file or directory

I already disabled them via gnome-tweaks before, but doing so again the
ways you asked me to do that.

Getting back to the config showed a few of them enabled indeed, maybe that was 
re-initialized to that?
Anyway - re-removed and disabled.
Reboot ...

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

Title:
  Activities Overview does not exit anymore getting the desktop stuck

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

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

[Bug 1896188] Re: Activities Overview does not exit anymore getting the desktop stuck

That was it, thanks Daniel!

Now I need to restore as much of my config as possible without breaking
it again ...

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

Title:
  Activities Overview does not exit anymore getting the desktop stuck

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

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

[Bug 1896188] GsettingsChanges.txt

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1896188/+attachment/5412103/+files/GsettingsChanges.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/1896188

Title:
  Show Application Overlay does not exit anymore getting the desktop
  stuck

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

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

[Bug 1896188] Re: Show Application Overlay does not exit anymore getting the desktop stuck

Now the description is complete in regard to all things worth to try that came 
to my mind.
Also the apport data as well as the video is attached.

Setting back to new for re-review by the Desktop Team.


P.S. is the overlay an application on it's own that I could try to kill from a 
console?
P.P.S. Can I somehow disable the "Show applications" overlay to not open as I 
can't stop muscle memory to open it and then I'm forced to reboot.

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

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

Title:
  Show Application Overlay does not exit anymore getting the desktop
  stuck

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

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

[Bug 1896188] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1896188/+attachment/5412105/+files/ProcEnviron.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/1896188

Title:
  Show Application Overlay does not exit anymore getting the desktop
  stuck

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

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

[Bug 1896188] Re: Show Application Overlay does not exit anymore getting the desktop stuck

The video shows:
00:09 - opening the "Show Applications" overlay works fine at first.
00:14 - searching an application in there works
00:16 - I open gedit and would expect to get back onto the desktop.
But I can't it sticks within the overlay.
I tried to hit the "Escape" key, clicking on windows, clicking on the
background, ...
Nothing gets me back.

The menu bar at the bottom still works, so all I can do is restart the
system from there.

** Attachment added: "Video showcasing the issue"

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896188/+attachment/5412101/+files/desktop-stuck-in-overlay.ogv

** Tags added: apport-collected focal

** Description changed:

Hi,
this must sound odd, but to me most Desktop bugs do :-/

The issue:
- If I hit the meta key the usual "search app" overlay appears.
- I search for an application and start it
- the overlay does NOT disappear anymore
- the miniature images of the just started app seems fine
- without being able to leave the overlay I'm stuck unable to input into
applications anymore
- Things like mouse and alt+f4 seem to work, therefore it seems to work fine
but not update the screen correctly.

There are other "screen update issues" that started to occur with the
above e.g. when I start firefox it only displays and later updates part
of the window. Resizing the window (bigger) does not change the
displayed area.

The way I can start applications in UI for now is via the run-command
on ALT+F2 entering the app directly.

## Tries to resolve so far:
- I have seen similar issues due to different themes that after upgrades fail
to work well. I usually used the "Yaru" theme, but I switched back to the
default theme (Adawaita) and issues remain.
- starting the overlay with a mouse click to the menu icon instead of meta
key => fails as well
- Go into lock screen and log back in - still in the hanging overlay
- go back to the last known working kernel (5.4.0-42) without any change in
behavior (=seems not kernel related)
- reset the full gnome config back to pristine state and reboot. Well I can
confirm that all config seems lost, but the issue still behaves the same
- Remove all packages that I considered not immediately needed (but not
things of the default install, you know all those things you installed once and
never needed) to ensure they have no bad influence - still bad

---

## Odd things that might (or not) be related:

Only read this section as "could it help me to understand the main issue
above", but not as individual or grouped report of other issues into one
bug.

Yesterday I had programs with text areas (gedit, gvim, ...) stuck. The text
panels just didn't initialize anymore - they stayed inactive. All of such
programs that I started before worked fine and I was assuming some auto-update
in background might have broken things. Therefore I tried to close out my open
work and reboot after a full upgrade of whatever packages were still
outstanding to upgrade. But this left me with the current problem.
BTW - now such editors initialize and work fine again.

While trying to create a video of this I found another helpful hint - this
really seems to affect all overlays. Usually for UI-bug-videos I use the
program "screenkey" which itself does an overlay showing the keys that were
pressed. That as well got stuck and I could not get back to a working desktop.
So it seems this is about a general "overlays are bad" more than "the
application search overlay is bad".
I thought that would be great for debugging, but I got this happening only
once while the issue with the application search overlay remains.

---

- I'll try to capture it on video so you can make more sense of it and
- also probably re-target it to the right component as well as letting me
- know what to do for better debugging.
+ I'll try to capture it on video so you can make more sense of it and also
probably re-target it to the right component as well as letting me know what to
do for better debugging.
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.8
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2018-10-12 (706 days ago)
+ InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
+ RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
+ Tags: focal
+ Uname: Linux 5.4.0-47-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-04-03 (167 days ago)
+ UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sbuild sudo
+ _MarkForUpload: True

--
You received this bug notification because you are a

[Bug 1896188] ProcCpuinfoMinimal.txt