Bug #1426596 “I get an “error report” popup on log-in” : Bugs : xorg package : Ubuntu

Revision history for this message

Tony Flury (anthony-flury) wrote on 2015-02-28:

#1

.proc.driver.nvidia.params.txt Edit (412 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (60.5 KiB, text/plain; charset="utf-8")
BootLog.gz Edit (588 bytes, application/x-gzip)
CurrentDmesg.txt Edit (5.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.4 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (619 bytes, text/plain; charset="utf-8")
DpkgLog.txt Edit (121.4 KiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (28.1 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (3.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (13.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (518 bytes, text/plain; charset="utf-8")
MonitorsUser.xml.txt Edit (1.7 KiB, text/plain; charset="utf-8")
NvidiaBugReportLog.txt Edit (760 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (4.0 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (3.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (147.7 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (319.3 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (587 bytes, text/plain; charset="utf-8")
XorgConf.txt Edit (750 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (36.8 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (49.6 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (7.6 KiB, text/plain; charset="utf-8")
nvidia-bug-report.log.gz Edit (73.2 KiB, application/x-gzip)
nvidia-settings.txt Edit (26.0 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (33.4 KiB, text/plain; charset="utf-8")

Tony Flury (anthony-flury) on 2015-02-28

description:

updated

Revision history for this message

penalvch (penalvch) wrote on 2015-03-01:

#2

Tony Flury, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please feel free to subscribe me to this new report.

Also, please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in xorg (Ubuntu):
status:	New → Invalid

Revision history for this message

Tony Flury (anthony-flury) wrote on 2015-03-02: Re: [Bug 1426596] Re: I get an "error report" popup on log-in

#3

Download full text (6.8 KiB)

Christopher,
Thanks for your reply, sadly I am unable to do this for two reasons :

1) The bug is intermittent - I have no knowledge of how to reproduce it - it doesn't occurr on every login (I think I mentioned this on the report that I filed).

2) When I try to use the existing crash report to report the bug - it reports "IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpnUQsVV is truncated: expected core file size >= 60002304, found: 22085632.',)". It does that even when the crash is fresh (i.e. just happened) or when this crash report is 6 days old (as it is now).

I thought that the bug report I submitted clearly pointed to an invalid call in the code - I just wish I had the time to investigate (either clearly document the reproduction or identify the actual bug.

So it seems that this bug will go unfixed :-(

________________________________
From: Christopher M. Penalver <email address hidden>
To: <email address hidden>
Sent: Sunday, 1 March 2015, 18:49
Subject: [Bug 1426596] Re: I get an "error report" popup on log-in

Tony Flury, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently.

Please feel free to subscribe me to this new report.

Also, please do not attach your crash report manually to this report and
reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

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

Christopher,
Thanks for your reply, sadly I am unable to do this for two reasons :

1) The bug is intermittent - I have no knowledge of how to reproduce it - it doesn't occurr on every login (I think I mentioned this on the report that I filed).

2) When I try to use the existing crash report to report the bug - it reports "IOError(u'Invalid core dump: BFD: Warning: /tmp/tmpnUQsVV is truncated: expected core file size >= 60002304, found: 22085632.',)". It does that even when the crash is fresh (i.e. just happened) or when this crash report is 6 days old (as it is now).

I thought that the bug report I submitted clearly pointed to an invalid call in the code - I just wish I had the time to investigate (either clearly document the reproduction or identify the actual bug.

So it seems that this bug will go unfixed :-(

________________________________
 From: Christopher M. Penalver <christopher.m.penalver@gmail.com>
To: anthony.flury@btinternet.com 
Sent: Sunday, 1 March 2015, 18:49
Subject: [Bug 1426596] Re: I get an "error report" popup on log-in

Tony Flury, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable
apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will
automatically open a new bug report which can then dealt with more
efficiently.

Please feel free to subscribe me to this new report.

Also, please do not attach your crash report manually to this report and
reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

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

Title:
  I get an "error report" popup on log-in

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  This doesn't occurr on every login, but it does occurr on the
  majority.

From the crash report it seems to be Xorg, rather than Nautilus
  desktop.

There are no obvious symptoms of this crash - i.e. everything seems to
  carry on regardless.

I am reporting this against xorg, due to the existance of
  _usr_bin_Xorg.0.crash in /var/crash - I assume that all the
  information you need has been extracted below ?

ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-46.75~precise1-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  331.113  Mon Dec  1 20:14:01 PST 2014
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  CompizPlugins: [core,composite,opengl,decor,resize,vpswitch,snap,imgpng,grid,regex,place,gnomecompat,compiztoolbox,unitymtgrabhandles,move,mousepoll,animation,wall,session,workarounds,expo,fade,scale,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Feb 28 00:05:49 2015
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:6502]
     Subsystem: CLEVO/KAPOK Computer Device [1558:6502]
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204)
  JockeyStatus: xorg:nvidia_331_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Enabled, In use)
  MachineType: Notebook W65_67SF
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic root=UUID=9b573783-9dac-471b-ba7f-755099846d9e ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

Revision history for this message

penalvch (penalvch) wrote on 2015-03-02:

#4

Tony Flury, thanks for the follow up information.

As upstream has a support focus on x64, does this still occur if you switch to this?

Changed in xorg (Ubuntu):
importance:	Undecided → Low
status:	Invalid → Incomplete

Revision history for this message

Tony Flury (anthony-flury) wrote on 2015-03-02:

#5

Download full text (4.6 KiB)

I am not sure - I don't have x64 installed - and I am reluctant to do - I don't have a spare partition to use.

It would take a lot of effort to completely recreate my settings on an x64 - unless I have misunderstood what you asked.

--
Tony

________________________________
From: Christopher M. Penalver <email address hidden>
To: <email address hidden>
Sent: Monday, 2 March 2015, 11:38
Subject: [Bug 1426596] Re: I get an "error report" popup on log-in

Tony Flury, thanks for the follow up information.

As upstream has a support focus on x64, does this still occur if you
switch to this?

** Changed in: xorg (Ubuntu)
Importance: Undecided => Low

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

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

Title:
I get an "error report" popup on log-in

Status in xorg package in Ubuntu:
Incomplete

Bug description:
This doesn't occurr on every login, but it does occurr on the
majority.

From the crash report it seems to be Xorg, rather than Nautilus
desktop.

There are no obvious symptoms of this crash - i.e. everything seems to
carry on regardless.

  I am reporting this against xorg, due to the existance of
  _usr_bin_Xorg.0.crash in /var/crash - I assume that all the
  information you need has been extracted below ?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-46.75~precise1-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module 331.113 Mon Dec 1 20:14:01 PST 2014
   GCC version: gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  CompizPlugins: [core,composite,opengl,decor,resize,vpswitch,snap,imgpng,grid,regex,place,gnomecompat,compiztoolbox,unitymtgrabhandles,move,mousepoll,animation,wall,session,workarounds,expo,fade,scale,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Feb 28 00:05:49 2015
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:6502]
     Subsystem: CLEVO/KAPOK Computer Device [1558:6502]
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204)
  JockeyStatus: xorg:nvidia_331_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Enabled, In use)
  MachineType: Notebook W65_67SF
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic root=UUID=9b573783-9dac-471b-ba7f-7550...

I am not sure - I don't have x64 installed - and I am reluctant to do - I don't have a spare partition to use.
 
It would take a lot of effort to completely recreate my settings on an x64 - unless I have misunderstood what you asked.
 
-- 
Tony

________________________________
 From: Christopher M. Penalver <christopher.m.penalver@gmail.com>
To: anthony.flury@btinternet.com 
Sent: Monday, 2 March 2015, 11:38
Subject: [Bug 1426596] Re: I get an "error report" popup on log-in

Tony Flury, thanks for the follow up information.

As upstream has a support focus on x64, does this still occur if you
switch to this?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  I get an "error report" popup on log-in

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This doesn't occurr on every login, but it does occurr on the
  majority.

From the crash report it seems to be Xorg, rather than Nautilus
  desktop.

There are no obvious symptoms of this crash - i.e. everything seems to
  carry on regardless.

I am reporting this against xorg, due to the existance of
  _usr_bin_Xorg.0.crash in /var/crash - I assume that all the
  information you need has been extracted below ?

ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-46.75~precise1-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  331.113  Mon Dec  1 20:14:01 PST 2014
   GCC version:  gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
  .tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  CompizPlugins: [core,composite,opengl,decor,resize,vpswitch,snap,imgpng,grid,regex,place,gnomecompat,compiztoolbox,unitymtgrabhandles,move,mousepoll,animation,wall,session,workarounds,expo,fade,scale,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Sat Feb 28 00:05:49 2015
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:6502]
     Subsystem: CLEVO/KAPOK Computer Device [1558:6502]
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140204)
  JockeyStatus: xorg:nvidia_331_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Enabled, In use)
  MachineType: Notebook W65_67SF
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic root=UUID=9b573783-9dac-471b-ba7f-755099846d9e ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03:bd04/01/2014:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.7.12-0ubuntu4
  version.libdrm2: libdrm2 2.4.52-1~precise2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-05-02:

#6

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

Changed in xorg (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Andreas Fritiofson (andreas-fritiofson) wrote on 2017-04-03:

#7

This still happens from time to time on a fresh install of 16.10 on a Dell Precision 5520. So x86_64. Apport says it's unreportable because the core file is truncated.

Changed in xorg (Ubuntu):
status:	Expired → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2017-05-07:

#8

Andreas Fritiofson, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

Changed in xorg (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Andreas Fritiofson (andreas-fritiofson) wrote on 2017-05-29:

#9

Reported as Bug 1694331.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-07-29:

#10

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

Changed in xorg (Ubuntu):
status:	Incomplete → Expired

Ubuntu
xorg package

I get an "error report" popup on log-in

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntuxorg package

I get an "error report" popup on log-in

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
xorg package