I've just tried to connect to a webdavs URL in Ubuntu 11.10 and I get
the same results as reported above: attempting to enter a folder makes
it appear as a file (after the moved permanently error), but using the
list view and expanding the tree shows the contents of a folder.
I've seen this
I imagine that the reporter has now moved on from this situation.
However, people in similar situations should see the following page for
ways to refresh the kernel's view of the partition table after adding
partitions:
http://serverfault.com/questions/36038/reread-partition-table-without-
I'm now running Kubuntu Hardy with KDE 3.5.10, and I haven't seen this
problem since I last commented, either.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
https://bugs.launchpad.net/bugs/31491
Title:
kio_http processes build up
For the record, the problem seemed to manifest itself when the memory
card in the camera was heavily utilised. Having fewer images stored on
the card seemed to make it less likely for the process of connecting to
stall. What I did notice was that the initialisation of hotplugged
devices did become
Thanks to everyone who figured this bug out. I installed backported
versions of ifupdown and netbase from Intrepid and this specific problem
seems to be solved for me.
However, after having to hunt down the apparent cause of the problem
(useless wlan0 interface being brought up at boot which does
Just looking at KNetworkManager in Hardy, and there doesn't seem to be
an option to connect automatically to trusted networks. I don't see how
this bug is somehow irreproducible, or rather I don't see how this
apparently missing feature is somehow present, thus invalidating the bug
- if it isn't a
*** This bug is a duplicate of bug 190595 ***
https://bugs.launchpad.net/bugs/190595
** This bug has been marked a duplicate of bug 190595
knetworkmanager does not automatically connect to trusted networks
--
It doesn't connect to any available wifi network automatically at boot
A comment on the attached program: if the bad block corresponds to a
directory, it probably isn't a good idea to try and fix it since this
appears to cause ext3 to panic and remount the affected partition read-
only.
--
Persistent SATA errors possibly indicating disk fault disappeared with new
The attached program can be used as follows:
python badblock.py device lba
For example, where smartctl reports an LBA_of_first_error of 12345678:
python badblock.py /dev/sda 12345678
This should report one of the following things if successful:
Bad block corresponds to file: filename
Bad
I've managed to reproduce the old error message with the new kernel, so
I'm going to close this bug. What I've done is to run a long test using
smartctl as follows:
smartctl -t long /dev/sda
Then, upon having a bad block reported, with...
smartctl -a /dev/sda
...producing a report like this...
For the old kernel:
cat /proc/version_signature version.log.old
** Attachment added: version.log.old
http://launchpadlibrarian.net/36604293/version.log.old
--
Persistent SATA errors possibly indicating disk fault disappeared with new
kernel
https://bugs.launchpad.net/bugs/493819
You
For old kernel:
uname -a uname-a.log.old
** Attachment added: uname-a.log.old
http://launchpadlibrarian.net/36604295/uname-a.log.old
--
Persistent SATA errors possibly indicating disk fault disappeared with new
kernel
https://bugs.launchpad.net/bugs/493819
You received this bug
Having now booted both the old and new kernels, I don't get the SATA-
related errors in the syslog at all. Here I'm including the output of
dmesg in the new kernel from today's experiments. I've also run short
smartctl tests in the old and new kernel environments without provoking
read errors in
Public bug reported:
I'm trying to track down an apparent change in behaviour between the kernels
supplied in the most recent packages for Ubuntu Hardy, specifically
linux-image-generic 2.6.24.25.27 and linux-image-generic 2.6.24.26.28,
concerning SATA error reporting, supposedly these
cat /proc/version_signature version.log
** Attachment added: version.log
http://launchpadlibrarian.net/36552498/version.log
--
Persistent SATA errors possibly indicating disk fault disappeared with new
kernel
https://bugs.launchpad.net/bugs/493819
You received this bug notification because
uname -a uname-a.log
** Attachment added: uname-a.log
http://launchpadlibrarian.net/36552507/uname-a.log
--
Persistent SATA errors possibly indicating disk fault disappeared with new
kernel
https://bugs.launchpad.net/bugs/493819
You received this bug notification because you are a member
Really? According to the following page, 8.04 is supported until April
2011 at the earliest:
https://wiki.kubuntu.org/
--
by upgrading to hardy, ksplash-engine-moodin got removed
https://bugs.launchpad.net/bugs/206542
You received this bug notification because you are a member of Ubuntu
Bugs,
Confirmed on a fully updated Kubuntu Hardy (recently upgraded from
Gutsy) with Firefox 3 running the Plastik KDE theme.
Installing the gtk2-engines package provided a number of Gtk+ themes.
Then, going into System Settings, under Look Feel choosing
Appearance, then entering the GTK Styles and
Just did a Gutsy to Hardy upgrade since Gutsy is now no longer
supported, and this issue remains.
It doesn't matter whether this issue is fixed in 8.10 or 9.04 if
people are upgrading to Hardy and will stick with that release. Indeed,
since one has to upgrade to Hardy to upgrade beyond Hardy
In my grub menu.lst file, the following line appears at the end of the
file:
### END DEBIAN AUTOMAGIC KERNELS LIST
Thus all the title, root, kernel, initrd definitions appear above this
comment. I looked at some old menu.lst files, and some of those do have
definitions between the above comment
Attached is my menu.lst file. Here is what I did:
1. I installed a new disk in my computer alongside my old disk.
2. I partitioned the new disk and formatted the partitions.
3. I mounted the new disk's partitions and copied files into them.
4. I edited the fstab on the new disk's root partition
OK, I ran update-grub and it appears that no changes were made, so I
suppose that the configuration is stable.
Thanks for the help and information!
--
Unable to boot Ubuntu server after update/upgrade
https://bugs.launchpad.net/bugs/321603
You received this bug notification because you are a
This bug seems to be similar to my own experiences, so I'm adding this
comment to it.
After having my system upgraded yesterday (2009-01-30) using the package
linux-image-2.6.22-16-generic_2.6.22-16.61_i386.deb, I found today that
it was impossible to boot my computer. Upon selecting any entry in
Of course, the last part of my comment should read, if such special
files with disk information *exist* then these should be documented
somewhere.
--
Unable to boot Ubuntu server after update/upgrade
https://bugs.launchpad.net/bugs/321603
You received this bug notification because you are a
I also found that if I open the Add camera... dialogue, edit the
existing camera, change the camera model and then change it back (so
that the dialogue thinks a change has been made), then press OK (and OK
to close the list of cameras), the connection problem seems to go away.
This is a better
Maybe. I'm not running 8.10, but the jython package still only
recommends jython-gcj in that release. So I guess the problem is still
there.
--
Jython integration with Java API seems awkward
https://bugs.launchpad.net/bugs/144154
You received this bug notification because you are a member of
Still an issue on Gutsy, kernel 2.6.22-16-generic, coreutils
5.97-5.3ubuntu3
--
Misleading error message with mv and existing directories
https://bugs.launchpad.net/bugs/71174
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: digikam
I experience the following problem, and this actually started when I
upgraded from Kubuntu Feisty to Gutsy. My camera (Fujifilm F31fd) was
previously registered in digiKam, but after having started the
application a few times after the upgrade
Public bug reported:
Binary package hint: jython
After installing the jython package, attempts to import Java API
functionality seem to fail:
Jython 2.1 on java1.4.2 (JIT: null)
import urllib
Traceback (innermost last):
File console, line 1, in ?
File
Public bug reported:
Binary package hint: konqueror
Unlike Hoary, Kubuntu Feisty seems not to include the ability to
navigate into archives (zipfiles, at least) as if they were directories.
Sadly, this means that users have to open the Ark application and use
the WinZip-style user interface
Still an issue on Feisty, kernel 2.6.20-16-generic, coreutils
5.97-5.2ubuntu3
--
Misleading error message with mv and existing directories
https://bugs.launchpad.net/bugs/71174
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: adept-manager
Choosing Help - Adept Manager Handbook produces the KDE help viewer
and the message There is no documentation available for
/adept_manager/index.html.
Adept Manager 2.1 Cruiser (Using KDE 3.5.6) on Kubuntu 7.04, English
language,
This is part of the Adept usability critique and doesn't really merit a
separate bug, but how is one supposed to know that Request Install is
actually going to install all packages whose details are being shown in
the card stack of details? I don't have the Adept Manager Handbook in
my install
I've no idea if this is the best bug to add my experiences to - the
title sums up my experiences, though - but upon installing Feisty, the
console doesn't handle my Norwegian keyboard properly. The æ, ø, å keys
are detected, but they print combinations of bizarre characters. Perhaps
by changing my
I still run Kubuntu Hoary with KDE 3.4.0, but I haven't had this problem
for a while. I don't use all of the sites I was using when I reported
this problem originally, so perhaps I'm not exposing the cause of the
bug any more, but it could be the case that some fix or other made its
way downstream
Well, as for the importance of this bug, I suppose that people expert
enough to want to have multiple installations probably should know how
to edit grub menus, but I'm a bit disappointed that there have been two
releases since Hoary without fixes for this. Had I had time, I would
have attempted a
No problem, Colin! I just thought it was a bit embarrassing for Ubuntu,
really.
--
grub menu contains combinatorial expansion of existing installations
https://launchpad.net/bugs/26031
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
37 matches
Mail list logo
