I am also getting this bug. the "fix" by starting a new config folder
made no difference.
** Changed in: vinagre (Ubuntu)
Status: New => Confirmed
--
vinagre crash with "BadRequest (invalid request code or no such operation)"
when I try to connect to VNC server
https://bugs.launchpad.net
Public bug reported:
When booting, the system cannot find the /dev/disk-by-uuid for the root
fs, and drops me to busybox. On checking
/dev/disk-by-uuid is missing the UUID symlink for my raid 1 root,
however the raid is up and running and available on /dev/md0
This has happened during a few rebo
Can noone else confirm this? I can't think that it is only my machine.
Intrepid is due out real soon and this will surely be a showstopper for
some users (static IPs can be configured from /etc/network/interfaces
but having it not work from network-manager is not good)
I'm sure the problem is rela
Updated to intrepid and the problem still remains. I have to use debians
init.d script to get my hdparm settings working.
There is still no obvious way of testing the hdparm.conf either as you
cannot do /etc/init.d/hdparm to see that is works fine.
--
hdparm not being triggered with udev
https:/
Is this related to the problem I am having ?
See:
https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/227705
I'm having to continue using the init.d script as it isn't working from
udev. Note that the init.d script is still useful. How else are users
supposed to check whether their hdparm.conf
Are any developers currently looking at this. The importance should be
decided and imho it is important as a new user should expect to be able
to configure their system with a fixed ip with the provided tools (it is
still possible from /etc/network/interfaces of course). Kubuntu Intrepid
should not
Ah ive been looking at the wrong site. Seems kubuntu.net is not updated.
confusing! I notice this bug is mentioned on the download page for
kubuntu on kubuntu.org. So at least it is considered important and
hopefully fixed soon.
--
unable to configure a fixed ip on wired interface on knetworkmana
I can also confirm this bug. Makes kmail rather unusable!
--
(Kubuntu Intrepid) KMail crashes when I create a new message and try to access
the body of the message
https://bugs.launchpad.net/bugs/275218
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscri
There is an upstream bug about this, but I'm not sure much attention has
been paid to it by any kde devs (lost in the sea of kde bugs!).
I notice a fair few people in the kde bug are running intrepid, so I
don't know if this is just a kubuntu bug, or an actual kde bug. But it
certainly is an impor
I forgot the link. sorry
http://bugs.kde.org/show_bug.cgi?id=168245
--
(Kubuntu Intrepid) KMail crashes when I create a new message and try to access
the body of the message
https://bugs.launchpad.net/bugs/275218
You received this bug notification because you are a member of Kubuntu
Bugs, which
Public bug reported:
I am unable to configure a fixed ip using knetworkmanager on intepid.
After configuring a fixed ip from the "edit connections" gui, I try to put it
online, but get an error i syslog
Oct 7 01:50:35 travelmate NetworkManager:
connection_get_settings_cb(): connection_get_set
What about machines which the sysadmin has only remote access to ? He
will want the machine to boot into degraded mode, so services can be
running until he can contact someone at the data centre to replace a
disk. having it stop at a prompt in this scenario is not helpful.
--
degraded raid boot p
Aaah ok. then I'm happy ;-)
--
degraded raid boot process should interactively prompt user before dropping to
recovery shell
https://bugs.launchpad.net/bugs/257568
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I don't understand setting this to won't fix. Some people may not want
to use the plasma interface. As long as this package is available, this
bug should be fixed. Closing the bug will not make the problem go away!
--
knetworkmanager under kde4 doesn't recognize the static IP connections that I
Also, this bug has been around since before the release of intrepid. If
knetworkmanager is going to be broken, it is better to remove it from
the jaunty release altogether.
--
knetworkmanager under kde4 doesn't recognize the static IP connections that I
have configured.
https://bugs.launchpad.n
Public bug reported:
Under high load this device drops outgoing packets resulting in poor throughput
and unresponsive (e.g. ssh) sessions during file transfers
Steps to reproduce:
Transfer any large file via a TCP-based protocol using this onboard ethernet
device at 100mbit
Patch here:
http://
Public bug reported:
/usr/share/hotkey-setup/acer.hk would benefit from some additional lines
adding the wireless button on and off keys.
on = e055
off = e056
for example
setkeycodes e055$KEY_F13 # Wireless on
setkeycodes e056$KEY_F14 # Wireless off
This is useful, as
Most likely the same problem discussed here:
http://www.ubuntuforums.org/showthread.php?t=247350
--
vmplayer No Longer Opening Virtual Server
https://launchpad.net/bugs/58367
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Noticed it again today
5557 root 19 0 17216 13m 10m R 95.8 1.3 0:00.79 apt-index-watch
3989 root 15 0 157m 20m 6076 S 4.0 2.0 0:37.68 Xorg
1 root 15 0 1632 540 448 S 0.0 0.1 0:01.03 init
Running latest version 0.3.9ubuntu5
** Changed in: libapt-front (Ubun
** Summary changed:
- sis900 drops tx packets on Foxconn 661FX7MJ-RSH motherboard
+ sis900 drops tx packets on Foxconn 661FX7MJ-RSH motherboard (Includes patch)
** Description changed:
Under high load this device drops outgoing packets resulting in poor
throughput
and unresponsive (e.g. ssh
This seems to already be fixed in the current 2.6.17 kernel. Maybe the
patch got in upstream ?
--
sis900 drops tx packets on Foxconn 661FX7MJ-RSH motherboard (Includes patch)
https://launchpad.net/bugs/57846
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
I'm also having this problem. It tries to stop my "root" raid, which of
course is impossible whilst it's in use.
A developer on irc said they need to disable the stop call in preinst.
and to check how they did it for version 2.5 in Debian.
Would have been nice too if we got a newer mdadm for edgy
Public bug reported:
Binary package hint: initramfs-tools
I am running edgy
I have / on a raid 1 device /dev/md0
This is comprised of /dev/hda1 and /dev/hdb1
I am not using evms, but mdadm to manage my devices.
If I remove /dev/hda1 and reboot, the machine will boot up fine, but in
degraded mo
When i refer to remove and readding the disk, i mean doing so by pulling
the cable. So "failing" the drive.
--
Unable to boot with degraded array
https://launchpad.net/bugs/60646
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Once at the busybox prompt I can use mdadm and zero the superblock on
/dev/hda1 and after that i can reboot and once rebooted add the disk
back in as a spare.
--
Unable to boot with degraded array
https://launchpad.net/bugs/60646
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
I believe this problem is more related to mdadm, and that it should have
been fixed in a recent upload (but wasn't)
** Changed in: dmraid (Ubuntu)
Sourcepackagename: dmraid => mdadm
--
System does not boot anymore
https://launchpad.net/bugs/59066
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
To clarify the problem:
During the "initramfs" stage, there are no /dev/disk/by-uuid/xxx made
for the raid devices so the new booting by filesystem uuid stuff for
grub will not work.
This should have been fixed with the latest mdadm upload (
2.4.1-6ubuntu2) but even with this new version my syste
I managed to upgrade by moving /etc/init.d/mdadm-raid and replacing with
an empty script, upgrading and then moving it back.
--
Upgrading mdadm package is impossible - can't upgrade while raid arrays active
https://launchpad.net/bugs/60623
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
The order that mdrun starts /dev/mdx devices seems to be based on many
factors. Degraded arrays can affect the order.
Note this debian bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354705
Which has been fixed by deprecating the use of mdrun. However ubuntu
still uses mdrun (from initfs).
I ran update-initramfs again and now the system boots fine with UUID in
grub (After the new mdadm update). I thought I had done this already,
but I guess not.
--
boot confused after stopping array
https://launchpad.net/bugs/38438
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
I have set bug to rejected as It's already fixed upstream (Which has
made its way into edgy)
** Changed in: linux-source-2.6.17 (Ubuntu)
Status: Confirmed => Rejected
--
sis900 drops tx packets on Foxconn 661FX7MJ-RSH motherboard (Includes patch)
https://launchpad.net/bugs/57846
--
ubun
Try running
update-initramfs -u
--
Root on raid fails to boot
https://launchpad.net/bugs/57607
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
*** This bug is a duplicate of bug 64531 ***
I have this same problem. Every few seconds apt-index-watch runs and
uses a huge chunk of cpu. This causes problems like stuttering in movie
playback etc. This was not happening last week, so it's a new problem.
Hope a fix comes out before edgy release.
I also have this problem. Only noticed it the last few days or so.
Makes playback of videos stutter and other problems.
--
apt-index-watcher uses way too much system ressources
https://launchpad.net/bugs/64531
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
*** This bug is a duplicate of bug 64531 ***
Should be fixed now
See https://launchpad.net/distros/ubuntu/+source/libapt-front/+bug/64531
Certainly a new version is available on apt for edgy.
--
80% cpu used apt-index-watch
https://launchpad.net/bugs/64562
--
ubuntu-bugs mailing list
ubuntu-
** Changed in: hotkey-setup (Ubuntu)
Status: Needs Info => Confirmed
--
Add keycodes for wireless button on Acer Travelmate 8100
https://bugs.launchpad.net/bugs/57849
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
Public bug reported:
Binary package hint: hdparm
Since hdparm was switched from init.d to being triggered by udev it has stopped
working on my machine.
Originally I thought it was the missing rule for /dev/sdx disks but even with
that change (https://bugs.launchpad.net/ubuntu/+source/hdparm/+bu
There was a kernel patch which broke smart over sata. A stock
2.6.20/2.6.21 kernel seems to be fine. Perhaps something was backported
from 2.6.22 on ubuntu where the problem is also in the stock
(kernel.org) kernel.
Some references
Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=42897
Confirmed I have this problem also.
** Changed in: gcc-4.2 (Ubuntu)
Status: New => Confirmed
--
gij man page install leaves dangling symlink
https://bugs.launchpad.net/bugs/128563
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubun
On Thursday 12 July 2007, Reinhard Tartler wrote:
> The boot process will hand for three minutes and leave you at a busy box
> shell. This could be improved so that the problem is detected earlier
> and the option of getting to the shell (and with suggested commands)
> appears earlier.
>
> Once in
Since upgrading to feisty I'm also having a similar problem with all my
SATA drives.
[EMAIL PROTECTED]:~# smartctl -d ata -l selftest /dev/sdd
smartctl version 5.36 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Error SMART Status command f
I build a 2.6.21-rc6 kernel from kernel.org and tried it. The smart
stuff is working fine. It was also working on an earlier kernel. I
should try a stock 2.6.20 kernel to see if it's something specific to
ubuntu causing the problem.
--
smartmontools/smartctl does not work on SATA drives on Linux
Latest kpowersave has button events.
** Changed in: acpid (Ubuntu)
Status: Incomplete => Fix Released
--
power button is ignored by acpi scripts when running kpowersave
https://bugs.launchpad.net/bugs/84480
You received this bug notification because you are a member of Ubuntu
Bugs, which
KPowersave 0.7.2 just went into feisty. This version does have support
for button events. However afaik Klaptop does not. So now we need to
just check for kpowersave i guess.
--
power button is ignored by acpi scripts when running kpowersave
https://launchpad.net/bugs/84480
--
ubuntu-bugs maili
Public bug reported:
Binary package hint: acpi-support
The power button is ignored by the acpi-support scripts when kpowersave is
running. However kpowersave
does not have any capability to manage what happens when power button is
pressed. It can handle lid events though.
from /etc/acpi/powerb
the file /usr/share/hotkey-setup/acer-aspire-1600.hk
is also suitable for the travelmate-8100 series.
I also un-commented the Wireless On/Off keys in this file. Why are they
commented out? It is very useful to be able to map the "wireless on"
button to something like "kdesu ifup wlan0"
so, on my
Sorry. Ignore last patch. this is a working one.
Of course, other laptops from acer might also share these keys, so it
might be better to add them into the generic acer one?
** Attachment added: "Fixed patch for hotkey-setup"
http://librarian.launchpad.net/5851312/hotkey-setup-fixed.diff
--
> (a) the wifi switching is handled in hardware already
on my laptop, in addition to sending a keycode it "turns on/off" the
wireless, but this is not particularly useful unless you have some
script constantly watching for it (It's not switched on/off in a way
which is hotplug compatible) and the
ok. the last diff was rubbish too :/ (I'm having a bad day)
Attached is a fixed one, and working (I tested it this time).
Sorry about that.
** Attachment added: "patch for /etc/init.d/hotkey-setup for travelmate 81*
laptops"
http://librarian.launchpad.net/5851895/hotkey-setup.diff
--
Add k
I am running feisty and network profiles do indeed seem broken.
Configure eth0 interface to 192.168.1.10
Create a new profile "test". Click apply.
KNetwork conf then saves the current ip config to Test? (It's unclear - save
selected doesnt seem to do anything?)
Create another profile "Test2" and
I'll try that, but hdparm does work when pointing to a partition though
(and just uses the underlying device).
--
hdparm not being triggered with udev
https://bugs.launchpad.net/bugs/227705
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
51 matches
Mail list logo
