[Desktop-packages] [Bug 1823917] Re: Can't set Chromium as the default browser when BROWSER variable is defined

[Walter Lapchynski]

** Description changed:

- Every time I launch the browser it suggests to be set as the default but if I 
click on that button nothing will change: I'll get the suggestion the next time 
I open Chromium, even if I reboot.
- Changing the default browser on configuration panel didn't solve the issue
+ STEPS TO REPRODUCE
+  1. Install firefox
+  2. Set `BROWSER=firefox`
+  3. Open firefox and make sure it is the default browser
+  4. Install chromium-browser
+  5. Open chromium-browser and set it as the default browser
+  6. Click on a link or use `xdg-open URL`
  
- Lubuntu 19.10 beta on Athlon 64x2 5200+
+ EXPECTED RESULTS
+ Link opens in chromium-browser
+ 
+ ACTUAL RESULTS
+ Link opens in firefox instead. Running chromium-browser from the terminal, 
when trying to change the default browser, the error "xdg-settings: $BROWSER is 
set and can't be changed with xdg-settings" appears. BROWSER, xdg-setting's 
default-web-browser, and xdg-mime's default for text/html remain unchanged. 
It's not possible to set the value of default-web-browser when the BROWSER 
variable is set. Yet, when making firefox default, the end result is that 
BROWSER is still set and default-web-browser and the default for text/html has 
changed.
+ 
+ chromium-browser 73.0.3683.103-0ubuntu1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1823917

Title:
  Can't set Chromium as the default browser when BROWSER variable is
  defined

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  STEPS TO REPRODUCE
   1. Install firefox
   2. Set `BROWSER=firefox`
   3. Open firefox and make sure it is the default browser
   4. Install chromium-browser
   5. Open chromium-browser and set it as the default browser
   6. Click on a link or use `xdg-open URL`

  EXPECTED RESULTS
  Link opens in chromium-browser

  ACTUAL RESULTS
  Link opens in firefox instead. Running chromium-browser from the terminal, 
when trying to change the default browser, the error "xdg-settings: $BROWSER is 
set and can't be changed with xdg-settings" appears. BROWSER, xdg-setting's 
default-web-browser, and xdg-mime's default for text/html remain unchanged. 
It's not possible to set the value of default-web-browser when the BROWSER 
variable is set. Yet, when making firefox default, the end result is that 
BROWSER is still set and default-web-browser and the default for text/html has 
changed.

  chromium-browser 73.0.3683.103-0ubuntu1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1824072] [NEW] Intel 710 series INC can't receive any packet on 18.04 & 18.10 Ubuntu-arm64-server

[Phil Yang]

Public bug reported:

## PCI info for the NIC XXV710DA2BLK
pci@:8e:00.1  enp142s0f1  networkEthernet Controller XL710 for 40GbE 
QSFP+

## link detected & promisc mode turned on
$ ip link list enp142s0f1
3: enp142s0f1:  mtu 1500 qdisc mq 
state UP mode DEFAULT group default qlen 1000
link/ether 3c:fd:fe:bb:cf:61 brd ff:ff:ff:ff:ff:ff

$ sudo ethtool enp142s0f1
Settings for enp142s0f1:
Supported ports: [ FIBRE ]
Supported link modes:   4baseCR4/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes:  4baseCR4/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: 4Mb/s
Duplex: Full
Port: Direct Attach Copper
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x0007 (7)
   drv probe link
Link detected: yes

$ sudo ethtool -i enp142s0f1
driver: i40e
version: 2.8.10-k
firmware-version: 6.01 0x800035da 1.1747.0
expansion-rom-version:
bus-info: :8e:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

## Kernel info
5.1-rc3+ commit 5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539

## Packet generated by IXIA
## XDP & tcpdump can't capture any packet.
$ sudo ./samples/bpf/xdp1 -N enp142s0f1

$ sudo tcpdump -i enp142s0f1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp142s0f1, link-type EN10MB (Ethernet), capture size 262144 bytes
15:08:50.176524 IP6 net-arm-thunderx2-03 > ff02::16: HBH ICMP6, multicast 
listener report v2, 1 group record(s), length 28
15:08:50.588515 IP6 net-arm-thunderx2-03 > ff02::16: HBH ICMP6, multicast 
listener report v2, 1 group record(s), length 28

=
Ubuntu 16.04.5 LTS with Kernel 4.15.0-43-generic + Intel 710 NIC (The same NIC 
XXV710DA2BLK):
tcpdump worked as expected.

$ sudo ethtool -i enp138s0f0
driver: i40e
version: 2.7.29
firmware-version: 6.80 0x80003d05 1.2007.0
expansion-rom-version:
bus-info: :8a:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

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

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

Title:
  Intel 710 series INC can't receive any packet on 18.04 & 18.10
  Ubuntu-arm64-server

Status in mutter package in Ubuntu:
  New

Bug description:
  ## PCI info for the NIC XXV710DA2BLK
  pci@:8e:00.1  enp142s0f1  networkEthernet Controller XL710 for 40GbE 
QSFP+

  ## link detected & promisc mode turned on
  $ ip link list enp142s0f1
  3: enp142s0f1:  mtu 1500 qdisc mq 
state UP mode DEFAULT group default qlen 1000
  link/ether 3c:fd:fe:bb:cf:61 brd ff:ff:ff:ff:ff:ff

  $ sudo ethtool enp142s0f1
  Settings for enp142s0f1:
  Supported ports: [ FIBRE ]
  Supported link modes:   4baseCR4/Full
  Supported pause frame use: Symmetric
  Supports auto-negotiation: Yes
  Supported FEC modes: Not reported
  Advertised link modes:  4baseCR4/Full
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Advertised FEC modes: Not reported
  Speed: 4Mb/s
  Duplex: Full
  Port: Direct Attach Copper
  PHYAD: 0
  Transceiver: internal
  Auto-negotiation: on
  Supports Wake-on: d
  Wake-on: d
  Current message level: 0x0007 (7)
 drv probe link
  Link detected: yes

  $ sudo ethtool -i enp142s0f1
  driver: i40e
  version: 2.8.10-k
  firmware-version: 6.01 0x800035da 1.1747.0
  expansion-rom-version:
  bus-info: :8e:00.1
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: yes
  supports-register-dump: yes
  supports-priv-flags: yes

  ## Kernel info
  5.1-rc3+ commit 5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539

  ## Packet generated by IXIA
  ## XDP & tcpdump can't capture any packet.
  $ sudo ./samples/bpf/xdp1 -N enp142s0f1

  $ sudo tcpdump -i enp142s0f1
  tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
  listening on enp142s0f1, link-type EN10MB (Ethernet), capture size 262144 
bytes
  15:08:50.176524 IP6 net-arm-thunderx2-03 > ff02::16: HBH ICMP6, multicast 
listener report v2, 1 group record(s), length 28
  15:08:50.588515 IP6 net-arm-thunderx2-03 > ff02::16: HBH ICMP6, multicast 
listener report v2, 1 group record(s), length 28

  

[Desktop-packages] [Bug 1823917] Re: Can't set Chromium as the default browser

[Walter Lapchynski]

> xdg-settings: $BROWSER is set and can't be changed with xdg-settings

That's some telling info right there.

Some things to note:

 * In lxqt-config-session, in both Default Applications and Environment
(Advanced) there is an option to set the BROWSER variable. It is set to
firefox by default. It will come back if it is deleted (possibly a bug).
Unlike TERM or EDITOR, which are part of the UNIX standard
(http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_01),
BROWSER is not always recognized by applications.

 * There is a Freedesktop Specification for MIME types
(https://www.freedesktop.org/wiki/Specifications/mime-apps-spec/) that
lxqt-config-file-associations interacts with. The xdg-utils (XDG = X
Desktop Group, the former name of Freedesktop) tools interact with this.
You can use them to find out which is your default browser via `xdg-mime
query default text/html`. Similarly, `xdg-open` determines the MIME type
of the argument it is given and passes it to the associated application.

 * There is also update-alternatives which allows you to assign
different definitions of various types of generic programs. For example,
you could easily select from different definitions for x-www-browser. I
mention this for completeness, but it's not particularly relevant.

Now to prove this is not an issue with LXQt, consider this scenario:

 1. Load Lubuntu, which has firefox installed by default
 2. Install Opera
 3. Note that `echo $BROWSER` returns "firefox"
 4. Note that `xdg-mime query default text/html` returns "firefox.desktop"
 5. Note that `xdg-settings get default-web-browser` returns "firefox.desktop"
 6. Note `xdg-open http://ubuntu.com` opens in firefox
 7. Open qterminal and `echo 'http://ubuntu.com'`
 8. Note that holding down Ctrl and clicking on the URL opens it up in firefox
 9. Open up Opera and set it as the default browser
10. Note that `echo $BROWSER` returns "firefox"
11. Note that `xdg-mime query default text/html` returns "opera.desktop"
12. Note that `xdg-settings get default-web-browser` returns "opera.desktop"
13. Note `xdg-open http://ubuntu.com` opens in opera
14. Open qterminal and `echo 'http://ubuntu.com'`
15. Note that holding down Ctrl and clicking on the URL opens it up in opera

So why the problem with chromium-browser? Let's get back to that quote:

> xdg-settings: $BROWSER is set and can't be changed with xdg-settings

When you try to make chromium-browser default, it sees the BROWSER
variable and just gives up, whereas Opera (and Firefox) ignores it and
actually sets it. This error is actually from xdg-settings. It won't set
default-web-browser while BROWSER exists. Yet, somehow firefox and opera
both seem to deal with this. Therefore, I would call this chromium-
browser's fault.


** Package changed: lxqt-session (Ubuntu) => chromium-browser (Ubuntu)

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Medium

** Summary changed:

- Can't set Chromium as the default browser
+ Can't set Chromium as the default browser when BROWSER variable is defined

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1823917

Title:
  Can't set Chromium as the default browser when BROWSER variable is
  defined

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  Every time I launch the browser it suggests to be set as the default but if I 
click on that button nothing will change: I'll get the suggestion the next time 
I open Chromium, even if I reboot.
  Changing the default browser on configuration panel didn't solve the issue

  Lubuntu 19.10 beta on Athlon 64x2 5200+

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot

[Joe Barnett]

downgrading to the 1.2.0 bios on xps 9575 appears to be working properly
(tested 3 reboots with no issues)

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

Title:
  [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working
  at gdm screen after boot

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see 
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered 
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823917] [NEW] Can't set Chromium as the default browser

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Every time I launch the browser it suggests to be set as the default but if I 
click on that button nothing will change: I'll get the suggestion the next time 
I open Chromium, even if I reboot.
Changing the default browser on configuration panel didn't solve the issue

Lubuntu 19.10 beta on Athlon 64x2 5200+

** Affects: chromium-browser (Ubuntu)
 Importance: Medium
 Status: Confirmed

-- 
Can't set Chromium as the default browser
https://bugs.launchpad.net/bugs/1823917
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to chromium-browser in Ubuntu.

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1753120] Re: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is also in package

[Lumar]

package libgtkmm-2.4-doc (not installed) failed to install/upgrade:
trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README',
which is also in package libgtkmm-2.4-dev:i386 1:2.24.5-2

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtkmm2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1753120

Title:
  package libgtkmm-2.4-doc (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README',
  which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2

Status in gtkmm2.4 package in Ubuntu:
  Confirmed
Status in gtkmm2.4 package in Debian:
  Fix Released

Bug description:
  E: /var/cache/apt/archives/libgtkmm-2.4-doc_1%3a2.24.5-2_all.deb:
  trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README',
  which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libgtkmm-2.4-doc (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Mar  3 10:59:55 2018
  DuplicateSignature:
   package:libgtkmm-2.4-doc:(not installed)
   Unpacking libgtkmm-2.4-doc (1:2.24.5-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-ebi0hY/58-libgtkmm-2.4-doc_1%3a2.24.5-2_all.deb 
(--unpack):
trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', 
which is also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2
  ErrorMessage: trying to overwrite 
'/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is also in package 
libgtkmm-2.4-dev:amd64 1:2.24.5-2
  InstallationDate: Installed on 2018-03-02 (1 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302)
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu2
  SourcePackage: gtkmm2.4
  Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/doc/libgtkmm-2.4-dev/examples/README', which is 
also in package libgtkmm-2.4-dev:amd64 1:2.24.5-2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtkmm2.4/+bug/1753120/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1290542] Re: pulseaudio crashed with SIGSEGV in prepare_next_write_item()

[Daniel van Vugt]

This crash doesn't seem to make the top 100 crashes in pulseaudio on
14.04 or 18.04. So that means I can't yet find it on errors.ubuntu.com
:(

MOZGIII, do you have any more information you can share? Like a link to
your crash on errors.ubuntu.com?

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

Title:
  pulseaudio crashed with SIGSEGV in prepare_next_write_item()

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  crashed while watching video via hdmi display port and hdmi
  displayport audio

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   2416 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 10 21:27:32 2014
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-03-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   main ()
  Title: pulseaudio crashed with SIGSEGV in pa_mainloop_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1821870] Re: gnome-shell segfault libmutter-clutter-2

[Daniel van Vugt]

Unfortunately that's the same crash from April 7th, and there's no new
information on that page.

Sorry, but next please try reproducing the crash so we can get a new
crash report per comment #1.

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

Title:
  gnome-shell segfault  libmutter-clutter-2

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome Shell restarts multiple times a day, after the crash I see this
  error in dmesg:

  [195984.712376] gnome-shell[5769]: segfault at 0 ip 7f662716e021
  sp 7fffbf225760 error 4 in libmutter-
  clutter-2.so[7f66270ee000+161000]

  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  gnome-shell:
Installed: 3.28.3-0ubuntu0.18.04.4
Candidate: 3.28.3-0ubuntu0.18.04.4

  libmutter-2-0:
Installed: 3.28.3-2~ubuntu18.04.2
Candidate: 3.28.3-2~ubuntu18.04.2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823573] Re: Bluetooth headset not available as output device

[Daniel van Vugt]

To get to the grub menu and select a different installed kernel, you
need to be fast. The instant the purple screen first appears on boot,
tap Escape.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1823573

Title:
  Bluetooth headset not available as output device

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Connecting my Bluetooth headset (Beoplay H8) appears to be working,
  and everything looks correct in the Bluetooth settings: However, the
  headset is not listed under "Output devices" in the sound menu after
  connecting, and all sounds are channeled through the built-in
  speakers.

  Media buttons on the headset are also rendered useless, not that there
  would be much use for them without sound anyways. Still worth noting,
  as everything including media buttons worked perfectly in 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stein  2603 F pulseaudio
   /dev/snd/pcmC0D0c:   stein  2603 F...m pulseaudio
   /dev/snd/pcmC0D0p:   stein  2603 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 23:00:38 2019
  InstallationDate: Installed on 2018-05-09 (332 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to disco on 2019-04-03 (4 days ago)
  dmi.bios.date: 10/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3PCN16WW(V2.00)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad 510S-13IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 510S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3PCN16WW(V2.00):bd10/14/2016:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80V0
  dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB
  dmi.product.version: Lenovo ideapad 510S-13IKB
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell

[Daniel van Vugt]

Thanks. That suggests removing extensions might not have helped.

Still, at some point in future we'll need to investigate this in more
detail. And before that, maybe test over a longer period of time.

** Changed in: gnome-shell (Ubuntu)
   Importance: Medium => High

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

Title:
  Unreasonable NVIDIA GPU VRAM usage on gnome-shell

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  GPU: NVIDIA GTX 1060 3GB 
  Ubuntu: 19.04, Kernel Linux luky-pc 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 
21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  NVIDIA driver version: 418.56
  Display settings: BenQ XL2411Z, 144Hz monitor, 1920x1080p 

  I have noticed this strange behavior only on gnome-shell where the overall 
gnome-shell desktop VRAM usage was taking up to 1GB of GPU VRAM which does not 
happen on other desktops, or on Windows, happens after some hours of normal 
desktop usage
  Even the system RAM increases a lot during normal usage, but remains 
acceptable

  This behaviour can be observed by using "nvidia-smi" a tool from the
  NVIDIA proprietary driver

  gnome-shell VRAM usage on a cold start: 139MB, + 9 MB
  X.org VRAM usage on cold start: 48MB + 18MB 
  Total: 214MB

  gnome-shell VRAM usage after some hours of normal usage: 445MB + 83 MB
  X.org VRAM usage after some hours of normal usage: 244MB + 18MB 
  Total: 800MB

  On windows or other desktops the GPU VRAM usage remains the same
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1822394] Re: [Dell XPS 15 9575] laptop keyboard & touchpad not working at gdm screen after boot

[Daniel van Vugt]

Is is possible to downgrade the BIOS at all?

The bug description says:

> Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0
bios

and the problematic BIOS versions are only a couple of weeks old:

https://www.dell.com/support/home/au/en/audhs1/drivers/driversdetails?driverid=p93yr
https://www.dell.com/support/home/au/en/audhs1/drivers/driversdetails?driverid=2rfmg

Unfortunately there's nothing newer yet either.

** Summary changed:

- [Dell XPS 15 9575] laptop keyboard & touchpad not working at gdm screen after 
boot
+ [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm 
screen after boot

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

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

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

Title:
  [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working
  at gdm screen after boot

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see 
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered 
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823175] Re: Battery status shows "Estimating..." when fully charged

[Daniel van Vugt]

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

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

** Changed in: gnome-shell (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: gnome-shell (Ubuntu Cosmic)
   Status: New => Triaged

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

Title:
  Battery status shows "Estimating..." when fully charged

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Bionic:
  Triaged
Status in gnome-shell source package in Cosmic:
  Triaged
Status in gnome-shell source package in Disco:
  Fix Released

Bug description:
  My battery is fully charged and it shows 100%. When it's connected to 
charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
  I'm using "Asus VivoBook x510uf"
  My battery status when connected to AC power:

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  40.367 Wh
  energy-empty:0 Wh
  energy-full: 40.367 Wh
  energy-full-design:  43.046 Wh
  energy-rate: 0 W
  voltage: 11.55 V
  percentage:  100%
  capacity:93.7764%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
    History (charge):
  15543934180.000   unknown
    History (rate):
  15543934180.000   unknown

  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   unknown
  warning-level:   none
  energy:  40.367 Wh
  energy-full: 40.367 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-missing-symbolic'

  Daemon:
    daemon-version:  0.99.7
    on-battery:  no
    lid-is-closed:   no
    lid-is-present:  yes
    critical-action: HybridSleep

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 17:04:22 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries

[Daniel van Vugt]

Awesome.

I guess the only remaining question is whether you can confirm that
downgrading to gnome-bluetooth 3.32.0 reintroduces the problem?

** Package changed: bluez (Ubuntu) => gnome-bluetooth (Ubuntu)

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

Title:
  Logitech M535 mouse only pairs successfully after 4-5 tries

Status in gnome-bluetooth package in Ubuntu:
  Incomplete

Bug description:
  I've had my mouse (Logitech M535) paired and working since upgrading
  to 18.04. I had to re-do the pairing after connecting to a different
  machine and now it takes 4-5 tries of pair/remove to connect the
  mouse, on every reboot / sleep cycle.

  The logs show:
  cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info

  But neither actually seem critical as this is shown upon successful
  pairing as well.

  a bluetoothctl session of a failed pairing:
  [bluetooth]# pair 34:88:5D:3E:A1:A4 
  Attempting to pair with 34:88:5D:3E:A1:A4
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes
  Pairing successful
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: no

  The mouse continues in pairing mode.

  When using the gnome-control-center Bluetooth module:
  cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)

  Finally when it connects:
  [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535
  [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 15 07:46:38 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 12-9Q33
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago)
  dmi.bios.date: 03/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 5C:51:4F:1D:50:3C  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN ISCAN 
RX bytes:16702 acl:290 sco:0 events:716 errors:0
TX bytes:44162 acl:142 sco:0 commands:427 errors:0

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 1592177] Re: Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour)

[Daniel van Vugt]

** Also affects: gtk+3.0 (Ubuntu Disco)
   Importance: Undecided
   Status: Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1592177

Title:
  Focus drops from search input in GtkFileChooserDialog after first
  character, which stops searching (broken behaviour)

Status in GTK+:
  Expired
Status in Ubuntu GNOME:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Bionic:
  Fix Committed
Status in gtk+3.0 source package in Cosmic:
  Fix Committed
Status in gtk+3.0 source package in Disco:
  Fix Released

Bug description:
  * Impact
  The focus gets removed from the search entry widget in the fileselector while 
typing which makes it difficult to use

  * Test case

  Steps:
  1. Open Gedit
  2. Choose Open -> Other Documents... to open a GtkFileChooserDialog
  3. Press on the search button next to Open
  4. Type what you are searching for

  Expected behaviour:
  Focus remains in the search input until I finish typing then results come up

  What happens instead:
  Searching stops after I enter the first characters because focus is lost from 
the search input

  * Regression potential

  The change is desactivating/reactivating typeahead in the gtk
  fileselector, check that this feature keeps working as it should
  (keyboard navigate by typing the first chars of a file/folder, that
  should move the focus to the first matching item and allows to
  navigate by hitting enter)

  

  I have noticed that after upgrading to GNOME 3.20 on Ubuntu GNOME
  16.04 that the built-in search functionality is almost impossible to
  use in the GTK file chooser (though it is the same one that allows you
  to save files as well as choose them).

  So if one types something into the search, after they have typed the
  first letter it will immediately select the top search result meaning
  one has to re-select the search box, this happens for every letter so
  searching for a long string becomes very annoying. If one carries on
  typing once it has selected the top result and unselected the search
  box it will start searching in the other search which only looks at
  results.

  Upstream bug:
  https://gitlab.gnome.org/GNOME/gtk/issues/1572


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823793] Re: [regression] Font scaling not working on gnome startup

[Daniel van Vugt]

** Changed in: mutter (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [regression] Font scaling not working on gnome startup

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  The font text scaling setting is not being loaded on gnome startup. I
  have font text scaling set to 1.25. After updating mutter to package
  version 3.32.0-1ubuntu1 the text scaling setting is not loaded any
  more when starting gnome. Steps to reproduce the issue:

  1) Set your font scaling factor to something other than the default
  '1'. This can be set, for example, either by using "Gnome tweaks" or
  with gsettings:

  settings set org.gnome.desktop.interface text-scaling-factor 1.25

  2) You'll see that the top bar text gets larger.
  3) Log out and log in. You'll see that the top bar text and text in general 
has been reset to the default '1'. The setting is still set to '1.25', but 
visually it's '1'.

  If you set the value to something else, it gets applied correctly,
  until you log out.

  
  This worked as expected on package version 3.32.0-1. I wonder if this patch 
listed in the CHANGELOG could have somehow created this side effect:
  debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 13:42:39 2019
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190408)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1777062] [NEW] Logitech M535 mouse only pairs successfully after 4-5 tries

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I've had my mouse (Logitech M535) paired and working since upgrading to
18.04. I had to re-do the pairing after connecting to a different
machine and now it takes 4-5 tries of pair/remove to connect the mouse,
on every reboot / sleep cycle.

The logs show:
cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info

But neither actually seem critical as this is shown upon successful
pairing as well.

a bluetoothctl session of a failed pairing:
[bluetooth]# pair 34:88:5D:3E:A1:A4 
Attempting to pair with 34:88:5D:3E:A1:A4
[CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
[CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
[CHG] Device 34:88:5D:3E:A1:A4 Paired: yes
Pairing successful
[CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no
[CHG] Device 34:88:5D:3E:A1:A4 Connected: no

The mouse continues in pairing mode.

When using the gnome-control-center Bluetooth module:
cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)

Finally when it connects:
[NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535
[CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes
[CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
[CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
[CHG] Device 34:88:5D:3E:A1:A4 Paired: yes

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 15 07:46:38 2018
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. XPS 12-9Q33
ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago)
dmi.bios.date: 03/03/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A08
dmi.board.name: XPS 12-9Q33
dmi.board.vendor: Dell Inc.
dmi.board.version: A08
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 12-9Q33
dmi.product.version: A08
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 5C:51:4F:1D:50:3C  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN ISCAN 
RX bytes:16702 acl:290 sco:0 events:716 errors:0
TX bytes:44162 acl:142 sco:0 commands:427 errors:0

** Affects: gnome-bluetooth (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-bug bionic
-- 
Logitech M535 mouse only pairs successfully after 4-5 tries
https://bugs.launchpad.net/bugs/1777062
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-bluetooth in Ubuntu.

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823382] Re: backport openssl 1.1.1 fixes to bionic and cosmic

[Dimitri John Ledkov]

Spot checking both bionic and cosmic, these builds look good.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic 
verification-done-cosmic

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

Title:
  backport openssl 1.1.1 fixes to bionic and cosmic

Status in neon27 package in Ubuntu:
  Fix Released
Status in neon27 source package in Bionic:
  Fix Committed
Status in neon27 source package in Cosmic:
  Fix Committed
Status in neon27 source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * neon27 doesn't work with openssl 1.1.1
   * backport fixes from disco to cosmic and bionic to resolve that

  [Test Case]

   * does not FTBFS

  [Regression Potential]

   * currently broken in cosmic, and will break once openssl is upgraded
  in bionic, so for all practical purposes it's completely busted at the
  moment.

  [Other Info]
   
   * Fixes already in disco and unstable.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Alec Larsen]

This problem also affects me with Zoom. I am also using a Dell Precision
5520 with Intel HD Graphics, and disabling animations in Tweaks /
Appearance / Animations fixes the problem for me.

I arrived at this thread by Googling the last few frames in my coredump:

```
$ gdb /usr/bin/gnome-shell -c CoreDump
GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/gnome-shell...(no debugging symbols found)...done.
[New LWP 16771]
[New LWP 16775]
[New LWP 16782]
[New LWP 16777]
[New LWP 16785]
[New LWP 16792]
[New LWP 16784]
[New LWP 16788]
[New LWP 16776]
[New LWP 16786]
[New LWP 16793]
[New LWP 16787]
[New LWP 16790]
[New LWP 16783]
[New LWP 16791]
[New LWP 16779]
[New LWP 16789]
[New LWP 16794]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/gnome-shell'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f8326767fe0 in meta_window_actor_is_destroyed () from 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
[Current thread is 1 (Thread 0x7f8329125ac0 (LWP 16771))]
(gdb) backtrace
#0  0x7f8326767fe0 in meta_window_actor_is_destroyed () at 
/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
#1  0x7f8322546dae in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
#2  0x7f832254671f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#3  0x7f8327221648 in  () at /usr/lib/libgjs.so.0
#4  0x7f8327222f94 in  () at /usr/lib/libgjs.so.0
#5  0x7f831f028f6c in  () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#6  0x7f831f01bed7 in  () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#7  0x7f831f0287d6 in  () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#8  0x7f831f028daf in  () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#9  0x7f831f029089 in  () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#10 0x7f831ee190c9 in  () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#11 0x14a67c2ca3c6 in  ()
#12 0x561eaa870a40 in  ()
#13 0x7ffea8948460 in  ()
#14 0xfff9 in  ()
#15 0x7f83203bf8c0 in  () at /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0
#16 0x7f82fc0739a0 in  ()
#17 0x14a67c49b66b in  ()
#18 0x6820 in  ()
#19 0x7f82dac1bba0 in  ()
#20 0x in  ()
(gdb)
```

I'm happy to help debugging if any other information is needed.

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in gjs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gjs source package in Bionic:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   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 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1290542] Re: pulseaudio crashed with SIGSEGV in prepare_next_write_item()

[MOZGIII]

I just got the same issue at Ubuntu 18.04

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

Title:
  pulseaudio crashed with SIGSEGV in prepare_next_write_item()

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  crashed while watching video via hdmi display port and hdmi
  displayport audio

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu10
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  christian   2416 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Mar 10 21:27:32 2014
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2014-03-07 (3 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301)
  ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=de_DE
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so
   pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
   main ()
  Title: pulseaudio crashed with SIGSEGV in pa_mainloop_dispatch()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

[Bug Watch Updater]

** Changed in: df-libreoffice
   Status: Confirmed => Fix Released

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

Title:
  LibreOffice doesn't detect JVM because of unexpected java.vendor
  property value

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openjdk-lts package in Ubuntu:
  New
Status in libreoffice package in Debian:
  New

Bug description:
  libreoffice autopkgtests are failing on disco with openjdk
  11.0.3+4-2ubuntu1.

  The likely culprit is that change:

  +openjdk-lts (11.0.3+4-2ubuntu1) disco; urgency=medium
  +
  +  * Sync packages with 11.0.3+4-2:
  +[ Matthias Klose ]
  +- Configure with vendor flags.

  Indeed with version 11.0.3+4-1ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Oracle Corporation

  And with version 11.0.3+4-2ubuntu1:

  $ java -XshowSettings -version 2>&1 | grep "java.vendor "
  java.vendor = Private Build

  Looking at the code in Libreoffice that looks for a JVM, it validates
  the vendor against a hardcoded list of known vendors:
  
https://cgit.freedesktop.org/libreoffice/core/tree/jvmfwk/plugins/sunmajor/pluginlib/vendorlist.cxx?h=libreoffice-6-2#n33

  Not sure what the purpose of that upstream code is, but this means the
  new openjdk-11 build in Ubuntu breaks it.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openjdk-11-jre-headless 11.0.3+4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 17:06:25 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (1003 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: openjdk-lts
  UpgradeStatus: Upgraded to disco on 2019-03-16 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1822839/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1824033] [NEW] Libreoffice Core Application Missing Application Icon In Plasma Task Manager

[Harley A.W. Lorenzo]

Public bug reported:

The main core application for Libreoffice is missing its icon in the
Task Manager when opened in Plasma. May affect other desktop
environments.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libreoffice-core 1:6.2.2-0ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu26
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Apr  9 18:31:36 2019
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2019-04-08 (1 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco

** Attachment added: "Screenshot of its appearance"
   
https://bugs.launchpad.net/bugs/1824033/+attachment/5254539/+files/Screenshot_20190409_183628.png

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

Title:
  Libreoffice Core Application Missing Application Icon In Plasma Task
  Manager

Status in libreoffice package in Ubuntu:
  New

Bug description:
  The main core application for Libreoffice is missing its icon in the
  Task Manager when opened in Plasma. May affect other desktop
  environments.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice-core 1:6.2.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu26
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Apr  9 18:31:36 2019
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2019-04-08 (1 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)

[Martin Wimpress]

** Changed in: indicator-application (Ubuntu)
   Status: Confirmed => Invalid

** No longer affects: ubuntu-mate

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

Title:
  nm-applet symbol not displayed on mate (18.04)

Status in indicator-application package in Ubuntu:
  Invalid
Status in mate-indicator-applet package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Invalid
Status in ubuntu-mate-settings package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 18.04, the network manager applet symbol
  isn't displayed any longer. The other functionality (asking for
  credentials) is working. I also see other symbols.

  
  aptitude show network-manager-gnome
  Paket: network-manager-gnome
  Version: 1.8.10-2ubuntu1
  Neu: ja
  Zustand: Installiert

  
  stdout/stderr:
  Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module"
  Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module"
  Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module"

  ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with
  accessibility bus: Did not receive a reply. Possible causes include:
  the remote application did not send a reply, the message bus security
  policy blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab
  information for modem at /org/freedesktop/ModemManager1/Modem/6: No
  ModemManager support

  (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is
  not available for modem at /org/freedesktop/ModemManager1/Modem/6

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on
  widget which has a parent

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy:
  assertion 'GTK_IS_WIDGET (widget)' failed

  (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on
  widget which has a parent

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-gnome 1.8.10-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Mar  8 21:27:56 2018
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  WpaSupplicantLog:
   
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823793] Re: [regression] Font scaling not working on gnome startup

[Harley A.W. Lorenzo]

Version 3.32.0-1ubuntu2 has also fixed the issue for me. I believe it is
triaged.

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

Title:
  [regression] Font scaling not working on gnome startup

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The font text scaling setting is not being loaded on gnome startup. I
  have font text scaling set to 1.25. After updating mutter to package
  version 3.32.0-1ubuntu1 the text scaling setting is not loaded any
  more when starting gnome. Steps to reproduce the issue:

  1) Set your font scaling factor to something other than the default
  '1'. This can be set, for example, either by using "Gnome tweaks" or
  with gsettings:

  settings set org.gnome.desktop.interface text-scaling-factor 1.25

  2) You'll see that the top bar text gets larger.
  3) Log out and log in. You'll see that the top bar text and text in general 
has been reset to the default '1'. The setting is still set to '1.25', but 
visually it's '1'.

  If you set the value to something else, it gets applied correctly,
  until you log out.

  
  This worked as expected on package version 3.32.0-1. I wonder if this patch 
listed in the CHANGELOG could have somehow created this side effect:
  debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 13:42:39 2019
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190408)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1812527] Re: [bionic][regression] gnome-shell crashes with SIGSEGV in meta_window_actor_is_destroyed(self=NULL) called from _switchWorkspaceDone() [windowManager.js:1787]

[Sjef Bosman]

Same problem here, and I have absolutely nothing related to Android
installed. When I switch workspaces, occasionally the system flashes and
all screens disappear, but all workspaces are correctly displayed after
2-3 seconds. Rarely a lot more crashes and the login screen reappears.

System: Ubuntu 18.04.2 LTS with GNOME 3.28.2. I changed my workspace
switching key-combination to Windows-PgUp and PgDown.

Workspace screens: 4 down, 2 wide
Active applications: Firefox, Whatsdesk, Skype, VirtualBox, Yate Client, 
Owncloud, Dropbox, Devilspie, Psensor and VirtualBox running Windows10.

I saved the syslog file, and if you're interested I can send it to you.
No other bug info found, neither in the folders you mentioned nor on the
errors.ubuntu.com website. It's funny though that the error reports on
that site stop on 2019-02-03, nothing newer.

I disabled Animation, let's see if it helps.

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

Title:
  [bionic][regression] gnome-shell crashes with SIGSEGV in
  meta_window_actor_is_destroyed(self=NULL) called from
  _switchWorkspaceDone() [windowManager.js:1787]

Status in gjs package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gjs source package in Bionic:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/cb400a6f83ed57af8bb117cf84d5ed6d7e2ffcee
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/927

  Switching workspace with the Android Emulator running will blink the
  screen as if gnome restarted, if I switch workspace one more time, it
  will completely crash and I will need to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  Uname: Linux 4.20.3-acso x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 19 20:05:34 2019
  DisplayManager: gdm3
  GsettingsChanges:
   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 2019-01-15 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823778] Re: Unable to set Serbian as Language

[Gunnar Hjalmarsson]

I checked panels/common/cc-common-language.c and found that all the
installed languages (including the two Serbian ones) are passed to the
insert_language() function, whose label_own_lang variable is assigned
the corresponding label. Hence the GHashTable returned by
cc_common_language_get_initial_languages() ought to include it all.

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

Title:
  Unable to set Serbian as Language

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Affected: 18.04.2 (did not try earlier versions of 18.04 series)
  Not affected: 16.04 - any version (UI was different)

  Preparation steps:
  1. open gnome control center
  2. open Region & Language
  3. open Manage installed languages
  4. open Install/Remove languages
  5. select Serbian, click Apply
  6. provide credentials for sudo installation
  7. wait for installation to complete
  8. click Close

  What is wrong:
  1. open gnome control center
  2. open Region & Language
  3. click Language selection
  4. Serbian is not visible

  Notes:
  - Serbian is visible for the Formats selection
  - Any other language I thought of: (Macedonian, Croatian, Bosnian, 
Russion...) simple work.

  
  Here is some dpkg output on installaed packages matching sr (Serbian) or hr 
(Croatian).

  ii  firefox-locale-sr  66.0.2+build1-0ubuntu0.18.04.1 
  amd64Serbian language pack for Firefox
  ii  gnome-getting-started-docs-sr  3.28.2-0ubuntu0.1  
  all  Help a new user get started in GNOME (Serbian)
  ii  gnome-user-docs-sr 3.28.2+git20180715-0ubuntu0.1  
  all  GNOME user's guide (Serbian)
  ii  hunspell-sr1:6.0.3-3  
  all  Serbian dictionary for hunspell
  ii  hyphen-sr  1:6.0.3-3  
  all  Serbian hyphenation patterns
  ii  language-pack-gnome-sr 1:18.04+20180712   
  all  GNOME translation updates for language Serbian
  ii  language-pack-gnome-sr-base1:18.04+20180712   
  all  GNOME translations for language Serbian
  ii  language-pack-sr   1:18.04+20180712   
  all  translation updates for language Serbian
  ii  language-pack-sr-base  1:18.04+20180712   
  all  translations for language Serbian
  ii  libreoffice-l10n-sr1:6.0.7-0ubuntu0.18.04.2   
  all  office productivity suite -- Serbian language package
  ii  thunderbird-locale-sr  
1:60.6.1+build2-0ubuntu0.18.04.1 amd64Serbian language pack 
for Thunderbird
  nebojsa@momcilo-desktop:~$ dpkg -l | grep -e "-hr"
  rc  language-pack-gnome-hr-base1:18.04+20180712   
  all  GNOME translations for language Croatian
  rc  language-pack-hr-base  1:18.04+20180712   
  all  translations for language Croatian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 20:10:54 2019
  InstallationDate: Installed on 2019-04-06 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1246272] Re: Keyboard layout changing randomly

[Vladymir]

actually, it doesn't switch layout (at least for me), but it ADDS A NEW LAYOUT 
instead! 
let me explain this. 
I do not use a "plain" en_us layout, but use us+dvorak and ru+dvorak (custom 
created). 
so, when "us+dvorak" is active, it adds "us" to the end of the list. 
when "ru+dvorak" is active, it adds "ru" to the end of the list. 
when added, new layout becomes selected. 
also, new added layout is not visible in gui settings, but everyone can see it 
by command 'setxkbmap -query'. 

also, I made a workaround for this crap. 
1. set 'org.gnome.settings-daemon.plugins.keyboard active false' to switch off 
defective plugin.
2. to switch layouts, I created keybindinds EMBEDDED into my layout (a new 
modifier key).
3. installed gxkb to have an indicator of selected layout in the system tray. 

I restored the lost multimedia keys and other keybindings in compiz
settings.

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

Title:
  Keyboard layout changing randomly

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1455097] Re: /etc/pm/sleep.d/ is no more processed

[Balint Reczey]

Verified 1.1ubuntu1.18.04.7~16.04.2 on Xenial, now without acpdid:

ubuntu@ip-172-31-3-29:~$ sudo service apt-daily-upgrade start & sleep 1; tail 
-f /var/log/unattended-upgrades/unattended-upgrades.log
[1] 1607
2019-04-09 20:58:27,975 INFO Initial blacklisted packages: 
2019-04-09 20:58:27,975 INFO Initial whitelisted packages: 
2019-04-09 20:58:27,975 INFO Starting unattended upgrades script
2019-04-09 20:58:27,975 INFO Allowed origins are: o=Ubuntu,a=xenial, 
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial
2019-04-09 20:58:31,986 INFO Packages that will be upgraded: busybox-initramfs 
busybox-static file libmagic1 libpam-systemd libpolkit-agent-1-0 
libpolkit-backend-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 linux-aws 
linux-headers-aws linux-image-aws ntfs-3g policykit-1 snapd systemd 
systemd-sysv ubuntu-core-launcher udev wget
2019-04-09 20:58:31,987 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2019-04-09 20:58:49,942 WARNING SIGTERM received, will stop
2019-04-09 20:58:52,944 WARNING SIGTERM received, will stop
2019-04-09 20:58:53,159 WARNING SIGNAL received, stopping

ubuntu@ip-172-31-3-29:~$ cat 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log .
Log started: 2019-04-09  20:58:35
(Reading database ... 76460 files and directories currently installed.)
Preparing to unpack .../libpolkit-gobject-1-0_0.105-14.1ubuntu0.5_amd64.deb ...
Unpacking libpolkit-gobject-1-0:amd64 (0.105-14.1ubuntu0.5) over 
(0.105-14.1ubuntu0.4) ...
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Setting up libpolkit-gobject-1-0:amd64 (0.105-14.1ubuntu0.5) ...
Processing triggers for libc-bin (2.23-0ubuntu11) ...
Log ended: 2019-04-09  20:58:37
...
ubuntu@ip-172-31-3-29:~$ dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all  automatic 
installation of security upgrades
ubuntu@ip-172-31-3-29:~$ yes no | sudo apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-aws-headers-4.4.0-1079 linux-headers-4.4.0-1079-aws 
linux-image-4.4.0-1079-aws
  linux-modules-4.4.0-1079-aws
The following packages will be upgraded:
  apt apt-transport-https apt-utils cloud-init distro-info-data file 
grub-common grub-legacy-ec2 grub-pc
  grub-pc-bin grub2-common libapt-inst2.0 libapt-pkg5.0 liblxc1 libmagic1 
libpam-systemd libsystemd0 libudev1
  linux-aws linux-headers-aws linux-image-aws login lxc-common ntfs-3g passwd 
policykit-1 python-apt-common
  python3-apt rsyslog snapd systemd systemd-sysv ubuntu-core-launcher udev 
uidmap
35 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/54.7 MB of archives.
After this operation, 118 MB of additional disk space will be used.
Do you want to continue? [Y/n] Abort.
ubuntu@ip-172-31-3-29:~$ dpkg -l acpid
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---==
rc  acpid  1:2.0.26-1ubuntu amd64Advanced 
Configuration and Power Interface event d
ubuntu@ip-172-31-3-29:~$ journalctl -a
...
Apr 09 20:58:49 ip-172-31-3-29 kernel: PM: Hibernation mode set to 'platform'
Apr 09 20:58:53 ip-172-31-3-29 systemd[1]: Started Daily apt upgrade and clean 
activities.
Apr 09 20:58:53 ip-172-31-3-29 sudo[1607]: pam_unix(sudo:session): session 
closed for user root
Apr 09 20:58:55 ip-172-31-3-29 systemd-sleep[8427]: Suspending system...
Apr 09 20:59:46 ip-172-31-3-29 kernel: PM: Syncing filesystems ... done.
Apr 09 20:59:46 ip-172-31-3-29 kernel: Freezing user space processes ... 
(elapsed 0.000 seconds) done.
...

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1455097

Title:
  /etc/pm/sleep.d/ is no more processed

Status in aiccu package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in ifplugd package in Ubuntu:
  New
Status in lizardfs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  Won't Fix
Status in toshset 

[Desktop-packages] [Bug 1823793] Re: [regression] Font scaling not working on gnome startup

[Juan Pablo Aroztegi]

Version 3.32.0-1ubuntu2, released today, has fixed the issue for me.

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

Title:
  [regression] Font scaling not working on gnome startup

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The font text scaling setting is not being loaded on gnome startup. I
  have font text scaling set to 1.25. After updating mutter to package
  version 3.32.0-1ubuntu1 the text scaling setting is not loaded any
  more when starting gnome. Steps to reproduce the issue:

  1) Set your font scaling factor to something other than the default
  '1'. This can be set, for example, either by using "Gnome tweaks" or
  with gsettings:

  settings set org.gnome.desktop.interface text-scaling-factor 1.25

  2) You'll see that the top bar text gets larger.
  3) Log out and log in. You'll see that the top bar text and text in general 
has been reset to the default '1'. The setting is still set to '1.25', but 
visually it's '1'.

  If you set the value to something else, it gets applied correctly,
  until you log out.

  
  This worked as expected on package version 3.32.0-1. I wonder if this patch 
listed in the CHANGELOG could have somehow created this side effect:
  debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  - X11: Add support for fractional scaling using Randr

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: mutter 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  8 13:42:39 2019
  InstallationDate: Installed on 2019-04-08 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190408)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823382] Re: backport openssl 1.1.1 fixes to bionic and cosmic

[Brian Murray]

Hello Dimitri, or anyone else affected,

Accepted neon27 into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neon27/0.30.2-3~ubuntu18.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: neon27 (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

** Changed in: neon27 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  backport openssl 1.1.1 fixes to bionic and cosmic

Status in neon27 package in Ubuntu:
  Fix Released
Status in neon27 source package in Bionic:
  Fix Committed
Status in neon27 source package in Cosmic:
  Fix Committed
Status in neon27 source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * neon27 doesn't work with openssl 1.1.1
   * backport fixes from disco to cosmic and bionic to resolve that

  [Test Case]

   * does not FTBFS

  [Regression Potential]

   * currently broken in cosmic, and will break once openssl is upgraded
  in bionic, so for all practical purposes it's completely busted at the
  moment.

  [Other Info]
   
   * Fixes already in disco and unstable.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823382] Please test proposed package

[Brian Murray]

Hello Dimitri, or anyone else affected,

Accepted neon27 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/neon27/0.30.2-3~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  backport openssl 1.1.1 fixes to bionic and cosmic

Status in neon27 package in Ubuntu:
  Fix Released
Status in neon27 source package in Bionic:
  Fix Committed
Status in neon27 source package in Cosmic:
  Fix Committed
Status in neon27 source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * neon27 doesn't work with openssl 1.1.1
   * backport fixes from disco to cosmic and bionic to resolve that

  [Test Case]

   * does not FTBFS

  [Regression Potential]

   * currently broken in cosmic, and will break once openssl is upgraded
  in bionic, so for all practical purposes it's completely busted at the
  moment.

  [Other Info]
   
   * Fixes already in disco and unstable.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823639] Re: Facing problem with Xorg recently. [(EE) intel(0): Failed to claim DRM device.]

[Timo Aaltonen]

also, I don't think modesetting driver was yet good enough in xserver
1.18, so -intel probably is the best option on stock xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1823639

Title:
  Facing problem with Xorg recently. [(EE) intel(0): Failed to claim DRM
  device.]

Status in plymouth package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 16.04 LTS

  Recently I have been facing problem with computer graphics.
  Sometimes while working, the system freezes and when the system resumes 
working a pop-up window appears stating that "An error occurred", and in the 
details of the error there is problem with Xorg.

  Today, after powering on the system, a message appeared saying:-
  "The system is running in low-graphics mode. You screen, graphics card, and 
input device settings could not be detected correctly. You will need to 
configure these yourself".
  Using a solution from askubuntu forum, I did the following:-

  1) Pressed Ctrl + Alt + F1
  2) Logged in with my credentials
  3) Ran the following commands: 
  $ sudo apt-get install --reinstall ubuntu-desktop
  $ sudo reboot

  This helped me open the system.

  Now, I checked whether the graphics driver is installed or not. So, I went to 
Settings > Software & Updates > Additional drivers.
  But, no driver is detected. 

  So, I guess that there no graphics driver installed on my system.

  After that, I tried the following solution, but the terminal says that
  requirement already satisfied:-

  https://askubuntu.com/a/183170

  Please help me resolve the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr  8 12:57:15 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics [8086:1606] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:06c1]
  InstallationDate: Installed on 2017-08-30 (586 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Vostro 3558
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-145-generic 
root=UUID=cb4d1c91-3742-4037-a99c-3a2a33b739a5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0HRXD8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/22/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0HRXD8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 3558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr  8 12:44:33 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1568 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.8

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823639] Re: Facing problem with Xorg recently. [(EE) intel(0): Failed to claim DRM device.]

[Timo Aaltonen]

try booting without 'splash', since it seems to be plymouth holding the
device

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1823639

Title:
  Facing problem with Xorg recently. [(EE) intel(0): Failed to claim DRM
  device.]

Status in plymouth package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 16.04 LTS

  Recently I have been facing problem with computer graphics.
  Sometimes while working, the system freezes and when the system resumes 
working a pop-up window appears stating that "An error occurred", and in the 
details of the error there is problem with Xorg.

  Today, after powering on the system, a message appeared saying:-
  "The system is running in low-graphics mode. You screen, graphics card, and 
input device settings could not be detected correctly. You will need to 
configure these yourself".
  Using a solution from askubuntu forum, I did the following:-

  1) Pressed Ctrl + Alt + F1
  2) Logged in with my credentials
  3) Ran the following commands: 
  $ sudo apt-get install --reinstall ubuntu-desktop
  $ sudo reboot

  This helped me open the system.

  Now, I checked whether the graphics driver is installed or not. So, I went to 
Settings > Software & Updates > Additional drivers.
  But, no driver is detected. 

  So, I guess that there no graphics driver installed on my system.

  After that, I tried the following solution, but the terminal says that
  requirement already satisfied:-

  https://askubuntu.com/a/183170

  Please help me resolve the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr  8 12:57:15 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics [8086:1606] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Broadwell-U Integrated Graphics [1028:06c1]
  InstallationDate: Installed on 2017-08-30 (586 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Vostro 3558
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-145-generic 
root=UUID=cb4d1c91-3742-4037-a99c-3a2a33b739a5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0HRXD8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/22/2016:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn0HRXD8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Vostro 3558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr  8 12:44:33 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1568 
   vendor BOE
  xserver.version: 2:1.18.4-0ubuntu0.8

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1272380] Re: Missing whitespace between generated man page refentrys

[Roger Light]

This is no longer an issue in recent Ubuntu releases.

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

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

Title:
  Missing whitespace between generated man page refentrys

Status in libxslt package in Ubuntu:
  Fix Released

Bug description:
  I am generating man pages from docbook xml using xsltproc and
  /usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl

  My man page contains entries like this for the "See Also" section:

 
  mosquitto
  8
  
  
  mosquitto-conf
  5
  

  When I process the man pages using xsltproc from Saucy, the resulting
  code looks like:

  \fBmosquitto\fR(8)\fBmosquitto-conf\fR(5)

  When viewed in man, this looks like "mosquitto(8)mosquitto-conf(5)" -
  with no space between the two entries.

  On Precise, the output from the same man page is:

  \fBmosquitto\fR(8)
  \fBmosquitto-conf\fR(5)

  and when viewed in man this looks like "mosquitto(8) mosquitto-
  conf(5)" as expected.

  The xml man pages and Makefile to generate the troff output can be
  found in http://mosquitto.org/files/source/mosquitto-1.2.3.tar.gz in
  the man directory.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1818766] Re: Update to 1.47

[Launchpad Bug Tracker]

This bug was fixed in the package snapd-glib - 1.47-0ubuntu0.16.04.0

---
snapd-glib (1.47-0ubuntu0.16.04.0) xenial; urgency=medium

  * New upstream release (LP: #1818766)
  * debian/rules:
- Build with --enable-installed-tests
  * debian/tests/control:
  * debian/tests/unit:
  * debian/snapd-glib-tests.install:
- Add autopkg tests
  * debian/libsnapd-glib1.symbols:
- Updated

snapd-glib (1.45-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream release (LP: #1793298):
- Remove deprecated snapd-login-service
- New API:
  - snapd_app_get_common_id
  - snapd_client_get_apps2_sync
  - snapd_client_get_apps2_async
  - snapd_client_get_apps2_finish
  - snapd_client_get_maintenance
  - snapd_client_get_snap_async
  - snapd_client_get_snap_finish
  - snapd_client_get_snap_sync
  - snapd_client_get_snaps_async
  - snapd_client_get_snaps_finish
  - snapd_client_get_snap_sync
  - snapd_maintenance_get_kind
  - snapd_maintenance_get_message
  - snapd_media_get_media_type
  - snapd_media_get_url
  - snapd_media_get_width
  - snapd_media_get_height
  - snapd_snap_get_base
  - snapd_snap_get_common_ids
  - snapd_snap_get_media
  - snapd_snap_get_mounted_from
  - snapd_snap_get_publisher_display_name
  - snapd_snap_get_publisher_id
  - snapd_snap_get_publisher_username
  - snapd_snap_get_publisher_validation
  - snapd_system_information_get_build_id
  - snapd_system_information_get_refresh_hold
  - snapd_system_information_get_refresh_last
  - snapd_system_information_get_refresh_next
  - snapd_system_information_get_refresh_schedule
  - snapd_system_information_get_refresh_timer
  - snapd_system_information_get_sandbox_features
  - SNAPD_ERROR_AUTH_CANCELLED
  - SNAPD_ERROR_NOT_FOUND
  - SNAPD_ERROR_NOT_IN_STORE
  - SNAPD_ERROR_NOT_CLASSIC
  - SNAPD_ERROR_REVISION_NOT_AVAILABLE
  - SNAPD_ERROR_CHANNEL_NOT_AVAILABLE
  - SNAPD_ERROR_NOT_A_SNAP
  - SNAPD_FIND_FLAGS_SCOPE_WIDE
- Deprecated API:
  - snapd_client_get_apps_sync
  - snapd_client_get_apps_async
  - snapd_client_get_apps_finish
  - snapd_client_list_async
  - snapd_client_list_finish
  - snapd_client_list_sync
  - snapd_login_async
  - snapd_login_finish
  - snapd_login_sync
  - snapd_snap_get_screenshots
- Fix buffer overflows reading HTTP chunked data
- Reconnect to snapd if disconnected while trying to send the request
- Handle short writes to snapd
- Remove cancelled requests from the request queue.
- Fix SnapdClient reference leak in each request
- Fix snapd_snap_match_channel not matching risks correctly
- Fix progress callback scope annotations
- Fix double-unref on cancelled requests
- Support new snap media and mounted-from fields
- Support filtering when querying apps
- Support snapd maintenance information
- Support new error codes
- GIR annotation fixes
  * debian/libsnapd-glib1.symbols:
- Updated
  * debian/control:
  * debian/snapd-login-service.install
- snapd-login-service removed

 -- Robert Ancell   Wed, 06 Mar 2019
15:54:33 +1300

** Changed in: snapd-glib (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to snapd-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1818766

Title:
  Update to 1.47

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  Fix Released
Status in snapd-glib source package in Bionic:
  Fix Released
Status in snapd-glib source package in Cosmic:
  Fix Released
Status in snapd-glib source package in Disco:
  Fix Released

Bug description:
  [Impact]
  A newer snapd-glib is available that adds support for new features in snapd. 
snapd-glib has an SRU exception as per https://wiki.ubuntu.com/SnapdGlibUpdates

  [Test Case]
  The reverse depends of snapd-glib should continue to function, this is 
currently:
  - gnome-software
  - gnome-initial-setup
  - pulseaudio

  [Regression Potential]
  Any new release has a risk of introducing bugs, this is mitigated by 
automatic regression tests.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823539] Re: gnome-control-center crashed with SIGSEGV in g_date_time_to_instant()

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

** Information type changed from Private to Public

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-control-center crashed with SIGSEGV in g_date_time_to_instant()

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  It crashed while attempting to configure time-zones, date and time
  while on the Live USB image.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: gnome-control-center 1:3.32.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CasperVersion: 1.402
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 14:19:11 2019
  ExecutablePath: /usr/bin/gnome-control-center
  JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', 
'--lines=1000'] failed with exit code 1: No journal files were opened due to 
insufficient permissions.
  LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  ProcCmdline: gnome-control-center user-accounts
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fda92523ca4 :mov
0x10(%rdi),%esi
   PC (0x7fda92523ca4) ok
   source "0x10(%rdi)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-control-center
  StacktraceTop:
   g_date_time_to_unix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-control-center crashed with SIGSEGV in g_date_time_to_unix()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

[Launchpad Bug Tracker]

This bug was fixed in the package upower - 0.99.7-2ubuntu0.18.04.1

---
upower (0.99.7-2ubuntu0.18.04.1) bionic; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * debian/control: update mantainer to ubuntu
  * debian/gbp.conf: update branch to ubuntu/bionic
  * d/p/daemon-Consider-pending-charge-when-calculating-the-displ.patch:
- Detect AC state on pending state (LP: #1745032)

  [ Iain Lane ]
  * debian/control: Update Vcs-* for Launchpad
  * gbp.conf: Set debian-tag to create ubuntu/xxx tags

 -- Iain Lane   Fri, 25 Jan 2019 16:38:41 +

** Changed in: upower (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: gnome-control-center (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in upower source package in Bionic:
  Fix Released
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:3.28.2-0ubuntu0.18.04.3

---
gnome-control-center (1:3.28.2-0ubuntu0.18.04.3) bionic; urgency=medium

  * debian/patches/power-Label-the-PENDING_CHARGING-state-as-Not-Charging.patch:
- Label the PENDING_CHARGING state as "Not Charging" (LP: #1745032)

 -- Marco Trevisan (Treviño)   Fri, 25 Jan 2019
19:04:00 +

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in upower source package in Bionic:
  Fix Released
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml

[Laurent Bonnaud]

I cannot reproduce the bug in Ubuntu 19.04.  Thanks for the fix!

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

Title:
  Unknown media types in /usr/share/mime/packages/kde.xml

Status in kdelibs:
  Won't Fix
Status in shared-mime-info:
  Won't Fix
Status in kde4libs package in Ubuntu:
  Confirmed
Status in shared-mime-info package in Ubuntu:
  Triaged
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  Here is the problem:

  # update-mime-database /usr/share/mime
  [...]
  Unknown media type in type 'uri/mms'

  Unknown media type in type 'uri/mmst'

  Unknown media type in type 'uri/mmsu'

  Unknown media type in type 'uri/pnm'

  Unknown media type in type 'uri/rtspt'

  Unknown media type in type 'uri/rtspu'

  It seems to come from this file:
/usr/share/mime/packages/kde.xml

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")

[Derk Willem te Bokkel]

okay apr 8 and apr 9 iso's have same issues kept logs of various boots
into the fresh installs .. no change in grub-source during testing was
made .. all with fresh installs

typical first boot is normal ..  no crash of xorg on first start ..
second boot shows lightdm briefly then xorg crashes while trying to use FBDEV 
last item before crash loads libfb.so then backtrace happens and crash ..

.. then xorg restarts with a working driver

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1821609

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870 (crash in xorg before using "foreign grub")

Status in lightdm package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[Desktop-packages] [Bug 1085706] Re: pam_ecryptfs: seteuid error

[Laurent Bonnaud]

The bug is still there in cosmic:

# journalctl | grep pam_ecryptfs
Apr 09 20:27:24 vougeot kcheckpass[757]: pam_ecryptfs: seteuid error


** Tags added: bionic cosmic

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

Title:
  pam_ecryptfs: seteuid error

Status in eCryptfs:
  Confirmed
Status in GNOME Screensaver:
  New
Status in ecryptfs-utils package in Ubuntu:
  Triaged
Status in gnome-screensaver package in Ubuntu:
  Triaged
Status in kscreenlocker package in Ubuntu:
  Confirmed
Status in plasma-workspace package in Ubuntu:
  Confirmed
Status in gnome-screensaver package in Debian:
  New

Bug description:
  I get this error message in the syslog when I authenticate succesfully
  in the screensaver.

  ---
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  DistroRelease: Ubuntu 12.10
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2012-06-13 (172 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  Package: gnome-screensaver 3.6.0-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
  Tags:  quantal running-unity
  Uname: Linux 3.5.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

[Sami Pietila]

I further tested this new 4.18.0-18-generic kernel and with this kernel
the wifi seems to work very good. I did not observe any slowness as I
did with the patched 4.18.0-16 kernel.

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   

[Desktop-packages] [Bug 1641308] Re: Partitions display wrong in gnome -disks - ok in gparted

[pothos]

Found the problem: The Debian source for the libparted package does not
include the patch introduced by commit c6dc6e5d in 2015 (No official
parted release since 2014, so picking commits is unfortunately needed).

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

Title:
  Partitions display wrong in gnome -disks - ok in gparted

Status in gnome-disk-utility package in Ubuntu:
  Confirmed

Bug description:
  The partitions displayed by gnome-disk-utility are wrong. When i use
  gparted the partitions displayed are correct.

  The display became wrong after i deleted 1 partition from the disk
  using gnome-disk-utility.

  Here is a screenshot of the 2 tools vision of the same disk:
  http://pasteboard.co/PjWpqeNzi.png

  Here is the fdisk:
  hippo@hippo-camp:~$ sudo fdisk -l
  [sudo] password for hippo: 
  Disk /dev/sdc: 465,8 GiB, 500107862016 bytes, 976773168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x1c0966b0

  Device Boot Start   End   Sectors   Size Id Type
  /dev/sdc1  *   63 758587953 758587891 361,7G  7 HPFS/NTFS/exFAT
  /dev/sdc3   758589438 903041023 144451586  68,9G  5 Extended
  /dev/sdc5   758589440 903041023 144451584  68,9G 83 Linux

  
  hippo@hippo-camp:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  gnome-disk-utility:
Installed: 3.18.3.1-1ubuntu1
Candidate: 3.18.3.1-1ubuntu1
Version table:
   *** 3.18.3.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  gparted:
Installed: 0.25.0-1
Candidate: 0.25.0-1
Version table:
   *** 0.25.0-1 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  I get *very nervous* when tools that have write access to partitions
  can't display them properly.

  
  Good hunt
  Matt

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-disk-utility 3.18.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Nov 12 12:16:39 2016
  ExecutablePath: /usr/bin/gnome-disks
  InstallationDate: Installed on 2016-10-11 (31 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-disk-utility
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823440] Re: ubuntu-report ftbfs in disco

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-report - 1.4.1

---
ubuntu-report (1.4.1) disco; urgency=medium

  * Ship go modules files for -dev now that distro moved to 1.11.
(LP: #1823440)

 -- Didier Roche   Tue, 09 Apr 2019 15:16:07 +0200

** Changed in: ubuntu-report (Ubuntu Disco)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1823440

Title:
  ubuntu-report ftbfs in disco

Status in ubuntu-report package in Ubuntu:
  Fix Released
Status in ubuntu-report source package in Disco:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417924361/buildlog_ubuntu-disco-amd64
  .ubuntu-report_1.4.0_BUILDING.txt.gz

 debian/rules override_dh_missing
  make[1]: Entering directory '/<>'
  dh_missing --fail-missing
  dh_missing: usr/share/gocode/src/github.com/ubuntu/ubuntu-report/go.mod 
exists in debian/tmp but is not installed to anywhere
  dh_missing: usr/share/gocode/src/github.com/ubuntu/ubuntu-report/go.sum 
exists in debian/tmp but is not installed to anywhere
  dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: golang-github-ubuntu-ubuntu-report-dev (2), 
libsysmetrics-dev (3), libsysmetrics1 (1), ubuntu-report (6)
 * dh_installdocs: golang-github-ubuntu-ubuntu-report-dev (0), 
libsysmetrics-dev (0), libsysmetrics1 (0), ubuntu-report (0)
 * dh_installman: golang-github-ubuntu-ubuntu-report-dev (0), 
libsysmetrics-dev (0), libsysmetrics1 (0), ubuntu-report (4)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
  make[1]: *** [debian/rules:39: override_dh_missing] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:14: binary] Error 2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1455097] Re: /etc/pm/sleep.d/ is no more processed

[Balint Reczey]

I need to verify this bug again because acpi was pulled in to the image.

** Tags removed: verification-done verification-done-xenial
** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1455097

Title:
  /etc/pm/sleep.d/ is no more processed

Status in aiccu package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in ifplugd package in Ubuntu:
  New
Status in lizardfs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  Won't Fix
Status in toshset package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact (unattended-upgrades)]

   * Unattended-upgrades does not gracefully stop installing updates
  when the system goes to hibernation potentially letting the system to
  hibernate in a state where the system can't resume from.

  [Test Case (unattended-upgrades)]

   * Configure the system to have several 20+ packages upgradable by
  unattended-upgrades. One easy way of setting this up is starting with
  a system where packages from -security are installed but packages from
  -updates are not and enabling -updates in u-u:

# echo 'Unattended-Upgrade::Allowed-Origins::
  "${distro_id}:${distro_codename}-updates";' > /etc/apt/apt.conf.d
  /51unattended-upgrades-updates-too

  * Pre-download upgrades
# unattended-upgraded --download-only

  * Trigger unattended-upgrades run:
#  service apt-daily-upgrade start

  * Hibernate, then resume the system and watch unattended-upgrades
  being gracefully stopped, checking /var/log/unattended-upgrades
  /unattended-upgrades.log. There should be packages left to be
  upgraded.

  [Regression Potential (unattended-upgrades)]

   * The added hook for unattended-upgrades may block the system from
  hibernation for 25 minutes if unattended-upgrades (or most likely a
  package upgrades) hangs. There is a better solution proposed based on
  systemd's inhibitor interface at https://github.com/mvo5/unattended-
  upgrades/issues/162 .

  [Original Bug Text]

  I added a new script in /etc/pm/sleep.d/ that worked fine before the
  upgrade to vivid. I was wondering why it doesn't work and I find out
  that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last
  logs from pm-suspend were on Apr 28, when I upgraded from utopic to
  vivid.

  The laptop suspends and wakes fine, it just seems that no pm scripts
  are run after suspend/powersave.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pm-utils 1.4.1-15
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 14 15:36:26 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-03-12 (792 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823437] Re: shotwell ftbfs in disco

[Launchpad Bug Tracker]

This bug was fixed in the package shotwell - 0.30.2-0ubuntu2

---
shotwell (0.30.2-0ubuntu2) disco; urgency=medium

  * debian/patches/git_glib_bindingflags.patch
- Fix references to GLib.BindingFlags (LP: #1823437)

 -- Ken VanDine   Tue, 09 Apr 2019 10:11:48
-0400

** Changed in: shotwell (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  shotwell ftbfs in disco

Status in shotwell package in Ubuntu:
  Fix Released
Status in shotwell source package in Disco:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417924359/buildlog_ubuntu-disco-
  amd64.shotwell_0.30.2-0ubuntu1_BUILDING.txt.gz

  multiple vala/glib errors

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823435] Re: session-migration ftbfs in disco

[Launchpad Bug Tracker]

This bug was fixed in the package session-migration - 0.3.4

---
session-migration (0.3.4) disco; urgency=medium

  * Fix failing tests due to keyfiles get from stdlib not keeping tuple
order. (LP: #1823435)

 -- Didier Roche   Tue, 09 Apr 2019 15:38:19 +0200

** Changed in: session-migration (Ubuntu Disco)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to session-migration in Ubuntu.
https://bugs.launchpad.net/bugs/1823435

Title:
  session-migration ftbfs in disco

Status in session-migration package in Ubuntu:
  Fix Released
Status in session-migration source package in Disco:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/417924320/buildlog_ubuntu-disco-amd64
  .session-migration_0.3.3_BUILDING.txt.gz

  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/depend
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/check.dir/DependInfo.cmake 
--color=
  Scanning dependencies of target check
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/build
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  nosetests3
  ...FF
  ==
  FAIL: Test that the migration happens as expected
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
144, in test_migration
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;')
  AssertionError: '10_test.sh;01_test.sh;02_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;'
  - 10_test.sh;01_test.sh;02_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;

  
  ==
  FAIL: Test subsequent runs with a new script
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
225, in test_subsequent_runs_with_new_script
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;')
  AssertionError: '02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;'
  - 02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;

  
  --
  Ran 9 tests in 8.615s

  FAILED (failures=2)
  make[5]: *** [CMakeFiles/check.dir/build.make:60: CMakeFiles/check] Error 1
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[4]: *** [CMakeFiles/Makefile2:76: CMakeFiles/check.dir/all] Error 2
  make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[3]: *** [CMakeFiles/Makefile2:83: CMakeFiles/check.dir/rule] Error 2
  make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[2]: *** [Makefile:167: check] Error 2
  make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  dh_auto_test: cd obj-x86_64-linux-gnu && make -j1 check ARGS\+=-j1 returned 
exit code 2
  make[1]: *** [debian/rules:18: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:10: build] Error 2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1772465]

[Beluga]

*** Bug 124222 has been marked as a duplicate of this bug. ***

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

Title:
  Pressing undo in Writer removes text but not formatting

Status in LibreOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  To reproduce this bug, follow these steps:

  1) Create two paragraphs of text, one with font size 14 and the other with 
size 18.
  2) Copy some text from the first paragraph to the end of the second paragraph 
using Ctrl-C and Ctrl-V.
  3) Now press immediately Ctrl-Z for undo.
  4) While the cursor is still at the end of the second paragraph, type some 
new text.

  As a user, I would expect the new text to have font size 18, since
  that’s the size of the text just before the cursor. However, as it
  appears, the new text gets font size 14 because of the text that was
  copied from the first paragraph. Thus it seems that Ctrl-Z did not
  undo the whole copy operation but instead just removed the copied text
  and left its formatting.

  Description:  Ubuntu 17.10
  Release:  17.10

  libreoffice-writer:
Installed: 1:5.4.6-0ubuntu0.17.10.1
Candidate: 1:5.4.6-0ubuntu0.17.10.1
Version table:
   *** 1:5.4.6-0ubuntu0.17.10.1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.4.5-0ubuntu0.17.10.5 500
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   1:5.4.1-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1
  ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16
  Uname: Linux 4.13.0-41-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 21 17:25:11 2018
  InstallationDate: Installed on 2017-02-13 (462 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772465/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1821403] Re: chromium browser crash on fresh offline system install

[Jozef Behran]

The chromium-browser metadata needs fixing (as explained in my last
comment) so that libnss3 gets upgraded automatically on "apt-get install
chromium-browser".

** Changed in: chromium-browser (Ubuntu)
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1821403

Title:
  chromium browser crash on fresh offline system install

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Steps to reproduce (and also what I expected and what happened):

  1. Disconnect computer from Internet
  2. Install Ubuntu (complete with reboot at the end).
  3. After running the (freshly installed) system, connect it to Internet
 and open a terminal and follow with the session outlined below. Enter
 commands on lines starting with "$" into the terminal. Things on lines
 starting with "//" are my comments and/or descriptions of what is
 expected output of the preceding command.

  $ sudo apt-get update
  // you should get the normal apt-get update output with no errors
  $ sudo apt-get install -y chromium-browser
  // you should get the normal apt-get install output here with no errors
  $ chromium-browser
  // expected result is to have the browser running and possibly some harmless
  // warnings below the "$ chromium-browser" line. What actually happens instead
  // is this:
  Fontconfig warning: "/etc/fonts/fonts.conf", line 146: blank doesn't take any 
effect anymore. please remove it from your fonts.conf
  [2805:2844:0322/144827.306513:FATAL:nss_util.cc(631)] 
NSS_VersionCheck("3.26") failed. NSS >= 3.26 is required. Please upgrade to the 
latest NSS, and if you still get this error, contact your distribution 
maintainer.
  Aborted (core dumped)
  // I believe that the problem is that the package "chromium-browser"
  // is either missing dependency on "libnss3-nssdb" or broken dependency
  // on "libnss3" (missing version number). To see, why, continue with:
  $ sudo apt-get install -y libnss3
  // What I got on the terminal myself follows (with some comments)
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
libnss3-nssdb
  // This is why I said the missing dependency might be "libnss3-nssdb"
  // Here apt-get is telling me that "libnss3-nssdb" is going to be
  // installed.
  The following packages will be upgraded:
libnss3 libnss3-nssdb
  2 upgraded, 0 newly installed, 0 to remove and 452 not upgraded.
  Need to get 1,135 kB of archives.
  After this operation, 2,048 B of additional disk space will be used.
  // I didn't use "-y" on my command line so apt-get asked for permission.
  // You might be missing the line below if you follow the session
  // exactly. I included the rest of apt-get output to show you what
  // exactly got installed by the command.
  Do you want to continue? [Y/n] 
  Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libnss3-nssdb 
all 2:3.28.4-0ubuntu0.14.04.5 [10.6 kB]
  Get:2 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libnss3 amd64 
2:3.28.4-0ubuntu0.14.04.5 [1,124 kB]
  Fetched 1,135 kB in 2s (477 kB/s)  
  (Reading database ... 166878 files and directories currently installed.)
  Preparing to unpack .../libnss3-nssdb_2%3a3.28.4-0ubuntu0.14.04.5_all.deb ...
  Unpacking libnss3-nssdb (2:3.28.4-0ubuntu0.14.04.5) over 
(2:3.23-0ubuntu0.14.04.1) ...
  Preparing to unpack .../libnss3_2%3a3.28.4-0ubuntu0.14.04.5_amd64.deb ...
  Unpacking libnss3:amd64 (2:3.28.4-0ubuntu0.14.04.5) over 
(2:3.23-0ubuntu0.14.04.1) ...
  Setting up libnss3-nssdb (2:3.28.4-0ubuntu0.14.04.5) ...
  Setting up libnss3:amd64 (2:3.28.4-0ubuntu0.14.04.5) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.9) ...
  // Now when I try to run the browser ...
  $ chromium-browser
  // ... this warning is still there ...
  Fontconfig warning: "/etc/fonts/fonts.conf", line 146: blank doesn't take any 
effect anymore. please remove it from your fonts.conf
  [2991:2991:0322/145149.851132:ERROR:gpu_process_transport_factory.cc(1019)] 
Lost UI shared context.
  // ... but no more "NSS_VersionCheck failed" nor "Aborted (core dumped)"
  // (and, of course, the terminal window on the desktop is no longer
  // alone as the fresh google-chrome window is making a company to it ...

  Final notes:

  - This bug may not occur if you try to install Ubuntu while connected to 
Internet.
  - The reason why I did a "fresh offline install" was that installing it while 
online
takes over a hour on my system, installing offline and then doing the 
commands above
took only about 10 minutes. You might want to try to take a look into why 
is online
Ubuntu install so slow but that is not the bug I want to report here (I 
will file
a different bug for that if I can figure out, how).
  - Offline installs are pretty common in 

[Desktop-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

[Sami Pietila]

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic 

[Desktop-packages] [Bug 1821403] Re: chromium browser crash on fresh offline system install

[Jozef Behran]

> chromium-browser requires a newer version of libnss3 than what was
initially installed.

It is the job of the package manager to either upgrade an outdated
version of a dependency package when the user tries to install something
or to ask the user to update the system first and then try again, not to
silently install a package with its requirement missing and leave the
user wondering what exactly happened.

The bug is that apt-get does not know that, probably because the
package-metadata is missing the information. The expected behavior here
is that "sudo apt-get install -y chromium-browser" does also upgrade
libnss3 when the libnss3 version currently installed is not enough to
run chromium-browser. Or to have it report an error saying something
like "your system must be updated before you can install this".

My understanding is that this requirement is not recorded in the
chromium-browser package metadata, so when an user tries to install the
package, the apt-get fails to pull in the correct version of libnss3,
leading to a broken package being installed.

> This is not a bug in chromium or libnss itself.

Agree. The bug in in the chromium-browser package metadata which does
not record the minimal libnss3 version necessary correctly, leading to
apt-get believing that "what was initially installed" is sufficient even
though it is not.

> A half-updated system is in an inconstistent state, and will
> result in undefined behaviours like this crash.

1. The system should be in a consistent state when just being
   freshly installed. If it is not, then the official
   installation image of the distribution is broken.
   There is no updating during the installation process nor
   any administrative commands being forcibly aborted
   afterwards.
2. If apt-get install  brings the system into an
   inconsistent state, then the  (or one of its
   dependencies) has broken or incomplete metadata which
   should get fixed. In the case of this bug the
   incomplete/broken metadata is missing "minimal version"
   for libnss3 in the chromium-browser package dependencies.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1821403

Title:
  chromium browser crash on fresh offline system install

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Steps to reproduce (and also what I expected and what happened):

  1. Disconnect computer from Internet
  2. Install Ubuntu (complete with reboot at the end).
  3. After running the (freshly installed) system, connect it to Internet
 and open a terminal and follow with the session outlined below. Enter
 commands on lines starting with "$" into the terminal. Things on lines
 starting with "//" are my comments and/or descriptions of what is
 expected output of the preceding command.

  $ sudo apt-get update
  // you should get the normal apt-get update output with no errors
  $ sudo apt-get install -y chromium-browser
  // you should get the normal apt-get install output here with no errors
  $ chromium-browser
  // expected result is to have the browser running and possibly some harmless
  // warnings below the "$ chromium-browser" line. What actually happens instead
  // is this:
  Fontconfig warning: "/etc/fonts/fonts.conf", line 146: blank doesn't take any 
effect anymore. please remove it from your fonts.conf
  [2805:2844:0322/144827.306513:FATAL:nss_util.cc(631)] 
NSS_VersionCheck("3.26") failed. NSS >= 3.26 is required. Please upgrade to the 
latest NSS, and if you still get this error, contact your distribution 
maintainer.
  Aborted (core dumped)
  // I believe that the problem is that the package "chromium-browser"
  // is either missing dependency on "libnss3-nssdb" or broken dependency
  // on "libnss3" (missing version number). To see, why, continue with:
  $ sudo apt-get install -y libnss3
  // What I got on the terminal myself follows (with some comments)
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
libnss3-nssdb
  // This is why I said the missing dependency might be "libnss3-nssdb"
  // Here apt-get is telling me that "libnss3-nssdb" is going to be
  // installed.
  The following packages will be upgraded:
libnss3 libnss3-nssdb
  2 upgraded, 0 newly installed, 0 to remove and 452 not upgraded.
  Need to get 1,135 kB of archives.
  After this operation, 2,048 B of additional disk space will be used.
  // I didn't use "-y" on my command line so apt-get asked for permission.
  // You might be missing the line below if you follow the session
  // exactly. I included the rest of apt-get output to show you what
  // exactly got installed by the command.
  Do you want to continue? [Y/n] 
  Get:1 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main libnss3-nssdb 
all 2:3.28.4-0ubuntu0.14.04.5 [10.6 kB]

[Desktop-packages] [Bug 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

[Sami Pietila]

Now dist-upgrade found that kernel. I can confirm, with this kernel
rfkill reports the device unblocked.

ID TYPE  DEVICE SOFT  HARD
 0 wlan  ideapad_wlan  unblocked unblocked
 1 bluetooth ideapad_bluetooth unblocked unblocked
 3 wlan  phy0  unblocked unblocked
 4 bluetooth hci0  unblocked unblocked

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

Title:
  Qualcomm Atheros QCA9377 wireless does not work

Status in linux package in Ubuntu:
  Fix Committed
Status in network-manager package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in network-manager source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Fix Committed
Status in network-manager source package in Cosmic:
  Invalid

Bug description:
  === SRU Justification ===
  [Impact] 
  Lenovo ideapad 530S-14ARR Wifi rfkill hard blocked

  [Fix]
  The platform in question doesn't have hardware RF switch, so quirk it
  off.
   
  [Test]
  User confirm it fixes the issue.

  [Regression Potential]
  Minimal. This fix is limited to one specific platform.

  === Original Bug Report ===
  I have Lenovo 530s laptop with Qualcomm Atheros QCA9377 802.11ac Wireless 
Network Adapter (rev 31).

  The menu shows that wireless is off. Turning on the wireless from the
  menu does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  1 11:42:34 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY 
 READONLY  DBUS-PATH   ACTIVE  DEVICE   
STATE  ACTIVE-PATH  SLAVE
   Wired connection 1  ada277fe-966d-33ff-aba2-8ba32d6ce5a9  ethernet  
155143  pe  1. maaliskuuta 2019 11.42.13  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/1  yes enx00e04c704f68  
activated  /org/freedesktop/NetworkManager/ActiveConnection/11  --
   virbr0  dc46fe89-5b22-438a-85d5-37be48a077ea  bridge
155143  pe  1. maaliskuuta 2019 11.42.13  no   0
 no/org/freedesktop/NetworkManager/Settings/2  yes virbr0   
activated  /org/freedesktop/NetworkManager/ActiveConnection/1   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sami   1315 F pulseaudio
   /dev/snd/controlC0:  sami   1315 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-02-20 (11 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IpRoute:
   default via 130.232.69.254 dev enx00e04c704f68 proto dhcp metric 100
   130.232.69.0/24 dev enx00e04c704f68 proto kernel scope link src 
130.232.69.176 metric 100
   169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MachineType: LENOVO 81H1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1.1
  PackageArchitecture: amd64
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=a6aaac69-de44-4491-bfb7-0e57c9ff25cf ro rootflags=subvol=@ quiet 
splash 

[Desktop-packages] [Bug 1455097] Re: /etc/pm/sleep.d/ is no more processed

[Balint Reczey]

Verified 1.1ubuntu1.18.04.7~16.04.2 on Xenial:

ubuntu@ip-172-31-9-2:~$ dpkg -l  unattended-upgrades  | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.2 all  automatic 
installation of security upgrades


ubuntu@ip-172-31-9-2:~$ sudo service apt-daily-upgrade start &  tail -f 
/var/log/unattended-upgrades/unattended-upgrades.log
[2] 13368
2019-04-09 16:11:45,975 INFO Initial blacklisted packages: 
2019-04-09 16:11:45,975 INFO Initial whitelisted packages: 
2019-04-09 16:11:45,976 INFO Starting unattended upgrades script
2019-04-09 16:11:45,976 INFO Allowed origins are: o=Ubuntu,a=xenial, 
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates
2019-04-09 16:13:06,974 INFO Initial blacklisted packages: 
2019-04-09 16:13:06,974 INFO Initial whitelisted packages: 
2019-04-09 16:13:06,974 INFO Starting unattended upgrades script
2019-04-09 16:13:06,974 INFO Allowed origins are: o=Ubuntu,a=xenial, 
o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates
2019-04-09 16:13:11,782 INFO Packages that will be upgraded: apt 
apt-transport-https apt-utils busybox-initramfs busybox-static cloud-init 
distro-info-data file grub-common grub-legacy-ec2 grub-pc grub-pc-bin 
grub2-common libapt-inst2.0 libapt-pkg5.0 libmagic1 libpam-systemd 
libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 libsystemd0 
libudev1 linux-aws linux-headers-aws linux-image-aws ntfs-3g policykit-1 
rsyslog snapd systemd systemd-sysv ubuntu-core-launcher udev wget
2019-04-09 16:13:11,782 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2019-04-09 16:13:17,835 WARNING SIGTERM received, will stop
2019-04-09 16:13:18,514 WARNING SIGNAL received, stopping

... connection lost.

After resume:
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-aws-headers-4.4.0-1079 linux-headers-4.4.0-1079-aws 
linux-image-4.4.0-1079-aws linux-modules-4.4.0-1079-aws
The following packages will be upgraded:
  apt apt-transport-https apt-utils busybox-initramfs busybox-static cloud-init 
file grub-common grub-legacy-ec2 grub-pc grub-pc-bin grub2-common libapt-inst2.0
  libapt-pkg5.0 liblxc1 libmagic1 libpam-systemd libpolkit-agent-1-0 
libpolkit-backend-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 linux-aws 
linux-headers-aws
  linux-image-aws login lxc-common ntfs-3g passwd policykit-1 python-apt-common 
python3-apt rsyslog snapd systemd systemd-sysv ubuntu-core-launcher udev uidmap 
wget
40 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 15.9 MB/56.1 MB of archives.
After this operation, 118 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
ubuntu@ip-172-31-9-2:~$ journalctl -a
Apr 09 16:13:17 ip-172-31-9-2 systemd[1]: Reached target Sleep.
Apr 09 16:13:17 ip-172-31-9-2 systemd[1]: Starting Hibernate...
Apr 09 16:13:17 ip-172-31-9-2 kernel: PM: Hibernation mode set to 'platform'
Apr 09 16:13:19 ip-172-31-9-2 sudo[13368]: pam_unix(sudo:session): session 
closed for user root
Apr 09 16:13:19 ip-172-31-9-2 systemd[1]: Started Daily apt upgrade and clean 
activities.
Apr 09 16:13:19 ip-172-31-9-2 systemd-sleep[13502]: Suspending system...
Apr 09 16:15:58 ip-172-31-9-2 kernel: PM: Syncing filesystems ... done.
Apr 09 16:15:58 ip-172-31-9-2 kernel: Freezing user space processes ... 
(elapsed 0.001 seconds) done.
Apr 09 16:15:58 ip-172-31-9-2 kernel: PM: Marking nosave pages: [mem 
0x-0x0fff]
Apr 09 16:15:58 ip-172-31-9-2 kernel: PM: Marking nosave pages: [mem 
0x0009e000-0x000f]
Apr 09 16:15:58 ip-172-31-9-2 kernel: PM: Basic memory bitmaps created
...

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1455097

Title:
  /etc/pm/sleep.d/ is no more processed

Status in aiccu package in Ubuntu:
  Invalid
Status in ceph package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in ifplugd package in Ubuntu:
  New
Status in lizardfs package in Ubuntu:
  New
Status in oss4 package in Ubuntu:
  New
Status in pm-utils package in Ubuntu:
  Won't Fix
Status in toshset package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed

Bug description:
  [Impact 

[Desktop-packages] [Bug 1823573] Re: Bluetooth headset not available as output device

[Potet]

I can't seem to figure out how to boot to an older kernel on this
laptop. Shift and Escape does noting, while the menus opened by
F-buttons fail to give advanced boot settings. It's all within the UEFI
safety net (which I kind of appreciate after years of BIOS trouble).

I know I have old kernel versions installed (if dpkg --list | grep
linux-image is anything to go by).

If it's any help, pavucontrol also fails to detect the headset, while
"bluetoothctl" returns "Agent registered // [Beoplay H8]#". So given
that pavucontrol is completely separate from Gnome control center, this
should not be a GUI problem?

I'm sorry for not being more helpful!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1823573

Title:
  Bluetooth headset not available as output device

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Connecting my Bluetooth headset (Beoplay H8) appears to be working,
  and everything looks correct in the Bluetooth settings: However, the
  headset is not listed under "Output devices" in the sound menu after
  connecting, and all sounds are channeled through the built-in
  speakers.

  Media buttons on the headset are also rendered useless, not that there
  would be much use for them without sound anyways. Still worth noting,
  as everything including media buttons worked perfectly in 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stein  2603 F pulseaudio
   /dev/snd/pcmC0D0c:   stein  2603 F...m pulseaudio
   /dev/snd/pcmC0D0p:   stein  2603 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 23:00:38 2019
  InstallationDate: Installed on 2018-05-09 (332 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to disco on 2019-04-03 (4 days ago)
  dmi.bios.date: 10/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3PCN16WW(V2.00)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad 510S-13IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 510S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3PCN16WW(V2.00):bd10/14/2016:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80V0
  dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB
  dmi.product.version: Lenovo ideapad 510S-13IKB
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1822394] Re: [Dell XPS 15 9575] laptop keyboard & touchpad not working at gdm screen after boot

[Phusho]

Same problem Precision 5530 2-in-1 with 1.4.8 bios. In my case touchpad
is always working, keyboard will sometime came after 15-20 seconds.
Closing and opening lid will fix problem. Also if you enter password
with on screen keyboard (touchscreen) and get to gnome keyboard is
working again. Ubuntu 18.04 kernel 4.18, 4.19, 4.20 and 5

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

Title:
  [Dell XPS 15 9575] laptop keyboard & touchpad not working at gdm
  screen after boot

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see 
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered 
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1822775] Re: Different input sources per window not work

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: New => Fix Released

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

Title:
  Different input sources per window not work

Status in gnome-control-center:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 19.04

  The option to apply different input source for each window doesn't
  work (it automatically reset itself)

  However, I manually change org.gnome.desktop.input-sources.per-window
  and it works.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1821870] Re: gnome-shell segfault libmutter-clutter-2

[Vincenzo Di Somma]

https://errors.ubuntu.com/oops/9f40d39c-5948-11e9-a557-fa163ee63de6

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

Title:
  gnome-shell segfault  libmutter-clutter-2

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Gnome Shell restarts multiple times a day, after the crash I see this
  error in dmesg:

  [195984.712376] gnome-shell[5769]: segfault at 0 ip 7f662716e021
  sp 7fffbf225760 error 4 in libmutter-
  clutter-2.so[7f66270ee000+161000]

  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  gnome-shell:
Installed: 3.28.3-0ubuntu0.18.04.4
Candidate: 3.28.3-0ubuntu0.18.04.4

  libmutter-2-0:
Installed: 3.28.3-2~ubuntu18.04.2
Candidate: 3.28.3-2~ubuntu18.04.2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823148] Re: eog crashed with SIGSEGV in g_mutex_lock()

[Laurent Bonnaud]

Thanks *a lot* for the fix!

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

Title:
  eog crashed with SIGSEGV in g_mutex_lock()

Status in eog package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  to reproduce this bug:

   - in eog load an image from a directory that contains several images
   - press F5

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: eog 3.32.0-1
  Uname: Linux 5.0.6-050006-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr  4 11:41:28 2019
  ExecutablePath: /usr/bin/eog
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: eog P1000443.jpg
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f53db0ce945 :   lock xadd 
%eax,(%rdi)
   PC (0x7f53db0ce945) ok
   source "%eax" ok
   destination "(%rdi)" (0x7575757575757575) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: eog
  StacktraceTop:
   g_mutex_lock (mutex=mutex@entry=0x7575757575757575) at 
../../../glib/gthread-posix.c:1354
   g_source_destroy_internal (source=0x5611bb416f10, 
context=0x7575757575757575, have_lock=0) at ../../../glib/gmain.c:1219
   g_source_destroy (source=) at ../../../glib/gmain.c:1287
   slideshow_clear_timeout (window=window@entry=0x5611bb1637e0 [EogWindow]) at 
../src/eog-window.c:1827
   slideshow_set_timeout (window=window@entry=0x5611bb1637e0 [EogWindow]) at 
../src/eog-window.c:1840
  Title: eog crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout kvm lpadmin lxd plugdev sambashare staff
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1808874] Re: nvidia-detector doesn't seem to detect nvidia

[Alberto Milone]

note: I think, in your case, the output of nvidia-detector is correct,
since you don't seem to have an obsolete driver installed. Also, the
list of obsolete drivers hasn't been updated in a long time (LP:
#1682291), and we have managed driver migrations using transitional
packages.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1808874

Title:
  nvidia-detector doesn't seem to detect nvidia

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  bdmurray@flash:~$ grep nvidia /proc/modules 
  nvidia_uvm 757760 0 - Live 0x (POE)
  nvidia_drm 40960 1 - Live 0x (POE)
  nvidia_modeset 1110016 3 nvidia_drm, Live 0x (POE)
  nvidia 14360576 84 nvidia_uvm,nvidia_modeset, Live 0x (POE)
  drm_kms_helper 172032 1 nvidia_drm, Live 0x
  drm 401408 4 nvidia_drm,drm_kms_helper, Live 0x
  ipmi_msghandler 53248 2 nvidia,ipmi_devintf, Live 0x
  bdmurray@flash:~$ nvidia-detector
  none
  bdmurray@flash:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1808874] Re: nvidia-detector doesn't seem to detect nvidia

[Alberto Milone]

>From what I remember, nvidia-detector was never meant to detect anything
other than obsolete nvidia drivers. It is, or was, only used by the
nvidia-common debconf script.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1808874

Title:
  nvidia-detector doesn't seem to detect nvidia

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  bdmurray@flash:~$ grep nvidia /proc/modules 
  nvidia_uvm 757760 0 - Live 0x (POE)
  nvidia_drm 40960 1 - Live 0x (POE)
  nvidia_modeset 1110016 3 nvidia_drm, Live 0x (POE)
  nvidia 14360576 84 nvidia_uvm,nvidia_modeset, Live 0x (POE)
  drm_kms_helper 172032 1 nvidia_drm, Live 0x
  drm 401408 4 nvidia_drm,drm_kms_helper, Live 0x
  ipmi_msghandler 53248 2 nvidia,ipmi_devintf, Live 0x
  bdmurray@flash:~$ nvidia-detector
  none
  bdmurray@flash:~$ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1682291] Re: obsolete drivers list may be out of date

[Alberto Milone]

I wrote an explanation of the current state of this in LP: #1808874

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1682291

Title:
  obsolete drivers list may be out of date

Status in ubuntu-drivers-common package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  ubuntu-drivers-common provides a file named obsolete which is
  presumably a list of obsolete nvidia drivers. It doesn't seem to have
  been updated recently:

   $ ls -lh /usr/share/ubuntu-drivers-common/obsolete
  -rw-r--r-- 1 root root 162 Jun 24  2011 
/usr/share/ubuntu-drivers-common/obsolete
  [  3:30PM 10459 ]  [ bdmurray@impulse:/tmp/dist-upgrader ]
   $ cat /usr/share/ubuntu-drivers-common/obsolete
  nvidia-glx
  nvidia-glx-new
  nvidia-glx-legacy
  nvidia-glx-envy
  nvidia-glx-new-envy
  nvidia-glx-legacy-envy
  nvidia-glx-177
  nvidia-glx-71
  nvidia-glx-190
  nvidia-glx-195

  Does it in fact need updating?

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1822513] Re: [regression] gnome-shell aspect ratio doesn't rotate with the rest of the screen

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.32.0-1ubuntu2

---
mutter (3.32.0-1ubuntu2) disco; urgency=medium

  * debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't invert the screen size when rotation is enabled (LP: #1822513)
- Remove unneeded cleanup changes
- Use xcb checked function to set scaling to catch errors
- Update screen size only after monitors modes have been derived
  (LP: #1822616)
- Trigger a monitors rebuild only if scale has changed (LP: #1823485)
- Only update UI scaling when output scaling is enabled (LP: #1822478)

 -- Marco Trevisan (Treviño)   Wed, 03 Apr 2019
19:19:59 -0400

** Changed in: mutter (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [regression] gnome-shell aspect ratio doesn't rotate with the rest of
  the screen

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  I'm testing 19.04 on an Acer-One S1003. An interesting quirk of that
  tablet is that the default screen orientation is portrait (as can be
  seen in BIOS setup, grub etc.)

  Ubuntu 19.04 support screen rotation out of the box. But after a
  recent update, the landscape mode is broken.

  In landscape, only the left hand portion the screen displays an image.
  The right hand part is black.

  The part that's shown is about as wide as the screen would be in
  portrait orientation.

  Another quirk is that landscape screenshots (taken with printscreen) have a 
portrait size, with some garbage at the bottom.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  GsettingsChanges:
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
  Package: mutter
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.32.0-1ubuntu2

---
mutter (3.32.0-1ubuntu2) disco; urgency=medium

  * debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't invert the screen size when rotation is enabled (LP: #1822513)
- Remove unneeded cleanup changes
- Use xcb checked function to set scaling to catch errors
- Update screen size only after monitors modes have been derived
  (LP: #1822616)
- Trigger a monitors rebuild only if scale has changed (LP: #1823485)
- Only update UI scaling when output scaling is enabled (LP: #1822478)

 -- Marco Trevisan (Treviño)   Wed, 03 Apr 2019
19:19:59 -0400

** Changed in: mutter (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  [regression][nvidia] All on screen text is tiny. Icons are normal size
  but text is nearly unreadable.

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix
Status in gnome-shell source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Fix Released
Status in nvidia-graphics-drivers-418 source package in Disco:
  Won't Fix

Bug description:
  Recently upgraded to Disco beta.

  Running a 1080p screen at 100% scaling.

  uname -a  :
  Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  Graphics card : GeForce GT 710/PCIe/SSE2
  Drivers version:  Nvidia-Driver-418

  
  Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct 
package to log it against) or an "Idiot User" issue. As I've upgraded this 
system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean 
install between upgrades.

  When I reboot, all on screen text is tiny. Icons are normal size but text is 
nearly unreadable. This also effects any text input boxes (i.e. user password)
  Text in "Show Applications" screen is also effected.

  *Workaroud*

  Only work around for the desktop is to go in to "Settings" then
  "Devices" then Adjust the scaling to 200%, hit Apply, then press
  "Revert Changes", this resets the scaling to normal.

  This does not fix the scaling in the "Show Applications" screen.

  Attached images in Scaling_Issues.zip :
  Image of text scaling after reboot : Scaling_Small.png
  Image after the "workaround" to show how it should look like: 
Scaling_Normal.png
  Image of "Show Applications" screen which is still effected : 
Applications_Small.png

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Sun Mar 31 16:00:21 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 
'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-09 (264 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1822775] Re: Different input sources per window not work

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:3.32.1-1ubuntu3

---
gnome-control-center (1:3.32.1-1ubuntu3) disco; urgency=medium

  * debian/patches/0001-region-Fix-input-source-options-not-being-applied.patch:
- Fix input sources per-window setting not being applied (LP: #1822775)

 -- Robert Ancell   Tue, 09 Apr 2019
14:27:07 +1200

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Different input sources per window not work

Status in gnome-control-center:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 19.04

  The option to apply different input source for each window doesn't
  work (it automatically reset itself)

  However, I manually change org.gnome.desktop.input-sources.per-window
  and it works.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823485] Re: X11: switching integer scaling values when fractional is enabled doesn't always work

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.32.0-1ubuntu2

---
mutter (3.32.0-1ubuntu2) disco; urgency=medium

  * debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't invert the screen size when rotation is enabled (LP: #1822513)
- Remove unneeded cleanup changes
- Use xcb checked function to set scaling to catch errors
- Update screen size only after monitors modes have been derived
  (LP: #1822616)
- Trigger a monitors rebuild only if scale has changed (LP: #1823485)
- Only update UI scaling when output scaling is enabled (LP: #1822478)

 -- Marco Trevisan (Treviño)   Wed, 03 Apr 2019
19:19:59 -0400

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

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

Title:
  X11: switching integer scaling values when fractional is enabled
  doesn't always work

Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  - Enable fractional scaling with:
   - gsettings set org.gnome.mutter experimental-features 
"['x11-randr-fractional-scaling']"

  From GNOME control center:
   - Say you're at 100%, switch to 200%
   - Or you're at 200% and switch to 100%.

  This switch might need two "apply" activations.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_sc

[Launchpad Bug Tracker]

This bug was fixed in the package mutter - 3.32.0-1ubuntu2

---
mutter (3.32.0-1ubuntu2) disco; urgency=medium

  * debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't invert the screen size when rotation is enabled (LP: #1822513)
- Remove unneeded cleanup changes
- Use xcb checked function to set scaling to catch errors
- Update screen size only after monitors modes have been derived
  (LP: #1822616)
- Trigger a monitors rebuild only if scale has changed (LP: #1823485)
- Only update UI scaling when output scaling is enabled (LP: #1822478)

 -- Marco Trevisan (Treviño)   Wed, 03 Apr 2019
19:19:59 -0400

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

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

Title:
  [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT
  "assertion failed: (width > 0 && height > 0 && scale > 0)" in
  meta_monitor_manager_xrandr_update_screen_size

Status in budgie-desktop package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-410 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix

Bug description:
  https://errors.ubuntu.com/problem/de2c123796506b10cd9d03070c91b581d7c6ae0c

  
  WORKAROUNDS

  Don't use kernel parameter nvidia-drm.modeset=1

  - or -

  Before trying to log in:

  1. Ctrl+Alt+F4, log in to VT4 and run:

 sudo Xorg :4 vt4

  2. Ctrl+Alt+F1, wait for the log screen to reappear, then log in
  normally.

  
  ORIGINAL DESCRIPTION

  I am unable to use the NVIDIA drivers Ubuntu Budgie installed with 3
  vertical displays. I changed to the X.org driver and rebooted. This
  error popped up on reboot. And now only one display is working. This
  one display is only working in landscape instead of portrait mode.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: budgie-core 10.5-0ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Apr  1 09:16:50 2019
  ExecutablePath: /usr/bin/budgie-wm
  InstallationDate: Installed on 2019-01-10 (80 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725.1)
  ProcCmdline: budgie-wm
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: budgie-desktop
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
  Title: budgie-wm crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to disco on 2019-03-25 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823664] Re: The touch screen malfunctions and moves the file.

[Sebastien Bacher]

Thank you for the video. Is the issue specific to nautilus or do you see
it if you use a file selector in e.g gedit or eog? Does it happen in
nautilus icons view or only listmode?

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

Title:
  The touch screen malfunctions and moves the file.

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell Inspiron 7559 4k touch screen notebook.
  Scrolls initially but does not scroll next.
  Double-clicking does not work properly.
  Subsequent scrolling moves files or directories.

  version 3.32.0-stable

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823148] Re: eog crashed with SIGSEGV in g_mutex_lock()

[Launchpad Bug Tracker]

This bug was fixed in the package eog - 3.32.0-2

---
eog (3.32.0-2) experimental; urgency=medium

  * d/p/EogWindow-Don-t-unref-timer-sources-before-destroying-the.patch:
- Don't unref timer sources before destroying them.
  Resolves a segfault in slideshow mode (lp: #1823148)


 -- Sebastien Bacher   Mon, 08 Apr 2019 10:49:46 +0200

** Changed in: eog (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  eog crashed with SIGSEGV in g_mutex_lock()

Status in eog package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  to reproduce this bug:

   - in eog load an image from a directory that contains several images
   - press F5

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: eog 3.32.0-1
  Uname: Linux 5.0.6-050006-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr  4 11:41:28 2019
  ExecutablePath: /usr/bin/eog
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcCmdline: eog P1000443.jpg
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f53db0ce945 :   lock xadd 
%eax,(%rdi)
   PC (0x7f53db0ce945) ok
   source "%eax" ok
   destination "(%rdi)" (0x7575757575757575) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: eog
  StacktraceTop:
   g_mutex_lock (mutex=mutex@entry=0x7575757575757575) at 
../../../glib/gthread-posix.c:1354
   g_source_destroy_internal (source=0x5611bb416f10, 
context=0x7575757575757575, have_lock=0) at ../../../glib/gmain.c:1219
   g_source_destroy (source=) at ../../../glib/gmain.c:1287
   slideshow_clear_timeout (window=window@entry=0x5611bb1637e0 [EogWindow]) at 
../src/eog-window.c:1827
   slideshow_set_timeout (window=window@entry=0x5611bb1637e0 [EogWindow]) at 
../src/eog-window.c:1840
  Title: eog crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout kvm lpadmin lxd plugdev sambashare staff
  separator:

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823175] Re: Battery status shows "Estimating..." when fully charged

[Iain Lane]

** No longer affects: upower (Ubuntu)

** No longer affects: upower (Ubuntu Bionic)

** No longer affects: upower (Ubuntu Cosmic)

** No longer affects: upower (Ubuntu Disco)

** No longer affects: gnome-shell (Ubuntu Bionic)

** No longer affects: gnome-shell (Ubuntu Cosmic)

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

Title:
  Battery status shows "Estimating..." when fully charged

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Disco:
  Fix Released

Bug description:
  My battery is fully charged and it shows 100%. When it's connected to 
charger, Battery symbol changes to battery-missing-symbol. It also shows 
"Estimating..." for time remaining.
  I'm using "Asus VivoBook x510uf"
  My battery status when connected to AC power:

  $ upower -d
  Device: /org/freedesktop/UPower/devices/line_power_AC0
    native-path:  AC0
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
    native-path:  BAT0
    vendor:   ASUSTeK
    model:ASUS Battery
    power supply: yes
    updated:  Thu 04 Apr 2019 05:14:53 PM +0430 (43 seconds ago)
    has history:  yes
    has statistics:   yes
    battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  40.367 Wh
  energy-empty:0 Wh
  energy-full: 40.367 Wh
  energy-full-design:  43.046 Wh
  energy-rate: 0 W
  voltage: 11.55 V
  percentage:  100%
  capacity:93.7764%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
    History (charge):
  15543934180.000   unknown
    History (rate):
  15543934180.000   unknown

  Device: /org/freedesktop/UPower/devices/DisplayDevice
    power supply: yes
    updated:  Thu 04 Apr 2019 08:26:58 PM +0430 (-11482 seconds ago)
    has history:  no
    has statistics:   no
    battery
  present: yes
  state:   unknown
  warning-level:   none
  energy:  40.367 Wh
  energy-full: 40.367 Wh
  energy-rate: 0 W
  percentage:  100%
  icon-name:  'battery-missing-symbolic'

  Daemon:
    daemon-version:  0.99.7
    on-battery:  no
    lid-is-closed:   no
    lid-is-present:  yes
    critical-action: HybridSleep

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 17:04:22 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-03-30 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1822478] Re: [regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable.

[Treviño]

** Changed in: mutter (Ubuntu Disco)
   Status: In Progress => Fix Committed

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

Title:
  [regression][nvidia] All on screen text is tiny. Icons are normal size
  but text is nearly unreadable.

Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Committed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Won't Fix
Status in gnome-shell source package in Disco:
  Invalid
Status in mutter source package in Disco:
  Fix Committed
Status in nvidia-graphics-drivers-418 source package in Disco:
  Won't Fix

Bug description:
  Recently upgraded to Disco beta.

  Running a 1080p screen at 100% scaling.

  uname -a  :
  Linux giga 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 21:58:11 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  Graphics card : GeForce GT 710/PCIe/SSE2
  Drivers version:  Nvidia-Driver-418

  
  Not 100% sure this is a Gnome-Shell issue (Not sure if this is the correct 
package to log it against) or an "Idiot User" issue. As I've upgraded this 
system for the past 3 releases (18.02, 18.10 & 19.04 beta) without a clean 
install between upgrades.

  When I reboot, all on screen text is tiny. Icons are normal size but text is 
nearly unreadable. This also effects any text input boxes (i.e. user password)
  Text in "Show Applications" screen is also effected.

  *Workaroud*

  Only work around for the desktop is to go in to "Settings" then
  "Devices" then Adjust the scaling to 200%, hit Apply, then press
  "Revert Changes", this resets the scaling to normal.

  This does not fix the scaling in the "Show Applications" screen.

  Attached images in Scaling_Issues.zip :
  Image of text scaling after reboot : Scaling_Small.png
  Image after the "workaround" to show how it should look like: 
Scaling_Normal.png
  Image of "Show Applications" screen which is still effected : 
Applications_Small.png

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  Date: Sun Mar 31 16:00:21 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.shell' b'enabled-extensions' b"['ubuntu-d...@ubuntu.com', 
'ubuntu-appindicat...@ubuntu.com', 'openweather-extens...@jenslody.de', 
'desktop-icons@csoriano']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-07-09 (264 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-03-29 (1 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823459] Re: guile-2.2 ftbfs in disco (arm64 only)

[Will Cooke]

** Changed in: guile-2.2 (Ubuntu)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to guile-2.2 in Ubuntu.
https://bugs.launchpad.net/bugs/1823459

Title:
  guile-2.2 ftbfs in disco (arm64 only)

Status in guile-2.2 package in Ubuntu:
  New
Status in guile-2.2 source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417969614/buildlog_ubuntu-disco-
  arm64.guile-2.2_2.2.4+1-1ubuntu2_BUILDING.txt.gz

  Totals for this test run:
  passes: 41515
  failures:   1
  unexpected passes:  0
  expected failures:  10
  unresolved test cases:  577
  untested test cases:1
  unsupported test cases: 1
  errors: 0

  warning: call to primitive-fork while multiple threads are running;
   further behavior unspecified.  See "Processes" in the
   manual, for more information.
  warning: call to primitive-fork while multiple threads are running;
   further behavior unspecified.  See "Processes" in the
   manual, for more information.
  ;;; SSAX warning: Skipping PI: xml

  ;;; SSAX warning: Skipping PI: PI

  ;;; SSAX warning: Skipping PI: PI1

  ;;; SSAX warning: (
   Warning:  DOCTYPE DECL  T   system1  found and skipped)
  ;;; SSAX warning: (
   Warning:  Internal DTD subset is not currently handled )
  ;;; SSAX warning: (
   Warning:  DOCTYPE DECL  T   system1  found and skipped)
  ;;; SSAX warning: Skipping PI: pi

  ;;; SSAX warning: DOCTYPE DECL T system1 found and skipped
  WARNING: (test-suite sxml-xpath): imported module (sxml xpath) overrides core 
binding `filter'
  FAIL: check-guile
  ==
  1 of 1 test failed
  Please report to bug-gu...@gnu.org
  ==
  make[4]: *** [Makefile:1956: check-TESTS] Error 1
  make[4]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[3]: *** [Makefile:2241: check-am] Error 2
  make[3]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[2]: *** [Makefile:1856: check-recursive] Error 1
  make[2]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[1]: *** [Makefile:2243: check] Error 2
  make[1]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823426] Re: librsvg ftbfs in disco (i386 only)

[Will Cooke]

** Changed in: librsvg (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

Title:
  librsvg ftbfs in disco (i386 only)

Status in librsvg package in Ubuntu:
  New
Status in librsvg source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
  disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

 Compiling phf_generator v0.7.23
   Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib
 --extern 
rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib 
--cap-lints allow`
  error[E0428]: the name `U1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5
   |
  2110 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
-
 previous definition of the type `U1024` here
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
^
 `U1024` redefined here
   |
   = note: `U1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `P1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   | - previous definition of the type 
`P1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   | ^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `N1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   - 
previous definition of the type `N1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   ^ 
`N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this 
module

 Compiling quote v0.6.8
   Running `rustc --crate-name quote 
/<>/vendor/quote/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' 
--cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C 
metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib
 --cap-lints allow`
  error: aborting due to 3 previous errors

  For more information about this error, try `rustc --explain E0428`.
  error: Could not compile `typenum`.

  Caused by:
process didn't exit successfully: `rustc --crate-name typenum 
/<>/vendor/typenum/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 
-C extra-filename=-373290d68c8bc9c3 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --cap-lints allow` (exit code: 
1)
  warning: build failed, waiting for other jobs to finish...
  error: build failed
  make[3]: *** [Makefile:1955: 
/<>/target/release/librsvg_internals.a] Error 101
  make[3]: Leaving directory '/<>'
  make[2]: *** [Makefile:1457: all-recursive] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [Makefile:940: all] Error 2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823448] Re: cogl ftbfs in disco (i386 only)

[Sebastien Bacher]

** Changed in: cogl (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  cogl ftbfs in disco (i386 only)

Status in cogl package in Ubuntu:
  New
Status in cogl source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417939758/buildlog_ubuntu-
  disco-i386.cogl_1.22.2-6_BUILDING.txt.gz

  make  check-local
  make[5]: Entering directory '/<>/tests'
  ( cd ./conform && make  test ) || exit $?
  make[6]: Entering directory '/<>/tests/conform'
  Key:
  ok = Test passed
  n/a = Driver is missing a feature required for the test
  FAIL = Unexpected failure
  FIXME = Test failed, but it was an expected failure
  PASS! = Unexpected pass

 Test  GL+FF GL+ARBFP GL+GLSL GL-NPT
  GL3ES2 ES2-NPT

   test_pipeline_user_matrix: ok   ok  ok ok ok 
ok  ok
  test_blend_strings: ok   ok  ok ok ok 
ok  ok
  test_blend: ok   ok  ok ok ok 
ok  ok
test_premult:  FIXMEFIXME   FIXME  FIXME  FIXME  
FIXME   FIXME
   test_path: ok   ok  ok ok ok 
ok  ok
  test_path_clip: ok   ok  ok ok ok 
ok  ok
 test_depth_test: ok   ok  ok ok ok 
ok  ok
 test_color_mask: ok   ok  ok ok ok 
ok  ok
  make[6]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[6]: *** Waiting for unfinished jobs
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
  make[6]: *** wait: No child processes.  Stop.
  make[2]: *** wait: No child processes.  Stop.
  make[2]: *** Waiting for unfinished jobs
  make[5]: *** [Makefile:875: test] Terminated
  make[2]: *** wait: No child processes.  Stop.
  E: Caught signal ‘Terminated’: terminating immediately
  make[4]: *** [Makefile:750: check-am] Terminated
  make: *** [debian/rules:7: build-arch] Terminated
  make[1]: [debian/rules:60: override_dh_auto_test] Terminated (ignored)
  Build killed with signal TERM after 150 minutes of inactivity

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823464] Re: gnome-keyring ftbfs in disco (s390x only)

[Will Cooke]

** Changed in: gnome-keyring (Ubuntu)
 Assignee: (unassigned) => James Henstridge (jamesh)

** Also affects: gnome-keyring (Ubuntu Disco)
   Importance: High
 Assignee: James Henstridge (jamesh)
   Status: New

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

Title:
  gnome-keyring ftbfs in disco (s390x only)

Status in gnome-keyring package in Ubuntu:
  New
Status in gnome-keyring source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417939174/buildlog_ubuntu-disco-s390x
  .gnome-keyring_3.31.91-1ubuntu1_BUILDING.txt.gz

  SKIP: test-pam 1 /pam/auth-no-start 
  SKIP: test-pam 2 /pam/auth-starts-creates-keyring 
  SKIP: test-pam 3 /pam/session-starts-creates-keyring 
  SKIP: test-pam 4 /pam/auth-starts-unlocks-existing 
  SKIP: test-pam 5 /pam/session-starts-unlocks-existing 
  SKIP: test-pam 6 /pam/session-starts-without-auth 
  SKIP: test-pam 7 /pam/auth-running-unlocks-existing 
  SKIP: test-pam 8 /pam/password-changes-running 
  SKIP: test-pam 9 /pam/password-changes-starts 
  SKIP: test-pam 10 /pam/password-change-start-in-session 
  PASS: test-timer 2 /gkm/timer/cancel
  PASS: test-timer 3 /gkm/timer/immediate
  PASS: test-timer 4 /gkm/timer/multiple
  PASS: test-timer 5 /gkm/timer/outstanding
  E: Caught signal ‘Terminated’: terminating immediately
  make[3]: *** wait: No child processes.  Stop.
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
  make[2]: *** wait: No child processes.  Stop.
  make[2]: *** Waiting for unfinished jobs
  make[2]: *** wait: No child processes.  Stop.
  make: *** [debian/rules:7: build-arch] Terminated
  make[1]: *** [debian/rules:30: override_dh_auto_test] Terminated
  make[6]: *** Deleting file 'test-login-keyring.log'
  make[5]: *** [Makefile:6466: check-TESTS] Terminated
  make[6]: *** wait: No child processes.  Stop.
  make[6]: *** Waiting for unfinished jobs
  make[6]: *** wait: No child processes.  Stop.
  make[4]: *** [Makefile:7156: check-am] Terminated
  Build killed with signal TERM after 150 minutes of inactivity

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823440] Re: ubuntu-report ftbfs in disco

[Iain Lane]

** Also affects: ubuntu-report (Ubuntu Disco)
   Importance: High
 Assignee: Didier Roche (didrocks)
   Status: New

** Tags removed: rls-dd-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1823440

Title:
  ubuntu-report ftbfs in disco

Status in ubuntu-report package in Ubuntu:
  New
Status in ubuntu-report source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417924361/buildlog_ubuntu-disco-amd64
  .ubuntu-report_1.4.0_BUILDING.txt.gz

 debian/rules override_dh_missing
  make[1]: Entering directory '/<>'
  dh_missing --fail-missing
  dh_missing: usr/share/gocode/src/github.com/ubuntu/ubuntu-report/go.mod 
exists in debian/tmp but is not installed to anywhere
  dh_missing: usr/share/gocode/src/github.com/ubuntu/ubuntu-report/go.sum 
exists in debian/tmp but is not installed to anywhere
  dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: golang-github-ubuntu-ubuntu-report-dev (2), 
libsysmetrics-dev (3), libsysmetrics1 (1), ubuntu-report (6)
 * dh_installdocs: golang-github-ubuntu-ubuntu-report-dev (0), 
libsysmetrics-dev (0), libsysmetrics1 (0), ubuntu-report (0)
 * dh_installman: golang-github-ubuntu-ubuntu-report-dev (0), 
libsysmetrics-dev (0), libsysmetrics1 (0), ubuntu-report (4)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
  make[1]: *** [debian/rules:39: override_dh_missing] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:14: binary] Error 2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823459] Re: guile-2.2 ftbfs in disco (arm64 only)

[Iain Lane]

** Also affects: guile-2.2 (Ubuntu Disco)
   Importance: High
 Assignee: Andrea Azzarone (azzar1)
   Status: New

** Tags removed: rls-dd-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to guile-2.2 in Ubuntu.
https://bugs.launchpad.net/bugs/1823459

Title:
  guile-2.2 ftbfs in disco (arm64 only)

Status in guile-2.2 package in Ubuntu:
  New
Status in guile-2.2 source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417969614/buildlog_ubuntu-disco-
  arm64.guile-2.2_2.2.4+1-1ubuntu2_BUILDING.txt.gz

  Totals for this test run:
  passes: 41515
  failures:   1
  unexpected passes:  0
  expected failures:  10
  unresolved test cases:  577
  untested test cases:1
  unsupported test cases: 1
  errors: 0

  warning: call to primitive-fork while multiple threads are running;
   further behavior unspecified.  See "Processes" in the
   manual, for more information.
  warning: call to primitive-fork while multiple threads are running;
   further behavior unspecified.  See "Processes" in the
   manual, for more information.
  ;;; SSAX warning: Skipping PI: xml

  ;;; SSAX warning: Skipping PI: PI

  ;;; SSAX warning: Skipping PI: PI1

  ;;; SSAX warning: (
   Warning:  DOCTYPE DECL  T   system1  found and skipped)
  ;;; SSAX warning: (
   Warning:  Internal DTD subset is not currently handled )
  ;;; SSAX warning: (
   Warning:  DOCTYPE DECL  T   system1  found and skipped)
  ;;; SSAX warning: Skipping PI: pi

  ;;; SSAX warning: DOCTYPE DECL T system1 found and skipped
  WARNING: (test-suite sxml-xpath): imported module (sxml xpath) overrides core 
binding `filter'
  FAIL: check-guile
  ==
  1 of 1 test failed
  Please report to bug-gu...@gnu.org
  ==
  make[4]: *** [Makefile:1956: check-TESTS] Error 1
  make[4]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[3]: *** [Makefile:2241: check-am] Error 2
  make[3]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[2]: *** [Makefile:1856: check-recursive] Error 1
  make[2]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  make[1]: *** [Makefile:2243: check] Error 2
  make[1]: Leaving directory '/<>/guile-2.2-2.2.4+1'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823426] Re: librsvg ftbfs in disco (i386 only)

[Iain Lane]

** Also affects: librsvg (Ubuntu Disco)
   Importance: High
 Assignee: Olivier Tilloy (osomon)
   Status: New

** Tags removed: rls-dd-incoming

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

Title:
  librsvg ftbfs in disco (i386 only)

Status in librsvg package in Ubuntu:
  New
Status in librsvg source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417925231/buildlog_ubuntu-
  disco-i386.librsvg_2.44.10-1_BUILDING.txt.gz

 Compiling phf_generator v0.7.23
   Running `rustc --crate-name phf_generator 
/<>/vendor/phf_generator/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=454a5a2ede7d0e81 
-C extra-filename=-454a5a2ede7d0e81 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
phf_shared=/<>/target/release/deps/libphf_shared-3211ae4bedecc506.rlib
 --extern 
rand=/<>/target/release/deps/librand-bc26f371fdd8f508.rlib 
--cap-lints allow`
  error[E0428]: the name `U1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2112:5
   |
  2110 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
-
 previous definition of the type `U1024` here
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
   | 
^
 `U1024` redefined here
   |
   = note: `U1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `P1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:5
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   | - previous definition of the type 
`P1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   | ^ `P1024` redefined here
   |
   = note: `P1024` must be defined only once in the type namespace of this 
module

  error[E0428]: the name `N1024` is defined multiple times
  --> 
/<>/target/release/build/typenum-44d960740a171e66/out/consts.rs:2113:35
   |
  2111 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   - 
previous definition of the type `N1024` here
  2112 | pub type U1024 = 
UInt, B0>, B0>, 
B0>, B0>, B0>, B0>, B0>, B0>, B0>, B0>;
  2113 | pub type P1024 = PInt; pub type N1024 = NInt;
   |   ^ 
`N1024` redefined here
   |
   = note: `N1024` must be defined only once in the type namespace of this 
module

 Compiling quote v0.6.8
   Running `rustc --crate-name quote 
/<>/vendor/quote/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 --cfg 'feature="default"' 
--cfg 'feature="proc-macro"' --cfg 'feature="proc-macro2"' -C 
metadata=7bcb03a3954c3d99 -C extra-filename=-7bcb03a3954c3d99 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --extern 
proc_macro2=/<>/target/release/deps/libproc_macro2-f0d4dedaba1fcdae.rlib
 --cap-lints allow`
  error: aborting due to 3 previous errors

  For more information about this error, try `rustc --explain E0428`.
  error: Could not compile `typenum`.

  Caused by:
process didn't exit successfully: `rustc --crate-name typenum 
/<>/vendor/typenum/src/lib.rs --color never --crate-type lib 
--emit=dep-info,link -C opt-level=3 -C debuginfo=2 -C metadata=373290d68c8bc9c3 
-C extra-filename=-373290d68c8bc9c3 --out-dir 
/<>/target/release/deps -L 
dependency=/<>/target/release/deps --cap-lints allow` (exit code: 
1)
  warning: build failed, waiting for other jobs to finish...
  error: build failed
  make[3]: *** [Makefile:1955: 
/<>/target/release/librsvg_internals.a] Error 101
  make[3]: Leaving directory '/<>'
  make[2]: *** [Makefile:1457: all-recursive] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [Makefile:940: all] Error 2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823437] Re: shotwell ftbfs in disco

[Iain Lane]

** Also affects: shotwell (Ubuntu Disco)
   Importance: High
 Assignee: Ken VanDine (ken-vandine)
   Status: New

** Tags removed: rls-dd-incoming

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

Title:
  shotwell ftbfs in disco

Status in shotwell package in Ubuntu:
  New
Status in shotwell source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417924359/buildlog_ubuntu-disco-
  amd64.shotwell_0.30.2-0ubuntu1_BUILDING.txt.gz

  multiple vala/glib errors

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823448] Re: cogl ftbfs in disco (i386 only)

[Iain Lane]

** Also affects: cogl (Ubuntu Disco)
   Importance: High
 Assignee: Sebastien Bacher (seb128)
   Status: New

** Tags removed: rls-dd-incoming

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

Title:
  cogl ftbfs in disco (i386 only)

Status in cogl package in Ubuntu:
  New
Status in cogl source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417939758/buildlog_ubuntu-
  disco-i386.cogl_1.22.2-6_BUILDING.txt.gz

  make  check-local
  make[5]: Entering directory '/<>/tests'
  ( cd ./conform && make  test ) || exit $?
  make[6]: Entering directory '/<>/tests/conform'
  Key:
  ok = Test passed
  n/a = Driver is missing a feature required for the test
  FAIL = Unexpected failure
  FIXME = Test failed, but it was an expected failure
  PASS! = Unexpected pass

 Test  GL+FF GL+ARBFP GL+GLSL GL-NPT
  GL3ES2 ES2-NPT

   test_pipeline_user_matrix: ok   ok  ok ok ok 
ok  ok
  test_blend_strings: ok   ok  ok ok ok 
ok  ok
  test_blend: ok   ok  ok ok ok 
ok  ok
test_premult:  FIXMEFIXME   FIXME  FIXME  FIXME  
FIXME   FIXME
   test_path: ok   ok  ok ok ok 
ok  ok
  test_path_clip: ok   ok  ok ok ok 
ok  ok
 test_depth_test: ok   ok  ok ok ok 
ok  ok
 test_color_mask: ok   ok  ok ok ok 
ok  ok
  make[6]: *** wait: No child processes.  Stop.
  make[3]: *** wait: No child processes.  Stop.
  make[6]: *** Waiting for unfinished jobs
  make[3]: *** Waiting for unfinished jobs
  make[3]: *** wait: No child processes.  Stop.
  make[6]: *** wait: No child processes.  Stop.
  make[2]: *** wait: No child processes.  Stop.
  make[2]: *** Waiting for unfinished jobs
  make[5]: *** [Makefile:875: test] Terminated
  make[2]: *** wait: No child processes.  Stop.
  E: Caught signal ‘Terminated’: terminating immediately
  make[4]: *** [Makefile:750: check-am] Terminated
  make: *** [debian/rules:7: build-arch] Terminated
  make[1]: [debian/rules:60: override_dh_auto_test] Terminated (ignored)
  Build killed with signal TERM after 150 minutes of inactivity

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823432] Re: openexr ftbfs in disco (i386 only)

[Will Cooke]

** Changed in: openexr (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  openexr ftbfs in disco (i386 only)

Status in openexr package in Ubuntu:
  New
Status in openexr source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417924506/buildlog_ubuntu-
  disco-i386.openexr_2.2.1-4build1_BUILDING.txt.gz

  compression 7, x sampling 2, y sampling 2: writing reading comparing
  compression 8, x sampling 2, y sampling 2: writing reading comparing
  compression 9, x sampling 2, y sampling 2: writing reading comparing
  random bits
  compression 0, x sampling 1, y sampling 1: writing reading 
comparingIlmImfTest: testCompression.cpp:330: void {anonymous}::writeRead(const 
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const 
Imf_2_2::Array2D&, const char*, int, int, int, int, 
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x], 
comp)' failed.
  FAIL IlmImfTest (exit status: 134)

  
  Testsuite summary for OpenEXR 2.2.1
  
  # TOTAL: 1
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See IlmImfTest/test-suite.log
  
  make[5]: *** [Makefile:966: test-suite.log] Error 1
  make[5]: Leaving directory '/<>/IlmImfTest'
  make[4]: *** [Makefile:1074: check-TESTS] Error 2
  make[4]: Leaving directory '/<>/IlmImfTest'
  make[3]: *** [Makefile:1148: check-am] Error 2
  make[3]: Leaving directory '/<>/IlmImfTest'
  make[2]: *** [Makefile:498: check-recursive] Error 1
  make[2]: Leaving directory '/<>'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
  make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:25: build-arch] Error 2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823435] Re: session-migration ftbfs in disco

[Iain Lane]

** Also affects: session-migration (Ubuntu Disco)
   Importance: High
 Assignee: Didier Roche (didrocks)
   Status: New

** Tags removed: rls-dd-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to session-migration in Ubuntu.
https://bugs.launchpad.net/bugs/1823435

Title:
  session-migration ftbfs in disco

Status in session-migration package in Ubuntu:
  New
Status in session-migration source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417924320/buildlog_ubuntu-disco-amd64
  .session-migration_0.3.3_BUILDING.txt.gz

  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/depend
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/check.dir/DependInfo.cmake 
--color=
  Scanning dependencies of target check
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/build
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  nosetests3
  ...FF
  ==
  FAIL: Test that the migration happens as expected
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
144, in test_migration
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;')
  AssertionError: '10_test.sh;01_test.sh;02_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;'
  - 10_test.sh;01_test.sh;02_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;

  
  ==
  FAIL: Test subsequent runs with a new script
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
225, in test_subsequent_runs_with_new_script
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;')
  AssertionError: '02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;'
  - 02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;

  
  --
  Ran 9 tests in 8.615s

  FAILED (failures=2)
  make[5]: *** [CMakeFiles/check.dir/build.make:60: CMakeFiles/check] Error 1
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[4]: *** [CMakeFiles/Makefile2:76: CMakeFiles/check.dir/all] Error 2
  make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[3]: *** [CMakeFiles/Makefile2:83: CMakeFiles/check.dir/rule] Error 2
  make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[2]: *** [Makefile:167: check] Error 2
  make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  dh_auto_test: cd obj-x86_64-linux-gnu && make -j1 check ARGS\+=-j1 returned 
exit code 2
  make[1]: *** [debian/rules:18: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:10: build] Error 2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823432] Re: openexr ftbfs in disco (i386 only)

[Iain Lane]

** Also affects: openexr (Ubuntu Disco)
   Importance: High
 Assignee: Sebastien Bacher (seb128)
   Status: New

** Tags removed: rls-cc-incoming rls-dd-incoming
** Tags added: rls-cc-notfixing

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

Title:
  openexr ftbfs in disco (i386 only)

Status in openexr package in Ubuntu:
  New
Status in openexr source package in Disco:
  New

Bug description:
  https://launchpadlibrarian.net/417924506/buildlog_ubuntu-
  disco-i386.openexr_2.2.1-4build1_BUILDING.txt.gz

  compression 7, x sampling 2, y sampling 2: writing reading comparing
  compression 8, x sampling 2, y sampling 2: writing reading comparing
  compression 9, x sampling 2, y sampling 2: writing reading comparing
  random bits
  compression 0, x sampling 1, y sampling 1: writing reading 
comparingIlmImfTest: testCompression.cpp:330: void {anonymous}::writeRead(const 
Imf_2_2::Array2D&, const Imf_2_2::Array2D&, const 
Imf_2_2::Array2D&, const char*, int, int, int, int, 
Imf_2_2::Compression, int, int): Assertion `equivalent (pf1[y][x], pf2[y][x], 
comp)' failed.
  FAIL IlmImfTest (exit status: 134)

  
  Testsuite summary for OpenEXR 2.2.1
  
  # TOTAL: 1
  # PASS:  0
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See IlmImfTest/test-suite.log
  
  make[5]: *** [Makefile:966: test-suite.log] Error 1
  make[5]: Leaving directory '/<>/IlmImfTest'
  make[4]: *** [Makefile:1074: check-TESTS] Error 2
  make[4]: Leaving directory '/<>/IlmImfTest'
  make[3]: *** [Makefile:1148: check-am] Error 2
  make[3]: Leaving directory '/<>/IlmImfTest'
  make[2]: *** [Makefile:498: check-recursive] Error 1
  make[2]: Leaving directory '/<>'
  dh_auto_test: make -j4 check VERBOSE=1 returned exit code 2
  make[1]: *** [debian/rules:16: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:25: build-arch] Error 2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823958] [NEW] xetex/xdvipdfmx produce invalid PDFs → update

[Paul Natsuo Kishimoto]

Public bug reported:

Hi,

I ran into an issue similar to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=907784. I have a large document (a Beamer
presentation with more than 100 frames) that I compile using
XeLaTeX/latexmk.

The document compiles without issue, producing a valid PDF. However, if
I add only:

\begin{frame}{Frame title}
\end{frame}

at a certain point, the result is a PDF file that is malformed
(according to evince, pdfinfo, etc.)

Finding the above Debian bug report, I downloaded texlive-
binaries_2018.20181218.49446-1_amd64.deb (from debian testing), and
extracted only the xdvipdfmx executable into ~/.local/bin. With this
executable, my modified file also compiles without error.

I suppose the fix is to update the version of texlive-binaries, or at
least xdvipdfmx, in 18.10.


$ lsb_release -rd && apt-cache policy texlive-binaries 
Description:Ubuntu 18.10
Release:18.10
texlive-binaries:
  Installed: 2018.20180824.48463-1ubuntu0.1
  Candidate: 2018.20180824.48463-1ubuntu0.1
  Version table:
 *** 2018.20180824.48463-1ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 2018.20180824.48463-1 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: texlive-binaries 2018.20180824.48463-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  9 15:16:09 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-10-11 (544 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: texlive-bin
UpgradeStatus: Upgraded to cosmic on 2018-11-11 (148 days ago)

** Affects: texlive-bin (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic wayland-session

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-bin in Ubuntu.
https://bugs.launchpad.net/bugs/1823958

Title:
  xetex/xdvipdfmx produce invalid PDFs → update

Status in texlive-bin package in Ubuntu:
  New

Bug description:
  Hi,

  I ran into an issue similar to https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=907784. I have a large document (a Beamer
  presentation with more than 100 frames) that I compile using
  XeLaTeX/latexmk.

  The document compiles without issue, producing a valid PDF. However,
  if I add only:

  \begin{frame}{Frame title}
  \end{frame}

  at a certain point, the result is a PDF file that is malformed
  (according to evince, pdfinfo, etc.)

  Finding the above Debian bug report, I downloaded texlive-
  binaries_2018.20181218.49446-1_amd64.deb (from debian testing), and
  extracted only the xdvipdfmx executable into ~/.local/bin. With this
  executable, my modified file also compiles without error.

  I suppose the fix is to update the version of texlive-binaries, or at
  least xdvipdfmx, in 18.10.

  
  $ lsb_release -rd && apt-cache policy texlive-binaries 
  Description:Ubuntu 18.10
  Release:18.10
  texlive-binaries:
Installed: 2018.20180824.48463-1ubuntu0.1
Candidate: 2018.20180824.48463-1ubuntu0.1
Version table:
   *** 2018.20180824.48463-1ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2018.20180824.48463-1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: texlive-binaries 2018.20180824.48463-1ubuntu0.1
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  9 15:16:09 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (544 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: texlive-bin
  UpgradeStatus: Upgraded to cosmic on 2018-11-11 (148 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823421] Re: deja-dup ftbfs in disco

[Iain Lane]

** Also affects: deja-dup (Ubuntu Disco)
   Importance: High
   Status: New

** Changed in: deja-dup (Ubuntu Disco)
   Status: New => In Progress

** Changed in: deja-dup (Ubuntu Disco)
 Assignee: (unassigned) => Iain Lane (laney)

** Tags removed: rls-dd-incoming

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1823421

Title:
  deja-dup ftbfs in disco

Status in deja-dup package in Ubuntu:
  In Progress
Status in deja-dup source package in Disco:
  In Progress

Bug description:
  https://launchpadlibrarian.net/417924442/buildlog_ubuntu-disco-amd64
  .deja-dup_38.3-1_BUILDING.txt.gz

  make[1]: Leaving directory '/<>'
 dh_auto_build -O--buildsystem=meson
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v
  [1/96] glib-compile-resources data/resources.vars.xml --sourcedir ../data/ui 
--sourcedir ../data --internal --generate --target data/resources.h
  [2/96] glib-compile-resources data/resources.vars.xml --sourcedir ../data/ui 
--sourcedir ../data --internal --generate --target data/resources.c 
--dependency-file data/resources.c.d
  [3/96] valac -C --debug --pkg gio-2.0 --color=always --directory 
deja-dup/nautilus/248796f@@dirhandling@sta --basedir ../deja-dup/nautilus 
--library dirhandling --header deja-dup/nautilus/dirhandling.h --vapi 
../dirhandling.vapi --pkg=config --pkg=posix --target-glib=2.46 --vapidir 
/<>/vapi --define=HAS_PACKAGEKIT 
/<>/libdeja/DirHandling.vala
  [4/96] valac -C --debug --pkg libsecret-1 --pkg libpeas-1.0 --pkg 
packagekit-glib2 --pkg goa-backend-1.0 --pkg goa-1.0 --pkg gio-unix-2.0 --pkg 
gio-2.0 --color=always --directory libdeja/ccd1814@@deja@sha --basedir 
../libdeja --library deja --header libdeja/deja.h --vapi ../deja.vapi 
--pkg=config --pkg=posix --target-glib=2.46 --vapidir /<>/vapi 
--define=HAS_PACKAGEKIT --pkg=secret --pkg=uriutils ../libdeja/Backend.vala 
../libdeja/BackendAuto.vala ../libdeja/BackendDrive.vala 
../libdeja/BackendFile.vala ../libdeja/BackendGCS.vala 
../libdeja/BackendGOA.vala ../libdeja/BackendLocal.vala 
../libdeja/BackendOpenstack.vala ../libdeja/BackendRackspace.vala 
../libdeja/BackendRemote.vala ../libdeja/BackendS3.vala 
../libdeja/BackendU1.vala ../libdeja/CommonUtils.vala 
../libdeja/DirHandling.vala ../libdeja/FilteredSettings.vala 
../libdeja/Network.vala ../libdeja/Operation.vala 
../libdeja/OperationBackup.vala ../libdeja/OperationFiles.vala 
../libdeja/OperationRestore.vala ../libdeja/OperationStatus.vala 
../libdeja/OperationVerify.vala ../libdeja/RecursiveDelete.vala 
../libdeja/RecursiveMove.vala ../libdeja/RecursiveOp.vala 
../libdeja/ToolPlugin.vala
  FAILED: libdeja/ccd1814@@deja@sha/Backend.c 
libdeja/ccd1814@@deja@sha/BackendAuto.c 
libdeja/ccd1814@@deja@sha/BackendDrive.c 
libdeja/ccd1814@@deja@sha/BackendFile.c libdeja/ccd1814@@deja@sha/BackendGCS.c 
libdeja/ccd1814@@deja@sha/BackendGOA.c libdeja/ccd1814@@deja@sha/BackendLocal.c 
libdeja/ccd1814@@deja@sha/BackendOpenstack.c 
libdeja/ccd1814@@deja@sha/BackendRackspace.c 
libdeja/ccd1814@@deja@sha/BackendRemote.c libdeja/ccd1814@@deja@sha/BackendS3.c 
libdeja/ccd1814@@deja@sha/BackendU1.c libdeja/ccd1814@@deja@sha/CommonUtils.c 
libdeja/ccd1814@@deja@sha/DirHandling.c 
libdeja/ccd1814@@deja@sha/FilteredSettings.c 
libdeja/ccd1814@@deja@sha/Network.c libdeja/ccd1814@@deja@sha/Operation.c 
libdeja/ccd1814@@deja@sha/OperationBackup.c 
libdeja/ccd1814@@deja@sha/OperationFiles.c 
libdeja/ccd1814@@deja@sha/OperationRestore.c 
libdeja/ccd1814@@deja@sha/OperationStatus.c 
libdeja/ccd1814@@deja@sha/OperationVerify.c 
libdeja/ccd1814@@deja@sha/RecursiveDelete.c 
libdeja/ccd1814@@deja@sha/RecursiveMove.c 
libdeja/ccd1814@@deja@sha/RecursiveOp.c libdeja/ccd1814@@deja@sha/ToolPlugin.c 
libdeja/deja.h libdeja/deja.vapi 
  valac -C --debug --pkg libsecret-1 --pkg libpeas-1.0 --pkg packagekit-glib2 
--pkg goa-backend-1.0 --pkg goa-1.0 --pkg gio-unix-2.0 --pkg gio-2.0 
--color=always --directory libdeja/ccd1814@@deja@sha --basedir ../libdeja 
--library deja --header libdeja/deja.h --vapi ../deja.vapi --pkg=config 
--pkg=posix --target-glib=2.46 --vapidir /<>/vapi 
--define=HAS_PACKAGEKIT --pkg=secret --pkg=uriutils ../libdeja/Backend.vala 
../libdeja/BackendAuto.vala ../libdeja/BackendDrive.vala 
../libdeja/BackendFile.vala ../libdeja/BackendGCS.vala 
../libdeja/BackendGOA.vala ../libdeja/BackendLocal.vala 
../libdeja/BackendOpenstack.vala ../libdeja/BackendRackspace.vala 
../libdeja/BackendRemote.vala ../libdeja/BackendS3.vala 
../libdeja/BackendU1.vala ../libdeja/CommonUtils.vala 
../libdeja/DirHandling.vala ../libdeja/FilteredSettings.vala 
../libdeja/Network.vala ../libdeja/Operation.vala 
../libdeja/OperationBackup.vala ../libdeja/OperationFiles.vala 
../libdeja/OperationRestore.vala ../libdeja/OperationStatus.vala 
../libdeja/OperationVerify.vala ../libdeja/RecursiveDelete.vala 
../libdeja/RecursiveMove.vala ../libdeja/RecursiveOp.vala 

[Desktop-packages] [Bug 1823435] Re: session-migration ftbfs in disco

[Launchpad Bug Tracker]

** Branch linked: lp:session-migration

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to session-migration in Ubuntu.
https://bugs.launchpad.net/bugs/1823435

Title:
  session-migration ftbfs in disco

Status in session-migration package in Ubuntu:
  New

Bug description:
  https://launchpadlibrarian.net/417924320/buildlog_ubuntu-disco-amd64
  .session-migration_0.3.3_BUILDING.txt.gz

  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/depend
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/check.dir/DependInfo.cmake 
--color=
  Scanning dependencies of target check
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make -f CMakeFiles/check.dir/build.make CMakeFiles/check.dir/build
  make[5]: Entering directory '/<>/obj-x86_64-linux-gnu'
  nosetests3
  ...FF
  ==
  FAIL: Test that the migration happens as expected
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
144, in test_migration
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;')
  AssertionError: '10_test.sh;01_test.sh;02_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;'
  - 10_test.sh;01_test.sh;02_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;

  
  ==
  FAIL: Test subsequent runs with a new script
  --
  Traceback (most recent call last):
File "/<>/obj-x86_64-linux-gnu/tests/migration_tests.py", line 
225, in test_subsequent_runs_with_new_script
  self.assertEqual(self.config.get('State', 'migrated'), 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;')
  AssertionError: '02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;' != 
'01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;'
  - 02_test.sh;08_testexecute.sh;10_test.sh;01_test.sh;
  + 01_test.sh;02_test.sh;10_test.sh;08_testexecute.sh;

  
  --
  Ran 9 tests in 8.615s

  FAILED (failures=2)
  make[5]: *** [CMakeFiles/check.dir/build.make:60: CMakeFiles/check] Error 1
  make[5]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[4]: *** [CMakeFiles/Makefile2:76: CMakeFiles/check.dir/all] Error 2
  make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[3]: *** [CMakeFiles/Makefile2:83: CMakeFiles/check.dir/rule] Error 2
  make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[2]: *** [Makefile:167: check] Error 2
  make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  dh_auto_test: cd obj-x86_64-linux-gnu && make -j1 check ARGS\+=-j1 returned 
exit code 2
  make[1]: *** [debian/rules:18: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:10: build] Error 2

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1742714] Re: MIR: mesa-vulkan-drivers FFE: install by default

[Didier Roche]

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

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

Title:
  MIR: mesa-vulkan-drivers FFE: install by default

Status in mesa package in Ubuntu:
  Invalid
Status in vulkan-loader package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  MIR mesa-vulkan-drivers:
  - is from mesa, which is already in main
  - maintained just as mesa is, by ubuntu-x-swat

  MIR vulkan-loader:
  https://bugs.launchpad.net/ubuntu/+source/vulkan-loader/+bug/1742711

  FFE:
  - new packages in the default install (mesa-vulkan-drivers, libvulkan1)
    -> no chance of regressing anything

  --

  A Vulkan related bug was filed at
  https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in
  a related note, having mesa-vulkan-drivers moved from Universe to Main
  and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten
  mature and since the OpenGL drivers are installed, it will very
  complimentary.

  Having this available will aid game developers and users who load up a
  Vulkan application and get errors. They may not know to enable
  Universe in their Software Manager and to manually install mesa-
  vulkan-drivers for their video card. They may just load up that Vulkan
  application, find out it doesn't work, and then give up on it. We
  cannot have that for future adoption of the API.

  Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV
  are implementing experimental support for Vulkan. For Ubuntu being a
  leader for the desktop and a base for GNU/Linux gaming, shouldn't it
  be painless for Ubuntu 18.04? Especially since it is a long term
  release for 5 years.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823916] [NEW] package libp11-kit-gnome-keyring (not installed) failed to install/upgrade: próba nadpisania "/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so", który is

[Łukasz Kołodziński]

Public bug reported:

its just error

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: libp11-kit-gnome-keyring (not installed)
ProcVersionSignature: Ubuntu 4.18.0-17.18-lowlatency 4.18.20
Uname: Linux 4.18.0-17-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Tue Apr  9 14:54:48 2019
ErrorMessage: próba nadpisania 
"/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so", który istnieje 
także w pakiecie gnome-keyring-pkcs11:amd64 3.28.2-0ubuntu1
InstallationDate: Installed on 2019-04-07 (2 days ago)
InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.4
SourcePackage: gnome-keyring
Title: package libp11-kit-gnome-keyring (not installed) failed to 
install/upgrade: próba nadpisania 
"/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so", który istnieje 
także w pakiecie gnome-keyring-pkcs11:amd64 3.28.2-0ubuntu1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package cosmic

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

Title:
  package libp11-kit-gnome-keyring (not installed) failed to
  install/upgrade: próba nadpisania "/usr/lib/x86_64-linux-gnu/pkcs11
  /gnome-keyring-pkcs11.so", który istnieje także w pakiecie gnome-
  keyring-pkcs11:amd64 3.28.2-0ubuntu1

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  its just error

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libp11-kit-gnome-keyring (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-17.18-lowlatency 4.18.20
  Uname: Linux 4.18.0-17-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Tue Apr  9 14:54:48 2019
  ErrorMessage: próba nadpisania 
"/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so", który istnieje 
także w pakiecie gnome-keyring-pkcs11:amd64 3.28.2-0ubuntu1
  InstallationDate: Installed on 2019-04-07 (2 days ago)
  InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.4
  SourcePackage: gnome-keyring
  Title: package libp11-kit-gnome-keyring (not installed) failed to 
install/upgrade: próba nadpisania 
"/usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so", który istnieje 
także w pakiecie gnome-keyring-pkcs11:amd64 3.28.2-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1747646] Re: Authentication error with google drive

[Robert C. Reynolds]

I attempted to run a daily backup to supplement the failed backup.
Oddly enough, the program recognized the original backup and attempted
to build on it rather than clearing the volume and starting fresh.  It
did fail with this message:

Traceback (innermost last):
  File "/snap/deja-dup/126/bin/duplicity", line 1560, in 
with_tempdir(main)
  File "/snap/deja-dup/126/bin/duplicity", line 1546, in with_tempdir
fn()
  File "/snap/deja-dup/126/bin/duplicity", line 1398, in main
do_backup(action)
  File "/snap/deja-dup/126/bin/duplicity", line 1528, in do_backup
incremental_backup(sig_chain)
  File "/snap/deja-dup/126/bin/duplicity", line 664, in incremental_backup
bytes_written = dummy_backup(tarblock_iter)
  File "/snap/deja-dup/126/bin/duplicity", line 227, in dummy_backup
while tarblock_iter.next():
  File "/snap/deja-dup/126/lib/python2.7/site-packages/duplicity/diffdir.py", 
line 523, in next
result = self.process(self.input_iter.next())
  File "/snap/deja-dup/126/lib/python2.7/site-packages/duplicity/diffdir.py", 
line 195, in get_delta_iter
for new_path, sig_path in collated:
  File "/snap/deja-dup/126/lib/python2.7/site-packages/duplicity/diffdir.py", 
line 286, in collate2iters
relem2 = riter2.next()
  File "/snap/deja-dup/126/lib/python2.7/site-packages/duplicity/diffdir.py", 
line 354, in combine_path_iters
refresh_triple_list(triple_list)
  File "/snap/deja-dup/126/lib/python2.7/site-packages/duplicity/diffdir.py", 
line 341, in refresh_triple_list
new_triple = get_triple(old_triple[1])
  File "/snap/deja-dup/126/lib/python2.7/site-packages/duplicity/diffdir.py", 
line 327, in get_triple
path = path_iter_list[iter_index].next()
  File "/snap/deja-dup/126/lib/python2.7/site-packages/duplicity/diffdir.py", 
line 239, in sigtar2path_iter
for tarinfo in tf:
  File "/usr/lib/python2.7/tarfile.py", line 2510, in next
tarinfo = self.tarfile.next()
  File "/usr/lib/python2.7/tarfile.py", line 2352, in next
raise ReadError("unexpected end of data")
 ReadError: unexpected end of data

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1747646

Title:
  Authentication error with google drive

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I'm having an issue using deja-dup to back up my laptop to my google
  drive.

  When backing only a small folder (eg: ~/Documents) every thing works fine.
  However when trying to backup my whole home folder (/home/myusername) I get 
an "Invalid credentials" error after 5-10 min.

  The back up seems to start normally and my destination folder starts
  filling with "duplicity-full...difftar.gz" files, but eventually I get
  the Invalid Credentials error.

  
  lsb_release -d
  Fedora release 27 (Twenty Seven)

  rpm -q deja-dup duplicity
  deja-dup-37.1-1.fc27.x86_64
  duplicity-0.7.16-1.fc27.x86_64

  deja-dup.log attached.
  I cannot attach deja-dup.gsettings since i can only join 1 file. Will send if 
needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1747646/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823857] Re: Backport to bionic a patch for improved fractional scaling

[Ubuntu Foundations Team Bug Bot]

The attachment "scaling-displays.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Backport to bionic a patch for improved fractional scaling

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I have been debugging why I do not get "Apply" button in Displays view
  when my primary monitor is on the left of the external monitor, but it
  appears when it is on the right. I traced the problem down to this
  issue and patch:

  https://gitlab.gnome.org/GNOME/mutter/issues/412
  https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/346

  Reading this issue tracker I see that some issues people are reporting
  my be connected to this problem. I would suggest, if possible, that
  this patch is backported to Bionic and its version of gnome-control-
  center.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1747646] Re: Authentication error with google drive

[Robert C. Reynolds]

I did get a full backup completed; however, there are a few details I
need help working through.

Whereas the entire backup will now complete, there are unencryption
errors when the volume is restore tested and there is where the backup
fails.  I apologize that I was unable to screenshot the message but it
is a typical restore test fail due to inability to decrypt the volume
message.

The other issue was relatively easy to mitigate but the file the backup
goes to on Google Drive does not seem to be picked up by Deja-Dup and it
will create a separate file series of the same name parallel to the
existing.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1747646

Title:
  Authentication error with google drive

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I'm having an issue using deja-dup to back up my laptop to my google
  drive.

  When backing only a small folder (eg: ~/Documents) every thing works fine.
  However when trying to backup my whole home folder (/home/myusername) I get 
an "Invalid credentials" error after 5-10 min.

  The back up seems to start normally and my destination folder starts
  filling with "duplicity-full...difftar.gz" files, but eventually I get
  the Invalid Credentials error.

  
  lsb_release -d
  Fedora release 27 (Twenty Seven)

  rpm -q deja-dup duplicity
  deja-dup-37.1-1.fc27.x86_64
  duplicity-0.7.16-1.fc27.x86_64

  deja-dup.log attached.
  I cannot attach deja-dup.gsettings since i can only join 1 file. Will send if 
needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1747646/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1815550] Re: gnome-shell high memory and CPU usage when using zsh and a custom XDG_DESKTOP_DIR="$HOME/"

[Bug Watch Updater]

** Changed in: gnome-shell-extension-desktop-icons
   Status: Unknown => New

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

Title:
  gnome-shell high memory and CPU usage when using zsh and a custom
  XDG_DESKTOP_DIR="$HOME/"

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Disco:
  In Progress

Bug description:
  This *may* be an nvidia-specific problem, but the RSS of gnome-shell
  on my system grows without limit (over a couple of hours it's
  increased past 10G).

  At the same time, gnome-shell appears to become progressively less
  responsive.

  Restarting gnome-shell (via  restart) drops shell RSS down to
  ~400MB and improves system responsiveness a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.30.2-2ubuntu2
  ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 
4.20.0
  Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 13:35:59 2019
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823544] Re: Unreasonable NVIDIA GPU VRAM usage on gnome-shell

[Luca Mastromatteo]

Yes but the amount of time I kept in the first test was not the same, I
just do not have enough time to test

In the first one my PC was up for almost a day unlike the second
scenario where the uptime was just 1h and a couple of minutes

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

Title:
  Unreasonable NVIDIA GPU VRAM usage on gnome-shell

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  GPU: NVIDIA GTX 1060 3GB 
  Ubuntu: 19.04, Kernel Linux luky-pc 5.0.0-8-generic #9-Ubuntu SMP Tue Mar 12 
21:58:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
  NVIDIA driver version: 418.56
  Display settings: BenQ XL2411Z, 144Hz monitor, 1920x1080p 

  I have noticed this strange behavior only on gnome-shell where the overall 
gnome-shell desktop VRAM usage was taking up to 1GB of GPU VRAM which does not 
happen on other desktops, or on Windows, happens after some hours of normal 
desktop usage
  Even the system RAM increases a lot during normal usage, but remains 
acceptable

  This behaviour can be observed by using "nvidia-smi" a tool from the
  NVIDIA proprietary driver

  gnome-shell VRAM usage on a cold start: 139MB, + 9 MB
  X.org VRAM usage on cold start: 48MB + 18MB 
  Total: 214MB

  gnome-shell VRAM usage after some hours of normal usage: 445MB + 83 MB
  X.org VRAM usage after some hours of normal usage: 244MB + 18MB 
  Total: 800MB

  On windows or other desktops the GPU VRAM usage remains the same
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.32.0-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1815550] Re: gnome-shell high memory and CPU usage when using zsh and a custom XDG_DESKTOP_DIR="$HOME/"

[Daniel van Vugt]

** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues 
#104
   https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/104

** Also affects: gnome-shell-extension-desktop-icons via
   https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/104
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-shell high memory and CPU usage when using zsh and a custom
  XDG_DESKTOP_DIR="$HOME/"

Status in gnome-shell-extension-desktop-icons:
  Unknown
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Disco:
  In Progress

Bug description:
  This *may* be an nvidia-specific problem, but the RSS of gnome-shell
  on my system grows without limit (over a couple of hours it's
  increased past 10G).

  At the same time, gnome-shell appears to become progressively less
  responsive.

  Restarting gnome-shell (via  restart) drops shell RSS down to
  ~400MB and improves system responsiveness a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.30.2-2ubuntu2
  ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 
4.20.0
  Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 13:35:59 2019
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1799258] Re: access to dashdock from the lock screen

[Daniel van Vugt]

*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1769383, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1769383
   Ubuntu dock/launcher is shown on the lock screen

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

Title:
  access to dashdock from the lock screen

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I installed the system on a cheap usb. allocated 10 GB. installed the
  dash to dock extension. transferred to the lower position. Here are
  the circumstances: the screen is locked, the panel is visible.
  (sometimes displayed with the original parameters: full length.
  configured else). I managed to remove an item from the panel. Made
  changes on the lock screen !! That is, the lock screen does not
  completely block. u18.10. where is security?

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1799258] Re: access to dashdock from the lock screen

[Sebastien Bacher]

** Package changed: ubuntu-report (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)

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

Title:
  access to dashdock from the lock screen

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  I installed the system on a cheap usb. allocated 10 GB. installed the
  dash to dock extension. transferred to the lower position. Here are
  the circumstances: the screen is locked, the panel is visible.
  (sometimes displayed with the original parameters: full length.
  configured else). I managed to remove an item from the panel. Made
  changes on the lock screen !! That is, the lock screen does not
  completely block. u18.10. where is security?

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823857] Re: Backport to bionic a patch for improved fractional scaling

[Mitar]

I made this patch for myself and it solved the problem.

** Patch added: "scaling-displays.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1823857/+attachment/5254413/+files/scaling-displays.patch

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

Title:
  Backport to bionic a patch for improved fractional scaling

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I have been debugging why I do not get "Apply" button in Displays view
  when my primary monitor is on the left of the external monitor, but it
  appears when it is on the right. I traced the problem down to this
  issue and patch:

  https://gitlab.gnome.org/GNOME/mutter/issues/412
  https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/346

  Reading this issue tracker I see that some issues people are reporting
  my be connected to this problem. I would suggest, if possible, that
  this patch is backported to Bionic and its version of gnome-control-
  center.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1823857] [NEW] Backport to bionic a patch for improved fractional scaling

[Mitar]

Public bug reported:

I have been debugging why I do not get "Apply" button in Displays view
when my primary monitor is on the left of the external monitor, but it
appears when it is on the right. I traced the problem down to this issue
and patch:

https://gitlab.gnome.org/GNOME/mutter/issues/412
https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/346

Reading this issue tracker I see that some issues people are reporting
my be connected to this problem. I would suggest, if possible, that this
patch is backported to Bionic and its version of gnome-control-center.

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

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

Title:
  Backport to bionic a patch for improved fractional scaling

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I have been debugging why I do not get "Apply" button in Displays view
  when my primary monitor is on the left of the external monitor, but it
  appears when it is on the right. I traced the problem down to this
  issue and patch:

  https://gitlab.gnome.org/GNOME/mutter/issues/412
  https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/346

  Reading this issue tracker I see that some issues people are reporting
  my be connected to this problem. I would suggest, if possible, that
  this patch is backported to Bionic and its version of gnome-control-
  center.

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 918489] Re: duplicity allows a new, different passphrase if an archive cache exists

[Yajo]

Although comment 22 is IMHO a duplicity bug, the fact that you can do a
full backup with a new passphrase is, for me, a feature. If somebody had
access to your passphrase, the safe thing to do is to rotate it, do a
full backup, and stick with the new one from there onwards.

There's a problem restoring, but that's another issue.

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

Title:
  duplicity allows a new, different passphrase if an archive cache
  exists

Status in Déjà Dup:
  Fix Released
Status in Duplicity:
  Confirmed
Status in deja-dup package in Ubuntu:
  Fix Released
Status in duplicity package in Ubuntu:
  Triaged
Status in deja-dup source package in Trusty:
  Fix Released
Status in duplicity source package in Trusty:
  Confirmed
Status in deja-dup source package in Xenial:
  Fix Released
Status in duplicity source package in Xenial:
  Confirmed
Status in deja-dup source package in Yakkety:
  Fix Released
Status in duplicity source package in Yakkety:
  Confirmed

Bug description:
  when doing a backup for the first time, dejadup verifies your
  passphrase by having you enter it twice.

  on future incremental backups it doesn't need to do this because
  entering the wrong password will result in the backup failing.

  with the periodic 'full' backups that happen from time to time,
  however, any password will be accepted.

  this can lead to a situation where you accidentally type the wrong
  password once and are left in a situation where you don't know what
  you typed and have no way to get your files (or do another incremental
  backup on top of it).

  i think this is what happened to me recently.

  clearly, the fix is to explicitly verify the passphrase is correct
  when doing a new full backup.  this may be a duplicity bug.

  === Ubuntu deja-dup SRU information ===

  [impact]
  Users may unwittingly re-set their backup password and not be able to restore 
their data.

  [test case]
  - $ deja-dup-preferences # set up a dummy backup
  - $ deja-dup --backup # complete first encrypted full backup
  - $ rename 's/\.2016/\.2000/' /path/to/test/backup/*
  - $ rename 's/\.2016/\.2000/' ~/.cache/deja-dup/*/*
  - $ deja-dup --backup # second backup, enter the wrong password
  - $ deja-dup --restore # try to restore with original password

  [regression potential]
  Should be limited?  The fix is to delete the duplicity cache files, which 
ought to be safe to delete.

  It's possible if a full backup is being resumed, we might delete the
  current progress.  That is a better bug to have than this bug, though.
  A more complicated patch would need to be investigated to prevent
  that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/918489/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1815550] Re: gnome-shell high memory and CPU usage when using zsh and a custom XDG_DESKTOP_DIR="$HOME/"

[Daniel van Vugt]

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Disco)
   Status: Triaged => In Progress

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

Title:
  gnome-shell high memory and CPU usage when using zsh and a custom
  XDG_DESKTOP_DIR="$HOME/"

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  In Progress
Status in gnome-shell-extension-desktop-icons source package in Disco:
  In Progress

Bug description:
  This *may* be an nvidia-specific problem, but the RSS of gnome-shell
  on my system grows without limit (over a couple of hours it's
  increased past 10G).

  At the same time, gnome-shell appears to become progressively less
  responsive.

  Restarting gnome-shell (via  restart) drops shell RSS down to
  ~400MB and improves system responsiveness a bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.30.2-2ubuntu2
  ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 
4.20.0
  Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 12 13:35:59 2019
  DisplayManager: gdm3
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1730071] Re: Application icons appear stretched when using scaling

[Treviño]

Fixed, see upstream issue https://github.com/ubuntu/gnome-shell-
extension-appindicator/issues/158

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Status: Confirmed => In Progress

** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues 
#158
   https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/158

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

Title:
  Application icons appear stretched when using scaling

Status in gnome-shell-extension-appindicator package in Ubuntu:
  In Progress

Bug description:
  The appindicator gnome extension shows the "system tray icons" in the
  upper right corner of the screen. However the icons appear vertically
  stretched. The problem appears to be purely visual, as they still work
  as expected.

  > lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  > apt-cache policy gnome-shell-extension-appindicator
  gnome-shell-extension-appindicator:
Installed: 17.10.1
Candidate: 17.10.1
Version table:
   *** 17.10.1 500
  500 http://gb.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1760447] Re: Indicator of Goldendict (Qt5 software) functions only after returning from screen lock

[Treviño]

*** This bug is a duplicate of bug 1714504 ***
https://bugs.launchpad.net/bugs/1714504

** This bug has been marked a duplicate of bug 1714504
   App indicator is not always displayed

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

Title:
  Indicator of Goldendict (Qt5 software) functions only after returning
  from screen lock

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  Steps:

  1. Install then run goldendict
  3. Its indicator appears, but you cannot drop its menu down
  4. Double-clicking on the indicator icon makes the app disappear and appear 
(that should not happen in an appindicator as it is similar to the old tray 
icon behaviour)
  5. Lock the screen then unlock it
  6. The indicator works fine after that

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell-extension-appindicator 18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 17:09:14 2018
  Dependencies:
   
  InstallationDate: Installed on 2017-10-02 (180 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago)

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp