Remaining issues for gnome-control-center 3.8 update
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Moved remaining issues from https:/
Perhaps these should be split into separate bugs:
* Consider simplifying the Ubuntu logo patch so that we don't have to wait on Design every cycle and to simplify backporting. LP: #1181442 The Ubuntu logo patch needs to be redone since upstream is now using the new gtk3 resource file
* symbol conflicts between gnome datetime panel and libtimezonemap (LP: #1187981)
* modemmanager needs to be updated. LP: #1123302
* input-sources-
* There's support for packagekit to install new language packs but not to uninstall them (since apparently PackageKit can't handle this)
* Do we really need sound_nua_
* Now named "Settings" Should we revert name to "System Settings" ?
* 59_install_
* We should probably just hide the new Sharing panel in Unity for now.
- The Sharing panel is useful although it was designed for a Red Hat style of handling services. With that model, services are not automatically run when installed, which allows those distros to include openssh-server by default. It's assumed that distros will install all the useful services by default.
- By default Ubuntu will get Screen Sharing (basically replacing vino-preferences) and Bluetooth Sharing (for computers with bluetooth)
- If someone adds PackageKit integration, perhaps Media Sharing (rygel) and Remote Login (openssh-server) could be enabled.
- However, the code currently requires systemd for the ssh "Remote Login" panel.
- Personal File Sharing is the frontend for gnome-user-share now but since it's just webdav sharing, this section is unusable in Ubuntu where gnome-user-share doesn't come with apache2. We could patch to hide this section.
Changed in gnome-control-center (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Moving the Sharing panel points to another bug would facilitate conversation regarding those potential changes separately from the rest of the issues. As I feel that to be the change that might spark the most discussion. The rest are smaller and mostly upgrades, so I feel the rest would probably be fine as one bug.