[Desktop-packages] [Bug 2062173] Re: Apparmor denies updating namespace with ecryptfs

[Zygmunt Krynicki]

The fix has landed in snapd so it will be available in the latest/edge
channel of snapd snap. If you refresh snapd with:

snap refresh --edge snapd

Then the fix will be immediately active.

You should refresh back to stable after the 2.63 release, unless you are
comfortable daily-driving possibly unstable software.

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

Title:
  Apparmor denies updating namespace with ecryptfs

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  In Progress

Bug description:
  Noticed on Ubuntu 23.10. Started misbehaving on April 17th 2024.

  $ snap info chromium
  ...
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: today at 08:58 CEST
  channels:
latest/stable:123.0.6312.122 2024-04-15 (2821) 168MB -
  ...

  
  When running chromium, it complains about not being able to open my home dir:
  cannot update snap namespace: cannot expand mount entry (none 
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 
0): cannot use invalid home directory "/home/tannerli": permission denied
  snap-update-ns failed with code 1

  AppArmor log shows that access to ecryptfs private folder was denied:

  Apr 18 13:13:21 hostname kernel: audit: type=1400
  audit(1713438801.579:437): apparmor="DENIED" operation="open"
  class="file" profile="snap-update-ns.chromium"
  name="/home/.ecryptfs/tannerli/.Private/" pid=32412 comm="5"
  requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

  
  I found out, that, under /var/lib/snapd/apparmor/profiles, while 
snap.chromium.chromium has the line
  owner @{HOMEDIRS}/.ecryptfs/*/.Private/ r,

  the file snap-update-ns.chromium does _not_ have the line. Adding it
  and reloading the profile allows chromium to start again.

  I'm nowhere near experienced enough to tell whether this line should
  be added by default or something else went wrong on my machine.

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


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

[Desktop-packages] [Bug 2062173] Re: Apparmor denies updating namespace with ecryptfs

[Zygmunt Krynicki]

This is fixed by https://github.com/snapcore/snapd/pull/13857

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

** Changed in: chromium-browser (Ubuntu)
   Status: New => Invalid

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

Title:
  Apparmor denies updating namespace with ecryptfs

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  In Progress

Bug description:
  Noticed on Ubuntu 23.10. Started misbehaving on April 17th 2024.

  $ snap info chromium
  ...
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: today at 08:58 CEST
  channels:
latest/stable:123.0.6312.122 2024-04-15 (2821) 168MB -
  ...

  
  When running chromium, it complains about not being able to open my home dir:
  cannot update snap namespace: cannot expand mount entry (none 
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 
0): cannot use invalid home directory "/home/tannerli": permission denied
  snap-update-ns failed with code 1

  AppArmor log shows that access to ecryptfs private folder was denied:

  Apr 18 13:13:21 hostname kernel: audit: type=1400
  audit(1713438801.579:437): apparmor="DENIED" operation="open"
  class="file" profile="snap-update-ns.chromium"
  name="/home/.ecryptfs/tannerli/.Private/" pid=32412 comm="5"
  requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

  
  I found out, that, under /var/lib/snapd/apparmor/profiles, while 
snap.chromium.chromium has the line
  owner @{HOMEDIRS}/.ecryptfs/*/.Private/ r,

  the file snap-update-ns.chromium does _not_ have the line. Adding it
  and reloading the profile allows chromium to start again.

  I'm nowhere near experienced enough to tell whether this line should
  be added by default or something else went wrong on my machine.

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


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

[Desktop-packages] [Bug 2062330] Re: Chromium fails to start with "invalid home directory"

[Zygmunt Krynicki]

This is fixed by https://github.com/snapcore/snapd/pull/13857

** Changed in: chromium-browser (Ubuntu)
   Status: New => In Progress

** Changed in: chromium-browser (Ubuntu)
   Status: In Progress => Invalid

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

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

Title:
  Chromium fails to start with "invalid home directory"

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  In Progress

Bug description:
  As of this morning chromium failed to launch, a problem which I've
  never had before.

  When I run from command line, I get this:
  $ chromium
  ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded 
(failed to map segment from shared object): ignored.
  cannot update snap namespace: cannot expand mount entry (none 
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 
0): cannot use invalid home directory "/home/macho": permission denied
  snap-update-ns failed with code 1

  Here is some more info:

  $ ls -la /home | grep macho
  drwx-- 34 macho macho 12288 Apr 18 08:55 macho

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: 2 days ago, at 01:07 EDT
  channels:
latest/stable:123.0.6312.122 2024-04-15 (2821) 168MB -
latest/candidate: 124.0.6367.60  2024-04-17 (2828) 169MB -
latest/beta:  124.0.6367.60  2024-04-16 (2827) 169MB -
latest/edge:  125.0.6420.3   2024-04-17 (2829) 170MB -
  installed:  123.0.6312.122(2821) 168MB -

  $ dpkg -l libgtk3-nocsd0
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name Version  Architecture Description
  
+++---->
  ii  libgtk3-nocsd0:amd64 3-1ubuntu2   amd64Library to disable Gtk+ 3 
cl

  Happy to provide any further info needed. This is on ubuntu 23.10

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


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

[Desktop-packages] [Bug 2062173] Re: Apparmor denies updating namespace with ecryptfs

[Zygmunt Krynicki]

** Changed in: snapd (Ubuntu)
 Assignee: (unassigned) => Zygmunt Krynicki (zyga)

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

Title:
  Apparmor denies updating namespace with ecryptfs

Status in chromium-browser package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  Noticed on Ubuntu 23.10. Started misbehaving on April 17th 2024.

  $ snap info chromium
  ...
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: today at 08:58 CEST
  channels:
latest/stable:123.0.6312.122 2024-04-15 (2821) 168MB -
  ...

  
  When running chromium, it complains about not being able to open my home dir:
  cannot update snap namespace: cannot expand mount entry (none 
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 
0): cannot use invalid home directory "/home/tannerli": permission denied
  snap-update-ns failed with code 1

  AppArmor log shows that access to ecryptfs private folder was denied:

  Apr 18 13:13:21 hostname kernel: audit: type=1400
  audit(1713438801.579:437): apparmor="DENIED" operation="open"
  class="file" profile="snap-update-ns.chromium"
  name="/home/.ecryptfs/tannerli/.Private/" pid=32412 comm="5"
  requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000

  
  I found out, that, under /var/lib/snapd/apparmor/profiles, while 
snap.chromium.chromium has the line
  owner @{HOMEDIRS}/.ecryptfs/*/.Private/ r,

  the file snap-update-ns.chromium does _not_ have the line. Adding it
  and reloading the profile allows chromium to start again.

  I'm nowhere near experienced enough to tell whether this line should
  be added by default or something else went wrong on my machine.

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


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

[Desktop-packages] [Bug 2062330] Re: Chromium fails to start with "invalid home directory"

[Zygmunt Krynicki]

** Changed in: snapd (Ubuntu)
 Assignee: (unassigned) => Zygmunt Krynicki (zyga)

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

Title:
  Chromium fails to start with "invalid home directory"

Status in chromium-browser package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  As of this morning chromium failed to launch, a problem which I've
  never had before.

  When I run from command line, I get this:
  $ chromium
  ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded 
(failed to map segment from shared object): ignored.
  cannot update snap namespace: cannot expand mount entry (none 
$HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 
0): cannot use invalid home directory "/home/macho": permission denied
  snap-update-ns failed with code 1

  Here is some more info:

  $ ls -la /home | grep macho
  drwx-- 34 macho macho 12288 Apr 18 08:55 macho

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  store-url: https://snapcraft.io/chromium
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: latest/stable
  refresh-date: 2 days ago, at 01:07 EDT
  channels:
latest/stable:123.0.6312.122 2024-04-15 (2821) 168MB -
latest/candidate: 124.0.6367.60  2024-04-17 (2828) 169MB -
latest/beta:  124.0.6367.60  2024-04-16 (2827) 169MB -
latest/edge:  125.0.6420.3   2024-04-17 (2829) 170MB -
  installed:  123.0.6312.122(2821) 168MB -

  $ dpkg -l libgtk3-nocsd0
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name Version  Architecture Description
  
+++---->
  ii  libgtk3-nocsd0:amd64 3-1ubuntu2   amd64Library to disable Gtk+ 3 
cl

  Happy to provide any further info needed. This is on ubuntu 23.10

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


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

[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory

[Zygmunt Krynicki]

This bug is now well-understood and a fix is proposed in:
https://github.com/snapcore/snapd/pull/13853

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

Title:
  chromium fails to start with non-standard home directory

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Triaged

Bug description:
  CURRENT WORKAROUND
  --

  snap disconnect chromium:dot-local-share-applications
  snap disconnect chromium:dot-local-share-icons

  Those are just "quality of life" interfaces (c.f. LP:1732482) that
  most users probably do not even use, disconnecting them will cause no
  breakage. (Of course, a proper diagnosis and fix is due.)

  ORIGINAL REPORT
  ---

  cannot update snap namespace: cannot expand mount entry (none
  $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-
  dir=$HOME 0 0): cannot use invalid home directory
  "/home/department/user_name": permission denied

  Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory 
/home/department/user_name
  Used to work fine up to last week.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Apr 17 10:32:18 2024
  InstallationDate: Installed on 2017-03-24 (2580 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   206  Error   2024-04-16T19:08:43+02:00  2024-04-16T19:16:51+02:00  Remove 
"chromium" snap
   207  Done2024-04-16T19:17:27+02:00  2024-04-16T19:18:44+02:00  Remove 
"chromium" snap
   208  Done2024-04-16T19:18:46+02:00  2024-04-16T19:19:47+02:00  Install 
"chromium" snap
   209  Done2024-04-17T10:31:58+02:00  2024-04-17T10:32:02+02:00  Connect 
chromium:password-manager-service to snapd:password-manager-service
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory

[Zygmunt Krynicki]

We are still debugging it, it's not this. It's related to HOMEDIRS
tunable and variable expansion, somehow.

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

Title:
  chromium fails to start with non-standard home directory

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Triaged

Bug description:
  CURRENT WORKAROUND
  --

  snap disconnect chromium:dot-local-share-applications
  snap disconnect chromium:dot-local-share-icons

  Those are just "quality of life" interfaces (c.f. LP:1732482) that
  most users probably do not even use, disconnecting them will cause no
  breakage. (Of course, a proper diagnosis and fix is due.)

  ORIGINAL REPORT
  ---

  cannot update snap namespace: cannot expand mount entry (none
  $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-
  dir=$HOME 0 0): cannot use invalid home directory
  "/home/department/user_name": permission denied

  Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory 
/home/department/user_name
  Used to work fine up to last week.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Apr 17 10:32:18 2024
  InstallationDate: Installed on 2017-03-24 (2580 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   206  Error   2024-04-16T19:08:43+02:00  2024-04-16T19:16:51+02:00  Remove 
"chromium" snap
   207  Done2024-04-16T19:17:27+02:00  2024-04-16T19:18:44+02:00  Remove 
"chromium" snap
   208  Done2024-04-16T19:18:46+02:00  2024-04-16T19:19:47+02:00  Install 
"chromium" snap
   209  Done2024-04-17T10:31:58+02:00  2024-04-17T10:32:02+02:00  Connect 
chromium:password-manager-service to snapd:password-manager-service
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 2061981] Re: chromium fails to start with non-standard home directory

[Zygmunt Krynicki]

We've debugged this issue and the problem is caused by apparmor re-
execution and configuration files being loaded from read-only snapd
squashfs, thus making HOMEDIRS customization invisible.

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

Title:
  chromium fails to start with non-standard home directory

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  CURRENT WORKAROUND
  --

  snap disconnect chromium:dot-local-share-applications
  snap disconnect chromium:dot-local-share-icons

  Those are just "quality of life" interfaces (c.f. LP:1732482) that
  most users probably do not even use, disconnecting them will cause no
  breakage. (Of course, a proper diagnosis and fix is due.)

  ORIGINAL REPORT
  ---

  cannot update snap namespace: cannot expand mount entry (none
  $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-
  dir=$HOME 0 0): cannot use invalid home directory
  "/home/department/user_name": permission denied

  Fails to start on Ubuntu 22.04 for users with 'non-standard' home directory 
/home/department/user_name
  Used to work fine up to last week.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2.22.04.1
  ProcVersionSignature: Ubuntu 6.5.0-27.28~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-27-generic x86_64
  NonfreeKernelModules: zfs nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed Apr 17 10:32:18 2024
  InstallationDate: Installed on 2017-03-24 (2580 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   206  Error   2024-04-16T19:08:43+02:00  2024-04-16T19:16:51+02:00  Remove 
"chromium" snap
   207  Done2024-04-16T19:17:27+02:00  2024-04-16T19:18:44+02:00  Remove 
"chromium" snap
   208  Done2024-04-16T19:18:46+02:00  2024-04-16T19:19:47+02:00  Install 
"chromium" snap
   209  Done2024-04-17T10:31:58+02:00  2024-04-17T10:32:02+02:00  Connect 
chromium:password-manager-service to snapd:password-manager-service
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)

[Zygmunt Krynicki]

The snapd side of this fix is baking in
https://github.com/snapcore/snapd/pull/9530

** Changed in: snapd
   Status: Confirmed => In Progress

** Changed in: snapd
 Assignee: (unassigned) => Zygmunt Krynicki (zyga)

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

Title:
  Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X
  display)

Status in Mutter:
  Unknown
Status in snapd:
  In Progress
Status in mutter package in Ubuntu:
  In Progress
Status in snapd package in Ubuntu:
  Won't Fix
Status in mutter source package in Groovy:
  In Progress
Status in snapd source package in Groovy:
  Won't Fix

Bug description:
  I'm trying to run chromium installed via snap in Ubuntu 20.10 when
  running Ubuntu Wayland session. Unfortunately, chromium wouldn't
  start:

  > chromium 
  [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

  I am able to run Firefox just fine (assuming that Firefox still runs
  on xwayland) and also Intellij snap works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 25 09:45:16 2020
  InstallationDate: Installed on 2016-09-05 (1480 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Snap: chromium 85.0.4183.121 (latest/stable)
  SnapSource: ubuntu/+source/chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1850282] Re: snap cannot be run while being upgraded − no user feedback

[Zygmunt Krynicki]

This is still in development but there's some actual progress recently.
Complete development history is visible in
https://github.com/snapcore/snapd/projects/3

We are aiming to release a, still disabled by default, but much improved
version of this as either 2.47 or 2.48, depending on when the reviews
arrive.

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

Title:
  snap cannot be run while being upgraded − no user feedback

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded to Ubuntu 19.10 with the new snap version of
  Chromium a week or two ago

  On starting my system today, I found that Chromium had disappeared
  from the launcher and wasn't even in the apps list.   using the
  command 'chromium' didn't work either, giving me the message that
  chromium wasn't installed.   "You can install it using snap install
  chromium".  Then when I try to install it, I get the message "chromium
  is already installed".

  After about 10 minutes of digging around, I discovered that the
  chromium snap was disabled.  I couldn't enable it because it was being
  refreshed.

  Come on!  this is unacceptable behaviour for any tool but especially a
  browser which must be one of the most heavily used applications on
  Ubuntu.  This will really hit the reputation of ubuntu with any user
  who has to take maybe more than 10 minutes to discover the problem, or
  may never discover it - Chromium may just mysteriously reappear some
  time later.

  Desired behaviour:   Never disappear.  Allow refresh to happen under the 
covers, transparently (as it used to with apt).
  Minimally acceptable behaviour: never disappear, but display a message 
"chromium is being refreshed.  Please try later".

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  channels:
stable:78.0.3904.70 2019-10-29 (920) 160MB -
candidate: 78.0.3904.70 2019-10-29 (920) 160MB -
beta:  78.0.3904.70 2019-10-22 (907) 165MB -
edge:  79.0.3941.4  2019-10-21 (905) 159MB -
  installed:   78.0.3904.70(917) 167MB disabled

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

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

[Desktop-packages] [Bug 1876083] Re: chromium snap from focal fails DNS lookups, or delays them (ipv6)

[Zygmunt Krynicki]

I'm marking this as medium as we should handle ipv6 better and this may
help to determine if there's a broad issue in the base snaps, either on
the configuration side or in the set of packages contained.

** Changed in: snapd
   Status: New => Triaged

** Changed in: snapd
   Importance: Undecided => Medium

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

Title:
  chromium snap from focal fails DNS lookups, or delays them (ipv6)

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When working with the chromium snap included in focal, it sometimes
  takes a few seconds to lookup an URL, sometimes it cannot resolve the
  hostname of the URL at all.

  Doing the same browsing using firefox doesn't show such behavior, no
  timeouts, no failed lookups, no delays.

  Any way how to debug that?  That is using IPv6 only.

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

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

[Desktop-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded

[Zygmunt Krynicki]

** Changed in: snapd
   Status: In Progress => Fix Released

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

Title:
  services start before apparmor profiles are loaded

Status in AppArmor:
  Invalid
Status in snapd:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in zsys package in Ubuntu:
  Invalid
Status in apparmor source package in Focal:
  Fix Released
Status in zsys source package in Focal:
  Invalid

Bug description:
  Per discussion with Zyga in #snapd on Freenode, I have hit a race
  condition where services are being started by the system before
  apparmor has been started. I have a complete log of my system showing
  the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/.
  Restarting apparmor using `sudo systemctl restart apparmor` is enough
  to bring installed snaps back to full functionality.

  Previously, when running any snap I would receive the following in the
  terminal:

  ---
  cannot change profile for the next exec call: No such file or directory
  snap-update-ns failed with code 1: File exists
  ---

  Updated to add for Jamie:

  $ snap version
  snap2.44.2+20.04
  snapd   2.44.2+20.04
  series  16
  ubuntu  20.04
  kernel  5.4.0-21-generic

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

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

[Desktop-packages] [Bug 1849371] Re: [snap] Cannot run chromium as user www-data because home directory is /var/www

[Zygmunt Krynicki]

The limitation on HOME is well known and for now has no workaround other
than to bind mount whatever custom home directory to /home/$LOGNAME.

I'm marking this as confirmed but I think it's going to be de-duplicated
in another pass. There's already a bug for this.

** Also affects: snapd
   Importance: Undecided
   Status: New

** Changed in: snapd
   Status: New => Confirmed

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

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

Title:
  [snap] Cannot run chromium as user www-data because home directory is
  /var/www

Status in snapd:
  Confirmed
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  Since the move to snap, and upgrade to 19.10, I can no longer use
  headless-chromium to do automated conversions.

  The script, as currently run by Apache (user www-data) as a back-end
  server process is:

  /usr/bin/timeout 60 chromium-browser --no-sandbox --headless
  --disable-gpu --window-size=2048,1448 --screenshot='dummy.pdf'
  'http://localhost/[...]' 2>&1 2>&1

  This returns error 1, with:

  dconf-CRITICAL **: 19:41:17.958: unable to create directory
  '/var/www/.cache/dconf': Permission denied.  dconf will not work
  properly.

  WARNING: cannot create user data directory: cannot create 
"/var/www/snap/chromium/899": 
  mkdir /var/www/snap: permission denied
  Sorry, home directories outside of /home are not currently supported.
  See https://forum.snapcraft.io/t/11209 for details.

  So... how are we supposed to use scripted Chrome for headless work, when the 
snaps don't support it?
  This is a major blocker for me, as it completely destroys my ability to do 
any development work, because the build-toolchain for selftests relies on the 
ability of chrome to operate headless.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: MATE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wBMLToINDAxMCsWAQOANCB4KgHxoldSnycKUFS/74BxT4EAgUCBgJUAlQ+pQLMAKDyAoHCwI0AwIDYABkQhAAAa/QA4Sx5REQAKICAgICAg/ABTTVMyNEE0NTAKICAg/wBINE1DQTEzMzYyCiAgAQkCAQQAAjqA0HI4LUAQLEWABkQhAAAeAR0AclHQHiBuKFUABkQhAAAeAR0AvFLQHiC4KFVABkQhAAAejArQkCBAMSAMQFUABkQhAAAYjArQiiDgLRAQPpYABkQhAAAY0g==
   modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 
1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 
720x480 640x480 640x480 640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAlpVNWODYxMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMTY4/ABMMjBDTQogICAgICAgAMU=
   modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 
640x480 640x480 640x480 720x400
  DRM.card0-HDMI-A-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAlpVNWNjIyMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMjI2/ABMMjBDTQogICAgICAgAM8=
   modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 
640x480 640x480 640x480 720x400
  Date: Tue Oct 22 19:48:51 2019
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sdb1  ext4   1.8T  491G  1.3T  29% /home
   tmpfs  tmpfs   32G  927M   31G   3% /dev/shm
   /dev/sdb1  ext4   1.8T  491G  1.3T  29% /home
  InstallationDate: Installed on 2017-02-03 (991 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic 
root=UUID=6ef42be7-d431-4d0d-bc57-79f7a96980ef ro
  Snap.ChromeDriverVersion:
   ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be 
preloaded (failed to map segment from shared object): ignored.
   ChromeDriver 77.0.3865.120 
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
  Snap.ChromiumVersion:
   ERROR: ld.so: object 'libgtk3-nocsd.so.0' 

[Desktop-packages] [Bug 1848753] Re: [snap] chromium times out connecting document portal with NFS home

[Zygmunt Krynicki]

** Changed in: snapd
   Status: New => Triaged

** Changed in: snapd
   Importance: Undecided => Medium

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

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

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

Title:
  [snap] chromium times out connecting document portal with NFS home

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  Triaged

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chromium cannot seem to remember accounts or
  passwords.

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

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

[Desktop-packages] [Bug 1661590] Re: GNOME Software only supports running one application from a snap

[Zygmunt Krynicki]

I just tried to reproduce the bug as outlined in the bug description. I
can confirm it is now fixed and working as expected. I'm marking the
snappy task as fix released.

** Changed in: snappy
   Status: In Progress => Fix Released

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

Title:
  GNOME Software only supports running one application from a snap

Status in GNOME Software:
  Fix Released
Status in Snappy:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released
Status in gnome-software source package in Artful:
  Won't Fix
Status in gnome-software source package in Bionic:
  Fix Released

Bug description:
  HOW TO REPRODUCE:

  1. Install LibreOffice snap ('nonfree' tag) from Ubuntu Software.
  2. Click on the 'Launch' button once you have it installed.

  WHAT IS EXPECTED: 
  It should launch the LibreOffice wizard instead of any of Writer, Calc, etc.

  WHAT ACTUALLY HAPPENS: 
  It launches LibreOffice Database.

  
  WHY THIS HAPPENS?

  Ubuntu Software probably picks the first listed command
  (libreoffice.base), as shown in

  $ snap info libreoffice
  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  tracking:stable
  installed:   5.3.0.3 (17) 374MB -
  refreshed:   2017-02-01 20:51:51 +0200 EET
  channels: 
stable:5.3.0.3 (17) 374MB -
candidate: 5.3.0.3 (17) 374MB -
beta:  5.3.0.3 (17) 374MB -
edge:  5.3.0.3 (17) 374MB -

  
  The order in snapcraft.yaml is different, so probably Snapcraft is changing 
the order (it might assume that 'libreoffice' is 'libreoffice.libreoffice', so 
it puts it further down.

  Here is snapcraft.yaml: https://git.launchpad.net/~bjoern-michaelsen
  /df-libreoffice/+git/libreoffice-snap-
  playground/tree/snapcraft.yaml?h=xenial

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

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

[Desktop-packages] [Bug 1848753] Re: [snap] chromium times out connecting document portal with NFS home

[Zygmunt Krynicki]

Ah, forgive me.

I think this bug requires someone to sit down and attempt to reproduce
it in a controlled environment. I cannot commit to do that anytime soon
as we have a number of open bugs, features we promised to deliver and a
handful of people working on the project.

I'd like to keep the bug open for the next pass of bug review that will
be done by another engineer. We are working towards reducing the number
of NEW, INPROGRESS and finally OPEN bugs so that we can devote more
attention to particular cases and work on debugging them properly.

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

Title:
  [snap] chromium times out connecting document portal with NFS home

Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  New

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chromium cannot seem to remember accounts or
  passwords.

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

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

[Desktop-packages] [Bug 1848753] Re: [snap] chromium times out connecting document portal with NFS home

[Zygmunt Krynicki]

It seems that loka 29 20:02:33 koira xdg-document-portal[16225]: error: Failed 
to load db: invalid gvdb header
 is relevant. I wonder if the database, whatever the format, is somehow corrupt.

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

Title:
  [snap] chromium times out connecting document portal with NFS home

Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  New

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chromium cannot seem to remember accounts or
  passwords.

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

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

[Desktop-packages] [Bug 1835024] Re: Links triggered within most snap apps open in a separate browser session

[Zygmunt Krynicki]

Given Maciek's comment about reproducing this with classic snaps I'm
marking this as confirmed.

Interested parties can keep track of
https://github.com/snapcore/snapd/pull/7659 where this issue may be
resolved for _some_ snaps but if confirmed, the same cause is affecting
all the strictly confined apps.

Marking as confirmed.

** Changed in: snapd
   Status: New => Confirmed

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

Title:
  Links triggered within most snap apps open in a separate browser
  session

Status in snapd:
  Confirmed
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Hi,
  I've recently made a clean install of Ubuntu 19.10 (development release) and 
have noticed that whenever I try to open a link from one of the snap apps 
(being it Slack or Skype) the links although opened in the default browser are 
being opened in a separate session of the web browser.

  I am using Firefox and it is installed as a regular deb package
  (default).

  This is wrong and causes issues with history, sessions and settings
  not being shared between these windows. Now I have the default browser
  I use + a separate session for Slack and another one for Skype. Not to
  mention Firefox also acts just like another Slack/Skype window so dash
  displays these as two instances of the same app.

  To reproduce:
  * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same 
behaviour).
  * Confirm FFox is installed as a regular deb package.
  * Install I suppose almost any snap app, although I've only reproduced this 
with Slack and Skype and haven't tried to install other apps.

  System monitor also seems to be installed but when trying to open links from 
the about window - translators - individual names, it seems to do nothing.
  On the other hand Gnome calculator which is also installed as a snap package 
opens the link in the about dialog correctly = in my default browser session.

  ```
  :~# which gnome-calculator 
  /snap/bin/gnome-calculator
  ```

  Thank you very much for looking into that.

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

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

[Desktop-packages] [Bug 1835024] Re: Links triggered within most snap apps open in a separate browser session

[Zygmunt Krynicki]

Recently we noticed that XDG_RUNTIME_DIR is set to a custom value for
both strictly and classically confined snap applications. It may be the
case that adjusting the runtime directory for a test shows that a remote
window is not opened.

I'm not proposing a solution yet but perhaps we can at least understand
the cause.

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

Title:
  Links triggered within most snap apps open in a separate browser
  session

Status in snapd:
  New
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Hi,
  I've recently made a clean install of Ubuntu 19.10 (development release) and 
have noticed that whenever I try to open a link from one of the snap apps 
(being it Slack or Skype) the links although opened in the default browser are 
being opened in a separate session of the web browser.

  I am using Firefox and it is installed as a regular deb package
  (default).

  This is wrong and causes issues with history, sessions and settings
  not being shared between these windows. Now I have the default browser
  I use + a separate session for Slack and another one for Skype. Not to
  mention Firefox also acts just like another Slack/Skype window so dash
  displays these as two instances of the same app.

  To reproduce:
  * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same 
behaviour).
  * Confirm FFox is installed as a regular deb package.
  * Install I suppose almost any snap app, although I've only reproduced this 
with Slack and Skype and haven't tried to install other apps.

  System monitor also seems to be installed but when trying to open links from 
the about window - translators - individual names, it seems to do nothing.
  On the other hand Gnome calculator which is also installed as a snap package 
opens the link in the about dialog correctly = in my default browser session.

  ```
  :~# which gnome-calculator 
  /snap/bin/gnome-calculator
  ```

  Thank you very much for looking into that.

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

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

[Desktop-packages] [Bug 1848753] Re: [snap] chromium times out connecting document portal with NFS home

[Zygmunt Krynicki]

Hello there.

loka 24 20:56:42 koira audit[12568]: AVC apparmor="DENIED"
operation="file_mmap" profile="/snap/snapd/4992/usr/lib/snapd/snap-
confine" name="/usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0" pid=12568
comm="snap-confine" requested_mask="m" denied_mask="m" fsuid=0 ouid=0

I'm very curious how this can happen. I can only suspect an
LD_LIBRARY_PATH or LD_PRELOAD variables is set and snap-confine is
actually honouring it somehow, despite that not normally affecting
AT_SECURE binaries

loka 24 20:56:42 koira audit[1068]: USER_AVC pid=1068 uid=105
auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/"
interface="org.freedesktop.DBus.ObjectManager"
member="GetManagedObjects" mask="send" name="org.bluez" pid=12568
label="snap.chromium.chromium"

This denial is fro the chromium snap and could probably be resolved by
connecting the "bluez" interface to chromium.

Neither of those explain why NFS is slow in this specific case that you
are trying. I wonder if this is some sort of remote side logging that
fails because of LAN not providing reverse IP mapping information.

Did you perhaps look at the NFS server logs?

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

Title:
  [snap] chromium times out connecting document portal with NFS home

Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Incomplete
Status in snapd package in Ubuntu:
  New

Bug description:
  I have my /home folder shared via NFS from a local server one floor
  below in my house. The server runs Ubuntu 18.04.

  After starting a snapped version of chromium-browser in my Ubuntu
  19.10 the document portal timeouts like this:

  XXX@koira:~$ chromium-browser
  2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document 
portal: Failed to activate service 'org.freedesktop.portal.Documents': timed 
out (service_start_timeout=12ms)

  After the timeout my chromium cannot seem to remember accounts or
  passwords.

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

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

[Desktop-packages] [Bug 1744584] Re: Exclude Snap .cache from Dejadup backups

[Zygmunt Krynicki]

I'm closing the snapd side of the issue. Thank you for improving deja-
dup everyone!

** Changed in: snappy
   Status: New => Invalid

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

Title:
  Exclude Snap .cache from Dejadup backups

Status in Déjà Dup:
  Fix Released
Status in Snappy:
  Invalid
Status in deja-dup package in Ubuntu:
  Fix Released

Bug description:
  The official Backup solution offered by Ubuntu does not support
  advanced whitelisting/blacklisting of directories. With the
  introduction of snaps, the cache of the snap apps is stored in ~/snaps
  /APP-NAME/VERSION/.cache. Unfortunately this means that Deja dup can't
  be configured to exclude these directories from backups.

  Since 2009, there have been several requests from the community to add
  support of advanced include/exclude support in Dejadup but there is no
  progress. Do you have any plans to provide minimum support for
  excluding specific snap folders such as .cache?

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1744584/+subscriptions

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

[Desktop-packages] [Bug 1809729] Re: Removing a snap triggers 'Starting scheduled backup' notification

[Zygmunt Krynicki]

I suspect this is caused by `udevadm trigger` and `udevadm settle` that
snapd invokes, for some snaps, depending on how they are made, when they
are removed.

There are multiple other bugs related to various issues (including
desktop crashing or minor annoyances) related to udev. I've added a tag
to this bug to ease discovery of such bugs for other developers.

** Project changed: snappy => snapd

** Changed in: snapd
   Status: New => Triaged

** Changed in: snapd
   Importance: Undecided => High

** Tags added: udev

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

Title:
  Removing a snap triggers 'Starting scheduled backup' notification

Status in snapd:
  Triaged
Status in deja-dup package in Ubuntu:
  New

Bug description:
  Removing a snap triggers the 'Starting scheduled backup' notification
  then (because I don't have the USB stick plugged in) the `Backup
  Failed: Error creating directory /media/adam/Adam Eveleigh: Permission
  denied` dialogue box. I am scheduled a backup, but should this
  dialogue box be opened every time I remove a snap?

  `journalctl -f` output for `snap remove notepad-plus-plus`:
  https://paste.ubuntu.com/p/Ksy4cmF6ZJ/

  ```
  $ snap version
  snap2.36.3+git1065.557f8c3~ubuntu16.04.1
  snapd   2.36.3+git1065.557f8c3~ubuntu16.04.1
  series  16
  ubuntu  18.10
  kernel  4.18.0-13-generic
  $ snap info core
  tracking: edge
  refresh-date: today at 11:20 GMT
  channels:  
stable:16-2.36.3 (6130) 93MB -
candidate: 16-2.36.3 (6130) 93MB -
beta:  16-2.36.3 (6130) 93MB -
edge:  16-2.36.3+git1065.557f8c3 (6199) 95MB -
  installed:   16-2.36.3+git1065.557f8c3 (6199) 95MB core
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: deja-dup 38.0-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: binder_linux ashmem_linux
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 25 11:24:59 2018
  InstallationDate: Installed on 2017-08-03 (508 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to cosmic on 2018-10-21 (65 days ago)

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

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

[Desktop-packages] [Bug 1835024] Re: Links triggered within most snap apps open in a separate browser session

[Zygmunt Krynicki]

Hello

I've tried to reproduce this on a fully up-to-date Ubuntu 19.10 system,
using gnome-calculator. I use firefox as my defualt browser. I clicked
on the credits link in gnome-calculator and I got a new tab in my
existing session.

I'm marking this bug as incomplete. Please clarify if the issue still
persists for you.

** Project changed: snappy => snapd

** Changed in: snapd
   Status: New => Incomplete

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

Title:
  Links triggered within most snap apps open in a separate browser
  session

Status in snapd:
  Incomplete
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Hi,
  I've recently made a clean install of Ubuntu 19.10 (development release) and 
have noticed that whenever I try to open a link from one of the snap apps 
(being it Slack or Skype) the links although opened in the default browser are 
being opened in a separate session of the web browser.

  I am using Firefox and it is installed as a regular deb package
  (default).

  This is wrong and causes issues with history, sessions and settings
  not being shared between these windows. Now I have the default browser
  I use + a separate session for Slack and another one for Skype. Not to
  mention Firefox also acts just like another Slack/Skype window so dash
  displays these as two instances of the same app.

  To reproduce:
  * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same 
behaviour).
  * Confirm FFox is installed as a regular deb package.
  * Install I suppose almost any snap app, although I've only reproduced this 
with Slack and Skype and haven't tried to install other apps.

  System monitor also seems to be installed but when trying to open links from 
the about window - translators - individual names, it seems to do nothing.
  On the other hand Gnome calculator which is also installed as a snap package 
opens the link in the about dialog correctly = in my default browser session.

  ```
  :~# which gnome-calculator 
  /snap/bin/gnome-calculator
  ```

  Thank you very much for looking into that.

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

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

[Desktop-packages] [Bug 1838038] Re: [snap] Chromium does not work with .local mdns/avahi name resolution

[Zygmunt Krynicki]

I see, it needs to be debugged further to determine what the problem is.
Unfortunately due to the design of snapd's handling of /etc (shared with
the host, with small exceptions), it is possible that the solution is
complex and could take some time to implement.

** Changed in: snapd
   Status: New => Triaged

** Changed in: snapd
   Importance: Undecided => Medium

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

Title:
  [snap] Chromium does not work with .local mdns/avahi name resolution

Status in snapd:
  Triaged
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chromium-does-not-
  work-with-local-mdns-avahi-name-resolution/12483)

  The current chromium snap does not allow to open any .local urls.

  This is most likely caused by https://forum.snapcraft.io/t/no-mdns-
  support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603.

  With the removal of the chromium deb and the switch to a snap-only
  deployment for this browser this is a pretty solid regression that
  should be addressed…

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

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

[Desktop-packages] [Bug 1838038] Re: [snap] Chromium does not work with .local mdns/avahi name resolution

[Zygmunt Krynicki]

I just attempted to reproduce this issue with:

- snapd 2.24~pre2 on Ubuntu 19.04
- chromium snap revision 861

I installed apache2 locally via apt and opened the link "fyke.local" in
both Firefox and Chromium. Note that Firefox accepted just fyke.local
and did the right thing while Chromium would search google unless I
spelled the link as "http://fyke.local;.

Perhaps this issue has been fixed since, marking as incomplete.

** Changed in: snapd
   Status: New => Incomplete

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

Title:
  [snap] Chromium does not work with .local mdns/avahi name resolution

Status in snapd:
  Incomplete
Status in chromium-browser package in Ubuntu:
  Confirmed

Bug description:
  (initially reported at https://forum.snapcraft.io/t/chromium-does-not-
  work-with-local-mdns-avahi-name-resolution/12483)

  The current chromium snap does not allow to open any .local urls.

  This is most likely caused by https://forum.snapcraft.io/t/no-mdns-
  support-in-snaps-should-core-have-a-modified-nsswitch-conf/7603.

  With the removal of the chromium deb and the switch to a snap-only
  deployment for this browser this is a pretty solid regression that
  should be addressed…

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

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

[Desktop-packages] [Bug 1822165] Re: [snap] steam:// application links don't work in chromium

[Zygmunt Krynicki]

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

** This bug has been marked a duplicate of bug 1776873
   Whitelisted allowedURLschemes breaks some desktop apps

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

Title:
  [snap] steam:// application links don't work in chromium

Status in snapd:
  New
Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  Example of a link: steam://connect/164.132.201.196:27119
  This link is supposed to open a window or start a game in the steam 
application, but steam is not doing anything. It works in non-snap Chromium 
(tested on a new installation and a chrome prompt appeared, maybe some setting 
in my snap version is preventing this?).

  Ubuntu 18.10
  Chromium Version 73.0.3683.75 (Official Build) snap (64-bit)

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

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

[Desktop-packages] [Bug 1808959] Re: [snap] core18-based snap fails to start on Solus/fedora29

[Zygmunt Krynicki]

In absense of test systems to check this I'm marking this as incomplete.
If the reporter can confirm the issue is fixed it would help us with the
bug tracking.

** Changed in: snapd
   Status: New => Incomplete

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

Title:
  [snap] core18-based snap fails to start on Solus/fedora29

Status in snapd:
  Incomplete
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  After installation of chromium and I try to start it I get this error
  inside my terminal.

  fredu  ~  chromium 
  execv failed: No such file or directory

  System:
  Description:Solus
  Release:3.

  Chromium:   stable
  snapd:  2.36.2

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

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

[Desktop-packages] [Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)

[Zygmunt Krynicki]

I've opened a fresh bug since the one referenced above was closed.
https://gitlab.gnome.org/GNOME/gdm/issues/483

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

Title:
  Ubuntu login screen never appears when using the Nvidia driver (and
  setting WaylandEnable=false fixes it)

Status in gdm:
  Unknown
Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/483
  formerly https://gitlab.gnome.org/GNOME/gdm/issues/435

  ---

  The boot process hangs with the last message being "started bpfilter".
  There is unusual Network activity during that time. The light of the
  WiFi adapter is blinking a lot.

  I am not sure the problem is with the gdm3 package. As a matter of
  fact, I would remove it and let someone more experienced to set it.
  I'm afraid I might break something, though.

  The specific steps or actions you took that caused you to encounter the 
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
  installed.

  The behavior you expected: I expected Ubuntu 18.10 to boot normally.

  The behavior you actually encountered: The computer gets stuck in a
  command-like environment with the last message being "started
  bpfilter". You can't type any commands.

  I have found that uninstalling the Nvidia proprietary drivers by going
  into recovery mode fixes the issue.

  Booting with the earlier kernel doesn't fix the issue. Installing the
  earlier v.340 driver also doesn't fix the issue.

  This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
  boot-after-starting-gnome-display-manager-on-intel-graphic) seems
  relevant. This is where I found the "solution".

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

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

[Desktop-packages] [Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)

[Zygmunt Krynicki]

I've added some extra debugging information to an upstream bug
https://gitlab.gnome.org/GNOME/gdm/issues/435#note_499818

** Bug watch added: gitlab.gnome.org/GNOME/gdm/issues #435
   https://gitlab.gnome.org/GNOME/gdm/issues/435

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

Title:
  Ubuntu login screen never appears when using the Nvidia driver (and
  setting WaylandEnable=false fixes it)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/435

  ---

  The boot process hangs with the last message being "started bpfilter".
  There is unusual Network activity during that time. The light of the
  WiFi adapter is blinking a lot.

  I am not sure the problem is with the gdm3 package. As a matter of
  fact, I would remove it and let someone more experienced to set it.
  I'm afraid I might break something, though.

  The specific steps or actions you took that caused you to encounter the 
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
  installed.

  The behavior you expected: I expected Ubuntu 18.10 to boot normally.

  The behavior you actually encountered: The computer gets stuck in a
  command-like environment with the last message being "started
  bpfilter". You can't type any commands.

  I have found that uninstalling the Nvidia proprietary drivers by going
  into recovery mode fixes the issue.

  Booting with the earlier kernel doesn't fix the issue. Installing the
  earlier v.340 driver also doesn't fix the issue.

  This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
  boot-after-starting-gnome-display-manager-on-intel-graphic) seems
  relevant. This is where I found the "solution".

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

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

[Desktop-packages] [Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)

[Zygmunt Krynicki]

I can reproduce this issue on my 19.04 system using GTX 650. If anyone
needs debug information or to try a new package I'm happy to offer my
help.

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

Title:
  Ubuntu login screen never appears when using the Nvidia driver (and
  setting WaylandEnable=false fixes it)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/gdm/issues/435

  ---

  The boot process hangs with the last message being "started bpfilter".
  There is unusual Network activity during that time. The light of the
  WiFi adapter is blinking a lot.

  I am not sure the problem is with the gdm3 package. As a matter of
  fact, I would remove it and let someone more experienced to set it.
  I'm afraid I might break something, though.

  The specific steps or actions you took that caused you to encounter the 
problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers
  installed.

  The behavior you expected: I expected Ubuntu 18.10 to boot normally.

  The behavior you actually encountered: The computer gets stuck in a
  command-like environment with the last message being "started
  bpfilter". You can't type any commands.

  I have found that uninstalling the Nvidia proprietary drivers by going
  into recovery mode fixes the issue.

  Booting with the earlier kernel doesn't fix the issue. Installing the
  earlier v.340 driver also doesn't fix the issue.

  This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in-
  boot-after-starting-gnome-display-manager-on-intel-graphic) seems
  relevant. This is where I found the "solution".

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

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

[Desktop-packages] [Bug 1794953] Re: GNOME Calculator snap has wrong theme in live session

[Zygmunt Krynicki]

** Changed in: snapd (Ubuntu)
 Assignee: Zygmunt Krynicki (zyga) => (unassigned)

** Changed in: snapd (Ubuntu Cosmic)
 Assignee: Zygmunt Krynicki (zyga) => (unassigned)

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

Title:
  GNOME Calculator snap has wrong theme in live session

Status in snapd:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in gnome-calculator source package in Cosmic:
  Invalid
Status in snapd source package in Cosmic:
  Confirmed

Bug description:
  Running GNOME Calculator (or System Monitor, for example) runs the app
  with Adwaita theme instead of Yaru when in the live session.  This
  seems to resolve itself when used in the real session.

  Steps to reproduce:

  * Launch a live USB stick in a VM (note: you might need to use nomodeset 
until that is fixed)
  * Open any of the seeded snaps and note that the theme is wrong.

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

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

[Desktop-packages] [Bug 1794953] Re: GNOME Calculator snap has wrong theme in live session

[Zygmunt Krynicki]

** Changed in: snapd
   Status: Fix Committed => Fix Released

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

Title:
  GNOME Calculator snap has wrong theme in live session

Status in snapd:
  Fix Released
Status in gnome-calculator package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in gnome-calculator source package in Cosmic:
  Invalid
Status in snapd source package in Cosmic:
  Confirmed

Bug description:
  Running GNOME Calculator (or System Monitor, for example) runs the app
  with Adwaita theme instead of Yaru when in the live session.  This
  seems to resolve itself when used in the real session.

  Steps to reproduce:

  * Launch a live USB stick in a VM (note: you might need to use nomodeset 
until that is fixed)
  * Open any of the seeded snaps and note that the theme is wrong.

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

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

[Desktop-packages] [Bug 1794953] Re: GNOME Calculator snap has wrong theme in live session

[Zygmunt Krynicki]

** Changed in: snapd
   Status: In Progress => Fix Committed

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

Title:
  GNOME Calculator snap has wrong theme in live session

Status in snapd:
  Fix Committed
Status in gnome-calculator package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in gnome-calculator source package in Cosmic:
  Invalid
Status in snapd source package in Cosmic:
  Confirmed

Bug description:
  Running GNOME Calculator (or System Monitor, for example) runs the app
  with Adwaita theme instead of Yaru when in the live session.  This
  seems to resolve itself when used in the real session.

  Steps to reproduce:

  * Launch a live USB stick in a VM (note: you might need to use nomodeset 
until that is fixed)
  * Open any of the seeded snaps and note that the theme is wrong.

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

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

[Desktop-packages] [Bug 1794953] Re: GNOME Calculator snap has wrong theme in live session

[Zygmunt Krynicki]

I have reproduced, debugged and fixed this. The PR with the fix is at
https://github.com/snapcore/snapd/pull/5912

I will ensure this is in the next 2.36 release candidate.

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

Title:
  GNOME Calculator snap has wrong theme in live session

Status in snapd:
  In Progress
Status in gnome-calculator package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in gnome-calculator source package in Cosmic:
  Invalid
Status in snapd source package in Cosmic:
  Confirmed

Bug description:
  Running GNOME Calculator (or System Monitor, for example) runs the app
  with Adwaita theme instead of Yaru when in the live session.  This
  seems to resolve itself when used in the real session.

  Steps to reproduce:

  * Launch a live USB stick in a VM (note: you might need to use nomodeset 
until that is fixed)
  * Open any of the seeded snaps and note that the theme is wrong.

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

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

[Desktop-packages] [Bug 1794953] Re: GNOME Calculator snap has wrong theme in live session

[Zygmunt Krynicki]

** Changed in: snapd
   Status: New => In Progress

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

Title:
  GNOME Calculator snap has wrong theme in live session

Status in snapd:
  In Progress
Status in gnome-calculator package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in gnome-calculator source package in Cosmic:
  Invalid
Status in snapd source package in Cosmic:
  Confirmed

Bug description:
  Running GNOME Calculator (or System Monitor, for example) runs the app
  with Adwaita theme instead of Yaru when in the live session.  This
  seems to resolve itself when used in the real session.

  Steps to reproduce:

  * Launch a live USB stick in a VM (note: you might need to use nomodeset 
until that is fixed)
  * Open any of the seeded snaps and note that the theme is wrong.

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

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

[Desktop-packages] [Bug 1794953] Re: GNOME Calculator snap has wrong theme in live session

[Zygmunt Krynicki]

** Also affects: snapd
   Importance: Undecided
   Status: New

** Changed in: snapd
 Assignee: (unassigned) => Zygmunt Krynicki (zyga)

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

Title:
  GNOME Calculator snap has wrong theme in live session

Status in snapd:
  New
Status in gnome-calculator package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed
Status in gnome-calculator source package in Cosmic:
  Invalid
Status in snapd source package in Cosmic:
  Confirmed

Bug description:
  Running GNOME Calculator (or System Monitor, for example) runs the app
  with Adwaita theme instead of Yaru when in the live session.  This
  seems to resolve itself when used in the real session.

  Steps to reproduce:

  * Launch a live USB stick in a VM (note: you might need to use nomodeset 
until that is fixed)
  * Open any of the seeded snaps and note that the theme is wrong.

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

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

[Desktop-packages] [Bug 1702351] Re: [snap] "User installation could not be completed"

[Zygmunt Krynicki]

Hey.

Can you check if this is still affecting your system?
In addition, can you please share your /etc/nsswitch.conf 

** Changed in: snapd
   Status: New => Confirmed

** Changed in: snapd
   Status: Confirmed => Incomplete

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

Title:
  [snap] "User installation could not be completed"

Status in snapd:
  Incomplete
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  This error occurs when the user group is composed of more than one
  word. My primary group is "domain users" since my user is in AD (I use
  SSSD).

  LANG=en_US snap run libreoffice
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  $ snap info --verbose libreoffice core

  name:  libreoffice
  summary:   "LibreOffice is a powerful office suite including word processing 
and creation of spreadsheets, slideshows and databases"
  publisher: canonical
  contact:   http://www.libreoffice.org/get-help/community-support/
  description: |
LibreOffice is a powerful office suite – its clean interface and
feature-rich tools help you unleash your creativity and enhance your
productivity. LibreOffice includes several applications that make it the 
most
powerful Free and Open Source office suite on the market: Writer (word
processing), Calc (spreadsheets), Impress (presentations), Draw (vector
graphics and flowcharts), Base (databases), and Math (formula editing).
  commands:
- libreoffice.base
- libreoffice.calc
- libreoffice.draw
- libreoffice.impress
- libreoffice
- libreoffice.math
- libreoffice.writer
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  beta
  installed: 5.3.4.2 (21) 368MB 
  refreshed: 2017-07-01 14:14:41 -0300 BRT
  channels:   
stable:  5.3.2.2 (19) 375MB -
candidate:   5.3.2.2 (19) 375MB -
beta:5.3.4.2 (21) 368MB -
edge:5.3.2.2 (19) 375MB -
  ---
  name:  core
  summary:   "snapd runtime environment"
  publisher: canonical
  contact:   snappy-canonical-storeacco...@canonical.com
  description: |
The core runtime environment for snapd
  type:  core
  notes: 
private: false
confinement: strict
devmode: false
jailmode:false
trymode: false
enabled: true
broken:  false
  tracking:  stable
  installed: 16-2 (2312) 83MB 
  refreshed: 2017-04-11 09:28:54 -0300 BRT
  channels:   
stable:  16-2  (2312) 83MB -
candidate:   16-2  (2312) 83MB -
beta:16-2  (2312) 83MB -
edge:16-2.26.7 (2317) 84MB -

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

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

[Desktop-packages] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia

[Zygmunt Krynicki]

I'm marking the snappy task as fix released. We have greatly improved
nvidia support from Ubuntu 16.04 to Ubuntu 18.04 and on other
distributions as well. Please reopen if you find it still affects you
somehow.

** Changed in: snappy
   Status: In Progress => Fix Released

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

Title:
  GL interfaces seem wedged for Krita on nvidia

Status in Snappy:
  Fix Released
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  In Progress
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-304 source package in Xenial:
  In Progress
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Won't Fix
Status in nvidia-graphics-drivers-361 source package in Xenial:
  Won't Fix

Bug description:
  Krita snap segfaults. I'm running nvidia proprietary drivers on Dell
  XPS 15.

  mark@mark-XPS-15-9550:~$ snap install krita
  97.84 MB / 97.84 MB 
[=]
 100.00 % 362.82 KB/s 

  Name   Version Rev  Developer
  krita  3.0-snap10  1krita
  mark@mark-XPS-15-9550:~$ krita
  QCoreApplication::arguments: Please instantiate the QApplication object first
  krita.lib.pigment: Compiled for arch: ::Vc::AVXImpl
  krita.lib.pigment: Features supported:
  krita.lib.pigment: "SSE2" ---  yes
  krita.lib.pigment: "SSSE3"---  yes
  krita.lib.pigment: "SSE4.1"   ---  yes
  krita.lib.pigment: "AVX " ---  yes
  libGL error: No matching fbConfigs or visuals found
  libGL error: failed to load driver: swrast
  Segmentation fault (core dumped)
  mark@mark-XPS-15-9550:~$

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

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

[Desktop-packages] [Bug 1766192] Re: [snap] cannot save file under $HOME

[Zygmunt Krynicki]

I'm marking this as triaged but I'm unsure how to solve it as we don't
want to allow write access to dot files in the home directory. Perhaps
libreoffice could be updated to create a different pattern for temporary
file names when under snap confinement?

** Changed in: snapd
   Status: New => Triaged

** Changed in: snapd
   Importance: Undecided => Low

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

Title:
  [snap] cannot save file under $HOME

Status in snapd:
  Triaged
Status in libreoffice package in Ubuntu:
  Triaged

Bug description:
  (this was initially reported on the forum:
  https://forum.snapcraft.io/t/libreoffice-6-0-3-not-so-stable/5032)

  When trying to save a file under $HOME (not a subdirectory), the user
  is presented with an error dialog:

  --- Error ---
  Error saving the document Untitled 1:
  Object not accessible.
  The object cannot be accessed
  due to insufficient user rights.
  [OK]

  This is because libreoffice tries to create a lock file of the form:
  "$HOME/.~lock.Untitled 1.odt", and the home interface doesn't allow
  writing hidden files (those with a filename that starts with a dot)
  under $HOME.

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)"

  DESKTOP_SESSION=ubuntu
  GTK_MODULES=gail:atk-bridge
  HOME=/home/osomon/snap/libreoffice/59
  LANG=fr_FR.UTF-8
  LC_MONETARY=fr_FR.UTF-8
  LC_NAME=fr_FR.UTF-8
  LC_NUMERIC=fr_FR.UTF-8
  LC_TIME=fr_FR.UTF-8
  
LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu::/snap/libreoffice/59/lib:/snap/libreoffice/59/usr/lib:/snap/libreoffice/59/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa
  
PATH=/snap/libreoffice/59/usr/sbin:/snap/libreoffice/59/usr/bin:/snap/libreoffice/59/sbin:/snap/libreoffice/59/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  SNAP=/snap/libreoffice/59
  SNAP_ARCH=amd64
  SNAP_COMMON=/var/snap/libreoffice/common
  SNAP_DATA=/var/snap/libreoffice/59
  
SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void
  SNAP_NAME=libreoffice
  SNAP_REEXEC=
  SNAP_REVISION=59
  SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common
  SNAP_USER_DATA=/home/osomon/snap/libreoffice/59
  SNAP_VERSION=6.0.3.2
  TEMPDIR=/tmp
  TMPDIR=/run/user/1000/snap.libreoffice
  XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg
  XDG_CURRENT_DESKTOP=ubuntu:GNOME
  
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop
  XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice
  XDG_SESSION_DESKTOP=ubuntu
  XDG_SESSION_TYPE=x11

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

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

[Desktop-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete()

[Zygmunt Krynicki]

I can still reproduce this now on my T470 with fully up-to-date bionic
(also tried the
https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging PPA)

kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE)
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) Backtrace:
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 0: /usr/bin/Xwayland 
(xorg_backtrace+0x4d) [0x561ba663e6bd]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 1: /usr/bin/Xwayland 
(0x561ba6496000+0x1ac459) [0x561ba6642459]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 2: 
/lib/x86_64-linux-gnu/libpthread.so.0 (0x7ff68662b000+0x12890) [0x7ff68663d890]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x24e9e3) 
[0x7ff6801269e3]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x1b3ed4) 
[0x7ff68008bed4]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x144c6a) 
[0x7ff68001cc6a]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x144cae) 
[0x7ff68001ccae]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 7: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x144d1c) 
[0x7ff68001cd1c]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 8: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0xad4b2) 
[0x7ff67ff854b2]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 9: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x25b6db) 
[0x7ff6801336db]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 10: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x3e2ae5) 
[0x7ff6802baae5]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 11: 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so (0x7ff67fed8000+0x3e1a13) 
[0x7ff6802b9a13]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 12: /usr/bin/Xwayland 
(0x561ba6496000+0xc8989) [0x561ba655e989]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 13: /usr/bin/Xwayland 
(0x561ba6496000+0xc7975) [0x561ba655d975]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 14: /usr/bin/Xwayland 
(0x561ba6496000+0x1969f2) [0x561ba662c9f2]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 15: /usr/bin/Xwayland 
(0x561ba6496000+0xcc5f7) [0x561ba65625f7]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 16: /usr/bin/Xwayland 
(0x561ba6496000+0xc7c3c) [0x561ba655dc3c]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 17: /usr/bin/Xwayland 
(0x561ba6496000+0x171ec8) [0x561ba6607ec8]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 18: /usr/bin/Xwayland 
(0x561ba6496000+0x175f10) [0x561ba660bf10]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 19: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) [0x7ff68625bb97]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) 20: /usr/bin/Xwayland 
(_start+0x2a) [0x561ba64d0ada]
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE)
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) Segmentation fault at 
address 0x68
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE)
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: Fatal server error:
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE) Caught signal 11 
(Segmentation fault). Server aborting
kwi 24 18:34:27 t470 org.gnome.Shell.desktop[6195]: (EE)


Let me know if you need some interactive debugging on this.

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete()

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca

  ---

  Steps to reproduce:
  Install 'slack' snap:

     sudo snap install slack --classic

  Run slack:

     slack

  Instacrash.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: xwayland 2:1.19.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Mar  9 10:31:06 2018
  DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/Xwayland
  ExtraDebuggingInterest: Yes, including running git bisection searches
  

[Desktop-packages] [Bug 1716034] Re: Network manager stops managing Ethernet links after upgrade

[Zygmunt Krynicki]

Chatting with Martin it seems that an upload to xenial-updates has
broken the logic since the test in network-manager's postinst script is
now out out date.

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

Title:
  Network manager stops managing Ethernet links after upgrade

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu, it stopped configuring the word connection on
  my headless computer (super annoying to deal with). In any case, it
  was an issue with NM config change that caused my wired device to
  become unmanaged.

  There are several people discussing this here:
  https://askubuntu.com/questions/882806/ethernet-device-not-managed

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

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

[Desktop-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

[Zygmunt Krynicki]

Possible duplicate https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1716034

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  In Progress

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety you will 
boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  before rebooting you should have a network connection after you
  reboot.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install netplan, configure to set up static network on an ethernet device 
using netplan.
  4) Upgrade to yakkety
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  
  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

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

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

[Desktop-packages] [Bug 1716034] Re: Network manager stops managing Ethernet links after upgrade

[Zygmunt Krynicki]

Looking at the changelog I see that the new conf.d file is a debian
addition. The relevant changelog says:

  * network-manager.postinst: Don't create
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf override on
new installations. We don't want NM to manage non-wifi/wwan on
servers/cloud instances, and for desktops live-build now installs a
netplan policy snippet to let NM handle all devices.

 -- Martin Pitt   Thu, 18 Aug 2016 08:42:16
+0200


Yet on my system there was no netplan, netplan is a dependency of 
"ubuntu-standard". Installing ubuntu-standard hasn't changed anything. I wonder 
how this was expected to work on upgrades.

In any case, I think that the "wwan" vs "gsm" is a separate bug that
needs investigation.

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

Title:
  Network manager stops managing Ethernet links after upgrade

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu, it stopped configuring the word connection on
  my headless computer (super annoying to deal with). In any case, it
  was an issue with NM config change that caused my wired device to
  become unmanaged.

  There are several people discussing this here:
  https://askubuntu.com/questions/882806/ethernet-device-not-managed

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

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

[Desktop-packages] [Bug 1716034] Re: Network manager stops managing Ethernet links after upgrade

[Zygmunt Krynicki]

This also affected my machines. Thanks to the forum reference I was able
to piece together this:

The file belonging to network-manager /usr/lib/NetworkManager/conf.d/10
-globally-managed-devices.conf contains:

[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:wwan

Curiously, at least on my machines, this also knocked out "gsm" type
connection which made me offline as I rely on 3G connections often.

The "solution" is to create an empty file at
/etc/NetworkManager/conf.d/10-globally-managed-devices.conf the presence
of which overrides the distribution packaged default.

I consider this a critical error as it can result in inability to
connect typical system to the network to pull in updates that would
resolve the problem.



** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Network manager stops managing Ethernet links after upgrade

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Ubuntu, it stopped configuring the word connection on
  my headless computer (super annoying to deal with). In any case, it
  was an issue with NM config change that caused my wired device to
  become unmanaged.

  There are several people discussing this here:
  https://askubuntu.com/questions/882806/ethernet-device-not-managed

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

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

[Desktop-packages] [Bug 1643910] Re: BAMF_DESKTOP_FILE_HINT not set in correct place for unity7

[Zygmunt Krynicki]

** Changed in: snappy
   Status: New => Triaged

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

Title:
  BAMF_DESKTOP_FILE_HINT not set in correct place for unity7

Status in Snappy:
  Triaged
Status in bamf package in Ubuntu:
  Triaged

Bug description:
  Occasionally when I pin items to the Unity7 launcher, the BAMF code
  (as I'm told) incorrectly matches to /snap/app/revision/ This is a
  security issue because the Exec= line points to /snap/app/revision/...
  which bypasses snap run (/snap/bin/...) and therefore snap-confine.

  I'm told by Marcus (aka, 3v1n0 aka Trevinho) that this is because
  BAMF_DESKTOP_FILE_HINT is not exported by snap env and instead only
  injected in the desktop file that is created in
  /var/lib/snapd/desktop/applications upon snap install. This means that
  the wrong Exec= (ie, where it points to the binary) may occur in two
  places:

  1. when launching /snap/bin/... from the command line
  2. when something in /var/lib/snapd/desktop/applications/*.desktop doesn't 
match properly

  In both cases, the initial launch is fine, but pinning the icon to the
  launcher results in the wrong entry in the Exec= line and launching
  from this pinned launcher entry after is unconfined. You can check by
  doing:

  1. launch application from the dash
  2. run sudo aa-status and see if it is launched under confinement
  3. pin the icon that is in the launcher
  4. close the application, then launch from the pinned icon
  5. run sudo aa-status and see if it is launched under confinement

  This doesn't happen all the time. For example, vlc seems to work fine
  both from the command line and from launching via a pinned launcher
  entry. chrome-test on the other hand doesn't seem to work with either.

  Related https://github.com/snapcore/snapd/pull/1580 -- puts
  BAMF_DESKTOP_FILE_HINT in the desktop file instead of in the
  environment, but Marco requested that this change
  (https://github.com/snapcore/snapd/pull/1580#issuecomment-234546220).

  https://trello.com/c/xP1hN3BF/152-improve-desktop-file-support-by-
  adding-a-new-bamf-desktop-file-hint-environment-hint also discussed
  this issue, but the card is archived and therefore it won't be worked
  on.

  I'm having trouble finding a simple reproducer (other than chrome-
  test) but am told by Marco that the BAMF matching will always work if
  BAMF_DESKTOP_FILE_HINT in the process' environment always points to
  the desktop file in /var/lib/snapd/desktop/applications. I will
  continue to look for a simple reproducer.

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

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

[Desktop-packages] [Bug 1574851] Re: libgl not found on nvidia machines (so far)

[Zygmunt Krynicki]

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

This is probably a duplicate of 1615248 that is now fixed upstream.

** This bug has been marked a duplicate of bug 1615248
   ubuntu-core-launcher nvidia driver detection is bogus

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

Title:
  libgl not found on nvidia machines (so far)

Status in Snappy:
  Triaged
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed

Bug description:
  So I've just had 2 recent complaints on libgl not being found on nvidia.
  here: 
http://askubuntu.com/questions/759647/opengl-error-in-snaps-ubuntu-16-04 
  and on IRC

  I cannot determine if anyone has had success running one of the 
desktop-example apps from the store on an nvidia gpu machine.
  I asked Alberto Aguirre on the mir team (who has a nvidia gpu) to try SDoC 
and install the ubuntu-clock-app from the store - he confirms seeing the exact 
same issue, he can be questioned if debug help is needed.

  Note, from an engagement on IRC earlier, the person confirmed that
  even rebuilding the clock snap locally and sideloading did not address
  the issue.

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

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

[Desktop-packages] [Bug 1574851] Re: libgl not found on nvidia machines (so far)

[Zygmunt Krynicki]

Thank you for completing this. I think this problem may go away entirely
with snapd 2.0.10 and snap-confine 1.0.34 that are currently in xenial-
proposed.

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

Title:
  libgl not found on nvidia machines (so far)

Status in Snappy:
  Triaged
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed

Bug description:
  So I've just had 2 recent complaints on libgl not being found on nvidia.
  here: 
http://askubuntu.com/questions/759647/opengl-error-in-snaps-ubuntu-16-04 
  and on IRC

  I cannot determine if anyone has had success running one of the 
desktop-example apps from the store on an nvidia gpu machine.
  I asked Alberto Aguirre on the mir team (who has a nvidia gpu) to try SDoC 
and install the ubuntu-clock-app from the store - he confirms seeing the exact 
same issue, he can be questioned if debug help is needed.

  Note, from an engagement on IRC earlier, the person confirmed that
  even rebuilding the clock snap locally and sideloading did not address
  the issue.

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

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

[Desktop-packages] [Bug 1574851] Re: libgl not found on nvidia machines (so far)

[Zygmunt Krynicki]

Dear reporter.

Can you please share the following information:

 - version of snapd and snap-confine (you can check with "apt-cache policy 
snap-confine")
 - make and model of the GPU you are using
 - the installed driver packages, you can quickly find this with "dpkg 
--get-selections | grep nvidia")
 - if the snap is public, name and revision of the snap you've tried ("snap 
list" shows the revision).

Thanks

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

Title:
  libgl not found on nvidia machines (so far)

Status in Snappy:
  Triaged
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed

Bug description:
  So I've just had 2 recent complaints on libgl not being found on nvidia.
  here: 
http://askubuntu.com/questions/759647/opengl-error-in-snaps-ubuntu-16-04 
  and on IRC

  I cannot determine if anyone has had success running one of the 
desktop-example apps from the store on an nvidia gpu machine.
  I asked Alberto Aguirre on the mir team (who has a nvidia gpu) to try SDoC 
and install the ubuntu-clock-app from the store - he confirms seeing the exact 
same issue, he can be questioned if debug help is needed.

  Note, from an engagement on IRC earlier, the person confirmed that
  even rebuilding the clock snap locally and sideloading did not address
  the issue.

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

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

[Desktop-packages] [Bug 1583057] Re: Deny audio recording for all snap applications

[Zygmunt Krynicki]

Can we please try to upstream this patch? This will help with making
other distributions share the security features and advantages of snaps.

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

Title:
  Deny audio recording for all snap applications

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Triaged
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Until we have a proper trust-store implementation with snappy and on
  the desktop/ubuntu core we want pulseaudio to simply deny any audio
  recording request coming from an app shipped as part of a snap.

  The implementation adds a module-snappy-policy module to pulseaudio
  which adds a hook for audio recording requests and checks on
  connection if the apparmor security label of the connecting peer
  starts with "snap." which will identify it as a snap application.

  Pulseaudio with the patch is available as part of the landing request
  at https://requests.ci-train.ubuntu.com/#/ticket/1428

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

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

[Desktop-packages] [Bug 1593407] Re: Guest session cannot run snaps

[Zygmunt Krynicki]

Guest session is already confined with an apparmor profile. I think that
there's no support for profile transitions there to run snap-confine and
everything else but it might be doable

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

Title:
  Guest session cannot run snaps

Status in lightdm package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 16.04.

  The guest session cannot execute snaps, because of a permission error.
  The AppArmor profile is not allowing access to /snap and other needed files 
and folders.

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

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

Re: [Desktop-packages] [Bug 562005] Re: Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no longer function while using proprietary drivers

[Zygmunt Krynicki]

If anyone cares, I have a 880M w510 lenovo laptop running vivid and
yes, this is still broken. If anyone needs some extra details I can
provide that.

On Fri, Jun 26, 2015 at 6:07 PM, Martin Spacek launch...@mspacek.mm.st wrote:
 there is plenty of similar reports around and forums discussions about
 that.

 Why not post them here?

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/562005

 Title:
   Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs
   no longer function while using proprietary drivers

 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+subscriptions

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

Title:
  Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs
  no longer function while using proprietary drivers

Status in Ubuntu Certification Programme:
  Invalid
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid

Bug description:
  The brightness controls of laptops with NVIDIA NVS 3100M or Quadro FX
  880M GPUs work  while running Nouveau or when using a text mode VT,
  but not while running X and using proprietary NVIDIA drivers.  It is
  possible to force the NVIDIA driver to control the backlight by adding
  [Option RegistryDwords EnableBrightnessControl=1] to the Devices
  section of xorg.conf . While this allows the backlight to be
  controlled, the increments are inconsistent and often result in a
  buzzing noise from the LED backlight on Lenovo ThinkPad T510s and
  W510s. Since this did not occur while running nouveau or when
  switching in text VT, something is wrong.

  This bad backlight behaviour has been confirmed on ThinkPad models T510 and 
W510 with NVIDIA NVS 3100m and Quadro FX 880M chipsets, respectively, via 
http://www.thinkwiki.org/wiki/Category:T510
  Because this issue is related to NVIDIA's proprietary video driver, this 
issue can only be solved by them. An NVIDIA developer has said he will 
investigate the issues, which are  discussed on the nvnews.net forums at 
http://www.nvnews.net/vbulletin/showthread.php?t=145105 and 
http://www.nvnews.net/vbulletin/showthread.php?t=150069 . For future reference, 
the latest NVIDIA drivers can be found in the Ubuntu X-Swat X updates PPA: 
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates

  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: nvidia-current 195.36.15-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Apr 12 23:48:02 2010
  DkmsStatus:
   nvidia-current, 195.36.15, 2.6.32-19-generic, x86_64: installed
  EcryptfsInUse: Yes
  GdmLog1:

  MachineType: LENOVO 4313CTO
  ProcCmdLine: BOOT_IMAGE=/bhostnamet/vmlinuz-2.6.32-19-generic 
rhostnamet=UUID=0b95b314-337f-49aa-86f9-6423e76e9f20 ro
  ProcEnviron:
   LANG=en_CA.utf8
   SHELL=/bin/bash
  SourcePackage: nvidia-graphics-drivers
  XorgLogOld:

  dmi.bios.date: 02/22/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET49WW (1 tp-smapi, 0.40, 2.6.32-19-generic, x86_64: 
installed
   vboxnetadp, 3.1.6, 2.6.32-19-generic, x86_64: installed
   vboxnetflt, 3.1.6, 2.6.32-19-generic, x86_64: installed
   vboxdrv, 3.1.6, 2.6.32-19-generic, x86_64: installed.12 )
  dmi.board.name: 4313CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MET49WW(1.12):bd02/22/2010:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4313CTO
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   x86_64
   kernel: 2.6.32-19-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-certification/+bug/562005/+subscriptions

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

[Desktop-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Zygmunt Krynicki]

Hey, a small update. Lantern test v2 tests exactly what happens when
brightness is set to 0. I have 10 samples so far and I will be able to
analyze them today. My gut feeling is that acpi aka firmware control
never tuns the backlight off entirely (so setting zero in userspace is
safe) while raw control will just disable all light at the same level. I
would suggest that for raw controls the bottom value should be 10% of
max brightness. The actual value also depends on if the scale is linear
or logarithmic which is on my TODO list to check in Lantern.

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System Settings - Brightness  Lock to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+subscriptions

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

[Desktop-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Zygmunt Krynicki]

Hey.

I'm researching the behaviour of backlight in the wild and my current
theory is that brightness of zero can equally well mean dim or
totally off. I don't have a test for that yet so the sample range is
very small (the hardware I have at home + several contributions from the
community) but that seems to be the case.

I also looked at windows API and I'm about to look at the current
Microsoft certification requirements. The API says that the values are
arbitrary and no mapping to actual light intensity can be assumed.

If you want to track my work, please look at
https://github.com/zyga/lantern

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  New

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System Settings - Brightness  Lock to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+subscriptions

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

[Desktop-packages] [Bug 1371032] Re: Cannot send MMS from Yoigo

[Zygmunt Krynicki]

** Attachment added: logs from a failed attempt to receive an MMS from/to 
Yoigo
   
https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1371032/+attachment/4229596/+files/network-test-session_10-09-2014_15%3A38%3A35.tar.gz

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

Title:
  Cannot send MMS from Yoigo

Status in “messaging-app” package in Ubuntu:
  Invalid
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “nuntium” package in Ubuntu:
  Fix Released
Status in “ofono” package in Ubuntu:
  Invalid
Status in “nuntium” package in Ubuntu RTM:
  Fix Released

Bug description:
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  AccessPointName = internet
  Name = Yoigo Internet
  Password = 
  Protocol = ip
  IPv6.Settings = { }
  Type = internet
  Active = 1
  Username = 
  Settings = { DomainNameServers=217.168.13.34,46.6.113.2, 
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31 
Interface=ccmni0 }

  [ /ril_0/context2 ]
  AccessPointName = mms
  MessageCenter = http://mmss/
  Name = Yoigo MMS
  Password = 
  Protocol = ip
  MessageProxy = 193.209.134.141:80
  IPv6.Settings = { }
  Type = mms
  Active = 0
  Username = 
  Settings = { }

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
  Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not 
attached

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
  /ril_0 1

  Additional info:
  - I didn't see any error in the messaging app.
  - Couldn't send nor receive MMS.
  - 3G connection is activated, but usually after a reboot. After a while, it 
looses it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1371032/+subscriptions

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

[Desktop-packages] [Bug 1371032] Re: Cannot send MMS from Yoigo

[Zygmunt Krynicki]

I have procured a yoigo SIM and I can now test this

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

Title:
  Cannot send MMS from Yoigo

Status in “messaging-app” package in Ubuntu:
  Invalid
Status in “network-manager” package in Ubuntu:
  Invalid
Status in “nuntium” package in Ubuntu:
  Fix Released
Status in “ofono” package in Ubuntu:
  Invalid
Status in “nuntium” package in Ubuntu RTM:
  Fix Released

Bug description:
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts
  [ /ril_1 ]
  [ /ril_0 ]
  [ /ril_0/context1 ]
  AccessPointName = internet
  Name = Yoigo Internet
  Password = 
  Protocol = ip
  IPv6.Settings = { }
  Type = internet
  Active = 1
  Username = 
  Settings = { DomainNameServers=217.168.13.34,46.6.113.2, 
Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31 
Interface=ccmni0 }

  [ /ril_0/context2 ]
  AccessPointName = mms
  MessageCenter = http://mmss/
  Name = Yoigo MMS
  Password = 
  Protocol = ip
  MessageProxy = 193.209.134.141:80
  IPv6.Settings = { }
  Type = mms
  Active = 0
  Username = 
  Settings = { }

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2
  Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not 
attached

  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context
  /ril_0 1

  Additional info:
  - I didn't see any error in the messaging app.
  - Couldn't send nor receive MMS.
  - 3G connection is activated, but usually after a reboot. After a while, it 
looses it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1371032/+subscriptions

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

[Desktop-packages] [Bug 1320522] [NEW] package texlive-base (not installed) failed to install/upgrade: próba nadpisania /usr/share/texmf/web2c/texmf.cnf, który istnieje także w pakiecie tex-common 2

[Zygmunt Krynicki]

Public bug reported:

I was upgrading from 12.04 to 14.04, I'm not sure why texlive-base
failed to update (I've removed it to try to recover the update process).
I had it installed on 12.04 but probably just through a package build
dependency.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: texlive-base (not installed)
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
Date: Sat May 17 14:18:45 2014
DuplicateSignature: package:texlive-base:(not installed):próba nadpisania 
/usr/share/texmf/web2c/texmf.cnf, który istnieje także w pakiecie tex-common 
2.10
ErrorMessage: próba nadpisania /usr/share/texmf/web2c/texmf.cnf, który 
istnieje także w pakiecie tex-common 2.10
InstallationDate: Installed on 2014-05-13 (4 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
SourcePackage: texlive-base
Title: package texlive-base (not installed) failed to install/upgrade: próba 
nadpisania /usr/share/texmf/web2c/texmf.cnf, który istnieje także w pakiecie 
tex-common 2.10
UpgradeStatus: Upgraded to trusty on 2014-05-17 (0 days ago)

** Affects: texlive-base (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package texlive-base (not installed) failed to install/upgrade: próba
  nadpisania /usr/share/texmf/web2c/texmf.cnf, który istnieje także w
  pakiecie tex-common 2.10

Status in “texlive-base” package in Ubuntu:
  New

Bug description:
  I was upgrading from 12.04 to 14.04, I'm not sure why texlive-base
  failed to update (I've removed it to try to recover the update
  process). I had it installed on 12.04 but probably just through a
  package build dependency.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: texlive-base (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  Date: Sat May 17 14:18:45 2014
  DuplicateSignature: package:texlive-base:(not installed):próba nadpisania 
/usr/share/texmf/web2c/texmf.cnf, który istnieje także w pakiecie tex-common 
2.10
  ErrorMessage: próba nadpisania /usr/share/texmf/web2c/texmf.cnf, który 
istnieje także w pakiecie tex-common 2.10
  InstallationDate: Installed on 2014-05-13 (4 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  SourcePackage: texlive-base
  Title: package texlive-base (not installed) failed to install/upgrade: próba 
nadpisania /usr/share/texmf/web2c/texmf.cnf, który istnieje także w pakiecie 
tex-common 2.10
  UpgradeStatus: Upgraded to trusty on 2014-05-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1320522/+subscriptions

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

[Desktop-packages] [Bug 871083] Re: gzip -9n sometimes generates a different output file on different architectures

[Zygmunt Krynicki]

I have a feeling that the very same bug affects python3.2 on Ubuntu
12.04. I have looked at the source code of the zlib module shipped with
python and while it's not exactly the same as gzip it seems to lack the
relevant memset to clear uninitialized garbage.

** Also affects: python
   Importance: Undecided
   Status: New

** Also affects: python3.2 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  gzip -9n sometimes generates a different output file on different
  architectures

Status in Python:
  New
Status in “clutter-1.0” package in Ubuntu:
  Fix Released
Status in “gtk+2.0” package in Ubuntu:
  Fix Released
Status in “gzip” package in Ubuntu:
  Fix Released
Status in “libtasn1-3” package in Ubuntu:
  Triaged
Status in “pam” package in Ubuntu:
  Fix Released
Status in “python3.2” package in Ubuntu:
  New
Status in “gzip” source package in Oneiric:
  Fix Released
Status in “pam” source package in Oneiric:
  Fix Released
Status in “clutter-1.0” source package in Precise:
  Fix Released
Status in “gtk+2.0” source package in Precise:
  Fix Released
Status in “gzip” source package in Precise:
  Fix Released
Status in “libtasn1-3” source package in Precise:
  Triaged
Status in “pam” source package in Precise:
  Fix Released
Status in “gzip” package in Debian:
  Fix Released

Bug description:
  SRU justification:
  libpam-modules is not multiarch-coinstallable because of unexplained 
misgeneration of compressed manpages on the buildds in a previous run.  This 
makes it impossible to use pam authentication for foreign-arch software due to 
the uninstallable modules, and also causes unpleasant upgrade issues.

  Test case:
  1) on amd64, enable armel in addition to i386 as a foreign architecture by 
running:
echo 'foreign-architecture armel'  /etc/dpkg/dpkg.cfg.d/multiarch-armel
echo 'deb [arch=armel] http://ports.ubuntu.com/ubuntu-ports/ oneiric main' 
 /etc/apt/sources.list
apt-get update
  2) try to install libpam-modules for the other two architectures by running 
'apt-get install libpam-modules:i386 libpam-modules:armel'
  3) confirm that both packages fail to install.
  4) enable oneiric-proposed (including for armel above).
  5) try to install libpam-modules for all three architectures by running 
'apt-get install libpam-modules libpam-modules:i386 libpam-modules:armel'
  6) confirm that the packages install successfully.

  error while updating

  ProblemType: Package
  DistroRelease: Ubuntu 11.10
  Package: libpam-modules 1.1.3-2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  Date: Sat Oct  8 18:57:52 2011
  ErrorMessage: ErrorMessage: './usr/share/man/man8/pam_shells.8.gz' is 
different from the same file on the system
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  SourcePackage: pam
  Title: package libpam-modules 1.1.3-2ubuntu1 failed to install/upgrade: 
ErrorMessage: './usr/share/man/man8/pam_shells.8.gz' is different from the same 
file on the system
  UpgradeStatus: Upgraded to oneiric on 2011-10-09 (0 days ago)

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

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

[Desktop-packages] [Bug 1174696] Re: Regression in sound quality on 13.04 as compared to 12.04 (HDMI over DP) on Thinkpad W510

[Zygmunt Krynicki]

Interesting find, I'll check if I have the same warning on precise.
Could this be the fault of the DP-to-HDMI adapter?

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

Title:
  Regression in sound quality on 13.04 as compared to 12.04 (HDMI over
  DP) on Thinkpad W510

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  This laptop is using a DP to HDMI adapter, connected to a HDMI
  monitor. Sound quality on 12.04 is perfect, sound quality on 13.04 is
  poor (cracking and metallic feeling)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: pulseaudio 1:3.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-19.29lp1169984v201304261303-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zyga   1668 F pulseaudio
   /dev/snd/controlC0:  zyga   1668 F pulseaudio
   /dev/snd/pcmC0D0c:   zyga   1668 F...m pulseaudio
  Date: Tue Apr 30 12:24:59 2013
  InstallationDate: Installed on 2013-04-29 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4318CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4318CTO
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1174696] Re: Regression in sound quality on 13.04 as compared to 12.04 (HDMI over DP) on Thinkpad W510

[Zygmunt Krynicki]

This is alsainfo from the same laptop, with the same DP/HDMI adapter and
the same screen as reported above, this time running Ubuntu 12.04:
http://www.alsa-
project.org/db/?f=05028563518fe47e02249fe0a1fbad8b5f786386

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

Title:
  Regression in sound quality on 13.04 as compared to 12.04 (HDMI over
  DP) on Thinkpad W510

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  This laptop is using a DP to HDMI adapter, connected to a HDMI
  monitor. Sound quality on 12.04 is perfect, sound quality on 13.04 is
  poor (cracking and metallic feeling)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: pulseaudio 1:3.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-19.29lp1169984v201304261303-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zyga   1668 F pulseaudio
   /dev/snd/controlC0:  zyga   1668 F pulseaudio
   /dev/snd/pcmC0D0c:   zyga   1668 F...m pulseaudio
  Date: Tue Apr 30 12:24:59 2013
  InstallationDate: Installed on 2013-04-29 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4318CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4318CTO
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1174696] [NEW] Regression in sound quality on 13.04 as compared to 12.04 (HDMI over DP) on Thinkpad W510

[Zygmunt Krynicki]

Public bug reported:

This laptop is using a DP to HDMI adapter, connected to a HDMI monitor.
Sound quality on 12.04 is perfect, sound quality on 13.04 is poor
(cracking and metallic feeling)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: pulseaudio 1:3.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-19.29lp1169984v201304261303-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  zyga   1668 F pulseaudio
 /dev/snd/controlC0:  zyga   1668 F pulseaudio
 /dev/snd/pcmC0D0c:   zyga   1668 F...m pulseaudio
Date: Tue Apr 30 12:24:59 2013
InstallationDate: Installed on 2013-04-29 (0 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
MarkForUpload: True
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/03/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6NET84WW (1.45 )
dmi.board.name: 4318CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4318CTO
dmi.product.version: ThinkPad W510
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug raring

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

Title:
  Regression in sound quality on 13.04 as compared to 12.04 (HDMI over
  DP) on Thinkpad W510

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  This laptop is using a DP to HDMI adapter, connected to a HDMI
  monitor. Sound quality on 12.04 is perfect, sound quality on 13.04 is
  poor (cracking and metallic feeling)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: pulseaudio 1:3.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-19.29lp1169984v201304261303-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zyga   1668 F pulseaudio
   /dev/snd/controlC0:  zyga   1668 F pulseaudio
   /dev/snd/pcmC0D0c:   zyga   1668 F...m pulseaudio
  Date: Tue Apr 30 12:24:59 2013
  InstallationDate: Installed on 2013-04-29 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4318CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4318CTO
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1174696] Re: Regression in sound quality on 13.04 as compared to 12.04 (HDMI over DP) on Thinkpad W510

[Zygmunt Krynicki]

I've tried all workarounds listed on
https://wiki.ubuntu.com/Audio/PositionReporting without success

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

Title:
  Regression in sound quality on 13.04 as compared to 12.04 (HDMI over
  DP) on Thinkpad W510

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  This laptop is using a DP to HDMI adapter, connected to a HDMI
  monitor. Sound quality on 12.04 is perfect, sound quality on 13.04 is
  poor (cracking and metallic feeling)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: pulseaudio 1:3.0-0ubuntu6
  ProcVersionSignature: Ubuntu 3.8.0-19.29lp1169984v201304261303-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  zyga   1668 F pulseaudio
   /dev/snd/controlC0:  zyga   1668 F pulseaudio
   /dev/snd/pcmC0D0c:   zyga   1668 F...m pulseaudio
  Date: Tue Apr 30 12:24:59 2013
  InstallationDate: Installed on 2013-04-29 (0 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET84WW (1.45 )
  dmi.board.name: 4318CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET84WW(1.45):bd10/03/2012:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4318CTO
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 837744] Re: inkscape crashed with SIGSEGV in sp_action_set_name()

[Zygmunt Krynicki]

This just crashed again. I don't have the SVG file, sorry

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

Title:
  inkscape crashed with SIGSEGV in sp_action_set_name()

Status in Inkscape: A Vector Drawing Tool:
  Invalid
Status in “inkscape” package in Ubuntu:
  Expired

Bug description:
  was saving a pdf

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: inkscape 0.48.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  CrashCounter: 1
  Date: Tue Aug 30 18:30:44 2011
  ExecutablePath: /usr/bin/inkscape
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  ProcCmdline: inkscape
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/usr/bin/tcsh
  SegvAnalysis:
   Segfault happened at: 0x8290afa: mov(%ebx),%esi
   PC (0x08290afa) ok
   source (%ebx) (0x) not located in a known VMA region (needed 
readable region)!
   destination %esi ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: inkscape
  StacktraceTop:
   ?? ()
   sp_action_set_name(SPAction*, Glib::ustring) ()
   Inkscape::Verb::name(SPDocument*, Glib::ustring) ()
   Inkscape::EventLog::updateUndoVerbs() ()
   Inkscape::CompositeUndoStackObserver::notifyClearUndoEvent() ()
  Title: inkscape crashed with SIGSEGV in sp_action_set_name()
  UpgradeStatus: Upgraded to oneiric on 2011-08-30 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

[Zygmunt Krynicki]

Testing, I'll let you know if it crashes

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

Title:
  Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Triaged

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Sat Feb 16 21:39:07 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

[Zygmunt Krynicki]

It crashed again.

For reference, I've added the PPA, updated everything, logged out,
checked that I don't have xorg config file (so that I keep getting sna
by default).

Program received signal SIGSEGV, Segmentation fault.
0x7f79d99ab5d0 in sna_pixmap_set_dri (pixmap=0x7f79de9d5220, 
sna=0x7f79dcf58010)
at ../../../src/sna/sna_dri.c:186
186 ../../../src/sna/sna_dri.c: Nie ma takiego pliku ani katalogu.
(gdb)  backtrace full
#0  0x7f79d99ab5d0 in sna_pixmap_set_dri (pixmap=0x7f79de9d5220, 
sna=0x7f79dcf58010)
at ../../../src/sna/sna_dri.c:186
priv = 0x7f79dead6940
tiling = -1
#1  sna_dri_create_buffer (draw=optimized out, attachment=0, format=32)
at ../../../src/sna/sna_dri.c:274
sna = 0x7f79dcf58010
buffer = optimized out
pixmap = optimized out
bo = optimized out
flags = 1
size = optimized out
bpp = optimized out
#2  0x7f79dd1aae5c in ?? ()
No symbol table info available.
#3  0x7f79dd1ab7f6 in ?? ()
No symbol table info available.
#4  0x7f79dd1abc10 in DRI2GetBuffersWithFormat ()
No symbol table info available.
#5  0x7f79dd1ad690 in ?? ()
No symbol table info available.
#6  0x7f79dd082a41 in ?? ()
No symbol table info available.
#7  0x7f79dd07154a in ?? ()
No symbol table info available.
#8  0x7f79dad7eea5 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#9  0x7f79dd071891 in _start ()
No symbol table info available.
(gdb) 


The gdb session is still active, ask for more data if you want

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

Title:
  Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Triaged

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No 

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

[Zygmunt Krynicki]

(gdb) p *priv
$2 = {
  pixmap = 0x7f79de9d5220, 
  gpu_bo = 0x0, 
  cpu_bo = 0x7f79dead4330, 
  gpu_damage = 0x7f79de849421, 
  cpu_damage = 0x0, 
  ptr = 0x7f79d6499000, 
  list = {
next = 0x7f79dead6970, 
prev = 0x7f79dead6970
  }, 
  stride = 1280, 
  clear_color = 0, 
  source_count = 4, 
  pinned = 0 '\000', 
  create = 11 '\v', 
  mapped = 0 '\000', 
  flush = 0 '\000', 
  shm = 0 '\000', 
  clear = 0 '\000', 
  header = 0 '\000', 
  cpu = 0 '\000'
}


I'll build the tree and get back to you

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

Title:
  Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Triaged

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Sat Feb 

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

[Zygmunt Krynicki]

Ok, built and ready, trying to get it to crash 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/1127497

Title:
  Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Triaged

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Sat Feb 16 21:39:07 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

[Zygmunt Krynicki]

Nothing, is there a chance it got fixed along the way? Do you want me to
try bisecting things?

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

Title:
  Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Triaged

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Sat Feb 16 21:39:07 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

[Zygmunt Krynicki]

I didn't install any package, just updated all my packages which
included xserver-xorg-video-intel. The version apt reports is
2:2.21.2+git20130213.9861423a-0ubuntu0sarvatt. This is an upgrade from
2:2.21.2-0ubuntu0

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

Title:
  Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Triaged

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Sat Feb 16 21:39:07 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

[Zygmunt Krynicki]

I can revert that and test if it exposes the issue.

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

Title:
  Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Triaged

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Sat Feb 16 21:39:07 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

[Zygmunt Krynicki]

That was quick. I didn't have to exit steam though, just launch it:

Program received signal SIGABRT, Aborted.
0x7ff335664037 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x7ff335664037 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x7ff335667698 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7ff33565ce03 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x7ff33565ceb2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x7ff33426d164 in sna_dri_schedule_swap (client=0x7ff339c4bab0, 
draw=0x7ff33a09b140, 
front=0x7ff339cb1100, back=0x7ff339b97700, target_msc=0x7fffa3cb6a28, 
divisor=0, remainder=0, 
func=0x7ff337a7cef0, data=0x7ff33a09b140) at sna_dri.c:2140
#5  0x7ff337a7c224 in DRI2SwapBuffers ()
#6  0x7ff337a7d3b4 in ?? ()
#7  0x7ff337952a41 in ?? ()
#8  0x7ff33794154a in ?? ()
#9  0x7ff33564eea5 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
#10 0x7ff337941891 in _start ()
(gdb) git backtrace
Undefined command: git.  Try help.
(gdb) backtrace full
#0  0x7ff335664037 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x7ff335667698 in abort () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2  0x7ff33565ce03 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#3  0x7ff33565ceb2 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#4  0x7ff33426d164 in sna_dri_schedule_swap (client=0x7ff339c4bab0, 
draw=0x7ff33a09b140, 
front=0x7ff339cb1100, back=0x7ff339b97700, target_msc=0x7fffa3cb6a28, 
divisor=0, remainder=0, 
func=0x7ff337a7cef0, data=0x7ff33a09b140) at sna_dri.c:2140
screen = optimized out
scrn = optimized out
sna = 0x7ff337828010
vbl = {request = {
type = (DRM_VBLANK_HIGH_CRTC_MASK | DRM_VBLANK_EVENT | 
DRM_VBLANK_NEXTONMISS | DRM_VBLANK_SECONDARY | unknown: 58884096), sequence = 
32755, signal = 140682528728598}, reply = {
type = (DRM_VBLANK_HIGH_CRTC_MASK | DRM_VBLANK_EVENT | 
DRM_VBLANK_NEXTONMISS | DRM_VBLANK_SECONDARY | unknown: 58884096), sequence = 
32755, tval_sec = 140682528728598, 
tval_usec = 4230521311723520}}
pipe = optimized out
info = 0x0
current_msc = 8
__PRETTY_FUNCTION__ = sna_dri_schedule_swap
#5  0x7ff337a7c224 in DRI2SwapBuffers ()
No symbol table info available.
#6  0x7ff337a7d3b4 in ?? ()
No symbol table info available.
#7  0x7ff337952a41 in ?? ()
No symbol table info available.
#8  0x7ff33794154a in ?? ()
No symbol table info available.
#9  0x7ff33564eea5 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#10 0x7ff337941891 in _start ()
No symbol table info available.

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

Title:
  Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Triaged

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: 

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

[Zygmunt Krynicki]

Ok, I'll undo the revert and keep pushing it

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

Title:
  Xorg crashes when exiting steam segfault in sna_pixmap_set_dri()

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Triaged

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Sat Feb 16 21:39:07 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam

[Zygmunt Krynicki]

Can you please apt-get install xserver-xorg-video-intel-dbg 
addr2line -e /usr/lib/xorg/modules/drivers/intel_drv.so 0xd40a1

That gives me sna_dri.c:186

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

Title:
  Xorg crashes when exiting steam

Status in “xserver-xorg-video-intel” package in Ubuntu:
  Incomplete

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Sat Feb 16 21:39:07 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam

[Zygmunt Krynicki]

I can no longer reproduce the crash. Steam was updated in the meantime
so it could have been fixed (workaround?) by valve

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

Title:
  Xorg crashes when exiting steam

Status in “xserver-xorg-video-intel” package in Ubuntu:
  New

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Sat Feb 16 21:39:07 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.2-0ubuntu2
  xserver.video_driver: intel

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

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

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam

[Zygmunt Krynicki]

Program received signal SIGSEGV, Segmentation fault.
0x7f868f35c0a1 in sna_pixmap_set_dri (pixmap=0x7f8694200b20, 
sna=0x7f8692908010) at ../../../src/sna/sna_dri.c:186
186 ../../../src/sna/sna_dri.c: Nie ma takiego pliku ani katalogu.
(gdb) backtrace full
#0  0x7f868f35c0a1 in sna_pixmap_set_dri (pixmap=0x7f8694200b20, 
sna=0x7f8692908010) at ../../../src/sna/sna_dri.c:186
priv = 0x7f8694205160
tiling = 1
#1  sna_dri_create_buffer (draw=optimized out, attachment=0, format=32) at 
../../../src/sna/sna_dri.c:280
sna = 0x7f8692908010
buffer = optimized out
pixmap = optimized out
bo = optimized out
flags = 1
size = optimized out
bpp = optimized out
#2  0x7f8692b5ae5c in ?? ()
No symbol table info available.
#3  0x7f8692b5b7f6 in ?? ()
No symbol table info available.
#4  0x7f8692b5bc10 in DRI2GetBuffersWithFormat ()
No symbol table info available.
#5  0x7f8692b5d690 in ?? ()
No symbol table info available.
#6  0x7f8692a32a41 in ?? ()
No symbol table info available.
#7  0x7f8692a2154a in ?? ()
No symbol table info available.
#8  0x7f869072eea5 in __libc_start_main () from 
/lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#9  0x7f8692a21891 in _start ()
No symbol table info available.

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

Title:
  Xorg crashes when exiting steam

Status in “xserver-xorg-video-intel” package in Ubuntu:
  New

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam

[Zygmunt Krynicki]

(gdb) info locals
priv = 0x7f8694205160
tiling = 1
(gdb) print *priv
$3 = {
  pixmap = 0x7f8694200b20, 
  gpu_bo = 0x0, 
  cpu_bo = 0x7f8693e673a0, 
  gpu_damage = 0x7f8693b996e1, 
  cpu_damage = 0x0, 
  ptr = 0x7f868eb58000, 
  list = {
next = 0x7f8694205190, 
prev = 0x7f8694205190
  }, 
  stride = 1280, 
  clear_color = 0, 
  flush = 1, 
  source_count = 4, 
  pinned = 0 '\000', 
  create = 11 '\v', 
  mapped = 0 '\000', 
  shm = 0 '\000', 
  clear = 0 '\000', 
  header = 0 '\000', 
  cpu = 0 '\000'
}


** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete = New

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

Title:
  Xorg crashes when exiting steam

Status in “xserver-xorg-video-intel” package in Ubuntu:
  New

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: 

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam

[Zygmunt Krynicki]

I just got it, it's still here:

Program received signal SIGSEGV, Segmentation fault.
0x7fa7fcea80a1 in sna_pixmap_set_dri (pixmap=0x7fa802bacbc0, 
sna=0x7fa800454010) at ../../../src/sna/sna_dri.c:186
186 ../../../src/sna/sna_dri.c: Nie ma takiego pliku ani katalogu.

Sadly I could not capture the traceback, perhaps
lightdm/plymouth/upstart somehow kill/respawn something.

I'll try again (following X debugging guidelines)

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

Title:
  Xorg crashes when exiting steam

Status in “xserver-xorg-video-intel” package in Ubuntu:
  New

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Sat Feb 16 21:39:07 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  

[Desktop-packages] [Bug 1127497] Re: Xorg crashes when exiting steam

[Zygmunt Krynicki]

I don't really know what triggers it. I tried a number of activities -
launching steam and immediately exiting it (via menu, indicator, or
accelerator), launching a game (I only tried uplink) and exiting. In the
end I don't see a pattern. I saw crashes immediately after starting and
long after keeping steam open in the background.

The only thing that I could add that is 'odd' is that I have not re-
enabled workspaces after reinstalling the system from scratch.

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

Title:
  Xorg crashes when exiting steam

Status in “xserver-xorg-video-intel” package in Ubuntu:
  New

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
  [196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
  [196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
  [196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
  [196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) 
[0x7f260caffc10]
  [196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
  [196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
  [196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
  [196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7f260a6d2ea5]
  [196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
  [196022.622] (EE) 
  [196022.622] (EE) Segmentation fault at address 0x7e

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.8-0ubuntu4
  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
  Date: Sat Feb 16 21:39:48 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
   virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:3977]
  InstallationDate: Installed on 2013-02-12 (4 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
  MachineType: LENOVO 2189
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5ECN92WW(V8.04)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
  dmi.product.name: 2189
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.42-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.6-0ubuntu2
  xserver.bootTime: Sat Feb 16 21:39:07 2013
  xserver.configfile: default
  xserver.errors:
   
  

[Desktop-packages] [Bug 1127497] [NEW] Xorg crashes when exiting steam

[Zygmunt Krynicki]

Public bug reported:

On current up-to-date raring with equally up-to-date steam (version
should be visible with apport-provided data) exiting steam with the
ALT+F4 shortcut crashes X like this:

[196022.622] (EE) Backtrace:
[196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
[196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
[196022.622] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f260ba85000+0xfbd0) [0x7f260ba94bd0]
[196022.622] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f260922c000+0xd40a1) [0x7f26093000a1]
[196022.622] (EE) 4: /usr/bin/X (0x7f260c97e000+0x180e5c) [0x7f260cafee5c]
[196022.622] (EE) 5: /usr/bin/X (0x7f260c97e000+0x1818cb) [0x7f260caff8cb]
[196022.622] (EE) 6: /usr/bin/X (DRI2GetBuffersWithFormat+0x10) [0x7f260caffc10]
[196022.622] (EE) 7: /usr/bin/X (0x7f260c97e000+0x183690) [0x7f260cb01690]
[196022.622] (EE) 8: /usr/bin/X (0x7f260c97e000+0x58a41) [0x7f260c9d6a41]
[196022.622] (EE) 9: /usr/bin/X (0x7f260c97e000+0x4754a) [0x7f260c9c554a]
[196022.622] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) 
[0x7f260a6d2ea5]
[196022.622] (EE) 11: /usr/bin/X (0x7f260c97e000+0x47891) [0x7f260c9c5891]
[196022.622] (EE) 
[196022.622] (EE) Segmentation fault at address 0x7e

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.8-0ubuntu4
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
Date: Sat Feb 16 21:39:48 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.20.155.1+bdcom, 3.8.0-6-generic, x86_64: installed
 virtualbox, 4.1.22, 3.8.0-6-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3977]
InstallationDate: Installed on 2013-02-12 (4 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210)
MachineType: LENOVO 2189
MarkForUpload: True
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-6-generic.efi.signed 
root=UUID=f4d68fc6-d76a-475e-8d08-80c5eb0cc48e ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/14/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 5ECN92WW(V8.04)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 3193WIN8 STD MLT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G580
dmi.modalias: 
dmi:bvnLENOVO:bvr5ECN92WW(V8.04):bd09/14/2012:svnLENOVO:pn2189:pvrLenovoG580:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoG580:
dmi.product.name: 2189
dmi.product.version: Lenovo G580
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.42-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.2-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2
xserver.bootTime: Sat Feb 16 21:39:07 2013
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.2-0ubuntu2
xserver.video_driver: intel

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


** Tags: amd64 apport-bug compiz-0.9 raring ubuntu

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

Title:
  Xorg crashes when exiting steam

Status in “xserver-xorg-video-intel” package in Ubuntu:
  New

Bug description:
  On current up-to-date raring with equally up-to-date steam (version
  should be visible with apport-provided data) exiting steam with the
  ALT+F4 shortcut crashes X like this:

  [196022.622] (EE) Backtrace:
  [196022.622] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x7f260cb2def6]
  [196022.622] (EE) 1: /usr/bin/X (0x7f260c97e000+0x1b3d39) [0x7f260cb31d39]
  [196022.622] (EE) 

[Desktop-packages] [Bug 1059422] [NEW] [fglrx] ASIC hang happened

[Zygmunt Krynicki]

Public bug reported:

Using daily 12.10 (soon after beta 2), X and console froze randomly this
morning. I could not switch from X to any of the virtual consoles which
was unusual for an display-related problem. I managed to connect via ssh
and found compiz and X stuck at 100% CPU. Syslog indicated that GPU had
frozen. I'm using fglrx 2.9.000-0ubuntu3 with Radeon HD 5450.

Syslog contained a section that describes the crash:

Oct  1 09:09:14 fx kernel: [ 2615.832077] DRHD: handling fault status reg 2
Oct  1 09:09:14 fx kernel: [ 2615.832084] INTR-REMAP: Request device [[00:00.0] 
fault index 2b
Oct  1 09:09:14 fx kernel: [ 2615.832084] INTR-REMAP:[fault reason 38] Blocked 
an interrupt request due to source-id verification failure
Oct  1 09:09:14 fx kernel: [ 2615.832089] INTR-REMAP: Request device [[00:00.1] 
fault index 2a
Oct  1 09:09:14 fx kernel: [ 2615.832089] INTR-REMAP:[fault reason 38] Blocked 
an interrupt request due to source-id verification failure
Oct  1 09:12:14 fx kernel: [ 2795.772989] [fglrx] ASIC hang happened
Oct  1 09:12:14 fx kernel: [ 2795.772994] Pid: 1591, comm: Xorg Tainted: P  
 O 3.5.0-16-generic #25-Ubuntu
Oct  1 09:12:14 fx kernel: [ 2795.772995] Call Trace:
Oct  1 09:12:14 fx kernel: [ 2795.773042]  [a01ab2fe] 
KCL_DEBUG_OsDump+0xe/0x10 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773072]  [a01b99bc] 
firegl_hardwareHangRecovery+0x1c/0x60 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773126]  [a023d4a9] ? 
_ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773179]  [a023d433] ? 
_ZN4Asic9WaitUntil15WaitForCompleteEv+0x93/0x100 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773235]  [a02507ee] ? 
_ZN15ExecutableUnits10CPRingIdleE15idle_WaitMethod12_QS_CP_RING_+0x11e/0x1e0 
[fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773292]  [a025067b] ? 
_ZN15ExecutableUnits7PM4idleE15idle_WaitMethod+0x4b/0x90 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773347]  [a0244d71] ? 
_ZN15QS_PRIVATE_CORE9QsPM4idleE15idle_WaitMethod+0x31/0x60 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773397]  [a022db8e] ? 
_ZN10QS_PRIVATE11synchronizeEv+0xce/0xe0 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773449]  [a0237848] ? 
_Z8uCWDDEQCmjjPvjS_+0x448/0x1200 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773452]  [8107c29e] ? down+0x2e/0x50
Oct  1 09:12:14 fx kernel: [ 2795.773488]  [a01e058f] ? 
firegl_cmmqs_CWDDE_32+0x36f/0x480 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773523]  [a01dedce] ? 
firegl_cmmqs_CWDDE32+0x8e/0x140 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773527]  [8105edd7] ? 
capable+0x17/0x20
Oct  1 09:12:14 fx kernel: [ 2795.773562]  [a01ded40] ? 
firegl_cmmqs_disabledriver+0x120/0x120 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773590]  [a01b494d] ? 
firegl_ioctl+0x1ed/0x250 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773611]  [a01a4ace] ? 
ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx]
Oct  1 09:12:14 fx kernel: [ 2795.773615]  [81193ab9] ? 
do_vfs_ioctl+0x99/0x590
Oct  1 09:12:14 fx kernel: [ 2795.773617]  [81194049] ? 
sys_ioctl+0x99/0xa0
Oct  1 09:12:14 fx kernel: [ 2795.773620]  [81689569] ? 
system_call_fastpath+0x16/0x1b
Oct  1 09:12:14 fx kernel: [ 2795.773623] pubdev:0xa0585180, num of 
device:1 , name:fglrx, major 9, minor 0. 
Oct  1 09:12:14 fx kernel: [ 2795.773625] device 0 : 0x8801b5588000 .
Oct  1 09:12:14 fx kernel: [ 2795.773626] Asic ID:0x68f9, revision:0x3c, 
MMIOReg:0xc90011e0.
Oct  1 09:12:14 fx kernel: [ 2795.773627] FB phys addr: 0xd000, MC 
:0xf, Total FB size :0x4000.
Oct  1 09:12:14 fx kernel: [ 2795.773629] gart table MC:0xf0f8fc000, 
Physical:0xdf8fc000, size:0x403000.
Oct  1 09:12:14 fx kernel: [ 2795.773630] mc_node :FB, total 1 zones
Oct  1 09:12:14 fx kernel: [ 2795.773632] MC start:0xf, 
Physical:0xd000, size:0xfd0.
Oct  1 09:12:14 fx kernel: [ 2795.773633] Mapped heap -- Offset:0x0, 
size:0xf8fc000, reference count:66, mapping count:0,
Oct  1 09:12:14 fx kernel: [ 2795.773635] Mapped heap -- Offset:0x0, 
size:0x100, reference count:1, mapping count:0,
Oct  1 09:12:14 fx kernel: [ 2795.773636] Mapped heap -- Offset:0xf8fc000, 
size:0x404000, reference count:1, mapping count:0,
Oct  1 09:12:14 fx kernel: [ 2795.773637] mc_node :INV_FB, total 1 zones
Oct  1 09:12:14 fx kernel: [ 2795.773639] MC start:0xf0fd0, 
Physical:0xdfd0, size:0x3030.
Oct  1 09:12:14 fx kernel: [ 2795.773640] Mapped heap -- Offset:0x302f4000, 
size:0xc000, reference count:1, mapping count:0,
Oct  1 09:12:14 fx kernel: [ 2795.773641] mc_node :GART_USWC, total 3 zones
Oct  1 09:12:14 fx kernel: [ 2795.773642] MC start:0x4010, 
Physical:0x0, size:0x5000.
Oct  1 09:12:14 fx kernel: [ 2795.773644] Mapped heap -- Offset:0x300, 
size:0x80, reference count:1, mapping count:0,
Oct  1 09:12:14 fx kernel: [ 2795.773645] Mapped 

[Desktop-packages] [Bug 1059422] Re: [fglrx] ASIC hang happened

[Zygmunt Krynicki]

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

Title:
  [fglrx] ASIC hang happened

Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
  Using daily 12.10 (soon after beta 2), X and console froze randomly
  this morning. I could not switch from X to any of the virtual consoles
  which was unusual for an display-related problem. I managed to connect
  via ssh and found compiz and X stuck at 100% CPU. Syslog indicated
  that GPU had frozen. I'm using fglrx 2.9.000-0ubuntu3 with Radeon HD
  5450.

  Syslog contained a section that describes the crash:

  Oct  1 09:09:14 fx kernel: [ 2615.832077] DRHD: handling fault status reg 2
  Oct  1 09:09:14 fx kernel: [ 2615.832084] INTR-REMAP: Request device 
[[00:00.0] fault index 2b
  Oct  1 09:09:14 fx kernel: [ 2615.832084] INTR-REMAP:[fault reason 38] 
Blocked an interrupt request due to source-id verification failure
  Oct  1 09:09:14 fx kernel: [ 2615.832089] INTR-REMAP: Request device 
[[00:00.1] fault index 2a
  Oct  1 09:09:14 fx kernel: [ 2615.832089] INTR-REMAP:[fault reason 38] 
Blocked an interrupt request due to source-id verification failure
  Oct  1 09:12:14 fx kernel: [ 2795.772989] [fglrx] ASIC hang happened
  Oct  1 09:12:14 fx kernel: [ 2795.772994] Pid: 1591, comm: Xorg Tainted: P
   O 3.5.0-16-generic #25-Ubuntu
  Oct  1 09:12:14 fx kernel: [ 2795.772995] Call Trace:
  Oct  1 09:12:14 fx kernel: [ 2795.773042]  [a01ab2fe] 
KCL_DEBUG_OsDump+0xe/0x10 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773072]  [a01b99bc] 
firegl_hardwareHangRecovery+0x1c/0x60 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773126]  [a023d4a9] ? 
_ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773179]  [a023d433] ? 
_ZN4Asic9WaitUntil15WaitForCompleteEv+0x93/0x100 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773235]  [a02507ee] ? 
_ZN15ExecutableUnits10CPRingIdleE15idle_WaitMethod12_QS_CP_RING_+0x11e/0x1e0 
[fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773292]  [a025067b] ? 
_ZN15ExecutableUnits7PM4idleE15idle_WaitMethod+0x4b/0x90 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773347]  [a0244d71] ? 
_ZN15QS_PRIVATE_CORE9QsPM4idleE15idle_WaitMethod+0x31/0x60 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773397]  [a022db8e] ? 
_ZN10QS_PRIVATE11synchronizeEv+0xce/0xe0 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773449]  [a0237848] ? 
_Z8uCWDDEQCmjjPvjS_+0x448/0x1200 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773452]  [8107c29e] ? 
down+0x2e/0x50
  Oct  1 09:12:14 fx kernel: [ 2795.773488]  [a01e058f] ? 
firegl_cmmqs_CWDDE_32+0x36f/0x480 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773523]  [a01dedce] ? 
firegl_cmmqs_CWDDE32+0x8e/0x140 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773527]  [8105edd7] ? 
capable+0x17/0x20
  Oct  1 09:12:14 fx kernel: [ 2795.773562]  [a01ded40] ? 
firegl_cmmqs_disabledriver+0x120/0x120 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773590]  [a01b494d] ? 
firegl_ioctl+0x1ed/0x250 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773611]  [a01a4ace] ? 
ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx]
  Oct  1 09:12:14 fx kernel: [ 2795.773615]  [81193ab9] ? 
do_vfs_ioctl+0x99/0x590
  Oct  1 09:12:14 fx kernel: [ 2795.773617]  [81194049] ? 
sys_ioctl+0x99/0xa0
  Oct  1 09:12:14 fx kernel: [ 2795.773620]  [81689569] ? 
system_call_fastpath+0x16/0x1b
  Oct  1 09:12:14 fx kernel: [ 2795.773623] pubdev:0xa0585180, num of 
device:1 , name:fglrx, major 9, minor 0. 
  Oct  1 09:12:14 fx kernel: [ 2795.773625] device 0 : 0x8801b5588000 .
  Oct  1 09:12:14 fx kernel: [ 2795.773626] Asic ID:0x68f9, revision:0x3c, 
MMIOReg:0xc90011e0.
  Oct  1 09:12:14 fx kernel: [ 2795.773627] FB phys addr: 0xd000, MC 
:0xf, Total FB size :0x4000.
  Oct  1 09:12:14 fx kernel: [ 2795.773629] gart table MC:0xf0f8fc000, 
Physical:0xdf8fc000, size:0x403000.
  Oct  1 09:12:14 fx kernel: [ 2795.773630] mc_node :FB, total 1 zones
  Oct  1 09:12:14 fx kernel: [ 2795.773632] MC start:0xf, 
Physical:0xd000, size:0xfd0.
  Oct  1 09:12:14 fx kernel: [ 2795.773633] Mapped heap -- Offset:0x0, 
size:0xf8fc000, reference count:66, mapping count:0,
  Oct  1 09:12:14 fx kernel: [ 2795.773635] Mapped heap -- Offset:0x0, 
size:0x100, reference count:1, mapping count:0,
  Oct  1 09:12:14 fx kernel: [ 2795.773636] Mapped heap -- 
Offset:0xf8fc000, size:0x404000, reference count:1, mapping count:0,
  Oct  1 09:12:14 fx kernel: [ 2795.773637] mc_node :INV_FB, total 1 zones
  Oct  1 09:12:14 fx kernel: [ 2795.773639] MC start:0xf0fd0, 
Physical:0xdfd0, size:0x3030.
  Oct  1 09:12:14 fx kernel: [ 2795.773640] Mapped heap -- 
Offset:0x302f4000, size:0xc000, reference count:1, mapping count:0,
  

[Desktop-packages] [Bug 1048387] [NEW] Banshee crashes when gapless playback is enabled

[Zygmunt Krynicki]

Public bug reported:

Banshee is crashing at the end of the current track every time.

The exception is coming from native code, around dbus.

After some trial and error I've determined that disabling gapless
playback makes the problem go away

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: banshee 2.4.1-3ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sun Sep  9 22:56:09 2012
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: banshee
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug quantal running-unity

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

Title:
  Banshee crashes when gapless playback is enabled

Status in “banshee” package in Ubuntu:
  New

Bug description:
  Banshee is crashing at the end of the current track every time.

  The exception is coming from native code, around dbus.

  After some trial and error I've determined that disabling gapless
  playback makes the problem go away

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: banshee 2.4.1-3ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Sun Sep  9 22:56:09 2012
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1048387] Re: Banshee crashes when gapless playback is enabled

[Zygmunt Krynicki]

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

Title:
  Banshee crashes when gapless playback is enabled

Status in “banshee” package in Ubuntu:
  New

Bug description:
  Banshee is crashing at the end of the current track every time.

  The exception is coming from native code, around dbus.

  After some trial and error I've determined that disabling gapless
  playback makes the problem go away

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: banshee 2.4.1-3ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Sun Sep  9 22:56:09 2012
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120905.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 804662] Re: jockey-gtk crashed with TypeError in _execute_child(): execv() arg 2 must contain only strings

[Zygmunt Krynicki]

Still on 26th March

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

Title:
  jockey-gtk crashed with TypeError in _execute_child(): execv() arg 2
  must contain only strings

Status in “jockey” package in Ubuntu:
  Confirmed

Bug description:
  just came up during ATI driver installation

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: jockey-gtk 0.9.2-0ubuntu7
  ProcVersionSignature: Ubuntu 3.0-2.3-generic-pae 3.0.0-rc4
  Uname: Linux 3.0-2-generic-pae i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Sat Jul  2 04:31:30 2011
  ExecutablePath: /usr/bin/jockey-gtk
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110701)
  InterpreterPath: /usr/bin/python2.7
  MachineType: System manufacturer System Product Name
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/jockey-gtk
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0-2-generic-pae 
root=UUID=69fb0a75-ad30-41d2-a270-fa5b2ac7d56d ro quiet splash vt.handoff=7
  PythonArgs: ['/usr/bin/jockey-gtk']
  SourcePackage: jockey
  Title: jockey-gtk crashed with TypeError in _execute_child(): execv() arg 2 
must contain only strings
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 04/14/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0906
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A785-M
  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.:bvr0906:bd04/14/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 965641] Re: Gnome control center crashes in bluetooth applet while clicking on the sound settings of a bluetooth headset

[Zygmunt Krynicki]

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

Title:
  Gnome control center crashes in bluetooth applet while clicking on the
  sound settings of a bluetooth headset

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

Bug description:
  I've got the PS3-EX01 bluetooth headset. I'm trying to pair it with my
  Precise desktop via a USB bluetooth dongle.

  Pairing works but attempting to use it as a sound device crashes the
  configuration applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.3.92-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 26 21:55:27 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 965641] [NEW] Gnome control center crashes in bluetooth applet while clicking on the sound settings of a bluetooth headset

[Zygmunt Krynicki]

Public bug reported:

I've got the PS3-EX01 bluetooth headset. I'm trying to pair it with my
Precise desktop via a USB bluetooth dongle.

Pairing works but attempting to use it as a sound device crashes the
configuration applet.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.3.92-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
Date: Mon Mar 26 21:55:27 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120218)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug precise

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

Title:
  Gnome control center crashes in bluetooth applet while clicking on the
  sound settings of a bluetooth headset

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

Bug description:
  I've got the PS3-EX01 bluetooth headset. I'm trying to pair it with my
  Precise desktop via a USB bluetooth dongle.

  Pairing works but attempting to use it as a sound device crashes the
  configuration applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.3.92-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.95-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 26 21:55:27 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 953166] [NEW] Banshee should slow down the drive while playing CD audio

[Zygmunt Krynicki]

Public bug reported:

Playing Audio CDs has poor user experience as the drive is spinning like
crazy. To work around that I manually resort to running hdparm -E 1
/dev/sr0 but it would be nice if banshee did this by default

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: banshee 2.3.6-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Mon Mar 12 17:15:39 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120218)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: banshee
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug precise

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

Title:
  Banshee should slow down the drive while playing CD audio

Status in “banshee” package in Ubuntu:
  New

Bug description:
  Playing Audio CDs has poor user experience as the drive is spinning
  like crazy. To work around that I manually resort to running hdparm -E
  1 /dev/sr0 but it would be nice if banshee did this by default

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: banshee 2.3.6-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Mon Mar 12 17:15:39 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 953166] Re: Banshee should slow down the drive while playing CD audio

[Zygmunt Krynicki]

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

Title:
  Banshee should slow down the drive while playing CD audio

Status in “banshee” package in Ubuntu:
  New

Bug description:
  Playing Audio CDs has poor user experience as the drive is spinning
  like crazy. To work around that I manually resort to running hdparm -E
  1 /dev/sr0 but it would be nice if banshee did this by default

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: banshee 2.3.6-1ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  Date: Mon Mar 12 17:15:39 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120218)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 947899] Re: Empty cancel button while installing application

[Zygmunt Krynicki]

** Attachment added: Screenshot of the problem with the empty button 
highlighted
   
https://bugs.launchpad.net/bugs/947899/+attachment/2821869/+files/software-center-empty-button-bug.png

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

Title:
  Empty cancel button while installing application

Status in “software-center” package in Ubuntu:
  New

Bug description:
  While installing any application in the software center the there is
  an empty button next to the progress bar.

  Steps to reproduce:

  1) Open software center
  2) Pick or search for an application
  3) Click on the install button

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: software-center 5.1.11
  ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
  Uname: Linux 3.2.0-18-generic x86_64
  ApportVersion: 1.94-0ubuntu1
  Architecture: amd64
  Date: Tue Mar  6 12:15:39 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120218)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 893529] Re: Window title ellipsis (when text does not fit) is oddly transparent

[Zygmunt Krynicki]

I can see this problem very often. Perhaps it goes away after logging in
(some times) but I can see it basically every day on each window that I
have.

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

Title:
  Window title ellipsis (when text does not fit) is oddly transparent

Status in Unity:
  New
Status in “metacity” package in Ubuntu:
  New

Bug description:
  This can be seen on any window with sufficiently long title and
  sufficiently small window. The text is cut off on the right with an
  ellipsis (three dots). The problem is that the rightmost part of the
  text becomes transparent and looks very strange.

  I have a screenshot (attached) that illustrates this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.24.0-0ubuntu2b1
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: compiz
  Date: Tue Nov 22 11:45:03 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.1.6, 3.0.0-13-generic, x86_64: installed
  GraphicsCard:
   nVidia Corporation GT216 [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo Device [17aa:2145]
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MachineType: LENOVO 4318CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-13-generic 
root=UUID=57a36408-e446-4575-9011-202b214b0bf4 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6NET76WW (1.37 )
  dmi.board.name: 4318CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6NET76WW(1.37):bd02/24/2011:svnLENOVO:pn4318CTO:pvrThinkPadW510:rvnLENOVO:rn4318CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4318CTO
  dmi.product.version: ThinkPad W510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.15.901-1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

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

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

[Desktop-packages] [Bug 886907] Re: Messaging Menu and Unity launcher does not display unread messages count from Thunderbird

[Zygmunt Krynicki]

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

** Summary changed:

- Messaging Menu and Unity launcher don't display unread messages count from 
Thunderbird
+ Messaging Menu and Unity launcher does not display unread messages count from 
Thunderbird

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

Title:
  Messaging Menu and Unity launcher does not display unread messages
  count from Thunderbird

Status in “thunderbird” package in Ubuntu:
  New

Bug description:
  I made a clean install of Oneiric (64bits edition) using all defaults options 
and now, when I receive new messages in Thunderbird, the letter from the 
Messaging Menu doesn't turn blue and I don't have any update of the message 
count in the Menu either.
  This was working fine previously when I was running Natty. I use two e-mail 
accounts which both use the IMAP protocols.

  The only three fields visible in the Messaging Menu, in the e-mail part, are 
: Mail, Compose New Message and Contacts which work as they should be.
  Whether I enable the Messaging Menu and Unity Integration Add-on in 
Thunderbird or not, the problem is still here.
  In the other hand, the on-screen notifications work perfectly.

  I also discovered that the Thunderbird Unity launcher might also
  display unread messages count. If this is the case, it not working
  either.

  While looking for such an already described bug in launchpad, I found bug 
#850229 being similar but not identical. I think the bug I report here might be 
different because i) I never have any update on the Unity launcher and ii) I 
don't have any update either of the unread messages count in the messaging 
menu. I think the case of bug #850229 was related to a wrong value of unread 
messages and not to the total absence of this value.
  In the discussion about bug #850299, comment #4 seems to correspond to the 
bug I report here.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: thunderbird 7.0.1+build1+nobinonly-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lionel 1915 F pulseaudio
   /dev/snd/pcmC0D0p:   lionel 1915 F...m pulseaudio
  BuildID: 20110929183320
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf040 irq 46'
     Mixer name : 'Nvidia MCP77/78 HDMI'
     Components : 'HDA:10ec0888,1025015e,00100202 
HDA:14f12c06,1025015e,0010 HDA:10de0006,10de0101,0010'
     Controls  : 29
     Simple ctrls  : 16
  Channel: release
  Date: Sun Nov  6 20:45:43 2011
  ExecutablePath: /usr/lib/thunderbird-7.0.1/thunderbird-bin
  ForcedLayersAccel: False
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  IpRoute:
   default dev tun0  proto static
   169.254.0.0/16 dev wlan0  scope link  metric 1000
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.4  metric 2
   193.10.16.0/22 dev tun0  proto kernel  scope link  src 193.10.16.103
   193.10.16.3 via 192.168.1.1 dev wlan0  proto static
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=7.0.1/20110929183320 (Running)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3121
  dmi.board.name: Makalu
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3121:bd09/12/2008:svnAcer,inc.:pnAspire6930G:pvrNotApplicable:rvnAcer,Inc.:rnMakalu:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 6930G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

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

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

[Desktop-packages] [Bug 880771] Re: Unable to shut down (from either lightdm or unity session)

[Zygmunt Krynicki]

I ran ck-list-sessions, interesting output.

It seems that rabbitmq-server is listed as a logged in user account.

** Attachment added: Output of ck-list-sessions with me logged in in Unity on 
tty7 and another me logged in on vt1
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/880771/+attachment/2571349/+files/sessions.txt

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

Title:
  Unable to shut down (from either lightdm or unity session)

Status in “gnome-session” package in Ubuntu:
  Incomplete

Bug description:
  Shutting down the computer from Unity logs me out (or crashes, hard to
  tell) to lightdm. Attempting to shut down from lightdm does nothing at
  all. This is a fresh Oneiric installation (not an upgrade) on Lenovo
  W510, with free software drivers (Nvidia Quadro 880FX)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 1.0.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 24 12:30:39 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 880771] [NEW] Unable to shut down (from either lightdm or unity session)

[Zygmunt Krynicki]

Public bug reported:

Shutting down the computer from Unity logs me out (or crashes, hard to
tell) to lightdm. Attempting to shut down from lightdm does nothing at
all. This is a fresh Oneiric installation (not an upgrade) on Lenovo
W510, with free software drivers (Nvidia Quadro 880FX)

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: lightdm 1.0.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Mon Oct 24 12:30:39 2011
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
ProcEnviron:
 PATH=(custom, user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug oneiric running-unity

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

Title:
  Unable to shut down (from either lightdm or unity session)

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Shutting down the computer from Unity logs me out (or crashes, hard to
  tell) to lightdm. Attempting to shut down from lightdm does nothing at
  all. This is a fresh Oneiric installation (not an upgrade) on Lenovo
  W510, with free software drivers (Nvidia Quadro 880FX)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 1.0.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 24 12:30:39 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 880771] Re: Unable to shut down (from either lightdm or unity session)

[Zygmunt Krynicki]

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

Title:
  Unable to shut down (from either lightdm or unity session)

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Shutting down the computer from Unity logs me out (or crashes, hard to
  tell) to lightdm. Attempting to shut down from lightdm does nothing at
  all. This is a fresh Oneiric installation (not an upgrade) on Lenovo
  W510, with free software drivers (Nvidia Quadro 880FX)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 1.0.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 24 12:30:39 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   PATH=(custom, user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 119693] Re: xchat-gnome 0.17 crashes on startup

[Zygmunt Krynicki]

This started happening for me mid-cycle in Natty, just tested on a fresh
Oneiric install, could this be re-opened?

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

Title:
  xchat-gnome 0.17 crashes on startup

Status in “xchat-gnome” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: xchat-gnome

  xchat-gnome 0.17 crashes on startup when it tries to display the initial 
setup dialog.
  This bug has already been fixed in the upstream SVN version.
  I'm attaching two patches that fix this bug.

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

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