[Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
Vasya, it is not ASUS fault and they have nothing to fix here. This problem is a low priority bug in DRM/Intel and it could only be fixed on DRM/Intel/kernel side. ASUS has nothing to do with it, it is not a bug in their ACPI DSDT code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1348890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
Here is this bug reported upstream by me: https://bugzilla.kernel.org/show_bug.cgi?id=92391 It was closed as duplicate with a reference to this one: https://bugs.freedesktop.org/show_bug.cgi?id=81762 It is not a problem with device initialization, it is rather a problem with device driver not initializing some fields in device op.region with a values expected by ACPI code. There was an experimental kernel branch which is expected to fix this bug but I'm not certain what is current status on this. Looks like there is next to none activity in DRM/Intel bugzilla report #81762 so chances seem to be low that we would get a proper fix anytime soon. ** Bug watch added: Linux Kernel Bug Tracker #92391 http://bugzilla.kernel.org/show_bug.cgi?id=92391 ** Bug watch added: freedesktop.org Bugzilla #81762 https://bugs.freedesktop.org/show_bug.cgi?id=81762 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re[2]: [Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
In russian: Тег kernel-bug-exists-upstream предполагает, что этот же баг есть в трекере у поставщика компонента - в данном случае это ядро linux. То есть если тег проставлен - предполагается, что на kernel.org это баг есть и о нём разработчики ядра знают. Так что да. если на kernel.org баг не отрепорчен - надо бы его втуда отрепортить, иначе мало шансов, что баг в итоге починят. In english: If a report is marked with kernel-bug-exists-upstream tag it implies that the same bug had been reported to upstream vendor of the bugged component in question - it is linux kernel in this particular case. So yep, in case there is no bug report on kernel.org for this bug it would be great if you would report it there so the bug might got noticed by kernel developers and would be eventually fixed. Tue, 14 Oct 2014 09:41:29 - от Danila Beketov 1348...@bugs.launchpad.net: Да я не совсем понял что нужно сделать. Меня попросили воспроизвести багу на последней версии ядра из upstream Убунты. Баг присутствует. Теперь тоже самое зарегать на kernel.org? On Fri, Oct 10, 2014 at 8:45 PM, Alexey Loukianov 1348...@bugs.launchpad.net wrote: Danila, it seems that you had added tag kernel-bug-exists-upstream to this report but I can't find any direct link to a bug on kernel.org. Could you please post it here? Thanks in advance. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event Status in “linux” package in Ubuntu: Confirmed Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348890/+subscriptions -- Бекетов Данила -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event Status in “linux” package in Ubuntu: Confirmed Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348890/+subscriptions --- С уважением, Алексей Лукьянов System Engineer *nix Specialist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
Danila, it seems that you had added tag kernel-bug-exists-upstream to this report but I can't find any direct link to a bug on kernel.org. Could you please post it here? Thanks in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1348890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 636278]
Posting here to help other people like me who had been searching for the correct bug report about yet another ptrace breakage that happen in Ubuntu 12.04+: it is bug #30410. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/636278 Title: ptrace and pokerstars To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/636278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978678]
I've got a report that this one also affects Diablo III. To be more precise - it fails to log in into Battle.Net with error 3007. Disabling ptrace_scope reported to fix the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/978678 Title: Starcraft II crashes before login in 12.04 (regression from 11.10) To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/978678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371897]
(In reply to comment #347) Apparently Wine has again rejected a winepulse patch after Maarten Lankhorst put a bunch of work into improving it in his wine/multimedia.git repo (http://repo.or.cz/w/wine/multimedia.git). Would you please provide some ground for your statement about rejection of the patch? As far as I can see from wine-devel mailing list log, Maarten had been - and most probably is still - working on this patch for quite a long time. Last time he tried to send it to wine-patches, which was try 12, had only been ten days ago. The patch is listed at http://source.winehq.org/patches/ page and is at New state - which is not Rejected obviously. AFAIRK Alexandre was out on vacation during that period of time, and that is a viable reason why hadn't been any conclusion made about this patch. Another thing to note is that there were no feedback about try 12 version of patch on the wine-devel list. I wouldn't be surprised if this patch would be ignored unless there would be some positive feedback received from other sound subsystem developers (Andrew, Joerg). Needless to say that accepting a large chunk of the code at once into Wine tree isn't a thing that commonly happens. My expectations are that - likely - this patch would finally find its way into Wine, but it won't happen right here and now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371897]
(In reply to comment #349) .. and it was certainly Maarten who recently added the following comment to his v16 version of the winepulse patch: Argh, bad luck then :-(. Hope it isn't a final resolution for this path, as PA, being a plague of a modern linux desktop, seems to be one of the things that Wine would have to cope with. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371897]
(In reply to comment #341) I am (unluckly) well aware how buggy PA is. Point is, just look at the comments of this bug report. Look at the answers we've been given ... ... Really, I appreciate the dev's work on such a big and complicated project as Wine is, but some news about this old (yet persistent) issue could help Sorry for delaying my answer for such a long time, but I have been having some medical issues last months preventing me from using computers. Fact is that I'm not a Wine developer, so I can't provide you with an official position on point. Still, I've been monitoring Wine's Bugzilla and wine-development list for a pretty long period of time so I can share with you my conclusions on the topic I had made through observations. Here they are: a) We all know a sad fact that not all people officially working on bugzilla maintenance are always polite and unbiased. On the contrary, most of the times you should expect a bit of rudeness and/or tension trying to get your bug not CLOSED WONTFIX, a patch accepted into the Wine tree, e.t.c. Personally I don't like this much but it is the way it is and it works more or less, keeping in mind the amount of bug reports devs get posted with every day. b) Audio subsystem rewrite we've been originally told about had been done, but not in the way it had been originally thought of. AFAIRK, initial intent was to get rid of all the old drivers, implement the only one instead, thus decreasing the maintenance burden from having to support N drivers into having to support 1 driver. It had been thought that OpenAL would serve as a viable backend, but in the end it turned out not to be a case. Instead Wine's audio subsystem had been rewriten so sound render path went through mmdevapi interface, and there had been three mmdevapi driver backends implemented for it: ALSA, OSS and CoreAudio. As far as I had read on bugzilla, mmdevapi maintainers are not against having separate PA mmdev driver in general, but as their time is limited they want to fix most of the outstanding show-stopper bugs in existing mmdevapi drivers first, and only then considering something like separate PA mmdevapi driver. c) So, taking into account what I had written in (b) - current short term support policy for PA seems to be Wine should work decently enough with alsa-pulse plugin, in case you have fresh-enough version of libalsa, alsa-plugins and PA installed, and possible long-term policy might include something like separate PA driver which would provide some additional benefits when used over ALSA-alsa-pulse render patch. Honestly, I can handle random crashes, loss of data, occasional lag, graphical issues (I remember the old times when most games wouldn't even start with Wine), but they all get fixed sooner or later... This issue, on the other hand, has been carried around for quite a while.. Well, it's not an in-fixable issue, actually. With older Wine versions you may wish to stick with out-of-tree patch that adds PA driver to the now obsolete winmm drivers architecture. If you want to use latest-n-greatest Wine releases (1.4+) - be sure to also use latest-n-greatest PA and alsa-plugins releases, it would fix most of the PA vs. Wine problems for you. You know, Wine devs are not magicians. Audio subsystem rewrite is a huge thing and it had mostly been done by three people out there (Andrew, Joerg, Maarten, maybe someone else I had forgot about), so it's not a big surprise it took a big amount of time, especially knowing the tight requirements AJ puts on the code that is accepted for inclusion. Dev's done a great job, sound subsystem works almost perfectly nowdays, and it is even capable of intelligently workaround some of the bugs of alsa- plugins that had been there for years. Looking at the quality curve Wine's audio subsystem had been gaining recently - I won't be surprised if some time later this year (say, this summer) there won't be any problems with using Wine vs. PA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371897]
(In reply to comment #339) The only answers you'll get will be either whine at your distro's mainteiners and make them update alsa-plugins to the latest git (and it still won't solve this problem) ... Fire up bugs please in case you've got problem after compiling and installing latest alsa-plugins from git. Whining is a cool thing but the only way to get bugs fixed is to fire up bugs and do anything you can to sort them out. or remove pulsaudio and go back to alsa (because who needs pulse? On a totally unrelated topic, switch to Netscape, no need for new fancy browsers or new web standards)... You don't know what you're talking about. PA is a buggy thing, alsa pulse plugin is also a buggy thing, and even default ALSA's dmix+plug setup is a buggy thing. Wanna details? Monitor wine-bugs list for messages by Andrew Eikum and Jörg Höhle - they are working really hard to workaround all the bugs in ALSA+dmix+PA+Wine that had been reported so far. So yeah, never thought I'd say this, but if you need audio output you should really consider a dual boot system with Linux and Windows, Wine simply won't work as for now. PROVE ME WRONG AND FIXE AUDIO ISSUES WITH PULSE PLEASE. In case you wanna be 100% sure about compatibility - dual booting is a good choice. If you can handle some problems - Wine isn't a bag choice either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
25.10.2011 18:38, Chow Loong Jin wrote: But it's fixed in Ubuntu Oneiric. And what does it change with regards to Linux Mint 9 Isadora users? Who cares if this bug was fixed in some fresh-n-shiny Ubuntu and/or Mint release while it is still not fixed in so-called Long Term Support version of Linux Mint? And - to be honest - I still occasionally hit this bug on Ubuntu 10.04 LTS despite the fact that it had been marked as fixed for Ubuntu months ago. Released fix had only changed the frequency this bug happens: before fix I've been hitting this bug every time I force my system to do fsck on next boot. After the fix I hit this bug about once in 4-5 fsck-enabled reboots. Better than nothing but still smells like crap. -- Best regards, Alexey Loukianov mailto:mooro...@mail.ru System Engineer,Mob.:+7(926)218-1320 *nix Specialist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/571707 Title: fsck progress stalls at boot, plymouthd/mountall eats CPU To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/571707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371897]
(In reply to comment #335) FWIW, feedback on the forum is that this is fixed. Which one of this is supposed to be fixed? If the minimum version of alsa-plugins needed is 1.0.24 (comment 331)... Read my comment once again: absolute minimum is 1.0.24 as with earlier versions you wouldn't get any sound at all from Wine+ALSA+PA combo (or it would hang very quickly, see bugs #28282 and #28066). Typical error message for too old alsa-plugins version is something like: ALSA lib pcm_pulse.c:1008:(_snd_pcm_pulse_open) Unknown field handle_underrun Since the release of the alsa-plugins v.1.0.24 there were a lot of other PA-related fixes commited into git so one wishing to get best of it have to download, compile and install git HEAD version of alsa-plugins. Actually it should be done by distro package maintainers as alsa-plugins release cycle seems to be too slow to deliver fixes timely to the users who need them. (In reply to comment #334) I thought that PulseAudio is in charge of everything by default, and when an app (like Wine) thinks it's using ALSA in this setup, it's actually using a wrapper provided by PulseAudio that translates ALSA calls to PulseAudio calls? It's actually a bit mixed. Apps are expected to use ALSA through a thing called alsalib (a.k.a. libalsa). This thing supports a concept of plugins (which are called - you guess - alsa plugins). Good examples of plugin are dmix and plug which are well-known to anyone who had ever been hand-configuring ALSA using asoundrc. Another example of alsa- plugin is a pulse plugin which is also provided by ALSA dev-team. This plugin acts as forward mechanism towards PA. Most of the problems with PA usually were caused by bugs in PA itself. On the other hands some bugs were caused by deficiency in pulse alsa-plugin. Yeah, I know that The Big Picture of the Sound Subsystem is a bit complicated in ALSA+PA enabled world :-). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371897]
(In reply to comment #330) Short question: Is PA 1.0 a hard requirement for getting stable sound under wine/alsa/PA combo? Quick answer: my tests shows that the hard requirement is to have recent enough alsa-plugins (at least v.1.0.24). Actually there had been a lot of PA-related fixes to alsa-plugins since 1.0.24 (last one landed to alsa-plugins git 12 days ago) and tests I tried at home showed great improvements in overall sound stability under Wine+PA+ALSA in case I build alsa-plugins from current git HEAD. As for PA version - everything around versions 0.9.x seemed to smell like public alpha-test of crappy and extremely buggy software. Almost every version I had tested so far had a lot of bugs, including ones unrelated to interoperability with Wine (latency issues, incorrect manipulations with soundcard hw mixer, rattling, sound distortions, incompatibilities with other apps, e.t.c.). Latest PA version I had tested so far was 0.9.23 and I can state that it might be considered almost bug-free for general use in case coupled with latest ALSA and alsa-plugins from current git. Don't know it they had fixed or broke something in 1.0 release and I personally wouldn't be happy to have almost untested piece of software to be included in F16 at a last minute. It'd be better to post in into rawhide or into testing and have volunteers test it before letting it into public. This discussion is an offtop here so I shut up :-). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371897]
(In reply to comment #327) does mean that those stuck on other Ubuntu versions (or non-Ubuntu distros using older PulseAudio versions) may still have issues... Truth is that those stuck on older version of buggy software would continue to hit those old bugs in that software. For example multichannel speakers configuration is a total mess under 10.04 LTS PulseAudio. The only way to fix it keeping PA installed is to manually build latest dev snapshot of PA - Ubuntu maintainers seem to have no interest in backporting fixes onto long term support stable version. They are content with the fixed for this bug landed into latest regular Ubuntu version. And so on. Returning back to Wine, it shouldn't took long for you to look into wine git logs and conclude that there were some compatibility patches for proper interaction with PA's alsa-plugin. You should still use the latest PA and alsa-plugins with a lot of bugfixes though to have mentioned patches work. Thus, answering to your initial question: there were some PA compatibility fixes addressed during Wine's sound subsystem rewrite but you should always stick to latest versions of all components of modern linux desktop sound subsystem to have most old bug fixed (and new introduced). P.S. Me personally would prefer to have separate mmdevapi backend for PulseAudio as it would be more backwards-compatible than sticking with PA's alsa-plugin emu. Still the final decision is to be made by Wine's devteam. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371897]
Good day 2ALL, As far as I know Andrew Eikum had recently finished dsound re- implementation over mmdevapi. So looks like it's time to request for status update on this bug. Stefan, Andrew, what are the plans for the future regarding Wine interactions with PulseAudio? Would it be separate mmdevapi backend like one that was mostly working from Maarten Lankhorst's git or should end-user stick with mmdevapi alsa backend and rely on pulseaudio alsa-plugin to do the job? Thanks in advance for clarifications. P.S. And it may be just the right time to finally close this bug? Wine's audio subsystem had undergone total rework and it might be reasonable to file a new bug about mmdevapi should have pulseaudio backend in case that is really needed to get sound properly working in PA-enabled environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371897]
(In reply to comment #318) ... I have read many times that after the change of sound architecture in wine the PA driver will be added. Em, I might be wrong, but I can't recall the claims that the PA driver would be added after sound system rewrite. AFAIRK, the claims were that after the sound subsystem rewrite Wine would use OpenAL for the sound output, and it would be OpenAL side to support actual output backend, should it be hw-accelerated AL drivers, openal-soft via ALSA or openal- soft PulseAudio backend. Still, I might be wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 371897]
(In reply to comment #321) OpenAL turned out to be no good for our purposes, so we went back to the model of writing multiple backends in Wine itself... Stefan, thanks for clarification and the status update. It's a very good news to hear that PA support would eventually find its way into Wine, although I still prefer not to use PA at all on my workstation - it's still a lot of pain jumping over the show-stopping bugs here and there (for ex., multiple sound distortion bug in SSE/MMX optimized volume scaler when using multichannel output setups). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/371897 Title: Occasional sound drops in Wine via PulseAudio To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/371897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 445849] Re: Highpitched rattling like sound with 5.1 surround configuration
Ok, well, I'm mostly from LFS/Gentoo/Fedora side of the table, but this month I'm working off-site and has to use external HDD with Linux Mint 9 (Ubuntu 10.04 LTS based) Live CD copied into as the main working system. Speakers setup here is an ordinary 5.1 cheap set from Defender connected to the MB's build-in HDA codec. Having problems with PulseAudio had become such a typical thing so I hadn't been surprised to run into high- pith sound distortions I get as soon as set soundcard to work with Analog Out 5.1 profile. For a first few weeks I hadn't had enough time to investigate so the solution was to simply set autospawn = no into /etc/pulse/client.conf, 'echo pcm.!default plug:dmix ~/.asoundrc' and reconfigure all relevant stuff to use alsa instead of pulse (gstreamer-properties, mplayer, vlc, e.t.c.). Today I finally had found some time to hunt down this bug. Quick google search lead me into this bug report, and reading a bunch of comments made me believe that the problem is related with incorrect PulseAudio SIMD optimizations and that it might be fixed in ubuntu-proposed and/or in the diwic/pulseaudio-testing ppa. Unfortunately both ubuntu-testing and diwic ppa hadn't been able to fix the problem. As for pusle* and libpulse* packages from lucid-testing - nothing seems to be changed after installing them. The problems with 5.1 distorted sound remain the same. Diwic's pulseaudio-testing ppa seems to be maverik-only, but the diwic/ppa seems to had fresh pulseaudio stuff. It is broken the same was as the packages in lucid-proposed though. Trying to investigate a bit mode I had turned off the PA auto spawning again, killalled pulseaudio and run PULSE_NO_SIMD=1 pulseaudio in the terminal. Having SIMD optimizations disabled this way fixes the problem: no more sound distortions caused by smart and cool daemon every desktop user should use PulseAudio. For now I'm going to export PULSE_NO_SIMD=1 system wide and maybe wait another year till this thing would be finally fixed in so-called LTS release. I'm quite disappointed in LTS support policy, really. This bug had been known for ages, and releasing such a simple thing as a workaround using aforementioned environment variable should had taken no longer than about a week. After making suffering people happy by applying workaround it would be reasonable to implement and test the real fix (for ex., rewrite SIMD assembly optimizations) and then finally release a patched version that does it right. Looks like Ubuntu's (and thus derivate distros) support policy is totally the opposite, leaving people suffer from the bug and hunting around for workarounds themselves (like switching into using Major Market Share OS or following one of the numerous FAQ about how to get the f***ing rid of this sh*tty PA on Ubuntu/Mint/Whatever). *sadface smile* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/445849 Title: Highpitched rattling like sound with 5.1 surround configuration To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/445849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 445849] Re: Highpitched rattling like sound with 5.1 surround configuration
Upd: Sad so report, but the PULSE_NO_SIMD=1 fixed only one part of the problem: the high frequency distortion. What had left is the strange volume pulsation over the channels. The most close match I can imagine to describe the problem is like someone is sitting at the mixer control and constantly moves the channel volume fader up and down in cycles. Or spins balance potentiometer forward-and-backwards. Perceived audio picture is mad and no-no for normal use. Have to revert back info disabling PA system wide. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/445849 Title: Highpitched rattling like sound with 5.1 surround configuration To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/445849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 668933] Re: autofs5 may fail if map contains utf8 characters
Well, generally speaking, yes, I can, but it would take a long time as I'm not using Ubuntu and its derived distros like Linux Mint at home or on any server I administer. Besides that I'm not sure that it should be patched into distro package exactly as I had posted here as the solution above was quick-n-dirty hack I had made in 5 minutes while being helping one of my customers to resolve the problems they been having with autofs5 + samba. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/668933 Title: autofs5 may fail if map contains utf8 characters -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 668933] Re: autofs5 may fail if map contains utf8 characters
Well, generally speaking, yes, I can, but it would take a long time as I'm not using Ubuntu and its derived distros like Linux Mint at home or on any server I administer. Besides that I'm not sure that it should be patched into distro package exactly as I had posted here as the solution above was quick-n-dirty hack I had made in 5 minutes while being helping one of my customers to resolve the problems they been having with autofs5 + samba. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/668933 Title: autofs5 may fail if map contains utf8 characters -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
16.11.2010 00:25, ingo wrote: The logical way to solve this issues/bugs would be to purge plymouth and set up a good functional system. Correct me if I'm wrong but it is perfectly possible to get rid of plymouth in initramfs and following boot process by simply not installing plymouth themes packages. Yes, it might require to delete metapackages like mint-meta-*, but I don't see much trouble in having them uninstalled anyway because the default set of packages that Mint tends to install is far from minimal set required to get a slim linux installation perfectly fitting the normal office workstation requirements. -- Best regards, Alexey Loukianov mailto:mooro...@mail.ru System Engineer,Mob.:+7(926)218-1320 *nix Specialist -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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
Re: [Bug 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
14.11.2010 19:59, Richard Postlewait wrote: It's fixed in Mint 10. Awesome! Then why the hell is this bug not fixed in latest LTS release? Regular one-year support releases are just a toys for home linux users while corporate one tend to use LTS releases for production use. And the fact that the major bug in LTS release wasn't fixed for months and when a new toy release comes out it happens that the bug is fixed in it while still being present in LTS release gives a very good reason to reconsider using something like CentOS/RHEL instead of Ubuntu/Mint LTS in production environment. Will take this in account in the future consulting my clients. -- Best regards, Alexey Loukianov mailto:mooro...@mail.ru System Engineer,Mob.:+7(926)218-1320 *nix Specialist -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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
Re: [Bug 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
15.11.2010 00:11, Chow Loong Jin wrote: Status in “mountall” source package in Lucid: Fix Released Again, Get The Facts™. I don't care what Mint LTS does, but Ubuntu LTS has it fixed, so please don't confuse the two again. Thanks for pointing out on this. So, what is the _real_ current status for this bug? I know how does it behave in Linux Mint 9 LTS (bug is still there). But what about Ubuntu 10.04 LTS? I've seen reports here that it is still not fixed too (most recent was by Richard Postlewait). So whom too believe? P.S. Needless to say that an argument that it took a way to long to fix it in Ubuntu (in case it is really fixed) still counts. And another thing to note: Get The Facts™, this bug is not about Ubuntu only. So I don't care if you care about what Mint LTS does - this bug applies to Mint LTS so all people here blaming about have got all rights and reasons to do so. -- Best regards, Alexey Loukianov mailto:mooro...@mail.ru System Engineer,Mob.:+7(926)218-1320 *nix Specialist -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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
Re: [Bug 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
15.11.2010 06:14, Chow Loong Jin wrote: 10 days is too long? Really? If it was really fixed in that 10 days and all people reporting here blaming Ubuntu are in reality just hadn't installed fresh updates or are using Mint instead then it was fast enough to call it good level of support. If not - it's a shame for Ubuntu. And it is certainly a shame for Mint that this bug is still unfixed. Then you can use this as basis to report about Mint's failures to your clients, but please keep in mind that Ubuntu is not Mint. It is certainly not. As for clients - unfortunately they prefer working workstations instead of reports about Mint's failures. About half of linux installations in production environment I've done last year were based on Mint LTS (rest were CentOS 5 based). Looking at the history of this bug I would reconsider to use Ubuntu instead of Mint in a near future, probably switching to the CentOS 6 as soon as it would be released. -- Best regards, Alexey Loukianov mailto:mooro...@mail.ru System Engineer,Mob.:+7(926)218-1320 *nix Specialist -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
Just got a report from my clients using Linux Mint 9. Today three of the workstations stalled at boot displaying plymouth animation screen and doing nothing (this is roughly what the client complaint was). Knowing about this bug I suggested them to press the C key on the keyboard. Shortly after the press all stalled workstations continued to boot normally. So, looks like the bug is still here and awaits to be fixed. -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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 668933] [NEW] autofs5 may fail if map contains utf8 characters
Public bug reported:
Binary package hint: autofs5
This bug is not in autofs itself, but instead is in smbclient.
Surely a separate bug report should be fired against smbclient but this bug may
be relatively easy workarounded in autofs5 auto.smb/auto.cifs maps.
Problem with smbclient may be easily demonstrated by examining the
following output:
r...@linuxws03:/etc# LANG=en+US.UTF-8 smbclient -N -gL linuxws03
Domain=[WG] OS=[Unix] Server=[Samba 3.4.7]
Disk|print$|Printer Drivers
IPC|IPC$|IPC Service (linuxws03 server (Samba, Ubuntu))
Disk|документы|
Disk|documents|
Domain=[WG] OS=[Unix] Server=[Samba 3.4.7]
Server|WGOFFICE|Office Linux Server (Samba 3.0.9-1.3E.16)
Server|LINUXWS03|linuxws03 server (Samba, Ubuntu)
Workgroup|WG|WGOFFICE
r...@linuxws03:/etc# LANG=C smbclient -N -gL linuxws03
Domain=[WG] OS=[Unix] Server=[Samba 3.4.7]
Disk|print$|Printer Drivers
IPC|IPC$|IPC Service (linuxws03 server (Samba, Ubuntu))
Disk|Disk|documents|
Domain=[WG] OS=[Unix] Server=[Samba 3.4.7]
Server|WGOFFICE|Office Linux Server (Samba 3.0.9-1.3E.16)
Server|LINUXWS03|linuxws03 server (Samba, Ubuntu)
Workgroup|WG|WGOFFICE
As you can see, the share named документы (this is russian word
meaning documents) gets lost when smbclient is being executed with C
locale resulting in totally incorrect output Disk|Disk|documents| - in
fact this should be two lines, one for Disk|документы| somehow mangled
to be ASCII-friendly, and another one for Disk|documents|. Yes, this
is a bug in smbclient that should be reported at a separate bug report.
To workaround this bug one may always use UFT-8 locale when running
smbclient and optionally converting the output using something like
iconv -f utf8 -t ascii -c | grep -v 'Disk||' .
My approach was for to modify auto.smb/auto.cifs by adding 'export
LANG=en_US.UTF-8' to the top of the file in order to fetch correct
shares list. Then some modifications should be done to the awk script
parsing the output:
$SMBCLIENT $smbopts -gL $key 2/dev/null| awk -v key=$key -v
opts=$mountopts -F'|' -- '
BEGIN { ORS=; first=1; }
/Disk/ {
if (first) {
print opts
first=0
}
gsub(/ /, \\ , $2)
sub(/\$/, \\$, $2)
print \\\n\t \/ $2 \ \:// key / $2 \
}
END {
if (!first)
print \n
else
exit 1
}
'
This would allow to mount shares with utf-8 names, including ones that
contain space characters in their names.
** Affects: autofs5 (Ubuntu)
Importance: Undecided
Status: New
** Tags: auto.cifs auto.smb autofs autofs5 smbclient utf8
--
autofs5 may fail if map contains utf8 characters
https://bugs.launchpad.net/bugs/668933
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 668933] [NEW] autofs5 may fail if map contains utf8 characters
Public bug reported:
Binary package hint: autofs5
This bug is not in autofs itself, but instead is in smbclient.
Surely a separate bug report should be fired against smbclient but this bug may
be relatively easy workarounded in autofs5 auto.smb/auto.cifs maps.
Problem with smbclient may be easily demonstrated by examining the
following output:
r...@linuxws03:/etc# LANG=en+US.UTF-8 smbclient -N -gL linuxws03
Domain=[WG] OS=[Unix] Server=[Samba 3.4.7]
Disk|print$|Printer Drivers
IPC|IPC$|IPC Service (linuxws03 server (Samba, Ubuntu))
Disk|документы|
Disk|documents|
Domain=[WG] OS=[Unix] Server=[Samba 3.4.7]
Server|WGOFFICE|Office Linux Server (Samba 3.0.9-1.3E.16)
Server|LINUXWS03|linuxws03 server (Samba, Ubuntu)
Workgroup|WG|WGOFFICE
r...@linuxws03:/etc# LANG=C smbclient -N -gL linuxws03
Domain=[WG] OS=[Unix] Server=[Samba 3.4.7]
Disk|print$|Printer Drivers
IPC|IPC$|IPC Service (linuxws03 server (Samba, Ubuntu))
Disk|Disk|documents|
Domain=[WG] OS=[Unix] Server=[Samba 3.4.7]
Server|WGOFFICE|Office Linux Server (Samba 3.0.9-1.3E.16)
Server|LINUXWS03|linuxws03 server (Samba, Ubuntu)
Workgroup|WG|WGOFFICE
As you can see, the share named документы (this is russian word
meaning documents) gets lost when smbclient is being executed with C
locale resulting in totally incorrect output Disk|Disk|documents| - in
fact this should be two lines, one for Disk|документы| somehow mangled
to be ASCII-friendly, and another one for Disk|documents|. Yes, this
is a bug in smbclient that should be reported at a separate bug report.
To workaround this bug one may always use UFT-8 locale when running
smbclient and optionally converting the output using something like
iconv -f utf8 -t ascii -c | grep -v 'Disk||' .
My approach was for to modify auto.smb/auto.cifs by adding 'export
LANG=en_US.UTF-8' to the top of the file in order to fetch correct
shares list. Then some modifications should be done to the awk script
parsing the output:
$SMBCLIENT $smbopts -gL $key 2/dev/null| awk -v key=$key -v
opts=$mountopts -F'|' -- '
BEGIN { ORS=; first=1; }
/Disk/ {
if (first) {
print opts
first=0
}
gsub(/ /, \\ , $2)
sub(/\$/, \\$, $2)
print \\\n\t \/ $2 \ \:// key / $2 \
}
END {
if (!first)
print \n
else
exit 1
}
'
This would allow to mount shares with utf-8 names, including ones that
contain space characters in their names.
** Affects: autofs5 (Ubuntu)
Importance: Undecided
Status: New
** Tags: auto.cifs auto.smb autofs autofs5 smbclient utf8
--
autofs5 may fail if map contains utf8 characters
https://bugs.launchpad.net/bugs/668933
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 489011] Re: ACPI keyboard events for backlight brightness up and down gone when using KMS on LG LGR405-G.CP22R1 notebook (Intel GMA X1300)
Unfortunately I can't test this as the notebook in question is had been lost. :-( -- ACPI keyboard events for backlight brightness up and down gone when using KMS on LG LGR405-G.CP22R1 notebook (Intel GMA X1300) https://bugs.launchpad.net/bugs/489011 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 467000] Re: insserv doesn't work with upstart
Thanks for patch, working brilliant, but only in case insserv is recent- enough. Users of releases prior to 10.04 should manually upgrade insserv to the package version 1.12.0-14. It is harmless to use binary deb compiled for 10.04 in 9.10 (that's what I did with Mint 8 installation), hadn't had a chance to test it with earlier Ubuntu releases. Nevertheless it is always possible to compile and install package from the source deb package in case there would some dependency problems on earlier Ubuntu (and derivates) releases. -- insserv doesn't work with upstart https://bugs.launchpad.net/bugs/467000 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 379761] Re: MASTER - FF 3.5 font hinting does not honour gnome-settings
Your proposal is good, but it needs upstream fix to firefox-3.5 to allow the behaviour to be controlled by a plugin / component. And keep in mind, that I hadn't done any extensive research concerning firefox-3.5 behavior comparing with firefox-3.0, so my proposals about the core of the bug might be wrong. -- MASTER - FF 3.5 font hinting does not honour gnome-settings https://bugs.launchpad.net/bugs/379761 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 379761] Re: MASTER - FF 3.5 font hinting does not honour gnome-settings
Well, the truth as always lies somewhere between. In fact font hinting may be set on per-application basis using Xft X resources. So any program you start up ends up with thsis Xft resources set up, no matter are the settings for font hinting set in .font.conf, in gconf or in .Xdefaults/.Xresources. The method of setting this up is up to implementator. KDE's way is to use .font.conf settings as the source for defaults. Gnome's way is to store this in gconf and commit them to X on the system startup/settings change program initialization/ This gets done by gnome-settings-daemon. Firefox uses GTK+ as it's rendering backend on linux. But firefox by itself isn't a Gnome application - the only thing (well, almost) that is used from Gnome is widget engine and file chooser dialog. It is perfectly normal for firefox to be set up on a system without gnome- settings-daemon installed/running, and in such cases GTK+ appearence is contolled by .gtkrc files instead of gconfd/gnome-settings-daemon. And here we come to a problem/bug described in this ticket: firefox-3.0 font hinting Xft X resources were controlled by gnome-settings-daemon, while firefox-3.5 don't. My proposal is that firefox-3.5 controls this settings by itself fetching defaults from .font.conf, and simply ignores gconf-settings-daemon's attemps to change them. It this proposal is right, then it shoud be fixed by upstream (mozilla.org), either by reverting firefox behaviour to the 3.0's state, or by adding special item to about:config which will allow to control whether shoud firefox read .fonts.conf and use it or not. -- MASTER - FF 3.5 font hinting does not honour gnome-settings https://bugs.launchpad.net/bugs/379761 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 390975] Re: fonts problem if kde+gnome
Have got the same problem. But it is incorrect to say that QT don't use subpixel rendering - in fact looks like that after installing KDE systemsettings and kdebase-workspace-bin fonts that are used by the firefox are controlled by KDE system settings, including KDE's ability to do subpixel rendering if properly configured for it. Affected parts of firefox include menu bars, popup menu, bookmarks toolbar and tabs selector, meanwhile page rendered and input boxes still use fonts from gnome-settings. -- fonts problem if kde+gnome https://bugs.launchpad.net/bugs/390975 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 390975] Re: fonts problem if kde+gnome
*** This bug is a duplicate of bug 379761 *** https://bugs.launchpad.net/bugs/379761 Looks like this is the duplicate of #379761. The problem is that firefox-3.5 uses ~/.fonts.conf instead of gconfd method to get fonts hinting settings to use. Figured it by changing fonts in KDE system settings one by one from sans to serif typeface and seeing no changes in FireFox. Meanwhile changing fonts hinting settings in KDE changed the FireFox appearence. After bringing KDE's settings for hinting in sync with gnome's firefox became more-or-less the same as it was before installing systemsettings and kdebase-workspace-bin. ** This bug has been marked a duplicate of bug 379761 MASTER - FF 3.5 font hinting does not honour gnome-settings -- fonts problem if kde+gnome https://bugs.launchpad.net/bugs/390975 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 363666] Re: Firefox font size is not adjusting to Gnome font size
*** This bug is a duplicate of bug 379761 ***
https://bugs.launchpad.net/bugs/379761
Do you use any firefox themes? If so - themes can force firefox to use
different fonts and sizes than the one you set in gnome-appearance-properties
(for ex. MacOSX theme does it).
If this is the case, you may either try to switch back to the default firefox
theme or try to tweak your firefox profile using ~/.mozzila/firefox/your
profile name/chrome/userChrome.css file:
/*
* Edit this file and copy it as userChrome.css into your
* profile-directory/chrome/
*/
/*
* Do not remove the @namespace line -- it's required for correct functioning
*/
@namespace
url(http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul;); /* set
default namespace to XUL */
menu, menuitem {
font-size: 8pt !important;
font-family: Sans !important;
}
--
Firefox font size is not adjusting to Gnome font size
https://bugs.launchpad.net/bugs/363666
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 489011] [NEW] ACPI keyboard events for backlight brightness up and down gone when using KMS on LG LGR405-G.CP22R1 notebook (Intel GMA X1300)
Public bug reported: Ubuntu 9.10, latest updates as of 27/11/2009. # uname -r 2.6.31-15-generic Systems affected: bug showed up after upgrade from 8.10 to 9.10. After normal bootup Fn+Home/Fn+End keycombos (brightness up/down) are ignored and nothing happens. acpi_listen shows no events for this keypresses, xev and getkeycodes also give nothing. As this keys were working good on 8.10 the first thing to try was to boot from 8.10 livecd and try to monitor ACPI/xev/getkeycodes there. Experiment showed that this keys were generating acpi events on 8.10, and it is obvious that they got lost somehow in 9.10. Most probable cause for this to happen was the KMS introduced in 9.10, so I tried to add nomodeset kernel parameter to the grub configs. After booting up keys started to work like a charm (there's a problem with them anyhow that the brightness level happen to change in a huge and unpredictable steps, and sometimes it stucks with a brightness set not to the maximum available level no matter how much times I press Fn+Home combo; setting brightness to maximum using the gnome power manager LCD brightness panel applet works as it should). The only thing affected when the KMS is active are ACPI events for brightness change keycombos, while brightness control works fine using the applet I had mentioned earlier. ** Affects: ubuntu Importance: Undecided Status: New -- ACPI keyboard events for backlight brightness up and down gone when using KMS on LG LGR405-G.CP22R1 notebook (Intel GMA X1300) https://bugs.launchpad.net/bugs/489011 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
