from:"Mathieu"

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1864301/+attachment/5330541/+files/GsettingsChanges.txt

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

Title:
  Resizing LibreOffice style window causes Gnome-Shell to freeze for 10
  seconds

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

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

[Bug 1864301] ShellJournal.txt

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1864301/+attachment/5330544/+files/ShellJournal.txt

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

Title:
  Resizing LibreOffice style window causes Gnome-Shell to freeze for 10
  seconds

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

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

[Bug 1864301] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1864301/+attachment/5330543/+files/ProcEnviron.txt

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

Title:
  Resizing LibreOffice style window causes Gnome-Shell to freeze for 10
  seconds

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

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

[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds

Hi Daniel,

I updated the bug information via apport-collect.

I don't have the time to test Ubuntu 20.04 ISO, sorry.

Thanks.

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

Title:
  Resizing LibreOffice style window causes Gnome-Shell to freeze for 10
  seconds

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

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

[Bug 1864301] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1864301/+attachment/5330542/+files/ProcCpuinfoMinimal.txt

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

Title:
  Resizing LibreOffice style window causes Gnome-Shell to freeze for 10
  seconds

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

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

[Bug 1864301] monitors.xml.txt

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/1864301/+attachment/5330545/+files/monitors.xml.txt

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

Title:
  Resizing LibreOffice style window causes Gnome-Shell to freeze for 10
  seconds

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

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

[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds

apport information

** Tags added: apport-collected

** Description changed:

  When I open LibreOffce Writer and decides to resize the Style window on
  the right of the screen (press F11 to toggle this window), Gnome-Shell
  completely freezes for a few seconds.
  
  I already rebooted and it's 100% reproducible.
  
  I initially reported this bug on Gnome-Shell Gitlab:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225#note_715411
  
  You can find more info there (journalctl logs)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.4
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-09-26 (150 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
+ RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
+ Tags:  eoan
+ Uname: Linux 5.3.0-40-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1864301/+attachment/5330540/+files/Dependencies.txt

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

Title:
  Resizing LibreOffice style window causes Gnome-Shell to freeze for 10
  seconds

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

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

[Bug 1864301] [NEW] Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds

2020-02-22 Thread Mathieu Tarral

Public bug reported:

When I open LibreOffce Writer and decides to resize the Style window on
the right of the screen (press F11 to toggle this window), Gnome-Shell
completely freezes for a few seconds.

I already rebooted and it's 100% reproducible.

I initially reported this bug on Gnome-Shell Gitlab:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225#note_715411

You can find more info there (journalctl logs)

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

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

Title:
  Resizing LibreOffice style window causes Gnome-Shell to freeze for 10
  seconds

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

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

[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds

2020-02-22 Thread Mathieu Tarral

System info:

Ubuntu 19.10
gnome-shell: 3.34.1+git20191024-1ubuntu1~19.10.1

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

Title:
  Resizing LibreOffice style window causes Gnome-Shell to freeze for 10
  seconds

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

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

[Bug 1851322] Re: VPN auto-connect is not working

2019-12-08 Thread Mathieu Tarral

@Daniel bug reported upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2008

It seems that today, even manually triggering the VPN connection doesn't work 
anymore.
If you don't set "store password for all users" for the VPN credentials, the 
connection will fails.

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2008
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/2008

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

Title:
  VPN auto-connect is not working

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

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

[Bug 1851992] Re: Lock screen not locking upon resume (org.gnome.desktop.lockdown disable-lock-screen set to true for some reason)

2019-12-05 Thread Mathieu Tarral

** Information type changed from Private Security to Public

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

Title:
  Lock screen not locking upon resume (org.gnome.desktop.lockdown
  disable-lock-screen set to true for some reason)

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

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

[Bug 1852908] [NEW] Reboot button does nothing on login screen

2019-11-17 Thread Mathieu Tarral

Public bug reported:

Hi,

When I'm boot my computer and the Gnome Shell login screen appears, if I
try to reboot the computer from the menu available in the top right, the
button does nothing.

I tried clicking multiple times, my computer won't reboot.

However, If i'm logged into my desktop, and then ask for a reboot, it
works.

So either there is a permission issue to reboot on Gnome Shell login
screen, or there is a deeper issue here.

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 17 13:52:59 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-09-26 (51 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Reboot button does nothing on login screen

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

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

[Bug 1851322] Re: VPN auto-connect is not working

2019-11-06 Thread Mathieu Tarral

I would rather not getting involved into too many bugtrackers, and as a
Ubuntu user, remain on Launchpad and provide the required information to
let you investigate.

Also, as you are a member of Ubuntu teams, you have more
authority/credibility than me, so that bug can be taken seriously by
Gnome-shell teams.

Thanks Sebastien.

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

Title:
  VPN auto-connect is not working

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

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

[Bug 1718931] Re: No VPN autoconnect

2019-10-24 Thread Mathieu Tarral

Hi,

I upgraded from 19.04 to 19.10, thinking that this would have solved the
bug since Gnome-shell is now 3.34, but the issue is still here.

I have no VPN auto-connect on Wifi network, but doing it manually works.

Please can you finally fix this ?

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

Title:
  No VPN autoconnect

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1718931/+subscriptions

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

[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

Split up unicode-data into its own bug; bug 1838323.

** No longer affects: unicode-data (Ubuntu)

** No longer affects: gnome-characters (Ubuntu Xenial)

** No longer affects: gnome-characters (Ubuntu Disco)

** No longer affects: gucharmap (Ubuntu Xenial)

** No longer affects: gucharmap (Ubuntu Bionic)

** No longer affects: gucharmap (Ubuntu Disco)

** No longer affects: icu (Ubuntu Xenial)

** No longer affects: icu (Ubuntu Bionic)

** No longer affects: icu (Ubuntu Disco)

** No longer affects: unicode-data (Ubuntu Xenial)

** No longer affects: unicode-data (Ubuntu Bionic)

** No longer affects: unicode-data (Ubuntu Disco)

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

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

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

[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

icu split up into bug 1838322.

** Changed in: openjdk-8 (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: openjdk-8 (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: openjdk-8 (Ubuntu Disco)
   Status: New => Fix Released

** No longer affects: icu (Ubuntu)

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

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

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

[Bug 1838321] Re: Support Japanese new era "令和 (Reiwa)"

Fixed in eoan, just needs a rebuild in other releases with a newer
unicode-data that has Reiwa in it. Still dependent on font having the
actual glyphs included (not the case at this moment in eoan).

** Also affects: gucharmap (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

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

Title:
  Support Japanese new era "令和 (Reiwa)"

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

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

[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

gucharmap split up into bug 1838321

** No longer affects: gucharmap (Ubuntu)

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

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

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

[Bug 1838321] [NEW] Support Japanese new era "令和 (Reiwa)"

Public bug reported:

[Background]
Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）

This is the meta bug to track packages that need fixes; which packages
have already been SRUd to previous releases, how to prioritize the work
needed, and general test cases for verifying that things are working as
expected.

[Impact]
Users who run Ubuntu in Japanese.

[Test cases]

1) Search for character "SQUARE ERA NAME"
2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:

 - SQUARE ERA NAME HEISEI: ㍻
 - SQUARE ERA NAME REIWA: 令和 (in a single glyph)

Display of the Reiwa square glyph is font-specific; it may show simply
as a empty square or a square with hex characters. If that is the case,
the unicode data supports the new character, but the selected font does
not include the new glyph.


[Regression potential]
This is a potentially large change as it impacts font display, character sets 
as well as date conversions. As such, extreme care should be taken to ensure 
that regressions are avoided, such that dates previous to May 1, 2019 continue 
to display as before, and dates onward are displayed with the new era symbols. 
The included test cases account for verifying the continued behavior or 
previous dates.

** Affects: gucharmap (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: gucharmap (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: gucharmap (Ubuntu Disco)
 Importance: Undecided
 Status: New

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

Title:
  Support Japanese new era "令和 (Reiwa)"

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

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

[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

2019-06-21 Thread Mathieu Trudel-Lapierre

Looks like noto sources now have the right glyphs (since their April 9
release, actually). It will need an update both in Debian and Ubuntu.

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

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

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

[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

2019-05-21 Thread Mathieu Trudel-Lapierre

mozc appears to be all done (LP: #1823444)

** Changed in: mozc (Ubuntu Xenial)
   Status: New => Fix Released

** Changed in: mozc (Ubuntu Bionic)
   Status: New => Fix Released

** Changed in: mozc (Ubuntu Cosmic)
   Status: New => Fix Released

** Changed in: mozc (Ubuntu Disco)
   Status: New => Fix Released

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1828884/+subscriptions

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

[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

2019-05-21 Thread Mathieu Trudel-Lapierre

unicode-data in eoan does include Reiwa. Reverse-depends probably still
need to be rebuilt (I'm testing gucharmap which seemed easy enough to
patch to work).

** Changed in: unicode-data (Ubuntu)
   Status: New => Fix Released

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1828884/+subscriptions

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

[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

2019-05-21 Thread Mathieu Trudel-Lapierre

Oops; picked the wrong openjdk...

FWIW; according to the email by Mitsuya Shibata, openjdk 8 and 11 at
least are affected (so, everything prior to disco if updates are not
applied. Openjdk-8 updates appear to already be at 8u212, which should
include Reiwa support. Marking as Fix Released so we can see at a glance
that it's already been covered.

** Also affects: openjdk-13 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: unicode-data (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: poppler-data (Ubuntu)
   Importance: Undecided
   Status: New

** Description changed:

  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）
  
  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the work
  needed, and general test cases for verifying that things are working as
  expected.
  
  [Impact]
  Users who run Ubuntu in Japanese.
  
  [Test cases]
  
  == Date conversion ==
  
  On applications that support writing dates in long form, or with symbols
  to denote era (either in X00.00.00 format or in GG1G5G1G format  (G-
  glyph; X- character):
  
  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"
  
  == Date output ==
  
  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"
  
  === Displaying formatted year for Japanese era with glibc ===
  
  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)
  
  == Character maps / font support ==
  
  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:
  
   - SQUARE ERA NAME HEISEI:  ㍻
   - SQUARE ERA NAME REIWA:   令和 (in a single glyph)
  
  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the case,
  the unicode data supports the new character, but the selected font does
  not include the new glyph.
  
  == Typing / input methods ==
  
  1) Type in 'heisei'
  2) Verify that the input method in use gives you an option "平成", and 
optionally also the square era glyph.
  3) Type in 'reiwa'
  4) Verify that the input method in use gives you an option that includes 
"令和", and possibly also the square era glyph (if supported for Heisei)
  
  5) Type in the following strings, and verify that the options are provided in 
the input method:
- * "れいわ"(reiwa) => "令和"
- * "れいわ"(reiwa) => "㋿"
- * "２０１８ねん"(2018nenn) => "平成三十年"
- * "２０１８ねん"(2018nenn) => "平成三十年"
- * "２０１９ねん"(2019nenn) => "平成三十一年"
- * "２０１９ねん"(2019nenn) => "令和元年"
- * "２０２０ねん"(2020nenn) => "令和二年"
+ * "れいわ"(reiwa) => "令和"
+ * "れいわ"(reiwa) => "㋿"
+ * "２０１８ねん"(2018nenn) => "平成三十年"
+ * "２０１９ねん"(2019nenn) => "平成三十一年"
+ * "２０１９ねん"(2019nenn) => "令和元年"
+ * "２０２０ねん"(2020nenn) => "令和二年"
  
  /!\ Some fonts, like fonts-noto-cjk, currently have no glyph for U+32FF.
  
  [Regression potential]
  This is a potentially large change as it impacts font display, character sets 
as well as date conversions. As such, extreme care should be taken to ensure 
that regressions are avoided, such that dates previous to May 1, 2019 continue 
to display as before, and dates onward are displayed with the new era symbols. 
The included test cases account for verifying the continued behavior or 
previous dates.

** No longer affects: openjdk-13 (Ubuntu)

** Also affects: openjdk-8 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: openjdk-8 (Ubuntu)
   Status: New => Fix Released

** Also affects: gucharmap (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: icu (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: unicode-data (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: poppler-data (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: mozc (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: libreoffice (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: libreoffice-l10n (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: openjdk-8 (Ubuntu Disco)
   Importance: Undecided
   Status: New

**

[Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

2019-05-16 Thread Mathieu Trudel-Lapierre

I don't think it's *-control-center.

At the time, that was filed there by pitti, who correctly pointed out
that something might need to depend on libnss-myhostname (from systemd)
for a fallback to resolving hostname via just /etc/hostname (since
/etc/hosts isn't changed). At this point though, it looks like this is
no longer required.

Now, AFAICT the desktop correctly calls to systemd via dbus to ask for
the change. I'll leave to you to make sure this is indeed the case
(since you had commented on the bug previously, and I can't see any
issues changing hostname as it is now, but maybe I'm not quite doing the
same tests you were).

unity-control-center is an obvious Won't Fix for Eoan or Disco, but I'll
let the Desktop Team decide whether this needs to be fixed in other
releases.

Finally, this is still assigned to systemd, low priority, because
hostnamed *doesn't* change /etc/hosts, and probably should (at the very
least for consistency, to avoid keeping a reference to an old name for
the system); but I didn't notice ill effects from not changing that
file. sudo certainly doesn't hang here trying to resolve the new or old
hostname.

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

Title:
[hostnamed] Changing hostname doesn't update /etc/hosts

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

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

[Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

2019-05-15 Thread Mathieu Trudel-Lapierre

** Tags removed: rls-x-incoming
** Tags added: rls-ee-incoming

** Also affects: gnome-control-center (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: unity-control-center (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Changed in: unity-control-center (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [hostnamed] Changing hostname doesn't update /etc/hosts

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

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

[Bug 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"

2019-05-13 Thread Mathieu Trudel-Lapierre

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

** No longer affects: ubuntu

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

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

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

[Bug 1828884] Re: Handling Japanese new era "令和 (Reiwa)"

2019-05-13 Thread Mathieu Trudel-Lapierre

mozc appears to already be Fix Released for most releases; this has been
handled as bug 1823444.

** Description changed:

  [Background]
  Many packages are affected by the requirement to support the new era "Reiwa" 
(令和）
  
  This is the meta bug to track packages that need fixes; which packages
  have already been SRUd to previous releases, how to prioritize the work
  needed, and general test cases for verifying that things are working as
  expected.
  
  [Impact]
  Users who run Ubuntu in Japanese.
  
  [Test cases]
  
  == Date conversion ==
  
  On applications that support writing dates in long form, or with symbols
  to denote era (either in X00.00.00 format or in GG1G5G1G format  (G-
  glyph; X- character):
  
  1) Enable date formatting in each of the above formats that are supported 
(long form or symbols)
  2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" 
or "R1.05.01"
  3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" 
or "H31.4.30"
  
  == Date output ==
  
  1) Set date to 2019/05/01
  2) Output date; verify that the year it is displayed as "令和元年"
  3) Set date to 2019/04/30
  4) Output date; verify that the year is diplayed as "平成31年"
  
  === Displaying formatted year for Japanese era with glibc ===
  
  Run:
  LC_ALL=ja_JP.utf8 date +%EY -d 20190430   # previous era (should still work 
as before SRUs)
  or
  LC_ALL=ja_JP.utf8 date +%EY -d 20190501   # new era (should now correctly 
display the new era)
  
- 
  == Character maps / font support ==
  
  1) Search for character "SQUARE ERA NAME"
  2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and 
"SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and 
that the glyphs are readable:
  
-  - SQUARE ERA NAME HEISEI:  ㍻
-  - SQUARE ERA NAME REIWA:   令和 (in a single glyph)
+  - SQUARE ERA NAME HEISEI:  ㍻
+  - SQUARE ERA NAME REIWA:   令和 (in a single glyph)
  
  Display of the Reiwa square glyph is font-specific; it may show simply
  as a empty square or a square with hex characters. If that is the case,
  the unicode data supports the new character, but the selected font does
  not include the new glyph.
  
- 
  == Typing / input methods ==
  
  1) Type in 'heisei'
  2) Verify that the input method in use gives you an option "平成", and 
optionally also the square era glyph.
- 1) Type in 'reiwa'
- 2) Verify that the input method in use gives you an option that includes 
"令和", and possibly also the square era glyph (if supported for Heisei)
+ 3) Type in 'reiwa'
+ 4) Verify that the input method in use gives you an option that includes 
"令和", and possibly also the square era glyph (if supported for Heisei)
  
+ 5) Type in the following strings, and verify that the options are provided in 
the input method:
+ * "れいわ"(reiwa) => "令和"
+ * "れいわ"(reiwa) => "㋿"
+ * "２０１８ねん"(2018nenn) => "平成三十年"
+ * "２０１８ねん"(2018nenn) => "平成三十年"
+ * "２０１９ねん"(2019nenn) => "平成三十一年"
+ * "２０１９ねん"(2019nenn) => "令和元年"
+ * "２０２０ねん"(2020nenn) => "令和二年"
+ 
+ /!\ Some fonts, like fonts-noto-cjk, currently have no glyph for U+32FF.
  
  [Regression potential]
  This is a potentially large change as it impacts font display, character sets 
as well as date conversions. As such, extreme care should be taken to ensure 
that regressions are avoided, such that dates previous to May 1, 2019 continue 
to display as before, and dates onward are displayed with the new era symbols. 
The included test cases account for verifying the continued behavior or 
previous dates.

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

** Changed in: mozc (Ubuntu)
   Status: New => Fix Released

** Summary changed:

- Handling Japanese new era "令和 (Reiwa)"
+ [META] Handling Japanese new era "令和 (Reiwa)"

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

** Also affects: libreoffice-l10n (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  [META] Handling Japanese new era "令和 (Reiwa)"

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

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

[Bug 1806379] Re: [MIR] gnome-shell-extension-desktop-icons

2018-12-11 Thread Mathieu Trudel-Lapierre

MIR approved. I see no particular issues with the package after
reviewing the code; no binary deps in universe, and it's a small package
that appears like it should be well maintained in Debian and Ubuntu.

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
   Status: New => Fix Committed

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1806379

Title:
  [MIR] gnome-shell-extension-desktop-icons

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

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

[Bug 1806379] Re: [MIR] gnome-shell-extension-desktop-icons

2018-12-04 Thread Mathieu Trudel-Lapierre

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1806379

Title:
  [MIR] gnome-shell-extension-desktop-icons

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

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

[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

2018-10-30 Thread Mathieu Barquin

Hi All,
any progress here ?
Thanks

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

Title:
  gnome-shell filling up syslog with thousands of entries with stack
  traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224
  in cosmic)

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

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

[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-28 Thread Mathieu Barquin

Hi All,
any progress here ?
Thanks

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

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

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

[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-17 Thread Mathieu Barquin

Hi Daniel,
thanks, no gnome-shell extensions installed

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

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

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

[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-16 Thread Mathieu Barquin

Here is it:
athieu@PC1:/var/log$ tail -100 syslog
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #2   7fffb8a304b0 I   
self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #3   7fffb8a30560 I   
resource:///org/gnome/gjs/modules/signals.js:128 (7fa2facc18b0 @ 386)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #4   55f922a9d330 i   
resource:///org/gnome/shell/ui/layout.js:538 (7fa2faa04310 @ 127)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #5   7fffb8a314e0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #6   7fffb8a320f0 b   
self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 gnome-shell[1993]: Object St.Icon (0x55f91fad6290), has 
been already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: == Stack trace for context 
0x55f91889c1e0 ==
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #0   7fffb8a303a0 I   
resource:///org/gnome/shell/ui/osdWindow.js:223 (7fa2faac78b0 @ 231)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #1   7fffb8a30470 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #2   7fffb8a304b0 I   
self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #3   7fffb8a30560 I   
resource:///org/gnome/gjs/modules/signals.js:128 (7fa2facc18b0 @ 386)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #4   55f922a9d330 i   
resource:///org/gnome/shell/ui/layout.js:538 (7fa2faa04310 @ 127)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #5   7fffb8a314e0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #6   7fffb8a320f0 b   
self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: == Stack trace for context 
0x55f91889c1e0 ==
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #0   7fffb8a303a0 I   
resource:///org/gnome/shell/ui/osdWindow.js:224 (7fa2faac78b0 @ 273)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #1   7fffb8a30470 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #2   7fffb8a304b0 I   
self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #3   7fffb8a30560 I   
resource:///org/gnome/gjs/modules/signals.js:128 (7fa2facc18b0 @ 386)
Oct 16 17:33:33 PC1 gnome-shell[1993]: Object St.BoxLayout (0x55f91f5ab8c0), 
has been already deallocated — impossible to set any property on it. This might 
be caused by the object having been destroyed from C code using something such 
as destroy(), dispose(), or remove() vfuncs.
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #4   55f922a9d330 i   
resource:///org/gnome/shell/ui/layout.js:538 (7fa2faa04310 @ 127)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #5   7fffb8a314e0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #6   7fffb8a320f0 b   
self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: == Stack trace for context 
0x55f91889c1e0 ==
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #0   7fffb8a303a0 I   
resource:///org/gnome/shell/ui/osdWindow.js:223 (7fa2faac78b0 @ 231)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #1   7fffb8a30470 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #2   7fffb8a304b0 I   
self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #3   7fffb8a30560 I   
resource:///org/gnome/gjs/modules/signals.js:128 (7fa2facc18b0 @ 386)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #4   55f922a9d330 i   
resource:///org/gnome/shell/ui/layout.js:538 (7fa2faa04310 @ 127)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #5   7fffb8a314e0 b   
resource:///org/gnome/gjs/modules/_legacy.js:82 (7fa2facb0b80 @ 71)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #6   7fffb8a320f0 b   
self-hosted:977 (7fa2facf01f0 @ 413)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: == Stack trace for context 
0x55f91889c1e0 ==
Oct 16 17:33:33 PC1 gnome-shell[1993]: Object St.Icon (0x55f91f50e490), has 
been already deallocated — impossible to set any property on it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #0   7fffb8a303a0 I   
resource:///org/gnome/shell/ui/osdWindow.js:224 (7fa2faac78b0 @ 273)
Oct 16 17:33:33 PC1 org.gnome.Shell.desktop[1993]: #1   7fffb8a30470 b   
resource:///org/gnome/gjs/modules/_legacy.js:82

[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-16 Thread Mathieu Barquin

and:
mathieu@PC1:/var/log$ uname -a
Linux PC1 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

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

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

[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-15 Thread Mathieu Barquin

I've upgraded to 18.10 the problem is still there ...

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

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

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

[Bug 1797236] [NEW] network-manager openvpn settings not being saved

2018-10-10 Thread Mathieu Trudel-Lapierre

Public bug reported:

I'm seeing some weird issue with the new NM + openvpn; if I create a new
VPN connection, and add certificate options (verify name exactly, plus
TLS auth), these options are not saved, leading to the connection
failing.

The following versions lead to an invalid connection:
ii  network-manager   1.12.4-1ubuntu1 amd64   
network management framework (daemon and userspace tools)
ii  network-manager-openvpn   1.8.6-1 amd64   
network management framework (OpenVPN plugin core)


Reverting to the following versions, things work again:
ii  network-manager   1.12.2-0ubuntu4 amd64   
network management framework (daemon and userspace tools)
ii  network-manager-openvpn   1.8.4-1 amd64   
network management framework (OpenVPN plugin core)


If I use an existing connection saved with a prior version of NM, the 
connection will be successful. If I go open the settings, hit Apply, all 
advanced TLS settings are wiped.

The connection then fails:

Oct 10 16:58:52 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
Oct 10 16:58:52 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]91.189.91.19:443
Oct 10 16:58:52 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET]91.189.91.19:443 [nonblock]
Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP connection established with 
[AF_INET]91.189.91.19:443
Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link local: (not bound)
Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link remote: 
[AF_INET]xx.xx.xx.xx:443
Oct 10 16:58:53 demeter nm-openvpn[6538]: Connection reset, restarting [0]
Oct 10 16:58:53 demeter nm-openvpn[6538]: SIGUSR1[soft,connection-reset] 
received, process restarting
Oct 10 16:58:58 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.
Oct 10 16:58:58 demeter nm-openvpn[6538]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
Oct 10 16:58:58 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used 
remote address: [AF_INET6]2001:67c:1562:0:1::1:443
Oct 10 16:58:58 demeter nm-openvpn[6538]: Attempting to establish TCP 
connection with [AF_INET6]2001:67c:1562:0:1::1:443 [nonblock]
Oct 10 16:58:59 demeter nm-openvpn[6538]: TCP: connect to 
[AF_INET6]:xxx:xx:xx::xx:443 failed: Network is unreachable
Oct 10 16:58:59 demeter nm-openvpn[6538]: SIGUSR1[connection 
failed(soft),init_instance] received, process restarting
Oct 10 16:59:04 demeter nm-openvpn[6538]: WARNING: No server certificate 
verification method has been enabled.  See http://openvpn.net/howto.html#mitm 
for more info.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: network-manager-openvpn (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  network-manager openvpn settings not being saved

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

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

[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console

2018-09-25 Thread Mathieu Trudel-Lapierre

Bug was confirmed fix, although we don't have a formal version number
for the pacakge that was tested, let's mark this verification-done.

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-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/1767918

Title:
  Login password from GDM is shown in plain text on the VT1 console

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

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

[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console

2018-09-24 Thread Mathieu Trudel-Lapierre

@Alan,

Can you confirm which version of plymouth you had installed?

You can use the following command to do so:

dpkg -l plymouth | cat

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

Title:
  Login password from GDM is shown in plain text on the VT1 console

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

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

[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console

2018-09-18 Thread Mathieu Trudel-Lapierre

That's not what I mean though. For SRU verification we should aim to
have a positive identification of the exact version of the plymouth
package that was used for the tests.

For example, this can be achieved by looking at 'dpkg -l plymouth |
cat':

要望=(U)不明/(I)インストール/(R)削除/(P)完全削除/(H)保持
| 状態=(N)無/(I)インストール済/(C)設定/(U)展開/(F)設定失敗/(H)半インストール/(W)トリガ待ち/(T)トリガ保留
|/ エラー?=(空欄)無/(R)要再インストール (状態,エラーの大文字=異常)
||/ 名前   バージョン アーキテクチ 説明
+++-==-==--==
ii  plymouth   0.9.3-1ubuntu8 amd64boot animation, logger and I/O 
multiplexer

This is from my PC, on cosmic. The version number on bionic would be
different.

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

Title:
  Login password from GDM is shown in plain text on the VT1 console

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

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

[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console

2018-09-18 Thread Mathieu Trudel-Lapierre

@Alan, could you please confirm which version of plymouth you have
installed for the tests you did?

Thanks!

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

Title:
  Login password from GDM is shown in plain text on the VT1 console

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

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

[Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console

2018-09-11 Thread Mathieu Trudel-Lapierre

** Description changed:

- https://gitlab.gnome.org/GNOME/gdm/issues/408
+ [Impact]
+ Sessions in specific circumstances when switching to TTY while plymouth is 
being activated or deactivated.
+ 
+ [Test cases]
+ Steps to reproduce:
+ 1) Log-in using X11 login via GDM.
+ 2) Use the desktop for a while.  (For some reason I cannot reproduce if I 
login and then restart after a short while).
+ 3) In Gnome click System menu -> Power Button -> Restart
+ 4) Quickly press CTRL-ALT-F1
+ 
+ Validate whether your login password is visible on the TTY.
+ 
+ [Regression Potential]
+ Possible regressions may include difficulty showing text-mode splash or boot 
messages given that this changes the state of tty based on plymouth's own 
activation state.
  
  ---
  
- I don't which package this applies to, but I believe the best bet is
- GDM.
+ https://gitlab.gnome.org/GNOME/gdm/issues/408
+ 
+ 
+ I don't which package this applies to, but I believe the best bet is GDM.
  
  Steps to reproduce:
  1) Log-in using X11 login via GDM.
  2) Use the desktop for a while.  (For some reason I cannot reproduce if I 
login and then restart after a short while).
  3) In Gnome click System menu -> Power Button -> Restart
  4) Quickly press CTRL-ALT-F1
  5) I see my login password in plain text in the console.  Once I saw the 
login password repeated twice.
  
  See attached photo with the login password blanked out.  Below the
  password is the console cursor.
  
  ## lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  
  ## apt-cache policy gdm3
  gdm3:
    Installed: 3.28.0-0ubuntu1
    Candidate: 3.28.0-0ubuntu1
    Version table:
   *** 3.28.0-0ubuntu1 500
  500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-18.19-generic 4.15.17
  Uname: Linux 4.15.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 14:54:07 2018
  InstallationDate: Installed on 2018-04-13 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: plymouth (Ubuntu)
 Assignee: Canonical Foundations Team (canonical-foundations) => Mathieu 
Trudel-Lapierre (cyphermox)

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

Title:
  Login password from GDM is shown in plain text on the VT1 console

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

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

[Bug 1780996] Re: Convert triggers to noawait

2018-07-12 Thread Mathieu Trudel-Lapierre

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

** Changed in: fusiondirectory (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

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

Title:
  Convert triggers to noawait

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

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

[Bug 1780996] Re: Convert triggers to noawait

2018-07-12 Thread Mathieu Trudel-Lapierre

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

** Changed in: fusiondirectory (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  Convert triggers to noawait

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

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

[Bug 1780996] Re: Convert triggers to noawait

2018-07-11 Thread Mathieu Trudel-Lapierre

dovecot for cosmic and bionic already changed to noawait triggers by
Debian maintainer.

** Changed in: dovecot (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: dovecot (Ubuntu Bionic)
   Status: New => Fix Released

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

** Changed in: dovecot (Ubuntu Xenial)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  Convert triggers to noawait

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

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

[Bug 1780996] Re: Convert triggers to noawait

2018-07-11 Thread Mathieu Trudel-Lapierre

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

** Changed in: dovecot (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  Convert triggers to noawait

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

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

[Bug 1770082] Re: systemd-networkd not renaming devices on boot

2018-06-29 Thread Mathieu Trudel-Lapierre

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

** Changed in: nplan (Ubuntu)
   Status: New => Fix Released

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

Title:
  systemd-networkd not renaming devices on boot

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

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

[Bug 1768088] Re: can't activate 2 independent reachable interface

2018-05-25 Thread Mathieu Trudel-Lapierre

Still a bug; if systemd-networkd requires a restart, then systemd-
networkd has something that it gets confused about, that we'll need to
figure out.

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

Title:
  can't activate 2 independent reachable interface

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

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

[Bug 1770082] Re: systemd-networkd not renaming devices on boot

2018-05-25 Thread Mathieu Trudel-Lapierre

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: netplan.io (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  systemd-networkd not renaming devices on boot

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

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

[Bug 1770082] Re: systemd-networkd not renaming devices on boot

2018-05-25 Thread Mathieu Trudel-Lapierre

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: netplan
   Status: Incomplete => Confirmed

** Changed in: cloud-init (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/1770082

Title:
  systemd-networkd not renaming devices on boot

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

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

[Bug 1772706] [NEW] USABILITY : "Add Bookmark"'s insertion into bookmark list moves all bookmarks downwards

2018-05-22 Thread Mathieu L BOUCHARD

Public bug reported:

Drag-and-drop to a folder listed in bookmarks causes the list of
bookmarks to move down as the "Add Bookmark" item inserts itself above
the bookmark list when the dragging enters the bookmarks list. If
approached from the right side and expecting to be able to drop
immediately in a bookmarked folder, this will move the dragged thing to
the wrong folder (the one just above in the list) or will add it to the
list (if the target was the first bookmark). At best, it makes the user
be surprised and slowed down to adjust position, or it makes the user
getting used to having to aim 1 item lower in the list.

Possible improvements (not all equally good) :

(a) Make "Add Bookmark" appear as soon as an item goes into drag mode.

(b) Make "Add Bookmark" always present

(c) Add a "Bookmarks" heading to the bookmarks list and have a "+"
button next to it, that can either be dragged to, or pressed to open a
folder selection dialogue.

(d) Make "Add Bookmark" appear below the list (but if there is a
scrollbar for the left pane, what should happen to it ?)

(e) Make "Add Bookmark" appear outside the list (as a floating element
nearby, or inside the black toolbar at the top of the window).

(f) any other ideas ?


Note : I am using Ubuntu 16.04.4 and 17.10, with Unity. This is not a "bug" per 
se, but it's not a support question either, which is not I didn't file it on 
the Answers or AskUbuntu sites instead.

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: error-prone usability

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

Title:
  USABILITY : "Add Bookmark"'s insertion into bookmark list moves all
  bookmarks downwards

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

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

[Bug 1732002] Re: cloud images in lxc get ipv6 address

2018-05-08 Thread Mathieu Trudel-Lapierre

This got landed in netplan.io 0.35 in bionic. The changes still should
be part of a SRU.

** Changed in: nplan (Ubuntu)
   Status: New => Fix Released

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

Title:
  cloud images in lxc get ipv6 address

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

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

[Bug 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...

2018-04-30 Thread Mathieu Trudel-Lapierre

** Description changed:

+ [Impact]
+ Server users on s390x configuring qeth devices.
+ 
+ [Test case]
+ 1) Reconfigure an interface for a QETH device
+ 2) Verify that 'netplan apply' completes successfully, without error.
+ 
+ [Regression potential]
+ This change has minimal potential for regression, and it only skip qeth-based 
devices from "replugging", which "disconnects" them by unbinding and rebinding 
the driver. Potential issues would be limited to failure to rename interfaces 
without a reboot, for configurations that depend on this (but it already would 
not have worked due to netplan apply failing to rebind the device).
+ 
+ ---
+ 
  When trying to add another interface for a QETH device on a s390x system
  netplan apply fails:
  
  sudo netplan apply
  Cannot replug encc003: [Errno 19] No such device
  Traceback (most recent call last):
    File "/usr/sbin/netplan", line 23, in 
  netplan.main()
    File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 40, in run
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 87, in 
command_apply
  stdout=fd, stderr=fd)
    File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 
'net_setup_link', '/sys/class/net/encc003']' returned non-zero exit status 4.
  
  It seems like rebinding of qeth devices is not allowed.
  With qeth devices, I guess one needs to "offline & online" them...
  Or like unbind a whole group of them, as there are three of them per 
interface.
  
  ubuntu@s1lp14:/sys/class/net/encc006/device$ ls -latr
  total 0
  drwxr-xr-x 5 root root0 Mar 16 02:06 ..
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 uevent
  drwxr-xr-x 6 root root0 Mar 16 13:44 .
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 online
  lrwxrwxrwx 1 root root0 Mar 16 13:44 subsystem -> ../../../bus/ccwgroup
  lrwxrwxrwx 1 root root0 Mar 16 13:44 driver -> 
../../../bus/ccwgroup/drivers/qeth
  drwxr-xr-x 2 root root0 Mar 16 13:44 vnicc
  --w--- 1 root root 4096 Mar 16 13:44 recover
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 priority_queueing
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portno
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portname
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 performance_stats
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 layer2
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 isolation
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 hw_trap
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev2 -> ../../css0/0.0.0bb4/0.0.c008
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev1 -> ../../css0/0.0.0bb3/0.0.c007
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev0 -> ../../css0/0.0.0bb2/0.0.c006
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 buffer_count
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_role
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_reflect_promisc
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_hostnotify
  --w--- 1 root root 4096 Mar 16 13:50 ungroup
  -r--r--r-- 1 root root 4096 Mar 16 13:50 switch_attrs
  -r--r--r-- 1 root root 4096 Mar 16 13:50 state
  drwxr-xr-x 2 root root0 Mar 16 13:50 power
  -r--r--r-- 1 root root 4096 Mar 16 13:50 inbuf_size
  -r--r--r-- 1 root root 4096 Mar 16 13:50 if_name
  -r--r--r-- 1 root root 4096 Mar 16 13:50 chpid
  -r--r--r-- 1 root root 4096 Mar 16 13:50 card_type
  -r--r--r-- 1 root root 4096 Mar 16 13:50 bridge_state
  drwxr-xr-x 2 root root0 Mar 16 13:50 blkt
  drwxr-xr-x 3 root root0 Mar 16 13:50 net
  
- $ echo 'encc006' | sudo tee driver/unbind 
+ $ echo 'encc006' | sudo tee driver/unbind
  encc006
  tee: driver/unbind: No such device
  
- $ echo 'cdev0' | sudo tee driver/unbind 
+ $ echo 'cdev0' | sudo tee driver/unbind
  cdev0
  tee: driver/unbind: No such device
  
- $ echo '0.0.c006' | sudo tee driver/unbind 
+ $ echo '0.0.c006' | sudo tee driver/unbind
  0.0.c006
  ubuntu@s1lp14:/sys/class/net/encc006/device$ Mar 16 13:52:28 s1lp14 
sudo[8046]:   ubuntu : TTY=pts/1 ; PWD=/sys/devices/qeth/0.0.c006 ; USER=root ; 
COMMAND=/usr/bin/tee driver/unbind
  Mar 16 13:52:28 s1lp14 sudo[8046]: pam_unix(sudo:session): session opened for 
user root by ubuntu(uid=0)
  Mar 16 13:52:28 s1lp14 systemd-networkd[7772]: encc006: Lost carrier
  Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Network configuration 
changed, trying to establish connection.
  Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Synchronized to time server 
91.189.89.198:123 (ntp.ubuntu.com).
  Mar 16 13:52:28 s1lp14 systemd-networkd[7772]: encc006.2653: Lost carrier
  Mar 16 13:52:28 s1lp14 systemd-timesyncd[1078]: Network configuration 
changed, trying to

[Bug 1758647] Re: ubiquity doesn't preselect the right default keyboard layout

2018-04-19 Thread Mathieu Trudel-Lapierre

There was a misunderstanding there: I never suggested we should use xkb-
keymap instead (or at least, that's not the message I was trying to
convey).

The intent was to reduce delta by not removing so much code, when
console-setup merges are already difficult. I didn't foresee that some
of that code setting a default would impact ubiquity (because ubiquity
does things specially with d-i components, sometimes running them
multiple times). There's always a need to update ubiquity after changing
d-i components; it's inevitable since some of them are embedded in
ubiquity source.

The removals of xkb-keymaps aren't ubiquity-specific: we don't use this
code in d-i, and instead use multiple screens to change keyboards.
That's a conscious decision.

The point for supporting xkb-keymap "in ubiquity" is more about making
sure that we either "rebuild" the value based on layoutcode/variantcode,
or otherwise unset it before running the configuration script -- ie.
leave it in, but just explicitly ignore its values.

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

Title:
  ubiquity doesn't preselect the right default keyboard layout

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

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

[Bug 1753431] Re: bonding does not works

2018-04-17 Thread Mathieu Trudel-Lapierre

Your original config in comment #1 is correct: you must specify the
underlying devices, because those names are matched later for
"interfaces:" in the bond config.

The issue with 802.3ad is likely a driver issue or a bug in systemd; the
right mode needs to be set by networkd (which may require rebooting
rather than just running 'netplan apply').

Reassigning to systemd for investigation, we do have unit / autopkg
tests running for netplan which look like 802.3ad is correctly set, but
they do not interact with other network devices (there are no other
network devices in the test environment).

Furthermore, is anything beyond the physical network adapters configured
to used 802.3ad? This is important for the bonding to work.

** Package changed: nplan (Ubuntu) => systemd (Ubuntu)

** Changed in: systemd (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/1753431

Title:
  bonding does not works

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

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

[Bug 1726912] Re: fails to keep dhcplease

2018-04-17 Thread Mathieu Trudel-Lapierre

This would be a systemd-networkd bug, which I suspect might have already
been fixed too. Reassigning to systemd.

** Package changed: nplan (Ubuntu) => 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/1726912

Title:
  fails to keep dhcplease

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

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

[Bug 1754422] Re: [MIR] volume-key

2018-04-17 Thread Mathieu Trudel-Lapierre

MIR approved.

The new version synced from debian in bionic (UNAPPROVED) looks good
now, and appears to have corrected test suite issues:

18057438 | X- | volume-key   | 0.3.9-4  | 6 hours
 | * volume-key/0.3.9-4 Component: universe Section: misc


** Changed in: volume-key (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  [MIR] volume-key

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

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

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-04-09 Thread Mathieu Trudel-Lapierre

unbound attempts to add itself as a local resolver (pointing to
127.0.0.1). I think this will require specific integration work so that
unbound can properly update/ tell systemd-networkd that it wants to be
able to serve as a resolver.

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

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

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

Title:
  replacement of resolvconf with systemd needs integration

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

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

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-04-09 Thread Mathieu Trudel-Lapierre

sendmail only uses an update-libc.d script to reload the daemon on
changes to resolv.conf, which should be sufficient for DNS resolution to
remain working as it did with resolvconf; seeing as the nameserver will
generally not change from 127.0.0.53

** Changed in: sendmail (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/1713803

Title:
  replacement of resolvconf with systemd needs integration

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

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

[Bug 1754422] Re: [MIR] volume-key

2018-04-09 Thread Mathieu Trudel-Lapierre

Have the tests been fixed? I really don't much like having things in
main that run tests but don't use the result; is there any way to just
ignore the test(s) that are really broken and otherwise keep the
remaining tests failing the build if they fail, such that we can catch a
possible regression?

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

Title:
  [MIR] volume-key

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

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

[Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()

2018-04-02 Thread Mathieu St-Gelais

I'm on Ubuntu 18.04, still beta, but fully updated, with dual screens on
two AMD R9 390, and it keeps happening after each login / screen unlock.

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

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_read_events() from ospoll_wait()

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

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

[Bug 1713803] Re: replacement of resolvconf with systemd needs integration

2018-03-26 Thread Mathieu Trudel-Lapierre

Looks like the current behavior should be sufficient for postfix to
integrate as well as it did with resolvconf: marking this Invalid.

** Changed in: postfix (Ubuntu)
   Status: Triaged => 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/1713803

Title:
  replacement of resolvconf with systemd needs integration

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

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

[Bug 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...

2018-03-26 Thread Mathieu Trudel-Lapierre

** Changed in: netplan
   Status: New => Fix Released

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

Title:
  'netplan apply' fails when trying to activate another interface on
  another QETH device ...

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

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

[Bug 1754422] Re: [MIR] volume-key

2018-03-22 Thread Mathieu Trudel-Lapierre

Wild guess is this is a test that expects user input, and the input
never shows up?

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

Title:
  [MIR] volume-key

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

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

[Bug 1753441] Re: [MIR] lame

Go for libmp3lame0, on the condition that CVE-2017-15019 be looked into.

** Changed in: lame (Ubuntu)
   Status: Incomplete => Fix Committed

** Changed in: lame (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

** Changed in: lame (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  [MIR] lame

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

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

[Bug 1753458] Re: [MIR] twolame

libtwolame0 is approved.

** Changed in: twolame (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  [MIR] twolame

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

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

[Bug 1753450] Re: [MIR] mpg123

libmpg123-0 's MIR is approved then.

** Changed in: mpg123 (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  [MIR] mpg123

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

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

[Bug 1753441] Re: [MIR] lame

** Changed in: lame (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

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

Title:
  [MIR] lame

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

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

[Bug 1753458] Re: [MIR] twolame

** Changed in: twolame (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

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

Title:
  [MIR] twolame

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

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

[Bug 1753450] Re: [MIR] mpg123

** Changed in: mpg123 (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

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

Title:
  [MIR] mpg123

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

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

[Bug 1753450] Re: [MIR] mpg123

MIR ack for libmpg123-0 if the Security Team acknowledges they are aware
of this requirement.

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

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

Title:
  [MIR] mpg123

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

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

[Bug 1753458] Re: [MIR] twolame

MIR ack for libtwolame0 if the Security Team acknowledges they are aware
of this requirement.

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

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

Title:
  [MIR] twolame

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

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

[Bug 1753441] Re: [MIR] lame