[Bug 1998716] Re: [raspi] Ubuntu 22.10 does not turn off monitor
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1998716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872594] Re: Ubuntu logo shifts vertically when the login screen appears
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 login screen appears
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872594/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872594] Re: Ubuntu logo shifts vertically when the login screen appears
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 plymouth the Watermark has vertical alignment of
themes/bgrt/bgrt.plymouth.desktop:WatermarkVerticalAlignment=.96
view->watermark_area.y = screen_height * plugin->watermark_vertical_alignment -
ply_image_get_height (plugin->watermark_image) *
plugin->watermark_vertical_alignment;
Which means the margin in plymouth is 4% of screen height.
So one way to fix this is to make plymouth know what "3em" is and calculate
that.
Or to teach gnome-shell to use 4% margin of the total screen.
I am going to try to do the latter.
--
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 login screen appears
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872594/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872594] Re: Ubuntu logo shifts vertically when the login screen appears
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 logo shifts vertically when the login screen appears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872594] Re: Ubuntu logo shifts vertically when the login screen appears
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 Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872594 Title: Ubuntu logo shifts vertically when the login screen appears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1872594] Re: Ubuntu logo shifts vertically when the login screen appears
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 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 login screen appears To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1872594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** 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. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1245534] Re: gnome archive manager incorrect handling of jar repositories
** 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1245534/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847307] Re: Install in english with italian keyboard - keyboard not set during install
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 available. Booting into "only-ubiquity" mode, keyboard selection indicator is missing and pressing "super+space" doesn't change keyboard layout either. If on the other hand I boot into full live session, I see that there is keyboard selection indicator and I can change keyboard layouts with "super+space". It seems like "keyboard-indicator" is missing from the "maybe-ubiquity /only-ubiquity" ubiquity-dm session. ** Changed in: ubiquity (Ubuntu) Status: Incomplete => Triaged ** Changed in: ubiquity (Ubuntu Focal) Status: Incomplete => Triaged ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Install in english with italian keyboard - keyboard not set during install + ubiquity-dm (maybe-ubiquity/only-ubiquity) missing keyboard indicator, when booted into Esc, Russian locale by default from isolinux BIOS boot -- 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/1847307 Title: ubiquity-dm (maybe-ubiquity/only-ubiquity) missing keyboard indicator, when booted into Esc, Russian locale by default from isolinux BIOS boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847307] Re: ubiquity-dm (maybe-ubiquity/only-ubiquity) missing keyboard indicator, when booted into Esc, Russian locale by default from isolinux BIOS boot
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. https://bugs.launchpad.net/bugs/1847307 Title: ubiquity-dm (maybe-ubiquity/only-ubiquity) missing keyboard indicator, when booted into Esc, Russian locale by default from isolinux BIOS boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1847307] Re: ubiquity-dm (maybe-ubiquity/only-ubiquity) missing keyboard indicator, when booted into Esc, Russian locale by default from isolinux BIOS boot
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 "corrado/p6/ee/1006" because the installer uses the US
- keyboard so i was forced to enter the computer name considering i have
- an US keyboard
+ [Impact]
+
+ * In ubiquity-dm (aka "maybe-ubiquity" or "only-ubiquity" modes) the
+ keyboard indicator is not shown. Thus users cannot change keyboard
+ layouts to input fields in various languages.
+
+ [Test Case]
+
+ * Boot installer in Russian language, i.e. only-ubiquity --- debian-
+ installer/language=ru keyboard-configuration/layoutcode?=ru
+
+ * Observe that the installer boots into Russian language by default
+
+ * Observe that in the top right corner there is a keyboard layout
+ indicator drop down, and it contains "en" and "ru" layouts.
+
+ [Regression Potential]
+
+ * Starting additional service during minimal ubiquity-dm will increase
+ slightly cpu/ram usage. However, it should still be well within the
+ declared RAM requirements.
+
+ [Other Info]
+
+ * Original bug report
+
+
+ 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
"corrado/p6/ee/1006" because the installer uses the US keyboard so i was forced
to enter the computer name considering i have an US keyboard
{"Media": "Ubuntu 19.10 \"Eoan Ermine\" - Beta amd64 (20191006)",
"Type": "GTK", "OEM": false, "PartitionMethod": "manual",
"DownloadUpdates": true, "Language": "en", "Minimal": false,
"RestrictedAddons": true, "Stages": {"0": "language", "1": "language",
"5": "console_setup", "11": "console_setup", "19": "prepare", "130":
"partman", "136": "partman", "142": "partman", "166": "partman", "172":
"partman", "178": "timezone", "182": "usersetup", "253": "user_done",
"815": "done"}}
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 8 18:25:48 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
only-ubiquity quiet splash ---
InstallationDate: Installed on 2019-10-08 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191006)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
** No longer affects: gnome-shell (Ubuntu)
** No longer affects: gnome-shell (Ubuntu Focal)
** Changed in: ubiquity (Ubuntu)
Assignee: Łukasz Zemczak (sil2100) => (unassigned)
** Changed in: ubiquity (Ubuntu Focal)
Assignee: Łukasz Zemczak (sil2100) => (unassigned)
--
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/1847307
Title:
ubiquity-dm (maybe-ubiquity/only-ubiquity) missing keyboard indicator,
when booted into Esc, Russian locale by default from isolinux BIOS
boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847307/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865226] Re: gdm3 fails to install /etc/pam.d/gdm-smartcard
** 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 install /etc/pam.d/gdm-smartcard To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** 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 installed To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
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 to booting to tty1 by default. Maybe it was bionic, or between xenial and bionic? -- 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 login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890619] Re: poppler fails to build on s390x with gcc10 due to symbols changes
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: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1890619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
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 login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
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. And migrate the rest of the login managers to tty1 too. -- 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 login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)
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 (libffi8ubuntu1 upgrade issue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)
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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)
@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 updates". That is not true for devel series. In devel series, -proposed is not for human consumption. Instead simply running devel series, release pocket is already testing and providing feedback from such config is useful. I'm not sure how we can update that testing page to be more informative. -- 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1886814] Re: posix_spawn usage in gnu make causes failures on s390x
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 (Ubuntu) Status: New => Fix Released ** Changed in: glibc (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: make-dfsg (Ubuntu) Status: New => 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/1886814 Title: posix_spawn usage in gnu make causes failures on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1886814/+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
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: Confirmed => Incomplete -- 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 1900754] [NEW] gdm is having crashes in livesession?
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: no password is available for user Oct 20 17:47:55 ubuntu gdm-autologin][4267]: pam_unix(gdm-autologin:session): session opened for user ubuntu by (uid=0) Oct 20 17:47:55 ubuntu gdm-autologin][4267]: gkr-pam: couldn't unlock the login keyring. Oct 20 17:57:58 ubuntu gdm-launch-environment][5298]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Oct 20 17:59:41 ubuntu systemd[1]: Stopping GNOME Display Manager... Oct 20 17:59:46 ubuntu gdm3[4257]: Gdm: GdmCommon: process (pid:4267, command 'gdm-session-worker [pam/gdm-autologin]') isn't dying after 5 seconds, now ignoring it. Oct 20 17:59:51 ubuntu gdm3[4257]: Gdm: GdmCommon: process (pid:5298, command 'gdm-session-worker [pam/gdm-launch-environment]') isn't dying after 5 seconds, now ignoring it. Oct 20 17:59:53 ubuntu gdm3[4257]: GLib: g_hash_table_foreach: assertion 'version == hash_table->version' failed Oct 20 17:59:53 ubuntu systemd[1]: gdm.service: Succeeded. Oct 20 17:59:53 ubuntu systemd[1]: Stopped GNOME Display Manager. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- 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 livesession? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1900754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1900754] Re: gdm is having crashes in livesession?
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 livesession? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1900754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)
** 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 issue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1892915/+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
** 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 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 1920987] Re: Europe/Simferopol, Crimea is RUSSIA
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 T 2:00 - EET 1930 Jun 21 3:00 - MSK 1941 Nov 1:00 C-Eur CE%sT 1944 Apr 13 3:00 Russia MSK/MSD 1990 3:00 - MSK 1990 Jul 1 2:00 2:00 - EET 1992 # Central Crimea used Moscow time 1994/1997. # # From Paul Eggert (2006-03-22): # The _Economist_ (1994-05-28, p 45) reports that central Crimea switched # from Kiev to Moscow time sometime after the January 1994 elections. # Shanks (1999) says "date of change uncertain", but implies that it happened # sometime between the 1994 DST switches. Shanks & Pottenger simply say # 1994-09-25 03:00, but that can't be right. For now, guess it # changed in May. 2:00 E-Eur EE%sT 1994 May # From IATA SSIM (1994/1997), which also says that Kerch is still like Kiev. 3:00 E-Eur MSK/MSD 1996 Mar 31 0:00s 3:00 1:00MSD 1996 Oct 27 3:00s # IATA SSIM (1997-09) says Crimea switched to EET/EEST. # Assume it happened in March by not changing the clocks. 3:00 Russia MSK/MSD 1997 3:00 - MSK 1997 Mar lastSun 1:00u # From Alexander Krivenyshev (2014-03-17): # time change at 2:00 (2am) on March 30, 2014 # https://vz.ru/news/2014/3/17/677464.html # From Paul Eggert (2014-03-30): # Simferopol and Sevastopol reportedly changed their central town clocks # late the previous day, but this appears to have been ceremonial # and the discrepancies are small enough to not worry about. 2:00 EU EE%sT 2014 Mar 30 2:00 4:00 - MSK 2014 Oct 26 2:00s 3:00 - MSK The above defines which timezone was used when in Crimea. But the mapping from Europe/Simferopol => country code [UA,RU] as appropriate for a given time period is not possible in the zone.tab file. Hence it currently stayed with: ./zone.tab:UA +4457+03406 Europe/Simferopol Crimea There is a newer format in zone1970.tab file which says: ./zone1970.tab:RU,UA+4457+03406 Europe/Simferopol Crimea But that is not helpful, as it lists two countries. And it still doesn't map country codes to the correct time periods. It almost feels like we either need a new country code for Crimea to explain that depending which year one is in, it should be one or the other country code. Or we need to extend the zore1970.tab format similar to the file format of europe format such that country codes can be specified for every relevant time period. So to get where you want to be, IANA needs to create a new tzdata format and for everyone to switch to it. I guess that would need to be requested via Discussions mailing list at IANA - see https://www.iana.org/time-zones There is nothing in particular that Ubuntu can do to fix tzdata. As disagreement across other users of tzdata across the network can introduce interoperability bugs. My only recommendation is to use Europe/Kiev or Europe/Moscow zones, which have the correct country code mappings for the most recent decades. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1920987 Title: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1920987/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1920987] Re: Europe/Simferopol, Crimea is RUSSIA
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 reflected in them, if and when, tzdata is improved. Would it be ok to close all the other tasks, whilst keeping tzdata one open? ** Summary changed: - Europe/Simferopol,Crimea is RUSSIA + IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ] ** No longer affects: ayatana-indicator-datetime (Ubuntu) ** No longer affects: evolution-ews (Ubuntu) ** No longer affects: gnome-clocks (Ubuntu) ** No longer affects: gnome-control-center (Ubuntu) ** No longer affects: libgweather (Ubuntu) ** No longer affects: liblangtag (Ubuntu) ** No longer affects: mate-control-center (Ubuntu) ** No longer affects: mate-panel (Ubuntu) ** No longer affects: publicsuffix (Ubuntu) ** Changed in: tzdata (Ubuntu) Importance: Undecided => Wishlist ** Changed in: tzdata (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1920987 Title: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1920987/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1923845] Re: Please compress packages with zstd by default
** 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 Title: Please compress packages with zstd by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1923845/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1803993] Re: Password appears on the VT1 screen
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 the VT1 screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843899] [NEW] gnome-shell calendar widget is not centered on the screen
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 edge of the top right indicators", instead of centered to the screen width.The blue line on the screenshot is the centre fold of the screen, you can see that the wallpaper is correctly centered with the animal circle in the centre. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gnome-shell-calendar.png" https://bugs.launchpad.net/bugs/1843899/+attachment/5288494/+files/gnome-shell-calendar.png ** 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 indicators", instead of centered to the screen width. + + The blue line on the screenshot is the centre fold of the screen, you + can see that the wallpaper is correctly centered with the animal circle + in the centre. -- 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/1843899 Title: gnome-shell calendar widget is not centered on the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen
** 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 indicators", instead of centered to the - screen width. + It feels as if it is centered, with an offset / margin on the left. - The blue line on the screenshot is the centre fold of the screen, you - can see that the wallpaper is correctly centered with the animal circle - in the centre. + between "right edge of the app menu" and "left edge of the top right + indicators", instead of centered to the screen width.The blue line on + the screenshot is the centre fold of the screen, you can see that the + wallpaper is correctly centered with the animal circle in the centre. -- 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/1843899 Title: gnome-shell calendar widget is not centered on the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen
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 notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1843899 Title: gnome-shell calendar widget is not centered on the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen
@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://bugs.launchpad.net/bugs/1843899 Title: gnome-shell calendar widget is not centered on the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843899/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1782538] [NEW] test-sleep now fails in lxc/lxd container
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 'test_fiemap(argv[0]) == 0' failed at ../src/test/test-sleep.c:96, function main(). Aborting. Aborted (core dumped) FAIL: test-sleep (code: 134) This is introduced with the hybernate offset patchset. Specifically, the last assertion introduced in test-sleep.c should be guarded against lxc/lxd containers `test_fiemap`. This is to be improved in a subsequent SRU. ** 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/1782538 Title: test-sleep now fails in lxc/lxd container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783305] [NEW] apparmor DENIED when a systemd unit with DynamicUsers=yes is launched in a lxd container
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 Loaded: loaded (/run/systemd/transient/testdynamic.service; transient) Transient: yes Active: failed (Result: exit-code) since Tue 2018-07-24 10:16:13 UTC; 6s ago Process: 470 ExecStart=/bin/true (code=exited, status=217/USER) Main PID: 470 (code=exited, status=217/USER) Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Forked /bin/true as 470 Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Changed dead -> running Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Job testdynamic.service/start finished, result=done Jul 24 10:16:13 systemd239 systemd[1]: Started /bin/true. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Failed to send unit change signal for testdynamic.service: Connection reset by peer Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Child 470 belongs to testdynamic.service. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Main process exited, code=exited, status=217/USER Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Failed with result 'exit-code'. Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Changed running -> failed Jul 24 10:16:13 systemd239 systemd[1]: testdynamic.service: Unit entered failed state. and on the host side, in journal there is: Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[14904]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:934): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:935): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:936): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:937): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=14904 comm="(true)" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:938): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:939): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:940): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi kernel: audit: type=1400 audit(1532427373.697:941): apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type= Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none Jul 24 11:16:13 sochi audit[3198]: AVC apparmor="DENIED" operation="file_lock" profile="lxd-systemd239_" pid=3198 comm="systemd" family="unix" sock_type="dgram" protocol=0 addr=none Can we somehow make DynamicUser work in lxd containers? ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: lxd (Ubuntu) Impor
[Bug 1783626] [NEW] systemd in cosmic should not migrate until apparmor abstract socket locks mediation is fixed
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 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/1783626 Title: systemd in cosmic should not migrate until apparmor abstract socket locks mediation is fixed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783626/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
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 of is: echo sync > /sys/module/scsi_mod/parameters/scan 2>/dev/null || : to redirect errors to oblivion, and to ignore errors from this action ** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: debian-installer (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: debian-installer (Ubuntu) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu) Importance: Undecided => Critical -- 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 on booting kernel 4.4 based d-i from 16.04.5 RC image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
** 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 on booting kernel 4.4 based d-i from 16.04.5 RC image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1784454/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1787748] Re: Ubuntu.session in gnome-session
** 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: Ubuntu.session in gnome-session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1787748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1790478] [NEW] gdm3 in cosmic fails to start fully in autopkgtest
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: systemd-sysv,
systemd,
udev,
systemd-container,
systemd-coredump,
libpam-systemd,
xserver-xorg-video-dummy,
xserver-xorg,
gdm3 [!s390x],
cron,
network-manager,
busybox-static,
apparmor,
pkg-config,
python3
The test does following:
out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])
self.assertIn(b'gdm-x-session gnome-session', out)
out = subprocess.check_output(['ps', 'u', '-C', 'Xorg'])
self.assertIn(b'Xorg vt1', out)
self.active_unit('gdm')
However, this now errors out upon the first command, meaning gdm-x-session is
not running anymore.
On bionic, this test case continues to operate correctly in the autopkgtest
cloud.
test_gdm3 (__main__.ServicesTest) ... ERROR
==
ERROR: test_gdm3 (__main__.ServicesTest)
--
Traceback (most recent call last):
File "/tmp/autopkgtest.RNx2A1/build.2Wy/src/debian/tests/boot-and-services",
line 66, in test_gdm3
out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session'])
File "/usr/lib/python3.6/subprocess.py", line 336, in check_output
**kwargs).stdout
File "/usr/lib/python3.6/subprocess.py", line 418, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['ps', 'u', '-C', 'gdm-x-session']'
returned non-zero exit status 1.
--
Ran 24 tests in 18.974s
FAILED (errors=1)
>From http://autopkgtest.ubuntu.com/packages/systemd/cosmic/i386
Thus it looks like there is a regression or a change of behavior of gdm3
in the cloud in cosmic; since bionic continues to work correctly.
I will mark this test as an expected failure for now, and monitor it
separately, as currently, this is blocking many migrations.
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: 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 gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1790478
Title:
gdm3 in cosmic fails to start fully in autopkgtest
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790478/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756006] Re: FFe: Support suspend-then-hibernate
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 gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1756006 Title: FFe: Support suspend-then-hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1773859] Re: upgrades to 18.04 fail
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 Status: Confirmed ** Also affects: systemd-shim (Ubuntu Cosmic) Importance: High Assignee: Steve Langasek (vorlon) Status: Won't Fix ** Changed in: systemd (Ubuntu Cosmic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1773859 Title: upgrades to 18.04 fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798996] Re: Cannot use it at all...
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: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1798996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798996] [NEW] Cannot use it at all...
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: regression-release ** Summary changed: - Cannot use it as a snap + Cannot use it at all... -- 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: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1798996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798996] Re: Cannot use it at all...
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1798996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798996] Re: Cannot use it at all...
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? =( -- 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 perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1798996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798996] Re: cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied
$ 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 Title: cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1798996/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1868409] Re: gnome-{calculator, logs, characters} snaps not removed after the equivalent APT packages are installed on 20.04, and gnome-software APT package not replaced by snap-store
** 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:
gnome-{calculator,logs,characters} snaps not removed after the
equivalent APT packages are installed on 20.04, and gnome-software APT
package not replaced by snap-store
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1868409/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876276] Re: Consider to include python-glade2 package into 20.04 LTS (focal) repositories as it is a dependency of many other packages
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 supportable. When things no longer meet basic maintenance criteria, they get removed. If and when software gets ported to supported stacks, they do come back. If you want any of that software, do work on porting it, or publish it elsehow (i.e. as vendorized confined snaps). ** Changed in: pygtk (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in Ubuntu. https://bugs.launchpad.net/bugs/1876276 Title: Consider to include python-glade2 package into 20.04 LTS (focal) repositories as it is a dependency of many other packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1876276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
** 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 performing TLS handshake: Internal error in memory allocation" and doesn't download any new email messages. This started happening two days ago shortly after updates were applied. Normally it would download the new email messages. Searching the web I found a Linux Mint forum with users having the same issue. Some users felt it maybe an expired certificate while others thought it might be related to the recent update. What can I do to get more information about this issue? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evolution 3.28.5-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 1 07:03:51 2020 InstallationDate: Installed on 2017-12-12 (870 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: - PATH=(custom, no username) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, no username) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to bionic on 2018-12-28 (489 days ago) ** Changed in: gnutls28 (Ubuntu) Importance: Undecided => High ** Changed in: evolution (Ubuntu) Status: Confirmed => Invalid ** Changed in: claws-mail (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnutls28 (Ubuntu) Status: Confirmed => Triaged ** Also affects: evolution (Ubuntu Groovy) Importance: Undecided Status: Invalid ** Also affects: claws-mail (Ubuntu Groovy) Importance: Undecided Status: Invalid ** Also affects: gnutls28 (Ubuntu Groovy) Importance: High Status: Triaged ** Also affects: evolution (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: claws-mail (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gnutls28 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: claws-mail (Ubuntu Focal) ** No longer affects: evolution (Ubuntu Focal) ** No longer affects: gnutls28 (Ubuntu Focal) ** Also affects: evolution (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: claws-mail (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gnutls28 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: claws-mail (Ubuntu Focal) Status: New => Invalid ** Changed in: evolution (Ubuntu Focal) Status: New => Invalid ** Changed in: gnutls28 (Ubuntu Focal) Importance: Undecided => High ** Changed in: gnutls28 (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1876286/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717471] Re: networkd does not accept / set advertised mtu
netplan needs to set DHCP.UseMTU=yes If I do that, my local instance no longer behaves strangely, and the MTU is correctly 1458 ** Also affects: nplan (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/1717471 Title: networkd does not accept / set advertised mtu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717471] [NEW] networkd does not accept / set advertised mtu
Public bug reported: Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. ** Affects: nplan (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: nplanfail -- 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/1717471 Title: networkd does not accept / set advertised mtu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714505] Re: systemd kmod builtin uses out of date kmod context
I think we should fix .udeb installation and the d-i to call `udevadm control --reload` after .udeb installation and before (re-)triggering udev. ** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Artful) Status: In Progress => Won't Fix ** No longer affects: systemd (Ubuntu Zesty) ** No longer affects: systemd (Ubuntu Trusty) ** No longer affects: systemd (Ubuntu Xenial) ** Changed in: systemd (Ubuntu) Status: In Progress => Won't Fix ** No longer affects: systemd (Ubuntu Artful) ** Also affects: debian-installer-utils (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/1714505 Title: systemd kmod builtin uses out of date kmod context To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1714505/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting
Something similar got reported recently upstream, and I got a brand new discovery that one should actually call $ udevadm control --reload -> whenever configuration is changed, as upstream knows that all of their internal state caching and reloading is racy. Could you please modify your reproducer test case to have: udevadm control --reload, before calling trigger action and check if this resolves your issue? If true, I believe netplan must call udevadm control --reload after writing out anything that udevd reads, which is udev .rules files and .link files. ** Also affects: nplan (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/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1691096] Re: mysql in lxd fails to start with systemd 233, 234: failed at step KEYRING
** Bug watch added: github.com/systemd/systemd/issues #6871 https://github.com/systemd/systemd/issues/6871 ** Also affects: systemd via https://github.com/systemd/systemd/issues/6871 Importance: Unknown Status: Unknown -- 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/1691096 Title: mysql in lxd fails to start with systemd 233, 234: failed at step KEYRING To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1691096/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718029] Re: cloudstack and azure datasources broken when using netplan/systemd-networkd
No changes in netplan required. ** Changed in: nplan (Ubuntu) Status: New => Invalid ** Changed in: netplan 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/1718029 Title: cloudstack and azure datasources broken when using netplan/systemd- networkd To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1718029/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720892] Re: 17.10Beta2. networking.service not available
Marking bug as invalid, as it is intentional that ifupdown is not installable by default. ** 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/1720892 Title: 17.10Beta2. networking.service not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1720892/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1720976] Re: no DNS resolution via systemd
Fresh boot of Artful (static IP via network manager and DNS should be at 192.168.1.1) -> NetworkManager has integration with systemd-resolved and thus should pass DNS information to resolved. Could you please show your NetworkManager configuration for the network in question? ** Also affects: network-manager (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/1720976 Title: no DNS resolution via systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1720976/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721203] [NEW] systemd armhf autopkgtest test-copy fails in artful
Public bug reported: systemd armhf autopkgtest test-copy fails in artful test-copy uses itself as the source to test copies. The test suite tries to test cases where maximum requested copy is below and above the internal buffer size. However, that fails when the maximum requested copy bytes is more than the source binary... as started to be the case with uber optimised artful toolchain on armhf, and after debug symbols stripped. Specifically test-copy started to be less than 32000 bytes. Awaiting improvement to the test suite upstream, simply keep test-copy unstripped such that systemd-tests can be used in adt tests without failures. ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Fix Committed ** Affects: systemd (Ubuntu Artful) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Fix Committed ** Tags: adt-fail armhf ** Also affects: systemd (Ubuntu Artful) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: New ** Bug watch added: github.com/systemd/systemd/issues #6981 https://github.com/systemd/systemd/issues/6981 ** Also affects: systemd via https://github.com/systemd/systemd/issues/6981 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu Artful) Status: New => Fix Committed ** Changed in: systemd (Ubuntu Artful) Importance: Undecided => High -- 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/1721203 Title: systemd armhf autopkgtest test-copy fails in artful To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1721203/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting
@original reporter have you added `udevadm control --reload` in the appropriate points in the test-harness and/or cloud-init? And does this resolve the race you have previously observed? Unassigning, Removing artful series target and marking incomplete, until further information is provided. ** No longer affects: systemd (Ubuntu Artful) ** No longer affects: nplan (Ubuntu Artful) ** Changed in: systemd (Ubuntu) Assignee: Balint Reczey (rbalint) => (unassigned) ** Changed in: systemd (Ubuntu) Status: New => Incomplete ** Changed in: nplan (Ubuntu) Status: New => Incomplete -- 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/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721204] [NEW] timesyncd has redundant condition conflict with ntp and others
Public bug reported: Cherrypick Drop systemd-timesyncd.service.d/disable-with-time-daemon.conf All major NTP implementations ship a native service file nowadays with a Conflicts=systemd-timesyncd.service so this drop-in is no longer necessary. Closes: #873185 This should resolve the current issue in Ubuntu, where when both ntpd and timesyncd are installed, both are enabled yet neither run. ** Affects: systemd (Ubuntu) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Fix Committed ** Affects: systemd (Ubuntu Artful) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Fix Committed ** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Artful) Importance: Undecided => High ** Changed in: systemd (Ubuntu Artful) Status: New => Fix Committed ** 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.net/bugs/1721204 Title: timesyncd has redundant condition conflict with ntp and others To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1721204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services
The unit entered a failed state, and thus would not automatically started until failed state clears. Why does bouncing of the services result in the daemon exiting with an error condition? Should that particular exit code result in a graceful shutdown of the service, such that the unit can be restarted again? What userspace events should be causing the start of this unit? a udev event / udev rule? a .path unit monitoring sysfs or some such? Is it possible to reproduce this on e.g. azure for me to investigate? I'm going to remove per-series tasks from systemd, until this issue is trianged. per-series tasks on the src:systemd package are used to track fixes/patches which have been developed and are ready for inclusion in the distribution. ** No longer affects: systemd (Ubuntu Artful) ** No longer affects: systemd (Ubuntu Zesty) ** No longer affects: systemd (Ubuntu Xenial) -- 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/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1698734] Re: systemd-resolved spams syslog whenever I'm disconnected
** No longer affects: systemd (Ubuntu Zesty) -- 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/1698734 Title: systemd-resolved spams syslog whenever I'm disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
** Also affects: systemd (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1721223/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722300] Re: Boot times since artful upgrade have increased 4 fold
please upgrade before reporting bugs 234-2ubuntu10 is out of date. Please try again with 234-2ubuntu12 ** 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/1722300 Title: Boot times since artful upgrade have increased 4 fold To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1722300/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1722481] [NEW] systemd should sync disks, before killing all processes on shutdown
Public bug reported: [Impact] * systemd-shutdown binary is executed to complete system shutdown. In xenial, it calls sync() after killing all processes, and not before killing them. This means that processes are racing the SIGKILL/TERM timeouts to sync all IO to disk. To mitigate this race condition, and make the shutdown process more reliable the sync() should also happen before process killing spree starts. [Fix] Backport upstream commit https://github.com/systemd/systemd/commit/2e79d1828a8da9b3af1b052297e3617905ec94f3 [Test Case] * Make sure systems still shuts down, including e.g. root on raid. [Regression Potential] * Shutdowns may appear to be slower due to two sync() calls instead of one * However total shutdown time should not be impacted much, as there really should not be much additional IO caused by killing all processes. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => 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/1722481 Title: systemd should sync disks, before killing all processes on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1722481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1669564] Re: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting
** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid ** Changed in: nplan (Ubuntu) Status: New => Triaged ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bb-series) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Bb-series) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: nplan (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: High Status: Invalid ** Also affects: nplan (Ubuntu Artful) Importance: Undecided Status: Triaged ** No longer affects: systemd (Ubuntu) ** No longer affects: systemd (Ubuntu Xenial) ** No longer affects: systemd (Ubuntu Zesty) ** No longer affects: systemd (Ubuntu Artful) ** No longer affects: systemd (Ubuntu Bb-series) -- 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/1669564 Title: udevadm trigger subsystem-match=net doesn't always run rules because of reconfiguration rate-limiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1669564/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714505] Re: systemd kmod builtin uses out of date kmod context
** No longer affects: debian-installer (Ubuntu Artful) ** No longer affects: debian-installer (Ubuntu Zesty) ** No longer affects: debian-installer (Ubuntu Xenial) ** No longer affects: debian-installer (Ubuntu Trusty) ** Also affects: debian-installer (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: debian-installer-utils (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: debian-installer (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: debian-installer-utils (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: debian-installer (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: debian-installer-utils (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Trusty) ** No longer affects: systemd (Ubuntu Xenial) ** No longer affects: systemd (Ubuntu Zesty) -- 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/1714505 Title: systemd kmod builtin uses out of date kmod context To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1714505/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1723390] [NEW] lxd containers have become degraded
Public bug reported: 20170920 container boots degraded with Oct 13 10:09:28 test20170920 systemd[256]: systemd-hostnamed.service: Failed at step NETWORK spawning /lib/systemd/systemd-hostnamed: Permission denied 20170919 container boots non-degraded. Package list changes are insignificant. ** 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/1723390 Title: lxd containers have become degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1723390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726124] Re: DNS domain search paths not updated when VPN started
network-manager has resolved integration and it does push search domains to resolved and they are updated in the /etc/resolv.conf. This should continue to work in 17.10. Hence marking this bug affect network-manager and network-manager-openvpn ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager-openvpn (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/1726124 Title: DNS domain search paths not updated when VPN started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1726124/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726439] Re: Link copied with "Copy Link Address" cannot be pasted with Shift-Insert
UpgradeStatus: Upgraded to artful on 2016-12-05 (321 days ago) -> really?! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1726439 Title: Link copied with "Copy Link Address" cannot be pasted with Shift- Insert To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726439/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726438] [NEW] networkd appear to loose DNS= state in netif file
Public bug reported: networkd appear to loose DNS= state in netif file taking old xenial, upgrading, looses DNS nameservers state ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: xenial ** Tags added: xenial ** Also affects: systemd (Ubuntu Xenial) 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/1726438 Title: networkd appear to loose DNS= state in netif file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces
I am suspecting the following cherrypick is missing in xenial: https://github.com/systemd/systemd/commit/1ed1f50f8277df07918e13cba3331a114eaa6fe3.patch will prepare a PPA with this fix applied, and will expedite an sru with this fix in. ** Bug watch added: github.com/systemd/systemd/issues #3890 https://github.com/systemd/systemd/issues/3890 ** Also affects: systemd via https://github.com/systemd/systemd/issues/3890 Importance: Unknown Status: Unknown -- 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/1727301 Title: 229-4ubuntu20 added ARP option breaks existing bonding interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1727301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces
** Description changed:
+ [Impact]
+
+ * Incomplete cherrypick of ARP functionality in networkd resulted in an
+ undesired side-effect, specifically NOARP flag started to be applied
+ unconditionally, specifically when it should not have, resulting in loss
+ of network connectivity.
+
+ * This is a regression in -updates.
+
+ [Test Case]
+
+ * Configure a bond using networkd
+ * Upgrade
+ * Make sure NOARP flag is not set on the interfaces / bond
+
+ [Regression Potential]
+
+ * This is an upstream fix for this issue.
+
+ [Other Info]
+
+ * Upstream fix
+
https://github.com/systemd/systemd/commit/1ed1f50f8277df07918e13cba3331a114eaa6fe3.patch
+
+ * Original bug report
+
this breaks existing configurations with bonding on upgrading from
229-4ubuntu19 to 229-4ubuntu20 on xenial
as bond interfaces are now by default configured without ARP. Hence you
suddenly lose network connectivity on upgrade. Very bad for a SRU.
Plus adding "ARP=yes" to the Link section of a .network file does not
work.
Before this update, bond interfaces (specifically 802.3ad) were
defaulting to ARP enabled. After the upgrade, they are created with
NOARP set on the link.
pre-upgrade:
eth0:
eth1:
bond0:
post-upgrade:
eth0:
eth1:
bond0:
Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
** Changed in: systemd (Ubuntu)
Importance: Undecided => Critical
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Critical
Status: Confirmed
** Also affects: systemd (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Xenial)
Status: New => In Progress
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: systemd (Ubuntu Zesty)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Artful)
Status: New => Fix Released
** Changed in: systemd (Ubuntu Bionic)
Status: Confirmed => Fix Released
** Changed in: systemd (Ubuntu Xenial)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: systemd (Ubuntu Xenial)
Milestone: None => xenial-updates
--
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/1727301
Title:
229-4ubuntu20 added ARP option breaks existing bonding interfaces
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1727301/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces
** Changed in: systemd (Ubuntu Zesty) Status: Fix Released => Confirmed ** Changed in: systemd (Ubuntu Bionic) Status: Fix Released => Confirmed ** Changed in: systemd (Ubuntu Zesty) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu Artful) Status: Fix Released => Confirmed ** Changed in: systemd (Ubuntu Artful) Importance: Undecided => Critical -- 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/1727301 Title: 229-4ubuntu20 added ARP option breaks existing bonding interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1727301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces
** Changed in: systemd (Ubuntu Zesty) Status: Confirmed => Invalid ** Changed in: systemd (Ubuntu Bionic) Status: Confirmed => Invalid ** Changed in: systemd (Ubuntu Artful) Status: Confirmed => 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/1727301 Title: 229-4ubuntu20 added ARP option breaks existing bonding interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1727301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730082] Re: 17.10 Shutdown Delayed 10 Min Due To Wifi
** Also affects: network-manager (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/1730082 Title: 17.10 Shutdown Delayed 10 Min Due To Wifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1730082/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1725348] Re: Systemd - Bypassing MemoryDenyWriteExecution policy
** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** 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 Ubuntu. https://bugs.launchpad.net/bugs/1725348 Title: Systemd - Bypassing MemoryDenyWriteExecution policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725348/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2017780] [NEW] gdm was failing to start for me, because smarcard.desktop was missing
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 which i think is an allowed action. I installed updates, gdm didn't start anymore because Smartcard.desktop is required to start settion and was unable to start it without it. Doing sudo apt install --reinstall -o Dpkg::Options::=--force-confmiss gnome-settings-daemon ressurected ability to start gdm But also ressurected Smartcard.desktop. How do I disable gdm to not attempt smartcard logins, when my system a) is not enrolled to use or trust any smarcards via pam or anything b) it is a yubikey with gpg certs c) i want gdm to still show and allow login with locally configured user despite smartcard plugged in ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- 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/2017780 Title: gdm was failing to start for me, because smarcard.desktop was missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2017780/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
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: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
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 secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 41159] Re: timezone data is duplicated over at least three packages in main
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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/41159 Title: timezone data is duplicated over at least three packages in main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/41159/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762391] Re: pam_group.so is not evaluated by gnome-terminal
** 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 (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1762391 Title: pam_group.so is not evaluated by gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1762391/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1818616] [NEW] gnome-keyring is not unlocked upon gdm login in disco
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 in through gdm3, I get a pop-up from gnome- keyring instructing me that gnome-keyring was not unlocked upon logging, and I have to re-enter the password again. The password for the account and the gnome-keyring are the same, and the keyring should be auto-unlocked. Looking at the journal, there is a red warning from gdm: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor XDG_RUNTIME_DIR are set. The messages after it are: Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon control file Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory /run/user/1000... Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox. Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory /run/user/1000. Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000... Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): session opened for user xnox by (uid=0) Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for Ubuntu Report. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers). Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers. Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate management daemon. Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus Socket. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System. Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000. Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor. Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default. Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms. Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox. I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see that XDG_RUNTIME_DIR to be created and set by logind. From the above logs I can see that it happens _after_ gdm-password is done. So It seems like something has changed in the stack, and gdm login / libpam-gnome-keyring no longer use systemd-logind PAM module to be part of the PAM session. But I'm not sure what has changed to cause this (gdm, gnome-keyring, pam, systemd). Am I the only one with this issue? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-keyring 3.31.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 5 08:22:01 2019 InstallationDate: Installed on 2016-01-26 (1134 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco release-dd-incoming ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Also affects: pam (Ubuntu) Importance: Undecided Status: New ** 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 gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1818616 Title: gnome-keyring is not unlocked upon g
[Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco
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 notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1818616 Title: gnome-keyring is not unlocked upon gdm login in disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1818616/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857211] Re: linphone fails to compile, does in debian
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) Importance: Undecided Status: New -- 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/1857211 Title: linphone fails to compile, does in debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1857211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857211] [NEW] linphone fails to compile, does in debian
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 -DORTP_STATIC -DSQLITE_STORAGE_ENABLED -DVCARD_ENABLED -DVIDEO_ENABLED -I/<>/include -I/<>/coreapi -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/coreapi -I/usr/include/gtk-2.0 -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -isystem /usr/include/libxml2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-Wall -Wuninitialized -Wno-error=deprecated-declarations -Wstrict-prototypes -Werror=strict-prototypes -fno-inline-small-functions -o CMakeFiles/linphone-gtk.dir/audio_assistant.c.o -c /<>/gtk/audio_assistant.c In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/gtk/linphone.h:31, from /<>/gtk/audio_assistant.c:22: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. make[3]: *** [gtk/CMakeFiles/linphone-gtk.dir/build.make:66: gtk/CMakeFiles/linphone-gtk.dir/audio_assistant.c.o] Error 1 libharfbuzz-dev is installed But it looks like /usr/include/harfbuzz is not included in the build. Is it a bug in our Cmake? In our harfbuzz? In our pango/gtk? Should the include be or should it be ? What's different between us and Debian, as it does build there. ** Affects: cmake (Ubuntu) Importance: Undecided Status: New ** Affects: harfbuzz (Ubuntu) Importance: Undecided Status: New ** Affects: linphone (Ubuntu) Importance: Undecided Status: New ** Affects: pango1.0 (Ubuntu) Importance: Undecided Status: New -- 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/1857211 Title: linphone fails to compile, does in debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1857211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1857211] Re: linphone fails to compile, does in debian
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 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/1857211 Title: linphone fails to compile, does in debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1857211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867133] [NEW] spinner theme flickers Ubuntu logo on gdm transition
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 flicker, where Ubuntu logo temporarily dissappears and instantly fades back in. This should be more smooth. For example, gdm could paint ubuntu logo at 100% opacity white without animation, whilst everything else fades-in. Or we could fade out ubuntu-logo in the spinner plymouth theme, such that on boot it is a tasteful pulsating logo that fades out, and back in. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: champagne ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- 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/1867133 Title: spinner theme flickers Ubuntu logo on gdm transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1867133/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends
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 chrome-gnome-shell to ubuntu-desktop recommends To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1679674] Re: s390x: Interface order in kvm guest image not predictable
This change got uploaded into ubuntu on 2017-03-28, before this bug report was filed, but due to various regressions was not published until 2017-04-08. With most current Ubuntu 17.04, and 232-21ubuntu2 stable interface names are used for virtio_net defices based on the bus IDs just like on LPAR and z/VM. Specifically interfaces names are renamed into: enc2 and enc3 for my xml of the guest, which corresponds to the devno in the xml definition: I am marking this bug as fix released. ** Changed in: systemd (Ubuntu) Status: Confirmed => 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/1679674 Title: s390x: Interface order in kvm guest image not predictable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1682437] [NEW] udev does not preserve virtio interface names on s390x upgrades
Public bug reported: Package: udev Version: 232-20 Severity: important Dear Maintainer, systemd 232-20 introduce the patch to generate stable interface names for virtio network interfaces on s390x. This is a good thing, and those names should be used for new installations. However, when upgrading existing virtual machines installations the new udev causes interfaces to be renamed from eth0 -> enc1 thus breaking networking configuration and possibly other configs (e.g. daemons, firewalls etc). Therefore on upgrade (but not clean installs) something like persistent net rules should be generated to preserve ethX interface names and thus not break networking configuration. I will attach a proposed patch to achieve this shortly for review. It is important to fix this in stretch such that upgrades to stretch are flawless. ** Affects: systemd (Ubuntu) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Triaged ** Tags: s390x ** Tags added: s390x ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-17.05 -- 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/1682437 Title: udev does not preserve virtio interface names on s390x upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1682484] [NEW] systemd: Logging from gnome session is passed on to all syslog facilities
Public bug reported:
Bug imported from Debian https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=837893
Package: systemd
Version: 231-6
Severity: normal
Since recently, log messages from programs running under the gnome
session have started appearing in all logs in /var/logs, including
/var/logs/kern.log, even though my rsyslog configuration has not
changed, and correctly only routes kern.* there.
This is very annoying since it fills the logs with messages that don't
belong there, and makes running logcheck tedious.
It seems this is a recent regression, since before I was able to route
these messages to a low-priority log using the following rsyslog
configuration:
user.=info;user.=notice;\
user.=warn -/var/log/user-low.log
If I look at the messages directly with journalctl -o verbose, it seems
they do not set the syslog facility, which should make them end up with
user facility, but doesn't.
** Affects: systemd
Importance: Unknown
Status: Unknown
** Affects: systemd (Ubuntu)
Importance: High
Assignee: Dimitri John Ledkov (xnox)
Status: Confirmed
** Affects: systemd (Ubuntu Zesty)
Importance: High
Assignee: Dimitri John Ledkov (xnox)
Status: Confirmed
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Bug watch added: github.com/systemd/systemd/issues #5640
https://github.com/systemd/systemd/issues/5640
** Also affects: systemd via
https://github.com/systemd/systemd/issues/5640
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Also affects: systemd (Ubuntu Zesty)
Importance: High
Assignee: Dimitri John Ledkov (xnox)
Status: 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/1682484
Title:
systemd: Logging from gnome session is passed on to all syslog
facilities
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1682484/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1668347] Re: Unable to set bridge_portpriority with networkd
** Also affects: systemd (Ubuntu Zesty) Importance: Medium Assignee: Dimitri John Ledkov (xnox) Status: In Progress -- 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/1668347 Title: Unable to set bridge_portpriority with networkd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668347/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1682499] [NEW] disable dnssec
Public bug reported: because pitti says so cherrypick from debian ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) 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/1682499 Title: disable dnssec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672542] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15
** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Zesty) 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. https://bugs.launchpad.net/bugs/1672542 Title: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1682774] Re: [systemd-udevd] Process '/bin/touch /var/lib/lsvpd/run.vpdupdate' failed with exit code 1
This udev rule is shipped by libvpd package, changing package assignment. ** Package changed: systemd (Ubuntu) => libvpd (Ubuntu) -- 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/1682774 Title: [systemd-udevd] Process '/bin/touch /var/lib/lsvpd/run.vpdupdate' failed with exit code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpd/+bug/1682774/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1682437] Re: udev does not preserve virtio interface names on s390x upgrades
** Description changed: + [Impact] + + * Upgrading s390x, kvm/qemu instances from yakkety to zesty results in a change of network interface names (e.g. from eth0 to stable/predictable bus_id name enc3, just like on z/VM and LPAR). + * This obviously results in loss of network connectivity as /etc/network/interfaces no longer matches the network interface names configured by systemd. + * The proposal is to generate udev rules on upgrade to preserve active interface names, in a very similar fashion to the no longer in use net-persistent-name generator. + + [Test Case] + + * Install zesty from scratch in kvm/qemu, network interfaces should use enc* names. + * Install yakkety, upgrade to zesty, network intefaces should use eth* names after upgrade and reboot. + + [Regression Potential] + + * This solution is similar to previous upgrades to stable networking + names for other types of network interfaces. This will make upgraded + systems look different from freshly installed systems. For users aiming + to have homogenious environments it is recommended to remove + /etc/udev/rules.d/70-persistent-net.rules and readjust + networking/daemon/firewall configurations to the new stable names enc*. + + [Other Info] + + * Original bug report filed in debian. + Package: udev Version: 232-20 Severity: important Dear Maintainer, systemd 232-20 introduce the patch to generate stable interface names for virtio network interfaces on s390x. This is a good thing, and those names should be used for new installations. However, when upgrading existing virtual machines installations the new udev causes interfaces to be renamed from eth0 -> enc1 thus breaking networking configuration and possibly other configs (e.g. daemons, firewalls etc). Therefore on upgrade (but not clean installs) something like persistent net rules should be generated to preserve ethX interface names and thus not break networking configuration. I will attach a proposed patch to achieve this shortly for review. It is important to fix this in stretch such that upgrades to stretch are flawless. ** Also affects: systemd (Ubuntu Zesty) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Triaged -- 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/1682437 Title: udev does not preserve virtio interface names on s390x upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1682437/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1683908] Re: Z system has no network after do-release-upgrade from Yakkety to Zesty
*** This bug is a duplicate of bug 1682437 *** https://bugs.launchpad.net/bugs/1682437 netcfg is irrelevant here. this is a known issue, and SRU is in progress to resolve this. ** Package changed: netcfg (Ubuntu) => systemd (Ubuntu) ** This bug has been marked a duplicate of bug 1682437 udev does not preserve virtio interface names on s390x upgrades -- 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/1683908 Title: Z system has no network after do-release-upgrade from Yakkety to Zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1683908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
