[Desktop-packages] [Bug 1838208] Re: Wifi stops responding sporadically on lenovo-yoga-720-15ikb

[Kai-Heng Feng]

Can you please still attach dmesg with latest kernel/firmware when the
issue happens?

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

Title:
  Wifi stops responding sporadically on lenovo-yoga-720-15ikb

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I can make this happen by trying to upload a large file using Firefox
  Nightly to https://send.firefox.com/ Within a few seconds (like 10-15)
  my wifi stops responding.

  Restarting network manager via service network-manager restart
  temporarily resolves the issue.

  This issue began appearing a week or so ago -- almost definitely not a
  month ago; my wifi used to be fine previously.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.18.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 14:59:13 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-10-31 (270 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IpRoute:
   default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION   CON-UUID
  CON-PATH   
   wlp1s0  wifi  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  dd-wrt-vap-5g 1  
21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlp1s0  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
   lo  loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.18.0   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asif   1938 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2018-10-31 (276 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80X7
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan wayland-session
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN33WW(V2.05)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 

[Desktop-packages] [Bug 1838208] Re: Wifi stops responding sporadically on lenovo-yoga-720-15ikb

[Kai-Heng Feng]

If restarting network-manager can fix the issue then it's less likely to
be a kernel bug.

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

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

Title:
  Wifi stops responding sporadically on lenovo-yoga-720-15ikb

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I can make this happen by trying to upload a large file using Firefox
  Nightly to https://send.firefox.com/ Within a few seconds (like 10-15)
  my wifi stops responding.

  Restarting network manager via service network-manager restart
  temporarily resolves the issue.

  This issue began appearing a week or so ago -- almost definitely not a
  month ago; my wifi used to be fine previously.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.18.0-1ubuntu5
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 28 14:59:13 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-10-31 (270 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IpRoute:
   default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000 
   192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION   CON-UUID
  CON-PATH   
   wlp1s0  wifi  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  dd-wrt-vap-5g 1  
21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   p2p-dev-wlp1s0  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
   lo  loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.18.0   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  asif   1938 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2018-10-31 (276 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80X7
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic 
root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  Tags:  eoan wayland-session
  Uname: Linux 5.2.0-8-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN33WW(V2.05)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  

[Desktop-packages] [Bug 1840875] [NEW] genaral Swap for errors

[Zaid Kilani]

Public bug reported:

I have problem with my snap packages
I have problem with DPKG being not able to do upgrades
I have problem with my Livepatch since I can't sign in to it

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-59.66-generic 4.15.18
Uname: Linux 4.15.0-59-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Aug 21 07:24:59 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
MachineType: Dell Inc. Inspiron 3521
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-59-generic 
root=UUID=fbe95d05-80c6-41a8-9680-336df596acb7 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 033MX4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A02
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd09/26/2012:svnDellInc.:pnInspiron3521:pvrA02:rvnDellInc.:rn033MX4:rvrA00:cvnDellInc.:ct8:cvrA02:
dmi.product.family: 103C_5335KV
dmi.product.name: Inspiron 3521
dmi.product.version: A02
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu

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

Title:
  genaral Swap for errors

Status in xorg package in Ubuntu:
  New

Bug description:
  I have problem with my snap packages
  I have problem with DPKG being not able to do upgrades
  I have problem with my Livepatch since I can't sign in to it

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-59.66-generic 4.15.18
  Uname: Linux 4.15.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Aug 21 07:24:59 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597]
  MachineType: Dell Inc. Inspiron 3521
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-59-generic 
root=UUID=fbe95d05-80c6-41a8-9680-336df596acb7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 033MX4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A02
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd09/26/2012:svnDellInc.:pnInspiron3521:pvrA02:rvnDellInc.:rn033MX4:rvrA00:cvnDellInc.:ct8:cvrA02:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 3521
  dmi.product.version: A02
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1833197] Re: crashes when creating annotations (Segmentation fault (core dumped))

[Launchpad Bug Tracker]

[Expired for evince (Ubuntu) because there has been no activity for 60
days.]

** Changed in: evince (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  crashes when creating annotations (Segmentation fault (core dumped))

Status in evince package in Ubuntu:
  Expired

Bug description:
  After creating several annotations in a PDF document evince ends up
  crashing with an inespecific segfault terminal output. It happens
  always, but it takes a long time, so it's hard to reproduce, and it
  doesn't always happens in the same place, despite I've tried to hit
  the bug reopening and inserting an annotation in the same place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1833197/+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 1833512] Re: Wifi password dialog popup don't take more the 20 ASCII-encoded characters

[Launchpad Bug Tracker]

[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Wifi password dialog popup don't take more the 20 ASCII-encoded
  characters

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  The max pass-phrase length for a WPA2-PSK, has a limit of 63 ASCII-
  encoded characters

  The password fields, in the dialog to write the pass-phrase for the
  Wifi network you are connecting to, is limiting this to 20 characters.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 20 09:59:57 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-06-19 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.1.1 dev enp0s25 proto dhcp metric 100
   169.254.0.0/16 dev enp0s25 scope link metric 1000
   192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.169 metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH
   enp0s25  ethernet  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  Wired connection 1  
cb8f8bbb-c98f-3fcd-8212-fdf5d6425ab1  
/org/freedesktop/NetworkManager/ActiveConnection/1
   wlp3s0   wifi  disconnected  limited   limited   
/org/freedesktop/NetworkManager/Devices/3  --  --   
 --
   lo   loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.16.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1833512/+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 1840874] [NEW] Mono Runtime error because of bug in LargeArrayBuilder in Mono 5.18

[Timotheus Pokorra]

Public bug reported:

This bug happens in Mono 5.18, in Ubuntu Disco (19.04).
I am using the package 5.18.0.240+dfsg-2ubuntu2.

You can reproduce the bug with the attached test program.
It has been fixed upstream in Mono 5.20, with quite a simple patch.

I got the patch merged into the Debian Mono package:
https://salsa.debian.org/dotnet-team/mono/merge_requests/3

Is there any chance, this patch could be applied to the next Ubuntu
release (19.10), or even Ubuntu Disco (19.04)?

See for more details:
https://bugzilla.redhat.com/show_bug.cgi?id=1704847
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919194

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

** Attachment added: "reproduce the bug with this code"
   
https://bugs.launchpad.net/bugs/1840874/+attachment/5283599/+files/file_1704847.txt

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

Title:
  Mono Runtime error because of bug in LargeArrayBuilder in Mono 5.18

Status in mono package in Ubuntu:
  New

Bug description:
  This bug happens in Mono 5.18, in Ubuntu Disco (19.04).
  I am using the package 5.18.0.240+dfsg-2ubuntu2.

  You can reproduce the bug with the attached test program.
  It has been fixed upstream in Mono 5.20, with quite a simple patch.

  I got the patch merged into the Debian Mono package:
  https://salsa.debian.org/dotnet-team/mono/merge_requests/3

  Is there any chance, this patch could be applied to the next Ubuntu
  release (19.10), or even Ubuntu Disco (19.04)?

  See for more details:
  https://bugzilla.redhat.com/show_bug.cgi?id=1704847
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919194

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1840874/+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 1840185] Re: simple-scan app closes with a big delay

[Robert Ancell]

This is the SANE drivers taking a long time to shutdown. Simple Scan
waits for them to complete, in case there is important things that need
to be done. I don't know which driver takes a long time.

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

Title:
  simple-scan app closes with a big delay

Status in simple-scan package in Ubuntu:
  New

Bug description:
  When I touch closing button I will wait for a while for exiting from this 
program. There are details in my video.
  Information from console:
  ubuntenok@ubuntenok-HP-250-G6-Notebook-PC:~$ simple-scan
  (simple-scan:13544): Gtk-WARNING **: 22:15:55.501: Failed to register client: 
GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register 
client

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: simple-scan 3.33.90-0ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 14 22:45:14 2019
  InstallationDate: Installed on 2019-08-14 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05c8:0233 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP Webcam
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 248a:8514 Maxxter Wireless Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-10-generic 
root=UUID=b1b8960c-e09c-4671-bcc2-1b3bd70c7ed4 ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.52
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832E
  dmi.board.vendor: HP
  dmi.board.version: 26.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.52:bd03/04/2019:svnHP:pnHP250G6NotebookPC:pvrType1ProductConfigId:rvnHP:rn832E:rvr26.35:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN HP 200
  dmi.product.name: HP 250 G6 Notebook PC
  dmi.product.sku: 3DN65ES#ACB
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1840185/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Rohan Paul]

Running the program in Windows gave me a Blue Screen Error.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Hui Wang]

You said the internal mic works well under windows10, so please run this
dump program under windows10, then upload the dump file to launchpad,
maybe we can find some difference from the linux.


** Attachment added: "RtHDDump_V226.zip"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+attachment/5283575/+files/RtHDDump_V226.zip

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 577038] Re: [Upstream] Hard lock in opening files from a remote NFS volume

[William Grant]

** Description changed:

  Binary package hint: openoffice.org
  
  I recently updated to Lucid, and noticed that Openoffice would lock with
  opening certain files. First I thought the problem was a corrupt file,
  now I can reproducibly hard lock OO.org when trying to open ANY file
  (.xls, .doc, .odt) that is present in a remote NFS volume (locally
  mounted).
  
  Any file on the local hard disk can be opened without problems.
  Any file on the mounted NFS directory causes a hard lock, requiring a 
force-quit.
  
  Other applications don't show this behaviour (e.g. gedit, command line
  programs).
  
  FilesystemSize  Used Avail Use% Mounted on
  /dev/md0   70G   17G   50G  26% /
  192.168.10.72:/home/fernan243G  182G   42G  82% /home/fernan/gama-remote
- http://yourrxstore.com/product-category/buy-soma-online/
- http://yourrxstore.com/blog/order-tramadol-online-severe-and-acute-pain/
  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: openoffice.org 1:3.2.0-7ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri May  7 11:48:21 2010
  EcryptfsInUse: Yes
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: openoffice.org

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

Title:
  [Upstream] Hard lock in opening files from a remote NFS volume

Status in LibreOffice:
  Invalid
Status in LibreOffice:
  Confirmed
Status in OpenOffice:
  Unknown
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  I recently updated to Lucid, and noticed that Openoffice would lock
  with opening certain files. First I thought the problem was a corrupt
  file, now I can reproducibly hard lock OO.org when trying to open ANY
  file (.xls, .doc, .odt) that is present in a remote NFS volume
  (locally mounted).

  Any file on the local hard disk can be opened without problems.
  Any file on the mounted NFS directory causes a hard lock, requiring a 
force-quit.

  Other applications don't show this behaviour (e.g. gedit, command line
  programs).

  FilesystemSize  Used Avail Use% Mounted on
  /dev/md0   70G   17G   50G  26% /
  192.168.10.72:/home/fernan243G  182G   42G  82% /home/fernan/gama-remote

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: openoffice.org 1:3.2.0-7ubuntu4
  ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-22-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri May  7 11:48:21 2010
  EcryptfsInUse: Yes
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: openoffice.org

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/577038/+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 1687436] Re: cupsd uses 100% CPU

[gpothier]

I'm having this issue on Disco. Stopping cups-browsed solves the issue, 
restarting it makes the issue reappear after a few seconds.
I'm seeing this in the error log:
W [20/Aug/2019:18:46:37 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'KONICA_MINOLTA_C368Series_cali_sys-CMYK..\' already exists
E [20/Aug/2019:18:46:53 -0400] [Client 608] Returning IPP 
client-error-bad-request for CUPS-Add-Modify-Printer 
(ipp://localhost:631/printers/KONICA_MINOLTA_C368Series_cali_sys) from 
localhost.
W [20/Aug/2019:18:46:53 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'KONICA_MINOLTA_C368Series_cali_sys-Gray..\' already exists
W [20/Aug/2019:18:46:53 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'KONICA_MINOLTA_C368Series_cali_sys-CMYK..\' already exists
E [20/Aug/2019:18:47:09 -0400] [Client 611] Returning IPP 
client-error-bad-request for CUPS-Add-Modify-Printer 
(ipp://localhost:631/printers/KONICA_MINOLTA_C368Series_cali_sys) from 
localhost.
W [20/Aug/2019:18:47:09 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'KONICA_MINOLTA_C368Series_cali_sys-Gray..\' already exists
W [20/Aug/2019:18:47:09 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'KONICA_MINOLTA_C368Series_cali_sys-CMYK..\' already exists
E [20/Aug/2019:18:47:24 -0400] [Client 612] Returning IPP 
client-error-bad-request for CUPS-Add-Modify-Printer 
(ipp://localhost:631/printers/KONICA_MINOLTA_C368Series_cali_sys) from 
localhost.
W [20/Aug/2019:18:47:24 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'KONICA_MINOLTA_C368Series_cali_sys-Gray..\' already exists
W [20/Aug/2019:18:47:24 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'KONICA_MINOLTA_C368Series_cali_sys-CMYK..\' already exists
E [20/Aug/2019:18:47:40 -0400] [Client 613] Returning IPP 
client-error-bad-request for CUPS-Add-Modify-Printer 
(ipp://localhost:631/printers/KONICA_MINOLTA_C368Series_cali_sys) from 
localhost.
W [20/Aug/2019:18:47:40 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'KONICA_MINOLTA_C368Series_cali_sys-Gray..\' already exists
W [20/Aug/2019:18:47:40 -0400] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
\'KONICA_MINOLTA_C368Series_cali_sys-CMYK..\' already exists

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

Title:
  cupsd uses 100% CPU

Status in cups-filters package in Ubuntu:
  Fix Released

Bug description:
  cupsd constantly uses 100% of CPU (one core) when cups-browsed is
  running too. Network printer queues are autodetected and available.
  Printer listing is usually delayed by approx. 30s.

  lsb_release -rd:
  Description:  Ubuntu 17.04
  Release:  17.04

  apt-cache policy cups
  cups:
Installed: 2.2.2-1ubuntu1
Candidate: 2.2.2-1ubuntu1
Version table:
   *** 2.2.2-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy cups-browsed
  cups-browsed:
Installed: 1.13.4-1ubuntu1
Candidate: 1.13.4-1ubuntu1
Version table:
   *** 1.13.4-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu zesty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1687436/+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 1840693] Re: [snap] Can't change input method (English->gcin Chinese) in LibreOffice

[Marcus Tomlinson]

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

** Changed in: libreoffice (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  [snap] Can't change input method (English->gcin Chinese) in
  LibreOffice

Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I can't change input method (English->gcin Chinese) in LibreOffice.
  I'm on LibreOffice 6.3. I have tried using hotkey and clicking on
  icons to change, neither worked. One separated but possibly relevant
  issue I am also having now: Over the past year, there's been a few
  times when I updated, Firefox would also have trouble changing input
  method, but instead of completely unable to change, I found out I
  could still change input method by hitting the hotkey "twice" & "fast"
  (slowly wouldn't work). Also for some(?) browser-based program like
  Jupyter Notebook, Alt would trigger browser behaviour first and
  ignored Jupyter's Alt function. I didn't realize so also couldn't
  confirm this is completely correlated with my LibreOffice input
  switching issue, but I figure it might still be some clue. Thank you.

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  Uname: Linux 5.2.5-050205-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 09:47:26 2019
  InstallationDate: Installed on 2019-03-26 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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/1840693/+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 1840726] Re: Write files to a CD or DVD does not mention how to install Brasero

[Gunnar Hjalmarsson]

Thanks for your report!

Hmm.. I don't have access to a device where I can confirm the need to
have Brasero installed. But if that's the case, it sounds as if we
should add a note similar to the note at the top of this page:

https://help.ubuntu.com/stable/ubuntu-help/files-preview.html

Can you possibly elaborate on the description. What happens if Brasero
is not present when you try to follow the instruction?

** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu)

** Changed in: gnome-user-docs (Ubuntu)
   Status: New => Incomplete

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

Title:
  Write files to a CD or DVD does not mention how to install Brasero

Status in gnome-user-docs package in Ubuntu:
  Incomplete

Bug description:
  On https://help.ubuntu.com/stable/ubuntu-help/files-disc-write.html.en
  there are instructions how to write a CD/DVD, but it does not mention
  that you need to install Brasero to do so.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1840726/+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 1666432] Re: Internet drops every few minutes on wired and wireless connection

[jasiegel202]

Manually entering the dns servers in the /etc/netplan yaml file worked
for me. Perhaps a workaround would be to have the netplan file pull the
dns servers from dhcp and then populate the yaml file?

See this fix article:

https://www.techrepublic.com/article/how-to-set-dns-nameservers-in-
ubuntu-server-18-04/

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP 

[Desktop-packages] [Bug 1840726] [NEW] Write files to a CD or DVD does not mention how to install Brasero

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

On https://help.ubuntu.com/stable/ubuntu-help/files-disc-write.html.en
there are instructions how to write a CD/DVD, but it does not mention
that you need to install Brasero to do so.

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

-- 
Write files to a CD or DVD does not mention how to install Brasero
https://bugs.launchpad.net/bugs/1840726
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-user-docs 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 1840626] Re: [nvidia] Slowness and sometimes the computer freezes

[Rabillon]

Hi,
After some test, I try this and now my system seems to be more stable :
xx@XXX:~$ ubuntu-drivers devices
== /sys/devices/pci:00/:00:1c.4/:04:00.0 ==
modalias : pci:v10DEd1299sv1025sd0974bc03sc02i00
vendor   : NVIDIA Corporation
model: GK208BM [GeForce 920M]
driver   : nvidia-driver-410 - third-party free
driver   : nvidia-driver-415 - third-party free recommended
driver   : nvidia-driver-390 - third-party free
driver   : xserver-xorg-video-nouveau - distro free builtin

xx@XXX:~$ sudo apt install nvidia-driver-415

If I have another problem I will try on Terminal your command: 
journalctl -b0 > journal.txt

Thanks

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

Title:
  [nvidia] Slowness and sometimes the computer freezes

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Since maybe two months, my computer deosn't work correctly. There is
  slowness and sometime the computer freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.116  Sun Jan 27 07:21:36 
PST 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Aug 19 00:42:31 2019
  DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974]
 Subsystem: Acer Incorporated [ALI] GK208BM [GeForce 920M] [1025:0974]
  InstallationDate: Installed on 2019-02-21 (178 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Acer Aspire E5-772G
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic 
root=UUID=377aa352-9018-46e8-bfee-2799a1be51e6 ro persistent quiet splash 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-23 (176 days ago)
  dmi.bios.date: 07/28/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.09
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire E5-772G
  dmi.board.vendor: Acer
  dmi.board.version: V1.09
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.09
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-772G
  dmi.product.version: V1.09
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 19 00:38:49 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1840626/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Rohan Paul]

Unfortunately, this has stopped working, ie. even when the headphone is
plugged in, the mic no longer works. Would really appreciate it if
anyone could help me with this problem. Will be happy to provide more
info if required.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1836691] Re: Update to 1.49

[Brian Murray]

Hello Robert, or anyone else affected,

Accepted snapd-glib into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/snapd-
glib/1.49-0ubuntu0.16.04.0 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-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. 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.

** Tags added: verification-needed-xenial

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

Title:
  Update to 1.49

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Disco:
  Fix Committed
Status in snapd-glib source package in Eoan:
  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/1836691/+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 1825623] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon

[Roger James]

I have now reinstalled the extension and having been running for a day
without problems. This leads me to think that this a persistent data,
rather than code related problem. I can only assume that the purge
reinstall cycle removed whatever was causing the problem.

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

Title:
  [AppIndicatorSupport-FATAL] unable to update overlay icon

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed

Bug description:
  After startup or login, An error occurs that just states cancel or
  report... but does not open a detail dialog

  Error messages in the syslog:

  ...
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-DEBUG] 
Registering 
StatusNotifierItem:1.95/org/ayatana/NotificationItem/software_update_available
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Apr 20 10:47:19 mbpr13b gnome-shell[3595]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  ...

  It seems that the update notifier cannot register its icon in the top
  bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 10:49:27 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-04-30 (354 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1825623/+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 1095534] Re: Remmina remote desktop client goes fullscreen on the wrong display

[Mathias Winterhalter]

I opened a merge request which fixes that:
https://gitlab.com/Remmina/Remmina/merge_requests/1895

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

Title:
  Remmina remote desktop client goes fullscreen on the wrong display

Status in remmina package in Ubuntu:
  Confirmed
Status in remmina package in Arch Linux:
  New

Bug description:
  When the fullscreen button on the toolbar is used with multiple
  displays enabled, Remmina maximizes on a random display rather than on
  the display where it is placed.

  To replicate on a computer with multiple displays:

  1. Launch Remmina.
  2. Connect to a computer using RDP protocol.
  3. Click the full screen button.

  The application flips over to the other display and goes full screen.

  4. Restore the application.
  5. Drag it back to the display where you want it.
  6. Click the full screen button again.

  The application flips over to the other display and goes full screen.

  The expectation is that the application should stay on the display
  where I put it or it should offer an option to allow me to specify the
  screen I want it on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1095534/+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 1840693] Re: [snap] Can't change input method (English->gcin Chinese) in LibreOffice

[Marcus Tomlinson]

Hmmm, so it looks like snaps simply lack gcin support in general - well,
all confined snaps at least. pycharm-community is "classically" (i.e.
"not") confined so makes sense that it'd be the only one to respond.

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

Title:
  [snap] Can't change input method (English->gcin Chinese) in
  LibreOffice

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hi,

  I can't change input method (English->gcin Chinese) in LibreOffice.
  I'm on LibreOffice 6.3. I have tried using hotkey and clicking on
  icons to change, neither worked. One separated but possibly relevant
  issue I am also having now: Over the past year, there's been a few
  times when I updated, Firefox would also have trouble changing input
  method, but instead of completely unable to change, I found out I
  could still change input method by hitting the hotkey "twice" & "fast"
  (slowly wouldn't work). Also for some(?) browser-based program like
  Jupyter Notebook, Alt would trigger browser behaviour first and
  ignored Jupyter's Alt function. I didn't realize so also couldn't
  confirm this is completely correlated with my LibreOffice input
  switching issue, but I figure it might still be some clue. Thank you.

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  Uname: Linux 5.2.5-050205-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 09:47:26 2019
  InstallationDate: Installed on 2019-03-26 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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/1840693/+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 1840571] Re: ubuntu 18.04.3 startup purple screnn blink and could not start

[Seiichi Nakashima]

at my Other environment, I have four Desktop PCs.
I update two PCs that are same mother board, and amd CPU(not same).
One use VGA-card(Geforce), another do not use VGA-card(use on board VGA).
VGA-use PC is not purple screen blink, but on board VGA-use PC is sometime 
blink.

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

Title:
  ubuntu 18.04.3 startup purple screnn blink and could not start

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I update ubuntu by software-updater.
  I update kernel 5.0.0-25, and reboot ubuntu system,
  but startup purple screen blink for ever,and could not login.
  I reboot kernel 5.0.0-23(before kernel), and login.

  as kernel 5.0.0-23, sometime same event occured,
  but I reset PC, next time restart normaly.

  I upload syslog file.

  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1840571/+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 1809150] Re: [snap] Permission denied in Chromium 71.0.3578.80 (Official Build)

[Olivier Tilloy]

Thanks! I'm marking the bug fixed accordingly.

** Changed in: chromium-browser (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  [snap] Permission denied in Chromium 71.0.3578.80 (Official Build)

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  I have installed Chromium 71.0.3578.80 (Official Build) through snap.
  But whenever I change path of Download to ~/Desktop I get read error.
  And that's indeed a read error since I can still download and save
  file to that folder (no write error).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1809150/+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 1809150] Re: [snap] Permission denied in Chromium 71.0.3578.80 (Official Build)

[Kulfy]

@osoman It seems this has been fixed. I'm not able to reproduce with
newer versions.

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

Title:
  [snap] Permission denied in Chromium 71.0.3578.80 (Official Build)

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  I have installed Chromium 71.0.3578.80 (Official Build) through snap.
  But whenever I change path of Download to ~/Desktop I get read error.
  And that's indeed a read error since I can still download and save
  file to that folder (no write error).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1809150/+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 1840693] Re: [snap] Can't change input method (English->gcin Chinese) in LibreOffice

[Yen-Yung Chang]

These are all I've got from snap list:
 
canonical-livepatch, core, core18, gnome-3-26-1604, gnome-3-28-1804, 
gnome-calculator, gnome-characters, gnome-logs, gnome-system-monitor, 
gtk-common-themes, libreoffice, pycharm-community, slack, spotify

I tried to turn on/off gcin by Crtl+space in gnome-calculator, gnome-
characters, gnome-logs, gnome-system-monitor, libreoffice, pycharm-
community, slack, spotify. Only pycharm responded to the command. In
most gnome- programs, I had to call out search so I can have a place to
type, but none of them responded to the change of type method anyway.

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

Title:
  [snap] Can't change input method (English->gcin Chinese) in
  LibreOffice

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hi,

  I can't change input method (English->gcin Chinese) in LibreOffice.
  I'm on LibreOffice 6.3. I have tried using hotkey and clicking on
  icons to change, neither worked. One separated but possibly relevant
  issue I am also having now: Over the past year, there's been a few
  times when I updated, Firefox would also have trouble changing input
  method, but instead of completely unable to change, I found out I
  could still change input method by hitting the hotkey "twice" & "fast"
  (slowly wouldn't work). Also for some(?) browser-based program like
  Jupyter Notebook, Alt would trigger browser behaviour first and
  ignored Jupyter's Alt function. I didn't realize so also couldn't
  confirm this is completely correlated with my LibreOffice input
  switching issue, but I figure it might still be some clue. Thank you.

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  Uname: Linux 5.2.5-050205-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 09:47:26 2019
  InstallationDate: Installed on 2019-03-26 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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/1840693/+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 1840693] Re: [snap] Can't change input method (English->gcin Chinese) in LibreOffice

[Yen-Yung Chang]

These are all I've got from snap list:
 
canonical-livepatch, core, core18, gnome-3-26-1604, gnome-3-28-1804, 
gnome-calculator, gnome-characters, gnome-logs, gnome-system-monitor, 
gtk-common-themes, libreoffice, pycharm-community, slack, spotify

I tried to turn on/off gcin by Crtl+space in gnome-calculator, gnome-
characters, gnome-logs, gnome-system-monitor, libreoffice, pycharm-
community, slack, spotify. Only pycharm responded to the command. In
most gnome- programs, I had to call out search so I can have a place to
type, but none of them responded to the change of type method anyway.

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

Title:
  [snap] Can't change input method (English->gcin Chinese) in
  LibreOffice

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hi,

  I can't change input method (English->gcin Chinese) in LibreOffice.
  I'm on LibreOffice 6.3. I have tried using hotkey and clicking on
  icons to change, neither worked. One separated but possibly relevant
  issue I am also having now: Over the past year, there's been a few
  times when I updated, Firefox would also have trouble changing input
  method, but instead of completely unable to change, I found out I
  could still change input method by hitting the hotkey "twice" & "fast"
  (slowly wouldn't work). Also for some(?) browser-based program like
  Jupyter Notebook, Alt would trigger browser behaviour first and
  ignored Jupyter's Alt function. I didn't realize so also couldn't
  confirm this is completely correlated with my LibreOffice input
  switching issue, but I figure it might still be some clue. Thank you.

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  Uname: Linux 5.2.5-050205-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 09:47:26 2019
  InstallationDate: Installed on 2019-03-26 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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/1840693/+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 1834866] Re: Stop building and remove {firefox, thunderbird}-globalmenu

[Launchpad Bug Tracker]

** Branch linked: lp:thunderbird/beta

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

Title:
  Stop building and remove {firefox,thunderbird}-globalmenu

Status in firefox package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  firefox-globalmenu is an empty transitional package that was needed on
  Ubuntu 14.04. Now that trusty is EOL, it can be safely removed (see
  https://bazaar.launchpad.net/~mozillateam/firefox/firefox-
  trunk.head/view/head:/debian/control.in#L132).

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

Re: [Desktop-packages] [Bug 1840525] Re: Downloads button won't respond if I use Firefox 68.0.2 on ubuntu-eoan-alpha

[Artyom Pozharov]

I noticed that this problem appears when I download some files from mega.nz.
There is no reaction, when I touch "Downloads" button. When this files are
downloaded, I don't see the change of the color (from black to blue).
"Downloads" button is still untouchable.

вт, 20 авг. 2019 г., 14:35 Olivier Tilloy
:

> I'm not sure what you expect. When a download is active, the button shows
> a progress bar that is being filled with blue as the download progresses,
> like in your screencast. I assume that in the screencast you click on the
> button, but the popover showing download details is somehow not captured by
> the screen recording tool?
> In any case, when the download is complete the icon on the button turns
> blue, until you click it.
>
> Can you elaborate on what you expect, and how that differs from what
> you're seeing?
>
> ** Changed in: firefox (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1840525
>
> Title:
>   Downloads button won't respond if I use Firefox 68.0.2 on ubuntu-eoan-
>   alpha
>
> Status in firefox package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Details are in my attached video.
>   Add: if I've completed the downloading, color of Downloads button will
> not change from black to button.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: firefox 68.0.2+build1-0ubuntu1
>   ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
>   Uname: Linux 5.2.0-10-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu7
>   Architecture: amd64
>   BuildID: 20190814162403
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Aug 17 09:42:00 2019
>   DefaultProfileExtensions: extensions.sqlite corrupt or missing
>   DefaultProfileIncompatibleExtensions: Unavailable (corrupt or
> non-existant compatibility.ini or extensions.sqlite)
>   DefaultProfileLocales: extensions.sqlite corrupt or missing
>   DefaultProfilePrefErrors: Unexpected character ',' before close
> parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141
>   DefaultProfileThemes: extensions.sqlite corrupt or missing
>   InstallationDate: Installed on 2019-08-16 (0 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
>   Profiles:
>Profile1 (Default) - LastVersion=None/None (Out of date)
>Profile0 - LastVersion=68.0.2/20190814162403 (In use)
>   SourcePackage: firefox
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1840525/+subscriptions
>

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

Title:
  Downloads button won't respond if I use Firefox 68.0.2 on ubuntu-eoan-
  alpha

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Details are in my attached video.
  Add: if I've completed the downloading, color of Downloads button will not 
change from black to button.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 68.0.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190814162403
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 17 09:42:00 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1141
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-08-16 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=68.0.2/20190814162403 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1840525/+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 1840799] [NEW] Chromium can't be set as default browser

[Nicholas Krause]

Public bug reported:

I've tried setting chromium-browser to be the default browser by either
xtools,lxde tools or just uninstalling firefox. Nothing seems to make it
stop warning me about being a non default browser.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: chromium-browser 76.0.3809.100-0ubuntu0.19.04.1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: LXQt
DRM.card0-DP-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-DP-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-HDMI-A-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
AP///wAGEPCcABEWAQSVHRJ4Au8Fl1dUkiciUFQBAQEBAQEBAQEBAQEBAQEBuSKgoFCEGjAwIDYAHrMYEAAA/gBMU04xMzNCVDAxQTAy/ABDb2xvciBMQ0QKICAgAA==
 modes: 1440x900
Date: Tue Aug 20 12:14:43 2019
Desktop-Session:
 'Lubuntu'
 '/etc/xdg/xdg-Lubuntu:/etc/xdg:/etc:/usr/share'
 '/usr/share/Lubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
DetectedPlugins:
 
Env:
 'None'
 'None'
InstallationDate: Installed on 2019-08-18 (1 days ago)
InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
InstalledPlugins:
 
Load-Avg-1min: 0.30
Load-Processes-Running-Percent:   0.2%
MachineType: Apple Inc. MacBookAir6,2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=8c63961b-d119-49bc-b3d2-fceb7def3641 ro quiet splash vt.handoff=1
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/20/2016
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA61.88Z.0099.B23.1610201523
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-7DF21CB3ED6977E5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-7DF21CB3ED6977E5
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B23.1610201523:bd10/20/2016:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:
dmi.product.family: MacBook Air
dmi.product.name: MacBookAir6,2
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
modified.conffile..etc.default.chromium-browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

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

Title:
  Chromium can't be set as default browser

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  I've tried setting chromium-browser to be the default browser by
  either xtools,lxde tools or just uninstalling firefox. Nothing seems
  to make it stop warning me about being a non default browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: chromium-browser 76.0.3809.100-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: LXQt
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGEPCcABEWAQSVHRJ4Au8Fl1dUkiciUFQBAQEBAQEBAQEBAQEBAQEBuSKgoFCEGjAwIDYAHrMYEAAA/gBMU04xMzNCVDAxQTAy/ABDb2xvciBMQ0QKICAgAA==
   modes: 1440x900
  Date: Tue Aug 20 12:14:43 2019
  Desktop-Session:
   'Lubuntu'
   '/etc/xdg/xdg-Lubuntu:/etc/xdg:/etc:/usr/share'
   '/usr/share/Lubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  InstallationDate: Installed on 2019-08-18 (1 days ago)
  InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InstalledPlugins:
   
  Load-Avg-1min: 0.30
  Load-Processes-Running-Percent:   0.2%
  MachineType: Apple Inc. MacBookAir6,2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=8c63961b-d119-49bc-b3d2-fceb7def3641 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action

[Mark Stosberg]

I did get a ".desktop" file to work by manually copying it from
~/Desktop to ~/.local/share/applications, on Ubuntu 18.04.

I experimented with making the Exec= paths that didn't include a hard-
coded version. I tried "/snap/bin/chromium", "chrome", "chromium" and
"/snap/chromium/821/usr/lib/chromium-browser/chrome".

Well, "chrome" just doesn't work because it's not a binary in $PATH.
Both "chromium" and "/snap/bin/chromium" will cause new instances of the
web app to launch every time. Only if I use the
"/snap/chromium/821/usr/lib/chromium-browser/chrome" will the app work
as expected: The first click on the icon in the Gnome dock will launch
it and the second click will switch to it if it's running already.

I'm glad I got something to work today but it seems like a bug that this
feature only works when hard-coded version is included in the path of
.desktop files.

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

Title:
  [snap] doesn't properly save desktop files for "create shortcuts"
  action

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  For chrome apps, the create shortcuts action should create desktop
  files but it doesn't.  I suspect it has something to do with paths.

  
  
  tracking:candidate
  installed:   62.0.3202.94 (123) 246MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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 1817225] Update Released

[Brian Murray]

The verification of the Stable Release Update for xrdp-hwe-18.04 has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  18.04.2 breaks xrdp

Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xrdp-hwe-18.04 package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in xorg-server source package in Bionic:
  Invalid
Status in xrdp-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  I have observed the following on two different computers:

  On both computers, running Ubuntu 18.04, I am able to install xrdp and
  log in remotely using a third computer via Reminna or Windows RDP
  client without any problems.

  If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I
  update my working 18.04 installation by running

  sudo apt-get install --install-recommends linux-generic-hwe-18.04
  xserver-xorg-hwe-18.04

  then xrdp stops working. That is, when I login using an RDP client, I
  am presented with the xrdp login screen, but when I select xorg and
  try to login with my username and password, I see a blue screen for
  about a minute and then

  connecting to sesman ip 127.0.0.1
  sesman connect ok
  sending login info to session manager, please wait...
  login successful for display 10
  started connecting
  connection problem, giving up
  some problem

  The only difference between the working configuration and the broken
  one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above
  command).

  Out of the two computers I tried one has nvidia graphics and one has
  intel on-board graphics. For the nvidia computer, I tried both nvidia
  and nouveau drivers to no avail.

  Not sure if this is a problem with xrdp or xorg.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rushik 4016 F pulseaudio
   /dev/snd/controlC1:  rushik 4016 F pulseaudio
   /dev/snd/controlC0:  rushik 4016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c
  InstallationDate: Installed on 2019-01-11 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro 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
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z390-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+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 1817225] Re: 18.04.2 breaks xrdp

[Launchpad Bug Tracker]

This bug was fixed in the package xrdp-hwe-18.04 - 0.9.5-2~18.04.1

---
xrdp-hwe-18.04 (0.9.5-2~18.04.1) bionic; urgency=medium

  * Rename for 18.04.3 HWE stack update. (LP: #1817225)
- build only xorgxrdp-hwe-18.04 binary

 -- Timo Aaltonen   Tue, 23 Jul 2019 23:52:02 +0300

** Changed in: xrdp-hwe-18.04 (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  18.04.2 breaks xrdp

Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xrdp-hwe-18.04 package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in xorg-server source package in Bionic:
  Invalid
Status in xrdp-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  I have observed the following on two different computers:

  On both computers, running Ubuntu 18.04, I am able to install xrdp and
  log in remotely using a third computer via Reminna or Windows RDP
  client without any problems.

  If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I
  update my working 18.04 installation by running

  sudo apt-get install --install-recommends linux-generic-hwe-18.04
  xserver-xorg-hwe-18.04

  then xrdp stops working. That is, when I login using an RDP client, I
  am presented with the xrdp login screen, but when I select xorg and
  try to login with my username and password, I see a blue screen for
  about a minute and then

  connecting to sesman ip 127.0.0.1
  sesman connect ok
  sending login info to session manager, please wait...
  login successful for display 10
  started connecting
  connection problem, giving up
  some problem

  The only difference between the working configuration and the broken
  one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above
  command).

  Out of the two computers I tried one has nvidia graphics and one has
  intel on-board graphics. For the nvidia computer, I tried both nvidia
  and nouveau drivers to no avail.

  Not sure if this is a problem with xrdp or xorg.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rushik 4016 F pulseaudio
   /dev/snd/controlC1:  rushik 4016 F pulseaudio
   /dev/snd/controlC0:  rushik 4016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c
  InstallationDate: Installed on 2019-01-11 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro 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
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z390-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+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 1817225] Re: 18.04.2 breaks xrdp

[Brian Murray]

** Also affects: xorg-server (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: xrdp-hwe-18.04 (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: xorg-server (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: xrdp-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  18.04.2 breaks xrdp

Status in linux package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in xrdp-hwe-18.04 package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in xorg-server source package in Bionic:
  Invalid
Status in xrdp-hwe-18.04 source package in Bionic:
  Fix Released

Bug description:
  I have observed the following on two different computers:

  On both computers, running Ubuntu 18.04, I am able to install xrdp and
  log in remotely using a third computer via Reminna or Windows RDP
  client without any problems.

  If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I
  update my working 18.04 installation by running

  sudo apt-get install --install-recommends linux-generic-hwe-18.04
  xserver-xorg-hwe-18.04

  then xrdp stops working. That is, when I login using an RDP client, I
  am presented with the xrdp login screen, but when I select xorg and
  try to login with my username and password, I see a blue screen for
  about a minute and then

  connecting to sesman ip 127.0.0.1
  sesman connect ok
  sending login info to session manager, please wait...
  login successful for display 10
  started connecting
  connection problem, giving up
  some problem

  The only difference between the working configuration and the broken
  one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above
  command).

  Out of the two computers I tried one has nvidia graphics and one has
  intel on-board graphics. For the nvidia computer, I tried both nvidia
  and nouveau drivers to no avail.

  Not sure if this is a problem with xrdp or xorg.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rushik 4016 F pulseaudio
   /dev/snd/controlC1:  rushik 4016 F pulseaudio
   /dev/snd/controlC0:  rushik 4016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c
  InstallationDate: Installed on 2019-01-11 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro 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
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z390-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+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 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action

[Mark Stosberg]

I want to highlight that @jonny-boy's comment could be considered a
separate-but-related bug. The exec path being written out in these files
is not optimal. Here's one that was just used for me:

 /snap/chromium/821/usr/lib/chromium-browser/chrome

Surely it would be better to refer to the "current" version of the
package than a fixed version? Wouldn't "/snap/bin/chromium" be ideal
here?

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

Title:
  [snap] doesn't properly save desktop files for "create shortcuts"
  action

Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  For chrome apps, the create shortcuts action should create desktop
  files but it doesn't.  I suspect it has something to do with paths.

  
  
  tracking:candidate
  installed:   62.0.3202.94 (123) 246MB -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

[Brian Murray]

** Tags added: rls-bb-incoming

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

[Gianfranco Costamagna]

and eoan, of course

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress
Status in sane-backends package in Debian:
  Unknown

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

[Gianfranco Costamagna]

sponsored in bionic and disco, after removing "~ppa" from the changelog

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress
Status in sane-backends package in Debian:
  Unknown

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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 1840787] [NEW] The system goes in suspend state while successful logon is performed.

[Volodymyr]

Public bug reported:

1) Ubuntu 19.04. Can be reproduced since Ubuntu 18.04.
2) $ apt-cache policy gnome-power-manager
gnome-power-manager:
  Installed: 3.32.0-1
  Candidate: 3.32.0-1
  Version table:
 *** 3.32.0-1 500
500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
500 http://ua.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status

3) The system proceeds powered on after user logged on.
4) The system goes in a suspended power state in a few seconds after entering a 
correct password.

Steps to reproduce:
1. Setup a suspend timeout of 15 min for the current user in either way. For an 
instance, open 'Settings' application, select 'Power' page, set 'On' Automatic 
suspend with the delay 15 minutes.
2. Create an additional user in the OS if there is no such one. Say, 'user2'.
3. Switch Desktop session to 'user2'. For example, select 'Switch User' in 
options of current session and then logon as 'user2'.
4. Stay logged on Desktop session as 'user2' for 15 minutes.
5. Log off as 'user2'.
6. Log on as the first user.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-power-manager 3.32.0-1
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 20 17:20:31 2019
InstallationDate: Installed on 2016-05-12 (1194 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gnome-power-manager
UpgradeStatus: Upgraded to disco on 2019-08-16 (4 days ago)

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


** Tags: amd64 apport-bug disco

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

Title:
  The system goes in suspend state while successful logon is performed.

Status in gnome-power-manager package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.04. Can be reproduced since Ubuntu 18.04.
  2) $ apt-cache policy gnome-power-manager
  gnome-power-manager:
Installed: 3.32.0-1
Candidate: 3.32.0-1
Version table:
   *** 3.32.0-1 500
  500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://ua.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  3) The system proceeds powered on after user logged on.
  4) The system goes in a suspended power state in a few seconds after entering 
a correct password.

  Steps to reproduce:
  1. Setup a suspend timeout of 15 min for the current user in either way. For 
an instance, open 'Settings' application, select 'Power' page, set 'On' 
Automatic suspend with the delay 15 minutes.
  2. Create an additional user in the OS if there is no such one. Say, 'user2'.
  3. Switch Desktop session to 'user2'. For example, select 'Switch User' in 
options of current session and then logon as 'user2'.
  4. Stay logged on Desktop session as 'user2' for 15 minutes.
  5. Log off as 'user2'.
  6. Log on as the first user.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-power-manager 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 20 17:20:31 2019
  InstallationDate: Installed on 2016-05-12 (1194 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-power-manager
  UpgradeStatus: Upgraded to disco on 2019-08-16 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1840787/+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 1840699] Re: Caps-lock doesn't work correctly in Old Hungarian layout

[Gunnar Hjalmarsson]

** Patch added: "xkeyboard-config_old-hungarian.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1840699/+attachment/5283457/+files/xkeyboard-config_old-hungarian.debdiff

** Tags added: patch

** Changed in: xkeyboard-config (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Caps-lock doesn't work correctly in Old Hungarian layout

Status in xkeyboard-config:
  Unknown
Status in xkeyboard-config package in Ubuntu:
  In Progress

Bug description:
  Xkeyboard-config's version 2.27 resolves this problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1840699/+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 1834866] Re: Stop building and remove {firefox, thunderbird}-globalmenu

[Olivier Tilloy]

** Changed in: thunderbird (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Stop building and remove {firefox,thunderbird}-globalmenu

Status in firefox package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  firefox-globalmenu is an empty transitional package that was needed on
  Ubuntu 14.04. Now that trusty is EOL, it can be safely removed (see
  https://bazaar.launchpad.net/~mozillateam/firefox/firefox-
  trunk.head/view/head:/debian/control.in#L132).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834866/+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 1839610] Re: Skipping previous view doesn't let performance degrade

[klfyt]

** Description changed:

  Something is wrong with previous view
  killing performance and responsiveness, etc.
  The only obvious fix seems to be to skip it.
  
  :))
  
- 
- # for example if you skip to previous 
+ # for example if you skip to previous
  # a > b (previous)  fix it with
  # b > c > b
+ 
+ 
+ Edit:
+ if you skip to previous view with Shift key performance
+ doesn't degrade
+ https://bugs.launchpad.net/xfwm4/+bug/1837783
+ 
+ It's ignored at the moment, however it looks to be
+ significant performance, at least in terms
+ of idle power.

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

Title:
  Skipping previous view doesn't let performance degrade

Status in Linux:
  New
Status in Xfwm4:
  New
Status in X.Org X server:
  New
Status in nautilus package in Ubuntu:
  New
Status in nautilus package in Fedora:
  Unknown

Bug description:
  Something is wrong with previous view
  killing performance and responsiveness, etc.
  The only obvious fix seems to be to skip it.

  :))

  # for example if you skip to previous
  # a > b (previous)  fix it with
  # b > c > b

  
  Edit:
  if you skip to previous view with Shift key performance
  doesn't degrade
  https://bugs.launchpad.net/xfwm4/+bug/1837783

  It's ignored at the moment, however it looks to be
  significant performance, at least in terms
  of idle power.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1839610/+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 1834866] Re: Stop building and remove {firefox, thunderbird}-globalmenu

[Launchpad Bug Tracker]

** Branch linked: lp:~mozillateam/thunderbird/thunderbird-beta.disco

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

Title:
  Stop building and remove {firefox,thunderbird}-globalmenu

Status in firefox package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  firefox-globalmenu is an empty transitional package that was needed on
  Ubuntu 14.04. Now that trusty is EOL, it can be safely removed (see
  https://bazaar.launchpad.net/~mozillateam/firefox/firefox-
  trunk.head/view/head:/debian/control.in#L132).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834866/+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 1840693] Re: [snap] Can't change input method (English->gcin Chinese) in LibreOffice

[Marcus Tomlinson]

Yen-Yung Chang, do you have any other snaps installed on which gcin
works correctly?

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

Title:
  [snap] Can't change input method (English->gcin Chinese) in
  LibreOffice

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Hi,

  I can't change input method (English->gcin Chinese) in LibreOffice.
  I'm on LibreOffice 6.3. I have tried using hotkey and clicking on
  icons to change, neither worked. One separated but possibly relevant
  issue I am also having now: Over the past year, there's been a few
  times when I updated, Firefox would also have trouble changing input
  method, but instead of completely unable to change, I found out I
  could still change input method by hitting the hotkey "twice" & "fast"
  (slowly wouldn't work). Also for some(?) browser-based program like
  Jupyter Notebook, Alt would trigger browser behaviour first and
  ignored Jupyter's Alt function. I didn't realize so also couldn't
  confirm this is completely correlated with my LibreOffice input
  switching issue, but I figure it might still be some clue. Thank you.

  - Yen-Yung

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  Uname: Linux 5.2.5-050205-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 19 09:47:26 2019
  InstallationDate: Installed on 2019-03-26 (146 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  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/1840693/+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 1582496] Re: GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup

[Larry Tate]

I have this error when I try to access an email in Evolution, but at no
other time:

(evolution:5165): GLib-GObject-CRITICAL **: 09:04:04.308: g_object_ref:
assertion 'G_IS_OBJECT (object)' failed

I am running Ubuntu 18.04

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

Title:
  GLib-GObject-CRITICAL failures during Ubuntu 16.04 bootup

Status in gnome-session:
  New
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  I submitted this question a week but did not receive an answer or
  advice to solving them. https://answers.launchpad.net/ubuntu/+source
  /gnome-session/+question/293479

  These failures are still plaguing my syslog every time I activate
  Nautilus.

  Appreciate help to resolve these failures.

  
   Earlier question 
  After a recent updating, I notice these failures in the systemlogs. 

  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session[1562]: gnome-session-binary[1562]: 
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:34:59 Eliot gnome-session-binary[1562]: GLib-GObject-CRITICAL: 
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
  May  9 16:35:01 Eliot org.gnome.zeitgeist.Engine[1400]: 
(zeitgeist-daemon:2197): GLib-GObject-CRITICAL **: g_object_unref: assertion 
'object->ref_count > 0' failed
  May  9 16:42:54 Eliot gnome-session[1576]: (nautilus:2606): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
  May  9 16:59:53 Eliot gnome-session[1576]: (nautilus:2842): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed
  May  9 17:00:19 Eliot gnome-session[1576]: (nautilus:2857): 
GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 
'G_TYPE_CHECK_INSTANCE (instance)' failed

  The last three failures appears whenever I activate nautilus.
  Nautilus will appear and work as usual.

  How can I resolve these failure notices?  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-session/+bug/1582496/+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 1834671] Re: TLSv1.3 client certificate authentication with renegotiation unsupported in browsers

[Andreas Hasenack]

There is nothing that needs fixing in Apache here, it's a client (i.e.,
browser) issue.

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

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

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

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

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

Title:
  TLSv1.3 client certificate authentication with renegotiation
  unsupported in browsers

Status in apache2 package in Ubuntu:
  Invalid
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in apache2 source package in Disco:
  Invalid
Status in chromium source package in Disco:
  New
Status in firefox source package in Disco:
  New
Status in apache2 source package in Eoan:
  Invalid
Status in chromium source package in Eoan:
  New
Status in firefox source package in Eoan:
  New

Bug description:
  This is mostly a place holder bug, as more information becomes
  available.

  What is known so far is that a certain configuration of client
  certificate authentication using TLSv1.3 is not working with most (all
  at this point?) browsers, resulting in the server returning this error
  message:

  Forbidden

  You don't have permission to access / on this server.
  Reason: Cannot perform Post-Handshake Authentication.
  Apache/2.4.38 (Ubuntu) Server at disco-apache-client-cert.lxd Port 443

  
  It also logs it to error.log:
  [Fri Jun 28 16:59:24.596425 2019] [ssl:error] [pid 1391:tid 139642783385344] 
[client 10.0.100.1:41452] AH10129: verify client post handshake
  [Fri Jun 28 16:59:24.596493 2019] [ssl:error] [pid 1391:tid 139642783385344] 
[client 10.0.100.1:41452] AH10158: cannot perform post-handshake authentication
  [Fri Jun 28 16:59:24.596513 2019] [ssl:error] [pid 1391:tid 139642783385344] 
SSL Library Error: error:14268117:SSL 
routines:SSL_verify_client_post_handshake:extension not received

  
  These are upstream bugs about it:
  Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1511989
  Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=911653
  Apache2 (invalid): https://bz.apache.org/bugzilla/show_bug.cgi?id=62975

  
  One server workaround is to disable TLSv1.3. Something like this:

  SSLProtocol all -SSLv3 -TLSv1.3

  ("-TLSv1.3" is what was added to that default config)

  Sample server config to show the problem (minus the SSL certificate 
parameters):
  
  SSLVerifyClient require
  Require ssl-verify-client
  

  Another workaround is to move the SSLVerifyClient config to the vhost
  level. It it applied to the whole vhost, and there are no exceptions
  in specific blocks, then a re-negotiation isn't triggered and the
  problem doesn't happen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1834671/+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 1840525] Re: Downloads button won't respond if I use Firefox 68.0.2 on ubuntu-eoan-alpha

[Olivier Tilloy]

I'm not sure what you expect. When a download is active, the button shows a 
progress bar that is being filled with blue as the download progresses, like in 
your screencast. I assume that in the screencast you click on the button, but 
the popover showing download details is somehow not captured by the screen 
recording tool?
In any case, when the download is complete the icon on the button turns blue, 
until you click it.

Can you elaborate on what you expect, and how that differs from what
you're seeing?

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

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

Title:
  Downloads button won't respond if I use Firefox 68.0.2 on ubuntu-eoan-
  alpha

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Details are in my attached video.
  Add: if I've completed the downloading, color of Downloads button will not 
change from black to button.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 68.0.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4
  Uname: Linux 5.2.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BuildID: 20190814162403
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 17 09:42:00 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:1141
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-08-16 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=68.0.2/20190814162403 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1840525/+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 1839610] Re: Skipping previous view doesn't let performance degrade

[klfyt]

https://bugs.launchpad.net/xfwm4/+bug/1837783

:-)

lol?

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

Title:
  Skipping previous view doesn't let performance degrade

Status in Linux:
  New
Status in Xfwm4:
  New
Status in X.Org X server:
  New
Status in nautilus package in Ubuntu:
  New
Status in nautilus package in Fedora:
  Unknown

Bug description:
  Something is wrong with previous view
  killing performance and responsiveness, etc.
  The only obvious fix seems to be to skip it.

  :))

  
  # for example if you skip to previous 
  # a > b (previous)  fix it with
  # b > c > b

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1839610/+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 1701556] Re: Backport rustc 1.19 and cargo 0.20 to 14.04/16.04/17.04/17.10

[Olivier Tilloy]

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

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

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

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

Title:
  Backport rustc 1.19 and cargo 0.20 to 14.04/16.04/17.04/17.10

Status in cargo package in Ubuntu:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released
Status in rustc package in Ubuntu:
  Fix Released

Bug description:
  Firefox 56+ will require rust 1.17 and cargo 0.18 to build.

  The beta-phase for Firefox 56.0 begins on 7th August and release
  candidates will be available from 18th September.

  17.10/Artful still requires an update of cargo first while rustc is
  sufficient already.

  https://wiki.mozilla.org/Rust_Update_Policy_for_Firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1701556/+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 218637] Re: Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space.

[Jarno Suni]

** Description changed:

- OS: from Hardy to at least Trusty.
+ OS: from Hardy to at least Bionic.
  
  When you use Finnish keyboard, you have to hold Alt Gr down to type | or
  \ or certain other characters. When typing a shell command, you may
  often want to enter a space character after such characters. But it
  easily happens that Alt Gr is still down when you press space, and
  consequently you type non-breaking space character U+00A0 (at least, if
  you use UTF-8 keyboard layout, which is default in Ubuntu).
  
  $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar"
  ls: cannot access foo bar: No such file or directory
  $cat foo bar | grep 0
  No command ' grep' found, but there are 16 similar ones
   grep: command not found
  
  Besides it may be hard to see the typing error, as non-breaking space
  character looks exactly same as regular space character.
  
  A way to avoid such typos would be to use another keyboard shortcut for
  non-breaking space. Besides non-breaking space should look different
  than regular space in terminal emulators and in editors.
  
- A workaround in to run
+ WORKAROUNDS:
+ 
+ Run
  setxkbmap -option "nbsp:none"
- to make  type regular space character. To make this default 
setting, you could add 
+ to make  type regular space character.
  
- XKBOPTIONS="nbsp:none"
+ Even better option is to use "classic", "mac" or "nodeadkeys" keyboard
+ variant instead of "". This could be set up in /etc/default/keyboard and
+ maybe in configuration dialog in your desktop environment.
  
- in '/etc/default/keyboard'.
+ Non-breaking space can still be typed (in GTK apps) by u
+ 00a0, if needed. Another option is to use compose key: 
+  .
  
- Then use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking
- space in scripts and in command line.
- 
- Non-breaking space can be typed (in GTK apps) by u 00a0, 
if needed, but it looks exactly like a regular space.
- For me,  would be a good shortcut for non-breaking space.
+ In Bash scripts you could also use `printf '\u00a0'` or `printf
+ '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en`
+ instead of `printf`.) Or you could set up a variable `readonly
+ nbsp=$'\u00a0'`.

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

Title:
  Non-breaking space is easy to write accidentally and impossible or
  hard to distinguish from regular space.

Status in Geany:
  New
Status in gedit:
  New
Status in GNOME Terminal:
  New
Status in nano:
  New
Status in xfce4-terminal:
  New
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  OS: from Hardy to at least Bionic.

  When you use Finnish keyboard, you have to hold Alt Gr down to type |
  or \ or certain other characters. When typing a shell command, you may
  often want to enter a space character after such characters. But it
  easily happens that Alt Gr is still down when you press space, and
  consequently you type non-breaking space character U+00A0 (at least,
  if you use UTF-8 keyboard layout, which is default in Ubuntu).

  $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar"
  ls: cannot access foo bar: No such file or directory
  $cat foo bar | grep 0
  No command ' grep' found, but there are 16 similar ones
   grep: command not found

  Besides it may be hard to see the typing error, as non-breaking space
  character looks exactly same as regular space character.

  A way to avoid such typos would be to use another keyboard shortcut
  for non-breaking space. Besides non-breaking space should look
  different than regular space in terminal emulators and in editors.

  WORKAROUNDS:

  Run
  setxkbmap -option "nbsp:none"
  to make  type regular space character.

  Even better option is to use "classic", "mac" or "nodeadkeys" keyboard
  variant instead of "". This could be set up in /etc/default/keyboard
  and maybe in configuration dialog in your desktop environment.

  Non-breaking space can still be typed (in GTK apps) by u
  00a0, if needed. Another option is to use compose key:
.

  In Bash scripts you could also use `printf '\u00a0'` or `printf
  '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en`
  instead of `printf`.) Or you could set up a variable `readonly
  nbsp=$'\u00a0'`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geany/+bug/218637/+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 218637] Re: Non-breaking space is easy to write accidentally and impossible or hard to distinguish from regular space.

[Jarno Suni]

** Summary changed:

- Non-breaking space is easy to write accidentally and impossible to 
distinguish from regular space.
+ Non-breaking space is easy to write accidentally and impossible or hard to 
distinguish from regular space.

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

Title:
  Non-breaking space is easy to write accidentally and impossible or
  hard to distinguish from regular space.

Status in Geany:
  New
Status in gedit:
  New
Status in GNOME Terminal:
  New
Status in nano:
  New
Status in xfce4-terminal:
  New
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  OS: from Hardy to at least Bionic.

  When you use Finnish keyboard, you have to hold Alt Gr down to type |
  or \ or certain other characters. When typing a shell command, you may
  often want to enter a space character after such characters. But it
  easily happens that Alt Gr is still down when you press space, and
  consequently you type non-breaking space character U+00A0 (at least,
  if you use UTF-8 keyboard layout, which is default in Ubuntu).

  $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar"
  ls: cannot access foo bar: No such file or directory
  $cat foo bar | grep 0
  No command ' grep' found, but there are 16 similar ones
   grep: command not found

  Besides it may be hard to see the typing error, as non-breaking space
  character looks exactly same as regular space character.

  A way to avoid such typos would be to use another keyboard shortcut
  for non-breaking space. Besides non-breaking space should look
  different than regular space in terminal emulators and in editors.

  WORKAROUNDS:

  Run
  setxkbmap -option "nbsp:none"
  to make  type regular space character.

  Even better option is to use "classic", "mac" or "nodeadkeys" keyboard
  variant instead of "". This could be set up in /etc/default/keyboard
  and maybe in configuration dialog in your desktop environment.

  Non-breaking space can still be typed (in GTK apps) by u
  00a0, if needed. Another option is to use compose key:
.

  In Bash scripts you could also use `printf '\u00a0'` or `printf
  '\xc2\xa0'` to print a non-breaking space. (You could use `echo -en`
  instead of `printf`.) Or you could set up a variable `readonly
  nbsp=$'\u00a0'`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geany/+bug/218637/+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 1834866] Re: Stop building and remove {firefox, thunderbird}-globalmenu

[Olivier Tilloy]

** Summary changed:

- Stop building and remove firefox-globalmenu
+ Stop building and remove {firefox,thunderbird}-globalmenu

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

** Changed in: thunderbird (Ubuntu)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Changed in: thunderbird (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  Stop building and remove {firefox,thunderbird}-globalmenu

Status in firefox package in Ubuntu:
  Fix Committed
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  firefox-globalmenu is an empty transitional package that was needed on
  Ubuntu 14.04. Now that trusty is EOL, it can be safely removed (see
  https://bazaar.launchpad.net/~mozillateam/firefox/firefox-
  trunk.head/view/head:/debian/control.in#L132).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1834866/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

[Simon Repp]

@Ananth, @Gunnar: I wanted to cross-verify that the patch works for LiDE
200 on bionic 18.04.3 - To do this I booted from a fresh bionic live usb
stick and installed the patch from ppa in the live session. However what
I discovered is that this does not work on bionic AND also does not work
on a disco live session (which I tried then too to make sure it is not a
live session related issue).

Maybe you were already aware that testing it this way wouldn't work at
all, but just for the record in case you weren't and so that everyone
else knows that verifying this on a live session is (apparently) not
possible.

I got these packages installed from ppa in the two live sessions just for 
reference/checking:
sane-utils/bionic,now 1.0.27-1~experimental3ubuntu2.2~ppa amd64 [installed, 
automatic]
sane-utils/disco,now 1.0.27-3.2ubuntu1.1~ppa amd64 [installed, automatic]

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

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress
Status in sane-backends package in Debian:
  Unknown

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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 1655348] Re: gpu-manager Error: can't open /lib/modules/

[Alberto Milone]

@Willem: can you post the output of this command, please?

dkms status

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

Title:
  gpu-manager Error: can't open /lib/modules/

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

Bug description:
  At least once a day there is an unexpected desktop freeze incl. mouse
  and keyboard. Even magic-sys-rq isn't possible, only hard switch-off.
  From smartmontools I can exclude a hardware failure.

  I've found that gpu-manager and systemd fail to load kernel modules.
  This is among the output of journalctl | grep modules
  Jan 10 13:12:34  systemd[1]: systemd-modules-load.service: Unit entered 
failed state.
  Jan 10 13:12:34  systemd[1]: systemd-modules-load.service: Failed with result 
'exit-code'.
  Jan 10 13:12:49  gpu-manager[791]: Error: can't open 
/lib/modules/4.4.0-57-generic/updates/dkms
  Jan 10 13:12:49  gpu-manager[791]: Error: can't open 
/lib/modules/4.4.0-57-generic/updates/dkms
  (terminal-output attached)

  dito with latest kernel

  Jan 11 07:53:04 gpu-manager[786]: Error: can't open 
/lib/modules/4.4.0-59-generic/updates/dkms
  Jan 11 07:53:04 gpu-manager[786]: Error: can't open 
/lib/modules/4.4.0-59-generic/updates/dkms

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-drivers-common 1:0.4.17.2
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 10 14:37:00 2017
  InstallationDate: Installed on 2012-02-05 (1801 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120204)
  SourcePackage: ubuntu-drivers-common
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (162 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1655348/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Rohan Paul]

Sorry, but this works only with my headset plugged in. If my headset is
not plugged in, then the mic again does not work. So #3 is a partial
solution.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Rohan Paul]

I managed to solve the issue by downloading the .deb file specified here
- https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1523100/comments/72. After installing it and then rebooting,
the mic started picking up sound.

NOTE: The complete solution involves: 
1. setting the internal microphone to be mapped to the pin 0x12 using 
alsa-tools-gui (hdajackretask) and then rebooting
2. Downloading and installing the .deb file mentioned above and then rebooting.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1812883] Re: Desktop view flashes every time ~/Desktop changes

[Roger James]

The extension is only fully removed if you purge it and reboot your
system.

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

Title:
  Desktop view flashes every time ~/Desktop changes

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  All of the icons on my desktop visibly flash every time I change
  anything in the folder ~/Desktop, even if the change is not something
  that is visible on my desktop.

  For example, "touch ~/Desktop/.#foo".

  I mean, the icons that haven't changed should never flash at all, even
  if a change is made that _does_ affect the visible display -- only the
  things that are actually new or different should change their
  appearance, and everything else should remain the same and not flash.
  But at the very least, there should be no flash when there are no
  visible changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: nautilus 1:3.30.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 22 11:38:30 2019
  InstallationDate: Installed on 2019-01-02 (20 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1812883/+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 1755538] Re: Invisible mouse cursor on login screen

[Daniel van Vugt]

** No longer affects: gdm3 (Ubuntu)

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #68
   https://gitlab.gnome.org/GNOME/mutter/issues/68

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/68
   Importance: Unknown
   Status: Unknown

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

Title:
  Invisible mouse cursor on login screen

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/mutter/issues/68

  ---

  Frequently, but not always, the mouse cursor is invisible in the login
  screen. I can move it, as when passing over a button it lights up, but
  I can't see where the cursor is.

  Once on the desktop, the problems are gone.

  I am running Ubuntu 18.04 dev on a Dell XPS 9360 FHD.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.27.92-0ubuntu1
  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: ubuntu-communitheme:ubuntu:GNOME
  Date: Tue Mar 13 10:30:38 2018
  InstallationDate: Installed on 2018-02-23 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1755538/+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