[Desktop-packages] [Bug 1851202] [NEW] Need iw 5.3 in 18.04 Bionic

[Jerry Kao]

Public bug reported:

Current iw verion in Bionic is 4.14. Need iw 5.3 for better 802.11ax
High-Efficiency Wireless support.

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

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

Title:
  Need iw 5.3 in 18.04 Bionic

Status in iw package in Ubuntu:
  New

Bug description:
  Current iw verion in Bionic is 4.14. Need iw 5.3 for better 802.11ax
  High-Efficiency Wireless support.

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

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

[Desktop-packages] [Bug 1851189] Re: gnome-control-center can't configure second virtualbox display

[Sebastien Bacher]

Thank you for your bug report, could you also report it upstream on
https://gitlab.gnome.org/GNOME/gnome-control-center/issues ?

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

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

Title:
  gnome-control-center can't configure second virtualbox display

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

Bug description:
  On a VirtualBox 6.0.14 host, with a fresh install of Ubuntu 19.10 and
  the virtualbox guest drivers installed, I can't configure a second
  display, although xrandr shows it to be present.

  Steps:

  1. Install VirtualBox
  2. Install Ubuntu 19.10 as a guest with 2 displays (note: at least 2048 MB 
RAM is required or the guest is chronically slow during installation; I gave 
the displays 32 MB RAM as well).
  3. In the guest, install virtualbox guest drivers and reboot.
  4. Run g-c-c and go to the Devices / Displays section.

  Expected result:

  I can choose to Join the displays, move them around with the mouse and
  Apply the new settings successfuly.

  Actual result:

  Display 2 is shown normally but Display 1 is just a number (see
  attached) - I can't move it around or Apply changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Mon Nov  4 11:49:05 2019
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-04T11:48:33.047928

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

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

[Desktop-packages] [Bug 1851067] Re: Unnecessary Delays Recovering from Screen Lock

[Sebastien Bacher]

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

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

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

Title:
  Unnecessary Delays Recovering from Screen Lock

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

Bug description:
  You can turn "Sreen Lock" off using gnome-control-center > Privacy >
  Screen Lock : Off:

  https://gitlab.gnome.org/GNOME/gnome-control-
  center/uploads/62e176ed49faf1defaf6e4a36ad86f77/ScreenLock.png

  **Side-note:** this is bad terminology because your screen will still
  go into the exact same state that "Screen Lock: On" accomplishes (upon
  an inactivity timeout), but the only difference is that you won't have
  to enter your password to regain access to the desktop. I would have
  named this "Require Password Authentication After Inactivity Timeout"
  (to me wordy is better than unclear).

  While this accomplishes "not having to re-enter your password when
  coming back from an inactivity timeout", I'm very dissatisfied with a
  couple of things.

  1) After reaching an "inactivity timeout" that "locks" your screen,
  you cannot unlock your screen by simply moving your mouse; you have to
  press the "enter" key. I want to be able to accomplish this also by
  moving my mouse.

  2) Even if you press the enter key, to come out of "lock mode", it
  takes too long before you can interact with the applications you had
  open. I expect this to be instantaneous! If I were coming out of a
  suspended state, I could understand some delay. However, I'm not
  coming out of a suspended state, I just coming out of a screen lock.

  I do not like how this works. The whole purpose of this, as far as I'm
  concerned, is to increase the lifespan of my display monitors. All I
  want this to do, when a inactivity timeout occurs, is turn off all my
  monitor, and the only delay I expect, when coming back to my desktop,
  is what ever delay my monitor causes; the desktop should be fully
  available even before my monitor starts to display the desktop again.

  Having to press Enter and waiting 5 or 10 seconds before I can start
  working is NOT something that anyone wants.

  Also, there should be separate setting for "blank screen x time", and
  "monitor power off after x time".

  My ideal settings would to make the screen go black after 5 minutes of
  inactively and to turn my monitors completely off after 15 minutes of
  inactively, and I'd like to control whether each of these requires
  password authentication or not. On the 5 minute one, I personally
  would note require a password, but I would require a password after
  monitor going off. However, on either of these, I expect the desktop
  to be fully functional immediately after coming out of these states.
  At the very least please remove these unnecessary delays.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov  2 16:58:25 2019
  InstallationDate: Installed on 2019-10-30 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  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/gnome-control-center/+bug/1851067/+subscriptions

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

[Desktop-packages] [Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)

[Rocko]

@jagosta: does it only crash if the dialogs are on different monitors?
That's what I find.

FWIW, I tried the live USB, but ootb Ubuntu 19.10 doesn't recognise the
HDMI monitor, so I can't do dual displays, and I also tried a VirtualBox
guest, but even after installing Ubuntu 19.10 and guest drivers, Ubuntu
19.10 doesn't correctly recognise the second monitor, so I can't do dual
displays.

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

Title:
  gnome-shell crashed with SIGABRT:
  mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion
  failed: (workspace == NULL)

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b

  gnome-shell crashes with this bug every time that:

  * I am editing a file in geany
  * I open the Find window (CTRL-F) and it opens on another monitor
  * I type in some text in the find window and press ENTER (or click the Next 
button)

  Note especially that the find window must be on the other monitor - if
  it's on the same monitor as geany, gnome-shell doesn't crash.

  (Note: I originally thought that if I moved the find window to the
  other window and then searched, gnome-shell crashed, but I think what
  happens is a) I open the window, b) I move it, search for something,
  and it works, c) I close it and re-open it - it then opens on the
  other monitor and searching will crash gnome-shell.)

  gnome-shell restarts, but the crash causes data loss, as most of the
  running applications don't reappear when it restarts.

  In case it's relevant, I have a laptop screen set at 2048x1152 and an
  external monitor configured to be above it at 2560x1440.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  Uname: Linux 5.4.0-050400rc4-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 10:37:36 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1570619894
  InstallationDate: Installed on 2019-07-01 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/rocko
  ProcEnviron:
   LANG=en_AU.UTF-8
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Signal: 6
  SourcePackage: gnome-shell
  StacktraceTop:
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
   () at /lib/x86_64-linux-gnu/libmutter-5.so.0
  Title: gnome-shell crashed with SIGABRT
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  separator:

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

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

[Desktop-packages] [Bug 1841296] Re: Update to 2.4.3

[Sebastien Bacher]

https://launchpad.net/ubuntu/+source/libshout/2.4.3-1

** Changed in: libshout (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Update to 2.4.3

Status in libshout package in Ubuntu:
  Fix Released
Status in libshout package in Debian:
  Fix Released

Bug description:
  The new version includes new features

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

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

[Desktop-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]

[Timo Aaltonen]

** Also affects: backport-iwlwifi-dkms (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: virtualbox (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

** Also affects: xtables-addons (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: gcc-9 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: nvidia-graphics-drivers-430 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: backport-iwlwifi-dkms (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: backport-iwlwifi-dkms (Ubuntu)
   Status: New => Fix Released

** Changed in: gcc-9 (Ubuntu Eoan)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Eoan)
   Status: New => Fix Released

** Changed in: nvidia-graphics-drivers-430 (Ubuntu Eoan)
   Status: New => Fix Released

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

** Changed in: xtables-addons (Ubuntu Eoan)
   Status: New => Won't Fix

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

Title:
  Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-
  branch’ and ‘-fcf-protection’ are not compatible]

Status in backport-iwlwifi-dkms package in Ubuntu:
  Fix Released
Status in gcc-9 package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Won't Fix
Status in xtables-addons package in Ubuntu:
  Won't Fix
Status in backport-iwlwifi-dkms source package in Eoan:
  New
Status in gcc-9 source package in Eoan:
  Won't Fix
Status in linux source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-430 source package in Eoan:
  Fix Released
Status in virtualbox source package in Eoan:
  Won't Fix
Status in xtables-addons source package in Eoan:
  Won't Fix

Bug description:
  Compiling kernels & kernel modules fails due to these errors:

  ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and
  ‘-fcf-protection’ are not compatible

  (This happens with any kernel modules.)

  This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf-
  protection by default on 19.10's gcc-9.

  Switching to gcc-8 allows compilation to proceed.

  WORKAROUND:

  sudo ln -fs gcc-8 /usr/bin/gcc

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1830961/+subscriptions

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

[Desktop-packages] [Bug 1828313] Re: wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to 19.04.

[Launchpad Bug Tracker]

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

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

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

Title:
  wifi cannot connect to openwrt hidden ssid after upgrade from 18.10 to
  19.04.

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  pls see my post here

  https://answers.launchpad.net/ubuntu/+question/680506

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

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

[Desktop-packages] [Bug 1842614] Re: second screen blinks

[Launchpad Bug Tracker]

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

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

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

Title:
  second screen blinks

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

Bug description:
  I have 2 screens,
  the second attached using DVI-D port 
  after installing an update  few days ago, the screen blinking alot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-60.67-generic 4.15.18
  Uname: Linux 4.15.0-60-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  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: Wed Sep  4 09:54:52 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:198e]
  InstallationDate: Installed on 2018-06-21 (439 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP ProDesk 400 G2 MT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-60-generic 
root=UUID=714f8ea4-960d-4217-830f-ce8729640270 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L02 v02.39
  dmi.board.asset.tag: SGH516TY7Q
  dmi.board.name: 198E
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: SGH516TY7Q
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL02v02.39:bd12/11/2014:svnHewlett-Packard:pnHPProDesk400G2MT:pvr:rvnHewlett-Packard:rn198E:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP ProDesk 400 G2 MT
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1842614] Re: second screen blinks

[Launchpad Bug Tracker]

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

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

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

Title:
  second screen blinks

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

Bug description:
  I have 2 screens,
  the second attached using DVI-D port 
  after installing an update  few days ago, the screen blinking alot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-60.67-generic 4.15.18
  Uname: Linux 4.15.0-60-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  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: Wed Sep  4 09:54:52 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [103c:198e]
  InstallationDate: Installed on 2018-06-21 (439 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP ProDesk 400 G2 MT
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-60-generic 
root=UUID=714f8ea4-960d-4217-830f-ce8729640270 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L02 v02.39
  dmi.board.asset.tag: SGH516TY7Q
  dmi.board.name: 198E
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: SGH516TY7Q
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL02v02.39:bd12/11/2014:svnHewlett-Packard:pnHPProDesk400G2MT:pvr:rvnHewlett-Packard:rn198E:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP ProDesk 400 G2 MT
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Desktop-packages] [Bug 1851189] Re: gnome-control-center can't configure second virtualbox display

[Rocko]

Here's the xrandr. It looks like 0x0 is selected for display Virtual2
and maybe this is confusing g-c-c.

** Attachment added: "xrandr"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1851189/+attachment/5302626/+files/xrandr

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

Title:
  gnome-control-center can't configure second virtualbox display

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

Bug description:
  On a VirtualBox 6.0.14 host, with a fresh install of Ubuntu 19.10 and
  the virtualbox guest drivers installed, I can't configure a second
  display, although xrandr shows it to be present.

  Steps:

  1. Install VirtualBox
  2. Install Ubuntu 19.10 as a guest with 2 displays (note: at least 2048 MB 
RAM is required or the guest is chronically slow during installation; I gave 
the displays 32 MB RAM as well).
  3. In the guest, install virtualbox guest drivers and reboot.
  4. Run g-c-c and go to the Devices / Displays section.

  Expected result:

  I can choose to Join the displays, move them around with the mouse and
  Apply the new settings successfuly.

  Actual result:

  Display 2 is shown normally but Display 1 is just a number (see
  attached) - I can't move it around or Apply changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Mon Nov  4 11:49:05 2019
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-04T11:48:33.047928

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

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

[Desktop-packages] [Bug 1851189] [NEW] gnome-control-center can't configure second virtualbox display

[Rocko]

Public bug reported:

On a VirtualBox 6.0.14 host, with a fresh install of Ubuntu 19.10 and
the virtualbox guest drivers installed, I can't configure a second
display, although xrandr shows it to be present.

Steps:

1. Install VirtualBox
2. Install Ubuntu 19.10 as a guest with 2 displays (note: at least 2048 MB RAM 
is required or the guest is chronically slow during installation; I gave the 
displays 32 MB RAM as well).
3. In the guest, install virtualbox guest drivers and reboot.
4. Run g-c-c and go to the Devices / Displays section.

Expected result:

I can choose to Join the displays, move them around with the mouse and
Apply the new settings successfuly.

Actual result:

Display 2 is shown normally but Display 1 is just a number (see
attached) - I can't move it around or Apply changes.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Mon Nov  4 11:49:05 2019
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-11-04T11:48:33.047928

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


** Tags: amd64 apport-bug eoan

** Attachment added: "g-c-c display settings"
   https://bugs.launchpad.net/bugs/1851189/+attachment/5302623/+files/g-c-c.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/1851189

Title:
  gnome-control-center can't configure second virtualbox display

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

Bug description:
  On a VirtualBox 6.0.14 host, with a fresh install of Ubuntu 19.10 and
  the virtualbox guest drivers installed, I can't configure a second
  display, although xrandr shows it to be present.

  Steps:

  1. Install VirtualBox
  2. Install Ubuntu 19.10 as a guest with 2 displays (note: at least 2048 MB 
RAM is required or the guest is chronically slow during installation; I gave 
the displays 32 MB RAM as well).
  3. In the guest, install virtualbox guest drivers and reboot.
  4. Run g-c-c and go to the Devices / Displays section.

  Expected result:

  I can choose to Join the displays, move them around with the mouse and
  Apply the new settings successfuly.

  Actual result:

  Display 2 is shown normally but Display 1 is just a number (see
  attached) - I can't move it around or Apply changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Mon Nov  4 11:49:05 2019
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-04T11:48:33.047928

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

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

[Desktop-packages] [Bug 1850696] Re: Regression: cannot close notifications

[Bug Watch Updater]

** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  Regression: cannot close notifications

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Upstream reports:

  * https://gitlab.gnome.org/GNOME/gnome-shell/issues/1805
  * https://gitlab.gnome.org/GNOME/gnome-shell/issues/1803

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

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

[Desktop-packages] [Bug 1848119]

[gmarr]

Discussed during the 2019-10-21 blocker review meeting: [0]

The decision to classify this bug as a "RejectedFreezeException" was
made as we think it's too late to potentially introduce instability to
fix log spam.

[0] https://meetbot.fedoraproject.org/fedora-blocker-
review/2019-10-21/f31-blocker-review.2019-10-21-16.00.txt

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

Title:
  gnome-shell infinite error loop when closing app in activities
  overview: Object St.Button (0x55aeadeca4a0), has been already
  deallocated ... [workspace.js:695]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Won't Fix
Status in mutter source package in Eoan:
  Triaged
Status in gnome-shell source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  [ Impact ]

  Gnome shell fills the journal with errors as soon as a view is closed
  from the overview

  Ubuntu 19.10 on Xorg
  gnome-shell 3.34.1-1ubuntu1

  [ Test case ]

  1) Open terminal and watch journalct -f /usr/bin/gnome-shell
  2) Open a window (i.e Files)
  3) Close Files in the activities overview
  4) gnome-shell spanws errors in the journal.

  Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 
0x55aead0b5360 ==
  Oct 14 23:25:38 titan gnome-shell[9919]: #0   55aeae6f3910 i   
resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15)
  Oct 14 23:25:38 titan gnome-shell[9919]: #1   7ffd96c5e360 b   
self-hosted:975 (7f438c12dee0 @ 392)

  [ Regression potential ]

  Key focus might not work properly in some shell elements, in
  particular the focus be owned by multiple actors or by none of them.

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

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

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

[Gunnar Hjalmarsson]

Thanks Alex!

On 2019-11-04 02:55, Alex Murray wrote:
> Also I note the bug descriptions lists ibus in Focal as Fix Released
> - but the latest version in focal (1.5.21-1~exp2ubuntu2) is the one
> with the patch reverted

Yeah.. ibus without specified series was marked "Fix Released" when the
CVE patch was disabled, and when I targeted to series for glib2.0, it
happened for ibus too (I removed all series bug focal). So there is
really no message in it.

> would you like me to upload an updated focal version as well to the
> above PPA?

It's not needed for the SRU verification. Alternatively you could just
upload to focal as soon as glib2.0 2.62.2-2 makes it to focal-release
(it's stuck in -proposed right now).

(On IRC I was also talking about another ibus change in focal, which
will require an apparmor change, but let's deal with that separately to
not complicate things too much.)

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  In Progress
Status in glib2.0 source package in Bionic:
  In Progress
Status in glib2.0 source package in Disco:
  In Progress
Status in glib2.0 source package in Eoan:
  In Progress
Status in glib2.0 source package in Focal:
  Fix Committed
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

[Alex Murray]

@gunnarhj - updated packages for ibus are now available in the ubuntu-
security-proposed PPA at https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa

Also I note the bug descriptions lists ibus in Focal as Fix Released -
but the latest version in focal (1.5.21-1~exp2ubuntu2) is the one with
the patch reverted - would you like me to upload an updated focal
version as well to the above PPA?

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  In Progress
Status in glib2.0 source package in Bionic:
  In Progress
Status in glib2.0 source package in Disco:
  In Progress
Status in glib2.0 source package in Eoan:
  In Progress
Status in glib2.0 source package in Focal:
  Fix Committed
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the updates in -proposed
  will allow the IBus patch to be re-enabled.

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
     - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates

[László Meskó]

Off-topic for Seahorse, but the reporter's (and my) real problem is about 
signing in LibreOffice.
I've found a way to sign document in LibreOffice on Ubuntu:

LibreOffice searches a keystore in this order:
a.) The environment variable MOZILLA_CERTIFICATE_FOLDER
b.) The Thunderbird profile
c.) The Mozilla suite profile
d.) The Firefox profile.
(source: https://wiki.openoffice.org/wiki/How_to_use_digital_Signatures )

So you do not need seahorse to sign documents in LibreOffice, only
Thunderbird or Firefox.

Steps:
1. Import your certificate into Thunderbird or Firefox key store (Edit, 
Preferences, etc.).
2. LO help says: "It is also necessary that the trust settings for the root 
certificates are set to trust the certificate to identify web sites and e-mail 
users." 
Make sure they are set.
3. In LibreOffice, Tools, Options, LibreOffie\Security, in "Certificate Path" 
the first keystore (for me) is "/home/lml/.thunderbird/something.default". 
(Note:
  - It seems you can choose between thunderbird and firefox keystore, but you 
can't.
  - The LO help mentions the "Certificate Detection" page, 
the Basic script there gives the same result.
)
Override this detected value using the following command to start LibreOffice 
using terminal:

MOZILLA_CERTIFICATE_FOLDER=sql:/home/lml/.thunderbird/something.default
soffice

(use your own path for Thunderbird or Firefox keystore)

The trick is to add "sql:" to the beginning of the value and override
the (otherwise correct) detected path. Maybe there is a problem in
LibreOffice not able to use the certificate folder...

I'm using Ubuntu 19.10, LibreOffice 6.3.2, Thunderbird 60.9.

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

Title:
  Seahorse unable to import pkcs12 certificates

Status in seahorse:
  New
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in seahorse package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Fedora:
  New
Status in seahorse package in Fedora:
  Unknown

Bug description:
  seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu
  18.04 LTS / GNOME 3.28.1

  When trying to import a certificate into seahorse/gnome-keyring on
  Ubuntu 18.04, seahorse GUI application shows the 'import' button
  greyed out, while mouse hovering the "import" button shows the message
  "Cannot import because there are no compatible importers".

  This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as
  I've just tested on my wife's laptop, but happens in my Laptop with
  Ubuntu 18.04 LTS (Seahorse 3.20.0-5).

  Because that problem, it's not possible to digitally sign documents
  with LibreOffice.

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

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

[Desktop-packages] [Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)

[Lonnie Lee Best]

I recently submitted a bug about this topic for Ubuntu 19.10:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #757
   https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757

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

Title:
  Unlocking the  screen takes 5 seconds in Xorg sessions (not so much in
  Wayland sessions)

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired
Status in mutter package in Ubuntu:
  Expired
Status in xorg-server package in Ubuntu:
  Expired

Bug description:
  This is a fresh installation of 18.04. After entering the password and
  pressing enter, it takes 5 seconds for the lock screen to disappear.
  This problem didn't happen on the same machine with 16.04 or 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 15:31:48 2018
  InstallationDate: Installed on 2018-05-04 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Rickyx]

I have been a victim of the same behaviour on Debian* for about 6 months.
The computer, assembled with amd64 architecture, crashes with both Debian 9 and 
Debian 10, both with proprietary NVidia and Nouveau drivers.

The mouse stops and the system is irreparably planted: no Sysreq, no
remote connection, no other terminals: nothing.

I activated all the logs I knew about but I didn't have any kind of
clarification.


Thank you,
Riccardo

ps. I know that the bug refers to Ubuntu but I suppose that, since the
basis of the system is the same, it may have a common cause.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1850201] Re: Memory usage grows when locking/unlocking the screen

[Balazs Pere]

What does it mean "doesn't free memory immediately"? Hours? Days? I never 
experienced decrease in memory usage, except for small fluctuations. I think it 
is a memory leak added to this slow garbage collection.
I also wrote about this problem to 
https://gitlab.gnome.org/GNOME/gjs/issues/217# but the guys there suggested me 
to report a bug here, because they thoght that this is not a garbage collection 
issue.
And it seems to me that gnome-shell or gjs is leaking without the extensions 
too.

** Bug watch added: gitlab.gnome.org/GNOME/gjs/issues #217
   https://gitlab.gnome.org/GNOME/gjs/issues/217

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

Title:
  Memory usage grows when locking/unlocking the screen

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Many times after logging in gnome-shell uses 600-800kB of memory, and
  also slows down quite a bit (e.g., 20-30 seconds waiting for login).
  Only after multiple resets (Alt+F2 r) drops the memory usage below
  200kB. I use my computer mainly for work, and the above phenomenon is
  quite disturbing. After a couple of hours of work memory usage is
  growing over 400kB again, and sometimes the reset (Alt+F2 r) doesn't
  help either. My system is Ubuntu 18.04.3 Gnome 3.28.2, but the newest
  Ubuntu also behaves similarly. This is an old issue, it was present in
  18.04, 18.10, 19.04 and now in 19.10. I use three computers, and all
  of them suffer with this problem. Anyone can check this with the
  "gnome-shell memory monitor"  gnome-shell extension.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Mon Oct 28 20:28:38 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-01-04 (297 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  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/1850201/+subscriptions

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

[Desktop-packages] [Bug 1785063] Re: [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all

[Cedric]

Hello, in the expectation that a hacker comes to save us from the claws
of MS (which is supposedly loves linux ...), here is the list of what
works or not works :

Works :

External HDMI connector (adapter): Select "HDMI 1"
Bluetooth

Does not work :

Internal jack connector
External jack connector (adapter)
Internal speakers

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

Title:
  [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all

Status in sound-2.6 (alsa-kernel):
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  No sound at all, through speakers or headphones jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  natty  4286 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug  2 15:07:12 2018
  InstallationDate: Installed on 2017-10-12 (293 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1248 F pulseaudio
natty  4286 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Galaxy Book 12, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-04-04 (120 days ago)
  dmi.bios.date: 06/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02HAC.004.170626.WY.1442
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SM-W720NZKBBTU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8766A2S-C01-G001-S0001+10.0.14393
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02HAC.004.170626.WY.1442:bd06/26/2017:svnSAMSUNGELECTRONICSCO.,LTD.:pnGalaxyBook12:pvrP02HAC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSM-W720NZKBBTU:rvrSGL8766A2S-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct32:cvrN/A:
  dmi.product.family: SAMSUNG GALAXY
  dmi.product.name: Galaxy Book 12
  dmi.product.version: P02HAC
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-10-13T14:38:49.320280

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1785063/+subscriptions

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

[Desktop-packages] [Bug 1851172] Re: evolution-addressbook-factory crashed with signal 5 in g_thread_new()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1845799, so 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.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1851172/+attachment/5302581/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1851172/+attachment/5302583/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1851172/+attachment/5302586/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1851172/+attachment/5302587/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1851172/+attachment/5302588/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1851172/+attachment/5302589/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1851172/+attachment/5302590/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1845799

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  evolution-addressbook-factory crashed with signal 5 in g_thread_new()

Status in evolution-data-server package in Ubuntu:
  New

Bug description:
  it was consuming all memory in the background

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: evolution-data-server 3.28.5-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  Date: Sun Nov  3 12:50:15 2019
  ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory
  InstallationDate: Installed on 2017-10-13 (750 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012)
  ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  Signal: 5
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_thread_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   e_data_factory_spawn_subprocess_backend () at 
/usr/lib/x86_64-linux-gnu/libebackend-1.2.so.10
   () at /usr/lib/x86_64-linux-gnu/libedata-book-1.2.so.25
   ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: evolution-addressbook-factory crashed with signal 5 in g_thread_new()
  UpgradeStatus: Upgraded to bionic on 2018-06-25 (495 days ago)
  UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps

[Olivier Tilloy]

** Changed in: chromium-browser (Ubuntu)
 Assignee: jon grahaqm (skyking2630) => (unassigned)

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

Title:
  Images are washed out or colors are skewed in some apps

Status in Eye of GNOME:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in colord package in Ubuntu:
  Confirmed
Status in eog package in Ubuntu:
  Confirmed

Bug description:
  Images are washed out or colors are skewed in some apps, notably
  Chrome/Chromium and Image Viewer (eog).

  Workaround:

  Settings > Devices > Colour >
  and disable or remove your monitor's colour profile

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

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

[Desktop-packages] [Bug 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

[Karsten Natusch]

Since my upgrade from 19.04 to 19.10 my T430 is facing a similar problem
with i915 fifo underruns:

The problem occurs by switching from user A to B. If user A is logged in
and want to switch to another user B (e.g. admin), then after entering
the credentials of the user B, the system hangs up.

Sometimes the system does not hang up directly. In this case the lock
screen pops up and if I try then to enter the credentials of user B
again, then the system hangs up. If I enter the credentials of the
former already logged in user A, then system does not hang up.

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

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

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id

[Desktop-packages] [Bug 1850702] Re: [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone sound is faint and distorted (but works fine in Windows)

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Samsung Notebook 7 Pro, Realtek ALC256, headphone jack] Headphone
  sound is faint and distorted (but works fine in Windows)

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can't get sound of my laptop (Samsung Notebook 7 Force) through the
  headphone jack. The speakers work fine.

  When I plug a headphone, I can hear the sound being played very
  faintly. If I bump the volume to the maximum, that is. The sound is
  very distorted, like a buzz effect being applied over it.

  I noticed that if I delete /.config/pulse the distortion goes away,
  but the sound remains very low. After some time, the buzzing effect
  comes back.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ubuntu-release-upgrader-core 1:19.10.15
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Wed Oct 30 16:03:41 2019
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filipe 1294 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-10-29 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 760XBE
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=c0332bcf-c9a8-4b67-9a6f-bf87cc7abdb8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-19-generic N/A
   linux-backports-modules-5.3.0-19-generic  N/A
   linux-firmware1.183.1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  

[Desktop-packages] [Bug 1740637] Re: Remove python-appindicator and gir1.2-appindicator-0.1

[Matthias Klose]

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

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

** Tags added: rls-ff-incoming

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

Title:
  Remove python-appindicator and gir1.2-appindicator-0.1

Status in libappindicator package in Ubuntu:
  Confirmed
Status in libappindicator source package in Focal:
  Confirmed

Bug description:
  gir1.2-appindicator-0.1 has no reverse dependencies (it is for gtk2
  GObject Introspection)

  There are only 2 packages that recommend python-appindicator. It would be 
trivial to drop the recommends. Those 2 packages (deluge and
  gtk-recordmydesktop) will probably be removed from Debian approx. September 
2019 because they use pygtk.

  $ reverse-depends python-appindicator
  Reverse-Recommends
  ==
  * deluge-gtk
  * gtk-recordmydesktop

  previous reverse depends
  ---
  * cherrytree — dependency on python-appindicator was dropped early in bionic. 
 RM requested in LP: #1731725
  * hamster-indicator - source package was removed (LP: #1739797)

  --
  OTHER GTK2 REVERSE DEPENDS
  --
  The other gtk2 libraries for libappindicator aren't planned for removal yet.

  $ reverse-depends libappindicator0.1-cil
  Reverse-Depends
  ===
  * libappindicator0.1-cil-dev
  * tasque

  $ reverse-depends libappindicator1
  Reverse-Recommends
  ==
  * nautilus-dropbox

  Reverse-Depends
  ===
  * alarm-clock-applet
  * gir1.2-appindicator-0.1 (proposed removal here)
  * gmpc
  * growl-for-linux
  * gxkb
  * hime
  * indicator-application-gtk2
  * libappindicator-dev
  * libappindicator0.1-cil
  * nitroshare
  * parcellite
  * python-appindicator (proposed removal here)
  * quicksynergy
  * wallch

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

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

[Desktop-packages] [Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]

[Andrea Corbellini]

Hi, I added Eoan series to the bug report as it hasn't been fixed there.
(The bug had been automatically marked as Fix Released after the Focal update)

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

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

** Also affects: mutter (Ubuntu Focal)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Fix Released

** Also affects: gnome-shell (Ubuntu Focal)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Won't Fix

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

** Changed in: gnome-shell (Ubuntu Eoan)
   Status: New => Won't Fix

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

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

Title:
  gnome-shell infinite error loop when closing app in activities
  overview: Object St.Button (0x55aeadeca4a0), has been already
  deallocated ... [workspace.js:695]

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Won't Fix
Status in mutter source package in Eoan:
  Triaged
Status in gnome-shell source package in Focal:
  Won't Fix
Status in mutter source package in Focal:
  Fix Released
Status in gnome-shell package in Fedora:
  Confirmed

Bug description:
  [ Impact ]

  Gnome shell fills the journal with errors as soon as a view is closed
  from the overview

  Ubuntu 19.10 on Xorg
  gnome-shell 3.34.1-1ubuntu1

  [ Test case ]

  1) Open terminal and watch journalct -f /usr/bin/gnome-shell
  2) Open a window (i.e Files)
  3) Close Files in the activities overview
  4) gnome-shell spanws errors in the journal.

  Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 
0x55aead0b5360 ==
  Oct 14 23:25:38 titan gnome-shell[9919]: #0   55aeae6f3910 i   
resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15)
  Oct 14 23:25:38 titan gnome-shell[9919]: #1   7ffd96c5e360 b   
self-hosted:975 (7f438c12dee0 @ 392)

  [ Regression potential ]

  Key focus might not work properly in some shell elements, in
  particular the focus be owned by multiple actors or by none of them.

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

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

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

[Bug Watch Updater]

** Changed in: network-manager-applet (Debian)
   Status: Unknown => Fix Released

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

Title:
  nm-connection-editor crashes when trying to modify connection without
  gnome-keyring installed

Status in Network Manager Applet:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-applet source package in Bionic:
  Fix Committed
Status in network-manager-applet package in Debian:
  Fix Released

Bug description:
  * Impact
  the connection editor segfault when using without gnome-keyring

  * Test case
  uninstall gnome-keyring and try to edit a connection, it shouldn't segfault

  * Regression potential
  the fix changes an error handling case, it shouldn't impact normal use

  
  

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

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

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

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

[Desktop-packages] [Bug 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12

[Paul]

Ok I actually made it work. Not sure if this still belongs here, but
might as well inform others how I fixed it. Maybe it will help you as
well.

Although I had never connected the iPhone to my PC before, I needed to
reset the trust settings to get the dialogue option to "trust this
device" on the iPhone.

The procedure is quite simple. Go to Settings > General >> Reset >>
Reset Location and Privacy. It is also explained here:
https://www.guidingtech.com/fix-iphone-trust-this-computer-not-showing-
up-issue/

By the way, I then still could not paste files on the iPhone. This might
be an Xubuntu specific issue, but I had to install iFuse first. See
here: https://askubuntu.com/questions/799414/how-to-move-files-from-
ubuntu-to-iphone

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

Title:
  Unhandled lockdown error (-2) - iphone ios 12

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on 
the Documents in the file manager, I got this error: Unhandled lockdown error 
(-2). 
  I attached a screenshot about this error.

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

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

[Desktop-packages] [Bug 1806080] Re: [snap] Chromium snap crashes when trying to access fs

[Efthimios Chaskaris]

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

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

Title:
  [snap] Chromium snap crashes when trying to access fs

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  When I attempt to upload or save on certain pages it crashes the browser.  
Some examples below.
  Does not happen on Google Drive.  Looks like it's trying to query the fs and 
dies when it can't.

  
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.5 LTS
  Release:  16.04
  Codename: xenial
  Kernel: 4.15.0-39-generic
  Chromium:   Version 70.0.3538.110 (Official Build) snap (64-bit)

  
  # Right click on blank page "save as"
  Nov 30 16:31:00 $HOSTNAME kernel: [35208.515968] audit: type=1400 
audit(1543595460.939:151): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/etc/fstab" pid=30734 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  # Restart browser
  Nov 30 16:31:04 $HOSTNAME dbus[1899]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name="org.freedesktop.secrets" pid=32093 label="snap.chromium.chromium" 
peer_pid=1823 peer_label="unconfined"
  Nov 30 16:31:04 $HOSTNAME kernel: [35212.081247] audit: type=1107 
audit(1543595464.507:152): pid=1384 uid=106 auid=4294967295 ses=4294967295 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=31991 label="snap.chromium.chromium" 
peer_pid=24826 peer_label="unconfined"
  Nov 30 16:31:05 $HOSTNAME kernel: [35213.238692] audit: type=1400 
audit(1543595465.663:153): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=31991 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Nov 30 16:31:05 $HOSTNAME kernel: [35213.274048] audit: type=1400 
audit(1543595465.699:154): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=31991 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  # Right click on blank page "save as" #2
  Nov 30 16:31:08 $HOSTNAME kernel: [35216.557849] audit: type=1400 
audit(1543595468.983:155): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/etc/fstab" pid=31991 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  # Restart browser
  Nov 30 16:31:13 $HOSTNAME dbus[1899]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name="org.freedesktop.secrets" pid=32646 label="snap.chromium.chromium" 
peer_pid=1823 peer_label="unconfined"
  Nov 30 16:31:14 $HOSTNAME kernel: [35221.656759] audit: type=1107 
audit(1543595474.083:156): pid=1384 uid=106 auid=4294967295 ses=4294967295 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=32544 label="snap.chromium.chromium" 
peer_pid=24826 peer_label="unconfined"
  Nov 30 16:31:23 $HOSTNAME kernel: [35230.641856] audit: type=1400 
audit(1543595483.067:157): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=32544 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  Nov 30 16:31:23 $HOSTNAME kernel: [35230.660955] audit: type=1400 
audit(1543595483.087:158): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=32544 
comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  
  # Upload to Salesforce case #2
  Nov 30 16:31:46 $HOSTNAME kernel: [35253.816946] audit: type=1400 
audit(1543595506.243:159): apparmor="DENIED" operation="open" 
profile="snap.chromium.chromium" name="/etc/fstab" pid=32544 comm="chrome" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  # Restart browser
  Nov 30 16:31:56 $HOSTNAME dbus[1899]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/secrets" 
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" 
name="org.freedesktop.secrets" pid=938 label="snap.chromium.chromium" 
peer_pid=1823 peer_label="unconfined"
  Nov 30 16:31:56 $HOSTNAME kernel: [35264.509009] audit: type=1107 
audit(1543595516.935:160): pid=1384 uid=106 auid=4294967295 ses=4294967295 
msg='apparmor="DENIED" operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" 

[Desktop-packages] [Bug 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12

[Paul]

Same problem here, but then on Xubuntu 18.04.3 LTS computer and an old
iPhone 4.

Failed to mount "Documents on XYZ iPhone".
Unhandled Lockdown error (-2).

When I type "idevicepair pair" in the terminal, it gives me the
following message:

ERROR: Could not validate with device
d91d11bb8bf8225ab0dd67380ddec2a8afcbdc58 because a passcode is set.
Please enter the passcode on the device and retry.

However, on the iPhone itself I do not receive the "trust this device?"
message, and thus am unable to continue. Rebooting the iPhone or
computer does not help.

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

Title:
  Unhandled lockdown error (-2) - iphone ios 12

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on 
the Documents in the file manager, I got this error: Unhandled lockdown error 
(-2). 
  I attached a screenshot about this error.

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

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

[Desktop-packages] [Bug 1849084] IwConfig.txt

[Mike Lykov]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1849084/+attachment/5302530/+files/IwConfig.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 ff 

[Desktop-packages] [Bug 1849084] RfKill.txt

[Mike Lykov]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1849084/+attachment/5302539/+files/RfKill.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 ff ff ff 

[Desktop-packages] [Bug 1849084] ProcCpuinfo.txt

[Mike Lykov]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1849084/+attachment/5302533/+files/ProcCpuinfo.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 

[Desktop-packages] [Bug 1849084] ProcEnviron.txt

[Mike Lykov]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1849084/+attachment/5302535/+files/ProcEnviron.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 

[Desktop-packages] [Bug 1849084] ProcModules.txt

[Mike Lykov]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1849084/+attachment/5302537/+files/ProcModules.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 

[Desktop-packages] [Bug 1849084] ProcInterrupts.txt

[Mike Lykov]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1849084/+attachment/5302536/+files/ProcInterrupts.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 

[Desktop-packages] [Bug 1849084] Lspci.txt

[Mike Lykov]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1849084/+attachment/5302531/+files/Lspci.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff 

[Desktop-packages] [Bug 1849084] ProcCpuinfoMinimal.txt

[Mike Lykov]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1849084/+attachment/5302534/+files/ProcCpuinfoMinimal.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 

[Desktop-packages] [Bug 1849084] Lsusb.txt

[Mike Lykov]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1849084/+attachment/5302532/+files/Lsusb.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff 

[Desktop-packages] [Bug 1849084] Dependencies.txt

[Mike Lykov]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1849084/+attachment/5302529/+files/Dependencies.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 

[Desktop-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract

[Apfelgriebs]

The bug is still present in Ubuntu 19.10.

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

Title:
  Abysmal memory leak on tracker-extract

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging
  madly. It became very difficult to use and I discovered the problem to
  be tracker-extract running and very rapidly leaking memory up to 100%
  and breaching into swap memory. I tried killing it several times but
  Tracker appears to relaunch it every time, so I deleted it from
  /usr/lib/tracker entirely.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: tracker 2.1.8-2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 13:02:25 2019
  InstallationDate: Installed on 2019-03-11 (42 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago)

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

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

[Desktop-packages] [Bug 1849084] CurrentDmesg.txt

[Mike Lykov]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1849084/+attachment/5302528/+files/CurrentDmesg.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 

[Desktop-packages] [Bug 1754872] Re: apt install xubuntu-desktop does not resolve dependencies properly

[Sean Davis]

Assigned this issue to xubuntu-docs. Let's document the correct way to
handle the installation of the xubuntu-desktop package, and make it easy
for users to find (and forums to point to) when these questions arise in
the future.


** Also affects: xubuntu-docs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xubuntu-docs (Ubuntu)
   Status: New => Confirmed

** Changed in: xubuntu-meta (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  apt install xubuntu-desktop does not resolve dependencies properly

Status in apt package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in indicator-datetime package in Ubuntu:
  Invalid
Status in xfce4-session package in Ubuntu:
  Fix Released
Status in xubuntu-docs package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Install `xubuntu-desktop` meta package on 18.04 LTS
  2. Login to session
  3a. Click on clock indicator on panel, select "Time & Date Settings"
  3b. Click on Gear, select "About this Computer" or "System Settings"
  3c. Click on keyboard layout indicator, select "Text Entry Settings"

  Expected results:
  xfce-oriented control center is opened

  Actual results:
  gnome-control-center is opened, but with empty window.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xubuntu-desktop 2.223
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Mar 10 21:10:11 2018
  SourcePackage: xubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1849084] WifiSyslog.txt

[Mike Lykov]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1849084/+attachment/5302541/+files/WifiSyslog.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[Mike Lykov]

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  combr  3311 F pulseaudio
 /dev/snd/controlC0:  combr  3311 F pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2018-11-22 (346 days ago)
InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
MachineType: HP HP Laptop 15-db0xxx
Package: linux-image-5.3.0-19-generic 5.3.0-19.20
PackageArchitecture: amd64
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=ff84e034-43ff-4c6f-914b-42dcdd53cf31 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-19-generic N/A
 linux-backports-modules-5.3.0-19-generic  N/A
 linux-firmware1.183.1
Tags:  eoan
Uname: Linux 5.3.0-19-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-11-02 (1 days ago)
UserGroups: adm cdrom dip disk docker libvirt lpadmin plugdev sambashare sudo 
wireshark
_MarkForUpload: True
dmi.bios.date: 04/06/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.02
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 84AE
dmi.board.vendor: HP
dmi.board.version: 86.19
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/06/2018:svnHP:pnHPLaptop15-db0xxx:pvrType1ProductConfigId:rvnHP:rn84AE:rvr86.19:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 15-db0xxx
dmi.product.sku: 4MK59EA#ACB
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP


** Tags added: apport-collected eoan

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  

[Desktop-packages] [Bug 1849084] CRDA.txt

[Mike Lykov]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1849084/+attachment/5302527/+files/CRDA.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff 

[Desktop-packages] [Bug 1849084] UdevDb.txt

[Mike Lykov]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1849084/+attachment/5302540/+files/UdevDb.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 ff ff ff 

[Desktop-packages] [Bug 1849084] PulseList.txt

[Mike Lykov]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1849084/+attachment/5302538/+files/PulseList.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 ff 

[Desktop-packages] [Bug 1849084] AlsaInfo.txt

[Mike Lykov]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1849084/+attachment/5302526/+files/AlsaInfo.txt

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 ff 

[Desktop-packages] [Bug 1848766] Re: xubuntu still pulls in Python2 via the python-gtk2-dev b-d in libappindicator

[Sean Davis]

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

Thanks. jbicha referred to
https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1740637
and mentioned that the python2 support is going to be dropped from
libappindicator, so this should no longer be an issue for Xubuntu.
Thanks for bringing it to my attention!

** Changed in: xubuntu-meta (Ubuntu)
   Status: New => Invalid

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

** This bug has been marked a duplicate of bug 1740637
   Remove python-appindicator and gir1.2-appindicator-0.1

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

Title:
  xubuntu still pulls in Python2 via the python-gtk2-dev b-d in
  libappindicator

Status in libappindicator package in Ubuntu:
  New
Status in pygtk package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  xubuntu still pulls in Python2 via the python-gtk2-dev b-d in
  libappindicator.  We don't want to have Python2 anymore in seeds and
  images.  So either xubuntu should stop using libappindicator, or
  libappindicator should provide Python3 packages.

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

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

[Desktop-packages] [Bug 1848766] Re: xubuntu still pulls in Python2 via the python-gtk2-dev b-d in libappindicator

[Matthias Klose]

just run: seeded-in-ubuntu python2.7

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

Title:
  xubuntu still pulls in Python2 via the python-gtk2-dev b-d in
  libappindicator

Status in libappindicator package in Ubuntu:
  New
Status in pygtk package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  xubuntu still pulls in Python2 via the python-gtk2-dev b-d in
  libappindicator.  We don't want to have Python2 anymore in seeds and
  images.  So either xubuntu should stop using libappindicator, or
  libappindicator should provide Python3 packages.

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

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

[Desktop-packages] [Bug 1848766] Re: xubuntu still pulls in Python2 via the python-gtk2-dev b-d in libappindicator

[Sean Davis]

Hey @doko,

>From what I can tell, we're not shipping libappindicator at all in
focal. Can you elaborate where this is coming from?

http://cdimage.ubuntu.com/xubuntu/daily-live/current/focal-desktop-
amd64.manifest

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

Title:
  xubuntu still pulls in Python2 via the python-gtk2-dev b-d in
  libappindicator

Status in libappindicator package in Ubuntu:
  New
Status in pygtk package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  New

Bug description:
  xubuntu still pulls in Python2 via the python-gtk2-dev b-d in
  libappindicator.  We don't want to have Python2 anymore in seeds and
  images.  So either xubuntu should stop using libappindicator, or
  libappindicator should provide Python3 packages.

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

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

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[Mike Lykov]

I see the miracle :)
according 
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues

I try two options:
1.  initcall_debug
2. echo 0 > /sys/power/pm_async

Before I can reproduce the bug each time I press power button for
suspend/resume (after resume I have a black screen with in 100% times
when conditions described above satisfied).

then I try to disable pm_async and after suspend/resume I have no this
bug. BUT, after restoring pm_async value to 1 via reboot, I cannot
reproduce bug anymore. It is not happen in same situation as earlier.

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 

[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields

[Efthimios Chaskaris]

On my laptop (Thinkpad L520) it doesn't work. Curiously, when swiping up
with mouse the OSK doesn't come up when Chromium is on the view, but it
comes up when on desktop. The OSK pops up fine on terminal, login field
and text editor. It also doesn't work on Chrome.

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

Title:
  New On-screen keyboard does not appear automatically when selecting
  some text fields

Status in OEM Priority Project:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-settings-daemon source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  on-screen keyboard cannot be reliably opened when running under xorg.

  [Test Case]
  1. Login into an xorg session
  1. Open an application with text-entries (e.g. Firefox)
  2. Try to enter text in a text entry using the new OSK

  Expected results:
  The on-screen keyboard should appear.

  [Regression Potential]
  The proposed fix requires a change in the way gnome-settings-daemon decides 
to enable or disable ibus. Please make sure that ibus correctly works when
  using a keyboard layout that requires it (e.g. chinese).

  [Original Report]
  I have always used an on-screen keyboard as a virtual keyboard for entering 
text in a different layout than my physical keyboard. This time I cannot, since 
I cannot manually trigger the new OSK.

  Steps:

  1. Open Firefox
  2. Try to enter text in a different layout using the new OSK
  3. You cannot make the OSK appear

  When enabled, the new OSK appears automatically in Activities, but I
  cannot trigger it outside GNOME apps. You have to enable the new OSK
  first from Universal Access in Settings.

  I consider this a regression from 16.04 LTS, where On-board is easily
  triggered.

  Workaround:

  sudo apt install onboard

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 11:31:16 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (180 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions

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

[Desktop-packages] [Bug 1851146] [NEW] No Virtual Terminals

[Joe Brown]

Public bug reported:

I'll start this bug report with my first disclaimer: I'm filing this
report from a fixed system.  The original system that I'm going to
reference has been installed over with the current system I'm filing
this report from.  The first install was UEFI, minimal install, not
connected to the internet during installation.  Now, I'll continue with
my story.

So, when doing the first install, I realized I had screwed up my
username when doing the install.  But you can't do a lot of the
'usermod' commands from the user you're logged in as.  Since I was
having to log in as a regular user, and then run 'sudo usermod', it was
stating that the user I was trying to modify was currently logged in.
So I logged out, and then attempted to switch to a tty, as I didn't need
a graphical login for root.

When trying to access virtual TTYs from Ctrl+Alt+F{3,4,5,6}, there were
no terminals to access.  I did some googling and didn't find anything
directly related.  Most were related to either accessing virtual
terminals, or getting back to a graphical desktop if you mistakenly get
to a vtty.  So I took to IRC (#ubuntu on freenode).  After someone did a
'!tty' to really rub salt in the wound, someone recommended that I try
uncommenting 'GRUB_TERMINAL=console' and regenerating grub.cfg, I took
them up on the offer.

So I open /etc/default/grub, and scroll down to that line.  I
immediately see it says 'grub-pc only'.  I knew my install was UEFI, but
since it was a fresh install I ignored the warning and did it anyway.
Uncommented GRUB_TERMINAL=console did a 'sudo update-grub'.  I went down
for a reboot...and my system did not boot again.  I considered chrooting
and fixing it, but I thought it may be less annoying to just re-install.
However, this time I elected to do a full install while connected to
wifi.  After booting up the first time, I try switch over to a TTY and
*POOF!*, I have ttys now.

So I'm not sure if my install the first time was simply busted, or the
difference of doing a minimal install vs a full install is what caused
my vtty issue.  But anyway.  Thought I'd open a bug.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  3 11:06:00 2019
InstallationDate: Installed on 2019-11-03 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  No Virtual Terminals

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I'll start this bug report with my first disclaimer: I'm filing this
  report from a fixed system.  The original system that I'm going to
  reference has been installed over with the current system I'm filing
  this report from.  The first install was UEFI, minimal install, not
  connected to the internet during installation.  Now, I'll continue
  with my story.

  So, when doing the first install, I realized I had screwed up my
  username when doing the install.  But you can't do a lot of the
  'usermod' commands from the user you're logged in as.  Since I was
  having to log in as a regular user, and then run 'sudo usermod', it
  was stating that the user I was trying to modify was currently logged
  in.  So I logged out, and then attempted to switch to a tty, as I
  didn't need a graphical login for root.

  When trying to access virtual TTYs from Ctrl+Alt+F{3,4,5,6}, there
  were no terminals to access.  I did some googling and didn't find
  anything directly related.  Most were related to either accessing
  virtual terminals, or getting back to a graphical desktop if you
  mistakenly get to a vtty.  So I took to IRC (#ubuntu on freenode).
  After someone did a '!tty' to really rub salt in the wound, someone
  recommended that I try uncommenting 'GRUB_TERMINAL=console' and
  regenerating grub.cfg, I took them up on the offer.

  So I open /etc/default/grub, and scroll down to that line.  I
  immediately see it says 'grub-pc only'.  I knew my install was UEFI,
  but since it was a fresh install I ignored the warning and did it
  anyway.  Uncommented GRUB_TERMINAL=console did a 'sudo update-grub'.
  I went down for a reboot...and my system did not boot again.  I
  considered chrooting and fixing it, but I thought it may be less
  annoying to just re-install.  However, this time I elected to do a
  full install while connected to wifi.  After booting up the first
  time, I 

[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields

[Mario Vukelic]

On Eoan (on the Dell XPS 9575 mentioned before), the OSK auto-summons
nearly everywhere as far as I can tell, incl. Chrome. The only
application I use and found so far where this does not work is Gnucash.

There is even an improvement in X that helps in this case: the OSK now
can be summoned by swiping up from the bottom screen edge, in the same
way as it previously worked only on Wayland.

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

Title:
  New On-screen keyboard does not appear automatically when selecting
  some text fields

Status in OEM Priority Project:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-settings-daemon source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  on-screen keyboard cannot be reliably opened when running under xorg.

  [Test Case]
  1. Login into an xorg session
  1. Open an application with text-entries (e.g. Firefox)
  2. Try to enter text in a text entry using the new OSK

  Expected results:
  The on-screen keyboard should appear.

  [Regression Potential]
  The proposed fix requires a change in the way gnome-settings-daemon decides 
to enable or disable ibus. Please make sure that ibus correctly works when
  using a keyboard layout that requires it (e.g. chinese).

  [Original Report]
  I have always used an on-screen keyboard as a virtual keyboard for entering 
text in a different layout than my physical keyboard. This time I cannot, since 
I cannot manually trigger the new OSK.

  Steps:

  1. Open Firefox
  2. Try to enter text in a different layout using the new OSK
  3. You cannot make the OSK appear

  When enabled, the new OSK appears automatically in Activities, but I
  cannot trigger it outside GNOME apps. You have to enable the new OSK
  first from Universal Access in Settings.

  I consider this a regression from 16.04 LTS, where On-board is easily
  triggered.

  Workaround:

  sudo apt install onboard

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 11:31:16 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (180 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions

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

[Desktop-packages] [Bug 1851144] [NEW] Switching from unity-greeter to lightdm-gtk-greeter prevents lightdm.service from starting

[jean-christophe manciot]

Public bug reported:

Ubuntu 20.04
lightdm 1.30.0-0ubuntu2
lightdm-gtk-greeter 2.0.6-0ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
Uname: Linux 5.3.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
Date: Sun Nov  3 16:15:54 2019
InstallationDate: Installed on 2015-04-28 (1650 days ago)
InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: lightdm
UpgradeStatus: Upgraded to focal on 2019-11-03 (0 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2018-10-30T10:37:29

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


** Tags: amd64 apport-bug focal

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

Title:
  Switching from unity-greeter to lightdm-gtk-greeter prevents
  lightdm.service from starting

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  lightdm 1.30.0-0ubuntu2
  lightdm-gtk-greeter 2.0.6-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  Date: Sun Nov  3 16:15:54 2019
  InstallationDate: Installed on 2015-04-28 (1650 days ago)
  InstallationMedia: Ubuntu-Server 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to focal on 2019-11-03 (0 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-10-30T10:37:29

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

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

[Desktop-packages] [Bug 1851143] [NEW] X11 session all commands ignored.

[corrado venturini]

Public bug reported:

Starting the x11 session I'm able to open the terminal, just once, so I was 
able to file this bug.
After that any action, with mouse or keyboard are ignored. This is to document 
bug #1850969

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  3 16:40:23 2019
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
InstallationDate: Installed on 2019-10-30 (4 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191030)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
 Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=1210135d-e0e3-467e-9083-5f35bd1d110d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: H110M-G/M.2
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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

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


** Tags: amd64 apport-bug focal reproducible ubuntu

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

Title:
  X11 session all commands ignored.

Status in xorg package in Ubuntu:
  New

Bug description:
  Starting the x11 session I'm able to open the terminal, just once, so I was 
able to file this bug.
  After that any action, with mouse or keyboard are ignored. This is to 
document bug #1850969

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  3 16:40:23 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2019-10-30 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191030)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=1210135d-e0e3-467e-9083-5f35bd1d110d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be 

[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields

[Efthimios Chaskaris]

I get this on Eoan, no OSK pop up for Chromium text fields on laptop.
Works on desktop.

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

Title:
  New On-screen keyboard does not appear automatically when selecting
  some text fields

Status in OEM Priority Project:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Bionic:
  Fix Released
Status in gnome-shell source package in Bionic:
  Fix Released
Status in gnome-settings-daemon source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  on-screen keyboard cannot be reliably opened when running under xorg.

  [Test Case]
  1. Login into an xorg session
  1. Open an application with text-entries (e.g. Firefox)
  2. Try to enter text in a text entry using the new OSK

  Expected results:
  The on-screen keyboard should appear.

  [Regression Potential]
  The proposed fix requires a change in the way gnome-settings-daemon decides 
to enable or disable ibus. Please make sure that ibus correctly works when
  using a keyboard layout that requires it (e.g. chinese).

  [Original Report]
  I have always used an on-screen keyboard as a virtual keyboard for entering 
text in a different layout than my physical keyboard. This time I cannot, since 
I cannot manually trigger the new OSK.

  Steps:

  1. Open Firefox
  2. Try to enter text in a different layout using the new OSK
  3. You cannot make the OSK appear

  When enabled, the new OSK appears automatically in Activities, but I
  cannot trigger it outside GNOME apps. You have to enable the new OSK
  first from Universal Access in Settings.

  I consider this a regression from 16.04 LTS, where On-board is easily
  triggered.

  Workaround:

  sudo apt install onboard

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  1 11:31:16 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-10-02 (180 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions

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

[Desktop-packages] [Bug 1849615]

[Release-mgmt-account-bot]

[Bugbug](https://github.com/mozilla/bugbug/) thinks this bug is a
regression, but please revert this change in case of error.

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

Title:
  WebRTC-related crashes

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  In Mozilla we've detected a spike of crashes in the Ubuntu-packaged
  version of Firefox 69.0.x. All the crashes are happening in the WebRTC
  code and specifically libc's FD_SET, FD_CLR and FD_ISSET range-
  checking safety is causing an abort. Is it possible that Firefox is
  being built with a FD_SETSIZE value that's different from what's used
  in libc?

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

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

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

[François Bouffard]

This is mostly a "mee too" post. Using a GTX 1060. The upgrade to 19.10
did not go well, stuck with graphical artifacts after a reboot. Further
reboots were met with kernel panics. Finally managed to boot kernel 5.0
in safe mode and finish the installation by choosing the "repair
packages" option. Was met with this autologin bug after (thanks to the
thread starter for noting that -- it was not clear autologin was the
culprit).

An additional detail: now I seem stuck with the 430 drivers. I cannot
upgrade to 435 because of "unmet dependencies" errors. Not sure if this
could be related given that clearly the nVidia drivers are involved in
this mess.

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

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

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

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

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

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

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

To manage 

[Desktop-packages] [Bug 1851046] Re: Enable Last.fm provider

[Jeremy Bicha]

It is disabled by default in GNOME. I don't know (or remember) why it's
disabled there.

https://gitlab.gnome.org/GNOME/gnome-online-
accounts/blob/master/meson_options.txt#L26

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Enable Last.fm provider

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

Bug description:
  Since a while now GOA supports Last.fm accounts but for some reason this 
provider is excluded in the Ubuntu build parameters of this package.
  Is there a specific reason why this is not enabled? Would it be possible to 
enable this provider as well?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-online-accounts 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Nov  2 16:07:05 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-26 (1437 days ago)
  InstallationMedia: It
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to eoan on 2019-10-20 (13 days ago)

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

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

[Desktop-packages] [Bug 1851134] [NEW] setting custom keyboard shortcut fails for certain keys

[Christopher Barrington-Leigh]

Public bug reported:

I click on settings in menu or press my settings icon key (above F9 key on 
Lenovo T450s keyboard). Navigate to "Keyboard Shortcuts".  Scroll to bottom to 
press "+" to add a custom shortcut. Define function, then click on "Set 
Shortcut...". Then I press the "Explorer" key, which is above the F12 on my 
keyboard. Instead of setting the shortcut, it brings up a file browser.
I can set my shortcut to shift-Explorer, but not to Explorer. This is even 
though no other keyboard shortcut listed is set to this key "Explorer".  The 
"Home folder" Launcher is set to "Disabled".
Changing the "Home folder" launcher keyboard shortcut to something else does 
not help.

Instead, once I click on "set Shortcut", it should listen to whatever I
choose.

The same problem exists for the "Search" key.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-settings-daemon 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  3 09:29:28 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2019-01-24 (282 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to eoan on 2019-10-31 (2 days ago)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "20191103_093407.jpg"
   
https://bugs.launchpad.net/bugs/1851134/+attachment/5302441/+files/20191103_093407.jpg

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

Title:
  setting custom keyboard shortcut fails for certain keys

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

Bug description:
  I click on settings in menu or press my settings icon key (above F9 key on 
Lenovo T450s keyboard). Navigate to "Keyboard Shortcuts".  Scroll to bottom to 
press "+" to add a custom shortcut. Define function, then click on "Set 
Shortcut...". Then I press the "Explorer" key, which is above the F12 on my 
keyboard. Instead of setting the shortcut, it brings up a file browser.
  I can set my shortcut to shift-Explorer, but not to Explorer. This is even 
though no other keyboard shortcut listed is set to this key "Explorer".  The 
"Home folder" Launcher is set to "Disabled".
  Changing the "Home folder" launcher keyboard shortcut to something else does 
not help.

  Instead, once I click on "set Shortcut", it should listen to whatever
  I choose.

  The same problem exists for the "Search" key.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-settings-daemon 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  3 09:29:28 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-24 (282 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: Upgraded to eoan on 2019-10-31 (2 days ago)

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

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

[Desktop-packages] [Bug 1848108] Re: [amdgpu] Screen Glitching & Kernel Panic

[Jarrod Farrell]

@kaihenfeng
Same white screen issue. But this time I actually collected last boot's journal 
and noticed this boot's and last boot's share a similar stack-trace at boot. 
Searching comes up with,
https://bugs.freedesktop.org/show_bug.cgi?id=107296
And judging from the comments they mention blank screens. But this stack trace 
appears regardless on a boot that gets a usable or a white void, albeit 
discretely different due to file differences it seems so it might not even be 
related. It's something I've observed.

** Bug watch added: freedesktop.org Bugzilla #107296
   https://bugs.freedesktop.org/show_bug.cgi?id=107296

** Attachment added: "journalctl-11-3-19"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848108/+attachment/5302439/+files/lastboot-review.log

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

Title:
  [amdgpu] Screen Glitching & Kernel Panic

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

Bug description:
  I've recently updated to Eoan, but it seems like some nasty bugs came
  with it, particularly from the amdgpu package.

  It started with visual glitches but it would occasionally freeze the
  screen with whatever playing in the background and require me to hard-
  shutdown to escape. Attached is an abridged `journalctl -b -1` showing
  the lines were the kernal panic occurred. I'll probably attach more as
  they occur and if it's not redundant.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct 14 21:27:34 2019
  DistUpgraded: 2019-10-13 05:03:20,327 DEBUG entry '# deb 
http://linux.teamviewer.com/deb stable main # disabled on upgrade to eoan' was 
disabled (unknown mirror)
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2019-03-22 (206 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KVCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro DEFAULT quiet splash ivrs_ioapic[32]=00:14.0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-10-13 (1 days ago)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET68W (1.48 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET68W(1.48):bd12/07/2018:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KVCTO1WW
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1848108] Re: [amdgpu] Screen Glitching & Kernel Panic

[Jarrod Farrell]

** Attachment added: "AMD Trace encountered in 5.4.0-050400rc4-generic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848108/+attachment/5302440/+files/amd-trace.log

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

Title:
  [amdgpu] Screen Glitching & Kernel Panic

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

Bug description:
  I've recently updated to Eoan, but it seems like some nasty bugs came
  with it, particularly from the amdgpu package.

  It started with visual glitches but it would occasionally freeze the
  screen with whatever playing in the background and require me to hard-
  shutdown to escape. Attached is an abridged `journalctl -b -1` showing
  the lines were the kernal panic occurred. I'll probably attach more as
  they occur and if it's not redundant.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Oct 14 21:27:34 2019
  DistUpgraded: 2019-10-13 05:03:20,327 DEBUG entry '# deb 
http://linux.teamviewer.com/deb stable main # disabled on upgrade to eoan' was 
disabled (unknown mirror)
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c3) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Raven Ridge [Radeon Vega Series / Radeon Vega Mobile 
Series] [17aa:506f]
  InstallationDate: Installed on 2019-03-22 (206 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 003: ID 13d3:56a6 IMC Networks Integrated Camera
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KVCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro DEFAULT quiet splash ivrs_ioapic[32]=00:14.0
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to eoan on 2019-10-13 (1 days ago)
  dmi.bios.date: 12/07/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0UET68W (1.48 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0UET68W(1.48):bd12/07/2018:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E585
  dmi.product.name: 20KVCTO1WW
  dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585
  dmi.product.version: ThinkPad E585
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1851128] [NEW] Stylus Use leads to Crash Application in Wayland Sessions

[Axel]

Public bug reported:

There is an issue in gtk. In Wayland sessions the use of a stylus leads
to crash of the application. It is apparently fixed in Gnome gtk.

When asking what should I do I got the answer that I should ask the
ubuntu gtk maintainers to  backport <
https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
, which I do
here and now.

Best regards

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  There is an issue in gtk. In Wayland sessions the use of a stylus
  leads to crash of the application. It is apparently fixed in Gnome
  gtk.

  When asking what should I do I got the answer that I should ask the
  ubuntu gtk maintainers to  backport <
  https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
  , which I do
  here and now.

  Best regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1851128/+subscriptions

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

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[Mike Lykov]

Yes, this bug also affects me.
I upgrade from Kubuntu 19.04 with 5.0 kernel to 19.10 with 5.3 kernel, and got 
described behaviour:

1. On 5.0 there is no problems (if I boot it in 19.10)
2. on 5.3 with default settings - there is a black screen after try to resume.
3. If I choose XRender with 5.3 in plasma settings - no problems.

current kernel 5.3.0-19-generic #20-Ubuntu SMP Fri Oct 18 09:04:39
I have no traces of oops in log, journalctl -b -1 -k show only
kernel: PM: suspend entry (deep)
string before resume/hang at black screen.

current driver xserver-xorg-video-amdgpu 19.0.1-1ubuntu1 amd64  
xorg log
[10.353] (II) AMDGPU(0): glamor X acceleration enabled on AMD RAVEN (DRM 
3.33.0, 5.3.0-19-generic, LLVM 9.0.0)
[10.353] (II) AMDGPU(0): glamor detected, initialising EGL layer.
[10.353] (==) AMDGPU(0): TearFree property default: auto
[10.353] (==) AMDGPU(0): VariableRefresh: disabled
[10.353] (II) AMDGPU(0): KMS Pageflipping: enabled

notebook with attached monitor
[10.396] (II) AMDGPU(0): EDID for output eDP
[10.396] (II) AMDGPU(0): Manufacturer: BOE  Model: 6a5  Serial#: 0
[10.396] (II) AMDGPU(0): Year: 2015  Week: 1
[10.396] (II) AMDGPU(0): EDID Version: 1.4
[10.396] (II) AMDGPU(0): Digital Display Input
[10.396] (II) AMDGPU(0): 6 bits per channel
[10.396] (II) AMDGPU(0): Digital interface is DisplayPort
[10.397] (II) AMDGPU(0): EDID for output HDMI-A-0
[10.397] (II) AMDGPU(0): Manufacturer: BNQ  Model: 801b  Serial#: 21573
[10.397] (II) AMDGPU(0): Year: 2017  Week: 15
[10.397] (II) AMDGPU(0): EDID Version: 1.3
[10.397] (II) AMDGPU(0): Digital Display Input
[10.398] (II) AMDGPU(0): Output eDP connected
[10.398] (II) AMDGPU(0): Output HDMI-A-0 connected
[10.398] (II) AMDGPU(0): Using spanning desktop for initial modes
[10.398] (II) AMDGPU(0): Output eDP using initial mode 1366x768 +0+0
[10.398] (II) AMDGPU(0): Output HDMI-A-0 using initial mode 2560x1440 
+1366+0
[10.399] (II) AMDGPU(0): [DRI2] Setup complete
[10.399] (II) AMDGPU(0): [DRI2]   DRI driver: radeonsi
[10.399] (II) AMDGPU(0): [DRI2]   VDPAU driver: radeonsi
[10.533] (II) AMDGPU(0): Front buffer pitch: 15872 bytes
[10.534] (II) AMDGPU(0): SYNC extension fences enabled
[10.534] (II) AMDGPU(0): Present extension enabled
[10.534] (==) AMDGPU(0): DRI3 enabled
[10.534] (==) AMDGPU(0): Backing store enabled
[10.534] (II) AMDGPU(0): Direct rendering enabled
[10.541] (II) AMDGPU(0): Use GLAMOR acceleration.
[10.541] (II) AMDGPU(0): Acceleration enabled
[10.541] (==) AMDGPU(0): DPMS enabled
[10.541] (==) AMDGPU(0): Silken mouse enabled
[10.541] (II) AMDGPU(0): Set up textured video (glamor)

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[Launchpad Bug Tracker]

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

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Confirmed

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[Launchpad Bug Tracker]

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

** Changed in: plasma-desktop (Ubuntu)
   Status: New => Confirmed

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 ff 

[Desktop-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver

[Launchpad Bug Tracker]

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

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

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

Title:
  Freeze on system-resume caused by kwin and amdgpu driver

Status in kwin package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  This is a well investigated bug by me.

  Problem: a black screen freeze occurs by suspend-resume process
  Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17
  Kernel version: default 5.3.10 or the mainline 5.4.0rc3
  xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works 
well

  This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is
  enabled in Plasma settings. Xrender is OK however I don't like screen
  tearing.

  On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the
  Gnome's compositor is enabled. (I don't know what is the default one
  there but I haven't disabled it)

  I think this is a Kwin / amdgpu driver related bug because of the
  differentiation. These can be fixed even in Kwin/opengl compositor not
  just in the amdgpu driver or in kernel.

  One possible solution: disable opengl compositor by suspend and re-
  enable it after login. Use fe.: Xrender before login / before the
  system restored from suspend.

  For Ubuntu's maintainers: Couldn't be this problem solved by a
  downstream solution? Maybe a proper script could be enough by resume
  and by suspend. There are a lot of bugs like this reported in
  freedesktop bugreport and the developers haven't got enough time for
  fix them fast enough.


  Syslog:

  Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 
8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 
08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 
00 00
  Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 
00010002
  Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 
0202 RCX: 046a
  Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 
0202 RDI: 0002
  Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: 
 R09: 94da76b2d170
  Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: 
b7b54274b70c R12: 94da76b2d000
  Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 
94da758d25d0 R15: 94da270d1400
  Oct 21 10:57:26 pc kernel: [ 9475.308861] FS:  7f2a1b9bea80() 
GS:94da87c4() knlGS:
  Oct 21 10:57:26 pc kernel: [ 9475.308863] CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 
00012c11 CR4: 003406e0
  Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace:
  Oct 21 10:57:26 pc kernel: [ 9475.308977]  
amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.308991]  commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309000]  ? commit_tail+0x50/0xc0 
[drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309009]  
drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309115]  amdgpu_dm_atomic_commit+0x95/0xa0 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309135]  drm_atomic_commit+0x4a/0x50 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309144]  
drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper]
  Oct 21 10:57:26 pc kernel: [ 9475.309159]  drm_mode_setcrtc+0x1cd/0x7a0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309234]  ? amdgpu_cs_wait_ioctl+0xd6/0x150 
[amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309249]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309262]  drm_ioctl_kernel+0xae/0xf0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309276]  drm_ioctl+0x234/0x3d0 [drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309290]  ? drm_mode_getcrtc+0x190/0x190 
[drm]
  Oct 21 10:57:26 pc kernel: [ 9475.309370]  amdgpu_drm_ioctl+0x4e/0x80 [amdgpu]
  Oct 21 10:57:26 pc kernel: [ 9475.309376]  do_vfs_ioctl+0x407/0x670
  Oct 21 10:57:26 pc kernel: [ 9475.309379]  ? do_futex+0x10f/0x1e0
  Oct 21 10:57:26 pc kernel: [ 9475.309382]  ksys_ioctl+0x67/0x90
  Oct 21 10:57:26 pc kernel: [ 9475.309384]  __x64_sys_ioctl+0x1a/0x20
  Oct 21 10:57:26 pc kernel: [ 9475.309388]  do_syscall_64+0x57/0x190
  Oct 21 10:57:26 pc kernel: [ 9475.309392]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b
  Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d 00 
64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff 

[Desktop-packages] [Bug 1851046] Re: Enable Last.fm provider

[Forage]

I just did a quick test with building the packages from the Ubuntu
repository with the single change of adding the "--enable-lastfm" build
parameter. After installing those packages and a reboot the Last.fm
account worked as supposed to.

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

Title:
  Enable Last.fm provider

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

Bug description:
  Since a while now GOA supports Last.fm accounts but for some reason this 
provider is excluded in the Ubuntu build parameters of this package.
  Is there a specific reason why this is not enabled? Would it be possible to 
enable this provider as well?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-online-accounts 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Nov  2 16:07:05 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-26 (1437 days ago)
  InstallationMedia: It
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to eoan on 2019-10-20 (13 days ago)

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

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

[Desktop-packages] [Bug 1851127] Re: app page shows no install progress

[Alan Pope  濾]

** Attachment added: "Screenshot from 2019-11-03 11-42-19.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851127/+attachment/5302434/+files/Screenshot%20from%202019-11-03%2011-42-19.png

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

Title:
  app page shows no install progress

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I just installed a couple of applications (bomb squad and android
  studio) and while installing, they show no install progress.

  Steps to reproduce

  Launch gnome-software
  Click an application from the front of G-S
  Click Install
  Fill in password

  Expected outcome

  I expect to be shown a progress bar, showing that installation is
  happening

  Actual outcome

  I see no progress, yet running `snap changes` in a terminal shows it is 
installing
  In addition, clicking "Install" again fails due to the install running.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  3 11:42:28 2019
  InstallationDate: Installed on 2019-10-27 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu10
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1851127] [NEW] app page shows no install progress

[Alan Pope  濾]

Public bug reported:

I just installed a couple of applications (bomb squad and android
studio) and while installing, they show no install progress.

Steps to reproduce

Launch gnome-software
Click an application from the front of G-S
Click Install
Fill in password

Expected outcome

I expect to be shown a progress bar, showing that installation is
happening

Actual outcome

I see no progress, yet running `snap changes` in a terminal shows it is 
installing
In addition, clicking "Install" again fails due to the install running.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-software 3.30.6-2ubuntu10
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  3 11:42:28 2019
InstallationDate: Installed on 2019-10-27 (6 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap3.30.6-2ubuntu10
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "Screenshot from 2019-11-03 11-42-13.png"
   
https://bugs.launchpad.net/bugs/1851127/+attachment/5302430/+files/Screenshot%20from%202019-11-03%2011-42-13.png

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

Title:
  app page shows no install progress

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I just installed a couple of applications (bomb squad and android
  studio) and while installing, they show no install progress.

  Steps to reproduce

  Launch gnome-software
  Click an application from the front of G-S
  Click Install
  Fill in password

  Expected outcome

  I expect to be shown a progress bar, showing that installation is
  happening

  Actual outcome

  I see no progress, yet running `snap changes` in a terminal shows it is 
installing
  In addition, clicking "Install" again fails due to the install running.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  3 11:42:28 2019
  InstallationDate: Installed on 2019-10-27 (6 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu10
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo

[Maxim Smih]

here is no such problem with the 5.0.0-15 kernel

** Description changed:

  Sometimes, when I turn off the computer, it hangs on the logo. I can not
  turn off the computer using alt + SysRq + REISUO. The light on the
  system unit continues to light, and the fan runs. This is a problem with
- kernel 5.0, 5.3.
+ kernel 5.0.0-15, 5.3.
  
- There is no such problem with the 4.15, 4.18.0.25 kernel. It happens
- that after 90 seconds it turns off. And with a new core, he writes that
- he will turn off after 90 seconds, but he will not turn off.
+ There is no such problem with the 4.15.0-66, 4.18.0.25 kernel. It
+ happens that after 90 seconds it turns off. And with a new core, he
+ writes that he will turn off after 90 seconds, but he will not turn off.
  
  Here is the error:
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message
  
  https://ibb.co/PcYvDLq
  https://ibb.co/4JMGwvC
  
  sudo dmesg|grep ACPI|less -  https://pastebin.com/PZxRGNyJ
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Пакет: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  CurrentDesktop: XFCE
  Дата: Четверг 5 09:44:35 2019 Дата
  установки: установлено в 2019-08 -09 (26 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 
(20190210)
  ProcEnviron:
   LANGUAGE = ru_UA: ru
   PATH = (пользовательский, нет пользователя)
   XDG_RUNTIME_ DIR = 
   LANG = ru_UA.UTF -8
   SHELL = / bin / bash
  SourcePackage: gvfs
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка)
  ---
  Тип проблемы: ошибка
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  AudioDevicesInUse:
   КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID
   / dev / snd / controlC0: макс. 1055 F  pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Установлен 2019-08-09 (37 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 
(20190210)
  IwConfig:
   enp0s25 без беспроводных расширений.
  
   enp7s4 нет беспроводных расширений.
  
   нет никаких беспроводных расширений.
  Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower
  Пакет: Linux (не установлен)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень 
= UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1
  ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18
  RelatedPackageV ersions:
   linux- restricted- modules- 4.15.0- 62-родовое N / A
   linux- backports- modules- 4.15.0 - 62-типовой N / A
   linux-прошивка 1.173.9
  RfKill:
  
  Теги: bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: нет журнала обновления (возможно, новая установка)
  Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 26.10.2015
  dmi. bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board. asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis. asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: 
svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: 
rn2820h: rvr: cvnHewlett- Packard: ct6: cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dvtwelet dv00 от компании HP
  :

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, when I turn off the computer, it hangs on the logo. I can
  not turn off the computer using alt + SysRq + REISUO. The light on the
  system unit continues to light, and the fan runs. This is a problem
  with kernel 5.0.0-15, 5.3.

  There is no such problem with the 4.15.0-66, 4.18.0.25 kernel. It
  happens that after 90 seconds it turns off. And with a new core, he
  writes that he will turn off after 90 seconds, but he will not turn
  off.

  Here is the error:
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq
  https://ibb.co/4JMGwvC

  sudo dmesg|grep ACPI|less -  https://pastebin.com/PZxRGNyJ

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Пакет: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  CurrentDesktop: XFCE
  Дата: Четверг 5 

[Desktop-packages] [Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo

[Maxim Smih]

here is no such problem with the 4.18.0.25 kernel. It happens that after
90 seconds it turns off. And with a new core, he writes that he will
turn off after 90 seconds, but he will not turn off.

** Description changed:

  Sometimes, when I turn off the computer, it hangs on the logo. I can not
  turn off the computer using alt + SysRq + REISUO. The light on the
  system unit continues to light, and the fan runs. This is a problem with
  kernel 5.0, 5.3.
  
- There is no such problem with the 4.15 kernel. It happens that after 90
- seconds it turns off. And with a new core, he writes that he will turn
- off after 90 seconds, but he will not turn off.
+ There is no such problem with the 4.15, 4.18.0.25 kernel. It happens
+ that after 90 seconds it turns off. And with a new core, he writes that
+ he will turn off after 90 seconds, but he will not turn off.
  
  Here is the error:
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message
  
  https://ibb.co/PcYvDLq
  https://ibb.co/4JMGwvC
  
  sudo dmesg|grep ACPI|less -  https://pastebin.com/PZxRGNyJ
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Пакет: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  CurrentDesktop: XFCE
  Дата: Четверг 5 09:44:35 2019 Дата
  установки: установлено в 2019-08 -09 (26 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 
(20190210)
  ProcEnviron:
   LANGUAGE = ru_UA: ru
   PATH = (пользовательский, нет пользователя)
   XDG_RUNTIME_ DIR = 
   LANG = ru_UA.UTF -8
   SHELL = / bin / bash
  SourcePackage: gvfs
  UpgradeStatus: журнал обновления отсутствует (возможно, новая установка)
  ---
  Тип проблемы: ошибка
  ApportVersion: 2.20.9-0ubuntu7.7
  Архитектура: amd64
  AudioDevicesInUse:
   КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID
   / dev / snd / controlC0: макс. 1055 F  pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Установлен 2019-08-09 (37 дней назад)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 
(20190210)
  IwConfig:
   enp0s25 без беспроводных расширений.
  
   enp7s4 нет беспроводных расширений.
  
   нет никаких беспроводных расширений.
  Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower
  Пакет: Linux (не установлен)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень 
= UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1
  ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18
  RelatedPackageV ersions:
   linux- restricted- modules- 4.15.0- 62-родовое N / A
   linux- backports- modules- 4.15.0 - 62-типовой N / A
   linux-прошивка 1.173.9
  RfKill:
  
  Теги: bionic
  Uname: Linux 4.15.0-62-generic x86_64
  UpgradeStatus: нет журнала обновления (возможно, новая установка)
  Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 26.10.2015
  dmi. bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F2 v01.60
  dmi.board. asset.tag: CZC8107S1Y
  dmi.board.name: 2820h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis. asset.tag: CZC8107S1Y
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: 
svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: 
rn2820h: rvr: cvnHewlett- Packard: ct6: cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dvtwelet dv00 от компании HP
  :

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1842865

Title:
  Xubuntu 18.04 sometimes freezes when turned on on logo

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Sometimes, when I turn off the computer, it hangs on the logo. I can
  not turn off the computer using alt + SysRq + REISUO. The light on the
  system unit continues to light, and the fan runs. This is a problem
  with kernel 5.0, 5.3.

  There is no such problem with the 4.15, 4.18.0.25 kernel. It happens
  that after 90 seconds it turns off. And with a new core, he writes
  that he will turn off after 90 seconds, but he will not turn off.

  Here is the error:
  info: task systemd shutdown:1 blocked for more than 120 seconds
  Not tainted 5.0.0-20-generic #21-Ubuntu
  «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

  https://ibb.co/PcYvDLq
  https://ibb.co/4JMGwvC

  sudo dmesg|grep ACPI|less -  https://pastebin.com/PZxRGNyJ

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Пакет: gvfs 1.36.1-0ubuntu1.3.3
  ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64