Ubuntu
user-setup package

Cannot launch sudo applications from GNOME menus

Bug #25598 reported by Chris Lancaster
26
Affects Status Importance Assigned to Milestone
user-setup (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I have made a small discovery, and it might not be the entire issue. I have
tested this on 3 laptops of mine, and it worked.

When you do an 'expert' install, you have the option to create users in the
installer. However, if you do so, you will not be able to run sudo applications
in Gnome. If you do NOT use this utility, the installer prompts you to make a
user account, and this account works. It seems the permissions given by the
'create users' portion of the installer is broken. The errors noted in this
thread: http://ubuntuforums.org/showthread.php?t=75722 are present when using
the create users function.

All installs are on intel machines, and are laptops. I have not been able to
test this on a desktop machine.

I apologize for the lack of technical data, but I am still new to Linux and Ubuntu.

Thank you.

http://ubuntuforums.org/showthread.php?t=75722: http://ubuntuforums.org/showthread.php?t=75722

See original description
Revision history for this message
Chris Lancaster (chris-365ink) wrote :

Forgot to mention, this is for the Breezy 5.10 release. I have not tested any
others.

Revision history for this message
Paul Boddie (paul-boddie) wrote :

This bug also applied to Kubuntu Hoary when installing in expert mode. I did
write about this in the Kubuntu Wiki [1] and there's a fairly old report
registered for it [2].

[1] https://wiki.ubuntu.com/KubuntuHoaryReleaseKnownProblems
[2] https://bugzilla.ubuntu.com/show_bug.cgi?id=9832

Revision history for this message
Carthik Sharma (carthik) wrote :

Is this still a bug with the Dapper Betas? (I strongly suspect not).

Can someone please confirm this now works as expected so we can close this bug?

Thank you for reporting this issue.

Changed in debian-installer:
status: Unconfirmed → Needs Info
Revision history for this message
Colin Watson (cjwatson) wrote :

(What's the basis of your suspicion that it is fixed?)

Revision history for this message
Carthik Sharma (carthik) wrote :

Colin, I knew this was a problem a time ago, and have seen people suggesting work-arounds in #ubuntu. I was thinking that since this was known since the Hoary, and since this bug hasn't had any updates or confirmations, the problem must have been fixed by now. Perhaps it is not - you know best :) Sorry if I was in error - I thought I might be which is why I put that in parantheses.

Revision history for this message
Colin Watson (cjwatson) wrote :

That scenario normally means that the bug is hard, not that it's been fixed. :-)

Revision history for this message
Carthik Sharma (carthik) wrote :

Colin,

Would this, and other bugs marked as dupes of this be actually duplicates of Bug #5100 ? Looks similar to me, but am not so certain myself.

Revision history for this message
Colin Watson (cjwatson) wrote :

I think there's a better bug report for that around somewhere, but I don't recall exactly where right now.

Colin Watson (cjwatson)
Changed in user-setup:
assignee: kamion → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for user-setup (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.