[Bug 1906770] Re: Kernel 5.4.0-56 Wi-Fi does not connect
The bug seems to be fixed, however I am having massive upload speed issues with said wifi hardware. With the same hardware under Windows, the problem does not occur. Maybe someone can help me to investigate the problem further. I have summarized the question here: https://askubuntu.com/questions/1292772/slow-upload-speed-via-wifi-on- ubuntu-18-04-with-fritzwlan-usb-stick-ac-860-ral -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906770 Title: Kernel 5.4.0-56 Wi-Fi does not connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906770] Re: Kernel 5.4.0-56 Wi-Fi does not connect
I can confirm the exact behaviour on Ubuntu 18.04. I use a FRITZ!WLAN USB Stick AC 860 with a Ralink mt7662u Chipset. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906770 Title: Kernel 5.4.0-56 Wi-Fi does not connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963203] [NEW] update-manager crashed with SIGSEGV in ffi_call_unix64()
Private bug reported: After running a partial upgrade, can't guess meta-package ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: update-manager 1:0.156.9 ProcVersionSignature: Ubuntu 3.2.0-19.31-generic 3.2.12 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Fri Mar 23 11:13:18 2012 ExecutablePath: /usr/bin/update-manager GsettingsChanges: InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/update-manager --dist-upgrade ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash TERM=unknown SegvReason: reading NULL VMA Signal: 11 SourcePackage: update-manager Title: update-manager crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: Upgraded to precise on 2012-03-13 (9 days ago) UserGroups: ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash dist-upgrade need-amd64-retrace precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/963203 Title: update-manager crashed with SIGSEGV in ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/963203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555388] Re: Update Package: BZFlag
Latest is 2.4.0 since 2011-08-06. Could we get another update package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/555388 Title: Update Package: BZFlag To manage notifications about this bug go to: https://bugs.launchpad.net/getdeb.net/+bug/555388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 112927] Re: Thread support not compiled in
I'm an upstream maintainer of XaoS. There is a known issue where user-defined formulas cause a crash if multiple threads are enabled. On the other hand, multiple threads work fine with the built-in formulas and deliver a nice speed boost on multi- core processors. XaoS only uses multiple threads if the user selects more than one thread via the command line via the -threads switch. The default is to use one thread even if thread support is compiled in, so I suppose it wouldn't hurt to enable it at compile time and give the users the option of using multiple threads if they aren't going to use user- defined formulas. The user defined formulas crash because the evaluation code is not re- entrant. I have asked the original author of the user-defined formulas to fix this but I don't think he's interested in maintaining the code. I have started looking into a fix but it will probably require a pretty major overhaul to the parser. Currently the parser is creating a stack- based notation for the formula, which it evaluates iteratively and with side-effects in a global data structure. It needs to be modified to parse the formula into an AST which is recursively evaluated without any side-effects. Reference: http://code.google.com/p/gnuxaos/issues/detail?id=31 ** Bug watch added: code.google.com/p/gnuxaos/issues #31 http://code.google.com/p/gnuxaos/issues/detail?id=31 -- Thread support not compiled in https://bugs.launchpad.net/bugs/112927 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224705] Re: Choosing hsv and hsv2 truecolor incoloring and outcoloring mode XaoS screen goes black.
This is now fixed in upstream the subversion repository. See upstream bug: http://code.google.com/p/gnuxaos/issues/detail?id=8. ** Bug watch added: code.google.com/p/gnuxaos/issues #8 http://code.google.com/p/gnuxaos/issues/detail?id=8 -- Choosing hsv and hsv2 truecolor incoloring and outcoloring mode XaoS screen goes black. https://bugs.launchpad.net/bugs/224705 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104178] Re: Magnatune plugin does not use OGG format
I just downloaded and tried Ubuntu GNU/Linux 8.04 live CD (32-bit, i386) and ran Rhythmbox on the belief that the Magnatune Rhythmbox plugin would play Magnatune's Ogg Vorbis files. The Magnatune plugin was already set up, so I clicked on it, let it download Magnatune's catalog and tried to play a track. Rhythmbox prompted me to find a suitable codec which means that Rhythmbox wasn't using the supplied pointers to Ogg Vorbis audio files Rhythmbox was trying to play MP3 audio files instead. Therefore I don't think this is a fixed issue for Ubuntu GNU/Linux. Perhaps Ubuntu GNU/Linux should make the Magnatune Rhythmbox plugin play Magnatune's Ogg Vorbis catalog by default, or stop distributing the current Magnatune Rhythmbox plugin until the upstream distributes a plugin that plays Ogg Vorbis by default. If this plugin is already fixed upstream, could Canonical package that version of this plugin and distribute it for Ubuntu users instead of the current plugin which encourages the user to get MP3 player software? It would be nice to see Rhythmbox play Magnatune out of the box without the need for the user to install software to which they might not have the applicable patent licenses. -- Magnatune plugin does not use OGG format https://bugs.launchpad.net/bugs/104178 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation - broken UTF support
** Also affects: xaos via http://sourceforge.net/support/tracker.php?aid=1188322 Importance: Unknown Status: Unknown -- Wrong characters codification in Xaos translation - broken UTF support https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation - broken UTF support
@Sergio Thank you for all your work on this! I have committed both the cat and the po file to the upstream CVS. They will be included in version 3.4 of XaoS along with the bug fix for the text. I expect to make a pre- release within the next week and the final version within the next month or so. I did find some small problems with your cat file. Several places, you had forgotten to include the ending double quote (), and I also had to convert the file from UTF-8 to Latin 1 encoding. Even though the bug fix automatically converts the strings returned by gettext, it still expects the catalogs to be in Latin 1 or 2 since that is what all the other catalogs are in. You can find the updated file at http://xaos.cvs.sourceforge.net/*checkout*/xaos/XaoS/catalogs/italiano.cat?revision=1.1. I confirmed that the tutorials successfully load and plays in Italian. -- Wrong characters codification in Xaos translation - broken UTF support https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation - broken UTF support
@Tormod Great! Thanks for your effort testing this. Did the patch make it in time to be included in Hardy? -- Wrong characters codification in Xaos translation - broken UTF support https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation.
If you are getting messages in English, it sounds like you are having a locale issue unrelated to the patch. Tutorials were always displayed correctly even without the patch, because they don't use gettext but instead have their own message catalog format. This catalog is read directly from the file so it is already in the correct encoding (Latin 1 or 2) before it is displayed on screen. Menus, dialogs, and other messages are localized using gettext, which always returns strings encoded in whatever encoding is specified by your locale, regardless of the original encoding. On modern systems, this is usually UTF-8. Since the xaos text engine doesn't handle UTF-8, it tries to interpret the strings it receives from gettext as Latin 1 or Latin 2, depending on the language, and that is where the garbled characters come from. The patch converts the text received from gettext back to Latin 1 or Latin 2 before passing them to the text engine. What is your LANG variable set to? The setting for LANG that worked for me is: export LANG=fr_FR.UTF-8 Please make sure that you use this setting exactly, since I don't know if LANG=fr will work or not. Also, after I installed support for the additional languages, I rebooted my system. I don't know if this is strictly necessary but you might want to give it a try. -- Wrong characters codification in Xaos translation. https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation.
In the catalogs directory, copy english.cat to e.g., italiano.cat. Read the instructions in the comments at the beginning of the file, then translate each entry from English to Italian. This file is used to translate the tutorials. Without it, all the tutorials will still be in English, even if your locale is set to Italian. -- Wrong characters codification in Xaos translation. https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation.
You might have to do make install before it will work. XaoS expects its locale files to be in /usr/share/locale. I will try it to test it myself if I get a chance tonight. -- Wrong characters codification in Xaos translation. https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation.
@Tormod I got my Ubuntu 7.10 VMWare image working again and I just tested the patch that you uploaded. It worked, but first I had to install the language support for all the languages I wanted to use via SystemAdministrationLanguage Support. After doing this and rebooting, I was able to set LANG to any of the languages supported by XaoS and the i18n text displayed correctly. Please give it a shot and let me know if it works for you. FYI, Hungarian or Czech are good languages to test with because they have lots of diacritical marks on the letters. French, German, and Spanish have them too, but you have to search around in the menus before you find a word that has them. Sorry about the original patch not compiling correctly. I had to recreate the changes on 3.2 and I didn't have a Linux box available to test it at the time. Thank you for fixing it and helping test. -- Wrong characters codification in Xaos translation. https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation.
This issue has been resolved in the upstream CVS and will be included in the upcoming 3.4 release. The problem is that XaoS's built-in text handling (the xprint function in grlib.c) only supports Latin-1 and Latin-2 encodings. On modern Linux systems (and Mac OS X), gettext returns strings in UTF-8. The solution is to convert the strings from UTF-8 back to Latin-1 or Latin-2 as appropriate before displaying them using XaoS's xprint function. The meat of the changes are in grlib.c, but also, every call to xprint had to be updated to pass in the proper encoding, which is stored in the uih-encoding field (an integer 1 or 2 indicating Latin-1 or Latin-2 or 0 indicating that the encoding should not be changed). For the help and tutorials, we pass in a 0 to prevent the text from being re-encoded. Tutorials pull strings directly from the appropriate catalog file instead of using gettext, so the text is already in the proper encoding. Help is not localized at all, so it also does not need to be re-encoded. You may be able to use this fix against the 3.2 version that is included in ubuntu. You can probably use grlib.c directly as I don't think it contains any other changes between 3.2 until now. However, you will need to hand patch the files that call the xprint function, since these files may contain other changes between 3.2 and now. I would encourage Ubuntu to upgrade the package to the latest version. In addition to this fix, 3.3 (and the upcoming 3.4) will contain numerous other fixes, as well as an extremely important new feature, the ability to render user-defined formulas. Debian has already moved to 3.3 in testing and unstable. I will let you know when 3.4 has been released (it may be a few more weeks yet). -- Wrong characters codification in Xaos translation. https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation.
P.S., please submit your Italian translation for inclusion in the upstream package. We would love to have it. Version 3.4 will require a bit more development before we are ready to impose a string freeze. There will be quite a few string changes between 3.2 and 3.4, so there will probably be additional strings that need to be translated for 3.4. -- Wrong characters codification in Xaos translation. https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation.
So you need a patch for this fix against the 3.2 sources with the ubuntu patches already applied? I don't know if i can get that to you by Thursday but I will try. I do not have a Linux environment set up right now since I use Mac OS X and my Ubuntu 7.10 VMWare image just got hosed. So even if I can produce the patch by Thursday, I won't be able to readily test it on Ubuntu. Regarding the po file, please submit it as an attachment to our patch tracker: http://sourceforge.net/tracker/?group_id=5771atid=305771. Also, to fully localize XaoS, you will also need to create a .cat file (in the catalogs directory). This is used to localize the tutorials. Please submit that along with the po file. -- Wrong characters codification in Xaos translation. https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation.
Here is the patch to fix the garbled text on systems using UTF-8. It should be applied against the 3.2 sources to which xaos_3.2-7ubuntu1.diff has already been applied. I have not had a chance to test it yet. ** Attachment added: xaos_3.2-i18nfix.diff http://launchpadlibrarian.net/13196716/xaos_3.2-i18nfix.diff -- Wrong characters codification in Xaos translation. https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation.
Here is the patch to fix the garbled text on systems using UTF-8. It should be applied against the 3.2 sources to which xaos_3.2-7ubuntu1.diff has already been applied. I have not had a chance to test it yet. ** Attachment added: xaos_3.2-i18nfix.diff http://launchpadlibrarian.net/13196717/xaos_3.2-i18nfix.diff -- Wrong characters codification in Xaos translation. https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 211710] Re: Wrong characters codification in Xaos translation.
This is a known issue with XaoS on modern Linux systems. See the following bug in our tracker: http://sourceforge.net/tracker/index.php?func=detailaid=1188322group_id=5771atid=105771 The problem is that XaoS's built-in text system can't handle UTF-8. It expects the text to be returned in Latin 1 or Latin 2, depending on the language, but Ubuntu and most other modern systems don't have these locales installed anymore. There is a workaround described in section 6 of the i18n README file: http://xaos.cvs.sourceforge.net/xaos/XaoS/src/i18n/README?revision=1.7view=markup Is adding support for the needed locales this something that could be addressed by the packager? I'm the Mac OS X maintainer, so I don't know a whole lot about debian packages. A possible fix might be to put some function call to convert the text from UTF-8 returned by gettext to Latin 1 or 2 as appropriate before passing it into the text handling routine, but I have not looked into this. Another possible fix (which would require a lot more work) is to replace XaoS's antiquated text system with the text drawing in a modern UI toolkit like gtk or qt. However, a prerequisite for this would be to write a new user interface for GTK or QT (easier than it sounds because of XaoS's portability framework, but still quite a bit of work). This is the approach I am taking for the Cocoa UI that I have written for Mac OS X. The menus and dialogs already handle UTF-8 correctly since they are native Mac OS X menus. However, the messages displayed on screen still go through XaoS's built-in text handling system and therefore don't show up correctly. The solution will be to replace calls to the built-in text handler with calls to the UI's text drawing functions. I'm not sure how much work that will be... possibly quite a bit. -- Wrong characters codification in Xaos translation. https://bugs.launchpad.net/bugs/211710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192882] Re: Xaos display problem with compiz
Can we move this HSV bug discussion to the XaoS Sourceforge tracker, please? https://sourceforge.net/tracker/index.php?func=detailaid=1917866group_id=5771atid=105771 I think that is appropriate since this affects more than just Ubuntu (or Linux, for that matter). If you want to open a new lanuchpad bug for HSV coloring and link to the XaoS tracker, that would be fine by me. -- Xaos display problem with compiz https://bugs.launchpad.net/bugs/192882 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192882] Re: Xaos display problem with compiz
I think this is a separate bug unrelated to the Beryl/Compiz transparency patch. The user who reported the HSV issue to us tested the following on Debian sid, and could not get HSV to work on any of them: 1) Unmodified 3.3 sources 2) 3.3 sources with the Beryl/Compiz transparency patch rolled back 3) 3.2 with the Beryl/Compiz transparency patch applied 4) Unmodified 3.2 sources This last one is the most surprising, but it surely confirms that nothing we changed in 3.3 is causing the problem. I tried HSV coloring with several versions that I had readily available to me. Here are the results: 1) Mac OS X 3.3 - hsv does NOT work 2) Mac OS X 3.2.2 - hsv does NOT work 3) Windows 3.2 - hsv DOES work 4) Windows 3.3 - hsv DOES work Most surprising here is the fact that HSV works on Windows 3.3. So again that suggests that nothing we changed in 3.3 inherently caused the problem. Also the fact that Mac 3.2.2 version does not work supports this conclusion. More likely there is some incompatibility between the X11 and Mac- specific code and the HSV coloring modes. 3.2.2 is the earliest version that is compatible with Mac OS X so I cannot test any further back than that. However, I would be interested to hear what you see when you try earlier versions of XaoS on Linux. However, we should probably move this discussion to a separate bug (or to the HSV bug on the sourceforge site that I linked earlier), since it does not appear to be related to Beryl/Compiz in any way. -- Xaos display problem with compiz https://bugs.launchpad.net/bugs/192882 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192882] Re: Xaos display problem with compiz
I am a co-maintainer of the upstream project. I normally work on the Mac OS X port, but I did apply some patches that Tormod submitted against the newly released 3.3. One of the patches we recently rolled into 3.3 was Tormod's patch for alpha transparency with Beryl and Compiz, and now we have a bug report that HSV TrueColor modes show all black. Is there any chance that you were using one of those modes when you took the screenshot? I am wondering if these could be related. See https://sourceforge.net/tracker/index.php?func=detailaid=1917866group_id=5771atid=105771 for more details. -- Xaos display problem with compiz https://bugs.launchpad.net/bugs/192882 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 164241] Re: add the echoaudio firmware to the alsa-firmware-loaders package.
Hello, I would like to second the request made by Bill Brown above. I have an Echo Audio Gina3G soundcard that is not being recognized by both Ubuntu 7.1 and Ubuntu Studio 7.1. The Echo Audio sound cards are popular in the semi-pro audio market (home recording, djs) and with people wanting high-quality sound output to home stereo systems. With the comprehensive GUI mixer echomixer I have had my Gina3G fully functional running Fedora with the Planet CCRMA audio packages. The absence of out-of-the-box recognition is preventing me, and likely others who are more musician than programmer, from using Ubuntu. Thanks, J.B. Wimbere -- add the echoaudio firmware to the alsa-firmware-loaders package. https://bugs.launchpad.net/bugs/164241 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/listinfo/ubuntu-bugs
[Bug 61476] Re: A radio choice with none of the options chosen?
** Attachment added: The aforementioned snapshot of my errant Power Management preference window. http://librarian.launchpad.net/4359499/Screenshot-Power%20Management%20Preferences.png -- A radio choice with none of the options chosen? https://launchpad.net/bugs/61476 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61476] A radio choice with none of the options chosen?
Public bug reported: Binary package hint: power-manager I'm sorry if I have picked the wrong package, but I hope I can include a screenshot which will make the issue I'm describing more clear. Perhaps identifying things by package name can be reconsidered--package names are almost entirely invisible to the common user. When I brought up the Power Management preferences I saw a radio button choice where none of the choices were made. This struck me as odd because I thought radio selections were to mean that one and only one of the choices was valid, so one of them had to be active at any particular time. Given that no power management icon is on my screen (no such icon in the notification area), I'm assuming the first option (Never display icon) is actually active. Considering that my desktop computer has no battery, I don't understand what the second option means and it should probably not be shown at all. ** Affects: power-manager (Ubuntu) Importance: Untriaged Status: Unconfirmed -- A radio choice with none of the options chosen? https://launchpad.net/bugs/61476 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61477] A save file prompt with no directory?
Public bug reported: While filing a bug about the power management preference panel, I found another bug in the save file prompt. I have no idea what package this prompt comes from. I'm running Ubuntu edgy, updated with the latest software as of the time/date stamp on this bug report. The attached picture tells the tale--the prompter shows no directory indicating where the file will be saved. It turns out this directory is my Desktop. ** Affects: Ubuntu Importance: Untriaged Status: Unconfirmed -- A save file prompt with no directory? https://launchpad.net/bugs/61477 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
