I have been having this bug off and on ever since using Ubuntu Breezy
(pretty sure it happens in both 386 and 686... but since it's so random,
and since I never really boot 386, I can't tell). I just found what I
think to be a breakthrough while booting up my PC today.
I started my machine up,
I have just managed to get my PS/2 keyboard working by unplugging it and
plugging it into my PC's other PS/2 port (labelled for use with a mouse)
Please see bug #48877 for my full post, PC specs (if needed), and current
xorg.conf file.
Here: https://launchpad.net/distros/ubuntu/+bug/48877
--
Yes I've worked around this problem magically. I'm trying to figure
out what it was that I did to get this to work, and hopefully it will
work for a new install of Dapper too.
--
Regular network drops with madwifi
https://launchpad.net/bugs/37821
--
ubuntu-bugs mailing list
I'm getting this too, with:
ubuntu dapper 6.06
KDE 3.5.2 (kubuntu-desktop package installed)
Amarok 1.4.1 - official package from:
deb http://kubuntu.org/packages/amarok-141 dapper main
Upon starting amarok, I see my memory usage start to slowly go way up...
and then amarok starts using 52% of
Public bug reported:
Binary package hint: xserver-xgl
This bug has been happening to me for some time now, quite randomly.
Each time I attempt to start amarok, there seems to be a random chance
that Xgl will crash, and I'll be greeted with my gdm login screen,
forcing me to restart my desktop
Full Xgl crash report attached
** Attachment added: Crash report
http://librarian.launchpad.net/7355682/_usr_bin_Xgl.1000.crash
--
Xgl crashes to gdm upon starting amarok
https://bugs.launchpad.net/bugs/107849
You received this bug notification because you are a member of Ubuntu
Bugs, which
I've been using the mysql database for my collection in amarok as well, and
have seen the same problem happening. This has been ever since updating to
Feisty.
Packages used:
Qt: 4.2.3-0ubuntu3
KDE: 3.5.6
Amarok: 1.4.5 (Build Date: Apr 4 2007) --- 2:1.4.5-0ubuntu7
mysql Ver 14.12 Distrib
It is indeed a problem with Network Manager, and not the madwifi drivers. I
have worked around this by uninstalling network manager, and simply configuring
wpa_supplicant by hand. This involved putting a startup script in /etc/init.d
that starts wpa_supplicant at bootup.
If you want to make
I also ran into the issue with no more accounts being available :(. Too
bad the new version had to wipe the old accounts off.
After seeing that this fix for Ubuntu went into hardy-proposed, I was
hoping to test the x86_64 build of weave in bug #442679 at mozilla bugs
with this. Oh well.. guess
Same problem on Fiesty.
I'm NOT running the packaged version of the drivers, but it's definitely ati's
fglrx drivers doing this.
This is still occurring with the NEW ones: version 8.41.7
Also note: one process seems to be spawning the other.
relevant output of: ps auxf
root 8892 0.0
This package is broken in Intrepid. Out of box, amarok does not find the
script, it does not have a .spec file to tell amarok to use it as a
transcoder, and the script is broken until using this version.
Here's how I fixed it on my system:
# Create symlink for amarok to find the script
sudo ln
I am having this issue on the Mythbuntu distribution. This distribution
is based off xfce. I have installed dolphin and ark, but there is no
extract here or extract to menu option in the right click menu.
I think this functionality may be enabled by installation of some other
package in the
Waiting on Intrepid Ibex Alpha5 to test as recommended.
The machine I had this problem on stopped doing this once I switched to
a USB keyboard, and I haven't tested the PS/2 keyboard lately (or even
updated my Ubuntu install on that machine lately either).
--
no ps/2 keyboard with kernel
I agree that this is a bug. My CPU usage is quite high on startup now,
and as soon as I do: sudo /etc/init.d/tremulous-server stop , I get my
CPU back ;).
In the meantime, I'm going to disable this for my machine.
--
tremulous-server starts on system startup, by default
With my problem, the keyboard not working seems to behave like a random
bug, popping up whenever it feels like it. I'm thinking that maybe this
is some sort of race condition, which may or may not be related to
multiple dependent threads running out of sync in the 686 kernel (But
then again, I'm
My Desktop is a Dell Dimension XPS Generation 2. I had lost track of this post
here, and forgot to update it with new info about the problem.
I am now running Edgy, and still occasionally run into the keyboard locking up
every once in a while, however, it seems much less frequent lately (or
Why does Ubuntu constantly have to mess with things that had already
been working and tested before, and then subsequently release them into
the repositories so it can break things for everyone?
This isn't just a problem with their version of netcat. I'm also
talking about pulseaudio, upstart,
Today it failed to mount on boot once again. I pressed S to skip
mounting, and upon trying to mount it manually, I get:
trinitr...@saturn:~$ sudo mount /media/terabyte
mount: /dev/md0: can't read superblock
trinitr...@saturn:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0]
Can verify that adding the -xkb command line flag fixes the problem!
Running Mythbuntu 10.04 Beta 2 with updates from apt.
I've attached a very simple patch for the session script in
/usr/share/mythbuntu/session.sh
** Patch added: Simple patch for mythbuntu session.sh
My RAID array still does not come up reliably upon every reboot. It
seems that if I reboot once after the not ready or present message,
it usually will come up fine the second time. I've been leaving my
system on for a while to avoid having to deal with this however.
Right now, I still need to
I am also seeing this upon update to mdadm_2.6.7.1-1ubuntu15 on a
mythbuntu box. Luckily I can just assemble and mount the array manually
afterwards, it just does not automatically do it upon boot.
This would probably be a showstopper for anyone brave enough to have
setup their root partition on
Found the line it was talking about in /var/lib/dpkg/info/mdadm.postinst
---SNIP---
if [ ! -f /proc/mdstat ] [ -x $(command -v modprobe 2/dev/null) ]; then
modprobe -k md /dev/null 21 || :
fi
if [ ! -f
*** This bug is a duplicate of bug 507881 ***
https://bugs.launchpad.net/bugs/507881
** This bug has been marked a duplicate of bug 507881
Plymouth doesn't show messages sent before the splash screen is visible
--
System won't boot after upgrade to 10.04
Looked into this more today and found that for some reason my array is
not being detected and assembled correctly after a reboot.
I've got a RAID 5 with 4 disks:
/dev/sdb1
/dev/sdc1
/dev/sdd1
/dev/sde1
Here's what I've accomplished so far:
1) I removed /dev/sde1 using sudo mdadm /dev/md0 --fail
Attached: output of examining all disk partitions with fdisk -l
** Attachment added: Examining partitions with fdisk -l
http://launchpadlibrarian.net/48587379/Examining_Partitions.txt
--
Mdadm array fails to assemble on boot.
https://bugs.launchpad.net/bugs/573477
You received this bug
Attached: kernel message log
** Attachment added: Kernel message log with working array before reboot, and
nothing after reboot
http://launchpadlibrarian.net/48587404/messages
--
Mdadm array fails to assemble on boot.
https://bugs.launchpad.net/bugs/573477
You received this bug notification
GParted just gave me troubles reformatting the drive again. Here are
the details of that.
** Attachment added: Gparted XFS format failure
http://launchpadlibrarian.net/48587994/gparted_details.htm
--
Mdadm array fails to assemble on boot.
https://bugs.launchpad.net/bugs/573477
You received
Now that I tried to create a new partition table and repartition /dev/sde,
mdadm is trying to use it strangely as a second array!! wtf?
GParted failed to repartition it a second time, and now this:
trinitr...@saturn:/media$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1]
--stop /dev/md_d0
[sudo] password for trinitronx:
mdadm: stopped /dev/md_d0
trinitr...@saturn:/media$ sudo mdadm --examine /dev/md_d0
mdadm: cannot open /dev/md_d0: No such file or directory
trinitr...@saturn:/media$ sudo mdadm --examine /dev/sde
mdadm: No md superblock detected on /dev/sde.
trinitr
Here is the successful output of GParted formatting /dev/sde1 before my
rebuild #5.
** Attachment added: Try #5 Repartitioning reformatting /dev/sde
http://launchpadlibrarian.net/48589374/gparted_details_SUCCESS.htm
--
Mdadm array fails to assemble on boot.
ok, finished rebuilding it and ran sudo mdadm --examine on every device and
partition. The info looks correct for:
/dev/sdb1
/dev/sdc1
/dev/sdd1
/dev/sde1
It reports mdadm: No md superblock detected for:
/dev/md0
/dev/sdb
/dev/sdc
/dev/sdd
/dev/sde
So hopefully this means that no superblock
I tried the fix by enabling the Mythbuntu autobuilds, and am currently
running version:
mythvideo 0.23.0+fixes25073-0ubuntu0+mythbuntu2
I'm still getting emails every hour like:
From: root sat...@lyraphase.com
To: root
Date: Fri, Jun 11, 2010 at 10:17 AM
Subject:Cron r...@saturn
Looks like I'm getting the jamu.py to exit some other way, as the lines
in my file read:
[..]
# Check if this is a Scheduled and Recorded graphics download request
if self.config['mythtv_watched']:
self._downloadScheduledRecordedGraphics()
sys.exit(0)
[..]
what is the status on this bug? I am experiencing it as well on my
updated Mythbuntu 10.04 Beta2 system.
--
mythfrontend.real crashed with SIGSEGV in
QX11PixmapData::x11ConvertToDefaultDepth()
https://bugs.launchpad.net/bugs/549593
You received this bug notification because you are a member of
Switched to gnome desktop in Mythbuntu 10.04 Beta 2 encountered this
bug. Needed to do the workaround.
Latest available version of mythtv on synaptic is:
0.23.0+fixes24158-0ubuntu2
Not sure if the numbering on trunk vs. fixes correlates... it still
seems to appear in this 'fixes' branch
I'm getting this message in an email from cron every hour.
Using mythvideo package 0.23.0+fixes24104-0ubuntu2
--
/usr/share/mythtv/mythvideo/scripts/jamu.py returns error on success
https://bugs.launchpad.net/bugs/485538
You received this bug notification because you are a member of Ubuntu
It does seem like there is a timing issue here. Some sort of race
condition causes the array to be assembled incorrectly, or not at all
perhaps. My gut tells me it's something to do with the new upstart
system that ubuntu moved to, because it never happened before they
switched.
I still haven't
Rebuilt again, and noticed an update for the mountall package too (not
sure if this was related).
Seems everything is being brought up fine now after a reboot. I just
hope it stays that way
--
Mdadm array fails to assemble on boot.
https://bugs.launchpad.net/bugs/573477
You received this bug
38 matches
Mail list logo
