[Desktop-packages] [Bug 1973306] [NEW] packages freezes on authentification with Wayland

[Johan Van Hoorde]

Public bug reported:

I want to report an issue which might well have been reported already,
although i could not find it. A few weeks ago I switched from Ubuntu LTS
20.04 towards the LTS 22.04 with Wayland as default.

I discovered that there is a sort of incompatibility between the
software-properties-package and the Wayland protocol, which occurs
systematically and never occurs when switching back to Xorg.

When one tries to add or change a rule in ‘other software’ the
application always freezes when the user is asked to authenticate. As
soon a one cancels the authentification procedure it unfreezes almost
immediately, but freezes again when the user retries to complete the
adding or alteration procedure. As said, this error never occurs if the
user switches back to an Xorg session.

See screenshot: the window with the communication 'software & updates
does not respond' and with the choice to close or to wait is hidden
behind the authentification window.

I am not really sure whether this bug has to be reported as a security
issue, but certainly the software-properties-package is of utmost
importance for a stable and secure OS.

My system:

OS: Ubuntu 22.04 LTS x86_64 
Kernel: 5.15.0-30-generic 
Uptime: 13 mins 
Packages: 1940 (dpkg), 17 (flatpak),
Shell: bash 5.1.16 
Resolution: 1920x1080 
DE: GNOME 42.0 
WM: Mutter 
WM Theme: Adwaita 
Theme: Adwaita [GTK2/3] 
Icons: Numix [GTK2/3] 
Terminal: gnome-terminal 
CPU: Intel i7-10510U (8) @ 4.900GHz 
GPU: Intel CometLake-U GT2 [UHD Grap
Memory: 2992MiB / 64007MiB

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

** Attachment added: "Software_freeze1.png"
   
https://bugs.launchpad.net/bugs/1973306/+attachment/5589516/+files/Software_freeze1.png

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

Title:
  packages freezes on authentification with Wayland

Status in software-properties package in Ubuntu:
  New

Bug description:
  I want to report an issue which might well have been reported already,
  although i could not find it. A few weeks ago I switched from Ubuntu
  LTS 20.04 towards the LTS 22.04 with Wayland as default.

  I discovered that there is a sort of incompatibility between the
  software-properties-package and the Wayland protocol, which occurs
  systematically and never occurs when switching back to Xorg.

  When one tries to add or change a rule in ‘other software’ the
  application always freezes when the user is asked to authenticate. As
  soon a one cancels the authentification procedure it unfreezes almost
  immediately, but freezes again when the user retries to complete the
  adding or alteration procedure. As said, this error never occurs if
  the user switches back to an Xorg session.

  See screenshot: the window with the communication 'software & updates
  does not respond' and with the choice to close or to wait is hidden
  behind the authentification window.

  I am not really sure whether this bug has to be reported as a security
  issue, but certainly the software-properties-package is of utmost
  importance for a stable and secure OS.

  My system:

  OS: Ubuntu 22.04 LTS x86_64 
  Kernel: 5.15.0-30-generic 
  Uptime: 13 mins 
  Packages: 1940 (dpkg), 17 (flatpak),
  Shell: bash 5.1.16 
  Resolution: 1920x1080 
  DE: GNOME 42.0 
  WM: Mutter 
  WM Theme: Adwaita 
  Theme: Adwaita [GTK2/3] 
  Icons: Numix [GTK2/3] 
  Terminal: gnome-terminal 
  CPU: Intel i7-10510U (8) @ 4.900GHz 
  GPU: Intel CometLake-U GT2 [UHD Grap
  Memory: 2992MiB / 64007MiB

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


-- 
Mailing list: https://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 1946525] Re: Removable media are not mounted automatically

[Johan Tol]

** Description changed:

  1) Ubuntu Desktop amd 64 20211008.1 daily build
- 2) udisks 2.9.4-1 
+ 2) udisks 2.9.4-1
  3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions 
disk images, should be mounted automatically
  4) the automount feature seems to be gone or non-functional in the last 
couple of days
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: udisks2 2.9.4-1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 
60-vboxadd.rules 70-snap.snap-store.rules
  Date: Sat Oct  9 01:37:13 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1)
  Lsusb:
-  Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
-  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
-  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
-  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash
  SourcePackage: udisks2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

Title:
  Removable media are not mounted automatically

Status in udisks2 package in Ubuntu:
  Confirmed

Bug description:
  1) Ubuntu Desktop amd 64 20211008.1 daily build
  2) udisks 2.9.4-1
  3) Inserted disks, in this case the Ubuntu and VirtualBox Guest Additions 
disk images, should be mounted automatically
  4) the automount feature seems to be gone or non-functional in the last 
couple of days

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: udisks2 2.9.4-1
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.firefox.rules 70-snap.core.rules 
60-vboxadd.rules 70-snap.snap-store.rules
  Date: Sat Oct  9 01:37:13 2021
  InstallationDate: Installed on 2021-10-08 (0 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211008.1)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic 
root=UUID=d07fdf87-8838-4ac4-889b-0ae8cdf3ebb5 ro quiet splash
  SourcePackage: udisks2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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


-- 
Mailing list: https://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 1923050] [NEW] Cannot resume from suspend

[Johan Larsson]

Public bug reported:

I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither
pushing the power button or opening the lid solves the issue. The led
indicator continues to pulsate and there's no indication of any response
from the computer.

I've tried switching between versions 450 and 460 of the Nvidia graphics
driver as well as Noveau and the issues persists regardless of which
driver I use.

This started happening no too long ago, maybe around a month from now.
It previously worked just fine.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-power-manager 3.32.0-2
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  8 14:54:05 2021
SourcePackage: gnome-power-manager
UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago)

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


** Tags: amd64 apport-bug groovy lenovo power

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

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

** Description changed:

  I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither
- pushing the power button or opening the lid solves the issue. I've tried
- switching between versions 450 and 460 of the Nvidia graphics driver as
- well as Noveau and the issues persists regardless of which driver I use.
+ pushing the power button or opening the lid solves the issue. The led
+ indicator continues to pulsate and there's no indication of any response
+ from the computer.
+ 
+ I've tried switching between versions 450 and 460 of the Nvidia graphics
+ driver as well as Noveau and the issues persists regardless of which
+ driver I use.
  
  This started happening no too long ago, maybe around a month from now.
  It previously worked just fine.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-power-manager 3.32.0-2
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  8 14:54:05 2021
  SourcePackage: gnome-power-manager
  UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago)

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

Title:
  Cannot resume from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38.
  Neither pushing the power button or opening the lid solves the issue.
  The led indicator continues to pulsate and there's no indication of
  any response from the computer.

  I've tried switching between versions 450 and 460 of the Nvidia
  graphics driver as well as Noveau and the issues persists regardless
  of which driver I use.

  This started happening no too long ago, maybe around a month from now.
  It previously worked just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-power-manager 3.32.0-2
  ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  8 14:54:05 2021
  SourcePackage: gnome-power-manager
  UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago)

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

-- 
Mailing list: https://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 1841826] Re: Going to sleep instead of logging in while lid closed & external display

[Johan Larsson]

No, Tim, it's connected via display port. I don't have any logitech gear
and disabling autostart for Dropbox does not help.

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

Title:
  Going to sleep instead of logging in while lid closed & external
  display

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have the above described problem, which seems to be very similar to
  bug #1716160

  - laptop is in docking station and 2 monitors are connected (HDMI,
  DVI)

  - If the lid is closed and I boot the laptop I can input my
  credentials in the login screen and after hitting ENTER the laptop
  goes to sleep

  - If I then press the power button of the docking station the laptop
  wakes up and goes straight to the ubuntu environment w/o any user
  identification

  The device is a Lenovo T420 with classic docking station. Ubuntu
  18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated
  Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior
  independent of the graphics used.

  I do not know what to do now since the latest state of bug #1716160 is
  "fix released" and so I guess it should be part of the ubuntu version
  I use?

  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 20:10:15 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-08-13 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1841826] Re: Going to sleep instead of logging in while lid closed & external display

[Johan Larsson]

I have this problem as well on ubuntu 20.10 on a Thinkpad T14 with
integrated Geforce MX330 graphics. My laptop is closed and docked via a
thunderbolt 3 dock to a single external monitor.

I have tried the fix proposed here:
https://askubuntu.com/questions/1083720/ubuntu-goes-suspended-after-
login-if-lid-is-closed/1239573#1239573 to no avail.

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

Title:
  Going to sleep instead of logging in while lid closed & external
  display

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I have the above described problem, which seems to be very similar to
  bug #1716160

  - laptop is in docking station and 2 monitors are connected (HDMI,
  DVI)

  - If the lid is closed and I boot the laptop I can input my
  credentials in the login screen and after hitting ENTER the laptop
  goes to sleep

  - If I then press the power button of the docking station the laptop
  wakes up and goes straight to the ubuntu environment w/o any user
  identification

  The device is a Lenovo T420 with classic docking station. Ubuntu
  18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated
  Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior
  independent of the graphics used.

  I do not know what to do now since the latest state of bug #1716160 is
  "fix released" and so I guess it should be part of the ubuntu version
  I use?

  Thank you very much.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.4-0ubuntu18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 20:10:15 2019
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'show-battery-percentage' b'true'
   b'org.gnome.desktop.interface' b'clock-show-date' b'true'
  InstallationDate: Installed on 2019-08-13 (14 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1904789] Re: [snap] Cannot confirm security exception for invalid certificate

[Johan]

I understand that it's particularly difficult to reproduce the bug
because it requires a mail server with a certificate problem. Since it
was blocking me, I temporarily dealt with this by not using the Snap
version of TB and returning to the versions from the official Ubuntu PPA
(in my case TB 68.10.0 on my Ubuntu 20.04.1 LTS machine and TB 78.3.2 on
my Ubuntu 20.10 machine) which are not affected by this issue. That's
why I tagged it as Snap-specific.

Today, I've finally found a solution to the certificate problem on my
email server (which of course was the goal all along) so I returned to
the Snap version on my Ubuntu LTS machine (to be able to use the most
recent version of TB). Now, the "Add Security Exception" window is not
blocking my anymore.

Sorry I can't bring more help to solve this problem but I hope this will
help others to deal with it.

So, I don't think we should close this ticket because bypassing the
security warning is still a useful temporary solution for end users
which shouldn't be blamed for servers problems that can sometimes occur
but as far as I'm concerned I can now move on.

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

Title:
  [snap] Cannot confirm security exception for invalid certificate

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Note: This bug is specific to the Snap version of Thunderbird, I can't
  reproduce it with the Ubuntu-packaged version for example (which I
  have installed on Ubuntu, used for multiple years and stopped using
  recently to get the more recent versions of TB available with Snap).

  When a certificate problem arrises with a server from which
  Thunderbird tries to retrieve emails, the "Add Security Exception"
  window gives you the option to "Confirm Security Exception" (meaning
  that Thunderbird will overlook the invalid certificate).

  The problem is that nothing happens when I click the "Confirm Security
  Exception" button. I've tried the usual workarounds, including
  removing the email account and adding it again, to no avail.

  The peculiar thing here is that I have had certificate problems
  before, when using a non-snap version of Thunderbird, and clicking the
  "Confirm Security Exception" button has always worked. Not with the
  Snap version it seems.

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

-- 
Mailing list: https://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 1904789] Re: [snap] Cannot confirm security exception for invalid certificate

[Johan]

Looking at the Error Console was the right idea, thanks. Here's the
error that is caught when clicking the "Confirm Security Exception"
button:

Exception { name: "NS_ERROR_FAILURE", message: "Component returned
failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIURI.port]", result:
2147500037, filename: "chrome://pippki/content/exceptionDialog.js",
lineNumber: 156, columnNumber: 0, data: null, stack:
"getURI@chrome://pippki/content/exceptionDialog.js:156:7\naddException@chrome://pippki/content/exceptionDialog.js:386:13\n_fireButtonEvent@chrome://global/content/elements/dialog.js:487:19\n_doButtonCommand@chrome://global/content/elements/dialog.js:466:29\n_handleButtonCommand@chrome://global/content/elements/dialog.js:460:19\nInformUserOfCertError@chrome://messenger/content/mailWindow.js:685:10\nOnStopRunningUrl@chrome://messenger/content/mailWindowOverlay.js:2938:30\n",
location: XPCWrappedNative_NoHelper }

The previous

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

Title:
  [snap] Cannot confirm security exception for invalid certificate

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Note: This bug is specific to the Snap version of Thunderbird, I can't
  reproduce it with the Ubuntu-packaged version for example (which I
  have installed on Ubuntu, used for multiple years and stopped using
  recently to get the more recent versions of TB available with Snap).

  When a certificate problem arrises with a server from which
  Thunderbird tries to retrieve emails, the "Add Security Exception"
  window gives you the option to "Confirm Security Exception" (meaning
  that Thunderbird will overlook the invalid certificate).

  The problem is that nothing happens when I click the "Confirm Security
  Exception" button. I've tried the usual workarounds, including
  removing the email account and adding it again, to no avail.

  The peculiar thing here is that I have had certificate problems
  before, when using a non-snap version of Thunderbird, and clicking the
  "Confirm Security Exception" button has always worked. Not with the
  Snap version it seems.

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

-- 
Mailing list: https://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 1904789] Re: [snap] Cannot confirm security exception for invalid certificate

[Johan]

By "nothing happens" I mean that the "Add Security Exception" window
stays open with seemingly no effect when clicking on the button "Confirm
Security Exception". Clicking multiple times doesn't change the state of
the window either. The only way to advance is to click "Cancel" which
closes the window (without adding the exception of course).

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

Title:
  [snap] Cannot confirm security exception for invalid certificate

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Note: This bug is specific to the Snap version of Thunderbird, I can't
  reproduce it with the Ubuntu-packaged version for example (which I
  have installed on Ubuntu, used for multiple years and stopped using
  recently to get the more recent versions of TB available with Snap).

  When a certificate problem arrises with a server from which
  Thunderbird tries to retrieve emails, the "Add Security Exception"
  window gives you the option to "Confirm Security Exception" (meaning
  that Thunderbird will overlook the invalid certificate).

  The problem is that nothing happens when I click the "Confirm Security
  Exception" button. I've tried the usual workarounds, including
  removing the email account and adding it again, to no avail.

  The peculiar thing here is that I have had certificate problems
  before, when using a non-snap version of Thunderbird, and clicking the
  "Confirm Security Exception" button has always worked. Not with the
  Snap version it seems.

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

-- 
Mailing list: https://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 1904789] Re: [snap] Cannot confirm security exception

[Johan]

Hi Olivier, thanks for your help.

snap run thunderbird
Gtk-Message: 11:39:31.230: Failed to load module "canberra-gtk-module"
Gtk-Message: 11:39:31.248: Failed to load module "canberra-gtk-module"

(directly at launch, then nothing when reproducing the issue)

Nothing either with journalctl -f | grep DEN.

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

Title:
  [snap] Cannot confirm security exception

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Note: This bug is specific to the Snap version of Thunderbird, I can't
  reproduce it with the Ubuntu-packaged version for example (which I
  have installed on Ubuntu, used for multiple years and stopped using
  recently to get the more recent versions of TB available with Snap).

  When a certificate problem arrises with a server from which
  Thunderbird tries to retrieve emails, the "Add Security Exception"
  window gives you the option to "Confirm Security Exception" (meaning
  that Thunderbird will overlook the invalid certificate).

  The problem is that nothing happens when I click the "Confirm Security
  Exception" button. I've tried the usual workarounds, including
  removing the email account and adding it again, to no avail.

  The peculiar thing here is that I have had certificate problems
  before, when using a non-snap version of Thunderbird, and clicking the
  "Confirm Security Exception" button has always worked. Not with the
  Snap version it seems.

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

-- 
Mailing list: https://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 1904789] [NEW] [snap] Cannot confirm security exception

[Johan]

Public bug reported:

Note: This bug is specific to the Snap version of Thunderbird, I can't
reproduce it with the Ubuntu-packaged version for example (which I have
installed on Ubuntu, used for multiple years and stopped using recently
to get the more recent versions of TB available with Snap).

When a certificate problem arrises with a server from which Thunderbird
tries to retrieve emails, the "Add Security Exception" window gives you
the option to "Confirm Security Exception" (meaning that Thunderbird
will overlook the invalid certificate).

The problem is that nothing happens when I click the "Confirm Security
Exception" button. I've tried the usual workarounds, including removing
the email account and adding it again, to no avail.

The peculiar thing here is that I have had certificate problems before,
when using a non-snap version of Thunderbird, and clicking the "Confirm
Security Exception" button has always worked. Not with the Snap version
it seems.

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

Title:
  [snap] Cannot confirm security exception

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Note: This bug is specific to the Snap version of Thunderbird, I can't
  reproduce it with the Ubuntu-packaged version for example (which I
  have installed on Ubuntu, used for multiple years and stopped using
  recently to get the more recent versions of TB available with Snap).

  When a certificate problem arrises with a server from which
  Thunderbird tries to retrieve emails, the "Add Security Exception"
  window gives you the option to "Confirm Security Exception" (meaning
  that Thunderbird will overlook the invalid certificate).

  The problem is that nothing happens when I click the "Confirm Security
  Exception" button. I've tried the usual workarounds, including
  removing the email account and adding it again, to no avail.

  The peculiar thing here is that I have had certificate problems
  before, when using a non-snap version of Thunderbird, and clicking the
  "Confirm Security Exception" button has always worked. Not with the
  Snap version it seems.

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

-- 
Mailing list: https://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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Johan Segerstedt]

The testing package of libasound2 built by @hui.wang has resolved the
issue for me as well. Thank you!

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

Title:
  [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After logging in, only a dummy device is available for audio playback
  (resulting in no audible playback). When running "pactl load-module
  module-detect" the sound card shows up, and playback works as
  expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UDCTO1WW
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Johan Segerstedt]

I have reported the issue upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030

** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1030
   https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1030

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

Title:
  [Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After logging in, only a dummy device is available for audio playback
  (resulting in no audible playback). When running "pactl load-module
  module-detect" the sound card shows up, and playback works as
  expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UDCTO1WW
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1901922] [NEW] No sound output device on startup

[Johan Segerstedt]

Public bug reported:

After logging in, only a dummy device is available for audio playback
(resulting in no audible playback). When running "pactl load-module
module-detect" the sound card shows up, and playback works as expected.

If pulseaudio is restarted with "pulseaudio -k" the playback device
disappears again. Running the above command get things working again.

If I change the following section in /etc/pulse/default.pa from:

### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
### Use the static hardware detection module (for systems that lack udev 
support)
load-module module-detect
.endif

To:

### Automatically load driver modules depending on the hardware available
#.ifexists module-udev-detect.so
#load-module module-udev-detect
#.else
### Use the static hardware detection module (for systems that lack udev 
support)
load-module module-detect
#.endif

Things start working as they should after running "pulseaudio -k".

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Oct 28 17:21:02 2020
InstallationDate: Installed on 2020-10-23 (4 days ago)
InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2020
dmi.bios.release: 1.9
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET40W(1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UDCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.9
dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UDCTO1WW
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug groovy

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

Title:
  No sound output device on startup

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After logging in, only a dummy device is available for audio playback
  (resulting in no audible playback). When running "pactl load-module
  module-detect" the sound card shows up, and playback works as
  expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UDCTO1WW
  dmi.product.sku: 

[Desktop-packages] [Bug 1868392] Re: Touchscreen not working in 5.3.0-42

[Johan]

Forgot to say, the bug report was done with kernel 5.3.0-40 with a
working touch screen.

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

Title:
  Touchscreen not working in 5.3.0-42

Status in xorg package in Ubuntu:
  New

Bug description:
  My Asus Zenbook touch screen works in 5.3.0-40, but stops working when
  I boot into the 5.3.0-42 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Mar 21 17:52:19 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-40-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13ff]
 Subsystem: ASUSTeK Computer Inc. GP108BM [GeForce MX250] [1043:13ff]
  InstallationDate: Installed on 2020-02-11 (38 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX481FL_UX481FL
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=af_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=c157ba74-8933-4447-9f11-e965279079be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX481FL.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX481FL
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX481FL.206:bd08/06/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX481FL_UX481FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX481FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX481FL_UX481FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://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 1868392] [NEW] Touchscreen not working in 5.3.0-42

[Johan]

Public bug reported:

My Asus Zenbook touch screen works in 5.3.0-40, but stops working when I
boot into the 5.3.0-42 kernel.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
Uname: Linux 5.3.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
ApportVersion: 2.20.11-0ubuntu8.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sat Mar 21 17:52:19 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.3.0-40-generic, x86_64: installed
 nvidia, 435.21, 5.3.0-42-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed
 virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:13ff]
   Subsystem: ASUSTeK Computer Inc. GP108BM [GeForce MX250] [1043:13ff]
InstallationDate: Installed on 2020-02-11 (38 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 004: ID 8087:0026 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. ZenBook UX481FL_UX481FL
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=af_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=c157ba74-8933-4447-9f11-e965279079be ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX481FL.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX481FL
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX481FL.206:bd08/06/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX481FL_UX481FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX481FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX481FL_UX481FL
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan kubuntu 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/1868392

Title:
  Touchscreen not working in 5.3.0-42

Status in xorg package in Ubuntu:
  New

Bug description:
  My Asus Zenbook touch screen works in 5.3.0-40, but stops working when
  I boot into the 5.3.0-42 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  

[Desktop-packages] [Bug 1834493] Re: Update mutter to 3.32.2+git20190711

[Johan Lindquist]

Any idea when the 3.32.2+git20190711 build will be in proposed?  Thanks,
Johan

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

Title:
  Update mutter to 3.32.2+git20190711

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Disco:
  In Progress

Bug description:
  [ Description ]

  The second stable release in the 3.32 series, plus commits on the 3.32
  stable branch from upstream.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Crash and memory fixes that should be safe, but also focus changes
  that might affect the focusing of some particular apps.

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

-- 
Mailing list: https://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 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

[Johan Bengtsson]

The slowness might have caused by some apparmor probs:
pr 11 15:16:58 zander kernel: [13422.621558] audit: type=1400 
audit(1554988618.771:27): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=13888 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:20:43 zander kernel: [13647.282091] audit: type=1400 
audit(1554988843.431:28): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=20908 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:25:43 zander kernel: [13947.374877] audit: type=1400 
audit(1554989143.520:29): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=27940 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:28:24 zander kernel: [14108.309867] audit: type=1400 
audit(1554989304.459:30): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=424 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:28:46 zander kernel: [14130.333125] audit: type=1400 
audit(1554989326.483:31): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=1116 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:00 zander kernel: [14984.432581] audit: type=1400 
audit(1554990180.581:32): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26456 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:03 zander kernel: [14987.725323] audit: type=1400 
audit(1554990183.873:33): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26546 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:05 zander kernel: [14989.287668] audit: type=1400 
audit(1554990185.433:34): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26584 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:43:06 zander kernel: [14990.386287] audit: type=1400 
audit(1554990186.533:35): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=26610 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:54:37 zander dbus-daemon[859]: [system] Activating service 
name='org.opensuse.CupsPkHelper.Mechanism' requested by ':1.167' (uid=1000 
pid=14054 comm="/usr/bin/python3 /usr/share/system-config-printer/" 
label="unconfined") (using servicehelper)
Apr 11 15:54:37 zander dbus-daemon[859]: [system] Successfully activated 
service 'org.opensuse.CupsPkHelper.Mechanism'
Apr 11 15:55:43 zander kernel: [15747.355081] audit: type=1400 
audit(1554990943.501:36): apparmor="DENIED" operation="open" 
profile="/usr/sbin/cupsd" name="/etc/gss/mech.d/" pid=15434 comm="ipp" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Apr 11 15:58:20 zander kernel: [15904.185434] audit: type=1400 
audit(1554991100.336:37): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=21257 
comm="apparmor_parser"
Apr 11 15:58:20 zander kernel: [15904.185716] audit: type=1400 
audit(1554991100.336:38): apparmor="STATUS" operation="profile_remove" 
profile="unconfined" name="/usr/sbin/cupsd" pid=21257 comm="apparmor_parser"

Did aa-disable cupsd and it seems faster.

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 

[Desktop-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

[Johan Bengtsson]

I have a situation that is similar but not with a windows server.

I have an experimental server which is installed with Ubuntu Disco.
Queues are authenticated with kerberos. This is IPP-Everywhere queues.

I have a client with Ubuntu 18.04.2 LTS.

Printing did not work with cups-2.2.7-1ubuntu2.4 on the client. Same
symptoms as described here, cannot print, authentication prompt despite
valid kerberos tickets.

I compiled upstream cups 2.2.7 with Eskos fix-password-prompt.patch AND
the kerberos truncate patch from #13 and installed it on the client.

It works, but printing is very slow, at least from firefox.

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
  seems to be acting more like AuthInfoRequired username,password i.e.
  it prompts for a password when printing rather than using the
  available Kerberos credentials.

  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:

  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
  -o printer-error-policy=abort-job -o auth-info-required=negotiate -m
  "CIS/hp-officejet_pro_476_576_series-ps.ppd"

  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
  as it's blocked by default) and the permissions on this file changed
  to 700 (owner root) as per manpage instructions.

  When using lp -d printer /tmp/test.txt I get the following response:

  Password for myuid on localhost?

  Typing my password gets the job accepted to the queue but it does
  spool to the Windows Print Server and in the error_log file I can see

  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)

  Any ideas how to fix this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Desktop-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

[Johan Bengtsson]

Is this fix available in Disco?

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
  seems to be acting more like AuthInfoRequired username,password i.e.
  it prompts for a password when printing rather than using the
  available Kerberos credentials.

  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:

  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
  -o printer-error-policy=abort-job -o auth-info-required=negotiate -m
  "CIS/hp-officejet_pro_476_576_series-ps.ppd"

  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
  as it's blocked by default) and the permissions on this file changed
  to 700 (owner root) as per manpage instructions.

  When using lp -d printer /tmp/test.txt I get the following response:

  Password for myuid on localhost?

  Typing my password gets the job accepted to the queue but it does
  spool to the Windows Print Server and in the error_log file I can see

  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)

  Any ideas how to fix this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 376715]

[Johan Andersson]

I've been searching like crazy for a native "minimize to tray" function
in TB 60, since the last version of 'MinimizeToTray' is deprecated - but
i soon realized that there's no such function added.

So if there's someone that got the time (and the will ofc) and knowledge
that could port https://github.com/foudfou/FireTray - i would be very
happy, and i guess a lot of other ppl would be too!

I'm sorry for the echo, but i felt the thread needed a "bump".

Best regards, meffe

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

Title:
  Thunderbird - feature request - nest in toolbar

Status in Mozilla Thunderbird:
  Won't Fix
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: mozilla-thunderbird

  Thunderbird should nest in the toolbar. Instead I keep quitting and
  having to restart the application. So the email reporting feature
  doesn't work etc. This feature is common in Amarok and Transmission
  Bit-Torrent. I am using Hardy 8.04

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

-- 
Mailing list: https://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 1590661] Re: Unable to unlock: "Time has expired"

[johan kristenson]

any update?
i have it on ubuntu 18.04.1

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

Title:
  Unable to unlock: "Time has expired"

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  Sometimes when coming back after locking the screen I am unable to
  unlock. The login box on the screen has a disabled password input
  field with the buttons also disabled.

  Except for the mouse, the entire screen is frozen. Even the time in
  the top of the screen stops going. The only way to continue is to move
  to a tty (Ctrl-Alt-F1), log in and kill gnome-screensaver.

  Since the time also stops going I have deduced that this seems to
  happen on days and times that correspond to when the cleaners are
  here. Because of this I speculate that they accidentally press some
  keys, including the enter key. This of course fails to unlock and
  after a certain timeout it then proceeds to freeze.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-screensaver 3.6.1-7ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jun  9 08:59:15 2016
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session session-name 'ubuntu'
   org.gnome.desktop.session idle-delay uint32 300
  InstallationDate: Installed on 2016-05-27 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1777654] Re: openvpn connection with secret is broken

[Johan Smits]

I also opened an issue at Debian: 
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/7
On debian the same issue occurs.

Your also not able to save your vpn config?

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

Title:
  openvpn connection with secret is broken

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

Bug description:
  when connecting an openvpn 2.4 server via ovpn configuration with a
  secret, journalctl shows this:

  gnome-shell[5063]: JS ERROR: error while reading VPN plugin output keyfile: 
GLib.KeyFileError: Key file does not have key “Title” in group “VPN Plugin UI”
   
_showNewStyleDialog@resource:///org/gnome/shell/ui/components/networkAgent.js:515:40
   
wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
   
_readStdoutNewStyle/<@resource:///org/gnome/shell/ui/components/networkAgent.js:489:17
  2018-06-19 15:39:44 example.com NetworkManager[966]:  
[1529415584.4116] 
vpn-connection[0x560e3577e840,b65547a8-8a347-1c21-c747-5296902abc6e,"Notebook",0]:
 Failed to request VPN secrets #3: No agents were available for this request.
  2018-06-19 15:39:44 example.com NetworkManager[966]:   
[1529415584.4126] 
vpn-connection[0x560e3577e840,b65547a8-8a347-1c21-c747-5296902abc6e,"Notebook",0]:
 VPN plugin: state changed: stopped (6)
  2018-06-19 15:39:44 example.com NetworkManager[966]:   
[1529415584.4131] 
vpn-connection[0x560e3577e840,b65547a8-8a347-1c21-c747-5296902abc6e,"Notebook",0]:
 VPN service disappeared

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager-openvpn 1.8.2-1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 19 15:33:29 2018
  InstallationDate: Installed on 2018-06-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: network-manager-openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Johan Marius Wesselink]

Tested the scilab 5.5.2 for ubuntu which works great. 
However, I did not test it before applying the jogl2 patch :-o.  

Had a look at the source and it seems that the Ubuntu version is patched to use 
the
generic version of jogl2. 

I would like to try and get this patch integrated in the Scilab source tree. 
Probably a difficult and slow process.

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Committed
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

  [Test case]
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped
   at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
   at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
   at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
   at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
   at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
   at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
   at org.scilab.modules.gui.SwingView.(Unknown Source)
   at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
   at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

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

-- 
Mailing list: https://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 1742894] Re: Scilab does not start after some upgrades on Ubuntu Xenial

[Johan Marius Wesselink]

I tested the proposed package on Lubuntu 17.10.

I tested some example programs they use either:
GLProfile glp = GLProfile.getDefault();
Or they use the GLCanvas default constructor.

Before this version all these examples emitted the typical error found
in the previous version of jogl2. The new package RESOLVED this problem.

I noticed after some experimenting that replacing getDefault with 
get(GLProfile.GL2);
also solved the problem. Then I found this thread.

I build scilab from source using the git repository. This is the master
and future 6.1 version it has the same problem. However, scilab 6 and
higher have the jogl2 library prebuild and distributed as a thirdparty
library. Removing this library doesn't work. The problem is that the
scirender module and the gui modules depend on the old syntax. The Java
path in the past was javax.media. In newer version of jogl2 this changed
to com.jogamp. This means that besides removing the faulty library from
scilab the modules scirender and gui need to be patched. I did just this
in the last days. The git master branch version 6.1 build and works with
the new jogl2 version. I noticed however one regression bug the cursor
selection in the plot window work kind of inverted. This is an old bug
which I have seen before.

So, yes this fixes the jogl2 bug. But, no likely not the scilab bug.
Depends how you get scilab and which version probably.

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

Title:
  Scilab does not start after some upgrades on Ubuntu Xenial

Status in Mesa:
  Confirmed
Status in libjogl2-java package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Invalid
Status in scilab package in Ubuntu:
  Invalid
Status in libjogl2-java source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Invalid
Status in scilab source package in Xenial:
  Invalid
Status in libjogl2-java source package in Artful:
  Fix Committed
Status in mesa source package in Artful:
  Invalid
Status in scilab source package in Artful:
  Invalid
Status in scilab package in Debian:
  Fix Released

Bug description:
  [Impact]

  Software that use libjogl2-java (Scilab, Matlab,...) fail to run,
  because Mesa dropped 'Gallium' from the renderer string.

  [Test case]
  Steps to reproduce:
  1. have installed Scilab on Ubuntu Xenial system
  2. install system updates
  3. try to launch Scilab from GUI - it does not start
  4. try to launch Scilab from terminal - it does not start with the following 
output in the terminal:

  $ scilab
  Could not create a Scilab main class. Error:
  Exception in thread "main" java.lang.InternalError: XXX0 profile[1]: GL3bc -> 
profileImpl GL4bc !!! not mapped
   at com.jogamp.opengl.GLProfile.computeProfileMap(GLProfile.java:2071)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDeviceCritical(GLProfile.java:1954)
   at com.jogamp.opengl.GLProfile.initProfilesForDevice(GLProfile.java:1875)
   at 
com.jogamp.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1842)
   at com.jogamp.opengl.GLProfile.access$000(GLProfile.java:80)
   at com.jogamp.opengl.GLProfile$1.run(GLProfile.java:230)
   at java.security.AccessController.doPrivileged(Native Method)
   at com.jogamp.opengl.GLProfile.initSingleton(GLProfile.java:216)
   at com.jogamp.opengl.GLProfile.getProfileMap(GLProfile.java:2297)
   at com.jogamp.opengl.GLProfile.get(GLProfile.java:988)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:722)
   at com.jogamp.opengl.GLProfile.getDefault(GLProfile.java:733)
   at org.scilab.modules.gui.SwingView.(Unknown Source)
   at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source)
   at org.scilab.modules.core.Scilab.(Unknown Source)

  Scilab cannot create Scilab Java Main-Class (we have not been able to
  find the main Scilab class. Check if the Scilab and thirdparty
  packages are available).

  Expected results:
  Scilab works normally on Ubuntu 16.04 LTS system.

  Actual results:
  see error above.

  [Regression potential]
  The fix is a simple oneliner that allows libjogl2-java to detect Mesa with 
both new and original version of Mesa.

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

-- 
Mailing list: https://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 1616332] Re: gnome-software using hundreds of MB of memory when not in use

[Johan Lejonborn]

This happend to me _three_ times in the last week, gnome-software runs
amok and takes up 16GB ram + 16GB Swap and managed to write a
13.7GB-14.3GB syslog. Uninstalled gnome-software while waiting for a
fix.

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

Title:
  gnome-software using hundreds of MB of memory when not in use

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  It seems gnome-software is running in the background all the time. Not
  a big deal if it was lightweight, but it seems to use hundreds of MB
  (from smem output):

PID User Command Swap  USS  PSS  
RSS 
   2291 jan  /usr/bin/gnome-software --g   285436   112576   117982   
134036 

  A total of over 400MB in RAM and swap combined.

  After killing and restarting, it takes "only" a bit over 100MB.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 
3.20.1+git20160617.1.0440874.ubuntu-xenial-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 24 09:45:53 2016
  InstallationDate: Installed on 2012-11-10 (1382 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-06-19 (65 days ago)

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

-- 
Mailing list: https://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 1716579] Re: gnome-software uses a very high cpu amount

[Johan Lejonborn]

This happend to me _three_ times in the last week, gnome-software runs
amok and takes up 16GB ram + 16GB Swap and managed to write a
13.7GB-14.3GB syslog. Couldn't view the syslogs, but there is a comment
in another bug-thread on the same issue with info from syslog:
https://bugs.launchpad.net/ubuntu/+source/gnome-
software/+bug/1616332/comments/12

For now i have uninstalled gnome-software, that fixes the problem...

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

Title:
  gnome-software uses a very high cpu amount

Status in gnome-software package in Ubuntu:
  Confirmed
Status in gnome-software source package in Artful:
  Confirmed

Bug description:
  The room was silent, when the fan of my laptop suddenly started making
  noise. I checked it and it was because of the intense amount of CPU in
  use because of gnome software.

  Gnome Software CPU use was over 60%.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-software 3.25.91-1ubuntu5
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 08:29:01 2017
  InstallationDate: Installed on 2017-08-21 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.25.91-1ubuntu5
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1246272] Re: Keyboard layout changing randomly

[Johan Holmberg]

The issue is present in 17.10 (using GNOME) as well.

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

Title:
  Keyboard layout changing randomly

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps 
changing from pt_br to what I think is en_us.
  It seems random so I don't know what trigger this, but sometimes just 
alt-tabbing is enough to mess with keyboard layout in one of the windows.
  I already removed the en_us from my keyboard sources, double checked the use 
of one source for all windows, and even removed accelerators to switch between 
layouts but none have worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center 1:3.6.3-0ubuntu44
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Wed Oct 30 09:12:48 2013
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2013-05-20 (163 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago)
  usr_lib_gnome-control-center:
   activity-log-manager  0.9.7-0ubuntu4
   deja-dup  27.3.1-0ubuntu1
   gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1
   gnome-control-center-signon   0.1.7~+13.10.20130724.1-0ubuntu1
   gnome-control-center-unity1.3+13.10.20131004-0ubuntu1

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

-- 
Mailing list: https://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 1683145] Re: Mouse pointer speed setting has no effect

[Johan Boule]

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

** This bug has been marked a duplicate of bug 1682193
   Mouse acceleration significantly reduced after upgrade to 17.04

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

Title:
  Mouse pointer speed setting has no effect

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  In Setting, Mouse & Touchpad, changing the Mouse pointer speed has no effect 
after upgrading from 16.10 to 17.04.
  Same with Touchpad pointer speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr 16 16:21:26 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-21 (664 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (0 days ago)

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

-- 
Mailing list: https://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 1393476] Re: xterm freezes

[Johan Blomqvist]

It seems that xterm freezes more frequently when scrolling in larger
files in vim using vertical splits. The effect seems to be present
regardless of using tmux splits or vim splits. The effect is worse for
me when using vim-splits (which always results in laggy scrolling in all
terminals I've tried).

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

Title:
  xterm freezes

Status in xterm package in Ubuntu:
  Confirmed

Bug description:
  i use xterm daily, it freezes maybe a couple times per week.  i
  typically run tmux, so i can just open another xterm, reattach my tmux
  session, and discard the frozen xterm.  wasn't happening in releases
  prior to trusty.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xterm 297-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  Date: Mon Nov 17 10:15:14 2014
  InstallationDate: Installed on 2014-01-30 (290 days ago)
  InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha i386 (20140129)
  SourcePackage: xterm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1683145] Re: Mouse pointer speed setting has no effect

[Johan Boule]

Guilherme, are you sure xinput has no effect at all ?
The effect might not be noticeable unless you try more extreme values. Here the 
range is between -1 and +1, so zero seems to be some average.

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

Title:
  Mouse pointer speed setting has no effect

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  In Setting, Mouse & Touchpad, changing the Mouse pointer speed has no effect 
after upgrading from 16.10 to 17.04.
  Same with Touchpad pointer speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr 16 16:21:26 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-21 (664 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (0 days ago)

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

-- 
Mailing list: https://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 1683145] Re: Mouse pointer speed setting has no effect

[Johan Boule]

Thank you Ivan Larionov for pointing me to this xinput tool, which can
also be used as a simple workaround : you can set the desired
acceleration using "xinput --set-prop   ". To know
the , run "xinput" without arguments and look for your mouse
device, then to know the , run "xinput --list-props " and
look for a property "Accel speed". For example, in my case (see previous
attachment), "xinput --set-prop 11 282 0.2".

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

Title:
  Mouse pointer speed setting has no effect

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  In Setting, Mouse & Touchpad, changing the Mouse pointer speed has no effect 
after upgrading from 16.10 to 17.04.
  Same with Touchpad pointer speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr 16 16:21:26 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-21 (664 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (0 days ago)

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

-- 
Mailing list: https://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 1683145] Re: Mouse pointer speed setting has no effect

[Johan Boule]

I'm adding xinput props details too.

** Attachment added: "xinput_props.txt"
   
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1683145/+attachment/4863607/+files/xinput_props.txt

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

Title:
  Mouse pointer speed setting has no effect

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  In Setting, Mouse & Touchpad, changing the Mouse pointer speed has no effect 
after upgrading from 16.10 to 17.04.
  Same with Touchpad pointer speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr 16 16:21:26 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-21 (664 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (0 days ago)

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

-- 
Mailing list: https://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 1683145] [NEW] Mouse pointer speed setting has no effect

[Johan Boule]

Public bug reported:

In Setting, Mouse & Touchpad, changing the Mouse pointer speed has no effect 
after upgrading from 16.10 to 17.04.
Same with Touchpad pointer speed.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Sun Apr 16 16:21:26 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2015-06-21 (664 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: unity-control-center
UpgradeStatus: Upgraded to zesty on 2017-04-16 (0 days ago)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Mouse pointer speed setting has no effect

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

Bug description:
  In Setting, Mouse & Touchpad, changing the Mouse pointer speed has no effect 
after upgrading from 16.10 to 17.04.
  Same with Touchpad pointer speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun Apr 16 16:21:26 2017
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-06-21 (664 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (0 days ago)

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

-- 
Mailing list: https://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 1662822] Re: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build

[Johan van Dijk]

This is probably a duplicate of  #1365200

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

Title:
  bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build

Status in bbswitch package in Ubuntu:
  Confirmed

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bbswitch-dkms 0.7-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-63-generic
  Date: Wed Feb  8 09:57:03 2017
  InstallationDate: Installed on 2014-06-23 (960 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageVersion: 0.7-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: bbswitch
  Title: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1646574] Re: Mouse cursor invisible or does not move

[Johan Ferner]

I first see this in the installer and that makes installing Ubuntu a 
challenge... 
The cursor does move but is invisible so you can kind of guess where you are 
supposed to click.
After installing the problem is still present.

Hardware is GTX 1080 on a desktop.

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

Title:
  Mouse cursor invisible or does not move

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  When using nouveau driver for my GTX 1070 (mobile) the mouse cursor is fixed 
in left upper corner or sometimes disappear. I actually can click or hover 
everywhere on the screen, I just don't know where the mouse is pointer at the 
moment.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-27-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900rc7-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP104M [GeForce GTX 1070] [10de:1be1] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070] [1558:6a04]
  InstallationDate: Installed on 2016-11-26 (5 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID ffc0:0040  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_67RSRP
  Package: xserver-xorg-video-nouveau 1:1.0.12-2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=a596a1fd-2912-4a20-a48c-6b8a32078b5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Tags:  yakkety ubuntu
  Uname: Linux 4.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd08/24/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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

-- 
Mailing list: https://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 1573052] Re: [packaging] gnome-software provides a broken symlink of /usr/lib/gs-plugins-9/libgs_plugin_xdg_app_reviews.so on Ubuntu 16.04

[johan]

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => johan (johan-ms-7267)

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

Title:
  [packaging] gnome-software provides a broken symlink of /usr/lib/gs-
  plugins-9/libgs_plugin_xdg_app_reviews.so on Ubuntu 16.04

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  ```
  $ file /usr/lib/gs-plugins-9/libgs_plugin_xdg_app_reviews.so
  /usr/lib/gs-plugins-9/libgs_plugin_xdg_app_reviews.so: broken symbolic link 
to libgs_plugin_xdg_app_reviews.so.0.0.0
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  Uname: Linux 4.5.0-buo-ren-vanilla-intel-ivybridge-optimized x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 21 21:44:09 2016
  InstallationDate: Installed on 2016-01-07 (104 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (13 days ago)

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

-- 
Mailing list: https://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 1307593] Re: [H87N-WIFI, Realtek ALC892, Green Headphone Out, Front] No sound at all

[Carl-Johan Kjellander]

This happened to me when installing a new graphics card.

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

Title:
  [H87N-WIFI, Realtek ALC892, Green Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound was ok on 12.04.4 but I've had no sound on my headphones since
  upgrading to 13.10.  Sound works on HDMI to screen.  Have tried to fix
  problem by trying fixes listed in No sound in Ubuntu 13.10 web pages
  but nothing worked for me.

  Ubuntu 13.10 64-bit  Memory 7.7 GiB  CPU intel core i5-4570  Graphics
  Intel Haswell Desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  simon  9189 F pulseaudio
   /dev/snd/controlC0:  simon  9189 F pulseaudio
  Date: Mon Apr 14 16:57:27 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-02 (12 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  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/controlC1:  simon  9189 F pulseaudio
   /dev/snd/controlC0:  simon  9189 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [H87N-WIFI, Realtek ALC892, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87N-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd05/07/2013:svnGigabyteTechnologyCo.,Ltd.:pnH87N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87N-WIFI:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: H87N-WIFI
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

-- 
Mailing list: https://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 1567841] Re: One of my two graphics cards has started to freeze the screen

[Carl-Johan Kjellander]

I have tried the daily-current, and I could not reproduce the bug by
running it for 20 hours, and usually I can trigger the bug within an
hour.

But, I could get the livecd to match my current setup exactly. For one
thing it uses unity and not gnome-shell, and I can't install things
temporarily with apt-get. So I had to use a statically compiled chromium
instead of google chrome.

I have found two ways of triggering the bug, and it is still there on
"Ubuntu 14.04.5 LTS", and that is by letting one of these two links run
for a long time in google chrome.

http://xkcd.com/1663/
 or
https://vicandblood.itch.io/dopesmoker

And it only happens with Chrome and not Firefox.

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

Title:
  One of my two graphics cards has started to freeze the screen

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I run a setup of 2 radeon graphics cards, with 3 screens, in the
  following layout from left to right counting from 0:

  Card 0 Screen 1, Card 1 Screen 0, Card 0 Screen 0 rotated ccw

  I have been running this setup for a year and it has worked fine. This
  monday I updated some packages and did a reboot, and I usually reboot
  just once a month cause I patch my running kernel with uptrack.

  After the reboot I started noticing problems with the second card,
  Card 1 above. With a mean time between failures of about an hour, the
  second card freezes the screen, I usually notice that the mouse
  pointer isn't visible anymore when I move it across from one screen to
  the middle one. For future reference, the window I have on the middle
  screen is a fullscreen emacs window.

  I have tried the following kernels: vmlinuz-3.13.0-77-generic,
  vmlinuz-3.13.0-79-generic, vmlinuz-3.13.0-83-generic

  All have the same problem. And nothing shows up in dmesg when the
  freeze occurs, or in the Xorg.0.log, I made copies from before and
  after a freeze.

  If I move the mouse, that I can't see, onto the middle screen, make
  emacs the active window (again I can't see this), scroll around a bit
  with the arrow keys and take a screenshot, the screenshot shows the
  correctly scrolled window, so the big X buffer is actually correctly
  updated.

  If I CTRL-ALT-L to lock the screens, they all go black, but when you
  press enter only the screens on Card 0 shows the lock screen, the
  middle one again shows frozen emacs.

  CTRL-ALT-F1 shows two text terminals on the outermost screens, in the
  middle, you've guessed it, frozen emacs.

  If I go to the menu and select Switch user, surprise! Now the frozen
  screen is gone and it is a gray login screen with the login menu
  actually on the screen to the right.

  Log back into my still running user, boooh, it again shows the
  same frozen emacs.

  Switch to a completely new user, screen in middle is correct and
  working.

  And lastly if I log out completely from my user and log in again the
  screen is now unfrozen, but I have lots of work and it is really
  really annoying to have to log out 8 times during a day at work.

  I'm gonna try one more ancient kernel just to see if there have been
  some changes to drm or the radeon driver, but I am pretty stumped on
  this one. It all worked fine last week.

  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Linux rymdborje 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,snap,imgpng,regex,animation,place,move,vpswitch,mousepoll,grid,unitymtgrabhandles,expo,workarounds,session,wall,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  8 10:38:17 2016
  DistUpgraded: 2015-03-16 15:26:59,578 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.36, 3.13.0-65-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:03f2]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] 
[1002:6613] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:04bb]
  InstallationDate: Installed on 2012-03-13 

[Desktop-packages] [Bug 1631528] [NEW] Blank screen after grub menu

[Johan Nilsson]

Public bug reported:

After a fresh install of Ubuntu Mate 16.04.1 on my laptop I have some
problems booting. After the grub menu the screen goes blank and nothing
happens after that. I think the system is booting properly apart from
the screen not showing anything, I can change the volume using the
hardware keys and I can connect with SSH from another machine. I've
found two workarounds for this problem.

1) Select recovery mode from the grub meny and then resume normal boot,
however, the screen resolution is not set properly.

2) Change my grub config file to boot into text mode. I commented out the line
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
and changed
GRUB_CMDLINE_LINUX=""
to
GRUB_CMDLINE_LINUX=”text"
and uncommented the line
#GRUB_TERMINAL=console

After running sudo update-grub and rebooting the system boots into MATE
and the correct screen resolution is set.

I've collected dmesg after a "blank screen" boot, let me know if there
is anything else I should provide.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: MATE
Date: Fri Oct  7 22:41:04 2016
InstallationDate: Installed on 2016-10-06 (1 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug freeze xenial

** Attachment added: "dmesg.txt"
   https://bugs.launchpad.net/bugs/1631528/+attachment/4757005/+files/dmesg.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/1631528

Title:
  Blank screen after grub menu

Status in xorg package in Ubuntu:
  New

Bug description:
  After a fresh install of Ubuntu Mate 16.04.1 on my laptop I have some
  problems booting. After the grub menu the screen goes blank and
  nothing happens after that. I think the system is booting properly
  apart from the screen not showing anything, I can change the volume
  using the hardware keys and I can connect with SSH from another
  machine. I've found two workarounds for this problem.

  1) Select recovery mode from the grub meny and then resume normal
  boot, however, the screen resolution is not set properly.

  2) Change my grub config file to boot into text mode. I commented out the line
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  and changed
  GRUB_CMDLINE_LINUX=""
  to
  GRUB_CMDLINE_LINUX=”text"
  and uncommented the line
  #GRUB_TERMINAL=console

  After running sudo update-grub and rebooting the system boots into
  MATE and the correct screen resolution is set.

  I've collected dmesg after a "blank screen" boot, let me know if there
  is anything else I should provide.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Oct  7 22:41:04 2016
  InstallationDate: Installed on 2016-10-06 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1617919] [NEW] mdadm segfault error 4 in libc-2.23.so

[Johan Ehnberg]

Public bug reported:

On Ubuntu 16.04.1 LTS Xenial, mdadm segfaults every day on two machines.
Everything works as normal though, and the RAID arrays are not degraded.

[3712474.763430] mdadm[17665]: segfault at 0 ip 7fd0369bed16 sp 
7fff8c5c9478 error 4 in libc-2.23.so[7fd036934000+1c]
[3712474.949633] mdadm[17727]: segfault at 0 ip 7f2814111d16 sp 
7ffca92fe168 error 4 in libc-2.23.so[7f2814087000+1c]
[3798863.008741] mdadm[25359]: segfault at 0 ip 7fa6af198d16 sp 
7ffc1b253e48 error 4 in libc-2.23.so[7fa6af10e000+1c]
[3798863.190382] mdadm[25393]: segfault at 0 ip 7f72218a0d16 sp 
7ffef918f118 error 4 in libc-2.23.so[7f7221816000+1c]
[3885251.386711] mdadm[32081]: segfault at 0 ip 7f3d99ca2d16 sp 
7ffe5e69a7a8 error 4 in libc-2.23.so[7f3d99c18000+1c]
[3885251.402337] mdadm[32083]: segfault at 0 ip 7f770ccc1d16 sp 
7ffe16074378 error 4 in libc-2.23.so[7f770cc37000+1c]
[3971638.258574] mdadm[7936]: segfault at 0 ip 7fcacddb3d16 sp 
7ffc062faff8 error 4 in libc-2.23.so[7fcacdd29000+1c]
[3971638.410750] mdadm[8053]: segfault at 0 ip 7ff573757d16 sp 
7fffd3cca398 error 4 in libc-2.23.so[7ff5736cd000+1c]

The segfault message always appears twice in quick succession.

It seems to be triggered by /etc/cron.daily/mdadm which essentially runs
mdadm --monitor --scan --oneshot

As such, the frequency is around every 85000 seconds or 24 hours give or
take, depending on when the cron job was executed.

It does not happen when running the command manually.

There is one similar bug #1576055 concerning libc and a few cases
elsewhere but further digging into this has yet to reveal anything
conclusive.

Note that these machines have almost exactly the same hardware (Xeon
D-1518, 16GB ECC), so hardware design flaws cannot be ruled out.
However, memory testing has not turned up any faults. That said, I know
some segfaults can be difficult to find even when they are hardware
issues.

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

** Package changed: gvfs (Ubuntu) => mdadm (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/1617919

Title:
  mdadm segfault error 4 in libc-2.23.so

Status in mdadm package in Ubuntu:
  New

Bug description:
  On Ubuntu 16.04.1 LTS Xenial, mdadm segfaults every day on two
  machines. Everything works as normal though, and the RAID arrays are
  not degraded.

  [3712474.763430] mdadm[17665]: segfault at 0 ip 7fd0369bed16 sp 
7fff8c5c9478 error 4 in libc-2.23.so[7fd036934000+1c]
  [3712474.949633] mdadm[17727]: segfault at 0 ip 7f2814111d16 sp 
7ffca92fe168 error 4 in libc-2.23.so[7f2814087000+1c]
  [3798863.008741] mdadm[25359]: segfault at 0 ip 7fa6af198d16 sp 
7ffc1b253e48 error 4 in libc-2.23.so[7fa6af10e000+1c]
  [3798863.190382] mdadm[25393]: segfault at 0 ip 7f72218a0d16 sp 
7ffef918f118 error 4 in libc-2.23.so[7f7221816000+1c]
  [3885251.386711] mdadm[32081]: segfault at 0 ip 7f3d99ca2d16 sp 
7ffe5e69a7a8 error 4 in libc-2.23.so[7f3d99c18000+1c]
  [3885251.402337] mdadm[32083]: segfault at 0 ip 7f770ccc1d16 sp 
7ffe16074378 error 4 in libc-2.23.so[7f770cc37000+1c]
  [3971638.258574] mdadm[7936]: segfault at 0 ip 7fcacddb3d16 sp 
7ffc062faff8 error 4 in libc-2.23.so[7fcacdd29000+1c]
  [3971638.410750] mdadm[8053]: segfault at 0 ip 7ff573757d16 sp 
7fffd3cca398 error 4 in libc-2.23.so[7ff5736cd000+1c]

  The segfault message always appears twice in quick succession.

  It seems to be triggered by /etc/cron.daily/mdadm which essentially runs
  mdadm --monitor --scan --oneshot

  As such, the frequency is around every 85000 seconds or 24 hours give
  or take, depending on when the cron job was executed.

  It does not happen when running the command manually.

  There is one similar bug #1576055 concerning libc and a few cases
  elsewhere but further digging into this has yet to reveal anything
  conclusive.

  Note that these machines have almost exactly the same hardware (Xeon
  D-1518, 16GB ECC), so hardware design flaws cannot be ruled out.
  However, memory testing has not turned up any faults. That said, I
  know some segfaults can be difficult to find even when they are
  hardware issues.

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

-- 
Mailing list: https://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 1510970] Re: Intel driver crashes on Ubuntu 15.10

[Johan Tol]

The same for me. Today I rolled back the "uxa"-workaround by deleting
the 20-intel.conf file from /etc/X11/xorg.conf.d (I didn't have one
before the workaround). After a couple of hours I still haven't had a
single crash. I guess 16.04 solved the problem.

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

[Desktop-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

typo: 16.06 --> 16.04

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  WORKAROUND: /etc/X11/xorg.conf.d/20-intel.conf

  with the following content:

  Section "Device"
   Identifier "Card0"
   Driver "Intel"
   Option "AccelMethod" "uxa"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:091c]
  InstallationDate: Installed on 2015-01-20 (281 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Acer Aspire VN7-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 

[Desktop-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

Shortly after its introduction I migrated to Ubuntu 16.04. Today I
rolled back the "uxa"-workaround by deleting the 20-intel.conf file from
/etc/X11/xorg.conf.d (I didn't have one before the workaround). After a
couple of hours I still haven't had a single crash. I guess 16.06 solved
the problem.

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  WORKAROUND: /etc/X11/xorg.conf.d/20-intel.conf

  with the following content:

  Section "Device"
   Identifier "Card0"
   Driver "Intel"
   Option "AccelMethod" "uxa"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:091c]
  InstallationDate: Installed on 2015-01-20 (281 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Acer Aspire VN7-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  

[Desktop-packages] [Bug 1588150] Re: Remove webkitgtk from archive

[Johan Mattsson]

Version 2.16.4 uses webkit2.

** Changed in: birdfont (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Remove webkitgtk from archive

Status in Bijiben:
  In Progress
Status in Empathy:
  Confirmed
Status in Evolution:
  Confirmed
Status in Geary:
  Confirmed
Status in bijiben package in Ubuntu:
  Triaged
Status in birdfont package in Ubuntu:
  Fix Committed
Status in cairo-dock-plugins package in Ubuntu:
  Triaged
Status in empathy package in Ubuntu:
  Triaged
Status in evolution package in Ubuntu:
  Triaged
Status in geary package in Ubuntu:
  Triaged
Status in gnome-web-photo package in Ubuntu:
  Triaged
Status in gtkpod package in Ubuntu:
  Triaged
Status in liferea package in Ubuntu:
  Triaged
Status in maildir-utils package in Ubuntu:
  Triaged
Status in surf package in Ubuntu:
  Triaged
Status in webkitgtk package in Ubuntu:
  Triaged
Status in xiphos package in Ubuntu:
  Triaged
Status in xombrero package in Ubuntu:
  Triaged

Bug description:
  webkitgtk is obsolete and has been replaced by webkit2gtk. This
  requires things to be ported to the new API.

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

-- 
Mailing list: https://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 1569674] Re: [Kubuntu] Fail to connect to wifi after a recent update

[Johan van Breda]

My system has the same problem. Looks like an un-initialized parameter.

Changes to the network via the GUI fail due to this, but nmcli still works.
That is  cumbersome, but provides a workaround.

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

Title:
  [Kubuntu] Fail to connect to wifi after a recent update

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I installed the recent updates in the Update Manager and after rebooting I 
wasn't able to connect to my wifi network anymore.
  It attempts to connect to the network and fails with the following error 
message:

  Failed to update connection [network name]
  connection.gateway-ping-timeout: can not set property:
  value "46730064" of type 'guint' is invalid or out of range for property 
'gateway-ping-timeout' of type 'guint'

  I am able to use wired connection.

  1. release:
  Description:Ubuntu Xenial Xerus (development branch)
  Release:16.04

  2. network-manager version:
  network-manager:
Installed: 1.1.93-0ubuntu3
Candidate: 1.1.93-0ubuntu3
Version table:
   *** 1.1.93-0ubuntu3 500
  500 http://il.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3. I expected the machine to connect to wifi as always

  4. it failed to connect with the above error message

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Apr 13 06:37:27 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-01 (11 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160331)
  IpRoute:
   default via 10.100.102.1 dev enp0s31f6  proto static  metric 100 
   10.100.102.0/24 dev enp0s31f6  proto kernel  scope link  src 10.100.102.5  
metric 100 
   169.254.0.0/16 dev enp0s31f6  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=false
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-04-12T22:28:14.870844
  nmcli-dev:
   DEVICE TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp0s31f6  ethernet  connected/org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  d956dc0d-4de6-4f45-8869-a3703d8d0d28  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp4s0 wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
  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/1569674/+subscriptions

-- 
Mailing list: https://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 1567841] Re: One of my two graphics cards has started to freeze the screen

[Carl-Johan Kjellander]

[354327.154763] [TTM] Out of kernel memory
[354327.154770] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224001] [TTM] Out of kernel memory
[354327.224008] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224572] [TTM] Out of kernel memory
[354327.224574] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224585] [TTM] Out of kernel memory
[354327.224587] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224594] chrome[16008]: segfault at 10 ip 7fafe02a5b5c sp 
7ffd84ced8f0 error 4 in r600_dri.so[7fafdffef000+399000]
[355403.930696] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (262144, 2, 4096, -12)

Maybe this is related?

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

Title:
  One of my two graphics cards has started to freeze the screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I run a setup of 2 radeon graphics cards, with 3 screens, in the
  following layout from left to right counting from 0:

  Card 0 Screen 1, Card 1 Screen 0, Card 0 Screen 0 rotated ccw

  I have been running this setup for a year and it has worked fine. This
  monday I updated some packages and did a reboot, and I usually reboot
  just once a month cause I patch my running kernel with uptrack.

  After the reboot I started noticing problems with the second card,
  Card 1 above. With a mean time between failures of about an hour, the
  second card freezes the screen, I usually notice that the mouse
  pointer isn't visible anymore when I move it across from one screen to
  the middle one. For future reference, the window I have on the middle
  screen is a fullscreen emacs window.

  I have tried the following kernels: vmlinuz-3.13.0-77-generic,
  vmlinuz-3.13.0-79-generic, vmlinuz-3.13.0-83-generic

  All have the same problem. And nothing shows up in dmesg when the
  freeze occurs, or in the Xorg.0.log, I made copies from before and
  after a freeze.

  If I move the mouse, that I can't see, onto the middle screen, make
  emacs the active window (again I can't see this), scroll around a bit
  with the arrow keys and take a screenshot, the screenshot shows the
  correctly scrolled window, so the big X buffer is actually correctly
  updated.

  If I CTRL-ALT-L to lock the screens, they all go black, but when you
  press enter only the screens on Card 0 shows the lock screen, the
  middle one again shows frozen emacs.

  CTRL-ALT-F1 shows two text terminals on the outermost screens, in the
  middle, you've guessed it, frozen emacs.

  If I go to the menu and select Switch user, surprise! Now the frozen
  screen is gone and it is a gray login screen with the login menu
  actually on the screen to the right.

  Log back into my still running user, boooh, it again shows the
  same frozen emacs.

  Switch to a completely new user, screen in middle is correct and
  working.

  And lastly if I log out completely from my user and log in again the
  screen is now unfrozen, but I have lots of work and it is really
  really annoying to have to log out 8 times during a day at work.

  I'm gonna try one more ancient kernel just to see if there have been
  some changes to drm or the radeon driver, but I am pretty stumped on
  this one. It all worked fine last week.

  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Linux rymdborje 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,snap,imgpng,regex,animation,place,move,vpswitch,mousepoll,grid,unitymtgrabhandles,expo,workarounds,session,wall,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  8 10:38:17 2016
  DistUpgraded: 2015-03-16 15:26:59,578 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.36, 3.13.0-65-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:03f2]
   Advanced Micro Devices, Inc. 

[Desktop-packages] [Bug 1567841] Re: One of my two graphics cards has started to freeze the screen

[Carl-Johan Kjellander]

[354327.154763] [TTM] Out of kernel memory
[354327.154770] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224001] [TTM] Out of kernel memory
[354327.224008] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224572] [TTM] Out of kernel memory
[354327.224574] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224585] [TTM] Out of kernel memory
[354327.224587] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (4096, 2, 4096, -12)
[354327.224594] chrome[16008]: segfault at 10 ip 7fafe02a5b5c sp 
7ffd84ced8f0 error 4 in r600_dri.so[7fafdffef000+399000]
[355403.930696] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM 
object (262144, 2, 4096, -12)

Maybe this is related?

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

Title:
  One of my two graphics cards has started to freeze the screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I run a setup of 2 radeon graphics cards, with 3 screens, in the
  following layout from left to right counting from 0:

  Card 0 Screen 1, Card 1 Screen 0, Card 0 Screen 0 rotated ccw

  I have been running this setup for a year and it has worked fine. This
  monday I updated some packages and did a reboot, and I usually reboot
  just once a month cause I patch my running kernel with uptrack.

  After the reboot I started noticing problems with the second card,
  Card 1 above. With a mean time between failures of about an hour, the
  second card freezes the screen, I usually notice that the mouse
  pointer isn't visible anymore when I move it across from one screen to
  the middle one. For future reference, the window I have on the middle
  screen is a fullscreen emacs window.

  I have tried the following kernels: vmlinuz-3.13.0-77-generic,
  vmlinuz-3.13.0-79-generic, vmlinuz-3.13.0-83-generic

  All have the same problem. And nothing shows up in dmesg when the
  freeze occurs, or in the Xorg.0.log, I made copies from before and
  after a freeze.

  If I move the mouse, that I can't see, onto the middle screen, make
  emacs the active window (again I can't see this), scroll around a bit
  with the arrow keys and take a screenshot, the screenshot shows the
  correctly scrolled window, so the big X buffer is actually correctly
  updated.

  If I CTRL-ALT-L to lock the screens, they all go black, but when you
  press enter only the screens on Card 0 shows the lock screen, the
  middle one again shows frozen emacs.

  CTRL-ALT-F1 shows two text terminals on the outermost screens, in the
  middle, you've guessed it, frozen emacs.

  If I go to the menu and select Switch user, surprise! Now the frozen
  screen is gone and it is a gray login screen with the login menu
  actually on the screen to the right.

  Log back into my still running user, boooh, it again shows the
  same frozen emacs.

  Switch to a completely new user, screen in middle is correct and
  working.

  And lastly if I log out completely from my user and log in again the
  screen is now unfrozen, but I have lots of work and it is really
  really annoying to have to log out 8 times during a day at work.

  I'm gonna try one more ancient kernel just to see if there have been
  some changes to drm or the radeon driver, but I am pretty stumped on
  this one. It all worked fine last week.

  Description:  Ubuntu 14.04.4 LTS
  Release:  14.04
  Linux rymdborje 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,snap,imgpng,regex,animation,place,move,vpswitch,mousepoll,grid,unitymtgrabhandles,expo,workarounds,session,wall,ezoom,fade,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr  8 10:38:17 2016
  DistUpgraded: 2015-03-16 15:26:59,578 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.36, 3.13.0-65-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed
   virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:03f2]
   Advanced Micro Devices, Inc. 

[Desktop-packages] [Bug 1567841] [NEW] One of my two graphics cards has started to freeze the screen

[Carl-Johan Kjellander]

Public bug reported:

I run a setup of 2 radeon graphics cards, with 3 screens, in the
following layout from left to right counting from 0:

Card 0 Screen 1, Card 1 Screen 0, Card 0 Screen 0 rotated ccw

I have been running this setup for a year and it has worked fine. This
monday I updated some packages and did a reboot, and I usually reboot
just once a month cause I patch my running kernel with uptrack.

After the reboot I started noticing problems with the second card, Card
1 above. With a mean time between failures of about an hour, the second
card freezes the screen, I usually notice that the mouse pointer isn't
visible anymore when I move it across from one screen to the middle one.
For future reference, the window I have on the middle screen is a
fullscreen emacs window.

I have tried the following kernels: vmlinuz-3.13.0-77-generic,
vmlinuz-3.13.0-79-generic, vmlinuz-3.13.0-83-generic

All have the same problem. And nothing shows up in dmesg when the freeze
occurs, or in the Xorg.0.log, I made copies from before and after a
freeze.

If I move the mouse, that I can't see, onto the middle screen, make
emacs the active window (again I can't see this), scroll around a bit
with the arrow keys and take a screenshot, the screenshot shows the
correctly scrolled window, so the big X buffer is actually correctly
updated.

If I CTRL-ALT-L to lock the screens, they all go black, but when you
press enter only the screens on Card 0 shows the lock screen, the middle
one again shows frozen emacs.

CTRL-ALT-F1 shows two text terminals on the outermost screens, in the
middle, you've guessed it, frozen emacs.

If I go to the menu and select Switch user, surprise! Now the frozen
screen is gone and it is a gray login screen with the login menu
actually on the screen to the right.

Log back into my still running user, boooh, it again shows the same
frozen emacs.

Switch to a completely new user, screen in middle is correct and
working.

And lastly if I log out completely from my user and log in again the
screen is now unfrozen, but I have lots of work and it is really really
annoying to have to log out 8 times during a day at work.

I'm gonna try one more ancient kernel just to see if there have been
some changes to drm or the radeon driver, but I am pretty stumped on
this one. It all worked fine last week.

Description:Ubuntu 14.04.4 LTS
Release:14.04
Linux rymdborje 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
Uname: Linux 3.13.0-77-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,snap,imgpng,regex,animation,place,move,vpswitch,mousepoll,grid,unitymtgrabhandles,expo,workarounds,session,wall,ezoom,fade,scale,unityshell]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Apr  8 10:38:17 2016
DistUpgraded: 2015-03-16 15:26:59,578 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.3.36, 3.13.0-65-generic, x86_64: installed
 virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed
 virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed
 virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:03f2]
 Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] 
[1002:6613] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:04bb]
InstallationDate: Installed on 2012-03-13 (1486 days ago)
InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 
(20111011)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-77-generic 
root=/dev/mapper/fiskgunnar-root ro nomdmonddf nomdmonisw
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2015-03-16 (388 days ago)
dmi.bios.date: 12/22/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0906
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P9X79
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0906:bd12/22/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name

[Desktop-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

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

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V18.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E35 (MS-7846)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  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.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7846
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  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: Thu Nov 12 22:41:25 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLogitech USB Receiver KEYBOARD, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.17.2-1ubuntu9

To 

[Desktop-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

This issue seems to be resolved in 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/1515784

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V18.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E35 (MS-7846)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  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.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7846
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  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: Thu Nov 12 22:41:25 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLogitech USB Receiver KEYBOARD, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.17.2-1ubuntu9

To manage notifications about 

Re: [Desktop-packages] [Bug 1358467] Re: Time and date not always there

[Johan Wysneus]

Thanks for your email. I reported this a long time ago and the problem 
seems to have disappeared in the meantime.

Regards
Johan


On 28/02/2016 23:20, Christopher M. Penalver wrote:
> Johan Wysneus, thank you for reporting this and helping make Ubuntu
> better.
>
> Could you please provide the full computer model as noted on the sticker
> of the computer itself (not from the Bug Description)?
>
> ** Changed in: xorg (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  Time and date not always there

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The time and date is not always displayed in the top right corner
  after boot up. Sometimes I have to reboot several times before time
  and date is displayed correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  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: Mon Aug 18 21:34:17 2014
  DistUpgraded: 2014-05-24 21:07:18,319 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
  InstallationDate: Installed on 2014-05-24 (86 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic 
root=UUID=a83be82f-cfd0-44f3-b18a-2e3c7a637068 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (86 days ago)
  dmi.bios.date: 04/30/2010
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 01KY.M008.20100430.RHU
  dmi.board.asset.tag: SAMSUNG
  dmi.board.name: N150P/N210P/N220P
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr01KY.M008.20100430.RHU:bd04/30/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P/N210P/N220P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P/N210P/N220P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: N150P/N210P/N220P
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Aug 18 16:41:23 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12336 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2

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

-- 
Mailing list: https://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 1540294] Re: Network manager stopped working after some update

[Johan]

Latest update of network-manager (feb 04) solved the issue for me.

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

Title:
  Network manager stopped working after some update

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  'sudo NetworkManager' gives:
  (NetworkManager:7010): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: Key file does not have group 'connectivity'

  To get network interface to work I have to do like this:
  'sudo ip link set dev eth0 down'
  'sudo dhclient eth0'

  
  Ubuntu 14.04.3 LTS

  'apt-cache policy network-manager':
  network-manager:
Installed: 0.9.8.8-0ubuntu7.2
Candidate: 0.9.8.8-0ubuntu7.2
Version table:
   *** 0.9.8.8-0ubuntu7.2 0
  500 http://mirror.one.com/ubuntu/ trusty-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.9.8.8-0ubuntu7.1 0
  500 http://mirror.one.com/ubuntu/ trusty-security/main amd64 Packages
   0.9.8.8-0ubuntu7 0
  500 http://mirror.one.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  1 10:57:19 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-28 (1190 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 192.168.1.1 dev eth0 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.110 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to trusty on 2016-02-01 (0 days ago)
  WifiSyslog:
   
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-02-01T11:14:17.778018
  nmcli-con:
   Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
   ** (process:6612): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
   Error: nmcli (0.9.8.8) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   not running unknownunknown unknown   unknown 
unknownunknown unknown

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

-- 
Mailing list: https://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 1540294] [NEW] Network manager stopped working after some update

[Johan]

Public bug reported:

'sudo NetworkManager' gives:
(NetworkManager:7010): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Key file does not have group 'connectivity'

To get network interface to work I have to do like this:
'sudo ip link set dev eth0 down'
'sudo dhclient eth0'


Ubuntu 14.04.3 LTS

'apt-cache policy network-manager':
network-manager:
  Installed: 0.9.8.8-0ubuntu7.2
  Candidate: 0.9.8.8-0ubuntu7.2
  Version table:
 *** 0.9.8.8-0ubuntu7.2 0
500 http://mirror.one.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
 0.9.8.8-0ubuntu7.1 0
500 http://mirror.one.com/ubuntu/ trusty-security/main amd64 Packages
 0.9.8.8-0ubuntu7 0
500 http://mirror.one.com/ubuntu/ trusty/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7.2
ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
Uname: Linux 3.13.0-77-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb  1 10:57:19 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-10-28 (1190 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IpRoute:
 default via 192.168.1.1 dev eth0 
 192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.110 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to trusty on 2016-02-01 (0 days ago)
WifiSyslog:
 
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-02-01T11:14:17.778018
nmcli-con:
 Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: 
 ** (process:6612): WARNING **: Could not initialize NMClient 
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was 
not provided by any .service files
 Error: nmcli (0.9.8.8) and NetworkManager (unknown) versions don't match. 
Force execution using --nocheck, but the results are unpredictable.
nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 not running unknownunknown unknown   unknown 
unknownunknown unknown

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


** Tags: amd64 apport-bug trusty

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

Title:
  Network manager stopped working after some update

Status in network-manager package in Ubuntu:
  New

Bug description:
  'sudo NetworkManager' gives:
  (NetworkManager:7010): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: Key file does not have group 'connectivity'

  To get network interface to work I have to do like this:
  'sudo ip link set dev eth0 down'
  'sudo dhclient eth0'

  
  Ubuntu 14.04.3 LTS

  'apt-cache policy network-manager':
  network-manager:
Installed: 0.9.8.8-0ubuntu7.2
Candidate: 0.9.8.8-0ubuntu7.2
Version table:
   *** 0.9.8.8-0ubuntu7.2 0
  500 http://mirror.one.com/ubuntu/ trusty-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   0.9.8.8-0ubuntu7.1 0
  500 http://mirror.one.com/ubuntu/ trusty-security/main amd64 Packages
   0.9.8.8-0ubuntu7 0
  500 http://mirror.one.com/ubuntu/ trusty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  1 10:57:19 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2012-10-28 (1190 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  IpRoute:
   default via 192.168.1.1 dev eth0 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.110 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   

[Desktop-packages] [Bug 1510970] Re: Intel driver crashes on Ubuntu 15.10

[Johan Tol]

Thank you Axel for pointing to the intel drivers. I installed the latest
drivers and enabled SNA again. It looks as if it takes longer to crash
now, but eventually it does. Prior to the update it was easy for me the
reproduce a crash with LibreOffice Calc. That requires a bit more effort
now. I guess I have to go back to uxa again.

-- 
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
  [

[Desktop-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

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

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V18.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E35 (MS-7846)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  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.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7846
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  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: Thu Nov 12 22:41:25 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputLogitech USB Receiver KEYBOARD, id 9
   inputLogitech USB Receiver KEYBOARD, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.17.2-1ubuntu9

To manage 

[Desktop-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

Here is the output of running xrandr just after logging inm only the
third time all resolutions are found:

johan@cdh7:~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 1600mm x 900mm
   1920x1080 60.00*+
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
johan@cdh7:~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 1600mm x 900mm
   1920x1080 60.00*+
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
johan@cdh7:~$ xrandr
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
HDMI1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected primary 3840x2160+0+0 (normal left inverted right x axis y 
axis) 1600mm x 900mm
   1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97
23.98  
   4096x2160 24.0023.98  
   3840x2160 30.00*   25.0024.0029.9723.98  
   1920x1080i60.0050.0059.94  
   1280x1024 60.02  
   1360x768  60.02  
   1152x864  59.97  
   1280x720  60.0050.0059.94  
   1024x768  60.00  
   800x600   60.32  
   720x576   50.00  
   720x576i  50.00  
   720x480   60.0059.94  
   640x480   60.0059.94  
   720x400   70.08  
VGA1 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
johan@cdh7:~$

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Mega

[Desktop-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

The problem still occurs when using  a kernel from vivid (3.19.0-35).

If I login, the resolution is not correct. If I fix the resolution
everything is fine until I logout (no need to reboot). If I login again,
the resolution is bad again.

The available resolutions seem to change from time to time. Sometimes after 
login I get only 1920x1080 when doing a login, but it drops back to 1024x768 as 
well, sometimes rescaling to 1920x1080 if I wait a bit longer (the error messag 
already appeared at that time).
After logging in and waiting approximately 20 seconds I can go to display 
options and reset my display to the full resolution( 3840x2160).

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V18.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E35 (MS-7846)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  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.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7846
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  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 

[Desktop-packages] [Bug 1515784] Re: UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

Updating the BIOS does not solve the problem. 
Output: of sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
V18.5
07/19/2014
Note that this is a regression when updating from utopic to wily.

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

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

Title:
  UHD resolution not found when logging in, can select after login

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  After updating from vivid to wily I noticed my screen no longer boots
  in UHD resolution. I can set the resolution during the session, but on
  next login it returns back to full hd. This is a regression from
  vivid, where the resolution worked without problem.

  This happens with different window managers.

  In cinnamon I get an additional error, which is solved by removing
  .config/monitors.xml

  none of the selected modes were compatible with the possible modes:
  Trying modes for CRTC 63
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 64
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 65
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
  Trying modes for CRTC 66
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
  CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

  I'm willing to invest some time in trying to find a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Thu Nov 12 22:42:35 2015
  DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
  InstallationDate: Installed on 2011-09-07 (1527 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
  MachineType: MSI MS-7846
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
  dmi.bios.date: 09/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V18.1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-E35 (MS-7846)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  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.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7846
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  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: Thu Nov 12 22:41:25 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button KEYBOARD, id 8
   inputLogitech 

[Desktop-packages] [Bug 1510970] Re: Intel driver crashes on Ubuntu 15.10

[Johan Tol]

Thank you Georgi for the workaround. Works for me!

-- 
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 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN)
  [2.658922] systemd[1]: Detected architecture x86-64.

  [  626.810377] 

[Desktop-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

Thank you Anoop for referring to 
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1510970
The workaround presented there works for me!

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  Unfortunately I have no clue how to reproduce the segfault. The last
  crash happened while I was reading some document and I did not push
  any button, moved the mouse or anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:091c]
  InstallationDate: Installed on 2015-01-20 (281 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Acer Aspire VN7-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No 

[Desktop-packages] [Bug 1515784] [NEW] UHD resolution not found when logging in, can select after login

[Johan Van de Wauw]

Public bug reported:

Hi,

After updating from vivid to wily I noticed my screen no longer boots in
UHD resolution. I can set the resolution during the session, but on next
login it returns back to full hd. This is a regression from vivid, where
the resolution worked without problem.

This happens with different window managers.

In cinnamon I get an additional error, which is solved by removing
.config/monitors.xml

none of the selected modes were compatible with the possible modes:
Trying modes for CRTC 63
CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 63: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
Trying modes for CRTC 64
CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 64: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
Trying modes for CRTC 65
CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 65: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)
Trying modes for CRTC 66
CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 0)
CRTC 66: trying mode 1920x1080@60Hz with output at 3840x2160@60Hz (pass 1)

I'm willing to invest some time in trying to find a solution.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,grid,vpswitch,move,gnomecompat,snap,wall,compiztoolbox,resize,imgpng,regex,place,unitymtgrabhandles,animation,fade,scale,session,expo,workarounds,ezoom,unityshell]
CompositorRunning: None
CurrentDesktop: X-Cinnamon
Date: Thu Nov 12 22:42:35 2015
DistUpgraded: 2015-11-06 20:56:17,323 DEBUG failed to SystemUnLock() (E:Not 
locked)
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7846]
InstallationDate: Installed on 2011-09-07 (1527 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110907)
MachineType: MSI MS-7846
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-17-generic 
root=UUID=a303977d-e14d-40d9-a9b7-982b12961f6c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to wily on 2015-11-06 (6 days ago)
dmi.bios.date: 09/24/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V18.1
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-E35 (MS-7846)
dmi.board.vendor: MSI
dmi.board.version: 3.0
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.:bvrV18.1:bd09/24/2013:svnMSI:pnMS-7846:pvr3.0:rvnMSI:rnH81M-E35(MS-7846):rvr3.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: MS-7846
dmi.product.version: 3.0
dmi.sys.vendor: MSI
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: Thu Nov 12 22:41:25 2015
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputLogitech USB Receiver KEYBOARD, id 9
 inputLogitech USB Receiver KEYBOARD, id 10
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.17.2-1ubuntu9

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


** Tags: amd64 apport-bug resolution ubuntu wily

** Description changed:

  Hi,
  
  After updating from vivid to wily I noticed my screen no longer boots in
- UHD resolution. I can set the resolution during the setting, but on next
+ UHD resolution. I can set the resolution during the session, but on next
  login it returns back to full hd. This is a regression from vivid, where
  the resolution worked without problem.
  
  This happens with 

[Desktop-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

Sorry for the delay, but I was able to generate a backtrace as described
by Dirk Seidel in comment #7 and comment #8. The backtrace is attached.

** Attachment added: "gdb-X.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1510998/+attachment/4512905/+files/gdb-X.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/1510998

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  Unfortunately I have no clue how to reproduce the segfault. The last
  crash happened while I was reading some document and I did not push
  any button, moved the mouse or anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:091c]
  InstallationDate: Installed on 2015-01-20 (281 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Acer Aspire VN7-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset 

[Desktop-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

Sorry, I can't generate a backtrace, same problem as Dirk: after
executing "continue" in gdb my entire system freezes, so I can't get
back to the X session.

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  Unfortunately I have no clue how to reproduce the segfault. The last
  crash happened while I was reading some document and I did not push
  any button, moved the mouse or anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Oct 28 16:30:43 2015
  DistUpgraded: 2015-10-27 11:46:32,614 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-31-generic, x86_64: installed
   bbswitch, 0.7, 4.2.0-16-generic, x86_64: installed
   nvidia-304, 304.128, 3.19.0-31-generic, x86_64: installed
   nvidia-304, 304.128, 4.2.0-16-generic, x86_64: installed
   vboxhost, 4.3.26, 3.19.0-31-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:091c]
  InstallationDate: Installed on 2015-01-20 (281 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei 
oder Verzeichnis nicht gefunden
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Acer Aspire VN7-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=5ebd3c26-8bee-44ee-a832-0dbfb0ee72f4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-27 (1 days ago)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No Asset 

[Desktop-packages] [Bug 1510998] Re: Xorg crashes with segfault on 15.10

[Johan Tol]

I have exactly the same problem since upgrading to 15.10. For me
reproducable in LibreOffice 5.0.3.2 Calc by a right mouse click followed
by selecting "Format Cells...".

Xorg.0.log.old:
[   674.409] (EE) Backtrace:
[   674.409] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55d163d7262e]
[   674.409] (EE) 1: /usr/bin/X (0x55d163bbe000+0x1b8999) [0x55d163d76999]
[   674.409] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f82b6c33000+0x352f0) 
[0x7f82b6c682f0]
[   674.409] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x24f18) [0x7f82b302ef18]
[   674.409] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x26157) [0x7f82b3030157]
[   674.409] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x2b4b1) [0x7f82b30354b1]
[   674.409] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x804e4) [0x7f82b308a4e4]
[   674.409] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x80e2c) [0x7f82b308ae2c]
[   674.409] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x82e1a) [0x7f82b308ce1a]
[   674.409] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x4197c) [0x7f82b304b97c]
[   674.409] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f82b300a000+0x59906) [0x7f82b3063906]
[   674.409] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55d163c1b654]
[   674.409] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55d163d76274]
[   674.409] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55d163c21502]
[   674.409] (EE) 14: /usr/bin/X (0x55d163bbe000+0xf495a) [0x55d163cb295a]
[   674.409] (EE) 15: /usr/bin/X (0x55d163bbe000+0xf5ef5) [0x55d163cb3ef5]
[   674.409] (EE) 16: /usr/bin/X (0x55d163bbe000+0x5818f) [0x55d163c1618f]
[   674.409] (EE) 17: /usr/bin/X (0x55d163bbe000+0x5c34b) [0x55d163c1a34b]
[   674.409] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f82b6c53a40]
[   674.409] (EE) 19: /usr/bin/X (_start+0x29) [0x55d163c046c9]
[   674.409] (EE)
[   674.409] (EE) Segmentation fault at address 0x0
[   674.409] (EE)
Fatal server error:
[   674.409] (EE) Caught signal 11 (Segmentation fault). Server aborting

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

Title:
  Xorg crashes with segfault on 15.10

Status in xorg package in Ubuntu:
  New

Bug description:
  I updated my system from 15.04 to 15.10 yesterday. Since then the X
  server has already crashed 5 times, which renders the system close to
  unusable for me.

  The corresponding messages in Xorg.0.log.old are:
  [ 12125.023] (EE)
  [ 12125.023] (EE) Backtrace:
  [ 12125.023] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55953d82762e]
  [ 12125.023] (EE) 1: /usr/bin/X (0x55953d673000+0x1b8999) [0x55953d82b999]
  [ 12125.023] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f7c10e7b000+0x352f0) 
[0x7f7c10eb02f0]
  [ 12125.023] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x24edc) [0x7f7c0d276edc]
  [ 12125.023] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x26157) [0x7f7c0d278157]
  [ 12125.023] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a1e8) [0x7f7c0d29c1e8]
  [ 12125.023] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x4a7ec) [0x7f7c0d29c7ec]
  [ 12125.023] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x59103) [0x7f7c0d2ab103]
  [ 12125.023] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f7c0d252000+0x593aa) [0x7f7c0d2ab3aa]
  [ 12125.023] (EE) 9: /usr/bin/X (0x55953d673000+0x13fb73) [0x55953d7b2b73]
  [ 12125.023] (EE) 10: /usr/bin/X (0x55953d673000+0x54ce3) [0x55953d6c7ce3]
  [ 12125.023] (EE) 11: /usr/bin/X (0x55953d673000+0x5818f) [0x55953d6cb18f]
  [ 12125.023] (EE) 12: /usr/bin/X (0x55953d673000+0x5c34b) [0x55953d6cf34b]
  [ 12125.023] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7f7c10e9ba40]
  [ 12125.023] (EE) 14: /usr/bin/X (_start+0x29) [0x55953d6b96c9]
  [ 12125.023] (EE)
  [ 12125.023] (EE) Segmentation fault at address 0x7f7e141995e0
  [ 12125.023] (EE)
  Fatal server error:
  [ 12125.023] (EE) Caught signal 11 (Segmentation fault). Server aborting

  I have attached the syslog file. The relevant messages for the three crashes 
from today can be found  at:
  Oct 28 15:56:36
  Oct 28 12:06:58
  Oct 28 09:08:51

  Unfortunately I have no clue how to reproduce the segfault. The last
  crash happened while I was reading some document and I did not push
  any button, moved the mouse or anything...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None

[Desktop-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Johan Potgieter]

I get this on Xubuntu 14.04 whenever I connect via wifi to my ios
personal hotspot. Often it does nothing more than ask to send the report
but other times it hangs after a few minutes. I have found it so
disruptive that I am unable to get any work done while connected to my
phone. I will try some of the remedies and hopefully it will sort out my
issue.

I wanted to add this note as I didn't see any mention of this happening
while connecting to a personal hotspot, as is the case with me.

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()

[Johan Potgieter]

I need to add that I have the latest versions of both libimobiledevice4
and libimobiledevice-utils and I still get this error. I dont get any
errors when connecting to any other wifi router or via ethernet cable.
Any suggestions would be appreciated.

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

Title:
  upowerd crashed with SIGSEGV in service_client_free()

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  it looks like nothing happend. When I switch on the PC and after loging in 
this window with 'report an error/bug' appeard. so I guess it is minor.
  thanks for doing :)

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic i686
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: i386
  Date: Wed Apr  9 15:37:43 2014
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2014-04-04 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386 
(20140326)
  ProcCmdline: /usr/lib/upower/upowerd
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0xb74e9919 :   mov
(%esi),%eax
   PC (0xb74e9919) ok
   source "(%esi)" (0x302e) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: upower
  StacktraceTop:
   service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   property_list_service_client_free () from 
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
   lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
   ?? ()
   g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: upowerd crashed with SIGSEGV in service_client_free()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://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 1429584] Re: gnome-terminal doesn't set $COLORTERM from 3.14 onwards

[Johan Boule]

Can we make it so the new VTE release appear in Ubuntu 15.04 ?

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

Title:
  gnome-terminal doesn't set $COLORTERM from 3.14 onwards

Status in gnome-terminal package in Ubuntu:
  Confirmed

Bug description:
  Gnome terminal has dropped the $COLORTERM workaround for invalid
  terminfo/termcap.

  References:
  
https://github.com/GNOME/gnome-terminal/commit/1d5c1b6ca6373c1301494edbc9e43c3e6a9c9aaf
  https://bugzilla.redhat.com/show_bug.cgi?id=1165439
  https://bugzilla.redhat.com/show_bug.cgi?id=1173688
  https://bugzilla.redhat.com/show_bug.cgi?id=1166428

  This affects release: Vivid Vervet

  Workaround I currently use is `.bashrc`:
   if [ -z $COLORTERM ]  cat /proc/$PPID/exe 2 /dev/null | grep -q 
gnome-terminal; then
    export COLORTERM=gnome-terminal
   fi

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

-- 
Mailing list: https://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 1475914] Re: login freezes or black screen with kernel higher than 3.19.0-15

[Johan Nilsson]

I have a similar issue with my laptop with AMD graphics running ubuntu
gnome 15.04, which I originally reported as #1447356. I have kernels
3.19.0-15 and 3.19.0-22 and both of them give a black screen after the
grub screen.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1475914

Title:
  login freezes or black screen with kernel higher than 3.19.0-15

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

Bug description:
  Env :
  Linux 3.19.0-22-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux
  VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde 
XT [Radeon HD 7770/8760 / R7 250X]
  using xorg default driver (not the proprietary)

  Facts :
  - On the login page, just after the boot, the system is freezed (or looping)
  - I can't open a terminal with Ctrl+Alt+F1
  - When I choose a previous kernel version from Grub, the problem occurs with 
all versions I had installed since 3.19.0-16
  3.19.0-15   OK
  3.19.0-16   KO
  3.19.0-18   KO
  3.19.0-20   KO
  3.19.0-21   KO
  3.19.0-22   KO
  - When I choose the recovery mode of the version that have the problem, the 
recovery menu freezes also (see attachment)
  - I've done a clean install on a new disk and after the update of the kernel 
(3.19.0-15 - 3.19.0-22) I have a black screen after the boot (no login 
screen). And I have the same problem trying the recovery mode with version 
3.19.0-22.

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

-- 
Mailing list: https://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 67691] Re: Nautilus can leave half-copied files on the target on error or cancel

[Johan Boule]

My doubt confirmed. I'll have to use rsync to fix the partial copies.

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

Title:
  Nautilus can leave half-copied files on the target on error or cancel

Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  If a file move/copy is stopped half way through (eg due to pressing
  cancel or volume full error), Nautilus advises there was an error but
  does not try to delete the half-copied file, leaving the impression to
  a user on the target file system that the file was successfully
  copied.

  When you do the copy again and press Skip all existing this will
  lead to data loss.

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

-- 
Mailing list: https://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 67691] Re: Nautilus can leave half-copied files on the target on error or cancel

[Johan Boule]

And now rsync reveals another problem... nautilus doesn't preserve mtime
while copying!

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

Title:
  Nautilus can leave half-copied files on the target on error or cancel

Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  If a file move/copy is stopped half way through (eg due to pressing
  cancel or volume full error), Nautilus advises there was an error but
  does not try to delete the half-copied file, leaving the impression to
  a user on the target file system that the file was successfully
  copied.

  When you do the copy again and press Skip all existing this will
  lead to data loss.

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

-- 
Mailing list: https://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 1388922] Re: xdg-open doesn't properly detect Xfce/Xubuntu

[Johan Gunnarsson]

Still happens on Xubuntu 15.04, but fixed upstream.

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

Title:
  xdg-open doesn't properly detect Xfce/Xubuntu

Status in Xdg-utils:
  Fix Released
Status in xdg-utils package in Ubuntu:
  Confirmed

Bug description:
  xdg-open doesn't detect the XFCE desktop environment on its fresh install on 
Ubuntu (not Xubuntu).
  I was able to fix that by adding 'elif [ x$DESKTOP_SESSION = xxubuntu ]; 
then DE=xfce;' line in 'detectDE()' function.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xdg-utils/+bug/1388922/+subscriptions

-- 
Mailing list: https://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 269904] Re: Screen refresh problems with nvidia cards

[Johan Boule]

I set up a reminder to check this issue once again on Utopic. So, today
I went to http://packages.ubuntu.com/utopic/compiz, clicked on the
Changelog link, searched for #269904, and didn't find it.

Tank you Mateusz for having added an utopic tag to this issue.

However as time passes, I can't help but think this bug will never be
officially fixed on Utopic, since its end of life date is just two
months from now.

You may just mark it as Won't fix for Utopic.

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

Title:
  Screen refresh problems with nvidia cards

Status in Compiz:
  Fix Released
Status in Compiz 0.9.11 series:
  In Progress
Status in Compiz Core:
  New
Status in Compiz Core 0.9.8 series:
  New
Status in compiz package in Ubuntu:
  Fix Released
Status in compiz-fusion-plugins-main package in Ubuntu:
  Fix Released
Status in compiz-plugins-main package in Ubuntu:
  Fix Released
Status in compiz source package in Precise:
  Confirmed
Status in compiz-plugins-main source package in Precise:
  Confirmed
Status in compiz source package in Trusty:
  Fix Released
Status in compiz-plugins-main source package in Trusty:
  Invalid
Status in compiz source package in Intrepid:
  Fix Released
Status in compiz-plugins-main source package in Intrepid:
  Won't Fix
Status in compiz-fusion-plugins-main package in Debian:
  Fix Released

Bug description:
  [Impact]

  Users of Nvidia gfx using the proprietary driver may see screen
  corruption during certain operations.

  [Test Case]

  * Install an Nvidia graphics adapter and the proprietary driver.
  * Observe the graphics corrupt.
  * Install the version of Compiz with this fix.
  * Observe corruption is gone.

  [Regression Potential]

  The patch for this was provided by Nvidia.  There could be some corner
  cases users hit that may cause other issues.  That said, enough
  testing has been done to confidently say that the gains provided by
  this fix far outweigh any corner cases.

  ---

  Original Description:

  == Proposed compiz-fusion-plugins-main patch ==
  See comment 234 by Anders Kaseorg and attached 
compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff.

  == Original report ==
  Binary package hint: compiz

  I'm using latest compiz on intrepid.

  Since jockey-gtk does not work on my box (I already filed a bug), I
  manually installed nvidia-glx-177 and added the driver → nvidia line
  to xorg.conf.

  Now I seem to be having some screen refresh problems when using
  compiz: parts of the screen are refreshed, but others aren't. That
  means nautilus doesn't show files or folders until I move the cursor
  over them, firefox doesn't show webpages properly until I scroll down,
  and so on.

  Please, tell me if there is any additional info I can provide to find
  out the cause.

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

-- 
Mailing list: https://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 269904] Re: Screen refresh problems with nvidia cards

[Johan Boulé]

A note about Ryan's comment #364 : compiz --version shows 0.9.11.3.
Wasn't the bug supposed to be fixed in 0.9.12.1 ?

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

Title:
  Screen refresh problems with nvidia cards

Status in Compiz:
  Fix Released
Status in Compiz 0.9.11 series:
  In Progress
Status in Compiz Core:
  New
Status in Compiz Core 0.9.8 series:
  New
Status in compiz package in Ubuntu:
  Fix Released
Status in compiz-fusion-plugins-main package in Ubuntu:
  Fix Released
Status in compiz-plugins-main package in Ubuntu:
  Fix Released
Status in compiz source package in Precise:
  New
Status in compiz-plugins-main source package in Precise:
  Confirmed
Status in compiz source package in Trusty:
  Fix Committed
Status in compiz-plugins-main source package in Trusty:
  Invalid
Status in compiz source package in Intrepid:
  Fix Released
Status in compiz-plugins-main source package in Intrepid:
  Won't Fix
Status in compiz-fusion-plugins-main package in Debian:
  Fix Released

Bug description:
  [Impact]

  Users of Nvidia gfx using the proprietary driver may see screen
  corruption during certain operations.

  [Test Case]

  * Install an Nvidia graphics adapter and the proprietary driver.
  * Observe the graphics corrupt.
  * Install the version of Compiz with this fix.
  * Observe corruption is gone.

  [Regression Potential]

  The patch for this was provided by Nvidia.  There could be some corner
  cases users hit that may cause other issues.  That said, enough
  testing has been done to confidently say that the gains provided by
  this fix far outweigh any corner cases.

  ---

  Original Description:

  == Proposed compiz-fusion-plugins-main patch ==
  See comment 234 by Anders Kaseorg and attached 
compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff.

  == Original report ==
  Binary package hint: compiz

  I'm using latest compiz on intrepid.

  Since jockey-gtk does not work on my box (I already filed a bug), I
  manually installed nvidia-glx-177 and added the driver → nvidia line
  to xorg.conf.

  Now I seem to be having some screen refresh problems when using
  compiz: parts of the screen are refreshed, but others aren't. That
  means nautilus doesn't show files or folders until I move the cursor
  over them, firefox doesn't show webpages properly until I scroll down,
  and so on.

  Please, tell me if there is any additional info I can provide to find
  out the cause.

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

-- 
Mailing list: https://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 269904] Re: Screen refresh problems with nvidia cards

[Johan Boulé]

And also fixed in 0.9.11.4, but not in 0.9.11.3.

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

Title:
  Screen refresh problems with nvidia cards

Status in Compiz:
  Fix Released
Status in Compiz 0.9.11 series:
  In Progress
Status in Compiz Core:
  New
Status in Compiz Core 0.9.8 series:
  New
Status in compiz package in Ubuntu:
  Fix Released
Status in compiz-fusion-plugins-main package in Ubuntu:
  Fix Released
Status in compiz-plugins-main package in Ubuntu:
  Fix Released
Status in compiz source package in Precise:
  New
Status in compiz-plugins-main source package in Precise:
  Confirmed
Status in compiz source package in Trusty:
  Fix Committed
Status in compiz-plugins-main source package in Trusty:
  Invalid
Status in compiz source package in Intrepid:
  Fix Released
Status in compiz-plugins-main source package in Intrepid:
  Won't Fix
Status in compiz-fusion-plugins-main package in Debian:
  Fix Released

Bug description:
  [Impact]

  Users of Nvidia gfx using the proprietary driver may see screen
  corruption during certain operations.

  [Test Case]

  * Install an Nvidia graphics adapter and the proprietary driver.
  * Observe the graphics corrupt.
  * Install the version of Compiz with this fix.
  * Observe corruption is gone.

  [Regression Potential]

  The patch for this was provided by Nvidia.  There could be some corner
  cases users hit that may cause other issues.  That said, enough
  testing has been done to confidently say that the gains provided by
  this fix far outweigh any corner cases.

  ---

  Original Description:

  == Proposed compiz-fusion-plugins-main patch ==
  See comment 234 by Anders Kaseorg and attached 
compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff.

  == Original report ==
  Binary package hint: compiz

  I'm using latest compiz on intrepid.

  Since jockey-gtk does not work on my box (I already filed a bug), I
  manually installed nvidia-glx-177 and added the driver → nvidia line
  to xorg.conf.

  Now I seem to be having some screen refresh problems when using
  compiz: parts of the screen are refreshed, but others aren't. That
  means nautilus doesn't show files or folders until I move the cursor
  over them, firefox doesn't show webpages properly until I scroll down,
  and so on.

  Please, tell me if there is any additional info I can provide to find
  out the cause.

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

-- 
Mailing list: https://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 269904] Re: Screen refresh problems with nvidia cards

[Johan Boulé]

I see a new compiz package version 1:0.9.12.0+15.04.20150202-0ubuntu1 for Vivid 
has been published on 2015-02-02.
However, according to the changelog of that realease, it does not close bug 
#269904.
So this raises the question: why has the status changed to Fix Released ? I 
can't seem to find a published version for Ubuntu 14.10/Utopic for example.
Shouldn't it be changed back to some other status ?

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

Title:
  Screen refresh problems with nvidia cards

Status in Compiz:
  Fix Released
Status in Compiz 0.9.11 series:
  In Progress
Status in Compiz Core:
  New
Status in Compiz Core 0.9.8 series:
  New
Status in compiz package in Ubuntu:
  Fix Released
Status in compiz-fusion-plugins-main package in Ubuntu:
  Fix Released
Status in compiz source package in Trusty:
  Confirmed
Status in compiz-fusion-plugins-main source package in Trusty:
  Confirmed
Status in compiz source package in Intrepid:
  Fix Released
Status in compiz-fusion-plugins-main source package in Intrepid:
  Won't Fix
Status in compiz-fusion-plugins-main package in Debian:
  Fix Released

Bug description:
  [Impact]

  Users of Nvidia gfx using the proprietary driver may see screen
  corruption during certain operations.

  [Test Case]

  * Install an Nvidia graphics adapter and the proprietary driver.
  * Observe the graphics corrupt.
  * Install the version of Compiz with this fix.
  * Observe corruption is gone.

  [Regression Potential]

  The patch for this was provided by Nvidia.  There could be some corner
  cases users hit that may cause other issues.  That said, enough
  testing has been done to confidently say that the gains provided by
  this fix far outweigh any corner cases.

  ---

  Original Description:

  == Proposed compiz-fusion-plugins-main patch ==
  See comment 234 by Anders Kaseorg and attached 
compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff.

  == Original report ==
  Binary package hint: compiz

  I'm using latest compiz on intrepid.

  Since jockey-gtk does not work on my box (I already filed a bug), I
  manually installed nvidia-glx-177 and added the driver → nvidia line
  to xorg.conf.

  Now I seem to be having some screen refresh problems when using
  compiz: parts of the screen are refreshed, but others aren't. That
  means nautilus doesn't show files or folders until I move the cursor
  over them, firefox doesn't show webpages properly until I scroll down,
  and so on.

  Please, tell me if there is any additional info I can provide to find
  out the cause.

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

-- 
Mailing list: https://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 269904] Re: Screen refresh problems with nvidia cards

[Johan Boulé]

OK, now i see that source package compiz 0.9.12.1 has been released.
However i'm a bit confused with the launchpad site to determine when
this package is scheduled to be built and on which specific binary
distributions is it going to land. Where can I see a link between this
source release and milestones/distributions ?

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

Title:
  Screen refresh problems with nvidia cards

Status in Compiz:
  Fix Released
Status in Compiz 0.9.11 series:
  In Progress
Status in Compiz Core:
  New
Status in Compiz Core 0.9.8 series:
  New
Status in compiz package in Ubuntu:
  Fix Released
Status in compiz-fusion-plugins-main package in Ubuntu:
  Fix Released
Status in compiz source package in Trusty:
  Confirmed
Status in compiz-fusion-plugins-main source package in Trusty:
  Confirmed
Status in compiz source package in Intrepid:
  Fix Released
Status in compiz-fusion-plugins-main source package in Intrepid:
  Won't Fix
Status in compiz-fusion-plugins-main package in Debian:
  Fix Released

Bug description:
  [Impact]

  Users of Nvidia gfx using the proprietary driver may see screen
  corruption during certain operations.

  [Test Case]

  * Install an Nvidia graphics adapter and the proprietary driver.
  * Observe the graphics corrupt.
  * Install the version of Compiz with this fix.
  * Observe corruption is gone.

  [Regression Potential]

  The patch for this was provided by Nvidia.  There could be some corner
  cases users hit that may cause other issues.  That said, enough
  testing has been done to confidently say that the gains provided by
  this fix far outweigh any corner cases.

  ---

  Original Description:

  == Proposed compiz-fusion-plugins-main patch ==
  See comment 234 by Anders Kaseorg and attached 
compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff.

  == Original report ==
  Binary package hint: compiz

  I'm using latest compiz on intrepid.

  Since jockey-gtk does not work on my box (I already filed a bug), I
  manually installed nvidia-glx-177 and added the driver → nvidia line
  to xorg.conf.

  Now I seem to be having some screen refresh problems when using
  compiz: parts of the screen are refreshed, but others aren't. That
  means nautilus doesn't show files or folders until I move the cursor
  over them, firefox doesn't show webpages properly until I scroll down,
  and so on.

  Please, tell me if there is any additional info I can provide to find
  out the cause.

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

-- 
Mailing list: https://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 1410690] [NEW] nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build

[Carl Johan Rehn]

Public bug reported:

NA

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331-updates 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
DKMSKernelVersion: 3.13.0-44-generic
Date: Wed Jan 14 09:30:54 2015
InstallationDate: Installed on 2013-12-31 (378 days ago)
InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
PackageVersion: 331.113-0ubuntu0.0.4
SourcePackage: nvidia-graphics-drivers-331-updates
Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel 
module failed to build
UpgradeStatus: Upgraded to trusty on 2014-06-20 (207 days ago)

** Affects: nvidia-graphics-drivers-331-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages trusty

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

Title:
  nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel
  module failed to build

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  New

Bug description:
  NA

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331-updates 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-44-generic
  Date: Wed Jan 14 09:30:54 2015
  InstallationDate: Installed on 2013-12-31 (378 days ago)
  InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel 
module failed to build
  UpgradeStatus: Upgraded to trusty on 2014-06-20 (207 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1410690/+subscriptions

-- 
Mailing list: https://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 967416] Re: inkscape crashed with SIGSEGV in file_save()

[Johan Engelen]

I want to remind you all that the majority of Inkscape's code is not at
all ready for multithreading. This save code, and all the code and data
it needs for saving the document is certainly not thread safe. So the
fix is to remove the _main_loop_run stuff, and just do the save right
there and then (block on the save, and only continue when it is done).

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

Title:
  inkscape crashed with SIGSEGV in file_save()

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in inkscape package in Ubuntu:
  Triaged

Bug description:
  Occurred when I closed Inkscape.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: inkscape 0.48.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Mar 28 15:01:15 2012
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(2029.1)
  ProcCmdline: inkscape /home/username/MyKaryotes/graphics/cell.svg
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  Title: inkscape crashed with SIGSEGV in sp_file_save_dialog()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 269904] Re: Screen refresh problems with nvidia cards

[Johan Boulé]

I confirm that applying the patch 0.9.12/revision/3916 solves the
partial-redraw / flickering issues on utopic with nvidia driver 346.22
on a geforce gt 740 card.

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

Title:
  Screen refresh problems with nvidia cards

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  Triaged
Status in Compiz Core:
  New
Status in Compiz Core 0.9.8 series:
  New
Status in compiz package in Ubuntu:
  Fix Released
Status in compiz-fusion-plugins-main package in Ubuntu:
  Fix Released
Status in compiz source package in Intrepid:
  Fix Released
Status in compiz-fusion-plugins-main source package in Intrepid:
  Won't Fix
Status in compiz-fusion-plugins-main package in Debian:
  Fix Released

Bug description:
  == Proposed compiz-fusion-plugins-main patch ==
  See comment 234 by Anders Kaseorg and attached 
compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff.

  == Original report ==
  Binary package hint: compiz

  I'm using latest compiz on intrepid.

  Since jockey-gtk does not work on my box (I already filed a bug), I
  manually installed nvidia-glx-177 and added the driver → nvidia line
  to xorg.conf.

  Now I seem to be having some screen refresh problems when using
  compiz: parts of the screen are refreshed, but others aren't. That
  means nautilus doesn't show files or folders until I move the cursor
  over them, firefox doesn't show webpages properly until I scroll down,
  and so on.

  Please, tell me if there is any additional info I can provide to find
  out the cause.

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

-- 
Mailing list: https://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 1396895] [NEW] nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to build

[Johan van Voskuilen]

Public bug reported:

Upon updating to the latest kernel version (3.16.0.25 from 3.16.0.24) my
display driver (nvidia 331.89) starts giving problems. Ubuntu 14.10.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331-uvm 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 3.16.0-25-generic
Date: Wed Nov 26 17:03:06 2014
InstallationDate: Installed on 2014-11-06 (20 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
PackageVersion: 331.89-0ubuntu5
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package utopic

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

Title:
  nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to
  build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  Upon updating to the latest kernel version (3.16.0.25 from 3.16.0.24)
  my display driver (nvidia 331.89) starts giving problems. Ubuntu
  14.10.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-uvm 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Wed Nov 26 17:03:06 2014
  InstallationDate: Installed on 2014-11-06 (20 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1396895/+subscriptions

-- 
Mailing list: https://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 1358429] [NEW] Can't enable Language Tools in Libre Office

[Johan Wysneus]

Public bug reported:

I can't enable Language Tools in Libre Office. When I try I get the
error message: LibreOffice 4.2.3.3, Could not create Java
implementation loader. I think it is installed ok, I just can't enable
it. I have asked for help on the forums, but nobody replied.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic i686
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
CurrentDesktop: Unity
Date: Mon Aug 18 20:06:14 2014
InstallationDate: Installed on 2014-05-24 (86 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to trusty on 2014-05-24 (85 days ago)

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


** Tags: apport-bug i386 trusty

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

Title:
  Can't enable Language Tools in Libre Office

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  I can't enable Language Tools in Libre Office. When I try I get the
  error message: LibreOffice 4.2.3.3, Could not create Java
  implementation loader. I think it is installed ok, I just can't
  enable it. I have asked for help on the forums, but nobody replied.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic i686
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Aug 18 20:06:14 2014
  InstallationDate: Installed on 2014-05-24 (86 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (85 days ago)

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

-- 
Mailing list: https://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 1358466] [NEW] Display settings seems to keep changing

[Johan Wysneus]

Public bug reported:

My display settings don’t seem to stay constant, e.g. sometimes
selections are highlighted in blue and sometimes in brown.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
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: Mon Aug 18 21:27:53 2014
DistUpgraded: 2014-05-24 21:07:18,319 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
   Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
InstallationDate: Installed on 2014-05-24 (86 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic 
root=UUID=a83be82f-cfd0-44f3-b18a-2e3c7a637068 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-05-24 (86 days ago)
dmi.bios.date: 04/30/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 01KY.M008.20100430.RHU
dmi.board.asset.tag: SAMSUNG
dmi.board.name: N150P/N210P/N220P
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr01KY.M008.20100430.RHU:bd04/30/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P/N210P/N220P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P/N210P/N220P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N150P/N210P/N220P
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Aug 18 16:41:23 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12336 
 vendor SEC
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: apport-bug compiz-0.9 i386 trusty 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/1358466

Title:
  Display settings seems to keep changing

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My display settings don’t seem to stay constant, e.g. sometimes
  selections are highlighted in blue and sometimes in brown.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  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: Mon Aug 18 21:27:53 2014
  DistUpgraded: 2014-05-24 21:07:18,319 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
  InstallationDate: Installed on 2014-05-24 (86 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic 

[Desktop-packages] [Bug 1358467] [NEW] Time and date not always there

[Johan Wysneus]

Public bug reported:

The time and date is not always displayed in the top right corner after
boot up. Sometimes I have to reboot several times before time and date
is displayed correctly.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
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: Mon Aug 18 21:34:17 2014
DistUpgraded: 2014-05-24 21:07:18,319 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
   Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
InstallationDate: Installed on 2014-05-24 (86 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic 
root=UUID=a83be82f-cfd0-44f3-b18a-2e3c7a637068 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to trusty on 2014-05-24 (86 days ago)
dmi.bios.date: 04/30/2010
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 01KY.M008.20100430.RHU
dmi.board.asset.tag: SAMSUNG
dmi.board.name: N150P/N210P/N220P
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr01KY.M008.20100430.RHU:bd04/30/2010:svnSAMSUNGELECTRONICSCO.,LTD.:pnN150P/N210P/N220P:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN150P/N210P/N220P:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N150P/N210P/N220P
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Aug 18 16:41:23 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   12336 
 vendor SEC
xserver.version: 2:1.15.1-0ubuntu2

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


** Tags: apport-bug compiz-0.9 i386 trusty 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/1358467

Title:
  Time and date not always there

Status in “xorg” package in Ubuntu:
  New

Bug description:
  The time and date is not always displayed in the top right corner
  after boot up. Sometimes I have to reboot several times before time
  and date is displayed correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  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: Mon Aug 18 21:34:17 2014
  DistUpgraded: 2014-05-24 21:07:18,319 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
 Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
  InstallationDate: Installed on 2014-05-24 (86 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
  

[Desktop-packages] [Bug 1288747] Re: [334] Parts of the UI randomly flicker when moving the mouse

[Johan Ferner]

Installed 340.24 from xorg-edgers on 14.04. Started firefox and google search 
home screen flickered like mad. Installed the compiz patch and flickering 
stopped. So far the patch is perfect. Will monitor memory consumption after a 
full working day.
Thanks for the patch!

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

Title:
  [334] Parts of the UI randomly flicker when moving the mouse

Status in Compiz:
  Triaged
Status in “compiz” package in Ubuntu:
  Triaged

Bug description:
  Nvidia 334.21 makes the UI jearky, googled and found this on Nvidia
  forums:

  This looks like a problem caused by the system compositor not
  properly waiting for X rendering to finish before performing OpenGL
  rendering in response. The GL_EXT_x11_sync_object extension was
  designed to solve this problem, but it looks like cogl (the back-end
  library used by GNOME's compositor) doesn't use it yet. 

  more details:
  
https://devtalk.nvidia.com/default/topic/690704/linux/-334-16-parts-of-the-ui-randomly-flicker-when-moving-the-mouse/post/4128101/#4128101
  --- 
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] É uma directoria: 
u'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu6)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.13.3-0ubuntu1
  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
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-16-generic, x86_64: installedError! Could not locate 
dkms.conf file.
   File:  does not exist.
   
   nvidia-331-updates, 331.38, 3.13.0-16-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF106 [GeForce GTS 450] [10de:0dc4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:34fe]
  InstallationDate: Installed on 2014-03-03 (4 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia
  Package: compiz 1:0.9.11+14.04.20140305-0ubuntu1
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-16-generic 
root=UUID=d2c3632d-4280-4961-91c8-0b7d3fe95be1 ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Tags:  trusty trusty possible-manual-nvidia-install ubuntu single-occurrence 
reproducible compiz-0.9
  Uname: Linux 3.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/17/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0620
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5QL-ASUS-SE
  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.:bvr0620:bd06/17/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL-ASUS-SE: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.11+14.04.20140305-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc3-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc3-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Mar  7 10:50:58 2014
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu6

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

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

[Desktop-packages] [Bug 967416] Re: inkscape crashed with SIGSEGV in file_save()

[Johan Engelen]

It depends on quick timing. When saving the document, control returns to
the GUI before the save is complete. If inkscape is closed in that
period: crash.

It seems a ton of crashes can happen when the save is still happening
while inkscape is closed. The code is not at all ready for
multithreading like that.

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

Title:
  inkscape crashed with SIGSEGV in file_save()

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in “inkscape” package in Ubuntu:
  Triaged

Bug description:
  Occurred when I closed Inkscape.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: inkscape 0.48.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Mar 28 15:01:15 2012
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(2029.1)
  ProcCmdline: inkscape /home/username/MyKaryotes/graphics/cell.svg
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  Title: inkscape crashed with SIGSEGV in sp_file_save_dialog()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 967416] Re: inkscape crashed with SIGSEGV in file_save()

[Johan Engelen]

So to fix this, the exit procedure should be able to figure out if some
threads are running in the background (the saving thread), and wait for
it to start destroying objects.

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

Title:
  inkscape crashed with SIGSEGV in file_save()

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in “inkscape” package in Ubuntu:
  Triaged

Bug description:
  Occurred when I closed Inkscape.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: inkscape 0.48.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Mar 28 15:01:15 2012
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(2029.1)
  ProcCmdline: inkscape /home/username/MyKaryotes/graphics/cell.svg
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  Title: inkscape crashed with SIGSEGV in sp_file_save_dialog()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 967416] Re: inkscape crashed with SIGSEGV in file_save()

[Johan Engelen]

wait for it to start destroying objects.
wait for it before starting to destroy objects.

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

Title:
  inkscape crashed with SIGSEGV in file_save()

Status in Inkscape: A Vector Drawing Tool:
  Triaged
Status in “inkscape” package in Ubuntu:
  Triaged

Bug description:
  Occurred when I closed Inkscape.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: inkscape 0.48.3.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Mar 28 15:01:15 2012
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(2029.1)
  ProcCmdline: inkscape /home/username/MyKaryotes/graphics/cell.svg
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  Title: inkscape crashed with SIGSEGV in sp_file_save_dialog()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1275164] Re: inkscape crashed with SIGSEGV in sp_ctrlpoint_set_color()

[Johan Engelen]

how to reproduce in trunk?

** Changed in: inkscape
   Status: New = Incomplete

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

Title:
  inkscape crashed with SIGSEGV in sp_ctrlpoint_set_color()

Status in Inkscape: A Vector Drawing Tool:
  Incomplete
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  it happens sometimes right after the clean empty devs  save 
  Remove a horizontal guide line

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: inkscape 0.48.4-3ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
  Uname: Linux 3.13.0-6-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Feb  1 01:42:37 2014
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-12-12 (50 days ago)
  InstallationMedia: Kubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  ProcCmdline: /usr/bin/inkscape
  ProcEnviron:
   LANGUAGE=de:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x74cb51 
_Z22sp_ctrlpoint_set_colorP11SPCtrlPointj+33:   cmp(%rdx),%rax
   PC (0x0074cb51) ok
   source (%rdx) (0x) not located in a known VMA region 
(needed readable region)!
   destination %rax ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   sp_ctrlpoint_set_color(SPCtrlPoint*, unsigned int) ()
   sp_guideline_set_color(SPGuideLine*, unsigned int) ()
   sp_dt_guide_event(SPCanvasItem*, _GdkEvent*, void*) ()
   sp_marshal_BOOLEAN__POINTER ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: inkscape crashed with SIGSEGV in sp_ctrlpoint_set_color()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 977003] Re: inkscape crashed with SIGSEGV in Avoid::VertInf::removeFromGraph()

[Johan Engelen]

fixed in rev. 13413

because of constructor ConnRef(Router *router, const unsigned int id),
_srcVert and _dstVert can be NULL, and _active can be false. this
constructor seems unfinished, but is used elsewhere in the code. hence
the crash.

** Changed in: inkscape
   Status: Triaged = Fix Committed

** Changed in: inkscape
Milestone: None = 0.91

** Changed in: inkscape
 Assignee: (unassigned) = Johan Engelen (johanengelen)

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

Title:
  inkscape crashed with SIGSEGV in Avoid::VertInf::removeFromGraph()

Status in Inkscape: A Vector Drawing Tool:
  Fix Committed
Status in “inkscape” package in Ubuntu:
  Triaged

Bug description:
  I was having huge difficulties to finish an image in which I was using
  diagram connectors to draw arrows between circles (a graph, for those
  who know what it is).

  At some point, I needed to draw the curved arrows in the image
  attached, and every time I needed to move the drawing or do anything
  with the arrows, like changing the markers' colors, these curved
  arrows kept turning into straight ones again, over and over.

  After a million times going like this, I asked inkscape to render a
  latex formula for me and, when the formula was ready, the arrows
  simply disappeared!

  This is everything that I remember happening before the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: inkscape 0.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
  Uname: Linux 3.0.0-17-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Mon Apr  9 02:49:18 2012
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x8822f11 _ZN5Avoid7VertInf15removeFromGraphEb+17:   
cmpb   $0x0,0x8(%esi)
   PC (0x08822f11) ok
   source $0x0 ok
   destination 0x8(%esi) (0x0008) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: inkscape
  Stacktrace:
   #0  0x08822f11 in Avoid::VertInf::removeFromGraph(bool) ()
   No symbol table info available.
   Não é possível acessar a memória no endereço 0xbfdedfac
  StacktraceTop: Avoid::VertInf::removeFromGraph(bool) ()
  Title: inkscape crashed with SIGSEGV in Avoid::VertInf::removeFromGraph()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: admin audio cdrom colord dialout fax fuse plugdev pulse-access 
saned scanner sudo users vboxusers voice

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

-- 
Mailing list: https://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 977003] Re: inkscape crashed with SIGSEGV in Avoid::VertInf::removeFromGraph()

[Johan Engelen]

correction: fixed in experimental rev 13413, trunk rev 13444

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

Title:
  inkscape crashed with SIGSEGV in Avoid::VertInf::removeFromGraph()

Status in Inkscape: A Vector Drawing Tool:
  Fix Committed
Status in “inkscape” package in Ubuntu:
  Fix Committed

Bug description:
  I was having huge difficulties to finish an image in which I was using
  diagram connectors to draw arrows between circles (a graph, for those
  who know what it is).

  At some point, I needed to draw the curved arrows in the image
  attached, and every time I needed to move the drawing or do anything
  with the arrows, like changing the markers' colors, these curved
  arrows kept turning into straight ones again, over and over.

  After a million times going like this, I asked inkscape to render a
  latex formula for me and, when the formula was ready, the arrows
  simply disappeared!

  This is everything that I remember happening before the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: inkscape 0.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
  Uname: Linux 3.0.0-17-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Mon Apr  9 02:49:18 2012
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x8822f11 _ZN5Avoid7VertInf15removeFromGraphEb+17:   
cmpb   $0x0,0x8(%esi)
   PC (0x08822f11) ok
   source $0x0 ok
   destination 0x8(%esi) (0x0008) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: inkscape
  Stacktrace:
   #0  0x08822f11 in Avoid::VertInf::removeFromGraph(bool) ()
   No symbol table info available.
   Não é possível acessar a memória no endereço 0xbfdedfac
  StacktraceTop: Avoid::VertInf::removeFromGraph(bool) ()
  Title: inkscape crashed with SIGSEGV in Avoid::VertInf::removeFromGraph()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: admin audio cdrom colord dialout fax fuse plugdev pulse-access 
saned scanner sudo users vboxusers voice

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

-- 
Mailing list: https://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 977003] Re: inkscape crashed with SIGSEGV in Avoid::VertInf::removeFromGraph()

[Johan Engelen]

** Changed in: inkscape (Ubuntu)
   Status: Triaged = Fix Committed

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

Title:
  inkscape crashed with SIGSEGV in Avoid::VertInf::removeFromGraph()

Status in Inkscape: A Vector Drawing Tool:
  Fix Committed
Status in “inkscape” package in Ubuntu:
  Fix Committed

Bug description:
  I was having huge difficulties to finish an image in which I was using
  diagram connectors to draw arrows between circles (a graph, for those
  who know what it is).

  At some point, I needed to draw the curved arrows in the image
  attached, and every time I needed to move the drawing or do anything
  with the arrows, like changing the markers' colors, these curved
  arrows kept turning into straight ones again, over and over.

  After a million times going like this, I asked inkscape to render a
  latex formula for me and, when the formula was ready, the arrows
  simply disappeared!

  This is everything that I remember happening before the crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: inkscape 0.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
  Uname: Linux 3.0.0-17-generic i686
  NonfreeKernelModules: fglrx
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Mon Apr  9 02:49:18 2012
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x8822f11 _ZN5Avoid7VertInf15removeFromGraphEb+17:   
cmpb   $0x0,0x8(%esi)
   PC (0x08822f11) ok
   source $0x0 ok
   destination 0x8(%esi) (0x0008) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: inkscape
  Stacktrace:
   #0  0x08822f11 in Avoid::VertInf::removeFromGraph(bool) ()
   No symbol table info available.
   Não é possível acessar a memória no endereço 0xbfdedfac
  StacktraceTop: Avoid::VertInf::removeFromGraph(bool) ()
  Title: inkscape crashed with SIGSEGV in Avoid::VertInf::removeFromGraph()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: admin audio cdrom colord dialout fax fuse plugdev pulse-access 
saned scanner sudo users vboxusers voice

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

-- 
Mailing list: https://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 1307648] Re: chromium 34 from proposed does not take input from keyboard in first entry point on several webpages

[Johan Hake]

I have the same problem. I cannot enter any url or any normal form text.
Passwords for one reason works though. This happened after upgrade to
14.04 Kubuntu with chromium 34.0.1847.116

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

Title:
  chromium 34 from proposed does not take input from keyboard in first
  entry point on several webpages

Status in “chromium-browser” package in Ubuntu:
  Incomplete

Bug description:
  To reproduce install chromium 34 from proposed with pepperflash. And
  find a site that you input some text into like indeed.com or some
  others. Then you hit the keys on the keyboard but no text is seen
  onscreen.

  I expected the text to be entering into chroumium like it is on any
  other browser. And for the text to be entered into the browser and
  transfered ot the webpage I am submitting it to.

  Instead it did not show up and indeed.com thought I did not enter anything 
even though I pressed several keys on my keyboard. 
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  chromium-browser:
Installed: 34.0.1847.116-0ubuntu1~pkg1006
Candidate: 34.0.1847.116-0ubuntu1~pkg1006
Version table:
   *** 34.0.1847.116-0ubuntu1~pkg1006 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-proposed/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   33.0.1750.152-0ubuntu1~pkg995.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu1~pkg1006
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Mon Apr 14 11:15:07 2014
  Desktop-Session:
   DESKTOP_SESSION = Lubuntu
   XDG_CONFIG_DIRS = 
/etc/xdg/lubuntu:/etc/xdg/xdg-Lubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/etc/xdg/lubuntu:/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:/usr/share/Lubuntu:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sdc4  
ext4  641G   61G  549G  10% /\nnone   tmpfs 4.0K 0  4.0K   
0% /sys/fs/cgroup\nudev   devtmpfs  1.9G  4.0K  1.9G   1% /dev\ntmpfs   
   tmpfs 386M  1.3M  385M   1% /run\nnone   tmpfs 5.0M 
0  5.0M   0% /run/lock\nnone   tmpfs 1.9G   17M  1.9G   1% 
/run/shm\nnone   tmpfs 100M   16K  100M   1% /run/user\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sdc4 41M  
565K   41M2% /\nnone 483K 2  483K1% 
/sys/fs/cgroup\nudev 480K   612  479K1% /dev\ntmpfs
483K   643  482K1% /run\nnone 483K 5  483K1% 
/run/lock\nnone 483K19  483K1% /run/shm\nnone 
483K13  483K1% /run/user\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-01-02 (102 days ago)
  InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha amd64 (20140101)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-04-14T10:56:12.681598

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

-- 
Mailing list: https://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 34745] Re: Beeps on tab

[Johan Boulé]

Daniel Holbach (dholbach) wrote on 2006-08-02: 
 Something not quite irrelevant: I had a quite embarrasing moment when I booted
 the GNOME 2.14 when I was in the office and its LONG login sound went as loud
 as my speakers could.

Let's not exagerate the matter here.. when you think about what an
embarrasing sound might be, it's not beeps that come to mind.

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

Title:
  Beeps on tab

Status in GNOME Terminal:
  New
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “readline5” package in Ubuntu:
  Confirmed

Bug description:
  Gnome-terminal beeps on tab. On an office full of Ubuntus, continous
  beeping is annoying.

  Beeping can be turned off from Edit:Current Profile:General:Terminal
  Bell. However, tab completition is one of the most used features of
  bash shell. There is absolutely no point in beeping all the time. Even
  though this is just an interface issue, it is something almost every
  user wants to change right away.

  Suggestion: change the default to no terminal bell.

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

-- 
Mailing list: https://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 537703] Re: Compiz intercepts alert sound from gnome-terminal

[Johan Boulé]

Ubuntu 13.04 same bug..

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

Title:
  Compiz intercepts alert sound from gnome-terminal

Status in Compiz:
  Confirmed
Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: compiz

  This is with up-to-date Lucid installed afresh from alpha 3.

  When compiz is active, the Gnome alert sound for gnome-terminal is
  intercepted and never played. I'm not sure other applications suffer
  from this, but I would find it strange it this were specific to gnome-
  terminal.

  Detailed steps to reproduce:
  - Check that the alert sound is enabled and audible:
- Click on the volume indicator in the panel and choose Sound 
preferences...
- Go to the Sound effects tab
- Set the alert volume slider to a nonzero value
- Make sure the master volume is also at a nonzero value
- Check sound can be heard by clicking on one of the unselected alert 
sounds in the list
- Close Sound preferences window
  - Press Alt-F2, enter gnome-terminal and press enter
  - Make sure the Terminal bell is enabled:
- Right-click on the terminal background, and select Profiles  Profile 
preferences
- Make sure Terminal bell is checked
- Close Profile preferences window
  - With compiz enabled, focus the terminal and hit backspace. No sound is 
played
  - Press Alt-F2, enter metacity --replace and press enter
  - Go back to the open terminal and hit backspace. The alert sound is played

  The above behaviour occurs regardless of whether the gconf key
  /apps/compiz/general/allscreens/options/audible_bell is set or not.
  Moreover, if one sets a visual effect to represent the bell (blur,
  water, wobbly, ...), it is displayed. So the bell is being sent,
  compiz is receiving it, but it never passes it to the relevant bit of
  the desktop that is supposed to play the sound. Metacity does.

  ProblemType: Bug
  Architecture: amd64
  CompizPlugins: 
[core,ccp,move,resize,place,decoration,session,commands,put,gnomecompat,dbus,png,workarounds,resizeinfo,regex,imgjpeg,text,mousepoll,svg,thumbnail,annotate,wall,animation,blur,wobbly,expo,scale,ezoom,obs,staticswitcher,scaleaddon,bench]
  Date: Thu Mar 11 21:44:56 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100224.1)
  MachineType: Hewlett-Packard HP Compaq dc5750 Microtower
  NonfreeKernelModules: nvidia
  Package: compiz 1:0.8.4-0ubuntu13
  PackageArchitecture: all
  PciDisplay: 02:00.0 VGA compatible controller [0300]: nVidia Corporation G94 
[GeForce 9600 GT] [10de:0622] (rev a1)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-rt 
root=UUID=318b5b88-1168-482d-9758-22d2940f076b ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.153-rt
  RelatedPackageVersions:
   xserver-xorg 1:7.5+3ubuntu1
   libgl1-mesa-glx 7.7-4ubuntu1
   libdrm2 2.4.18-1ubuntu2
   xserver-xorg-video-intel 2:2.9.1-1ubuntu12
   xserver-xorg-video-ati 1:6.12.191-1ubuntu1
  SourcePackage: compiz
  Uname: Linux 2.6.31-10-rt x86_64
  dmi.bios.date: 08/07/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E3 v02.35
  dmi.board.name: 0A64h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC7011NMX
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E3v02.35:bd08/07/2008:svnHewlett-Packard:pnHPCompaqdc5750Microtower:pvr:rvnHewlett-Packard:rn0A64h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq dc5750 Microtower
  dmi.sys.vendor: Hewlett-Packard
  glxinfo: Error: [Errno 2] No such file or directory
  system: distro = Ubuntu, architecture = x86_64, kernel = 2.6.31-10-rt

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

-- 
Mailing list: https://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 1216167] Re: inkscape crashed with SIGSEGV in pathv_to_linear_and_cubic_beziers()

[Johan Engelen]

Perhaps this call
void PathManipulator::_createControlPointsFromGeometry()
{
//...
Geom::PathVector pathv = 
pathv_to_linear_and_cubic_beziers(_spcurve-get_pathvector());

If the _spcurve has been deleted by someone else, the
_spcurve-get_pathvector() will return a corrupted pointer and will
crash the program on first use in pathv_to_linear_and_cubic_beziers.

?

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

Title:
  inkscape crashed with SIGSEGV in pathv_to_linear_and_cubic_beziers()

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  :(

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: inkscape 0.48.4-1ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-3.6-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Aug 24 02:53:35 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-07-27 (27 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x7c47ed 
_Z33pathv_to_linear_and_cubic_beziersRKSt6vectorIN4Geom4PathESaIS1_EE+45:   
mov(%rsi),%rdi
   PC (0x007c47ed) ok
   source (%rsi) (0x0010) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   pathv_to_linear_and_cubic_beziers(std::vectorGeom::Path, 
std::allocatorGeom::Path  const) ()
   Inkscape::UI::PathManipulator::_createControlPointsFromGeometry() ()
   Inkscape::UI::PathManipulator::_externalChange(unsigned int) ()
   
Inkscape::XML::CompositeNodeObserver::notifyAttributeChanged(Inkscape::XML::Node,
 unsigned int, Inkscape::Util::ptr_sharedchar, 
Inkscape::Util::ptr_sharedchar) ()
   Inkscape::XML::SimpleNode::setAttribute(char const*, char const*, bool) ()
  Title: inkscape crashed with SIGSEGV in pathv_to_linear_and_cubic_beziers()
  UpgradeStatus: Upgraded to saucy on 2013-08-04 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 1216167] Re: inkscape crashed with SIGSEGV in pathv_to_linear_and_cubic_beziers()

[Johan Engelen]

I can't find anything obvious that is wrong in the code of the top 3 functions 
of the stack trace.
One thing to try is if pathv_to_linear_and_cubic_beziers is OK if the argument 
is a PathVector with an empty Path in it.
PathVector pv;
pv.push_back(Path());
pathv_to_linear_and_cubic_beziers(pv);

Windows build is broken so cannot try it right now.

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

Title:
  inkscape crashed with SIGSEGV in pathv_to_linear_and_cubic_beziers()

Status in Inkscape: A Vector Drawing Tool:
  New
Status in “inkscape” package in Ubuntu:
  New

Bug description:
  :(

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: inkscape 0.48.4-1ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-3.6-generic 3.11.0-rc6
  Uname: Linux 3.11.0-3-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Aug 24 02:53:35 2013
  ExecutablePath: /usr/bin/inkscape
  InstallationDate: Installed on 2013-07-27 (27 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: inkscape
  SegvAnalysis:
   Segfault happened at: 0x7c47ed 
_Z33pathv_to_linear_and_cubic_beziersRKSt6vectorIN4Geom4PathESaIS1_EE+45:   
mov(%rsi),%rdi
   PC (0x007c47ed) ok
   source (%rsi) (0x0010) not located in a known VMA region (needed 
readable region)!
   destination %rdi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   pathv_to_linear_and_cubic_beziers(std::vectorGeom::Path, 
std::allocatorGeom::Path  const) ()
   Inkscape::UI::PathManipulator::_createControlPointsFromGeometry() ()
   Inkscape::UI::PathManipulator::_externalChange(unsigned int) ()
   
Inkscape::XML::CompositeNodeObserver::notifyAttributeChanged(Inkscape::XML::Node,
 unsigned int, Inkscape::Util::ptr_sharedchar, 
Inkscape::Util::ptr_sharedchar) ()
   Inkscape::XML::SimpleNode::setAttribute(char const*, char const*, bool) ()
  Title: inkscape crashed with SIGSEGV in pathv_to_linear_and_cubic_beziers()
  UpgradeStatus: Upgraded to saucy on 2013-08-04 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

-- 
Mailing list: https://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 885592] Re: No parent folder button in Nautilus

[Johan Boulé]

I just find it amazing there's are buttons for Go to previous visited
location and Go to next visited location, but no way to go one level
up in the tree ... come on, it's a tree browser, not some web browser!

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

Title:
  No parent folder button in Nautilus

Status in Nautilus:
  New
Status in “nautilus” package in Ubuntu:
  Triaged

Bug description:
  After update to oneiric, I don't see any easy way (read: toolbar
  button) to navigate to the parent folder. There is a menu entry, and
  there are keyboard shortcuts, but neither gives an easy way to quickly
  navigate up in the directory tree with the mouse (in particular if you
  want to go up two or three levels).

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Thu Nov  3 09:49:25 2011
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (17 days ago)

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

-- 
Mailing list: https://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 166371] Re: Illustrator CS SVG won't load: namespace URIs in entities

[Johan Engelen]

backported in r9985.
Please test.

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

Title:
  Illustrator CS SVG won't load: namespace URIs in entities

Status in Inkscape: A Vector Drawing Tool:
  Fix Committed
Status in “inkscape” package in Ubuntu:
  Triaged

Bug description:
  Opening an SVG exported from Illustrator CS on Windows
  XP crashes Inkscape on Windows XP with the message:

  inkscape.exe:2296: Warning **: SVGView: error loading
  document

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

-- 
Mailing list: https://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 1243076] Re: libapache2-mod-auth-mysql is missing in 13.10 amd64

[Johan]

** Also affects: software-center
   Importance: Undecided
   Status: New

** No longer affects: software-center

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

Title:
  libapache2-mod-auth-mysql is missing in 13.10 amd64

Status in “software-center” package in Ubuntu:
  Confirmed

Bug description:
  When I search for libapache2-mod-auth-mysql I get two results
  listed:

  a) libapache2-mod-auth-mysql
  b) libapache2-mod-auth-mysql:i386

  When I click on the more information-button next to one of them, it
  states:

  Not found. There is no such package »libapache2-mod-auth-mysql« in your 
current software sources..
  (Translated from german.)

  That might even be the reason the update from 13.04 didn't finished
  yesterday, because I use/used this package in my apacha2's vhost
  config. So apaches configure check stumbeld upon invalid
  configuration, and the installation process stopped.

  This page btw states that there is such a package:
  https://launchpad.net/ubuntu/saucy/+package/libapache2-mod-auth-mysql

  --
  lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  LC_ALL=C apt-cache policy libapache2-mod-auth-mysql
  libapache2-mod-auth-mysql:
Installed: (none)
Candidate: (none)
Version table:
   4.3.9-13.1ubuntu1 0
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: software-center 13.10-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 22 09:29:26 2013
  ExecutablePath: /usr/share/software-center/software-center
  InstallationDate: Installed on 2011-11-10 (711 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/python2.7
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_DE:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-center
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (0 days ago)

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

-- 
Mailing list: https://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 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers

[Carl Johan]

@Danny
My bug turned out to be a different one, but it manifested itself similar to 
this bug. The problem came from having an external monitor connected via the 
VGA port at startup. For some reason that caused compiz to respond very slowly. 
I have solved the problem by connecting the monitor after booting into ubuntu.

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

Title:
  [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class
  hardware and 943/945 graphics controllers

Status in Mesa:
  Confirmed
Status in Release Notes for Ubuntu:
  Invalid
Status in “mesa” package in Ubuntu:
  Fix Released
Status in “nux” package in Ubuntu:
  Fix Released
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  After the upgrade to Mesa 9.2.0 unity is barely usable.
  Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, 
using 100% cpu.

  A downgrade to mesa 9.1.6-2ubuntu2 restores full performance.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgl1-mesa-glx 9.2-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Sep  9 01:51:45 2013
  DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0110]
  InstallationDate: Installed on 2013-09-07 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago)
  dmi.bios.date: 12/01/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: U90/U100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Ver.001
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: Ver.001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001:
  dmi.product.name: U90/U100
  dmi.product.version: Ver.001
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Sep  9 01:46:55 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1001 
   vendor HSD
  xserver.version: 2:1.14.2.901-2ubuntu4

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

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