autospawn = no does not help at all.
The only way I know that prevents pulseaudio from starting, is to move the
/usr/bin/pulseaudio binary away from it’s location.
This allows the system to start up normally.
I then run:
(sudo mv /usr/bin/pa /usr/bin/pulseaudio); LANG=C pulseaudio -
Oh, forgot to mention that I used ext3 for the system partition and
added the sync option in /etc/fstab, so hopefully nothing was lost
when writing to the log file..
--
karmic release candidate restarts computer when starting
https://bugs.launchpad.net/bugs/458676
You received this bug
That’s it?
If pulseaudio is not doing anything wrong with the HDMI, then something else
is. I do not care what anymore.
I have provided all information asked for, and more. I have spent a lot of time
trying to find out what is wrong, but no-one seems to care enough. Fine, let
this bug plague
I have just tried the lucid alpha2, and that still failed for me.
For karmic, I have tried some more variations, including upgrading
various gnome packages, gdm, trying other display managers,
upgrading/downgrading xorg and with it the video drivers, and also
trying various kernels.
It is
If downgrading to the jaunty version or upgrading to the lucid version (by
adding the repositories of the distribution and removing the karmic ones), then
the sound works, but no volume control, and System-Preferences-Sound does not
work (just a dialog that is waiting..).
If installing the
The crash is clearly sound related, and only occurs when pulseaudio
works.
** Package changed: gdm (Ubuntu) = pulseaudio (Ubuntu)
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete = New
--
karmic release candidate restarts computer when starting
Update:
Problem still occurs with all system updates applied.
--
karmic release candidate restarts computer when starting
https://bugs.launchpad.net/bugs/458676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Darko: This bug (458676) is it. Do not create a new one. The driver you
are referring to is fglrx, which is known to work, but is not a solution
to the bug, just a way to avoid it. See earlier posts for this bug. The
bug is related to the free driver, known as readeonhd and ati, which
you do not
Darko: livecd install menu option works, while the Try Ubuntu without
installing menu option does not (as it goes via GDM). However, if you
need to use the livecd desktop environment, simply choose cancel when
the installation starts.
Aaron: You should try newer or older packages of GDM and/or
The radeon/ati drivers are obviously supposed to work in Ubuntu 9.10.
I currenly use Ubuntu 9.04 with the radeon driver, and it works well (used to
use fglrx in Ubuntu 8.10, but can not get dual screen setup to work in Ubuntu
9.04 with fglrx, while it is extremely easy with the radeon driver).
With compiz I assume you are referring to the settings for desktop
effects.
Using fglrx, the system works fine both with and without desktop effects.
Using radeon, the desktop effects are off in the stock install, and can not be
enabled.
Have been trying to figure out more exactly when the
try the gnome failsafe session or the xterm
I assume you refer to choises from the log-in screen, which I have never
been able to reach using the Ubuntu 9.10 RC using the radeon driver (the
default). see comment below soon.
--
karmic release candidate restarts computer when starting
Have gone over it again. See archive for the various log archives.
Using only amd64 variants.
No problems with Kubuntu 9.10 RC live CD, the install, or after install.
see 910rc-stock-kubuntu-logs.tar.gz
Booting the Ubuntu 9.10 RC live CD causes the system to restart at 2nd loading
screen, i.e
** Description changed:
When booting the Karmic RC livecd (or an installation of it), the
computer restarts when it seems like it is just about to show the
desktop or login-screen.
- Interestingly, when using the live, if instead choosing to install it
succeeds to start the installer,
I’m guessing this is related to gdm since startx works but normal
booting does not.
When disabling xplash in /etc/gdm/Init/Default i get:
black screen -- login screen background -- black screen -- restart
When also adding automatic login in /etc/gdm/gdm.schemas i get:
black screen -- loading
the bug description is not clear
What is not clear?
What can be done to make this more clear?
Tried to get some more messages by adding a while(true); do sleep 0.1;
sync; done; to the /etc/gdm/PreSession/Default and got:
/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch
** Description changed:
- When booting the Karmic RC livecd, the computer restarts when it seems like
it is just about to show the desktop.
- Interestingly, if instead choosing to install it succeeds to start the
installer, and if then choosing to quit the installer, one ends up on the
You get the issue in a stock installation?
Yes. Exactly the same as when booting the live CD.
Do you get the login screen correctly displayed after installation?
No. The system restarts when one would expect the login screen to appear.
Same thing also happens when choosing the automatic login
** Tags added: ubuntu-boot
--
karmic release candidate fails to boot
https://bugs.launchpad.net/bugs/458676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: logs after starting X via startx from single user mode
http://launchpadlibrarian.net/34489046/k64-rc-updated.via-single.tar.gz
--
karmic release candidate fails to boot
https://bugs.launchpad.net/bugs/458676
You received this bug notification because you are a member of
** Attachment added: logs after booting normally (which fails)
http://launchpadlibrarian.net/34489124/k64-rc-updated.tar.gz.tar.gz
--
karmic release candidate fails to boot
https://bugs.launchpad.net/bugs/458676
You received this bug notification because you are a member of Ubuntu
Bugs,
Trying using the release candidate again.
The logs are the result after making all system updates, and then trying to
boot.
When trying to boot normally, only ro kernel option. The same thing as always
happens. The kernel text appears. Then X starts and the loading screen appears.
Then the
No idea where the bug is. Is it in upstart?
** Package changed: ubuntu = upstart (Ubuntu)
--
karmic release candidate fails to boot
https://bugs.launchpad.net/bugs/458676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Package changed: ubuntu = upstart (Ubuntu)
--
karmic release candidate fails to boot
https://bugs.launchpad.net/bugs/458676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I’m using the Karmic RC.
This happens for me both using grub1 and grub2.
It also happens both on my actual hardware (780G board with HD3200), and in
virtual box (version 3.0.8 r53138).
It also happens for both i386 and amd64.
Since I also suffer from
Errors at the recovery mode menu in post 2 above is because of
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/459636
--
karmic release candidate fails to boot
https://bugs.launchpad.net/bugs/458676
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 458352 ***
https://bugs.launchpad.net/bugs/458352
** This bug has been marked a duplicate of bug 458352
Karmic - Corrupted Recovery Menu
--
Can't boot into recovery mode
https://bugs.launchpad.net/bugs/459636
You received this bug notification because
Public bug reported:
When booting the Karmic RC livecd, it restarts when it seems like it is just
about to show the desktop.
Interestingly, if instead choosing to install it succeeds to start the
installer, and if then choosing to quit the installer, one ends up on the
desktop, which appears
** Attachment added: lspci -vv
http://launchpadlibrarian.net/34189091/lspcivv.txt
--
karmic release candidate fails to boot
https://bugs.launchpad.net/bugs/458676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
If installing and later trying to boot using legacy GRUB:
title Ubuntu 9.10, RC, kernel 2.6.31-14
root(hd0,0)
kernel /boot/vmlinuz-2.6.31-14-generic
root=UUID=1e015df5-1c88-4ffe-b02b-240fef87bd3c ro
initrd /boot/initrd.img-2.6.31-14-generic
..the same problem as
*** This bug is a duplicate of bug 368895 ***
https://bugs.launchpad.net/bugs/368895
** This bug has been marked a duplicate of bug 368895
gitosis not working after upgrade to 9.04
--
gitosis does not work at all since python scripts do not run as python2.5
Public bug reported:
Binary package hint: gitosis
Using Ubuntu 9.04.
Installed package version: 0.2+20080825-2
None of the python scripts in the package have a specification of which python
version is to be used.
This means that it works fine in Intrepid where the default is python2.5, but
does
** Attachment added: patch that could be applied with $$ sudo patch -p1 -i
/path/to/git.diff -d /
http://launchpadlibrarian.net/30994712/git.diff
--
gitosis does not work at all since python scripts do not run as python2.5
https://bugs.launchpad.net/bugs/421298
You received this bug
Too many comments here already, but feel that I must voice my opinion
too, and say that firefox should not be installed by default if it
requires an EULA. Epiphany or Iceweasel can be used instead. Place
firefox in multiverse or whatever.
--
AN IRRELEVANT LICENSE IS PRESENTED TO YOU
Yes, very annoying. At least make it optional.
--
[Hardy] Update Manager doesn't display package versions anymore
https://bugs.launchpad.net/bugs/189406
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
35 matches
Mail list logo
