Hardcodes ubuntu username

Bug #319393 reported by Loïc Minier
2
Affects Status Importance Assigned to Milestone
casper (Ubuntu)
Fix Released
Wishlist
Unassigned
ubuntu-mid-default-settings (Ubuntu)
New
Undecided
Unassigned
user-setup (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Hi,

The startx session (event.d upstart job) hardcodes the ubuntu user; we should change casper to use the target username instead.

Bye,

Revision history for this message
Kyle Cheung (kylezoa) wrote :

Thank you for taking the time to make Ubuntu better. Since what you submitted is a Feature Request to improve Ubuntu, you are invited to post your idea in Ubuntu Brainstorm at [WWW] https://brainstorm.ubuntu.com/ where it can be discussed, voted by the community and reviewed by developers. Thanks for taking the time to share your opinion!

Revision history for this message
Loïc Minier (lool) wrote :

This is actually part of a spec discussed at UDS: https://blueprints.launchpad.net/ubuntu/+spec/mid-display-manager

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

Having read the wiki page, I don't think it makes sense to do any of this in user-setup. user-setup already exports the username in passwd/username, and casper can retrieve that in a post-installation hook (ubiquity-hooks/) and do whatever it wants with it.

Changed in user-setup (Ubuntu):
status: New → Won't Fix
Changed in casper (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Loïc Minier (lool) wrote :

Thanks for the pointers

Revision history for this message
Stéphane Graber (stgraber) wrote :

casper no longer hardcodes the username anywhere.

Changed in casper (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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