Oh, I see that I neglected to credit Hedley Finger for the alias code.
It's been so long I forgot that I got that here. Thanks Hedley -- that's
made my life easier for sure!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
While I might not phrase my comment as loneanon has, he is correct on
every point. In previous versions of (k)ubuntu users could edit files as
root using Kate. Making that no longer possible is taking away
functionality that many of us were used to. I have yet to see any
justification for this
'Invalid' defined as: Not a bug. May be a support request or spam.
This designation seems a bit cavalier. Root could edit in Kate before.
Now it can't, presumably because of changes made in the ongoing
development. That is a bug.
As end users we appreciate the efforts that are made by the
Yes. Annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762864
Title:
kate cannot run as root
To manage notifications about this bug go to:
Just adding my voice to this bug and pointing out that its presence is
preventing my migration to the 16.04 version of Kubuntu. I have Xenial
installed and ready to go but simply can't use it if it is necessary to
restore all my apps in their respective desktops on each boot. 14.04
still works
For me, the problem was solved by doing a clean install of Karmic. Thank
you for all your work on this excellent application.
--
Data CDs authored by Kubuntu K3b 1.68.0 are unreadable
https://bugs.launchpad.net/bugs/487761
You received this bug notification because you are a member of Kubuntu
I have to agree with Derek. With due respect to all the techs who do the
hard work of keeping Ubuntu (and especially Kubuntu in my case) so
great, I find that, as technical folks, we sometimes get overly focused
on the technical side and forget about the larger world in which that
exists.
FWIW:
1. I'm having this problem intermittently
2. When it occurs on my Karmic box, it also occurs on a Windows 7 laptop
(wireless) on my home network.
3. Other computers on the network (XP both wired and wireless) remain
functional DNS wise, except that sometimes my web request to the router
Not currently. Juk now acts the same as Amarok and Dragon Player since
my upgrade to Karmic: MP3 (and other media types) files simply don't
play. I don't believe this is a problem with Juk.
(Media files DO play in vlc and totem)
I'm going to try a clean install. Thanks for looking at this.
Actually, I'm starting to think that this is not only a K3B bug but a
(K)Ubuntu system bug. I run a WinXP virtual machine on my Kubuntu box
and it cannot find the writer either in cases when K3B cannot. This is
in conflict with the report from ssus. ssus - are you still having
success with
Prodigal wrote:
Ok how exactly did any of you manage to update when the update manager
itself will not work?
Console apt-get update? If so which program are you updating? I'm
getting security errors when I try to run apt-get install or apt-get
update no matter which package I try to
First of all, my drive is a 716A like that of ssus not a 719A as I
originally stated. Second and most important, this problem appears to be
FIXED in the latest version of K3b: 1.0.4-2ubuntu1~gutsy1
NeroLinux was starting to look pretty good, but K3b is the best and my
application of choice for
OK - I spoke too soon. After the 4th disk K3b lost touch with the writer
again. Here is the dmesg output:
[1167230.405850] hdc: status error: status=0x59 { DriveReady SeekComplete
DataRequest Error }
[1167230.405856] hdc: status error: error=0x44 { AbortedCommand
LastFailedSense=0x04 }
Public bug reported:
Binary package hint: k3b
This is similar to #114471 which is now closed. My Plextor 719A DVD
burner worked fine in K3B in Edgy. When I upgraded to Feisty this
scenario occurred: When the machine is booted, it finds the drive and I
can burn exactly one CD or DVD. Then it
14 matches
Mail list logo
