I believe this is systemd intentional to not change bond parameters if
the bond already exists. It is assumed that something else has already
created the bond, and thus networkd should not be "updating" the params.
Despite networkd creating the bond in the first place...
** Changed in: systemd
I see more chatter about journald aborting upstream and on the mailing
lists. Imho, just because journald was not scheduled to run kind of
means that maybe it has too low of a priority, or the system is
overloaded. It does not show that journald is actually at fault here,
and/or failing. Imho, one
v231 networkd changes have been introduced in xenial long time ago, and
the referenced patch appears to have been in xenial's networkd for a
long while now.
If this bug is not resolved for you, please reopen it.
** Changed in: systemd (Ubuntu Xenial)
Status: In Progress => Fix Released
** Changed in: systemd (Ubuntu Zesty)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu Zesty)
Status: Confirmed => Won't Fix
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu Zesty)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
** Changed in: systemd (Ubuntu Zesty)
Status: Confirmed => Won't Fix
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Artful)
Status: Confirmed => In Progress
--
You received this bug notification because you are a
Public bug reported:
[Impact]
In artful, there are autopkgtest failures that can be improved/fixed
with the following commits:
* stop using ext3, and instead use ext4 as fsck.ext3 may be missing in
the initramfs.
* correctly parse prefixes, when parsing units and deciding which
binaries to
** Changed in: systemd (Ubuntu Zesty)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Xenial)
Status: New => Invalid
** Changed in: systemd (Ubuntu Artful)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Changed in: systemd (Ubuntu Zesty)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1736955
Title:
dep8 test systemd-fsckd fails on s390
To
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1746765
Title:
systemd FTBFS on arm64
To manage
Public bug reported:
TEST-16-EXTEND-TIMEOUT
started to fail, in a nested qemu VM for the casess success_all &
success_start
sed -i 's/wait_for success_all/# wait_for success_all/'
test/TEST-16-EXTEND-TIMEOUT/assess.sh
sed -i 's/wait_for success_start/# wait_for success_start/'
this is actually not true, as they got re-disabled.
** Changed in: systemd (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1749540
There appears to be an init.d scripts loop between cups & plymouth
** Also affects: cups (Ubuntu)
Importance: Undecided
Status: New
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Proposed fix in systemd. Run systemd-tmpfiles, during postinst, the way
it would be run on boot, such that all base files are correct, including
any overrides shipped by any other package; systemd; in transient
runtime dir.
At the same time, the dh_installinit is silenced to not produce the
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** No longer affects: ubuntu-z-systems
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1784454
Title:
kernel panic
13: if [ -f /sys/module/scsi_mod/parameters/scan ]; then
14:echo sync > /sys/module/scsi_mod/parameters/scan
15: fi
Not sure how come the file is there, yet "cannot be created" when we try
to echo into it... maybe it's not writable or disappears.
I think the quickest botch that i can think
** Changed in: gnome-session (Ubuntu)
Importance: Undecided => Critical
** Tags added: rls-cc-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1787748
Title:
Public bug reported:
$ lxc launch images:debian/sid test-dynamicusers
$ lxc exec test-dynamicusers bash
$ systemd-run --unit=testdynamic -p DynamicUser=yes --uid=xnox /bin/true
$ systemctl status testdynamic.service
# systemctl status testdynamic.service
● testdynamic.service - /bin/true
Public bug reported:
== test-sleep ===
Hibernation configured and possible: no
Hybrid-sleep configured and possible: no
Suspend-then-Hibernate configured and possible: no
Unable to read extent map for '/usr/lib/systemd/tests/test-sleep':
Inappropriate ioctl for device
Assertion
Public bug reported:
systemd in cosmic should not migrate until apparmor abstract socket
locks mediation is fixed
See https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: block-proposed
--
You
** Changed in: systemd (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.
https://bugs.launchpad.net/bugs/1727825
Title:
networkd DHCP immediately drops lease ( on igbx cards )
Fixed upstream in
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=e91f1a7d2a6b8400b6b331d5b72287dcb5164a39
** Summary changed:
- dns resolution only works for domains in 'search'.
+ NetworkManager incorrectly uses resolved' route-only DNS setting, resulting
in dns
There are relative and maximum caps set. So at the moment you clearly show that
these maximum caps are respected.
Please reopen, if you can reproduce the case when the reported max caps on your
system are breached. As in, journals are bigger than the the 'max '
setting as calculated by journal
/var/log/systemd is not a path used by systemd
Could you please paste the output of:
$ journalctl -b -u systemd-journald.service | grep max
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
** Changed in: systemd (Ubuntu)
Status: Invalid => Incomplete
--
You
pcre2 library is not in Ubuntu Main, and therefore cannot be used, at
runtime, by such a core package as systemd.
once pcre2 is available in main, and thus has full Ubuntu Security
support, I will be able to enable pattern matching support.
** Also affects: pcre2 (Ubuntu)
Importance:
Public bug reported:
it seems like gnome-shell; or something that calls into gnome-shell;
have trouble with sqlite:
journalctl -b -e | grep -e gnome-shell -e org.gnome.Shell.desktop | grep
sqlite
has a lot of:
org.gnome.Shell.desktop[24475]:
** Also affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1748147
Title:
Upgrading systemd sets incorrect
** Package changed: systemd (Ubuntu) => ubuntu-meta (Ubuntu)
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Fix Committed
** Changed in: ubuntu-meta (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are
This is desktop policy decision that a logged in user can shut down the
machine, this is expected behavior, and that's how / why clicking the
power button in top right corner -> shutdown icon works. Ditto long
clicking that shutdown icon works to suspend the machine too.
Being physical user on
** Summary changed:
- I/O Error after clicking "reboot now"
+ I/O Error after clicking "reboot now" - Ubuntu font missing from casper
shutdown
** Also affects: casper (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
**
This has totally slipped my radar, I'm sorry.
I will ensure this lands into bionic 18.04.0.
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-18.04
** Also affects: systemd (Ubuntu
@superm1
It would have been nice to coordinate systemd uploads, this is by far,
not the only patch set that needs uploading for systemd.
** Tags added: block-proposed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
@rrs
> BTW, does Ubuntu have the systemd/udevd mount propagation fix included ?
yes no maybe =
Added in debian at ed16ca8690eb69c248a0a741def5324eedc9149d
Removed from debian at d529d047752d8492d43e42e8b4223d6d37fa3dd3
Meaning it was for a while, if you mean the Debian bug linked to this bug
** Package changed: ubuntu => networkd-dispatcher (Ubuntu)
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Committed
** Changed in: networkd-dispatcher (Ubuntu)
Status: Triaged => Fix Released
--
May I backtrack a bit, and ask how is this system configured? And is it
a desktop or a server configuration? Is it a fresh install or an
upgrade?
Specifically, what I am confused about is how the networking is
configured and where /etc/resolv.conf is pointing at.
I see that NetworkManager and
** Package changed: systemd (Ubuntu) => resolvconf (Ubuntu)
** Changed in: resolvconf (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
** Also affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in: rsyslog (Ubuntu)
Status: New => Confirmed
** Changed in: rsyslog (Ubuntu)
Importance: Undecided => High
** Changed in: rsyslog
resolvconf (1.79ubuntu10) bionic; urgency=medium
* Fix race of not injecting resolved config into resolvconf on LXD
container boot. LP: #1763108
-- Dimitri John Ledkov <x...@ubuntu.com> Thu, 12 Apr 2018 12:46:24
+0100
** Changed in: systemd (Ubuntu Bionic)
Status: Triaged
/etc/systemd/netword/uplink0.link
that's invalid path, no?
/etc/systemd/network/ is the right path, and should work.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
in summary the consensus is as follows:
- cloud-init should not provide accept-ra key to netplan.io
- netplan.io should not emit any accept-ra keys to networkd
- networkd, when not receiving any accept-ra keys should use kernel implicit
default
- networkd, when in implicit RA mode, should not
ged in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-18.04
** Changed in: debian-installer (Ubuntu)
Milestone: later => ubuntu
>From dist-upgrade logs:
2018-04-23 09:04:43,230 ERROR got error from PostInstallScript
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to
execute child process "./xorg_fix_proprietary.py" (No such file or directory)
(8))
>From journal:
screensaver is broken?
Apr 23 14:17:10 ubuntu
Package: rsyslog 8.16.0-1ubuntu10
Package out of date, please upgrade, and check if it resolves the
problem you report...
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Changed in: rsyslog (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
*** This bug is a duplicate of bug 1765803 ***
https://bugs.launchpad.net/bugs/1765803
Can you please attach the tarball of /var/log/installer?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in Ubuntu.
Removing systemd task, as the fixes are only needed in the rsyslog
package w.r.t. permissions used.
** No longer affects: systemd (Ubuntu Bionic)
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
systemd upgrades are now failing in my build chroots, and I suspect it
is related to this change.
Setting up systemd (234-2ubuntu12.3) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
[/usr/lib/tmpfiles.d/tmp.conf:15] Failed to replace
Opened from
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/comments/40
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in
During installation 'ubuntu-desktop' was selected, and is still
installed.
Thus this is a desktop system, and looks like it behaves correctly for a
desktop system.
If you wish to configure your desktop differently please see System
preferences -> power -> Suspend & Power Button -> Automatic
Ubiquity should not be booting anymore awaiting network configuration
(i.e. systemd-networkd-wait-online is not enabled). Is there anything
else to do for this bug report?
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => Incomplete
--
You received this bug notification because
@mdeslaur there is polari, which is gtk3 and wayland compatible.
Note that we are not using wayland by default in 18.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/1758163
>From systemd point of view, the patches are relatively straight forward,
and simply add "one more way to sleep/suspend/hybernate/etc" without
affecting any other code paths or any other functionality. Thus i see
little risk for landing the systemd patches.
If this turns out to be bad, only the
I am confused about the original statement "Ubiquity then have proposed
to set an encrypted swap dir" because ubiquity does not propose to do
such things at all.
By default we do not create swap partitions, in the full disk encryption
case we use LVM and encrypt the whole VG which contains swap
** Changed in: systemd (Ubuntu Artful)
Status: New => In Progress
** Changed in: systemd (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.
@vanvugt
@mc3man
This bug was specifically about the Ubuntu Desktop Installer, and the
experience one has with it.
Are you experiencing something similar, on the installed system, after
the installation is done and you use Ubuntu normally? In that case
that's a separate issue. Please open a new
Ok, reading more carefully it looks like udevadm is failing, when called
by netplan.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
I've tried to reproduce this, and failed...
$ sudo debootstrap --include=systemd bionic bionic
...
$ ls -lnatr bionic/var/log/ | grep journal
drwxr-sr-x+ 2 0 101 4096 Mar 16 18:23 journal
So fresh installation of systemd works as expected.
I guess we need to trace where/what/why certain
: livecd-rootfs (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: Invalid
** Also affects: livecd-rootfs (Ubuntu Xenial)
Importance: Undecided
Status: New
** Description changed:
When trying to add another interface for a QETH device on a s390x system
netplan apply fails:
sudo netplan apply
Cannot replug encc003: [Errno 19] No such device
Traceback (most recent call last):
File "/usr/sbin/netplan", line 23, in
netplan.main()
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: Confirmed
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu Bionic)
Milestone: None => ubuntu-18.03
--
You received th
nassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu Artful)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.n
I guess this is also preventing upgrades in Windows WSL.
** Also affects: systemd (Ubuntu Bionic)
Importance: Medium
Status: Triaged
** Changed in: systemd (Ubuntu Bionic)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu Bionic)
Milest
To launch the deb I use $ /usr/bin/gnome-system-monitor, from a gnome-
terminal.
After a reboot, deb works, snap doesn't.
List of interfaces http://paste.ubuntu.com/p/qxcMzGY8PF/
I do get denies http://paste.ubuntu.com/p/cJhj7rCvZB/
Is my system somehow misconfigured / not stock? =(
--
$ snap version
snap2.35.5+18.10
snapd 2.35.5+18.10
series 16
ubuntu 18.10
kernel 4.18.0-10-generic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1798996
looks like .deb is bad too.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1798996
Title:
Cannot use it at all...
To manage notifications about this bug go to:
Public bug reported:
$ gnome-system-monitor
cannot perform readlinkat() on the mount namespace file descriptor of the init
process: Permission denied
And it does not start at all.
** Affects: gnome-system-monitor (Ubuntu)
Importance: Critical
Status: Confirmed
** Tags:
the deb can be started as root, be previously it would work as non-root
too.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1798996
Title:
Cannot use it at all...
To
systemd-shim removed from the archive, so cannot be fixed really.
** Changed in: systemd-shim (Ubuntu Bionic)
Status: Confirmed => Won't Fix
** Changed in: systemd-shim (Ubuntu)
Status: Incomplete => Won't Fix
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
sufficiently large swapfile should be enough, as systemd has support to
hibernate to a file offset.
However, none-the-less, I did not manage to resume off that myself yet.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
In systemd package for a while, there is a boot-and-services test case,
which tries to install common/typical things and ensure they continue to
operate with new systemd.
One of the test cases is gdm3. The test case dependencies are:
Tests: boot-and-services
Depends:
** Also affects: gnome-terminal (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: gnome-terminal (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd
I wonder if we should change the packaging of tzdata to always build the
stuff that icu needs/wants. Such that an update of tzdata ripples
through to icu as well. Somehow.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or
local configuration.
As far as I recall, I should be running just "stock" configs.
I did not install system with disco, but upgraded to disco throughout
development series.
Upon booting, and logging
I also have recently added a second, non-admin, user account on the
system using the gnome control centre. Such that on the gdm3 login
screen I need to select which account I am logging into.
Not sure if this is relevant or not.
** Tags added: release-dd-incoming
--
You received this bug
This is still not fixed.
** Changed in: systemd (Ubuntu)
Status: Fix Released => Confirmed
--
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/1803993
Title:
Password appears on
** Description changed:
With the new eoan wallpaper it is obvious that calendar widget, is not
in fact, centered on the screen. Nor is like left/right aligned to the
centre either.
- It feels as if it is centered, between "right edge of the app menu" and
- "left edge of the top right
With help from willcooke, it seems that the dock pushes the calendar to
be centered on the space between the dock right edge and the right edge
of the screen, when dock has "auto-hide" setting turned off.
With auto-hide on, calendar widget is correctly centered.
--
You received this bug
Public bug reported:
With the new eoan wallpaper it is obvious that calendar widget, is not
in fact, centered on the screen. Nor is like left/right aligned to the
centre either.
It feels as if it is centered, with an offset / margin on the left.
between "right edge of the app menu" and "left
@laney
in that case the wallpaper background should too be centered and zoomed
on the 'content area', especially if such concept / area exists.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://launchpadlibrarian.net/456587485/buildlog_ubuntu-focal-
amd64.linphone_3.12.0-3.1_BUILDING.txt.gz
** Also affects: cmake (Ubuntu)
Importance: Undecided
Status: New
** Also affects: harfbuzz (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linphone (Ubuntu)
Public bug reported:
[ 75%] Building C object gtk/CMakeFiles/linphone-gtk.dir/audio_assistant.c.o
cd /<>/obj-x86_64-linux-gnu/gtk && /usr/bin/cc -DBCTBX_STATIC
-DBELCARD_STATIC -DBELLESIP_STATIC -DBELR_STATIC -DBZRTP_STATIC -DHAVE_CONFIG_H
-DLINPHONE_EXPORTS -DLINPHONE_STATIC -DMS2_STATIC
cmake was uploaded to fix it all
** Changed in: pango1.0 (Ubuntu)
Status: New => Invalid
** Changed in: linphone (Ubuntu)
Status: New => Invalid
** Changed in: harfbuzz (Ubuntu)
Status: New => Invalid
** Changed in: cmake (Ubuntu)
Status: New => Invalid
--
You
Public bug reported:
spinner theme flickers Ubuntu logo on gdm transition
At the end of boot, spinner disappears and Ubuntu logo remains 100%
opacity white on screen.
Then GDM starts, and performs a fade-in animation of background
gradient, and fade-ins Ubuntu logo.
This results in visual
I'm not sure that will work, when browsers are shipped as a snap.
Does this package work with chromium as a snap?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1866841
Title:
Add
** Also affects: gnome-calculator (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1868409
Title:
gtk2 and python2 are obsolete.
... and so is anything that uses them.
virtaal in focal uses gtk3 and python3, and does not depend on python-
glade2.
The rest are not shipped in focal.
How or why did you generate this list?
Ubuntu ships modern, maintained software, that is security
All tests run automatically, and yes flatpak-builder was automatically
tested and new flatpak with this fix migrated fine.
See http://autopkgtest.ubuntu.com/packages/flatpak-builder/groovy/s390x
** Also affects: flatpak (Ubuntu)
Importance: Undecided
Status: New
** Changed in: flatpak
Hm, so is desktop working on this? Have we figured out at all what is
happening? Or just the general symptoms that dbus seems to be non-
responsive and then everything goes bad?
** Changed in: dbus (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: dbus (Ubuntu Focal)
Status:
@satmandu
Thank you for pointing that documentation out.
It is correct that it is helpful to test Proposed, but I think that
information was written when packages in proposed were only published
for stable series, which only contain prospective Stable Release
Updates, and is the way "for testing
also using groovy-proposed is not supported, as it contains incompatible
mix of packages.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1892915
Title:
gnome-shell crashing
The deps are now out of date. At least mozjs68 has now moved.
--
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/1892915
Title:
gnome-shell crashing (libffi8ubuntu1 upgrade issue)
We could use gfxpalyload blacklist, to mark certain nvidia cards there.
And then gfxpayload will not be set to keep, and then vt.handoff will
not be appended.
See grub-gfxpayload-lists package, and files in /usr/share/grub-
gfxpayload-lists/blacklist/
My current preference would be the gdm3 fix.
However dropping vt.handoff is not regression free it may impact
flavours that use lightdm.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic
Public bug reported:
-- Logs begin at Tue 2020-10-20 17:36:53 UTC, end at Tue 2020-10-20 18:01:10
UTC. --
Oct 20 17:47:52 ubuntu systemd[1]: Starting GNOME Display Manager...
Oct 20 17:47:53 ubuntu systemd[1]: Started GNOME Display Manager.
Oct 20 17:47:55 ubuntu gdm-autologin][4267]: gkr-pam:
however that is old 19.1 iso
** Changed in: gdm3 (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/1900754
Title:
gdm is having crashes in
tah.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1890619
Title:
poppler fails to build on s390x with gcc10 due to symbols changes
To manage notifications about this bug go to:
Ubuntu no longer uses vt.handover and it should not be specified at all
anymore.
We boot directly to tty1, always and everywhere, and we should not be
setting that at all.
Thus a patch changing that from 7 to 1 is not a good idea for focal+.
And I can't quite remember which releases we have
** Also affects: pam (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rls-gg-incoming
--
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/1865226
Title:
gdm3 fails to
** Changed in: pam (Ubuntu)
Status: New => Invalid
--
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/1865226
Title:
gdm-smartcard pam config needs to be updated for Ubuntu and
However, ubiquity.json gnome-shell mode does have:
"right": ["a11y", "keyboard", "aggregateMenu"]
i wonder why it doesn't show up.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
301 - 400 of 419 matches
Mail list logo
