I've now installed the proprietary fglrx driver, reinstated the
"vt.handoff=7" in /etc/grub.d/10_linux and then did a "Sudo update-
grub".
Upon booting with the current Ubuntu 3.5.0-17-28 kernel, I didn't have a
black screen anymore. Other than that, there's next to none difference
between booting
I've now installed the proprietary fglrx-updates (version 2:9.000-0ubuntu3)
from the Quantal repositories.
Just like Francisco T., I can now access the Settings dialog without problems.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to calligr
I can confirm that, the issue is *not* fixed with Ati Radeon cards! Radeon HD
6850 here.
Even with kernel 3.5.0-15.23, it's still the same. After selecting an entry
from the Grub menu and booting starts, the screen goes blank, and the monitor
displays "no signal". When booting ends, the screen c
I can confirm this bug.
Kubuntu Quantal Quetzal Beta x64 with latest updates. Krita version is
2.5.2-0ubuntu1 from the Quantal repositories.
Open Krita, then open an arbitrary image or create a new one, so the
configuration menu entry becomes avaiable. Try clicking on the menu
entry for the confi
** Description changed:
after the latest updates I get a black screen during bootup... it seems
related to the vt.handoff=7 feature of grub.
Infact removing this I can see at least the virtualterminal during bootup.
Maybe it is not correctly patched the latest release of grub (2.00-5ubuntu1
Tried out the .21 kernel, but it already has the black screen bug.
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays "no signal". When booting ends and X
starts up, the screen comes back to life, and the Lig
Tested the .20 kernel now, and it's already there as well.
Will continue further down.
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays "no signal". When booting ends and X
starts up, the screen comes back
Testing 3.5.0-14.19, already there, too.
How far back does this reach?
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays "no signal". When booting ends and X
starts up, the screen comes back to life, and the
Running 3.5.0-14.18... Guess who's there? Our friend, the bug.
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays "no signal". When booting ends and X
starts up, the screen comes back to life, and the LightDM
Yes, it's in .17 as well. Only one more to go now.
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays "no signal". When booting ends and X
starts up, the screen comes back to life, and the LightDM login scree
Already there in .16 as well.
Looks like a commit between .15 and .16 caused the bug.
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays "no signal". When booting ends and X
starts up, the screen comes back
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays "no signal". When booting ends and X
starts up, the screen comes back to life, and the LightDM login screen appears.
I'm using a Radeon HD 6850 with the ope
I just downloaded and installed the 14.15 kernel and tried it out. Good thing I
did, because it also has the bug.
I *thought* I had installed 14.15 before the upgrade, where the boot screen had
still worked fine, but it seems I'm mistaken there.
I went further back to kernel 13.14, but it has the
Perhaps I should also mention that I've now tried out the just released
mainline kernel 3.6.0 final.
Like all other mainline kernels I've tried, it *doesn't* have the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I tried out all three kernels listed above: 10.10, 5.5 and 1.1. Surprisingly
enough, all three have the black screen bug.
What to do next?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Just looked, and kernel 3.4.0-1.2 has builds avaiable. Should I take that one
instead?
https://launchpad.net/ubuntu/+source/linux/3.4.0-1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title
Do you have a downloadable version of that kernel?
Further down on the page, under "Builds", it says "Failed to build" for amd64
(and for all other platforms, too).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I've tried out kernel 3.4.0-1.2 now, and the bug is even there.
Now this is getting uncanny.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black ("no signal") after Grub,
ibus just crashed on me with the same obscure message:
"SIGABRT in g_assertion_message()"
I'm using Quantal x64 with latest updates and Kde 4.9.2.
On closing Aegisub, ibus suddenly crashed - seemed pretty random.
Didn't have this happening before.
Just looked it up in Synaptic, and ibus version
Anything else for me to try out?
I've been thinking... It could be that the bug appeared because of an update to
the video drivers in the xorg-edgers repository I'm using.
Some Ubuntu-specific modification to the kernel, which isn't present in the
mainline kernel, doesn't go well with the curren
The bug can't be fixed, as it's still the very same version of ibus.
Seem it appears only on rare conditions when closing an application.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048161
Title:
Shouldn't I rather try the Ubuntu-specific version of the kernel, rather than
the mainline version?
As we've seen before, no version of the mainline kernel I've tried has the bug.
The latest version of the Ubuntu-specific 3.2 kernel is 3.2.0-32.51:
https://launchpad.net/ubuntu/+source/linux/3.2.0
Just tried the 3.2.0-32.51 Ubuntu kernel. Even there it's the same black
screen during boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black ("no signal") after Grub,
@Lucazade
I've tried out what you suggested, so I launched a root Kwrite by
entering in the "Run" dialog:
kdesu kwrite
I opened /etc/grub.d/10_linux and replaced the line:
set vt_handoff=vt.handoff=7
with:
set vt_handoff=
I also opened /etc/default/grub and changed the gfxpayload to
** Description changed:
After selecting an entry from the Grub menu and booting starts, the screen
goes blank, and the monitor displays "no signal". When booting ends and X
starts up, the screen comes back to life, and the LightDM login screen appears.
I'm using a Radeon HD 6850 with the ope
Public bug reported:
After selecting an entry from the Grub menu and booting starts, the screen goes
blank, and the monitor displays "no signal". When booting ends and X starts up,
the screen comes back to life, and the LightDM login screen appears.
I'm using a Radeon HD 6850 with the opensource
Ok, I've filed a new bug here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1057532
@Lucazade,
Please confirm at the link above that the bug also affects you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black ("no signal") after Grub, comes back to l
Using the kernel 3.6 rc7 from the mainline now.
The bootscreen works fine, so the bug is fixed here :D
I've installed the kernel manually now. Is there a way to add a
Launchpad repository for the kernel, so you always have the latest
kernel installed, without having to do it manually?
** Changed
I've downloaded all three rcs you listed, installed rc1, rebooted... and lookit
there, already rc1 works fine and has the bug fixed :D
Now that was quick. No need anymore for the other two.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notificatio
I've installed and tested now both mainline kernels, 3.5.3 and 3.5.4.
Both kernels work fine and display the bootscreen as they should.
To check back, I've booted into 3.5.0-15.23 again, and yes, the black
screen during boot is still the very same there.
--
You received this bug notification bec
I've taken a look at the mainline kernel index to get the next 3.5 kernel after
3.5.4 for testing - however, there is no next 3.5 kernel.
The kernel following 3.5.4 is 3.6-rc1.
As none of the mainline kernels exhibits the bug, apparently one of the
modifications that Ubuntu did to the mainline ke
I'm already using proposed, so I just reloaded the software list and installed
the new kernel 3.5.0-16.24 which it offered.
On reboot though, it sadly exhibited the same black screen bug as before with
.23, no change there.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
**
No, it's not a Grub bug. I initially wasn't using any grub_gfx_payload
option, but the bug was the same, in Grub 1.99 as well as in Grub 2.00.
Then I added it, and while the resolution of the Grub menu changed
properly, it nothing about the black screen bug.
It's a kernel regression. I've now inst
Anything left to do here?
Or should I mark this as "fixed"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1057532
Title:
Monitor goes black ("no signal") after Grub, comes back to life when X
star
Public bug reported:
An application I would like to use requires wxWidgets of version 2.9+.
The current version of wxWidgets is 2.9.4, which came out about three
months ago:
Quote from http://wxwidgets.org/
"wxWidgets 2.9.4 Released
2012-07-09
wxWidgets 2.9.4 has been officially released. It is
Okay. Although I can't see any difference between booting with vt.handoff=7 and
the 3.6 mainline kernel, which I did before, and booting now with a current 3.5
Ubuntu kernel and vt.handoff turned off - no screen flickering or anything with
the latter.
Thus I don't quite see the point of this vt.
I've read that already. However, as I already said, there is *no* difference,
if vt.handoff is enabled or not.
I've disabled vt.handoff now, as per above, and booting is very smooth:
- Grub boot menu appears (with customised background image)
- after making a selection (or waiting until the boot
The status change for the Debian bug is *wrong*, as there has been no fix
released.
The bug was merely closed, pointing to a discussion from last year about
wxWidgets 2.9. However, that discussion ended in November last year, without
ever going anywhere.
As such, the issue at hand is still compl
I just updated Krita (and the rest of the Calligra suite) to version
2.5.3-0ubuntu2 from the Quantal repositories. The crash is still all the same
there. I'm using the latest free Radeon driver here.
Looking at the Backtrace below, I can see that it refers to two different
versions of libllvm: 3
I'm running Kde, not Unity (nor any other Gnome stuff), but ibus still
crashed, so I doubt it's in any way related to Unity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048161
Title:
ibus-daemon
41 matches
Mail list logo
