[Bug 2060361] Re: Dateisysten
Nautilus Problem, möglich. Kernel problem, halte ich für unwahrscheinlich aber nicht unmöglich. Sicher ist allerdings das ohne Nachvollziehbare Schritte hier leider keine weiterhelfen kann. Ich aktualisiere den Fall dazu passend, aber ohne weitere Info wird leider nichts mehr passieren. P.S. Ich halte es auch immer noch für möglich das es eine Unsicherheit/Unklarheit bei der verwendung ist und alles eigentlich OK ist. Doch auch das kann man ohne Nachvollziehbares nicht prüfen. ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Changed in: nautilus (Ubuntu) Status: New => Incomplete ** Changed in: cloud-images Status: Incomplete => Invalid -- 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/2060361 Title: Dateisysten To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/2060361/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000644] Re: switching workspaces with shortcut sometimes freezes screen
FYI Undocked with just the laptop screen it does not trigger the issue. But docking the running system to initialize all additional screens makes it trigger up again once I leave into the activities screen (as described before). -- 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/2000644 Title: switching workspaces with shortcut sometimes freezes screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000644] Re: switching workspaces with shortcut sometimes freezes screen
Considering it impossible to work with a system hanging every few hours I debugged this over the weekend a few times, but sadly to no further insight. Eventually I've given up and re-deployed Mantic on the system trying to either "help by verifying the issue still exists" or "getting out of it". I can confirm that, at least on my system, the issue is still reproducible right after new installation of Mantic. The workaround of a fix number of workspaces still does not work for me. Setups showing this: - Laptop + 2 external monitors, intel gpu - Laptop + 2 external monitors + 2 via displaylink, intel gpu I intend to undock, reboot and test if it also shows on this machine without external monitors - didn't find the time yet. -- 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/2000644 Title: switching workspaces with shortcut sometimes freezes screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000644] Re: switching workspaces with shortcut sometimes freezes screen
FYI: Since the signature of bug 2035016 is quite similar I checked, but I already have the mutter components on 45.0-2ubuntu1. -- 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/2000644 Title: switching workspaces with shortcut sometimes freezes screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2000644] Re: switching workspaces with shortcut sometimes freezes screen
I see the same on Jammy, like the others it is reproducible easily by hitting the meta key and exiting from there in any way (hit ESC, select anything to start, ...). Sadly setting fixed workspaces (10) did not work around the issues for me, like it did for others. Occasionally (seems to depend if this issue races with something else as it seems more likely if the system has more apps running and me doing more things) I also get the stuck-desktop experience out of that. Usually starting with the mouse not being able to click everything anymore and a while after with a totally stuck desktop (not even ctrl-alt-f# gets me out anymore). That "stuckness" if it is still phase-I (mouse can't clock it all) sometimes resolves itself after a few minutes - no log entries in journal when that un-stucking happens. -- 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/2000644 Title: switching workspaces with shortcut sometimes freezes screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2000644/+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
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.
** 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 1892456] Re: [MIR] malcontent
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 1964600] Re: [MIR] gnome-bluetooth3
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
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 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
FYI the re-upload of a fuse3 open-vm-tools happened yesterday and it migrated to jammy-release. Any issues with the images? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1956949 Title: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse" To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1956949/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956949] Re: CPC AWS jammy builds fail with: "fuse3 : Breaks: fuse"
@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"
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
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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
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
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)
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
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)
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)
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)
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 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
** 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 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
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 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context
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
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 1916705] [NEW] glib2.0 >=2.67.3 breaks include from an extern C context
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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
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 857651] Re: Unable to hide users from login screen / user switcher
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
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1896188/+attachment/5412104/+files/ProcCpuinfoMinimal.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] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1896188/+attachment/5412107/+files/monitors.xml.txt ** 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 + - I usually have a lot of screen attached, to be sure that is unrelated I undocked the laptop and restarted with just the one laptop screen -> still the same issue - 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 + + + I attached a video of the issue down below so you can take a look. + --- ## 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. - --- 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 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] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1896188/+attachment/5412102/+files/Dependencies.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] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1896188/+attachment/5412106/+files/ShellJournal.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
Hi Daniel, I'm on it ... :-) Video just completed - I already wrote that I'll attach one. And I separated the "potentially related, but other issues" into an extra section for exactly the reason of keeping this bug to one issue, but at the same time I want/need to provide all info that might be wanted. ** Summary changed: - GTK Overlays do not refresh/exit and get the desktop stuck + Show Application Overlay does not exit anymore getting the desktop stuck ** 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: - ## 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. -- 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: GTK Overlays do not refresh/exit and get the desktop stuck
** 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 - - 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" + 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. --- ## Odd things happened recently that might (or not) be related: 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. --- 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. ** 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
[Bug 1896188] Re: GTK Overlays do not refresh/exit and get the desktop stuck
** Summary changed: - Overlays do not refresh anymore and get the desktop stuck + GTK Overlays do not refresh/exit and get the desktop stuck -- 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: GTK Overlays do not refresh/exit and get 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: Overlays do not refresh anymore and get the desktop stuck
** 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 + + 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" + --- ## Odd things happened recently that might (or not) be related: 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. --- 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. -- 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: GTK Overlays do not refresh/exit and get 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: Overlays do not refresh anymore and get the desktop stuck
** 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) - - ## Tries to resolve that I want to do but don't yet know how: - - reset the full gnome config back to pristine state (maybe back up my old one) so we could check if "any" config is related to this. + - 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 happened recently that might (or not) be related: 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. --- 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. -- 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: Overlays do not refresh anymore and get 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: Overlays do not refresh anymore and get the desktop stuck
On backup I had: mv: cannot stat '.gnome2': No such file or directory mv: cannot stat '.gconfd': No such file or directory mv: cannot stat '.metacity': No such file or directory but worked for the rest Also disabled all extensions (didn't have any active, but can't hurt) Restarting into that now ... -- 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: Overlays do not refresh anymore and get 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: Overlays do not refresh anymore and get the desktop stuck
Trying hard reset of my config via: $ mkdir -p ~/.backup-gnome-config/ && for f in .gnome .gnome2 .gconf .gconfd .metacity .config/dconf; do mv $f ~/.backup-gnome-config/; done $ gnome-tweaks # then reset to defaults -- 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: Overlays do not refresh anymore and get 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: Overlays do not refresh anymore and get the desktop stuck
** 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. + 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) ## Tries to resolve that I want to do but don't yet know how: - reset the full gnome config back to pristine state (maybe back up my old one) so we could check if "any" config is related to this. --- ## Odd things happened recently that might (or not) be related: 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. --- 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. -- 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: Overlays do not refresh anymore and get 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: Overlays do not refresh anymore and get the desktop stuck
** 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 ## Tries to resolve that I want to do but don't yet know how: - reset the full gnome config back to pristine state (maybe back up my old one) so we could check if "any" config is related to this. --- ## Odd things happened recently that might (or not) be related: 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. --- 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. -- 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: Overlays do not refresh anymore and get 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] [NEW] Overlays do not refresh anymore and get the desktop stuck
Public bug reported: 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. ## 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. ## Tries to resolve that I want to do but don't yet know how: - reset the full gnome config back to pristine state (maybe back up my old one) so we could check if "any" config is related to this. --- ## Odd things happened recently that might (or not) be related: 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. --- 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. ** 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/1896188 Title: Overlays do not refresh anymore and get 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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
And on Bionic we only need to do so for amd64 Here is a new MP for Bionic: https://code.launchpad.net/~paelzer/britney/hints-ubuntu-bionic-disable-systemd-v2/+merge/390793 ** Branch linked: lp:~paelzer/britney/hints-ubuntu-bionic-disable- systemd-v2 -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
The problem with Xenial is that there it isn't just flaky "systemd- fsckd" much more seems to be broken. I'll revise my Bionic MP, but for Xenial I'd like to hear from ddstreet/rbalint how they think we should go on there ... -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Focal test hint was accepted tonight and things moved there. @Kelsey - Steve denied the hint as a reset since recently a few results were good. Maybe you want to submit the same as force-badtest and bring it up like that for X? The results for xenial really look similarly bad ... xenial amd64 boot-and-services (F 45% f 0% S 0% B 5% => P 50%/) .FF...BFF.F. boot-smoke (F 80% f 0% S 0% B 5% => P 15%/) F.FF..BF systemd-fsckd (F 65% f 0% S 0% B 5% => P 30%/) FF.FFF.F..B.FF.F ppc64el no failures s390x no failures I know that ddstreet is considering the SRU updates for systemd to also mark those flaky. I'm still +1 to mark them force-badtest until then but I'm not the one to decide. -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
** Branch linked: lp:~paelzer/britney/hints-ubuntu-focal-disable-systemd -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Thanks rbalint for pointing me to the other bug for the s390x fail we see now. I'll continue there and consider the Groovy portion of this one closed again. -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Groovy It seems this isn't over for groovy, it was mentioned that the issues in the subtest "tests-in-lxd" would be related to some fstab issues in those issues. But recently all architectures, but s390x recovered. I assume that the fstab issue is fixed but something else surfaces now. groovy s390x tests-in-lxd (F 100% f 0% S 0% B 0% => P 0%/) FF boot-and-services (F 3% f 0% S 0% B 0% => P 96%/) .F systemd-fsckd (F 26% f 73% S 0% B 0% => P 0%/) fFFfFF We see when systemd-fsckd was marked flaky (F->f), but tests-in-lxd continues to perma-stop any migration depending on systemd. Currently this holds back a lot of things in groovy, it seems to be: qemu/1:5.0-5ubuntu7 chiark-tcl/1.3.4ubuntu3 cmake-extras/1.5-1ubuntu1 cstore-fdw/1.7.0-1 dateparser/0.7.4-1 dpdk/19.11.4-1 gem2deb/1.2.1 glibc/2.32-0ubuntu2 gnome-desktop3/3.37.90.1-1ubuntu1 grep/3.4-1 libnss-nis/3.1-0ubuntu3 libnss-nisplus/1.3-0ubuntu3 link-grammar/5.8.0-1 mksh/59b-1 natsort/7.0.1-1 openconnect/8.10-1 orafce/3.13.4-1 pandas/1.0.5+dfsg-3 pango1.0/1.46.1-1 php-nesbot-carbon/2.32.2-1 php-shellcommand/1.6.1-1 php-twig/2.13.0-1 postgresql-12/12.4-1 postgresql-common/216 postgresql-multicorn/1.4.0-2 reprotest/0.7.15 snapd/2.46.1+20.10 symfony/4.4.11+dfsg-1ubuntu1 systemd/246.4-1ubuntu1 tracker/2.3.4-1build1 vis/0.6-3 Therefore re-opening the groovy task, this isn't over yet :-/ @rbalint please let us know if you know more details about it already. ** Changed in: systemd (Ubuntu) Status: Fix Released => 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
[15:17] ddstreet: any updates on 1892358? [15:18] @paelzer sorry not yet, i'll have systemd ready for upload next week including fixing the autopkgtests [15:21] ok -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
@ddstret - any update how to proceed? If you have no time yet, then the MPs to ignore the fail until we have a new version are up - just ack them and I guess the SRU Team will follow. -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
If not going for marking the subtest flaky as in groovy, I have prepared force-reset-test as alternatives in: - https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390005 - https://code.launchpad.net/~paelzer/britney/hints-ubuntu-focal-disable-systemd/+merge/390004 -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
To match the open packages blocked on this in active releases I added linux-meta for BIonic (thanks Kleber for the hint) and Focal (Thanks Kelsey for the hint). I think all of those had enough of retry-until-success and I'd ask again for how we should proceed there. Masking/Resetting the test via an override would throw away so much other coverage, but lacking other feedback I'll at least proposed the change - maybe this also brings more attention to here. Last 20 focal amd64 upstream (F 5% S 0% B 5% => P 90%/) F.B. systemd-fsckd (F 95% S 0% B 5% => P 0%/) FFBF ppc64el systemd-fsckd (F 65% S 0% B 0% => P 35%/) ...F s390x systemd-fsckd (F 60% S 0% B 0% => P 40%/) bionic amd64 boot-smoke (F 20% S 0% B 0% => P 80%/) ...F.FFF upstream (F 10% S 0% B 0% => P 90%/) ...F..F. systemd-fsckd (F 85% S 0% B 0% => P 15%/) FFF.FF.. They all seem to continue to be heavy on "systemd-fsckd" ** Also affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta (Ubuntu) Status: New => Invalid -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Util-linux SRU in Focal blocked as well, updating tags. ** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Changed in: util-linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
True @Kleber, here the stats of Bionic - at least on x86 you seem to have barely a chance. bionic amd64 boot-smoke (F 40% S 0% B 0% => P 60%/) ...F.FFF.FF.FF.. upstream (F 5% S 0% B 0% => P 95%/) ..F. systemd-fsckd (F 90% S 0% B 0% => P 10%/) FFF.F.FF i386 upstream (F 20% S 0% B 0% => P 80%/) .F.F..FF systemd-fsckd (F 20% S 0% B 0% => P 80%/) FF.F..F. ppc64el upstream (F 15% S 0% B 0% => P 85%/) F..FF... systemd-fsckd (F 10% S 0% B 0% => P 90%/) ...F...F s390x no failures armhf no failures arm64 logind (F 15% S 0% B 5% => P 80%/) ...B.FFF -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Here an (monospace) overview of recent focal tests. focal amd64 networkd-testpy(F 5% S 0% B 5% => P 90%/) .B...F.. boot-and-services (F 5% S 0% B 5% => P 90%/) .B...F.. upstream (F 5% S 0% B 5% => P 90%/) .B...F.. systemd-fsckd (F 95% S 0% B 5% => P 0%/) FBFF ppc64el systemd-fsckd (F 45% S 0% B 0% => P 55%/) FFF...F..F.. s390x systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF. There also are some linux-meta uploads blocked by the same, but I don't know what task to add for them. -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
https://launchpad.net/ubuntu/+source/systemd/246.2-1ubuntu1 is still in proposed and I was looking forward to a bunch of custom triggers this morning. But I found everything migrated this morning despite those new tests not being done. https://autopkgtest.ubuntu.com/packages/s/systemd/groovy/amd64 Since the bug had no update about it I checked and found: http://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/4957 Thanks rbalint - this certainly unblocks things for now. Anything coming later should test against the new systemd version and then hopefully work. Due to that I think we can set the formerly affected extra tasks to invalid (since they were only here for tracking of the update-excuses tag). ** Changed in: ntpsec (Ubuntu) Status: Confirmed => Invalid ** Changed in: kbd (Ubuntu) Status: Confirmed => Invalid ** Changed in: iputils (Ubuntu) Status: Confirmed => Invalid ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Invalid ** Also affects: build-essential (Ubuntu) Importance: Undecided Status: New ** Changed in: build-essential (Ubuntu Focal) Status: New => Confirmed ** Changed in: build-essential (Ubuntu) Status: New => Invalid ** Changed in: qemu (Ubuntu Focal) Status: New => Confirmed ** Changed in: qemu (Ubuntu) Status: Confirmed => Invalid ** Changed in: systemd (Ubuntu) Status: New => Fix Committed -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
What is left is the similar situation in Focal (as mentioned before). I have updated the tasks to reflect that properly and get update-excuse tagging there. In Focal it is currently blocking qemu and build-essential SRUs and I wanted to ask if the plan is to do the same upload+test-reset there or anything else. @ddstreet - rbalint said you are prepping the systemd SRUs, could you let us know what is the plan there? -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/build-essential/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
[16:34] seb128, cpaelzer ahasenack sorry, i was out and apparently forgot setting that in my email. the last systemd upload should fix everything except for the livecd-rootfs revert that made fstab in lxd images invalide [16:45] rbalint: " the last systemd upload" means groovy I guess, what about focal? [16:47] cpaelzer, sru-s are usually prepared by ddstreet, but i guess you mean the flakiness [16:49] cpaelzer, as i look at the last runs the latest focal systemd upload got flakier without a change in systemd so it may be an infra issue or needs more investigation [16:50] rbalint: do you want a new bug about it for you and ddstreet then? [16:50] to focus the discussion in one place I mean [16:50] cpaelzer, LP: #1892358 is not open against focal so i think just adding focal would be enough Task added ** Also affects: iputils (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: glib2.0 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: kbd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ntpsec (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: qemu (Ubuntu Focal) ** No longer affects: kbd (Ubuntu Focal) ** No longer affects: ntpsec (Ubuntu Focal) ** No longer affects: glib2.0 (Ubuntu Focal) ** No longer affects: iputils (Ubuntu Focal) -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1892358/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Adding glib2.0 as it had a rebuild for libffi and will be blocke dby this as well. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed -- 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/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1892358/+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
The last two updates went smooth for me, not triggering it. I'm still too afraid to "just update while working" as I did in the past since it could drag things down thou :-/ I was feeling like this could be solved, but reading that Steve is also affected I'm worried that I might just not hit the same race/trigger by accident. -- 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/systemd/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803230] Re: [MIR] teckit & xxhash, new rdeps of texlive-bin
xxhash was a code split from a package already in main and already promoted in Disco/Eoan. It came back now as dependency for rsync and (thanks Steve) Foundations is subscribed to cover it. Can be promoted to main in groovy ** Changed in: xxhash (Ubuntu) Status: Incomplete => In Progress ** Changed in: xxhash (Ubuntu) Assignee: Steve Langasek (vorlon) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to teckit in Ubuntu. https://bugs.launchpad.net/bugs/1803230 Title: [MIR] teckit & xxhash, new rdeps of texlive-bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/teckit/+bug/1803230/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803230] Re: [MIR] teckit & xxhash, new rdeps of texlive-bin
FYI: As mentioned int he MIR Team meeting, since doko had to run I've sent a mail to vorlon asking if foundations is going to adopt it. ** Changed in: xxhash (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to teckit in Ubuntu. https://bugs.launchpad.net/bugs/1803230 Title: [MIR] teckit & xxhash, new rdeps of texlive-bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/teckit/+bug/1803230/+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
I hit that again today on an upgrade. Network manager didn't come up again. Mai 20 11:04:46 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9491] caught SIGTERM, shutting down normally. Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9504] dhcp4 (enp0s31f6): canceled DHCP transaction Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9504] dhcp4 (enp0s31f6): state changed extended -> done Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9504] device (enp0s31f6): DHCPv4: trying to acquire a new lease within 90 seconds Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9733] dhcp4 (wlp4s0): canceled DHCP transaction Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9812] dhcp4 (wlp4s0): state changed bound -> done Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9813] device (wlp4s0): DHCPv4: trying to acquire a new lease within 90 seconds Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9817] device (p2p-dev-wlp4s0): state change: disconnected -> unmanaged (reason 'unmanaged', sys-iface-state: 'managed') Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9825] device (strswanbr2-nic): released from master device strswanbr2 Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9829] device (strswanbr1-nic): released from master device strswanbr1 Mai 20 11:04:46 Keschdeichel NetworkManager[1330]: [1589965486.9831] device (veth47e5): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0047] device (virbr0-nic): released from master device virbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0050] device (vethcc7405c8): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0069] device (vetha09a9db4): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0077] device (veth754add92): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0094] device (vethc060f004): released from master device virbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0101] device (veth3152ecc9): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.0109] device (vethb6dd0569): released from master device lxdbr0 Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1008] device (virbr0): bridge port vnet1 was detached Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1025] manager: NetworkManager state is now CONNECTED_SITE Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1030] device (virbr0): bridge port vnet0 was detached Mai 20 11:04:47 Keschdeichel NetworkManager[1330]: [1589965487.1629] exiting (success) Mai 20 11:04:47 Keschdeichel systemd[1]: NetworkManager.service: Succeeded. Mai 20 11:04:48 Keschdeichel nm-openvpn[847263]: SIGTERM[hard,] received, process exiting $ systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: inactive (dead) since Wed 2020-05-20 11:04:47 CEST; 15min ago Docs: man:NetworkManager(8) Main PID: 1330 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 38269) Memory: 12.2M CGroup: /system.slice/NetworkManager.service But that still isn't the root cause. And before this plenty of things failed on GetNameOwner() in that sense it is similar to the former occurance. Mai 20 11:03:56 Keschdeichel systemd[1]: Reloading. Mai 20 11:03:56 Keschdeichel systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run> Mai 20 11:04:11 Keschdeichel tracker-store[976018]: OK Mai 20 11:04:11 Keschdeichel systemd[18845]: tracker-store.service: Succeeded. Mai 20 11:04:21 Keschdeichel systemd[1]: We couldn't coldplug machine-qemu\x2d13\x2dfocal.scope, proceeding anyway: Connection timed out Mai 20 11:04:46 Keschdeichel systemd[1]: We couldn't coldplug machine-qemu\x2d11\x2dbionic.scope, proceeding anyway: Connection timed out Mai 20 11:04:46 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Mai 20 11:04:46
[Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
There are plenty of components involved in "trying" to fix this by spice upstream. The discussion in https://gitlab.freedesktop.org/spice/linux/vd_agent/-/issues/9 is rather long. It eventually seems to be fixed in https://gitlab.freedesktop.org/spice/linux/vd_agent/-/merge_requests/4 I think we have all components in place, except the spice-vdagent 0.20 and maybe spice-protocol 14.1. The series of fixes for spcie-vdagent linked there would be: e0bfa67 configure: bump gtk+ >= 3.22 2c72378 clipboard: remove vdagent-selection-id usage 79d0125 configure: depend on gobject ff30f58 configure: bump gobject >= 2.50 fb69a49 vdagent: use G_OPTION_FLAG_NONE aa26d1d clipboard: gobject-ify VDAgentClipboards 2ad6c15 clipboard: filter out only our own events c9e8067 clipboard: only send release when no immediate grab a2fc33c clipboard: implement CAP_CLIPBOARD_GRAB_SERIAL >From https://gitlab.freedesktop.org/spice/linux/vd_agent.git Our libglib2.0-dev and libgtk-3-dev are new enough as well. But spice-protocol needs: 045a6978 vdagent: introduce VD_AGENT_CAP_CLIPBOARD_GRAB_SERIAL 4f397d69 vdagent: introduce VD_AGENT_CAP_CLIPBOARD_NO_RELEASE_ON_REGRAB That is in 0.14.1 which only is in Ubuntu 20.10 already, but not in Focal (14.0 there). I'd expect that 0.20 would not even build without spice-protocol 0.14.1 since the definition of VD_AGENT_CAP_CLIPBOARD_GRAB_SERIAL is missing. Well it might skip it safely. But the report of lwk32 says building 0.20 is fixing his issue, so let us give it a try. We cant take: a2fc33c clipboard: implement CAP_CLIPBOARD_GRAB_SERIAL c9e8067 clipboard: only send release when no immediate grab without this change to spice-protocol which is hard to SRU. The rest of the patches applies cleanly, but I'm unsure if there can be any gain without these final commits. @lwk32 would you mind giving the PPA [1] a try with an otherwise unmodified Ubuntu 20.04 if that fixes the issue for you as well? P.S. We might want to wait until the more clear fix in bug 1852183 lands to not mix results of verifications of -proposed - but we can sniff things right now based on the PPA. [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4060 ** Bug watch added: gitlab.freedesktop.org/spice/linux/vd_agent/-/issues #9 https://gitlab.freedesktop.org/spice/linux/vd_agent/-/issues/9 ** Also affects: spice-protocol (Ubuntu) Importance: Undecided Status: New ** Changed in: spice-protocol (Ubuntu) Status: New => Fix Released ** Changed in: spice-protocol (Ubuntu Focal) Status: New => Incomplete -- 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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
Since Daniel split up the "related but not the same" mutter changes to bug 1852183 (thanks for that work BTW!) let us here focus on the spice component. Thanks lwk32 for identifying a fix for that, I'll be taking a look if that is SRU-safely backportable to Focal. ** Also affects: spice-vdagent (Ubuntu) Importance: Undecided Status: New ** Changed in: virt-manager (Ubuntu) Status: Confirmed => Invalid ** Changed in: spice (Ubuntu) Status: Confirmed => Invalid ** Changed in: qemu (Ubuntu) Status: Confirmed => Invalid ** Bug watch added: Debian Bug tracker #854936 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854936 ** Also affects: spice-vdagent (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854936 Importance: Unknown Status: Unknown ** Also affects: qemu (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: virt-manager (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: spice (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: spice-vdagent (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: spice (Ubuntu Focal) ** No longer affects: qemu (Ubuntu Focal) ** No longer affects: virt-manager (Ubuntu Focal) ** Changed in: spice-vdagent (Ubuntu) Status: New => Fix Released ** Changed in: spice-vdagent (Ubuntu Focal) Status: New => Triaged -- 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
Re: [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
> Thank you. Did you try it on Ubuntu or Kubuntu host? Host was Ubuntu -- 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/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/mutter/+bug/1872527/+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)
I can't recreate this on a 20.04 host neither with virt-manager open or not. Only in the guest. I tried editor (gnome) and kate (KDE editor) on y gnome based 20.04. Very awkward issue, I hope my video helps and I'm looking forward to what Desktop people say as well. -- 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/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/mutter/+bug/1872527/+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 with virt-manager
Here is an example, - on the bottom you see keys pressed (all arrive int he guest) - on the right you see xclip looped as shown in comment #2 - on the left you see the editor I add a few lines of text in the editor to explain what is going on. @John - does that somewhat match what you are seeing? @Desktop-team - any idea what might be going on? ** Attachment added: "hanging-clipboard-20.04.ogv" https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1872527/+attachment/5354358/+files/hanging-clipboard-20.04.ogv ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: virt-manager (Ubuntu) Status: New => Invalid ** Summary changed: - Clipboard doesn't work 100% of the time in Ubuntu 20.04 with virt-manager + Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) -- 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/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/mutter/+bug/1872527/+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)
@Desktop Team: For its similarity with bug 1852183 I'll start with `mutter`, but please re-triage this to where you think this really belongs. ** Tags added: champagne -- 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/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/mutter/+bug/1872527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen
Same happening for me, with two rows of screens, three on top two in the bottom row. Primary is top left. ** Attachment added: "Screenshot_20200408_130437-search-bar-half-visible.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+attachment/5349458/+files/Screenshot_20200408_130437-search-bar-half-visible.png -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen
Overview of the affected layout ** Attachment added: "Screenshot_20200408_132041-layout.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571/+attachment/5349459/+files/Screenshot_20200408_132041-layout.png -- 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/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871607] Re: Aactivities overview is too small (half an icon high)
*** This bug is a duplicate of bug 1869571 *** https://bugs.launchpad.net/bugs/1869571 ** Attachment added: "Screenshot_20200408_132041-layout.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871607/+attachment/5349457/+files/Screenshot_20200408_132041-layout.png ** This bug has been marked a duplicate of bug 1869571 Vertical dual monitor setup with main monitor on bottom causes overview to only use one eigth of screen -- 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/1871607 Title: Aactivities overview is too small (half an icon high) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871607] Re: Aactivities overview is too small (half an icon high)
*** This bug is a duplicate of bug 1869571 *** https://bugs.launchpad.net/bugs/1869571 [13:14] cpaelzer, what screen resolution/scaling factor/video card do you use? That would be: eDP-1 connected primary 1920x1080+0+840 (normal left inverted right x axis y axis) 344mm x 193mm DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) DP-2-1 disconnected (normal left inverted right x axis y axis) DP-2-2 connected 1920x1080+0+1920 (normal left inverted right x axis y axis) 598mm x 336mm DP-2-3 connected 1920x1080+1920+1920 (normal left inverted right x axis y axis) 598mm x 336mm DVI-I-2-2 connected 1080x1920+1920+0 left (normal left inverted right x axis y axis) 598mm x 336mm DVI-I-1-1 connected 1920x1080+3000+840 (normal left inverted right x axis y axis) 598mm x 336mm Card: i915 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) Scaling is 100% on each screen. I'll attach a screenshot of the layout and check the mentoned bug https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869571 -- 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/1871607 Title: Aactivities overview is too small (half an icon high) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871607] Re: Aactivities overview is too small (half an icon high)
** Attachment added: "Screenshot_20200408_130437-search-bar-half-visible.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871607/+attachment/5349456/+files/Screenshot_20200408_130437-search-bar-half-visible.png -- 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/1871607 Title: Aactivities overview is too small (half an icon high) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871607/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871607] [NEW] Aactivities overview is too small (half an icon high)
Public bug reported: Hi, since the upgrade to Focal I wonder why the "activities" overview isn't readable anymore. It is the one you get to when you click "activities" in the top let or hit the "meta" key. In my case this preview is only half an icon high, so I have to assume what things are based on half an icon that is also partially faded out it seems. A screenshot will explain ... ** 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/1871607 Title: Aactivities overview is too small (half an icon high) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871607/+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
Sure @seb128 - I'll let you know if it happens again (as I did a cleaning-reboot now). -- 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/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: Gnome Shell crashed on background upgrade of accountsservice
> could you add the journalctl log from that session, that might include some hints Sure attached here, you see in the initial report and the later comments the time indexes to look out for. Also FYI for the rtkit issue that you will see in there => bug 1871543 ** Attachment added: "journal-gnome-restarts.log" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+attachment/5349396/+files/journal-gnome-restarts.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: Gnome Shell crashed on background upgrade of accountsservice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: Gnome Shell crashed on background upgrade of accountsservice
> Also do you have any gnome-shell/gdm crash collected in /var/crash? No, just these: $ ll /var/crash/*.crash -rw-r- 1 paelzer whoopsie 3589735 Apr 6 08:34 /var/crash/_usr_bin_gnome-clocks.1000.crash -rw-r- 1 paelzer whoopsie 53170176 Apr 8 10:36 /var/crash/_usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 /var/crash/_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash -- 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: Gnome Shell crashed on background upgrade of accountsservice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: Gnome Shell crashed on background upgrade of accountsservice
> 1. Look in /var/crash for crash files and if found run: >ubuntu-bug YOURFILE.crash > Then tell us the ID of the newly-created bug. Again, they all seem to be prior or follow on issues, but they already have IDs in the error tracker. /var/crash/_usr_bin_gnome-clocks.1000.uploaded a615fed4-77d0-11ea-a806-fa163ee63de6 /var/crash/_usr_bin_konversation.1000.uploaded 0e56c64e-7976-11ea-ab51-fa163e983629 /var/crash/_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.uploaded 29cd6100-7976-11ea-a249-fa163e6cac46 They all show up in my personal error-list at: https://errors.ubuntu.com/user/350ea932144813c645983ba6ebba1ab8a271bbbcc08853010a42e92011f8802f77829fce9a7ad953c6c31a499d176f6312a0148c01ef7facaaa87be74566a786 -- 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: Gnome Shell crashed on background upgrade of accountsservice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: Gnome Shell crashed on background upgrade of accountsservice
Hi Daniel, none of the crashes that I had has the same signature as those that are reported on the dup. Furthermore as I outlined the crashes seem to be secondary issues after soemthing breaks and recycles gnome-shell. I'd ask for re-triage as that doesn't seem to be the same thing to me. ** This bug is no longer a duplicate of bug 1843982 Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: Gnome Shell crashed on background upgrade of accountsservice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: Gnome Shell crashed on background upgrade of accountsservice
Another crash just happened: Apr 08 10:28:06 Keschdeichel systemd[1]: Reloading. Apr 08 10:28:06 Keschdeichel systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run> Apr 08 10:28:17 Keschdeichel dbus-daemon[1726352]: [session uid=1000 pid=1726352] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by '> Apr 08 10:28:17 Keschdeichel systemd[10683]: Starting Tracker metadata database store and lookup manager... Apr 08 10:28:17 Keschdeichel dbus-daemon[1726352]: [session uid=1000 pid=1726352] Successfully activated service 'org.freedesktop.Tracker1' Apr 08 10:28:17 Keschdeichel systemd[10683]: Started Tracker metadata database store and lookup manager. Apr 08 10:28:32 Keschdeichel systemd[1]: We couldn't coldplug machine-qemu\x2d4\x2df\x2drtkit.scope, proceeding anyway: Connection timed out Apr 08 10:28:32 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 10:28:32 Keschdeichel avahi-daemon[1726370]: Got SIGTERM, quitting. Apr 08 10:28:32 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 10:28:32 Keschdeichel ModemManager[1727115]: Caught signal, shutting down... Apr 08 10:28:32 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated -- 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: Gnome Shell crashed on background upgrade of accountsservice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] [NEW] Gnome Shell crashed on background upgrade of accountsservice
Public bug reported: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel ModemManager[1308]: Caught signal, shutting down... Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe78:26c2. Apr 08 06:09:19 Keschdeichel systemd[1]: accounts-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group on interface strswanbr2.IPv4 with address 192.168.2.0. Apr 08 06:09:19 Keschdeichel systemd[1]: gdm.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. Apr 08 06:09:19 Keschdeichel
[Bug 1855993] Re: Navit FTBFS - cmake fix needed to work with newer pango
I'm preparing an interim fix for navit to get out of the way of this and less dependent on the cmake fix. We can revert that once cmake is up to date. But sooner or later this should probably be fixed in cmake either with a backport or a move to the 3.16 version that has the change anyway. ** Changed in: pango1.0 (Ubuntu) Status: New => Won't Fix ** Changed in: navit (Ubuntu) Status: New => Triaged ** Changed in: navit (Ubuntu) Assignee: (unassigned) => Christian Ehrhardt (paelzer) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1855993 Title: Navit FTBFS - cmake fix needed to work with newer pango To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1855993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
