large image crashes desktop
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Ubuntu GNOME |
Undecided
|
Unassigned | ||
Bug Description
this image,
https:/
will crash the desktop back to the login screen.
happens when viewed in firefox, and when downloaded and viewed with Image Viewer.
14.04 LTS
| clayton baber (baberlicious) wrote : | #2 |
as i remember, Apport never detected a problem and never asked to report.
there are some files in /var/crash... but i'm unsure if they relate to this crash, as i've had a few since then (with different hardware).
i did however manage to trace the crash back to the open source video driver... the crash did not occur if i was using the proprietary driver.
as of right now, i'm using a different video card that doesn't hardly work with the open source driver... but i still have the old card. i'd be willing to put the old one back in and revert to the open source driver and reproduce the crash, if you could tell me exactly how i could get the relevent data pertaining to the crash (and not any old crash stuff :)
for reference these are the file names that are currently in /var/crash:
_usr_bin_
_usr_bin_
_usr_bin_
_usr_bin_
_usr_bin_
_usr_bin_
| Elias Psallidas (eliasps) wrote : | #3 |
Can you empty the content of /var/crash and try to reproduce this issue in order to check if there is a new entry in it afterwards? If there will be, then it would be helpful to identify the source of it and attach the information to the bug report.
| clayton baber (baberlicious) wrote : | #4 |
sure thing... give me a little bit so i can do the surgery :)
| clayton baber (baberlicious) wrote : | #5 |
ok, i can reproduce the issue without a doubt. i click on the link in the description, and it crashes back to login screen.
however, apport never detects anything wrong, and /var/crash is empty :(
any ideas?
| Elias Psallidas (eliasps) wrote : | #6 |
Too bad, unless someone jumps in with a better idea to figure out the cause, maybe you should check the /var/log/syslog file and the dmesg command for any pointers. You can paste their output here: http://
| clayton baber (baberlicious) wrote : | #7 |
looked through them.. nothing look just super obviously wrong to me.. but i don't know much. meh, here they are
/var/log/syslog http://
dmesg http://
| Elias Psallidas (eliasps) wrote : | #8 |
Can you try creating a new user for your Ubuntu? Either using the Accounts in System Settings or via terminal:
sudo adduser username
sudo adduser username sudo
And add the required information (leave the defaults if you want). Then log in with the new user and check if it can be reproduced there. This will tell us if there is an issue with your Xorg configuration on your current user.
| clayton baber (baberlicious) wrote : | #9 |
tested two new users, both reproduce the issue
| clayton baber (baberlicious) wrote : | #10 |
interestingly enough, the first user produced something in /var/crash : http://
however, the second user did not
| Elias Psallidas (eliasps) wrote : | #11 |
If this was generated by this crash, then you can collect all the information needed to file a new bug using:
sudo ubuntu-bug /var/crash/
And Apport will collect all the required info about the crash and attach them to a new bug report. The report will be private until it gets ckecked out by a bug supervisor.
| Launchpad Janitor (janitor) wrote : | #12 |
[Expired for Ubuntu GNOME because there has been no activity for 60 days.]
| Changed in ubuntu-gnome: | |
| status: | Incomplete → Expired |


Hello,
Thank you for taking the time to submit this report.
When you login into the environment again, isn't Apport prompt you to report this issue using it?
You can check in the directory /var/crash if there is any file related to this issue?