date:20191020

Can you please run:

  apport-collect 1849055

to send us more information about your gnome-shell?

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  gnome-extensions fails to load after boot

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Most of the time when I start or restart Ubuntu-19.10 the gnome-extensions 
that I have enabled fail to load.  I am forced to go each time to gnome-tweaks 
to re-enable these extensions which is very 
  frustrating.  This worked fine in Ubuntu 19.04.  I am using a Dell Inspiron 
1420 laptop.  Thank you
  for any help with this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: 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  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 22:14:29 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia-340, 340.107, 5.3.0-18-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell G86M [GeForce 8400M GS] [1028:01f3]
  InstallationDate: Installed on 2016-01-26 (1363 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Inspiron 1420
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash noresume vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/19/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0Y918J
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd12/19/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0Y918J:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1420
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sun Oct 20 21:04:57 2019
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849055/+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 1849055] [NEW] gnome-extensions fails to load after boot

2019-10-20 Thread sally

Public bug reported:

Most of the time when I start or restart Ubuntu-19.10 the gnome-extensions that 
I have enabled fail to load.  I am forced to go each time to gnome-tweaks to 
re-enable these extensions which is very 
frustrating.  This worked fine in Ubuntu 19.04.  I am using a Dell Inspiron 
1420 laptop.  Thank you
for any help with this.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: 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  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 20 22:14:29 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: nvidia-340, 340.107, 5.3.0-18-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell G86M [GeForce 8400M GS] [1028:01f3]
InstallationDate: Installed on 2016-01-26 (1363 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. Inspiron 1420
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash noresume vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/19/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0Y918J
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd12/19/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0Y918J:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1420
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Sun Oct 20 21:04:57 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.5+git20191008-0ubuntu1

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


** Tags: amd64 apport-bug eoan possible-manual-nvidia-install 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/1849055

Title:
  gnome-extensions fails to load after boot

Status in xorg package in Ubuntu:
  New

Bug description:
  Most of the time when I start or restart Ubuntu-19.10 the gnome-extensions 
that I have enabled fail to load.  I am forced to go each time to gnome-tweaks 
to re-enable these extensions which is very 
  frustrating.  This worked fine in Ubuntu 19.04.  I am using a Dell Inspiron 
1420 laptop.  Thank you
  for any help with this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: 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  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the

[Desktop-packages] [Bug 1029932] Re: Brightness and Volume laptop keys behave inconsistently

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

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

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

Title:
  Brightness and Volume laptop keys behave inconsistently

Status in One Hundred Papercuts:
  Expired
Status in gnome-power-manager package in Ubuntu:
  Expired

Bug description:
  Holding the volume up button causes the volume to continually go up.
  The same doesn't work for brightness - the button has to be repeatedly
  pressed.

  This inconsistency can be confusing for users. I believe the
  preferable behaviour is that of the volume buttons.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-power-manager 3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  CheckboxSubmission: 346c69198d9a34d2dea85736f0dd6571
  CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
  Date: Fri Jul 27 14:13:03 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1029932/+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 1029932] Re: Brightness and Volume laptop keys behave inconsistently

[Expired for One Hundred Papercuts because there has been no activity
for 60 days.]

** Changed in: hundredpapercuts
   Status: Incomplete => Expired

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

Title:
  Brightness and Volume laptop keys behave inconsistently

Status in One Hundred Papercuts:
  Expired
Status in gnome-power-manager package in Ubuntu:
  Expired

Bug description:
  Holding the volume up button causes the volume to continually go up.
  The same doesn't work for brightness - the button has to be repeatedly
  pressed.

  This inconsistency can be confusing for users. I believe the
  preferable behaviour is that of the volume buttons.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-power-manager 3.4.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: amd64
  CheckboxSubmission: 346c69198d9a34d2dea85736f0dd6571
  CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3
  Date: Fri Jul 27 14:13:03 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-power-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1840799] Re: Chromium can't be set as default browser

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

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

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

Title:
  Chromium can't be set as default browser

Status in chromium-browser package in Ubuntu:
  Expired

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1840799/+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 1848951] Re: High CPU when just moving the mouse

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

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

Title:
  High CPU when just moving the mouse

Status in Mutter:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1848951/+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 1782425] Re: Unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value

** Changed in: gnome-settings-daemon
   Status: Unknown => Fix Released

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

Title:
  Unable to change Power off timeout from 60 seconds ("The system will
  power off automatically in 60 seconds") to custom value

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.04 LTS installed with GNOME desktop
  2. Click Power Off button or physical ACPI Power Button and see window with 
default 60 seconds timeout "The system will power off automatically in 60 
seconds"
  3. Try to set lower or higher timeout value anywhere (in `dconf`, 
`gsettings`, etc.)

  Expected results:
  User is able to change Power off timeout from 60 seconds ("The system will 
power off automatically in 60 seconds") to custom value.

  Actual results:
  User is unable to change Power off timeout from 60 seconds ("The system will 
power off automatically in 60 seconds") to custom value.

  Note: problem was first described on AskUbuntu (
  https://askubuntu.com/q/1057271/66509 ).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 18 22:42:50 2018
  DisplayManager: gdm3
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-28 (81 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1782425/+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 1848563] Re: Activities overview unwanted scrolling when clicking popup menu on page 4 onward

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Activities overview unwanted scrolling when clicking popup menu on
  page 4 onward

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When I right-click on an application in the overview, the page
  automatically moves to the one below when I move the mouse to select
  one of the menu options. This only affects pages 4 and below (the
  right-click on applications on pages 1-3 works as expected), but it
  does not affect the last page (in my case, page 6) presumably since
  there is no page below it to scroll to. The bug happens every time I
  try, no matter the application.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 13:04:45 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-22 (299 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-14 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1848563/+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 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell

** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Counter-Strike Global Offensive freezes in gnome-shell

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to ubuntu 19.10, when I launch counter strike global offensive 
from steam the game is frozen. I can alt-tab and close the game. Tried in 
fluxbox window manager where the game works, changed fullscreen to windowed 
fullscreen in the options and tried on gnome again, now the desktop isn't 
responding after launching the game and I had to ctrl-alt-f3 to reboot my 
machine.
  Using a Radeon RX 580 video card.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1848852/+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 1848951] Re: High CPU when just moving the mouse

In theory you might be able to avoid around 87% of the problem by
changing your mouse polling rate from 1000Hz to 125Hz. To do that you
need to add a kernel parameter:

  usbhid.mousepoll=8

or similar... https://wiki.archlinux.org/index.php/Mouse_polling_rate

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

Title:
  High CPU when just moving the mouse

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1848951/+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 1848836] Re: Unmounted drive shortcut is on the dock

2019-10-20 Thread frenchy82

Thanks Daniel van Vugt (vanvugt) for taking the time for this answer.

https://github.com/micheleg/dash-to-dock/issues/1031


** Bug watch added: github.com/micheleg/dash-to-dock/issues #1031
   https://github.com/micheleg/dash-to-dock/issues/1031

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

Title:
  Unmounted drive shortcut is on the dock

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

Bug description:
  Hi,

  On ubuntu 19.10,when the google account is set, there is a shortcut in
  nautilus.

  This shortcut, even when if it's not mounted, is visible in the dock
  when show-mounts option is actived.

  If i'm not wrong, it should be visible only when it's mounted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1848836/+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 1848951] Re: High CPU when just moving the mouse

Is there anything I can do by my side to at least lower the cpu usage or
no?

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

Title:
  High CPU when just moving the mouse

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1848951/+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 1848965] Re: Video Playback very choppy

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1848965

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: bionic

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (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/1848965

Title:
  Video Playback very choppy

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  My laptop is HP Pavilion g7 (Intel® Core™ i5-2430M CPU with Radeon HD
  6470M and Intel HD 3000 GPUs

  Already have played with Ubuntu on older spec desktops with no issues
  at all, however when when installing Ubuntu 18.04 from installation
  USB, had to boot with nomodeset to overcome freezing as a result of
  Ubuntu 18.04 not recognising/supporting these drivers

  Tried to search for additional drivers but none found

  Video handling resorts to llvmpipe (LLVM 9.0.0, 256 bits)

  My problem is that Video Playback is VLC very choppy in full screen
  mode - seems to get a little better when minimised, but effectively
  not usable.

  Have tried many threads posted regarding this problem, but nothing
  seems to work.

  Would really like to migrate my workload onto Ubuntu 18.04 operating
  system, but this seems to be a real non starter where i can't play
  video content, as video editing is a core function in my workload.

  Not sure if there is a solution for this, however after researching
  many similar threads, coupled with your in depth response to similar
  problems leaves me hopeful that you can point me in the right
  direction, or worst case scenario tell me there is no solution at all,
  and that I will have to stick to the hateful Windows 10 which is
  supported and working.

  1) not sure if it is just a simple graphics acceleration problem ?
  2) as flgrx no longer supported (for AMD Catalyst on Radeon HD 6470 M - can I 
disable this GPU somewhere on boot - as this seems to be where boot goes into a 
tizz. If so, how would I do this.
  3) if i did this would XORG then recognise other GPU - Intel HD 3000 and give 
me correct rendering to eliminate choppy video

  I am a noob, but have been playing with Ubuntu for some time, albeit
  at very low level, not totally computer illiterate, but do feel I am
  out of my depth in trying to resolve this. It just seems odd that it
  works fine on much lower spec and older desktops, but that I cant get
  this to work on my not so outdated laptop.

  Ubuntu Release 18.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1848965/+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 1079190] Re: gnome-control-center keyboard shortcuts does not manage keyboard power button keybindings properly

2019-10-20 Thread Alexis Wilke

I got here because of a question asked on the Ubuntu stack here:

https://askubuntu.com/questions/115333/how-do-i-disable-the-sleep-
button-on-my-keyboard

My keyboard Sleep button is right next to the Esc key. It's just too
close and way to easy to end up clicking on it. It would be nicer to
have the keys in the usual Keyboard Shortcuts window. It sounds like
this should be an easy one since it's very much the same as the other
keys... right?

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

Title:
  gnome-control-center keyboard shortcuts does not manage keyboard power
  button keybindings properly

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

Bug description:
  My keyboard has a "sleep" button on it.  I wish to reassign it to open
  a terminal rather than shut down my computer.  To do so, I click on
  gnome-control-center -> keyboard -> shortcuts -> launchers -> Launch
  Terminal, then I press the "sleep" button on my keyboard.  The "sleep"
  button appears to be properly assigned to run the terminal command.
  However, when I press the "sleep" button now, I would expect it to
  launch a terminal.  Instead it puts the computer to sleep.

  Digging further, it appears that the power buttons on the computer (including 
those on the keyboard) are controlled by the following dconf settings:
  org.gnome.settings-daemon.plugins.power   button-hibernate
  org.gnome.settings-daemon.plugins.power   button-power
  org.gnome.settings-daemon.plugins.power   button-sleep
  org.gnome.settings-daemon.plugins.power   button-suspend

  If I use dconf-editor to set these values to 'nothing', then the
  "sleep" button on my keyboard opens the terminal as expected.  The
  gnome-control-center keyboard shortcuts GUI does not disable the power
  settings for this button automatically for me.

  The gnome-control-center keyboard shortcuts GUI should know about and
  manage the org.gnome.settings-daemon.plugins.power button settings.
  It should allow the buttons to be re-assigned like other keyboard
  buttons.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-control-center 1:3.4.2-0ubuntu19
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Thu Nov 15 08:33:50 2012
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2012-10-31 (14 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to quantal on 2012-11-01 (14 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu4
   deja-dup24.0-0ubuntu1
   gnome-control-center-signon 0.0.18-0ubuntu1
   indicator-datetime  12.10.2-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1079190/+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 1848951] Re: Xorg and gnome-shell consuming large amount of CPU

I've been working on a number of issues causing this. It is much
improved in Ubuntu 19.10 but not yet quite at the point of being
declared fixed.

Tracking in: https://gitlab.gnome.org/GNOME/mutter/issues/283

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

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

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

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

** Summary changed:

- Xorg and gnome-shell consuming large amount of CPU
+ Xorg and gnome-shell consuming large amount of CPU when just moving the mouse

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

Title:
  High CPU when just moving the mouse

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1848951/+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 1848951] Re: Xorg and gnome-shell consuming large amount of CPU when just moving the mouse

Your mouse is very fast (1000Hz) so you will notice the problem 8x more
than most people (most mice are 125Hz).

http://x7.a4tech.com/product.aspx?id=68

** Summary changed:

- Xorg and gnome-shell consuming large amount of CPU when just moving the mouse
+ High CPU when just moving the mouse

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

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

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

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

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Tags added: performance

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

Title:
  High CPU when just moving the mouse

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1848951/+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 1848930] Re: Windows resize when sleep and wakeup on 100% display scale

** 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-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1848930

Title:
  Windows resize when sleep and wakeup on 100% display scale

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

Bug description:
  Scaling built-in display to "100%" makes my windows resize when I
  sleep my laptop and wake up again.

  Steps to reproduce:
  1) In system settings, in the "Screen display" section, change "Scale" to 
"100%"
  2) Open a window (e.g. a browser) and resize to most of the screen
  3) Close laptop screen and wait for it to go to sleep
  4) Open laptop screen
  5) Observe that the browser window is now only the top-left quarter of the 
screen, not its original dimensions

  Reproduced on 19.04 and 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 15:47:21 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-09 (252 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848930/+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 1848982] [NEW] NVIDIA VER 340.107 crashes steam

2019-10-20 Thread Blake

Public bug reported:

NVIDIA binary driver VER 340.17 is crashing steam. If I purge all NVIDIA
drivers Steam runs successfully from Nouveau, but seems to have
performance issues in game. Steam support was unhelpful and referred me
to anyone else.

Steam output from terminal is:

Running Steam on ubuntu 18.04 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
Installing breakpad exception handler for appid(steam)/version(1570046470)
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Installing breakpad exception handler for appid(steam)/version(1570046470)
Installing breakpad exception handler for appid(steam)/version(1570046470)
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Installing breakpad exception handler for appid(steam)/version(1570046470)
STEAM_RUNTIME_HEAVY: ./steam-runtime-heavy
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
[2019-10-20 23:14:06] Startup - updater built Oct  2 2019 18:45:27
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[2019-10-20 23:14:06] Checking for update on startup
[2019-10-20 23:14:06] Checking for available updates...
[2019-10-20 23:14:06] Downloading manifest: 
client-download.steampowered.com/client/steam_client_ubuntu12
[2019-10-20 23:14:07] Download skipped: /client/steam_client_ubuntu12 version 
1570046470, installed version 1570046470
[2019-10-20 23:14:07] Nothing to do
[2019-10-20 23:14:07] Verifying installation...
[2019-10-20 23:14:07] Performing checksum verification of executable files
[2019-10-20 23:14:07] Verification complete
glXChooseVisual failed
glXChooseVisual failedMain.cpp (332) : Assertion Failed: Fatal Error: 
glXChooseVisual failed
Main.cpp (332) : Assertion Failed: Fatal Error: glXChooseVisual failed
Installing breakpad exception handler for appid(steam)/version(1570046470)
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
[1020/231407.890104:INFO:crash_reporting.cc(242)] Crash reporting enabled for 
process: browser
assert_20191020231407_6.dmp[4562]: Uploading dump (out-of-process)
/tmp/dumps/assert_20191020231407_6.dmp
[1020/231407.906715:WARNING:crash_reporting.cc(281)] Failed to set crash key: 
UserID with value: 0
[1020/231407.906773:WARNING:crash_reporting.cc(281)] Failed to set crash key: 
BuildID with value: 1570042210
[1020/231407.906777:WARNING:crash_reporting.cc(281)] Failed to set crash key: 
SteamUniverse with value: Public
[1020/231407.906780:WARNING:crash_reporting.cc(281)] Failed to set crash key: 
Vendor with value: Valve
assert_20191020231407_6.dmp[4562]: Finished uploading minidump 
(out-of-process): success = yes
assert_20191020231407_6.dmp[4562]: response: 
CrashID=bp-1182d0aa-9897-4e1e-8016-1d5d82191020
assert_20191020231407_6.dmp[4562]: file 
''/tmp/dumps/assert_20191020231407_6.dmp'', upload yes: 
''CrashID=bp-1182d0aa-9897-4e1e-8016-1d5d82191020''

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  NVIDIA VER 340.107 crashes steam

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

Bug description:
  NVIDIA binary driver VER 340.17 is crashing steam. If I purge all
  NVIDIA drivers Steam runs successfully from Nouveau, but seems to have
  performance issues in game. Steam support was unhelpful and referred
  me to anyone else.

  Steam output from terminal is:

  Running Steam on ubuntu 18.04 64-bit
  STEAM_RUNTIME is enabled automatically
  Pins up-to-date!
  Installing breakpad exception handler for appid(steam)/version(1570046470)
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Installing breakpad exception handler for appid(steam)/version(1570046470)
  Installing breakpad exception handler for appid(steam)/version(1570046470)
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Installing breakpad exception handler for appid(steam)/version(1570046470)
  STEAM_RUNTIME_HEAVY: ./steam-runtime-heavy
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  [2019-10-20 23:14:06] Startup - updater built Oct  2 2019 18:45:27
  Looks like steam didn't shutdown cleanly, scheduling immediate update check
  [2019-10-20 23:14:06] Checking for update on startup
  [2019-10-20 23:14:06] Checking for available updates...
  [2019-10-20 23:14:06] Downloading manifest:

[Desktop-packages] [Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell

But just to be sure, please also follow these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

Title:
  Counter-Strike Global Offensive freezes in gnome-shell

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to ubuntu 19.10, when I launch counter strike global offensive 
from steam the game is frozen. I can alt-tab and close the game. Tried in 
fluxbox window manager where the game works, changed fullscreen to windowed 
fullscreen in the options and tried on gnome again, now the desktop isn't 
responding after launching the game and I had to ctrl-alt-f3 to reboot my 
machine.
  Using a Radeon RX 580 video card.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1848852/+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 1730765] Re: Mounted external devices do not appear in dock

Isn't this fixed in 19.10?

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: Confirmed => 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/1730765

Title:
  Mounted external devices do not appear in dock

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

Bug description:
  Hi,

  when plugging a usb-thumb or external hard drive or any other storage
  media ( phone… )

  I expected them to appear in the dock.

  Instead, they appear on desktop which forces
  - to leave current activity to look at the desktop,
  - or to open nautilus to find the new device.

  Dock is a very nice place for these plugged-in devices ;-) maybe at
  its bottom end, where trash used to be located in Unity dock ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1730765/+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 1848852] Re: Game freezes in gnome-shell

Tracking in:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1673

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

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/1673
   Importance: Unknown
   Status: Unknown

** Summary changed:

- Game freezes in gnome-shell
+ Counter-Strike Global Offensive freezes in gnome-shell

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

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

Title:
  Counter-Strike Global Offensive freezes in gnome-shell

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to ubuntu 19.10, when I launch counter strike global offensive 
from steam the game is frozen. I can alt-tab and close the game. Tried in 
fluxbox window manager where the game works, changed fullscreen to windowed 
fullscreen in the options and tried on gnome again, now the desktop isn't 
responding after launching the game and I had to ctrl-alt-f3 to reboot my 
machine.
  Using a Radeon RX 580 video card.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1848852/+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 1848836] Re: Unmounted drive shortcut is on the dock

I think I disagree with your preference, but rather than relying on my
opinion let's see what the developers say...

Please report the bug upstream:

  https://github.com/micheleg/dash-to-dock/issues

and then tell us the new bug ID.

** Tags added: eoan

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

Title:
  Unmounted drive shortcut is on the dock

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

Bug description:
  Hi,

  On ubuntu 19.10,when the google account is set, there is a shortcut in
  nautilus.

  This shortcut, even when if it's not mounted, is visible in the dock
  when show-mounts option is actived.

  If i'm not wrong, it should be visible only when it's mounted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1848836/+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 1848900] Re: [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

** Summary changed:

- Blank display with Eoan Ermine live DVD on Ryzen 3 2200G
+ [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (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/1848900

Title:
  [amdgpu] Blank display with Eoan Ermine live DVD on Ryzen 3 2200G

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Regression with Ryzen 3 2200G, UEFI Asrock B450 Pro4 motherboard and
  55-75 Hz monitor.

  Booting Xubuntu 19.10 live iso with safe graphics options did give a
  stable desktop display, but

  xubuntu@xubuntu:~$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080 77.00* 
  xubuntu@xubuntu:~$ 

  The monitor is only supposed to have a maximum vertical refresh rate
  of 75 Hz. Xrandr reports 77 Hz as the only choice.  The monitor
  reports 60 Hz, not that I trust the monitor.

  Swapping monitors and running many reboots the situation seems to
  be...

  Old versions of Ubuntu (Bionic and Dingo) can handle the hardware.
  Standard boot sometimes gives a blank screen.  
  Standard boot sometimes gives a badly pixelated display 
  (Ctl-Alt-F6, Ctl-Alt-F7 temporarily improves it).  
  Connecting a 144 Hz monitor convinces something (the firmware?) 
  that fast refreshes are OK on a slow monitor, or at least it fails to 
  reread and abide by the slow monitor's limitations when swapping back.
  Something, I don't know what, convinces the computer to run the display 
  at 60 Hz, sometimes. 

  The motherboard has three video ports; DP, HDMI and VGA (using an onboard 
  DP? to VGA converter chip).  The fast monitor has DP, HDMI and VGA ports, 
  but I only experimented with the DP connection.  The slow monitor has VGA and 
  DVI-D ports.  I experimented with VGA to VGA and HDMI via a passive adapter 
  to DVI.  When running in the badly pixelated mode xorg seems to think that 
  the VGA port is "DP-1".

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.427
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Oct 20 00:17:34 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega 
Series / Radeon Vega Mobile Series] [1002:15dd]
  LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash nomodeset ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: B450 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd07/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sat Oct 19 23:52:52 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile:

[Desktop-packages] [Bug 1848731] Re: Audio output device changes upon unlock/login

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

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 1847570, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1847570
   PulseAudio automatically switches to HDMI sound output on login

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

Title:
  Audio output device changes upon unlock/login

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a ThinkPad X250 and updated To Ubuntu 19.10 today from 19.04.

  
  Locking/Suspending and logging in changes my audio output device.
  This did not happen in 19.04.

  
   How to reproduce 

  When I lock my session with key combination "Win+L" and then unlock it again, 
the sound that's been playing through my headphones/speakers stops playing. 
When I check the audio settings, "HDMI/DisplayPort 2 - Built-in audio" is 
selected.
  When I select "Headphones - Built-in audio", sound continues playing.

  There is no related log output in dmesg.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848731/+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 1848741] Re: Ubuntu 19.10 graphics artefacts on ryzen 2500u

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1848741

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: eoan

** Summary changed:

- Ubuntu 19.10 graphics artefacts on ryzen 2500u
+ Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => 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/1848741

Title:
  Ubuntu 19.10 horizontal graphics corruption on Ryzen 2500u

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have graphics artefacts: screan tearing, pieces of the previous
  window appear in the newly opened window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848741/+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 1848563] Re: Application right-click bug in overview

Thanks for the video, that's excellent.

I found an upstream bug report for the issue already:

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/498

So we should track and discuss it there for now.

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

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/498
   Importance: Unknown
   Status: Unknown

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

** Summary changed:

- Application right-click bug in overview
+ Activities overview unwanted scrolling when clicking popup menu

** Summary changed:

- Activities overview unwanted scrolling when clicking popup menu
+ Activities overview unwanted scrolling when clicking popup menu on page 4 
onward

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

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

Title:
  Activities overview unwanted scrolling when clicking popup menu on
  page 4 onward

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When I right-click on an application in the overview, the page
  automatically moves to the one below when I move the mouse to select
  one of the menu options. This only affects pages 4 and below (the
  right-click on applications on pages 1-3 works as expected), but it
  does not affect the last page (in my case, page 6) presumably since
  there is no page below it to scroll to. The bug happens every time I
  try, no matter the application.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 13:04:45 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-22 (299 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-14 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1848563/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

** Summary changed:

- Automatic login fails and then all subsequent logins fail. Killing 
gnome-session-binary fixes it, or just not using automatic login.
+ [nvidia] Automatic login fails and then all subsequent logins fail. Killing 
gnome-session-binary fixes it, or just not using automatic login.

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

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

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.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.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-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.5+git20190820-0ubuntu3
  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+git20190815-1
  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/gdm3/+bug/1845801/+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 1825626] Re: nvLock: client timed out, taking the lock

Sounds like maybe a fix/workaround went into mutter 3.34. Does anyone
see this problem in Ubuntu 19.10?

** Tags added: bionic

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

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  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] 是一个目录: 
'/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] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  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.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/gnome-desktop/+bug/1825626/+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 1817128] Re: gnome-keyring not automatically unlocked on login

This bug was closed in comment #5. If you have any ongoing issues then
please open new bugs.

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

Title:
  gnome-keyring not automatically unlocked on login

Status in gnome-keyring package in Ubuntu:
  Fix Released

Bug description:
  Hi

  After initializing and filling the login screen, at the start screen
  prompts for password to unlock the session keyring. Is this normal on
  Ubuntu disk 19.04.02?

  Note: When filling the login screen to start the micro, should it not
  be unlocked automatically?

  Attached the image of the request I fired it.

  Thank you


  **
  Hi

  Após inicialização e preenchimento da tela de login, ao iniciar a tela
  pede senha para desbloqueio do chaveiro de sessão. Isso é normal no
  Ubuntu disco 19.04.02?

  Obs: Quando do preenchimento da tela de login para iniciar o micro o
  desbloqueio não deveria ser automático?

  Em anexo a imagem da solicitação de desboquei-o.

  Obrigado

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+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 1809737] Re: Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks xkb.c:2387)

Oops, sorry. I was expecting a Xorg fix since that's what's crashing,
and probably should still get its own fix.

Sorry I can't tell where to propose Onboard fixes other than here. It
doesn't look like it is being maintained(?)


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

** Changed in: onboard (Ubuntu)
 Assignee: (unassigned) => sonald (yinshuiboy)

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

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

Title:
  Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks
  xkb.c:2387)

Status in Onboard:
  New
Status in X.Org X server:
  New
Status in onboard package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Onboard 1.4.1 crashes the entire Desktop if I selected any alternate
  character from pop-up

  [bishop@fringe ~]$ ls /usr/share/xsessions/
  xfce.desktop

  [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP
  XFCE

  [bishop@fringe ~]$ echo $XDG_SESSION_TYPE
  x11

  [bishop@fringe ~]$ cat /etc/*-release
  Fedora release 29 (Twenty Nine)
  NAME=Fedora
  VERSION="29 (Twenty Nine)"
  ID=fedora
  VERSION_ID=29
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f29"
  PRETTY_NAME="Fedora 29 (Twenty Nine)"
  ANSI_COLOR="0;34"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:29"
  HOME_URL="https://fedoraproject.org/;
  
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/;
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help;
  BUG_REPORT_URL="https://bugzilla.redhat.com/;
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=29
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=29
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy;
  Fedora release 29 (Twenty Nine)
  Fedora release 29 (Twenty Nine)

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1809737/+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 1791405] Re: bluetooth always in discoverable mode (security issue)

** Also affects: gnome-bluetooth (Ubuntu Focal)
   Importance: Medium
   Status: Fix Released

** Also affects: bluez (Ubuntu Focal)
   Importance: Undecided
   Status: Confirmed

** Changed in: bluez (Ubuntu Focal)
   Status: Confirmed => Triaged

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

** Changed in: bluez (Ubuntu Eoan)
   Status: Fix Committed => Triaged

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

** No longer affects: bluez (Ubuntu Eoan)

** Tags added: fixed-upstream

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

Title:
  bluetooth always in discoverable mode (security issue)

Status in bluez package in Ubuntu:
  Triaged
Status in gnome-bluetooth package in Ubuntu:
  Fix Released
Status in gnome-bluetooth source package in Bionic:
  Fix Released
Status in gnome-bluetooth source package in Cosmic:
  Fix Released
Status in gnome-bluetooth source package in Disco:
  Fix Released
Status in bluez source package in Focal:
  Triaged
Status in gnome-bluetooth source package in Focal:
  Fix Released
Status in gnome-bluetooth package in Fedora:
  Won't Fix

Bug description:
  Excerpt from a similar report
  (https://bugzilla.redhat.com/show_bug.cgi?id=1602985) :

  Opening the Bluetooth settings will make the device discoverable
  again, but does not make the device undiscoverable after the settings
  are closed (this is not intended behavior; devices should only be
  discoverable when the bluetooth settings UI is open).

  There seem to be a merge request :

  https://gitlab.gnome.org/GNOME/gnome-bluetooth/merge_requests/1

  Could you please merge it asap, it should be treated as a security
  issue IMHO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1791405/+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 1782425] Re: Unable to change Power off timeout from 60 seconds ("The system will power off automatically in 60 seconds") to custom value

** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #369
   https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/369

** Changed in: gnome-settings-daemon
   Importance: Medium => Unknown

** Changed in: gnome-settings-daemon
   Status: Confirmed => Unknown

** Changed in: gnome-settings-daemon
 Remote watch: GNOME Bug Tracker #790128 => 
gitlab.gnome.org/GNOME/gnome-settings-daemon/issues #369

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

Title:
  Unable to change Power off timeout from 60 seconds ("The system will
  power off automatically in 60 seconds") to custom value

Status in GNOME Settings Daemon:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.04 LTS installed with GNOME desktop
  2. Click Power Off button or physical ACPI Power Button and see window with 
default 60 seconds timeout "The system will power off automatically in 60 
seconds"
  3. Try to set lower or higher timeout value anywhere (in `dconf`, 
`gsettings`, etc.)

  Expected results:
  User is able to change Power off timeout from 60 seconds ("The system will 
power off automatically in 60 seconds") to custom value.

  Actual results:
  User is unable to change Power off timeout from 60 seconds ("The system will 
power off automatically in 60 seconds") to custom value.

  Note: problem was first described on AskUbuntu (
  https://askubuntu.com/q/1057271/66509 ).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.2-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 18 22:42:50 2018
  DisplayManager: gdm3
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2018-04-28 (81 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1782425/+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 1809737] Re: Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks xkb.c:2387)

2019-10-20 Thread sonald

daniel,

This is an attempted fix for onboard, is it appropriate to submit to xserver 
project? 
BTW, I'm still wondering why this have not been fixed for so long.

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

Title:
  Onboard crashes the entire desktop (Xorg crashes in _XkbSetMapChecks
  xkb.c:2387)

Status in Onboard:
  New
Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  Onboard 1.4.1 crashes the entire Desktop if I selected any alternate
  character from pop-up

  [bishop@fringe ~]$ ls /usr/share/xsessions/
  xfce.desktop

  [bishop@fringe ~]$ echo $XDG_CURRENT_DESKTOP
  XFCE

  [bishop@fringe ~]$ echo $XDG_SESSION_TYPE
  x11

  [bishop@fringe ~]$ cat /etc/*-release
  Fedora release 29 (Twenty Nine)
  NAME=Fedora
  VERSION="29 (Twenty Nine)"
  ID=fedora
  VERSION_ID=29
  VERSION_CODENAME=""
  PLATFORM_ID="platform:f29"
  PRETTY_NAME="Fedora 29 (Twenty Nine)"
  ANSI_COLOR="0;34"
  LOGO=fedora-logo-icon
  CPE_NAME="cpe:/o:fedoraproject:fedora:29"
  HOME_URL="https://fedoraproject.org/;
  
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/;
  SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help;
  BUG_REPORT_URL="https://bugzilla.redhat.com/;
  REDHAT_BUGZILLA_PRODUCT="Fedora"
  REDHAT_BUGZILLA_PRODUCT_VERSION=29
  REDHAT_SUPPORT_PRODUCT="Fedora"
  REDHAT_SUPPORT_PRODUCT_VERSION=29
  PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy;
  Fedora release 29 (Twenty Nine)
  Fedora release 29 (Twenty Nine)

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1809737/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

Reploy #17, no, no sound could be record. all quiet.

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1767995] Re: Horizontal scroll doesn't honor Natural Scrolling preference

2019-10-20 Thread Paul White

** Tags added: eoan

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

Title:
  Horizontal scroll doesn't honor Natural Scrolling preference

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

Bug description:
  It appears that the horizontal scroll setting is locked to only one
  direction and does not honor the natural scrolling preference.

  This has been posted on askubuntu.com
  (https://askubuntu.com/questions/1029128/inverted-horizontal-
  scrolling-ubuntu-18-04), but hasn't been reported as a bug yet (as per
  my searches).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767995/+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 1767995] Re: Horizontal scroll doesn't honor Natural Scrolling preference

2019-10-20 Thread tom

Still in 19.10

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

Title:
  Horizontal scroll doesn't honor Natural Scrolling preference

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

Bug description:
  It appears that the horizontal scroll setting is locked to only one
  direction and does not honor the natural scrolling preference.

  This has been posted on askubuntu.com
  (https://askubuntu.com/questions/1029128/inverted-horizontal-
  scrolling-ubuntu-18-04), but hasn't been reported as a bug yet (as per
  my searches).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1767995/+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 1847247]

2019-10-20 Thread Ehsan-mozilla

Hi Olivier,

Thanks for the bug report.  It has been a while since that patch was
landed so my memory may be a bit rusty, but I don't believe we
considered the use case of Linux distributions side-loading dictionaries
in this way...

Would it be a useful work-around to convert these dictionaries to the
[WebExtension dictionary format](https://developer.mozilla.org/en-
US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/dictionaries)?  I
haven't tested this myself, but at least in Firefox it is [possible to
side-load
extensions](https://extensionworkshop.com/documentation/publish
/distribute-sideloading/#standard-extension-folders), so perhaps
installing such extensions to a location like
`/usr/lib/thunderbird/extensions/{uuid}` may be a useful workaround?

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

Title:
  External dictionaries are not loaded

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

Bug description:
  On Ubuntu Eoan and most recent Thunderbird, the external Hunspell
  dictionaries are not available anymore on Thunderbird for spellcheck.

  The symlink is still in place:
  lrwxrwxrwx   1 root root20 dec 15  2017 dictionaries -> 
../../share/hunspell

  But data doesn't get loaded for some reason.

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

2019-10-20 Thread Kmaglione+bmo

Yes, we considered it. That directory was never intended for third-party
use. If you want to install distribution dictionaries specifically for
Thunderbird, you need to bundle them as extensions.

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

Title:
  External dictionaries are not loaded

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

Bug description:
  On Ubuntu Eoan and most recent Thunderbird, the external Hunspell
  dictionaries are not available anymore on Thunderbird for spellcheck.

  The symlink is still in place:
  lrwxrwxrwx   1 root root20 dec 15  2017 dictionaries -> 
../../share/hunspell

  But data doesn't get loaded for some reason.

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

2019-10-20 Thread Olivier Tilloy

@kmag @ehsan @aswan: can you please comment on the above request?

At the moment I'm holding back on updating the Ubuntu packages to
version 68 in stable Ubuntu releases (it's only available in version
19.10 that was released yesterday) because from a user perspective this
is a regression.

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

Title:
  External dictionaries are not loaded

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

Bug description:
  On Ubuntu Eoan and most recent Thunderbird, the external Hunspell
  dictionaries are not available anymore on Thunderbird for spellcheck.

  The symlink is still in place:
  lrwxrwxrwx   1 root root20 dec 15  2017 dictionaries -> 
../../share/hunspell

  But data doesn't get loaded for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1847247/+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 1848965] [NEW] Video Playback very choppy

2019-10-20 Thread Bradley Wooldridge

Public bug reported:

My laptop is HP Pavilion g7 (Intel® Core™ i5-2430M CPU with Radeon HD
6470M and Intel HD 3000 GPUs

Already have played with Ubuntu on older spec desktops with no issues at
all, however when when installing Ubuntu 18.04 from installation USB,
had to boot with nomodeset to overcome freezing as a result of Ubuntu
18.04 not recognising/supporting these drivers

Tried to search for additional drivers but none found

Video handling resorts to llvmpipe (LLVM 9.0.0, 256 bits)

My problem is that Video Playback is VLC very choppy in full screen mode
- seems to get a little better when minimised, but effectively not
usable.

Have tried many threads posted regarding this problem, but nothing seems
to work.

Would really like to migrate my workload onto Ubuntu 18.04 operating
system, but this seems to be a real non starter where i can't play video
content, as video editing is a core function in my workload.

Not sure if there is a solution for this, however after researching many
similar threads, coupled with your in depth response to similar problems
leaves me hopeful that you can point me in the right direction, or worst
case scenario tell me there is no solution at all, and that I will have
to stick to the hateful Windows 10 which is supported and working.

1) not sure if it is just a simple graphics acceleration problem ?
2) as flgrx no longer supported (for AMD Catalyst on Radeon HD 6470 M - can I 
disable this GPU somewhere on boot - as this seems to be where boot goes into a 
tizz. If so, how would I do this.
3) if i did this would XORG then recognise other GPU - Intel HD 3000 and give 
me correct rendering to eliminate choppy video

I am a noob, but have been playing with Ubuntu for some time, albeit at
very low level, not totally computer illiterate, but do feel I am out of
my depth in trying to resolve this. It just seems odd that it works fine
on much lower spec and older desktops, but that I cant get this to work
on my not so outdated laptop.

Ubuntu Release 18.04.3

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

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

Title:
  Video Playback very choppy

Status in xorg package in Ubuntu:
  New

Bug description:
  My laptop is HP Pavilion g7 (Intel® Core™ i5-2430M CPU with Radeon HD
  6470M and Intel HD 3000 GPUs

  Already have played with Ubuntu on older spec desktops with no issues
  at all, however when when installing Ubuntu 18.04 from installation
  USB, had to boot with nomodeset to overcome freezing as a result of
  Ubuntu 18.04 not recognising/supporting these drivers

  Tried to search for additional drivers but none found

  Video handling resorts to llvmpipe (LLVM 9.0.0, 256 bits)

  My problem is that Video Playback is VLC very choppy in full screen
  mode - seems to get a little better when minimised, but effectively
  not usable.

  Have tried many threads posted regarding this problem, but nothing
  seems to work.

  Would really like to migrate my workload onto Ubuntu 18.04 operating
  system, but this seems to be a real non starter where i can't play
  video content, as video editing is a core function in my workload.

  Not sure if there is a solution for this, however after researching
  many similar threads, coupled with your in depth response to similar
  problems leaves me hopeful that you can point me in the right
  direction, or worst case scenario tell me there is no solution at all,
  and that I will have to stick to the hateful Windows 10 which is
  supported and working.

  1) not sure if it is just a simple graphics acceleration problem ?
  2) as flgrx no longer supported (for AMD Catalyst on Radeon HD 6470 M - can I 
disable this GPU somewhere on boot - as this seems to be where boot goes into a 
tizz. If so, how would I do this.
  3) if i did this would XORG then recognise other GPU - Intel HD 3000 and give 
me correct rendering to eliminate choppy video

  I am a noob, but have been playing with Ubuntu for some time, albeit
  at very low level, not totally computer illiterate, but do feel I am
  out of my depth in trying to resolve this. It just seems odd that it
  works fine on much lower spec and older desktops, but that I cant get
  this to work on my not so outdated laptop.

  Ubuntu Release 18.04.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848965/+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 1848940] Re: gnome-control-center does not respect symbolic links

2019-10-20 Thread Gunnar Hjalmarsson

Hmm.. I'm afraid that's a bit over my head. But yes, it's apparent that
what you want to do is not compatible with how the Ubuntu/GNOME desktop
is designed.

A simple way to prevent gnome-control-center from touching
/etc/default/locale and /etc/default/keyboard is to create a second
user. By doing so, changes of the language and input source settings
will be saved in user specific files and only affect the current user.
Not sure if that would help in your case.

Otherwise this is an upstream design matter, so an upstream issue would
be the best way to propose a reconsideration of the design in this
respect.

https://gitlab.gnome.org/GNOME/gnome-control-center/issues

** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Wishlist

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

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

Title:
gnome-control-center does not respect symbolic links

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

Bug description:
Configuration files created as symbolic links are overwritten by
gnome-control-center. This probably affects any configuration file
managed by gnome-control-center.

Test case:
--

1.) Create symbolic links of the following files

sudo mv /etc/default/locale /etc/default/locale.test && sudo ln -s
/etc/default/locale.test /etc/default/locale

sudo mv /etc/default/keyboard /etc/default/keyboard.test && sudo ln -s
/etc/default/keyboard.test /etc/default/keyboard

sudo mv /etc/hostname /etc/hostname.test && sudo ln -s
/etc/hostname.test /etc/hostname

2.) Change the language, the keyboard layout and the hostname in
gnome-control-center.

Expected result:
The link destination should be overwritten so that the symbolic link is
preserved.

Actual result:
The symbolic link itself is overwritten so that the symbolic link is lost.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848940/+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 1848951] Re: Xorg and gnome-shell consuming large amount of CPU

** Patch removed: "Screenshot from 2019-10-20 20-01-53.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848951/+attachment/5298666/+files/Screenshot%20from%202019-10-20%2020-01-53.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/1848951

Title:
  Xorg and gnome-shell consuming large amount of CPU

Status in xorg package in Ubuntu:
  New

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848951/+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 1848958] Re: Suspend takes 3 minutes and screen is garbled after resume with nouveau driver after upgrade to 19.10

2019-10-20 Thread DRracer

** Description changed:

  In Kubuntu 19.04 (kernel 5.0) suspend and resume was almost working on
  my machine, say 9 of 10 times it went well. The problematic suspends
  were mostly when there way an OpenGL app running. I was able to lived
  with that, the machine was able to achieve 30+days uptime.
  
  After upgrading to 19.10 the machine now behaves weird:
- 1. Suspend takes 3 minutes to complete. The screen blanks relatively fast as 
before, but the machine is up and running for 3 minutes before finally entering 
sleep.
+ 1. Suspend takes 3 minutes to complete. The screen blanks relatively fast as 
before, but the machine is up and running for another 3 minutes before finally 
entering sleep.
  
  2. Resume is normal as before and does its job, however:
  - the screen is completely garbled. It looks like the video RAM content was 
lost.
  - the GPU seems to operate normally, the cursor is drawn correctly (see 
attached photo).
  
  3. Restarting the X-server resolves the issue, i.e. the screen contains
  reasonable content
  
  4. Text console is working correctly even without restarting the
  X-server
  
  I'd like to help fixing this or at least provide technical info that
  will lead to fixing this issue, please tell me what shall I try/test.
  Thank you.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Oct 20 23:18:53 2019
  DistUpgraded: 2019-10-19 10:33:23,032 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
-  NVIDIA Corporation G94M [GeForce 9800M GS] [10de:062b] (rev a1) (prog-if 00 
[VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] G94M [GeForce 9800M 
GS] [1462:7220]
+  NVIDIA Corporation G94M [GeForce 9800M GS] [10de:062b] (rev a1) (prog-if 00 
[VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] G94M [GeForce 9800M 
GS] [1462:7220]
  InstallationDate: Installed on 2019-04-21 (182 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Micro-Star International GT627
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=bec74662-d895-4581-a6ea-6f92fea32635 ro resume=/dev/sda6 iommu=soft
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (1 days ago)
  dmi.bios.date: 04/07/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A1651IMS.10V
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-1651
  dmi.board.vendor: MSI
  dmi.board.version: Ver 1.000
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA1651IMS.10V:bd04/07/2009:svnMicro-StarInternational:pnGT627:pvrVer1.000:rvnMSI:rnMS-1651:rvrVer1.000:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: GT627
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Ver 1.000
  dmi.sys.vendor: Micro-Star International
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Description changed:

  In Kubuntu 19.04 (kernel 5.0) suspend and resume was almost working on
  my machine, say 9 of 10 times it went well. The problematic suspends
  were mostly when there way an OpenGL app running. I was able to lived
  with that, the machine was able to achieve 30+days uptime.
  
  After upgrading to 19.10 the machine now behaves weird:
  1. Suspend takes 3 minutes to complete. The screen blanks relatively fast as 
before, but the machine is up and running for another 3 minutes before finally 
entering sleep.
  
  2. Resume is normal as before and does its job, however:
  - the screen is completely garbled. It looks like the video RAM content was 
lost.
  - the GPU seems to operate normally, the cursor is drawn correctly (see 
attached photo).
  
  3. Restarting the X-server resolves the issue, i.e. the screen contains
  reasonable content
  
  4. Text

[Desktop-packages] [Bug 1848958] [NEW] Suspend takes 3 minutes and screen is garbled after resume with nouveau driver after upgrade to 19.10

2019-10-20 Thread DRracer

Public bug reported:

In Kubuntu 19.04 (kernel 5.0) suspend and resume was almost working on
my machine, say 9 of 10 times it went well. The problematic suspends
were mostly when there way an OpenGL app running. I was able to lived
with that, the machine was able to achieve 30+days uptime.

After upgrading to 19.10 the machine now behaves weird:
1. Suspend takes 3 minutes to complete. The screen blanks relatively fast as 
before, but the machine is up and running for another 3 minutes before finally 
entering sleep.

2. Resume is normal as before and does its job, however:
- the screen is completely garbled. It looks like the video RAM content was 
lost.
- the GPU seems to operate normally, the cursor is drawn correctly (see 
attached photo).

3. Restarting the X-server resolves the issue, i.e. the screen contains
reasonable content

4. Text console is working correctly even without restarting the
X-server

5. Tried running KDE with and without compositor, got the same results.

I'd like to help fixing this or at least provide technical info that
will lead to fixing this issue, please tell me what shall I try/test.
Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xserver-xorg-video-nouveau 1:1.0.16-1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sun Oct 20 23:18:53 2019
DistUpgraded: 2019-10-19 10:33:23,032 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 NVIDIA Corporation G94M [GeForce 9800M GS] [10de:062b] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] G94M [GeForce 9800M GS] 
[1462:7220]
InstallationDate: Installed on 2019-04-21 (182 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: Micro-Star International GT627
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=bec74662-d895-4581-a6ea-6f92fea32635 ro resume=/dev/sda6 iommu=soft
SourcePackage: xserver-xorg-video-nouveau
UpgradeStatus: Upgraded to eoan on 2019-10-19 (1 days ago)
dmi.bios.date: 04/07/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A1651IMS.10V
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-1651
dmi.board.vendor: MSI
dmi.board.version: Ver 1.000
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA1651IMS.10V:bd04/07/2009:svnMicro-StarInternational:pnGT627:pvrVer1.000:rvnMSI:rnMS-1651:rvrVer1.000:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: GT627
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: Ver 1.000
dmi.sys.vendor: Micro-Star International
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan ubuntu

** Attachment added: "garbled screen content"
   
https://bugs.launchpad.net/bugs/1848958/+attachment/5298715/+files/P1450191s.jpg

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

Title:
  Suspend takes 3 minutes and screen is garbled after resume with
  nouveau driver after upgrade to 19.10

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  In Kubuntu 19.04 (kernel 5.0) suspend and resume was almost working on
  my machine, say 9 of 10 times it went well. The problematic suspends
  were mostly when there way an OpenGL app running. I was able to lived
  with that, the machine was able to achieve 30+days uptime.

  After upgrading to 19.10 the machine now behaves weird:
  1. Suspend takes 3 minutes to complete. The screen blanks relatively fast as 
before, but the machine is up and running for another 3 minutes before finally 
entering sleep.

  2. Resume is normal as before and does its job, however:
  - the screen is completely garbled. It looks like the video RAM content was 
lost.
  - the GPU seems to

[Desktop-packages] [Bug 1848940] Re: gnome-control-center does not respect symbolic links

2019-10-20 Thread Matthias Kruzenski

In short: Symbolic links are absolutely necessary to exclude files from
overlayfs.

Long explanation:
I use overlayfs to protect my system's root file system. With overlayfs all
changes are only in RAM. So any change is only temporary.

I want some changes to be persistent. To do that I copy these files to
another partition and create a link. For example I want that my system
remembers any network connection so I move /etc/NetworkManager/system-
connections/ to another partition and create a link to it. The same
applies to the home directory or /var/lib/AccountsService/users/. This
will exclude these files from overlayfs.

This gives me a superfast system that allows me to do almost any
experiment. If something goes wrong I just restart it and it's the same
as before. Even more, it's almost impossible to infect this system with
malware. It also use full disk encryption (including /boot) and runs
from usb. It is a highly secure system...

I'm pretty sure there are many more use cases that require symbolic
links for config files.

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

Title:
gnome-control-center does not respect symbolic links

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

Bug description:
Configuration files created as symbolic links are overwritten by
gnome-control-center. This probably affects any configuration file
managed by gnome-control-center.

Test case:
--

1.) Create symbolic links of the following files

sudo mv /etc/default/locale /etc/default/locale.test && sudo ln -s
/etc/default/locale.test /etc/default/locale

sudo mv /etc/default/keyboard /etc/default/keyboard.test && sudo ln -s
/etc/default/keyboard.test /etc/default/keyboard

sudo mv /etc/hostname /etc/hostname.test && sudo ln -s
/etc/hostname.test /etc/hostname

2.) Change the language, the keyboard layout and the hostname in
gnome-control-center.

Expected result:
The link destination should be overwritten so that the symbolic link is
preserved.

Actual result:
The symbolic link itself is overwritten so that the symbolic link is lost.

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

[Desktop-packages] [Bug 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

2019-10-20 Thread Dexuan Cui

The typical boot-up time of my Ubuntu VM on Hyper-V is 20~30 seconds for
a Desktop version of Ubuntu, and 10~20 seconds for a Server version. I
tried Ubuntu 19.04 just now and it also took 20+ seconds.

I never achieve a boot-up time of 2s.

I do know Ubuntu can boot up fast in 2~3 seconds in WSL (Windows
Subsystem for Linux), though I didn't try it in person.

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

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

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  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/1848534/+subscriptions

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

[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic

2019-10-20 Thread Ivan Cherkasov

Same problem on Ubuntu 18.04.3 LTS. ls hangs in
/run/user/1000/gvfs/mtp:host=... .

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

Title:
  MTP not working/very slow on Bionic

Status in libmtp:
  New
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmtp/+bug/1792085/+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 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

2019-10-20 Thread M

Hi,

If possible, please try 19.04 or LTS 18.04 and compare startup time - my
guess is that it will start almost immediately and you will see, that
you already reproduced it :)

I'm sure let's say in 90% :) -> 28 seconds is looonnnggg (like I said,
I've got about 2 seconds for older Ubuntu).

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

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

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  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/1848534/+subscriptions

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

[Desktop-packages] [Bug 1848951] Re: Xorg and gnome-shell consuming large amount of CPU

2019-10-20 Thread Ubuntu Foundations Team Bug Bot

The attachment "Screenshot from 2019-10-20 20-01-53.png" 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1848951

Title:
  Xorg and gnome-shell consuming large amount of CPU

Status in xorg package in Ubuntu:
  New

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848951/+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 1848942] Re: Freeze on opening font viewer

2019-10-20 Thread Artyom

I do not think that it is a duplicate of bug 1845362. As for me, it
never crashes - always freezes

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

Title:
  Freeze on opening font viewer

Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  When I open gnome-font-viewer, after few seconds interface freezes and
  I only can move my cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:02:24 2019
  InstallationDate: Installed on 2019-10-20 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1848942/+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 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

2019-10-20 Thread Dexuan Cui

Hi M, since I can not reproduce the delay issue, I don't know what I can
do now. :-(

Do you think if it's related to Xorg?

Can you install a new VM from scratch from the server .iso
(http://releases.ubuntu.com/19.10/ubuntu-19.10-live-server-amd64.iso)
and see if you can reproduce the same issue?

The server .iso doesn't install Xorg, and a lot of other packages used
in a Desktop environment. I hope you can not repro the issue with it,
then we'll have a good starting point.

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

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

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1848951] Re: Xorg and gnome-shell consuming large amount of CPU

** Description changed:

- I have installed fresh Ubuntu 18.04.03 on my PC.
+ I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had Ubuntu
+ 16.04 version but didn't have any such problems with the cpu usage.
  
  But I have saw in terminal that somehow the processes Xorg and gnome-
- shell use always 20% when just moving the mouse around.
+ shell use always 20% when just moving the mouse around for 18.04
+ version.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
-  Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
-Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
-  Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
-Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
+  Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
+    Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
+  Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
+    Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

Title:
  Xorg and gnome-shell consuming large amount of CPU

Status in xorg package in Ubuntu:
  New

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC. Previously I had
  Ubuntu 16.04 version but didn't have any such problems with the cpu
  usage.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around for 18.04
  version.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])

[Desktop-packages] [Bug 1848940] Re: gnome-control-center does not respect symbolic links

2019-10-20 Thread Gunnar Hjalmarsson

This does not seem to be a bug. AFAIK you are not expected to replace
those system config files with symlinks. Why do you want to do that?

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

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

Title:
  gnome-control-center does not respect symbolic links

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

Bug description:
  Configuration files created as symbolic links are overwritten by
  gnome-control-center. This probably affects any configuration file
  managed by gnome-control-center.

  Test case:
  --

  1.) Create symbolic links of the following files

  sudo mv /etc/default/locale /etc/default/locale.test && sudo ln -s
  /etc/default/locale.test /etc/default/locale

  sudo mv /etc/default/keyboard /etc/default/keyboard.test && sudo ln -s
  /etc/default/keyboard.test /etc/default/keyboard

  sudo mv /etc/hostname /etc/hostname.test && sudo ln -s
  /etc/hostname.test /etc/hostname

  2.) Change the language, the keyboard layout and the hostname in
  gnome-control-center.

  
  Expected result:
  The link destination should be overwritten so that the symbolic link is 
preserved.

  Actual result:
  The symbolic link itself is overwritten so that the symbolic link is lost.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848940/+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 1848534] Re: [Microsoft Hyper-V guest] System shows graphic artifacts for a moment, then text cursor for about minute and then starts

2019-10-20 Thread M

Hi,

Thanks for comments #25 and #26,

I don't know how fast is your machine, but on mine earlier (before
19.10) I had startup in just few seconds, now have this delay. Yes, this
is maybe not critical, but should be fixed, because can go into Ubuntu
20.04 ;)

Anyway, I'm using stock kernel 5.3 + I've done "systemd-analyze blame"

In first line I had also many seconds with plymouth-quit-wait.service.

I've done

sudo apt remove plymouth-theme-ubuntu-text
sudo apt remove plymouth-theme-ubuntu-logo
sudo apt remove lighttpd

and removed splash from /etc/default/grub

(yes, I can do it, this is not my critical VM)

Result:

kernel starts, I see messages, then screen cleans and I have delay

systemd-analyze doesn't show anything specific (all delays are very
short - the longest is gdm like yours and the rest looks quite similar)

I don't know if this is Ubuntu or Hyper-V specific,

other ideas?

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

Title:
  [Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
  then text cursor for about minute and then starts

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

Bug description:
  AFter upgrade system shows graphic artefacts for a moment and then
  text cursor for about minute (it looks like hanged) and then starts.

  In 19.04 startup required 1 or 2 seconds.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 17 17:42:27 2019
  InstallationDate: Installed on 2019-07-04 (104 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  VarLogDistupgradeLspcitxt:
   
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  InstallationDate: Installed on 2019-07-04 (105 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: xorg-server (not installed)
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash 
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  RfKill:
   
  Tags:  eoan ubuntu
  Uname: Linux 5.3.0-18-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/30/2019
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core

[Desktop-packages] [Bug 1848951] Re: Xorg and gnome-shell consuming large amount of CPU

** Attachment added: "Screenshot from 2019-10-20 20-05-06.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848951/+attachment/5298682/+files/Screenshot%20from%202019-10-20%2020-05-06.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/1848951

Title:
  Xorg and gnome-shell consuming large amount of CPU

Status in xorg package in Ubuntu:
  New

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: B85M-D2V
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848951/+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 1848951] [NEW] Xorg and gnome-shell consuming large amount of CPU

Public bug reported:

I have installed fresh Ubuntu 18.04.03 on my PC.

But I have saw in terminal that somehow the processes Xorg and gnome-
shell use always 20% when just moving the mouse around.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-31-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 20 20:54:50 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 
250X] [1002:683d] (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 [1462:2710]
InstallationDate: Installed on 2019-10-19 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B85M-D2V
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/06/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: B85M-D2V
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

** Patch added: "Screenshot from 2019-10-20 20-01-53.png"
   
https://bugs.launchpad.net/bugs/1848951/+attachment/5298666/+files/Screenshot%20from%202019-10-20%2020-01-53.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/1848951

Title:
  Xorg and gnome-shell consuming large amount of CPU

Status in xorg package in Ubuntu:
  New

Bug description:
  I have installed fresh Ubuntu 18.04.03 on my PC.

  But I have saw in terminal that somehow the processes Xorg and gnome-
  shell use always 20% when just moving the mouse around.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:54:50 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: amdgpu, 19.30-855429, 5.0.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / 
R7 250X] [1002:683d] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] R7770-PMD1GD5 
[1462:2710]
  InstallationDate: Installed on 2019-10-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D2V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=1df6f37d-128f-4083-bd66-0a5c437227a0 ro

[Desktop-packages] [Bug 1848942] Re: Freeze on opening font viewer

2019-10-20 Thread Paul White

Probably a duplicate of bug 1845362

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

Title:
  Freeze on opening font viewer

Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  When I open gnome-font-viewer, after few seconds interface freezes and
  I only can move my cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:02:24 2019
  InstallationDate: Installed on 2019-10-20 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1848942/+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 1848942] [NEW] Freeze on opening font viewer

2019-10-20 Thread Artyom

Public bug reported:

When I open gnome-font-viewer, after few seconds interface freezes and I
only can move my cursor.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-font-viewer 3.34.0-1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 20 20:02:24 2019
InstallationDate: Installed on 2019-10-20 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-font-viewer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Freeze on opening font viewer

Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  When I open gnome-font-viewer, after few seconds interface freezes and
  I only can move my cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-font-viewer 3.34.0-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 20:02:24 2019
  InstallationDate: Installed on 2019-10-20 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1848942/+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 1848940] [NEW] gnome-control-center does not respect symbolic links

2019-10-20 Thread Matthias Kruzenski

Public bug reported:

Configuration files created as symbolic links are overwritten by gnome-
control-center. This probably affects any configuration file managed by
gnome-control-center.

Test case:
--

1.) Create symbolic links of the following files

sudo mv /etc/default/locale /etc/default/locale.test && sudo ln -s
/etc/default/locale.test /etc/default/locale

sudo mv /etc/default/keyboard /etc/default/keyboard.test && sudo ln -s
/etc/default/keyboard.test /etc/default/keyboard

sudo mv /etc/hostname /etc/hostname.test && sudo ln -s
/etc/hostname.test /etc/hostname

2.) Change the language, the keyboard layout and the hostname in gnome-
control-center.


Expected result:
The link destination should be overwritten so that the symbolic link is 
preserved.

Actual result:
The symbolic link itself is overwritten so that the symbolic link is lost.

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


** Tags: link overwritten symbolic

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

Title:
  gnome-control-center does not respect symbolic links

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

Bug description:
  Configuration files created as symbolic links are overwritten by
  gnome-control-center. This probably affects any configuration file
  managed by gnome-control-center.

  Test case:
  --

  1.) Create symbolic links of the following files

  sudo mv /etc/default/locale /etc/default/locale.test && sudo ln -s
  /etc/default/locale.test /etc/default/locale

  sudo mv /etc/default/keyboard /etc/default/keyboard.test && sudo ln -s
  /etc/default/keyboard.test /etc/default/keyboard

  sudo mv /etc/hostname /etc/hostname.test && sudo ln -s
  /etc/hostname.test /etc/hostname

  2.) Change the language, the keyboard layout and the hostname in
  gnome-control-center.

  
  Expected result:
  The link destination should be overwritten so that the symbolic link is 
preserved.

  Actual result:
  The symbolic link itself is overwritten so that the symbolic link is lost.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848940/+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 1823550] Re: GtkSourceView (gedit - Text Editor and others) wrongly has monospaced font in dropdown (context) menu

2019-10-20 Thread Norbert

** Tags removed: cosmic eoan

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

Title:
  GtkSourceView (gedit - Text Editor and others) wrongly has monospaced
  font in dropdown (context) menu

Status in GtkSourceView:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Invalid
Status in gtksourceview3 package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Invalid
Status in pluma package in Ubuntu:
  Invalid
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Released
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 17.04 or later installed
  2. Open any application with GtkSourceView component - such as Pluma, Gedit, 
Giggle, Gitg, gnome-builder and maybe others (see complete list with `apt-cache 
rdepends libgtksourceview-3.0-1`)
  3. Click right mouse button on text zone

  Expected result:
  * dropdown menu has normal font as all other interface elements

  Actual result:
  * dropdwon menu wrongly has monospaced font

  Notes:
  * first seen in 17.04, but persists in 17.10, 18.04 LTS, 18.10, 19.04 
releases.
  * seems to be caused by GTK3 library

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: pluma 1.18.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  7 20:13:24 2019
  InstallationDate: Installed on 2018-08-07 (243 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: pluma
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtksourceview/+bug/1823550/+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 1810745] Re: HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel on 18.04 LTS, 18.10, 19.04 and 19.10

2019-10-20 Thread Norbert

** Tags removed: cosmic
** Tags added: focal

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

Title:
  HPLIP hp-systray tray icon does not show dropdown menu in MATE Panel
  on 18.04 LTS, 18.10, 19.04 and 19.10

Status in HPLIP:
  New
Status in hplip package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu MATE 18.04 LTS with all updates
  2. Install HPLIP into it with `sudo apt install hplip-gui`
  3. Log out.

  Expected results:
  * HPLIP shows hp-systray icon and its fully functional

  Actual results:
  * HPLIP shows hp-systrat icon but it is non-functional (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mate-panel 1.20.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Jan  7 12:15:48 2019
  InstallationDate: Installed on 2019-01-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: mate-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1810745/+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 1721955] Re: Human, Human-Clearlooks and other themes have incorrect gray window title color

2019-10-20 Thread Norbert

** Tags removed: cosmic
** Tags added: focal

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

Title:
  Human, Human-Clearlooks and other themes have incorrect gray window
  title color

Status in community-themes package in Ubuntu:
  New
Status in compiz package in Ubuntu:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in human-theme package in Ubuntu:
  Confirmed
Status in marco package in Ubuntu:
  Invalid
Status in mate-themes package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 17.10 MATE or 18.04 LTS MATE
  2. Install Human theme from `human-theme` package
  3. Select Human theme from `mate-control-center` Appearance

  Expected results:
  window title color is set to Ubuntu's orange (#FFBE6B)

  Actual results:
  window title color is set to different gray/silver color (#a5a5a2)

  Note:
  other themes are affected too.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: human-theme 0.39.2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: i386
  CurrentDesktop: MATE
  Date: Sat Oct  7 15:43:03 2017
  InstallationDate: Installed on 2017-10-07 (0 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 
(20170925.1)
  PackageArchitecture: all
  SourcePackage: human-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/community-themes/+bug/1721955/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2019-10-20 Thread Bickhaus

In case it's helpful, I posted a bug about this (but, perhaps,
incorrectly as an ALSA problem) with my Alsa and PulseAudio information:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846290

Above, it was mentioned that perhaps this is regards to module-switch-
on-connect.  FWIW, when I was testing Fedora 31, it correctly picked my
onboard sound controller rather than my HDMI monitors (which have an
audio passthrough but no onboard audio capabilities/speakers of their
own) from the start and never tried to switch the output device to HDMI.

I have further noticed that when I try to launch games via Steam, they
have no sound, even if I make sure line out is the selected sound output
device in gnome-settings prior to launching Steam.  I did not have this
problem on 19.04, so I wonder if it's related?  Any tips on how I can
further investigate and maybe file a separate bug report if necessary?

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Eoan:
  Triaged

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1845801] Re: Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2019-10-20 Thread dehein

Nvidia GTX1060 proprietary driver. After upgrade i had to disable the autologin 
via command line:
press ctrl + alt + F3 
login with username
now my background and steam where always shown, just type in everything even if 
you dont see it.
edit with nano or however  /etc/gdm3/custom.conf and comment out the login 
data. if you can't see whats in the editor, use the arrow keys to the right and 
it will gradually start to show (at least it does in nano).

Basically it is a breaking bug for me and would easily drive away any
noob user. I think this should have a much higher priority ASAP.

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

Title:
  Automatic login fails and then all subsequent logins fail. Killing
  gnome-session-binary fixes it, or just not using automatic login.

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

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.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.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-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.5+git20190820-0ubuntu3
  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+git20190815-1
  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/gdm3/+bug/1845801/+subscriptions

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

[Desktop-packages] [Bug 1848930] [NEW] Windows resize when sleep and wakeup on 100% display scale

2019-10-20 Thread Kevin

Public bug reported:

Scaling built-in display to "100%" makes my windows resize when I sleep
my laptop and wake up again.

Steps to reproduce:
1) In system settings, in the "Screen display" section, change "Scale" to "100%"
2) Open a window (e.g. a browser) and resize to most of the screen
3) Close laptop screen and wait for it to go to sleep
4) Open laptop screen
5) Observe that the browser window is now only the top-left quarter of the 
screen, not its original dimensions

Reproduced on 19.04 and 19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 20 15:47:21 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-02-09 (252 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to eoan on 2019-10-20 (0 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Windows resize when sleep and wakeup on 100% display scale

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Scaling built-in display to "100%" makes my windows resize when I
  sleep my laptop and wake up again.

  Steps to reproduce:
  1) In system settings, in the "Screen display" section, change "Scale" to 
"100%"
  2) Open a window (e.g. a browser) and resize to most of the screen
  3) Close laptop screen and wait for it to go to sleep
  4) Open laptop screen
  5) Observe that the browser window is now only the top-left quarter of the 
screen, not its original dimensions

  Reproduced on 19.04 and 19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 20 15:47:21 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-09 (252 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848930/+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 1817073] Re: GNOME Shell crash when an asset is not found (due to too many logs spawn by appindicator extension)

2019-10-20 Thread Linus

Answer #15 from bug #1825623 fixed it though

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

Title:
  GNOME Shell crash when an asset is not found (due to too many logs
  spawn by appindicator extension)

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

Bug description:
  GNOME Shell freeze and crash if appindicator can't lookup an icon. A
  lot of messages are spawned in the logs:

  Feb 20 15:40:46 neutrino gnome-shell[2735]: message repeated 2 times: [ 
[AppIndicatorSupport-FATAL] unable to lookup icon for Cozy Drive1_4575]
  Feb 20 15:40:46 neutrino gnome-shell[2735]: [AppIndicatorSupport-FATAL] 
unable to lookup icon for Cozy Drive1_4578
  Feb 20 15:41:32 neutrino gnome-shell[2735]: message repeated 3611 times: [ 
[AppIndicatorSupport-FATAL] unable to lookup icon for Cozy Drive1_4578]
  Feb 20 15:41:32 neutrino gnome-shell[2735]: ../../../../glib/gmem.c:135: 
failed to allocate 32 bytes
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: GNOME Shell crashed 
with signal 5
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: == Stack trace for 
context 0x55b19a6e3210 ==
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #0 7fff92c183f0 I 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:309
 (7f6f5b632550 @ 680)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #1 7fff92c184d0 b 
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #2 7fff92c18540 I 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:260
 (7f6f5b6324c0 @ 115)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #3 7fff92c18620 b 
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #4 7fff92c186c0 I 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:425
 (7f6f5b632820 @ 960)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #5 7fff92c18790 b 
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #6 7fff92c18800 I 
self-hosted:977 (7f6f63cf0280 @ 413)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #7 7fff92c18870 I 
self-hosted:977 (7f6f63cf0280 @ 413)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #8 7fff92c188f0 I 
resource:///org/gnome/gjs/modules/signals.js:128 (7f6f63cc18b0 @ 386)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #9 7fff92c18940 I 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:162
 (7f6f5b6320d0 @ 96)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #10 7fff92c189d0 I 
self-hosted:261 (7f6f63cc1dc0 @ 223)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #11 7fff92c189d0 I 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:156
 (7f6f5b632040 @ 65)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #12 7fff92c18ab0 b 
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #13 7fff92c18b30 I 
self-hosted:981 (7f6f63cf0280 @ 474)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #14 7fff92c18bb0 I 
self-hosted:981 (7f6f63cf0280 @ 474)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #15 7fff92c19ca0 b 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/util.js:42 
(7f6f5b63b670 @ 145)

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/984

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1817073/+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 1842882] Re: gnome-control-center no longer shows all the xrandr resolutions

2019-10-20 Thread Rocko

I think it's fixed now, so closing.

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

Title:
  gnome-control-center no longer shows all the xrandr resolutions

Status in mutter package in Ubuntu:
  Invalid

Bug description:
  Very recently gnome-control-center started only showing a subset of
  the available screen resolutions. I'll attach a screenshot and also
  the xrandr dump to show what I mean, eg you can see that the 2048x1152
  (16:9) resolution is now missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.33.90-1ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  5 15:56:47 2019
  InstallationDate: Installed on 2019-07-01 (65 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1842882/+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 1817073] Re: GNOME Shell crash when an asset is not found (due to too many logs spawn by appindicator extension)

2019-10-20 Thread Linus

Didn't have a problem with this in 19.04, but after upgrading to 19.10
it's back...

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

Title:
  GNOME Shell crash when an asset is not found (due to too many logs
  spawn by appindicator extension)

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

Bug description:
  GNOME Shell freeze and crash if appindicator can't lookup an icon. A
  lot of messages are spawned in the logs:

  Feb 20 15:40:46 neutrino gnome-shell[2735]: message repeated 2 times: [ 
[AppIndicatorSupport-FATAL] unable to lookup icon for Cozy Drive1_4575]
  Feb 20 15:40:46 neutrino gnome-shell[2735]: [AppIndicatorSupport-FATAL] 
unable to lookup icon for Cozy Drive1_4578
  Feb 20 15:41:32 neutrino gnome-shell[2735]: message repeated 3611 times: [ 
[AppIndicatorSupport-FATAL] unable to lookup icon for Cozy Drive1_4578]
  Feb 20 15:41:32 neutrino gnome-shell[2735]: ../../../../glib/gmem.c:135: 
failed to allocate 32 bytes
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: GNOME Shell crashed 
with signal 5
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: == Stack trace for 
context 0x55b19a6e3210 ==
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #0 7fff92c183f0 I 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:309
 (7f6f5b632550 @ 680)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #1 7fff92c184d0 b 
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #2 7fff92c18540 I 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:260
 (7f6f5b6324c0 @ 115)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #3 7fff92c18620 b 
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #4 7fff92c186c0 I 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:425
 (7f6f5b632820 @ 960)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #5 7fff92c18790 b 
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #6 7fff92c18800 I 
self-hosted:977 (7f6f63cf0280 @ 413)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #7 7fff92c18870 I 
self-hosted:977 (7f6f63cf0280 @ 413)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #8 7fff92c188f0 I 
resource:///org/gnome/gjs/modules/signals.js:128 (7f6f63cc18b0 @ 386)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #9 7fff92c18940 I 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:162
 (7f6f5b6320d0 @ 96)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #10 7fff92c189d0 I 
self-hosted:261 (7f6f63cc1dc0 @ 223)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #11 7fff92c189d0 I 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:156
 (7f6f5b632040 @ 65)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #12 7fff92c18ab0 b 
resource:///org/gnome/gjs/modules/_legacy.js:82 (7f6f63cb0b80 @ 71)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #13 7fff92c18b30 I 
self-hosted:981 (7f6f63cf0280 @ 474)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #14 7fff92c18bb0 I 
self-hosted:981 (7f6f63cf0280 @ 474)
  Feb 20 15:41:32 neutrino org.gnome.Shell.desktop[2735]: #15 7fff92c19ca0 b 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/util.js:42 
(7f6f5b63b670 @ 145)

  https://gitlab.gnome.org/GNOME/gnome-shell/issues/984

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1817073/+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 669248] Re: Spreadsheet Prints Chart on Multiple Pages

2019-10-20 Thread Christopher M. Penalver

Stephen Rasku, this is still reproducible, and has a WORKAROUND in:
Version: 6.3.2.2 (x64)
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c

If this still affects you, please perform the steps requested in
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/669248/comments/8
.

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

Title:
  Spreadsheet Prints Chart on Multiple Pages

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Expired
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org

  1) lsb_release -rd
  Description:  Ubuntu 11.10
  Release:  11.10

  2) apt-cache policy libreoffice-calc
  libreoffice-calc:
Installed: 1:3.4.4-0ubuntu1
Candidate: 1:3.4.4-0ubuntu1
Version table:
   *** 1:3.4.4-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.4.3-3ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages

  3) What is expected to happen in LibreOffice Calc via the Terminal:

  cd ~/Desktop && wget -c
  
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/669248/+attachment/1718719/+files/Printing%20Bug.ods
  -O example.ods && localc -nologo example.ods

  is when one attempts to print via File -> Print the entire file is
  printed in one page as in the Excel screenshot
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/669248/+attachment/2635295/+files/excel.png
  .

  4) What happens instead is the chart is printed across multiple pages.

  WORKAROUND: File -> Print Preview -> Format Page -> change drop down
  Scaling mode to Fit print range(s) on number of pages -> combo box
  Number of pages 1 -> OK button -> File -> Print

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: openoffice.org-core 1:3.2.0-7ubuntu4.1
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sun Oct 31 15:14:01 2010
  ExecutablePath: /usr/lib/openoffice/program/soffice.bin
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: openoffice.org

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/669248/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

2019-10-20 Thread Hui Wang

The testing kernel in the #12 is for fixing the internal mic, so no need
to test external mic plugging (#13).

For #14, it is internal mic, could you record sound with internal mic?

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1848924] [NEW] Snap Evince can't open pdf files in USB drive

2019-10-20 Thread Dario Menin

Public bug reported:

Steps to reproduce:

- Put a .pdf file in an external USB drive
- Double click on it or open it with Evince in any way

Evince starts but it can't show the document, giving the error:

Error opening file /media/username/Storage/file-name.pdf: Permission
denied

lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04

snap --version
snap2.42
snapd   2.42
series  16
ubuntu  18.04
kernel  4.15.0-65-generic

snap list | grep evince
evince3.32.0+git27.47fa15b1   163   stable
ken-vandine   -

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


** Tags: snap

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

Title:
  Snap Evince can't open pdf files in USB drive

Status in evince package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  - Put a .pdf file in an external USB drive
  - Double click on it or open it with Evince in any way

  Evince starts but it can't show the document, giving the error:

  Error opening file /media/username/Storage/file-name.pdf: Permission
  denied

  lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  snap --version
  snap2.42
  snapd   2.42
  series  16
  ubuntu  18.04
  kernel  4.15.0-65-generic

  snap list | grep evince
  evince3.32.0+git27.47fa15b1   163   stable
ken-vandine   -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1848924/+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 1848895] Re: Video recorder uses up to GBs of memory in a few seconds

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

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

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

Title:
  Video recorder uses up to GBs of memory in a few seconds

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  This was reported upstream in
  https://gitlab.gnome.org/GNOME/mutter/issues/853 and closed since it
  is a problem in shell and not mutter. I requested the maintainer to
  move it to gnome-shell tracker instead of merely closing the issue.
  Otherwise I will file a new ticket.

  It is no exaggeration to say that the problem makes the video recorder
  unusable. In barely two or three seconds the shell becomes slow and
  barely responsive, memory usage easily scales up to 3 or 4 GB and
  never goes down except by restarting the shell [1].

  The video recorder is an important tool for reporting problems.

  Besides, an average user might not even now that there is such thing
  as a shell, let alone "shell restarting", so please consider the awful
  impression this might make regarding overall performance of the
  system.

  ---

  [1] Which is specially annoying in ubuntu 19.10 because of a bug in
  chromium snap (https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1848841) when restarting shell that forces me to also
  restart chromium.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 19 19:43:29 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-13 (128 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848895/+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 1817128] Re: gnome-keyring not automatically unlocked on login

Checking service status indicates the failures:

```
service gdm3 status
Process: ExecStartPre: /usr/share/gdm/generate-config 
(code=exited,status=0/SUCCESS)
Process: ExecStartPre: /usr/lib/gdm3/gdm-wait-for-drm 
(code=exited,status=0/SUCCESS)
...

gdm-password: gkr-pam: unable to local control file
```

Relevant components:

  * gdm3 3.34.1-1
  * gnome-shell 3.34.1-1
  * gnome-keyring 3.34.0-1


Also tried:

/etc/gdm/custom.conf

# Enable automatic login for user
[daemon]
AutomaticLogin=username
AutomaticLoginEnable=True

but this lead to a either a black screen with a mouse pointer, or after
resetting the dconf

```
dconf reset -f /
```

it would eventually crash and had to be hard rebooted.

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

Title:
  gnome-keyring not automatically unlocked on login

Status in gnome-keyring package in Ubuntu:
  Fix Released

Bug description:
  Hi

  After initializing and filling the login screen, at the start screen
  prompts for password to unlock the session keyring. Is this normal on
  Ubuntu disk 19.04.02?

  Note: When filling the login screen to start the micro, should it not
  be unlocked automatically?

  Attached the image of the request I fired it.

  Thank you


  **
  Hi

  Após inicialização e preenchimento da tela de login, ao iniciar a tela
  pede senha para desbloqueio do chaveiro de sessão. Isso é normal no
  Ubuntu disco 19.04.02?

  Obs: Quando do preenchimento da tela de login para iniciar o micro o
  desbloqueio não deveria ser automático?

  Em anexo a imagem da solicitação de desboquei-o.

  Obrigado

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+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 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco

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

Filed report as well on Gnome:
https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28

Relevant components:

  * gdm3 3.34.1-1
  * gnome-shell 3.34.1-1
  * gnome-keyring 3.34.0-1

So, no lightdm, unlike this similar issue:
https://github.com/canonical/lightdm/issues/70


they also suggested that the dconf may have become corrupted. 

I've tried as well:

```
mv .config/dconf/user ~/.config/dconf/user.bak
```

But didn't work.


** Bug watch added: gitlab.gnome.org/GNOME/gnome-keyring/issues #28
   https://gitlab.gnome.org/GNOME/gnome-keyring/issues/28

** Bug watch added: github.com/canonical/lightdm/issues #70
   https://github.com/canonical/lightdm/issues/70

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

Title:
  gnome-keyring is not unlocked upon gdm login in disco

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or 
local configuration.
  As far as I recall, I should be running just "stock" configs.
  I did not install system with disco, but upgraded to disco throughout 
development series.

  Upon booting, and logging in through gdm3, I get a pop-up from gnome-
  keyring instructing me that gnome-keyring was not unlocked upon
  logging, and I have to re-enter the password again.

  The password for the account and the gnome-keyring are the same, and
  the keyring should be auto-unlocked.

  Looking at the journal, there is a red warning from gdm:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor 
XDG_RUNTIME_DIR are set.

  The messages after it are:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory 
/run/user/1000...
  Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory 
/run/user/1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000...
  Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
(ssh-agent emulation).
  Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for 
Ubuntu Report.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (restricted).
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (access for web browsers).
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate 
management daemon.
  Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus 
Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000.
  Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default.
  Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms.
  Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox.

  I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see
  that XDG_RUNTIME_DIR to be created and set by logind. From the above
  logs I can see that it happens _after_ gdm-password is done.

  So It seems like something has changed in the stack, and gdm login /
  libpam-gnome-keyring no longer use systemd-logind PAM module to be
  part of the PAM session. But I'm not sure what has changed to cause
  this (gdm, gnome-keyring, pam, systemd).

  Am I the only one with this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode

[Desktop-packages] [Bug 1848731] Re: Audio output device changes upon unlock/login

2019-10-20 Thread Kai-Heng Feng

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

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

Title:
  Audio output device changes upon unlock/login

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a ThinkPad X250 and updated To Ubuntu 19.10 today from 19.04.

  
  Locking/Suspending and logging in changes my audio output device.
  This did not happen in 19.04.

  
   How to reproduce 

  When I lock my session with key combination "Win+L" and then unlock it again, 
the sound that's been playing through my headphones/speakers stops playing. 
When I check the audio settings, "HDMI/DisplayPort 2 - Built-in audio" is 
selected.
  When I select "Headphones - Built-in audio", sound continues playing.

  There is no related log output in dmesg.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848731/+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 1848918] [NEW] [snap] "Save As" dialogue: Clicking on Home button opens unexpected folder

2019-10-20 Thread Alex N.

Public bug reported:

In the "save as" dialogue (i.e. via "Save link as...") clicking on the
Home button icon on the left side opens
"/home/username/snap/chromium/899" and not my personal folder.

Package: chromium-browser
Version: 77.0.3865.120-0ubuntu1~snap1

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

** Description changed:

  In the "save as" dialogue (i.e. via "Save link as...") clicking on the
  Home button icon on the left side opens
  "/home/username/snap/chromium/899" and not my personal folder.
+ 
+ Package: chromium-browser
+ Version: 77.0.3865.120-0ubuntu1~snap1

** Summary changed:

- [snap] "Save As" dialogue home button
+ [snap] "Save As" dialogue: Clicking on Home button opens unexpected folder

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

Title:
  [snap] "Save As" dialogue: Clicking on Home button opens unexpected
  folder

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  In the "save as" dialogue (i.e. via "Save link as...") clicking on the
  Home button icon on the left side opens
  "/home/username/snap/chromium/899" and not my personal folder.

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848918/+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 1848919] [NEW] [snap] Permission denied on Private folder

2019-10-20 Thread Alex N.

Public bug reported:

When accessing the Private (/home/username/Private, Encrypted Directory)
folder (e.g. via "Link save as...") it shows "Could not read contents of
Private, Error opening directory ...: Permission denied"

Package: chromium-browser
Version: 77.0.3865.120-0ubuntu1~snap1

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

** Description changed:

- When accessing the Private folder (e.g. via "Link save as...") it shows
- "Could not read contents of Private, Error opening directory ...:
- Permission denied"
+ When accessing the Private (/home/username/Private, Encrypted Directory)
+ folder (e.g. via "Link save as...") it shows "Could not read contents of
+ Private, Error opening directory ...: Permission denied"
  
  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

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

Title:
  [snap] Permission denied on Private folder

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When accessing the Private (/home/username/Private, Encrypted
  Directory) folder (e.g. via "Link save as...") it shows "Could not
  read contents of Private, Error opening directory ...: Permission
  denied"

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848919/+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 1792085] Re: MTP not working/very slow on Bionic

2019-10-20 Thread Chris Barnes

Same problem on Ubuntu 18.04 LTS with all updates and Samsung Galaxy S8.
Why did Google have to implement MTP instead of good old fashioned media
access over USB like we used to have ? The good old days where the
storage would show up just like a USB stick ? What is the benefit of MTP
?:-(

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

Title:
  MTP not working/very slow on Bionic

Status in libmtp:
  New
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmtp/+bug/1792085/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

** Attachment added: "alsa-info.txt.10.20"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298554/+files/alsa-info.txt.10.20

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

** Attachment added: "Screenshot from 2019-10-20 18-17-27.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298553/+files/Screenshot%20from%202019-10-20%2018-17-27.png

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

also dmesg


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298555/+files/dmesg.txt

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

The behavior is different with the test kernel. please find the
screenshot and the alsa-info below.

** Attachment added: "Screenshot from 2019-10-20 18-18-34.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+attachment/5298552/+files/Screenshot%20from%202019-10-20%2018-18-34.png

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

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

2019-10-20 Thread Steve-b-2

(In reply to Steve B. from comment #6)
> That works too.
> 
> I can stop editing my exports now; thanks...

I spoke too soon! It has reappeared.

Odd: I did see it go away when you contacted me. Perhaps a previous
version fixed it, but the latest reintroduces the error...

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

Title:
  Lightning: Cannot dismiss reminders. Got a VALUE parameter with an
  illegal type for property: VALUE=DURATION

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

Bug description:
  Cannot dismiss reminders for a recurrence with exceptions. Calendar entries 
like this are generated:
  BEGIN:VALARM
  ACTION:DISPLAY
  DESCRIPTION:My recurrence
  TRIGGER;VALUE=DURATION:-PT120M
  X-LIC-ERROR;X-LIC-ERRORTYPE=PARAMETER-VALUE-PARSE-ERROR:Got a VALUE parame
   ter with an illegal type for property: VALUE=DURATION
  END:VALARM

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xul-ext-lightning 1:60.8.0+build1-0ubuntu0.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vectro 2004 F pulseaudio
   /dev/snd/controlC0:  vectro 2004 F pulseaudio
  BuildID: 20190705212852
  Channel: Unavailable
  CurrentDesktop: KDE
  Date: Wed Oct  2 17:50:39 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.14 metric 600
  Locales: extensions.sqlite corrupt or missing
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705212852 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  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.sku: T4M40UT#ABA
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1846423/+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 1817128] Re: gnome-keyring not automatically unlocked on login

I can see that this problem is still present on eoan-ermine.

I upgraded from a development version to the latest 19.10

After several configurations of my shell, including zsh, oh-my-ssh and
others, after trying to login this morning, the issue appeared. no
system update, but a few small installations.


I'm unable to login via graphical interface, but able to do so on a separate 
terminal (CTRL+ALT+F2) directly to the terminal.

service gdm3 status shows the service active but shows errors:

gdm3: GDMDisplay: Session never registered, failing
gdm-password: gkr-pam: unable to locate daemon control file
gdm-password: pam_unix(gdm-password: session): session opened for user x by 
uid=0

and continues with the same error

How to solve this? at the moment i can only use terminal based login, no
UI

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

Title:
  gnome-keyring not automatically unlocked on login

Status in gnome-keyring package in Ubuntu:
  Fix Released

Bug description:
  Hi

  After initializing and filling the login screen, at the start screen
  prompts for password to unlock the session keyring. Is this normal on
  Ubuntu disk 19.04.02?

  Note: When filling the login screen to start the micro, should it not
  be unlocked automatically?

  Attached the image of the request I fired it.

  Thank you


  **
  Hi

  Após inicialização e preenchimento da tela de login, ao iniciar a tela
  pede senha para desbloqueio do chaveiro de sessão. Isso é normal no
  Ubuntu disco 19.04.02?

  Obs: Quando do preenchimento da tela de login para iniciar o micro o
  desbloqueio não deveria ser automático?

  Em anexo a imagem da solicitação de desboquei-o.

  Obrigado

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1817128/+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 1818616] Re: gnome-keyring is not unlocked upon gdm login in disco

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

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

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

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

Title:
  gnome-keyring is not unlocked upon gdm login in disco

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or 
local configuration.
  As far as I recall, I should be running just "stock" configs.
  I did not install system with disco, but upgraded to disco throughout 
development series.

  Upon booting, and logging in through gdm3, I get a pop-up from gnome-
  keyring instructing me that gnome-keyring was not unlocked upon
  logging, and I have to re-enter the password again.

  The password for the account and the gnome-keyring are the same, and
  the keyring should be auto-unlocked.

  Looking at the journal, there is a red warning from gdm:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor 
XDG_RUNTIME_DIR are set.

  The messages after it are:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory 
/run/user/1000...
  Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory 
/run/user/1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000...
  Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
(ssh-agent emulation).
  Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for 
Ubuntu Report.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (restricted).
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (access for web browsers).
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate 
management daemon.
  Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus 
Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000.
  Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default.
  Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms.
  Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox.

  I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see
  that XDG_RUNTIME_DIR to be created and set by logind. From the above
  logs I can see that it happens _after_ gdm-password is done.

  So It seems like something has changed in the stack, and gdm login /
  libpam-gnome-keyring no longer use systemd-logind PAM module to be
  part of the PAM session. But I'm not sure what has changed to cause
  this (gdm, gnome-keyring, pam, systemd).

  Am I the only one with this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  5 08:22:01 2019
  InstallationDate: Installed on 2016-01-26 (1134 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160125)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago)

To manage notifications

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

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

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

** Changed in: gnome-keyring (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-keyring is not unlocked upon gdm login in disco

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or 
local configuration.
  As far as I recall, I should be running just "stock" configs.
  I did not install system with disco, but upgraded to disco throughout 
development series.

  Upon booting, and logging in through gdm3, I get a pop-up from gnome-
  keyring instructing me that gnome-keyring was not unlocked upon
  logging, and I have to re-enter the password again.

  The password for the account and the gnome-keyring are the same, and
  the keyring should be auto-unlocked.

  Looking at the journal, there is a red warning from gdm:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor 
XDG_RUNTIME_DIR are set.

  The messages after it are:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory 
/run/user/1000...
  Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory 
/run/user/1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000...
  Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
(ssh-agent emulation).
  Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for 
Ubuntu Report.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (restricted).
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (access for web browsers).
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate 
management daemon.
  Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus 
Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000.
  Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default.
  Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms.
  Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox.

  I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see
  that XDG_RUNTIME_DIR to be created and set by logind. From the above
  logs I can see that it happens _after_ gdm-password is done.

  So It seems like something has changed in the stack, and gdm login /
  libpam-gnome-keyring no longer use systemd-logind PAM module to be
  part of the PAM session. But I'm not sure what has changed to cause
  this (gdm, gnome-keyring, pam, systemd).

  Am I the only one with this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  5 08:22:01 2019
  InstallationDate: Installed on 2016-01-26 (1134 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160125)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago)

To manage

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

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

I've reproduced this bug on eoan-ermine. See my comments on the related
bug report #1817128

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

Title:
  gnome-keyring is not unlocked upon gdm login in disco

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or 
local configuration.
  As far as I recall, I should be running just "stock" configs.
  I did not install system with disco, but upgraded to disco throughout 
development series.

  Upon booting, and logging in through gdm3, I get a pop-up from gnome-
  keyring instructing me that gnome-keyring was not unlocked upon
  logging, and I have to re-enter the password again.

  The password for the account and the gnome-keyring are the same, and
  the keyring should be auto-unlocked.

  Looking at the journal, there is a red warning from gdm:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor 
XDG_RUNTIME_DIR are set.

  The messages after it are:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory 
/run/user/1000...
  Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory 
/run/user/1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000...
  Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
(ssh-agent emulation).
  Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for 
Ubuntu Report.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (restricted).
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (access for web browsers).
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate 
management daemon.
  Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus 
Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000.
  Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default.
  Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms.
  Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox.

  I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see
  that XDG_RUNTIME_DIR to be created and set by logind. From the above
  logs I can see that it happens _after_ gdm-password is done.

  So It seems like something has changed in the stack, and gdm login /
  libpam-gnome-keyring no longer use systemd-logind PAM module to be
  part of the PAM session. But I'm not sure what has changed to cause
  this (gdm, gnome-keyring, pam, systemd).

  Am I the only one with this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  5 08:22:01 2019
  InstallationDate: Installed on 2016-01-26 (1134 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160125)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago)

To manage notifications about this bug go to:

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

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

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

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

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

Title:
  gnome-keyring is not unlocked upon gdm login in disco

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or 
local configuration.
  As far as I recall, I should be running just "stock" configs.
  I did not install system with disco, but upgraded to disco throughout 
development series.

  Upon booting, and logging in through gdm3, I get a pop-up from gnome-
  keyring instructing me that gnome-keyring was not unlocked upon
  logging, and I have to re-enter the password again.

  The password for the account and the gnome-keyring are the same, and
  the keyring should be auto-unlocked.

  Looking at the journal, there is a red warning from gdm:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor 
XDG_RUNTIME_DIR are set.

  The messages after it are:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory 
/run/user/1000...
  Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory 
/run/user/1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000...
  Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
(ssh-agent emulation).
  Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for 
Ubuntu Report.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (restricted).
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (access for web browsers).
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate 
management daemon.
  Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus 
Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000.
  Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default.
  Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms.
  Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox.

  I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see
  that XDG_RUNTIME_DIR to be created and set by logind. From the above
  logs I can see that it happens _after_ gdm-password is done.

  So It seems like something has changed in the stack, and gdm login /
  libpam-gnome-keyring no longer use systemd-logind PAM module to be
  part of the PAM session. But I'm not sure what has changed to cause
  this (gdm, gnome-keyring, pam, systemd).

  Am I the only one with this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  5 08:22:01 2019
  InstallationDate: Installed on 2016-01-26 (1134 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160125)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago)

To manage notifications about

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

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

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

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

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

Title:
  gnome-keyring is not unlocked upon gdm login in disco

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm not sure if this is a regression in my gnome-keyring, gdm3, or pam, or 
local configuration.
  As far as I recall, I should be running just "stock" configs.
  I did not install system with disco, but upgraded to disco throughout 
development series.

  Upon booting, and logging in through gdm3, I get a pop-up from gnome-
  keyring instructing me that gnome-keyring was not unlocked upon
  logging, and I have to re-enter the password again.

  The password for the account and the gnome-keyring are the same, and
  the keyring should be auto-unlocked.

  Looking at the journal, there is a red warning from gdm:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Looking at the code, this happens when neither GNOME_KEYRING_CONTROL nor 
XDG_RUNTIME_DIR are set.

  The messages after it are:
  Mar 05 08:15:58 ottawa gdm-password][18338]: gkr-pam: unable to locate daemon 
control file
  Mar 05 08:15:58 ottawa gdm-password][18338]: pam_unix(gdm-password:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[1]: Created slice User Slice of UID 1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Runtime Directory 
/run/user/1000...
  Mar 05 08:15:58 ottawa systemd-logind[1376]: New session 3 of user xnox.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Runtime Directory 
/run/user/1000.
  Mar 05 08:15:58 ottawa systemd[1]: Starting User Manager for UID 1000...
  Mar 05 08:15:58 ottawa systemd[18344]: pam_unix(systemd-user:session): 
session opened for user xnox by (uid=0)
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on Sound System.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
(ssh-agent emulation).
  Mar 05 08:15:58 ottawa systemd[18344]: Started Pending report trigger for 
Ubuntu Report.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (restricted).
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Paths.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG cryptographic agent 
and passphrase cache (access for web browsers).
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Timers.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on GnuPG network certificate 
management daemon.
  Mar 05 08:15:58 ottawa systemd[18344]: Starting D-Bus User Message Bus Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Listening on D-Bus User Message Bus 
Socket.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Sockets.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Basic System.
  Mar 05 08:15:58 ottawa systemd[1]: Started User Manager for UID 1000.
  Mar 05 08:15:58 ottawa systemd[18344]: Started Emacs text editor.
  Mar 05 08:15:58 ottawa systemd[18344]: Reached target Default.
  Mar 05 08:15:58 ottawa systemd[18344]: Startup finished in 72ms.
  Mar 05 08:15:58 ottawa systemd[1]: Started Session 3 of user xnox.

  I don't believe GNOME_KEYRING_CONTROL used to be set, however I do see
  that XDG_RUNTIME_DIR to be created and set by logind. From the above
  logs I can see that it happens _after_ gdm-password is done.

  So It seems like something has changed in the stack, and gdm login /
  libpam-gnome-keyring no longer use systemd-logind PAM module to be
  part of the PAM session. But I'm not sure what has changed to cause
  this (gdm, gnome-keyring, pam, systemd).

  Am I the only one with this issue?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-keyring 3.31.90-1ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  5 08:22:01 2019
  InstallationDate: Installed on 2016-01-26 (1134 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160125)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-keyring
  UpgradeStatus: Upgraded to disco on 2019-01-15 (48 days ago)

To manage notifications about

[Desktop-packages] [Bug 1847772]

Created attachment 9102698
1575512-glue.patch (v1b)

Here's the final patch with added comments and error checking as well as
added #ifdef since otherwise SeaMonkey won't compile since it doesn't
have mailGlue (but suiteGlue instead).

Try:
https://treeherder.mozilla.org/#/jobs?repo=try-comm-central=feccca1eb30ca259599ff91a887f68c1d942f5b7

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

Title:
  E-mail folder names are not localized in thunderbird 68

Status in Mozilla Thunderbird:
  In Progress
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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

2019-10-20 Thread Acelists

Comment on attachment 9102753
1575512-glue-mark2.patch (v1b)

Review of attachment 9102753:
-

I find it a bit excessive to add a whole new class for this, but it does work 
so if you like it better...
Please again add the TODO comment of this being a temporary hack.
I assume this does not break Seamonkey now.

::: mailnews/imap/src/nsImapService.cpp
@@ +2416,5 @@
>server->GetRootFolder(getter_AddRefs(rootFolder));
> +  bool ready;
> +  if (rootFolder && !folderName.IsEmpty() &&
> +  // Skip folder processing if folder names aren't ready yet.
> +  // That happens early in initalisation.

typo

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

Title:
  E-mail folder names are not localized in thunderbird 68

Status in Mozilla Thunderbird:
  In Progress
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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

Created attachment 9102763
1575512-glue-mark2.patch (v1c).

Fixed typo and added more comments.

We've discussed improved error handling on IRC. initializeStrings()
shouldn't really fail, unless someone removes some of the eight folder
name strings or the system is so damaged that it can't find the bundle.

Passing the error our to the final-ui-startup observer is also not
useful since it could only report it.

While looking at the code I saw four uses of nsString(XXX).get() which
is of course nonsense.

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

Title:
  E-mail folder names are not localized in thunderbird 68

Status in Mozilla Thunderbird:
  In Progress
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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

Changing that event to profile-after-change doesn't help. In the IMAP
code `ready` is always false :-( - Setting it to true makes the test
pass as expected.

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

Title:
  E-mail folder names are not localized in thunderbird 68

Status in Mozilla Thunderbird:
  In Progress
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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

You can see the simplification in the interdiff:
https://bugzilla.mozilla.org/attachment.cgi?oldid=9102584=interdiff=9102588=1

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

Title:
  E-mail folder names are not localized in thunderbird 68

Status in Mozilla Thunderbird:
  In Progress
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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

Created attachment 9102751
1575512-glue-mark2.patch

Here's the whole thing reshuffled. We don't call into the glue any more
but the glue calls the folders.

This is the simpler solution although the patch is bigger due to all the
boilerplate.

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

Title:
  E-mail folder names are not localized in thunderbird 68

Status in Mozilla Thunderbird:
  In Progress
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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

Created attachment 9102753
1575512-glue-mark2.patch (v1b)

Slightly optimised, we only check the app name once, so if there are
thousands of URI in the permissions file, we don't get the app name
repeatedly. Debug patch doesn't apply any more.

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

Title:
  E-mail folder names are not localized in thunderbird 68

Status in Mozilla Thunderbird:
  In Progress
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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

> Can this be made 'attribute boolean finalUiStartupDone' ?

You mean "readonly". I don't think so. I don't have an instance of
nsIMailGlue. I just get the service and run one of its methods.

I'll worry about the other comments tomorrow.

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

Title:
  E-mail folder names are not localized in thunderbird 68

Status in Mozilla Thunderbird:
  In Progress
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After updating to Thunderbird 68.1.1 from the Ubuntu archive, folder
  names Inbox, Drafts, Sent, Archives, Spam, Trash all appear in English
  in the French UI. The rest of the UI is in French.

  This issue is still present in Thunderbird 1:68.1.2+build1-0ubuntu1.

  This problem doesn’t exist in Thunderbird 68.1.1 nor in 68.1.2
  downloaded directly from Mozilla.

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