[Desktop-packages] [Bug 795540] Re: package pcscd 1.7.0-2ubuntu2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

** Changed in: pcsc-lite (Ubuntu)
   Status: New => Confirmed

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

Title:
  package pcscd 1.7.0-2ubuntu2 failed to install/upgrade: ErrorMessage:
  subprocess installed post-installation script returned error exit
  status 1

Status in pcsc-lite package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pcscd

  jadler@server:~$ lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04
  jadler@server:~$ apt-cache policy pcsc
  pcscada-dbg   pcscd pcsc-omnikey  pcsc-tools
  jadler@server:~$ apt-cache policy pcsc-lite
  N: Unable to locate package pcsc-lite
  jadler@server:~$ apt-cache policy pcscd 
  pcscd:
Installed: 1.7.0-2ubuntu2
Candidate: 1.7.0-2ubuntu2
Version table:
   *** 1.7.0-2ubuntu2 0
  500 http://se.archive.ubuntu.com/ubuntu/ natty/universe amd64 Packages
  100 /var/lib/dpkg/status

  Upgrading 10.10 to 11.04

  ProblemType: Package
  DistroRelease: Ubuntu 11.04
  Package: pcscd 1.7.0-2ubuntu2
  ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11
  Uname: Linux 2.6.35-28-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri Jun 10 08:17:33 2011
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: pcsc-lite
  Title: package pcscd 1.7.0-2ubuntu2 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to natty on 2011-06-09 (0 days ago)

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

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

[Desktop-packages] [Bug 1806269] Re: nm-connection-editor crashes when trying to modify connection

[shasheene]

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

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

Title:
  nm-connection-editor crashes when trying to modify connection

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  Thread 1 "nm-connection-e" received signal SIGSEGV, Segmentation fault.   
   
  0x77ba6b53 in modules_initialized (object=, 
res=0x56048a40, user_data=) at 
src/libnma/nma-cert-chooser-button.c:98
  98  src/libnma/nma-cert-chooser-button.c: No such file or directory. 

  
  This occurs when the package "gnome-keyring" is not installed.

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

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

[Desktop-packages] [Bug 1839637] Re: Display driver missing

[Launchpad Bug Tracker]

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

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

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

Title:
  Display driver missing

Status in linux package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  After system update and reboot, system stay on the purple screen for
  long time.Then after going to advanced mode and from recovery option,
  I run check for broken packages. After completion system was restarted
  on normal mode and found the display driver missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  9 20:58:18 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated 
Graphics Controller [1458:d000]
  InstallationDate: Installed on 2019-08-05 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. G41M-Combo
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  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.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  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/linux/+bug/1839637/+subscriptions

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

[Desktop-packages] [Bug 1839637] Re: Display driver missing

[Launchpad Bug Tracker]

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

** Changed in: xorg-server (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Display driver missing

Status in linux package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  After system update and reboot, system stay on the purple screen for
  long time.Then after going to advanced mode and from recovery option,
  I run check for broken packages. After completion system was restarted
  on normal mode and found the display driver missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug  9 20:58:18 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e32] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 4 Series Chipset Integrated 
Graphics Controller [1458:d000]
  InstallationDate: Installed on 2019-08-05 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. G41M-Combo
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=ffc3eaf1-87dc-4ccf-9b94-b12d46e2b1b6 ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  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.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  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/linux/+bug/1839637/+subscriptions

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

[Desktop-packages] [Bug 1245473]

[Bestcdrwriting]

At Best CDR Writing, we are providing you the best CDR and RPL reports atan 
affordablr cost. We will deliver you 100% pilagarism free and best quality work.
https://bestcdrwriting.com/

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

Title:
  Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes
  shortcuts with ctrl+shift, etc not working in any program

Status in GNOME Settings Daemon:
  Fix Released
Status in GNOME Shell:
  Won't Fix
Status in Unity:
  Confirmed
Status in X.Org X server:
  Unknown
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Triaged
Status in gnome-settings-daemon package in ALT Linux:
  Unknown
Status in gnome-settings-daemon package in Debian:
  New
Status in gnome-settings-daemon package in Fedora:
  Won't Fix
Status in gnome-settings-daemon package in openSUSE:
  Confirmed

Bug description:
  Tried only with ctrl+shift, maybe behaves the same for other modifier
  key combinations when used as shortcut for switching layouts.

  - Set ctrl+shift as shortcut for switching keyboard layouts
  - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work 
(actually Terminal window loses focus when ctrl+shift is pressed, and layout is 
switched)

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-settings-daemon 3.8.5-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Oct 28 16:40:02 2013
  InstallationDate: Installed on 2013-10-23 (5 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen

[Daniel van Vugt]

** Also affects: ubuntu-ux
   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/1843899

Title:
  gnome-shell calendar widget is not centered on the screen

Status in Ubuntu UX:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.

  It feels as if it is centered, with an offset / margin on the left.

  between "right edge of the app menu" and "left edge of the top right
  indicators", instead of centered to the screen width.The blue line on
  the screenshot is the centre fold of the screen, you can see that the
  wallpaper is correctly centered with the animal circle in the centre.

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

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

[Desktop-packages] [Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen

[Daniel van Vugt]

My second preference would probably be something completely different:
Move the clock calendar to the right hand side.

My third preference would be the current behaviour of placing the
clock/calendar over the work area (maximized windows') centre.

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

Title:
  gnome-shell calendar widget is not centered on the screen

Status in Ubuntu UX:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.

  It feels as if it is centered, with an offset / margin on the left.

  between "right edge of the app menu" and "left edge of the top right
  indicators", instead of centered to the screen width.The blue line on
  the screenshot is the centre fold of the screen, you can see that the
  wallpaper is correctly centered with the animal circle in the centre.

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

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

[Desktop-packages] [Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen

[Daniel van Vugt]

Despite comment #9, my personal vote would be for the clock/calendar to
never move, always be centred.

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

Title:
  gnome-shell calendar widget is not centered on the screen

Status in Ubuntu UX:
  New
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.

  It feels as if it is centered, with an offset / margin on the left.

  between "right edge of the app menu" and "left edge of the top right
  indicators", instead of centered to the screen width.The blue line on
  the screenshot is the centre fold of the screen, you can see that the
  wallpaper is correctly centered with the animal circle in the centre.

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

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

[Desktop-packages] [Bug 1806269] Re: nm-connection-editor crashes when trying to modify connection

[shasheene]

Hi,

I have this same problem on Ubuntu 18.04 i386, using an up-to-date
bionic environment (main/universe/multiverse of bionic, bionic-updates
and bionic-backports repos) .

I am attaching an apport service /var/crash log file. I couldn't find
any network-manager-gnome dbg packages, so I'm not sure the backtrace
will have symbols. If you need more information I am happy to help.

Reproduction: Launch nm-connection-editor, then double-click a connection to 
modify it.
Workaround: Install gnome-keyring (which recommended package, not a dependency) 
[1]

Given 18.04 is the last Ubuntu release with i386 support, I am unable to
move to a more recent Ubuntu release such as cosmic (or beyond) at this
stage. I am developing a live CD used by many users who aren’t Linux
experts, may have poor internet connection and may be using very old
computers. Given it's a non-persistent environment, saving passwords
with gnome-keyring is not useful, and the password prompt will likely
cause much confusion. My intention is to provide an i386 version based
on Ubuntu 18.04 until the maintenance support window ends in 2023 [2]

[1] https://packages.ubuntu.com/disco/network-manager-gnome
[2] https://ubuntu.com/about/release-cycle

** Attachment added: "_usr_bin_nm-connection-editor.999.crash"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1806269/+attachment/5296863/+files/_usr_bin_nm-connection-editor.999.crash

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

Title:
  nm-connection-editor crashes when trying to modify connection

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

Bug description:
  Thread 1 "nm-connection-e" received signal SIGSEGV, Segmentation fault.   
   
  0x77ba6b53 in modules_initialized (object=, 
res=0x56048a40, user_data=) at 
src/libnma/nma-cert-chooser-button.c:98
  98  src/libnma/nma-cert-chooser-button.c: No such file or directory. 

  
  This occurs when the package "gnome-keyring" is not installed.

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

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

[Desktop-packages] [Bug 1683383]

[Bestcdrwriting]

At Best CDR Writing, we are providing you the best CDR and RPL reports atan 
affordablr cost. We will deliver you 100% pilagarism free and best quality work.
https://bestcdrwriting.com/

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts (reopen)

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  From duplicate bug 1720364 report.

  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher in mate-control-center
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ---
  Original description below:

  This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
  Zesty Zapus.

  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  Apparently, the bug has reappeared after the patch that used to fix
  the problem (208_switch_on_release.diff) has been removed from X.Org
  1.19 packages. There is an updated patch in the upstream ticket
  https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the
  attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 17 17:46:35 2017
  InstallationDate: Installed on 2015-05-01 (716 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions

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

[Desktop-packages] [Bug 1847904] Re: intel grafic

[Daniel van Vugt]

The correct latest Intel graphics driver is:
  /usr/lib/xorg/modules/drivers/modesetting_drv.so
provided by package:
  xserver-xorg-core
which you probably do have.

So please describe what kind of problem you are trying to solve.

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

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

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

Title:
  intel grafic

Status in Ubuntu:
  Incomplete

Bug description:
  cant install intel grafic drivers

  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
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 13 14:59:11 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:15bd]
  InstallationDate: Installed on 2019-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 1d57:fa01 Xenta 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=704348ec-f63c-4238-870e-381e532c8448 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.504:bd11/13/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X200MA
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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/+bug/1847904/+subscriptions

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

[Desktop-packages] [Bug 1845898] Re: Unable to set touchpad Edge Scrolling in Eoan

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1845898

** Tags added: iso-testing

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

Title:
  Unable to set touchpad Edge Scrolling in Eoan

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

Bug description:
  After installing the Eoan Beta on a Dell Latitude E6400 attempting to
  set touchpad Edge Scrolling was unsuccessful. It actually seemed to
  work as long as the System Settings window was left open but as soon
  as the window is closed the Edge Scrolling setting reverts to off.

  I did however find that simply installing the package 'xserver-xorg-
  input-synaptics' solves the problem. In fact it adds the additional
  setting option of Two Finger Scrolling to the control center UI. I'm
  not sure if that package should be installed by default or not?

  Steps to reproduce are simple:
  (1) Install Ubuntu Eoan on a laptop (could possibly work with a keyboard with 
an incorporated touchpad).
  (2) Open Gnome Control Center (System Settings) and go to Devices > Mouse & 
Touchpad.
  (3) Select Edge Scrolling and you'll notice the "button" turn green. Close 
System Settings. 
  (4) Reopen System Settings and you'll see Edge Scrolling has turned off again.
  (5) Install 'xserver-xorg-input-synaptics' and then reboot.
  (6) Repeat the above steps and you'll find that setting Edge Scrolling is 
successful even after closing System Settings. Additionally you'll find that a 
new Two Finger Scrolling option has been added to the UI.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.0.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 22:15:09 2019
  InstallationDate: Installed on 2019-09-30 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1843899] Re: gnome-shell calendar widget is not centered on the screen

[Launchpad Bug Tracker]

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

Title:
  gnome-shell calendar widget is not centered on the screen

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  With the new eoan wallpaper it is obvious that calendar widget, is not
  in fact, centered on the screen. Nor is like left/right aligned to the
  centre either.

  It feels as if it is centered, with an offset / margin on the left.

  between "right edge of the app menu" and "left edge of the top right
  indicators", instead of centered to the screen width.The blue line on
  the screenshot is the centre fold of the screen, you can see that the
  wallpaper is correctly centered with the animal circle in the centre.

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

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

[Desktop-packages] [Bug 1847740] Re: Auto-hide dock causes clock/notification to move

[Daniel van Vugt]

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

Come to think of it, this was most recently discussed in Paris via bug
1843899, so let's use that.

** This bug has been marked a duplicate of bug 1843899
   gnome-shell calendar widget is not centered on the screen

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

Title:
  Auto-hide dock causes clock/notification to move

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  When disabling / enabling hiding of the dock - or indeed changing the
  width of the dock - in system settings - the clock / notification area
  moves. These feels wrong. The clock is not related to the dock size,
  and should not move with it. The clock should be in the centre of the
  display, not the centre of the usable area of the desktop I believe.

  Steps to reproduce

  Open system settings
  Select dock
  change the toggle to auto-hide the dock
  Observe the clock move with the toggle

  Expected behaviour

  Clock/notification are is locked to the middle of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 11:11:44 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 
'Sundry', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['org-gnome-screenshot', 'update-manager']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2019-10-11 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011)
  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/1847740/+subscriptions

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

[Desktop-packages] [Bug 1847740] Re: Auto-hide dock causes clock/notification to move

[Daniel van Vugt]

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

I personally agree with your perspective that this should not happen,
but it is the designed behaviour (ask didrocks, willcooke). The
intention was that the clock should be positioned to have the same
centre line as any maximized window's title.

P.S. The desktop icons seem to be moving in the wrong direction in your
screenshots. Please open a new bug if that's a concern.

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

Title:
  Auto-hide dock causes clock/notification to move

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  When disabling / enabling hiding of the dock - or indeed changing the
  width of the dock - in system settings - the clock / notification area
  moves. These feels wrong. The clock is not related to the dock size,
  and should not move with it. The clock should be in the centre of the
  display, not the centre of the usable area of the desktop I believe.

  Steps to reproduce

  Open system settings
  Select dock
  change the toggle to auto-hide the dock
  Observe the clock move with the toggle

  Expected behaviour

  Clock/notification are is locked to the middle of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 11:11:44 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 
'Sundry', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['org-gnome-screenshot', 'update-manager']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2019-10-11 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011)
  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/1847740/+subscriptions

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

[Desktop-packages] [Bug 1847740] Re: Auto-hide dock causes clock/notification to move

[Launchpad Bug Tracker]

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

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

Title:
  Auto-hide dock causes clock/notification to move

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  When disabling / enabling hiding of the dock - or indeed changing the
  width of the dock - in system settings - the clock / notification area
  moves. These feels wrong. The clock is not related to the dock size,
  and should not move with it. The clock should be in the centre of the
  display, not the centre of the usable area of the desktop I believe.

  Steps to reproduce

  Open system settings
  Select dock
  change the toggle to auto-hide the dock
  Observe the clock move with the toggle

  Expected behaviour

  Clock/notification are is locked to the middle of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 11:11:44 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 
'Sundry', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['org-gnome-screenshot', 'update-manager']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2019-10-11 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011)
  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/1847740/+subscriptions

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

[Desktop-packages] [Bug 1847882] Re: Excessive use of gnome-shell memory

[Daniel van Vugt]

I suspect more people would complain about not being able to load
whatever extension they want, than do complain about broken extensions.

But we may never know... We only have proof of the latter :)


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

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

Title:
  Excessive use of gnome-shell memory

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  After 9 hours of uptime, I have the gnome-shell process that uses 6GB
  of memory ...

  emanu@emanuc:~$ ps aux | grep gnome-shell
  gdm   2014  0.0  1.0 2857772 175052 ?  Ssl  13:42   0:10 
/usr/bin/gnome-shell
  emanu 2934  6.3 38.7 10087648 6350632 ?Ssl  13:43  36:18 
/usr/bin/gnome-shell
  emanu 2963  0.0  0.1 520028 17796 ?Sl   13:43   0:00 
/usr/lib/gnome-shell/gnome-shell-calendar-server
  emanu 3278  0.2  0.6 2608268 111668 ?  Sl   13:43   1:33 gjs 
/home/emanu/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/da
  emon.js
  emanu13107  0.0  0.0   9056   924 pts/2S+   23:18   0:00 grep 
gnome-shell

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 12 23:22:21 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-18 (235 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  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/1847882/+subscriptions

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

[Desktop-packages] [Bug 1847740] Re: Auto-hide dock causes clock/notification to move

[Daniel van Vugt]

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

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

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

Title:
  Auto-hide dock causes clock/notification to move

Status in gnome-shell package in Ubuntu:
  Opinion

Bug description:
  When disabling / enabling hiding of the dock - or indeed changing the
  width of the dock - in system settings - the clock / notification area
  moves. These feels wrong. The clock is not related to the dock size,
  and should not move with it. The clock should be in the centre of the
  display, not the centre of the usable area of the desktop I believe.

  Steps to reproduce

  Open system settings
  Select dock
  change the toggle to auto-hide the dock
  Observe the clock move with the toggle

  Expected behaviour

  Clock/notification are is locked to the middle of the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 11:11:44 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 
'Sundry', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.notifications' b'application-children' 
b"['org-gnome-screenshot', 'update-manager']"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2019-10-11 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011)
  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/1847740/+subscriptions

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

[Desktop-packages] [Bug 1706460] Re: Outdated Totem documentation describes and mentions features absent from the software

[Bug Watch Updater]

** Changed in: totem
   Status: Unknown => Fix Released

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

Title:
  Outdated Totem documentation describes and mentions features absent
  from the software

Status in Totem:
  Fix Released
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  'man totem' mentions "F9   toggle display of the playlist" and
  the Help document in totem often describes choosing the "sidebar"
  option from the "View" menu.

  Pressing F9 does nothing.  There is no "sidebar" option in the "View"
  menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul 25 18:47:38 2017
  InstallationDate: Installed on 2016-06-05 (415 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (103 days ago)

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

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

[Desktop-packages] [Bug 1826040] Re: examples.desktop file is not executable and only opens into default text editor(gedit)

[Daniel van Vugt]

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

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

Title:
  examples.desktop file is not executable and only opens into default
  text editor(gedit)

Status in example-content package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  New

Bug description:
  ~$ file examples.desktop 
  examples.desktop: UTF-8 Unicode text

  Does not open or spawn content in: /usr/share/example-content/

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: example-content 50
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 12:46:47 2019
  Dependencies:
   
  InstallationDate: Installed on 2019-04-22 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: example-content
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1847736] Re: examples.desktop file in home dir is opening in gedit

[Daniel van Vugt]

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

It was also reported in disco -> bug 1826040

** Tags added: eoan

** This bug has been marked a duplicate of bug 1826040
   examples.desktop file is not executable and only opens into default text 
editor(gedit)

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

Title:
  examples.desktop file in home dir is opening in gedit

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The "examples.desktop" file in the home directory should open
  /usr/share/example-content but instead it opens the .desktop file in
  gedit.

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

-- 
Mailing list: https://launchpad.net/~desktop-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

[Daniel van Vugt]

jibel, that's the intended behaviour. We default to always switching to
the most recent audio device plugged in. To disable that you will need
to comment out:

### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794)
.ifexists module-switch-on-connect.so
load-module module-switch-on-connect
.endif

-- 
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:
  Confirmed

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 1846477] Re: Dragging icons in launcher is slow until shell restarted

[Daniel van Vugt]

Hmm, OK. Marco says his fix was related to this bug.

To avoid confusion, if it reappears then please open a new bug with
information answering comment #9.

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Dragging icons in launcher is slow until shell restarted

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Fix Released

Bug description:
  Today I noticed that dragging icons up and down the launcher is
  painfully slow, to the point where it feels like the desktop has
  locked up. The gnome-shell process is pegged at 100% while this is
  happening.

  Restarting gnome shell (alt+f2, r) makes it faster to refresh the move
  of the icon but still super slow at drawing the line where you drop
  it.

  However, it's super fast on clean boot of a separate machine - x220 (7
  years old i7) and another nvidia 960 gpu equipped i7 laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct  3 12:24:48 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-02-04 (605 days ago)
  InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 
20180202-11:07
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-19 (13 days ago)

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

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

[Desktop-packages] [Bug 1847729] Re: Memory leak of gnome-shell after sleep mode

[Daniel van Vugt]

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

** Summary changed:

- Memory leak of gnome-shell after sleep mode
+ Memory leak of gnome-shell after sleep mode, when arc-menu extension is loaded

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

Title:
  Memory leak of gnome-shell after sleep mode, when arc-menu extension
  is loaded

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Whenever I put my laptop to sleep mode, the memory used by the gnome-shell 
process (usr/bin/gnome-shell) increase! each time something around 50 to 100MB. 
So after 10 to 15 times of sleeping and waking up, it takes more than 1GB of 
RAM and the whole system becomes laggy!
  I'm using Ubuntu 18.04.03 LTS with GNOME 3.28.2.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 11:26:29 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-15 (237 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1706460] Re: Outdated Totem documentation describes and mentions features absent from the software

[Daniel van Vugt]

** Bug watch added: gitlab.gnome.org/GNOME/totem/issues #108
   https://gitlab.gnome.org/GNOME/totem/issues/108

** Changed in: totem
   Importance: Medium => Unknown

** Changed in: totem
   Status: Expired => Unknown

** Changed in: totem
 Remote watch: GNOME Bug Tracker #729766 => gitlab.gnome.org/GNOME/totem/issues 
#108

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

Title:
  Outdated Totem documentation describes and mentions features absent
  from the software

Status in Totem:
  Unknown
Status in totem package in Ubuntu:
  Fix Released

Bug description:
  'man totem' mentions "F9   toggle display of the playlist" and
  the Help document in totem often describes choosing the "sidebar"
  option from the "View" menu.

  Pressing F9 does nothing.  There is no "sidebar" option in the "View"
  menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  Uname: Linux 4.10.0-26-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul 25 18:47:38 2017
  InstallationDate: Installed on 2016-06-05 (415 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: totem
  UpgradeStatus: Upgraded to zesty on 2017-04-13 (103 days ago)

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

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

[Desktop-packages] [Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss

[LaurensV]

Same issue as previous 3 reporters. All was fine until the latest
update(s), I now have the hiss back... Any idea on what might've
changed?

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

Title:
  Dell XPS 13 9350/9360 headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

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

[Desktop-packages] [Bug 1793126]

[Qa-admin-q]

Dear vaaydayaasra,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  Automatic cell alignment in Calc breaks with bidi-neutral characters

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

Bug description:
  Calc seems to assign the alignment of any particular text cell based
  on the contents of the cell: if the first character is a LTR
  character, the cell is aligned to the left, and if the first character
  is RTL, the cell is aligned to the right. This is desirable behavior
  but it breaks when the first character is neutral, i.e. a character
  that behaves as RTL in an RTL context and as LTR in a LTR context.

  See the attached screenshot where cell A1 "abc" is automatically
  aligned to the left and cell A2 "ابت" to the right. When I surround
  these strings with parentheses, which are bidi-neutral characters, in
  A3 and A4, both are aligned to the left. For some reason, even font
  metrics break with this assignment, as the last character of the
  Arabic string overlaps visually with the closing parenthesis (I think
  this is a separate issue and I’ll file it as such).

  In column C, I have copied the contents of column A but changed the
  directionality setting of cell C4 manually to RTL through Format Cells
  > Text direction. Here the cell is properly aligned to the right and
  the closing parenthesis does not overlap with the last character of
  the string.

  According to the Unicode standard, neutral characters should not
  affect directionality, and that’s what I would expect as a user, too.
  I think the best solution would be for Calc to skip all neutral
  characters in the beginning of the string and just consider the first
  strong character for cell alignment. Even better, Calc could use this
  heuristics to assign full text directionality for the cell, not just
  change alignment. Right now, if you start the cell with an RTL
  character followed by a LTR inset and then continue with RTL again,
  the substrings are ordered as in a LTR context ("FIRST second THIRD"),
  not as in true RTL ("THIRD second FIRST").

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:26:18 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  SourcePackage: 

[Desktop-packages] [Bug 1065486] Re: Calc hangs while opening xlsx file

[Christopher M. Penalver]

Kamalakar Agashe, this is no longer reproducible in:
Version: 6.3.2.2 (x64)
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c

This is a significant bug in Ubuntu. If you need a fix for the bug in
previous versions of Ubuntu, please perform as much as possible of the
SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

** Changed in: libreoffice (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  Calc hangs while opening xlsx file

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 12.04.1 LTS
  Release:  12.04

  Version: libreoffice-calc 1:3.5.4-0ubuntu1.1

  I installed libreoffice-dbg 1:3.5.4-0ubuntu1.1
  and followed instructions.
  $ soffice --backtrace

  and opened the xlsx file and libreoffice hanged.

  I killed the process by opening another terminal.
  $ pkill -15 soffice.bin

  gdbtrace.log file is attached.

  Then I have run
  $ soffice --strace

  and opened the xlsx file and libreoffice hanged.

  I killed the process by opening another terminal.
  $ pkill -15 soffice.bin

  $ bzip2 strace.log

  strace.log.bz2 file is attached.

  WORKAROUND: I am using Libreoffice 4.0 from
  https://launchpad.net/~libreoffice/+archive/ppa?field.series_filter=precise
  on Ubuntu 12.04 and the file opens OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28
  Uname: Linux 3.2.0-31-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: i386
  Date: Thu Oct 11 17:16:28 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 849741] Re: modified graphic style names reset after document close/open

[Christopher M. Penalver]

juhoeemeli, this is no longer reproducible in:
Version: 6.3.2.2 (x64)
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c

This is a significant bug in Ubuntu. If you need a fix for the bug in
previous versions of Ubuntu, please perform as much as possible of the
SRU Procedure [1] to bring the need to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

** No longer affects: df-libreoffice

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

** Changed in: libreoffice (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  modified graphic style names reset after document close/open

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Creating and modifying graphic styles works except for renaming a
  style. After document close/open the style name gets reset to what it
  was when first created.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.3-1ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Sep 14 09:59:43 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1847633] Re: 19.10 wifi networks menu doesn't respect natural scrolling settings

[tom]

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

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

Title:
  19.10 wifi networks menu doesn't respect natural scrolling settings

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce
  Be in 19.10
  Set natural scrolling to on/true/yes for mouse/touchpad
  Go to select network
  on the list of wifi SSIDs, scroll down. It won't move. Scroll up. It scrolls 
down.

  I've only tested this with touchpad, but I'm guessing it affects mice
  too? Can anyone verify?

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

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

[Desktop-packages] [Bug 1159835] Re: Index entry for Table of Contents (TOC) level 10 backs to level 1

[Christopher M. Penalver]

Fikrul Arif, if this still affects you, could you please report upstream
as requested in
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1159835/comments/2
?

Reproducible as per Bug Description in:
Version: 6.3.2.2 (x64)
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c

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

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

Title:
  Index entry for Table of Contents (TOC) level 10 backs to level 1

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  How to reproduce:
  1. In LibreOffice Writer, select a word
  2. Click Insert -> Indexes and Tables -> Entry...
  3. In Index combobox, select Table of Contents; in Level entry, enter "10"
  4. Click Insert; click Close
  5. Save and quit from LibreOffice
  6. Reopen the document in LibreOffice Writer
  7. Right click the indexed word; click Index Entry...
  Expected: the Level entry value is "10"
  Real: the Level entry value is "1"

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice-core 1:3.6.2~rc2-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Mon Mar 25 22:08:40 2013
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2012-11-04 (140 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1720262] Re: gnome-screenshot Actions don't work in default Ubuntu 17.10 session

[Futó Tamás]

The above mentioned two buggy features (Take a Screenshot of the Current Window 
and Take a Screenshot of a Selected Area) are still disabled via the 
/usr/share/applications/org.gnome.Screenshot.desktop file in Ubuntu 18.04.3 LTS 
which is a supported version right now.
Actually the commented out actions have a link in comments to this issue which 
led me here.

I've tried enabling back these actions (then log out, then login). Then
the actions appeared on right clicking on the Screenshot icon but these
features still doesn't work. I can see on the mouse pointer that
something should happen (it changes to loading indicator), but finally
nothing will happen, I can't get the screenshot.

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

Title:
  gnome-screenshot Actions don't work in default Ubuntu 17.10 session

Status in GNOME Shell:
  Confirmed
Status in gnome-screenshot package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in gnome-screenshot source package in Artful:
  Fix Released

Bug description:
  Ubuntu 17.10 Beta
  Ubuntu session (Wayland)

  Open the Activities Overview.
  Right-click on Screenshot.

  2 of the 3 extra desktop actions don't work.

  Works
  =
  Take a Screenshot of the Whole Screen

  Doesn't Work
  
  Take a Screenshot of the Current Window
  Take a Screenshot of a Selected Area

  Other Info
  ==
  All 3 functions work if you open Screenshot and click the buttons in the app.

  The Current Window action is upstream, but Selected Area is an Ubuntu
  patch.

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

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

Re: [Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Scott Palmer]

I can confirm that I am still having this issue on 3.34 as well
(Manjaro).

This is shocking to me that anyone using Gnome to develop doesn't
encounter this bug at minimum of 5x per day.  Or are Gnome developers
using MacOS and MBPs to develop like those in the lol "Linux"
Foundation.


+Scott


‐‐‐ Original Message ‐‐‐
On Sunday, October 13, 2019 7:42 AM, kohey  wrote:

> Yes, the issue still happens with 3.34.
> My work around is to trigger the following script through a keyboard shortcut.
> gsettings set org.gnome.desktop.peripherals.touchpad send-events disabled
> sleep 1
> gsettings set org.gnome.desktop.peripherals.touchpad send-events enabled
> gsettings set org.gnome.desktop.peripherals.touchpad tap-to-click false
> sleep 1
> gsettings set org.gnome.desktop.peripherals.touchpad tap-to-click true
>
> -
>
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1181666
>
> Title:
> gnome-shell randomly blocks mouse clicks from working in app windows
>
> Status in GNOME Shell:
> Confirmed
> Status in Ubuntu GNOME:
> Confirmed
> Status in gnome-shell package in Ubuntu:
> Confirmed
> Status in mutter package in Ubuntu:
> Confirmed
>
> Bug description:
> Under GNOME 3, the use of the mouse-click stops occasionally, though I
> can still move the mouse around and can still click on items in the
> Activities screen and the top-bar.
>
> I can use alt-tab to cycle windows and can still type into already-
> active textboxes in windows, but I cannot click within the windows,
> and the mouse is not picked up at all by the windows.
>
> I can open the alt-f2 "run command" dialogue, but cannot type into it.
>
> The workaround I'm using is to open terminal (ctrl-alt-T) and run
> "gnome-shell -r", and restarting that command every time I have the
> problem again.
>
> Please ask if there's anything I forgot to mention.
>
> ADDITIONAL: The error tends to happen randomly, but it seems to happen
> upon opening a new window, changing windows, closing windows, or
> opening the activities pane (whether a change of window is thus
> instigated or not)
>
> ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
> and to log in again, but that is also less than ideal
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.04
> Package: gnome-shell 3.6.3.1-0ubuntu6
> ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
> Uname: Linux 3.8.0-22-generic x86_64
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> Date: Sun May 19 07:02:18 2013
> DisplayManager: gdm
> GsettingsChanges:
>  b'org.gnome.desktop.interface' b'clock-show-date' b'true'
>  b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
>  b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
>  b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
>  b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
> InstallationDate: Installed on 2013-05-04 (14 days ago)
> InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
> (20130424)
> MarkForUpload: True
> ProcEnviron:
>  LANGUAGE=en_GB:en
>  PATH=(custom, no user)
>  XDG_RUNTIME_DIR=
> LANG=en_GB.UTF-8
>  SHELL=/bin/bash
> SourcePackage: gnome-shell
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, 

[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[kohey]

Yes, the issue still happens with 3.34.
My work around is to trigger the following script through a keyboard shortcut.
gsettings set org.gnome.desktop.peripherals.touchpad send-events disabled
sleep 1
gsettings set org.gnome.desktop.peripherals.touchpad send-events enabled
gsettings set org.gnome.desktop.peripherals.touchpad tap-to-click false
sleep 1
gsettings set org.gnome.desktop.peripherals.touchpad tap-to-click true

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

Bug description:
  Under GNOME 3, the use of the mouse-click stops occasionally, though I
  can still move the mouse around and can still click on items in the
  Activities screen and the top-bar.

  I can use alt-tab to cycle windows and can still type into already-
  active textboxes in windows, but I cannot click within the windows,
  and the mouse is not picked up at all by the windows.

  I can open the alt-f2 "run command" dialogue, but cannot type into it.

  The workaround I'm using is to open terminal (ctrl-alt-T) and run
  "gnome-shell -r", and restarting that command every time I have the
  problem again.

  Please ask if there's anything I forgot to mention.

  ADDITIONAL: The error tends to happen randomly, but it seems to happen
  upon opening a new window, changing windows, closing windows, or
  opening the activities pane (whether a change of window is thus
  instigated or not)

  ADDITIONAL 2: (sorry, it's early) The other workaround is to log out
  and to log in again, but that is also less than ideal

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-shell 3.6.3.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Sun May 19 07:02:18 2013
  DisplayManager: gdm
  GsettingsChanges:
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
   b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
   b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'"
   b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'"
   b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'"
  InstallationDate: Installed on 2013-05-04 (14 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 
(20130424)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1847597] Re: gnome-control-center cannot access google account

[Gunnar Hjalmarsson]

Changed the affected package.

@Luigi: The error message indicates that Google requires some kind of
verification. Do you have a verified Google address, and is it that
address you enter?

** Package changed: gnome-control-center (Ubuntu) => gnome-online-
accounts (Ubuntu)

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

Title:
  gnome-control-center cannot access google account

Status in gnome-online-accounts package in Ubuntu:
  Incomplete

Bug description:
  Good morning,

  If I run "gnome-control-center online-accounts" from the terminal and
  trying to add a Google account, I get this error: "Sign in with Google
  is temporarily disabled for this app. This app has not been verified
  yet by Google in order to use Google sign in". On the web, Google
  suggests to contact you, so here I am. Can you fix please? I would use
  my drive folders on my ubuntu 16.04. Thanks in advance.

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

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

[Desktop-packages] [Bug 1847882] Re: Excessive use of gnome-shell memory

[Emanuele]

Update: I have disabled and removed all the additional extensions from: 
/home/user/.local/share/gnome-shell/extensions, after 3 hours of uptime, now 
the ram is stable on the 200mb/300mb.
So I think the problem was caused by some extension.
I wonder, given the instability that extensions can have, if it is not wrong to 
have them installed so easily to the user (gnome-software)?
Maybe keep only some popular and well tested repository extensions?

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

Title:
  Excessive use of gnome-shell memory

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After 9 hours of uptime, I have the gnome-shell process that uses 6GB
  of memory ...

  emanu@emanuc:~$ ps aux | grep gnome-shell
  gdm   2014  0.0  1.0 2857772 175052 ?  Ssl  13:42   0:10 
/usr/bin/gnome-shell
  emanu 2934  6.3 38.7 10087648 6350632 ?Ssl  13:43  36:18 
/usr/bin/gnome-shell
  emanu 2963  0.0  0.1 520028 17796 ?Sl   13:43   0:00 
/usr/lib/gnome-shell/gnome-shell-calendar-server
  emanu 3278  0.2  0.6 2608268 111668 ?  Sl   13:43   1:33 gjs 
/home/emanu/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/da
  emon.js
  emanu13107  0.0  0.0   9056   924 pts/2S+   23:18   0:00 grep 
gnome-shell

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 12 23:22:21 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-18 (235 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  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/1847882/+subscriptions

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

[Desktop-packages] [Bug 1082941] Re: Duplex printing in LibreOffice not working

[Christopher M. Penalver]

** Description changed:

  I have an Epson Stylus Office BX625FWD printer and am using the epson-
  inkjet-printer-workforce-635-1.0.1-1lsb3.2 driver package.  When I try
  to print duplex from LibreOffice it will always print single sided, yet
  if I print from any other program it will work as expected.
+ 
+ WORKAROUND: Use Abiword or print to PDF and then print via Evince /
+ Adobe Reader (via WINE).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-writer 1:3.5.4-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31
  Uname: Linux 3.2.0-33-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  Date: Sun Nov 25 18:49:59 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  MarkForUpload: True
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  TERM=xterm
-  PATH=(custom, user)
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  TERM=xterm
+  PATH=(custom, user)
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-05-19 (190 days ago)

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

Title:
  Duplex printing in LibreOffice not working

Status in libreoffice package in Ubuntu:
  Expired

Bug description:
  I have an Epson Stylus Office BX625FWD printer and am using the epson-
  inkjet-printer-workforce-635-1.0.1-1lsb3.2 driver package.  When I try
  to print duplex from LibreOffice it will always print single sided,
  yet if I print from any other program it will work as expected.

  WORKAROUND: Use Abiword or print to PDF and then print via Evince /
  Adobe Reader (via WINE).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libreoffice-writer 1:3.5.4-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31
  Uname: Linux 3.2.0-33-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  Date: Sun Nov 25 18:49:59 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to precise on 2012-05-19 (190 days ago)

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

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

[Desktop-packages] [Bug 1846215] Re: Unable to rename file on desktop

[Nicholas Harvey]

This problem no longer exists with latest updates applied and so this
bug can be closed now.

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

Title:
  Unable to rename file on desktop

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

Bug description:
  Right-click on a desktop icon and select 'rename. This opens the
  rename dialogue box. You can move the cursor around the name but you
  cannot modify the text. At this stage you also cannot close the
  dialogue box by any of the buttons or by clicking on the desktop.
  Other desktop functions seem to be frozen at this point also. Only way
  yo recover is to logout or reboot. Reproducible every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell-extension-desktop-icons 19.01.4-1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 14:35:30 2019
  InstallationDate: Installed on 2019-09-23 (8 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (3 days ago)

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

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

[Desktop-packages] [Bug 1022912] Re: Error in Cross-Reference Dialog or in Fields>Other-Dialog when inserting Cross-References

[Christopher M. Penalver]

Wolfgang Zukrigl, this is now fixed as the missing cross reference numbers 
appear in both the attached document and a brand new one:
Version: 6.3.2.2 (x64)
Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c

If you need a fix for the bug in previous versions of Ubuntu, please
perform as much as possible of the SRU Procedure [1] to bring the need
to a developer's attention.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

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

** Changed in: libreoffice (Ubuntu)
   Status: Expired => Fix Released

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

Title:
  Error in Cross-Reference Dialog or in Fields>Other-Dialog when
  inserting Cross-References

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce the bug:
  Insert a picture (for example with Menue Insert > Picture > From File
  Right Click on the picture and select “Caption” and enter some text (for 
example "Example picture one"). You get a footline to the picture wich says 
“Illustration 1: Example picture one”.
  Repeat this for a second picture.
  Now try to add a cross-reference to one of the pictures: Place the cursor on 
some free text-writing-area. Then menue Insert > Cross-reference. In the Type 
field select “Illustration”. In the Selection field, the shown choices are not 
“Illustration 1” and “Illustration 2” but “llustration 1” and “llustration 2”. 
The first letter is missing. ...see screenshot

  This really turns into a problem, when I work with my own number-variables:
  In some text-area try:
  Select Menue Insert > Fields > Other, change to tab Variables. As Type select 
“Number range”. Note that the above used “Illustration” is also such a number 
range”. In the Name field type “Example” and push the button Insert. In another 
Paragraph add also some of these Example-Number-Range-variables. You get the 
numbers “1”, “2” and so on ...see second screenshot.
  Now try to make Cross-References to these numbers:
  Put the Cursor in another free text-writing-area and choose from the menu 
Insert>Cross-reference. As Type choose “Example”. The Selection-Aea remains 
empty. Expected behaviour: In the Selection Area the Numers 1, 2, and so on 
appear and can be selected.

  My Ubuntu-Version. 12.04, I am using gnome-shell
  --- 
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  Package: libreoffice 1:3.5.3-0ubuntu1
  PackageArchitecture: i386
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19
  Tags:  precise
  Uname: Linux 3.2.0-26-generic-pae i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1847904] [NEW] intel grafic

[Wadewitz Mathias]

Public bug reported:

cant install intel grafic drivers

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
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 13 14:59:11 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:15bd]
InstallationDate: Installed on 2019-10-12 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 1d57:fa01 Xenta 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X200MA
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=704348ec-f63c-4238-870e-381e532c8448 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/13/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X200MA.504
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X200MA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.504:bd11/13/2014:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X200MA
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
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

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

Title:
  intel grafic

Status in xorg package in Ubuntu:
  New

Bug description:
  cant install intel grafic drivers

  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
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 13 14:59:11 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [1043:15bd]
  InstallationDate: Installed on 2019-10-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 003: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 1d57:fa01 Xenta 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic 
root=UUID=704348ec-f63c-4238-870e-381e532c8448 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.504
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No 

[Desktop-packages] [Bug 1847882] Re: Excessive use of gnome-shell memory

[Emanuele]

Update: The problem of excessive use of memory I have at every start,
after a short time, about 1 hour of activity the memory in use of gnome-
shell goes to more than 1Gb.

I checked on the notebook with the same version of Ubuntu and the same
configuration: package version, extension version, then a 99% replica,
the gnome shell process is kept at about 234mb / 328mb of memory in use.

Hardware difference:
Notebook(no bug): CPU: Intel i3-6006, GPU: integrated Intel HD 520, session 
Wayland.
Desktop(bug): CPU: Ryzen 2600x, GPU: NVIDIA gtx 750 ti (NVIDIA proprietary 
driver 435.21), Xorg session.


** Attachment added: "photo_2019-10-13_12-29-08.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847882/+attachment/5296801/+files/photo_2019-10-13_12-29-08.jpg

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

Title:
  Excessive use of gnome-shell memory

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After 9 hours of uptime, I have the gnome-shell process that uses 6GB
  of memory ...

  emanu@emanuc:~$ ps aux | grep gnome-shell
  gdm   2014  0.0  1.0 2857772 175052 ?  Ssl  13:42   0:10 
/usr/bin/gnome-shell
  emanu 2934  6.3 38.7 10087648 6350632 ?Ssl  13:43  36:18 
/usr/bin/gnome-shell
  emanu 2963  0.0  0.1 520028 17796 ?Sl   13:43   0:00 
/usr/lib/gnome-shell/gnome-shell-calendar-server
  emanu 3278  0.2  0.6 2608268 111668 ?  Sl   13:43   1:33 gjs 
/home/emanu/.local/share/gnome-shell/extensions/gsconn...@andyholmes.github.io/service/da
  emon.js
  emanu13107  0.0  0.0   9056   924 pts/2S+   23:18   0:00 grep 
gnome-shell

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 12 23:22:21 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-02-18 (235 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  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/1847882/+subscriptions

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

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

[Ilya Brik]

I wonder how do you , guys, declare the bug as invalid while the issue is 
exists and it's still relevant.
You could at least call it duplicate with a reference to another issue, but 
INVALID it is not.
To the point:
This issue is relevant for me on a freshly installed Kubuntu 19.04.
I tried to use the workaround proposed by @ronny, but it doesn't look as a good 
idea:

sudo apt remove isc-dhcp-client 

Sun 13 Oct 2019 13:45:45 IDT
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  dns-root-data dnsmasq-base isc-dhcp-common libdns-export1104 
libisc-export1100 libkf5modemmanagerqt6 libndp0 libopenconnect5 libstoken1 
libteamdctl0 libtomcrypt1 libtommath1 libtss2-esys0 libtss2-udev pptp-linux
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  isc-dhcp-client network-manager network-manager-gnome network-manager-pptp 
network-manager-pptp-gnome plasma-nm ubuntu-minimal

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

Title:
  Avahi-daemon withdraws address record

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

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

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

  
  for no known reason.

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

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

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

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

[Desktop-packages] [Bug 1838806] Re: vulkan apps makes desktop freeze with kernel 5.0 on amdgpu raven ridge

[Luca]

Fixed in mesa-vulkan-drivers:amd64 (19.0.8-0ubuntu0~18.04.3)

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

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  vulkan apps makes desktop freeze with kernel 5.0 on amdgpu raven ridge

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  After yesterday update to 5.0.0-23-generic of the linux-generic-
  hwe-18.04 kernel every vulkan applications (e.g. steam or vulkan-
  smoketest) make my desktop freeze (ssh continue working, but the only
  option is to use sysqr to reboot the system).

  Similar bug reports:
  https://github.com/ValveSoftware/steam-for-linux/issues/6268 says it has been 
fixed in mesa 19.X but don't specify which version
  this seems related too
  https://lists.freedesktop.org/archives/amd-gfx/2018-March/020569.html

  
  APU:

  ryzen 2200g

  workaround:

  use AMDVLK instead of RADV

  ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: [gfxhub] VMC page fault 
(src_id:0 ring:158 vmid:3 pasid:32768, for process vulkan-smoketes pid 6759 
thread vulkan-smoketes pid 6759)
  ago 02 19:19:48 ghv kernel: amdgpu :07:00.0:   in page starting at 
address 0x00174000 from 27
  ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x0030153D
  ago 02 19:19:48 ghv kernel: amdgpu :07:00.0: [gfxhub] VMC page fault 
(src_id:0 ring:158 vmid:3 pasid:32768, for process vulkan-smoketes pid 6759 
thread vulkan-smoketes pid 6759)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: mesa-vulkan-drivers (not installed)
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Aug  2 20:11:54 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  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] Vega [Radeon Vega 8 
Mobile] [1002:15dd]
  InstallationDate: Installed on 2018-11-30 (244 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.90
  dmi.board.name: AB350M 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.:bvrP5.90:bd07/03/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  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/mesa/+bug/1838806/+subscriptions

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

[Desktop-packages] [Bug 1847597] Re: gnome-control-center cannot access google account

[Luigi]

I start the application typing in the terminal the following command:

"gnome-control-center online-accounts"

Could you tell me how to do xprop on the application?

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

Title:
  gnome-control-center cannot access google account

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

Bug description:
  Good morning,

  If I run "gnome-control-center online-accounts" from the terminal and
  trying to add a Google account, I get this error: "Sign in with Google
  is temporarily disabled for this app. This app has not been verified
  yet by Google in order to use Google sign in". On the web, Google
  suggests to contact you, so here I am. Can you fix please? I would use
  my drive folders on my ubuntu 16.04. Thanks in advance.

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

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

[Desktop-packages] [Bug 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell

[Pierre-Antoine Champin]

Sorry (again) for the late reply.

I just got an opportunity to install a fresh ubuntu 19.04, so I thought
I would give a try to the patch... But on this fresh install, I do not
have the problem... (without even enabling proposed packaged).

I don't even understand *why* the x11-bell module is *not* loaded... 
(I did install the ubuntu-sounds package, as this is a condition in 
start-pulseaudio-x11).

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Committed

Bug description:
  * Impact
  The package force load a bell sound which can conflicts with the user 
configuration

  * Test case
  - Enable a login sound in session
  - Login into a GNOME/Ubuntu session
  -> the configured sound should be played

  * Regression potential
  Try other desktop environments to make sure their login sound behaviour isn't 
changed, it shouldn't since the customization dropped was specific to the 
Ubuntu sound theme

  ---

  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

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

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

[Desktop-packages] [Bug 1847896] Re: Unable to shutdown or restart from log-in screen

[Paul White]

Marking confirmed as user on forums also seeing issue:
https://ubuntuforums.org/showthread.php?t=2429058

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  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: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  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/1847896/+subscriptions

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

[Desktop-packages] [Bug 1847896] Re: Unable to shutdown or restart from log-in screen

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1847896

** Tags added: iso-testing

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  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: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  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/1847896/+subscriptions

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

[Desktop-packages] [Bug 1847896] [NEW] Unable to shutdown or restart from log-in screen

[Paul White]

Public bug reported:

When selecting the shutdown icon from the log-in screen you are prompted
with a dialog that allows you to either cancel, restart or shutdown.

It has been noted that the restart and shutdown options no longer work.

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: GNOME
Date: Sun Oct 13 09:08:23 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-05-17 (148 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Unable to shutdown or restart from log-in screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When selecting the shutdown icon from the log-in screen you are
  prompted with a dialog that allows you to either cancel, restart or
  shutdown.

  It has been noted that the restart and shutdown options no longer
  work.

  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: GNOME
  Date: Sun Oct 13 09:08:23 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-05-17 (148 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517)
  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/1847896/+subscriptions

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

[Desktop-packages] [Bug 1847706] Re: Deja Dup still tells python-gi (python 2) is required while duplicity is now python3

[Nobuto Murata]

** Changed in: deja-dup
   Status: Triaged => Invalid

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

Title:
  Deja Dup still tells python-gi (python 2) is required while duplicity
  is now python3

Status in Déjà Dup:
  Invalid
Status in deja-dup package in Ubuntu:
  Fix Released
Status in deja-dup source package in Eoan:
  Fix Released

Bug description:
  Please see the screenshot attached. When running a backup operation
  against a remote server with SSH, Deja Dup stops by saying "python-gi"
  package is required.

  However, duplicity is updated with Python3 now, so it doesn't make
  sense to install Python 2 based package. The prerequisite check needs
  to be updated probably with python3-gi instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: deja-dup 40.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 11 12:34:15 2019
  InstallationDate: Installed on 2019-08-28 (43 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1847706/+subscriptions

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