date:20200214

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

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

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

Title:
  gnome-shell freezes and must be killed from console

Status in gnome-shell package in Ubuntu:
  Expired

Bug description:
  This has been happening more often recently.  I can't point to any
  particular thing triggering it.  I am hopeful some useful information
  will be contained in the debugging info.  When this happens,
  everything on my screen freezes aside from the mouse cursor.  I can
  use ctrl-alt-Fx to get to another TTY, log in, and at that point I
  have to kill -9 gnome-shell.  When I do this, it seems to take several
  running processes (like Firefox, slack) with it, but not all of them.
  When I return to my X VT, gnome-shell restarts and some applications
  are felt running.  I have no idea why.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Dec 16 10:06:17 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-12-03 (12 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  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/1856596/+subscriptions

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

[Desktop-packages] [Bug 1856465] Re: Apport icon did not appear in gnome even though it was running and displaying windows.

[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]

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

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

Title:
  Apport icon did not appear in gnome even though it was running and
  displaying windows.

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

Bug description:
  When I attempted to send a bug report for gnome-control-center via
  terminal, the Apport window appeared saying "Collecting information".
  However, the gnome side-dock did not display the apport logo at all,
  only the system monitor, systems-settings, and every other running
  program with windows being displayed.

  I expected the Apport icon to appear on the side-dock. It never did,
  and I was unable to see the report or send it as a result, except by
  opening Notifications and clicking "Ubuntu is ready".

  This issue occurred at around 11:54 AM, EDT, on December 15, 2019.

  Description:  Ubuntu 19.10
  Release:  19.10

  gnome-shell:
Installed: 3.34.1+git20191024-1ubuntu1~19.10.1
Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1
Version table:
   *** 3.34.1+git20191024-1ubuntu1~19.10.1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.34.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 11:54:07 2019
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-11-20 (24 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1861408] Re: firefox apparmor messages

2020-02-14 Thread John Johansen

I should further note that this needs kernel patches to be fixed.

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

Title:
  firefox apparmor messages

Status in apparmor package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
  19.3.

  i see there is newer ubuntu version in
  
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
  , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
  apparmor.

  i have not found a page for firefox bugs in linux mint sites, so i
  belive i should report here. but i have also asked about that in linux
  mint's irc and then github.

  i have enabled apparmor for firefox and see these types of messages in
  syslog:

  Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
  pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")

  Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5525.077960] audit: type=1400 audit(1580226276.440:27):
  apparmor="DENIED" operation="capable"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
  comm="firefox" capability=21  capname="sys_admin"

  Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/RealtimeKit1"
  interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
  name="org.freedesktop.RealtimeKit1" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
  member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/Private/RemoteVolumeMonitor"
  interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
  mask="send" name=":1.35" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="ListMounts2" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="LookupMount" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
  pid=15948 comm="/usr/lib/firefox/firefox "
  label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/hostname1"
  interface="org.freedesktop.DBus.Properties" member="GetAll"
  mask="send" name=":1.120" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
  peer_label="unconfined"

  Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
  member="Change" mask="send" name="ca.desrt.dconf" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
  peer_label="unconfined"

  Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
  [10131.880788] audit: type=1400 audit(1580237490.777:123):
  apparmor="DENIED" operation="open"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
  comm="firefox" requested_mask="wrc" denied_mask="wrc" fsuid=1000
  ouid=1000

  these appeared while saving a file:

  Jan 30 11:08:28 dinar-HP-Pavilion-g7-Notebook-PC

[Desktop-packages] [Bug 1861408] Re: firefox apparmor messages

2020-02-14 Thread John Johansen

Firefox uses cap sys_admin to set up its sandbox, which is extremely
unfortunate but required on linux to be able to set up the
user_namespace, do the chroot etc. Current the LSM and user namespaces
don't interact as well as they should.

AppArmor can NOT properly determine the policy namespace that it should
be in with the user_namespace after firefox enters its sandbox. This
result in the cap_sys admin messages

This is a known problem and we are working on it. At the moment we
recommend granting the capability in the profile and letting firefox
setup its sandbox. Unfortunately this means you can't guarantee the rest
of the program isn't doing things it shouldn't.

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

Title:
  firefox apparmor messages

Status in apparmor package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
  19.3.

  i see there is newer ubuntu version in
  
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
  , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
  apparmor.

  i have not found a page for firefox bugs in linux mint sites, so i
  belive i should report here. but i have also asked about that in linux
  mint's irc and then github.

  i have enabled apparmor for firefox and see these types of messages in
  syslog:

  Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
  pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")

  Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5525.077960] audit: type=1400 audit(1580226276.440:27):
  apparmor="DENIED" operation="capable"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
  comm="firefox" capability=21  capname="sys_admin"

  Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/RealtimeKit1"
  interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
  name="org.freedesktop.RealtimeKit1" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
  member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/Private/RemoteVolumeMonitor"
  interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
  mask="send" name=":1.35" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="ListMounts2" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="LookupMount" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
  pid=15948 comm="/usr/lib/firefox/firefox "
  label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/hostname1"
  interface="org.freedesktop.DBus.Properties" member="GetAll"
  mask="send" name=":1.120" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
  peer_label="unconfined"

  Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/ca/desrt/dconf/Writer/user"

[Desktop-packages] [Bug 1863391] [NEW] GNOME fractional scaling: fullscreen video misbehaves

2020-02-14 Thread pheidrias

Public bug reported:

When scaling the desktop to e.g. 150%, fullscreen video does seem to
trigger constant changes of the scaling factor: the system switches
every 0.5s from 150% to 100% to 200% or things like those.

The problem does not occur, when there is another windows present (e.g.
a "always-on-top" terminal windows).

Also, KDE doesn't have this problem.

The problem exists in freshly installed 19.10 and 20.04, too. I couldn't find 
any reason, why sometimes firefox fullscreen videos do work and sometimes not. 
Video playback (e.g. GNOME video player or VLC) does not work properly in 
19.10, whereas it works most of the time in 20.04.

How can I help to dig into this?

1) Ubuntu 19.10, 20.04
2) latest available (problem exists since several weeks)
3) What you expected to happen: fullscreen video playback in scaled mode
4) What happened instead: screen starts changing (randomly?) the scaling factor 
or at least this is the impression one gets

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


** Tags: 20.04

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

Title:
  GNOME fractional scaling: fullscreen video misbehaves

Status in metacity package in Ubuntu:
  New

Bug description:
  When scaling the desktop to e.g. 150%, fullscreen video does seem to
  trigger constant changes of the scaling factor: the system switches
  every 0.5s from 150% to 100% to 200% or things like those.

  The problem does not occur, when there is another windows present
  (e.g. a "always-on-top" terminal windows).

  Also, KDE doesn't have this problem.

  The problem exists in freshly installed 19.10 and 20.04, too. I couldn't find 
any reason, why sometimes firefox fullscreen videos do work and sometimes not. 
  Video playback (e.g. GNOME video player or VLC) does not work properly in 
19.10, whereas it works most of the time in 20.04.

  How can I help to dig into this?

  1) Ubuntu 19.10, 20.04
  2) latest available (problem exists since several weeks)
  3) What you expected to happen: fullscreen video playback in scaled mode
  4) What happened instead: screen starts changing (randomly?) the scaling 
factor or at least this is the impression one gets

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

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

[Desktop-packages] [Bug 1863390] [NEW] GPU lockup ring 0 stalled for more than X msec

2020-02-14 Thread Jamie Bainbridge

Public bug reported:

Since the update:

 xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic;

which resulted from:

 https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-
ati/+bug/1841718

I've experienced GPU freezes where all video becomes unresponsive, both
Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to full. I am
still able to access the system via SSH.

Sometimes dmesg ends up full of this message repeating over and over:

 radeon :01:00.0: ring 0 stalled for more than 24040msec
 radeon :01:00.0: GPU lockup (current fence id 0x9e44 last 
fence id 0x9e49 on ring 0)

I sometimes get a few GPU soft reset which seem to fail in drm(?):

 radeon :01:00.0: Saved 110839 dwords of commands on ring 0.
 radeon :01:00.0: GPU softreset: 0x0008
 ...
 radeon :01:00.0: Wait for MC idle timedout !
 radeon :01:00.0: Wait for MC idle timedout !
 [drm] PCIE GART of 1024M enabled (table at 0x00162000).
 radeon :01:00.0: WB enabled 
 radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 
and cpu addr 0x725651ad
 radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c 
and cpu addr 0xc3678ed8
 radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 
and cpu addr 0xdbd9e01b
 [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x8504)=0xCAFEDEAD)
 [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume

Even if the above reset doesn't happen, this freeze always results in a
unable to handle page fault" BUG in radeon_ring_backup, entered from
various call paths, eg:

 BUG: unable to handle page fault for address: bc2d80574ffc
 ...
 Oops:  [#1] SMP PTI 
 CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic 
#202001262030
 Workqueue: radeon-crtc radeon_flip_work_func [radeon]
 RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon]
 Call Trace:
  radeon_gpu_reset+0xc3/0x2f0 [radeon]
  radeon_flip_work_func+0x1f3/0x250 [radeon]
  ? __schedule+0x2e0/0x760
  process_one_work+0x1b5/0x370
  worker_thread+0x50/0x3d0
  kthread+0x104/0x140
  ? process_one_work+0x370/0x370
  ? kthread_park+0x90/0x90
  ret_from_fork+0x35/0x40

or:

 BUG: unable to handle page fault for address: c03901000ffc
 ...
 Oops:  [#1] SMP PTI

 CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic #30~18.04.1-Ubuntu
 RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon]
 Call Trace:
  radeon_gpu_reset+0xb9/0x340 [radeon]
  ? dma_fence_wait_timeout+0x48/0x110
  ? reservation_object_wait_timeout_rcu+0x19d/0x340
  radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon]
  radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon]
  ? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
  drm_ioctl_kernel+0xb0/0x100 [drm]
  drm_ioctl+0x389/0x450 [drm]
  ? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  ? __switch_to_asm+0x34/0x70
  ? __switch_to_asm+0x40/0x70
  radeon_drm_ioctl+0x4f/0x80 [radeon]
  do_vfs_ioctl+0xa9/0x640
  ? __schedule+0x2b0/0x670
  ksys_ioctl+0x75/0x80
  __x64_sys_ioctl+0x1a/0x20
  do_syscall_64+0x5a/0x130
  entry_SYSCALL_64_after_hwframe+0x44/0xa9

I've tried both 5.3.0-28-generic and 5.5.0-050500-generic from kernel-
ppa but that made no difference. It appears to be a bug in radeon.

Nothing specific makes this happen, just regular usage with a
compositing window manager. I'm not playing games or particularly
exercising the GPU. The last two times I was just reading in web
browser. It's also happened in the middle of the night while I was
asleep. Sometimes I have a few days uptime, sometimes it happens in less
than 24 hours from boot.

This never happened before the radeon update mentioned on the first
line.

I'll attach two files of dmesg output. As per
https://wiki.ubuntu.com/X/Troubleshooting/Freeze I've installed and
started apport for next time it happens.

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

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

Title:
  GPU lockup ring 0 stalled for more than X msec

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

Bug description:
  Since the update:

   xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic;

  which resulted from:

   https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-
  ati/+bug/1841718

  I've experienced GPU freezes where all video becomes unresponsive,
  both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to
  full. I am still able to access the system via SSH.

  Sometimes dmesg ends up full of this message repeating over and over:

   radeon :01:00.0: ring

[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec

2020-02-14 Thread Jamie Bainbridge

** Attachment added: "dmesg-2020-02-14.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+attachment/5328273/+files/dmesg-2020-02-14.txt

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

Title:
  GPU lockup ring 0 stalled for more than X msec

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

Bug description:
  Since the update:

   xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic;

  which resulted from:

   https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-
  ati/+bug/1841718

  I've experienced GPU freezes where all video becomes unresponsive,
  both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to
  full. I am still able to access the system via SSH.

  Sometimes dmesg ends up full of this message repeating over and over:

   radeon :01:00.0: ring 0 stalled for more than 24040msec
   radeon :01:00.0: GPU lockup (current fence id 0x9e44 last 
fence id 0x9e49 on ring 0)

  I sometimes get a few GPU soft reset which seem to fail in drm(?):

   radeon :01:00.0: Saved 110839 dwords of commands on ring 0.
   radeon :01:00.0: GPU softreset: 0x0008
   ...
   radeon :01:00.0: Wait for MC idle timedout !
   radeon :01:00.0: Wait for MC idle timedout !
   [drm] PCIE GART of 1024M enabled (table at 0x00162000).
   radeon :01:00.0: WB enabled 
   radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 
and cpu addr 0x725651ad
   radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c 
and cpu addr 0xc3678ed8
   radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 
and cpu addr 0xdbd9e01b
   [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x8504)=0xCAFEDEAD)
   [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume

  Even if the above reset doesn't happen, this freeze always results in
  a unable to handle page fault" BUG in radeon_ring_backup, entered from
  various call paths, eg:

   BUG: unable to handle page fault for address: bc2d80574ffc
   ...
   Oops:  [#1] SMP PTI 
   CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic 
#202001262030
   Workqueue: radeon-crtc radeon_flip_work_func [radeon]
   RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xc3/0x2f0 [radeon]
radeon_flip_work_func+0x1f3/0x250 [radeon]
? __schedule+0x2e0/0x760
process_one_work+0x1b5/0x370
worker_thread+0x50/0x3d0
kthread+0x104/0x140
? process_one_work+0x370/0x370
? kthread_park+0x90/0x90
ret_from_fork+0x35/0x40

  or:

   BUG: unable to handle page fault for address: c03901000ffc
   ...
   Oops:  [#1] SMP PTI

   CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic 
#30~18.04.1-Ubuntu
   RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xb9/0x340 [radeon]
? dma_fence_wait_timeout+0x48/0x110
? reservation_object_wait_timeout_rcu+0x19d/0x340
radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon]
radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
drm_ioctl_kernel+0xb0/0x100 [drm]
drm_ioctl+0x389/0x450 [drm]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
radeon_drm_ioctl+0x4f/0x80 [radeon]
do_vfs_ioctl+0xa9/0x640
? __schedule+0x2b0/0x670
ksys_ioctl+0x75/0x80
__x64_sys_ioctl+0x1a/0x20
do_syscall_64+0x5a/0x130
entry_SYSCALL_64_after_hwframe+0x44/0xa9

  I've tried both 5.3.0-28-generic and 5.5.0-050500-generic from kernel-
  ppa but that made no difference. It appears to be a bug in radeon.

  Nothing specific makes this happen, just regular usage with a
  compositing window manager. I'm not playing games or particularly
  exercising the GPU. The last two times I was just reading in web
  browser. It's also happened in the middle of the night while I was
  asleep. Sometimes I have a few days uptime, sometimes it happens in
  less than 24 hours from boot.

  This never happened before the radeon update mentioned on the first
  line.

  I'll attach two files of dmesg output. As per
  https://wiki.ubuntu.com/X/Troubleshooting/Freeze I've installed and
  started apport for next time it happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+subscriptions

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

[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec

2020-02-14 Thread Jamie Bainbridge

** Attachment added: "dmesg-2020-02-15.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+attachment/5328274/+files/dmesg-2020-02-15.txt

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

Title:
  GPU lockup ring 0 stalled for more than X msec

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

Bug description:
  Since the update:

   xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic;

  which resulted from:

   https://bugs.launchpad.net/fedora/+source/xserver-xorg-video-
  ati/+bug/1841718

  I've experienced GPU freezes where all video becomes unresponsive,
  both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to
  full. I am still able to access the system via SSH.

  Sometimes dmesg ends up full of this message repeating over and over:

   radeon :01:00.0: ring 0 stalled for more than 24040msec
   radeon :01:00.0: GPU lockup (current fence id 0x9e44 last 
fence id 0x9e49 on ring 0)

  I sometimes get a few GPU soft reset which seem to fail in drm(?):

   radeon :01:00.0: Saved 110839 dwords of commands on ring 0.
   radeon :01:00.0: GPU softreset: 0x0008
   ...
   radeon :01:00.0: Wait for MC idle timedout !
   radeon :01:00.0: Wait for MC idle timedout !
   [drm] PCIE GART of 1024M enabled (table at 0x00162000).
   radeon :01:00.0: WB enabled 
   radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 
and cpu addr 0x725651ad
   radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c 
and cpu addr 0xc3678ed8
   radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 
and cpu addr 0xdbd9e01b
   [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed 
(scratch(0x8504)=0xCAFEDEAD)
   [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume

  Even if the above reset doesn't happen, this freeze always results in
  a unable to handle page fault" BUG in radeon_ring_backup, entered from
  various call paths, eg:

   BUG: unable to handle page fault for address: bc2d80574ffc
   ...
   Oops:  [#1] SMP PTI 
   CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic 
#202001262030
   Workqueue: radeon-crtc radeon_flip_work_func [radeon]
   RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xc3/0x2f0 [radeon]
radeon_flip_work_func+0x1f3/0x250 [radeon]
? __schedule+0x2e0/0x760
process_one_work+0x1b5/0x370
worker_thread+0x50/0x3d0
kthread+0x104/0x140
? process_one_work+0x370/0x370
? kthread_park+0x90/0x90
ret_from_fork+0x35/0x40

  or:

   BUG: unable to handle page fault for address: c03901000ffc
   ...
   Oops:  [#1] SMP PTI

   CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic 
#30~18.04.1-Ubuntu
   RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon]
   Call Trace:
radeon_gpu_reset+0xb9/0x340 [radeon]
? dma_fence_wait_timeout+0x48/0x110
? reservation_object_wait_timeout_rcu+0x19d/0x340
radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon]
radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
drm_ioctl_kernel+0xb0/0x100 [drm]
drm_ioctl+0x389/0x450 [drm]
? radeon_gem_busy_ioctl+0x80/0x80 [radeon]
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
? __switch_to_asm+0x34/0x70
? __switch_to_asm+0x40/0x70
radeon_drm_ioctl+0x4f/0x80 [radeon]
do_vfs_ioctl+0xa9/0x640
? __schedule+0x2b0/0x670
ksys_ioctl+0x75/0x80
__x64_sys_ioctl+0x1a/0x20
do_syscall_64+0x5a/0x130
entry_SYSCALL_64_after_hwframe+0x44/0xa9

  I've tried both 5.3.0-28-generic and 5.5.0-050500-generic from kernel-
  ppa but that made no difference. It appears to be a bug in radeon.

  Nothing specific makes this happen, just regular usage with a
  compositing window manager. I'm not playing games or particularly
  exercising the GPU. The last two times I was just reading in web
  browser. It's also happened in the middle of the night while I was
  asleep. Sometimes I have a few days uptime, sometimes it happens in
  less than 24 hours from boot.

  This never happened before the radeon update mentioned on the first
  line.

  I'll attach two files of dmesg output. As per
  https://wiki.ubuntu.com/X/Troubleshooting/Freeze I've installed and
  started apport for next time it happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1863390/+subscriptions

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

[Desktop-packages] [Bug 1861408] Re: firefox apparmor messages

2020-02-14 Thread dinar qurbanov

i asked about sys_admin capability and got some answers:
https://groups.google.com/forum/#!topic/mozilla.dev.platform/UK4nm7MtTxQ

(i wanted to ask in firefox-dev mailing list but the dev-platform list
was said about as more appropriate).

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

Title:
  firefox apparmor messages

Status in apparmor package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
  19.3.

  i see there is newer ubuntu version in
  
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
  , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
  apparmor.

  i have not found a page for firefox bugs in linux mint sites, so i
  belive i should report here. but i have also asked about that in linux
  mint's irc and then github.

  i have enabled apparmor for firefox and see these types of messages in
  syslog:

  Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
  pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")

  Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5525.077960] audit: type=1400 audit(1580226276.440:27):
  apparmor="DENIED" operation="capable"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
  comm="firefox" capability=21  capname="sys_admin"

  Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/RealtimeKit1"
  interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
  name="org.freedesktop.RealtimeKit1" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
  member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/Private/RemoteVolumeMonitor"
  interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
  mask="send" name=":1.35" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="ListMounts2" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="LookupMount" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
  pid=15948 comm="/usr/lib/firefox/firefox "
  label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")

  Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/hostname1"
  interface="org.freedesktop.DBus.Properties" member="GetAll"
  mask="send" name=":1.120" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
  peer_label="unconfined"

  Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
  member="Change" mask="send" name="ca.desrt.dconf" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
  peer_label="unconfined"

  Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
  [10131.880788] audit: type=1400 audit(1580237490.777:123):
  apparmor="DENIED" operation="open"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
  name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

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

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

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  In Progress
Status in asterisk package in Ubuntu:
  In Progress
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  In Progress
Status in dballe package in Ubuntu:
  In Progress
Status in gambas3 package in Ubuntu:
  In Progress
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  In Progress
Status in gnunet package in Ubuntu:
  In Progress
Status in hoel package in Ubuntu:
  In Progress
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  In Progress
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  In Progress
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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

[Desktop-packages] [Bug 1863219] Re: WiFi module RTL8723DE not supported @live / installed session

2020-02-14 Thread Brian Murray

You could test preview images of 20.04 by downloading them from here:

http://cdimage.ubuntu.com/ubuntu/daily-live/current/

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

** No longer affects: kernel-package (Ubuntu)

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

Title:
  WiFi module RTL8723DE not supported @live / installed session

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi
  I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some 
wireless connectivity problems with Realtek chips.
  My system compatible with rtl8723de wifi driver module. Laptop model no HP 
14q-cs0009tu.
  Ubuntu live session can’t detect the card nor the post-installed OS does.
  Therefore, no wifi switch/icon.
  I would hope Ubuntu 20.04 LTS natively support this wireless chip.
  regards.

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

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

[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

2020-02-14 Thread Benoit Tainturier

Adam: I am using Ubuntu 19.10, LibreOffice 6.3.4.2, and a default session (X11).
Actually, copy/paste worked really better on the 1st of February and during the 
days after. I thought it was fixed! Today, the issue is exactly the same as 
before.

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

Title:
  [X11] copy/paste (clipboard) is broken in Ubuntu 19.10

Status in LibreOffice:
  Confirmed
Status in Mutter:
  Fix Released
Status in libreoffice package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Triaged
Status in libreoffice source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Triaged

Bug description:
  I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10.

  In this environment, copy/cut/paste often fails.  Specifically, the
  paste command sometimes does not paste the text that was cut/copied
  most recently.  Instead, it pastes text that was cut/copied at some
  prior time.

  I use LibreOffice Writer a lot, and I now see this problem very often,
  i.e. many times every day.

  There is some discussion of the problem here:

 https://ask.libreoffice.org/en/question/213510/copypaste-issues-
  libreoffice-calc/

  Several posters there say that they are also using Ubuntu 19.10.

  Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager:

 https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34
  -Clipboard-Manager

  It seems like that could be related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

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

[Desktop-packages] [Bug 1175882] Re: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images)

2020-02-14 Thread Bug Watch Updater

** Changed in: df-libreoffice
   Status: New => Incomplete

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

Title:
  Hangs while modifying document (after completion of paste from Wep
  Page with Multiple Images)

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Follow these steps to bring LibreOffice writer to a crawl:

  1) Allow this page to fully load in firefox (in a new tab):
  http://www.amorosity.com/SlingBlade/

  2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire
  page's contents into memory).

  3) Open LibreOffice writer, and paste your clipboard into it.

  I don't mind waiting for all the images to get loaded. The main point
  here, is that performance is not only slow during the initial paste.
  After the images get fully loaded into the word processing document,
  interacting with the document becomes impractical. Everything you try
  to do makes the application hang for several seconds.

  I have 4 gigabytes of RAM available for LibreOffice writer to use as
  it wishes, but it must be using some type of swap file (instead) while
  I'm modifying this large document. However, I have a really fast
  solid-state hard drive, so you'd think that even that would be fast on
  my machine.

  My machine should have the specs to enable me the ability to handle
  converting this large web page into a word processing document.

  Yes there are other ways to achieve what I'm trying to do, but this
  bug is about how LibreOffice can't handle the job. If it was
  programmed just right, it would make use of the resources my computer
  would gladly provide it, and scale up to this rather intensive task.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-writer 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May  2 23:09:24 2013
  InstallationDate: Installed on 2013-04-02 (31 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+subscriptions

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

[Desktop-packages] [Bug 1863282] Re: libreoffice menu bar disappeared

2020-02-14 Thread Cuyo

Hi
i think i can wait for 20.04 in April. Meanwhile libreoffice-gtk3 library 
restores menu bar.
Thanks.

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

Title:
  libreoffice  menu bar disappeared

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Last kde neon 18.04 update Libreoffice menu bar disappeared. Uninstall 
libreoffice-kde & libreoffice-kde4 resolve problem, but need to install 
libreoffice-gtk3.
  KDE neon User Edition 5.18 18.04
  libreoffice-kde 1:6.0.7-0ubuntu0.18.04.10
  libreoffice-kde4 1:6.0.7-0ubuntu0.18.04.10

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

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

[Desktop-packages] [Bug 1175882]

2020-02-14 Thread Arivleone

Thanks for reporting the problem.
I can't reproduce in 
Version: 6.3.4.2
Build ID: 60da17e045e08f1793c57c00ba83cdfce946d0aa
CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: kde5; 
Locale: id-ID (id_ID.UTF-8); UI-Language: en-US
Calc: threaded

and

Version: 7.0.0.0.alpha0+
Build ID: 4ff12ba6f4639c73587f2bb58afcc3ca6fb30105
CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: kf5; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-01-24_21:09:14
Locale: id-ID (id_ID.UTF-8); UI-Language: en-US
Calc: threaded

I am using KDE, when I try to reproduce, the Writer went to laggy, but
it didn't locks up the entire desktop. I think it's normal, because we
using amount of memory to copy the huge of content. Should I change it
to RESOLVED NOTABUG? I change to NEEDINFO for a while

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

Title:
  Hangs while modifying document (after completion of paste from Wep
  Page with Multiple Images)

Status in LibreOffice:
  Incomplete
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  Follow these steps to bring LibreOffice writer to a crawl:

  1) Allow this page to fully load in firefox (in a new tab):
  http://www.amorosity.com/SlingBlade/

  2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire
  page's contents into memory).

  3) Open LibreOffice writer, and paste your clipboard into it.

  I don't mind waiting for all the images to get loaded. The main point
  here, is that performance is not only slow during the initial paste.
  After the images get fully loaded into the word processing document,
  interacting with the document becomes impractical. Everything you try
  to do makes the application hang for several seconds.

  I have 4 gigabytes of RAM available for LibreOffice writer to use as
  it wishes, but it must be using some type of swap file (instead) while
  I'm modifying this large document. However, I have a really fast
  solid-state hard drive, so you'd think that even that would be fast on
  my machine.

  My machine should have the specs to enable me the ability to handle
  converting this large web page into a word processing document.

  Yes there are other ways to achieve what I'm trying to do, but this
  bug is about how LibreOffice can't handle the job. If it was
  programmed just right, it would make use of the resources my computer
  would gladly provide it, and scale up to this rather intensive task.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libreoffice-writer 1:4.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May  2 23:09:24 2013
  InstallationDate: Installed on 2013-04-02 (31 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401)
  MarkForUpload: True
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+subscriptions

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

[Desktop-packages] [Bug 1846940]

2020-02-14 Thread Tim Passingham

Until prompted by the status change (mentioning 6.3.4) on this I hadn't
checked it, expecting to have to wait for 6.4 on ubuntu.

I can confirm it's fixed in Version: 6.3.5.1
Build ID: 1:6.3.5~rc1-0ubuntu0.19.10.1~lo1
CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: x11; 
Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB
Calc: threaded

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

Title:
  [upstream] Loop in libreoffice-calc when scrolling to top of
  spreadsheet

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

Bug description:
  Have a spreadsheet used in many past release of calc that is now
  failing.  When opening this sheet and if not currently at the top of
  the sheet using the mouse wheel to move to the top (top line to the
  top of the window) soffice.bin goes to 100% cpu and stays there.
  Can't use the mouse wheel to move off of the top line.  Can move off
  the top line by using the mouse and scroll bar.  As soon as you are
  off the top line the loop in soffice.bin stops.  This is the only
  sheet I can find that fails but it does fail on this laptop and also
  my desktop which is also running Ubuntu 19.10/libreoffice-
  calc-6.3.2.2.  Adding failing spreadsheet file to this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice-calc 1:6.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  6 06:35:42 2019
  InstallationDate: Installed on 2019-10-03 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1846940/+subscriptions

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

[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-02-14 Thread Eric Desrochers

** Description changed:

+ 
+ [Impact]
+ [Test Case]
+ [Potential Regression]
+ 
+ [Other informations]
+ 
+ * Upstream bug[0] and fix[1]:
+ 
+ https://bugzilla.redhat.com/show_bug.cgi?id=1575944
+ https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/f03ae35
+ 
+ * Only affectinb Bionic:
+ 
+ $ git describe --contains f03ae35
+ 1.10.8~2
+ 
+ $ rmadison network-manager
+ ==> network-manager | 1.10.6-2ubuntu1.2   | bionic-updates
+ network-manager | 1.20.4-2ubuntu2.2   | eoan-updates   
+ network-manager | 1.22.4-1ubuntu2 | focal
+ 
+ [Original description]
  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.
-  
+ 
  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux
-  
- Machine Type = s390x 
-  
+ 
+ Machine Type = s390x
+ 
  ---Debugger---
  A debugger is not configured
-  
+ 
  ---Steps to Reproduce---
-  When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
+  When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface
  
  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface
  
  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode
  
- root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
+ root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121
  
  [ethernet]
  mac-address-blacklist=
  
  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0
  
  [ipv4]
  dns-search=
  method=auto
  
  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto
  
  From /var/log/syslog, we can see ip got assigned:
  
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1
  
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
- link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
- inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
-valid_lft 353sec preferred_lft 353sec
- inet6 fe80::ff:feb3:b522/64 scope link 
-valid_lft forever preferred_lft forever
- 
+ link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
+ inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
+    valid_lft 353sec preferred_lft 353sec
+ inet6 fe80::ff:feb3:b522/64 scope link
+    valid_lft forever preferred_lft forever
  
  
+++
  Bond interface, ipv4 automatic mode and ipv6 manual mode
  
- root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
+ root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300
  
  [ethernet]
  mac-address-blacklist=
  
  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0
  
  [ipv4]
  dns-search=
  method=auto
  
  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual
  
  No automatic ip assigned to ipv4 and no requests to dhcp server seen in 
/var/log/syslog
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
- link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
- inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute 
-valid_lft forever preferred_lft forever
- 
+ link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
+ inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute
+    valid_lft forever preferred_lft forever
  
  ==> Correct LP-Package

[Desktop-packages] [Bug 1846940]

2020-02-14 Thread Libreoffice-commits

Xisco Fauli committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/0d3d40b2668c879d8deb3b39f7c243e22b70bdcb

tdf#121963: Add unittest

It will be available in 7.0.0.

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

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

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

Title:
  [upstream] Loop in libreoffice-calc when scrolling to top of
  spreadsheet

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

Bug description:
  Have a spreadsheet used in many past release of calc that is now
  failing.  When opening this sheet and if not currently at the top of
  the sheet using the mouse wheel to move to the top (top line to the
  top of the window) soffice.bin goes to 100% cpu and stays there.
  Can't use the mouse wheel to move off of the top line.  Can move off
  the top line by using the mouse and scroll bar.  As soon as you are
  off the top line the loop in soffice.bin stops.  This is the only
  sheet I can find that fails but it does fail on this laptop and also
  my desktop which is also running Ubuntu 19.10/libreoffice-
  calc-6.3.2.2.  Adding failing spreadsheet file to this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice-calc 1:6.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  6 06:35:42 2019
  InstallationDate: Installed on 2019-10-03 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1846940/+subscriptions

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

[Desktop-packages] [Bug 1846940]

2020-02-14 Thread Libreoffice-commits

Xisco Fauli committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/2f9b7f4d7d35d0e2d85132792f8c74c54f05d6c1

tdf#121963: Add unittest (part 2)

It will be available in 7.0.0.

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

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

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

Title:
  [upstream] Loop in libreoffice-calc when scrolling to top of
  spreadsheet

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

Bug description:
  Have a spreadsheet used in many past release of calc that is now
  failing.  When opening this sheet and if not currently at the top of
  the sheet using the mouse wheel to move to the top (top line to the
  top of the window) soffice.bin goes to 100% cpu and stays there.
  Can't use the mouse wheel to move off of the top line.  Can move off
  the top line by using the mouse and scroll bar.  As soon as you are
  off the top line the loop in soffice.bin stops.  This is the only
  sheet I can find that fails but it does fail on this laptop and also
  my desktop which is also running Ubuntu 19.10/libreoffice-
  calc-6.3.2.2.  Adding failing spreadsheet file to this bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libreoffice-calc 1:6.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  6 06:35:42 2019
  InstallationDate: Installed on 2019-10-03 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1846940/+subscriptions

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

[Desktop-packages] [Bug 1849859] Re: smb printing fails

I'm updating focal to 4.11.5 (hoping debian will update to 4.11.6 soon,
and will check again how printing is working in this release. If it
still fails, I'll grab the patches I saw being discussed upstream and
apply them, and then I will have something I can start preparing as an
SRU.

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

Title:
  smb printing fails

Status in cups package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in system-config-printer package in Ubuntu:
  Confirmed

Bug description:
  when I connect to smb server (nas) permanently appears

  "Error while getting peer-to-peer dbus connection: Operation was
  cancelled"

  The printer at this NAS doesn't work too.

  "held for authentication KeyError: 'auth-info-required'"

  The same printer at usb port works fine.

  Ubuntu development version 20.04
  system-config-printer version 1.5.11-4ubuntu1
  smbclient version 2:4.10.7+dfsg-0ubuntu3

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

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

[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-02-14 Thread Edwin Peer

Regarding your question about LLDP and IPv6...

The default Ubuntu 18.04.3 configuration has an IPv6 enabled kernel, but
the interface only has the default link local address configured. I've
seen it do router solicitation on link state changes and periodically
thereafter. I think I recall seeing somewhere above that you were going
to try without IPv6. Have you seen different behavior with IPv6
disabled?

I don't expect to see LLDP because I have the two NICs wired directly to
each other, back to back. I'm not running any LLDP daemon on the host.

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

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

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.
  D[00:04:56.425845] Detected Rx sequence error.
  D[00:04:57.929209] Detected Rx sequence error.
  [00:05:04.529548] Benchmark complete.
  Benchmark rate summary:
Num received samples: 2995435936
Num dropped samples:  4622800
Num overruns detected:0
Num transmitted samples:  3008276544
Num sequence errors (Tx): 0
Num sequence errors (Rx): 15
Num underruns detected:   0
Num late commands:0
Num timeouts (Tx):0
Num timeouts (Rx):0
  Done!

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$

  
  In this particular case description, the nodes are USRP x310s. However, we 
have the same issue with N210 nodes dropping samples connected to the BCM57416 
NetXtreme-E Dual-Media 10G RDMA Ethernet device.

  There is no problem

[Desktop-packages] [Bug 1863376] [NEW] Seg Fault during version check

2020-02-14 Thread Clinton H

Public bug reported:

1) Ubuntu 19.10
2) 3.34.1
3) No seg fault.
4) Seg fault occurred when checking nautilus version.

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

** Attachment added: "gnome_version_seg_fault.png"
   
https://bugs.launchpad.net/bugs/1863376/+attachment/5328235/+files/gnome_version_seg_fault.png

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

Title:
  Seg Fault during version check

Status in nautilus package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) 3.34.1
  3) No seg fault.
  4) Seg fault occurred when checking nautilus version.

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

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

[Desktop-packages] [Bug 1863151] Re: apparmor messages for libreoffice 1:6.0.7-0ubuntu0.18.04.10 etc

2020-02-14 Thread dinar qurbanov

i think that that means that apparmor profile lags behind libreoffice
and should be updated.

if it is by design, than there could be comments about that, and it is
possible to remove the logs by "deny" keywords.

that messages are bad because they use space in syslog making it harder
to read, and they appear on desktop if aa-notify is used.

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

Title:
  apparmor messages for libreoffice 1:6.0.7-0ubuntu0.18.04.10 etc

Status in libreoffice package in Ubuntu:
  New

Bug description:
  i have reported 3 bugs for apparmor's libreoffice profile:
  https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862331
  https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863097
  https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863103
  i am afraid i make too much bug reports, so i am going to write other reports 
here, if they appear.

  i have now seen this message:

  Feb 13 20:56:25 dinar-Lenovo-G580 kernel: [29200.067772] audit:
  type=1400 audit(1581616585.668:272): apparmor="ALLOWED"
  operation="open" profile="libreoffice-soffice"
  name="/home/dinar/.config/dconf/user" pid=14211 comm="soffice.bin"
  requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

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

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

[Desktop-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it

2020-02-14 Thread Eric Desrochers

Thanks for reporting the outcome of your test.

We will start the SRU process in order to update network-manager package
next week.

Regards,

Eric

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.
   
  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
 valid_lft 353sec preferred_lft 353sec
  inet6 fe80::ff:feb3:b522/64 scope link 
 valid_lft forever preferred_lft forever

  
  
+++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in 
/var/log/syslog
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute 
 valid_lft forever preferred_lft forever

  
  ==> Correct LP-Package need to be assigned...!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions

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

[Desktop-packages] [Bug 1863374] [NEW] Version command line argument should be lower case.

2020-02-14 Thread Clinton H

Public bug reported:

1) Ubuntu 19.10
2) Version 3.34.0
3) If I type the following in the terminal, the gedit version should be 
displayed: gedit -v
4) The gedit version was not displayed. The uppercase -V argument should be 
changed to a -v lower case argument.

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

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

Title:
  Version command line argument should be lower case.

Status in gedit package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) Version 3.34.0
  3) If I type the following in the terminal, the gedit version should be 
displayed: gedit -v
  4) The gedit version was not displayed. The uppercase -V argument should be 
changed to a -v lower case argument.

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

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

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

** Changed in: voms-mysql-plugin (Ubuntu)
   Status: New => In Progress

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

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

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

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  In Progress
Status in asterisk package in Ubuntu:
  In Progress
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  In Progress
Status in dballe package in Ubuntu:
  In Progress
Status in gambas3 package in Ubuntu:
  In Progress
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  In Progress
Status in hoel package in Ubuntu:
  In Progress
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  In Progress
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  In Progress
Status in w1retap package in Ubuntu:
  In Progress
Status in zoneminder package in Ubuntu:
  In Progress

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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

[Desktop-packages] [Bug 1863151] Re: apparmor messages for libreoffice 1:6.0.7-0ubuntu0.18.04.10 etc

2020-02-14 Thread Heather Ellsworth

I understand the issue with cert8.db and key3.db being used (#1862331)
but I don't see what the problem is with the other apparmor messages you
see in journalctl. Can you please make clear what the problem with these
messages are?

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

Title:
  apparmor messages for libreoffice 1:6.0.7-0ubuntu0.18.04.10 etc

Status in libreoffice package in Ubuntu:
  New

Bug description:
  i have reported 3 bugs for apparmor's libreoffice profile:
  https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1862331
  https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863097
  https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1863103
  i am afraid i make too much bug reports, so i am going to write other reports 
here, if they appear.

  i have now seen this message:

  Feb 13 20:56:25 dinar-Lenovo-G580 kernel: [29200.067772] audit:
  type=1400 audit(1581616585.668:272): apparmor="ALLOWED"
  operation="open" profile="libreoffice-soffice"
  name="/home/dinar/.config/dconf/user" pid=14211 comm="soffice.bin"
  requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

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

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

[Desktop-packages] [Bug 1863282] Re: libreoffice menu bar disappeared

2020-02-14 Thread Heather Ellsworth

Thanks for the report!

I was able to reproduce the missing menu bar in libreoffice on a kde
neon 5.18.0 system if I installed libreoffice-kde and/or libreoffice-
kde4 (libreoffice-kde depends on libreoffice-kde4). If either/both of
these are installed, then you will not have a menu bar in libreoffice.

My guess is this is because your plasma version is 5 when you're
installing libreoffice-kde4. In 19.10, we provide libreoffice-kde5 and I
bet this would work but I can't test it because if you update your repos
to point to eoan instead of bionic and go to install libreoffice-kde5,
it will remove the neon-desktop. Also, since kde neon is based on Ubuntu
LTS only, there is no 19.10 version to try.

So for now, I recommend installing libreoffice (do not install
libreoffice-kde/libreoffice-kde4):

$ sudo apt install libreoffice

Yes, this does install libreoffice-gnome and libreoffice-gtk3, but that
should not conflict with anything you are doing.

The next Ubuntu LTS is 20.04, due in April, and I would expect this
issue to go away with libreoffice-kde5 in the kde neon image based on
20.04. So I'll leave this bug open until that is confirmed.

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

** Changed in: libreoffice (Ubuntu)
 Assignee: (unassigned) => Heather Ellsworth (hellsworth)

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

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

Title:
  libreoffice  menu bar disappeared

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Last kde neon 18.04 update Libreoffice menu bar disappeared. Uninstall 
libreoffice-kde & libreoffice-kde4 resolve problem, but need to install 
libreoffice-gtk3.
  KDE neon User Edition 5.18 18.04
  libreoffice-kde 1:6.0.7-0ubuntu0.18.04.10
  libreoffice-kde4 1:6.0.7-0ubuntu0.18.04.10

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

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

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

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

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

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

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  In Progress
Status in asterisk package in Ubuntu:
  In Progress
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  In Progress
Status in dballe package in Ubuntu:
  In Progress
Status in gambas3 package in Ubuntu:
  In Progress
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  In Progress
Status in hoel package in Ubuntu:
  In Progress
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  In Progress
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  In Progress
Status in tntdb package in Ubuntu:
  In Progress
Status in voms-mysql-plugin package in Ubuntu:
  In Progress
Status in vtk7 package in Ubuntu:
  New
Status in w1retap package in Ubuntu:
  New
Status in zoneminder package in Ubuntu:
  New

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

** Changed in: qt4-x11 (Ubuntu)
   Status: New => In Progress

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  In Progress
Status in asterisk package in Ubuntu:
  In Progress
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  In Progress
Status in dballe package in Ubuntu:
  In Progress
Status in gambas3 package in Ubuntu:
  In Progress
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  In Progress
Status in hoel package in Ubuntu:
  In Progress
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  In Progress
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  In Progress
Status in tango package in Ubuntu:
  New
Status in tntdb package in Ubuntu:
  New
Status in voms-mysql-plugin package in Ubuntu:
  New
Status in vtk7 package in Ubuntu:
  New
Status in w1retap package in Ubuntu:
  New
Status in zoneminder package in Ubuntu:
  New

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

** Changed in: pike8.0 (Ubuntu)
   Status: New => In Progress

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

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  In Progress
Status in asterisk package in Ubuntu:
  In Progress
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  In Progress
Status in dballe package in Ubuntu:
  In Progress
Status in gambas3 package in Ubuntu:
  In Progress
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  In Progress
Status in hoel package in Ubuntu:
  In Progress
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  In Progress
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  In Progress
Status in pvpgn package in Ubuntu:
  In Progress
Status in qt4-x11 package in Ubuntu:
  In Progress
Status in redland package in Ubuntu:
  New
Status in tango package in Ubuntu:
  New
Status in tntdb package in Ubuntu:
  New
Status in voms-mysql-plugin package in Ubuntu:
  New
Status in vtk7 package in Ubuntu:
  New
Status in w1retap package in Ubuntu:
  New
Status in zoneminder package in Ubuntu:
  New

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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

[Desktop-packages] [Bug 1794478] Comment bridged from LTC Bugzilla

2020-02-14 Thread bugproxy

--- Comment From abhir...@in.ibm.com 2020-02-14 12:51 EDT---
Eric,

network-manager 1.10.6-2ubuntu1.3+testpkg20201202b1 fix provided is
Working good.

Network connection with auto ipv4 mode and manual ipv6 mode is NOW
rightly setting ipv4 from server and manual ipv6.

Deactivated and Activated the network connection to see both ips are
still retained. No issues seen here.

restart of network manager also the ips are retained.

--- Comment From abhir...@in.ibm.com 2020-02-14 12:59 EDT---
nmcli c s for bond device , the output parameters being watched are now as 
expected

ipv4.method:auto
ipv6.method:manual
ipv6.addresses: fe81::ff:fe97:a27f/64
GENERAL.STATE:  activated
IP4.ADDRESS[1]: 10.2.3.60/24
IP6.ADDRESS[1]: fe81::ff:fe97:a27f/64

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

Title:
  Automatic ipv4 not assigned to bond interface is manual ipv6 is
  assigned to it

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Confirmed

Bug description:
  ---Problem Description---
  Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get 
automatic ipv4 assigned from dhcp server.
   
  ---uname output---
  Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 
2018 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   When user configures ipv4 as automatic and ipv6 as manual for bond interface 
automatic ipv4 is not getting assigned.
  Looks like dhcp client request for ipv4 is not done to dhcp server after 
maunal ipv6 is assigned quickly to bond interface

  This issue will not happen in below cases:
  1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan 
interface.
  2)with ipv4 automatic and ipv6 automatic configuration for bond interface
  3)with ipv4 automatic and ipv6 disabled configuration for bond interface

  Configuration:
  Bond interface, ipv4 automatic mode and ipv6 automatic mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=63e54542-5135-47ac-a954-b861c3937be2
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537944121

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  dns-search=
  method=auto

  From /var/log/syslog, we can see ip got assigned:

  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 
255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on 
test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e)
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 
10.2.3.1
  Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1

  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  28: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute 
test_bond
 valid_lft 353sec preferred_lft 353sec
  inet6 fe80::ff:feb3:b522/64 scope link 
 valid_lft forever preferred_lft forever

  
  
+++
  Bond interface, ipv4 automatic mode and ipv6 manual mode

  root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond 
  [connection]
  id=test_bond
  uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab
  type=bond
  interface-name=test_bond
  permissions=
  timestamp=1537943300

  [ethernet]
  mac-address-blacklist=

  [bond]
  downdelay=0
  fail_over_mac=none
  miimon=100
  mode=active-backup
  num_grat_arp=0
  primary_reselect=always
  updelay=0

  [ipv4]
  dns-search=
  method=auto

  [ipv6]
  addr-gen-mode=stable-privacy
  address1=fe81::32a5:bc5f:287f:8db8/64
  dns-search=
  method=manual

  No automatic ip assigned to ipv4 and no requests to dhcp server seen in 
/var/log/syslog
  root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond
  29: test_bond:  mtu 1500 qdisc 
noqueue state UP group default qlen 1000
  link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff
  inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute 
 valid_lft forever preferred_lft forever

  
  ==> Correct LP-Package need to be

[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-02-14 Thread Edwin Peer

The tpa_aborts shouldn't be a concern. They merely indicate that a TCP
flow could not be aggregated. That could have a performance impact, of
course, but that should manifest as counted drops somewhere if this were
the case.

Importantly, the tpa_aborts only apply to TCP traffic, but you see the
problem for ICMP and UDP too.

Note, the tpa_aborts also appear to be evident on the primary as active
interface while things are working as expected. A difference in
magnitude tpa_aborts from one test run to another may be a clue about
something else that's happening though, but I'm not sure that we are
comparing apples to apples with respect the ethtool -S dumps posted thus
far (when were they captured relative to the test runs, which interface
was active at the time, etc?).

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

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

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.
  D[00:04:56.425845] Detected Rx sequence error.
  D[00:04:57.929209] Detected Rx sequence error.
  [00:05:04.529548] Benchmark complete.
  Benchmark rate summary:
Num received samples: 2995435936
Num dropped samples:  4622800
Num overruns detected:0
Num transmitted samples:  3008276544
Num sequence errors (Tx): 0
Num sequence errors (Rx): 15
Num underruns detected:   0
Num late commands:0
Num timeouts (Tx):0
Num timeouts (Rx):0
  Done!

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$

  
  In

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

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

** Changed in: opensmtpd-extras (Ubuntu)
   Status: New => In Progress

** Changed in: orthanc-mysql (Ubuntu)
   Status: New => In Progress

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  In Progress
Status in asterisk package in Ubuntu:
  In Progress
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  In Progress
Status in dballe package in Ubuntu:
  In Progress
Status in gambas3 package in Ubuntu:
  In Progress
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  In Progress
Status in hoel package in Ubuntu:
  In Progress
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  In Progress
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  In Progress
Status in opensmtpd-extras package in Ubuntu:
  In Progress
Status in orthanc-mysql package in Ubuntu:
  In Progress
Status in pike8.0 package in Ubuntu:
  New
Status in pvpgn package in Ubuntu:
  New
Status in qt4-x11 package in Ubuntu:
  New
Status in redland package in Ubuntu:
  New
Status in tango package in Ubuntu:
  New
Status in tntdb package in Ubuntu:
  New
Status in voms-mysql-plugin package in Ubuntu:
  New
Status in vtk7 package in Ubuntu:
  New
Status in w1retap package in Ubuntu:
  New
Status in zoneminder package in Ubuntu:
  New

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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

[Desktop-packages] [Bug 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1

2020-02-14 Thread Richard Anthony Horan

Bug report filed https://bugzilla.kernel.org/show_bug.cgi?id=206535

** Bug watch added: Linux Kernel Bug Tracker #206535
   https://bugzilla.kernel.org/show_bug.cgi?id=206535

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1861345

Title:
  Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted
  Front speakers 5.1

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

Bug description:
  Ubuntu 18.04.3 LTS
  Kernel 5.5.0
  pulseaudio:
Installed: 1:11.1-1ubuntu7.4
  X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound.

  I have surround 5.1 speakers and the Front Left and Right are Muted.  
  I have to unmute Headphones in alsamixer to hear sound from the front left 
and right speakers is the workaround.

  This step should not be required for speakers 5.1 to work.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard2533 F pulseaudio
   /dev/snd/controlC1:  richard2533 F pulseaudio
   /dev/snd/controlC0:  richard2533 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on 
vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-28-generic N/A
   linux-backports-modules-5.3.0-28-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+subscriptions

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

[Desktop-packages] [Bug 1863258] Re: Install the widevine binary upon request in Chromium snap

2020-02-14 Thread Michel-Ekimia

** Description changed:

  Use case :
  
- - Start a video on netflix.com ( with chrome/ubuntu user agent ) 
+ - Start a video on netflix.com ( with chrome/ubuntu user agent )
  - Get a mysterious Netflix Error saying your browser is not supported
  - Start Firefox and watch your video
  
  Solution :
  
  - Detects when browsing a website that may need widevine ( see how
  firefox team did )
  
  - ask user if he wants this non-free binary plugin
  
  - Run some script like
  https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that
  would copy the widevine plugin in snap user directory
+ 
+ 
+ Notes :
+ 
+ - Widevine versions and binary url from mozilla
+ https://hg.mozilla.org/releases/mozilla-
+ beta/file/default/toolkit/content/gmp-sources/widevinecdm.json

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

Title:
  Install the widevine binary upon request in Chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Use case :

  - Start a video on netflix.com ( with chrome/ubuntu user agent )
  - Get a mysterious Netflix Error saying your browser is not supported
  - Start Firefox and watch your video

  Solution :

  - Detects when browsing a website that may need widevine ( see how
  firefox team did )

  - ask user if he wants this non-free binary plugin

  - Run some script like
  https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that
  would copy the widevine plugin in snap user directory


  Notes :

  - Widevine versions and binary url from mozilla
  https://hg.mozilla.org/releases/mozilla-
  beta/file/default/toolkit/content/gmp-sources/widevinecdm.json

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

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

[Desktop-packages] [Bug 1863222] Re: Please update to hwdata 0.332

2020-02-14 Thread Hans Joachim Desserud

** Bug watch added: Debian Bug tracker #947191
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947191

** Also affects: hwdata (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947191
   Importance: Unknown
   Status: Unknown

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

Title:
  Please update to hwdata 0.332

Status in hwdata package in Ubuntu:
  New
Status in hwdata package in Debian:
  Unknown

Bug description:
  Please update hwdata to 0.332, and update the homepage and watch file
  to better track newer versions.

  https://github.com/vcrhonek/hwdata/releases

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

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

[Desktop-packages] [Bug 1863219] Re: WiFi module RTL8723DE not supported @live / installed session

2020-02-14 Thread Suvendu Dey

** Also affects: kernel-package (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  WiFi module RTL8723DE not supported @live / installed session

Status in kernel-package package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi
  I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some 
wireless connectivity problems with Realtek chips.
  My system compatible with rtl8723de wifi driver module. Laptop model no HP 
14q-cs0009tu.
  Ubuntu live session can’t detect the card nor the post-installed OS does.
  Therefore, no wifi switch/icon.
  I would hope Ubuntu 20.04 LTS natively support this wireless chip.
  regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1863219/+subscriptions

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

[Desktop-packages] [Bug 1863258] Re: Install the widevine binary upon request in Chromium snap

2020-02-14 Thread Olivier Tilloy

** Changed in: chromium-browser (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Install the widevine binary upon request in Chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Use case :

  - Start a video on netflix.com ( with chrome/ubuntu user agent ) 
  - Get a mysterious Netflix Error saying your browser is not supported
  - Start Firefox and watch your video

  Solution :

  - Detects when browsing a website that may need widevine ( see how
  firefox team did )

  - ask user if he wants this non-free binary plugin

  - Run some script like
  https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that
  would copy the widevine plugin in snap user directory

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

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

[Desktop-packages] [Bug 1863282] [NEW] libreoffice menu bar disappeared

2020-02-14 Thread Cuyo

Public bug reported:

Last kde neon 18.04 update Libreoffice menu bar disappeared. Uninstall 
libreoffice-kde & libreoffice-kde4 resolve problem, but need to install 
libreoffice-gtk3.
KDE neon User Edition 5.18 18.04
libreoffice-kde 1:6.0.7-0ubuntu0.18.04.10
libreoffice-kde4 1:6.0.7-0ubuntu0.18.04.10

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

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

Title:
  libreoffice  menu bar disappeared

Status in libreoffice package in Ubuntu:
  New

Bug description:
  Last kde neon 18.04 update Libreoffice menu bar disappeared. Uninstall 
libreoffice-kde & libreoffice-kde4 resolve problem, but need to install 
libreoffice-gtk3.
  KDE neon User Edition 5.18 18.04
  libreoffice-kde 1:6.0.7-0ubuntu0.18.04.10
  libreoffice-kde4 1:6.0.7-0ubuntu0.18.04.10

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

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

[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2020-02-14 Thread Sze Attila

I I did it!
1.) I opened the  /etc/xdg/autostart/spice-vdagent.desktop   file with "sudo 
gedit".
2.) I modified the file to:
[Desktop Entry]
Name=Spice vdagent
Comment=Agent for Spice guests
Exec=/usr/bin/spice-vdagent
Terminal=false
Type=Application
Categories=
X-GNOME-Autostart-Phase=Initialization
NoDisplay=false
X-GNOME-Autostart-enabled=false
3.) Saved
4.) After I did it same with the  
/usr/share/gdm/autostart/LoginWindow/spice-vdagent.desktop   file.
(Interesting: when I browsing this folder with "Nautilus", just a "Spice 
vdagent" named file was there... but when I opened this folder with "sudo 
gedit" there a "spice-vdagent.desktop", so I opened.)
5.) Saved
6.) Finally: $ sudo systemctl stop spice-vdagentd  and  $ sudo systemctl 
disable spice-vdagentd
7.) Reboot... and the "Cannot access vdagent virtio channel 
/dev/virtio-ports/com.redhat.spice.0" error message is gone!
P.S: How the heck can modified my comments? I can't find..
:)

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

Title:
  spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

Status in spice-vdagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  $ journalctl -b

  [...]

  oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent
  virtio channel /dev/virtio-ports/com.redhat.spice.0

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: spice-vdagent 0.17.0-1ubuntu2
  Uname: Linux 4.19.0-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 14:34:00 2018
  InstallationDate: Installed on 2017-10-13 (378 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: spice-vdagent
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions

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

[Desktop-packages] [Bug 1863219] Re: WiFi module RTL8723DE not supported @live / installed session

2020-02-14 Thread Suvendu Dey

** Package changed: ubuntu => network-manager (Ubuntu)

** Description changed:

  Hi
  I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some 
wireless connectivity problems with Realtek chips.
  My system compatible with rtl8723de wifi driver module. Laptop model no HP 
14q-cs0009tu.
  Ubuntu live session can’t detect the card nor the post-installed OS does.
+ Therefore, no wifi switch/icon.
  I would hope Ubuntu 20.04 LTS natively support this wireless chip.
  regards.

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

Title:
  WiFi module RTL8723DE not supported @live / installed session

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi
  I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some 
wireless connectivity problems with Realtek chips.
  My system compatible with rtl8723de wifi driver module. Laptop model no HP 
14q-cs0009tu.
  Ubuntu live session can’t detect the card nor the post-installed OS does.
  Therefore, no wifi switch/icon.
  I would hope Ubuntu 20.04 LTS natively support this wireless chip.
  regards.

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

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

[Desktop-packages] [Bug 1863219] [NEW] WiFi module RTL8723DE not supported @live / installed session

You have been subscribed to a public bug:

Hi
I am using Ubuntu 19.10(gnome) desktop with kernel 5.3. It lacks some wireless 
connectivity problems with Realtek chips.
My system compatible with rtl8723de wifi driver module. Laptop model no HP 
14q-cs0009tu.
Ubuntu live session can’t detect the card nor the post-installed OS does.
I would hope Ubuntu 20.04 LTS natively support this wireless chip.
regards.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment realtek rtl8723de wifi
-- 
WiFi module RTL8723DE not supported @live / installed session
https://bugs.launchpad.net/bugs/1863219
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager in Ubuntu.

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

[Desktop-packages] [Bug 1863262] Re: package xdg-desktop-portal (not installed) failed to install/upgrade: no package named 'xdg-desktop-portal' is installed, cannot configure

2020-02-14 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package xdg-desktop-portal (not installed) failed to install/upgrade:
  no package named 'xdg-desktop-portal' is installed, cannot configure

Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  unknown error encountered

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xdg-desktop-portal (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Fri Feb 14 20:20:57 2020
  ErrorMessage: no package named 'xdg-desktop-portal' is installed, cannot 
configure
  InstallationDate: Installed on 2020-02-13 (1 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: xdg-desktop-portal
  Title: package xdg-desktop-portal (not installed) failed to install/upgrade: 
no package named 'xdg-desktop-portal' is installed, cannot configure
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1863262/+subscriptions

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

[Desktop-packages] [Bug 1863258] Re: Install the widevine binary upon request in Chromium snap

2020-02-14 Thread Michel-Ekimia

** Tags added: bionic focal

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

Title:
  Install the widevine binary upon request in Chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Use case :

  - Start a video on netflix.com ( with chrome/ubuntu user agent ) 
  - Get a mysterious Netflix Error saying your browser is not supported
  - Start Firefox and watch your video

  Solution :

  - Detects when browsing a website that may need widevine ( see how
  firefox team did )

  - ask user if he wants this non-free binary plugin

  - Run some script like
  https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that
  would copy the widevine plugin in snap user directory

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

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

[Desktop-packages] [Bug 1863262] [NEW] package xdg-desktop-portal (not installed) failed to install/upgrade: no package named 'xdg-desktop-portal' is installed, cannot configure

2020-02-14 Thread jitendra

Public bug reported:

unknown error encountered

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: xdg-desktop-portal (not installed)
ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
Date: Fri Feb 14 20:20:57 2020
ErrorMessage: no package named 'xdg-desktop-portal' is installed, cannot 
configure
InstallationDate: Installed on 2020-02-13 (1 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: xdg-desktop-portal
Title: package xdg-desktop-portal (not installed) failed to install/upgrade: no 
package named 'xdg-desktop-portal' is installed, cannot configure
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xdg-desktop-portal (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package xdg-desktop-portal (not installed) failed to install/upgrade:
  no package named 'xdg-desktop-portal' is installed, cannot configure

Status in xdg-desktop-portal package in Ubuntu:
  New

Bug description:
  unknown error encountered

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: xdg-desktop-portal (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Fri Feb 14 20:20:57 2020
  ErrorMessage: no package named 'xdg-desktop-portal' is installed, cannot 
configure
  InstallationDate: Installed on 2020-02-13 (1 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: xdg-desktop-portal
  Title: package xdg-desktop-portal (not installed) failed to install/upgrade: 
no package named 'xdg-desktop-portal' is installed, cannot configure
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1863262/+subscriptions

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

[Desktop-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)

2020-02-14 Thread Marlon W. Santos

dualshock3nerd's solution also works for me too!
Thanks!!!

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

Title:
Volume notification keeps popping up constantly (the notify-OSD bubble
on top-right corner)

Status in pulseaudio package in Ubuntu:
Confirmed

Bug description:
I upgraded to Ubuntu 16.04 yesterday, I did a clean install while
preserving the home directory which is mounted in a separate
partition. Even during the installation I had constant volume
notification bubble appearing on the top-right corner of my screen, it
would come and go about twice every minute. I just thought it was due
to installing hardware drivers or something but the problem persisted
even when I booted into the freshly installed system. I did some
searching and two users reported the exact problem. And one more
suggested this happens because constant disconnect and reconnect of
the sound card which makes sense as the sound settings flashes briefly
during every popup. Someone on IRC suggested to kill pulseaudio and
thus restart it, that does not fix the issue. I also tried the Live
environment thinking it might be due to some old config files in home
partition (which was preserved during upgrade), but this problem
happens in the live environment as well, which makes sense because it
was present during installation as well.

Users with the same issue:
http://ubuntuforums.org/showthread.php?t=2323815
http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04

http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: sidd 1651 F pulseaudio
/dev/snd/controlC0: sidd 1651 F pulseaudio
/dev/snd/controlC1: sidd 1651 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 12:31:12 2016
InstallationDate: Installed on 2016-05-23 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
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.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: 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.

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

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

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

** Changed in: mysql-ocaml (Ubuntu)
   Status: New => In Progress

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

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  In Progress
Status in asterisk package in Ubuntu:
  In Progress
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  In Progress
Status in dballe package in Ubuntu:
  In Progress
Status in gambas3 package in Ubuntu:
  In Progress
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  In Progress
Status in hoel package in Ubuntu:
  In Progress
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  In Progress
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  New
Status in opensmtpd-extras package in Ubuntu:
  New
Status in orthanc-mysql package in Ubuntu:
  New
Status in pike8.0 package in Ubuntu:
  New
Status in pvpgn package in Ubuntu:
  New
Status in qt4-x11 package in Ubuntu:
  New
Status in redland package in Ubuntu:
  New
Status in tango package in Ubuntu:
  New
Status in tntdb package in Ubuntu:
  New
Status in voms-mysql-plugin package in Ubuntu:
  New
Status in vtk7 package in Ubuntu:
  New
Status in w1retap package in Ubuntu:
  New
Status in zoneminder package in Ubuntu:
  New

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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

[Desktop-packages] [Bug 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

2020-02-14 Thread Sarpreet

I am still seeing thins on a fresh Eoan install ..
https://bugs.launchpad.net/bugs/1857892

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

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

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1863258] [NEW] Install the widevine binary upon request in Chromium snap

2020-02-14 Thread Michel-Ekimia

Public bug reported:

Use case :

- Start a video on netflix.com ( with chrome/ubuntu user agent ) 
- Get a mysterious Netflix Error saying your browser is not supported
- Start Firefox and watch your video

Solution :

- Detects when browsing a website that may need widevine ( see how
firefox team did )

- ask user if he wants this non-free binary plugin

- Run some script like
https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that
would copy the widevine plugin in snap user directory

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

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

Title:
  Install the widevine binary upon request in Chromium snap

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Use case :

  - Start a video on netflix.com ( with chrome/ubuntu user agent ) 
  - Get a mysterious Netflix Error saying your browser is not supported
  - Start Firefox and watch your video

  Solution :

  - Detects when browsing a website that may need widevine ( see how
  firefox team did )

  - ask user if he wants this non-free binary plugin

  - Run some script like
  https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 that
  would copy the widevine plugin in snap user directory

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

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

[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround

** Also affects: isc-kea (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: isc-kea (Ubuntu)
   Status: New => In Progress

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

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

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

Title:
  Remove my_bool typedef workaround

Status in argus-clients package in Ubuntu:
  In Progress
Status in asterisk package in Ubuntu:
  In Progress
Status in clickhouse package in Ubuntu:
  In Progress
Status in cppdb package in Ubuntu:
  In Progress
Status in dballe package in Ubuntu:
  In Progress
Status in gambas3 package in Ubuntu:
  In Progress
Status in gearmand package in Ubuntu:
  In Progress
Status in gerbera package in Ubuntu:
  In Progress
Status in gnokii package in Ubuntu:
  In Progress
Status in hoel package in Ubuntu:
  In Progress
Status in isc-kea package in Ubuntu:
  In Progress
Status in jabberd2 package in Ubuntu:
  In Progress
Status in kannel package in Ubuntu:
  In Progress
Status in libgda5 package in Ubuntu:
  In Progress
Status in libodb-mysql package in Ubuntu:
  In Progress
Status in lyricue package in Ubuntu:
  In Progress
Status in motion package in Ubuntu:
  In Progress
Status in mysql-8.0 package in Ubuntu:
  In Progress
Status in mysql-ocaml package in Ubuntu:
  In Progress
Status in mysqltcl package in Ubuntu:
  In Progress
Status in opendnssec package in Ubuntu:
  New
Status in opensmtpd-extras package in Ubuntu:
  New
Status in orthanc-mysql package in Ubuntu:
  New
Status in pike8.0 package in Ubuntu:
  New
Status in pvpgn package in Ubuntu:
  New
Status in qt4-x11 package in Ubuntu:
  New
Status in redland package in Ubuntu:
  New
Status in tango package in Ubuntu:
  New
Status in tntdb package in Ubuntu:
  New
Status in voms-mysql-plugin package in Ubuntu:
  New
Status in vtk7 package in Ubuntu:
  New
Status in w1retap package in Ubuntu:
  New
Status in zoneminder package in Ubuntu:
  New

Bug description:
  During the previous development cycle, when mysql 8 was introduced,
  too many reverse deps failed due to the my_bool removal. It was then
  decided to put that back in to let the reverse dependencies build
  again.

  Now we should try to drop it one more time, and instead fix the
  reverse dependencies. Either by updating them, if upstream fixed it,
  or reintroducing only this my_bool typedef in the reverse dependency
  itself, instead of in mysql as it's now.

  This bug will track these tasks:
  - remove my_bool workaround from Ubuntu's mysql 8 package
  - fix the build of the reverse dependencies, each one a task of this bug.

  PPA with test builds:
  https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool-
  removal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions

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

[Desktop-packages] [Bug 1792822] Re: Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

2020-02-14 Thread Jeppe Rask

I was able to solve the problem, by switching GPU-driver.
"Software & Updates" -> "Additional Drivers" - I switched from:
"Using X.Org X server - Nouveau display driver" to the NVIDIA-435.

Perhaps this is only specific to my setup, by powering monitors from GPU
as well as motherboard. Hope it helps someone.

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

Title:
  Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

Status in mutter package in Ubuntu:
  Expired

Bug description:
  Dual monitor setup works fine in 16.04 LTS. Not anymore in 18.04(.1).
  This renders 18.04 useless. Till this is solved will have to stick
  with 16.04. i.e. this is a pretty critical bug!

  
  After a fresh install from DVD first got a freeze on login screen (live CD 
will run ubuntu though!). This could be solved by switching to lightdm display 
manager. (Boo! for GDM that cannot even show a login screen without freezing 
the system)

  But one issue remains: the dual monitor setup will not work in 18.04.

  I can see the mouse move to the second monitor. I can drag windows
  there (and lose sight of them). I can see the mouse cursor change to
  click a link. But otherwise there is a completely black screen, or
  dots / colored fields, but nothing even resembling a program.

  MB: Gigabyte GA-A75M-UD2H
  Monitor that works fine: ASUS on Radeon HD 6550D
  monitor that only shows mouse cursor: benq on Radeon HD 4870 (onboard on the 
gigabyte motherboard)

  Note: dual monitor setup did not work with other upgrades after 16.04. I 
hoped this would be solved with the next LTS update. Not so, to great 
disappointment!
  Ubuntu really fails if with new major updates it makes systems fall down. 
This kind of thing should work FLAWLESS out of the box! How would anyone move 
to Ubuntu when this kind of thing does not work? Windows is a drama, but at 
least it has the mere basics working!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Sep 16 23:09:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-133-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-134-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-135-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] 
[1002:9640] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6550D] 
[1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:9440] 
(prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology RV770 [Radeon HD 4870] 
[174b:0851]
  InstallationDate: Installed on 2016-10-02 (714 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic 
root=UUID=a5b3b47d-aa17-4b49-ba9a-eeaefc2556d6 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6c
  dmi.board.name: GA-A75M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6c:bd11/17/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-A75M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel:

[Desktop-packages] [Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap

2020-02-14 Thread Sergio Schvezov

If I were a betting person, I would put my stakes on gdk-pixbuf
(https://github.com/snapcrafters/vscode/blob/master/files/bin/wrapper#L36)

If that is part of code's environment, whatever it calls will leak that
env into the callee...

sergiusens@umbar:~$ snap run --shell code
sergiusens@umbar:~$ cd $SNAP
sergiusens@umbar:/snap/code/25$ cat electron-launch 
#!/usr/bin/env bash

# On Fedora $SNAP is under /var and there is some magic to map it to /snap.
# We need to handle that case and reset $SNAP
SNAP=$(echo $SNAP | sed -e "s|/var/lib/snapd||g")

if [ "$SNAP_ARCH" == "amd64" ]; then
  ARCH="x86_64-linux-gnu"
elif [ "$SNAP_ARCH" == "armhf" ]; then
  ARCH="arm-linux-gnueabihf"
elif [ "$SNAP_ARCH" == "arm64" ]; then
  ARCH="aarch64-linux-gnu"
else
  ARCH="$SNAP_ARCH-linux-gnu"
fi

export XDG_CACHE_HOME=$SNAP_USER_COMMON/.cache
if [[ -d $SNAP_USER_DATA/.cache && ! -e $XDG_CACHE_HOME ]]; then
  # the .cache directory used to be stored under $SNAP_USER_DATA, migrate it
  mv $SNAP_USER_DATA/.cache $SNAP_USER_COMMON/
fi
mkdir -p $XDG_CACHE_HOME

# Gdk-pixbuf loaders
export GDK_PIXBUF_MODULE_FILE=$XDG_CACHE_HOME/gdk-pixbuf-loaders.cache
export GDK_PIXBUF_MODULEDIR=$SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/2.10.0/loaders
if [ -f $SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders ]; then
  $SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders > 
$GDK_PIXBUF_MODULE_FILE
fi

# Create $XDG_RUNTIME_DIR if not exists (to be removed when 
https://pad.lv/1656340 is fixed)
[ -n "$XDG_RUNTIME_DIR" ] && mkdir -p $XDG_RUNTIME_DIR -m 700

exec "$@"
sergiusens@umbar:/snap/code/25$ if [ "$SNAP_ARCH" == "amd64" ]; then
>   ARCH="x86_64-linux-gnu"
> elif [ "$SNAP_ARCH" == "armhf" ]; then
>   ARCH="arm-linux-gnueabihf"
> elif [ "$SNAP_ARCH" == "arm64" ]; then
>   ARCH="aarch64-linux-gnu"
> else
>   ARCH="$SNAP_ARCH-linux-gnu"
> fi
sergiusens@umbar:/snap/code/25$ 
sergiusens@umbar:/snap/code/25$ export XDG_CACHE_HOME=$SNAP_USER_COMMON/.cache
sergiusens@umbar:/snap/code/25$ if [[ -d $SNAP_USER_DATA/.cache && ! -e 
$XDG_CACHE_HOME ]]; then
>   # the .cache directory used to be stored under $SNAP_USER_DATA, migrate it
>   mv $SNAP_USER_DATA/.cache $SNAP_USER_COMMON/
> fi
sergiusens@umbar:/snap/code/25$ mkdir -p $XDG_CACHE_HOME
sergiusens@umbar:/snap/code/25$ 
sergiusens@umbar:/snap/code/25$ # Gdk-pixbuf loaders
sergiusens@umbar:/snap/code/25$ export 
GDK_PIXBUF_MODULE_FILE=$XDG_CACHE_HOME/gdk-pixbuf-loaders.cache
sergiusens@umbar:/snap/code/25$ export 
GDK_PIXBUF_MODULEDIR=$SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/2.10.0/loaders
sergiusens@umbar:/snap/code/25$ if [ -f 
$SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders ]; then
>   $SNAP/usr/lib/$ARCH/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders > 
> $GDK_PIXBUF_MODULE_FILE
> fi
sergiusens@umbar:/snap/code/25$ firefox
ExceptionHandler::GenerateDump cloned child 570327
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
sergiusens@umbar:/snap/code/25$ unset GDK_PIXBUF_MODULE_FILE 
sergiusens@umbar:/snap/code/25$ unset GDK_PIXBUF_MODULEDIR 
sergiusens@umbar:/snap/code/25$ firefox

###!!! [Child][MessageChannel] Error:
(msgtype=0x370135,name=PContent::Msg_DetachBrowsingContext) Closed
channel: cannot send/recv


As you can see, env exported gets a crash, next, after unsetting, everything is 
fine.

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

Title:
  Firefox crashreporter crashed with SIGSEGV in memcpy() when opening
  links from Visual Studio Code snap

Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  How the crash happened:

  0) Firefox is already open with a few tabs.
  1) Click on a link in VS Code.
  2) Firefox crashes
  3) The crashreporter of firefex pops up.
  4) Click on "Send to Mozilla".
  5) Crash.

  Here is the crashreport of Firefox: 
https://crash-stats.mozilla.org/report/index/b6952db2-9983-4f67-b51c-f03a60190727#tab-details
  I send it manually via about:crashes because the crashreporter is crashed.

  VS Code is installed as a snap by the way.

  $ snap list
  Name   Version  Rev   Tracking  Publisher Notes
  code   2213894e 11stablevscode✓   classic
  core   16-2.39.37270  stablecanonical✓core
  core18 20190709 1066  stablecanonical✓base
  gtk-common-themes  0.1-22-gab0a26b  1313  stablecanonical✓-
  telegram-desktop   1.7.13   836   stabletelegram.desktop  -

  As you can see telegram is also installed as as snap. but open links
  from telegram just work.

  Auto generated data below
  ---

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: firefox 68.0.1+build1-0ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic

[Desktop-packages] [Bug 1792822] Re: Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

2020-02-14 Thread Jeppe Rask

Hi, I'm seeing this error as well.

The last frame shown while logging in freezes on the second monitor and
only the cursor updates.

I have enabled iGPU Multi-Monitor for my ASUS motherboard, which enabled
me to connect one monitor through the motherboard and one through my GPU
- the one connected to the GPU is the one that freezes. This has
previously worked with Ubuntu 18.04.

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

Title:
  Dual monitor not working in 18.04(.1) on a dual-radeon-GPU system

Status in mutter package in Ubuntu:
  Expired

Bug description:
  Dual monitor setup works fine in 16.04 LTS. Not anymore in 18.04(.1).
  This renders 18.04 useless. Till this is solved will have to stick
  with 16.04. i.e. this is a pretty critical bug!

  
  After a fresh install from DVD first got a freeze on login screen (live CD 
will run ubuntu though!). This could be solved by switching to lightdm display 
manager. (Boo! for GDM that cannot even show a login screen without freezing 
the system)

  But one issue remains: the dual monitor setup will not work in 18.04.

  I can see the mouse move to the second monitor. I can drag windows
  there (and lose sight of them). I can see the mouse cursor change to
  click a link. But otherwise there is a completely black screen, or
  dots / colored fields, but nothing even resembling a program.

  MB: Gigabyte GA-A75M-UD2H
  Monitor that works fine: ASUS on Radeon HD 6550D
  monitor that only shows mouse cursor: benq on Radeon HD 4870 (onboard on the 
gigabyte motherboard)

  Note: dual monitor setup did not work with other upgrades after 16.04. I 
hoped this would be solved with the next LTS update. Not so, to great 
disappointment!
  Ubuntu really fails if with new major updates it makes systems fall down. 
This kind of thing should work FLAWLESS out of the box! How would anyone move 
to Ubuntu when this kind of thing does not work? Windows is a drama, but at 
least it has the mere basics working!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Sep 16 23:09:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-133-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-134-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-135-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6550D] 
[1002:9640] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd BeaverCreek [Radeon HD 6550D] 
[1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4870] [1002:9440] 
(prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology RV770 [Radeon HD 4870] 
[174b:0851]
  InstallationDate: Installed on 2016-10-02 (714 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H
  ProcEnviron:
   LANGUAGE=nl_NL
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nl_NL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-135-generic 
root=UUID=a5b3b47d-aa17-4b49-ba9a-eeaefc2556d6 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/17/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6c
  dmi.board.name: GA-A75M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6c:bd11/17/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-A75M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2

[Desktop-packages] [Bug 1863184] Re: Application does not stay open on Ubuntu 20.04 and closes automatically

2020-02-14 Thread Edson José dos Santos

I ask you to analyze the content and then delete it.

It was the only way to send crash data to the totem

** Attachment added: "Crash"
   
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1863184/+attachment/5328158/+files/usr_bin_totem.1000.crash.txt

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

Title:
  Application does not stay open on Ubuntu 20.04 and closes
  automatically

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello Ubuntu Team

  When we click on the totem it opens and closes automatically, as seen
  in the gif image on the link below.

  [img]https://i.imgur.com/TYA8hrg.mp4[/img]

  I tried to report this error by ubuntu-bug -w, but an error message
  appears that can be seen in the gif image below.

  [img]https://i.imgur.com/xm9QSb9.mp4[/img]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-04-28 (291 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: totem 3.34.1-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-04 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: 
'/var/log/Xorg.0.log'
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1863184] Re: Application does not stay open on Ubuntu 20.04 and closes automatically

2020-02-14 Thread Edson José dos Santos

I ask you to analyze the content and then delete it.

It was the only way to send crash data to the totem

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

Title:
  Application does not stay open on Ubuntu 20.04 and closes
  automatically

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  Hello Ubuntu Team

  When we click on the totem it opens and closes automatically, as seen
  in the gif image on the link below.

  [img]https://i.imgur.com/TYA8hrg.mp4[/img]

  I tried to report this error by ubuntu-bug -w, but an error message
  appears that can be seen in the gif image below.

  [img]https://i.imgur.com/xm9QSb9.mp4[/img]
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-04-28 (291 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: totem 3.34.1-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-04 (9 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: 
'/var/log/Xorg.0.log'
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-02-14 Thread Nivedita Singhvi

Edwin,

Do you happen to notice any IPv6 or LLDP or other link-local traffic
on the interfaces? (including backup interface). 

The MTR loss  % is purely a capture of their packets xmitted 
and responses received, so for that UDP MTR test, this is saying
that UDP packets were lost, somewhere. 

The NIC does not have any drops showing via ethtool -S 
stats but I'm hunting down which are the right pair of before/afters.

Other than the tpa_abort counts, there were no errors that I saw.
I can't tell what the tpa_abort means for the frame - is it purely 
a failure only to coalesce, or does it end up dropping packets at
some point in that functionality? I'm assuming not, as whatever the
reason, those would be counted as drops, I hope, and printed in 
the interface stats. 

I'll attach all the stats here once I get them sorted out, I thought
I had a clean diff of before and after from the tester, but after
looking through, I don't think the file I have is from before/after
the mtr test, as there was negligible UDP traffic. I'll try and
get clarification from the reporter. 

Note that when the provision of primary= is used to configure 
which interface is primary, and when the primary port is used
as the active interface for the bond, no problems are seen (and
that works deterministically to set the correct active interface).

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

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

Bug description:
  The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G
  RDMA Ethernet device seems to be dropping data

  Basically, we are dropping data, as you can see from the benchmark
  tool as follows:

  tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 
10e6 --tx_rate 10e6 --duration 300
  [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; 
UHD_3.14.1.1-0-g98c7c986
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam

  [00:00:00.07] Creating the usrp device with: ...
  [INFO] [X300] X300 initialization sequence...
  [INFO] [X300] Maximum frame size: 1472 bytes.
  [INFO] [X300] Radio 1x clock: 200 MHz
  [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
  [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s)
  [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s)
  [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001)
  [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0)
  [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0)
  [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0)
  Using Device: Single USRP:
Device: X-Series Device
Mboard 0: X310
RX Channel: 0
  RX DSP: 0
  RX Dboard: A
  RX Subdev: SBX-120 RX
RX Channel: 1
  RX DSP: 0
  RX Dboard: B
  RX Subdev: SBX-120 RX
TX Channel: 0
  TX DSP: 0
  TX Dboard: A
  TX Subdev: SBX-120 TX
TX Channel: 1
  TX DSP: 0
  TX Dboard: B
  TX Subdev: SBX-120 TX

  [00:00:04.305374] Setting device timestamp to 0...
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels
  [WARNING] [UHD] Unable to set the thread priority. Performance may be 
negatively affected.
  Please see the general application notes in the manual for instructions.
  EnvironmentError: OSError: error in pthread_setschedparam
  [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels
  [00:00:06.693119] Detected Rx sequence error.
  D[00:00:09.402843] Detected Rx sequence error.
  DD[00:00:40.927978] Detected Rx sequence error.
  D[00:01:44.982243] Detected Rx sequence error.
  D[00:02:11.400692] Detected Rx sequence error.
  D[00:02:14.805292] Detected Rx sequence error.
  D[00:02:41.875596] Detected Rx sequence error.
  D[00:03:06.927743] Detected Rx sequence error.
  D[00:03:47.967891] Detected Rx sequence error.
  D[00:03:58.233659] Detected Rx sequence error.
  D[00:03:58.876588] Detected Rx sequence error.
  D[00:04:03.139770] Detected Rx sequence error.
  D[00:04:45.287465] Detected Rx sequence error.

[Desktop-packages] [Bug 1863186] Re: package sdl2-dev depends on outdated version of libpulse-dev

2020-02-14 Thread Juhani Numminen

Please note that libsdl2-dev has an unversioned dependency on libpulse-
dev.

There seems to be a local version mismatch between the libpulse
packages: “libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but
1:11.1-1ubuntu7.5 is installed”.

Did you have the bionic-proposed repository enabled at some point but
don't have it anymore? I think if you enabled the proposed updates then
you might be able to install libpulse-dev again.

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

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

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

Title:
  package sdl2-dev depends on outdated version of libpulse-dev

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  $ sudo apt install libsdl2-dev 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libsdl2-dev : Depends: libpulse-dev but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  $ sudo aptitude install libsdl2-dev 
  The following NEW packages will be installed:

  

   The following packages have unmet dependencies:
   libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 
1:11.1-1ubuntu7.5 is installed
  Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 
1:11.1-1ubuntu7.5 is installed

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

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

[Desktop-packages] [Bug 1863186] [NEW] package sdl2-dev depends on outdated version of libpulse-dev

You have been subscribed to a public bug:

$ sudo apt install libsdl2-dev 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libsdl2-dev : Depends: libpulse-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

$ sudo aptitude install libsdl2-dev 
The following NEW packages will be installed:



 The following packages have unmet dependencies:
 libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 
is installed
Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 
1:11.1-1ubuntu7.5 is installed

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

-- 
package sdl2-dev depends on outdated version of libpulse-dev
https://bugs.launchpad.net/bugs/1863186
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pulseaudio in Ubuntu.

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

[Desktop-packages] [Bug 1183765] Re: During typography thumbnailing, the Font Viewer window becomes very unresponsive

https://gitlab.gnome.org/GNOME/gnome-font-viewer/issues/2

** Changed in: gnome-font-viewer
   Importance: Medium => Undecided

** Changed in: gnome-font-viewer
 Remote watch: GNOME Bug Tracker #701005 => None

** Bug watch added: gitlab.gnome.org/GNOME/gnome-font-viewer/issues #2
   https://gitlab.gnome.org/GNOME/gnome-font-viewer/issues/2

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

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

Title:
  During typography thumbnailing, the Font Viewer window becomes very
  unresponsive

Status in GNOME Font Viewer:
  Fix Released
Status in One Hundred Papercuts:
  Triaged
Status in gnome-font-viewer package in Ubuntu:
  Triaged

Bug description:
  
  HOW TO REPRODUCE
  
  1. Close Font Viewer.
  2. Install "edubuntu-fonts" package.
  3. Launch Font Viewer, and scroll through the listed typographies.

  *
  BEHAVIOUR
  *
  - EXPECTED: The scrolling to be fluid.
  - REAL: The scrolling is very choppy; with the window being very unresponsive 
for a long time, because the thumbnailing not being performed as a background 
process.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-font-viewer 3.7.5-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11
  Uname: Linux 3.8.0-22-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Fri May 24 12:09:03 2013
  InstallationDate: Installed on 2013-05-21 (2 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-font-viewer/+bug/1183765/+subscriptions

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

[Desktop-packages] [Bug 1375819] Re: gnome-font-viewer freezes up itself or the X session

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

** This bug has been marked a duplicate of bug 1183765
   During typography thumbnailing, the Font Viewer window becomes very 
unresponsive

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

Title:
  gnome-font-viewer freezes up itself or the X session

Status in gnome-font-viewer package in Ubuntu:
  Triaged
Status in gnome-font-viewer package in Fedora:
  Won't Fix

Bug description:
  When I open gnome-font-viewer by clicking on font file (tried on TTF
  and PFB) it sometimes locks up. Then nothing can be done within the
  window, but the rest of X session works. However sometimes the whole X
  session freezes, only mouse cursor moves. It can be worked around by
  switching to tty1 and killall'ing gnome-font-viewer.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-font-viewer 3.12.0-1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Sep 30 16:46:07 2014
  InstallationDate: Installed on 2013-07-21 (436 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  SourcePackage: gnome-font-viewer
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (4 days ago)

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

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

[Desktop-packages] [Bug 1407149] Re: Opened up Font Viewer, now it won't close

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

** This bug is no longer a duplicate of bug 1375819
   gnome-font-viewer freezes up itself or the X session
** This bug has been marked a duplicate of bug 1183765
   During typography thumbnailing, the Font Viewer window becomes very 
unresponsive

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

Title:
  Opened up Font Viewer, now it won't close

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

Bug description:
  I opened up the Fonts Viewer, and now it won't close.

  I just now opened the System Monitor and before I could select the
  Font Viewer Process to kill it, a popup window came up saying "Font
  Viewer has failed to respond.  Click here to terminate it or here to
  Wait."  I terminated the process.

  ProblemType: Bug
  DistroRelease: elementary OS 0.3
  Package: elementary-desktop 1.354+398~ubuntu0.3.1 [origin: 
LP-PPA-elementary-os-daily]
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CrashDB: elementary_meta
  CurrentDesktop: Pantheon
  Date: Fri Jan  2 13:27:02 2015
  InstallationDate: Installed on 2014-12-27 (6 days ago)
  InstallationMedia: elementary OS 0.3 "Freya" - Daily amd64 (20140810)
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: elementary-meta
  SuspiciousXErrors:
   
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1425786] Re: Installing font via font viewer freezes system

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

** This bug is no longer a duplicate of bug 1375819
   gnome-font-viewer freezes up itself or the X session
** This bug has been marked a duplicate of bug 1183765
   During typography thumbnailing, the Font Viewer window becomes very 
unresponsive

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

Title:
  Installing font via font viewer freezes system

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

Bug description:
  Installing fonts for a specific program (trelby), if we open the font
  in font viewer and press the install button, it will install fine but
  the system will become unresponsive on successful install.  cannot
  open terminal for xkill, nor does any force close warning come up.
  The only way to get control is to ctrl+alt+f1 into commandline and
  sudo reboot the system.

  This is on an older laptop running Freya Beta 2 32bit.

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

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

[Desktop-packages] [Bug 1429539] Re: The system hangs during installation of fonts with font viewer elementary

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

** This bug is no longer a duplicate of bug 1375819
   gnome-font-viewer freezes up itself or the X session
** This bug has been marked a duplicate of bug 1183765
   During typography thumbnailing, the Font Viewer window becomes very 
unresponsive

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

Title:
  The system hangs during installation of fonts with font viewer
  elementary

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

Bug description:
  When installing the elementary sources freezes and only back to typing
  Ctrl + Alt + F2 and reboot. It has always happened, the fonts are
  .ttf.

  ProblemType: Bug
  DistroRelease: elementary OS 0.3
  Package: elementary-desktop 1.368+414~ubuntu0.3.1 [origin: 
LP-PPA-elementary-os-daily]
  Uname: Linux 3.19.0-031900-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CrashDB: elementary_meta
  CurrentDesktop: Pantheon
  Date: Sun Mar  8 05:47:35 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-03-08 (0 days ago)
  InstallationMedia: elementary OS 0.3 "Freya" - Daily amd64 (20150208)
  SourcePackage: elementary-meta
  SuspiciousXErrors:
   
  ThirdParty: True
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1862767] Re: gnome-control-center crashes when try to open it

2020-02-14 Thread adin

Further information.  After updating the packages the error returned
(nvidia is still uninstalled).

$ gnome-control-center --verbose
**
cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object:
 assertion failed: (G_IS_OBJECT (object))
Bail out! 
cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object:
 assertion failed: (G_IS_OBJECT (object))
Aborted (core dumped)

The kernel is the same.

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

Title:
  gnome-control-center crashes when try to open it

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

Bug description:
  gnome-control center crashes when trying to open it.  Tested as
  following

  $ gnome-control-center --verbose
  **
  
cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object:
 assertion failed: (G_IS_OBJECT (object))
  Bail out! 
cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object:
 assertion failed: (G_IS_OBJECT (object))
  Aborted (core dumped)

  When trying to open it through the graphical interface it dies
  silently.  A message of error would help too.

  Additional information:
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt-cache policy gnome-control-center
  gnome-control-center:
Installed: 1:3.34.1-1ubuntu2
Candidate: 1:3.34.1-1ubuntu2
Version table:
   *** 1:3.34.1-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 11 09:24:49 2020
  InstallationDate: Installed on 2018-05-07 (644 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago)

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

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

[Desktop-packages] [Bug 1863239] Re: /dev/bus/usb// device file of HP multi-function printer assigned to "audio" group

2020-02-14 Thread Till Kamppeter

** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-20.04

** Changed in: pulseaudio (Ubuntu)
Milestone: None => ubuntu-20.04

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

** Changed in: libmtp (Ubuntu)
Milestone: None => ubuntu-20.04

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

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in libmtp package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for the printer has group ownership "audio" and not "lp":

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

  The printer is the device /dev/bus/usb/001/063:

  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
  Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
  Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
  Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
  Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

  There must be a bug somewhere in the UDEV rules.

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

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

[Desktop-packages] [Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2020-02-14 Thread Sze Attila

Hi Yas and everyone on this page!
I'm totally 'rookie' in the world of Ubuntu LinuX.. I just some weeks ago 
arrived from "Bill's World" :D and firstly must to say a big sorry about my 
English. I have some important question about your "bug solution". Repeat: I'm 
really 'rookie' so please don't laugh on me.

1.) I find the /etc/xdg/autostart/spice-vdagent.desktop  file
2.) I can't find /usr/share/gdm/autostart/LoginWindow/spice-vdagent.desktop  
file! There is just a "Spice vdagent" named file, not the 
"spice-vdagent.desktop" file.. weird. (screen save attached)

How must to do it... step by step?
3.) When I open the  /etc/xdg/autostart/spice-vdagent.desktop  file with "sudo 
gedit" the "spice-vdagent.desktop" file contains these lines:
[Desktop Entry]
Name=Spice vdagent
Comment=Agent for Spice guests
Exec=/usr/bin/spice-vdagent
Terminal=false
Type=Application
Categories=
X-GNOME-Autostart-Phase=Initialization
NoDisplay=true

5.) Where must put it the  "X-GNOME-Autostart-enabled=false"  line in this 
file? At below is this correct..?
[Desktop Entry]
Name=Spice vdagent
Comment=Agent for Spice guests
Exec=/usr/bin/spice-vdagent
Terminal=false
Type=Application
Categories=
X-GNOME-Autostart-Phase=Initialization
X-GNOME-Autostart-enabled=false
NoDisplay=true

6.) When I changed and saved. Just copy this file into the
"/usr/share/gdm/autostart/LoginWindow/" folder...? Because that folder
not contains the "spice-vdagent.desktop file" there is just the "Spice
vdagent" file... or maybe I must open this "Spice vdagent" with "sudo
gedit" and write into that "X-GNOME-Autostart-enabled=false" line?

Thanx and waiting for your answers!
"May the Tux be with you, always."
:)

** Attachment added: "screen save – forum cannot access vdagent"
   
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+attachment/5328156/+files/screen%20save%20%E2%80%93%20forum%20cannot%20access%20vdagent

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

Title:
  spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

Status in spice-vdagent package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  $ journalctl -b

  [...]

  oct 26 07:26:57 romanescu spice-vdagent[1345]: Cannot access vdagent
  virtio channel /dev/virtio-ports/com.redhat.spice.0

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: spice-vdagent 0.17.0-1ubuntu2
  Uname: Linux 4.19.0-gnu x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 14:34:00 2018
  InstallationDate: Installed on 2017-10-13 (378 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: spice-vdagent
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions

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

[Desktop-packages] [Bug 1863239] [NEW] /dev/bus/usb// device file of HP multi-function printer assigned to "audio" group

2020-02-14 Thread Till Kamppeter

Public bug reported:

When testing HPLIP I found out that CUPS backends can access my printer
only when they are running as root, when they are running as the special
user lp, as it is usually the case, they cannot access the printer.

So I tried to find out why and saw that the /dev/bus/usb/*/* device file
for the printer has group ownership "audio" and not "lp":

till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$

The printer is the device /dev/bus/usb/001/063:

till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera
Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 

There must be a bug somewhere in the UDEV rules.

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

** Affects: systemd (Ubuntu)
 Importance: High
 Status: New

** Affects: udev (Ubuntu)
 Importance: High
 Status: New

** Description changed:

  When testing HPLIP I found out that CUPS backends can access my printer
  only when they are running as root, when they are running as the special
  user lp, as it is usually the case, they cannot access the printer.
  
  So I tried to find out why and saw that the /dev/bus/usb/*/* device file
  for the printer has group ownership "audio" and not "lp":
  
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll 
/dev/bus/usb/*/*
  crw-rw-r--  1 root root189,   0 Feb 11 14:17 /dev/bus/usb/001/001
  crw-rw-r--  1 root root189,   2 Feb 11 14:17 /dev/bus/usb/001/003
  crw-rw-r--  1 root root189,   3 Feb 11 14:17 /dev/bus/usb/001/004
  crw-rw-r--  1 root plugdev 189,   4 Feb 14 12:23 /dev/bus/usb/001/005
  crw-rw-r--  1 root root189,   5 Feb 11 14:17 /dev/bus/usb/001/006
  crw-rw+ 1 root audio   189,  62 Feb 14 12:37 /dev/bus/usb/001/063
  crw-rw-r--  1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001
  crw-rw-r--  1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003
+ till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$
+ 
+ The printer is the device /dev/bus/usb/001/063:
+ 
+ till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb
+ Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit 
Ethernet
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. 
+ Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated 
Camera
+ Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
+ Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor
+ Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ 
  
  There must be a bug somewhere in the UDEV rules.

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

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

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

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

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

Title:
  /dev/bus/usb/*/* device file of HP multi-function printer assigned to
  "audio" group

Status in pulseaudio package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in udev package in Ubuntu:
  New

Bug description:
  When testing HPLIP I found out that CUPS backends can access my
  printer only when they are running as root, when they are running as
  the special user lp, as it is usually the case, they cannot access the
  printer.

  So I tried to find out why and saw that the /dev/bus/usb/*/* device
  file for

[Desktop-packages] [Bug 1841783] Re: Update to 1.2.0?

2020-02-14 Thread Bug Watch Updater

** Changed in: speex (Debian)
   Status: Unknown => New

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

Title:
  Update to 1.2.0?

Status in speex package in Ubuntu:
  Triaged
Status in speex package in Debian:
  New

Bug description:
  The source was split in rc2, Debian didn't follow the change and we
  are in sync, do we want to update?

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

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

[Desktop-packages] [Bug 1863222] [NEW] Please update to hwdata 0.332

2020-02-14 Thread Amr Ibrahim

Public bug reported:

Please update hwdata to 0.332, and update the homepage and watch file to
better track newer versions.

https://github.com/vcrhonek/hwdata/releases

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


** Tags: focal upgrade-software-version

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

Title:
  Please update to hwdata 0.332

Status in hwdata package in Ubuntu:
  New

Bug description:
  Please update hwdata to 0.332, and update the homepage and watch file
  to better track newer versions.

  https://github.com/vcrhonek/hwdata/releases

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

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

[Desktop-packages] [Bug 1841783] Re: Update to 1.2.0?

2020-02-14 Thread Amr Ibrahim

The Debian maintainer has not touched the package since 2014. Maybe
Ubuntu should go ahead and update.

** Tags added: focal

** Bug watch added: Debian Bug tracker #949717
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949717

** Also affects: speex (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949717
   Importance: Unknown
   Status: Unknown

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

Title:
  Update to 1.2.0?

Status in speex package in Ubuntu:
  Triaged
Status in speex package in Debian:
  Unknown

Bug description:
  The source was split in rc2, Debian didn't follow the change and we
  are in sync, do we want to update?

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

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

[Desktop-packages] [Bug 1792932] Re: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.

2020-02-14 Thread Timo Aaltonen

thanks for testing!

I don't see how this update would regress qbzr autopkgtest (timeouts),
but somehow it seeemingly did

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

Title:
  Desktop fails to boot in vbox:  Xorg assert failure: Xorg:
  ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion
  `!global_keys[type].created' failed.

Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Confirmed
Status in xorg-server source package in Bionic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280
  https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80

  ---

  Test Case:
  Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box

  Actual Result
  Black screen or dropped to the login screen if the user skips ubiquity-dm

  Workaround:
  Add nomodeset on the kernel command line or from the boot menu, press F6 then 
select nomodeset

  Possibly a duplicate of bug 1432137

  Fix:
  Backport a patch from 1.20.2

  Regression potential:
  None really, we've had this xserver version since 18.10 and in the HWE 
backport, this patch backport is for 18.04 stock xserver but should work the 
same. It just skips initializing glamor if the system is using software 
fallback.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.20.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AssertionMessage: Xorg: ../../../../dix/privates.c:384: 
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
  CasperVersion: 1.395
  CompositorRunning: None
  Date: Mon Sep 17 12:42:24 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:

  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd ---  keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", 
file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92
   __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", 
file=0x563dbf96db38 "../../../../dix/privates.c", line=384, 
function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101
   dixRegisterPrivateKey ()
  Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: 
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1855220] Re: xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

2020-02-14 Thread Chris Guiver

I noticed this effect today on qa-test of lubuntu 20.04 daily on

hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)

This is a different box, however on the dc7700 the choppy behavior
occurs much of the time (still occurs as I tested on dc7700 earlier
today), today on this 8200 box the choppy behavior is far less, and only
occasional.

Blank & Cycle are still 10 mins, yet choppy behavior is occurring 3-15
secs (little point counting time on dc7700) so it's less evident, but
once you notice it - it sort of stands out here too.

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

Title:
  xscreensaver is choppy on lubuntu 20.04 daily qa-test (flurry)

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

Bug description:
  Lubuntu 20.04 daily QA-test on
  hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

  
  Displays have been adjusted to my setup (one above the other) but I doubt 
this is an issue

  I suspended system, waited, pressed ESC to wake & it resumed to
  xscreensaver, but 'flurry' was chopped and showing white/black patches
  on display as if glitching... I touched mouse & my session removed.

  opened xscreensaver & preview - yep glitch there too... changed to
  'fliptext' & no issues, but flurry is very jerky with image switching
  to almost-blocky-bad-signal (I think it's alternating between showing
  something else, text; it seems to vary on what I've had on screen
  before screensaver is loaded & continuing to show xscreensaver..)

  attempts to screengrab with delay have failed (just capturing black
  screen)..

  `lshw -C video` reports I'm using nouveau.

  This issue may not relate to 'xserver-xorg-video-nouveau', but I
  suspect it's there. I've performed this test a number of times on
  various boxes without issue (will do so again once I shutdown this).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-video-nouveau 1:1.0.16-1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.432
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Dec  5 04:04:51 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G86 [Quadro NVS 290] [10de:042f] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation G86 [Quadro NVS 290] [10de:0492]
  LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191204)
  MachineType: Hewlett-Packard HP Compaq dc7700 Small Form Factor
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash ---
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E1 v01.05
  dmi.board.name: 0A54h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E1v01.05:bd08/30/2006:svnHewlett-Packard:pnHPCompaqdc7700SmallFormFactor:pvr:rvnHewlett-Packard:rn0A54h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7700 Small Form Factor
  dmi.product.sku: ET090AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1855220/+subscriptions

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

[Desktop-packages] [Bug 1792932] Re: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.

2020-02-14 Thread Jean-Baptiste Lallement

I also tried the packages from proposed on top of 18.04.0 on which I
could reproduce the original issue and the packages from proposed fixed
it. double verification done.

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

Title:
  Desktop fails to boot in vbox:  Xorg assert failure: Xorg:
  ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion
  `!global_keys[type].created' failed.

Status in X.Org X server:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Xenial:
  Confirmed
Status in xorg-server source package in Bionic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280
  https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80

  ---

  Test Case:
  Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box

  Actual Result
  Black screen or dropped to the login screen if the user skips ubiquity-dm

  Workaround:
  Add nomodeset on the kernel command line or from the boot menu, press F6 then 
select nomodeset

  Possibly a duplicate of bug 1432137

  Fix:
  Backport a patch from 1.20.2

  Regression potential:
  None really, we've had this xserver version since 18.10 and in the HWE 
backport, this patch backport is for 18.04 stock xserver but should work the 
same. It just skips initializing glamor if the system is using software 
fallback.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.20.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AssertionMessage: Xorg: ../../../../dix/privates.c:384: 
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
  CasperVersion: 1.395
  CompositorRunning: None
  Date: Mon Sep 17 12:42:24 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcEnviron:

  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd ---  keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", 
file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92
   __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", 
file=0x563dbf96db38 "../../../../dix/privates.c", line=384, 
function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101
   dixRegisterPrivateKey ()
  Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: 
dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

-- 
Mailing list:

[Desktop-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0

Also, I even tried disabling the power saving feature
(i915.enable_psr=0) but it still seems to lock up or hang.

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:15 dharkan

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

apport information

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

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

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915

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

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  |

[Desktop-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0

| [Fri Feb 14 18:55:37 2020] i915 :00:02.0: GPU HANG: ecode 9:1:0x, 
hang on rcs0
| [Fri Feb 14 18:55:37 2020] GPU hangs can indicate a bug anywhere in the 
entire gfx stack, including userspace.
| [Fri Feb 14 18:55:37 2020] Please file a _new_ bug report on 
bugs.freedesktop.org against DRI -> DRM/Intel
| [Fri Feb 14 18:55:37 2020] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
| [Fri Feb 14 18:55:37 2020] The GPU crash dump is required to analyze GPU 
hangs, so please always attach it.
| [Fri Feb 14 18:55:37 2020] GPU crash dump saved to /sys/class/drm/card0/error
| [Fri Feb 14 18:55:37 2020] i915 :00:02.0: Resetting rcs0 for hang on rcs0
| [Fri Feb 14 18:55:45 2020] i915 :00:02.0: Resetting rcs0 for hang on rcs0

So included saved crash dump from /sys/class/drm/card0/error.


** Attachment added: "/sys/class/drm/card0/error"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1862865/+attachment/5328143/+files/drm-error.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584]

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

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on

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

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0

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

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on

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

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for

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

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting

[Desktop-packages] [Bug 1862865] PciMultimedia.txt

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328134/+files/PciMultimedia.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang

[Desktop-packages] [Bug 1862865] Card0.Codecs.codec.2.txt

apport information

** Attachment added: "Card0.Codecs.codec.2.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328129/+files/Card0.Codecs.codec.2.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting

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

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb

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

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0

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

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang

[Desktop-packages] [Bug 1862865] Card0.Codecs.codec.0.txt

apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328128/+files/Card0.Codecs.codec.0.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting

[Desktop-packages] [Bug 1862865] Lsusb-v.txt

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1862865/+attachment/5328133/+files/Lsusb-v.txt

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  |

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

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on

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

apport information

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

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

Title:
  i915 :00:02.0: Resetting rcs0 for stuck wait on rcs0

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Confirmed
Status in mesa source package in Focal:
  Invalid

Bug description:
  Hi,

  Every now and again, my session locks up with the following logged:

  | i915 :00:02.0: Resetting rcs0 for hang on rcs0

  Most of the time, it recovers on it's own but sometimes locks up
  completely requring a reboot. When that happens this is logged:

  | Feb  2 10:37:23 dharkan kernel: [71018.593184] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.593993] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.594130] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:23 dharkan kernel: [71018.595937] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:23 dharkan kernel: [71018.596728] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:28 dharkan kernel: [71022.816232] Asynchronous wait on fence 
i915:compiz[1495]:105ece timed out (hint:intel_atomic_commit_ready+0x0/0x54 
[i915])
  | Feb  2 10:37:31 dharkan kernel: [71026.593149] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.593958] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.596916] i915 :00:02.0: Resetting 
chip for hang on rcs0
  | Feb  2 10:37:31 dharkan kernel: [71026.598661] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:31 dharkan kernel: [71026.599391] [drm:gen8_reset_engines 
[i915]] *ERROR* rcs0 reset request timed out: {request: 0001, RESET_CTL: 
0001}
  | Feb  2 10:37:35 dharkan kernel: [71030.592141] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:39 dharkan kernel: [71034.323140] GpuWatchdog[1860]: segfault 
at 0 ip 55689a4eb33d sp 7f69b674d700 error 6 in 
chrome[5568968fd000+6abe000]
  | Feb  2 10:37:39 dharkan kernel: [71034.323157] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:37:43 dharkan kernel: [71038.592101] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:45 dharkan kernel: [71040.576093] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:47 dharkan kernel: [71042.592066] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:49 dharkan kernel: [71044.576075] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:51 dharkan kernel: [71046.592045] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:53 dharkan kernel: [71048.576098] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:55 dharkan kernel: [71050.592029] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:57 dharkan kernel: [71052.576037] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:37:59 dharkan kernel: [71054.592034] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:01 dharkan kernel: [71056.576021] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:03 dharkan kernel: [71058.592006] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:04 dharkan kernel: [71059.461584] GpuWatchdog[43507]: segfault 
at 0 ip 55ac6731833d sp 7fe71901e700 error 6 in 
chrome[55ac6372a000+6abe000]
  | Feb  2 10:38:04 dharkan kernel: [71059.461600] Code: 00 79 09 48 8b 7d a0 
e8 31 2c 72 fc 41 8b 85 00 01 00 00 85 c0 0f 84 ab 00 00 00 49 8b 45 00 4c 89 
ef be 01 00 00 00 ff 50 58  04 25 00 00 00 00 37 13 00 00 c6 05 61 3c 59 03 
01 80 bd 7f ff
  | Feb  2 10:38:05 dharkan kernel: [71060.575986] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:07 dharkan kernel: [71062.591982] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:09 dharkan kernel: [71064.575976] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:11 dharkan kernel: [71066.591956] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2 10:38:13 dharkan kernel: [71068.575937] i915 :00:02.0: Resetting 
rcs0 for hang on rcs0
  | Feb  2

[Desktop-packages] [Bug 1862865] Re: i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0