Public bug reported:
Binary package hint: xserver-xorg-video-intel
Started to experience this problem after upgrade to beta Lucid.
Running 2.6.31 kernel since 2.6.32 kernels fail to boot on my hardware.
Boots OK with ACPI off. Even 2.6.32-16 fails to boot with ACPI on.
# lsb_release -rd
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/41647331/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/41647332/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41647333/Dependencies.txt
**
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Started to experience this problem after upgrade to beta Lucid.
Running 2.6.31 kernel since 2.6.32 kernels fail to boot on my hardware.
Boots OK with ACPI off. Even 2.6.32-16 fails to boot with ACPI on.
ProblemType: Crash
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/41647331/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/41647332/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41647333/Dependencies.txt
**
I can confirm a similar problem on my Intel 855GM. System boot OK with
2.6.31.X but I haven't been able too boot any of the 2.6.32-X kernels
normaly.
When I disabled ACPI with a boot option in grub, the kernel 2.6.32-15
booted, but the system where unstable and crashed after 1 minute.
# lspci
I don't think this problem has to do with the kernel version. It's more of a
integration problem in the development of startup-script for bluez bluetooth
services. When the package bluez-utils is removed, the problem goes away.
Before bluez start, everything works fine. After bluez is started I
Public bug reported:
I have upgraded a couple of Gutsy systems 2 weeks ago now. Since the
upgrade it's not possible to shutdown any of the systems with the menu
command
System - Shut Down... - Shut down
I'm expecting the system to shutdown.
I'm keeping the systems updated daily.
Description:
Tried to replicate this problem today.
Gutsy 2008-03-13
ii gstreamer0.10- 0.10.14-1ubunt GStreamer plugin for ALSA
ii gstreamer0.10- 0.10.6-0ubuntu GStreamer plugin for ESD
ii gstreamer0.10- 0.10.2-2ubuntu FFmpeg plugin for GStreamer
ii gstreamer0.10- 0.10.14-1ubunt GStreamer plugin for
Can't repeate this bug anymore. Fixed?
Oh well... Since the problem described in this problem does not seem to exist
anymore, it's time to close this bug.
** Changed in: rhythmbox (Ubuntu)
Status: Incomplete = Invalid
--
Crash when changing song
https://bugs.launchpad.net/bugs/133179
I suffered the same problem when updating my server to gutsy.
Resolution was removing evms.
--
gutsy can not mount root filesystem (device or resource busy)
https://bugs.launchpad.net/bugs/137180
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Nope, not PowerPC. It´s a AMD Athlon XP.
From the Valgrind file:
--13274-- Arch and hwcaps: X86, x86-sse1
--
Crash when changing song
https://bugs.launchpad.net/bugs/133179
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
OK. After a huge effort I managed to get a Valgrind log. It's
extreemly slow to run Valgrind :-)
valgrind 1:3.2.3-1ubuntu1
rhythmbox 0.11.2-0ubuntu2
** Attachment added: Log from Valgrind when the crash appears
Public bug reported:
Binary package hint: rhythmbox
Running Gutsy. Latest uppdates as of 2007-08-17.
ii gstreamer0.10-alsa 0.10.14-1ubuntu2 GStreamer plugin for ALSA
ii gstreamer0.10-esd 0.10.6-0ubuntu1 GStreamer plugin for ESD
ii gstreamer0.10-gnomevfs
Thanks...
Will try it tonight. I think this is a bug in the Ubuntu environment though.
This bug should be registered om bluez-utils then.
2007/4/25, johan [EMAIL PROTECTED]:
This is a work around:
A quick search around the Internet and it turns out that using the
Synaptic Package Manager to
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: None = xorg-server
--
Blutooth DiNovo does not work after boot
https://bugs.launchpad.net/bugs/96036
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: desktop-effects
Machine:
Dell Precision M65, NVIDIA Quadro® FX 350M 512MB
The following makes my problem appear:
- Installing fresh Feisty Beta
- Updating with update-manager
- installing nvidia-glx
- Run nvidia-xconfig
- Restart computer cold
- Log in,
Even with autologin via gdm the functionality stops.
But when run this way it hangs after gnome splash has been shown.
What is the common denominator for theese two ways of starting X and
gnome? Is it possibly some auto-something-system that restarts or starts
during this step?
Any suggestions?
Tested on several computers now. Same behaviour.
** Changed in: Ubuntu
Status: Needs Info = Confirmed
--
Blutooth DiNovo does not work after boot
https://bugs.launchpad.net/bugs/96036
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Public bug reported:
First of all... I don't know if this is a DiNovo problem or a general
USB/Wireless/Bluetooth problem.
I'm using Logitech DiNovo Bluetooth Keyboard and mouse. The following config:
- Ubuntu Feisty Herd 5 with updates made once per day.
- Linux 2.6.20-12-generic #2 SMP i686
*** This bug is a duplicate of bug 89425 ***
** This bug has been marked a duplicate of bug 89425
Failed to install, conflicting files in xrgb
--
file owned by x11-common included
https://launchpad.net/bugs/89424
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: x11-common
Failed to install when going from server-desktop dist.
dpkg: error processing
/var/cache/apt/archives/x11-common_1%3a7.2-0ubuntu1_i386.deb (--unpack):
trying to overwrite `/etc/X11/rgb.txt', which is also in package xrgb
Errors were
Public bug reported:
Binary package hint: xrgb
When trying to upgrade from server-desktop I got an error while trying
to install xrgb from depends.
Unpacking xrgb (from .../xrgb_1%3a1.0.0-0ubuntu2_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/xrgb_1%3a1.0.0-0ubuntu2_i386.deb
Running feisty since herd 1 without X.
I've been removing and adding some packages to create a desktop
environment instead of a server installation.
My problem occured when trying to install x-window-system package.
dpkg -l reports:
Name Version
Strange...
This is a newly installed Feisty Herd5
$ dpkg -l *xrgb*
ii xrgb 1.0.0-0ubuntu2 X RGB database and utilities
$ dpkg -L xrgb | grep rgb.txt
/etc/X11/rgb.txt
/usr/lib/X11/rgb.txt
--
Failed to install, conflicting files in xrgb
https://launchpad.net/bugs/89425
--
But...
From a newly installed computer:
$ dpkg -L x11-common | grep rgb.txt
/usr/share/X11/rgb.txt
Must have been a upgrade issue. Some old reference to /etc/X11/rgb.txt
in x11-common.
From a computer that's been upgraded from
dapper-edgy-feisty(herd1)...-...feisty(herd5):
$ dpkg -L
The bug seems to be solved with new python package.
--
update-manager crashed in feisty
https://launchpad.net/bugs/79274
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: gdm
I'm been experiencing trouble starting gdmsetup since upgrading to gdm
2.17.5-0ubuntu1 in Feisty from edgy.
Before upgrading everything was OK. Ran it yesterday.
strace gdmsetup halts on
futex(0x8133df0, FUTEX_WAIT, 2, NULL
** Affects: gdm
And the factory gdm.conf file
** Attachment added: gdm.conf that is used
http://librarian.launchpad.net/5774486/gdm.conf
--
gdmsetup halts on futex
https://launchpad.net/bugs/79660
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
dpkg -l *gdm*
ii edgy-gdm-themes 0.8-0ubuntu1
ii feisty-gdm-themes 0.8-0ubuntu2
ii gdm 2.17.5-0ubuntu1
** Attachment added: output from strace gdmsetup
http://librarian.launchpad.net/5774480/err
--
gdmsetup halts on futex
*** This bug is a duplicate of bug 79660 ***
** This bug has been marked a duplicate of bug 79660
gdmsetup halts on futex
--
Cannot run gdmsetup
https://launchpad.net/bugs/66034
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Problem changed when upgrading:
makedev (2.3.1-83ubuntu2) ...
python-gconf (2.17.2-0ubuntu2) ...
python-gnomecanvas (2.17.2-0ubuntu2) ...
python-gnome2 (2.17.2-0ubuntu2) ...
Now the error is:
warning: could not initiate dbus
current dist not found in meta-release file
Running Feisty Fawn 7.04
ii
Public bug reported:
Binary package hint: update-manager
Introspect error: The name org.freedesktop.UpdateManager was not provided by any
.service files
Traceback (most recent call last):
File /usr/bin/update-manager, line 86, in module
app = UpdateManager(data_dir)
File
** Attachment added: Problem Report for update-manager
http://librarian.launchpad.net/5726456/_usr_bin_update-manager.1000.crash
--
Update-manager crashes at connect to Dbus
https://launchpad.net/bugs/79149
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Sorry...
Should have added some more info from the start...
Running Feisty with update-manager 0.51build1
The error first occurred today after I ran an upgrade manually with apt-
get. First tried to start from the new GNOME Control-panel. I got a
crashreport. Tried from console and got
Came accross same problem on a Dell 2950 with Perc RAID controller.
Have done a number of tests and I am unable to get Ubuntu Dapper to boot
from discs on the RAID-controller on this machine.
--
Grub - Error 21 returned
https://launchpad.net/bugs/8978
--
ubuntu-bugs mailing list
35 matches
Mail list logo
