Hi,
I just upgraded from Kubuntu 8.04 to 9.10 and then to 10.04 and didn't
experience the problem. I used to have this problem on previous upgrades on the
exact same system, so it appears it has been fixed. I vote to close it.
--
Upgrade tool crashed with " Cannot allocate memory"
https://bugs.
Sebastien, I will be upgrading my laptop from Kubuntu 8.04 to 10.04 one
of these days, so I will post back here. Frankly, I am scared to
upgrade, but it will be a good test because it is double upgrade from
8.04 to 9.10 and then to 10.04 (Kubuntu doesn't support a direct
upgrade).
--
[patch] Upgr
On Tue, Aug 12, 2008 at 6:51 AM, Jonathan Thomas <...> wrote:
> Could you see if this is an issue with the KDE4 version of Dolphin?
>
> ** Changed in: dolphin (Ubuntu)
> Status: New => Incomplete
OK, I just ran a couple of more tests:
- First I reproduced it in KDE 3 in Hardy, just in cas
What's the point of looking at the log files ? This seems like a trivial
bug, which my patch (submitted about 6 months ago) fixes.
--
Gutsy cdromupgrade script fails
https://bugs.launchpad.net/bugs/154195
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
On Sun, Feb 24, 2008 at 3:03 PM, Brian Visel wrote:
> This bug has been around for over two years. It has been reported for
> over one year.
>
> It's incredibly demotivating. I'm just disappointed with Ubuntu's
> organization at this point. There doesn't seem to be any way to
> escalate this.
It is naive to expect that this can be fixed by the community. Problems
of this kind can only be fixed by a coordinated entity with resources:
someone that can purchase different hard drives, possibly laptops, and
is able to put some pressure on the manufacturers for information, and
to invest sign
On Dec 14, 2007 2:18 PM, Brian Visel wrote:
>[...]
> Reasonable Limits / Criteria for a fix:
> * There should be fewer than ~15 load cycles per hour, except during heavy
> usage while on battery.
> * This provides a life expectancy of over four years, which is reasonable
> for a hard disk.
Public bug reported:
When Dolphin is browsing an SMB share like "smb://server/share/dir" and
the user clicks on a .tgz file like
"smb://server/share/dir/archive.tgz", Dolphin tries to open
"tar://server/share/dir/archive.tgz". It can't because this is on an SMB
share, so it just fails with an err
Here is the workaround which worked for me:
* Download the Kubuntu "Alternate Install CD", burn it and mount it in /cdrom
* From a shell execute:
cd $(mktemp -d)
tar xzf /cdrom/dists/gutsy/main/dist-upgrader/binary-all/gutsy.tar.gz
wget http://launchpadlibrarian.net/10255100/DistUpgradeViewText.pa
Happened to me too. There seems to be a small bug in
DistUpgradeViewText.py. The attached patch fixed the problem for me.
** Attachment added: "DistUpgradeViewText.patch"
http://launchpadlibrarian.net/10255100/DistUpgradeViewText.patch
--
Gutsy cdromupgrade script fails
https://bugs.launchpad
On Nov 2, 2007 5:12 AM, Javier Arántegui wrote:
> Hi!
>
> How are the things going? I'm not a developer and am unable to apply the
> simplest patch :-(
>
> It's a little bit frustating to be in no men's land. Now my distro is in
> the middle of the update process so neither I don't get the updates
I don't think it is realistic to expect that ordinary users will be able
to find this bug and administer a workaround from the command line on
their own. At the very least a detailed description of the problem and
the workaround should be prominently displayed in the upgrade
instructions.
I still
Guys, is there any progress on this bug ? It is extremely serious. It
was reported during the upgrade to Feisty, and it looks like it is still
present during the upgrade to Gutsy. I was bitten before, when I
upgraded a coworker's computer to Feisty (thank god he didn't attempt to
do it alone).
I c
I don't know if it is relevant, but I performed the Feisty upgrade
logged on as a different user - not the one experiencing the problems.
I was actually upgrading the system of a friend, so I used my own
account to do the upgrade. When I log on as the user which performed the
upgrade (myself), eve
It happened to me too. In my case, this is how Konqueror looks all the time not
only with Ctrl+N(!), so it is a huge problem for me. I just submitted a bug
(possibly duplicate of this one):
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/114947
Any ideas how to fix it ?
--
Konqueror new
This bug probably is a duplicate of this one:
https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/110702/
--
Konqueror menus and toolbars broken/missing after upgrade to Feisty
https://bugs.launchpad.net/bugs/114947
You received this bug notification because you are a member of Kubuntu
Team, w
Public bug reported:
Binary package hint: konqueror
I performed an upgrade to Kubuntu Feisty. After the upgrade, Konqueror
is missing toolbars, most of the menus are missing and the rest are
badly scrambled. I am attaching a screenshot. I couldn't find a way to
restore the menus and toolbars, so
A couple things to notice in the screenshot:
- The "Help" menu is second instead of last. You cannot see it in the snapshot,
but the "View" menu is missing most of its items.
- There is no location bar, no buttons for navigation (and there is no way to
enable them)
** Attachment added: "Snapsh
** Bug watch added: KDE Bug Tracking System #78509
http://bugs.kde.org/show_bug.cgi?id=78509
** Also affects: kdenetwork (upstream) via
http://bugs.kde.org/show_bug.cgi?id=78509
Importance: Unknown
Status: Unknown
--
kpf fails to serve file names containing ~
https://bugs.launchp
I think I have isolated the problem in the source. It is in
kdenetwork-3.5.6/kpf/src/Server.cpp lines 252-265:
// If there's .. or ~ in the path, we disallow. Either there's a mistake
// or someone's trying to [EMAIL PROTECTED] us. I wouldn't have worried
about ~
// normally, because
Public bug reported:
Binary package hint: kpf
kpf (KDE's public file server) doesn't serve files whose names contain the
character "~" and returns HTTP error 403 (forbidden). For example, setup a
simple test directory and create two files:
mkdir ~/testdir
touch ~/testdir/file1.txt
touch ~/testd
I have a couple Kubuntu machines in our office to waiting to be
upgraded, but I am putting that on hold for now. I can't risk it -
apparently here some people's machines were hosed after the crash
(shouldn't there be something on the main site, to warn people
temporarily against upgrading). It is a
Forgot to add some details: I ran "aptitude dist-uprade" after the crash and
everything is fine now - I am happily running Feisty.
I don't think is related to with wireless networking, but for the record my
laptop is with Intel 3945ABG.
--
[MASTER] [kde] Upgrade tool crashed (edgy -> feisty)
ht
Encountered the same problem today - the stack trace is exactly the
same. If necessary I can upload my log files.
--
[MASTER] [kde] Upgrade tool crashed (edgy -> feisty)
https://bugs.launchpad.net/bugs/107188
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Public bug reported:
Binary package hint: sun-java5-jre
I have already reported this bug aianst the Debian package:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416452
Basically, when /etc/localtime is not a symlink, the Java runtime cannot
reliably detect the system timezone. Depending on t
25 matches
Mail list logo
