Since we ruled out netplan, mark it invalid.
Focus on systemd-networkd for now.
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
I identified that systems I spawn as q35 right away work.
Only those where the initial cloud init runs as i440fx and then I change them
to q35 are affected.
I compared configurations and eventually had even my converted instance
running, to the point that it was hard to tell why.
I found that
On those live CDs there should be no NTP daemon running anyway.
And even if so we switched which defaults to non-utc for the following reason:
rtconutc
chronyd assumes by default that the RTC keeps local time (including
any daylight saving changes). This is convenient on PCs
Public bug reported:
Hi,
I miss some hidden trigger of "netplan apply" to understand the following case.
I have kvm guests, you can spawn your own one to reproduce via:
$ uvt-simplestreams-libvirt --verbose sync --source
http://cloud-images.ubuntu.com/daily arch=amd64 release=bionic
Hi,
first of all I beg your pardon - while I'm just the one cleaning old bugs - it
is bad that you had to wait so long.
Now lets get to your case...
This is a mix of systemd and ifup based network ocnfiguration, and in
Artful a lot of this was still in flight.
In Bionic there is a simplified
FYI
NMAP
Started to consider pcre2 due to the bug, but they have zillions of regrex use
cases and it would be a major effort that doesn't seem to happen anytime soon.
Freeradius implemented pcre2 due to our bug in
I just found that further calls to
$ sudo systemctl restart gdm
Seem to alternate between good/bad state.
Here is the log of one such bad restarts:
http://paste.ubuntu.com/p/Dx7Sk3wDyx/
OTOH, the service could just in general not be restarable - so take this
with a grain of salt
--
You
I have found this to be locally reproducible with:
$ autopkgtest --shell-fail --apt-upgrade --no-built-binaries
--testname=boot-and-services
--apt-pocket=proposed=src:systemd,src:dbus,src:iproute2,src:glibc
systemd_239-7ubuntu6.dsc -- qemu --qemu-options='-cpu host'
...ubuntu7 completed tonight thanks!
I tested 2 times from proposed in the local tester and working as expected now.
Unfortunately the systemd upload itself failed at some of the flaky
(boot and smoke) tests. But it seemed more like the VM it ran in would
be dead.
I retriggered the 4 tests
@Daniel: the latest gdm even in proposed that Dimitri and I can easily
try is currently 3.29.91-1ubuntu2
--
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/1790478
Title:
gdm3 in cosmic
Summarizing the Server Team related task status for a better overview.
For postfix a discussion existed, and they seem not to have any better tracker
set up.
For the others I reported new issues upstream, so that they are aware and we
have something to track.
I listed those new ones after
** Summary changed:
- demotion of pcre3 in favor of pcre2
+ demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Also affects: php7.3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: php7.3 (Ubuntu)
Status: New => Triaged
** Changed in:
Public bug reported:
Auth from phone, will update description after reboot
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.3-0ubuntu18.04.3
ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode
** Description changed:
- Auth from phone, will update description after reboot
+ For two days in a row (one would have been a one-off WTF that I don't
+ care to report) my system now hang after unlocking from the UI.
+
+ I can't see any obvious hanging processes that would be the obvious
+
** Attachment added: "'systemctl status --all' while hanging"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1813248/+attachment/5232401/+files/screenlock-hang-services.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3
** Attachment added: "Photo of UI while hanging"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1813248/+attachment/5232403/+files/IMG_20190125_065748248.jpg
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Attachment added: "Full journal output while hanging"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1813248/+attachment/5232402/+files/screenlock-hang-journal.txt.gz
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
** Description changed:
[Impact]
The so called "browsing a windows network" made use of an SMB1 protocol
version feature. Recent versions of samba, including the one released with
bionic, default to a higher versions of the protocol which lacks this feature.
As a result, the "other
The Dup 1667113 had tracked some more affected packages - since all are
dupped on this bug here let me add those tasks here so that all
component owners are aware.
** Also affects: ceph (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ifmail (Ubuntu)
Importance: Undecided
*** This bug is a duplicate of bug 1597439 ***
https://bugs.launchpad.net/bugs/1597439
Thanks Andreas, also I now have taken a look at the demotion.
The only reason to demote is was that the need from unity to pull it in went
away.
There was no explicit demotion reason filed.
Therefore we
Hi Daniel, thanks for taking a look.
#1 the WIFI crash is known (bug 1804841) and much worse with the 4.15 kernel
I'm not actively using WIFI atm due to that, it is just NM trying to configure
it as fallback.
But all networking goes via Wire
#3 I handled, that was a while before the issues and
** Also affects: gnome-keyring (Ubuntu)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
We checked what actually is the backend that the "ssh-add -c" is trying to
reach.
First we thought that should be the ssh-agent spawned for gnome-keyring-daemon
[1]
In PS that is visible as:
1 1000 4029 1 20 0 656132 15860 - SLl ? 0:24
/usr/bin/gnome-keyring-daemon
Since removing
- gnome-shell-extension-multi-monitors
- gnome-shell-extension-system-monitor
The issue is no more triggering.
Thanks as it resolved my issue.
I'm not sure if we can do much more, lets keep it incomplete
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1812247
Title:
ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
To
Public bug reported:
[Availability]
zeromq3 exists in Universe already. Current version in disco is 4.2.5-2 and it
builds in amd64, arm64, armhf, i386, ppc64el, s390x.
It produces two binary packages: a library runtime, and its corresponding
development package. We need the runtime libzmq5 in
Hi Luke,
thanks for the bug report and your help to make Ubuntu better.
I'm unsure what ssh could/should do differently in this case.
For similar issues there was a gnome PR [1] that went into gnome that should
allow a "yes and remember" kind of use-case. Not sure if that is missing in the
Added a pango1.0 task for awareness
--
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:
FTBFS in focal blocking gpsd transition for libgps25
To manage notifications
navit actually just naively includes and the error pups up
much below that.
It has #define GDK_ENABLE_BROKEN might that be related?
Build dep is:
libgtk2.0-dev
Which brings in:
libpango1.0-dev | 1.44.7-1 | focal | amd64, arm64, armhf,
i386, ppc64el, s390x
And that has
This is in Focal, lets close the bug
pango1.0 | 1.44.7-1 | focal | source
** Changed in: pango1.0 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pango1.0 in
navit last time built fine in Eoan on 2019-09-10
Comparing the environments between late Eoan and Focal...
The Eoan version of pango-coverage.h doesn't have the include that is
failing me.
** Bug watch added: gitlab.kitware.com/cmake/cmake/issues #19531
#ubuntu-desktop was helpful:
[11:29] cpaelzer, hey, it's
https://gitlab.kitware.com/cmake/cmake/issues/19531
[11:29] RikMills, ^
[11:29] cpaelzer, we talked about it on friday on #ubuntu-release, we
should backport that patch to cmake
--
You received this bug notification because you are a
** Also affects: cmake (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cmake (Ubuntu)
Assignee: (unassigned) => Rik Mills (rikmills)
** Changed in: cmake (Ubuntu)
Status: New => Triaged
** Description changed:
+ A change in Pango [1] broke builds using GTK2 as
.
** 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 Ubunt
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
> 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
@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
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
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
> 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:
> 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
> 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
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.
**
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
** 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
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
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
*** 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
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"
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
*** 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
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
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
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
-
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
@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
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.
** 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
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
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
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
[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.
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
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% =>
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.
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
[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
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
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
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
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.
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
** 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
** 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
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
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
** 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
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
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:
** 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
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
** 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.
** 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
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.
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.
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?
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
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.
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
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.
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.
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
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
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
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
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
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
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
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
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.
1 - 100 of 133 matches
Mail list logo
