Re: Request for Comments (RFC): Potential change in setting sound card volume on boot
On Tue, Jun 26, 2007 at 09:20:59PM -0400, Daniel T. Chen wrote: (4) Additionally, users seem split on whether a default login sound in a graphical environment should be muted[4] or audible. To alleviate the issues given above, I am requesting comments from developers and users alike regarding the following proposal that changes alsa-utils's initscript usage[0]: I'm not sure this alleviates number 4 - surely it will always result in the login sound being muted? mixer_app won't be started until some time after the sound has started playing. It also leaves us with the issue of what to do with the GDM sound. Muting that by default would be an accessibility problem... -- Matthew Garrett | [EMAIL PROTECTED] -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Tribe 2 released
Hi, how can make a bootshart please a small tutatiol. thijs burema 2007/6/28, Martin Pitt [EMAIL PROTECTED]: Hello Ubuntu developers, welcome to Gutsy Gibbon Tribe 2, which will in time become Ubuntu 7.10. Pre-releases of Gutsy are *not* encouraged for anyone needing a stable system or anyone who is not comfortable running into occasional, even frequent breakage. They are, however, recommended for Ubuntu developers and those who want to help in testing, reporting, and fixing bugs. Tribe 2 is the second in a series of milestone CD images that will be released throughout the Gutsy development cycle. The Tribe images are known to be reasonably free of show-stopper CD build or installer bugs, while representing a very recent snapshot of Gutsy. You can download it here: http://cdimage.ubuntu.com/releases/gutsy/tribe-2/ (Ubuntu) http://cdimage.ubuntu.com/kubuntu/releases/gutsy/tribe-2/ (Kubuntu) http://cdimage.ubuntu.com/edubuntu/releases/gutsy/tribe-2/ (Edubuntu) http://cdimage.ubuntu.com/xubuntu/releases/gutsy/tribe-2/ (Xubuntu) See http://wiki.ubuntu.com/Mirrors for a list of mirrors. The first set of new features landed in Tribe 2 and are ready for large-scale testing. Please refer to the following web pages for details: http://www.ubuntu.com/testing/tribe2 (Ubuntu) https://wiki.kubuntu.org/GutsyGibbon/Tribe2/Kubuntu (Kubuntu) https://wiki.ubuntu.com/GutsyGibbon/Tribe2/Xubuntu (Xubuntu) This is quite an early set of images, so you should expect some bugs. Among these are the following (so you don't need to bother reporting these if you encounter them): * The desktop CD installer hangs indefinitely on some systems when choosing manual partitioning. If this happens to you, close the installer (wait a bit until you are offered to forcefully quit it), open a Terminal (in Applications - Accessories), and run: sudo killall ubiquity; sudo ubiquity (https://launchpad.net/bugs/122645) * When using restricted-manager to enable the proprietary Nvidia or ATi graphics driver on the live CD, the required driver packages will not be installed automatically to the newly installed target system and thus the graphical user interface will not start. Please only enable those drivers in an installed system for now. (https://launchpad.net/bugs/114296) * On Edubuntu server installs, the Building LTSP root step takes a very long time (in the order of 15 minutes) without visible progress. It will eventually finish, though. (https://launchpad.net/bugs/121547) * On Edubuntu server installs, the default DHCP configuration for thin clients is flawed, so that they will not boot from the server. To fix this, remove the line with 'next-server' from /etc/ltsp/dhcpd.conf and restart the DHCP server with sudo /etc/init.d/dhcp3-server restart (https://launchpad.net/bugs/122796) If the graphical system does not come up or is very slow, please file a bug against compiz: https://launchpad.net/ubuntu/+source/compiz/+filebug Please include a copy of the files ~/.xsession-errors and /var/log/Xorg.0.log, and the output of glxinfo and xdpyinfo. If you're interested in following the changes as we further develop Gutsy, have a look at the gutsy-changes mailing list: http://lists.ubuntu.com/mailman/listinfo/gutsy-changes Please be aware that this list usually has several dozen mails every day. We also suggest that you subscribe to the ubuntu-devel-announce list if you're interested in following Ubuntu development. This is a low-traffic list (a few posts a month) carrying announcements of approved specifications, policy changes, alpha releases, and other interesting events. http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce Bug reports should go to the Ubuntu bug tracker: https://bugs.launchpad.net/ubuntu Enjoy, The Ubuntu Development Team http://www.ubuntu.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGg64FDecnbV4Fd/IRApsBAJ4+xsYtFeE8EX4/GFXpN8ri2qEcCACgg0Th ravyiz4ZTwtVoH90bD3q7hk= =QYRT -END PGP SIGNATURE- -- ubuntu-devel-announce mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Ubiquity usability study
Unfortunately I have not yet had a chance to go through all of this, but I wanted to respond to a few points: On Thu, Jun 28, 2007 at 08:05:45PM +1200, Matthew Paul Thomas wrote: There are other visible errors in this screen, too. * Your new operating system is comically vague. The installer knows very well that it's installing Kubuntu, not some other OS. (I do not think that reducing translation requirements for derivatives is a good excuse for vagueness in Ubuntu and Kubuntu themselves.) There are translation requirements in Ubuntu and Kubuntu too; in fact, these are the most pressing concerns. For example Ubuntu in Korean is written thus: 우분투 (stem) 우분투가 (subject) 우분투를 (object) 우분투는 (something called topic) I'm not sure how to correctly write Kubuntu in Korean, though 쿠분투 would be my best guess. Given Korean spelling rules it certainly won't be a matter of prepending a character. Edubuntu and Xubuntu are also relevant. Or let's take Hebrew, where we have: אובונטו (stem) האובונטו (with definite article, e.g. the Ubuntu such-and-such) There are quite a few languages where I know that the name of the operating system should be transliterated but I don't know how to write Ubuntu in those languages. (Any Arabic-family or Indic-family speakers reading this?) You're effectively proposing that we maintain a table of all the possible translations of all the strings mentioning Ubuntu for each derivative into all the languages we support. We do that for precisely two strings right now in packages I'm aware of, on the CD bootloader screens, and I've already had complaints from translators about that. We have multiple projects on the boil right now involving improving support for more derivatives and reducing the patchsets they need to carry. Translation efforts for more languages are appearing, and most of the new ones are in language families that historically have tended to transliterate the name of the operating system. The problem is only going to get worse. I also do not think that we are entitled to disregard the needs of derivatives or of translators simply because it makes user interface design a little easier. User interface design is important to Ubuntu, but so is helping out derivatives, and so is localisation. I have no problem, of course, with the string being rephrased in other ways, and I think it probably should be; the current phrasing is rather clumsy. However, we settled on the approach of removing unnecessary branding years ago and I don't want all that work to be undone now. But if there are more than about half a dozen keyboard layouts, and you're not even showing what they look like, asking people to choose Which layout is most similar to your keyboard is completely unreasonable *regardless* of how the options are listed. (So this was a mistake on my part in the initial design.) I think it's worth noting that people do often (I know, not always, but pretty often) know what sort of keyboard they're using. It's not a *total* black box that they have to guess. I'd hazard a guess that the proliferation of options is confusing even if you think you already know what keyboard layout you're using: the fact that you can see all this choice means that you have to think about it. Do you think it would help if the UI started out by just displaying the default option for your language and country (the one we already select by default) plus the text box, accompanied by a Change... button? By making the safest option the default option, the risk to accidentally destroy information on another partition could be reduced. If the safest option cannot be identified, we would suggest to provide no default option and force the user to examine the options and make a choice. Dual booting also seems to be the most likely case for less technical users, and so the Manual option would be the best default. I'm trying to reconcile the screenshot of this step with Celeste's statement in the report that the participants were given the scenario to install Kubuntu along with Windows. Really? Where is that option? Is that what Manual is supposed to mean? If so, no wonder people just chose the default. I don't know of any dictionary where manual is defined as alongside Windows. I think you're laying on the sarcasm a little thick. :-) Though I haven't read the report yet, I suspect Celeste meant that the participants were given a system on which Windows was installed and instructed to install Kubuntu alongside it. Building on Celeste's ideas, I think we should have the first page of the partitioner include the existing radio buttons and titles for each option, but also a long description below each option that explains what it does. Defining the options would be a step forward, but it would be much better if they were reworded instead. For example: This is roughly https://wiki.ubuntu.com/UbuntuExpress/PartitioningTool, the last major
