Public bug reported:
I've removed all packages not originating from ubuntu.com; there were
still hundreds of "Broken" packages listed. I've removed a lot of them,
but there's also a bunch of "essentials" like ubuntu-desktop, gnome-
shell, gnome-settings-daemon.
ProblemType: Bug
DistroRelease:
We are a few versions further, of everything, but I'm still having
issues with (nearly identical) HPE Bl460gen7 hosts, some of which fail
on the lshw step, others don't. Did anyone get an insight on how to
solve this? Or work around it?
--
You received this bug notification because you are a
Seeing the issue still with Version: 3.4.2-4ubuntu1. Radio streams just stop
with the "internal data stream error". Other players such (VLC, TuneIn app)
play the same stations/URLs just fine.
It takes at most a few minutes for the error to occur so it renders Rhythmbox
completely useless as
Seeing the issue still with Version: 3.4.2-4ubuntu1. Radio streams just stop
with the "internal data stream error". Other players such (TuneIn app) play the
same stations/URLs just fine.
It takes at most a few minutes for the error to occur so it renders Rhythmbox
completely useless as online
Hi,
I seem to have same problem with bluetooth headset Plantronics Backbeat pro2:
A2DP works fine, media keys work. But when switching to HSF/HFP, no playback
and no audio from mic.
Headset seems to switch the mode (something in the Noice cancellation audibly
changes) when switching between
This also applies to the list of emails in a folder, this makes
scrolling trough my mails a very colorful experience..., but also makes
it render subject text over adjacent columns.
** Attachment added: "screenshot email list"
I started experiencing this problem on 12.04, it persisted after upgrading to
12.10 and even persisted after a clean install (on an empty partition) of
13.04. It also happens when I just boot from a USB stick with 13.04.
This is always with the same partitions and I'm guessing that might be
adding a line create 640 syslog adm in /etc/logrotate.d/rsyslog (in
the two blocks) resolves the permission issue for me (Ubuntu 12.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/940030
Title:
I added the AUTO -all to my mdadm.conf and updated the initramfs. The
result is that no array is assembled automatically at startup and I
enter the recovery shell. Then I perform an mdadm -A -s and all arrays
are assembled correctly. This assembly takes about 2-3 seconds and
correctly assembles
That's correct, one of the 3 devices is another array. But this setup
worked in previous Ubuntu releases. If I remember correctly I created
the array in Ubuntu 10.04, and it has since worked in 11.04 and 11.10.
It's always been the same array, I know that at least once it was a
clean new install
of course, see attachment
** Attachment added: md5 info
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/990913/+attachment/3448634/+files/mdadm_blkid_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No, adding rootdelay=180 doesn't solve the problem. I now have
configured the system not to start with a degraded array. Which results
in the boot process being interrupted by a initramfs/rescue shell. In
that shell I stop the raid (mdadm --stop /dev/md5) and re-assemble the
arrays: mdadm -A
What is the status of this bug supposed to be in Ubuntu 12.04 with
kernel 3.2.0-32-generic #51-Ubuntu SMP Wed Sep 26 21:33:09 UTC 2012
x86_64?
I updated to this version (coming from 11.10) last weekend, and now my
nested raid always starts in degraded mode.
What I can reproduce every time:
Power
Sorry, previous post wasn't completed. To this post attached: the dmesg
output. It seems md finds md4 before it starts with md5. Yet,
/proc/mdstat returns another order, and most importantly: md5 is started
in degraded mode.
What i tried:
- added rootdelay=6 as kernel option in grub
- added this
I'm running Precise, and for some reason I got a partial distribution upgrade
from the software update; It suggested to remove 125 Obsolete packages. Which
included a lot of the i386 libraries (I at some point explicitly installed
ia32-libs to have those, and I never uninstalled that package.)
In the process of testing fglrx versions and radeonhd, I found that the
good old radeon does suspend to ram and wakes up correctly afterwards.
--
[Vostro 1000] Resume fails after suspend/hibernate
https://bugs.launchpad.net/bugs/468850
You received this bug notification because you are a member
I can suspend to ram and wake up again without problem (and without removing
the video module).
My configuration: Ubuntu Karmic, kernel 2.6.31-17-generic.
What did I do:
first I purged the old version of the fglrx driver and installed the recent
version (9.12, released December 17th 2009) of
I tested the radeonhd driver (the 1.2.5-1 version in ubuntu 9.10). This
doesn't make suspend work either. The system becomes unresponsive after
wake-up from suspend to ram.
--
[Vostro 1000] Resume fails after suspend/hibernate
https://bugs.launchpad.net/bugs/468850
You received this bug
terminator: reproducable
gnome-terminal: reproducable
xterm: not reproducable
konsole: not reproducable
I also noticed that the location of the mouse pointer matters when you
switch from terminator/gnome-terminal to gedit: the mouse pointer should
not be over the terminal window. If the mouse
I can hibernate fine, but suspend makes the screen and keyboard become mostly
unresponsive.
To be more precise: I can shutdown/reboot the notebook by pressing
alt-printscreen-b, but shift nor numlock lights can be toggled. I can login
with SSH, but Xorg wont react. Running some x commands just
Public bug reported:
Binary package hint: gnome-terminal
Steps to reproduce:
* open a gnome-terminal window and maximize it (i don't know wheter maximizing
is necessary, but it seems to help)
* fill the window with text (run dmesg for instance)
* start selecting text from the top of the window
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37373821/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/37373822/XsessionErrors.txt
--
gnome terminal doesn't leave select mode and keeps overwriting clipboard and
makes selecting
*** This bug is a duplicate of bug 468850 ***
https://bugs.launchpad.net/bugs/468850
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/37250060/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/37250061/AplayDevices.txt
** Attachment
*** This bug is a duplicate of bug 468850 ***
https://bugs.launchpad.net/bugs/468850
Public bug reported:
(Same) or from description at least similar bug as
https://bugs.launchpad.net/ubuntu/+bug/468850
Dell Studio 1535, suspend (and hibernated) worked fine with Ubuntu 8.04, 8.10
9.04.
I'm not an expert, but I also tend to think wpa_supplicant may be the
culprit: when the roaming happens, and I just wanted to use iwconfig and
dhclient3, I did killall NetworkManager, but the device kept roaming
(I'm not sure whether the roaming was still logged, but looking at
watch iwconfig eth1
Why is this bug still incomplete?
I can also confirm it exists and is very irritating.
I'm running Ubuntu Intrepid
Linux ambrosio 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64
GNU/Linux
Network manager version: 0.7~~svn20081018t105859-0ubuntu1.8.10.1
Package: network-manager-gnome
Public bug reported:
My system boots fine with the 2.6.24-21-generic kernel, but with the
linux-2.6.24-21-xen kernel, it gives this (see attachment) error message
and stops booting.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
xen kernel Eeeks when starting HAL
** Attachment added: log_xencrash
http://launchpadlibrarian.net/18697773/log_xencrash
--
xen kernel Eeeks when starting HAL
https://bugs.launchpad.net/bugs/286016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I seem to be having the same Kernel BUG. It seems to prevent hald from
working (when gnome starts it says failed to initialize hal).
I get kernel BUG at mm/slab.c:597! in dmesg, and it says Process hald (pid:
4204, ti=d6138000 task=db90c030 task.ti=d6138000), so I assume hal has
something to do
lspci -vvnn
** Attachment added: lspci -vvnn output
http://launchpadlibrarian.net/8280703/lspci-vvnn.txt
--
kernel BUG at mm/slab.c:597!
https://bugs.launchpad.net/bugs/111589
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I can reproduce it every time I boot the pc.
When i do ps aux, I can still see hald, hald-runner and
hald-addon-keyboard processes
(one of them was Defunct.
I tried restarting hald (/etc/init.d/dbus restart), it seems to hang for a
while on hald. And another Kernel BUG at ... appeared in
31 matches
Mail list logo
