Re: [Desktop-packages] [Bug 1633912] Re: Problem with DNS resolution after suspend

2016-10-22 Thread Jonas Schwabe 
Workaround worked for me and fixed multiple issues! I can use DNS while
being connected to a VPN again :)

Plurtu <1633...@bugs.launchpad.net> schrieb am Sa., 22. Okt. 2016,
10:25:

> More people with the same problem:
> https://ubuntuforums.org/showthread.php?t=2340142
>
> Workaround: Edit /etc/NetworkManager/NetworkManager.conf and remove the
> line "dns=dnsmasq".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1633912
>
> Title:
>   Problem with DNS resolution after suspend
>
> Status in network-manager package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I
>   have network issues, one time I was not able to connect to a wifi
>   network (might report another bug if this occurees again, but maybe it
>   is related, as in network-manager is in some broken state after
>   suspend).
>
>   Here is whats happening pretty often: After resume from suspend I have
>   a solid network connection, no problem to ping machines in LAN or on
>   the internet. But DNS resolution is broken until I restart the
>   network-manager service.
>
>   I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it
>   should be in there.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: network-manager 1.2.4-0ubuntu1
>   ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
>   Uname: Linux 4.8.0-22-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu8
>   Architecture: amd64
>   CurrentDesktop: Unity
>   Date: Sun Oct 16 21:01:09 2016
>   IfupdownConfig:
># interfaces(5) file used by ifup(8) and ifdown(8)
>auto lo
>iface lo inet loopback
>   InstallationDate: Installed on 2016-09-28 (18 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
>   IpRoute:
>default via 192.168.0.1 dev wlp58s0  proto static  metric 600
>169.254.0.0/16 dev br-541a0f9bec93  scope link  metric 1000
>172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1
> linkdown
>172.18.0.0/16 dev br-541a0f9bec93  proto kernel  scope link  src
> 172.18.0.1
>192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src
> 192.168.0.118  metric 600
>   NetworkManager.state:
>[main]
>NetworkingEnabled=true
>WirelessEnabled=true
>WWANEnabled=true
>   SourcePackage: network-manager
>   UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
>   nmcli-nm:
>RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING
> WIFI-HW  WIFI WWAN-HW  WWAN
>running  1.2.4connected  started  full  enabled
>  enabled  enabled  enabled  enabled
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+subscriptions
>

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

Title:
  Problem with DNS resolution after suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I
  have network issues, one time I was not able to connect to a wifi
  network (might report another bug if this occurees again, but maybe it
  is related, as in network-manager is in some broken state after
  suspend).

  Here is whats happening pretty often: After resume from suspend I have
  a solid network connection, no problem to ping machines in LAN or on
  the internet. But DNS resolution is broken until I restart the
  network-manager service.

  I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it
  should be in there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 21:01:09 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-09-28 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev br-541a0f9bec93  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-541a0f9bec93  proto kernel  scope link  src 172.18.0.1 
   192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.0.118  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW

[Desktop-packages] [Bug 1633912] Re: Problem with DNS resolution after suspend

2016-10-16 Thread Jonas Schwabe 
▶ sudo killall dnsmasq
Works as well, afterwards things work again.

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

Title:
  Problem with DNS resolution after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I
  have network issues, one time I was not able to connect to a wifi
  network (might report another bug if this occurees again, but maybe it
  is related, as in network-manager is in some broken state after
  suspend).

  Here is whats happening pretty often: After resume from suspend I have
  a solid network connection, no problem to ping machines in LAN or on
  the internet. But DNS resolution is broken until I restart the
  network-manager service.

  I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it
  should be in there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 21:01:09 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-09-28 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev br-541a0f9bec93  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-541a0f9bec93  proto kernel  scope link  src 172.18.0.1 
   192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.0.118  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1633912] [NEW] Problem with DNS resolution after suspend

2016-10-16 Thread Jonas Schwabe 
Public bug reported:

I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I have
network issues, one time I was not able to connect to a wifi network
(might report another bug if this occurees again, but maybe it is
related, as in network-manager is in some broken state after suspend).

Here is whats happening pretty often: After resume from suspend I have a
solid network connection, no problem to ping machines in LAN or on the
internet. But DNS resolution is broken until I restart the network-
manager service.

I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it
should be in there.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 16 21:01:09 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-09-28 (18 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.0.1 dev wlp58s0  proto static  metric 600 
 169.254.0.0/16 dev br-541a0f9bec93  scope link  metric 1000 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
 172.18.0.0/16 dev br-541a0f9bec93  proto kernel  scope link  src 172.18.0.1 
 192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.0.118  
metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Problem with DNS resolution after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I
  have network issues, one time I was not able to connect to a wifi
  network (might report another bug if this occurees again, but maybe it
  is related, as in network-manager is in some broken state after
  suspend).

  Here is whats happening pretty often: After resume from suspend I have
  a solid network connection, no problem to ping machines in LAN or on
  the internet. But DNS resolution is broken until I restart the
  network-manager service.

  I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it
  should be in there.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Oct 16 21:01:09 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-09-28 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev br-541a0f9bec93  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   172.18.0.0/16 dev br-541a0f9bec93  proto kernel  scope link  src 172.18.0.1 
   192.168.0.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.0.118  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.4connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://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 1068404] Re: Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx upgrade

2013-08-01 Thread Jonas Schwabe 
I installed the new beta of fglrx without installing a non default intel
driver on 13.04 and it works, there are some other bugs in this driver
thought. On high performance mode  can't use dual head for example but the
initial bug is fixed.

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

Title:
  Low graphics mode in muxless hybrid ATI/Intel GPU systems after fglrx
  upgrade

Status in X.org xf86-video-intel:
  Won't Fix
Status in “fglrx-installer” package in Ubuntu:
  In Progress
Status in “fglrx-installer-updates” package in Ubuntu:
  Triaged
Status in “fglrx-installer” source package in Quantal:
  Confirmed
Status in “fglrx-installer-updates” source package in Quantal:
  Triaged
Status in “xserver-xorg-video-intel” package in openSUSE:
  In Progress

Bug description:
  [Impact]

   * Hybrid systems with ATI/intel GPUs using fglrx get a segmentation
  fault in X when using 12.10. In stock 12.04.1 these systems were
  working fine.

   * This bug represents a severe regression from precise to quantal,
  since is crashing on startup

   * The proposed patch updates the driver to version 13.2beta3 of
  upstream which seems to resolve this issue

  [Test Case]

   * Get an hybrid ATI/intel system.
     Install quantal: The system should boot fine
     Install the proprietary fglrx package and reboot: The X server crashes on 
startup

  [Regression Potential]

   * This solution does not need any change on the intel driver (as a previous 
workaround needed).
   * No regressions have been reported so far using this most recent fglrx 
upstream, by the people affected by this bug

  ==

  After installing the latest fglrx-updates package on Ubuntu 12.10
  (fglrx-updates_9.000-0ubuntu3_amd64) I have the same issue that was
  present before AMD fixed switchable graphics on PowerXpress 4.0 cards
  (such as my HD 6470M coupled with the intel HD Graphics 3000 of my
  intel Core i5-2430M). The X server has a segmentation fault and the
  low graphics mode is activated.

  WORKAROUND: fglrx-installer-13 2:13.101~beta-0ubuntu1~xedgers~quantal1 from:
  https://launchpad.net/~xorg-edgers/+archive/ppa?field.series_filter=quantal

  WORKAROUND: Follow carefully the instructions here:
  https://help.ubuntu.com/community/BinaryDriverHowto/ATI#WORKAROUND

  As per Nick Andrik, this is a version regression of xserver-xorg-
  video-intel from 2.20.2 (working and in below mentioned PPA) and
  2.20.3. The regression commit is
  http://cgit.freedesktop.org/xorg/driver/xf86-video-
  intel/commit/?id=05dcc5f1699ba90fc14c50882e8d4be89bc4a4f9 .

  Upstream fglrx has published a new version (> 13.1 ) of the driver
  which seems to solve this issue. No need to revert the commit in the
  Intel driver any more.

  ATTENTION:
  1. If you choose the integrated GPU (via Catalyst or via amdconfig --px-igpu) 
and your X server crashes on startup, then your are probably affected by this 
bug:
  https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1088220

  2. If your system includes an old ATI GPU card (Radeon HD 2x00 3x00 4x00) 
which is not supported any more by fglrx drivers, then probably you suffer from 
this bug:
  https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1058040
  Subscribe and comment there please.

  If the X server loads (so you see no low graphics mode window) but you get no 
menu bars, window decorations, etc, then press Ctrl+Shift+T to open a terminal, 
write in there:
  unity --replace &
  and post a comment with the result.

  The logs from the intial bug report follow:

  Here is the Xorg log:
  [20.924]
  X.Org X Server 1.13.0
  Release Date: 2012-09-05
  [20.924] X Protocol Version 11, Revision 0
  [20.924] Build Operating System: Linux 3.2.0-30-generic x86_64 Ubuntu
  [20.924] Current Operating System: Linux marco-HP-Pavilion-g6-Notebook-PC 
3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64
  [20.924] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=5374f779-2ae8-4842-a390-e21317364c6c ro quiet splash vt.handoff=7
  [20.924] Build Date: 08 October 2012  03:34:01PM
  [20.924] xorg-server 2:1.13.0-0ubuntu6 (For technical support please see 
http://www.ubuntu.com/support)
  [20.924] Current version of pixman: 0.26.0
  [20.924]  Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [20.924] Markers: (--) probed, (**) from config file, (==) default 
setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [20.924] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Oct 19 02:42:21 
2012
  [20.924] (==) Using config file: "/etc/X11/xorg.conf"
  [20.924] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [20.924] (==) ServerLayout "aticonf

[Desktop-packages] [Bug 1057489] Re: colord-sane crashed with SIGABRT in raise()

2012-09-27 Thread Jonas Schwabe 
*** This bug is a duplicate of bug 1027139 ***
https://bugs.launchpad.net/bugs/1027139


** Visibility changed to: Public

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

Title:
  colord-sane crashed with SIGABRT in raise()

Status in “colord” package in Ubuntu:
  New

Bug description:
  I am unable to reproduce this crash again. It happened somewhen after
  closing Dash. However I don't know if this is related.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: colord 0.1.21-1ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  Date: Thu Sep 27 13:51:49 2012
  ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord-sane
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64+mac (20120922)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord-sane
  ProcEnviron:
   
  Signal: 6
  SourcePackage: colord
  StacktraceTop:
   raise () from /lib/x86_64-linux-gnu/libc.so.6
   abort () from /lib/x86_64-linux-gnu/libc.so.6
   ?? () from /lib/x86_64-linux-gnu/libc.so.6
   __fortify_fail () from /lib/x86_64-linux-gnu/libc.so.6
   __chk_fail () from /lib/x86_64-linux-gnu/libc.so.6
  Title: colord-sane crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Desktop-packages] [Bug 1043458] Re: Xorg crashed with SIGABRT in SetCompatOutput()

2012-09-20 Thread Jonas Schwabe 
Blacklisting radeon is a work around. Using catalyst should work as well
I guess.

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

Title:
  Xorg crashed with SIGABRT in SetCompatOutput()

Status in “xorg-server” package in Ubuntu:
  Confirmed

Bug description:
  Trying to boot a gui from a usb live image. low graphics mode appears and 
won't let me navigate options to repair - no mouse cursor.
  Copied xorg.conf.failsafe to xorg.conf
  a desktop gui then displays afetr servcie lightdm restart but no panel, dash 
etc
  from a pseudo terminal compiz --replace fails

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-core 2:1.12.99.905-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3
  Uname: Linux 3.5.0-13-generic x86_64
  ApportVersion: 2.5.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.321
  Date: Wed Aug 29 17:40:09 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3389]
   Advanced Micro Devices [AMD] nee ATI Whistler XT [AMD Radeon HD 6700M 
Series] [1002:6740] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3389]
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120824)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcCmdline: X -br -ac -noreset -nolisten tcp vt7 :0
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent 
file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   xf86SetScrnInfoModes ()
   xf86InitialConfiguration ()
   ?? () from /usr/lib/xorg/modules/drivers/modesetting_drv.so
   ?? () from /usr/lib/xorg/modules/drivers/modesetting_drv.so
   InitOutput ()
  Title: Xorg crashed with SIGABRT in xf86SetScrnInfoModes()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/05/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1B
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3389
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 10.31
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1B:bd10/05/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058C11244720001620100:rvnHewlett-Packard:rn3389:rvr10.31:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: 058C11244720001620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.38-0ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.1-4~ubuntu1

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

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

[Desktop-packages] [Bug 1052151] Re: Xorg crash - Current live CD

2012-09-17 Thread Jonas Schwabe 
Blacklisting radeon is a workaround.
The intel driver should be priorized automaticaly as the radeon driver does not 
support this configuration (it even did not in 12.04).

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

Title:
  Xorg crash - Current live CD

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My laptop won't boot with the current live builds. After the greeting screen 
xorg crashes and shows low graphic mode informations.
  I have a hybrid graphics configuration which worked on 12.04.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.323
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Sep 17 19:34:03 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04cc]
   Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
     Subsystem: Dell Vostro 3350 [1028:04cc]
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120917)
  MachineType: Dell Inc. Vostro 3350
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0M516T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/30/2011:svnDellInc.:pnVostro3350:pvrNotSpecified:rvnDellInc.:rn0M516T:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3350
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.8.0-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.7-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu1

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

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

[Desktop-packages] [Bug 1052151] Re: Xorg crash - Current live CD

2012-09-17 Thread Jonas Schwabe 
** Summary changed:

- Xorg crash
+ Xorg crash - Current live CD

** Description changed:

- With the current live builds I have issues to boot my laptop. After the 
greeting screen xorg crashes and shows low graphic mode informations. 
- I have a hybrid graphics configuration.
+ My laptop won't boot with the current live builds. After the greeting screen 
xorg crashes and shows low graphic mode informations.
+ I have a hybrid graphics configuration which worked on 12.04.
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.323
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Sep 17 19:34:03 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: Dell Device [1028:04cc]
-  Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
-Subsystem: Dell Vostro 3350 [1028:04cc]
+  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Dell Device [1028:04cc]
+  Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
+    Subsystem: Dell Vostro 3350 [1028:04cc]
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120917)
  MachineType: Dell Inc. Vostro 3350
  ProcEnviron:
-  TERM=linux
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=linux
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0M516T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/30/2011:svnDellInc.:pnVostro3350:pvrNotSpecified:rvnDellInc.:rn0M516T:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3350
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.8.0-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.7-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu1

** Attachment removed: "full backtrace"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052151/+attachment/3321061/+files/-home-ubuntu-dgb-Xorg.txt

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

Title:
  Xorg crash - Current live CD

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My laptop won't boot with the current live builds. After the greeting screen 
xorg crashes and shows low graphic mode informations.
  I have a hybrid graphics configuration which worked on 12.04.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.323
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Sep 17 19:34:03 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04cc]
   Advanced Micro Devices [AMD] nee ATI Caicos

[Desktop-packages] [Bug 1052151] Re: Xorg crash

2012-09-17 Thread Jonas Schwabe 
-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1052151

Title:
  Xorg crash - Current live CD

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My laptop won't boot with the current live builds. After the greeting screen 
xorg crashes and shows low graphic mode informations.
  I have a hybrid graphics configuration which worked on 12.04.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.323
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Sep 17 19:34:03 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04cc]
   Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
     Subsystem: Dell Vostro 3350 [1028:04cc]
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120917)
  MachineType: Dell Inc. Vostro 3350
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0M516T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/30/2011:svnDellInc.:pnVostro3350:pvrNotSpecified:rvnDellInc.:rn0M516T:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3350
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.8.0-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.7-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu1

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

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

[Desktop-packages] [Bug 1052151] Re: Xorg crash

2012-09-17 Thread Jonas Schwabe 
** Attachment added: "full backtrace"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052151/+attachment/3321062/+files/-home-ubuntu-gdb-Xorg.txt

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

Title:
  Xorg crash - Current live CD

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My laptop won't boot with the current live builds. After the greeting screen 
xorg crashes and shows low graphic mode informations.
  I have a hybrid graphics configuration which worked on 12.04.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.323
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Sep 17 19:34:03 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04cc]
   Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
     Subsystem: Dell Vostro 3350 [1028:04cc]
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120917)
  MachineType: Dell Inc. Vostro 3350
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0M516T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/30/2011:svnDellInc.:pnVostro3350:pvrNotSpecified:rvnDellInc.:rn0M516T:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3350
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.8.0-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.7-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu1

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

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

[Desktop-packages] [Bug 1052151] Re: Xorg crash

2012-09-17 Thread Jonas Schwabe 
** Attachment added: "full backtrace"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1052151/+attachment/3321061/+files/-home-ubuntu-dgb-Xorg.txt

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

Title:
  Xorg crash - Current live CD

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My laptop won't boot with the current live builds. After the greeting screen 
xorg crashes and shows low graphic mode informations.
  I have a hybrid graphics configuration which worked on 12.04.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.323
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Sep 17 19:34:03 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04cc]
   Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
     Subsystem: Dell Vostro 3350 [1028:04cc]
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120917)
  MachineType: Dell Inc. Vostro 3350
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0M516T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/30/2011:svnDellInc.:pnVostro3350:pvrNotSpecified:rvnDellInc.:rn0M516T:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 3350
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.8.0-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.39-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.7-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu1

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

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

[Desktop-packages] [Bug 1052151] [NEW] Xorg crash - Current live CD

2012-09-17 Thread Jonas Schwabe 
Public bug reported:

My laptop won't boot with the current live builds. After the greeting screen 
xorg crashes and shows low graphic mode informations.
I have a hybrid graphics configuration which worked on 12.04.


ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.7+1ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CasperVersion: 1.323
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Mon Sep 17 19:34:03 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:04cc]
 Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
   Subsystem: Dell Vostro 3350 [1028:04cc]
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120917)
MachineType: Dell Inc. Vostro 3350
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0M516T
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd09/30/2011:svnDellInc.:pnVostro3350:pvrNotSpecified:rvnDellInc.:rn0M516T:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 3350
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 
9.0~git20120903.e1673d20.is.git20120821.c1114c61-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.7-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu1

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


** Tags: amd64 apport-bug crash quantal ubuntu

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

Title:
  Xorg crash - Current live CD

Status in “xorg” package in Ubuntu:
  New

Bug description:
  My laptop won't boot with the current live builds. After the greeting screen 
xorg crashes and shows low graphic mode informations.
  I have a hybrid graphics configuration which worked on 12.04.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: xorg 1:7.7+1ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.323
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Sep 17 19:34:03 2012
  DistUpgraded: Fresh install
  DistroCodename: quantal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:04cc]
   Advanced Micro Devices [AMD] nee ATI Caicos [Radeon HD 6400M/7400M Series] 
[1002:6760] (prog-if 00 [VGA controller])
     Subsystem: Dell Vostro 3350 [1028:04cc]
  LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120917)
  MachineType: Dell Inc. Vostro 3350
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0M516T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.

[Desktop-packages] [Bug 1034924] [NEW] gnome-screensaver crashes after long idle

2012-08-09 Thread Jonas Schwabe 
Public bug reported:

After locking the computer for a long time ~1h the screensaver becomes
unresponsive (unable to log back in)

in VT I could do:
killall gnome-screensaver to return to the desktop.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-screensaver 3.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
Uname: Linux 3.2.0-27-generic x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Thu Aug  9 16:07:57 2012
EcryptfsInUse: Yes
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GsettingsGnomeSession:
 org.gnome.desktop.session idle-delay uint32 600
 org.gnome.desktop.session session-name 'ubuntu'
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
UpgradeStatus: No upgrade log present (probably fresh install)
WindowManager: No value set for 
`/desktop/gnome/session/required_components/windowmanager'

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


** Tags: amd64 apport-bug precise running-unity

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

Title:
  gnome-screensaver crashes after long idle

Status in “gnome-screensaver” package in Ubuntu:
  New

Bug description:
  After locking the computer for a long time ~1h the screensaver becomes
  unresponsive (unable to log back in)

  in VT I could do:
  killall gnome-screensaver to return to the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-screensaver 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Thu Aug  9 16:07:57 2012
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)
  WindowManager: No value set for 
`/desktop/gnome/session/required_components/windowmanager'

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

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

[Desktop-packages] [Bug 1034924] Re: gnome-screensaver crashes after long idle

2012-08-09 Thread Jonas Schwabe 
-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1034924

Title:
  gnome-screensaver crashes after long idle

Status in “gnome-screensaver” package in Ubuntu:
  New

Bug description:
  After locking the computer for a long time ~1h the screensaver becomes
  unresponsive (unable to log back in)

  in VT I could do:
  killall gnome-screensaver to return to the desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-screensaver 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21
  Uname: Linux 3.2.0-27-generic x86_64
  ApportVersion: 2.0.1-0ubuntu12
  Architecture: amd64
  Date: Thu Aug  9 16:07:57 2012
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)
  WindowManager: No value set for 
`/desktop/gnome/session/required_components/windowmanager'

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

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

[Desktop-packages] [Bug 1011780] Re: trying to install psychonauts enters infinite crash loop on i386

2012-06-17 Thread Jonas Schwabe 
Definitely happens on 64bit systems, too.
I have the same issues.

** Summary changed:

- trying to install psychonauts enters infinite crash loop on i386
+ trying to install psychonauts enters infinite crash loop

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

Title:
  trying to install psychonauts enters infinite crash loop

Status in “software-center” package in Ubuntu:
  Confirmed

Bug description:
  
  WORKAROUND:
  Until this bug is fixed, you can install Psychonauts using a terminal as 
shown:
$ sudo apt-get install psychonauts

  ---
  Installing Psychonauts from the Ubuntu Software Center eventually (after 
downloading) caused the software center to repeatedly crash and pop up a new 
crash report dialog every few seconds (before previous ones were closed). Had 
to killall -9 software-center and apport-gtk.

  After this happened, simply launching the software center caused the
  crash loop to happen again. Launching and killing it a few times seems
  to have fixed it.

  Also, the size of the psychonauts package is reported as 134.9 MB in
  stead of 4.1 GB.

  $ lsb_release -rd
  Description:  Ubuntu 12.04 LTS
  Release:  12.04

  Ubuntu Software Center version 5.2.2.2

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

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

[Desktop-packages] [Bug 998389] Re: Brasero crashes on clicking the close window control while burning

2012-05-12 Thread Jonas Schwabe 
** Attachment added: "Crash report (could for some reasons not be processed)"
   
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/998389/+attachment/3142646/+files/_usr_bin_brasero.1000.crash

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

Title:
  Brasero crashes on clicking the close window control while burning

Status in “brasero” package in Ubuntu:
  New

Bug description:
  I am sorry I can't attach an apport bug report as apport simply does 
something wired while reporting this (simply disappears but does not crash). I 
will look into this, too.
  I will therefore attach valgrind output and the unformated crash file. But I 
think this will likely be reproducible for everyone as it does not only happen 
while burning but also while creating iso files.
  Steps to do:
  Create a new data disc with brasero, if you want to try this with iso files 
put some big files onto the disc as you need a few seconds to reproduce the bug.
  Start the burning/writing process and simply click on the close button (X) in 
the window control.
  Program crashes and if you really burn something the disc braseero was 
burning won't stop spinning. I had to use "cdrecord -abort" to eject it as 
eject just shows: 
  eject: Kann nicht auswerfen! Letzter Fehler: Unpassender IOCTL (I/O-Control) 
für das Gerät
  (eject: Eject failed! Last error: Wrong IOCTL for this device)

  What I was expecting:
  Either a confirmation to cancel the burn process or a simple minimization to 
the notification area.

  
  Valgrind output attached.
  Interesting data:
  ==8515== Process terminating with default action of signal 11 (SIGSEGV)
  ==8515==  Access not within mapped region at address 0x10
  ==8515==at 0x508A30E: brasero_task_clock_tick (burn-task.c:150)
  ==8515==by 0x79918DA: g_timeout_dispatch (gmain.c:3859)
  ==8515==by 0x7990C99: g_main_context_dispatch (gmain.c:2515)
  ==8515==by 0x799105F: g_main_context_iterate.isra.23 (gmain.c:3123)
  ==8515==by 0x7991459: g_main_loop_run (gmain.c:3317)
  ==8515==by 0x508A8D5: brasero_task_start_items (burn-task.c:442)
  ==8515==by 0x508AE52: brasero_task_start (burn-task.c:623)
  ==8515==by 0x507562C: brasero_burn_run_imager (brasero-burn.c:1343)
  ==8515==by 0x50763FE: brasero_burn_record_session (brasero-burn.c:2248)
  ==8515==by 0x5077BA9: brasero_burn_record (brasero-burn.c:2826)
  ==8515==by 0x5090A72: brasero_burn_dialog_run_real 
(brasero-burn-dialog.c:2227)
  ==8515==by 0x5092118: brasero_burn_dialog_run (brasero-burn-dialog.c:2508)

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

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

[Desktop-packages] [Bug 998389] Re: Brasero crashes on clicking the close window control while burning

2012-05-12 Thread Jonas Schwabe 
** Attachment added: "Valgrind output"
   
https://bugs.launchpad.net/bugs/998389/+attachment/3142645/+files/brasero.vgrind

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

Title:
  Brasero crashes on clicking the close window control while burning

Status in “brasero” package in Ubuntu:
  New

Bug description:
  I am sorry I can't attach an apport bug report as apport simply does 
something wired while reporting this (simply disappears but does not crash). I 
will look into this, too.
  I will therefore attach valgrind output and the unformated crash file. But I 
think this will likely be reproducible for everyone as it does not only happen 
while burning but also while creating iso files.
  Steps to do:
  Create a new data disc with brasero, if you want to try this with iso files 
put some big files onto the disc as you need a few seconds to reproduce the bug.
  Start the burning/writing process and simply click on the close button (X) in 
the window control.
  Program crashes and if you really burn something the disc braseero was 
burning won't stop spinning. I had to use "cdrecord -abort" to eject it as 
eject just shows: 
  eject: Kann nicht auswerfen! Letzter Fehler: Unpassender IOCTL (I/O-Control) 
für das Gerät
  (eject: Eject failed! Last error: Wrong IOCTL for this device)

  What I was expecting:
  Either a confirmation to cancel the burn process or a simple minimization to 
the notification area.

  
  Valgrind output attached.
  Interesting data:
  ==8515== Process terminating with default action of signal 11 (SIGSEGV)
  ==8515==  Access not within mapped region at address 0x10
  ==8515==at 0x508A30E: brasero_task_clock_tick (burn-task.c:150)
  ==8515==by 0x79918DA: g_timeout_dispatch (gmain.c:3859)
  ==8515==by 0x7990C99: g_main_context_dispatch (gmain.c:2515)
  ==8515==by 0x799105F: g_main_context_iterate.isra.23 (gmain.c:3123)
  ==8515==by 0x7991459: g_main_loop_run (gmain.c:3317)
  ==8515==by 0x508A8D5: brasero_task_start_items (burn-task.c:442)
  ==8515==by 0x508AE52: brasero_task_start (burn-task.c:623)
  ==8515==by 0x507562C: brasero_burn_run_imager (brasero-burn.c:1343)
  ==8515==by 0x50763FE: brasero_burn_record_session (brasero-burn.c:2248)
  ==8515==by 0x5077BA9: brasero_burn_record (brasero-burn.c:2826)
  ==8515==by 0x5090A72: brasero_burn_dialog_run_real 
(brasero-burn-dialog.c:2227)
  ==8515==by 0x5092118: brasero_burn_dialog_run (brasero-burn-dialog.c:2508)

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

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

[Desktop-packages] [Bug 998389] [NEW] Brasero crashes on clicking the close window control while burning

2012-05-12 Thread Jonas Schwabe 
Public bug reported:

I am sorry I can't attach an apport bug report as apport simply does something 
wired while reporting this (simply disappears but does not crash). I will look 
into this, too.
I will therefore attach valgrind output and the unformated crash file. But I 
think this will likely be reproducible for everyone as it does not only happen 
while burning but also while creating iso files.
Steps to do:
Create a new data disc with brasero, if you want to try this with iso files put 
some big files onto the disc as you need a few seconds to reproduce the bug.
Start the burning/writing process and simply click on the close button (X) in 
the window control.
Program crashes and if you really burn something the disc braseero was burning 
won't stop spinning. I had to use "cdrecord -abort" to eject it as eject just 
shows: 
eject: Kann nicht auswerfen! Letzter Fehler: Unpassender IOCTL (I/O-Control) 
für das Gerät
(eject: Eject failed! Last error: Wrong IOCTL for this device)

What I was expecting:
Either a confirmation to cancel the burn process or a simple minimization to 
the notification area.


Valgrind output attached.
Interesting data:
==8515== Process terminating with default action of signal 11 (SIGSEGV)
==8515==  Access not within mapped region at address 0x10
==8515==at 0x508A30E: brasero_task_clock_tick (burn-task.c:150)
==8515==by 0x79918DA: g_timeout_dispatch (gmain.c:3859)
==8515==by 0x7990C99: g_main_context_dispatch (gmain.c:2515)
==8515==by 0x799105F: g_main_context_iterate.isra.23 (gmain.c:3123)
==8515==by 0x7991459: g_main_loop_run (gmain.c:3317)
==8515==by 0x508A8D5: brasero_task_start_items (burn-task.c:442)
==8515==by 0x508AE52: brasero_task_start (burn-task.c:623)
==8515==by 0x507562C: brasero_burn_run_imager (brasero-burn.c:1343)
==8515==by 0x50763FE: brasero_burn_record_session (brasero-burn.c:2248)
==8515==by 0x5077BA9: brasero_burn_record (brasero-burn.c:2826)
==8515==by 0x5090A72: brasero_burn_dialog_run_real 
(brasero-burn-dialog.c:2227)
==8515==by 0x5092118: brasero_burn_dialog_run (brasero-burn-dialog.c:2508)

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

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

Title:
  Brasero crashes on clicking the close window control while burning

Status in “brasero” package in Ubuntu:
  New

Bug description:
  I am sorry I can't attach an apport bug report as apport simply does 
something wired while reporting this (simply disappears but does not crash). I 
will look into this, too.
  I will therefore attach valgrind output and the unformated crash file. But I 
think this will likely be reproducible for everyone as it does not only happen 
while burning but also while creating iso files.
  Steps to do:
  Create a new data disc with brasero, if you want to try this with iso files 
put some big files onto the disc as you need a few seconds to reproduce the bug.
  Start the burning/writing process and simply click on the close button (X) in 
the window control.
  Program crashes and if you really burn something the disc braseero was 
burning won't stop spinning. I had to use "cdrecord -abort" to eject it as 
eject just shows: 
  eject: Kann nicht auswerfen! Letzter Fehler: Unpassender IOCTL (I/O-Control) 
für das Gerät
  (eject: Eject failed! Last error: Wrong IOCTL for this device)

  What I was expecting:
  Either a confirmation to cancel the burn process or a simple minimization to 
the notification area.

  
  Valgrind output attached.
  Interesting data:
  ==8515== Process terminating with default action of signal 11 (SIGSEGV)
  ==8515==  Access not within mapped region at address 0x10
  ==8515==at 0x508A30E: brasero_task_clock_tick (burn-task.c:150)
  ==8515==by 0x79918DA: g_timeout_dispatch (gmain.c:3859)
  ==8515==by 0x7990C99: g_main_context_dispatch (gmain.c:2515)
  ==8515==by 0x799105F: g_main_context_iterate.isra.23 (gmain.c:3123)
  ==8515==by 0x7991459: g_main_loop_run (gmain.c:3317)
  ==8515==by 0x508A8D5: brasero_task_start_items (burn-task.c:442)
  ==8515==by 0x508AE52: brasero_task_start (burn-task.c:623)
  ==8515==by 0x507562C: brasero_burn_run_imager (brasero-burn.c:1343)
  ==8515==by 0x50763FE: brasero_burn_record_session (brasero-burn.c:2248)
  ==8515==by 0x5077BA9: brasero_burn_record (brasero-burn.c:2826)
  ==8515==by 0x5090A72: brasero_burn_dialog_run_real 
(brasero-burn-dialog.c:2227)
  ==8515==by 0x5092118: brasero_burn_dialog_run (brasero-burn-dialog.c:2508)

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

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

[Desktop-packages] [Bug 855940] Re: seahorse crashed with SIGSEGV in g_simple_async_result_complete()

2012-03-29 Thread Jonas Schwabe 
I can reproduce this by starting the keyserver sync while having network
connection issues (e.g. no working DNS or general connection issues).
When an error message appears telling there are network problems dismiss
it and cancel the sync process.

Try selecting multiple keys to sync as dismissing the error messages for
one key will also close the sync window normally.

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

Title:
  seahorse crashed with SIGSEGV in g_simple_async_result_complete()

Status in “seahorse” package in Ubuntu:
  Incomplete

Bug description:
  I was attempting to import keys from keyserver.ubuntu.com

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: seahorse 3.1.92-0ubuntu1 [modified: usr/bin/seahorse 
usr/lib/seahorse/seahorse-ssh-askpass]
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Wed Sep 21 14:36:53 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/seahorse
  ProcCmdline: seahorse
  SegvAnalysis:
   Segfault happened at: 0x43bcb9:  mov(%rbx),%rdi
   PC (0x0043bcb9) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: seahorse
  StacktraceTop:
   ?? ()
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: seahorse crashed with SIGSEGV in g_simple_async_result_complete()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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