Bug #1534680 “error after booting 15.10, ubuntu seems to be work...” : Bugs : linux package : Ubuntu

Revision history for this message

Luc Henderieckx (luc-henderieckx) wrote on 2016-01-15:

#1

AlsaInfo.txt Edit (43.4 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (392 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (58.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (13.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (14.3 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (761 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (137 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.3 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (23.8 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (127.4 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (86.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Brad Figg (brad-figg) wrote on 2016-01-15: Status changed to Confirmed

#2

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

Alberto Salvia Novella (es20490446e) wrote on 2016-01-16: Re: error after booting 15.10

#3

Please:

1. Edit the bug description, so it tells in English how to reproduce the bug and what are the consequences of it.
2. Edit the title, so it is specific and meaningful.
3. Set this bug status back to "confirmed".

Thank you.

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

Revision history for this message

Luc Henderieckx (luc-henderieckx) wrote on 2016-01-16:

#4

System program error discovered. Unfortunately there was an internal error in Ubuntu 15.10.
After clicking away the error messages ubuntu seems to be working fine.
I had some problems before (with earlier versions of ubuntu) with the video driver of AMD (GPU build-in in the microprocessor).

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed
summary:	- error after booting 15.10 + error after booting 15.10, ubuntu seems to be working fine afterwards

Revision history for this message

Alberto Salvia Novella (es20490446e) wrote on 2016-01-18:

#5

Thanks.

description:	updated
Changed in linux (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2016-01-21:

#6

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily

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

Revision history for this message

penalvch (penalvch) wrote on 2016-01-25:

#7

Luc Henderieckx, 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 dist-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 a terminal, navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By default, this sends the crash to the Ubuntu Error Tracker infrastructure, which is different than Launchpad. For more on this, please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted to Launchpad, for example to ease triage and add others to your report, one would need to open the following file via a terminal:
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 file the crash report via:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

However, this report is being closed since the process outlined above will deal with this issue more efficiently.

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 linux (Ubuntu):
importance:	Medium → Undecided
status:	Incomplete → Invalid

Revision history for this message

Luc Henderieckx (luc-henderieckx) wrote on 2016-01-27: Re: [Bug 1534680] Re: error after booting 15.10, ubuntu seems to be working fine afterwards

#8

Download full text (5.3 KiB)

I did not succeed in running the proposed update in Ubunto 15.10. I
re-installed Ubuntu 15.10 several times and each time it developed the same
error when I installed the AMD video driver. I got tired of it and I now
installed Mint 17.3, which seems to be based on Ubuntu, and that works
flawlessly after installing the very same AMD video driver. This may give
you a clue about in which direction you have to look to find this bug ....
It most certainly has something to do with an incompatibility between
Ubuntu 15.10 and the AMD Linux video driver for sure ...
Kind regards, Luc Henderieckx

Kind regards,
Vriendelijke groeten,

Luc Henderieckx
http://www.henderieckx.com

2016-01-25 10:34 GMT+01:00 Christopher M. Penalver <
<email address hidden>>:

> Luc Henderieckx, 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
> dist-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 a terminal, navigate to your /var/crash directory and file your report
> with:
> sudo ubuntu-bug /var/crash/_my_crash_report.crash
>
> where _my_crash_report.crash is the crash you would like to report. By
> default, this sends the crash to the Ubuntu Error Tracker
> infrastructure, which is different than Launchpad. For more on this,
> please see https://wiki.ubuntu.com/ErrorTracker .
>
> However, if after doing this you would still like to have a crash report
> posted to Launchpad, for example to ease triage and add others to your
> report, one would need to open the following file via a terminal:
> 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 file the crash report via:
> sudo ubuntu-bug /var/crash/_my_crash_report.crash
>
> However, this report is being closed since the process outlined above
> will deal with this issue more efficiently.
>
> 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: linux (Ubuntu)
> Importance: Medium => Undecided
>
> ** Changed in: linux (Ubuntu)
> Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1534680
>
> Title:
> error after booting 15.10, ubuntu seems to be working fine afterwards
>
> Status in linux package in Ubuntu:
> Invalid
>
> Bug description:
> System program error discovered. Unfortunately there was an internal
> error in Ubuntu 15.10.
>
> After clicking away the error messages ubuntu seems to be working fine.
> I had some problems before (with earlier versi...

I did not succeed in running the proposed update in Ubunto 15.10. I
re-installed Ubuntu 15.10 several times and each time it developed the same
error when I installed the AMD video driver. I got tired of it and I now
installed Mint 17.3, which seems to be based on Ubuntu, and that works
flawlessly after installing the very same AMD video driver. This may give
you a clue about in which direction you have to look to find this bug ....
It most certainly has something to do with an incompatibility between
Ubuntu 15.10 and the AMD Linux video driver for sure ...
Kind regards, Luc Henderieckx

Kind regards,
Vriendelijke groeten,

Luc Henderieckx
http://www.henderieckx.com

2016-01-25 10:34 GMT+01:00 Christopher M. Penalver <
christopher.m.penalver@gmail.com>:

> Luc Henderieckx, 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
> dist-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 a terminal, navigate to your /var/crash directory and file your report
> with:
> sudo ubuntu-bug /var/crash/_my_crash_report.crash
>
> where _my_crash_report.crash is the crash you would like to report. By
> default, this sends the crash to the Ubuntu Error Tracker
> infrastructure, which is different than Launchpad. For more on this,
> please see https://wiki.ubuntu.com/ErrorTracker .
>
> However, if after doing this you would still like to have a crash report
> posted to Launchpad, for example to ease triage and add others to your
> report, one would need to open the following file via a terminal:
> 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 file the crash report via:
> sudo ubuntu-bug /var/crash/_my_crash_report.crash
>
> However, this report is being closed since the process outlined above
> will deal with this issue more efficiently.
>
> 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: linux (Ubuntu)
>    Importance: Medium => Undecided
>
> ** Changed in: linux (Ubuntu)
>        Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1534680
>
> Title:
>   error after booting 15.10, ubuntu seems to be working fine afterwards
>
> Status in linux package in Ubuntu:
>   Invalid
>
> Bug description:
>   System program error discovered. Unfortunately there was an internal
>   error in Ubuntu 15.10.
>
>   After clicking away the error messages ubuntu seems to be working fine.
>   I had some problems before (with earlier versions of Ubuntu) with the
> video driver of AMD (GPU build-in in the microprocessor).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.10
>   Package: linux-image-4.2.0-24-generic 4.2.0-24.29
>   ProcVersionSignature: Ubuntu 4.2.0-24.29-generic 4.2.8-ckt1
>   Uname: Linux 4.2.0-24-generic x86_64
>   NonfreeKernelModules: fglrx
>   ApportVersion: 2.19.1-0ubuntu5
>   Architecture: amd64
>   AudioDevicesInUse:
>    USER        PID ACCESS COMMAND
>    /dev/snd/controlC1:  luchen     1189 F.... pulseaudio
>    /dev/snd/controlC0:  luchen     1189 F.... pulseaudio
>   CurrentDesktop: Unity
>   Date: Fri Jan 15 18:22:50 2016
>   HibernationDevice: RESUME=UUID=eaaf960d-0d95-47d3-8de4-9dd6a51bb8a1
>   InstallationDate: Installed on 2015-11-27 (49 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   IwConfig:
>    enp2s0    no wireless extensions.
>
>    lo        no wireless extensions.
>   MachineType: Gigabyte Technology Co., Ltd. GA-A75-D3H
>   ProcFB: 0 VESA VGA
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-24-generic
> root=UUID=900d57dd-4196-4110-91ff-505b397b804a ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>    linux-restricted-modules-4.2.0-24-generic N/A
>    linux-backports-modules-4.2.0-24-generic  N/A
>    linux-firmware                            1.149.3
>   RfKill:
>
>   SourcePackage: linux
>   UdevLog: Error: [Errno 2] Bestand of map bestaat niet: '/var/log/udev'
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 11/17/2011
>   dmi.bios.vendor: Award Software International, Inc.
>   dmi.bios.version: F5a
>   dmi.board.name: GA-A75-D3H
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.board.version: x.x
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
>   dmi.modalias:
> dmi:bvnAwardSoftwareInternational,Inc.:bvrF5a:bd11/17/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75-D3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
>   dmi.product.name: GA-A75-D3H
>   dmi.sys.vendor: Gigabyte Technology Co., Ltd.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1534680/+subscriptions
>

Ubuntu
linux package

error after booting 15.10, ubuntu seems to be working fine afterwards

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntulinux package

error after booting 15.10, ubuntu seems to be working fine afterwards

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package