Sorry, not running ubuntu on same box again, cannot try to duplicate the
situation.
On Wed, Aug 13, 2008 at 4:43 PM, Andreas Moog
<[EMAIL PROTECTED]>wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't be
i have taken a different approach, just to say that now my restart works.
the change is quite drastic though. i upgraded to feisty, and then
installed the 2.6.19-5-generic kernel, which restarts fine.
so this is a temporary workaround, although those seeking stability will
probably opt to stay wi
This bug just occurred to me after a vanilla install of Gutsy + standard
procedure upgrade to Hardy.
I have installed nothing new, everything is vanilla.
--
evolution crashed with signal 5 in camel_stub_send()
https://bugs.launchpad.net/bugs/127954
You received this bug notification because you
I just got this bug after booting into my hardy install for the second
time.
I upgraded from a vanilla install of gutsy to hardy through the 'update-
manager -d' command.
--
mixer_applet2 crashed with SIGSEGV in g_object_unref()
https://bugs.launchpad.net/bugs/124416
You received this bug notifi
I got this bug after opening evolution for the first time on a vanilla
install of gutsy + hardy dist-upgrade.
--
evolution crashed with signal 5 in camel_url_new()
https://bugs.launchpad.net/bugs/187747
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug c
I just got this bug...
--
serpentine crashed with SIGSEGV in g_type_check_instance()
https://bugs.launchpad.net/bugs/132737
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
I just got this exact bug...
--
gnome-app-install crashed with signal 5 in PyEval_EvalFrameEx()
https://bugs.launchpad.net/bugs/187477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Me too...
--
[apport] alacarte crashed with TypeError in on_item_tree_cursor_changed()
https://bugs.launchpad.net/bugs/175602
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Yep, I get the exact same error message from the command line, the
gnome-font viewer simply will not load.
Using latest Hardy build.
--
gnome-font-viewer dont loads
https://bugs.launchpad.net/bugs/164920
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Sorry, but no longer have linux installed on current computer (windows
issues...)
I cannot give the backtrace, I am sorry.
On 5/17/07, Bryce Harrington <[EMAIL PROTECTED]> wrote:
>
> Thanks for your bug report. Please try to obtain a backtrace
> http://wiki.ubuntu.com/DebuggingProgramCrash and at
Public bug reported:
Binary package hint: acpi
I cannot restart edgy, everytime I try to restart, the bar goes all the
way to the right on the usplash, but then it hangs...and I have to
manually reboot the computer. Someone on the ubuntu forums suggested to
add "acpi=force" at the end of my kern
yes the only problem is restarting. it boots up fine and shuts down fine.
i have a desktop, and i'm using edgy eft, kernel 2.6.17-10-386. here's my
ubuntu device database entry:
http://hwdb.ubuntu.com/?xml=a5ded9623c62b48c737de9d0c4b4dd1a
i'll try those suggestion and see what's going on.
On 10
Okay I tried pressing Alt+SysRq+1 and Alt+SysRq+t at the time of the hang,
but I noticed that my keyboard turns off at this time, so I cannot press any
keys, as no power is coming into the keyboard.
i will reply to you with the output of the 'reboot' command from recovery
mode.
On 10/28/06, Erik
Okay, I wrote down the ouput. This is from the recovery mode cosole:
[EMAIL PROTECTED]:~# reboot
[EMAIL PROTECTED]:~# init: rcS-sulogin process (4037) killed by signal 15.
* Stopping GNOME Display Manager
* Stopping Common Unix Printing System: cupsd
* Stopping System Tools Backends system-tools-
Well the only changes I have made to my xorg.conf file is that i've changed
my driver from mesa to the fglrx driver, and it works peerfectly. also,
i've added more screen resolutions to that file, and at the end of it, i
added another section which says:
Section "Extensions"
Option "Composite" "0
Well i've never tried disabling usplash for my default kernel, but when in
the recovery mode kernel, i also have this problem (and there's no usplash
on the recovery mode kernel).
On 10/28/06, Nicolas DERIVE <[EMAIL PROTECTED]> wrote:
>
> Sorry, I hadn't understand exactly your problem. Do you hav
Public bug reported:
This happened when I tried coming back from standby.
I had enabled the fglrx driver graphically and manually, and had enabled
Composite in xorg.conf
Coming back from standby, I got a flashing screen of what looked like
the shutdown (power button) menu, but completely distort
** Attachment added: "CoreDump.gz"
http://librarian.launchpad.net/6933895/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6933896/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://librarian.launchpad.net/6933897/Disassembly.txt
** Attachm
Public bug reported:
Binary package hint: linux-image-2.6.19-6-generic
after i updated my feisty to this kernel, i cannot boot, the error is
acpi related, because it says "acpi: Unable to put cooling device 'on' "
or something along those lines.
i don't know ehere to look for a full kernel log,
Ah, sorry, I forgot to mention it also will not work with the
2.6.19-6-generic kernel. I've already tried, with the same result.
On 11/26/06, Laurent Bigonville <[EMAIL PROTECTED]> wrote:
>
> could you try with version 2.6.19-6-generic?
>
> ** Changed in: linux-source-2.6.19 (Ubuntu)
>Sta
Sorry for not being so helpful. I was really impatient, and installed
dapper again, which is completely stable for me. I will try feisty with the
new kernel though, sounds good.
On 12/15/06, Ben Collins <[EMAIL PROTECTED]> wrote:
>
> No response in several weeks. If you want to start working on
21 matches
Mail list logo
