** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Changed in: firefox (Ubuntu)
Milestone: None => ubuntu-24.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to devhelp in Ubuntu.
This got a lot worse in noble, it's now not just vertical shift, but the
scaling of the logo too. It is twice as small as the plymouth one.
Or maybe plymouth shows things twice as large?
I don't know how to figure out which one is getting the maths wrong.
--
You received this bug notification
aha! patching gnome-shell does nothing, so we need to patch like yaru-
themes.
and 4% there doesn't work, as if it doesn't compute.
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop
hm setting padding to 4% does not do it.
i am starting to suspect the screen total size is off. by a lot.
--
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/1872594
Title:
Ubuntu
In gnome shell:
Logo is aligned to 1 vertically, and then has margin of 3em
this._logoBin = new St.Widget({
style_class: 'login-dialog-logo-bin',
x_align: Clutter.ActorAlign.CENTER,
y_align: Clutter.ActorAlign.END,
});
.login-dialog-logo-bin {
margin: 3em 0; }
Where as in
in jammy gnome-shell it is:
.login-dialog-logo-bin { padding: 24px 0px; }
--
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/1872594
Title:
Ubuntu logo shifts vertically when the
** Changed in: mutter (Ubuntu)
Status: Confirmed => Incomplete
--
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/1998716
Title:
[raspi] Ubuntu 22.10 does not turn off monitor
Please see https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/2017780
--
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/2006059
Title:
systemd refuses to start
i think this SRU has triggered unexpected failure to start gdm
(potentially unrelated to the content of this sru)
--
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/2006059
Title:
Public bug reported:
gdm was failing to start for me, because smarcard.desktop was missing
I use yubikey for gpg & ssh, and not for "smartcard authentication".
I tried hard to not have any smartcard login on my gdm screen.
I removed /etc/xdg/autostart/org.gnome.SettingsDaemon.Smartcard.desktop
** Also affects: hello (Ubuntu)
Importance: Undecided
Status: New
** Tags added: block-proposed-impish
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Is there anything in particular about all the other packages that you
marked them as affected? I suspect that they all use Ubuntu's provided
tzdata as the source of information, and hence they will all be
reflecting simply whatever tzdata tells them. Hence any changes will be
automatically
The upstream IANA tzdata file format is very restrictive and cannot
change and reflect country codes correctly, across correct historical
dates.
>From "europe" file:
Zone Europe/Simferopol 2:16:24 - LMT 1880
2:16 - SMT 1924 May 2 # Simferopol Mean
** Changed in: wireshark (Ubuntu)
Status: Confirmed => In Progress
--
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
** Changed in: libffi (Ubuntu)
Status: Incomplete => Invalid
--
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
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
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:
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:
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
@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
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
** 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
** 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
Oooh, gsd-keyboard is missing
** Description changed:
- I installed (overwriting an existing partition) from Ubuntu 19.10 "Eoan
- Ermine" - Beta amd64 (20191006) selecting "Language": "en_US" and
- keyboard italian. When i entered the computer name "corrado-p6-ee-1006"
- i see instead
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.
I used BIOS boot, and preseed Esc at the burning-person screen, and
selected Russian option from the language selection.
This way, russian locale is appended to the kernel commandline and upon
live session boot, I expect Russian locale to be selected for
everything, and Russian/English keyboards
** Tags removed: md5sum
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1245534
Title:
gnome archive manager incorrect handling of jar repositories
To manage notifications
** Description changed:
+ [testcase]
+
+ $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995
+ [...]
+ - Status: The certificate is trusted.
+ *** Fatal error: Internal error in memory allocation.
+
+
When Evolution checks my verizon.net account it displays the message
"Error
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
** 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:
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
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
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:
[ 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
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)
@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.
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
** 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
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
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
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
** 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
$ 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
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? =(
--
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
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:
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:
** 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:
** 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
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
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
This affects systemd-fsckd autopkgtest
** Also affects: systemd (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/1748280
Title:
Please do check our configuration first. As far as I can tell, this is
invalid.
Ubuntu Privacy references are located at
https://www.ubuntu.com/legal/dataprivacy
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Bug watch added: github.com/systemd/systemd/issues #9482
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member
An empty match, does not match any interfaces hence none are
configured
What's the output of $ networkctl ? i suspect no interfaces are
maganaged, right?
Note the config mentioned in this bug report looks buggy, and different
from the askubuntu reference - which does appear to have a valid
** Also affects: systemd (Ubuntu Cosmic)
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/1778936
Title:
please re-add
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
Yes, the critical connection is the option to use in this case.
You may also check the leases themselves in /run/systemd/netif/leases
and check if the T1/T2/Lifetime are sensible, with each subsequent one
higher than the prior. And if not, contact your ISP support to correct
those.
** Changed
temd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Also affects: rsyslog (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
D
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Released => Fix Committed
--
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/1766969
Title:
DNS cannot be resolved in Public
Well, on Ubuntu we do not have nss-nis package.
As libnss_nis is shipped in libc6, and thus available everywhere. Thus
adding a depends or a drop-in is a non-starter as well it would be
installed by default everywhere.
I'm not sure if we can somehow detect that it was enabled, and require
nscd
Public bug reported:
I have a lot of errors in my journal of the following form:
ERROR:value_store_frontend.cc(58)] Error while writing
kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
often the same id is reported 2 or 3 times. Many of them are the same
over and over again.
May 21 15:42:17
Public bug reported:
I see the followings errors from gnome-shell on my bionic Desktop:
$ journalctl -b _PID=18271 | grep 'Failed to set'
May 24 13:13:33 sochi gnome-shell[18271]: Failed to set the markup of the actor
'ClutterText': Error on line 1: Entity did not end with a semicolon; most
journald appears to sigabort upon rotating systemd journal file, in
fsync...
#0 0x7f6d47f7c237 in fsync (fd=46) at ../sysdeps/unix/sysv/linux/fsync.c:27
resultvar = 0
sc_cancel_oldtype = 0
sc_ret =
#1 0x7f6d47abf6a0 in fsync_directory_of_file.lto_priv.56 (fd=)
@Daniel van Vugt (vanvugt)
Does pressing Enter causes the system to reboot, after it hangs?
Do you see a plymouth purple screen instructing you to remove
installation media and hit enter?
Do you see a console text message instructing you to "Remove
installation media and reboot" (meaning
Removing systemd, as I believe there is nothing to be changed in systemd
for this fix to land.
Are the affected users fixed with the proposed kernel? Please test
proposed kernel asap! Otherwise the change will be dropped from the
kernel again on xenial =(
** No longer affects: systemd (Ubuntu)
** Also affects: klibc (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Assignee: Seth Forshee (sforshee)
Status: Fix Released
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Description changed:
+ Cherrypick
+
https://github.com/systemd/systemd/commit/3776f9cf00b163eedeb0325691d23df11385cbc5
+
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: Confirmed
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug
** Description changed:
This means that software installed via snap isn't transparently
available for units to use. As snaps are first-class citizens in
Ubuntu, we should update the PATH.
Specifically, this is evident by e.g. $ systemd-run env. Or any other
daemons that spawn shell
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Cosmic)
Status: New => Fix Committed
--
You received this bug notification because you
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug notification
Please provide the contents of /etc/netplan on the affected systems, and
please let me know, if removing files in said directory makes networkd
ignore interfaces.
Please provide output of $ networkctl
By default, if there is no netplan configuration, networkd does not
"force use of
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Assignee: Kai-Heng Feng (kaihengfeng)
Status: Confirmed
** Also affects: linux (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/1767172
Title:
Regression: /etc/modules checked against
*** 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.
>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
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
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
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
/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
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
** 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.
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: 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
--
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
** 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
1 - 100 of 419 matches
Mail list logo
