[Desktop-packages] [Bug 1845802] Re: Corrupt/skewed gnome-shell panel rendering

[Daniel van Vugt]

** Summary changed:

- Smeared top panel and hint tips on Plank and browser icon
+ Corrupt/skewed gnome-shell panel rendering

** Tags added: radeon

** Summary changed:

- Corrupt/skewed gnome-shell panel rendering
+ [radeon] Corrupt/skewed gnome-shell panel rendering

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

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

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

Title:
  [radeon] Corrupt/skewed gnome-shell panel rendering

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

Bug description:
  It would take more than one snapshot, but this all happens on Dell
  external monitor:

  1. Top panel has blurred/smeared icons.
  2. Hint tips on browser icons are also smeared.
  3. Plank tips are smeared or blurry on some icons.

  Screenshot after exiting full screen (could not restore to full) and top 
panel was set to autohide and would not budge.
  https://justpaste.it/7rqzp

  Otherwise, everything is okay on laptop monitor itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sat Sep 28 13:23:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e]
  InstallationDate: Installed on 2019-09-28 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=64852f66-77ef-4b0f-b326-aec23cfe7db3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2017
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.asset.tag: CNU148133S
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.sku: LQ168AW#ABA
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso

[vmware-gos-Yuhua]

No file /etc/network/interfaces in ubuntu-19.10-beta-desktop-amd64.iso.

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

Title:
  file /etc/network/interfaces is missing in eoan-desktop-amd64.iso

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The file /etc/network/interfaces is missing after install guestOS with
  eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi.

  This issue cause a failure for VMware Guest OS Customization

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

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

[Desktop-packages] [Bug 1845892] Re: gedit crashes system when launched from terminal as root

[Bashing-om]

Guilherme; Hey -

The fact of the matter is that "sudo" is no longer the means to enable
'root's" use of GUI applications; as gksu is depreciated. Not a miss-
configuration of the system either.

Preferable is "admin://" - though there are 2 other alternates that I am aware 
of.
If you do, as I, prefer "sudo" then try as
sudo -H gedit etc/apt/sources
to start a GUI App from terminal.

Else there is also "pkexec". To do so you may have to install the admin package:
sudo apt install nautilus-admin.
then: pkexec gedit

Please try these alternatives and advise on the result.

Still - look at this as a miss use of privileges rather than a bug until
proven otherwise.

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

Title:
  gedit crashes system when launched from terminal as root

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  This happens whenever I try to edit a file (for example 
/etc/apt/sources.list) or open gedit with root privileges. Application window 
opens, characters are replaced by squares, and becomes impossible to drag or 
resize it as my system completely stalls. Also if firefox is open, it also 
becomes unresponsive and crashes. 
  This screenshot summarises what i have been experiencing so far: 
https://i.imgur.com/8R6vZhE.jpg
  Additionally, it also happens with nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 19:34:14 2019
  InstallationDate: Installed on 2016-11-14 (1048 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (403 days ago)

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

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

[Desktop-packages] [Bug 1842898] Re: Scroll bar in the focussed Terminal window is almost invisible

[Daniel van Vugt]

** Changed in: yaru-theme (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Scroll bar in the focussed Terminal window is almost invisible

Status in Yaru Theme:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released

Bug description:
  Scroll bar in the focussed Terminal window is almost invisible.

  Strangely it's quite visible for all the other (unfocussed) Terminal
  windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: yaru-theme-gtk 19.10.1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Thu Sep  5 17:50:51 2019
  InstallationDate: Installed on 2019-05-02 (126 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501)
  PackageArchitecture: all
  SourcePackage: yaru-theme
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1834967] Re: Activities overview doesn't shrink some windows adequately and they are partially off screen

[Daniel van Vugt]

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

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

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

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

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

Title:
  Activities overview doesn't shrink some windows adequately and they
  are partially off screen

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

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-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/1834967/+subscriptions

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

[Desktop-packages] [Bug 1845165] Re: gnome-shell crashed with SIGSEGV in in ??() [non-native amd64 package]

[Daniel van Vugt]

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

Title:
  gnome-shell crashed with SIGSEGV in  in ??() [non-native
  amd64 package]

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Ubuntu desktop netboot install on i386.

  Session crashes on login.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic i686
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: i386
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 24 11:07:13 2019
  Disassembly: value is not available
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-07-15 (1897 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  PackageArchitecture: amd64
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  SegvAnalysis: Failure: invalid literal for int() with base 16: ''
  Signal: 11
  SourcePackage: gnome-shell
  Stacktrace:
   #0   in ?? ()
   PC unavailable, cannot determine locals.
   Backtrace stopped: not enough registers or memory available to unwind further
  StacktraceTop:  in ?? ()
  Title: gnome-shell crashed with SIGSEGV in  in ??() [non-native 
amd64 package]
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (548 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1845792] Re: gnome-shell crashed with SIGSEGV in meta_get_window_actors()

[Daniel van Vugt]

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

** This bug is no longer a duplicate of private bug 1845136
** This bug has been marked a duplicate of private bug 1844850

** This bug is no longer a duplicate of bug 1844850
   gnome-shell crashed with SIGSEGV in meta_get_window_actors()
** This bug has been marked a duplicate of bug 1843182
   gnome-shell crashed with SIGSEGV in meta_get_window_actors()

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

Title:
  gnome-shell crashed with SIGSEGV in meta_get_window_actors()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Several gnome-shell crashes

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  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: Sat Sep 28 19:31:52 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-09-28 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_get_window_actors () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   shell_global_get_window_actors () from /usr/lib/gnome-shell/libgnome-shell.so
   ffi_call_unix64 () from /lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_get_window_actors()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Desktop-packages] [Bug 1832786] Re: [snap] chromium-browser ignores system password store

[Launchpad Bug Tracker]

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

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

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

Title:
  [snap] chromium-browser ignores system password store

Status in chromium-browser package in Ubuntu:
  Expired

Bug description:
  The new chromium 75 snap package intentionally ignores the system
  password store:

  
https://chromium.googlesource.com/chromium/src.git/+/master/docs/linux_password_storage.md

  Normally, chromium auto-detects what type of password store to use,
  previously this has resulted in chromium connecting to the gnome
  password store. The new snap release passes the command line argument:

  '--password-store=basic'

  Which bypasses the gnome password storage.

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

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

[Desktop-packages] [Bug 1845197] Re: GNOME Shell seemingly locked up at login

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1845198
   GNOME Shell seemingly locked up at login

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

Title:
  GNOME Shell seemingly locked up at login

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  In 19.10, and also running the X PPA from
  http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

  When I logged in (after having attached a Bluetooth speaker in order
  to test if it was being reconnected correctly) GNOME Shell isn't
  responding to mouse or keyboard input.

  The clock continues to tell the right time, and the mouse moves around
  the screen and is repainted correctly.

  Most recent output from gdb here:
  https://paste.ubuntu.com/p/pSshP8V2SZ/

  Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

  Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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

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

[Desktop-packages] [Bug 1844850] Re: gnome-shell crashed with SIGSEGV in meta_get_window_actors()

[Daniel van Vugt]

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

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 1843182
   gnome-shell crashed with SIGSEGV in meta_get_window_actors()

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

Title:
  gnome-shell crashed with SIGSEGV in meta_get_window_actors()

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Crashed at log out from Settings

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 21 07:24:58 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-08-02 (49 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_get_window_actors () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   shell_global_get_window_actors () from /usr/lib/gnome-shell/libgnome-shell.so
   ffi_call_unix64 () from /lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_get_window_actors()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1843182] Re: gnome-shell crashed with SIGSEGV in meta_get_window_actors()

[Daniel van Vugt]

** Information type changed from Private to Public

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

** Summary changed:

- gnome-shell crashed with SIGSEGV in meta_get_window_actors()
+ gnome-shell crashed with SIGSEGV in meta_get_window_actors() when using 
extension dash-to-panel

** Also affects: gnome-shell-extension-dash-to-panel (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-shell crashed with SIGSEGV in meta_get_window_actors() when
  using extension dash-to-panel

Status in gnome-shell package in Ubuntu:
  Invalid
Status in gnome-shell-extension-dash-to-panel package in Ubuntu:
  Confirmed

Bug description:
  The error appeared immediately after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  8 17:12:33 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-09-08 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   meta_get_window_actors () from /lib/x86_64-linux-gnu/libmutter-5.so.0
   shell_global_get_window_actors () from /usr/lib/gnome-shell/libgnome-shell.so
   ffi_call_unix64 () from /lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /lib/x86_64-linux-gnu/libffi.so.6
   ?? () from /lib/libgjs.so.0
  Title: gnome-shell crashed with SIGSEGV in meta_get_window_actors()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1834967] Re: Activities overview doesn't shrink some windows adequately and they are partially off screen

[Carlos Pita]

Hi Daniel, for me is ubuntu-dock, I've not even tested this with
upstream dash-to-dock.

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

Title:
  Activities overview doesn't shrink some windows adequately and they
  are partially off screen

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

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-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-extension-dashtodock/+bug/1834967/+subscriptions

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

[Desktop-packages] [Bug 1845825] Re: i2c_designware and i2c_hid failures on shutdown

[Daniel van Vugt]

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

apport-collect 1845825

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

** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)

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

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

Title:
  i2c_designware and i2c_hid failures on shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1. Using Ubuntu 19.10
  2. Shutdown system
  3. System get stuck at the windows with this messages:

  i2c_designware.o: controller timed out
  i2c_hid: failed to change power settings.

  It might not be related to the shutdown not happening, still that's
  the only clue I have.

  I attach the screenshot and dmesg output after the following boot.

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

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

[Desktop-packages] [Bug 1845198] Re: GNOME Shell seemingly locked up at login

[Daniel van Vugt]

** Tags added: 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/1845198

Title:
  GNOME Shell seemingly locked up at login

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress
Status in gnome-shell source package in Eoan:
  In Progress

Bug description:
  In 19.10, and also running the X PPA from
  http://ppa.launchpad.net/canonical-x/x-staging/ubuntu

  When I logged in (after having attached a Bluetooth speaker in order
  to test if it was being reconnected correctly) GNOME Shell isn't
  responding to mouse or keyboard input.

  The clock continues to tell the right time, and the mouse moves around
  the screen and is repainted correctly.

  Most recent output from gdb here:
  https://paste.ubuntu.com/p/pSshP8V2SZ/

  Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/

  Journal here:  https://paste.ubuntu.com/p/GZcWsQdRhd/

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

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

[Desktop-packages] [Bug 1844809] Re: clicking desktop notifications to bring up linked up works intermittently in 19.10?

[Daniel van Vugt]

This sounds like it might be related to focus stealing prevention. That
is the code which prevents new windows getting focus if the system
thinks you're busy with something else, so new windows would only get in
the way.

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

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

Title:
  clicking desktop notifications to bring up linked up works
  intermittently in 19.10?

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

Bug description:
  This is not going to be the highest quality bug report :-(, since it's
  an intermittent issue and I don't know exactly what triggers it and I
  can't even say with 100% certainty that it's new in 19.10, but I
  _think_ it is so I wanted to give people a heads-up just in case.

  I just upgrade to 19.10 from 19.04. I use the Google Hangouts Chrome
  app. When I get a text message in Hangouts it pops up a desktop
  notification. Usually clicking on the notification causes the Hangouts
  window to open. When I clicked on the notification nothing happened.
  Then I got a second notification later and clicked on that one and the
  window opened as it should have. Then I got a third notification later
  and clicked on that one and again the window didn't open.

  I _believe_, though I can't say for certain, that this worked
  consistently in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 20 11:20:19 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1844811] Re: system menu is no longer dark in Yaru-dark or Adwaita-dark theme

[Daniel van Vugt]

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

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


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

** This bug has been marked a duplicate of bug 1842886
   Yaru-dark shell menus are not dark

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

Title:
  system menu is no longer dark in Yaru-dark or Adwaita-dark theme

Status in yaru-theme package in Ubuntu:
  New

Bug description:
  The system menu from the top bar is no longer dark in the Adwait-dark
  or Yaru-dark theme after upgrading from 19.04 to 19.10. See attached
  screenshot. Oddly, it _is_ dark in HighContrast theme, which I don't
  think it should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 20 11:27:41 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-09-12 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago)

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

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

[Desktop-packages] [Bug 1841794] Re: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed ob

[Daniel van Vugt]

Weird. Now the page is correctly showing 3.34.0-3ubuntu1 is the latest.

https://launchpad.net/ubuntu/+source/mutter

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

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

Title:
  gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from
  ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper
  for an already freed object of type: Clutter.PropertyTransition"]

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/10051642bda6e2a9a27fe0b0d5f84f8b1f29438f

  ubuntu-bug crash report for bug reported in LP: #1841680

  On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when
  opening up applications from the dock.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 10:42:41 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-19 (554 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to eoan on 2019-08-27 (0 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sbuild sudo
  separator:

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

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

[Desktop-packages] [Bug 1834967] Re: Activities overview doesn't shrink some windows adequately and they are partially off screen

[Daniel van Vugt]

Sorry, I was on vacation and lost track...

Does everyone only experience this bug with dash-to-dock? Or is this a
bug which we have inherited in ubuntu-dock too?

** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)

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

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

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

** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Activities overview doesn't shrink some windows adequately and they
  are partially off screen

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

Bug description:
  Details in my screenshot: https://photos.app.goo.gl/BR6H56eug7JFMGU37

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.32.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8
  Uname: Linux 5.0.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  1 20:38:43 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-07-01 (0 days ago)
  InstallationMedia:
   
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.32.2+git20190626-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-extension-dashtodock/+bug/1834967/+subscriptions

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

[Desktop-packages] [Bug 1804568] Re: click position is flipped to cursor position when in tent mode

[Daniel van Vugt]

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

** Tags removed: cosmic

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

Title:
  click position is flipped to cursor position when in tent mode

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  same bug is present 18.04 and 18.10:

  after I log in in tent mode the screen goes upside down, and after

  xrandr --output eDP-1 --rotate normal

  it goes back to normal however now the cursor is upside down, and
  click position and cursor position isnt the same, they are flipped

  thank you for the fix in advance

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: coreutils 8.28-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 22 04:28:21 2018
  ExecutablePath: /bin/sleep
  InstallationDate: Installed on 2018-11-22 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANG=hu_HU.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1950 F pulseaudio
   /dev/snd/controlC1:  imi1950 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-03-30 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-8-generic N/A
   linux-backports-modules-5.0.0-8-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-8-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.31
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.60
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imi1333 F pulseaudio
   /dev/snd/controlC1:  imi1333 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-23 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917)
  MachineType: HP HP Spectre x360 Convertible 13-w0XX
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-10-generic N/A
   linux-backports-modules-5.3.0-10-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/03/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.49
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.71
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible 13-w0XX
  dmi.product.sku: Z9E46EA#ABV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1845899] Re: gnome-terminal won't run with python 3.7.3, but it will with python 3.6.8

[Chris Guiver]

Thank you for taking the time to report this bug and trying to help make
Ubuntu better.

However, it seems that you are not using a software package provided by
the official Ubuntu repositories, or packages provided for your release.

Because of this the Ubuntu project may not support or fix your
particular bug.

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

The link
https://packages.ubuntu.com/search?suite=all=names=python3
shows python3 3.7 is used by Ubuntu 19.04 (disco) and is not the
supported python3 (3.6) provided and supported for 18.04 (bionic).

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

Title:
  gnome-terminal won't run with python 3.7.3, but it will with python
  3.6.8

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  For quite some time, I've been battling with a problem where my gnome-
  terminal won't run.

  I have finally isolated it down to Python 3.7.3.

  When my symlink for python3 points to python 3.7.3, I cannot get 
gnome-terminal to run.
  When I point my symlink for python3 to python 3.6.8, gnome-terminal runs fine.

  I have not tried versions between python 3.6.8 and python 3.7.3, but I
  have narrowed it down all the way.

  Steps for me to reproduce...starting with symlink python3->python 3.6.8
  Attempt to run gnome-terminal from favorites bar. It runs fine.
  Keep the gnome-terminal open
  From within gnome-terminal:

$ sudo rm /usr/bin/python3
$ sudo ln -s /usr/bin/python3.7 /usr/bin/python3

  Now attempt to run gnome-terminal from the favorites bar...the mouse
  pointer spins, indicating that it is trying to run gnome-
  terminal...after a short time, the mouse pointer stops spinning, but
  gnome-terminal does NOT start.

  Now, from the open gnome-terminal do the following steps:
 $ sudo rm /usr/bin/python3
 $ sudo ln -s /usr/bin/python3.6 /usr/bin/python3

  Now attempt to run gnome-terminal from the favorites bar...it runs
  fine.

  I have switched the python3 symlink between python 3.7.3 and python
  3.6.8 many times at this point and I'm always able to reproduce the
  above.

  Feel free to email me if you have questions.

  Best regards,

  --Jay Sevison

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 20:31:45 2019
  InstallationDate: Installed on 2019-09-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1845102] Re: Video tearing in Celluloid with new Yaru theme

[Daniel van Vugt]

This sounds like a coincidence as I don't think the theme can directly
cause screen tearing.

Please run this command to send us more information about the affected
machine:

  apport-collect 1845102

** Package changed: yaru-theme (Ubuntu) => mutter (Ubuntu)

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

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

Title:
  Video tearing in Celluloid with new Yaru theme

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  My specs:
  Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450]
  Intel(R) Core(TM)2 Quad CPU Q9400  @ 2.66GHz

  Latest version of Celluloid (0.17) obtained by PPA:
  https://launchpad.net/~xuzhen666/+archive/ubuntu/gnome-mpv

  
  When I use the new Ubuntu 19.10 dev theme (all gray Yaru), video playback 
starts to tear in Celluloid (I wasn't able to capture it with 
SimpleScreenRecorder, sorry, the tearing does not appear in the capture). 
  Really similar tearing occurs with Adwaita as the enabled theme. 
  It however does NOT occur at all with the  older Yaru theme (which I copied 
from my Ubuntu 19.04 install).

  There is no tearing with any of the themes enabled in Wayland.
  Tearing is scant and impossible to appreciate in VLC.
  These issues occur only in X, and in Celluloid. 

  The reason I'm reporting this to you is because it coincides with the
  theme change.

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

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

[Desktop-packages] [Bug 1841794] Re: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed ob

[Daniel van Vugt]

The latest version of mutter in eoan is presently 3.34.0-1ubuntu1, so do
we declare this unfixed?...

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

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

Title:
  gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from
  ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper
  for an already freed object of type: Clutter.PropertyTransition"]

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Eoan:
  Fix Committed

Bug description:
  https://errors.ubuntu.com/problem/10051642bda6e2a9a27fe0b0d5f84f8b1f29438f

  ubuntu-bug crash report for bug reported in LP: #1841680

  On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when
  opening up applications from the dock.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 27 10:42:41 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2018-02-19 (554 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in g_log_default_handler()
  UpgradeStatus: Upgraded to eoan on 2019-08-27 (0 days ago)
  UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare 
sbuild sudo
  separator:

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

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

[Desktop-packages] [Bug 1799103] Re: [radeon] Screen corrupted (skewed stride) after boot

[Daniel van Vugt]

** Changed in: mutter (Ubuntu)
   Status: Won't Fix => New

** Tags removed: cosmic
** Tags added: disco

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

Title:
  [radeon] Screen corrupted (skewed stride) after boot

Status in mutter package in Ubuntu:
  New

Bug description:
  after reboot during upgrade 18.04 to 18.10, screen doesn't show login, see 
pic.
  However, if I mouseover the line, colors/lines change, and if I click middle 
of screen I see the cursor changing from 'arrow' to 'vertical line where you 
can type'. I then type the login password and voilà! I get the cosmic 
cuttlefish desktop and everything works fine :-D

  I have 2 more pics for the blind/hidden login sequence

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 01:57:20 2018
  DistUpgraded: 2018-10-20 12:00:41,261 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS690 [Radeon X1200] [1002:791e] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RS690 [Radeon X1200] [1043:826d]
  InstallationDate: Installed on 2018-10-05 (16 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ed7ef936-bff3-46c8-887d-205d5a70d4d4 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (1 days ago)
  dmi.bios.date: 06/26/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M2A-VM ACPI BIOS Revision 0901
  dmi.board.name: M2A-VM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2A-VMACPIBIOSRevision0901:bd06/26/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2A-VM:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
  xserver.bootTime: Sat Oct 20 22:32:39 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.1-3ubuntu2

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

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

[Desktop-packages] [Bug 1792167] Re: Display size detected incorrectly

[Daniel van Vugt]

Sorry I lost track of this bug. The attachment in comment #7 shows:

HDMI-1 connected 1920x1080+1366+0 (0x8b) normal (normal left inverted
right x axis y axis) 160mm x 90mm

So the hardware is indeed reporting itself as ~7.2 inches. This is a
hardware fault (incorrect EDID data?) I have seen before. Probably the
best we can hope for is to add heuristics to detect faulty hardware, but
that would be unreliable and unlikely to ever happen.


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

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  My external monitor is detected as 7" although it is 32". All
  applications which use Qt auto scaling have huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  It seems not related to the display server, compositor or window
  manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as
  well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on
  Wayland).

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1845899] [NEW] gnome-terminal won't run with python 3.7.3, but it will with python 3.6.8

[Jay Sevison]

Public bug reported:

For quite some time, I've been battling with a problem where my gnome-
terminal won't run.

I have finally isolated it down to Python 3.7.3.

When my symlink for python3 points to python 3.7.3, I cannot get gnome-terminal 
to run.
When I point my symlink for python3 to python 3.6.8, gnome-terminal runs fine.

I have not tried versions between python 3.6.8 and python 3.7.3, but I
have narrowed it down all the way.

Steps for me to reproduce...starting with symlink python3->python 3.6.8
Attempt to run gnome-terminal from favorites bar. It runs fine.
Keep the gnome-terminal open
>From within gnome-terminal:

  $ sudo rm /usr/bin/python3
  $ sudo ln -s /usr/bin/python3.7 /usr/bin/python3

Now attempt to run gnome-terminal from the favorites bar...the mouse
pointer spins, indicating that it is trying to run gnome-
terminal...after a short time, the mouse pointer stops spinning, but
gnome-terminal does NOT start.

Now, from the open gnome-terminal do the following steps:
   $ sudo rm /usr/bin/python3
   $ sudo ln -s /usr/bin/python3.6 /usr/bin/python3

Now attempt to run gnome-terminal from the favorites bar...it runs fine.

I have switched the python3 symlink between python 3.7.3 and python
3.6.8 many times at this point and I'm always able to reproduce the
above.

Feel free to email me if you have questions.

Best regards,

--Jay Sevison

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
Uname: Linux 4.15.0-64-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 29 20:31:45 2019
InstallationDate: Installed on 2019-09-27 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  gnome-terminal won't run with python 3.7.3, but it will with python
  3.6.8

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  For quite some time, I've been battling with a problem where my gnome-
  terminal won't run.

  I have finally isolated it down to Python 3.7.3.

  When my symlink for python3 points to python 3.7.3, I cannot get 
gnome-terminal to run.
  When I point my symlink for python3 to python 3.6.8, gnome-terminal runs fine.

  I have not tried versions between python 3.6.8 and python 3.7.3, but I
  have narrowed it down all the way.

  Steps for me to reproduce...starting with symlink python3->python 3.6.8
  Attempt to run gnome-terminal from favorites bar. It runs fine.
  Keep the gnome-terminal open
  From within gnome-terminal:

$ sudo rm /usr/bin/python3
$ sudo ln -s /usr/bin/python3.7 /usr/bin/python3

  Now attempt to run gnome-terminal from the favorites bar...the mouse
  pointer spins, indicating that it is trying to run gnome-
  terminal...after a short time, the mouse pointer stops spinning, but
  gnome-terminal does NOT start.

  Now, from the open gnome-terminal do the following steps:
 $ sudo rm /usr/bin/python3
 $ sudo ln -s /usr/bin/python3.6 /usr/bin/python3

  Now attempt to run gnome-terminal from the favorites bar...it runs
  fine.

  I have switched the python3 symlink between python 3.7.3 and python
  3.6.8 many times at this point and I'm always able to reproduce the
  above.

  Feel free to email me if you have questions.

  Best regards,

  --Jay Sevison

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 20:31:45 2019
  InstallationDate: Installed on 2019-09-27 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1551599] Re: Remove button missing after package installation

[SeongJin Cheong]

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => SeongJin Cheong (azmaster82)

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

Title:
  Remove button missing after package installation

Status in One Hundred Papercuts:
  Confirmed
Status in Release Notes for Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Confirmed
Status in gnome-software source package in Yakkety:
  Confirmed
Status in gnome-software source package in Zesty:
  Confirmed

Bug description:
  [What Happens]
  ==
  Installing
  --
  1. Open the Software app (GNOME Software). Search for clocks.
  2. Click Install next to Clocks.
  3. The Install button becomes insensitive and changes to Installing...
  4. The Install button becomes sensitive again and changes back to Install (it 
should have changed to Remove)
  5. If you click the Clocks row (still in the All page), the Clocks info page 
opens with an Install button (it should have a Launch button and a Remove 
button).
  6. If you switch to the Installed page, Clocks correctly shows up with a 
Remove button.
  7. If you click the Clocks row in the Installed page, the Clocks info page 
correctly opens with a Launch button and a Remove button.
  8. Close the Software app then reopen it. Same results as #4-7 above.
  9. $ pkill gnome-software
  10. Open the Software app. Now Clocks shows up correctly in the All page with 
a Remove button and the Clocks info page correctly includes the Launch and 
Remove buttons but not the Install button.

  Removing
  
  11. Click the Remove button to uninstall Clocks.
  12. The Remove button becomes insensitive again and changes to Removing...
  12. We basically get the same broken results as before. In the All page, the 
Clocks row shows Remove still. Clicking the Clocks row shows the Info page with 
Launch and Remove.
  One change is that in the Installed page, Clocks shows up twice, once with an 
Install button, once with a Remove button.
  Completely stopping the gnome-software process (via logging out or the pkill 
trick mentioned in #9) is necessary for the Software app to correctly register 
Clocks as being removed.

  I was unable to reproduce this bug with Fedora 24.

  Other Info
  ==
  See also bug 1582959 which is similar but a bit different.

  In bug 1679417, a user reported that the package disappears from the
  Installed list if Remove is selected but password authentication is
  cancelled or failed.

  [Original bug report]
  =
  Used gnome-software to install a package.

  Once it was installed I expected to see an option to remove it.

  As can be seen all I see is the option to Install the package.

  If you click Install you are then given the option to remove the
  package.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.91~git20160229.ceb6b9d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Mar  1 08:05:06 2016
  InstallationDate: Installed on 2015-10-29 (123 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1792167] Re: Display size detected incorrectly

[Daniel van Vugt]

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

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Expired => Confirmed

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

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

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  My external monitor is detected as 7" although it is 32". All
  applications which use Qt auto scaling have huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  It seems not related to the display server, compositor or window
  manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as
  well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on
  Wayland).

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~desktop-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] [NEW] Unable to set touchpad Edge Scrolling in Eoan

[Erick Brunzell]

Public bug reported:

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)

** Affects: gnome-control-center (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-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 1727130] Re: Marking text using touchpad stops working after awaking from suspended state on laptop

[Daniel van Vugt]

This bug is old and has reached end of life (reported against 17.10
which is no longer supported).

I suggest opening a new bug for 18.04 by running:

  ubuntu-bug libinput


** Tags added: artful

** Changed in: libinput (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Marking text using touchpad stops working after awaking from suspended
  state on laptop

Status in libinput package in Ubuntu:
  Won't Fix

Bug description:
  I am running Ubuntu Budgie 17.10 installed “clean” on a Lenovo
  Thinkpad X1 Carbon (3rd generation).I use the touchpad to mark a
  block of text (e.g., as part of a copy-and-paste operation) by holding
  my thumb on the left part of the touchpad and moving another finger on
  the touchpad to select the area to be marked.  This capability works
  fine until I awake my laptop (by opening the lid) from a suspended
  state (when the laptop lid is closed).  After awaking from a suspend,
  if I hold my thumb on the left part of the touchpad, any other
  movements on the touchpad with another finger do not move the cursor
  on the screen.  I have attached an image of the mouse/touchpad
  settings.  Incidentally, selection of the “two finger scrolling” or
  “natural scrolling” options appear to have no effect on this issue.
  For completeness, if I use the physical left-mouse button (above the
  touchpad) I can then move a finger on the touchpad (or move the
  trackpoint “red button in the center of the keyboard”) to mark text.
  It is only when I am trying to mark text using a “holding a thumb” on
  the touchpad *PLUS* a moving finger on the touchpad that I encounter
  this issue after awaking the laptop from a suspended state.  After a
  reboot of the system, all works fine, until a subsequent awaking from
  a suspend.

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

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

[Desktop-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly

[Ghost]

Oddly i have had the same issue and I today i was getting annoyed so i
went to wifi and switched from my 5G to 2.4 and it has been solid since.
I will update if anything changes. Can finally not have to run a
constant ping to keep it alive. on 5G when running a constant ping that
would prevent the issue from happening

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

Title:
  "Activation of network connection failed" popup shows incessantly

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

Bug description:
  All network connections work normally, however the popup "Activation
  of network connection failed" keeps showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:04:56 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 
600 
   192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 
linkdown 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1845892] Re: gedit crashes system when launched from terminal as root

[Guilherme]

Hi there Bashing-om.

Thanks for the quick response.
I'm starting gedit from terminal. 
$gedit runs without any issue, however
$sudo gedit ... yields all the said issues.
As a layman in the subject, I don't know if this is really a bug or 
misconfiguration in my system. But the fact is that it wasn't happening since 
last week or so.

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

Title:
  gedit crashes system when launched from terminal as root

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  This happens whenever I try to edit a file (for example 
/etc/apt/sources.list) or open gedit with root privileges. Application window 
opens, characters are replaced by squares, and becomes impossible to drag or 
resize it as my system completely stalls. Also if firefox is open, it also 
becomes unresponsive and crashes. 
  This screenshot summarises what i have been experiencing so far: 
https://i.imgur.com/8R6vZhE.jpg
  Additionally, it also happens with nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 19:34:14 2019
  InstallationDate: Installed on 2016-11-14 (1048 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (403 days ago)

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

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

[Desktop-packages] [Bug 1845892] Re: gedit crashes system when launched from terminal as root

[Bashing-om]

Hello Guilherme

You do not say how you are starting gedit. As policykit now applies what 
results:
gedit admin:///etc/apt/sources ?


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

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

Title:
  gedit crashes system when launched from terminal as root

Status in gedit package in Ubuntu:
  Incomplete

Bug description:
  This happens whenever I try to edit a file (for example 
/etc/apt/sources.list) or open gedit with root privileges. Application window 
opens, characters are replaced by squares, and becomes impossible to drag or 
resize it as my system completely stalls. Also if firefox is open, it also 
becomes unresponsive and crashes. 
  This screenshot summarises what i have been experiencing so far: 
https://i.imgur.com/8R6vZhE.jpg
  Additionally, it also happens with nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 19:34:14 2019
  InstallationDate: Installed on 2016-11-14 (1048 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (403 days ago)

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

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

[Desktop-packages] [Bug 1845892] [NEW] gedit crashes system when launched from terminal as root

[Guilherme]

Public bug reported:

This happens whenever I try to edit a file (for example /etc/apt/sources.list) 
or open gedit with root privileges. Application window opens, characters are 
replaced by squares, and becomes impossible to drag or resize it as my system 
completely stalls. Also if firefox is open, it also becomes unresponsive and 
crashes. 
This screenshot summarises what i have been experiencing so far: 
https://i.imgur.com/8R6vZhE.jpg
Additionally, it also happens with nautilus.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gedit 3.28.1-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
Uname: Linux 4.15.0-65-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 29 19:34:14 2019
InstallationDate: Installed on 2016-11-14 (1048 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gedit
UpgradeStatus: Upgraded to bionic on 2018-08-21 (403 days ago)

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


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

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

Title:
  gedit crashes system when launched from terminal as root

Status in gedit package in Ubuntu:
  New

Bug description:
  This happens whenever I try to edit a file (for example 
/etc/apt/sources.list) or open gedit with root privileges. Application window 
opens, characters are replaced by squares, and becomes impossible to drag or 
resize it as my system completely stalls. Also if firefox is open, it also 
becomes unresponsive and crashes. 
  This screenshot summarises what i have been experiencing so far: 
https://i.imgur.com/8R6vZhE.jpg
  Additionally, it also happens with nautilus.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 19:34:14 2019
  InstallationDate: Installed on 2016-11-14 (1048 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gedit
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (403 days ago)

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

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

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

[Christophe Lyon]

Like others reported here, I observe the same problem (slowness) with my
Samsung Galaxy A5 and ubuntu-18.04.

I tried Android File Transfer as suggested in comment #10, and it's indeed way 
faster. That being said, I had to switch my phone to using the "Image transfer 
protocol" (MTP (or PTP?), not sure what's the actual name in english), and it 
seems this also sped up access via Thunar.
Switching back to "File transfer protocol", the access is again very slow under 
Thunar.

As other complained, this was reported 1 year ago, and apparently no
progress? (No even a "OK I could reproduce the problem...)

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

Title:
  MTP not working/very slow on Bionic

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

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

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

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

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

  That's all!

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

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

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

Re: [Desktop-packages] [Bug 1514474] Re: package tex-common 6.04... Safe legit patch?

[jonny]

Hey thanks so much for your rapid response. Just the response makes me
feel better.

Hmm but that is strange about your acct on 16.x being used with Google
when you been using 18.x. That is strange. I hope no one injected
anything malicious somehow. I don't see how an email from Google would
imply that, but heck what if someone cloned an old machine or logged in
as you from an Ubuntu 16.x machine.

Idk. Anyway you have a great day thanks again so much for the reply and
not getting angry with me. Nothing is safe these days so I hope I can be
viewed as being vigilant, opposed to just annoying lol.

See ya later!!

Sent via 

> On Sep 29, 2019, at 11:10 AM, enrico de bernart  
> wrote:
> 
> Frankly long time passed and the only thing I can suppose that upgrading to
> 18.04 my account expired, hope this helps.
> 
> Pls note also that just couple of days ago I received a mail from Google
> about the use of my account 65 days ago on Ubuntu 16 but is long time all
> my computers are on 18 (I revoked access from that machine).
> 
> Regards
> Enrico
> 
> 
> Il dom 29 set 2019, 17:54 jonny  ha scritto:
> 
>> Im greatful for the fix, so thank you.
>> 
>>  I'm just curious, I seen you have a new acct at launchpad. Like just
>> today your acct was created, with what looks like the sole purpose to
>> push this patch. I don't mean to be accusatory and I certainly don't
>> know how to read source code, but I've read stories of malicious patches
>> getting pushed thru under the radar, so I'm hoping you can just explain
>> why this acct was created today, same day to push the patch. I'm sure
>> I'm being paranoid so im sorry. Surely theres a perfectly good
>> explanation for all this.
>> 
>> Thanks for your time and info. Thank you so much for helping the Linux
>> community.
>> 
>> Sent via 
>> 
>>> On Sep 28, 2019, at 9:39 PM, ashley lakin <1514...@bugs.launchpad.net>
>> wrote:
>>> 
>>> ** Changed in: tex-common (Ubuntu)
>>>  Status: Confirmed => Fix Released
>>> 
>>> --
>>> You received this bug notification because you are subscribed to a
>>> duplicate bug report (1734294).
>>> https://bugs.launchpad.net/bugs/1514474
>>> 
>>> Title:
>>> package tex-common 6.04 failed to install/upgrade: subprocess
>>> installed post-installation script returned error exit status 1
>>> 
>>> Status in tex-common package in Ubuntu:
>>> Fix Released
>>> 
>>> Bug description:
>>> dist-upgrade from wily to xenial
>>> 
>>> ProblemType: Package
>>> DistroRelease: Ubuntu 16.04
>>> Package: tex-common 6.04
>>> ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
>>> Uname: Linux 4.2.0-16-generic x86_64
>>> NonfreeKernelModules: nvidia
>>> ApportVersion: 2.19.2-0ubuntu4
>>> Architecture: amd64
>>> Date: Mon Nov  9 09:56:09 2015
>>> ErrorMessage: subprocess installed post-installation script returned
>> error exit status 1
>>> InstallationDate: Installed on 2011-07-12 (1580 days ago)
>>> InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64
>> (20110705.1)
>>> PackageArchitecture: all
>>> RelatedPackageVersions:
>>>  dpkg 1.18.3ubuntu1
>>>  apt  1.0.10.2ubuntu1
>>> SourcePackage: tex-common
>>> Title: package tex-common 6.04 failed to install/upgrade: subprocess
>> installed post-installation script returned error exit status 1
>>> UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)
>>> 
>>> To manage notifications about this bug go to:
>>> 
>> https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+subscriptions
>> 
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1629599).
>> https://bugs.launchpad.net/bugs/1514474
>> 
>> Title:
>>  package tex-common 6.04 failed to install/upgrade: subprocess
>>  installed post-installation script returned error exit status 1
>> 
>> Status in tex-common package in Ubuntu:
>>  Fix Released
>> 
>> Bug description:
>>  dist-upgrade from wily to xenial
>> 
>>  ProblemType: Package
>>  DistroRelease: Ubuntu 16.04
>>  Package: tex-common 6.04
>>  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
>>  Uname: Linux 4.2.0-16-generic x86_64
>>  NonfreeKernelModules: nvidia
>>  ApportVersion: 2.19.2-0ubuntu4
>>  Architecture: amd64
>>  Date: Mon Nov  9 09:56:09 2015
>>  ErrorMessage: subprocess installed post-installation script returned
>> error exit status 1
>>  InstallationDate: Installed on 2011-07-12 (1580 days ago)
>>  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64
>> (20110705.1)
>>  PackageArchitecture: all
>>  RelatedPackageVersions:
>>   dpkg 1.18.3ubuntu1
>>   apt  1.0.10.2ubuntu1
>>  SourcePackage: tex-common
>>  Title: package tex-common 6.04 failed to install/upgrade: subprocess
>> installed post-installation script returned error exit status 1
>>  UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)
>> 
>> To manage notifications about this bug go to:
>> 
>> https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+subscriptions
>> 
> 
> -- 
> You received this bug notification 

[Desktop-packages] [Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account

[Matheus Reich]

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

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

Title:
  Not able to log in into Google Account, aswell as Microsoft account

Status in gnome-initial-setup package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid

Bug description:
  After the first boot up of Ubuntu 18.10, it invites me to log-in into
  several accounts, including Google and Microsoft accounts. After I
  log-in into Ubuntu One, my next step is to log in my Google Account,
  but the log-in page never loads, and when it does (after a couple of
  minutes), and I insert my log in credentials, it fails the log-in
  process, all of this happens with the Microsoft account too. The
  Ubuntu One account logs-in without a hitch, but the rest does not.

  1) Description:   Ubuntu 18.10
  Release:  18.10

  2) gnome-initial-setup:
Instalado: 3.30.0-1ubuntu3
Candidato: 3.30.0-1ubuntu3.1
Tabela de versão:
   3.30.0-1ubuntu3.1 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
   *** 3.30.0-1ubuntu3 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-initial-setup 3.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 11:12:31 2018
  ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup
  InstallationDate: Installed on 2018-11-27 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1802982] Re: GNOME Software keeps logging out of the Ubuntu One account

[Matheus Reich]

This still affects Ubuntu 19.04 and 19.10.

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

Title:
  GNOME Software keeps logging out of the Ubuntu One account

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Every time I restart the system, my Ubuntu One account that is was
  connected to ubuntu Software keeps disconnected. This doesn't happen
  with the Snap account, only with the Ubuntu One account.

  Description:  Ubuntu 18.10
  Release:  18.10

  gnome-software:
Instalado: 3.30.2-0ubuntu8
Candidato: 3.30.2-0ubuntu8
Tabela de versão:
   *** 3.30.2-0ubuntu8 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.30.2-0ubuntu5 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages

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

-- 
Mailing list: https://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 1514474] Re: package tex-common 6.04... Safe legit patch?

[enrico de bernart]

Frankly long time passed and the only thing I can suppose that upgrading to
18.04 my account expired, hope this helps.

Pls note also that just couple of days ago I received a mail from Google
about the use of my account 65 days ago on Ubuntu 16 but is long time all
my computers are on 18 (I revoked access from that machine).

Regards
Enrico


Il dom 29 set 2019, 17:54 jonny  ha scritto:

> Im greatful for the fix, so thank you.
>
>   I'm just curious, I seen you have a new acct at launchpad. Like just
> today your acct was created, with what looks like the sole purpose to
> push this patch. I don't mean to be accusatory and I certainly don't
> know how to read source code, but I've read stories of malicious patches
> getting pushed thru under the radar, so I'm hoping you can just explain
> why this acct was created today, same day to push the patch. I'm sure
> I'm being paranoid so im sorry. Surely theres a perfectly good
> explanation for all this.
>
> Thanks for your time and info. Thank you so much for helping the Linux
> community.
>
> Sent via 
>
> > On Sep 28, 2019, at 9:39 PM, ashley lakin <1514...@bugs.launchpad.net>
> wrote:
> >
> > ** Changed in: tex-common (Ubuntu)
> >   Status: Confirmed => Fix Released
> >
> > --
> > You received this bug notification because you are subscribed to a
> > duplicate bug report (1734294).
> > https://bugs.launchpad.net/bugs/1514474
> >
> > Title:
> >  package tex-common 6.04 failed to install/upgrade: subprocess
> >  installed post-installation script returned error exit status 1
> >
> > Status in tex-common package in Ubuntu:
> >  Fix Released
> >
> > Bug description:
> >  dist-upgrade from wily to xenial
> >
> >  ProblemType: Package
> >  DistroRelease: Ubuntu 16.04
> >  Package: tex-common 6.04
> >  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
> >  Uname: Linux 4.2.0-16-generic x86_64
> >  NonfreeKernelModules: nvidia
> >  ApportVersion: 2.19.2-0ubuntu4
> >  Architecture: amd64
> >  Date: Mon Nov  9 09:56:09 2015
> >  ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
> >  InstallationDate: Installed on 2011-07-12 (1580 days ago)
> >  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64
> (20110705.1)
> >  PackageArchitecture: all
> >  RelatedPackageVersions:
> >   dpkg 1.18.3ubuntu1
> >   apt  1.0.10.2ubuntu1
> >  SourcePackage: tex-common
> >  Title: package tex-common 6.04 failed to install/upgrade: subprocess
> installed post-installation script returned error exit status 1
> >  UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)
> >
> > To manage notifications about this bug go to:
> >
> https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+subscriptions
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1629599).
> https://bugs.launchpad.net/bugs/1514474
>
> Title:
>   package tex-common 6.04 failed to install/upgrade: subprocess
>   installed post-installation script returned error exit status 1
>
> Status in tex-common package in Ubuntu:
>   Fix Released
>
> Bug description:
>   dist-upgrade from wily to xenial
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: tex-common 6.04
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
>   Uname: Linux 4.2.0-16-generic x86_64
>   NonfreeKernelModules: nvidia
>   ApportVersion: 2.19.2-0ubuntu4
>   Architecture: amd64
>   Date: Mon Nov  9 09:56:09 2015
>   ErrorMessage: subprocess installed post-installation script returned
> error exit status 1
>   InstallationDate: Installed on 2011-07-12 (1580 days ago)
>   InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64
> (20110705.1)
>   PackageArchitecture: all
>   RelatedPackageVersions:
>dpkg 1.18.3ubuntu1
>apt  1.0.10.2ubuntu1
>   SourcePackage: tex-common
>   Title: package tex-common 6.04 failed to install/upgrade: subprocess
> installed post-installation script returned error exit status 1
>   UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+subscriptions
>

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  Fix Released

Bug description:
  dist-upgrade from wily to xenial

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu4
  Architecture: amd64
  Date: Mon Nov  9 09:56:09 2015
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 

[Desktop-packages] [Bug 1845859] [NEW] Control Center not returning to the previous menu as it should

[Matheus Reich]

Public bug reported:

When I'm inside the Devices menu, and I enter the "Keyboard Shortcuts"
submenu, there is a problem when I want to return to the previous menu,
which in this case is the Devices menu. When I press the return button,
the left column with the submenus list that is inside Devices takes the
whole screen of the program, instead of presenting the left column on
it's standard size. I don't know if this is a glitch/bug or if it is
intended, but I do find it to be very weird looking. It would be nice if
this was fixed before the release of Ubuntu 19.10.

Steps to reproduce it:
1 - Enter GCC
2 - Go to Devices
3 - Enter Keyboard Shortcuts
4 - Return to the previous menu using the Return Arrow button at the top left 
part of the window

What is expected:
It should return to the previous menu inside Devices that you were before 
entering the Keyboard Shortcuts submenu.

What happens:
It returns to a blank screen that is only presenting the submenus inside 
Devices, without returning to the previous submenu that you were (screenshot 
has been added presenting what the issue looks like).

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
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 29 12:55:25 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-09-29 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
ProcEnviron:
 LANG=pt_BR.UTF-8
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "This screenshot presents the screen after pressing the 
return button inside the Keyboard Shortcuts submenu."
   
https://bugs.launchpad.net/bugs/1845859/+attachment/5292585/+files/Captura%20de%20tela%20de%202019-09-29%2013-02-45.png

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

Title:
  Control Center not returning to the previous menu as it should

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

Bug description:
  When I'm inside the Devices menu, and I enter the "Keyboard Shortcuts"
  submenu, there is a problem when I want to return to the previous
  menu, which in this case is the Devices menu. When I press the return
  button, the left column with the submenus list that is inside Devices
  takes the whole screen of the program, instead of presenting the left
  column on it's standard size. I don't know if this is a glitch/bug or
  if it is intended, but I do find it to be very weird looking. It would
  be nice if this was fixed before the release of Ubuntu 19.10.

  Steps to reproduce it:
  1 - Enter GCC
  2 - Go to Devices
  3 - Enter Keyboard Shortcuts
  4 - Return to the previous menu using the Return Arrow button at the top left 
part of the window

  What is expected:
  It should return to the previous menu inside Devices that you were before 
entering the Keyboard Shortcuts submenu.

  What happens:
  It returns to a blank screen that is only presenting the submenus inside 
Devices, without returning to the previous submenu that you were (screenshot 
has been added presenting what the issue looks like).

  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
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 12:55:25 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-09-29 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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/1845859/+subscriptions

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

[Desktop-packages] [Bug 1845859] Re: Control Center not returning to the previous menu as it should

[Matheus Reich]

It is worth noting that I am running the Ubuntu 19.10 Beta inside a
VMWare session.

** Description changed:

  When I'm inside the Devices menu, and I enter the "Keyboard Shortcuts"
  submenu, there is a problem when I want to return to the previous menu,
  which in this case is the Devices menu. When I press the return button,
  the left column with the submenus list that is inside Devices takes the
  whole screen of the program, instead of presenting the left column on
  it's standard size. I don't know if this is a glitch/bug or if it is
  intended, but I do find it to be very weird looking. It would be nice if
  this was fixed before the release of Ubuntu 19.10.
+ 
+ Steps to reproduce it:
+ 1 - Enter GCC
+ 2 - Go to Devices
+ 3 - Enter Keyboard Shortcuts
+ 4 - Return to the previous menu using the Return Arrow button at the top left 
part of the window
+ 
+ What is expected:
+ It should return to the previous menu inside Devices that you were before 
entering the Keyboard Shortcuts submenu.
+ 
+ What happens:
+ It returns to a blank screen that it only presenting the submenus inside 
Devices, without returning to the previous submenu that you were (screenshot 
has been added presenting what the issue looks like).
  
  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
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 12:55:25 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-09-29 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  ProcEnviron:
-  LANG=pt_BR.UTF-8
-  LANGUAGE=pt_BR:pt:en
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=pt_BR.UTF-8
+  LANGUAGE=pt_BR:pt:en
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  When I'm inside the Devices menu, and I enter the "Keyboard Shortcuts"
  submenu, there is a problem when I want to return to the previous menu,
  which in this case is the Devices menu. When I press the return button,
  the left column with the submenus list that is inside Devices takes the
  whole screen of the program, instead of presenting the left column on
  it's standard size. I don't know if this is a glitch/bug or if it is
  intended, but I do find it to be very weird looking. It would be nice if
  this was fixed before the release of Ubuntu 19.10.
  
  Steps to reproduce it:
  1 - Enter GCC
  2 - Go to Devices
  3 - Enter Keyboard Shortcuts
  4 - Return to the previous menu using the Return Arrow button at the top left 
part of the window
  
  What is expected:
  It should return to the previous menu inside Devices that you were before 
entering the Keyboard Shortcuts submenu.
  
  What happens:
- It returns to a blank screen that it only presenting the submenus inside 
Devices, without returning to the previous submenu that you were (screenshot 
has been added presenting what the issue looks like).
+ It returns to a blank screen that is only presenting the submenus inside 
Devices, without returning to the previous submenu that you were (screenshot 
has been added presenting what the issue looks like).
  
  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
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 12:55:25 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-09-29 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  ProcEnviron:
   LANG=pt_BR.UTF-8
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Control Center not returning to the previous menu as it should

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

Bug description:
  When I'm inside the Devices menu, and I enter the "Keyboard Shortcuts"
  submenu, there is a problem when I want to return to the previous
  menu, which in this case is the Devices menu. When I press the return
  button, the left column with the submenus list that is inside Devices
  takes the whole screen of the program, instead of presenting the left
  column on it's standard size. I don't know if this is a glitch/bug or
  if it is intended, but I do find it to be very weird looking. It would
  be 

Re: [Desktop-packages] [Bug 1514474] Re: package tex-common 6.04... Safe legit patch?

[jonny]

Im greatful for the fix, so thank you.

  I'm just curious, I seen you have a new acct at launchpad. Like just
today your acct was created, with what looks like the sole purpose to
push this patch. I don't mean to be accusatory and I certainly don't
know how to read source code, but I've read stories of malicious patches
getting pushed thru under the radar, so I'm hoping you can just explain
why this acct was created today, same day to push the patch. I'm sure
I'm being paranoid so im sorry. Surely theres a perfectly good
explanation for all this.

Thanks for your time and info. Thank you so much for helping the Linux
community.

Sent via 

> On Sep 28, 2019, at 9:39 PM, ashley lakin <1514...@bugs.launchpad.net> wrote:
> 
> ** Changed in: tex-common (Ubuntu)
>   Status: Confirmed => Fix Released
> 
> -- 
> You received this bug notification because you are subscribed to a
> duplicate bug report (1734294).
> https://bugs.launchpad.net/bugs/1514474
> 
> Title:
>  package tex-common 6.04 failed to install/upgrade: subprocess
>  installed post-installation script returned error exit status 1
> 
> Status in tex-common package in Ubuntu:
>  Fix Released
> 
> Bug description:
>  dist-upgrade from wily to xenial
> 
>  ProblemType: Package
>  DistroRelease: Ubuntu 16.04
>  Package: tex-common 6.04
>  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
>  Uname: Linux 4.2.0-16-generic x86_64
>  NonfreeKernelModules: nvidia
>  ApportVersion: 2.19.2-0ubuntu4
>  Architecture: amd64
>  Date: Mon Nov  9 09:56:09 2015
>  ErrorMessage: subprocess installed post-installation script returned error 
> exit status 1
>  InstallationDate: Installed on 2011-07-12 (1580 days ago)
>  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
>  PackageArchitecture: all
>  RelatedPackageVersions:
>   dpkg 1.18.3ubuntu1
>   apt  1.0.10.2ubuntu1
>  SourcePackage: tex-common
>  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
> installed post-installation script returned error exit status 1
>  UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+subscriptions

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  Fix Released

Bug description:
  dist-upgrade from wily to xenial

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu4
  Architecture: amd64
  Date: Mon Nov  9 09:56:09 2015
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-07-12 (1580 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago)

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

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

[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen

[Jarno Suni]

Oh, I found alternative way that works for GRUB menu resolution and
console resolution, too, and no need to create /etc/X11/xorg.conf.

Edit /etc/default/grub accordingly: 
GRUB_GFXMODE=1280x1024,auto
GRUB_GFXPAYLOAD_LINUX=keep,text

You may want to or have to use a different resolution than 1280x1024.

Thereafter "sudo update-grub" and reboot.

Reference: 
https://linuxconfig.org/how-to-increase-tty-console-resolution-on-ubuntu-18-04-server
https://www.gnu.org/software/grub/manual/grub/html_node/Simple-configuration.html

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

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support

[Jamie Strandboge]

** Description changed:

  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.
  
  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all connected
  clients (snaps or not), record by classic snaps (see bug 1787324) and
  record by strict mode snaps if either the pulseaudio or new-in-
  snapd-2.41 audio-record interfaces were connected. With this change,
  snapd is in a position to migrate snaps to the new audio-playback and
  audio-record interfaces and properly mediate audio recording (see
  https://forum.snapcraft.io/t/upcoming-pulseaudio-interface-
  deprecation/13418).
  
  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not, whether
  the pulseaudio or audio-record interfaces are connected. Adjusting
  pulseaudio in the manner does not require coordination with any release
  of snapd. It does need a newer version of snapd-glib, which was recently
  updated to 1.49 in the last SRU.
  
  [Test Case]
  
- Since the pulseaudio mediation behavior triggers when the security label
- starts with 'snap.' it is su
+ IMPORTANT: if updating pulseaudio while the session is running, either
+ need to reboot for the test or kill pulseaudio so it can restart with
+ the new snap policy
  
  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes
  
  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes
  
  $ paplay /tmp/out.wav && echo "yes"
  yes
  
  For confined, non-snap applications:
  $ sudo apt-get install evince
  
  $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav
  && echo yes
  
  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes
  
  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes
  
  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic
  
  $ snap run --shell test-snapd-classic-confinement
  
  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)
  
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes
  
  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes
  
  $ paplay /tmp/out.wav && echo "yes"
  yes
  
  For strict snaps with pulseaudio:
  $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap
  
  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -
  
  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...
  
  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/
  
  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes
  
  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)
  
  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes
  
  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes
  
  For strict snaps with audio-playback/audio-record:
  $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04
  $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap
  
  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
  audio-recordtest-snapd-audio-record:audio-record--
  
  $ test-snapd-audio-record.play --help  # ensure SNAP dirs are created
  ...
  
  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-audio-
  record/common/
  
  $ test-snapd-audio-record.play 
/var/snap/test-snapd-audio-record/common/Noise.wav && echo yes
  

[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support

[Jamie Strandboge]

** Description changed:

  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.
  
  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all connected
  clients (snaps or not), record by classic snaps (see bug 1787324) and
  record by strict mode snaps if either the pulseaudio or new-in-
  snapd-2.41 audio-record interfaces were connected. With this change,
  snapd is in a position to migrate snaps to the new audio-playback and
  audio-record interfaces and properly mediate audio recording (see
  https://forum.snapcraft.io/t/upcoming-pulseaudio-interface-
  deprecation/13418).
  
  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not, whether
  the pulseaudio or audio-record interfaces are connected. Adjusting
  pulseaudio in the manner does not require coordination with any release
  of snapd. It does need a newer version of snapd-glib, which was recently
  updated to 1.49 in the last SRU.
  
  [Test Case]
  
  Since the pulseaudio mediation behavior triggers when the security label
  starts with 'snap.' it is su
  
  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes
  
  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes
  
  $ paplay /tmp/out.wav && echo "yes"
  yes
  
  For confined, non-snap applications:
  $ sudo apt-get install evince
  
  $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav
  && echo yes
  
  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes
  
  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes
  
- 
  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic
  
  $ snap run --shell test-snapd-classic-confinement
  
  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)
  
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes
  
  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes
  
  $ paplay /tmp/out.wav && echo "yes"
  yes
  
  For strict snaps with pulseaudio:
  $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap
  
  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -
  
  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...
  
  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/
  
  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes
  
  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)
  
  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes
  
  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes
  
- 
  For strict snaps with audio-playback/audio-record:
+ $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04
  $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap
  
  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
  audio-recordtest-snapd-audio-record:audio-record--
  
  $ test-snapd-audio-record.play --help  # ensure SNAP dirs are created
  ...
  
  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-audio-
  record/common/
  
  $ test-snapd-audio-record.play 
/var/snap/test-snapd-audio-record/common/Noise.wav && echo yes
  xcb_connection_has_error() returned true
  yes
  
  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to 

[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support

[Jamie Strandboge]

Attaching test-snapd-pulseaudio and test-snapd-audio-record snaps.

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

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  Since the pulseaudio mediation behavior triggers when the security
  label starts with 'snap.' it is su

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  
  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For strict snaps with pulseaudio:
  $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes

  
  For strict snaps with audio-playback/audio-record:
  $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap

  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
  audio-recordtest-snapd-audio-record:audio-record--

  $ test-snapd-audio-record.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav 

[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support

[Jamie Strandboge]

** Description changed:

+ [Impact]
+ Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.
  
- # Original summary: pulseaudio built with --enable-snappy but 'Enable
- Snappy support: no'
+ To correct this situation but not regress existing behavior, Ubuntu
+ 19.04's pulseaudio was updated patch to allow playback to all connected
+ clients (snaps or not), record by classic snaps (see bug 1787324) and
+ record by strict mode snaps if either the pulseaudio or new-in-
+ snapd-2.41 audio-record interfaces were connected. With this change,
+ snapd is in a position to migrate snaps to the new audio-playback and
+ audio-record interfaces and properly mediate audio recording (see
+ https://forum.snapcraft.io/t/upcoming-pulseaudio-interface-
+ deprecation/13418).
+ 
+ The patch to pulseaudio consists of adding a module, enabling it in
+ default.pa and then when it is enabled, pulseaudio when faced with a
+ record operation will, when the connecting process is a snap (ie, its
+ security label (ie, apparmor label) starts with 'snap.'), query snapd
+ via its control socket to ask if the snap is classic and if not, whether
+ the pulseaudio or audio-record interfaces are connected. Adjusting
+ pulseaudio in the manner does not require coordination with any release
+ of snapd. It does need a newer version of snapd-glib, which was recently
+ updated to 1.49 in the last SRU.
+ 
+ [Test Case]
+ 
+ Since the pulseaudio mediation behavior triggers when the security label
+ starts with 'snap.' it is su
+ 
+ For unconfined applications:
+ $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
+ yes
+ 
+ $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
+ ^Cyes
+ 
+ $ paplay /tmp/out.wav && echo "yes"
+ yes
+ 
+ For confined, non-snap applications:
+ $ sudo apt-get install evince
+ 
+ $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav
+ && echo yes
+ 
+ $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
+ ^Cyes
+ 
+ $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
+ yes
+ 
+ 
+ For classic snaps:
+ $ sudo snap install test-snapd-classic-confinement --classic
+ 
+ $ snap run --shell test-snapd-classic-confinement
+ 
+ $ cat /proc/self/attr/current   # verify we are classic confined
+ snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)
+ 
+ $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
+ yes
+ 
+ $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
+ ^Cyes
+ 
+ $ paplay /tmp/out.wav && echo "yes"
+ yes
+ 
+ For strict snaps with pulseaudio:
+ $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap
+ 
+ $ snap connections test-snapd-pulseaudio
+ Interface   Plug  Slot Notes
+ pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -
+ 
+ $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
+ ...
+ 
+ $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
+ pulseaudio/common/
+ 
+ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
+ xcb_connection_has_error() returned true
+ yes
+ 
+ (note, the xcb_connection_has_error() message is due to the x11
+ interface not being connecting which is unrelated to mediation. x11 is
+ left out to ensure that just audio-playback/audio-record are tested)
+ 
+ $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
+ ...
+ ^Cyes
+ 
+ $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
+ ...
+ yes
+ 
+ 
+ For strict snaps with audio-playback/audio-record:
+ $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap
+ 
+ $ snap connections test-snapd-audio-record  # record not connected
+ Interface   PlugSlot Notes
+ audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
+ audio-recordtest-snapd-audio-record:audio-record--
+ 
+ $ test-snapd-audio-record.play --help  # ensure SNAP dirs are created
+ ...
+ 
+ $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-audio-
+ record/common/
+ 
+ $ test-snapd-audio-record.play 
/var/snap/test-snapd-audio-record/common/Noise.wav && echo yes
+ xcb_connection_has_error() returned true
+ yes
+ 
+ (note, the xcb_connection_has_error() message is due to the x11
+ interface not being connecting which is 

[Desktop-packages] [Bug 1845847] [NEW] Programs don't scale properly on 1366x768 monitor. On a dual monitor setup, moving app from 1920x1080 monitor to 1366x768 monitor the left 2cm is missing because

[Bruce Arnold]

Public bug reported:

This is the Sept. 28 beta version of Ubuntu 19.10.
lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: firefox 69.0.1+build1-0ubuntu2
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
BuildID: 20190918155341
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 29 09:23:01 2019
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
DefaultProfileThemes: extensions.sqlite corrupt or missing
InstallationDate: Installed on 2019-09-28 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profiles:
 Profile1 (Default) - LastVersion=None/None (Out of date)
 Profile0 - LastVersion=69.0.1/20190918155341 (In use)
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Programs don't scale properly on 1366x768 monitor. On a dual monitor
  setup, moving app from 1920x1080 monitor to 1366x768 monitor the left
  2cm is missing because the window is too big.  Tested with firefox and
  also Rythmbox.

Status in firefox package in Ubuntu:
  New

Bug description:
  This is the Sept. 28 beta version of Ubuntu 19.10.
  lsb_release -rd
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: firefox 69.0.1+build1-0ubuntu2
  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
  BuildID: 20190918155341
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 09:23:01 2019
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:997
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  InstallationDate: Installed on 2019-09-28 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=69.0.1/20190918155341 (In use)
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support

[Jamie Strandboge]

** Attachment added: "test-snapd-audio-record_1_amd64.snap"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+attachment/5292539/+files/test-snapd-audio-record_1_amd64.snap

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

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  Since the pulseaudio mediation behavior triggers when the security
  label starts with 'snap.' it is su

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  
  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For strict snaps with pulseaudio:
  $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes

  
  For strict snaps with audio-playback/audio-record:
  $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap

  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
  audio-recordtest-snapd-audio-record:audio-record--

[Desktop-packages] [Bug 1781428] Re: pulseaudio built with --enable-snappy but 'Enable Snappy support: no'

[Jamie Strandboge]

** Description changed:

+ 
+ # Original summary: pulseaudio built with --enable-snappy but 'Enable
+ Snappy support: no'
+ 
+ # Original description
+ 
  From https://launchpadlibrarian.net/377100864/buildlog_ubuntu-cosmic-
  amd64.pulseaudio_1%3A12.0-1ubuntu1_BUILDING.txt.gz:
  
  ...
  dh_auto_configure -- --enable-x11 --disable-hal-compat 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--with-module-dir=\${prefix}/lib/pulse-12.0/modules 
--with-zsh-completion-dir=\${datadir}/zsh/vendor-completions 
--with-bash-completion-dir=\${datadir}/bash-completion/completions 
--with-systemduserunitdir=\${prefix}/lib/systemd/user --enable-snappy 
--disable-bluez4 --enable-gsettings --disable-gconf
   ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-x11 --disable-hal-compat 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--with-module-dir=\${prefix}/lib/pulse-12.0/modules 
--with-zsh-completion-dir=\${datadir}/zsh/vendor-completions 
--with-bash-completion-dir=\${datadir}/bash-completion/completions 
--with-systemduserunitdir=\${prefix}/lib/systemd/user --enable-snappy 
--disable-bluez4 --enable-gsettings --disable-gconf
  ...
  Enable Ubuntu trust store: no
  Enable Snappy support: no
  Enable Apparmor:   yes
  
- 
- At this point, the patch should probably be dropped, otherwise applications 
like chromium, etc will no longer be able to record.
+ At this point, the patch should probably be dropped, otherwise
+ applications like chromium, etc will no longer be able to record.

** Summary changed:

- pulseaudio built with --enable-snappy but 'Enable Snappy support: no'
+ please enable snap mediation support

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

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:

  # Original summary: pulseaudio built with --enable-snappy but 'Enable
  Snappy support: no'

  # Original description

  From https://launchpadlibrarian.net/377100864/buildlog_ubuntu-cosmic-
  amd64.pulseaudio_1%3A12.0-1ubuntu1_BUILDING.txt.gz:

  ...
  dh_auto_configure -- --enable-x11 --disable-hal-compat 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--with-module-dir=\${prefix}/lib/pulse-12.0/modules 
--with-zsh-completion-dir=\${datadir}/zsh/vendor-completions 
--with-bash-completion-dir=\${datadir}/bash-completion/completions 
--with-systemduserunitdir=\${prefix}/lib/systemd/user --enable-snappy 
--disable-bluez4 --enable-gsettings --disable-gconf
   ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-x11 --disable-hal-compat 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--with-module-dir=\${prefix}/lib/pulse-12.0/modules 
--with-zsh-completion-dir=\${datadir}/zsh/vendor-completions 
--with-bash-completion-dir=\${datadir}/bash-completion/completions 
--with-systemduserunitdir=\${prefix}/lib/systemd/user --enable-snappy 
--disable-bluez4 --enable-gsettings --disable-gconf
  ...
  Enable Ubuntu trust store: no
  Enable Snappy support: no
  Enable Apparmor:   yes

  At this point, the patch should probably be dropped, otherwise
  applications like chromium, etc will no longer be able to record.

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

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

[Desktop-packages] [Bug 1760068] Re: Wrong resolution at unlock screen

[Jarno Suni]

I used 
sudo nvidia-xconfig
to create initial /etc/X11/xorg.conf file like told in #18

Then added

Section "Files"
ModulePath "/usr/lib/nvidia-340/xorg"
ModulePath "/usr/lib/xorg/modules"
#   ModulePath "/usr/lib/x86_64-linux-gnu/xorg"
EndSection

in /etc/X11/xorg.conf
The last directory is empty, so I guess that is why it is ok to comment it out.
Works for the login screen, but other TTY:s have small resolution.

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

Title:
  Wrong resolution at unlock screen

Status in light-locker package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed

Bug description:
  After coming out of suspend - the unlock screen is at 640x480
  resolution.

  Expect to see unlock screen at 1920x1080 resolution.

  Using nvidia-340.

  Previously tested using nouveau driver where resolution at unlock
  screen was correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-locker 1.8.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 30 11:31:20 2018
  InstallationDate: Installed on 2017-09-02 (209 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  SourcePackage: light-locker
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1843627] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()

[Andreas Remchen]

The problem is with active calendar of my Google account. Everything
works very well with Nextcloud.

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

Title:
  evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Status in evolution-data-server:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/evolution/issues/616

  ---

  I don't know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 13:41:26 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2018-12-02 (282 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
   PC (0x7f36355653ae) ok
   source "(%r8)" (0x7f36) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2937
   __GI___libc_malloc (bytes=32) at malloc.c:3051
   g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1843627/+subscriptions

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

[Desktop-packages] [Bug 1734095]

[Andre Klapper]

Maciej: Is this still an issue? Or can this be closed as RESOLVED
OBSOLETE?

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

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

Bug description:
  After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software
  and Updates app and attempt to change anything it does not popup the
  authorization dialog and will not let changes through.  In sylog I see

  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 
3 identities that can be used for authentication. Only considering one.
  Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of 
begin_modal failed
  Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed 
to show modal dialog. Dismissing authentication request for action-id 
com.ubuntu.softwareproperties.applychanges cookie 
1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740
  Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: 
ERROR:root:Authentication canceled, changes have not been saved

  Before the upgrade it was ok.
  Other apps that require authorisation function as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Nov 23 10:07:44 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2014-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago)

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

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

[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

[Tim Richardson]

I haven't had this problem for several releases, so it is only triggered
under some circumstances. I suspected the hangouts extension (which I no
longer use)

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
    Installed: 3.18.1.2-1ubuntu1.16.04.1
    Candidate: 3.18.1.2-1ubuntu1.16.04.1
    Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.1.2-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I'm using gnome-session-flashback

  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs

  Expected:
  The screen should lock after the configured timeout in settings.

  I've been having this issue sice before 14.04, which I recently
  upgraded (fresh install) to 16.04.

  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the
  session with CTRL-ALT-L.

  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure

  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
  pretty sure that Chrome is doing something else of what i've found
  out.

  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a

  2) Gnome screen saver never receives the "session idle" status
  callback.

  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...

  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
     array [
    object path "/org/gnome/SessionManager/Inhibitor1686"
     ]
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId
  ('test',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason
  ('manual idle inhibit',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetFlags
  (uint32 12,)

  12=4(suspend) + 8(idle)

  5) When testing, I can inhibit for 70 seconds, idle timeout being 60
  (1 minute). After these 70 seconds pass, the screen locks.

  6) Regarding Chrome, this is the information I get when querying the 
inhibitor:
  GetAppId: ('/usr/bin/google-chrome-stable',)
  GetReason: ('Uploading data to 10.200.0.163',)
  GetFlags: (uint32 4,)

  The flags just inhibits suspend, not locking or entering powersaving
  mode.

  This inhibitor seems to stay for 10-15 seconds, then goes away for
  another 30-60 seconds. The screen NEVER locks when this tab is open.
  No matter the inhibitor is present or not.

  I'm not sure where to go on. If it's a Chrome bug it must be using
  other mechanisms to prevent the idle timeout. Any ideas on what to
  look for?

  Julian.

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

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

[Desktop-packages] [Bug 1845825] [NEW] i2c_designware and i2c_hid failures on shutdown

[Daniele Dellafiore]

Public bug reported:

1. Using Ubuntu 19.10
2. Shutdown system
3. System get stuck at the windows with this messages:

i2c_designware.o: controller timed out
i2c_hid: failed to change power settings.

It might not be related to the shutdown not happening, still that's the
only clue I have.

I attach the screenshot and dmesg output after the following boot.

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


** Tags: eoan

** Attachment added: "dmesg"
   https://bugs.launchpad.net/bugs/1845825/+attachment/5292444/+files/dmesg

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

Title:
  i2c_designware and i2c_hid failures on shutdown

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  1. Using Ubuntu 19.10
  2. Shutdown system
  3. System get stuck at the windows with this messages:

  i2c_designware.o: controller timed out
  i2c_hid: failed to change power settings.

  It might not be related to the shutdown not happening, still that's
  the only clue I have.

  I attach the screenshot and dmesg output after the following boot.

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

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

[Desktop-packages] [Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

[W-barath-hotmail]

This bug is 5 years old, and really, it should be a release-blocking
bug.

How much more severe can a bug be than causing physical damage,
bypassing security, corrupting the filesystem, and causing users to lose
work?

It's difficult to believe that Canonical has a competent release manager
if they're ignoring this for 5 years.

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy gnome-session-bin
  gnome-session-bin:
    Installed: 3.18.1.2-1ubuntu1.16.04.1
    Candidate: 3.18.1.2-1ubuntu1.16.04.1
    Version table:
   *** 3.18.1.2-1ubuntu1.16.04.1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.1.2-1ubuntu1 500
  500 http://es.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I'm using gnome-session-flashback

  What happens:
  The screen doesn't lock when having certain pages in Chrome tabs

  Expected:
  The screen should lock after the configured timeout in settings.

  I've been having this issue sice before 14.04, which I recently
  upgraded (fresh install) to 16.04.

  After fresh install, the screen would turn down and lock the computer
  after 10 minutes (or whatever time I setup). At one point it stopped
  working. The screen never shuts down unless I manually lock the
  session with CTRL-ALT-L.

  I've followed the steps in
  https://wiki.ubuntu.com/DebuggingScreenLocking#Debugging_procedure

  The culprit seems to be that Chrome issues some suspend inhibitions
  through dbus when doing certain operations. Many people find this
  problem when using Yahoo Mail. I can reproduce it with Odoo. I'm
  pretty sure that Chrome is doing something else of what i've found
  out.

  1) Gnome screen saver works correctly. I can trigger it manually with:
  $ gnome-screensaver-command -a

  2) Gnome screen saver never receives the "session idle" status
  callback.

  3) When Chrome is not running, I can manually inhibit the idle status:
  $ gnome-session-inhibit --app-id test --reason "manual idle inhibit" 
--inhibit-only --inhibit idle:suspend
  Inhibiting until Ctrl+C is pressed...

  4) I can query the inhibitors:
  $ dbus-send --print-reply --dest=org.gnome.SessionManager 
/org/gnome/SessionManager org.gnome.SessionManager.GetInhibitorsmethod return 
time=1468170482.066533 sender=:1.19 -> destination=:1.1315311 serial=1329103 
reply_serial=2
     array [
    object path "/org/gnome/SessionManager/Inhibitor1686"
     ]
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetAppId
  ('test',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetReason
  ('manual idle inhibit',)
  $ gdbus call --session --dest org.gnome.SessionManager --object-path 
/org/gnome/SessionManager/Inhibitor1686 --method 
org.gnome.SessionManager.Inhibitor.GetFlags
  (uint32 12,)

  12=4(suspend) + 8(idle)

  5) When testing, I can inhibit for 70 seconds, idle timeout being 60
  (1 minute). After these 70 seconds pass, the screen locks.

  6) Regarding Chrome, this is the information I get when querying the 
inhibitor:
  GetAppId: ('/usr/bin/google-chrome-stable',)
  GetReason: ('Uploading data to 10.200.0.163',)
  GetFlags: (uint32 4,)

  The flags just inhibits suspend, not locking or entering powersaving
  mode.

  This inhibitor seems to stay for 10-15 seconds, then goes away for
  another 30-60 seconds. The screen NEVER locks when this tab is open.
  No matter the inhibitor is present or not.

  I'm not sure where to go on. If it's a Chrome bug it must be using
  other mechanisms to prevent the idle timeout. Any ideas on what to
  look for?

  Julian.

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

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