[Desktop-packages] [Bug 2027677] [NEW] Wrong desktop icon in new thunderbird release 115.0 of snap package

[Johannes Kaiser]

Public bug reported:

In the snap package of version 115.0 is wrong desktop icon.

It shows instead of the new icon (execpted something like this:
https://commons.wikimedia.org/wiki/File:Thunderbird_2023_icon.svg) the
old Thunderbird icon.

File needs to be replaced, which is probably located here:
/snap/thunderbird/350/meta/gui/thunderbird.png.

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

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

Title:
  Wrong desktop icon in new thunderbird release 115.0 of snap package

Status in thunderbird package in Ubuntu:
  New

Bug description:
  In the snap package of version 115.0 is wrong desktop icon.

  It shows instead of the new icon (execpted something like this:
  https://commons.wikimedia.org/wiki/File:Thunderbird_2023_icon.svg) the
  old Thunderbird icon.

  File needs to be replaced, which is probably located here:
  /snap/thunderbird/350/meta/gui/thunderbird.png.

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


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

[Desktop-packages] [Bug 544496] Re: [RS100] desktop became slow after upgrading to Lucid

[Johannes Satter]

You are right brooo https://crackshit.com/

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

Title:
  [RS100] desktop became slow after upgrading to Lucid

Status in xserver-xorg-driver-ati:
  Won't Fix
Status in xserver-xorg-video-ati package in Ubuntu:
  Incomplete
Status in Debian:
  Won't Fix

Bug description:
  [Problem]
  Switching to KMS as the default for radeon causes a performance regression, 
seen with compiz enabled or with 3D games.

  This is caused by the new vline support which prevents tearing with Xv
  but reduces performance as a consequence.

  [Workarounds]
  Pick your poison:
  * Disable compiz
  * Disable kms (grub: radeon.modeset=0)
  * Patch to revert the vline change
  * Wait for DRI2 page flipping support which will give better results for 
full-screen apps

  Situation on Maverick is worse on some chips.

  [Original Report]
  Binary package hint: xserver-xorg-video-ati

  I upgraded my laptop to Lucid somewhere around Alpha 2.

  The first thing that I noticed is that the display was much slower
  than in Karmic. I tried to run with and without modesetting, but there
  is no difference.

  Compositing worked fine in Karmic, however it is useless in Lucid,
  which means that performance of both 2D and 3D regreessed.

  CPU load of Xorg is high as soon as there is some activity on the
  screen.

  I was also trying to enable different options in xorg.conf
  (http://dri.freedesktop.org/wiki/ATIRadeon) with no success.

  ProblemType: Bug
  Architecture: i386
  CheckboxSubmission: fd17ddbce499316ea5512e53f255b019
  CheckboxSystem: 79d4f9e1ffc31ae443cb2de53cd33e42
  Date: Mon Mar 22 21:21:40 2010
  DistroRelease: Ubuntu 10.04
  DkmsStatus: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Compaq Presario
  Package: xserver-xorg-video-radeon 1:6.12.191-1ubuntu2
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     3.3V 32-bit PC Card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic 
root=UUID=737a8285-476e-4d78-9849-96d939d64b95 ro single
  ProcEnviron:
   LANG=sl_SI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  SourcePackage: xserver-xorg-video-ati
  Uname: Linux 2.6.32-16-generic i686
  dmi.bios.date: 11/25/2003
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 0F0B
  dmi.board.name: 07D4h
  dmi.board.vendor: Compaq
  dmi.board.version: KBC Revision: 1328
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compaq
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr0F0B:bd11/25/2003:svnCompaq:pnPresario:pvr0100:rvnCompaq:rn07D4h:rvrKBCRevision1328:cvnCompaq:ct10:cvrN/A:
  dmi.product.name: Presario
  dmi.product.version: 0100
  dmi.sys.vendor: Compaq
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-16-generic
  ---
  Architecture: i386
  CheckboxSubmission: fd17ddbce499316ea5512e53f255b019
  CheckboxSystem: 79d4f9e1ffc31ae443cb2de53cd33e42
  DistroRelease: Ubuntu 10.04
  DkmsStatus: Error: [Errno 2] No such file or directory
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Compaq Presario
  Package: xserver-xorg-video-ati 
1:6.12.191+git20100314.67e81c8f-0ubuntu0sarvatt
  PackageArchitecture: i386
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     3.3V 32-bit PC Card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic 
root=UUID=737a8285-476e-4d78-9849-96d939d64b95 ro quiet lapic splash
  ProcEnviron:
   LANG=sl_SI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
  Tags: lucid lucid
  Uname: Linux 2.6.32-16-generic i686
  UnreportableReason: This is not a genuine Ubuntu package
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev 
plugdev powerdev scanner tape video www-data
  dmi.bios.date: 11/25/2003
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 0F0B
  dmi.board.name: 07D4h
  dmi.board.vendor: Compaq
  dmi.board.version: KBC Revision: 1328
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compaq
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenix:bvr0F0B:bd11/25/2003:svnCompaq:pnPresario:pvr0100:rvnCompaq:rn07D4h:rvrKBCRevision1328:cvnCompaq:ct10:cvrN/A:
  dmi.product.name: Presario
  dmi.product.version: 0100
  dmi.sys.vendor: Compaq
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-16-generic

  [lspci]
  01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon 
Mobility U1 [1002:4336]
   Subsystem: Compaq Computer Corporation Device 

[Desktop-packages] [Bug 2002453] [NEW] wayland external monitor turned off for second user

[Johannes Timm]

Public bug reported:

Im using Gonome-Wayland for the login screen and user sessions on my
hybrid (Intel+Nvidia) laptop.

When Im in the login screen all monitors are turned on (and display the
mouse). The first user that logs in and starts its Wayland session can
use all screens. This session is left running and the swithc user
functionality is used to log into the other account. Here only the
Laptop screen (intel) works, the external screen turns off (no signal).
Within the login screen all screens work.

Im using the multiuser capabilities to distinguish between my "work" and
"personal" user profile.

Its intended that both users and the login screen may use all screens at
all times. Theoretically each user may have their personal set of
devices using advanced features of loginctl.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
Uname: Linux 5.15.0-57-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 10 23:57:02 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-07-16 (178 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  wayland external monitor turned off for second user

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Im using Gonome-Wayland for the login screen and user sessions on my
  hybrid (Intel+Nvidia) laptop.

  When Im in the login screen all monitors are turned on (and display
  the mouse). The first user that logs in and starts its Wayland session
  can use all screens. This session is left running and the swithc user
  functionality is used to log into the other account. Here only the
  Laptop screen (intel) works, the external screen turns off (no
  signal). Within the login screen all screens work.

  Im using the multiuser capabilities to distinguish between my "work"
  and "personal" user profile.

  Its intended that both users and the login screen may use all screens
  at all times. Theoretically each user may have their personal set of
  devices using advanced features of loginctl.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.5-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74
  Uname: Linux 5.15.0-57-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 10 23:57:02 2023
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-07-16 (178 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  RelatedPackageVersions: mutter-common 42.5-0ubuntu1
  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/2002453/+subscriptions


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

[Desktop-packages] [Bug 1968910] Re: Extension NAME already installed in /usr/share/gnome-shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not be loaded

[Johannes]

Try
:~$ gnome-shell-extension-prefs

I had the same problem and somehow extensions where disabled globally
while having the exact same log messages. If that's what you are
experiencing, the bug is reduced to misleading log entries.

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

Title:
  Extension NAME already installed in /usr/share/gnome-
  shell/extensions/NAME. /usr/share/gnome-shell/extensions/NAME will not
  be loaded

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I see the following error messages in the system logs about gnome-
  shell extensions:

  # journalctl | grep Extension
  [...]
  Apr 13 18:30:51 jophur gnome-shell[831]: Extension d...@rastersoft.com 
already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. 
/usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded
  Apr 13 18:30:51 jophur gnome-shell[831]: Extension 
ubuntu-appindicat...@ubuntu.com already installed in 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. 
/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be 
loaded
  Apr 13 18:30:51 jophur gnome-shell[831]: Extension ubuntu-d...@ubuntu.com 
already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. 
/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be loaded

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell-extension-ubuntu-dock 72~ubuntu3
  Uname: Linux 5.17.2-051702-generic x86_64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Apr 13 19:57:37 2022
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-ubuntu-dock
  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/1968910/+subscriptions


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

[Desktop-packages] [Bug 1970615] Re: WebGL does not work in snap firefox

[Johannes Stöckelmaier]

This problem also occurred to me using a fresh install of Ubuntu 22.04.

Firefox throws an error:
glxtest: Could not connect to wayland socket

Firefox falls back to xwayland. I noticed it as all the text was unsharp using 
fractional scaling.
The problem also occurred when removing firefox snap and installing it as 
flatpak.

Using firefox-esr (91.8) as snap solves the problem.

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

Title:
  WebGL does not work in snap firefox

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Ubuntu 22.04 LTS I am no longer able to use WebGL
  on firefox.

  If I go to https://get.webgl.org/ it says
  "Hmm. While your browser seems to support WebGL, it is disabled or 
unavailable. If possible, please ensure that you are running the latest drivers 
for your video card."

  This is the case on my laptop with Intel HD4600 Graphics and on my
  desktop with AMD Vega 56 Graphics. Both are on Ubuntu 22.04 LTS with
  snap firefox.

  troels@troels-thinkpad:~$ glxinfo | grep OpenGL
  OpenGL vendor string: Intel
  OpenGL renderer string: Mesa Intel(R) HD Graphics 4600 (HSW GT2)
  OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.0.1
  OpenGL core profile shading language version string: 4.60
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile
  OpenGL core profile extensions:
  OpenGL version string: 3.1 Mesa 22.0.1
  OpenGL shading language version string: 1.40
  OpenGL context flags: (none)
  OpenGL extensions:
  OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.1
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
  OpenGL ES profile extensions:

  
  I therefore have to use Chrome instead for developement using three.js

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


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

[Desktop-packages] [Bug 1965639] Re: purple screen after login using fingerprint

[Johannes Zeiser]

Here is the file from step 3

The directory /var/crash is empty, or at least ls /var/crash/ does not
return anything.

There are some error reports, but just about onedrive and they are from
last year, so I doubt they are relevant for this problem.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965639/+attachment/5571260/+files/prevboot.txt

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

Title:
  purple screen after login using fingerprint

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I updated the machine yesterday, and additionally added the
  fingerprint to pam using pam-auth-update. The screen now stays purple
  after logging in using the finger, but works fine after logging in
  using the password.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 19 21:37:43 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.103.01, 5.13.0-28-generic, x86_64: installed
   nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2294]
  InstallationDate: Installed on 2020-12-10 (464 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20NN002NGE
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic 
root=UUID=2bcb2bd8-2364-4f28-9085-f6c366d45c6d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/24/2021
  dmi.bios.release: 1.89
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2LET89W (1.89 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NN002NGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2LET89W(1.89):bd11/24/2021:br1.89:efr1.20:svnLENOVO:pn20NN002NGE:pvrThinkPadX390Yoga:rvnLENOVO:rn20NN002NGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20NN_BU_Think_FM_ThinkPadX390Yoga:
  dmi.product.family: ThinkPad X390 Yoga
  dmi.product.name: 20NN002NGE
  dmi.product.sku: LENOVO_MT_20NN_BU_Think_FM_ThinkPad X390 Yoga
  dmi.product.version: ThinkPad X390 Yoga
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  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+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Desktop-packages] [Bug 1953010] [NEW] [snap] WebMIDI not working

[Johannes Feulner]

Public bug reported:

WebMIDI does not work when chromium is installed from snap package.
However, it works when installed via apt install.

Chromium version: Version 93.0.4577.82 (Offizieller Build) snap (64-Bit)  
Channel: stable
OS Version: Ubuntu 20

Steps to reproduce the problem:
1. Execute in brower's console

if (navigator.requestMIDIAccess) {
   navigator.requestMIDIAccess({sysex: false})
  .then(m => alert("WebMIDI ready")) .catch(m =>alert("WebMIDI failed"));
 } else {
 alert("Sorry, no WebMIDI support in your browser.");
 }

What is the expected behavior?
alert: WebMIDI ready

What went wrong?
alert: WebMIDI failed, WebMIDI cannot be used at all

Without the catch-clause the error message is:
Uncaught (in promise) DOMException: Platform dependent initialization failed.

Did this work before? Yes Version 90.0.4430.72 (Offizieller Build) Built
on Ubuntu installed via apt install.

See also:
https://bugs.chromium.org/p/chromium/issues/detail?id=1254727=reporter%3Ajofeux%40gmail.com=1

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


** Tags: snap webmidi

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

Title:
  [snap] WebMIDI not working

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  WebMIDI does not work when chromium is installed from snap package.
  However, it works when installed via apt install.

  Chromium version: Version 93.0.4577.82 (Offizieller Build) snap (64-Bit)  
Channel: stable
  OS Version: Ubuntu 20

  Steps to reproduce the problem:
  1. Execute in brower's console

  if (navigator.requestMIDIAccess) {
 navigator.requestMIDIAccess({sysex: false})
.then(m => alert("WebMIDI ready")) .catch(m =>alert("WebMIDI failed"));
   } else {
   alert("Sorry, no WebMIDI support in your browser.");
   }

  What is the expected behavior?
  alert: WebMIDI ready

  What went wrong?
  alert: WebMIDI failed, WebMIDI cannot be used at all

  Without the catch-clause the error message is:
  Uncaught (in promise) DOMException: Platform dependent initialization failed.

  Did this work before? Yes Version 90.0.4430.72 (Offizieller Build)
  Built on Ubuntu installed via apt install.

  See also:
  
https://bugs.chromium.org/p/chromium/issues/detail?id=1254727=reporter%3Ajofeux%40gmail.com=1

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


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

[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

[Johannes]

I am affected, although not every time I resume my laptop. Perhaps 10 %
of the times, and possibly with more likelihood if my laptop has been
suspended for a while.

I haven't yet found how to reproduce this bug in a repeatable manner.
Have you got clues? or do you want me to upload some logs (tell me which logs)?

PS: Using Ubuntu 21.04 with GNOME 3.38.

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

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


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

[Desktop-packages] [Bug 1943569] Re: Sometimes distorted sound in or after Firefox

[Johannes Mages]

I think it occured before too. But as I mentioned in a older bug report
of me (https://bugs.launchpad.net/bugs/1930192) it could be a Firefox-
thing because it occur mostly after I started Firefox. Now I switched to
Brave and will test if the issue also occur here.

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

Title:
  Sometimes distorted sound in or after Firefox

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Sometimes when I open Firefox and play a video or start Plex Media
  Player or start to play a game I get a distorted audio/sound.

  I modified the Pulse Audio daemon.conf by this tutorial
  https://medium.com/@gamunu/enable-high-quality-audio-on-
  linux-6f16f3fe7e1f to improve the sound in Linux. The deamon.conf
  should be attached. When I get this issue I have to open a terminal
  and enter »pulseaudio -k«. After this it's normal again.

  Here's a complete hwinfo:
  https://gist.github.com/Johnnii360/1cbdbb0f27180013652a01f21c2f4792

  My sound card is a Creative SoundBlaster X-Fi Titanium Fatal1ty (EMU20k2).
  Kernel version: 5.4.0-84-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Sep 14 12:25:30 2021
  InstallationDate: Installed on 2019-11-10 (674 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.40
  dmi.board.name: Z390 Phantom Gaming 4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2021-05-31T09:26:29.202354
  mtime.conffile..etc.pulse.daemon.conf: 2020-12-26T09:12:04.962975

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


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

[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer

[Johannes Mages]

Ooookay... I've seen a comment in the Ubuntu Software Center at the
Firefox that the Firefox cause this weird freezes.

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

Title:
  gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-
  offscreen-effect.c:213: Unable to create an Offscreen buffer

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Addition for bug report 1930128

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat May 29 12:20:21 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1608008084
  GsettingsChanges:
   b'org.gnome.desktop.background' b'show-desktop-icons' b'true'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

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


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

[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer

[Johannes Mages]

Okay today it really happened again after standby mode. I got nothing
about a crash in /var/crash and in my
https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4
isn't something either. Magic SysRq couldn't be used because the system
was completely frozen.

This is the only thing I can offer you, but maybe it will not help you:

20:16:17 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps
20:12:43 gvfsd-dnssd: Error calling org.gtk.vfs.MonitorClient.Changed(): 
Zeitüberschreitung wurde erreicht (g-io-error-quark, 24)
20:12:43 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps
20:12:13 Xorg: (II) event1  - Power Button: device is a keyboard
20:12:13 gnome-shell: cr_declaration_parse_list_from_buf: assertion 'parser' 
failed
20:12:13 Xorg: (II) event8  - Logitech Gaming Mouse G502 Keyboard: device is a 
keyboard
20:12:13 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps
20:12:13 Xorg: (II) systemd-logind: got resume for 13:69
20:12:12 psensor: [2021-09-14T18:12:12] [ERR] nvctrl: Failed to retrieve 
measure of type 20204 for NVIDIA GPU 1
20:12:12 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps
19:14:29 Xorg: (II) systemd-logind: got pause for 13:65
19:14:28 MainThread: Sandbox: attempt to open unexpected file /proc/self/maps

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

Title:
  gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-
  offscreen-effect.c:213: Unable to create an Offscreen buffer

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Addition for bug report 1930128

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat May 29 12:20:21 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1608008084
  GsettingsChanges:
   b'org.gnome.desktop.background' b'show-desktop-icons' b'true'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

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


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

[Desktop-packages] [Bug 1943569] Re: Sometimes distorted sound in or after Firefox

[Johannes Mages]

** Attachment added: "daemon.conf"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1943569/+attachment/5525159/+files/daemon.conf

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

Title:
  Sometimes distorted sound in or after Firefox

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sometimes when I open Firefox and play a video or start Plex Media
  Player or start to play a game I get a distorted audio/sound.

  I modified the Pulse Audio daemon.conf by this tutorial
  https://medium.com/@gamunu/enable-high-quality-audio-on-
  linux-6f16f3fe7e1f to improve the sound in Linux. The deamon.conf
  should be attached. When I get this issue I have to open a terminal
  and enter »pulseaudio -k«. After this it's normal again.

  Here's a complete hwinfo:
  https://gist.github.com/Johnnii360/1cbdbb0f27180013652a01f21c2f4792

  My sound card is a Creative SoundBlaster X-Fi Titanium Fatal1ty (EMU20k2).
  Kernel version: 5.4.0-84-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Sep 14 12:25:30 2021
  InstallationDate: Installed on 2019-11-10 (674 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.40
  dmi.board.name: Z390 Phantom Gaming 4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2021-05-31T09:26:29.202354
  mtime.conffile..etc.pulse.daemon.conf: 2020-12-26T09:12:04.962975

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


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

[Desktop-packages] [Bug 1943569] [NEW] Sometimes distorted sound in or after Firefox

[Johannes Mages]

Public bug reported:

Sometimes when I open Firefox and play a video or start Plex Media
Player or start to play a game I get a distorted audio/sound.

I modified the Pulse Audio daemon.conf by this tutorial
https://medium.com/@gamunu/enable-high-quality-audio-on-
linux-6f16f3fe7e1f to improve the sound in Linux. The deamon.conf should
be attached. When I get this issue I have to open a terminal and enter
»pulseaudio -k«. After this it's normal again.

Here's a complete hwinfo:
https://gist.github.com/Johnnii360/1cbdbb0f27180013652a01f21c2f4792

My sound card is a Creative SoundBlaster X-Fi Titanium Fatal1ty (EMU20k2).
Kernel version: 5.4.0-84-generic

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.11
ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
Uname: Linux 5.4.0-84-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Sep 14 12:25:30 2021
InstallationDate: Installed on 2019-11-10 (674 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.40
dmi.board.name: Z390 Phantom Gaming 4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
modified.conffile..etc.pulse.daemon.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-05-31T09:26:29.202354
mtime.conffile..etc.pulse.daemon.conf: 2020-12-26T09:12:04.962975

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


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

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

Title:
  Sometimes distorted sound in or after Firefox

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sometimes when I open Firefox and play a video or start Plex Media
  Player or start to play a game I get a distorted audio/sound.

  I modified the Pulse Audio daemon.conf by this tutorial
  https://medium.com/@gamunu/enable-high-quality-audio-on-
  linux-6f16f3fe7e1f to improve the sound in Linux. The deamon.conf
  should be attached. When I get this issue I have to open a terminal
  and enter »pulseaudio -k«. After this it's normal again.

  Here's a complete hwinfo:
  https://gist.github.com/Johnnii360/1cbdbb0f27180013652a01f21c2f4792

  My sound card is a Creative SoundBlaster X-Fi Titanium Fatal1ty (EMU20k2).
  Kernel version: 5.4.0-84-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.11
  ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133
  Uname: Linux 5.4.0-84-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Sep 14 12:25:30 2021
  InstallationDate: Installed on 2019-11-10 (674 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.40
  dmi.board.name: Z390 Phantom Gaming 4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be 

[Desktop-packages] [Bug 1937916] Re: xrandr --scale 0.5 confines display to native solution on secondary sceen, but mouse moves on the upscaled screen

[Johannes Kalliauer]

** Summary changed:

-  xrandr --scale confines mouse to native solution on secondary sceen
+ xrandr --scale 0.5 confines display to native solution on secondary sceen, 
but mouse moves on the upscaled screen

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

Title:
  xrandr --scale 0.5 confines display to native solution on secondary
  sceen, but mouse moves on the upscaled screen

Status in xorg-server package in Ubuntu:
  New

Bug description:
  `--scale 0.5 --filter nearest` works on the internal screen, however
  not on the external screen (via USB-C with Display-Port)

  `xrandr --output eDP-1 --primary --mode 1920x1080 --pos 0x0 --scale
  0.5 --filter nearest --dpi 141 --output DP-1-3 --mode 3840x2160
  --scale .5 --pos 960x0 --filter nearest`

  results in a display of the solution 1920x1080 (upper left quater),
  however the mouse uses the whole 3840x2160-space, leading to an offset
  between mouse and display.

  However this does not occur on the internal screen.

  xrandr:
  xrandr program version   1.5.1
  Server reports RandR version 1.6

  host:
   Static hostname: lws84.imws.tuwien.ac.at
 Icon name: computer-laptop
   Chassis: laptop
  Operating System: Fedora 34 (Workstation Edition) 
   CPE OS Name: cpe:/o:fedoraproject:fedora:34
Kernel: Linux 5.13.4-200.fc34.x86_64
  Architecture: x86-64
   Hardware Vendor: Lenovo
Hardware Model: ThinkPad P15 Gen 1

  Screen:
  https://www.lg.com/de/monitore/lg-27UK670-B

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


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

[Desktop-packages] [Bug 1937916] [NEW] xrandr --scale confines mouse to native solution on secondary sceen

[Johannes Kalliauer]

Public bug reported:

`--scale 0.5 --filter nearest` works on the internal screen, however not
on the external screen (via USB-C with Display-Port)

`xrandr --output eDP-1 --primary --mode 1920x1080 --pos 0x0 --scale 0.5
--filter nearest --dpi 141 --output DP-1-3 --mode 3840x2160 --scale .5
--pos 960x0 --filter nearest`

results in a display of the solution 1920x1080 (upper left quater),
however the mouse uses the whole 3840x2160-space, leading to an offset
between mouse and display.

However this does not occur on the internal screen.

xrandr:
xrandr program version   1.5.1
Server reports RandR version 1.6

host:
 Static hostname: lws84.imws.tuwien.ac.at
   Icon name: computer-laptop
 Chassis: laptop
Operating System: Fedora 34 (Workstation Edition) 
 CPE OS Name: cpe:/o:fedoraproject:fedora:34
  Kernel: Linux 5.13.4-200.fc34.x86_64
Architecture: x86-64
 Hardware Vendor: Lenovo
  Hardware Model: ThinkPad P15 Gen 1

Screen:
https://www.lg.com/de/monitore/lg-27UK670-B

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

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

Title:
   xrandr --scale confines mouse to native solution on secondary sceen

Status in xorg-server package in Ubuntu:
  New

Bug description:
  `--scale 0.5 --filter nearest` works on the internal screen, however
  not on the external screen (via USB-C with Display-Port)

  `xrandr --output eDP-1 --primary --mode 1920x1080 --pos 0x0 --scale
  0.5 --filter nearest --dpi 141 --output DP-1-3 --mode 3840x2160
  --scale .5 --pos 960x0 --filter nearest`

  results in a display of the solution 1920x1080 (upper left quater),
  however the mouse uses the whole 3840x2160-space, leading to an offset
  between mouse and display.

  However this does not occur on the internal screen.

  xrandr:
  xrandr program version   1.5.1
  Server reports RandR version 1.6

  host:
   Static hostname: lws84.imws.tuwien.ac.at
 Icon name: computer-laptop
   Chassis: laptop
  Operating System: Fedora 34 (Workstation Edition) 
   CPE OS Name: cpe:/o:fedoraproject:fedora:34
Kernel: Linux 5.13.4-200.fc34.x86_64
  Architecture: x86-64
   Hardware Vendor: Lenovo
Hardware Model: ThinkPad P15 Gen 1

  Screen:
  https://www.lg.com/de/monitore/lg-27UK670-B

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


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

[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer

[Johannes Mages]

Ah never mind. The Display Port of my RTX 2070 stopped working.

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

Title:
  gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-
  offscreen-effect.c:213: Unable to create an Offscreen buffer

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Addition for bug report 1930128

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat May 29 12:20:21 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1608008084
  GsettingsChanges:
   b'org.gnome.desktop.background' b'show-desktop-icons' b'true'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

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


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

[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer

[Johannes Mages]

Hi Daniel! The issue occurred again today. In this time I was connected
via AnyDesk to my PC from my office to fill my database in Tellico. Now
it's always black screen. I will add some additional informations this
evening when I'm at home.

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

Title:
  gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-
  offscreen-effect.c:213: Unable to create an Offscreen buffer

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Addition for bug report 1930128

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat May 29 12:20:21 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1608008084
  GsettingsChanges:
   b'org.gnome.desktop.background' b'show-desktop-icons' b'true'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

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


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

[Desktop-packages] [Bug 1768609] Re: can't add KDE apps to GNOME dock

[Johannes Kalliauer]

The user can make a workaround, by using the .desktop the same
as the `WM_CASS` (returned by the command `xprop`).

e.g.
- for Doplin use `dolphin.desktop`
- for JabRef use `org.jabref.gui.JabRefMain.desktop`
 
source: https://askubuntu.com/a/1347954/676490

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

Title:
  can't add KDE apps to GNOME dock

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

Bug description:
  Hi,

  I clean installed Ubuntu 18.04 yesterday and noticed I couldn't add
  KDE apps to the GNOME dock. Basically, the "Add to Favorites" option
  is missing from the right-click menu of dock icons of currently-
  running KDE apps.

  If I search for a KDE app using the "Show Applications" button, and
  right-click on an app in the search results before running it, that
  menu does contain "Add to Favorites". However, if this is used, the
  added app behaves incorrectly, in that clicking on its icon in the
  dock always launches a new instance rather than bringing any existing
  instance to the front.

  Previously I used Ubuntu 14.04 (with Unity) and KDE apps could be
  added to the dock and managed as expected (i.e. clicking app icon when
  app is running brought it to the front).

  Some searching around suggests this might be related to missing
  StartWMClass fields in the .desktop files of the KDE apps. I added
  StartWMClass=kate to /usr/share/applications/org.kde.kate.desktop and
  that seemed to fix the problem. However this didn't work for Konsole,
  so there might be more to fixing this in general.

  I think this is probably either a KDE bug (they need to correct all
  their .desktop files?), a GNOME bug, or at the very least an Ubuntu-
  level regression in the Unity->GNOME transition that may justify
  taking action somewhere.

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

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

[Desktop-packages] [Bug 1930729] [NEW] File-Roller unpacks file wrongly on »Extract here« in Nautilus

[Johannes Mages]

Public bug reported:

At the time I'm on arranging my Atari ST disk images for my Gotek USB-
Stick Floppy Emulator. I downloaded the zipped images from a specific
homepage. Many were be unzipped correctly but some not. I'm use here the
»Extract here« command in Nautilus.

So... When I unzip the archives there will be created a folder with the
name of the zip file itself (I wish I could also unzip without that like
in 7-Zip etc.) and the zipped file in the zip archive will be placed in
this folder. But there are some zips it's not like above. On this zips
it will be created with the name of the zipped file (file in the zip
archive) and the folder itself is empty.

For example:

Zip file »bubble_bobble.zip« contains »Bubble Bobble.STX« so it will be
created a folder named »Bubble Bobble« with the »Bubble Bobble.STX« file
placed in it. That's correct!

Zip file »chuckie_egg.zip« contains »chuckie_egg.STX« and File-Roller
creates a folder named »chuckie_egg.STX« with no placed file in it. It's
like File-Roller ignores the base folder creation and tries to extract
the file as I basically want. So I have open every single failed zip
file in File-Roller and have to unzip it manually by click on »Extract«.
THEN FR unzipps it correctly. I also tried a newer version from Flathub
(3.38.0) but it's the same issue here.

Because I miss the function on »Extract here« to choose between "Naked"
(without folder) and with creating a folder named like the zip file
itself.

I hope you understand what I mean?! ;)

I attached you the zip for more diagnostics by your side.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: file-roller 3.36.3-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun  3 17:06:20 2021
InstallationDate: Installed on 2019-11-10 (571 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: file-roller
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.apport.crashdb.conf: 2021-05-31T09:26:29.202354

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "On of the failing zip files"
   
https://bugs.launchpad.net/bugs/1930729/+attachment/5502212/+files/chuckie_egg.zip

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

Title:
  File-Roller unpacks file wrongly on »Extract here« in Nautilus

Status in file-roller package in Ubuntu:
  New

Bug description:
  At the time I'm on arranging my Atari ST disk images for my Gotek USB-
  Stick Floppy Emulator. I downloaded the zipped images from a specific
  homepage. Many were be unzipped correctly but some not. I'm use here
  the »Extract here« command in Nautilus.

  So... When I unzip the archives there will be created a folder with
  the name of the zip file itself (I wish I could also unzip without
  that like in 7-Zip etc.) and the zipped file in the zip archive will
  be placed in this folder. But there are some zips it's not like above.
  On this zips it will be created with the name of the zipped file (file
  in the zip archive) and the folder itself is empty.

  For example:

  Zip file »bubble_bobble.zip« contains »Bubble Bobble.STX« so it will
  be created a folder named »Bubble Bobble« with the »Bubble Bobble.STX«
  file placed in it. That's correct!

  Zip file »chuckie_egg.zip« contains »chuckie_egg.STX« and File-Roller
  creates a folder named »chuckie_egg.STX« with no placed file in it.
  It's like File-Roller ignores the base folder creation and tries to
  extract the file as I basically want. So I have open every single
  failed zip file in File-Roller and have to unzip it manually by click
  on »Extract«. THEN FR unzipps it correctly. I also tried a newer
  version from Flathub (3.38.0) but it's the same issue here.

  Because I miss the function on »Extract here« to choose between
  "Naked" (without folder) and with creating a folder named like the zip
  file itself.

  I hope you understand what I mean?! ;)

  I attached you the zip for more diagnostics by your side.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: file-roller 3.36.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  3 17:06:20 2021
  InstallationDate: Installed on 2019-11-10 (571 days ago)
  

[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer

[Johannes Mages]

I already did. This is the addition for 1930128. There is no extra crash
file for gnome shell. This here is the only one.

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

Title:
  gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-
  offscreen-effect.c:213: Unable to create an Offscreen buffer

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Addition for bug report 1930128

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat May 29 12:20:21 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1608008084
  GsettingsChanges:
   b'org.gnome.desktop.background' b'show-desktop-icons' b'true'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

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

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

[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer

[Johannes Mages]

Oh, didn't see that. Sorry! But yes I had this issue sometimes in the
past but now was the time to report it finally. :) It's a bit annoying
to get this freeze sometimes. But I don't know in what connection with
what App it was.

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

Title:
  gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-
  offscreen-effect.c:213: Unable to create an Offscreen buffer

Status in mutter package in Ubuntu:
  New

Bug description:
  Addition for bug report 1930128

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat May 29 12:20:21 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1608008084
  GsettingsChanges:
   b'org.gnome.desktop.background' b'show-desktop-icons' b'true'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

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

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

[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer

[Johannes Mages]

Hi Daniel,

sorry but in this case there is no error tracker for 2021-05-29:
https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4

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

Title:
  gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-
  offscreen-effect.c:213: Unable to create an Offscreen buffer

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Addition for bug report 1930128

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat May 29 12:20:21 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1608008084
  GsettingsChanges:
   b'org.gnome.desktop.background' b'show-desktop-icons' b'true'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

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

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

[Desktop-packages] [Bug 1930128] Re: Xorg freeze

[Johannes Mages]

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  I just started Foxit Reader to config it. While I browse through the
  title menues to find the preferences the whole GDM or x.org sessione
  freezes. The only way to restart was to some restart commands over the
  Off-Shell (Ctrl + Alt + F3).

  Wont fixed the issue:

  - busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s 
'Meta.restart("Restarting...")'
  - sudo killall -HUP gnome-shell
  - sudo systemctl restart gdm (kicked me back to login after every login)

  Fixed the issue:
  - sudo systemctl restart systemd-logind

  The last command fixed it after a short time. I tried to jump back
  every time with Ctrl + Alt + F1 and anytime it worked.

  I have no idea if this is a Foxit Reader bug or a issue by GDM/xorg.

  I additionally attached you my latest protocols. In this time the
  freeze occured.

  Best regards,
  Johannes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.80  Fri May  7 06:55:54 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 29 12:28:07 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.80, 5.4.0-73-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2070 Rev. A] 
[1043:875c]
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=454b3874-3032-4cb6-9e5c-92a00ed53afb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.40
  dmi.board.name: Z390 Phantom Gaming 4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  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+git20200226-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/xorg-server/+bug/1930128/+subscriptions

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

[Desktop-packages] [Bug 1930192] Re: Addition for bug 1930128

[Johannes Mages]

** Information type changed from Private to Public

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

Title:
  Addition for bug 1930128

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Addition for bug report 1930128

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat May 29 12:20:21 2021
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1608008084
  GsettingsChanges:
   b'org.gnome.desktop.background' b'show-desktop-icons' b'true'
   b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
   b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
   b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /var/lib/gdm3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/false
  RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

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

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

[Desktop-packages] [Bug 1930128] Re: Xorg freeze

[Johannes Mages]

Hi Daniel!

Thank you for your help. I've tried step 1 and 2 but both failed at
first. So I've done step 3 and applied the workaround, restarted the
system and tried to reproduce the issue. Nothing, all is working fine.
But now I've tried to resend the crash file and now it worked.

Here's the new bug report: https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1930192

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

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hello!

  I just started Foxit Reader to config it. While I browse through the
  title menues to find the preferences the whole GDM or x.org sessione
  freezes. The only way to restart was to some restart commands over the
  Off-Shell (Ctrl + Alt + F3).

  Wont fixed the issue:

  - busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s 
'Meta.restart("Restarting...")'
  - sudo killall -HUP gnome-shell
  - sudo systemctl restart gdm (kicked me back to login after every login)

  Fixed the issue:
  - sudo systemctl restart systemd-logind

  The last command fixed it after a short time. I tried to jump back
  every time with Ctrl + Alt + F1 and anytime it worked.

  I have no idea if this is a Foxit Reader bug or a issue by GDM/xorg.

  I additionally attached you my latest protocols. In this time the
  freeze occured.

  Best regards,
  Johannes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.80  Fri May  7 06:55:54 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 29 12:28:07 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.80, 5.4.0-73-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2070 Rev. A] 
[1043:875c]
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=454b3874-3032-4cb6-9e5c-92a00ed53afb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.40
  dmi.board.name: Z390 Phantom Gaming 4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  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+git20200226-1
  version.xserver-xo

[Desktop-packages] [Bug 1930128] Re: Xorg freeze

[Johannes Mages]

Ah I forgot to mention that Foxit Reader was installed by their
installation script. It's no Flatpak or snapcraft.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello!

  I just started Foxit Reader to config it. While I browse through the
  title menues to find the preferences the whole GDM or x.org sessione
  freezes. The only way to restart was to some restart commands over the
  Off-Shell (Ctrl + Alt + F3).

  Wont fixed the issue:

  - busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s 
'Meta.restart("Restarting...")'
  - sudo killall -HUP gnome-shell
  - sudo systemctl restart gdm (kicked me back to login after every login)

  Fixed the issue:
  - sudo systemctl restart systemd-logind

  The last command fixed it after a short time. I tried to jump back
  every time with Ctrl + Alt + F1 and anytime it worked.

  I have no idea if this is a Foxit Reader bug or a issue by GDM/xorg.

  I additionally attached you my latest protocols. In this time the
  freeze occured.

  Best regards,
  Johannes

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.80  Fri May  7 06:55:54 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 29 12:28:07 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.80, 5.4.0-73-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2070 Rev. A] 
[1043:875c]
  InstallationDate: Installed on 2019-11-10 (566 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=454b3874-3032-4cb6-9e5c-92a00ed53afb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.40
  dmi.board.name: Z390 Phantom Gaming 4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  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+git20200226-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/xorg/+bug/1930128/+subscriptions

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

[Desktop-packages] [Bug 1930128] [NEW] Xorg freeze

[Johannes Mages]

Public bug reported:

Hello!

I just started Foxit Reader to config it. While I browse through the
title menues to find the preferences the whole GDM or x.org sessione
freezes. The only way to restart was to some restart commands over the
Off-Shell (Ctrl + Alt + F3).

Wont fixed the issue:

- busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s 
'Meta.restart("Restarting...")'
- sudo killall -HUP gnome-shell
- sudo systemctl restart gdm (kicked me back to login after every login)

Fixed the issue:
- sudo systemctl restart systemd-logind

The last command fixed it after a short time. I tried to jump back every
time with Ctrl + Alt + F1 and anytime it worked.

I have no idea if this is a Foxit Reader bug or a issue by GDM/xorg.

I additionally attached you my latest protocols. In this time the freeze
occured.

Best regards,
Johannes

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.80  Fri May  7 06:55:54 
UTC 2021
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May 29 12:28:07 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 460.80, 5.4.0-73-generic, x86_64: installed
 virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2070 Rev. A] [1043:875c]
InstallationDate: Installed on 2019-11-10 (566 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic 
root=UUID=454b3874-3032-4cb6-9e5c-92a00ed53afb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.40
dmi.board.name: Z390 Phantom Gaming 4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
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+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug false-gpu-hang focal freeze third-party-packages 
ubuntu

** Attachment added: "protocols"
   https://bugs.launchpad.net/bugs/1930128/+attachment/5501018/+files/protocols

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello!

  I just started Foxit Reader to config it. While I browse through the
  title menues to find the preferences the whole GDM or x.org sessione
  freezes. The only way to restart was to some restart commands over th

[Desktop-packages] [Bug 1926032] Re: [i915] Screen "disconnects" when updating screen buffer

[Johannes Konow]

Most certainly not a problem with hdmi connection. I have had windows
installed on the same machine without issues. The behavior is such that
it is very clear that as soon as you move the mouse after a period of
idle, the problem occurs. Also if the computer receives a notification
after a period of idle it occurs.

There is a definite link to activity which renders new information on
the screen buffer. It can play a movie without a problem on vlc but when
I pause, it disconnects the screen (presumably because the "pause" bars
appear on the screen). If I right click to add subtitles or change
something else in the video it also appears at the exact same time I
click. This problem is very repeatable. I can do a phone quality video
if that would be of interest.

If it was a problem with hdmi it would be more random in behavior and it
would be a problem on windows as well.

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

Title:
  [i915] Screen "disconnects" when updating screen buffer

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

Bug description:
  I have a problem in which the screen will behave as if I pulled the
  HDMI or turned the computer off (no source) for a few seconds until
  the screen comes back on again. This happens a lot when I open a new
  window, moves the mouse after it has been still for a while or I open
  a new window or move the current window.

  I can watch a whole movie without this problem but as soon as I pause
  or touch the controls of VLC or move the mouse the problem reocurr. It
  seems to be after a certain idle period most of the time, but not
  always. Sometimes it happens many times in a row.

  The setup is my home built media PC with intel integrated graphics
  (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer
  AV receiver.

  I have tried probably every possible resolution and screen update
  frequency and the problem is still there.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 24 21:57:54 2021
  DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) 
[1849:3e98]
  InstallationDate: Installed on 2020-12-01 (144 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago)
  dmi.bios.date: 05/14/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.10
  dmi.board.name: H310CM-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  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+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1926333] [NEW] Xorg freeze

[Johannes Mages]

Public bug reported:

Xorg / Gnome freeze after enabling Intel Speed Shift in UEFI. Desktop
doesn't respond to key combinations like Ctrl + Alt + F3 to go into the
console. Only SysRq + R and SysRq + E let the system awake again. This
bug occurs when the system want to go into Power Saving Mode.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
Uname: Linux 5.4.0-72-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/gpu0'
.proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/capabilities/mig'
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.73.01  Thu Apr  1 21:40:36 
UTC 2021
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 27 19:58:04 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 460.73.01, 5.4.0-72-generic, x86_64: installed
 virtualbox, 6.1.16, 5.4.0-71-generic, x86_64: installed
 virtualbox, 6.1.16, 5.4.0-72-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
 NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2070 Rev. A] [1043:875c]
InstallationDate: Installed on 2019-11-10 (534 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-generic 
root=UUID=454b3874-3032-4cb6-9e5c-92a00ed53afb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.40
dmi.board.name: Z390 Phantom Gaming 4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
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+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg / Gnome freeze after enabling Intel Speed Shift in UEFI. Desktop
  doesn't respond to key combinations like Ctrl + Alt + F3 to go into
  the console. Only SysRq + R and SysRq + E let the system awake again.
  This bug occurs when the system want to go into Power Saving Mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101
  Uname: Linux 5.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 

[Desktop-packages] [Bug 1926032] [NEW] Screen "disconnects" when updating screen buffer

[Johannes Konow]

Public bug reported:

I have a problem in which the screen will behave as if I pulled the HDMI
or turned the computer off (no source) for a few seconds until the
screen comes back on again. This happens a lot when I open a new window,
moves the mouse after it has been still for a while or I open a new
window or move the current window.

I can watch a whole movie without this problem but as soon as I pause or
touch the controls of VLC or move the mouse the problem reocurr. It
seems to be after a certain idle period most of the time, but not
always. Sometimes it happens many times in a row.

The setup is my home built media PC with intel integrated graphics
(i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer AV
receiver.

I have tried probably every possible resolution and screen update
frequency and the problem is still there.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 24 21:57:54 2021
DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) 
[1849:3e98]
InstallationDate: Installed on 2020-12-01 (144 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago)
dmi.bios.date: 05/14/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.10
dmi.board.name: H310CM-ITX/ac
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
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+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Screen "disconnects" when updating screen buffer

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a problem in which the screen will behave as if I pulled the
  HDMI or turned the computer off (no source) for a few seconds until
  the screen comes back on again. This happens a lot when I open a new
  window, moves the mouse after it has been still for a while or I open
  a new window or move the current window.

  I can watch a whole movie without this problem but as soon as I pause
  or touch the controls of VLC or move the mouse the problem reocurr. It
  seems to be after a certain idle period most of the time, but not
  always. Sometimes it happens many times in a row.

  The setup is my home built media PC with intel integrated graphics
  (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer
  AV receiver.

  I have tried probably every possible resolution and screen update
  frequency and the problem is still there.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: 

[Desktop-packages] [Bug 1915283] [NEW] [ThinkPad X1 Yoga G5, Realtek ALC285] TRS-Microphone recognized as Headphone

[Johannes Fried]

Public bug reported:

Expected

If I plug in a 3-contact TRS microphone, PulseAudio should show it as a plugged 
in microphone. 

Actual
--
Pulse Audio still reports the "Headphones Stereo Microphone" as unplugged. The 
meter shows no signal. The main output changes its Port form "Speaker" to 
"Headphones (plugged in)" and the speakers are muted. 

Additional Information
--

Microphone Model: König CMP-MIC8 (https://www.amazon.de/Konig-CMP-MIC8
-Mikrofon-mit-Kabel-Schwarz/dp/B000WGW96K?language=en_GB). It features a
3-contact, TRS plug. It is the same plug as for a standard stereo
headphone. The microphone worked on another Windows PC and a Zoom H5
pocket recorder. It requires plug-in power.

A 4-contact TRRS headset works as expected (speakers are muted,
headphone output and microphone input are enabled, microphone meter
shows input signal).

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Feb 10 15:52:50 2021
InstallationDate: Installed on 2020-09-12 (151 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed
Symptom_Card: sof-hda-dsp - sof-hda-dsp
Symptom_Jack: Black Mic, Right
Symptom_Type: None of the above
Title: [20UCS03S00, Realtek ALC285, Black Mic, Right] Recording problem
UpgradeStatus: Upgraded to groovy on 2021-02-10 (0 days ago)
dmi.bios.date: 10/15/2020
dmi.bios.release: 1.14
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET24W (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UCS03S00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnLENOVO:bvrN2WET24W(1.14):bd10/15/2020:br1.14:efr1.8:svnLENOVO:pn20UCS03S00:pvrThinkPadX1YogaGen5:rvnLENOVO:rn20UCS03S00:rvrNotDefined:cvnLENOVO:ct31:cvrNone:
dmi.product.family: ThinkPad X1 Yoga Gen 5
dmi.product.name: 20UCS03S00
dmi.product.sku: LENOVO_MT_20UC_BU_Think_FM_ThinkPad X1 Yoga Gen 5
dmi.product.version: ThinkPad X1 Yoga Gen 5
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy kernel-sound

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

Title:
  [ThinkPad X1 Yoga G5, Realtek ALC285] TRS-Microphone recognized as
  Headphone

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Expected
  
  If I plug in a 3-contact TRS microphone, PulseAudio should show it as a 
plugged in microphone. 

  Actual
  --
  Pulse Audio still reports the "Headphones Stereo Microphone" as unplugged. 
The meter shows no signal. The main output changes its Port form "Speaker" to 
"Headphones (plugged in)" and the speakers are muted. 

  Additional Information
  --

  Microphone Model: König CMP-MIC8 (https://www.amazon.de/Konig-CMP-MIC8
  -Mikrofon-mit-Kabel-Schwarz/dp/B000WGW96K?language=en_GB). It features
  a 3-contact, TRS plug. It is the same plug as for a standard stereo
  headphone. The microphone worked on another Windows PC and a Zoom H5
  pocket recorder. It requires plug-in power.

  A 4-contact TRRS headset works as expected (speakers are muted,
  headphone output and microphone input are enabled, microphone meter
  shows input signal).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed Feb 10 15:52:50 2021
  InstallationDate: Installed on 2020-09-12 (151 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Black Mic, Right
  Symptom_Type: None of the above
  Title: [20UCS03S00, Realtek ALC285, Black Mic, Right] Recording problem
  UpgradeStatus: Upgraded to groovy on 2021-02-10 (0 days ago)
  dmi.bios.date: 10/15/2020
  dmi.bios.release: 1.14
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2WET24W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UCS03S00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  

[Desktop-packages] [Bug 1800003] Re: evince crashes in FcConfigParseAndLoad

[Johannes Martin]

I experienced the same problem on an Ubuntu 18.04.5 system.

It was appearantly caused by .config being a symbolic link to a directory on a 
different file system. Once I moved that .config directory to my home 
directory, I was able to start evince. If the symbolic link points to a 
directory on the same file system, evince seems to work fine.
 
Linking .local to a directory on some other file system might cause similar 
problems.

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

Title:
  evince crashes in FcConfigParseAndLoad

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  I have the following situation persistently on my system (Ubuntu
  18.04.1 on Dell Latitude E6500):

  Evince called with any pdf file crashes immediately with a
  segmentation fault. From the crash dump, I see that the crash happens
  in fontconfig's FcConfigParseAndLoad function, i.e. when the system
  fonts.conf is read. I can reproduce the crash with the following
  minimal example:

  
  #include 

  const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
  FcConfig* config;

  int main(){
 FcConfigParseAndLoad(config, filename, FcTrue);
  }
  

  The fonts.conf file used here is also absolutely minimal:

  
  
  
  
  
  

  (Get me right. It first happened with my system fonts.conf, which is
  not empty. In order to find out whether a specific entry lead to the
  crash, I deleted entry after entry, ultimately reaching the file
  above, and always FcConfigParseAndLoad crashes.

  I have no idea how to go on from here.

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

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

[Desktop-packages] [Bug 1829221] Re: second, dead, mouse pointer left on screen after login, x11 session

[Johannes Scheller]

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

Travis solution worked however after the next reboot the problem
reappears. Any idea how to fix it permanently?

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

Title:
  second, dead, mouse pointer left on screen after login, x11 session

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  This seems to have become repeatable, and applies even on the first
  login session immediately after booting the computer. I don't know if
  this is the right package to report against; another possible culprit:
  gdm:

  When I log into the default "Ubuntu" session (ie: on xorg), gdm's
  mouse pointer remains on screen during the screen blank, and after the
  gnome desktop comes up. It stays on the top just like you'd expect of
  the mouse pointer, but it's immobile and unresponsive. It's left at
  the same position on the screen that it was while using gdm, and is
  the same size as it was in gdm (ie: gdm is not scaled, but gnome
  session desktop scaled to 150% - the *working* in-session mouse
  pointer is also 150% larger than gdm's dead one).

  It looks like gdm and gnome are running in the same x11 session?
  Seeing as the mouse pointer stays solid *during* the transition from
  gdm into the gnome desktop. Not even a flicker. It's almost as if
  we're trying to have smooth transitions for these sorts of things,
  which is good of course, but maybe is a bug in that?

  It disappears when I log into a Wayland session, it appears only to
  affect x11 sessions.

  I've taken to just moving the mouse pointer to the far bottom right
  corner of the screen before logging in, so at least it's not very
  intrusive.

  There are a few reports of similar in askubuntu from a few years back,
  but with no helpful or applicable solution. eg:

  
https://askubuntu.com/questions/521241/i-have-two-cursors-on-my-screen-one-of-which-is-always-on-top-and-will-never-mo
  
https://askubuntu.com/questions/598096/14-04-second-mouse-pointer-stuck-in-middle-of-the-screen

  To answer the points made there, the xinput --list output is shown
  below. Executing that command and rebooting makes no difference. In
  the Displays Prefs there is no second "Unknown" display to disable.
  (The machine has precisely one display, and that's all Settings sees.
  It's a desktop, not a laptop, and it only has an AMD Vega integrated
  graphics. It also has only one mouse.)

  rachel@twilight:~$ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ HID 04b4:3003 Mouse id=9[slave  pointer 
 (2)]
  ⎜   ↳ HID 04b4:3003 Consumer Control  id=11   [slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Mouseid=15   [slave  
pointer  (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=16   
[slave  pointer  (2)]
  ⎜   ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=17   
[slave  pointer  (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ HID 04b4:3003   id=8[slave  
keyboard (3)]
  ↳ HID 04b4:3003 System Controlid=10   [slave  
keyboard (3)]
  ↳ HID 04b4:3003 Keyboard  id=12   [slave  
keyboard (3)]
  ↳ Dell Dell AC511 USB SoundBarid=13   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0  id=14   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0 System Control   id=18   
[slave  keyboard (3)]
  ↳ Eee PC WMI hotkeys  id=19   [slave  
keyboard (3)]
  ↳ HID 04b4:3003 Consumer Control  id=20   [slave  
keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=21   
[slave  keyboard (3)]
  ↳ Microsoft Microsoft® Nano Transceiver v1.0 Consumer Control id=22   
[slave  keyboard (3)]

  (I don't know what's with the duplicated MS Nano Transceiver Consumer
  Control entries)

  I thought of a couple of things to try after starting to write this
  ticket but didn't want to lose the ticket in progress, so will add
  comments if they show up anything. In particular, I am running the
  experimental feature to enable xrandr fractional scaling. This issue
  didn't show up right after enabling that, only a couple of days later,
  so it didn't seem 

[Desktop-packages] [Bug 1877580] Re: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all

[Johannes]

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

** This bug is no longer a duplicate of bug 1879989
   "Failed to play sound: No such driver"  ubuntu 20.04
** This bug has been marked a duplicate of bug 1879939
   Audio stopped working after 5.4.0-31 kernel update

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

Title:
  [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After upgrade from 19.10 to 20.04 (xubuntu) I've lost the sound on the 
headphones.
  The internal loud speakers works ok when the headphones are not plugged in.

  More specifically:
  If I open the pavucontrol without the headphones plugged in I see that is 
correctly mentioning the output as Port: "Speakers (plugged-in)" and everything 
works ok, I have sound from the speakers.

  The moment I plug in the headphones, for a fraction of a second I can
  hear sound on the headphones, and then the output port switches to
  "headphones" which is the moment I lose the sound.

  The fraction that I hear the sound is when the jack is half-inserted
  and I get the sound on one channel only. When is fully inserted, the
  computer detects it and makes the switch.

  I've tried also in alsamixer all possibilities I could imagine,
  playing with mute/unmute and gain of each channel, with no success

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May  8 15:41:08 2020
  InstallationDate: Installed on 2019-08-08 (274 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1877580] Re: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound at all

[Johannes]

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

** This bug has been marked a duplicate of bug 1879989
   "Failed to play sound: No such driver"  ubuntu 20.04

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

Title:
  [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After upgrade from 19.10 to 20.04 (xubuntu) I've lost the sound on the 
headphones.
  The internal loud speakers works ok when the headphones are not plugged in.

  More specifically:
  If I open the pavucontrol without the headphones plugged in I see that is 
correctly mentioning the output as Port: "Speakers (plugged-in)" and everything 
works ok, I have sound from the speakers.

  The moment I plug in the headphones, for a fraction of a second I can
  hear sound on the headphones, and then the output port switches to
  "headphones" which is the moment I lose the sound.

  The fraction that I hear the sound is when the jack is half-inserted
  and I get the sound on one channel only. When is fully inserted, the
  computer detects it and makes the switch.

  I've tried also in alsamixer all possibilities I could imagine,
  playing with mute/unmute and gain of each channel, with no success

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri May  8 15:41:08 2020
  InstallationDate: Installed on 2019-08-08 (274 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bnv1312 F pulseaudio
bnv   21367 F alsamixer
   /dev/snd/pcmC0D0c:   bnv1312 F...m pulseaudio
   /dev/snd/pcmC0D0p:   bnv1312 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Latitude 7490, Realtek ALC3246, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.product.sku: 081C
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1879132] [NEW] flatpaks not in search results when snap plugin is installed

[Johannes Rohr]

Public bug reported:

without the snap plugin being installed, a search for e.g. zoom,
telegram or signal returns the respective flatpaks. With the snap plugin
installed, all flatpak results are suddenly hidden, I get *only* snap
results for the same searches. Flatpaks only appear in the "installed"
tab. Whether or not this is no purpose, this is inconvenient. You don't
what to have two different app stores (gnome-software and snap-store)
installed in parallel, when a single one could be doing the job.

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

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

Title:
  flatpaks not in search results when snap plugin is installed

Status in gnome-software package in Ubuntu:
  New

Bug description:
  without the snap plugin being installed, a search for e.g. zoom,
  telegram or signal returns the respective flatpaks. With the snap
  plugin installed, all flatpak results are suddenly hidden, I get
  *only* snap results for the same searches. Flatpaks only appear in the
  "installed" tab. Whether or not this is no purpose, this is
  inconvenient. You don't what to have two different app stores (gnome-
  software and snap-store) installed in parallel, when a single one
  could be doing the job.

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

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

Re: [Desktop-packages] [Bug 1858753] Re: listing of files is temporarily a few minutes corrupted

[Johannes von Schlichtegroll]

** Attachment added: "screencast_20200108_09.47_(++)_error_starting_00.19.mp4"
   
https://bugs.launchpad.net/bugs/1858753/+attachment/5318491/+files/screencast_20200108_09.47_%28++%29_error_starting_00.19.mp4

** Attachment added: "screenshot_process_whoopsie_2020-01-08 09-54-55.png"
   
https://bugs.launchpad.net/bugs/1858753/+attachment/5318492/+files/screenshot_process_whoopsie_2020-01-08%2009-54-55.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/1858753

Title:
  listing of files is temporarily a few minutes corrupted

Status in compiz package in Ubuntu:
  Incomplete
Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  listing of files is temporarily a few minutes corrupted

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.21
  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: Wed Jan  8 07:32:12 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3909]
  InstallationDate: Installed on 2019-02-11 (330 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 13d3:3494 IMC Networks 
   Bus 002 Device 002: ID 174f:1169 Syntek 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80QR
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=a2de3362-190e-4c23-ac87-af227c4b0888 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/25/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CCCN20WW(V2.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo B50-10
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo B50-10
  dmi.modalias: 
dmi:bvnLENOVO:bvrCCCN20WW(V2.06):bd08/25/2016:svnLENOVO:pn80QR:pvrLenovoB50-10:rvnLENOVO:rnLenovoB50-10:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoB50-10:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80QR
  dmi.product.version: Lenovo B50-10
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-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 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Jan  8 06:00:20 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
  xserver.video_driver: modeset

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

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

[Desktop-packages] [Bug 1858753] [NEW] listing of files is temporarily a few minutes corrupted

[Johannes von Schlichtegroll]

Public bug reported:

listing of files is temporarily a few minutes corrupted

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.21
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: Wed Jan  8 07:32:12 2020
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3909]
InstallationDate: Installed on 2019-02-11 (330 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 003: ID 13d3:3494 IMC Networks 
 Bus 002 Device 002: ID 174f:1169 Syntek 
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80QR
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic 
root=UUID=a2de3362-190e-4c23-ac87-af227c4b0888 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/25/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: CCCN20WW(V2.06)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo B50-10
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo B50-10
dmi.modalias: 
dmi:bvnLENOVO:bvrCCCN20WW(V2.06):bd08/25/2016:svnLENOVO:pn80QR:pvrLenovoB50-10:rvnLENOVO:rnLenovoB50-10:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoB50-10:
dmi.product.family: IDEAPAD
dmi.product.name: 80QR
dmi.product.version: Lenovo B50-10
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-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 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Jan  8 06:00:20 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial

** Attachment added: "screencast_20191214_21.03_(++).mp4"
   
https://bugs.launchpad.net/bugs/1858753/+attachment/5318460/+files/screencast_20191214_21.03_%28++%29.mp4

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

Title:
  listing of files is temporarily a few minutes corrupted

Status in xorg package in Ubuntu:
  New

Bug description:
  listing of files is temporarily a few minutes corrupted

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.21
  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: Wed Jan  8 07:32:12 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[17aa:3909]
  InstallationDate: Installed on 2019-02-11 (330 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 

[Desktop-packages] [Bug 1851807] Re: xdg-desktop-portal-gtk spams logs

[Johannes Winter]

Same behaviour in current debian sid.

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

Title:
  xdg-desktop-portal-gtk spams logs

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk source package in Eoan:
  Confirmed

Bug description:
  Every minute I get a log entry that looks like

  > xdg-desktop-por[ ]: Failed to get application states:
  GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window
  list: GDBus.Error: org.freedesktop.DBus.Error.AccessDenied: App
  introspection not allowed

  Upstream bug-report: https://github.com/flatpak/xdg-desktop-portal-
  gtk/issues/222

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xdg-desktop-portal-gtk 1.4.0-2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 10:51:30 2019
  InstallationDate: Installed on 2019-11-07 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: xdg-desktop-portal-gtk
  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-gtk/+bug/1851807/+subscriptions

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

Re: [Desktop-packages] [Bug 1825621] Re: Textbearbeitung -gedit- läßt sich nicht sauber aufrufen. Keine weiße Fläche, Eingaben sind nicht möglich

[Bors Johannes]

Sehr geehrte Damen und Herren,
mein Problem ist gelöst. Ich habe Ubuntu 18.04 neu auf mein
Laptop installiert und die "Textbearbeitung" funktioniert jetzt
reibungslos.
Ich bitte zu entschuldigen, dass ich mich nicht mehr gemeldet habe.

Wo der Fehler gelegen hat ist jetzt natürlich nicht mehr zu klären. 
Mit freundlichem Gruß
Johannes Bors



> Launchpad Bug Tracker <1825...@bugs.launchpad.net> hat am 23. Juni 2019 um 
> 06:18 geschrieben:
> 
> 
> [Expired for gedit (Ubuntu) because there has been no activity for 60
> days.]
> 
> ** Changed in: gedit (Ubuntu)
>Status: Incomplete => Expired
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1825621
> 
> Title:
>   Textbearbeitung -gedit- läßt sich nicht sauber aufrufen. Keine weiße
>   Fläche, Eingaben sind nicht möglich
> 
> Status in gedit package in Ubuntu:
>   Expired
> 
> Bug description:
>   /home/nomennescio/Schreibtisch/gedit nach Aufruf.png
>   Dies erschein nach Aufruf; damit zu arbeiten ist nicht möglich
>   Vielen Dank für Ihre Hilfe.
>   Johannes Bors
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: gedit 3.28.1-1ubuntu1.1
>   ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
>   Uname: Linux 4.15.0-47-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Apr 20 10:23:33 2019
>   InstallationDate: Installed on 2019-04-07 (12 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
> (20180426)
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=de_DE.UTF-8
>SHELL=/bin/bash
>   SourcePackage: gedit
>   UpgradeStatus: No upgrade log present (probably fresh install)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825621/+subscriptions

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

Title:
  Textbearbeitung -gedit- läßt sich nicht sauber aufrufen. Keine weiße
  Fläche, Eingaben sind nicht möglich

Status in gedit package in Ubuntu:
  Expired

Bug description:
  /home/nomennescio/Schreibtisch/gedit nach Aufruf.png
  Dies erschein nach Aufruf; damit zu arbeiten ist nicht möglich
  Vielen Dank für Ihre Hilfe.
  Johannes Bors

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 10:23:33 2019
  InstallationDate: Installed on 2019-04-07 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1825544] Re: Switch User menu item gone after upgrade to Ubuntu 19.04

[Johannes Rohr]

I upgraded both machines from Cosmic to Disco. In both instances, the
menu item was there before and was gone after the upgrade.

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

Title:
  Switch User menu item gone after upgrade to Ubuntu 19.04

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After today's upgrade to Ubuntu 19.04 with GNOME Shell 3.32, the
  switch user menu is gone, even though org.gnome.desktop.lockdown
  disable-user-switching is  false

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

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

[Desktop-packages] [Bug 1825544] Re: Switch User menu item gone after upgrade to Ubuntu 19.04

[Johannes Rohr]

For completeness' sake: Just upgraded another machine and I see the same
here.

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

Title:
  Switch User menu item gone after upgrade to Ubuntu 19.04

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After today's upgrade to Ubuntu 19.04 with GNOME Shell 3.32, the
  switch user menu is gone, even though org.gnome.desktop.lockdown
  disable-user-switching is  false

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

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

[Desktop-packages] [Bug 1825621] [NEW] Textbearbeitung -gedit- läßt sich nicht sauber aufrufen. Keine weiße Fläche, Eingaben sind nicht möglich

[Bors Johannes]

Public bug reported:

/home/nomennescio/Schreibtisch/gedit nach Aufruf.png
Dies erschein nach Aufruf; damit zu arbeiten ist nicht möglich
Vielen Dank für Ihre Hilfe.
Johannes Bors

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gedit 3.28.1-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 20 10:23:33 2019
InstallationDate: Installed on 2019-04-07 (12 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  Textbearbeitung -gedit- läßt sich nicht sauber aufrufen. Keine weiße
  Fläche, Eingaben sind nicht möglich

Status in gedit package in Ubuntu:
  New

Bug description:
  /home/nomennescio/Schreibtisch/gedit nach Aufruf.png
  Dies erschein nach Aufruf; damit zu arbeiten ist nicht möglich
  Vielen Dank für Ihre Hilfe.
  Johannes Bors

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gedit 3.28.1-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 10:23:33 2019
  InstallationDate: Installed on 2019-04-07 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1825544] Re: Switch User menu item gone after upgrade to Ubuntu 19.04

[Johannes Rohr]

I can still switch to the first virtual console with Ctrl-Alt-F1 and
open a new session, also switch between the sessions with ctrl-alt-fX

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

Title:
  Switch User menu item gone after upgrade to Ubuntu 19.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After today's upgrade to Ubuntu 19.04 with GNOME Shell 3.32, the
  switch user menu is gone, even though org.gnome.desktop.lockdown
  disable-user-switching is  false

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

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

[Desktop-packages] [Bug 1825544] [NEW] Switch User menu item gone after upgrade to Ubuntu 19.04

[Johannes Rohr]

Public bug reported:

After today's upgrade to Ubuntu 19.04 with GNOME Shell 3.32, the switch
user menu is gone, even though org.gnome.desktop.lockdown disable-user-
switching is  false

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

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

Title:
  Switch User menu item gone after upgrade to Ubuntu 19.04

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After today's upgrade to Ubuntu 19.04 with GNOME Shell 3.32, the
  switch user menu is gone, even though org.gnome.desktop.lockdown
  disable-user-switching is  false

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

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

[Desktop-packages] [Bug 1822276] [NEW] Folder where a document was saved last is not saved

[Johannes]

Public bug reported:

This is probably a "duplicate" of a bug, which was fixed in evince 2.27, but 
now in evince 3.30 it seems to reappear again. Additionally, I am not sure if 
this is an evince bug or a gtk3 bug.
The main problem is that the folder where a document was saved last is never 
stored. So for me a common workflow is downloading a pdf of a scientific 
publication and I need to store it somewhere in my filesystem. In many other 
instances (sumatrapdf on windows) the folder where I saved the last pdf is 
always stored. This means after I saved the first document for all subsequent 
documents I don't need to navigate the file system again.
At the moment evince always starts in the home folder and I need to navigate 
through my filesystem again.
This is on fedora 29 with evince 3.30.2 and gtk3 3.24.1.

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

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

Title:
  Folder where a document was saved last is not saved

Status in evince package in Ubuntu:
  New

Bug description:
  This is probably a "duplicate" of a bug, which was fixed in evince 2.27, but 
now in evince 3.30 it seems to reappear again. Additionally, I am not sure if 
this is an evince bug or a gtk3 bug.
  The main problem is that the folder where a document was saved last is never 
stored. So for me a common workflow is downloading a pdf of a scientific 
publication and I need to store it somewhere in my filesystem. In many other 
instances (sumatrapdf on windows) the folder where I saved the last pdf is 
always stored. This means after I saved the first document for all subsequent 
documents I don't need to navigate the file system again.
  At the moment evince always starts in the home folder and I need to navigate 
through my filesystem again.
  This is on fedora 29 with evince 3.30.2 and gtk3 3.24.1.

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

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

[Desktop-packages] [Bug 1818666] [NEW] no network(with cable)

[Johannes Merten]

Public bug reported:

Description:Trisquel GNU/Linux 8.0, Flidas
Release:8.0
---
network-manager:
  Installiert:   1.2.6-0ubuntu0.16.04.3
  Installationskandidat: 1.2.6-0ubuntu0.16.04.3
  Versionstabelle:
 *** 1.2.6-0ubuntu0.16.04.3 500
500 https://archive.trisquel.info/trisquel flidas-security/main amd64 
Packages
500 https://archive.trisquel.info/trisquel flidas-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 https://archive.trisquel.info/trisquel flidas/main amd64 Packages
---


after starting the system there is no eth(0?) network available, after 
gdm-login it take some time, starting the network-managager leads to a freeze 
of the network-manager while rebooting the system it take a lot more time and 
there are also some error messages. i think they are included in the "Extra 
debug information". sorry i'm not sure, this is my first bug-report. 


a have this problem since i use trisquel, this problem doesnt exist with 
ubuntu, i think
sometimes everything works fine. :)

if this bug-report is not written correct, please contact me if
possible. thanks

ProblemType: Bug
DistroRelease: Trisquel 8.0
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-142.168+8.0trisquel2-generic 4.4.167-gnu
Uname: Linux 4.4.0-142-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Mar  5 14:38:31 2019
InstallationDate: Installed on 2018-12-27 (68 days ago)
InstallationMedia: Trisquel 8.0 "flidas" - Release amd64 (20180417)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug flidas

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

Title:
  no network(with cable)

Status in xorg package in Ubuntu:
  New

Bug description:
  Description:  Trisquel GNU/Linux 8.0, Flidas
  Release:  8.0
  ---
  network-manager:
Installiert:   1.2.6-0ubuntu0.16.04.3
Installationskandidat: 1.2.6-0ubuntu0.16.04.3
Versionstabelle:
   *** 1.2.6-0ubuntu0.16.04.3 500
  500 https://archive.trisquel.info/trisquel flidas-security/main amd64 
Packages
  500 https://archive.trisquel.info/trisquel flidas-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.93-0ubuntu4 500
  500 https://archive.trisquel.info/trisquel flidas/main amd64 Packages
  ---

  
  after starting the system there is no eth(0?) network available, after 
gdm-login it take some time, starting the network-managager leads to a freeze 
of the network-manager while rebooting the system it take a lot more time and 
there are also some error messages. i think they are included in the "Extra 
debug information". sorry i'm not sure, this is my first bug-report. 

  
  a have this problem since i use trisquel, this problem doesnt exist with 
ubuntu, i think
  sometimes everything works fine. :)

  if this bug-report is not written correct, please contact me if
  possible. thanks

  ProblemType: Bug
  DistroRelease: Trisquel 8.0
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168+8.0trisquel2-generic 4.4.167-gnu
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar  5 14:38:31 2019
  InstallationDate: Installed on 2018-12-27 (68 days ago)
  InstallationMedia: Trisquel 8.0 "flidas" - Release amd64 (20180417)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1760866] Re: evince crashed with SIGSEGV

[Johannes Kalliauer]

** Information type changed from Private to Public

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

Title:
  evince crashed with SIGSEGV

Status in evince package in Ubuntu:
  New

Bug description:
  Occured after updating Ubuntu 16.04 to Ubuntu 18.04

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: evince 3.28.0-1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 15:48:35 2018
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2017-04-07 (360 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  KernLog:
   
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=ca55c159-bb62-4dd8-b07c-62b6ef55e404 ro quiet splash vt.handoff=1
  SegvAnalysis:
   Segfault happened at: 0x5650d6d0e82d:mov0x38(%r13),%rax
   PC (0x5650d6d0e82d) ok
   source "0x38(%r13)" (0x0038) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   ()
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   start_thread (arg=0x7f24b5b97700) at pthread_create.c:463
  Title: evince crashed with SIGSEGV
  UpgradeStatus: Upgraded to bionic on 2018-03-29 (4 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1768753] Re: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()

[Johannes Martin]

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

Since the bug this is a duplicate of is marked private, there is no way
for us to "look at the other bug report to see if there is any missing
information that you can provide, or to see if there is a workaround for
the bug".

I found a hint for a workaround here:
https://askubuntu.com/questions/927859/libreoffice-writer-crashes-on-start

That works for me, too.

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

Title:
  soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()

Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  libreoffice is crashed

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic i686
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 09:25:08 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2016-10-18 (561 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803)
  ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc --splash-pipe=5
  SegvAnalysis:
   Segfault happened at: 0xa2b81c15:movb   $0x0,(%eax)
   PC (0xa2b81c15) ok
   source "$0x0" ok
   destination "(%eax)" (0xbf14dfe0) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: libreoffice
  StacktraceTop:
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   ?? () from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
   JNI_CreateJavaVM () from 
/usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
  Title: soffice.bin crashed with SIGSEGV in JNI_CreateJavaVM()
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

Re: [Desktop-packages] [Bug 1785107] Re: Ghostscript and pstoedit versions not compatible in 18.04 Bionic Beaver

[Johannes Schmitz]

One of our students has tested this and it seems to work fine now.

Am Di., 2. Okt. 2018 um 15:51 Uhr schrieb Marc Deslauriers <
marc.deslauri...@canonical.com>:

> Hello, thanks for reporting this issue.
> Ghostscript has been updated to 9.25 in current releases of Ubuntu.
>
> Could you please verify that your issue has been resolved, and update
> this bug accordingly?
>
> Thanks!
>
>
> ** Changed in: ghostscript (Ubuntu)
>Status: Confirmed => Incomplete
>
> ** Changed in: pstoedit (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1785107
>
> Title:
>   Ghostscript and pstoedit versions not compatible in 18.04 Bionic
>   Beaver
>
> Status in pstoedit:
>   Won't Fix
> Status in ghostscript package in Ubuntu:
>   Incomplete
> Status in pstoedit package in Ubuntu:
>   Incomplete
>
> Bug description:
>   The Ghostscript version 9.22 included in Ubuntu 18.04 has an issue with
> pstoedit.
>   There is a known issue with the DELAYBIND command in that particular
> ghostscript version which causes the problems:
>
>   https://bugs.ghostscript.com/show_bug.cgi?id=698652
>
>   Therefore an update of ghostscript and or pstoedit is urgently
>   necessary.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/pstoedit/+bug/1785107/+subscriptions
>

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

Title:
  Ghostscript and pstoedit versions not compatible in 18.04 Bionic
  Beaver

Status in pstoedit:
  Won't Fix
Status in ghostscript package in Ubuntu:
  Incomplete
Status in pstoedit package in Ubuntu:
  Incomplete

Bug description:
  The Ghostscript version 9.22 included in Ubuntu 18.04 has an issue with 
pstoedit.
  There is a known issue with the DELAYBIND command in that particular 
ghostscript version which causes the problems:

  https://bugs.ghostscript.com/show_bug.cgi?id=698652

  Therefore an update of ghostscript and or pstoedit is urgently
  necessary.

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

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

[Desktop-packages] [Bug 1793558] [NEW] package python3-brlapi 5.5-4ubuntu2.0.1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

[Johannes]

Public bug reported:

update error

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3-brlapi 5.5-4ubuntu2.0.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 firefox:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Sep 20 18:07:40 2018
ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
InstallationDate: Installed on 2018-04-29 (144 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: brltty
Title: package python3-brlapi 5.5-4ubuntu2.0.1 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package python3-brlapi 5.5-4ubuntu2.0.1 failed to install/upgrade:
  Abhängigkeitsprobleme - verbleibt unkonfiguriert

Status in brltty package in Ubuntu:
  New

Bug description:
  update error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-brlapi 5.5-4ubuntu2.0.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   firefox:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Sep 20 18:07:40 2018
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  InstallationDate: Installed on 2018-04-29 (144 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: brltty
  Title: package python3-brlapi 5.5-4ubuntu2.0.1 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

[Johannes Niediek]

Thanks Iain, everything you wrote makes sense to me (including that I
should have used the Debian bug tracker). Everything works fine after
apt-get install --reinstall libappstream4.

Best,
Johannes

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

Title:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

Status in AppStream:
  Fix Released
Status in appstream package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Fix Released

Bug description:
  When running

    sudo apt update

  in a terminal I sometimes see the following message printed within the
  output.

    (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

  This started happening today (5th August). Otherwise apt update and
  apt upgrade seem to correctly update the system.

  --

  https://gitlab.gnome.org/GNOME/glib/issues/1480

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libglib2.0-0 2.57.2-1
  ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
  Uname: Linux 4.17.0-6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  5 17:52:41 2018
  InstallationDate: Installed on 2018-07-12 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

[Johannes Niediek]

I still see the problem on Debian, could you elaborate which package
contains the fix?

Info:

> dpkg-query -s appstream

Package: appstream
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 656
Maintainer: Matthias Klumpp 
Architecture: amd64
Version: 0.12.2-2

> appstreamcli refresh-cache

(appstreamcli:3963): GLib-CRITICAL **: 09:07:57.805:
g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types ||
GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite
(GVSB(builder)->type)' failed

and so on.

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

Title:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

Status in AppStream:
  Fix Released
Status in appstream package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Fix Released

Bug description:
  When running

    sudo apt update

  in a terminal I sometimes see the following message printed within the
  output.

    (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047:
  g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed

  This started happening today (5th August). Otherwise apt update and
  apt upgrade seem to correctly update the system.

  --

  https://gitlab.gnome.org/GNOME/glib/issues/1480

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: libglib2.0-0 2.57.2-1
  ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
  Uname: Linux 4.17.0-6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Aug  5 17:52:41 2018
  InstallationDate: Installed on 2018-07-12 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Johannes Michael]

A simple restart fixed this for me on 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/1508146

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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

[Desktop-packages] [Bug 1785107] Re: Ghostscript and pstoedit versions not compatible in 18.04 Bionic Beaver

[Johannes Schmitz]

Then at least pstoedit should be updated to a version that supports
REALLYDELAYBIND such as 3.71.

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

Title:
  Ghostscript and pstoedit versions not compatible in 18.04 Bionic
  Beaver

Status in pstoedit:
  Won't Fix
Status in ghostscript package in Ubuntu:
  New
Status in pstoedit package in Ubuntu:
  New

Bug description:
  The Ghostscript version 9.22 included in Ubuntu 18.04 has an issue with 
pstoedit.
  There is a known issue with the DELAYBIND command in that particular 
ghostscript version which causes the problems:

  https://bugs.ghostscript.com/show_bug.cgi?id=698652

  Therefore an update of ghostscript and or pstoedit is urgently
  necessary.

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

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

[Desktop-packages] [Bug 1786196] [NEW] purple-matrix broken, needs update

[Johannes Schmitz]

Public bug reported:

The purple-matrix version included in ubuntu is broken as it does not
allow to connect to matrix.org with the new cloudflare setup.

https://github.com/matrix-org/purple-matrix/issues/72

Therefore, an update is needed or the package remains dysfunctional.

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


** Tags: matrix pidgin purple purple-matrix

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

Title:
  purple-matrix broken, needs update

Status in ghostscript package in Ubuntu:
  New

Bug description:
  The purple-matrix version included in ubuntu is broken as it does not
  allow to connect to matrix.org with the new cloudflare setup.

  https://github.com/matrix-org/purple-matrix/issues/72

  Therefore, an update is needed or the package remains dysfunctional.

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

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

Re: [Desktop-packages] [Bug 1228870] Re: package thunderbird 17.0.8+build1-0ubuntu0.13.04.1 failed to install/upgrade: Größe des symbolischen Links »/usr/lib/thunderbird/distribution/extensions« wurde

[Johannes Bauer]

Hi gf,

actually I don't even remember this issue. I've never had a problem 
since then.

Thank you very much!

Hannes


Am 08.07.2018 um 20:17 schrieb gf:
> Hello Johannes,
> Thank you for submitting this bug and reporting a problem with Thunderbird.  
> You made this bug report in 2013 and there have been several versions of 
> Ubuntu and Thunderbird since then.
>
> Could you confirm that this is no longer a problem and that we can close the 
> ticket?
> If it is still a problem, are you still interested in finding a solution to 
> this bug?
> If you are, could you run the following (only once):
> apport-collect 1228870
> and upload the updated logs and and any other logs that are relevant for this 
> particular issue.
>
> Thank you again for helping make Ubuntu and Thunderbird better.
> G
>
> ** Changed in: thunderbird (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  package thunderbird 17.0.8+build1-0ubuntu0.13.04.1 failed to
  install/upgrade: Größe des symbolischen Links
  »/usr/lib/thunderbird/distribution/extensions« wurde von 104 zu 48
  geändert

Status in thunderbird package in Ubuntu:
  Incomplete

Bug description:
  Unmet dependencies. Output of "apt-get install -f":

  Paketlisten werden gelesen... Fertig
  Abhängigkeitsbaum wird aufgebaut.   
  Statusinformationen werden eingelesen Fertig
  Abhängigkeiten werden korrigiert ... Fertig
  Das folgende Paket wurde automatisch installiert und wird nicht mehr benötigt:
webaccounts-extension-common
  Verwenden Sie »apt-get autoremove«, um es zu entfernen.
  Die folgenden zusätzlichen Pakete werden installiert:
thunderbird
  Vorgeschlagene Pakete:
ttf-lyx
  Die folgenden Pakete werden aktualisiert (Upgrade):
thunderbird
  1 aktualisiert, 0 neu installiert, 0 zu entfernen und 10 nicht aktualisiert.
  2 nicht vollständig installiert oder entfernt.
  Es müssen noch 0 B von 29,2 MB an Archiven heruntergeladen werden.
  Nach dieser Operation werden 14,2 MB Plattenplatz zusätzlich benutzt.
  Möchten Sie fortfahren [J/n]? 
  (Lese Datenbank ... 246108 Dateien und Verzeichnisse sind derzeit 
installiert.)
  Vorbereitung zum Ersetzen von thunderbird 17.0.8+build1-0ubuntu0.13.04.1 
(durch .../thunderbird_1%3a24.0+build1-0ubuntu0.13.04.1_amd64.deb) ...
  Ersatz für thunderbird wird entpackt ...
  dpkg: Fehler beim Bearbeiten von 
/var/cache/apt/archives/thunderbird_1%3a24.0+build1-0ubuntu0.13.04.1_amd64.deb 
(--unpack):
   Größe des symbolischen Links »/usr/lib/thunderbird/distribution/extensions« 
wurde von 104 zu 48 geändert
  Es wurde kein Apport-Bericht verfasst, da das Limit MaxReports bereits 
erreicht ist.
  Trigger für bamfdaemon werden verarbeitet ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Trigger für desktop-file-utils werden verarbeitet ...
  Trigger für gnome-menus werden verarbeitet ...
  Trigger für man-db werden verarbeitet ...
  Fehler traten auf beim Bearbeiten von:
   
/var/cache/apt/archives/thunderbird_1%3a24.0+build1-0ubuntu0.13.04.1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: thunderbird 17.0.8+build1-0ubuntu0.13.04.1
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu8.3
  AptOrdering:
   thunderbird: Install
   thunderbird: Configure
   thunderbird-gnome-support: Configure
   thunderbird-locale-de: Configure
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hannes 2156 F pulseaudio
   /dev/snd/controlC0:  hannes 2156 F pulseaudio
  BuildID: 20130803220711
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Channel: release
  Date: Sat Sep 21 17:02:25 2013
  DpkgTerminalLog:
   Vorbereitung zum Ersetzen von thunderbird 17.0.8+build1-0ubuntu0.13.04.1 
(durch .../thunderbird_1%3a24.0+build1-0ubuntu0.13.04.1_amd64.deb) ...
   Ersatz für thunderbird wird entpackt ...
   dpkg: Fehler beim Bearbeiten von 
/var/cache/apt/archives/thunderbird_1%3a24.0+build1-0ubuntu0.13.04.1_amd64.deb 
(--unpack):
Größe des symbolischen Links »/usr/lib/thunderbird/distribution/extensions« 
wurde von 104 zu 48 geändert
  DuplicateSignature: package:thunderbird:17.0.8+build1-0ubuntu0.13.04.1:Größe 
des symbolischen Links »/usr/lib/thunderbird/distribution/extensions« wurde von 
104 zu 48 geändert
  ErrorMessage: Größe des symbolischen Links 
»/usr/lib/thunderbird/distribution/extensions« wurde von 104 zu 48 geändert
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  Installatio

[Desktop-packages] [Bug 1760905] Re: nautilus does not start at all

[Johannes Kalliauer]

@seb128 @SebastienBacher Thanks Deleting that file helped. :-)

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

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

Title:
  nautilus does not start at all

Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  Since Ubuntu 16.04 is updated to Ubuntu 18.04, Nautilus does not
  start.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Tue Apr  3 17:13:56 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-04-07 (360 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: nautilus
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_enum () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-03-29 (5 days ago)
  UserGroups:
   
  usr_lib_nautilus:
   dropbox  2015.10.28
   nautilus-actions 3.2.3-1build3

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

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

[Desktop-packages] [Bug 1764127] Re: frequent crashes during boot on Ryzen 3 2200G

[Johannes von Löwis]

** Package changed: gnome-control-center (Ubuntu) => linux-signed-hwe-
edge (Ubuntu)

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

Title:
  frequent crashes during boot on Ryzen 3 2200G

Status in linux-signed-hwe-edge package in Ubuntu:
  New

Bug description:
  Most of the time when booting Ubuntu 18.04 (beta) on my recently bought Ryzen 
3 2200 G (Micro-Star International Co., Ltd. MS-7A34/B350 PC MATE (MS-7A34), 
BIOS A.C0 03/08/2018) computer it crashes. 
  Sometimes it boots OK and I do not encounter (major) problems (see below).

  Booting in recovery mode works fine (always, as far as I can tell) but
  then I get only 1024x768 graphics.

  When it hangs during boot, I sometimes see a message: 
  fb: switching to amdgpudrmfb from EFI VGA.

  When boots OK and seems to work OK I frequently see messages in the dmesg 
output:
  [ 1480.928786] pcieport :00:01.2: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=000a(Transmitter ID)
  [ 1480.928793] pcieport :00:01.2:   device [1022:15d3] error 
status/mask=1000/6000
  [ 1480.928797] pcieport :00:01.2:[12] Replay Timer Timeout  
  [ 1495.262748] pcieport :00:01.2: AER: Corrected error received: id=0008
  [ 1495.262757] pcieport :00:01.2: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=000a(Transmitter ID)
  [ 1495.262764] pcieport :00:01.2:   device [1022:15d3] error 
status/mask=1000/6000
  [ 1495.262768] pcieport :00:01.2:[12] Replay Timer Timeout  

  
  Also messages like
  [1.240481] WARNING: CPU: 3 PID: 168 at 
/build/linux-18ur8S/linux-4.15.0/drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_resource.c:1322
 construct+0x96e/0x9b0 [amdgpu]
  [1.240485] Modules linked in: amdkfd amd_iommu_v2 amdgpu(+) chash 
i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
i2c_piix4 drm r8169 mii ahci libahci wmi video
  [1.240499] CPU: 3 PID: 168 Comm: systemd-udevd Not tainted 
4.15.0-15-generic #16-Ubuntu
  [1.240502] Hardware name: Micro-Star International Co., Ltd. MS-7A34/B350 
PC MATE (MS-7A34), BIOS A.C0 03/08/2018
  [1.240549] RIP: 0010:construct+0x96e/0x9b0 [amdgpu]
  [1.240551] RSP: 0018:9f2441f73790 EFLAGS: 00010202
  [1.240554] RAX: 0004 RBX: 8f19bc81a400 RCX: 
8f19bc0d12c0
  [1.240556] RDX: 8f19bc0d12c0 RSI: c0562108 RDI: 
8f19bc0d1348
  [1.240558] RBP: 9f2441f737f0 R08: 8f19ca2e70a0 R09: 
8f19bb80e900
  [1.240560] R10:  R11:  R12: 
8f19bc9beb80
  [1.240562] R13: 8f19bb828000 R14:  R15: 
8f19bb828000
  [1.240565] FS:  7fcb1b4ce680() GS:8f19ca2c() 
knlGS:
  [1.240567] CS:  0010 DS:  ES:  CR0: 80050033
  [1.240569] CR2: 5586ffbcde18 CR3: 000405172000 CR4: 
003406e0
  [1.240572] Call Trace:
  [1.240616]  ? dal_aux_engine_dce110_create+0x2a/0x80 [amdgpu]
  [1.240621]  ? _cond_resched+0x19/0x40
  [1.240625]  ? kmem_cache_alloc_trace+0x198/0x1b0
  [1.240667]  ? dcn10_create_resource_pool+0x2a/0x60 [amdgpu]
  [1.240709]  dcn10_create_resource_pool+0x41/0x60 [amdgpu]
  [1.240751]  dc_create_resource_pool+0x46/0x180 [amdgpu]
  [1.240754]  ? _cond_resched+0x19/0x40
  [1.240756]  ? __kmalloc+0x1e7/0x220
  [1.240798]  ? dal_gpio_service_create+0xa1/0x120 [amdgpu]
  [1.240839]  dc_create+0x244/0x6c0 [amdgpu]
  [1.240882]  dm_hw_init+0xf2/0x2a0 [amdgpu]
  [1.240914]  amdgpu_device_init+0xd23/0x1620 [amdgpu]
  [1.240946]  amdgpu_driver_load_kms+0x8b/0x2e0 [amdgpu]
  [1.240957]  drm_dev_register+0x149/0x1d0 [drm]
  [1.240988]  amdgpu_pci_probe+0x113/0x150 [amdgpu]
  [1.240992]  local_pci_probe+0x47/0xa0
  [1.240995]  pci_device_probe+0x145/0x1b0
  [1.240999]  driver_probe_device+0x31e/0x490
  [1.241001]  __driver_attach+0xa7/0xf0
  [1.241004]  ? driver_probe_device+0x490/0x490
  [1.241006]  bus_for_each_dev+0x70/0xc0
  [1.241008]  driver_attach+0x1e/0x20
  [1.241011]  bus_add_driver+0x1c7/0x270
  [1.241013]  ? 0xc0611000
  [1.241015]  driver_register+0x60/0xe0
  [1.241017]  ? 0xc0611000
  [1.241020]  __pci_register_driver+0x5a/0x60
  [1.241054]  amdgpu_init+0x96/0xa9 [amdgpu]
  [1.241058]  do_one_initcall+0x52/0x19f
  [1.241061]  ? __vunmap+0x81/0xb0
  [1.241063]  ? _cond_resched+0x19/0x40
  [1.241065]  ? kmem_cache_alloc_trace+0xa6/0x1b0
  [1.241069]  ? do_init_module+0x27/0x209
  [1.241071]  do_init_module+0x5f/0x209
  [1.241074]  load_module+0x191e/0x1f10
  [1.241077]  ? ima_post_read_file+0x96/0xa0
  [1.241080]  SYSC_finit_module+0xfc/0x120
  [1.241083]  ? SYSC_finit_module+0xfc/0x120
  ...
  are found every now and 

[Desktop-packages] [Bug 1764127] [NEW] frequent crashes during boot on Ryzen 3 2200G

[Johannes von Löwis]

Public bug reported:

Most of the time when booting Ubuntu 18.04 (beta) on my recently bought Ryzen 3 
2200 G (Micro-Star International Co., Ltd. MS-7A34/B350 PC MATE (MS-7A34), BIOS 
A.C0 03/08/2018) computer it crashes. 
Sometimes it boots OK and I do not encounter (major) problems (see below).

Booting in recovery mode works fine (always, as far as I can tell) but
then I get only 1024x768 graphics.

When it hangs during boot, I sometimes see a message: 
fb: switching to amdgpudrmfb from EFI VGA.

When boots OK and seems to work OK I frequently see messages in the dmesg 
output:
[ 1480.928786] pcieport :00:01.2: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=000a(Transmitter ID)
[ 1480.928793] pcieport :00:01.2:   device [1022:15d3] error 
status/mask=1000/6000
[ 1480.928797] pcieport :00:01.2:[12] Replay Timer Timeout  
[ 1495.262748] pcieport :00:01.2: AER: Corrected error received: id=0008
[ 1495.262757] pcieport :00:01.2: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=000a(Transmitter ID)
[ 1495.262764] pcieport :00:01.2:   device [1022:15d3] error 
status/mask=1000/6000
[ 1495.262768] pcieport :00:01.2:[12] Replay Timer Timeout  


Also messages like
[1.240481] WARNING: CPU: 3 PID: 168 at 
/build/linux-18ur8S/linux-4.15.0/drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dcn10_resource.c:1322
 construct+0x96e/0x9b0 [amdgpu]
[1.240485] Modules linked in: amdkfd amd_iommu_v2 amdgpu(+) chash 
i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
i2c_piix4 drm r8169 mii ahci libahci wmi video
[1.240499] CPU: 3 PID: 168 Comm: systemd-udevd Not tainted 
4.15.0-15-generic #16-Ubuntu
[1.240502] Hardware name: Micro-Star International Co., Ltd. MS-7A34/B350 
PC MATE (MS-7A34), BIOS A.C0 03/08/2018
[1.240549] RIP: 0010:construct+0x96e/0x9b0 [amdgpu]
[1.240551] RSP: 0018:9f2441f73790 EFLAGS: 00010202
[1.240554] RAX: 0004 RBX: 8f19bc81a400 RCX: 8f19bc0d12c0
[1.240556] RDX: 8f19bc0d12c0 RSI: c0562108 RDI: 8f19bc0d1348
[1.240558] RBP: 9f2441f737f0 R08: 8f19ca2e70a0 R09: 8f19bb80e900
[1.240560] R10:  R11:  R12: 8f19bc9beb80
[1.240562] R13: 8f19bb828000 R14:  R15: 8f19bb828000
[1.240565] FS:  7fcb1b4ce680() GS:8f19ca2c() 
knlGS:
[1.240567] CS:  0010 DS:  ES:  CR0: 80050033
[1.240569] CR2: 5586ffbcde18 CR3: 000405172000 CR4: 003406e0
[1.240572] Call Trace:
[1.240616]  ? dal_aux_engine_dce110_create+0x2a/0x80 [amdgpu]
[1.240621]  ? _cond_resched+0x19/0x40
[1.240625]  ? kmem_cache_alloc_trace+0x198/0x1b0
[1.240667]  ? dcn10_create_resource_pool+0x2a/0x60 [amdgpu]
[1.240709]  dcn10_create_resource_pool+0x41/0x60 [amdgpu]
[1.240751]  dc_create_resource_pool+0x46/0x180 [amdgpu]
[1.240754]  ? _cond_resched+0x19/0x40
[1.240756]  ? __kmalloc+0x1e7/0x220
[1.240798]  ? dal_gpio_service_create+0xa1/0x120 [amdgpu]
[1.240839]  dc_create+0x244/0x6c0 [amdgpu]
[1.240882]  dm_hw_init+0xf2/0x2a0 [amdgpu]
[1.240914]  amdgpu_device_init+0xd23/0x1620 [amdgpu]
[1.240946]  amdgpu_driver_load_kms+0x8b/0x2e0 [amdgpu]
[1.240957]  drm_dev_register+0x149/0x1d0 [drm]
[1.240988]  amdgpu_pci_probe+0x113/0x150 [amdgpu]
[1.240992]  local_pci_probe+0x47/0xa0
[1.240995]  pci_device_probe+0x145/0x1b0
[1.240999]  driver_probe_device+0x31e/0x490
[1.241001]  __driver_attach+0xa7/0xf0
[1.241004]  ? driver_probe_device+0x490/0x490
[1.241006]  bus_for_each_dev+0x70/0xc0
[1.241008]  driver_attach+0x1e/0x20
[1.241011]  bus_add_driver+0x1c7/0x270
[1.241013]  ? 0xc0611000
[1.241015]  driver_register+0x60/0xe0
[1.241017]  ? 0xc0611000
[1.241020]  __pci_register_driver+0x5a/0x60
[1.241054]  amdgpu_init+0x96/0xa9 [amdgpu]
[1.241058]  do_one_initcall+0x52/0x19f
[1.241061]  ? __vunmap+0x81/0xb0
[1.241063]  ? _cond_resched+0x19/0x40
[1.241065]  ? kmem_cache_alloc_trace+0xa6/0x1b0
[1.241069]  ? do_init_module+0x27/0x209
[1.241071]  do_init_module+0x5f/0x209
[1.241074]  load_module+0x191e/0x1f10
[1.241077]  ? ima_post_read_file+0x96/0xa0
[1.241080]  SYSC_finit_module+0xfc/0x120
[1.241083]  ? SYSC_finit_module+0xfc/0x120
...
are found every now and then.

** Affects: linux-signed-hwe-edge (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  frequent crashes during boot on Ryzen 3 2200G

Status in linux-signed-hwe-edge package in Ubuntu:
  New

Bug description:
  Most of the time when booting Ubuntu 18.04 (beta) on my recently bought Ryzen 
3 2200 G (Micro-Star International 

[Desktop-packages] [Bug 1760905] Re: nautilus does not start at all

[Johannes Kalliauer]

When running in terminal following message occurs:


(nautilus:6672): GLib-GIO-ERROR **: 15:28:37.119: Settings schema 
'org.gnome.nautilus.preferences' does not contain a key named 
'search-filter-time-type'
Trace/breakpoint trap

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

Title:
  nautilus does not start at all

Status in nautilus package in Ubuntu:
  New

Bug description:
  Since Ubuntu 16.04 is updated to Ubuntu 18.04, Nautilus does not
  start.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Tue Apr  3 17:13:56 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-04-07 (360 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: nautilus
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_enum () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-03-29 (5 days ago)
  UserGroups:
   
  usr_lib_nautilus:
   dropbox  2015.10.28
   nautilus-actions 3.2.3-1build3

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

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

[Desktop-packages] [Bug 1760870] Re: nautilus-desktop crashed with signal 5

[Johannes Kalliauer]

If I start it in the terminal I get following error-messages:

(nautilus-desktop:24013): GLib-GIO-ERROR **: 10:45:17.365: Settings schema 
'org.gnome.nautilus.preferences' does not contain a key named 
'search-filter-time-type'
Trace/breakpoint trap (core dumped)


** Information type changed from Private to Public

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

Title:
  nautilus-desktop crashed with signal 5

Status in nautilus package in Ubuntu:
  New

Bug description:
  Occurred after updating Ubuntu 16.04 to Ubuntu 18.04

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  3 15:42:33 2018
  ExecutablePath: /usr/bin/nautilus-desktop
  ExecutableTimestamp: 1521922016
  InstallationDate: Installed on 2017-04-07 (360 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: nautilus-desktop
  ProcCwd: /home/jkalliau
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_enum () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus-desktop crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-03-29 (4 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  usr_lib_nautilus:
   dropbox  2015.10.28
   nautilus-actions 3.2.3-1build3

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

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

[Desktop-packages] [Bug 1760905] Re: nautilus does not start at all

[Johannes Kalliauer]

** Information type changed from Private to Public

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

Title:
  nautilus does not start at all

Status in nautilus package in Ubuntu:
  New

Bug description:
  Since Ubuntu 16.04 is updated to Ubuntu 18.04, Nautilus does not
  start.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Tue Apr  3 17:13:56 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-04-07 (360 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: nautilus
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_settings_get_enum () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ()
   g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2018-03-29 (5 days ago)
  UserGroups:
   
  usr_lib_nautilus:
   dropbox  2015.10.28
   nautilus-actions 3.2.3-1build3

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

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

[Desktop-packages] [Bug 1761428] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()

[Johannes Kalliauer]

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

** Description changed:

  ibus crashes in normal operation condition without any indications
  
- Might be related to following Bugs #1712902 #1380982 #1304708 #1295603
- #1252666 #1048161
- [https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1048161 #1048161]
+ Might be related to following Bugs
+ https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1048161
+ https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1252666
+ https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1295603
+ https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1304708
+ https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1380982
+ https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1712902
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  5 11:25:56 2018
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2017-04-07 (362 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim --address 
unix:tmpdir=/tmp/ibus
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   ()
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to bionic on 2018-03-29 (6 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo

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

Title:
  ibus-daemon crashed with SIGABRT in g_assertion_message()

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus crashes in normal operation condition without any indications

  Might be related to following Bugs
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1048161
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1252666
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1295603
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1304708
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1380982
  https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1712902

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  5 11:25:56 2018
  ExecutablePath: /usr/bin/ibus-daemon
  InstallationDate: Installed on 2017-04-07 (362 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim --address 
unix:tmpdir=/tmp/ibus
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ()
   ()
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-daemon crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: Upgraded to bionic on 2018-03-29 (6 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

[Johannes Winter]

Followed slava-dr tipps, but didn't manage to get external mic working
on asus x555ua.

Any more tips on how to connect "unconnected pins" ?

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Desktop-packages] [Bug 1697126] [NEW] Popping sound whenever a client connects / disconnects

[Johannes H. Jensen]

Public bug reported:

I'm getting an annoying popping sound whenever pulseaudio gets a new
connection or a connection dies. This is especially annoying since
google chrome seems to open new connections rather often for no apparent
reason, interrupting music playback with glitches.

Steps to reproduce:
1. Start playback of some audio with totem or similar
2. Play a silent audio file with paplay silence.wav, I got mine from audacity
3. Observe pops in the playback from totem

Interestingly there are no pops if I use paplay instead of totem for
step 1. Attaching debug output from pulseaudio - during the
reproducer above.

My sound card is a USB DAC:

card 3: DAC [UAC1 DAC], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.2
ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
Uname: Linux 4.4.0-79-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  joh   19113 F pulseaudio
 /dev/snd/controlC2:  joh   19113 F pulseaudio
 /dev/snd/controlC1:  joh   19113 F pulseaudio
 /dev/snd/controlC0:  joh   19113 F pulseaudio
CurrentDesktop: GNOME
Date: Sat Jun 10 04:06:46 2017
InstallationDate: Installed on 2011-10-01 (2078 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to xenial on 2016-09-18 (264 days ago)
dmi.bios.date: 09/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.7
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97 GAMING 5 (MS-7917)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/18/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7917
dmi.product.version: 1.0
dmi.sys.vendor: MSI

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


** Tags: amd64 apport-bug xenial

** Attachment added: "debug output from pulseaudio - while reproducing the 
issue"
   
https://bugs.launchpad.net/bugs/1697126/+attachment/4893344/+files/pa-popping.log

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

Title:
  Popping sound whenever a client connects / disconnects

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I'm getting an annoying popping sound whenever pulseaudio gets a new
  connection or a connection dies. This is especially annoying since
  google chrome seems to open new connections rather often for no
  apparent reason, interrupting music playback with glitches.

  Steps to reproduce:
  1. Start playback of some audio with totem or similar
  2. Play a silent audio file with paplay silence.wav, I got mine from audacity
  3. Observe pops in the playback from totem

  Interestingly there are no pops if I use paplay instead of totem for
  step 1. Attaching debug output from pulseaudio - during the
  reproducer above.

  My sound card is a USB DAC:

  card 3: DAC [UAC1 DAC], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.2
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  joh   19113 F pulseaudio
   /dev/snd/controlC2:  joh   19113 F pulseaudio
   /dev/snd/controlC1:  joh   19113 F pulseaudio
   /dev/snd/controlC0:  joh   19113 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Jun 10 04:06:46 2017
  InstallationDate: Installed on 2011-10-01 (2078 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to xenial on 2016-09-18 (264 days ago)
  dmi.bios.date: 09/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97 GAMING 5 (MS-7917)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd09/18/2014:svnMSI:pnMS-7917:pvr1.0:rvnMSI:rnZ97GAMING5(MS-7917):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7917
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage 

[Desktop-packages] [Bug 1687614] Re: broken ghostscript with 9.18~dfsg~0-0ubuntu2.3 to 9.18~dfsg~0-0ubuntu2.4 update

[Johannes Schmitz]

I installed the package and can confirm that it solves the issue.

>From my side feel free to go ahead and publish it.

Thank you!

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

Title:
  broken ghostscript with 9.18~dfsg~0-0ubuntu2.3 to
  9.18~dfsg~0-0ubuntu2.4 update

Status in GS-GPL:
  Unknown
Status in ghostscript package in Ubuntu:
  Triaged

Bug description:
  After the last ghostscript udpate I have problems with the textext
  inkscape plugin that uses pstoedit that uses ghostscript.

  The command looks like this:

  pstoedit -f plot-svg tmp.pdf tmp.svg -dt -ssp -psarg -r9600x9600 -pta

  The error (short version):

  Error: /invalidaccess in --run--
  Current allocation mode is global
  Last OS error: No such file or directory
  Current file position is 87896
  GPL Ghostscript 9.18: Unrecoverable error, exit code 1
  PostScript/PDF Interpreter finished. Return status 256 executed command : 
/usr/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS -r9600x9600 
"/tmp/psinsRrD8m"
  The interpreter seems to have failed, cannot proceed !

  See the attached log for the full text.

  I tried to downgrade to circumvent the issue but unsuccessfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1687614/+subscriptions

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

[Desktop-packages] [Bug 1687614] Re: broken ghostscript with 9.18~dfsg~0-0ubuntu2.3 to 9.18~dfsg~0-0ubuntu2.4 update

[Johannes Schmitz]

How, long till the patch? This is effectively stopping people from work,
why not to deploy the patch ASAP?

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

Title:
  broken ghostscript with 9.18~dfsg~0-0ubuntu2.3 to
  9.18~dfsg~0-0ubuntu2.4 update

Status in GS-GPL:
  Unknown
Status in ghostscript package in Ubuntu:
  Triaged

Bug description:
  After the last ghostscript udpate I have problems with the textext
  inkscape plugin that uses pstoedit that uses ghostscript.

  The command looks like this:

  pstoedit -f plot-svg tmp.pdf tmp.svg -dt -ssp -psarg -r9600x9600 -pta

  The error (short version):

  Error: /invalidaccess in --run--
  Current allocation mode is global
  Last OS error: No such file or directory
  Current file position is 87896
  GPL Ghostscript 9.18: Unrecoverable error, exit code 1
  PostScript/PDF Interpreter finished. Return status 256 executed command : 
/usr/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS -r9600x9600 
"/tmp/psinsRrD8m"
  The interpreter seems to have failed, cannot proceed !

  See the attached log for the full text.

  I tried to downgrade to circumvent the issue but unsuccessfully.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gs-gpl/+bug/1687614/+subscriptions

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

Re: [Desktop-packages] [Bug 1687614] Re: broken ghostscript with 9.18~dfsg~0-0ubuntu2.3 to 9.18~dfsg~0-0ubuntu2.4 update

[Johannes Schmitz]

Can you please tell me how to downgrade?

Am 02.05.2017 21:55 schrieb "Eric Gourgoulhon"
<1687...@bugs.launchpad.net>:

> The bug has also been reported in
> https://askubuntu.com/questions/910341/inkscape-error-with-textext
> Downgrading to ghostscript 9.18~dfsg~0-0ubuntu2 circumvented it for me
> (Ubuntu 16.04).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1687614
>
> Title:
>   broken ghostscript with 9.18~dfsg~0-0ubuntu2.3 to
>   9.18~dfsg~0-0ubuntu2.4 update
>
> Status in ghostscript package in Ubuntu:
>   Confirmed
>
> Bug description:
>   After the last ghostscript udpate I have problems with the textext
>   inkscape plugin that uses pstoedit that uses ghostscript.
>
>   The command looks like this:
>
>   pstoedit -f plot-svg tmp.pdf tmp.svg -dt -ssp -psarg -r9600x9600 -pta
>
>   The error (short version):
>
>   Error: /invalidaccess in --run--
>   Current allocation mode is global
>   Last OS error: No such file or directory
>   Current file position is 87896
>   GPL Ghostscript 9.18: Unrecoverable error, exit code 1
>   PostScript/PDF Interpreter finished. Return status 256 executed command
> : /usr/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS
> -r9600x9600 "/tmp/psinsRrD8m"
>   The interpreter seems to have failed, cannot proceed !
>
>   See the attached log for the full text.
>
>   I tried to downgrade to circumvent the issue but unsuccessfully.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ghostscript/+
> bug/1687614/+subscriptions
>

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

Title:
  broken ghostscript with 9.18~dfsg~0-0ubuntu2.3 to
  9.18~dfsg~0-0ubuntu2.4 update

Status in ghostscript package in Ubuntu:
  Confirmed

Bug description:
  After the last ghostscript udpate I have problems with the textext
  inkscape plugin that uses pstoedit that uses ghostscript.

  The command looks like this:

  pstoedit -f plot-svg tmp.pdf tmp.svg -dt -ssp -psarg -r9600x9600 -pta

  The error (short version):

  Error: /invalidaccess in --run--
  Current allocation mode is global
  Last OS error: No such file or directory
  Current file position is 87896
  GPL Ghostscript 9.18: Unrecoverable error, exit code 1
  PostScript/PDF Interpreter finished. Return status 256 executed command : 
/usr/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS -r9600x9600 
"/tmp/psinsRrD8m"
  The interpreter seems to have failed, cannot proceed !

  See the attached log for the full text.

  I tried to downgrade to circumvent the issue but unsuccessfully.

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

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

[Desktop-packages] [Bug 1687614] [NEW] broken ghostscript with 9.18~dfsg~0-0ubuntu2.3 to 9.18~dfsg~0-0ubuntu2.4 update

[Johannes Schmitz]

Public bug reported:

After the last ghostscript udpate I have problems with the textext
inkscape plugin that uses pstoedit that uses ghostscript.

The command looks like this:

pstoedit -f plot-svg tmp.pdf tmp.svg -dt -ssp -psarg -r9600x9600 -pta

The error (short version):

Error: /invalidaccess in --run--
Current allocation mode is global
Last OS error: No such file or directory
Current file position is 87896
GPL Ghostscript 9.18: Unrecoverable error, exit code 1
PostScript/PDF Interpreter finished. Return status 256 executed command : 
/usr/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS -r9600x9600 
"/tmp/psinsRrD8m"
The interpreter seems to have failed, cannot proceed !

See the attached log for the full text.

I tried to downgrade to circumvent the issue but unsuccessfully.

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

** Attachment added: "Error log"
   
https://bugs.launchpad.net/bugs/1687614/+attachment/4870792/+files/gs_error_log.txt

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

Title:
  broken ghostscript with 9.18~dfsg~0-0ubuntu2.3 to
  9.18~dfsg~0-0ubuntu2.4 update

Status in ghostscript package in Ubuntu:
  New

Bug description:
  After the last ghostscript udpate I have problems with the textext
  inkscape plugin that uses pstoedit that uses ghostscript.

  The command looks like this:

  pstoedit -f plot-svg tmp.pdf tmp.svg -dt -ssp -psarg -r9600x9600 -pta

  The error (short version):

  Error: /invalidaccess in --run--
  Current allocation mode is global
  Last OS error: No such file or directory
  Current file position is 87896
  GPL Ghostscript 9.18: Unrecoverable error, exit code 1
  PostScript/PDF Interpreter finished. Return status 256 executed command : 
/usr/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS -r9600x9600 
"/tmp/psinsRrD8m"
  The interpreter seems to have failed, cannot proceed !

  See the attached log for the full text.

  I tried to downgrade to circumvent the issue but unsuccessfully.

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

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

[Desktop-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

[Johannes Martin]

Switching "-l" to "-f" in /lib/systemd/system/cups.service solved the
problem for me. cupsd has now been up for about an hour without shutting
down automatically.

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

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

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

[Desktop-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

[Johannes Martin]

I'm also affected by this bug, lots of shared printers (this is the cups
server for the network) and cupsd shutting down claiming printer sharing
was off.

launchpad-groovix: in 14.04, the only allowed values for
BrowseLocalProtocol are All and dnssd, in 16.04 I see All, dnssd, and
none. Is CUPS some deprecated setting? My cupsd.conf does not have this
set at all, so it's using the default whatever that is.

Adding BrowseLocalProtocol dnssd to cupsd.conf did not solve the problem
for me, btw.

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

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

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

[Desktop-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while

[Johannes Martin]

I'm also affected by this bug, lots of shared printers (this is the cups
server for the network) and cupsd shutting down claiming printer sharing
was off.

launchpad-groovix: in 14.04, the only allowed values for
BrowseLocalProtocol are All and dnssd, in 16.04 I see All, dnssd, and
none. Is CUPS some deprecated setting? My cupsd.conf does not have this
set at all, so it's using the default whatever that is.

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

Title:
  CUPS web interface stops responding after a while

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Xenial:
  Fix Committed

Bug description:
  after 6 minutes or so, cups is not responding.
  it do not produce error on the log, just stop working, worse, it exit with 0

  
⌌—⌍
  |root@cupsmachine :~# systemctl status cups   
|
  |● cups.service - CUPS Scheduler  
|
  |   Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: 
enabled)|
  |   Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago 
|
  | Docs: man:cupsd(8)  
|
  |  Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, 
status=0/SUCCESS)|
  | Main PID: 28686 (code=exited, status=0/SUCCESS) 
|
  | 
|
  |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler.   
|
  
⌎—⌏

  I got to launch it again, so I have finish with a cron job like
  */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && 
systemctl start cups

  but it is a dirty solution. I have no idea of what make it stop.
  NB: I have seen problems related to apparmor, this machine has no apparmor 
package.

  [Impact]

  If you want to use the CUPS web interface in Xenial and therefore set
  "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown
  when it is idle and then an attempt to access http://localhost:631/
  via a web browser fails. People get confused as other access to CUPS

  [Testcase]

  Take a CUPS setup on Xenial with no shared print queues and CUPS only
  listening on the domain socket. Activate the web interface via

  cupsctl WebInterface=Yes

  Now you are able to access the web interface via
  http://localhost:631/. Wait for some minutes without accessing CUPS
  until the CUPS daemon shuts down automatically. Try to open the web
  interface again and it will not work.

  With the fixed CUPS package CUPS will not auto-shutdown when the web
  interface is activated.

  [Regression Potential]

  Low, as we are removing a simple distro patch to get back to the
  original, upstream behavior.

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

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

[Desktop-packages] [Bug 1352809] Re: /usr/bin/lp on Trusty using -h option doesn't work as expected

[Johannes Martin]

The bug is back in cups-client 1.7.2-0ubuntu1.7!

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

Title:
  /usr/bin/lp on Trusty using -h option doesn't work as expected

Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Trusty:
  Fix Released
Status in cups source package in Utopic:
  Fix Released

Bug description:
  [SRU justification]
  The -h option should override the value stored in the CUPS_SERVER environment 
variable

  [Impact]
  Without this fix, user is unable to define the printserver to use with the -h 
option

  [Fix]
  Verify if the -h option has defined the printserver before using CUPS_SERVER 
to define it.

  [Test Case]
  $ export CUPS_SERVER="blah"
  $ lp -h {valid printserver} -d {printqueue} /etc/hosts

  Without the fix :
  lp: No such file or directory

  With the fix :
  request id is {printqueue}-37 (1 file(s))

  [Regression]
  None expected. New code path (from upstream patch) is only triggered if
  -h option is used.

  [Original description of the problem]

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Codename: trusty

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  cups-client:
    Installed: 1.7.2-0ubuntu1.1

  3) What you expected to happen

  When using lp -h to send a print job to a printer, I expected to the
  job to be sent to the printer and to override any env variables set or
  conf file setting

  4) What happened instead

  To summarise the behaviour I'm seeing

  1) with CUPS_SERVER env variable unset and no ServerName set in 
/etc/cups/client.conf, we see that using lp -h with hostnames gives us error 
"lp: Error - add '/version=1.1' to server name."
  Using IPs sends the job to the printer as expected.

  2) with CUPS_SERVER env variable set using hostname with/without port
  and no ServerName set in /etc/cups/client.conf, we see that the only
  time it sends a job is when an IP and port are used. Otherwise it
  seems to error. I believe it's using the env variable, even though -h
  is being used.

  3) with CUPS_SERVER env variable set using IP address with/without
  port and no ServerName set in /etc/cups/client.conf we see that the
  job is always sent using lp -h but it is always sent to the value in
  env variable, thus ignoring the command line.

  ===

  with CUPS_SERVER env variable unset and no ServerName option set in
  /etc/cups/client.conf

  $ lp test2.txt
  lp: Error - scheduler not responding. (expected as no server is set or 
specified)

  Using hostname
  $ lp -h server1:631 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h server1 test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using IP address
  $ lp -h 192.168.254.8 test2.txt
  request id is PDF-54 (1 file(s))

  $ lp -h 192.168.254.8:631 test2.txt
  request id is PDF-55 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=server1

  $ lp test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using hostname
  $ lp -h server1 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h server1:631 test2.txt
  lp: Error - add '/version=1.1' to server name.

  Using IP address
  $ lp -h 192.168.254.8 test2.txt
  lp: Error - add '/version=1.1' to server name.

  $ lp -h 192.168.254.8:631 test2.txt
  request id is PDF-56 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=server:631

  Same results as above

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=192.168.254.8:631

  $ lp -h 555.555.555.555 test2.txt
  request id is PDF-66 (1 file(s))

  ===

  With CUPS_SERVER env variable *set CUPS_SERVER=192.168.254.8

  Same results as above

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

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

[Desktop-packages] [Bug 1453137] Re: using pidgin login now fails with "Login verification down or unavailable"

[Johannes Rehm]

I still get the same error in Ubuntu 16.04.1. Also installing the newest 
version from here
https://launchpad.net/ubuntu/yakkety/amd64/libmeanwhile1/1.0.2-9
does not help.
But it works when I use the window .exe with wine

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

Title:
  using pidgin login now fails with "Login verification down or
  unavailable"

Status in meanwhile package in Ubuntu:
  Confirmed
Status in pidgin package in Ubuntu:
  Confirmed

Bug description:
  after upgrading to vivid libmeanwhile plugin no longer works with pidgin 
always reporting "Login verification down or unavailable".
  This is a know bug upstream 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764584.
  The current solution is to use older meanwhile library (not tested but in bug 
report above)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: libmeanwhile1 1.0.2-5
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Fri May  8 08:42:23 2015
  InstallationDate: Installed on 2014-04-11 (392 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: meanwhile
  UpgradeStatus: Upgraded to vivid on 2015-05-07 (0 days ago)

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

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

[Desktop-packages] [Bug 1533480] Re: banshee stops respondiing during media import

[Johannes Konow]

I have tried various scenarios... First I tried with eMusic only
disabled and that didn't work for me. Then I tried disabling all the
suggested extensions and that made the import seamless. Then I tried to
purge the settings folder for banshee and reinstalled it and tried again
with only podcast disabled and it does work... kinda. It crashed on the
first import halfway through and the second one worked but no progress
bar.

Something very fishy is going on here.

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

Title:
  banshee stops respondiing during media import

Status in banshee package in Ubuntu:
  Confirmed

Bug description:
  Trying to import media to banshee in ubuntu 16.04 freezes banshee.
  Import works fine in rhythmbox. Problem only with banshee

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-5-generic 4.3.0-5.16
  ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
  Uname: Linux 4.3.0-5-generic x86_64
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  krishnan   1972 F pulseaudio
   /dev/snd/controlC0:  krishnan   1972 F pulseaudio
  Date: Wed Jan 13 10:20:16 2016
  HibernationDevice: RESUME=UUID=1f4f89ff-6e3c-4610-8450-a25509f5b5c5
  InstallationDate: Installed on 2015-12-26 (17 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: LENOVO INVALID
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic.efi.signed 
root=UUID=0bf37a84-dc7d-4bd4-999a-f8df2baffc39 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-5-generic N/A
   linux-backports-modules-4.3.0-5-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83CN12WW(V1.01)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo G505s
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G505s
  dmi.modalias: 
dmi:bvnLENOVO:bvr83CN12WW(V1.01):bd04/23/2013:svnLENOVO:pnINVALID:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505s:
  dmi.product.name: INVALID
  dmi.product.version: Lenovo G505s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1629493] Re: xorg problems after upgrade from 14.04 to 16.04

[johannes]

** Description changed:

  I have big problems after upgrading from the software center to 16.04.
- My computer gets stuck in the boot process. It only works in recovery
- mode and if I change the display server to gdm instead of lightdm. The
- computer still boots into ttpy1 but from there I can start a window
- sessiond with startx.
+ My computer gets stuck in the boot process showing only the ubuntu logo.
  
- The fan from my pc is very loud. In low graphics mode, the hardware ist
- not recognized...what should I do?
+ The startup works in recovery mode but only if I change the display
+ server to gdm instead of lightdm. The computer than boots into ttpy1
+ from where I can start a window sessiond with startx.
+ 
+ The fan from my pc is very loud. In low graphics mode, the hardware is
+ not recognized correctly as it seems. My graphics card is ADM readon
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.1:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.1
  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: GNOME
  Date: Sat Oct  1 02:08:44 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
-Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071]
+  Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
+    Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071]
  InstallationDate: Installed on 2013-03-10 (1300 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Sony Corporation VPCEC4B4E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=ecee3b65-74b1-4e3c-9fe8-d2ce7e83ba5e ro recovery nomodeset 
radeon.audio=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1140Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:svnSonyCorporation:pnVPCEC4B4E:pvrC6086ZZW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCEC4B4E
  dmi.product.version: C6086ZZW
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  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: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Oct  1 02:03:43 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  
+ 
  xserver.version: 2:1.18.3-1ubuntu2.3

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

Title:
  xorg problems after upgrade from 14.04 to 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I have big problems after upgrading from the software center to 16.04.
  My computer gets stuck in the boot process showing only the ubuntu
  logo.

  The startup works in recovery mode but only if I change the display
  server to gdm instead of lightdm. The computer than boots into ttpy1
  from where I can start a window sessiond with startx.

  The fan from my pc is very loud. In low graphics mode, the hardware is
  not recognized correctly as it seems. My graphics card is ADM readon

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 

[Desktop-packages] [Bug 1629493] [NEW] xorg problems after upgrade from 14.04 to 16.04

[johannes]

Public bug reported:

I have big problems after upgrading from the software center to 16.04.
My computer gets stuck in the boot process. It only works in recovery
mode and if I change the display server to gdm instead of lightdm. The
computer still boots into ttpy1 but from there I can start a window
sessiond with startx.

The fan from my pc is very loud. In low graphics mode, the hardware ist
not recognized...what should I do?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: GNOME
Date: Sat Oct  1 02:08:44 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 
6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071]
InstallationDate: Installed on 2013-03-10 (1300 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Sony Corporation VPCEC4B4E
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=ecee3b65-74b1-4e3c-9fe8-d2ce7e83ba5e ro recovery nomodeset 
radeon.audio=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/06/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1140Y8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:svnSonyCorporation:pnVPCEC4B4E:pvrC6086ZZW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCEC4B4E
dmi.product.version: C6086ZZW
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
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: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sat Oct  1 02:03:43 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  xorg problems after upgrade from 14.04 to 16.04

Status in xorg package in Ubuntu:
  New

Bug description:
  I have big problems after upgrading from the software center to 16.04.
  My computer gets stuck in the boot process. It only works in recovery
  mode and if I change the display server to gdm instead of lightdm. The
  computer still boots into ttpy1 but from there I can start a window
  sessiond with startx.

  The fan from my pc is very loud. In low graphics mode, the hardware
  ist not recognized...what should I do?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: GNOME
  Date: Sat Oct  1 02:08:44 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071]
  InstallationDate: Installed on 2013-03-10 (1300 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  

[Desktop-packages] [Bug 1621374] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Johannes Schmitt]

Public bug reported:

When upgrading from 16.04 to 14.04, the package tex-common 6.04 seems to
have caused problems.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Sep  8 10:23:04 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2014-01-21 (960 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-09-08 (0 days ago)

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

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

Status in tex-common package in Ubuntu:
  New

Bug description:
  When upgrading from 16.04 to 14.04, the package tex-common 6.04 seems
  to have caused problems.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep  8 10:23:04 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-01-21 (960 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-09-08 (0 days ago)

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

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

[Desktop-packages] [Bug 1531224] Re: lightdm-gtk-greeter flickers once little after lightdm starts

[Johannes Lange]

Recently, xserver-xorg-video-intel has been updated to xserver-xorg-
video-intel 2:2.99.917+git20160325-1ubuntu1.1 to fix
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1568604. However, this update doesn't fix the bug discussed
here for me.

Ubuntu 16.04.1 LTS (xenial)
Hardware: Dell OptiPlex 3020 with Core i5-4690 and Intel HD Graphics 4600

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

Title:
  lightdm-gtk-greeter flickers once little after lightdm starts

Status in LightDM GTK+ Greeter:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  New

Bug description:
  Bug context:
   · Arch Linux x86_64 4.3.3-2-ARCH
   · systemd 228-3 (using lightdm-plymouth.service)
   · plymouth 0.9.2-8 (compiled from AUR)
   · lightdm 1:1.16.6-2
   · lightdm-gtk-greeter 1:2.0.1-2

  At the end of boot process, right after plymouth splash, lightdm starts 
normally and the GTK+ greeter login screen is shown for about 1 second, but 
then the screen instantly flickers (goes black) and the greeter is redrawn. 
From here on, everything works flawlessly, but the brief flickering is 
certainly annoying.
  This happens every time and no other greeter I have tried presents this 
issue, so I can confirm it is lightdm-gtk-greeter-related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1531224/+subscriptions

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

[Desktop-packages] [Bug 1572250] Re: Wrong type of Wi-Fi device (wlp2s0) after boot

[Johannes Stickel]

I have the same issue, however using brcmfmac instead of iwlwifi.

Your workaround (reloading the module) works fine.

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

Title:
  Wrong type of Wi-Fi device (wlp2s0) after boot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello
  My Wi-Fi adapter is Intel 7260. After boot I have

  nmcli device status
  DEVICE  TYPE  STATECONNECTION 
  wlp2s0  ethernet  unavailable  -- 
  lo  loopback  unmanaged--

  after some dirty fix (sudo rmmod iwlmvm iwlwifi && sudo modprobe
  iwlwifi)

  nmcli device status
  DEVICE  TYPE  STATE CONNECTION 
  wlp2s0  wifi  disconnected  -- 
  lo  loopback  unmanaged --

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Apr 19 22:22:59 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
   
   #auto wlp2s0
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.123  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
libreCMC91f33459-b8b5-43ea-a742-a09720f20821  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1284308] Re: Can't copy files from a bluetooth device: Another operation in progress

[johannes]

Confirmed on Linux Mint Debian with gvfs 1.22.2. Also, browsing with Thunar is 
quite sluggish.
 

Workaround for some Nokia (Symbian) phones:


obexfs -b  


where  is the Bluetooth address of the device and  is the 
directory where you want to mount the device.

No root privileges required. Make sure you own the path, otherwise you
can only access it as root.

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

Title:
  Can't copy files from a bluetooth device: Another operation in
  progress

Status in gvfs:
  Invalid
Status in gvfs package in Ubuntu:
  Triaged

Bug description:
  1)  lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  2) apt-cache policy gvfs
  gvfs:
    Installed: 1.20.1-1ubuntu1
    Candidate: 1.20.1-1ubuntu1
    Version table:
   *** 1.20.1-1ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one pairs their bluetooth phone,
  browses it, and attempt to copy a file from the phone to Ubuntu, it
  does so successfully.

  4) What happens instead is a window pops up noting:
  Error while copying “example.txt”.
  There was an error copying the file into /home/test/
  Show more details
  Another operation in progress

  Originally reproduced in 13.10.

  /usr/lib/gvfs/gvfsd-obexftp 'host=[XX:XX:XX:XX:XX:XX]'
  ** Message: transfer of example.txt to /tmp/gvfsobexftp-tmp-NTNMQX started
  ** Message: filename: /Internal storage/Download/example.txt (example.txt) 
copying to /tmp/gvfsobexftp-tmp-NTNMQX (retval 2)
  ** Message: ChangeCurrentFolderToRoot failed
  ** Message: transfer got cancelled
  ** Message: ChangeCurrentFolderToRoot failed

  WORKAROUND: Connect phone via USB cord to transfer files from the
  phone to Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

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

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

[Desktop-packages] [Bug 1314556] Re: Unable to mount Android MTP device

[Johannes Konow]

I can confirm this on two computers. One with 15.10 and the other with
14.04 (LTS version). Thing is, gMTP is working fine out of the box on
both computers so the issue is not the hardware.

I have had problems with MTP ever since android switched to MTP (various
phones, various computers) but have worked around with SD cards up until
now... new phone doesn't have SD card slot.

I feel this is a very important issue that needs solving ASAP if we want
the regular user to feel comfortable using Ubuntu.

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

Title:
  Unable to mount Android MTP device

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I have the same problem on 3 computers with 14.04:

  So I tried,
   mtp-detect 
  Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

  Listing raw device(s)
  Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
 Found 1 device(s):
 Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10
  Attempting to connect device(s)
  ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
  LIBMTP libusb: Attempt to reset device
  inep: usb_get_endpoint_status(): Resource temporarily unavailable
  outep: usb_get_endpoint_status(): Device or resource busy
  ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on 
second attempt
  Unable to open raw device 0
  OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs-backends 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 30 11:18:12 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor
  InstallationDate: Installed on 2013-02-12 (441 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago)

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

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

[Desktop-packages] [Bug 1314556] Re: Unable to mount Android MTP device

[Johannes Konow]

Sorry, was too quick. Should add that I have tried various workarounds
with udev rules, the workaround in comment #40 etc, nothing seems to fix
the connection out of the box. I need to rely on gMTP for transfer.

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

Title:
  Unable to mount Android MTP device

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  I have the same problem on 3 computers with 14.04:

  So I tried,
   mtp-detect 
  Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

  Listing raw device(s)
  Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
 Found 1 device(s):
 Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10
  Attempting to connect device(s)
  ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
  LIBMTP libusb: Attempt to reset device
  inep: usb_get_endpoint_status(): Resource temporarily unavailable
  outep: usb_get_endpoint_status(): Device or resource busy
  ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on 
second attempt
  Unable to open raw device 0
  OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gvfs-backends 1.20.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 30 11:18:12 2014
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor
  InstallationDate: Installed on 2013-02-12 (441 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago)

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

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

[Desktop-packages] [Bug 1438003] Re: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib.

[johannes lindgren]

Experiencing the same thing as krupier123 on Ubuntu 14.10. I have tried
all workarounds mentioned here. Reinstalling NetworkManager fixes the
issue for a couple of minutes, then the connection dies again.
Rebooting, suspending, setting managed=true in NetworkManager.conf does
not do anything.

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

Title:
  (1) Creating object for path
  '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-
  glib.

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  While attempting to connect to an SSID for the first time, it fails, and I 
consistently get:
  (1) Creating object for path 
'/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu11
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Mar 29 23:08:37 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-03-29 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlan0   wifi  connected /org/freedesktop/NetworkManager/Devices/4  
www.ubuntu.com  71c36534-c491-4479-aa91-9238b10f3945  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlan1   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   eth0ethernet  unavailable   /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Desktop-packages] [Bug 1489816] Re: gstreamer/rhythmbox submits invalid Disc IDs to MusicBrainz (Trusty Tahr)

[Johannes Dewender]

Hm, I was kind of hoping that an actual Trusty user could test this..

Anyways, I used a PC with 2 drives, using one for a Trusty Live DVD to
test this.

Opening my "Guano Apes  - Don't Give Me Names" CD (having a traling data
track with multimedia) in Rhythmbox on a vanilla system didn't find the
disc on MusicBrainz.

Installing gstreamer1.0-plugins-base_1.2.4-1~ubuntu2 (updating
dependencies automatically) made Rhythmbox find the disc on MusicBrainz.

=> verified

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  gstreamer/rhythmbox submits invalid Disc IDs to MusicBrainz (Trusty
  Tahr)

Status in gst-plugins-base:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 source package in Trusty:
  Fix Committed

Bug description:
  Gstreamer calculates an ID for Audio CDs and optionally submits it to 
MusicBrainz.
  This enables programs to find the corresponding metadata for a CD on 
MusicBrainz.

  Gstreamer < 1.3.1 doesn't do this correctly for CDs with data tracks,
  leading to invalid Disc IDs being submitted to the MusicBrainz
  database.

  This is reported upstream in https://bugzilla.gnome.org/show_bug.cgi?id=708991
  and fixed in gstreamer 1.3.1. The corresponding patch is supplied as an 
attachment here.
  Trusty Tahr is using 1.2.x and there is no new release on that branch.
  Trusty Tahr is still supported until 2019. It would be really nice if that 
can be fixed.

  The bug surfaces as a problem in Rhythmbox because starting with 2.97
  this uses gstreamer for MusicBrainz Disc ID handling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-base/+bug/1489816/+subscriptions

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

[Desktop-packages] [Bug 1517562] [NEW] package fglrx-updates-core (not installed) failed to install/upgrade: attemp to overwrite, »/usr/bin/clinfo« which is in package clinfo 2.0.15.04.28-1

[Johannes]

Public bug reported:

sudo apt-get install fglrx-update causes problem if package clinfo is
already installed.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: fglrx-updates-core (not installed)
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Nov 18 17:57:14 2015
DistUpgraded: 2015-11-11 19:07:48,913 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.4, 4.2.0-18-generic, x86_64: installed
 virtualbox-guest, 5.0.4, 4.2.0-18-generic, x86_64: installed
DuplicateSignature: package:fglrx-updates-core:(not installed):Versuch, 
»/usr/bin/clinfo« zu überschreiben, welches auch in Paket clinfo 2.0.15.04.28-1 
ist
ErrorMessage: Versuch, »/usr/bin/clinfo« zu überschreiben, welches auch in 
Paket clinfo 2.0.15.04.28-1 ist
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R7 370 / R9 270X/370 
OEM] [1002:6810] (prog-if 00 [VGA controller])
   Subsystem: Hightech Information System Ltd. Device [1787:201c]
InstallationDate: Installed on 2015-11-11 (6 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=99bcc9e4-5b16-4fc9-9b4c-da5ec1767175 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.2ubuntu5
 apt  1.0.10.2ubuntu1
SourcePackage: fglrx-installer-updates
Title: package fglrx-updates-core (not installed) failed to install/upgrade: 
Versuch, »/usr/bin/clinfo« zu überschreiben, welches auch in Paket clinfo 
2.0.15.04.28-1 ist
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-11-11 (6 days ago)
dmi.bios.date: 08/22/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3905
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-M PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3905:bd08/22/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Nov 18 17:46:27 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9
xserver.video_driver: radeon

** Affects: fglrx-installer-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package compiz-0.9 need-duplicate-check ubuntu wily

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

Title:
  package fglrx-updates-core (not installed) failed to install/upgrade:
  attemp to overwrite, »/usr/bin/clinfo« which is in package clinfo
  2.0.15.04.28-1

Status in fglrx-installer-updates package in Ubuntu:
  New

Bug description:
  sudo apt-get install fglrx-update causes problem if package clinfo is
  already installed.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: fglrx-updates-core (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 18 17:57:14 2015
  DistUpgraded: 2015-11-11 19:07:48,913 DEBUG enabling apt cron job
  DistroCodename: 

[Desktop-packages] [Bug 1510970] Re: Intel driver crashes on Ubuntu 15.10

[Johannes Merkert]

I updated the kernel to 4.3 today but still got two crashes since then.

I also created /etc/mkinitcpio.conf and put "i915" in the file but that
did not change anything.

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 

[Desktop-packages] [Bug 1510970] Re: Intel driver crashes on Ubuntu 15.10

[Johannes Merkert]

Today I had a scenario where I could reproduce the Bug: I opened
LibreOffice Writer and inserted areas into the document. The first one
always worked but when I created the second area the X-server crashed.

I also noticed that apport took longer with each crash. After the third
crash I always killed apport because it prevented me for more than 30s
to log in again.

Could you give some update on the status of this bug? Is somebody from Intel 
working on this? 
I have to downgrade to an older Ubuntu version if this bug can't be fixed soon.

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): 

Re: [Desktop-packages] [Bug 1510180] Re: Xorg freeze

[Dipl.-Ing. (FH) Johannes Neugschwentner]

thx!!!

I've updated my BIOS.
So far I've had a few crashes ... but it wasn't clear if it's not due to my
new mt7601Usta patched wifi-driver ... usb wifi stick ...

If I see the patterned screen with full freeze again I'll send another bug
report ...
If not, I'll give it a few days and change the bug-report status (if I
don't forget) ...

thx, J

+--[ RSA 2048]+
|  .  |
|   . . o |
|  . o +  |
| .   = . |
|S   = E o|
| o + * o.|
|  o @ +  |
|   + *   |
|...  |
+-+
+--+
|tn?bo |
|i-?*  |
|+c1   |
|=?|
|f  #  ##  |
|   # #|
|   #  ##  |
|#  ## |
| ##   ##  |
+--+
 jsstyle.github.com

2015-11-01 11:53 GMT-04:00 Christopher M. Penalver <
christopher.m.penal...@gmail.com>:

> Dipl.-Ing. (FH) Johannes Neugschwentner, thank you for reporting this
> and helping make Ubuntu better.
>
> As per https://www.asus.com/Motherboards/H97IPLUS/HelpDesk_Download/ an
> update to your computer's buggy and outdated BIOS is available (2604).
> If you update to this following
> https://help.ubuntu.com/community/BIOSUpdate does it change anything?
>
> If it doesn't, could you please both specify what happened, and provide
> the output of the following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
>
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful. As well, you don't
> have to create a new bug report.
>
> Once the BIOS is updated, if the problem is still reproducible, and the
> information above is provided, then please mark this report Status New.
> Otherwise, please mark this as Invalid.
>
> Thank you for your understanding.
>
> ** Tags added: bios-outdated-2604
>
> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1510180
>
> Title:
>   Xorg freeze
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Neither the proprietery nor the open source driver work well for my
>   ATI graphics card.
>
>   The OS driver is the better choice, as it crashes about twice a day and
> that's it ...
>   Crashes = strange patterns filling the screen plus X crashing (Keyboard
> combinations don't have effect anymore I think ... tried to quit my code
> editor with alt+f4 which should have closed all sourcefiles I was working
> on, still some of them were scrambled after reboot)
>
>   The proprietary driver works well for some time, then brings on all
> kinds of artifacts, displaying old (buffered) parts of windows where they
> aren't etc., for example on mouse scrolling ... unusable really
>   The Troubleshooting guide says something to check and by trial n error
> fix this in the BIOS by trying all AGP APERTURE SIZE settings ... well, I
> ain't got no AGP, I got the new stuff (ahemmm ... forget the name ...)
>   Also, I read it doesn't work with the new kernel of Ubuntu Wily ... so I
> guess I'm in luck I switched back in time.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: xorg 1:7.7+7ubuntu4
>   ProcVersionSignature: Ubuntu 4.2.0-16.19-lowlatency 4.2.3
>   Uname: Linux 4.2.0-16-lowlatency x86_64
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.19.1-0ubuntu3
>   Architecture: amd64
>   CompizPlugins:
> [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Mon Oct 26 12:42:14 2015
>   DistUpgraded: 2015-10-23 23:59:32,729 DEBUG enabling apt cron job
>   DistroCodename: wily
>   DistroVariant: ubuntu
>   EcryptfsInUse: Yes
>   ExtraDebuggingInterest: Yes
>   GpuHangFrequency: Several times a day
>   GpuHangReproducibility: Seems to happen randomly
>   GpuHangStarted: Since before I upgraded
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360]
> [1002:6658] (prog-if 00 [VGA controller])
>  Subsystem: XFX Pine Group Inc. Device [1682:7260]
>   InstallationDate: Installed on 2014-11-21 

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

[Johannes Merkert]

apport information

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

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
  [2.658922] 

[Desktop-packages] [Bug 1510970] UdevLog.txt

[Johannes Merkert]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1510970/+attachment/4508547/+files/UdevLog.txt

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
  [2.658922] systemd[1]: 

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

[Johannes Merkert]

apport information

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

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
  [2.658922] systemd[1]: 

[Desktop-packages] [Bug 1510970] xserver.devices.txt

[Johannes Merkert]

apport information

** Attachment added: "xserver.devices.txt"
   
https://bugs.launchpad.net/bugs/1510970/+attachment/4508553/+files/xserver.devices.txt

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
  [2.658922] 

[Desktop-packages] [Bug 1510970] XorgLog.txt

[Johannes Merkert]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1510970/+attachment/4508549/+files/XorgLog.txt

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
  [2.658922] systemd[1]: 

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

[Johannes Merkert]

apport information

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

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
  [2.658922] 

[Desktop-packages] [Bug 1510970] xdpyinfo.txt

[Johannes Merkert]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1510970/+attachment/4508552/+files/xdpyinfo.txt

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
  [2.658922] systemd[1]: 

[Desktop-packages] [Bug 1510970] LightdmLog.txt

[Johannes Merkert]

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1510970/+attachment/4508538/+files/LightdmLog.txt

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
  [2.658922] 

[Desktop-packages] [Bug 1510970] LightdmGreeterLog.txt

[Johannes Merkert]

apport information

** Attachment added: "LightdmGreeterLog.txt"
   
https://bugs.launchpad.net/bugs/1510970/+attachment/4508536/+files/LightdmGreeterLog.txt

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
  [

[Desktop-packages] [Bug 1510970] XorgLogOld.txt

[Johannes Merkert]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1510970/+attachment/4508550/+files/XorgLogOld.txt

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS 
+ACL +XZ -LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
  [2.658922]