Bug #1565563 “xdiagnose” : Bugs : xorg package : Ubuntu

Revision history for this message

Mardersteig Andreas H. (andreastec11) wrote on 2016-04-03:

#1

BootLog.txt Edit (4.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (76.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.6 KiB, text/plain; charset="utf-8")
DkmsStatus.txt Edit (509 bytes, text/plain; charset="utf-8")
DpkgLog.txt Edit (78.6 KiB, text/plain; charset="utf-8")
GconfCompiz.txt Edit (46.5 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (25.1 KiB, text/plain; charset="utf-8")
LightdmDisplayLog.txt Edit (1.0 KiB, text/plain; charset="utf-8")
LightdmGreeterLog.txt Edit (13.1 KiB, text/plain; charset="utf-8")
LightdmGreeterLogOld.txt Edit (11.5 KiB, text/plain; charset="utf-8")
LightdmLog.txt Edit (5.1 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (27.9 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (675 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.9 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (283 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.0 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.8 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (147.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (302.0 KiB, text/plain; charset="utf-8")
UnitySupportTest.txt Edit (595 bytes, text/plain; charset="utf-8")
XorgLog.txt Edit (47.0 KiB, text/plain; charset="utf-8")
XorgLogOld.txt Edit (48.9 KiB, text/plain; charset="utf-8")
Xrandr.txt Edit (3.4 KiB, text/plain; charset="utf-8")
xdpyinfo.txt Edit (116.5 KiB, text/plain; charset="utf-8")
xserver.devices.txt Edit (511 bytes, text/plain; charset="utf-8")
xserver.outputs.txt Edit (752 bytes, text/plain; charset="utf-8")

Revision history for this message

penalvch (penalvch) wrote on 2016-06-11:

#2

Mardersteig Andreas H., thank you for taking the time to report this and helping to make Ubuntu better. Unfortunately, this report didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the problem,
2. The behavior you expected, and
3. The behavior you actually encountered (in as much detail as possible).

Thank you for your understanding.

tags:	added: bios-outdated-1.17
Changed in xorg (Ubuntu):
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

Mardersteig Andreas H. (andreastec11) wrote on 2016-06-11:

#3

Thank you so much for your reply of today! In between I'm running on 16.04 and it's a miracle, that I still can do my work on this installation (never change a running horse). I think a complete new install of ubuntu would cure most glitches I experience from time to time. Now next is this "outdated" bios, I have to see, how to get that updated without a glimpse of Windoze left on this machine. Thanks again, I've downloaded the links you mentioned, so next time, I'll dive into them before reporting a strange behavior, promised! Walk in sunshine!

Revision history for this message

penalvch (penalvch) wrote on 2016-06-11:

#4

Mardersteig Andreas H., to clarify, do you still have the issue with 16.04?

If not, then this report may be closed as Status Invalid.

Revision history for this message

Mardersteig Andreas H. (andreastec11) wrote on 2016-06-12:

#5

Download full text (3.3 KiB)

Yes, I still have it (again): The unity-desktop-version went 'unusable' again, first vanishing completely of the 'launcher', at one of the next startups, even the top bar, where you can turn off the machine or suspend or restart or log out, was gone and when unity completes its start procedure, it ends up full screen, no menues, no chance to call up any 'apps' = programs or the terminal, so I switched to the 'xfce' version, where I can use - as it seems - every app I really need for work as: Krusader, System Monitor, Libre Office, OpenOffice Ver 4.1.1 to handle my oooold .sxw-files. Perhaps the latter, I should explain closer:

Under ubuntu 14.04 in summer 2014 came up a new version of LibreOffice, where the Libre-people had ended their support for old OpenOffice files, like the .sxw-type. Then I deleted everything of that current LibreOffice version by Synaptic Manager and 'by hand & foot' and installed OpenOffice 4.1.1. All went ok then. But upgrading my ubuntu to version 14.10 in fall 2014, - oh miracle! - a LibreOffice version came back to my machine next to the willingly installed OpenOffice ver 4.1.1, after that I only used the OpenOffice suite 4.1.1 and left the re-gained version of LibreOffice untouched. After upgrading to ubuntu 15.04 in spring 2015, I used my OpenOffice Writer 4.1.1 to make .odt-files of all my old .sxw-files on my machine, quite a bunch of files, mostly from the 1990 decade. I need my old stuff, since I am administrating a movie estate & archive, which started in the late 1890 til 1960, so my old files have all a still valuable content. Mostly no garbage.

When I had problems with unity under 15.10, Jack Wallen praised somewhere the better speed of Gnome desktop, but I did not like it. For me, I like Unity best, because I have the full current date and a precise full time, so I can see with one view, how much of a minute is already over (to catch a bus or tram). Perfect for me.

Upgrading to Ubuntu 16.04 this spring kinda 'cured' my Unity problems: everything worked again fine, but after a few weeks or days, the first thing, I noticed was, I had the menu bar in Claws Mail, but the drop-down menues would not open, so I fumbled around in system settings and in unity-tweak-tool. No success. The rest please read again at the very top of this message.

I continue with the list of apps, I use for my work: at and within startup: Shutter, Psensor, keyboard set to German only (I use the English version of Ubuntu 16.04), CopyQ, ClassicMenu Indicator, Alarm Clock, System Monitor, Krusader, Wine app: Time & Chaos = Calendar; these are all from my Unity-Startup-file (have not found any under XFCE yet).

For work, I use the current LibreOffice now, OpenOffice for my old .sxw-files, I save my work as MS-Word-doc-files and as MS-Excel-xls-files (MSO 2003), Ristretto Viewer, XnView for sorting, Wine-App: Adobe Photoshop CS, Gimp, Inkscape, Simple Scan, Evince, Master PDF Editor, PDF-Shuffler, YAGF; Internet: Firefox, Opera, Vivaldi, Claws Mail, Transmission, youtube-dl; Audacious, MPlayer, Audacity, WinFF, Puddletag, gMTP;

I am sure, that the occuring failures are not a bug, but caused by me or harddisk failures. In April I had ho...

Yes, I still have it (again): The unity-desktop-version went 'unusable' again, first vanishing completely of the 'launcher', at one of the next startups, even the top bar, where you can turn off the machine or suspend or restart or log out, was gone and when unity completes its start procedure, it ends up full screen, no menues, no chance to call up any 'apps' = programs or the terminal, so I switched to the 'xfce' version, where I can use - as it seems - every app I really need for work as: Krusader, System Monitor, Libre Office, OpenOffice Ver 4.1.1 to handle my oooold .sxw-files. Perhaps the latter, I should explain closer:

Under ubuntu 14.04 in summer 2014 came up a new version of LibreOffice, where the Libre-people had ended their support for old OpenOffice files, like the .sxw-type. Then I deleted everything of that current LibreOffice version by Synaptic Manager and 'by hand & foot' and installed OpenOffice 4.1.1. All went ok then. But upgrading my ubuntu to version 14.10 in fall 2014, - oh miracle! - a LibreOffice version came back to my machine next to the willingly installed OpenOffice ver 4.1.1, after that I only used the OpenOffice suite 4.1.1 and left the re-gained version of LibreOffice untouched. After upgrading to ubuntu 15.04 in spring 2015, I used my OpenOffice Writer 4.1.1 to make .odt-files of all my old .sxw-files on my machine, quite a bunch of files, mostly from the 1990 decade. I need my old stuff, since I am administrating a movie estate & archive, which started in the late 1890 til 1960, so my old files have all a still valuable content. Mostly no garbage.

When I had problems with unity under 15.10, Jack Wallen praised somewhere the better speed of Gnome desktop, but I did not like it. For me, I like Unity best, because I have the full current date and a precise full time, so I can see with one view, how much of a minute is already over (to catch a bus or tram). Perfect for me.

Upgrading to Ubuntu 16.04 this spring kinda 'cured' my Unity problems: everything worked again fine, but after a few weeks or days, the first thing, I noticed was, I had the menu bar in Claws Mail, but the drop-down menues would not open, so I fumbled around in system settings and in unity-tweak-tool. No success. The rest please read again at the very top of this message.

I continue with the list of apps, I use for my work: at and within startup: Shutter, Psensor, keyboard set to German only (I use the English version of Ubuntu 16.04), CopyQ, ClassicMenu Indicator, Alarm Clock, System Monitor, Krusader, Wine app: Time & Chaos = Calendar; these are all from my Unity-Startup-file (have not found any under XFCE yet).

For work, I use the current LibreOffice now, OpenOffice for my old .sxw-files, I save my work as MS-Word-doc-files and as MS-Excel-xls-files (MSO 2003), Ristretto Viewer, XnView for sorting, Wine-App: Adobe Photoshop CS, Gimp, Inkscape, Simple Scan, Evince, Master PDF Editor, PDF-Shuffler, YAGF; Internet: Firefox, Opera, Vivaldi, Claws Mail, Transmission, youtube-dl; Audacious, MPlayer, Audacity, WinFF, Puddletag, gMTP;

I am sure, that the occuring failures are not a bug, but caused by me or harddisk failures. In April I had hoped, XDiagnose would list those causes for experts. I started with Ubuntu in 2012 or 2011.

Did that help in any way? Probably not. Thank you again. Then please kill this thread.

Revision history for this message

Mardersteig Andreas H. (andreastec11) wrote on 2016-06-12:

#6

Or advise me, what to do next, thanks!

Revision history for this message

penalvch (penalvch) wrote on 2016-06-12:

#7

Mardersteig Andreas H., to clarify, after the Unity desktop issue, is there a crash file in /var/crash?

Revision history for this message

Mardersteig Andreas H. (andreastec11) wrote on 2016-06-12:

#8

2016-06-12_Krusader_419.png Edit (81.2 KiB, image/png)

Christopher M. Penalver, yes, there are several, a screenshot is attached here.

Revision history for this message

penalvch (penalvch) wrote on 2016-06-12:

#9

Mardersteig Andreas H., 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/FILENAME.crash

Where FILENAME is the actual name of the file found in the folder.

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

Ubuntu
xorg package

xdiagnose

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntuxorg package

xdiagnose

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
xorg package