[Desktop-packages] [Bug 1801151] Re: firefox scrollbar in ubuntu mate

[Launchpad Bug Tracker]

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

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

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

Title:
  firefox scrollbar in ubuntu mate

Status in Mozilla Firefox:
  Incomplete
Status in firefox package in Ubuntu:
  Expired

Bug description:
  I want to report 3 bugs related to Firefox browser in Ubuntu Mate
  18.04 and 18.10:

  1- The scrollbar width is so small. And I do not know how to increase
  it.

  2- When I click in empty scrollbar in firefox, the bar goes directly
  to the place instead of goes down screen by screen.

  3- the scale display in firefox and in the whole Ubuntu Mate is so
  bad. all sentences are so small. Could you make the scale display and
  firefox work like in Kubuntu because in Kubuntu the firefox and scale
  display work great.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1801151/+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 1828606] Re: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'

[Bug Watch Updater]

** Changed in: gvfs
   Status: Unknown => New

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

Title:
  Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access
  based share enumeration = yes'

Status in gvfs:
  New
Status in gvfs package in Ubuntu:
  New

Bug description:
  From Ubuntu 18.04's GUI, if I open the "Files" app and go to "Other
  Locations", I see my samba/SMB server. If I double click it, it then
  lists *some* of my shares. Specifically, it lists those where I didn't
  use Samba's 'access based share enumeration = yes'[1] (which allows
  some shares to be made completely invisible to some users). Note that
  Ubuntu has *not* yet asked me to authenticate, so it makes sense that
  I shouldn't yet be able to see shares I'm not entitled to.

  The bug is: even after I authenticate (and let it remember my
  password), then go back to Other Locations>MyServer, it *still*
  doesn't show the other shares. In fact, I can't find *any* way to see
  the other shares.

  Contrast this with macOS Finder. If I navigate to MyServer in the
  share list, it doesn't show *any* shares until I authenticate, then it
  shows *all* shares that the user has access to (and none of the shares
  the user doesn't have access to).

  Ubuntu could either:
   - adopt macOS Finder behaviour and get authentication first, or
   - update the share list after authentication is performed.

  Its current behaviour makes some shares totally inaccessible (the crux
  of the bug).

  I doubt it matters, but my server is: FreeNAS 11.2-U4 (current newest)
  using ZFS, running samba 4.9.6.  Other users on the FreeNAS forum see
  the same behaviour[2], so it's not particular to my setup.

  [1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
  [2] 
https://www.ixsystems.com/community/threads/accessing-smb-shares-from-ubuntu-18-04-doesnt-show-all-shares-in-gui.75961/

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1828606/+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 1829256] Re: [Dell Vostro 5568] Cannot find display brightness settings anywhere

[Daniel van Vugt]

Your screenshot seems to show an HP ZBook 17 G5. But this bug was
reported from a Dell Vostro 5568.

Please tell us which machine is affected. If it is the HP then we will
need to close this bug and ask you to open a new bug from that machine
instead.

** Summary changed:

- Cannot find display brightness settings anywhere
+ [Dell Vostro 5568] Cannot find display brightness settings anywhere

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  [Dell Vostro 5568] Cannot find display brightness settings anywhere

Status in Ubuntu:
  Incomplete

Bug description:
  Ubuntu:

  Description:  Ubuntu 19.04
  Release:  19.04

  xorg:
Instalovaná verze: 1:7.7+19ubuntu12
Kandidát:  1:7.7+19ubuntu12
Tabulka verzí:
   *** 1:7.7+19ubuntu12 500
  500 http://cz.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 15 11:12:23 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   als, master, 4.18.0-20-generic, x86_64: installed
   als, master, 5.0.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0786]
  MachineType: Dell Inc. Vostro 5568
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0HG2TP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd10/04/2018:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn0HG2TP:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5568
  dmi.product.sku: 0786
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1829256/+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 1829228] Re: boot time is too long and running HD videos starts flickering

[Daniel van Vugt]

Please be careful to only report one problem per bug. I will make this
bug just about the long boot time. If you want to discuss the other
issue then please open another bug.

Your long boot time appears to be multiple problems in the kernel log
(CurrentDmesg.txt). I can't quite put my finger on just one cause
though.

Now reassigning this bug to the kernel.

** Summary changed:

- boot time is too long and running HD videos starts flickering
+ boot time is too long

** Package changed: xorg (Ubuntu) => linux (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/1829228

Title:
  boot time is too long

Status in linux package in Ubuntu:
  New

Bug description:
  boot time is too long and running HD videos starts flickering

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01: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)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May 15 17:25:35 2019
  DistUpgraded: 2018-09-28 10:50:13,399 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.15.0-48-generic, x86_64: installed
   nvidia, 390.116, 4.15.0-50-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:39c7]
 Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:39c7]
  InstallationDate: Installed on 2018-03-31 (409 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=998b8ab4-3e79-4347-99f7-06c2fadbd335 ro quiet splash noresume 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (229 days ago)
  dmi.bios.date: 10/23/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN36WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN36WW:bd10/23/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: ideapad 320-15IKB
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  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: Tue May 14 07:06:58 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829228/+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 1827428] Re: Mouse cursor left frozen copy of itself

[Daniel van Vugt]

** Summary changed:

- Mouse cursor left freezed copy of itself
+ Mouse cursor left frozen copy of itself

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

Title:
  Mouse cursor left frozen copy of itself

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Mouse cursor left freezed copy of itself over all the windows after
  login after lock screen. Functionality is not broken. It's just not
  aesthetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 16:10:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] 
[103c:8392]
  InstallationDate: Installed on 2019-04-29 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 17-an0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8392
  dmi.board.vendor: HP
  dmi.board.version: 40.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-an0xx
  dmi.product.sku: 2FP35EA#ACB
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+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 1827428] Re: Mouse cursor left freezed copy of itself

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Mouse cursor left frozen copy of itself

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Mouse cursor left freezed copy of itself over all the windows after
  login after lock screen. Functionality is not broken. It's just not
  aesthetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 16:10:09 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] 
[103c:8392]
  InstallationDate: Installed on 2019-04-29 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP OMEN by HP Laptop 17-an0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/21/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.05
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8392
  dmi.board.vendor: HP
  dmi.board.version: 40.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP OMEN
  dmi.product.name: OMEN by HP Laptop 17-an0xx
  dmi.product.sku: 2FP35EA#ACB
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+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 1829221] Re: second, dead, mouse pointer left on screen after login, x11 session

[Daniel van Vugt]

*** This bug is a duplicate of bug 1827428 ***
https://bugs.launchpad.net/bugs/1827428

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1827428, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Tags added: xrandr-scaling

** Tags added: cursor

** This bug has been marked a duplicate of bug 1827428
   Mouse cursor left freezed copy of itself

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

Title:
  second, dead, mouse pointer left on screen after login, x11 session

Status in mutter package in Ubuntu:
  New

Bug description:
  This seems to have become repeatable, and applies even on the first
  login session immediately after booting the computer. I don't know if
  this is the right package to report against; another possible culprit:
  gdm:

  When I log into the default "Ubuntu" session (ie: on xorg), gdm's
  mouse pointer remains on screen during the screen blank, and after the
  gnome desktop comes up. It stays on the top just like you'd expect of
  the mouse pointer, but it's immobile and unresponsive. It's left at
  the same position on the screen that it was while using gdm, and is
  the same size as it was in gdm (ie: gdm is not scaled, but gnome
  session desktop scaled to 150% - the *working* in-session mouse
  pointer is also 150% larger than gdm's dead one).

  It looks like gdm and gnome are running in the same x11 session?
  Seeing as the mouse pointer stays solid *during* the transition from
  gdm into the gnome desktop. Not even a flicker. It's almost as if
  we're trying to have smooth transitions for these sorts of things,
  which is good of course, but maybe is a bug in that?

  It disappears when I log into a Wayland session, it appears only to
  affect x11 sessions.

  I've taken to just moving the mouse pointer to the far bottom right
  corner of the screen before logging in, so at least it's not very
  intrusive.

  There are a few reports of similar in askubuntu from a few years back,
  but with no helpful or applicable solution. eg:

  
https://askubuntu.com/questions/521241/i-have-two-cursors-on-my-screen-one-of-which-is-always-on-top-and-will-never-mo
  
https://askubuntu.com/questions/598096/14-04-second-mouse-pointer-stuck-in-middle-of-the-screen

  To answer the points made there, the xinput --list output is shown
  below. Executing that command and rebooting makes no difference. In
  the Displays Prefs there is no second "Unknown" display to disable.
  (The machine has precisely one display, and that's all Settings sees.
  It's a desktop, not a laptop, and it only has an AMD Vega integrated
  graphics. It also has only one mouse.)

  rachel@twilight:~$ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ HID 04b4:3003 Mouse id=9[slave  pointer 
 (2)]
  ⎜   ↳ HID 04b4:3003 Consumer Control  id=11   [slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Mouseid=15   [slave  
pointer  (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=16   
[slave  pointer  (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=17   
[slave  pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ HID 04b4:3003   id=8[slave  
keyboard (3)]
  ↳ HID 04b4:3003 System Controlid=10   [slave  
keyboard (3)]
  ↳ HID 04b4:3003 Keyboard  id=12   [slave  
keyboard (3)]
  ↳ Dell Dell AC511 USB SoundBarid=13   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0  id=14   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0 System Control   id=18   
[slave  keyboard (3)]
  ↳ Eee PC WMI hotkeys  id=19   [slave  
keyboard (3)]
  ↳ HID 04b4:3003 Consumer Control  id=20   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=21   
[slave  keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiv

[Desktop-packages] [Bug 1773502] Re: High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's Resources tab

[Daniel van Vugt]

AFAIK, gnome-system-monitor is one of those rare apps which are software
rendered (because GTK) but also try to animate at a smooth frame rate.

It's a rare combination and a useful test case.

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  gnome-shell or X.org using high cpu
  My fanless nettop use a Intel Celeron 847 CPU. On around 1 boot on 3, the CPU 
of one core is kept at 100 % by a process, this high CPU usage start few second 
after the boot. It seems related to the graphical system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 09:52:20 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773502/+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 1828846] Re: ecra

[Steve Beattie]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  ecra

Status in xorg package in Ubuntu:
  New

Bug description:
  Notebook hp elitebook 8440p com sensor de rotação da tela, ao instalar 
ubuntu19 ele reconhece a tela virada 180 graus e o ponteiro do mouse no 
sentindo certo.
  Ao tentar inverter a tela através de comandos ou configuração ela vira porem 
o mouse ainda fica invertido.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 15:54:42 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:172a]
  MachineType: Hewlett-Packard HP EliteBook 8440p
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=3a114823-2ff8-428d-8823-ecbf3fb1e030 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.0B
  dmi.board.name: 172A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.2C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.0B:bd06/02/2010:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.2C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8440p
  dmi.product.sku: SJ905UP#ABA
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1828846/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Dan Streetman]

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

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

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

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

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

** Changed in: systemd (Ubuntu Eoan)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

** Changed in: systemd (Ubuntu Disco)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

** Changed in: systemd (Ubuntu Cosmic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Tags added: ddstreet-next

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress
Status in udisks2 package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress
Status in udisks2 source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  In Progress
Status in udisks2 source package in Cosmic:
  New
Status in linux source package in Disco:
  New
Status in systemd source package in Disco:
  In Progress
Status in udisks2 source package in Disco:
  Invalid
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  In Progress
Status in udisks2 source package in Eoan:
  Invalid

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1827451] Re: Japanese new era "Reiwa(令和)" support

[Ikuya Awashiro]

> Is this really a sufficient test case?

Yes."R" means "令和".

If you want to show "令和1年5月1日", they should be

 5. Set “Format" to "平成11年12月31日"
 6. Cell should show "令和1年5月1日" (not "Naruhito1年5月1日”or "平成31年5月1日")

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

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

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice-l10n package in Ubuntu:
  Fix Released
Status in libreoffice source package in Xenial:
  In Progress
Status in libreoffice source package in Bionic:
  In Progress
Status in libreoffice source package in Cosmic:
  Fix Committed
Status in libreoffice-l10n source package in Cosmic:
  Fix Committed

Bug description:
  Japanese new era "Reiwa(令和)" has began at 2019-05-01.
  These patches add Reiwa support for Libreoffice Bionic/Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  3 10:44:42 2019
  InstallationDate: Installed on 2018-07-21 (285 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release 
amd64(20180506.1)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

  [Impact]

   * This effects all users who use the Japanese era date format in
  LibreOffice.

   * The fix is currently in LibreOffice 6.2.3 on eoan.

  [Test Case]

   1. Start Calc
   2. Put "01/05/2019" into a cell
   3. Right-click on the cell and select "Format Cells"
   4. Set “Language" to "Japanese"
   5. Set “Format" to "H11.12.31"
   6. Cell should show "R1.05.01" (not "N1.05.01”)

  [Regression Potential]

   * The fix is minor so potential for regression is low.

   * A combination of autopkgtests and manual testing as described above
  should provide reasonable confidence that no regressions sneaked in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1827451/+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 1828108] Re: GNOME default to a document font not installed by Ubuntu

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings - 19.04.3.1

---
ubuntu-settings (19.04.3.1) disco; urgency=medium

  * ubuntu-settings.gsettings-override:
- set the document font to 'Sans 11' for Ubuntu, the GNOME default
  changed to Cantarell which is not installed for us (lp: #1828108)

 -- Sebastien Bacher   Tue, 07 May 2019 20:19:36
+0200

** Changed in: ubuntu-settings (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  GNOME default to a document font not installed by Ubuntu

Status in gnome-flashback package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Disco:
  Fix Released

Bug description:
  * Impact

  The document font changed in GNOME 3.31 to be 'Cantarell 11' but that
  font is not installed in Ubuntu so a fallback font is used instead.

  * Test case
  Install gnome-tweaks and look at the document font, it should be 'Sans 11' 
and not 'undefined'

  * Regression potential
  It's just changing the default value to be what it was before, the impact 
should be low (the UI is going to look different in place where the fallback 
was used but that's what the fix is about)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1828108/+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 1825447] Update Released

[Brian Murray]

The verification of the Stable Release Update for gnome-shell-extension-
appindicator 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 gnome-shell-extension-appindicator in
Ubuntu.
https://bugs.launchpad.net/bugs/1825447

Title:
  Indicators Scroll events are not emitted in 19.04

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Disco:
  Fix Released

Bug description:
  [ Impact ]

  Scroll events aren't delivered to app-indicators

  [ Test case ]
   - Run an indicator that supports scroll events (i.e. radiotray-ng or run
 
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js
 with gjs
   - Scroll events should be delivered

  [ Regression potential ]

  Scroll events over other shell actors aren't working (i.e. changing volume 
with scroll)
   

  ---

  It appears the code used in the 19.04 packaging of the appindicator is
  from master and not the tagged ubuntu-19.04 commit from the ubuntu
  branch. The master branch is not delivering scroll events, which stops
  my application (radiotray-ng) from being able to adjust its volume
  levels.

  I've swapped out the code under /usr/share/gnome-shell/extensions
  /ubuntu-appindicat...@ubuntu.com/ with the ubuntu branch and scrolling
  on an indicator icon works again.

  I've filed an issue on github as well.

  https://github.com/ubuntu/gnome-shell-extension-
  appindicator/issues/169

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1825447/+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 1813471] Re: Thunderbird crashes with GTK_USE_PORTAL environment variable.

[Bug Watch Updater]

** Changed in: thunderbird
   Importance: Medium => Critical

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

Status in Mozilla Thunderbird:
  New
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1813471/+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 1825447] Re: Indicators Scroll events are not emitted in 19.04

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell-extension-appindicator -
29-1~ubuntu19.04.1

---
gnome-shell-extension-appindicator (29-1~ubuntu19.04.1) disco; urgency=medium

  * Backport from eoan to fix LP: #1825447

gnome-shell-extension-appindicator (29-1) experimental; urgency=medium

  [ Matteo F. Vescovi ]
  * New upstream release

  [ Marco Trevisan (Treviño) ]
  * dbusMenu: Fix indentation
  * testTool: Remove trailing spaces
  * testTool: Add item to toggle attention
  * testTool: Log signals to terminal
  * appIndicator: Connect to scroll-event signal.
Fixes #169

 -- Iain Lane   Tue, 30 Apr 2019 11:11:16
+0100

** Changed in: gnome-shell-extension-appindicator (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  Indicators Scroll events are not emitted in 19.04

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Disco:
  Fix Released

Bug description:
  [ Impact ]

  Scroll events aren't delivered to app-indicators

  [ Test case ]
   - Run an indicator that supports scroll events (i.e. radiotray-ng or run
 
https://github.com/ubuntu/gnome-shell-extension-appindicator/blob/master/indicator-test-tool/testTool.js
 with gjs
   - Scroll events should be delivered

  [ Regression potential ]

  Scroll events over other shell actors aren't working (i.e. changing volume 
with scroll)
   

  ---

  It appears the code used in the 19.04 packaging of the appindicator is
  from master and not the tagged ubuntu-19.04 commit from the ubuntu
  branch. The master branch is not delivering scroll events, which stops
  my application (radiotray-ng) from being able to adjust its volume
  levels.

  I've swapped out the code under /usr/share/gnome-shell/extensions
  /ubuntu-appindicat...@ubuntu.com/ with the ubuntu branch and scrolling
  on an indicator icon works again.

  I've filed an issue on github as well.

  https://github.com/ubuntu/gnome-shell-extension-
  appindicator/issues/169

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1825447/+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 1828108] Update Released

[Brian Murray]

The verification of the Stable Release Update for ubuntu-settings 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 ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1828108

Title:
  GNOME default to a document font not installed by Ubuntu

Status in gnome-flashback package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Disco:
  Fix Released

Bug description:
  * Impact

  The document font changed in GNOME 3.31 to be 'Cantarell 11' but that
  font is not installed in Ubuntu so a fallback font is used instead.

  * Test case
  Install gnome-tweaks and look at the document font, it should be 'Sans 11' 
and not 'undefined'

  * Regression potential
  It's just changing the default value to be what it was before, the impact 
should be low (the UI is going to look different in place where the fallback 
was used but that's what the fix is about)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1828108/+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 1828606] Re: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'

[Sean McBride]

https://gitlab.gnome.org/GNOME/gvfs/issues/398

** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #398
   https://gitlab.gnome.org/GNOME/gvfs/issues/398

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

Title:
  Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access
  based share enumeration = yes'

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  New

Bug description:
  From Ubuntu 18.04's GUI, if I open the "Files" app and go to "Other
  Locations", I see my samba/SMB server. If I double click it, it then
  lists *some* of my shares. Specifically, it lists those where I didn't
  use Samba's 'access based share enumeration = yes'[1] (which allows
  some shares to be made completely invisible to some users). Note that
  Ubuntu has *not* yet asked me to authenticate, so it makes sense that
  I shouldn't yet be able to see shares I'm not entitled to.

  The bug is: even after I authenticate (and let it remember my
  password), then go back to Other Locations>MyServer, it *still*
  doesn't show the other shares. In fact, I can't find *any* way to see
  the other shares.

  Contrast this with macOS Finder. If I navigate to MyServer in the
  share list, it doesn't show *any* shares until I authenticate, then it
  shows *all* shares that the user has access to (and none of the shares
  the user doesn't have access to).

  Ubuntu could either:
   - adopt macOS Finder behaviour and get authentication first, or
   - update the share list after authentication is performed.

  Its current behaviour makes some shares totally inaccessible (the crux
  of the bug).

  I doubt it matters, but my server is: FreeNAS 11.2-U4 (current newest)
  using ZFS, running samba 4.9.6.  Other users on the FreeNAS forum see
  the same behaviour[2], so it's not particular to my setup.

  [1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
  [2] 
https://www.ixsystems.com/community/threads/accessing-smb-shares-from-ubuntu-18-04-doesnt-show-all-shares-in-gui.75961/

To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/1828606/+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 1828606] Re: Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access based share enumeration = yes'

[Andre Klapper]

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

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

Title:
  Ubuntu 18.04 "Files" app unable to show Samba/SMB shares where 'access
  based share enumeration = yes'

Status in gvfs:
  Unknown
Status in gvfs package in Ubuntu:
  New

Bug description:
  From Ubuntu 18.04's GUI, if I open the "Files" app and go to "Other
  Locations", I see my samba/SMB server. If I double click it, it then
  lists *some* of my shares. Specifically, it lists those where I didn't
  use Samba's 'access based share enumeration = yes'[1] (which allows
  some shares to be made completely invisible to some users). Note that
  Ubuntu has *not* yet asked me to authenticate, so it makes sense that
  I shouldn't yet be able to see shares I'm not entitled to.

  The bug is: even after I authenticate (and let it remember my
  password), then go back to Other Locations>MyServer, it *still*
  doesn't show the other shares. In fact, I can't find *any* way to see
  the other shares.

  Contrast this with macOS Finder. If I navigate to MyServer in the
  share list, it doesn't show *any* shares until I authenticate, then it
  shows *all* shares that the user has access to (and none of the shares
  the user doesn't have access to).

  Ubuntu could either:
   - adopt macOS Finder behaviour and get authentication first, or
   - update the share list after authentication is performed.

  Its current behaviour makes some shares totally inaccessible (the crux
  of the bug).

  I doubt it matters, but my server is: FreeNAS 11.2-U4 (current newest)
  using ZFS, running samba 4.9.6.  Other users on the FreeNAS forum see
  the same behaviour[2], so it's not particular to my setup.

  [1] https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html
  [2] 
https://www.ixsystems.com/community/threads/accessing-smb-shares-from-ubuntu-18-04-doesnt-show-all-shares-in-gui.75961/

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

[Vseerror]

(In reply to Alessandro Menti from comment #13)
> I confirm I'm seeing the crash as well on TB 60.5.3 - since the Arch Linux 
> build does not have debug symbols enabled, I'm recompiling the package to see 
> if I can get a proper backtrace.

Alessandro recompiling from 
http://ftp.mozilla.org/pub/thunderbird/releases/60.6.1/linux-x86_64/ ? 
Did you have success?

And does this also happen with Firefox?

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

Title:
  Thunderbird crashes with GTK_USE_PORTAL environment variable.

Status in Mozilla Thunderbird:
  New
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Crash happens at startup, even for a new profile, as long as any
  e-mail accounts are configured.

  In profile creation mode, the crash happens as soon as an e-mail
  account is added.

  If all e-mail accounts are removed from prefs.js, then Thunderbird
  doesn't crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2619 F pulseaudio
   /dev/snd/controlC0:  vectro 2619 F pulseaudio
  BuildID: 20190116085154
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Sun Jan 27 06:55:37 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefSources: prefs.js
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-03-23 (309 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  IpRoute:
   default via 172.20.0.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600
  MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127
  Profile1Extensions: extensions.sqlite corrupt or missing
  Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile1Locales: extensions.sqlite corrupt or missing
  Profile1PrefSources: prefs.js
  Profile1Prefs:
   extensions.lastAppVersion: "60.4.0" (prefs.js)
   network.cookie.prefsMigrated: true (prefs.js)
   places.history.expiration.transient_current_max_pages: 104858 (prefs.js)
  Profile1Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile0 (Default) - LastVersion=60.4.0/20190116085154
   Profile1 - LastVersion=60.4.0/20190116085154
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1813471/+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 1828116] Re: Password works uppercase and lowercase

[Sebastien Bacher]

Does it happen with simple password? like if you "sudo passwd " and set 
"one" does it log in using "ONE"?
Can you also add the journalctl log after getting the issue and the output of 
"dpkg -l | grep pam"

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

Title:
  Password works uppercase and lowercase

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

Bug description:
  When I log in on the console, I can type my password either uppercase
  or lowercase. I can log in regardless.

  $ uname -a
  4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  Ubuntu 18.04 patched as of today.

  $ sudo cat /etc/shadow | grep $USER
  ...:$6$...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-06 (94 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.3-0ubuntu18.04.4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1828116/+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 487720] Re: Restore fails with "Invalid data - SHA1 hash mismatch"

[The Great Gazauga]

This is absolutely still an issue in the latest versions of Ubuntu.

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

Title:
  Restore fails with "Invalid data - SHA1 hash mismatch"

Status in Déjà Dup:
  Invalid
Status in Duplicity:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released
Status in duplicity source package in Lucid:
  Fix Released
Status in duplicity source package in Maverick:
  Won't Fix
Status in duplicity source package in Natty:
  Fix Released

Bug description:
  When restoring a backup, one might see an error like:

  Invalid data - SHA1 hash mismatch:
  Calculated hash: 0b2bc4c2fb98b36f9891f9172f909d70ab5662e9
  Manifest hash: 11cd330357618de52e4e5361a6e63b09ee951ae2

  This can happen when a volume file was not completely written to the
  backend before duplicity was interrupted (say, shutting down the
  machine or whatever).  When duplicity resumes the backup next run, it
  will start with the next volume.  The half-complete volume file will
  sit on the backend and cause this error later when restoring.

  You can manually recover from this by either restoring from your older
  backup sets or by restoring individual files that don't happen to be
  in the corrupted volume.

  == To Reproduce ==

  See attachment
  
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/487720/+attachment/2159465/+files/test.sh
  for a test script tor reproduce the problem.

  == Ubuntu SRU Justification ==

  This is a serious data loss problem for users, which won't be noticed
  until they try to restore.  With Ubuntu 11.10 including Deja Dup, some
  users may think to back up their data first then upgrade, and may
  accidentally create corrupted backups.

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/487720/+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 1822062] Re: Race condition on boot between cups and sssd

[Launchpad Bug Tracker]

This bug was fixed in the package cups - 2.2.7-1ubuntu2.5

---
cups (2.2.7-1ubuntu2.5) bionic; urgency=medium

  * d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if
installed (LP: #1822062)

 -- Victor Tapia   Wed, 24 Apr 2019 16:58:30
+0200

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

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released
Status in cups source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1822062] Re: Race condition on boot between cups and sssd

[Launchpad Bug Tracker]

This bug was fixed in the package cups - 2.2.8-5ubuntu1.3

---
cups (2.2.8-5ubuntu1.3) cosmic; urgency=medium

  * d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if
installed (LP: #1822062)

 -- Victor Tapia   Wed, 24 Apr 2019 17:21:13
+0200

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

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

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released
Status in cups source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1822062] Re: Race condition on boot between cups and sssd

[Launchpad Bug Tracker]

This bug was fixed in the package cups - 2.1.3-4ubuntu0.8

---
cups (2.1.3-4ubuntu0.8) xenial; urgency=medium

  * d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if
installed (LP: #1822062)

 -- Victor Tapia   Tue, 23 Apr 2019 17:44:19
+0200

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released
Status in cups source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1822062] Re: Race condition on boot between cups and sssd

[Launchpad Bug Tracker]

This bug was fixed in the package cups - 2.2.10-4ubuntu1

---
cups (2.2.10-4ubuntu1) disco; urgency=medium

  * d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if
installed (LP: #1822062)

 -- Victor Tapia   Wed, 24 Apr 2019 17:02:49
+0200

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

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released
Status in cups source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1829298] [NEW] File, Edit, View, Etc Application menu is missing since update. profile reset & reinstall does nothing

[Mark Underwood]

Public bug reported:

I believe this has occurred since the last update, but this did not
occur on a machine I use.

I've tried renaming the profile and tried reinstalling libreoffice via
synaptic.

1) $ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04

2) $ apt-cache policy libreoffice
libreoffice:
  Installed: 1:6.0.7-0ubuntu0.18.04.5
  Candidate: 1:6.0.7-0ubuntu0.18.04.5
  Version table:
 *** 1:6.0.7-0ubuntu0.18.04.5 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 1:6.0.3-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

3) There should be an application menu in all sub programs of
libreoffice.

4) Writer, Calc, Impress, Math, etc do not have the top menu: File,
Edit, View, etc.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice 1:6.0.7-0ubuntu0.18.04.5
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed May 15 16:01:55 2019
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot of libreoffice window"
   
https://bugs.launchpad.net/bugs/1829298/+attachment/5264119/+files/LibreofficeMenuMissing.jpeg

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

Title:
  File,Edit,View,Etc Application menu is missing since update. profile
  reset & reinstall does nothing

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I believe this has occurred since the last update, but this did not
  occur on a machine I use.

  I've tried renaming the profile and tried reinstalling libreoffice via
  synaptic.

  1) $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  2) $ apt-cache policy libreoffice
  libreoffice:
Installed: 1:6.0.7-0ubuntu0.18.04.5
Candidate: 1:6.0.7-0ubuntu0.18.04.5
Version table:
   *** 1:6.0.7-0ubuntu0.18.04.5 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   1:6.0.3-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) There should be an application menu in all sub programs of
  libreoffice.

  4) Writer, Calc, Impress, Math, etc do not have the top menu: File,
  Edit, View, etc.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice 1:6.0.7-0ubuntu0.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed May 15 16:01:55 2019
  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/1829298/+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 1822062] Update Released

[Brian Murray]

The verification of the Stable Release Update for cups 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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1822062

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released
Status in cups source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

[Tim Richardson]

This works. Thanks. What does gdm3 do that requires this?

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

Title:
  gdm3, hybrid nvidia with modeset=1, no external monitors detected

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gdm3 package in Debian:
  New

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1825946] Re: 'nm' autopkgtest fails due to GI stderr output

[Dan Streetman]

> could you also add the patch which fixes bug 1754671

Can you create a debdiff?  It's not clear to me which patch, exactly,
fixes that bug; the upload containing the fix contains a large amount of
changes.

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

Title:
  'nm' autopkgtest fails due to GI stderr output

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  [impact]

  'nm' testcase contains:
  from gi.repository import NetworkManager, NMClient, GLib  


 

  which generates output to stderr:
  /tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning: 
NetworkManager was imported without specifying a version first. Use 
gi.require_version('NetworkManager', '1.0') before import to ensure that the 
right version gets loaded.

  the gi.require_version call has already been added to cosmic and
  disco.

  [test case]

  see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
  results.

  [other info]

  this only fails intermittently, but the failure is clearly not an
  actual problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1825946/+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 1828116] Re: Password works uppercase and lowercase

[G S]

I keep fully updating with `apt`; you can assume I'm running the latest
official stable releases

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

Title:
  Password works uppercase and lowercase

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

Bug description:
  When I log in on the console, I can type my password either uppercase
  or lowercase. I can log in regardless.

  $ uname -a
  4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  Ubuntu 18.04 patched as of today.

  $ sudo cat /etc/shadow | grep $USER
  ...:$6$...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-06 (94 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.3-0ubuntu18.04.4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1828116/+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 1828116] Re: Password works uppercase and lowercase

[G S]

> Do you get the issue in the lock screen as well on only on the boot greeter?
Yes

> Could you try adding another user to the system and see if it has the
same bug?

Here are my steps:
1. Add a new user with a password made of lowercase, numbers and a % sign
1. Lock the screen
1. "Login as another user"
1. Use the lowercase password
1. Logged in 
1. Lock the screen
1. Use the same password, with capslock on
1. Logged in

To be clear, it works when:
* There is an external keyboard connected to the laptop and I use the external 
keyboard
* There is an external keyboard connected to the laptop and I use the internal 
keyboard
* There is no external keyboard connected to the laptop and I use the internal 
keyboard

If you have any pointers, I'm happy to help by providing logs and
looking at/building some code. I won't touch any config until we sort
this out

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

Title:
  Password works uppercase and lowercase

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

Bug description:
  When I log in on the console, I can type my password either uppercase
  or lowercase. I can log in regardless.

  $ uname -a
  4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  Ubuntu 18.04 patched as of today.

  $ sudo cat /etc/shadow | grep $USER
  ...:$6$...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-06 (94 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.3-0ubuntu18.04.4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1828116/+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 1802622] Re: Ubuntu Cosmic nvidia-340 needs patch for "Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t'

[Ubuntu Foundations Team Bug Bot]

The attachment "kmem_cache_create_usercopy.patch" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Ubuntu Cosmic nvidia-340 needs patch for "Bad or missing usercopy
  whitelist? Kernel memory exposure attempt detected from SLUB object
  'nvidia_stack_t'

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  New

Bug description:
  Since upgrading from Ubuntu 18.04 Bionic to Ubuntu 18.10 Cosmic, I've
  started seeing issues with getting into Xorg.

  My config:

  01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] 
(rev a2) (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd G92 [GeForce GTS 250]

  System Information
  Manufacturer: Gigabyte Technology Co., Ltd.
  Product Name: P55A-UD4

  Ubuntu 18.04 Cosmic w/nvidia-340 proprietary drivers.

  This appears to be, in part, due to a newer kernel with stricter
  permissions around kernel access.

  This seems to have been fixed in Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88
  ... by backporting the fix from nvidia-390:
  https://bugzilla.redhat.com/show_bug.cgi?id=1570493
  https://bugzilla.redhat.com/attachment.cgi?id=1425704

  Could this patch also be applied to nvidia-340 for Ubuntu?

  Error I'm seeing on my own system (from dmesg):

  [   74.596816] resource sanity check: requesting [mem 0x000c-0x000f], 
which spans more than PCI Bus :00 [mem 0x000c-0x000d window]
  [   74.596945] caller os_map_kernel_space+0x9f/0xb0 [nvidia] mapping multiple 
BARs
  [   75.351656] [ cut here ]
  [   75.351661] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size 3)!
  [   75.351675] WARNING: CPU: 7 PID: 4310 at mm/usercopy.c:81 
usercopy_warn+0x81/0xa0
  [   75.351676] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) ipmi_devintf ipmi_msghandler ip6t_REJECT 
nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt snd_hda_codec_realtek 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 input_leds 
nf_log_ipv4 nf_log_common nvidia_uvm(POE) xt_LOG snd_hda_codec_generic 
snd_hda_intel snd_hda_codec intel_powerclamp mxm_wmi snd_hda_core kvm_intel 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event kvm nvidia(POE) snd_rawmidi 
snd_seq snd_seq_device irqbypass drm snd_timer intel_cstate snd xt_limit 
i7core_edac serio_raw soundcore xt_tcpudp mac_hid wmi xt_addrtype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack sch_fq_codel ip6table_filter it87 
hwmon_vid coretemp ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat
  [   75.351718]  parport_pc nf_conntrack_ftp nf_conntrack libcrc32c ppdev 
iptable_filter bpfilter sunrpc lp parport ip_tables x_tables autofs4 pata_acpi 
hid_generic usbhid hid gpio_ich firewire_ohci firewire_core crc_itu_t 
pata_it8213 r8169 lpc_ich i2c_i801 mii ahci libahci
  [   75.351737] CPU: 7 PID: 4310 Comm: Xorg Tainted: P   OE 
4.18.0-11-generic #12-Ubuntu
  [   75.351738] Hardware name: Gigabyte Technology Co., Ltd. 
P55A-UD4/P55A-UD4, BIOS F15 09/16/2010
  [   75.351741] RIP: 0010:usercopy_warn+0x81/0xa0
  [   75.351742] Code: 50 ac 41 51 4d 89 d8 48 c7 c0 89 8d 4f ac 49 89 f1 48 89 
f9 48 0f 45 c2 48 c7 c7 f0 a1 50 ac 4c 89 d2 48 89 c6 e8 f1 cf df ff <0f> 0b 48 
83 c4 18 c9 c3 48 c7 c6 b2 8a 52 ac 49 89 f1 49 89 f3 eb 
  [   75.351773] RSP: 0018:bcc5414f3b58 EFLAGS: 00010282
  [   75.351775] RAX:  RBX: 9eb29383ae58 RCX: 
0006
  [   75.351776] RDX: 0007 RSI: 0092 RDI: 
9eb29fdd64b0
  [   75.351777] RBP: bcc5414f3b70 R08: 0001 R09: 
03e1
  [   75.351778] R10: 0004 R11:  R12: 
0003
  [   75.351779] R13: 0001 R14: 9eb29383ae5b R15: 
9eb29383aea0
  [   75.351781] FS:  7ff9251eca80() GS:9eb29fdc() 
knlGS:
  [   75.351782] CS:  0010 DS:  ES:  CR0: 80050033
  [   75.351783] CR2: 7ff9207ca000 CR3: 00020f3f2000 CR4: 
06e0
  [   75.351785] Call Trace:
  [   75.351791]  __check_heap_object+0xc2/0x110
  [   75.351793]  __check_object_size+0x14c/0x178
  [   75.351936]  os_memcpy_to_user+0x26/0x50 [nvidia]
  [   75.352047]  _nv001372rm+0xa5/0x260 [nvidia]
  [   75.352050] WARNING: kernel stack frame pointer at 8342e4ff 

[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Balint Reczey]

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

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Fix Committed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to be safe, too.

  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $

[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Balint Reczey]

Verified 1.15.5-1ubuntu5.16.04.0 on Xenial:

ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd  | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version Architecture Description
+++-==-===--=
ii  kbd1.15.5-1ubuntu5.16.04.0 amd64Linux console font and 
keytable utilities
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty4; echo 
$?
The keyboard is in Unicode (UTF-8) mode
0
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -a -C /dev/tty4; 
echo $?
0
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -a -C /dev/tty4; 
echo $?
0
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -C /dev/tty4
The keyboard is in xlate (8-bit) mode
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -u -C /dev/tty4; 
echo $?
0
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty4
The keyboard is in Unicode (UTF-8) mode
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -u -C /dev/tty0; 
echo $?
The keyboard is in some unknown mode
Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
0
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -f -u -C /dev/tty0; 
echo $?
0
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty0
The keyboard is in Unicode (UTF-8) mode
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -s -C /dev/tty0
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty0
The keyboard is in raw (scancode) mode
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -u -C /dev/tty0; 
echo $?
The keyboard is in raw (scancode) mode
Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
0
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Fix Committed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboar

[Desktop-packages] [Bug 1802622] Re: Ubuntu Cosmic nvidia-340 needs patch for "Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t'

[satmandu]

This is the patch from debian for this issue. The driver seems to
compile fine with it.


** Patch added: "kmem_cache_create_usercopy.patch"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1802622/+attachment/5264097/+files/kmem_cache_create_usercopy.patch

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

Title:
  Ubuntu Cosmic nvidia-340 needs patch for "Bad or missing usercopy
  whitelist? Kernel memory exposure attempt detected from SLUB object
  'nvidia_stack_t'

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  New

Bug description:
  Since upgrading from Ubuntu 18.04 Bionic to Ubuntu 18.10 Cosmic, I've
  started seeing issues with getting into Xorg.

  My config:

  01:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] 
(rev a2) (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd G92 [GeForce GTS 250]

  System Information
  Manufacturer: Gigabyte Technology Co., Ltd.
  Product Name: P55A-UD4

  Ubuntu 18.04 Cosmic w/nvidia-340 proprietary drivers.

  This appears to be, in part, due to a newer kernel with stricter
  permissions around kernel access.

  This seems to have been fixed in Debian:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88
  ... by backporting the fix from nvidia-390:
  https://bugzilla.redhat.com/show_bug.cgi?id=1570493
  https://bugzilla.redhat.com/attachment.cgi?id=1425704

  Could this patch also be applied to nvidia-340 for Ubuntu?

  Error I'm seeing on my own system (from dmesg):

  [   74.596816] resource sanity check: requesting [mem 0x000c-0x000f], 
which spans more than PCI Bus :00 [mem 0x000c-0x000d window]
  [   74.596945] caller os_map_kernel_space+0x9f/0xb0 [nvidia] mapping multiple 
BARs
  [   75.351656] [ cut here ]
  [   75.351661] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size 3)!
  [   75.351675] WARNING: CPU: 7 PID: 4310 at mm/usercopy.c:81 
usercopy_warn+0x81/0xa0
  [   75.351676] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) ipmi_devintf ipmi_msghandler ip6t_REJECT 
nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt snd_hda_codec_realtek 
nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 input_leds 
nf_log_ipv4 nf_log_common nvidia_uvm(POE) xt_LOG snd_hda_codec_generic 
snd_hda_intel snd_hda_codec intel_powerclamp mxm_wmi snd_hda_core kvm_intel 
snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event kvm nvidia(POE) snd_rawmidi 
snd_seq snd_seq_device irqbypass drm snd_timer intel_cstate snd xt_limit 
i7core_edac serio_raw soundcore xt_tcpudp mac_hid wmi xt_addrtype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack sch_fq_codel ip6table_filter it87 
hwmon_vid coretemp ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_nat_ftp nf_nat
  [   75.351718]  parport_pc nf_conntrack_ftp nf_conntrack libcrc32c ppdev 
iptable_filter bpfilter sunrpc lp parport ip_tables x_tables autofs4 pata_acpi 
hid_generic usbhid hid gpio_ich firewire_ohci firewire_core crc_itu_t 
pata_it8213 r8169 lpc_ich i2c_i801 mii ahci libahci
  [   75.351737] CPU: 7 PID: 4310 Comm: Xorg Tainted: P   OE 
4.18.0-11-generic #12-Ubuntu
  [   75.351738] Hardware name: Gigabyte Technology Co., Ltd. 
P55A-UD4/P55A-UD4, BIOS F15 09/16/2010
  [   75.351741] RIP: 0010:usercopy_warn+0x81/0xa0
  [   75.351742] Code: 50 ac 41 51 4d 89 d8 48 c7 c0 89 8d 4f ac 49 89 f1 48 89 
f9 48 0f 45 c2 48 c7 c7 f0 a1 50 ac 4c 89 d2 48 89 c6 e8 f1 cf df ff <0f> 0b 48 
83 c4 18 c9 c3 48 c7 c6 b2 8a 52 ac 49 89 f1 49 89 f3 eb 
  [   75.351773] RSP: 0018:bcc5414f3b58 EFLAGS: 00010282
  [   75.351775] RAX:  RBX: 9eb29383ae58 RCX: 
0006
  [   75.351776] RDX: 0007 RSI: 0092 RDI: 
9eb29fdd64b0
  [   75.351777] RBP: bcc5414f3b70 R08: 0001 R09: 
03e1
  [   75.351778] R10: 0004 R11:  R12: 
0003
  [   75.351779] R13: 0001 R14: 9eb29383ae5b R15: 
9eb29383aea0
  [   75.351781] FS:  7ff9251eca80() GS:9eb29fdc() 
knlGS:
  [   75.351782] CS:  0010 DS:  ES:  CR0: 80050033
  [   75.351783] CR2: 7ff9207ca000 CR3: 00020f3f2000 CR4: 
06e0
  [   75.351785] Call Trace:
  [   75.351791]  __check_heap_object+0xc2/0x110
  [   75.351793]  __check_object_size+0x14c/0x178
  [   75.351936]  os_memcpy_to_user+0x26/0x50 [nvidia]
  [   75.352047]  _nv001372rm+0xa5/0x260 [nvidia]
  [   75.352050] WARNING: kernel stack frame pointer at 8342e4ff in 
Xorg:4310 has bad value 5ccb4a79
  [   75.352051] unwind stack type:0 next_

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[pekon]

I also confirm that Paco Angulo (3rpako)'s suggestion (#42) worked for
my laptop too. It's Asus with I7 core running Debian-10. Thanks Paco
Angulo.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1798961/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Balint Reczey]

Verified 2.0.4-2ubuntu1.18.04.0 on Bionic:

test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionArchitecture Description
+++-==-==--=
ii  kbd2.0.4-2ubuntu1.18.04.0 amd64Linux console font and 
keytable utilities
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty4; echo $?
The keyboard is in Unicode (UTF-8) mode
0
test@test-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -a -C /dev/tty4; echo 
$?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -a -C /dev/tty4; echo 
$?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -C /dev/tty4
The keyboard is in xlate (8-bit) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -u -C /dev/tty4; echo 
$?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty4
The keyboard is in Unicode (UTF-8) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
The keyboard is in some unknown mode
Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -f -u -C /dev/tty0; 
echo $?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty0
The keyboard is in Unicode (UTF-8) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -s -C /dev/tty0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty0
The keyboard is in raw (scancode) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
The keyboard is in raw (scancode) mode
Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
0
test@test-Standard-PC-i440FX-PIIX-1996:~$

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Fix Committed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo k

[Desktop-packages] [Bug 1813064] Re: nvidia-graphics-drivers-340 340.107-0ubuntu2 ADT test failure with linux 5.0.0-1.2

[satmandu]

There's actually a second patch that is recommended as per the libreelec
tree:

https://github.com/LibreELEC/LibreELEC.tv/blob/9012226b40baa26241069317fdce6174935ca71b/packages/x11/driver/xf86
-video-nvidia-legacy/patches/xf86-video-nvidia-legacy-02-fix-
linux-5.1.patch

I've combined both patches.

** Patch added: "buildfix_kernel_5.1.patch"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1813064/+attachment/5264095/+files/buildfix_kernel_5.1.patch

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

Title:
  nvidia-graphics-drivers-340 340.107-0ubuntu2 ADT test failure with
  linux 5.0.0-1.2

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/amd64/n/nvidia-graphics-drivers-340/20190123_164221_e6b8e@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/i386/n/nvidia-graphics-drivers-340/20190123_165434_e6b8e@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1813064/+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 1813064] Re: nvidia-graphics-drivers-340 340.107-0ubuntu2 ADT test failure with linux 5.0.0-1.2

[satmandu]

The additional patch needed can be modeled off the one at
https://bugs.archlinux.org/task/62610 labeled as nvidia-340xx.patch

I've updated the patch to be additive on top of the
buildfix_kernel_5.0.patch


** Patch added: "buildfix_kernel_5.1.patch"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1813064/+attachment/5264094/+files/buildfix_kernel_5.1.patch

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

Title:
  nvidia-graphics-drivers-340 340.107-0ubuntu2 ADT test failure with
  linux 5.0.0-1.2

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Fix Released

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/amd64/n/nvidia-graphics-drivers-340/20190123_164221_e6b8e@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco-canonical-kernel-team-unstable/disco/i386/n/nvidia-graphics-drivers-340/20190123_165434_e6b8e@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1813064/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

[dwmw2]

These systems are using dnsmasq not systemd-resolver. This was done for
historical reasons; I'm not sure of the specific bug which caused that
choice.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1716857] Re: gdm3, hybrid nvidia with modeset=1, no external monitors detected

[Jeremy Soller]

The solution to this is to run X11 as root, so it can use VGA arbiter
and detect displays on both the NVIDIA and modesetting drivers.

Add this to /etc/X11/Xwrapper.config :
needs_root_rights = yes

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

Title:
  gdm3, hybrid nvidia with modeset=1, no external monitors detected

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in gdm3 package in Debian:
  New

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+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 1754671] Re: Full-tunnel VPN DNS leakage regression

[Till Kamppeter]

dwmw2, did you apply the systemd fix from comment #27? For this bug to
be fixed you need BOTRH the fixed packages of network-manager and
systemd.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Balint Reczey]

Verified 2.0.4-2ubuntu1.18.10.0 on Cosmic:

test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionArchitecture Description
+++-==-==--=
ii  kbd2.0.4-2ubuntu1.18.10.0 amd64Linux console font and 
keytable utilities
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty4; echo $?
The keyboard is in Unicode (UTF-8) mode
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -a -C /dev/tty4; echo 
$?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -C /dev/tty4
The keyboard is in xlate (8-bit) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty4
The keyboard is in Unicode (UTF-8) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
The keyboard is in some unknown mode
Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -f -u -C /dev/tty0; 
echo $?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty0
The keyboard is in Unicode (UTF-8) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -s -C /dev/tty0
test@test-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -C /dev/tty0
The keyboard is in raw (scancode) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -u -C /dev/tty0; echo 
$?
The keyboard is in raw (scancode) mode
Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
0
test@test-Standard-PC-i440FX-PIIX-1996:~$

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Fix Committed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kb

[Desktop-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

[dwmw2]

I am receiving reports that it isn't fixed in 18.04 either. Users are
still seeing DNS lookups on the local network, until they manually edit
the VPN config to include:

[ipv4]
dns-priority=-1
dns-search=~.;

I thought that wasn't going to be necessary?

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Triaged

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1829274] [NEW] ppd file has wrong language after cups update

[pauljohn32]

Public bug reported:

When the cups system is upgraded during an Ubuntu release, the ppd file
for the Konica Minolta printer that I use is replaced.

The PPD file I found on the Konica site starts like this:

```
*PPD-Adobe: "4.3"
*% Linux Version
[cut license]

*FormatVersion: "4.3"
*LanguageVersion: English
*LanguageEncoding: ISOLatin1
*FileVersion: "20002."

*Manufacturer: "KONICA MINOLTA"
*ModelName: "KONICA MINOLTA C451 PS/P"
*ShortNickName: "KONICA MINOLTA C451 PS(P)"
*NickName: "KONICA MINOLTA C451 PS(P)"
*PCFileName: "KOC451UX.ppd"
*Product: "(C451)"
*PSVersion: "(3015.102) 1"
```

When the system upgrade occurs (this has happened several times over the
years), the English language version is replaced by Chinese.

```
*PPD-Adobe: "4.3"
*% Linux Version
*FormatVersion: "4.3"
*LanguageVersion: Simplified Chinese
*LanguageEncoding: None
*FileVersion: "20002."

*Manufacturer: "KONICA MINOLTA"
*ModelName: "KONICA MINOLTA C451 PS/P"
*ShortNickName: "KONICA MINOLTA C451 PS(P)"
*NickName: "KONICA MINOLTA C451 PS(P)"
*PCFileName: "KOC451SCX.ppd"
*Product: "(C451)"
*PSVersion: "(3015.102) 1"
```

I asked about this in the "askubuntu" forum a few months ago, but waited till 
now to say it really is a bug and report to you.
https://askubuntu.com/questions/1038456/printer-config-uses-wrong-language

The bad effect of this is that the printer menus do not have correct
English language labels and options, so you can't see, for example
"Print 2 sided".  You see just question marks and failed efforts to show
Chinese.

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

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

Title:
  ppd file has wrong language after cups update

Status in cups package in Ubuntu:
  New

Bug description:
  When the cups system is upgraded during an Ubuntu release, the ppd
  file for the Konica Minolta printer that I use is replaced.

  The PPD file I found on the Konica site starts like this:

  ```
  *PPD-Adobe: "4.3"
  *% Linux Version
  [cut license]

  *FormatVersion: "4.3"
  *LanguageVersion: English
  *LanguageEncoding: ISOLatin1
  *FileVersion: "20002."

  *Manufacturer: "KONICA MINOLTA"
  *ModelName: "KONICA MINOLTA C451 PS/P"
  *ShortNickName: "KONICA MINOLTA C451 PS(P)"
  *NickName: "KONICA MINOLTA C451 PS(P)"
  *PCFileName: "KOC451UX.ppd"
  *Product: "(C451)"
  *PSVersion: "(3015.102) 1"
  ```

  When the system upgrade occurs (this has happened several times over
  the years), the English language version is replaced by Chinese.

  ```
  *PPD-Adobe: "4.3"
  *% Linux Version
  *FormatVersion: "4.3"
  *LanguageVersion: Simplified Chinese
  *LanguageEncoding: None
  *FileVersion: "20002."

  *Manufacturer: "KONICA MINOLTA"
  *ModelName: "KONICA MINOLTA C451 PS/P"
  *ShortNickName: "KONICA MINOLTA C451 PS(P)"
  *NickName: "KONICA MINOLTA C451 PS(P)"
  *PCFileName: "KOC451SCX.ppd"
  *Product: "(C451)"
  *PSVersion: "(3015.102) 1"
  ```

  I asked about this in the "askubuntu" forum a few months ago, but waited till 
now to say it really is a bug and report to you.
  https://askubuntu.com/questions/1038456/printer-config-uses-wrong-language

  The bad effect of this is that the printer menus do not have correct
  English language labels and options, so you can't see, for example
  "Print 2 sided".  You see just question marks and failed efforts to
  show Chinese.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1829274/+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 1829273] [NEW] Upgrade 18.10 to 19.04 Failed

[Rob Peters]

Public bug reported:

Upgrading ubuntu budgie 18.10 to 19.04 failed on two systems:  Messages
are:

Could not install “Install-info”
Could not install “Libvlc-bin”
Could not install the upgrade the upgrade has aborted.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: install-info 6.5.0.dfsg.1-4build1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Wed May 15 10:07:46 2019
InstallationDate: Installed on 2018-09-30 (226 days ago)
InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180912)
SourcePackage: texinfo
UpgradeStatus: Upgraded to disco on 2019-05-15 (0 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2018-09-30T12:05:22.835880

** Affects: texinfo (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 texinfo in Ubuntu.
https://bugs.launchpad.net/bugs/1829273

Title:
  Upgrade 18.10 to 19.04 Failed

Status in texinfo package in Ubuntu:
  New

Bug description:
  Upgrading ubuntu budgie 18.10 to 19.04 failed on two systems:
  Messages are:

  Could not install “Install-info”
  Could not install “Libvlc-bin”
  Could not install the upgrade the upgrade has aborted.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: install-info 6.5.0.dfsg.1-4build1
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Wed May 15 10:07:46 2019
  InstallationDate: Installed on 2018-09-30 (226 days ago)
  InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Alpha amd64 
(20180912)
  SourcePackage: texinfo
  UpgradeStatus: Upgraded to disco on 2019-05-15 (0 days ago)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2018-09-30T12:05:22.835880

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1829273/+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 1828682] Re: Utility applications are not placed in the Utilities folder

[Gunnar Hjalmarsson]

A handy extension is available:

https://extensions.gnome.org/extension/1217/appfolders-manager/

Maybe it's best to let the users organize their icons themselves.

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

Title:
  Utility applications are not placed in the Utilities folder

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  New

Bug description:
  Some utility applications used in Ubuntu are not placed in the
  Utilities folder. These applications are:

  Language Support
  Software & Updates
  Livepatch
  Software Updater
  Power Statistics
  Startup Applications
  Startup Disk Creator
  Passwords and Keys
  Input Method

  Please, consider moving them to the Utilities folder.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1828682/+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 1829271] [NEW] cups bug with samsung printer

[frenzisys]

Public bug reported:

Saumsung printer need a patch to work with cups because has this issue 
https://github.com/apple/cups/issues/5562#issuecomment-483377904
Need to upgrade to newer version or apply this patch 
https://github.com/apple/cups/commit/8829edfef0d496677a94b0c1b2f08f8e407af444
Thanks

All cups 2.2.10-4xxx in Ubuntu 19.04 published until now have the same
bug

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


** Tags: cups printer samsung

** Description changed:

- Saumsung printer need a patch to work with cups because his this issue 
https://github.com/apple/cups/issues/5562#issuecomment-483377904
+ Saumsung printer need a patch to work with cups because has this issue 
https://github.com/apple/cups/issues/5562#issuecomment-483377904
  Need to upgrade to newer version or apply this patch 
https://github.com/apple/cups/commit/8829edfef0d496677a94b0c1b2f08f8e407af444
  Thanks
  
- 
  All cups 2.2.10-4xxx in Ubuntu 19.04 published until now have the same
  bug

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

Title:
  cups bug with samsung printer

Status in cups package in Ubuntu:
  New

Bug description:
  Saumsung printer need a patch to work with cups because has this issue 
https://github.com/apple/cups/issues/5562#issuecomment-483377904
  Need to upgrade to newer version or apply this patch 
https://github.com/apple/cups/commit/8829edfef0d496677a94b0c1b2f08f8e407af444
  Thanks

  All cups 2.2.10-4xxx in Ubuntu 19.04 published until now have the same
  bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1829271/+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 1824661] Re: Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to blank screen that flashes a couple times. Can't get to tty.

[Eric Adams]

This issue was apparently resolved with the release of 19.04 as I have
not encountered it since then. This report should be closed.

** No longer affects: lightdm (Ubuntu)

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

** Changed in: slick-greeter (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Nvidia issues with 19.04 and XPS 15 9750 GTX 1050 Ti Mobile: Boots to
  blank screen that flashes a couple times. Can't get to tty.

Status in linux package in Ubuntu:
  Invalid
Status in slick-greeter package in Ubuntu:
  Invalid

Bug description:
  Hello. I am having issues consistently with this laptop and the Nvidia
  drivers in 19.04. I have tested this on Ubuntu, Kubuntu, Ubuntu
  Budgie, and Ubuntu MATE. This is with both the recommended 418 driver
  as well as 390. Today I tried installing the latest daily of Ubuntu
  MATE with the proprietary driver option on my Dell XPS 15 9570 with
  Nvidia GP107M (GeForce GRX 1050 Time Mobile). Boots to blank screen
  that flashes a couple times. Can't get to tty. Reboot, editing grub to
  include nomodeset. Boots to underscore character in the top left. I
  can get tty at least. 418 driver is installed. Looking at logs but
  nothing seems obvious. If there's anything I can do to help with this
  please let me know. Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Sat Apr 13 18:27:12 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2019-04-13 (0 days ago)
  InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  MachineType: Dell Inc. XPS 15 9570
  ProcEnviron:
   TERM=cygwin
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=add8471d-1273-4547-aef3-4be006f9eb9c ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.1
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.1:bd02/01/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

[Xiscofauli]

Verified in

Version: 6.3.0.0.alpha1+
Build ID: a3e649c3384d19a5ad540c3d65d5f79b66fd9090
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

@Michael Stahl, thanks for fixing this issue!!

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

Title:
  [Upstream] Applying autocorrect to text with URLs causes Writer to
  hang

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  When attempting to apply autocorrect to text that contains URLs to
  convert to hyperlinks (https://ask.libreoffice.org/en/question/6393
  /how-may-i-do-writer-recognize-hyperlinks-automatically/) causes
  Writer to stop responding requiring a force quit.

  Version 6.2.2.2

  Severity: Normal.

  Reproducible:
  Always

  Steps to reproduce:
  Open a new Writer document.
  Turn URL recognition on - Tools | Auto Correct | Auto correct options | 
Options tab
  Insert text containing URLs (see below)
  Set paragraph style to default
  Apply auto correct - Tools | Auto Correct | Apply

  Actual result:
  Libre Office hangs

  Expected result:
  Auto correct applied, text urls converted to hyperlinks

  Bug is evident in both deb and snap versions of LO, but not in earlier
  5.x or 6.x series.

  Sample test with URLs:
  This webpage is and example of a url that should be able to be converted to a 
hyperlink . As is this page  
and this page .

  These pages should also be able to be converted using the method
  linked to above ,
  .

  A typical use for a page like this would be a bibliography or
  reference list .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  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: Mon May 13 20:38:07 2019
  InstallationDate: Installed on 2019-05-11 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Libreoffice-commits]

Michael Stahl committed a patch related to this issue.
It has been pushed to "libreoffice-6-2":

https://git.libreoffice.org/core/+/b25317070ed36cc1c1e588871b4dd7e77d0a7f49%5E%21

tdf#125261 sw_redlinehide: fix inf. loop in SwAutoFormat::AutoCorrect()

It will be available in 6.2.5.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

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

Title:
  [Upstream] Applying autocorrect to text with URLs causes Writer to
  hang

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  When attempting to apply autocorrect to text that contains URLs to
  convert to hyperlinks (https://ask.libreoffice.org/en/question/6393
  /how-may-i-do-writer-recognize-hyperlinks-automatically/) causes
  Writer to stop responding requiring a force quit.

  Version 6.2.2.2

  Severity: Normal.

  Reproducible:
  Always

  Steps to reproduce:
  Open a new Writer document.
  Turn URL recognition on - Tools | Auto Correct | Auto correct options | 
Options tab
  Insert text containing URLs (see below)
  Set paragraph style to default
  Apply auto correct - Tools | Auto Correct | Apply

  Actual result:
  Libre Office hangs

  Expected result:
  Auto correct applied, text urls converted to hyperlinks

  Bug is evident in both deb and snap versions of LO, but not in earlier
  5.x or 6.x series.

  Sample test with URLs:
  This webpage is and example of a url that should be able to be converted to a 
hyperlink . As is this page  
and this page .

  These pages should also be able to be converted using the method
  linked to above ,
  .

  A typical use for a page like this would be a bibliography or
  reference list .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libreoffice (not installed)
  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: Mon May 13 20:38:07 2019
  InstallationDate: Installed on 2019-05-11 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1828811/+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 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

[Sebastien Bacher]

@Mathieu, why do you think it's a gnome-control-center issue? It just
calls to hostnamed no?

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

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

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Xenial:
  New
Status in systemd source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  New
Status in gnome-control-center package in Debian:
  Fix Released

Bug description:
  GUI
  ---
  1a. Run sudo gnome-control-center, or...
  1b. Save the gnome-control-center.pkla from 
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556
 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run 
gnome-control-center as an admin user

  2. Enter the Details panel
  3. The "Device name" (hostname) text field should be editable; change the 
text to something else.
  4. The hostname is updated instantly which can be verified by looking in 
/etc/hostname. However /etc/hosts/ is not updated.

  Command line
  
  hostnamectl set-hostname

  The hostnamed documentation at 
http://www.freedesktop.org/wiki/Software/systemd/hostnamed says
  "To properly handle name lookups with changing local hostnames without having 
to edit /etc/hosts for them we recommend using hostnamed in combination with 
nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ "

  Without /etc/hosts being handled correctly, the hostnamed integration
  is only half-working.


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 08:52:57 2013
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+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 1829256] [NEW] Cannot find display brightness settings anywhere

[Daniel Martinek]

Public bug reported:

Ubuntu:

Description:Ubuntu 19.04
Release:19.04

xorg:
  Instalovaná verze: 1:7.7+19ubuntu12
  Kandidát:  1:7.7+19ubuntu12
  Tabulka verzí:
 *** 1:7.7+19ubuntu12 500
500 http://cz.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 15 11:12:23 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 als, master, 4.18.0-20-generic, x86_64: installed
 als, master, 5.0.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 620 [1028:0786]
MachineType: Dell Inc. Vostro 5568
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=cs_CZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro recovery nomodeset
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/04/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 0HG2TP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd10/04/2018:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn0HG2TP:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 5568
dmi.product.sku: 0786
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco ubuntu

** Attachment added: "screenshot of the bug"
   
https://bugs.launchpad.net/bugs/1829256/+attachment/5264023/+files/Sn%C3%ADmek%20z%202019-05-15%2009-07-10.png

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

Title:
  Cannot find display brightness settings anywhere

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu:

  Description:  Ubuntu 19.04
  Release:  19.04

  xorg:
Instalovaná verze: 1:7.7+19ubuntu12
Kandidát:  1:7.7+19ubuntu12
Tabulka verzí:
   *** 1:7.7+19ubuntu12 500
  500 http://cz.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Operace zamítnuta: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 15 11:12:23 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   als, master, 4.18.0-20-generic, x86_64: installed
   als, master, 5.0.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:0786]
  MachineType: Dell Inc. Vostro 5568
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=d3c1a21c-bf79-43cc-9eb9-83748dbaf57d ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0HG2TP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd10/04/2018:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn0HG2TP:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5568
  dmi.product.sku: 0786
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: l

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

[Mathieu Trudel-Lapierre]

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

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

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

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

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

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

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

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

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

Status in gnome-control-center package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Xenial:
  New
Status in systemd source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  New
Status in gnome-control-center package in Debian:
  Fix Released

Bug description:
  GUI
  ---
  1a. Run sudo gnome-control-center, or...
  1b. Save the gnome-control-center.pkla from 
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556
 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run 
gnome-control-center as an admin user

  2. Enter the Details panel
  3. The "Device name" (hostname) text field should be editable; change the 
text to something else.
  4. The hostname is updated instantly which can be verified by looking in 
/etc/hostname. However /etc/hosts/ is not updated.

  Command line
  
  hostnamectl set-hostname

  The hostnamed documentation at 
http://www.freedesktop.org/wiki/Software/systemd/hostnamed says
  "To properly handle name lookups with changing local hostnames without having 
to edit /etc/hosts for them we recommend using hostnamed in combination with 
nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ "

  Without /etc/hosts being handled correctly, the hostnamed integration
  is only half-working.


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 08:52:57 2013
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+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 1828108] Re: GNOME default to a document font not installed by Ubuntu

[Sebastien Bacher]

Installing ubuntu-settings 19.04.3.1 the correct font is
listed/displayed

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

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

Title:
  GNOME default to a document font not installed by Ubuntu

Status in gnome-flashback package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Disco:
  Fix Committed

Bug description:
  * Impact

  The document font changed in GNOME 3.31 to be 'Cantarell 11' but that
  font is not installed in Ubuntu so a fallback font is used instead.

  * Test case
  Install gnome-tweaks and look at the document font, it should be 'Sans 11' 
and not 'undefined'

  * Regression potential
  It's just changing the default value to be what it was before, the impact 
should be low (the UI is going to look different in place where the fallback 
was used but that's what the fix is about)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/1828108/+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 1825396] Re: "Open in Terminal" returns "Text ended before matching quote was found for '"

[Iain Lane]

OK got it in eoan, will update disco now (might take some time to be
processed).

** Description changed:

+ [ Description ]
+ 
  Attempting to open a Desktop folder named "aaa'bbb" (without double
  quotes) using the "Open in Terminal" option from the context menu
  produces a notification message stating:
  
- Execution of "x-terminal-emulator --working-directory=/home/... 
+ Execution of "x-terminal-emulator --working-directory=/home/...
  Text ended before matching quote was found for '. (The text was 
"x-terminal-emulator --working-directory=/home/x/Desktop/aaa'bbb")
  
  This suggests improper escaping (possible security impact with command
  injection).
+ 
+ [ QA ]
  
  Steps to reproduce:
  
  1. On the Ubuntu 19.04.0 amd64 Desktop, right-click, and select "New folder"
  2. Enter the following folder name and press Enter: aaa'bbb
  3. Right-click on the newly created folder icon
  4. Select "Open in Terminal"
  5. The above notification pops up, no terminal window opens.
  
  The expected outcome would be:
  5. A terminal window opens in directory ~/Desktop/aaa'bbb
+ 
+ [ Regression potential ]
+ 
+ See bug #1829244
+ 
+ [ ... ]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01.1-1
  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: Thu Apr 18 18:40:28 2019
  InstallationDate: Installed on 2019-04-14 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Disco)
   Status: New => In Progress

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Disco)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  "Open in Terminal" returns "Text ended before matching quote was found
  for '"

Status in gnome-shell-extension-desktop-icons:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Disco:
  In Progress

Bug description:
  [ Description ]

  Attempting to open a Desktop folder named "aaa'bbb" (without double
  quotes) using the "Open in Terminal" option from the context menu
  produces a notification message stating:

  Execution of "x-terminal-emulator --working-directory=/home/...
  Text ended before matching quote was found for '. (The text was 
"x-terminal-emulator --working-directory=/home/x/Desktop/aaa'bbb")

  This suggests improper escaping (possible security impact with command
  injection).

  [ QA ]

  Steps to reproduce:

  1. On the Ubuntu 19.04.0 amd64 Desktop, right-click, and select "New folder"
  2. Enter the following folder name and press Enter: aaa'bbb
  3. Right-click on the newly created folder icon
  4. Select "Open in Terminal"
  5. The above notification pops up, no terminal window opens.

  The expected outcome would be:
  5. A terminal window opens in directory ~/Desktop/aaa'bbb

  [ Regression potential ]

  See bug #1829244

  [ ... ]

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01.1-1
  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: Thu Apr 18 18:40:28 2019
  InstallationDate: Installed on 2019-04-14 (4 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1825396/+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 1829244] [NEW] [SRU] 19.04.3

[Iain Lane]

Public bug reported:

[ Description ]

This is a bugfix release from upstream.

The fix we really want is for bug #1825396. Here are the changes (minus
translation only changes):

* e7bb13c730bedb221d82fba2c1c5db38124d9fc8 (tag: 19.01.3) Prepare for 19.01.3 
release
* 90672b945cfda190afd2e36ad26bbb14dad96b46 Prepare for 19.01.2 release
* 1e1d5f3254f18cfc0d05cb11bafd2043a2833754 fileItem.js: Remove unneeded method 
call
* 86f6fed3a52164a2e34613b72bb7b2e5bd90 fileItem.js: cancel file monitoring 
on destroy
* 46cd8fad4765f52ab2592301322f4bc0ff1b8393 General: fix opening terminal in 
folder
* 4fd2b5c3cc1545cf7f381bfb85ea615648eac55f general: add new files top to 
bottom, left to right
* 0b383878934e3b88424ead5f7fae77e3a13dfe52 (upstream/fix_version_compatibility) 
desktopGrid.js: Check shell version for method existence
* b0cfb3d4ff5d9298a5aafb1ef6bcd39512fc64b0 (upstream/fix_hang_on_rename) 
desktopGrid.js: remove unnecessary NULL parameters
* c95a571ba36569fdfd04aab56983af5fb685d936 desktopGrid.js: Fix keyboard hang 
when renaming
* d9f017bd1fcee9a31162ffdf2b3b7ccffebf19f8 desktopGrid: Make paste menuitem 
always visible
* 58e39822faba203d457990f611718c166caa2d90 desktopGrid: Don't use deprecated 
BoxPointer APIs
* f6457f36668dd4faab699d121663385d46410989 desktopGrid: Handle empty clipboard
* 11f6260ef71a8a15b0aafa4f3a6d2dee437bb95d prefs.js: Fix untranslated texts in 
prefs
* b114cdfa9899e25900a7aee62618f05ba5e49e3e desktopManager: Add rubber band to 
background group
* 4ad6ff5736ca873f5fc07356a019eb456a211faf desktopManager: Don't clear previous 
selection when using ctrl/shift.

[ QA ]

I think this is probably *not* covered by the GNOME MRE, since it's not
a part of core GNOME. Let's test this explicitly then.

Don't clear previous selection when using ctrl/shift.
-

1. Have multiple icons on the desktop
2. Select one of them by clicking
3a. Hold ctrl and click some of the others. The selection should toggle.
3b. Hold shift and click / drag a selection to cover some of the unselected 
icons. They should become selected.

Handle empty clipboard
--

With nothing in the clipboard, check the right click menu doesn't result
in any warnings.

general: add new files top to bottom, left to right
---

Check that new files added to the desktop get added in this order. e.g.
"touch ~/Desktop/{1..10}"

general
---

Check that launching desktop files works, that filesystem events are
responded to, etc.

[ Regression potential ]

Shell extensions can completely break the shell. If just this extension
is broken then there might be no desktop.

** Affects: gnome-shell-extension-desktop-icons (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: gnome-shell-extension-desktop-icons (Ubuntu Disco)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Description changed:

  [ Description ]
  
  This is a bugfix release from upstream.
  
  The fix we really want is for bug #1825396. Here are the changes (minus
  translation only changes):
  
  * e7bb13c730bedb221d82fba2c1c5db38124d9fc8 (tag: 19.01.3) Prepare for 19.01.3 
release
  * 90672b945cfda190afd2e36ad26bbb14dad96b46 Prepare for 19.01.2 release
  * 1e1d5f3254f18cfc0d05cb11bafd2043a2833754 fileItem.js: Remove unneeded 
method call
  * 86f6fed3a52164a2e34613b72bb7b2e5bd90 fileItem.js: cancel file 
monitoring on destroy
  * 46cd8fad4765f52ab2592301322f4bc0ff1b8393 General: fix opening terminal in 
folder
  * 4fd2b5c3cc1545cf7f381bfb85ea615648eac55f general: add new files top to 
bottom, left to right
  * 0b383878934e3b88424ead5f7fae77e3a13dfe52 
(upstream/fix_version_compatibility) desktopGrid.js: Check shell version for 
method existence
  * b0cfb3d4ff5d9298a5aafb1ef6bcd39512fc64b0 (upstream/fix_hang_on_rename) 
desktopGrid.js: remove unnecessary NULL parameters
  * c95a571ba36569fdfd04aab56983af5fb685d936 desktopGrid.js: Fix keyboard hang 
when renaming
  * d9f017bd1fcee9a31162ffdf2b3b7ccffebf19f8 desktopGrid: Make paste menuitem 
always visible
  * 58e39822faba203d457990f611718c166caa2d90 desktopGrid: Don't use deprecated 
BoxPointer APIs
  * f6457f36668dd4faab699d121663385d46410989 desktopGrid: Handle empty clipboard
  * 11f6260ef71a8a15b0aafa4f3a6d2dee437bb95d prefs.js: Fix untranslated texts 
in prefs
  * b114cdfa9899e25900a7aee62618f05ba5e49e3e desktopManager: Add rubber band to 
background group
  * 4ad6ff5736ca873f5fc07356a019eb456a211faf desktopManager: Don't clear 
previous selection when using ctrl/shift.
  
  [ QA ]
  
  I think this is probably *not* covered by the GNOME MRE, since it's not
  a part of core GNOME. Let's test this explicitly then.
  
  Don't clear previous selection when using ctrl/shift.
  -
  
  1. Have multiple icons on the desktop
  2. Select one of them by clicking
  3a. Hold ctrl and click som

[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Balint Reczey]

Verified 2.0.4-4ubuntu1.19.04.0 on Disco:
test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionArchitecture Description
+++-==-==--=
ii  kbd2.0.4-4ubuntu1.19.04.0 amd64Linux console font and 
keytable utilities
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty4; echo $?
[sudo] password for test: 
The keyboard is in Unicode (UTF-8) mode
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty4
The keyboard is in xlate (8-bit) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty4
The keyboard is in Unicode (UTF-8) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
The keyboard is in some unknown mode
Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -f -u -C /dev/tty0; 
echo $?
0
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -C /dev/tty0
The keyboard is in Unicode (UTF-8) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -s -C /dev/tty0
test@test-Standard-PC-i440FX-PIIX-1996:~$  sudo kbd_mode -C /dev/tty0
The keyboard is in raw (scancode) mode
test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
The keyboard is in raw (scancode) mode
Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
0
test@test-Standard-PC-i440FX-PIIX-1996:~$

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Fix Committed
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Fix Committed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBoo

[Desktop-packages] [Bug 1829221] Re: second, dead, mouse pointer left on screen after login, x11 session

[Sebastien Bacher]

** No longer affects: gnome-session (Ubuntu)

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

Title:
  second, dead, mouse pointer left on screen after login, x11 session

Status in mutter package in Ubuntu:
  New

Bug description:
  This seems to have become repeatable, and applies even on the first
  login session immediately after booting the computer. I don't know if
  this is the right package to report against; another possible culprit:
  gdm:

  When I log into the default "Ubuntu" session (ie: on xorg), gdm's
  mouse pointer remains on screen during the screen blank, and after the
  gnome desktop comes up. It stays on the top just like you'd expect of
  the mouse pointer, but it's immobile and unresponsive. It's left at
  the same position on the screen that it was while using gdm, and is
  the same size as it was in gdm (ie: gdm is not scaled, but gnome
  session desktop scaled to 150% - the *working* in-session mouse
  pointer is also 150% larger than gdm's dead one).

  It looks like gdm and gnome are running in the same x11 session?
  Seeing as the mouse pointer stays solid *during* the transition from
  gdm into the gnome desktop. Not even a flicker. It's almost as if
  we're trying to have smooth transitions for these sorts of things,
  which is good of course, but maybe is a bug in that?

  It disappears when I log into a Wayland session, it appears only to
  affect x11 sessions.

  I've taken to just moving the mouse pointer to the far bottom right
  corner of the screen before logging in, so at least it's not very
  intrusive.

  There are a few reports of similar in askubuntu from a few years back,
  but with no helpful or applicable solution. eg:

  
https://askubuntu.com/questions/521241/i-have-two-cursors-on-my-screen-one-of-which-is-always-on-top-and-will-never-mo
  
https://askubuntu.com/questions/598096/14-04-second-mouse-pointer-stuck-in-middle-of-the-screen

  To answer the points made there, the xinput --list output is shown
  below. Executing that command and rebooting makes no difference. In
  the Displays Prefs there is no second "Unknown" display to disable.
  (The machine has precisely one display, and that's all Settings sees.
  It's a desktop, not a laptop, and it only has an AMD Vega integrated
  graphics. It also has only one mouse.)

  rachel@twilight:~$ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ HID 04b4:3003 Mouse id=9[slave  pointer 
 (2)]
  ⎜   ↳ HID 04b4:3003 Consumer Control  id=11   [slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Mouseid=15   [slave  
pointer  (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=16   
[slave  pointer  (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=17   
[slave  pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ HID 04b4:3003   id=8[slave  
keyboard (3)]
  ↳ HID 04b4:3003 System Controlid=10   [slave  
keyboard (3)]
  ↳ HID 04b4:3003 Keyboard  id=12   [slave  
keyboard (3)]
  ↳ Dell Dell AC511 USB SoundBarid=13   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0  id=14   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0 System Control   id=18   
[slave  keyboard (3)]
  ↳ Eee PC WMI hotkeys  id=19   [slave  
keyboard (3)]
  ↳ HID 04b4:3003 Consumer Control  id=20   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=21   
[slave  keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=22   
[slave  keyboard (3)]

  (I don't know what's with the duplicated MS Nano Transceiver Consumer
  Control entries)

  I thought of a couple of things to try after starting to write this
  ticket but didn't want to lose the ticket in progress, so will add
  comments if they show up anything. In particular, I am running the
  experimental feature to enable xrandr fractional scaling. This issue
  didn't show up right after enabling that, only a couple of days later,
  so it didn't seem immediately relevant.

  Also, trying with a different pointing device attached in case that
  transceiver is doing something odd. (never had problems before, had it

[Desktop-packages] [Bug 1829077] Re: disco 19.04 doesn't shutdown

[Sebastien Bacher]

Thank you for your bug report, could you add the journalctl log from a
such boot?

** Package changed: gnome-power-manager (Ubuntu) => systemd (Ubuntu)

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

Title:
  disco 19.04 doesn't shutdown

Status in systemd package in Ubuntu:
  New

Bug description:
  I have a fresh install of Ubuntu 19.04 GNOME 64 bits.
  When I choose "Power Off", it closes the session screen but then the it 
displays the red dots who scroll under Ubuntu logo and it never stop completely.
  I can listen the hard disk containing my home directory which stops (the 
system is on a SSD).
  Each time, I have to switch off the computer. I can start it again without 
any problem.

  The command "sudo shutdown now" give the same result.
  This computer had not this problem with the previous version of Ubuntu.

  Proc : AMD Fx 8320
  Motherboard : Asrock 970 Extreme 4
  graphic card : Radeon 6850
  Ram : 8Go
  Ubuntu 19.04 is the only OS on the SSD system drive
  /home is on a second hard drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829077/+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 1828116] Re: Password works uppercase and lowercase

[Sebastien Bacher]

Do you get the issue in the lock screen as well on only on the boot
greeter?

Could you try adding another user to the system and see if it has the
same bug?

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

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

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

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

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

Title:
  Password works uppercase and lowercase

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

Bug description:
  When I log in on the console, I can type my password either uppercase
  or lowercase. I can log in regardless.

  $ uname -a
  4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 
x86_64 GNU/Linux

  Ubuntu 18.04 patched as of today.

  $ sudo cat /etc/shadow | grep $USER
  ...:$6$...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-02-06 (94 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gdm3 3.28.3-0ubuntu18.04.4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1828116/+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 1828176] Re: Dock indicators do not work for snap apps

[Sebastien Bacher]

Do you get the issue after a fresh login? Do you have any extensions
loaded? Could you add your journalctl log to the bug after getting the
issue? It works fine here (tested with gnome-system-monitor for example,
which is installed  by default)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Incomplete

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

Title:
  Dock indicators do not work for snap apps

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Incomplete

Bug description:
  I have installed a minimal version of Ubuntu 19.04 and later I
  installed a few snap apps through the software center. Specifically,
  Caprine, Slack, Skype.

  Those apps load correctly, appear correctly on the dock at the bottom
  of the screen, however the indicators that should show a running app
  are absent for every such app.

  Tapping a snap application icon on the dock sometimes brings it on the
  foreground as expected (this happens with Slack), but other times (as
  with Caprine and Skype) nothing happens.

  Please note that tapping Activities (or hitting the Windows button)
  shows all the respective application windows which means that this is
  probably a snap & ubuntu dock only thing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1828176/+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 1829111] Re: Openvpn connection icons missing from display

[Sebastien Bacher]

Thank you for your bug report, what package did you update? What do you call 
"unstable packages"?
Can you take a screenshot of the issue?
Is that happening in xorg sessions as well? Or only wayland?

** Changed in: network-manager-openvpn (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Openvpn connection icons missing from display

Status in network-manager-openvpn package in Ubuntu:
  Incomplete

Bug description:
  Having upgraded to the unstable packages I no longer see an indication
  on the vpn dropdown to show what vpn's are connected and which are
  not.

  The last one active is shown at the top of the dropdown list, but
  others in the list are missing the indication that they used to have
  to say they are connected.

  The following appears in the log at the same time so I think its
  related.

  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #6   
7ffcd0736aa0 b   resource:///org/gnome/gjs/modules/signals.js:128 (7fc4db3cb820 
@ 386)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #7   
7ffcd0736b50 b   resource:///org/gnome/shell/ui/tweener.js:238 (7fc4db3cb3a0 @ 
159)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #8   
7ffcd0736bf0 b   resource:///org/gnome/shell/ui/tweener.js:209 (7fc4db3cb280 @ 
15)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: == Stack 
trace for context 0x55f2c9f241e0 ==
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #0   
55f2d255fca8 i   resource:///org/gnome/shell/ui/background.js:722 (7fc4daf08430 
@ 22)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #1   
55f2d255fc20 i   resource:///org/gnome/shell/ui/tweener.js:106 (7fc4db3c8940 @ 
37)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #2   
7ffcd0736720 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 
(7fc4db3d0670 @ 54)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #3   
7ffcd0736870 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:342 
(7fc4db3d0700 @ 1742)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #4   
7ffcd0736920 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:355 
(7fc4db3d0790 @ 100)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #5   
7ffcd07369b0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:370 
(7fc4db3d0820 @ 10)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #6   
7ffcd0736aa0 b   resource:///org/gnome/gjs/modules/signals.js:128 (7fc4db3cb820 
@ 386)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #7   
7ffcd0736b50 b   resource:///org/gnome/shell/ui/tweener.js:238 (7fc4db3cb3a0 @ 
159)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #8   
7ffcd0736bf0 b   resource:///org/gnome/shell/ui/tweener.js:209 (7fc4db3cb280 @ 
15)
  May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: g_object_run_dispose: 
assertion 'G_IS_OBJECT (object)' failed
  May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: Object Meta.Background 
(0x55f2cdc6f230), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: g_object_run_dispose: 
assertion 'G_IS_OBJECT (object)' failed
  May 15 13:52:03 pnunn-XPS-13-9370 gnome-shell[2942]: Object Meta.Background 
(0x55f2cdc6f230), has been already deallocated — impossible to access it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: == Stack 
trace for context 0x55f2c9f241e0 ==
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #0   
55f2d255fca8 i   resource:///org/gnome/shell/ui/background.js:722 (7fc4daf08430 
@ 22)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #1   
55f2d255fc20 i   resource:///org/gnome/shell/ui/tweener.js:106 (7fc4db3c8940 @ 
37)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #2   
7ffcd0736720 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 
(7fc4db3d0670 @ 54)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #3   
7ffcd0736870 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:342 
(7fc4db3d0700 @ 1742)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #4   
7ffcd0736920 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:355 
(7fc4db3d0790 @ 100)
  May 15 13:52:03 pnunn-XPS-13-9370 org.gnome.Shell.desktop[2942]: #5   
7ffcd07369b0 b   resource:///o

[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[ghomem]

This is happening on 16.0.4 LTS with ethernet connected PCs. Relevant
logs:

May 15 00:58:28 shuttle01 dhclient[1203]: DHCPREQUEST of 192.168.1.89 on enp2s0 
to 192.168.1.3 port 67 (xid=0x218cacc0)
May 15 00:58:28 shuttle01 dhclient[1203]: DHCPACK of 192.168.1.89 from 
192.168.1.3
May 15 00:58:28 shuttle01 dhclient[1203]: bound to 192.168.1.89 -- renewal in 
29125 seconds.
May 15 01:17:01 shuttle01 CRON[24411]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
May 15 01:39:44 shuttle01 avahi-daemon[893]: Withdrawing address record for 
192.168.1.89 on enp2s0.
May 15 01:39:44 shuttle01 avahi-daemon[893]: Leaving mDNS multicast group on 
interface enp2s0.IPv4 with address 192.168.1.89.
May 15 01:39:44 shuttle01 avahi-daemon[893]: Interface enp2s0.IPv4 no longer 
relevant for mDNS.
May 15 01:39:44 shuttle01 whoopsie[1467]: [01:39:44] Cannot reach: 
https://daisy.ubuntu.com
May 15 01:39:44 shuttle01 whoopsie[1467]: [01:39:44] offline

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1827346] Re: Power: Fail to set delay time when the value is 90 minutes

[Robie Basak]

I don't see uploads for Bionic or for Disco?

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

Title:
  Power: Fail to set delay time when the value is 90 minutes

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in OEM Priority Project xenial series:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

  Fail to set delay time when the value is 90 minutes.

  In cc-power-panel.ui, the value of 90 minutes is 4800 (80*60), not
  5400 (90*60). When setting the delay time to 90 minutes, the UI will
  show "80 minutes" after reopening "All Settings". (Please refer to the
  photo in #1 and #2)

  [Test Case]

  1) Go to [All Settings][Power][Automatic suspend]

  2) Set delay time to 90 minutes (On Battery Power or Plugged in)

  3) Close [All Settings]

  4) Reopen [All Settings][Power][Automatic suspend]

  5) Check if the value is 90 minutes.

  [Regression Potential]

  Low. The value of 90 minutes is wrong. Just correct the value to 5400.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1827346/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

[Ken VanDine]

@roaf:  This was driven by an OEM request, so the priority was bionic.
We also needed to make sure disco (and later) was covered to ensure we
made the next LTS as well.

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in OEM Priority Project:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  Fix Committed
Status in libqmi source package in Bionic:
  Fix Committed
Status in modemmanager source package in Bionic:
  Fix Committed
Status in libmbim source package in Disco:
  Fix Released
Status in libqmi source package in Disco:
  Fix Released
Status in modemmanager source package in Disco:
  Fix Released
Status in libmbim source package in Eoan:
  Fix Released
Status in libqmi source package in Eoan:
  Fix Released
Status in modemmanager source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e and DW5821 support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+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 1829228] [NEW] boot time is too long and running HD videos starts flickering

[pushpendra]

Public bug reported:

boot time is too long and running HD videos starts flickering

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01: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)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed May 15 17:25:35 2019
DistUpgraded: 2018-09-28 10:50:13,399 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.116, 4.15.0-48-generic, x86_64: installed
 nvidia, 390.116, 4.15.0-50-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:39c7]
   Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:39c7]
InstallationDate: Installed on 2018-03-31 (409 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 5986:210f Acer, Inc 
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80XL
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=998b8ab4-3e79-4347-99f7-06c2fadbd335 ro quiet splash noresume 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-09-28 (229 days ago)
dmi.bios.date: 10/23/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 4WCN36WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 320-15IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN36WW:bd10/23/2017:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
dmi.product.family: ideapad 320-15IKB
dmi.product.name: 80XL
dmi.product.version: Lenovo ideapad 320-15IKB
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
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: Tue May 14 07:06:58 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.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/1829228

Title:
  boot time is too long and running HD videos starts flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  boot time is too long and running HD videos starts flickering

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01: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)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed May 15 17:25:35 2019
  DistUpgraded: 2018-09-28 10:50:13,399 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.116, 4.15.0-

[Desktop-packages] [Bug 1760115] Re: gnome-system-monitor crashed with SIGABRT

[Sebastien Bacher]

The error is https://errors.ubuntu.com/problem/19e723ae and has 292,
probably not worth a SRU since it's a low number, the deb is not used by
default and it's easy to workaround

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

Title:
  gnome-system-monitor crashed with SIGABRT

Status in gnome-system-monitor package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 18.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-monitor 3.28.0-1
  Uname: Linux 4.15.12-041512-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 30 19:44:31 2018
  ExecutablePath: /usr/bin/gnome-system-monitor
  ProcCmdline: gnome-system-monitor
  Signal: 6
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   Glib::RegexError::throw_func(_GError*) () at 
/usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  Title: gnome-system-monitor crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1760115/+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 1773502] Re: High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's Resources tab

[Sebastien Bacher]

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

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  gnome-shell or X.org using high cpu
  My fanless nettop use a Intel Celeron 847 CPU. On around 1 boot on 3, the CPU 
of one core is kept at 100 % by a process, this high CPU usage start few second 
after the boot. It seems related to the graphical system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 09:52:20 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773502/+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 1760115] Re: gnome-system-monitor crashed with SIGABRT

[Sebastien Bacher]

The issue is fixed in newer versions (GNOME 3.30/cosmic/distro) and in the snap 
(which is how the software is shipped in bionic by default)
https://gitlab.gnome.org/GNOME/gnome-system-monitor/commit/18bd98e2

** Changed in: gnome-system-monitor (Ubuntu)
   Status: New => Fix Released

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

Title:
  gnome-system-monitor crashed with SIGABRT

Status in gnome-system-monitor package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 18.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-monitor 3.28.0-1
  Uname: Linux 4.15.12-041512-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 30 19:44:31 2018
  ExecutablePath: /usr/bin/gnome-system-monitor
  ProcCmdline: gnome-system-monitor
  Signal: 6
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   Glib::RegexError::throw_func(_GError*) () at 
/usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  Title: gnome-system-monitor crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1760115/+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 1829156] Re: Chrome multimedia keys doesn't work after screen lock 18.04

[Sebastien Bacher]

Thank you for your bug reports. What desktop environment/session do you
use? When you mention multimedia keys is that keyboard ones? Do you get
the same  issue in e.g totem or is it specific to chrome?

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Incomplete

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

Title:
  Chrome multimedia keys doesn't work after screen lock 18.04

Status in gnome-settings-daemon package in Ubuntu:
  Incomplete

Bug description:
  So chrome introduced this multimedia key support and it works pretty
  well. I use google play music to listen to music and the play/pause
  multimedia keys are useful. but at an event where the screen is locked
  and i log back in, the multimedia keys doesn't work. i have to restart
  chrome to make it work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1829156/+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 1829221] Re: second, dead, mouse pointer left on screen after login, x11 session

[Rachel Greenham]

It does appear to be related to the xrandr scaling experimental feature,
after all. Revert that to default and the issue disappears. Guessing
that probably makes it a mutter bug, and being of an experimental
feature at that is hopefully of interest to someone but not urgent. In
view of that didn't test switching pointing device.

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

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

Title:
  second, dead, mouse pointer left on screen after login, x11 session

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

Bug description:
  This seems to have become repeatable, and applies even on the first
  login session immediately after booting the computer. I don't know if
  this is the right package to report against; another possible culprit:
  gdm:

  When I log into the default "Ubuntu" session (ie: on xorg), gdm's
  mouse pointer remains on screen during the screen blank, and after the
  gnome desktop comes up. It stays on the top just like you'd expect of
  the mouse pointer, but it's immobile and unresponsive. It's left at
  the same position on the screen that it was while using gdm, and is
  the same size as it was in gdm (ie: gdm is not scaled, but gnome
  session desktop scaled to 150% - the *working* in-session mouse
  pointer is also 150% larger than gdm's dead one).

  It looks like gdm and gnome are running in the same x11 session?
  Seeing as the mouse pointer stays solid *during* the transition from
  gdm into the gnome desktop. Not even a flicker. It's almost as if
  we're trying to have smooth transitions for these sorts of things,
  which is good of course, but maybe is a bug in that?

  It disappears when I log into a Wayland session, it appears only to
  affect x11 sessions.

  I've taken to just moving the mouse pointer to the far bottom right
  corner of the screen before logging in, so at least it's not very
  intrusive.

  There are a few reports of similar in askubuntu from a few years back,
  but with no helpful or applicable solution. eg:

  
https://askubuntu.com/questions/521241/i-have-two-cursors-on-my-screen-one-of-which-is-always-on-top-and-will-never-mo
  
https://askubuntu.com/questions/598096/14-04-second-mouse-pointer-stuck-in-middle-of-the-screen

  To answer the points made there, the xinput --list output is shown
  below. Executing that command and rebooting makes no difference. In
  the Displays Prefs there is no second "Unknown" display to disable.
  (The machine has precisely one display, and that's all Settings sees.
  It's a desktop, not a laptop, and it only has an AMD Vega integrated
  graphics. It also has only one mouse.)

  rachel@twilight:~$ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ HID 04b4:3003 Mouse id=9[slave  pointer 
 (2)]
  ⎜   ↳ HID 04b4:3003 Consumer Control  id=11   [slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Mouseid=15   [slave  
pointer  (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=16   
[slave  pointer  (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=17   
[slave  pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ HID 04b4:3003   id=8[slave  
keyboard (3)]
  ↳ HID 04b4:3003 System Controlid=10   [slave  
keyboard (3)]
  ↳ HID 04b4:3003 Keyboard  id=12   [slave  
keyboard (3)]
  ↳ Dell Dell AC511 USB SoundBarid=13   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0  id=14   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0 System Control   id=18   
[slave  keyboard (3)]
  ↳ Eee PC WMI hotkeys  id=19   [slave  
keyboard (3)]
  ↳ HID 04b4:3003 Consumer Control  id=20   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=21   
[slave  keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=22   
[slave  keyboard (3)]

  (I don't know what's with the duplicated MS Nano Transceiver Consumer
  Control entries)

  I thought of a couple of things to try after starting to write this
  ticket but didn't want to lose the ticket in progres

[Desktop-packages] [Bug 1829221] [NEW] second, dead, mouse pointer left on screen after login, x11 session

[Rachel Greenham]

Public bug reported:

This seems to have become repeatable, and applies even on the first
login session immediately after booting the computer. I don't know if
this is the right package to report against; another possible culprit:
gdm:

When I log into the default "Ubuntu" session (ie: on xorg), gdm's mouse
pointer remains on screen during the screen blank, and after the gnome
desktop comes up. It stays on the top just like you'd expect of the
mouse pointer, but it's immobile and unresponsive. It's left at the same
position on the screen that it was while using gdm, and is the same size
as it was in gdm (ie: gdm is not scaled, but gnome session desktop
scaled to 150% - the *working* in-session mouse pointer is also 150%
larger than gdm's dead one).

It looks like gdm and gnome are running in the same x11 session? Seeing
as the mouse pointer stays solid *during* the transition from gdm into
the gnome desktop. Not even a flicker. It's almost as if we're trying to
have smooth transitions for these sorts of things, which is good of
course, but maybe is a bug in that?

It disappears when I log into a Wayland session, it appears only to
affect x11 sessions.

I've taken to just moving the mouse pointer to the far bottom right
corner of the screen before logging in, so at least it's not very
intrusive.

There are a few reports of similar in askubuntu from a few years back,
but with no helpful or applicable solution. eg:

https://askubuntu.com/questions/521241/i-have-two-cursors-on-my-screen-one-of-which-is-always-on-top-and-will-never-mo
https://askubuntu.com/questions/598096/14-04-second-mouse-pointer-stuck-in-middle-of-the-screen

To answer the points made there, the xinput --list output is shown
below. Executing that command and rebooting makes no difference. In the
Displays Prefs there is no second "Unknown" display to disable. (The
machine has precisely one display, and that's all Settings sees. It's a
desktop, not a laptop, and it only has an AMD Vega integrated graphics.
It also has only one mouse.)

rachel@twilight:~$ xinput --list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ HID 04b4:3003 Mouse   id=9[slave  pointer  (2)]
⎜   ↳ HID 04b4:3003 Consumer Controlid=11   [slave  pointer  (2)]
⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Mouse  id=15   [slave  pointer 
 (2)]
⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control   id=16   
[slave  pointer  (2)]
⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control   id=17   
[slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ HID 04b4:3003 id=8[slave  keyboard (3)]
↳ HID 04b4:3003 System Control  id=10   [slave  keyboard (3)]
↳ HID 04b4:3003 Keyboardid=12   [slave  keyboard (3)]
↳ Dell Dell AC511 USB SoundBar  id=13   [slave  keyboard (3)]
↳ Microsoft Microsoft® Nano Transceiver v1.0id=14   [slave  
keyboard (3)]
↳ Microsoft Microsoft® Nano Transceiver v1.0 System Control id=18   [slave  
keyboard (3)]
↳ Eee PC WMI hotkeysid=19   [slave  keyboard (3)]
↳ HID 04b4:3003 Consumer Controlid=20   [slave  keyboard (3)]
↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control   id=21   
[slave  keyboard (3)]
↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control   id=22   
[slave  keyboard (3)]

(I don't know what's with the duplicated MS Nano Transceiver Consumer
Control entries)

I thought of a couple of things to try after starting to write this
ticket but didn't want to lose the ticket in progress, so will add
comments if they show up anything. In particular, I am running the
experimental feature to enable xrandr fractional scaling. This issue
didn't show up right after enabling that, only a couple of days later,
so it didn't seem immediately relevant.

Also, trying with a different pointing device attached in case that
transceiver is doing something odd. (never had problems before, had it
years, no idea if that doubling-up has always been there.)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-session 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed May 15 11:38:19 2019
InstallationDate: Installed on 2019-05-11 (3 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: gnome-session
UpgradeStatus: 

[Desktop-packages] [Bug 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Daniel van Vugt]

*** This bug is a duplicate of bug 1808002 ***
https://bugs.launchpad.net/bugs/1808002

You may find the old Ubuntu Unity desktop more efficient. You can
install it as a login option with:

  sudo apt install unity-session

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Omar Bahareth]

*** This bug is a duplicate of bug 1808002 ***
https://bugs.launchpad.net/bugs/1808002

I know this is slightly getting off-topic but is there anything other
than gnome-shell you would recommend that I can use for the time being?

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Daniel van Vugt]

*** This bug is a duplicate of bug 1808002 ***
https://bugs.launchpad.net/bugs/1808002

A different app causing high CPU in gnome-shell would be a different
bug. Each app is different due to differing rendering methods.

High CPU in gnome-shell caused by Firefox would be bug 1696305. But you
said the problem happens for you with Chrome (comment #12, bug 1808002),
or with the system monitor (comment #13, bug 1773502).

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Daniel van Vugt]

*** This bug is a duplicate of bug 1808002 ***
https://bugs.launchpad.net/bugs/1808002

I would expect high CPU in general on your laptop because you are using
3840x2160 and gnome-shell is not yet very efficient.

Please use the above bugs, and/or keep an eye on all the work being done
to improve it:

https://trello.com/c/pe5mRmx7

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Omar Bahareth]

*** This bug is a duplicate of bug 1808002 ***
https://bugs.launchpad.net/bugs/1808002

I'm not so sure it's the same as the other two, I'll run another test
tonight. Can you recommend any other app to try? Firefox maybe?

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1760115] Re: gnome-system-monitor crashed with SIGABRT

[Hans L]

Not sure if this is exactly the same bug, but I get an easily reproduce-
able crash when using the search bar(magnifying glass icon) under the
"Processes" tab, by typing a '[' character into the textbox.

terminate called after throwing an instance of 'Glib::RegexError'
Aborted

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

Title:
  gnome-system-monitor crashed with SIGABRT

Status in gnome-system-monitor package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 beta

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: gnome-system-monitor 3.28.0-1
  Uname: Linux 4.15.12-041512-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 30 19:44:31 2018
  ExecutablePath: /usr/bin/gnome-system-monitor
  ProcCmdline: gnome-system-monitor
  Signal: 6
  SourcePackage: gnome-system-monitor
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6
   Glib::RegexError::throw_func(_GError*) () at 
/usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1
  Title: gnome-system-monitor crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1760115/+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 1826604] Re: Extension causes saving files to desktop to be slow

[Chris]

Thanks gonsolo, that workaround worked for me (with a restart)

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

Title:
  Extension causes saving files to desktop to be slow

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

Bug description:
  To reproduce:
  1. Create a text file (foo.txt) on the desktop and open in gedit.
  2. Type a few lines in the file and save it.

  Expected: the file saves more or less instantly.

  Observed:
  - The file takes several seconds to save.
  - The following lines appear in the journal:

  Apr 26 22:20:40 khaeru-laptop gnome-shell[3205]: JS ERROR: TypeError: 
fileItem is null
   
_updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:339:17
   
_monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:299:89

  Notes:
  - Repeating #1 and #2 with a file that is in another folder (i.e., not on the 
desktop), the file saves instantly, and the log messages do not appear.
  - This might be a duplicate/alternate description of lp#1816205.
  - Discovered while trying to diagnose lp#1826219.

  $ lsb_release -rd && apt-cache policy gnome-shell-extension-desktop-icons
  Description:Ubuntu 19.04
  Release:19.04
  gnome-shell-extension-desktop-icons:
    Installed: 19.01.1-1
    Candidate: 19.01.1-1
    Version table:
   *** 19.01.1-1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu disco/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01.1-1
  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: Fri Apr 26 22:24:04 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-10-11 (562 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-04-22 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1826604/+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 1829124] Re: Activities overview workspace previews don't include secondary monitors

[Daniel van Vugt]

No problem. Please go to comment #2 :)

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

Title:
  Activities overview workspace previews don't include secondary
  monitors

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  I can't see and manage applications on 2 of 3 monitors using
  Activities. For example I started different application on all 3
  monitors and run Activities. You can see on attached "Activities.png"
  screenshot what only an application from the primary display is shown.

  I set "Workspaces span displays" option in GNOME Tweaks but this
  doesn't help. If to use "Multi monitors add-on" it allows to shown
  individual activities for each display, but can't collect all
  applications from all displays together.

  This produce a serious problem if only the primary monitor is on, but
  some application was opened on currently turned off monitor. No way to
  move it to currently working monitor.

  Reproduced on Ubuntu 18.04.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829124/+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 1829160] Re: Xorg and wayland crash

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

** Package changed: xorg (Ubuntu) => xorg-server (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/1829160

Title:
  Xorg and wayland crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 19.10, on either Gnome or Ubuntu desktops whether you use
  wayland or xorg upon hitting the super key or by pointing the mouse on
  the upper left corner xorg / wayland crashes or gets stuck.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.1.2-050102-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed May 15 10:29:59 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.6, 5.0.0-14-generic, x86_64: installed
   virtualbox, 6.0.6, 5.1.1-050101-generic, x86_64: installed
   virtualbox, 6.0.6, 5.1.2-050102-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] 
[1025:1134]
  InstallationDate: Installed on 2019-05-09 (5 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190508)
  Lsusb:
   Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA 
Technology Corp. JMS567 SATA 6Gb/s bridge
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b571 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer TravelMate P259-M
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.1.2-050102-generic 
root=UUID=c0ff169b-318d-4b2c-8938-1e09f710166e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/27/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.28
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Lyra_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd06/27/2017:svnAcer:pnTravelMateP259-M:pvrV1.28:rvnAcer:rnLyra_SK:rvrV1.28:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: SKL
  dmi.product.name: TravelMate P259-M
  dmi.product.sku: TravelMate P259-M_1134_1.28
  dmi.product.version: V1.28
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1829160/+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 1829160] [NEW] Xorg and wayland crash

[Obvi84-w]

Public bug reported:

On Ubuntu 19.10, on either Gnome or Ubuntu desktops whether you use
wayland or xorg upon hitting the super key or by pointing the mouse on
the upper left corner xorg / wayland crashes or gets stuck.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
Uname: Linux 5.1.2-050102-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed May 15 10:29:59 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.0.6, 5.0.0-14-generic, x86_64: installed
 virtualbox, 6.0.6, 5.1.1-050101-generic, x86_64: installed
 virtualbox, 6.0.6, 5.1.2-050102-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:1134]
InstallationDate: Installed on 2019-05-09 (5 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190508)
Lsusb:
 Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA 
Technology Corp. JMS567 SATA 6Gb/s bridge
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b571 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer TravelMate P259-M
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.1.2-050102-generic 
root=UUID=c0ff169b-318d-4b2c-8938-1e09f710166e ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/27/2017
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.28
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Lyra_SK
dmi.board.vendor: Acer
dmi.board.version: V1.28
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd06/27/2017:svnAcer:pnTravelMateP259-M:pvrV1.28:rvnAcer:rnLyra_SK:rvrV1.28:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: SKL
dmi.product.name: TravelMate P259-M
dmi.product.sku: TravelMate P259-M_1134_1.28
dmi.product.version: V1.28
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan kubuntu performance reproducible 
single-occurrence ubuntu

** Attachment added: "hardware.txt"
   
https://bugs.launchpad.net/bugs/1829160/+attachment/5263914/+files/hardware.txt

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

Title:
  Xorg and wayland crash

Status in xorg package in Ubuntu:
  New

Bug description:
  On Ubuntu 19.10, on either Gnome or Ubuntu desktops whether you use
  wayland or xorg upon hitting the super key or by pointing the mouse on
  the upper left corner xorg / wayland crashes or gets stuck.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  Uname: Linux 5.1.2-050102-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed May 15 10:29:59 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.0.6, 5.0.0-14-generic, x86_64: installed
   virtualbox, 6.0.6, 5.1.1-050101-generic, x86_64: installed
   virtualbox, 6.0.6, 5.1.2-050102-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] 
[1025:1134]
  InstallationDate: Installed on 2019-05-09 (5 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190508)
  Lsusb:
   Bus 002 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA 
Technology Corp. JMS567 SATA 6Gb/s bridge
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

[Desktop-packages] [Bug 1829124] Re: Activities overview workspace previews don't include secondary monitors

[vladf]

I saw #1743736, but I have different issue - only the primary display have 
overview. All other haven't it. In #1743736:
"But for the secondary display, I see windows from all workspaces being shown 
in the overview mode"

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

Title:
  Activities overview workspace previews don't include secondary
  monitors

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  I can't see and manage applications on 2 of 3 monitors using
  Activities. For example I started different application on all 3
  monitors and run Activities. You can see on attached "Activities.png"
  screenshot what only an application from the primary display is shown.

  I set "Workspaces span displays" option in GNOME Tweaks but this
  doesn't help. If to use "Multi monitors add-on" it allows to shown
  individual activities for each display, but can't collect all
  applications from all displays together.

  This produce a serious problem if only the primary monitor is on, but
  some application was opened on currently turned off monitor. No way to
  move it to currently working monitor.

  Reproduced on Ubuntu 18.04.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829124/+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 1332875] Re: [UPSTREAM] Writer: unable to select multiple pictures with SHIFT

[Marcus Tomlinson]

*** This bug is a duplicate of bug 1481835 ***
https://bugs.launchpad.net/bugs/1481835

Sorry crysman, yes this issue is still present. I forgot to link it to
the duplicate [1] which is still being tracked. My apologies.

[1] https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1481835

** This bug has been marked a duplicate of bug 1481835
   [UPSTREAM] Unable to group raster image(s) with drawing object(s)

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

Title:
  [UPSTREAM] Writer: unable to select multiple pictures with SHIFT

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  I am unable to select multiple pictures with SHIFT. It used to work
  normally aprx. a year-two ago, what've happened? This is VERY
  unpleasant bug!

  You may reproduce it easily:
  1) create a new document
  2) insert two PNG images via Insert -> Image
  3) try to select them both with SHIFT

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 21 22:17:58 2014
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2013-10-26 (238 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to trusty on 2014-06-11 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1332875/+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 1829156] [NEW] Chrome multimedia keys doesn't work after screen lock 18.04

[Basith Kunimal]

Public bug reported:

So chrome introduced this multimedia key support and it works pretty
well. I use google play music to listen to music and the play/pause
multimedia keys are useful. but at an event where the screen is locked
and i log back in, the multimedia keys doesn't work. i have to restart
chrome to make it work again.

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

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

Title:
  Chrome multimedia keys doesn't work after screen lock 18.04

Status in gnome-settings-daemon package in Ubuntu:
  New

Bug description:
  So chrome introduced this multimedia key support and it works pretty
  well. I use google play music to listen to music and the play/pause
  multimedia keys are useful. but at an event where the screen is locked
  and i log back in, the multimedia keys doesn't work. i have to restart
  chrome to make it work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1829156/+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 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Daniel van Vugt]

*** This bug is a duplicate of bug 1808002 ***
https://bugs.launchpad.net/bugs/1808002

Thanks. You have just described bug 1808002 and bug 1773502 so I am
marking this as a duplicate of one of them.

** This bug has been marked a duplicate of bug 1808002
   Gnome shell is consuming high cpu usage when running Chrome

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1421808] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from WakeupHandler()

[Daniel van Vugt]

Tracking in
https://errors.ubuntu.com/problem/a221de843241aab4d9728bcad808922b71c4a11c

** Description changed:

+ https://errors.ubuntu.com/problem/a221de843241aab4d9728bcad808922b71c4a11c
+ 
  The error is reported on boot up.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  8 12:36:52 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-04-24 (660 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130403)
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
-  
+ 
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
-  OsAbort ()
-  ?? ()
-  FatalError ()
-  xf86VTEnter ()
-  WakeupHandler ()
+  OsAbort ()
+  ?? ()
+  FatalError ()
+  xf86VTEnter ()
+  WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to vivid on 2015-01-30 (14 days ago)
  UserGroups:

** Tags added: disco

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

Title:
  Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
  WakeupHandler()

Status in xorg-server package in Ubuntu:
  Confirmed

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

  The error is reported on boot up.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.16.2.901-1ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-12-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb  8 12:36:52 2015
  ExecutablePath: /usr/bin/Xorg
  InstallationDate: Installed on 2013-04-24 (660 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130403)
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:

  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   OsAbort ()
   ?? ()
   FatalError ()
   xf86VTEnter ()
   WakeupHandler ()
  Title: Xorg crashed with SIGABRT in OsAbort()
  UpgradeStatus: Upgraded to vivid on 2015-01-30 (14 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1421808/+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 1773502] Re: High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's Resources tab

[Daniel van Vugt]

^^^
Moved to bug 1756508

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

Title:
  High CPU usage in gnome-shell & Xorg when using gnome-system-monitor's
  Resources tab

Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  gnome-shell or X.org using high cpu
  My fanless nettop use a Intel Celeron 847 CPU. On around 1 boot on 3, the CPU 
of one core is kept at 100 % by a process, this high CPU usage start few second 
after the boot. It seems related to the graphical system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 26 09:52:20 2018
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2018-04-29 (26 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Package: gnome-shell 3.28.1-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773502/+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 1756508] Re: Gnome-shell CPU load dramatically high and stuck high with Eclipse

[Daniel van Vugt]

** Changed in: gnome-shell (Ubuntu)
   Status: Expired => Confirmed

** Tags removed: artful
** Tags added: bionic

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

Title:
  Gnome-shell CPU load dramatically high and stuck high with Eclipse

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I recently upgraded Ubuntu from 16.04 to 17.10. Since I did, I cannot use 
Eclipse any more.
  I can start Eclipse, but as soon as I try to de-maximize it, gnome-shell CPU 
load raises to 80%-95% and remains that level. I ¥t sometimes drops a bit down 
to 70% but still keeps high and blocks everything. Even if by chance and 
patience I succeed closing Eclipse, the CPU load keeps high.
  Until now I found no way to recover.

  Ubuntu 17.10
  Gnome 3.26.2
  Runs in Virtual box
  Core i7x2
  8 GB RAM

  Eclipse Photon 4.8 M6
  But same happened with Oyxgen 4.7.2

  Other info needed, please let me know... not sure how to circle this closer. 
Once it happens, it's over .
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-02-20 (759 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  Package: gnome-shell 3.26.2-0ubuntu0.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Tags:  artful
  Uname: Linux 4.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to artful on 2018-01-18 (60 days ago)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1756508/+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 1829124] Re: Activities overview window spread keeps windows on their original monitors instead of bringing them together onto one

[Daniel van Vugt]

Oh I see from the screenshot now. How about this description...

** Summary changed:

- Activities overview window spread keeps windows on their original monitors 
instead of bringing them together onto one
+ Activities overview workspace previews don't include secondary monitors

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

Title:
  Activities overview workspace previews don't include secondary
  monitors

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  I can't see and manage applications on 2 of 3 monitors using
  Activities. For example I started different application on all 3
  monitors and run Activities. You can see on attached "Activities.png"
  screenshot what only an application from the primary display is shown.

  I set "Workspaces span displays" option in GNOME Tweaks but this
  doesn't help. If to use "Multi monitors add-on" it allows to shown
  individual activities for each display, but can't collect all
  applications from all displays together.

  This produce a serious problem if only the primary monitor is on, but
  some application was opened on currently turned off monitor. No way to
  move it to currently working monitor.

  Reproduced on Ubuntu 18.04.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829124/+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 1829124] Re: Activities overview window spread keeps windows on their original monitors instead of bringing them together onto one

[Daniel van Vugt]

I'm not sure, but are you describing bug 1743736?

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

Title:
  Activities overview workspace previews don't include secondary
  monitors

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  I can't see and manage applications on 2 of 3 monitors using
  Activities. For example I started different application on all 3
  monitors and run Activities. You can see on attached "Activities.png"
  screenshot what only an application from the primary display is shown.

  I set "Workspaces span displays" option in GNOME Tweaks but this
  doesn't help. If to use "Multi monitors add-on" it allows to shown
  individual activities for each display, but can't collect all
  applications from all displays together.

  This produce a serious problem if only the primary monitor is on, but
  some application was opened on currently turned off monitor. No way to
  move it to currently working monitor.

  Reproduced on Ubuntu 18.04.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829124/+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 1332875] Re: [UPSTREAM] Writer: unable to select multiple pictures with SHIFT

[crysman]

Hello, please, why is this set to invalid?

I'm running Xubuntu with Libreoffice Version: 6.0.7.3 Build ID:
1:6.0.7-0ubuntu0.18.04.5

and this bug (unable to select multiple images) is still
existent/persists.

selecting multiple drawings (e.g. circles or squares with SHIFT works,
though)

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

Title:
  [UPSTREAM] Writer: unable to select multiple pictures with SHIFT

Status in LibreOffice:
  Invalid
Status in libreoffice package in Ubuntu:
  Invalid

Bug description:
  I am unable to select multiple pictures with SHIFT. It used to work
  normally aprx. a year-two ago, what've happened? This is VERY
  unpleasant bug!

  You may reproduce it easily:
  1) create a new document
  2) insert two PNG images via Insert -> Image
  3) try to select them both with SHIFT

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-core 1:4.2.3~rc3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Jun 21 22:17:58 2014
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2013-10-26 (238 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to trusty on 2014-06-11 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1332875/+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 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Omar Bahareth]

This is what I regularly see in the system monitor.

** Attachment added: "Screenshot from 2019-05-15 11-04-00.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+attachment/5263901/+files/Screenshot%20from%202019-05-15%2011-04-00.png

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Omar Bahareth]

dmesg.txt

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+attachment/5263898/+files/dmesg.txt

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Omar Bahareth]

So this issue is happening when I have a single Chrome tab open (on this
issue page) and nothing else. The usage does spike up to higher than 25%
for a couple of seconds then back down to 10%-ish (one for Xorg and one
for Gnome shell, so 20% on average). My laptop fans spin quite loudly
too. I thought it might have been because I was trying a new GTK theme,
but I went back to Yaru dark and I still see the same issue.

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Omar Bahareth]

lspcik.txt

** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+attachment/5263899/+files/lspcik.txt

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Omar Bahareth]

journal.txt

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+attachment/5263900/+files/journal.txt

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1828967] Re: Gnome shell and Xorg use at least 10% CPU

[Omar Bahareth]

xrandr.txt

** Attachment added: "xrandr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+attachment/5263897/+files/xrandr.txt

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

Title:
  Gnome shell and Xorg use at least 10% CPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Related to Issue #1773959

  On a fresh install of Ubuntu 19.04 on a 2019 Dell XPS 13, I have very high 
CPU usage from gnome-shell and Xorg (each one is taking up around 10%) when no 
other process is running. This increased greatly to more than 20% for 
gnome-shell when I enabled showing seconds in the top bar. After disabling 
seconds, I went back to ~10% cpu usage for each of those processes again. I 
opened this because most of the other relevant issues are closed, expired, or 
marked as invalid.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Unity
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-05-13 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828967/+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 1829124] Re: Activities overview window spread keeps windows on their original monitors instead of bringing them together onto one

[vladf]

Daniel, I think I added an inaccurate description and therefore you
misunderstood me. You changes summary to "Activities overview window
spread keeps windows on their original monitors instead of bringing them
together onto one", but I talked about workspaces with available
applications. Look at attached screenshot "Activities with marks.jpg".
You can see what application from the primary monitor is shown on
workspace previews, application form other monitors are not shown. And
the option "Workspaces span displays" ("The current workspace includes
additional displays") doesn't have any effect.

I think a correct summary: Workspaces include application from the
primary display only even if to use "Workspaces span displays" option.

** Attachment added: "Activities with marks.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829124/+attachment/5263895/+files/Activities%20with%20marks.jpg

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

Title:
  Activities overview window spread keeps windows on their original
  monitors instead of bringing them together onto one

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  I can't see and manage applications on 2 of 3 monitors using
  Activities. For example I started different application on all 3
  monitors and run Activities. You can see on attached "Activities.png"
  screenshot what only an application from the primary display is shown.

  I set "Workspaces span displays" option in GNOME Tweaks but this
  doesn't help. If to use "Multi monitors add-on" it allows to shown
  individual activities for each display, but can't collect all
  applications from all displays together.

  This produce a serious problem if only the primary monitor is on, but
  some application was opened on currently turned off monitor. No way to
  move it to currently working monitor.

  Reproduced on Ubuntu 18.04.2.

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