[Bug 1920987] Re: Europe/Simferopol, Crimea is RUSSIA

2021-03-24 Thread Dimitri John Ledkov
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 1920987] Re: Europe/Simferopol, Crimea is RUSSIA

2021-03-24 Thread Dimitri John Ledkov
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 1916705] Re: glib2.0 >=2.67.3 breaks include from an extern C context

2021-03-15 Thread Dimitri John Ledkov
** 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 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)

2021-02-05 Thread Dimitri John Ledkov
** 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 1900754] Re: gdm is having crashes in livesession?

2020-10-20 Thread Dimitri John Ledkov
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 1900754] [NEW] gdm is having crashes in livesession?

2020-10-20 Thread Dimitri John Ledkov
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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

2020-09-10 Thread Dimitri John Ledkov
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 1886814] Re: posix_spawn usage in gnu make causes failures on s390x

2020-09-02 Thread Dimitri John Ledkov
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 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)

2020-08-28 Thread Dimitri John Ledkov
@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 1892915] Re: gnome-shell crashing (libffi8ubuntu1 upgrade issue)

2020-08-27 Thread Dimitri John Ledkov
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)

2020-08-27 Thread Dimitri John Ledkov
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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-08-17 Thread Dimitri John Ledkov
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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-08-17 Thread Dimitri John Ledkov
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 1890619] Re: poppler fails to build on s390x with gcc10 due to symbols changes

2020-08-06 Thread Dimitri John Ledkov
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.

2020-07-13 Thread Dimitri John Ledkov
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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-06-25 Thread Dimitri John Ledkov
** 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 1865226] Re: gdm3 fails to install /etc/pam.d/gdm-smartcard

2020-06-23 Thread Dimitri John Ledkov
** 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 1847307] Re: ubiquity-dm (maybe-ubiquity/only-ubiquity) missing keyboard indicator, when booted into Esc, Russian locale by default from isolinux BIOS boot

2020-06-15 Thread Dimitri John Ledkov
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 1847307] Re: ubiquity-dm (maybe-ubiquity/only-ubiquity) missing keyboard indicator, when booted into Esc, Russian locale by default from isolinux BIOS boot

2020-06-15 Thread Dimitri John Ledkov
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: Install in english with italian keyboard - keyboard not set during install

2020-06-15 Thread Dimitri John Ledkov
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 1245534] Re: gnome archive manager incorrect handling of jar repositories

2020-06-12 Thread Dimitri John Ledkov
** 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 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."

2020-06-04 Thread Dimitri John Ledkov
** 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 1876276] Re: Consider to include python-glade2 package into 20.04 LTS (focal) repositories as it is a dependency of many other packages

2020-05-01 Thread Dimitri John Ledkov
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 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

2020-03-26 Thread Dimitri John Ledkov
** 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 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends

2020-03-12 Thread Dimitri John Ledkov
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 1867133] [NEW] spinner theme flickers Ubuntu logo on gdm transition

2020-03-12 Thread Dimitri John Ledkov
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 1857211] Re: linphone fails to compile, does in debian

2019-12-23 Thread Dimitri John Ledkov
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 1857211] [NEW] linphone fails to compile, does in debian

2019-12-21 Thread Dimitri John Ledkov
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

2019-12-21 Thread Dimitri John Ledkov
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 1843899] Re: gnome-shell calendar widget is not centered on the screen

2019-09-13 Thread Dimitri John Ledkov
@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 1843899] Re: gnome-shell calendar widget is not centered on the screen

2019-09-13 Thread Dimitri John Ledkov
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

2019-09-13 Thread Dimitri John Ledkov
** 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] [NEW] gnome-shell calendar widget is not centered on the screen

2019-09-13 Thread Dimitri John Ledkov
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 1803993] Re: Password appears on the VT1 screen

2019-06-05 Thread Dimitri John Ledkov
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 1818616] [NEW] gnome-keyring is not unlocked upon gdm login in disco

2019-03-05 Thread Dimitri John Ledkov
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 

[Bug 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco

2019-03-05 Thread Dimitri John Ledkov
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 1762391] Re: pam_group.so is not evaluated by gnome-terminal

2019-01-17 Thread Dimitri John Ledkov
** 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 41159] Re: timezone data is duplicated over at least three packages in main

2018-12-12 Thread Dimitri John Ledkov
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 1798996] Re: cannot perform readlinkat() on the mount namespace file descriptor of the init process: Permission denied

2018-10-24 Thread Dimitri John Ledkov
$ 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 1798996] Re: Cannot use it at all...

2018-10-24 Thread Dimitri John Ledkov
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 use it at all...

2018-10-20 Thread Dimitri John Ledkov
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...

2018-10-20 Thread Dimitri John Ledkov
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...

2018-10-20 Thread Dimitri John Ledkov
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 1773859] Re: upgrades to 18.04 fail

2018-10-04 Thread Dimitri John Ledkov
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 1756006] Re: FFe: Support suspend-then-hibernate

2018-10-01 Thread Dimitri John Ledkov
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 1790478] [NEW] gdm3 in cosmic fails to start fully in autopkgtest

2018-09-03 Thread Dimitri John Ledkov
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 1787748] Re: Ubuntu.session in gnome-session

2018-08-19 Thread Dimitri John Ledkov
** 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 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

2018-07-30 Thread Dimitri John Ledkov
** 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 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

2018-07-30 Thread Dimitri John Ledkov
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 1783626] [NEW] systemd in cosmic should not migrate until apparmor abstract socket locks mediation is fixed

2018-07-25 Thread Dimitri John Ledkov
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 1783305] [NEW] apparmor DENIED when a systemd unit with DynamicUsers=yes is launched in a lxd container

2018-07-24 Thread Dimitri John Ledkov
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)
   

[Bug 1782538] [NEW] test-sleep now fails in lxc/lxd container

2018-07-19 Thread Dimitri John Ledkov
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 1748280] Re: 'nova reboot' on arm64 is just 'nova reboot --hard' but slower

2018-07-03 Thread Dimitri John Ledkov
This affects systemd-fsckd autopkgtest

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1748280

Title:
  'nova reboot' on arm64 is just 'nova reboot --hard' but slower

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1748280/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1779956] Re: GDPR Compliance

2018-07-03 Thread Dimitri John Ledkov
Please do check our configuration first. As far as I can tell, this is
invalid.

Ubuntu Privacy references are located at
https://www.ubuntu.com/legal/dataprivacy

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

** Bug watch added: github.com/systemd/systemd/issues #9482
   https://github.com/systemd/systemd/issues/9482

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/9482
   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/1779956

Title:
  GDPR Compliance

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1779956/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1779721] Re: systemd-networkd does not configure DHCPv4

2018-07-03 Thread Dimitri John Ledkov
** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

** Changed in: netplan.io (Ubuntu)
   Status: New => Invalid

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov  (xnox)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1779721

Title:
  systemd-networkd does not configure DHCPv4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1779721] Re: systemd-networkd does not configure DHCPv4

2018-07-02 Thread Dimitri John Ledkov
An empty match, does not match any interfaces hence none are
configured

What's the output of $ networkctl ? i suspect no interfaces are
maganaged, right?

Note the config mentioned in this bug report looks buggy, and different
from the askubuntu reference - which does appear to have a valid config.

** Also affects: netplan.io (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/1779721

Title:
  systemd-networkd does not configure DHCPv4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch

2018-06-27 Thread Dimitri John Ledkov
** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1778936

Title:
  please re-add Support-system-image-read-only-etc.patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd

2018-06-21 Thread Dimitri John Ledkov
Proposed fix in systemd. Run systemd-tmpfiles, during postinst, the way
it would be run on boot, such that all base files are correct, including
any overrides shipped by any other package; systemd; in transient
runtime dir.

At the same time, the dh_installinit is silenced to not produce the
systemd-tmpfiles snippet which this package does not need.

This solves the issue of integration with rsyslog; generically; without
requiring to backport debhelper, nor change rsyslog package.

** Changed in: rsyslog (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: rsyslog (Ubuntu Xenial)
   Status: Confirmed => Invalid

** Changed in: rsyslog (Ubuntu Artful)
   Status: Confirmed => Invalid

** Changed in: rsyslog (Ubuntu Bionic)
   Status: Confirmed => Invalid

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Fix Committed

** Patch added: "lp1748147.diff"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748147/+attachment/5155096/+files/lp1748147.diff

** Changed in: debhelper (Ubuntu Bionic)
   Status: In Progress => Won't Fix

** Changed in: debhelper (Ubuntu Bionic)
 Assignee: Seyeong Kim (xtrusia) => (unassigned)

** Changed in: debhelper (Ubuntu Artful)
   Status: In Progress => Won't Fix

** Changed in: debhelper (Ubuntu Artful)
 Assignee: Seyeong Kim (xtrusia) => (unassigned)

** Changed in: debhelper (Ubuntu Xenial)
   Status: In Progress => Won't Fix

** Changed in: debhelper (Ubuntu Xenial)
 Assignee: Seyeong Kim (xtrusia) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1748147

Title:
  [SRU] debhelper support override from /etc/tmpfiles.d for systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/debhelper/+bug/1748147/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1776013] Re: systemd-networkd: DHCP lease lost (Ubuntu 18.04)

2018-06-10 Thread Dimitri John Ledkov
Yes, the critical connection is the option to use in this case.

You may also check the leases themselves in /run/systemd/netif/leases
and check if the T1/T2/Lifetime are sensible, with each subsequent one
higher than the prior. And if not, contact your ISP support to correct
those.


** Changed 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/1776013

Title:
  systemd-networkd: DHCP lease lost (Ubuntu 18.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1776013/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd

2018-06-06 Thread Dimitri John Ledkov
There are multiple bugs here.

I do not believe testcase of the rsyslog <-> systemd is wrong, and
whilst debhelper support is good, is not what would fix rsyslog <->
systemd in Ubuntu.

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

** Also affects: rsyslog (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1748147

Title:
  [SRU] debhelper support override from /etc/tmpfiles.d for systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/debhelper/+bug/1748147/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

2018-06-05 Thread Dimitri John Ledkov
** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1766969

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1774417] Re: systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno = Operation not permitted

2018-05-31 Thread Dimitri John Ledkov
Well, on Ubuntu we do not have nss-nis package.

As libnss_nis is shipped in libc6, and thus available everywhere. Thus
adding a depends or a drop-in is a non-starter as well it would be
installed by default everywhere.

I'm not sure if we can somehow detect that it was enabled, and require
nscd installation at that point.

I'd rather not unsandbox logind.

** Also affects: glibc (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nis (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: glibc (Ubuntu)

** Bug watch added: Debian Bug tracker #878625
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625

** Also affects: nis (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625
   Importance: Unknown
   Status: Unknown

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

** Changed in: nis (Ubuntu)
   Status: New => 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/1774417

Title:
  systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno =
  Operation not permitted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1774417/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1773180] [NEW] 7, 000 errors a day of ERROR:value_store_frontend.cc(58)] Error while writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to

2018-05-24 Thread Dimitri John Ledkov
Public bug reported:

I have a lot of errors in my journal of the following form:

ERROR:value_store_frontend.cc(58)] Error while writing
kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to

often the same id is reported 2 or 3 times. Many of them are the same
over and over again.

May 21 15:42:17 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154217.618607:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
May 21 15:42:17 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154217.619171:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
May 21 15:42:34 sochi org.gnome.Shell.desktop[18271]: 
[4202:10132:0521/154234.396928:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:42:34 sochi org.gnome.Shell.desktop[18271]: 
[4202:10132:0521/154234.397539:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:42:34 sochi org.gnome.Shell.desktop[18271]: 
[4202:10132:0521/154234.401254:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:42:35 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154235.535549:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
May 21 15:42:35 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154235.536151:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
May 21 15:43:12 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154312.925656:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:43:12 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154312.926314:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:43:12 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154312.927266:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:43:13 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154313.818263:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
May 21 15:43:13 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154313.818848:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
May 21 15:43:22 sochi org.gnome.Shell.desktop[18271]: 
[4202:9917:0521/154322.585837:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:43:22 sochi org.gnome.Shell.desktop[18271]: 
[4202:9917:0521/154322.586337:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:43:22 sochi org.gnome.Shell.desktop[18271]: 
[4202:9917:0521/154322.587444:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:43:23 sochi org.gnome.Shell.desktop[18271]: 
[4202:10132:0521/154323.676650:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
May 21 15:43:23 sochi org.gnome.Shell.desktop[18271]: 
[4202:10132:0521/154323.677423:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
May 21 15:44:04 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154404.243205:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:44:04 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154404.243478:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:44:04 sochi org.gnome.Shell.desktop[18271]: 
[4202:9863:0521/154404.247541:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:44:04 sochi org.gnome.Shell.desktop[18271]: 
[4202:10226:0521/154404.801699:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
May 21 15:44:04 sochi org.gnome.Shell.desktop[18271]: 
[4202:10226:0521/154404.802603:ERROR:value_store_frontend.cc(58)] Error while 
writing hdokiejnpimakedhajhdlcegeplioahd.browser_action to
May 21 15:44:05 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154405.239334:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:44:05 sochi org.gnome.Shell.desktop[18271]: 
[4202:10393:0521/154405.239837:ERROR:value_store_frontend.cc(58)] Error while 
writing kbfnbcaeplbcioakkpcpgfkobkghlhen.browser_action to
May 21 15:44:05 sochi org.gnome.Shell.desktop[18271]: 

[Bug 1773177] [NEW] Failed to set the markup of the actor 'ClutterText': Error on line 1 char 28: Odd character 'S', expected a '=' after attribute name 'Less-than' of element ':'

2018-05-24 Thread Dimitri John Ledkov
Public bug reported:

I see the followings errors from gnome-shell on my bionic Desktop:

$ journalctl -b _PID=18271 | grep 'Failed to set'
May 24 13:13:33 sochi gnome-shell[18271]: Failed to set the markup of the actor 
'ClutterText': Error on line 1: Entity did not end with a semicolon; most 
likely you used an ampersand character without intending to start an entity - 
escape ampersand as 
May 24 14:07:18 sochi gnome-shell[18271]: Failed to set the markup of the actor 
'ClutterText': Error on line 1 char 28: Odd character 'S', expected a '=' after 
attribute name 'Less-than' of element ':'
May 24 14:07:18 sochi gnome-shell[18271]: Failed to set the markup of the actor 
'ClutterText': Error on line 1 char 28: Odd character 'S', expected a '=' after 
attribute name 'Less-than' of element ':'
May 24 14:07:19 sochi gnome-shell[18271]: Failed to set the markup of the actor 
'ClutterText': Error on line 1 char 28: Odd character 'S', expected a '=' after 
attribute name 'Less-than' of element ':'
May 24 14:07:19 sochi gnome-shell[18271]: Failed to set the markup of the actor 
'ClutterText': Error on line 1 char 28: Odd character 'S', expected a '=' after 
attribute name 'Less-than' of element ':'

There are no additional / relevant messages around these.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May 24 14:43:54 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2012-01-12 (2323 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2018-01-11 (132 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages uec-images

** Summary changed:

- ailed to set the markup of the actor 'ClutterText': Error on line 1 char 28: 
Odd character 'S', expected a '=' after attribute name 'Less-than' of element 
':'
+ Failed to set the markup of the actor 'ClutterText': Error on line 1 char 28: 
Odd character 'S', expected a '=' after attribute name 'Less-than' of element 
':'

-- 
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/1773177

Title:
  Failed to set the markup of the actor 'ClutterText': Error on line 1
  char 28: Odd character 'S', expected a '=' after attribute name 'Less-
  than' of element ':'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773177/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

2018-05-24 Thread Dimitri John Ledkov
journald appears to sigabort upon rotating systemd journal file, in
fsync... 

#0  0x7f6d47f7c237 in fsync (fd=46) at ../sysdeps/unix/sysv/linux/fsync.c:27
resultvar = 0
sc_cancel_oldtype = 0
sc_ret = 
#1  0x7f6d47abf6a0 in fsync_directory_of_file.lto_priv.56 (fd=) at ../src/journal/journal-file.c:483
path = 0x55c0f3ce1540 "/var/log/journal//system@-00-000.journal"
dn = 0x55c0f3cda680 "/var/log/journal/"
dfd = 46
st = {st_dev = 64768, st_ino = 29360293, st_nlink = 1, st_mode = 33184, 
st_uid = 0, st_gid = 101, __pad0 = 0, st_rdev = 0, st_size = 134217728, 
st_blksize = 4096, st_blocks = 262152, st_atim = {tv_sec = 1523965107, tv_nsec 
= 217770755}, st_mtim = {tv_sec = 1523965108, tv_nsec = 564627151}, st_ctim = 
{tv_sec = 1523965108, tv_nsec = 564627151}, __glibc_reserved = {0, 0, 0}}
r = 
#2  0x7f6d47b347a7 in journal_file_rotate (f=0x7fffc919e0c0, 
compress=, seal=, deferred_closes=0x55c0f3cd2e00) 
at ../src/journal/journal-file.c:3496
p = 0x55c0f3ce1470 "/var/log/journal//system@-00-000.journal"
l = 
old_file = 0x55c0f3d27760
new_file = 0x0
r = 
__PRETTY_FUNCTION__ = "journal_file_rotate"
#3  0x55c0f2c80f71 in do_rotate (s=, f=0x7fffc919e0c0, 
name=0x55c0f2c8bae7 "system", seal=, uid=0) at 
../src/journal/journald-server.c:466
#4  0x55c0f2c810ce in server_rotate (s=0x7fffc919e020) at 
../src/journal/journald-server.c:488
#5  0x55c0f2c8372b in write_to_journal (priority=6, n=21, 
iovec=0x7fffc919a880, uid=0, s=0x7fffc919e020) at 
../src/journal/journald-server.c:717
#6  dispatch_message_real (s=0x7fffc919e020, iovec=0x7fffc919a880, n=21, 
m=, c=, tv=, priority=6, 
object_pid=0) at ../src/journal/journald-server.c:877
#7  0x55c0f2c83a78 in server_driver_message (s=0x7fffc919e020, 
object_pid=, message_id=, format=) 
at ../src/journal/journald-server.c:911
#8  0x55c0f2c88692 in dev_kmsg_record (l=163, p=, 
s=0x7fffc919e020) at ../src/journal/journald-kmsg.c:160
#9  server_read_dev_kmsg (s=, s=) at 
../src/journal/journald-kmsg.c:346
#10 0x7f6d47abb160 in source_dispatch (s=s@entry=0x55c0f3cd44d0) at 
../src/libsystemd/sd-event/sd-event.c:2303
#11 0x7f6d47abb3fa in sd_event_dispatch (e=, 
e@entry=0x55c0f3cd3f10) at ../src/libsystemd/sd-event/sd-event.c:2663
#12 0x7f6d47abb589 in sd_event_run (e=, 
timeout=18446744073709551615) at ../src/libsystemd/sd-event/sd-event.c:2723
#13 0x55c0f2c78b16 in main (argc=, argv=) at 
../src/journal/journald.c:110

** Also affects: systemd (Ubuntu Cosmic)
   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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1773148

Title:
  /lib/systemd/systemd-
  
journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773148/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (22s / no limit)"

2018-05-18 Thread Dimitri John Ledkov
@Daniel van Vugt (vanvugt)

Does pressing Enter causes the system to reboot, after it hangs?

Do you see a plymouth purple screen instructing you to remove
installation media and hit enter?

Do you see a console text message instructing you to "Remove
installation media and reboot" (meaning hard-reset)?

** Also affects: casper (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: systemd (Ubuntu Bionic)

-- 
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/1706939

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (22s / no limit)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

2018-05-18 Thread Dimitri John Ledkov
Removing systemd, as I believe there is nothing to be changed in systemd
for this fix to land.

Are the affected users fixed with the proposed kernel? Please test
proposed kernel asap! Otherwise the change will be dropped from the
kernel again on xenial =(

** No longer affects: systemd (Ubuntu)

** No longer affects: systemd (Ubuntu Xenial)

** No longer affects: systemd (Ubuntu Bionic)

-- 
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/1726930

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

2018-05-18 Thread Dimitri John Ledkov
** Also affects: klibc (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   Importance: Medium
 Assignee: Seth Forshee (sforshee)
   Status: Fix Released

** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Cosmic)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Bionic)
   Status: New => 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/1760106

Title:
  FFe: Enable configuring resume offset via sysfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1760106/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1768104] Re: systemd sometimes misdetects Xen VMs (fixed up-stream)

2018-05-18 Thread Dimitri John Ledkov
** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Description changed:

+ Cherrypick
+ 
https://github.com/systemd/systemd/commit/3776f9cf00b163eedeb0325691d23df11385cbc5
+ 
  It appears that Xen-based VMs sometimes report themselves as Microsoft
  Hyper-V via CPUID — apparently this is for compatibility with Windows
  guests. systemd 237 (as found in Bionic) gives preference to this CPUID
  information when detecting Xen, and thus it erroneously assumes that the
  guest is running under Hyper-V. This causes Xen-related services (and
  anything else that relies on systemd's VM-detection functionality) to
  fail.
  
  I *believe* this is a regression from systemd 229 as used in Xenial — we
  have at least a few Xen-based VMs that report as Hyper-V via CPUID and
  don't have this issue on that version — but i haven't confirmed that for
  certain.
  
  Anyway, i've submitted a ticket with more details to the up-stream
  project, and that has now been resolved through a fairly simple change
  which applies cleanly to the Bionic systemd sources:
  
  https://github.com/systemd/systemd/issues/8844
  
  Would it be possible to pull this down? As mentioned, Xen-based Ubuntu
  VMs can seriously misbehave without it.
  
  Thanks!
  
  See also: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728573
  
  ---
  
  % lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  
  % apt-cache policy systemd
  systemd:
-   Installed: 237-3ubuntu10
-   Candidate: 237-3ubuntu10
-   Version table:
-  *** 237-3ubuntu10 500
- 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 237-3ubuntu10
+   Candidate: 237-3ubuntu10
+   Version table:
+  *** 237-3ubuntu10 500
+ 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ 100 /var/lib/dpkg/status

-- 
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/1768104

Title:
  systemd sometimes misdetects Xen VMs (fixed up-stream)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1768104/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

2018-05-18 Thread Dimitri John Ledkov
** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
   Status: Confirmed

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1766969

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1771858] Re: /snap/bin not in default PATH for units

2018-05-18 Thread Dimitri John Ledkov
** Description changed:

  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.
  
  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).
+ 
+ Since v232 systemd provides support for environment generators, snapd
+ should package/ship a snippet that injects the correct snapd path into
+ systemd environment.
+ 
+ E.g.:
+ 
+ $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
+ $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
+ sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
+ 
+ Something similar can be done for user-environment-generators too. Note
+ that user-environment-generators can generate unique variables per user.
+ 
+ Note please use /usr/lib path, as it appears that /lib/systemd path is
+ not working atm. Will check if that needs to be fixed up.

** Also affects: snapd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Cosmic)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: systemd (Ubuntu Xenial)
   Status: New => Confirmed

** Description changed:

  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.
  
  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).
  
  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.
  
  E.g.:
  
  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
  
  Something similar can be done for user-environment-generators too. Note
  that user-environment-generators can generate unique variables per user.
  
  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.
+ 
+ systemd in xenial does not support system-environment-generators, thus
+ we probably need to upload a patch to change the DEFAULT_PATH compiled
+ in default there.

** Summary changed:

- /snap/bin not in default PATH for units
+ /snap/bin not in default PATH for units, snapd should ship 
system-environment-generators to inject /snap/bin into $PATH

** Description changed:

  This means that software installed via snap isn't transparently
  available for units to use.  As snaps are first-class citizens in
  Ubuntu, we should update the PATH.
  
  Specifically, this is evident by e.g. $ systemd-run env. Or any other
  daemons that spawn shell scripts (e.g. cloud-init metadata acquired
  shell hooks, etc.).
  
  Since v232 systemd provides support for environment generators, snapd
  should package/ship a snippet that injects the correct snapd path into
  systemd environment.
  
  E.g.:
  
  $ sudo mkdir -p /usr/lib/systemd/system-environment-generators
  $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \
  sudo tee /usr/lib/systemd/system-environment-generators/90-snapd
  
  Something similar can be done for user-environment-generators too. Note
  that user-environment-generators can generate unique variables per user.
  
  Note please use /usr/lib path, as it appears that /lib/systemd path is
  not working atm. Will check if that needs to be fixed up.
  
  systemd in xenial does not support system-environment-generators, thus
  we probably need to upload a patch to change the DEFAULT_PATH compiled
  in default there.
+ 
+ [Testcase]
+ 
+ $ systemd-run /usr/bin/env
+ $ journalctl -e | grep PATH
+ 
+ Output should contain /snap/bin

-- 
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/1771858

Title:
  /snap/bin not in default PATH for units, snapd should ship system-
  environment-generators to inject /snap/bin into $PATH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1771791] Re: Need to pre-depend on stuff used by systemctl, so systemctl works in other package's preinst

2018-05-18 Thread Dimitri John Ledkov
** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Cosmic)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1771791

Title:
  Need to pre-depend on stuff used by systemctl, so systemctl works in
  other package's preinst

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771791/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1771858] Re: /snap/bin not in default PATH for units

2018-05-18 Thread Dimitri John Ledkov
** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1771858

Title:
  /snap/bin not in default PATH for units

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771858/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04

2018-05-17 Thread Dimitri John Ledkov
Please provide the contents of /etc/netplan on the affected systems, and
please let me know, if removing files in said directory makes networkd
ignore interfaces.

Please provide output of $ networkctl

By default, if there is no netplan configuration, networkd does not
"force use of systemd-networkd" and "does not interferes with ifupdown".
Thus specifics about your system are required to describe the bug in
detail and/or eventually fix Ubuntu or specific systems in question.

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

** Also affects: ifupdown (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ifupdown (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/1771236

Title:
  forced use of systemd-networkd interferes with ifupdown in 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1771236/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1762385] Re: dell_wmi: Unknown key codes

2018-05-14 Thread Dimitri John Ledkov
** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   Importance: Medium
 Assignee: Kai-Heng Feng (kaihengfeng)
   Status: Confirmed

** Also affects: systemd (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: linux (Ubuntu Cosmic)

-- 
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/1762385

Title:
  dell_wmi: Unknown key codes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1767172] Re: Regression: /etc/modules checked against blacklist

2018-05-01 Thread Dimitri John Ledkov
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1767172

Title:
  Regression: /etc/modules checked against blacklist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767172/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1766747] Re: package apt-config-icons (not installed) failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 127

2018-04-25 Thread Dimitri John Ledkov
*** This bug is a duplicate of bug 1765803 ***
https://bugs.launchpad.net/bugs/1765803

Can you please attach the tarball of /var/log/installer?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1766747

Title:
  package apt-config-icons (not installed) failed to install/upgrade:
  dpkg-deb --control subprocess returned error exit status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1766747/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1765724] Re: Xenial -> Bionic - System fails to boot after upgrade - systemd-cryptsetup@cryptswap1.service fails to start

2018-04-24 Thread Dimitri John Ledkov
>From dist-upgrade logs:
2018-04-23 09:04:43,230 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to 
execute child process "./xorg_fix_proprietary.py" (No such file or directory) 
(8))

>From journal:
screensaver is broken?
Apr 23 14:17:10 ubuntu org.gnome.ScreenSaver[1341]: Unable to init server: 
Could not connect: Connection refused
Apr 23 14:17:10 ubuntu gnome-screensav[1390]: Cannot open display: 

gnome-shell fails to start?
Apr 23 14:17:12 ubuntu gnome-shell[1606]: Failed to create backend: Could not 
find a primary drm kms device
Apr 23 14:17:12 ubuntu gnome-session[1355]: gnome-session-binary[1355]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Apr 23 14:17:12 ubuntu gnome-session-binary[1355]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Apr 23 14:17:12 ubuntu gnome-session-binary[1355]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
Apr 23 14:17:12 ubuntu gdm-launch-environment][1195]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
Apr 23 14:17:12 ubuntu systemd-logind[1028]: Removed session c1.
Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No 
data available

Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] Activating 
service name='org.gnome.ScreenSaver' requested by ':1.3' (uid=121 pid=1647 
comm="/usr/lib/gnome-session/gnome-session-binary --auto
Apr 23 14:17:12 ubuntu org.gnome.ScreenSaver[1645]: Unable to init server: 
Could not connect: Connection refused
Apr 23 14:17:12 ubuntu gnome-screensav[1654]: Cannot open display: 
Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] Activated 
service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver exited 
with status 1
Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: 
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling 
StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.f
Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: CRITICAL: Unable to create a 
DBus proxy for GnomeScreensaver: Error calling StartServiceByName for 
org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error
Apr 23 14:17:12 ubuntu gnome-shell[1656]: Failed to create backend: Could not 
find a primary drm kms device
Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: 
WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: WARNING: App 
'org.gnome.Shell.desktop' exited with code 1
Apr 23 14:17:12 ubuntu gnome-session-binary[1647]: Unrecoverable failure in 
required component org.gnome.Shell.desktop
Apr 23 14:17:12 ubuntu gdm-launch-environment][1627]: 
pam_unix(gdm-launch-environment:session): session closed for user gdm
Apr 23 14:17:12 ubuntu gdm3[1187]: GdmDisplay: display lasted 0.292659 seconds
Apr 23 14:17:12 ubuntu systemd-logind[1028]: Removed session c2.
Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No 
data available
Apr 23 14:17:12 ubuntu spice-vdagentd[1186]: Error getting active session: No 
data available
Apr 23 14:17:12 ubuntu gdm3[1187]: Child process -1643 was already dead.


This looks like a virtual machine, no? What graphics card does it have 
configured? is it QLX? and is the virtual machine using UEFI or BIOS? Is KVM 
available?


** Changed in: cryptsetup (Ubuntu)
   Status: New => Invalid

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Xenial -> Bionic - System fails to boot after upgrade - 
systemd-cryptsetup@cryptswap1.service fails to start
+ Xenial -> Bionic - System fails to boot after upgrade - gnome-screensaver & 
gnome-shell fail to start?

** Description changed:

  Test Case:
  1. Install Xenial Desktop with encrypted home
  2. Upgrade to bionic
  3. Reboot
  
  Actual Result
- The system hangs on boot when it activates the encrypted swap. There are the 
following entries in the journal:
+ The system appears to fail to start gnome-shell / gnome-screensaver:
+ 
+ Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] 
Activating service name='org.gnome.ScreenSaver' requested by ':1.3' (uid=121 
pid=1647 comm="/usr/lib/gnome-session/gnome-session-binary --auto
+ Apr 23 14:17:12 ubuntu org.gnome.ScreenSaver[1645]: Unable to init server: 
Could not connect: Connection refused
+ Apr 23 14:17:12 ubuntu gnome-screensav[1654]: Cannot open display:
+ Apr 23 14:17:12 ubuntu dbus-daemon[1645]: [session uid=121 pid=1645] 
Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver 
exited with status 1
+ Apr 23 14:17:12 ubuntu gnome-session[1647]: gnome-session-binary[1647]: 
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling 
StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.f
+ Apr 23 14:17:12 ubuntu 

[Bug 1766567] Re: rsyslog config of tmpfiles generates bogus log messages

2018-04-24 Thread Dimitri John Ledkov
Package: rsyslog 8.16.0-1ubuntu10

Package out of date, please upgrade, and check if it resolves the
problem you report...


** Changed in: systemd (Ubuntu)
   Status: New => Invalid

** Changed in: rsyslog (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1766567

Title:
  rsyslog config of tmpfiles generates bogus log messages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1766567/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1761630] Re: journald takes over /dev/log in bionic, impacts usability of syslog querying

2018-04-22 Thread Dimitri John Ledkov
Removing systemd task, as the fixes are only needed in the rsyslog
package w.r.t. permissions used.

** No longer affects: systemd (Ubuntu Bionic)

** No longer affects: systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1761630

Title:
  journald takes over /dev/log in bionic, impacts usability of syslog
  querying

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1761630/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1751813] Re: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr]

2018-04-19 Thread Dimitri John Ledkov
In light of comment #51 above, I shall pursue uploading a udev-udeb with
modprobe.d config snippet that forces scsi_mod.scan=sync.

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => In Progress

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Critical

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-18.04

** Changed in: debian-installer (Ubuntu)
Milestone: later => ubuntu-18.04

-- 
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/1751813

Title:
  Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array
  [S822L] [ipr]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751813/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1765173] Re: networkd waits 10 seconds for ipv6 network discovery by default

2018-04-19 Thread Dimitri John Ledkov
in summary the consensus is as follows:

- cloud-init should not provide accept-ra key to netplan.io
- netplan.io should not emit any accept-ra keys to networkd
- networkd, when not receiving any accept-ra keys should use kernel implicit 
default
- networkd, when in implicit RA mode, should not block on getting RA as a 
pre-condition for a link to become ready

I believe cloud-init & netplan.io portions are done already.

** Changed in: cloud-init (Ubuntu)
   Status: New => Fix Released

** Changed in: netplan.io (Ubuntu)
   Status: New => Fix Released

** Changed in: systemd (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1765173

Title:
  networkd waits 10 seconds for ipv6 network discovery by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1765173/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1765463] Re: Bionic: systemd: rename interface

2018-04-19 Thread Dimitri John Ledkov
/etc/systemd/netword/uplink0.link

that's invalid path, no?

/etc/systemd/network/ is the right path, and should work.


** Changed in: systemd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1765463

Title:
  Bionic: systemd: rename interface

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765463/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1762899] Re: /etc/resolv.conf empty after upgrading from 16.04 to 18.40

2018-04-12 Thread Dimitri John Ledkov
resolvconf (1.79ubuntu10) bionic; urgency=medium

  * Fix race of not injecting resolved config into resolvconf on LXD
container boot. LP: #1763108

 -- Dimitri John Ledkov <x...@ubuntu.com>  Thu, 12 Apr 2018 12:46:24
+0100

** Changed in: systemd (Ubuntu Bionic)
   Status: Triaged => Fix Released

** Package changed: systemd (Ubuntu Bionic) => resolvconf (Ubuntu
Bionic)

-- 
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/1762899

Title:
  /etc/resolv.conf empty after upgrading from 16.04 to 18.40

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1762899/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1763108] Re: xenial2bionic release upgrade loses DNS: empty resolv.conf

2018-04-12 Thread Dimitri John Ledkov
** Package changed: systemd (Ubuntu) => resolvconf (Ubuntu)

** Changed in: resolvconf (Ubuntu)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1763108

Title:
  xenial2bionic release upgrade loses DNS: empty resolv.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1763108/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration

2018-04-11 Thread Dimitri John Ledkov
May I backtrack a bit, and ask how is this system configured? And is it
a desktop or a server configuration? Is it a fresh install or an
upgrade?

Specifically, what I am confused about is how the networking is
configured and where /etc/resolv.conf is pointing at.

I see that NetworkManager and ifupdown were mentioned. Do you have both
of these configured and try to manage a) networking b) /etc/resolv.conf?

And what are the steps to reproduce this? Ideally with something simple
and reproducible like a lxd container launched with $ lxd launch ubuntu-
daily:artful test-container

Note that overriding make_resolv_conf() is a good thing, and it should
not at all be used. None of our network configuration tools rely on
make_resolv_conf() which is an extremely bad interface that writes out a
static file and looses information, as it assumes that there is only
ever one interface and one dhcp. Hence you will notice that everything
(networkd+resolved, ifupdown+resolvconf, networkmanager) overridee
make_resolv_conf.

I'm not quite sure what was done to your system, but resolvconf can be
used to managed the /etc/resolv.conf and that is integrated with
resolved. You will notice that resolved stub nameserver is pulled into
resolvconf config, and thus resolvconf can own /etc/resolv.conf which is
what happens on upgrades.

Please update the bug description on how to reproduce the problem you
are seeing, without ranting or jumping to conclusions, or trying to make
any unnecessary changes, because it is hard to understand what you are
trying to achieve, which may have been made worse with unnecessary
workarounds.

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

** Changed in: resolvconf (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/1745463

Title:
  Disabling systemd-resolved breaks dhclient resolvconf integration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1762386] Re: [FFe] Add networkd-dispatcher

2018-04-11 Thread Dimitri John Ledkov
** Package changed: ubuntu => networkd-dispatcher (Ubuntu)

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Fix Committed

** Changed in: networkd-dispatcher (Ubuntu)
   Status: Triaged => Fix Released

-- 
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/1762386

Title:
  [FFe] Add networkd-dispatcher

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1762386/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1748095] Re: Non-root user can reboot machine from the command line

2018-04-09 Thread Dimitri John Ledkov
This is desktop policy decision that a logged in user can shut down the
machine, this is expected behavior, and that's how / why clicking the
power button in top right corner -> shutdown icon works. Ditto long
clicking that shutdown icon works to suspend the machine too.

Being physical user on the physical display console, means one can pull
the power cord too, no need for sudo to do that.

If you don't want regular users to be able to shutdown the machine,
adjust the policy on your system accordingly.

** Changed in: systemd (Ubuntu)
   Status: New => Opinion

-- 
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/1748095

Title:
  Non-root user can reboot machine from the command line

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748095/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1752202] Re: U2F not working after upgrade: systemd dropped udev rules and libu2f-udev not installed

2018-04-09 Thread Dimitri John Ledkov
** Package changed: systemd (Ubuntu) => ubuntu-meta (Ubuntu)

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1752202

Title:
  U2F not working after upgrade: systemd dropped udev rules and libu2f-
  udev not installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1752202/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1748147] Re: Upgrading systemd sets incorrect permissions on /var/log/

2018-04-09 Thread Dimitri John Ledkov
** Also affects: rsyslog (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1748147

Title:
  Upgrading systemd sets incorrect permissions on /var/log/

To manage notifications about this bug go to:
https://bugs.launchpad.net/debhelper/+bug/1748147/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1730028] Re: logspam about Duplicate line for path "/var/log"

2018-04-09 Thread Dimitri John Ledkov
** Also affects: rsyslog (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

** Changed in: rsyslog (Ubuntu)
   Status: New => Confirmed

** Changed in: rsyslog (Ubuntu)
   Importance: Undecided => High

** Changed in: rsyslog (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1730028

Title:
  logspam about Duplicate line for path "/var/log"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1730028/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1731522] Re: systemd-resolved does not listen on TCP port, cannot serve large records (Cannot ping pod51041.outlook.com but can dig.)

2018-04-05 Thread Dimitri John Ledkov
This has totally slipped my radar, I'm sorry.

I will ensure this lands into bionic 18.04.0.


** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-18.04

** Also affects: systemd (Ubuntu Bionic)
   Importance: High
 Assignee: Dimitri John Ledkov (xnox)
   Status: Triaged

** Also affects: systemd (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Artful)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: systemd (Ubuntu Artful)
Milestone: None => artful-updates

** Changed in: systemd (Ubuntu Artful)
   Status: New => Triaged

** 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/1731522

Title:
  systemd-resolved does not listen on TCP port, cannot serve large
  records (Cannot ping pod51041.outlook.com but can dig.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1731522/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

2018-04-04 Thread Dimitri John Ledkov
@rrs
> BTW, does Ubuntu have the systemd/udevd mount propagation fix included ?

yes no maybe =

Added in debian at ed16ca8690eb69c248a0a741def5324eedc9149d
Removed from debian at d529d047752d8492d43e42e8b4223d6d37fa3dd3
Meaning it was for a while, if you mean the Debian bug linked to this bug 
report.
But not since laptop-mode-tools 1.68 was fixed.

I believe the debian bug attached to this bug report is a red herring.

https://git.launchpad.net/~ubuntu-core-dev/+git/systemd/commit/?h
=ubuntu-bionic=ed16ca8690eb69c248a0a741def5324eedc9149d

https://git.launchpad.net/~ubuntu-core-
dev/+git/systemd/commit/?h=d529d047752d8492d43e42e8b4223d6d37fa3dd3

** No longer affects: systemd (Debian)

** Changed in: systemd (Ubuntu Bionic)
   Status: Confirmed => 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/1726930

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+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

2018-04-04 Thread Dimitri John Ledkov
@superm1

It would have been nice to coordinate systemd uploads, this is by far,
not the only patch set that needs uploading for systemd.

** Tags added: block-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to 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 1760598] Re: I/O Error after clicking "reboot now" - Ubuntu font missing from casper shutdown

2018-04-04 Thread Dimitri John Ledkov
** Summary changed:

- I/O Error after clicking "reboot now"
+ I/O Error after clicking "reboot now" - Ubuntu font missing from casper 
shutdown

** Also affects: casper (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: casper (Ubuntu)
   Status: New => Confirmed

** Description changed:

+ ubuntu Plymouth theme now correctly uses Ubuntu font, meaning it needs
+ to be cached for display of the shutdown message.
+ 
+ We really should be using shutdown initramfs on the livecd
+ 
+ --
+ 
  Tested in Virtualbox VM.
  Ubuntu MATE works after force-reboot, but after I click on "restart now" 
after completing the installation, the screen shows me this:
  
  req_error: I/O error, dev sr0, sector 1488792
  
  And the above message loops a couple times, and wont turn off the
  computer to restart.
  
  No error happens after force reboot, and the OS boots properly, but I'm
  curious as to what's causing this.

** Changed in: casper (Ubuntu)
   Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1760598

Title:
  I/O Error after clicking "reboot now" - Ubuntu font missing from
  casper shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1760598/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

2018-04-04 Thread Dimitri John Ledkov
@vanvugt
@mc3man

This bug was specifically about the Ubuntu Desktop Installer, and the
experience one has with it.

Are you experiencing something similar, on the installed system, after
the installation is done and you use Ubuntu normally? In that case
that's a separate issue. Please open a new bug.

If people experience shutdown issues of the live image, please clearly
state which image serial is used and what the symptoms are and how to
reproduce it.

-- 
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/1706939

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1736072] Re: Encrypted swap does not work

2018-04-03 Thread Dimitri John Ledkov
I am confused about the original statement "Ubiquity then have proposed
to set an encrypted swap dir" because ubiquity does not propose to do
such things at all.

By default we do not create swap partitions, in the full disk encryption
case we use LVM and encrypt the whole VG which contains swap as an LVM
volume, home directory encryption has been removed.

Please indicate the steps performed in ubiquity that yielded "an
ecrypted swap dir"?

** Changed in: ubiquity (Ubuntu Bionic)
   Status: New => Incomplete

** No longer affects: ubiquity (Ubuntu Bionic)

** No longer affects: systemd (Ubuntu Bionic)

** No longer affects: cryptsetup (Ubuntu Bionic)

-- 
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/1736072

Title:
  Encrypted swap does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1736072/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1758865] Re: regression artful sru upgrade

2018-03-26 Thread Dimitri John Ledkov
** Changed in: systemd (Ubuntu Artful)
   Status: New => In Progress

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1758865

Title:
  regression artful sru upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1758865/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"

2018-03-26 Thread Dimitri John Ledkov
Ubiquity should not be booting anymore awaiting network configuration
(i.e. systemd-networkd-wait-online is not enabled). Is there anything
else to do for this bug report?

** Changed in: systemd (Ubuntu Bionic)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1706939

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (21s / no limit)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1758273] Re: DD2.2 freezes/hangs after 20mins of uptime

2018-03-26 Thread Dimitri John Ledkov
During installation 'ubuntu-desktop' was selected, and is still
installed.

Thus this is a desktop system, and looks like it behaves correctly for a
desktop system.

If you wish to configure your desktop differently please see System
preferences -> power -> Suspend & Power Button -> Automatic suspend
settings.

Please note, that Ubuntu Desktop is not supported on ppc64el, and there
genuinly should be no reason to install and configure a desktop
environment. In general port-forwarding and ssh should be sufficient to
accomplish anything. (e.g. to use a client web-browser to access a
webserver serving to localhost only, etc).

I will mark this bug invalid, as everything appears to work as expected.

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: ubuntu-power-systems
   Status: Incomplete => 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/1758273

Title:
  DD2.2 freezes/hangs after 20mins of uptime

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1758273/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

  1   2   3   4   5   >