** Also affects: kwin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425541
Title:
kwin crashes on login and on resume from hibernate and
to
switch to a terminal and use killall kwin and then DISPLAY=:0 kwin to restart
it but this has not yet worked.
The crash can be reproduced sometimes.
-- Backtrace:
Application: KWin (kwin), signal: Aborted
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[KCrash
Thanks for the advice, Chris! The --newmode/--addmode arguments will be
very useful. I do want to use that mode quite badly, as the display
represents all other resolutions I tried (of which there were many on
the older kernels) very badly.
I presently cannot remember on what basis I concluded
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658597/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658605/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658592/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658596/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
Title:
Boot
apport information
** Tags added: apport-collected
** Description changed:
Graphics worked in Precise. After upgrading, lightdm does not load, but
the safe graphics mode dialog is displayed, instead This dialog fails
to accomplish anything other than allowing me to exit to a terminal and
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658598/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658601/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
Title:
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658604/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
Title:
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658591/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
Title:
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658606/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658599/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658594/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658593/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
Title:
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658600/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658603/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658595/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
Title:
Boot
apport information
** Attachment added: xserver.outputs.txt
https://bugs.launchpad.net/bugs/1173491/+attachment/3658607/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You are correct Chris, the original logs were indeed from a working
session. I did not consider that they might only cover one session - my
apologies, I hope I have not wasted anyone's time!
As you can see by the spam :S it looks like I successfully ran apport-
collect from the VT... I had to
An interesting thing I noticed is that, upon login into the VT, ubuntu
tells me that there is a new release available (13.04) and that I
sould use do-release-upgrade to upgrade to it. Perhaps something went
wrong in the upgrade process.
Actually trying to run do-release-upgrade tells me that
Ahhh, given what you just mentioned, I remembered that I had added a
line to /etc/lightdm/lightdm.conf, in order to force light-dm to use the
native resoltution of the display:
display-setup-script=xrandr --output HDMI2 --primary --mode 1440x900
This was returning a failure code, causing
Thanks Timo,
Unfortunately, the kernel you linked does not appear to work any better.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
Title:
Boot to Safe Graphics after upgrade to Raring
To
Public bug reported:
Graphics worked in Precise. After upgrading, lightdm does not load, but
the safe graphics mode dialog is displayed, instead This dialog fails
to accomplish anything other than allowing me to exit to a terminal and
I thus cannot use the system in graphical mode at all (even
Please let me know if I can provide further helpful information. (Or if
imdoinitwrong.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1173491
Title:
Boot to Safe Graphics after upgrade to Raring
I'm having the same problem. Notifications used to mostly just turn up
on left hand monitor in Maverick, for me, but in Natty they are always
in the invisible area, which does make them quite useless.
David, is your solution a suggestion to the devs, or is it meant for
users, who are looking for
Thank you for your insight and your suggested fix, edemeulle. I have run
into this bug myself and it can be rather annoying.
I have some experience with python, although I know little about /proc
and what kinds of things the cmdline entry for a process might
possibly contain in general. I was
Well, that was silly of me... forgot to fix my fix for the fix :S .
Here's what I meant to post:
# Check if the process with pid is running
def pid_running(pid):
if os.path.isdir('/proc/' + str(pid)):
with open('/proc/' + str(pid) + '/comm') as fd:
cmd =
Just in case anyone else finds their way here before finding a solution.
There is useful information in the plugin's bug tracker:
http://code.google.com/p/pidgin-facebookchat/issues/detail?id=246
In particular, I found that the recommendation to disable the option
called Show Facebook
Thank you for the updates, madbiologist!
Do you know if I could run apport-collect, although I'm not the original
reporter? If so, I'll be happy to sit down with a different working
system and try to figure out, how to run apport blindly. Hopefully any
prompts involved should be predictable
Hey Bryce
The original reporter may have worked around the issue and then
forgotten about it. I was just hoping to help fix this.
Is my input of no use...? I'll save myself any further effort on this if
it isn't.
Thanks
Nick
--
10.4 RC Live CD - Blank screen with Radeon 5870
Hi Bryce,
I tried to run apport-collect 569372, but as there does not appear to
be an update to this bug, I assume the attempt failed. As this is a
blank screen issue, I had no visual feedback to see why it failed.
Here's what I tried to do:
-booted the final release (not RC) normally
-waited
I have the same problem on my Radeon 5850.
When booting the live CD with default options, the graphical boot splash
(Plymouth) works, although it runs at a low resolution (Presumably
640x480). Once the x server should take over the screen, the screen
simply blanks, although the system continues
Hi
I need to use subversion for work and encountered problems installing
subclipse from the update site, so I am looking foward to finding it in
the ubuntu repositories.
In the mean time, Stephane, I highly appreciate your efforts of
packaging subclipse. I have already installed it on one of my
35 matches
Mail list logo
