curtiswtaylorjr, update your operative system!
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu
I am having the same problem as described above. Any help is
appreciated.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
Last upstream version fixes this
** Changed in: kdesudo
Status: Confirmed => Fix Released
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing lis
try:
sudo chown -R ben.ben ~
to make you own your stuff.
See if that fixes it. Make sure to upgrade kdesudo too.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-b
I am getting an error when I install kdesudo ... wine: /home/ben/.wine
is not owned by you
does this help to better define the error?
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct sub
I disagree due to the fact that uninstall kdesudo and it works and
after it stops working I reinstall it. It has something to do with
kdesudo
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a d
This issue is probably due to one of the other programs you have
installed. It sounds very strange, but I doubt it is related directly
to kdesudo.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have read what you all have posted and somewhat understand but not
fully. I have been going round and round with this issue of kdesudo and
cannot figure out what I need to do to get this fixed. I use gusty and
have tried to get an answer as to how to fix this issue or how to get a
fix for it.
Wouter Horré: That sounds sane to me.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
I'm not sure about this, but I think you need *read* access on
~/.Xauthority to able to connect to X. With NFS root_squash, root is
mapped to nobody, which would require .Xauthority to be world readable,
which is not the case.
Can somebody confirm this hypothesis?
--
kdesu ownership change
https
maybeway36 wrote:
> Seems like a different issue, all right. I don't use NFS, and it works
> fine here.
I thought the same, but maybe we are wrong.
Here's why:
gogh wrote:
> I have exactly the same behavior as wateenellende here.
> kdesu version 1.1-0ubuntu2.2 doesn't fix it.
Brian Buchanan wr
Seems like a different issue, all right. I don't use NFS, and it works
fine here.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Does anyone know how connections to X are made ?
If this is completely independent from any file owner issue, then bug
144722 is not a duplicate of this bug and should be treated separately.
Unfortunately I can't find an "unduplicate" button.
--
kdesu ownership change
https://bugs.launchpad.net/
Just read my original bug report, 144722, which is marked as duplicate
of this one.
On Nov 24, 2007 4:47 PM, maybeway36 <[EMAIL PROTECTED]> wrote:
> Looks like someone should file another bug.
>
>
> On Nov 24, 2007 2:29 AM, wateenellende <[EMAIL PROTECTED]> wrote:
> > In that case, there must be s
Looks like someone should file another bug.
On Nov 24, 2007 2:29 AM, wateenellende <[EMAIL PROTECTED]> wrote:
> In that case, there must be something else wrong as well.
>
> The kdesudo ubuntu2.2 did not work for me, programs could not connect to
> the X server. If I recall correctly, issueing an
In that case, there must be something else wrong as well.
The kdesudo ubuntu2.2 did not work for me, programs could not connect to
the X server. If I recall correctly, issueing an "xhost +" would resolve
that.
Removing kdesudo and using kdesu instead worked for me.
Other people have reported tha
The current version of kdesudo in gutsy and hardy does not need root-write
access to $HOME.
The kdesudo version released in the first gutsy, did however start programs as
root, but with the users environment variables.
This evil and ugly bug told programs like adept, dolphin, konqueror and others
IMHO, this is not a "NFS permission problem", because having
root_squash is desirable behaviour and not a problem. Secondly users
may not have control over the NFS server (such as here at work), so
root_squash will always be in effect, and kdesudo should work in such
an environment anyway.
Anyway,
@gogh: I do think your problem is a duplicate of this bug. If kdesudo
is working as it should, it never accesses files in ~/.kde, but only
in /root/.kde. So mounting your home file system with root_squash
should not be an issue if kdesudo is working correctly.
kdesudo_1.1-0ubuntu5_i386.deb as post
I confirm that I have the same no_root_squash behaviour. Mounting my
home this way granted access to kdesu. BUT, I don't think that this is a
fix. Using no_root_squash introduce serious security problems and I
don't want to mount my filesystems that way. Anyway, I didn't change nor
update my NFS se
I thought I had bug 144722 today, but it turned out to be a NFS
permission problem. /home was exported without no_root_squash i.e.
root_squash was in effect. (I was also using NFS4, fyi) I believe that
this situation would prevent the sudo (or kdesudo) process from having
access to the root owned
I have exactly the same behavior as wateenellende here.
kdesu version 1.1-0ubuntu2.2 doesn't fix it.
Duplicated bug 144722 describe my problem more accuratly than this one.
Seems to me that it is not the same issue. My /home is through NFSv4
like described in the 144722 bug. The problem appears a
Running apps as root worked for me; other users did not.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
Just checked today, as I saw that kdesudo was updated.
Still can't connect to X server. (original bug 144722, marked as duplicate of
this one)
I'm a bit lost, did there exist a version that did not have this problem ?
If so, is this the fix that was uploaded to Hardy ? If that is the case, can we
At least it works with root, as it sohuld, and normal users can get a
fix. If they want to use different users, they can remove kdesudo and
run kdesu.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which
Last upload to hardy fixes the issue.
THe patch has been merged with the bzr branch.
** Changed in: kdesudo (Ubuntu Hardy)
Status: Confirmed => Fix Released
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubun
You can't run programs as non-root users (like you could in an earlier
version) and I still have no clue what's going on.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Copied to gutsy-updates.
** Changed in: kdesudo (Ubuntu Gutsy)
Status: Fix Committed => Fix Released
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
Can someone please bring Frode M. Døving's fix into gutsy-proposed?
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have some questions:
1. Why was kdesudo 1.1-0ubuntu2.2 put in proposed?
2. How is it different from kdesudo 1.1-0ubuntu5, posted by Frode M. Døving and
verified to work?
3. What is simple-patchsys.mk?
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notifi
I have verified that kdesudo 1.1-0ubuntu2.2 fixes the issue of
ownership. However I did receive this information when upgrading the
package:
Preparing to replace kdesudo 1.1-0ubuntu2 (using
.../kdesudo_1.1-0ubuntu2.2_amd64.deb) ...
Unpacking replacement kdesudo ...
/var/lib/dpkg/info/kdesudo.pos
Please bring version 5 into proposed. Why was version 2.2 introduced?
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
With kdesudo 1.1-0ubuntu2.2 we are back to being unable to start anything
non-root:
--
[EMAIL PROTECTED]:~$ kdesudo -u safeav xosview
Xlib: connection to ":0.0" refused by server
Xlib:
No protocol specified
Can't open display named
--
--
kdesu ownership change
https:/
What has changed in kdesudo "2.1" since kdesudo "5"? What was wrong
with version 5?
On 10/31/07, Jonathan Riddell <[EMAIL PROTECTED]> wrote:
> On Wed, Oct 31, 2007 at 08:24:03PM -, maybeway36 wrote:
> > Is this the same version 1.1-0ubuntu5?
>
> No.
>
> --
> kdesu ownership change
> https://bu
On Wed, Oct 31, 2007 at 08:24:03PM -, maybeway36 wrote:
> Is this the same version 1.1-0ubuntu5?
No.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mai
Is this the same version 1.1-0ubuntu5?
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
New package accepted into gutsy-proposed, please test.l
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
Seems simple-patchsys.mk isn't enabled for some reason in this package.
Altered debian/rules to apply our patch (but not the other patches in
debian/patches).
** Attachment added: "patch for 2.2"
http://launchpadlibrarian.net/10225512/DIFF
--
kdesu ownership change
https://bugs.launchpad.net
http://ubuntu.lnix.net/misc/kdesudo_1.1-0ubuntu5_i386.deb
This should work perfectly.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bug
I also have this bug when using the "run as root" feature in Dolphin for
example.
My workaround is to change the home folder and files permissions back to the
user using the console, so far.
Is there a working patch available?
The ones posted above seem not to work 100%.
--
kdesu ownership chan
Ditto that.
On 10/25/07, jott <[EMAIL PROTECTED]> wrote:
> Please do not move kdesudo_1.1-0ubuntu2.1_i386.deb to gutsy-updates,
> but continue with a version based on Frode's kdesudo_1.1-0ubuntu5_i386.deb.
> Thanks
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received thi
@Martin: I have just tested kdesudo_1.1-0ubuntu2.1_i386.deb from gutsy-
proposed.
This version does _NOT_ solve all problems:
kdesudo konsole ->
[EMAIL PROTECTED]:~# echo $UID $HOME
0 /home/jo
[EMAIL PROTECTED]:~# pwd
/home/jo
but should be /root imo.
Frode's kdesudo_1.1-0ub
kdesudo_1.1-0ubuntu5 also fixes the problems I had with root-konqueror
and dolphin (dup Bug #144722).
"echo $UID $HOME" in a root-dolphin's terminal now returns: 0 /root
Thanks for the fix.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification becaus
I can confirm that kdesudo_1.1-0ubuntu5 fixes the problem mentioned in
the dup bug #132245. When running 'kdesudo kwrite', kwrite now uses /tmp
/kde-root and /tmp/ksocket-root.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a me
** Changed in: kdesudo (Ubuntu Gutsy)
Assignee: (unassigned) => Jonathan Riddell (jr)
** Changed in: kdesudo
Assignee: (unassigned) => Kubuntu KdeSudo Development Team
(kubuntu-kdesudo)
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification
That's how sudo works. It's like typing in a terminal:
sudo su anotheruser
On 10/22/07, jeroenvrp <[EMAIL PROTECTED]> wrote:
> @Frode: Thank you. The new deb (5 (2nd upload)) works fine, I don't need
> xhost +local: anymore to start X-applications as another (non-root)
> user. Only issue that rema
@Frode: Thank you. The new deb (5 (2nd upload)) works fine, I don't need
xhost +local: anymore to start X-applications as another (non-root)
user. Only issue that remains (by maybe thats a feature) is the issue
with the passwords. I have to give my own password (like sudo root) to
start an X-app as
Is the fix in the repos yet?
On 10/22/07, Frode M. Døving <[EMAIL PROTECTED]> wrote:
> jeroenvrp: Sorry, my bad. New deb up at same location.
>
> --
> kdesu ownership change
> https://bugs.launchpad.net/bugs/155032
> You received this bug notification because you are a direct subscriber
> of a dup
jeroenvrp: Sorry, my bad. New deb up at same location.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
@Frode: Yes, I even restarted X. When I downgraded to
kdesudo_1.1-0ubuntu3, it worked again right after I'd downgraded. So I
rather have kdesudo_1.1-0ubuntu3 than kdesudo_1.1-0ubuntu5.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because yo
Accepted into gutsy-proposed, please test.
** Changed in: kdesudo (Ubuntu Gutsy)
Status: Confirmed => Fix Committed
** Tags added: verification-needed
** Tags removed: needs-verification
** Changed in: kdesudo (Ubuntu Hardy)
Assignee: (unassigned) => Jonathan Riddell (jr)
--
kdesu
Can it be something with your session? Tried logging out and back in?
I can certainly kdesudo to root and other users on two machines. with
kdesudo_1.1-0ubuntu5.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Tested kdesudo_1.1-0ubuntu3, but now I can't use kdesudo for root
anymore (no permission for X). Reverted back to kdesudo_1.1-0ubuntu3.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
Oeps...
Must read:
Tested kdesudo_1.1-0ubuntu5, but now I can't use kdesudo for root
anymore (no permission for X). Reverted back to kdesudo_1.1-0ubuntu3.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs,
Tonio: this is sane for sudo, you shouldn't use sudo for graphical apps
for exactly that reason. not a bug in sudo imo.
jeroenvrp: I'm working on this issue now.
You can have a look at my changes and test:
http://ubuntu.lnix.net/misc/kdesudo_debdiff_ubuntu3_dynamic_xauth.diff
http://ubuntu.lnix.n
** Changed in: kdesudo
Status: New => Confirmed
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
** Also affects: kdesudo
Importance: Undecided
Status: New
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
I don't if it is related, but a part of this bug is not solved.
(confirming to marked as duplicate bug #144722.
I can indeed now start X-applications with root.
I still can't start applications as another user on my local system
(user "test" in the below example) without doing "xhost +local:" (x
On the other hand, I consider this a sudo bug and not a kdesudo one.
Remove your yakuakerc file, and start it via : sudo yakuake
Then look at your yakuakerc file... :
-rw--- 1 root root 25 2007-10-21 12:24 .kde/share/config/yakuakerc
--
kdesu ownership change
https://bugs.launchpad.net/bugs
Fix works, thank you
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listin
** Changed in: kdesudo (Ubuntu Gutsy)
Status: New => Confirmed
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
uploaded to gutsy-proposed
** Description changed:
- THIS IS A SECURITY ERROR!!
-
If I make kdesu this change the ownership to root to file in USER home,
and when you want to change the settings of this program as a regular
user you CAN'T becouse is owned by the root.
** Tags added: needs
.deb with fix.
** Attachment added: "kdesudo_fixed_deb"
http://launchpadlibrarian.net/10085282/kdesudo_1.1-0ubuntu3_i386.deb
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact fo
** Attachment added: "debdiff from ubuntu2 with fix."
http://launchpadlibrarian.net/10085122/kdesudo_environment.debdiff
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ub
sudo apt-get remove kdesudo
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
Like it says in the dup bug 132245 removing the package is not a fix,
it's a workaround at best and not a great one. If we need you to test
something you don't have the package to test any more, be prepared to
reinstall if we need you to test things.
--
kdesu ownership change
https://bugs.launchp
This is _NOT_ a security bug
sorry :)
** This bug is no longer flagged as a security issue
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mail
confirmed. this is evil.
** Changed in: kdesudo (Ubuntu)
Sourcepackagename: meta-kde => kdesudo
Importance: Undecided => Critical
Status: New => Confirmed
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ub
Removing the kdesudo package will fix this temporarily.
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
** Visibility changed to: Public
--
kdesu ownership change
https://bugs.launchpad.net/bugs/155032
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
70 matches
Mail list logo
