[Bug 1765058] Re: Regression: 046d:08da Logitech, Inc. QuickCam Messanger not detected in Bionic
Hi, since COVID-19 forced everyone to dig up old webcams, I thought I'd share my "universal" workaround (sorry it's a clunky one): Step 1 (one time): sudo apt install v4l2loopback-utils Step 2 (redo after reboot): sudo modprobe v4l2loopback devices=1 exclusive_caps=1 Step 3 (before starting a video call): ffmpeg -vsync 2 -f v4l2 -i /dev/video0 -pix_fmt yuv420p -f v4l2 /dev/video1 Notes: * In the above Step 3, /dev/video0 is the "problematic" webcam and /dev/video1 the newly created loopback device. You can check which is which with 'v4l2-ctl --list-devices' (after installing v4l2-ctl with 'sudo apt install v4l-utils') * I recommend letting ffmpeg run in an open terminal during the video call, and stopping it with CTRL-C when finished (so that the webcam can power down and the CPU is not unnecessarily loaded) * What all this does: simply spoken, the problem is that some old webcams expose nonstandard parameters/controls to the software, and not all programs can deal with that. This solution makes a "virtual webcam" with bog-standard properties. The ffmpeg command streams the output from the real webcam to the virtual webcam. * For higher resolution webcams, it may be necessary to add a -s 640x480 or -s 1280x720 or something along those lines to the ffmpeg command. Carefully, because the order of the flags matters. * To use the virtual device in cheese (and possibly other older programs), I believe you still need v4l1compat.so (which solves a different, independent problem). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765058 Title: Regression: 046d:08da Logitech, Inc. QuickCam Messanger not detected in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765058/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772081] Re: HP x360 - Ryzen 2500U Locks up
> disabling it increases power consumption of CPU at least by 80% in idle state That doesn't say much at all. _Suppose_ the CPU's power consumption is 5W in C6 state, and it indeed increases by 80%, then it becomes 9W, or 4W more. I could live with that - at least until a better fix becomes available. The problem is of course that those are imaginary numbers. Does anyone have some data on the increase in power consumption, in W, of a real system upon disabling C6 state? Otherwise, I may attempt to measure it myself once I find some time. But that can take a while... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772081 Title: HP x360 - Ryzen 2500U Locks up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768352] Re: mate-screensaver screen lock can be bypassed by power cycling monitor
Any progress on fixing this in the LTS version? AFAIC this is a pretty high-profile security issue, and may not very prudent to leave open for months after it's fixed upstream. Imagine the storm of bad press if Microsoft or Apple were to pull something like this - or even if this bug report catches the eye of the wrong people... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768352 Title: mate-screensaver screen lock can be bypassed by power cycling monitor To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1768352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072136] Re: [FFe] After doing updates, update manager propose to install an empty list of updates
The good news: released fix works. What's a bit worrisome, though, is that I had to *manually* run sudo apt-get install update-manager update-manager-core python3-update-manager in order to be able to use update-manager to install all other updates, some of which were long overdue because of this bug. I'm not sure if update-manager would eventually have updated automatically, but even then, I can imagine that a lot of users would be permanently at risk from outdated software because of having disabled automatic updates or because of running ubuntu on a laptop that never gets the chance to update automatically [as the bug itself prevents updating manually, at least for users who only know update-manager]. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072136 Title: [FFe] After doing updates, update manager propose to install an empty list of updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1072136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636402] Re: Low text contrast with Ambiant-Mate color scheme
I do get that you're trying to motivate someone to tweak the Ambiant- Mate theme, and I do agree that it is not particularly comfortable to use in Pluma. However, I don't think threatening to recommend another distro will impress many people, given that all one needs to do is go into Preferences... Font & Colors... and choose another theme, such as "Radiant-MATE". What annoys me more is that choosing "Radiant-Mate" desktop-wide in "Appearance Preferences" neither affects pluma, nor the MATE terminal. For the latter app, this is especially unforgivable, since it has a "Use colors from system theme" check box that is explicitly supposed to follow "Appearance Preferences" according to the help document. So we actually have 3 bugs here: (1) Ambiant-Mate is poorly readable (That would be this bug, except that it might need to be filed against the theme instead of pluma, per your post #3 . It can also be argued to be a matter of opinion, though if a large percentage of the users turn out to be of the opinion that it's poorly readable, then it is a problem nevertheless.) (2) "Use colors from system theme" in MATE terminal does not do what is says. (3) There is no corresponding way to make pluma follow the system theme (also, consistency???) Feel free to modify the "Affects" field of this bug and file 2 more bugs (assuming they're not in some bug tracker here or upstream already). I'd do it myself if I had more time... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636402 Title: Low text contrast with Ambiant-Mate color scheme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pluma/+bug/1636402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 563808] Re: glob2 assert failure: glob2: src/Building.cpp:2848: void Building::integrity(): Assertion `(*it)->targetBuilding==this' failed.
** Bug watch added: Non-GNU Savannah Bug Tracker #25731 http://savannah.nongnu.org/bugs/?25731 ** Also affects: glob2 via http://savannah.nongnu.org/bugs/?25731 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #592412 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592412 ** Also affects: glob2 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592412 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/563808 Title: glob2 assert failure: glob2: src/Building.cpp:2848: void Building::integrity(): Assertion `(*it)->targetBuilding==this' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/glob2/+bug/563808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
The Optimus issue most definitely must be filed as a separate bug (and comments on it go there). In order for a bug tracking system like this to work well, the technical scope of a bug must be narrowly defined; that's software development good practice 101. If the scope of a bug is vague or allowed to creep, no developer will touch the "assign to me" button with a 10-foot pole. In fact, this is exactly the reason why lp:1268257 has been sitting there for 18 months without any progress; the error description consisted of a *symptom* that could have a very large number of causes, so nobody was willing to go look into all of them. It was only after it was realized that lp:1431753 was the cause in the vast majority of cases that things started moving. In this context, kudos go to teo1978 for forcing the breakthrough by finding and applying a workaround for lp:1450251 . You guys have to forgive him for being a bit testy. Even the most patient person would throw a fit after waiting 18 moths for a trivial-looking fix to a bug that made thousands of users lose their GUI every few weeks, and then getting another show-stopping problem when applying that fix! Anyhow, the scope of *this* bug is the DKMS violation, which is fully fixed. From a *technical* perspective, the Optimus issue is an entirely unrelated bug. The fact that it's triggered by the present fix does not matter a this stage. Just to set the record straight (you might want to use part of this in the description of the new bug): there are (at least) 2 separate ways to get Optimus support working in Ubuntu: (1) nvidia-prime : allows you to switch between running the whole desktop on Intel or Nvidia. The choice is made in the nvidia control panel and takes effect when logging out and back in. It's far from a perfect solution but at least it's easy to use. (2) bumblebee : allows you to specify on which card to run a given program at the command-line (or by editing the application launcher). I personally prefer this route because it gives me more granular control and doesn't force you to log out, but novice users may find it cumbersome. It appears that the configuration files of the packages that are involved in both (1) and (2) did not anticipate drivers newer than 331 to be used with 14.04, resulting in a blank screen upon login. The fix for (1) is in Anna's link: http://vxlabs.com/2015/02/05/solving-the-ubuntu-14-04-nvidia-346-nvidia-prime-black-screen-issue/ . As for (2), see my post: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340-updates/+bug/1431753/comments/62 . Now, if canonical was really serious about LTS, they would have a sufficiently large and professional team working on this. The person responsible for the nvidia driver would have remembered to contacted the people responsible for the gpu-manager and bumblebee packages, or at the very least have been reminded of it by my post, which I made when the fix was still in the "proposed" stage. The actual release of the fix would have been delayed while those other developers would be updating the configuration files of their respective packages (that's, like, less than an hour of work), and the updates would need another round of testing. After 18 months, nobody would have cared about those few days, and it would have prevented the present outpouring of disappointment. And yes, there is a lesson to be learned here. It is becoming increasingly clear that Ubuntu Mobile, much like Windows Mobile, will never compete with the 800-pound gorillas Android and iOS on the mobile platform, and all efforts in that direction are an utter waste. Also, thinking that the desktop will go away is naive; desktops will continue being the platform of choice in the workplace (as well as the enthusiast's basement) for the foreseeable future. Therefore, Canonical should go back to doing what it did best: pushing Linux into the desktop market. And since IT managers generally don't want to upgrade all systems every 6 months. LTS support deserves far more love than it's currently getting. Windows 10's retreat to the desktop metaphor was largely driven by the realization that the desktop market is firmly shifting into the domain of professionals (and enthusiasts), who are not well-served with bells and whistles, frequent breakage and a dumbed-down interface. How long will it take until Shuttleworth gets the memo? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Sezer, you're not going to believe this, but the issue you're having with steam has nothing to to with the nvidia driver, but is caused by a completely unrelated kernel bug that just happened to occur at the same time people started testing the fix for the nvidia driver; see lp:1479093 . The fix for the kernel bug is already released, so just upgrade your kernel yet again, and your steam problem will go away. I have to add that I also got confused by wine not working anymore after applying the nvidia patch (and upgrading the kernel for the first time in many months in order to test it), and it took me almost 2 hours to figure out the problem was unrelated. This whole affair is turning into one of the most frustrating experiences I've ever had with Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Mat, I am happy you got past your blank-screen problem, even though the things mentioned in my previous post may or may not have played a role in solving it. To be perfectly clear toward other people who come across this discussion, the points (1)-(4) in my previous post DO NOT represent a step-by-step solution for getting a graphical desktop back after running a routine kernel upgrade. They are a few things *I* tried for the specific case of APPLYING THE DRIVERS FROM TRUSTY-PROPOSED TO AN EXISTING BUMBLEBEE SETUP. And it's quite likely some of them are not useful or even harmful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
For anyone who didn't get the message, fixed versions of the the 440 driver (with legacy GPU support) and the 446 driver (which only supports relatively recent GPUs) are now available in the official trusty- proposed repository. A few people (including me) have reported trying them with the 3.13 kernel and getting encouraging results. So, for those of you who cannot wait to have a fix up and running, try trusty-proposed ; for the rest, it looks like the long wait for a fix in the "default distribution" is almost over. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Fix confirmed on 2 very different machines both running Ubuntu 14.04 "Trusty" with the 3.13 kernel. Detailed notes: AMD workstation with only a discrete nvidia GPU (nothing else) Synaptic complained about conflicts when selecting updated driver from trusty-proposed (something involving nvidia-libopencl1-* vs nvidia-opencl-icd-* IIRC). Installing through aptitude worked better. No further issues when rebooting, updating the kernel and rebooting again. Intel laptop running bumblebee == Blank screen after updating. Solutions tried: (1) starting the kernel with nogpumanager and removing /etc/X11/xorg.conf generated by gpu-manager (2) removing the newly created file /etc/prime-discrete (3) sudo sed -i 's/-current/-346-updates/g' /etc/bumblebee/bumblebee.conf (4) adding lines for 340 and 346 to /etc/modprobe.d/bumblebee.conf Applying all of the above fixed the problem, and (1)-(3) without (4) didn't, so it's very likely that (4) is necessary. What I cannot tell is which of (1)-(3) are also necessary and which are optional.(*) Bottom line is that special precautions should be taken to prevent bumblebee from breaking when rolling this out. (*) I could of course figure that out by reverting the changes one-by- one, but this bug already robbed me of an outrageous amount of my time and all of my goodwill, so you're on your own. Thanks a lot for finally fixing it, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
No, this is *not* fixed for 331 and 331-updates; in fact, nothing has changed. The "fix released" status presumably was set by yet another inattentive user who landed onto this Launchpad page after getting a whoopsie error. Unfortunately, the status cannot easily be reverted to "triaged" because of what I feel is a shortcoming in Launchpad. There is some good news, though: Alberto Milone over at lp:1431753 (which describes the actual *source* of the problem) hinted at intending to provide a fix for 14.04. Unfortunately, he hasn't provided any updates, details or time frame in the last 3 weeks. So, those of you who have not become completely embittered by Canonical's unforgivable lack of attention to this atrocious bug in their "Less Than Stellar" (LTS) line, PLEASE head over to lp:1431753 and politely draw their attention to the fact that a massive number of users are very badly affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
*bump* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Nice! Will this work with the 3.13 kernel in 14.04 ? Also, do you have any idea when it will be available to end-users? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Alberto, thank you sooo much, that is great news. Especially since there seems to be another wave of bitter comments and confusion on lp:1268257 . Two questions: - Am I understanding correctly that you'll fix the problem for the 331 driver AND that we'll have the option of using the 340 or 346 driver with the 3.13 kernel in 14.04 ? (For me personally, _either_ solution would work. Having newer drivers is always nice, but there might hypothetically be people with really old hardware who require the old driver.) - Do you have any idea when either solution will be available to end-users? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
@Adam Koczur (sbv): you do indeed appear to have the wrong bug report; the bug we're (effectively) talking about *here* is also triggered by 331.113-0ubuntu0.0.4 from nvidia-331-updates (it's what I'm running) and is described more accurately at lp:1431753 . In case you wonder why the heck this is not a duplicate, see lp:1450251 . I don't know whether I have to laugh or cry. @Robert Dinse (nanook): you probably should take the 3.19 discussion to the relevant LP bug report - @Adam Koczur (sbv), can you please povide an "lp:" link? There is far too much offtopic talk on this one as it is already. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
@Adam Koczur (sbv): nice, that is a step in the right direction! However, I have to point out that pretty much everyone who is affected by this bug is running the 3.13 kernel that comes with Trusty; those who are running newer (non-LTS) kernels all have newer nvidia drivers (except the ones with legacy graphic cards, but that's a minority; nvidia's legacy support goes quite a way back...) So, do you think it would be safe to test your ppa with the 3.13 kernel, or is that not expected to work? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Dear Alberto and others, Could you please please backport this fix to the 331 driver, which is the most recent one available for 14.04 LTS (Trusty)? Or at the very least explain why this might not be as trivial as it sounds? This bug impacts a massive amount of Trusty users, and failing to get a graphical interface every time the kernel is upgraded is quite high-profile; a lot of people are abandoning Ubuntu altogether for it. Our whole workplace may do so soon because one of the programs we use professionally requires the proprietary Nvidia driver and our support people cannot afford the time commitment to have everyone use the non-LTS branches. I also feel I need to point out that the "users affected" and bug heat of this report ( lp:1431753 ) are misleadingly low. Most of the users who trigger this bug land at lp:1268257 . If you look at the stats of *that* bug and all the recent comments, the whole affair starts to look like a trainwreck. We tried to make lp:1268257 a duplicate of this bug ( lp:1431753 ), which would presumably bump the latter to the top of the priority list, but were prevented from doing so by a bug in Launchpad itself ( lp:1450251 ). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
@Bill Turner, wb4alm (wb4alm): FYI, "Triaged" means that a bug supervisor has determined that the bug report contains all necessary information to start working on it. This is in my opinion the (only) correct status for nvidia-graphics-drivers-331 and nvidia-graphics- drivers-331-updates (note that some of the necessary information is in lp:1431753 ). See also https://help.launchpad.net/Bugs/Statuses . @Daniel van Vugt (vanvugt): thank you, thank you so much!!! You might have saved my sanity there (depending on whether the issue will actually get fixed in a reasonable time span). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
This is my current Hanlon-compliant(*) theory as to why the fix is not backported: - Anyone looking up this bug will land at the top of the page, where the status is displayed. A small percentage will make random changes to the status by lack of attention or understanding. - This bug report is visited by huge numbers of people, so even though the percentage of "inattentives" is small, we're seeing lots of random status changes in its activity log. - The problem is that some status changes are irrevocable. Specifically, shortly after the fix was released for the 340 and 346 drivers, people mistakenly changed the status for the 331 drivers and the bug as a whole to "fix released". This made it fall off the devs' radar, and there doesn't seem to be a way to roll back the status. In my opinion, this is stupid and should be filed as a bug against Launchpad itself. My current plan to work around this problem is to mark this bug ( lp:1268257 ) a duplicate of lp:1431753 , which - has the status set correctly, including a target for "Trusty", - has a more knowledgeable description of the root cause of the problem and how to fix it, - is frequented by people who can actually fix it, - suffers from a low "bug heat", which will change dramatically if my plan succeeds, - does not suffer from random status changes. However, a new problem surfaced: trying to set the dupe in Launchpad invariably gives a timeout error (Error ID: OOPS-f524378385a3a281890972cc17c96962 OOPS-bb927226a672db21659a9f400adc4757 etc...) I speculate this is due to the huge size of this bug in terms of followers, duplicates, people affected and comments. Whatever be the cause, it's yet another bug to be filed against Launchpad itself. Needless to say, I'm getting deeply disillusioned with Ubuntu, Canonical and its bug fixing process... (*) My alternative theories that are not compliant with Hanlon's razor are probably not appropriate for this venue. :-P -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
@ Sébastien BOUISSET (sbouisset): your're using the non-LTS branch of Ubuntu. I've been repeating ad nauseam during the last few weeks that the issue is NOT FIXED in the LTS branch, which uses the 331 driver, and is popular with professional users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
Oh come on, this is completely wrong! This bug is *NOT * fixed for the 331 driver (and also not for "NVIDIA Drivers Ubuntu" because 331 is the most recent driver available in 14.04 LTS (Trusty)). Why doesn't launchpad allow to correct this mistake by setting it back the "Confirmed"??? If the devs are under the mistaken impression it is fixed, it will never get their attention. What does it take to rectify this? Opening yet another new bug and marking this one as a duplicate? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
The fact that there are so many accidental edits to the status of this bug seems to indicate it's getting large numbers of views. Canonical, your LTS user base is bleeding. For pity's sake, make it stop. Talking about accidental edits, can someone please, please set the status for "NVIDIA Drivers Ubuntu" back to "Confirmed"? See my message #259 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
** Changed in: nvidia-drivers-ubuntu Assignee: done (mnmarkonissinen) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
@stephen (stephen-puttick) : I don't think that's needed; it is my understanding from lp:1431753 that this bug is already fully characterized, and fixed for the 340 and 346 drivers in Utopic and Vivid. Furthermore, the fact that the fix appears to be performed at the level of the metadata strongly suggests that it would be absolutely trivial to apply the same fix to the 331 drivers in (un)Trust(worth)y. Canonical might have their reasons for not "backporting" the fix to their LTS release, but as long as the only noise we get from them is crickets chirping, it is hardly surprising that the community is starting to ask questions about their motives and/or professionalism... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
You might have meant to say 14.04. Which is still supported till March 1019. That's a very long time for Canonical to claim to be supporting something that's so broken... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
@ awol (awol99) : I'll do you one better. At my workplace, we just started the process of gradually upgrading all our machines from 12.04 Precise to 14.04 Trusty. After starting with a few, we've hit this bug. Yesterday, I had a discussion about it with the person responsible for software maintenance, and it looks like we'll be upgrading the whole shop to Debian instead. It's not just the direct annoyance caused by this bug (though it is rather serious given that one of the programs we use professionally requires the proprietary Nvidia driver), but more importantly what Canonical's response (or rater lack thereof) implies for our future level of support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
As long as the current LTS (i.e. 331) drivers are not fixed, I think it is wrong to set the status for nvidia-drivers-ubuntu to "Fix Released". Can someone with the necessary permissions please undo the status change by royalsabz (mehrshad-5843) ? And set the importance to "High", while you're at it? This is a really important high-impact bug that should be as high as possible on the agenda until it's completely fixed for all currently supported releases. In this light, the apparent casual lack of attention from Canonical's side is beyond my comprehension. I can only speculate they're too busy making Vivid attractive enough to lure in new users, and are forgetting about keeping long-time users. To the people who think that's the right thing to do: please try to weigh the potential harm caused by delaying Vivid a day or so against the actual harm of having thousands of long-time users' desktops breaking en masse because of running seemingly-innocuous kernel updates... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
Can someone please, please apply the fix that worked for 346 and 340 to 331 also? Or at the very least explain why this might not be as trivial as it sounds? As I pointed out in lp:1431753, 331 is still the most recent driver supported by the current LTS release. This is a bug that affects thousands of users, not all of whom will be willing/skilled to upgrade their kernels (and then upgrade them again and again every time short-term support runs out). This bug has impacted us badly, and I'm on the verge of stopping to recommend people to use Ubuntu LTS in professional settings, as I feel Canonical is betraying its LTS users big time here. And I'm not the only one losing my patience; see for instance comment #249... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431753] Re: Nvidia binary driver FTBS due to DKMS layer violation
Sorry, but 331 is still the most recent driver supported by the LTS release. While "LTS" doesn't seem to mean much to Canonical anymore, at least try to keep up the appearance. Especially for a bug that affects thousands of users, not all of whom will be willing/skilled to upgrade their kernels (and then upgrade them again and again every time short- term support runs out). ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: Invalid => Confirmed ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431753 Title: Nvidia binary driver FTBS due to DKMS layer violation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1431753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
The workaround in post #100 works at the level of the individual user, but it's a bit flawed in the sense that it will be undone every time the driver (not the kernel) is updated. In addition, if I understand the legal aspects correctly (IANAL), it does not qualify as a fix because Canonical cannot _distribute_ it without committing a license violation. And requiring the user to reinstall the driver after every kernel upgrade (post #101) *definitely* doesn't qualify as a fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file"
** Also affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: "objdump: '... .tmp_nv.o': No such file" To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026356] Re: Bad validation on Scales box on Axis (chart properties)
Warning: launchpad's autogenerated hyperlinks in my previous post are wrong; the explicit "https://"; link is the only correct one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026356 Title: Bad validation on Scales box on Axis (chart properties) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1026356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026356] Re: Bad validation on Scales box on Axis (chart properties)
I linked this to upstream bug #49987 , but on second thought, upstream bug #57697 contains more recent and relevant info (they ought to mark one a duplicate of the other). https://www.libreoffice.org/bugzilla/show_bug.cgi?id=57697 Between the 2 upstream reports, it appears the bug occurs in 3.5.x and 3.6.x, but is fixed from 3.7 onwards. The upstream info also led me to find a workaround (for my specific instance, anyway): in the "Format Axis" dialog, one can click on the "Numbers" tab, uncheck "source format" (if it's checked), then choose Category: Number and Format: General. Then click "OK" and open the "Format Axis" dialog _again_, and then everything should work as expected. This workaround has been a life-saver for me as I'm on a machine I currently can't upgrade, and Ubuntu Precise is still supported till 2017... ** Bug watch added: LibreOffice Bugzilla #57697 https://www.libreoffice.org/bugzilla/show_bug.cgi?id=57697 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026356 Title: Bad validation on Scales box on Axis (chart properties) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1026356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 577658] Re: Bad validation on Scales box on Axis (chart properties)
*** This bug is a duplicate of bug 1026356 *** https://bugs.launchpad.net/bugs/1026356 ** This bug has been marked a duplicate of bug 1026356 Bad validation on Scales box on Axis (chart properties) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/577658 Title: Bad validation on Scales box on Axis (chart properties) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/577658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026356] Re: Bad validation on Scales box on Axis (chart properties)
** Bug watch added: freedesktop.org Bugzilla #49987 https://bugs.freedesktop.org/show_bug.cgi?id=49987 ** Also affects: df-libreoffice via https://bugs.freedesktop.org/show_bug.cgi?id=49987 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026356 Title: Bad validation on Scales box on Axis (chart properties) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1026356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101636] Re: LICENSE.aic94xx-seq in linux-firmware - is this firmware distributable?
I had the same confusion as you. The only way I could make sense out of it all is that Canonical did not obtain the same (non-transferable) "distributor" license as Fedora core (and perhaps Debian), and instead must abide by the end-user license license: http://www.adaptec.com/adapteccom/templates/driverdetail.aspx?NRMODE=Published&NRORIGINALURL=%2fen-us%2fspeed%2fscsi%2flinux%2faic94xx-seq-30-1_tar_gz.htm&NRCACHEHINT=Guest which would indeed forbid distribution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101636 Title: LICENSE.aic94xx-seq in linux-firmware - is this firmware distributable? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1101636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152744] Re: mountall is lying about /run's noexec
Thanks Marc! I suspected as much, but I thought I'd ask to be sure. Since it's just released, sysadmins will be happy to find the above clarification in this thread, which helps planning reboots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1152744 Title: mountall is lying about /run's noexec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1152744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152744] Re: mountall is lying about /run's noexec
Sorry for the naive question, but how severe are the security implications of this? Does there exist a CVE, or otherwise a discussion of the implications? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1152744 Title: mountall is lying about /run's noexec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1152744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234071] Re: Multiple windows open on double click
This seems to have regressed in Precise (orage 4.8.3-1); I'm currently experiencing the exact same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/234071 Title: Multiple windows open on double click To manage notifications about this bug go to: https://bugs.launchpad.net/xfce/+bug/234071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40537] Re: [Upstream] [hardy] OpenOffice cannot write to NFS files
This is nothing short of appalling: - Issue still present in LibreOffice on Precise (LTS) - It's been 7 (seven) years - Currently, the workaround is to edit a file that gets overwritten with every update: http://ubuntuforums.org/showthread.php?t=1645957&p=11891452#post11891452 The attached patch yields control over these essential flags back to /etc/libreoffice/soffice.sh , which is part of libreoffice-common but is ignored by /usr/lib/libreoffice/program/soffice (in the same package). It would be trivial for the package maintainer to apply this fix, with no loss of functionality whatsoever. People who are on NSFv3 simply would have to edit a flag in /etc/libreoffice/soffice.sh one time; since it's in /etc , later updates should leave it alone. Nothing changes for anyone else. ** Patch added: "libreoffice.patch" https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/40537/+attachment/3706957/+files/libreoffice.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/40537 Title: [Upstream] [hardy] OpenOffice cannot write to NFS files To manage notifications about this bug go to: https://bugs.launchpad.net/openoffice/+bug/40537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032456] Re: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2
Confirmed with Canon MP520 on Precise . Tested very thoroughly with all different combinations of flags. Didn't work: lpadmin -p Canon-PIXMA-MP520 -o usb-unidir-default=true Didn't work: lpadmin -p Canon-PIXMA-MP520 -o usb-no-reattach-default=true Did work: both of the above flags set at the same time. Details: $ lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 014: ID 04a9:1724 Canon, Inc. Bus 003 Device 003: ID 0409:0059 NEC Corp. HighSpeed Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5719 IMC Networks Bus 003 Device 004: ID 0409:0059 NEC Corp. HighSpeed Hub Bus 003 Device 005: ID 046d:c042 Logitech, Inc. G3 Laser Mouse Bus 003 Device 006: ID 046d:c313 Logitech, Inc. Internet 350 Keyboard Bus 003 Device 007: ID 0b95:7720 ASIX Electronics Corp. AX88772 Bus 003 Device 008: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel Port Bus 003 Device 009: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port Bus 003 Device 010: ID 0d8c:0006 C-Media Electronics, Inc. Storm HP-USB500 5.1 Headset My 2c: it very much sounds like the remedy to bug 987485 and bug 997040 is worse than the disease, and that the above 2 flags should be made the default rather than the exception. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1032456 Title: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1032456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 910672] Re: [REDWOOD] dell U2410 monitor repeatedly turns itself on and off when suspended
Same problem with Intel HD Graphics 4000 on Xubuntu Precise GPU: Intel Corporation Ivy Bridge Graphics Controller Monitor: Viewsonic VX2025wm connected via HDMI Kernel: 3.5.0-27-generic X.Org X Server 1.11.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/910672 Title: [REDWOOD] dell U2410 monitor repeatedly turns itself on and off when suspended To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/910672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 999910] Re: [IVB]12.04 64 bit System freezes (mouse, keyboard)
@Timo: I'm sorry for the clueless question, but can you please explain why this is marked "Fix Released" for Precise? Precise is an LTS version, and it was my understanding that as long as Precise is supported, fixes to proper bugs should to be backported to the "vanilla" (3.2) kernel line. Can you confirm it is now Canonical's official policy that users experiencing kernel bugs should be smart/motivated enough to figure out the problem is fixed in a newer kernel that can be installed through an optional "backports" package? In other words, does Canonical now officially recommend the installation of "backport" packages in order to keep an LTS version functional? Also, it seems that Debian did backport the fix to 3.2 a couple of months ago. Can we expect this to tricle down to Ubuntu, and if yes, approximately when? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689268#489 Finally note that HD 4000 is *very* common hardware (it's probably well on its way to become the most widely used video chip), and the problem is pretty serious, yet I found the solution (installing a "backport" kernel) relatively hard to find. I wonder what this "new policy" will do for Ubuntu's reputation among the less knowledgeable users who didn't figure out the kernel upgrade... ** Bug watch added: Debian Bug tracker #689268 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689268 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/10 Title: [IVB]12.04 64 bit System freezes (mouse, keyboard) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/10/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969520] Re: IcedTea Java Web Start fails to open .jnlp file
The above workaround will break every time the package is updated. The correct workaround (in line with what Sam_ posted) is: sudo update-alternatives --config javaws and then choose the number in front of /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/javaws Of course, this doesn't change the fact that this is a bug that needs to be fixed. Specifically, the packages should provide the package manager with the necessary hints so that the alternatives are always set right (if I understand the software stack correctly). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969520 Title: IcedTea Java Web Start fails to open .jnlp file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/969520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 411358] Re: Thunderbird2 gconf gmt problem 'Bad key or directory name' because of plus symbol (+)
** Also affects: thunderbird via https://bugzilla.mozilla.org/show_bug.cgi?id=541130 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/411358 Title: Thunderbird2 gconf gmt problem 'Bad key or directory name' because of plus symbol (+) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/411358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 411358] Re: Thunderbird2 gconf gmt problem 'Bad key or directory name' because of plus symbol (+)
There seems to be a regression; the bug came back in Thunderbird 13.0.1 and 14.0 (what I have here) on Lucid. Here's the upstream bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=541130 ** Bug watch added: Mozilla Bugzilla #541130 https://bugzilla.mozilla.org/show_bug.cgi?id=541130 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/411358 Title: Thunderbird2 gconf gmt problem 'Bad key or directory name' because of plus symbol (+) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/411358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 588523] Re: Autofs5 fails on cascading/hierarchical mounts
By the way, importance = Wishlist ??? This is clearly a regression, ie. something that used to work as expected, and now doesn't work as expected anymore. Set the importance as low as you want, but please don't make it look like a feature request! Furthermore, the "bug heat" and # of people affected by this bug are in fact higher than most of the "importance=Low" bugs in autofs ... BTW. using version 4 as a workaround is even worse than I thought because it doesn't support "direct mapping". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/588523 Title: Autofs5 fails on cascading/hierarchical mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/588523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 588523] Re: Autofs5 fails on cascading/hierarchical mounts
We tried autofs5.0.5 (natty) and autofs5.0.6 (oneiric), but the problem persisted (on 32-bit Lucid). Then we tried autofs4.1.4 (karmic) - same version as mentioned by dezibelz - and the problems went away (still on 32-bit Lucid). But it's obviously not ideal to be running an old unsupported version like that... Anyhow, bottom line is that it's not fixed yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/588523 Title: Autofs5 fails on cascading/hierarchical mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/588523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 905026] Re: Browser plugin not working after upgrade to Sun jre 1.6.0_26-b03
I would like to invite anyone reading this to consider installing the (officially supported) package icedtea6-plugin and test whether their frequently used Java web applications work with it. I know the open- source Java implementations have been plagued by all kinds of compatibility issues, but OpenJDK & IcedTea have been improving by leaps and bounds, up to a point that even picky java apps often work with them. Indeed, Oracle picked a particularly bad timing for this questionable move. I have no particular interest in pushing the open-source alternatives but I feel Oracle should pay for this. Make them feel they're rendering their newly acquired assets irrelevant by declaring war on the open source community! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/905026 Title: Browser plugin not working after upgrade to Sun jre 1.6.0_26-b03 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sun-java6/+bug/905026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505085] Re: gnome-settings-daemon extensive disk usage
For anyone struggling with this problem and searching for workarounds, the upstream discussion is a good read. Apparently, it is possible to entirely disable the housekeeping mechanism that is responsible for this problem: https://bugzilla.gnome.org/show_bug.cgi?id=625609#c6 Doing so will (1) disable purging of old thumbnails, so one either has to live with the thumbnail cache growing boundlessly, or implement a different workaround, such as the one suggested by Eric Link https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/505085/comments/13 (2) disable the low disk space check and warning - if your disk is nearly full, you'll have to keep an eye on it yourself (3) possibly disable other housekeeping functionality - when experiencing additional side effects, it might be a good idea to feed them back to the community Of course, this is still a (somewhat unsatisfactory) workaround, and we're eagerly awaiting an actual fix from the upstream gnome-settings- daemon maintenance team. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/505085 Title: gnome-settings-daemon extensive disk usage To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/505085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54191] Re: Mouse button click delayed
OK, can anyone check whether the problem is still present in Maverick? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/54191 Title: Mouse button click delayed -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54191] Re: Mouse button click delayed
Yes, my second post corrects the first. The fact that you're getting the problem at all (I presume you're using Maverick?) pretty much confirms Jakob Unterwurzacher's post of 2010-09-14 for the case of Maverick, so we now know that "fix committed" is still the correct status. What I don't fully understand is by what mechanism the importance was changed from "Low" to "Unknown". Also, that option in your xorg.conf should prevent the problem from occurring at all, no matter what X version you're using, so something doesn't make sense here. I think you *might* have used incorrect syntax in your xorg.conf, where the correct syntax would be (note not only the section but also "off" instead of "no"): Section "InputClass" Option "Emulate3Buttons" "off" EndSection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/54191 Title: Mouse button click delayed -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54191] Re: Mouse button click delayed
Oops sorry, forget my previous post. In Jaunty and Lucid, X will start up having the problem, but it will go away as soon as the middle button is pressed (I'm on Lucid and use the middle button so often I forgot the bug is still there). Can anyone check whether the problem is still present in Maverick? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/54191 Title: Mouse button click delayed -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54191] Re: Mouse button click delayed
This bug was actually fixed as a side effect of the Ubuntu installer not generating an xorg.conf anymore and letting X autodetect the hardware on startup instead. X by default does not enable the Emulate3Buttons flag (I speculate having this flag enabled in the default xorg.conf file was an Ubuntu-specific "feature"), so the problem is gone. I believe this "fix" first occurred in Jaunty, and the first LTS version that has it is Lucid. However, I also believe the Ubuntu upgrader keeps the old xorg.conf file, so merely upgrading to a current version won't make this problem (or the Emulate3Buttons flag that causes it) go away - this can only be accomplished by editing xorg.conf or by installing the current version from scratch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/54191 Title: Mouse button click delayed -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544935] Re: netcat-openbsd exits too soon
I just wasted a full, extremely frustrating working day trying to find why a complicated script involving in-house software and a tangle of named pipes and background commands stopped working. Now it's after midnight, I'm still at work, and I found out it's this. I'm right now very tempted to give up on ubuntu. Even worse, the -q workaround doesn't work for me; I had -q in my scripts all the time just for good measure. My server-side application is a sponge. Like the unix "sort" command, it first soaks up all the input, and only after it receives and EOF through the input channel, it processes the input and starts producing output. Traditional netcat behavior with -q x would be (from the client-side point of view): - upon receipt of an EOF on stdin, close the output stream, putting the TCP connection in half-close state (this effectively transmits the EOF to the server, triggering my server-side application to start processing) - wait x seconds (while data from the server-side application flows in) - quit (in my case, it actually quits before the x seconds are over because the server closes its side of connection when it finishes processing) Ubuntu's new borken netcat does the following instead: - receive an EOF on stdin but don't let the remote host know (I speculate this is a "feature" of BSD netcat but it might also be another ubuntu bug) - wait x seconds - quit (only now an EOF is detected at the server side, but it's too late to send data back) As you can see, my scripts are now broken beyond repair. My only solution is installing netcat-traditional. One of the great features of the traditional netcat was that it could function as a two-way unix pipe for TCP (hint: net-cat). Swallowing the EOF breaks this, as illustrated by the above example. I don't know what people were thinking when they changed this, but they surely haven't been reading the traditional netcat man page: You may be asking "why not just use telnet to connect to arbitrary ports?" Valid question, and here are some reasons. Telnet has the "standard input EOF" problem, so one must introduce calculated delays in driving scripts to allow network output to finish. This is the main rea- son netcat stays running until the *network* side closes. Further discussions about this issue: http://oskt.secure-endpoints.com/man/knc.1.pdf http://www.eggheadcafe.com/software/aspnet/36139087/example-code-for-using-gawks--operators.aspx nc6 seems to have the best solution: by default, it works like the "BSD-style" netcat, but it has the --half-close flag which makes it work like traditional netcat (and saves the day for me). http://linux.die.net/man/1/nc6 -- netcat-openbsd exits too soon https://bugs.launchpad.net/bugs/544935 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 195483] Re: Sound Juicer - MP3 quality doesn't change
Ah, so you mean the new parameters are poorly documented??? BTW, xingmux only adds a header, it doesn't touch or affect the audio in any way: http://www.gstreamer.net/data/doc/gstreamer/head/gst-plugins-ugly-plugins/html/gst-plugins-ugly-plugins-xingmux.html It would be clearer and technically more accurate to refer to the different profiles as "lame" and "lamemp3enc" (if that's what you mean). Using ambiguous language is asking for being misinterpreted. -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 325200] Re: cannot switch keyboard layout after reconnecting keyboard
I can confirm this issue in Lucid. Here's a workaround (in a terminal): setxkbmap cz setxkbmap us -- cannot switch keyboard layout after reconnecting keyboard https://bugs.launchpad.net/bugs/325200 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 195483] Re: Sound Juicer - MP3 quality doesn't change
I also submitted a patch upstream which processes the file gnome-audio-profiles.schemas.in.in , from which gnome-audio-profiles.schemas is generated at compile time. The package maintainer is free to choose whichever patch they find most convenient to use. ;) http://bugzilla-attachments.gnome.org/attachment.cgi?id=171324 -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 195483] Re: Sound Juicer - MP3 quality doesn't change
I attached a patch to be applied to /usr/share/gconf/schemas/gnome- audio-profiles.schemas > What's the next step to get the bug solved? The next step is to get this patch into Maverick. In an ideal world, gnome-media should adopt it, then Ubuntu should simply pull it in from the upstream repo's. However, there's no time for that anymore; the gnome-media people haven't even looked at my new bug report yet, leave alone discussed it and committed it, and Maverick comes out of beta and into "release candidate" in 2 days, at which point they won't be willing to change a lot anymore, leave alone pulling in new stuff from upstream. Our only chance is that some friendly ubuntu developer is willing to slip this in as a last-minute ubuntu-specific patch. I wouldn't hold my breath; my best bet is that users will still be plagued with quality=6 until "Natty Narwhal" comes out. It's a shame because it's only a few lines in gnome-audio-profiles.schemas (ignoring translation to other languages than English for now); no recompiling required or anything. > As to the new parameters being discussed, they still seem to > lack definition ABX results or else it's just your imagination. http://www.hydrogenaudio.org/forums/index.php?showtopic=16295 http://wiki.hydrogenaudio.org/index.php?title=ABX Evaluation of sound quality is pathologically susceptible to listener bias. This is why there is a market for "$ ultra high quality S/PDIF cables" and other such snake oil. ** Patch added: "patch for /usr/share/gconf/schemas/gnome-audio-profiles.schemas" https://bugs.launchpad.net/ubuntu/+source/sound-juicer/+bug/195483/+attachment/1651579/+files/maverick_mp3.patch -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 195483] Re: Sound Juicer - MP3 quality doesn't change
- This is not about bit rate, this is about quality. Getting a higher bit rate does not automatically equal getting a higher quality. In fact, botching the psychoacoustics model with a load of settings is a good recipe to get similar or higher bit rates but a lower quality. - For assessing quality, one person's subjective listening tests mean next to nothing. It is for this reason that I kept my own perception of sound quality out of this discussion (I also have a set of pretty good headphones and trained ears, but that's simply not relevant). However, there are ways to objectively test quality, by using ABX methodology, long systematic testing, a large sample of listeners, and sounds statistical analysis. That 's exactly what the folks at hydrogenaudio.org did, and they came up with recommended settings for standalone LAME. They also found that it's easy to pull down the quality by giving LAME a bunch of extra switches (you'd have to go digging through the hydrogenaudio forums for that). For this reason, I will trust anything that gives output that is bitwise identical to standalone LAME with the hydrogenaudio recommended switches, and I will not trust anything else. The "lamemp3enc" element falls into the former category, the "lame" element into the latter. Histograms of bitrates are irrelevant. - Conicidentally, the same people at hydrogenaudio.org found that "Nowadays LAME is considered the best MP3 encoder at mid-high bitrates and features the best VBR model among MP3 implementations." Oh, and there's what they think about Xing: "The Xing (pronounced "zing") MP3 encoder was one of the fastest MP3 encoders. Of course that comes with a price, and quality wasn't on par with encoders tuned for quality instead of speed, like FhG Slowenc (Audioactive) and LAME." So here we are, LAME is at the very least one of the best encoders out there, and nobody will miss the restricted ones that were thrown out. As FiloSottile said, the "lame" interface to liblame is buggy, the "lamemp3enc" interface is not. The only thing up for discussion is really how to call "lamemp3enc" (and make sure it's implemented in the Maverick release). Here's my proposal again: https://bugzilla.gnome.org/show_bug.cgi?id=630779 CD Quality -- audio/x-raw-int,rate=44100,channels=2 ! lamemp3enc name=enc target=0 quality=2 ! xingmux ! id3v2mux Portable MP3 Player Quality --- audio/x-raw-int,rate=44100,channels=2 ! lamemp3enc name=enc target=0 quality=6 ! xingmux ! id3v2mux Voice Quality - audio/x-raw-int,rate=44100,channels=2 ! lamemp3enc name=enc target=1 bitrate=56 mono=true ! xingmux ! id3v2mux ** Bug watch added: GNOME Bug Tracker #630779 https://bugzilla.gnome.org/show_bug.cgi?id=630779 -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 388160] Re: user input -- mouse queuing flaw
*** This bug is a duplicate of bug 54191 *** https://bugs.launchpad.net/bugs/54191 @Fabio Marconi: I finally succeeded in installing Lucid (had some technical problems doing so and not a lot of time to experiment). The bug is now present when freshly starting X, but disappears as soon as the user presses the middle mouse button. You could have known this by looking at the Xorg bug of which this one is a duplicate https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/54191 (see post #10; just to make this 100% clear for other people, I'll try to mark this bug as a duplicate). I personally use the middle mouse button so frequently (for pasting) that after installing Lucid, I didn't even notice the bug was still there, but there may be other users who don't use their middle mouse button so much and still have problems. @daniel: judging by what you wrote, your written English is probably better than a significant percentage of native English speakers (at least here in the USA). I would classify your fluency as "advanced" to "near-native". Don't reply to this to thank me; this is a site for reporting bugs and there's no place for off-topic stuff. ** This bug has been marked a duplicate of bug 54191 Mouse button click delayed * You can subscribe to bug 54191 by following this link: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/54191/+subscribe -- user input -- mouse queuing flaw https://bugs.launchpad.net/bugs/388160 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 195483] Re: Sound Juicer - MP3 quality doesn't change
** Also affects: gnome-media via https://bugzilla.gnome.org/show_bug.cgi?id=619642 Importance: Unknown Status: Unknown -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 195483] Re: Sound Juicer - MP3 quality doesn't change
BruceR, the things you're saying are simply not true. This is complex business and I can understand it confuses you, but please don't make stuff up. Browse Gnome Bugzilla (links at the end of this post). Look at the source code. Encode the same sample with gstreamer and with standalone LAME and do a binary comparison on the outputs (a hex editor might be helpful for this purpose). What you need to understand is that the deprecated "lame" element and the new "lamemp3enc" element are simply two different gstreamer interfaces to the same liblame library. The "lame" element is called by specifying "lame" in the gstreamer pipeline, the "lamemp3enc" element is called by specifying "lamemp3enc" in the gstreamer pipeline. Not difficult so far. Now, here are the differences: - The "lame" element tried to expose each and every LAME flag to the user, including many developmental flags that were never meant by the LAME developers to be set by end-users. Unfortunately, it had default values for each and every of these flags, and it would pass all of them on to liblame. This was harmful because (1) not all of the "lame" element's default values were sensible and (2) these flags override a number of settings that otherwise would be set internally by liblame at runtime depending on the situation. - Specifically to cure this problem, Sebastian Dröge wrote the "lamemp3enc" element, at the request of (among others) Gabriel Bouvigne (LAME developer), David Joaquim (gnac developer) and myself. The "lamemp3enc" element is a much simpler interface, giving the user only the few options that were meant by the LAME developers to be set by end-users. Flags that are not specified by the user (in the gstreamer pipeline) are mostly left "undefined", allowing liblame to achieve its maximum quality by setting the corresponding settings internally to sensible values depending on the situation. If you don't believe me, here's some background information. Please do your homework (ie. read each and every post *carefully*) before posting again. https://bugzilla.gnome.org/show_bug.cgi?id=494528 http://git.gnome.org/browse/gnome-media/commit/?id=155f6ce6463a95146664b08b924d057679ca2f7c https://bugzilla.gnome.org/show_bug.cgi?id=619642 https://bugzilla.gnome.org/show_bug.cgi?id=626285 ** Bug watch added: GNOME Bug Tracker #619642 https://bugzilla.gnome.org/show_bug.cgi?id=619642 ** Bug watch added: GNOME Bug Tracker #626285 https://bugzilla.gnome.org/show_bug.cgi?id=626285 -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 195483] Re: Sound Juicer - MP3 quality doesn't change
The gstreamer bug is fixed but the implementation of this fix depends on sound juicer - updated remote watch accordingly. ** Changed in: sound-juicer Importance: Critical => Unknown ** Changed in: sound-juicer Status: Fix Released => Unknown ** Changed in: sound-juicer Remote watch: GNOME Bug Tracker #494528 => GNOME Bug Tracker #519882 -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 195483] Re: Sound Juicer - MP3 quality doesn't change
Bruce R, please read all the posts carefully. The "lame" element is known to be broken, and has been superseded by "lamemp3enc". Stop encouraging people to use the "lame" element. https://bugzilla.gnome.org/show_bug.cgi?id=494528 (FYI, Gabriel Bouvigne is one of the core LAME developers). I did elaborate tests and not even once succeeded to make the "lame" element produce the same output as the standalone LAME program, because the "lame" element internally sets a whole series of developmental LAME flags to ill-conceived values. Ironically, the combination of flags you're suggesting are the ones I came up with in January 2009: https://bugs.launchpad.net/ubuntu/+source/sound-juicer/+bug/195483/comments/22 Notice the last two sentences of my post. Yes, these flags seem to be well behaved if you only look at the output bitrates, but remember, bitrates are not everything. It's perfectly possible to encode at high bitrates and still have audible artifacts *cough* xingmp3encoder *cough* Again, the "lame" element is officially deprecated; the "lamemp3enc" element leaves all flags at their (good) default values and produces outputs that are bitwise identical to standalone LAME. Oh yeah, I still don't know what name=enc does, but it's definitely *not* "ensuring use of the correct LAME plugin". My best guess so far is that it sets some tag, which perhaps facilitates interfacing with some other program. -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 195483] Re: Sound Juicer - MP3 quality doesn't change
OK, this might be getting confusing. Just a summary for people who are new to this bug, and some suggestions for future directions: - People initially filed this as a sound-juicer bug, while *at that time*, it was actually a gstreamer bug; the "lame" element, which was responsible for encoding mp3 files by interfacing with the LAME mp3 library, was misbehaving. - Rather than attempting to fix the "lame" element, which was entirely based on incorrect assumptions, Sebastian Dröge created a brand new LAME interface named "lamemp3enc", which is simple to use and in line with the LAME developer's UI guidelines. http://lame.sourceforge.net/lame_ui_example.php Around that time, I stopped following this bug, assuming that it would be fixed soon (I'm using RubyRipper with standalone lame for my own CD ripping purposes so I'm not directly affected). - Now, more than a year later, "lamemp3enc" is indeed in gstreamer0.10-plugins-ugly-multiverse (which is good), but sound juicer still calls the obsolete and buggy "lame" element instead of "lamemp3enc" (which is inane). - So, what we're looking at *right now* is a sound juicer bug (yes I consider a default setting that results in "data loss" - quality loss actually - a bug), and what we need is suggestions for default gstreamer pipe lines for sound-juicer. - A good starting point for this would be hydrogeaudio.org - the guys over there are digital audio professionals and enthusiasts and they have done an incredible amount of ABX blind testing and debating to come up with recommendations for using lame. http://wiki.hydrogenaudio.org/index.php?title=LAME * For what most people would call "CD quality", they recommend VBR qualities 0,1,2 or 3 (according to taste). * For "portable mp3 player quality", they recommend VBR qualities 4, 5 or 6 * For "voice quality" they recommend ABR with a target bitrate lower than 100. The current juicer presets join the channels to mono when voice is selected, so in that case, a target bit rate of 56 seems sensible (ie. "lamemp3enc name=enc target=1 bitrate=56 mono=true" , thus mimicking "--preset voice" of standalone lame). - How to implement this all depend on how much of these internals one would want to expose to the user. While I myself would very much enjoy juicer giving me the option to choose between VBR and ABR and set the quality/bitrate myself (as FiloSottile seems to suggest), juicer's design philosophy seem to be to keep it simple and stupid. In that case picking one "CD quality" preset, one "portable mp3 player" preset, and one "voice" preset would be the way to go. - Finally, the sound juicer devs (or whoever makes up these defaults) seem to be biased towards lower bitrates/qualities; the current "CD quality" preset attempts to use VBR quality 6, in which most people could clearly hear the artifacts giving good enough listening conditions. - Anyway, to stay totally in line with juicer's design philosophy (however objectionable this may be), my final recommendation would be to use FiloSottile's "audio/x-raw-int,rate=44100,channels=2 ! ... ! xingmux ! id3v2mux" with the following lamemp3enc lines: "CD quality": lamemp3enc name=enc target=0 quality=2 "portable mp3 player quality": lamemp3enc name=enc target=0 quality=6 "voice quality": lamemp3enc name=enc target=1 bitrate=56 mono=true PS: I don't know why it would be needed to specify name=enc but it won't hurt and a lot of people are doing it, so it might be good for something. -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 388160] Re: user input -- mouse queuing flaw
Thanks huug for posting the workaround. What a relief! Looking at the workaround, fixing this seems trivial (ubuntu's install scripts should no longer add "Emulate3Buttons" to xorg.conf unless a a 2-button mouse is detected). Thus, it qualifies as a "papercut". Changing status back to "confirmed". ** Changed in: hundredpapercuts Status: Incomplete => Confirmed ** This bug has been marked a duplicate of bug 54191 Mouse button click delayed ** This bug is no longer a duplicate of bug 54191 Mouse button click delayed -- user input -- mouse queuing flaw https://bugs.launchpad.net/bugs/388160 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 195483] Re: Sound Juicer - MP3 quality doesn't change
Seems that I was was a bit too quick on the trigger with my "nobody takes it serious" statement. Sebastian Dröge essentially fixed the bug upstream, and I have good hopes that it won't be long before the fix comes to an Ubuntu repository near you :) -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 195483] Re: Sound Juicer - MP3 quality doesn't change
** Also affects: gstreamer via http://bugzilla.gnome.org/show_bug.cgi?id=494528 Importance: Unknown Status: Unknown -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 195483] Re: Sound Juicer - MP3 quality doesn't change
They rightly marked that bug report "resolved" because (just like here on launchpad) it was filed as a Juicer bug, while it really is a bug in the gstreamer LAME plugin, not in Juicer. The actual bug that causes all our misery is here: http://bugzilla.gnome.org/show_bug.cgi?id=494528 The problem is just that they're not taking it very seriously. ** Bug watch added: GNOME Bug Tracker #494528 http://bugzilla.gnome.org/show_bug.cgi?id=494528 ** Changed in: sound-juicer Status: Invalid => Unknown ** Changed in: sound-juicer Bugwatch: GNOME Bug Tracker #519882 => GNOME Bug Tracker #494528 -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 195483] Re: Sound Juicer - MP3 quality doesn't change
@Christian Niemeyer: I believe vbr-mean-bitrate actually requests ABR encoding, which conflicts with vbr-quality=4, the switch that requests VBR encoding. @tigerdog: Nyquist's theorem dictates that the lowpass frequency needs to be significantly lower than half of the bitrate (44100) to avoid aliasing artefacts (which can be quite severe). I believe standalone Lame internally sets the lowpass to 21000 when asked for CBR 320 (the highest quality available), to 19500 when given -V 0 (the highest VBR quality), and even lower for lower qualities. Anything higher than 21000 is considered unsafe with regard to aliasing. @everyone: knowing just how many "internal" switches LAME has and how unskillfully the defaults are set in the gstreamer plugin, it is very unlikely to find a gstreamer command line that works as intended and will pass rigorous listening tests. The issues with the above command- lines perfectly illustrate my point. The only way to fix the problem is at code level, and posting command-lines will just distract from this. -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 23573] Re: [Upstream] [hardy] OpenOffice embeds full fonts into pdf/ps files
In the spirit of open source, I would prefer the OOo developers to give the user the choice of not embedding the fonts. They can bury it in some menus and not set it by default so that it takes the users some effort to shoot themselves in the foot. That said, Ubuntu does offer a workaround: simply do File... Print... and choose "PDF" as a printer. By default, the resulting file will be dropped into the directory ~/PDF and will not contain embedded fonts. Of course, you will be missing out on OOo's fancy PDF customization options, but at least, you will have a tiny PDF file. -- [Upstream] [hardy] OpenOffice embeds full fonts into pdf/ps files https://bugs.launchpad.net/bugs/23573 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 195483] Re: Sound Juicer - MP3 quality doesn't change
Things are actually worse than they seem. As a matter of fact, LAME should only be invoked with a handful of simple "master" options (like -V4), each of which activates myriads of internal encoder parameters. Manually setting those parameters through "advanced" switches will disrupt the carefully tuned balance between the different encoder parameters, and result in substandard MP3 files. See the LAME man pages and also http://wiki.hydrogenaudio.org/index.php?title=LAME Now, the problem is, the gstreamer LAME plugin implements an large number of these "advanced" switches, and sets them all to a default value, thereby completely overriding LAME's normal mode of operation. A list of these options can be obtained by typing: gst-inspect-0.10 lame The developers of gst-plugins-ugly are even aware of this, judging by the gstlame.c source code, which is ridden with comments like this: /* FIXME 0.11: Remove all properties except the useful ones. Nobody knows what most * properties are doing and they're intended for LAME developers only. */ As a demonstration, I tried to find a combination of gstreamer lame settings that reproduce the behavior of invoking standalone LAME. After half a day of trying, I gave up. Conclusion: gstlame.c is broken. If you want to rip CDs to mp3 format on UBUNTU, use rubyripper instead of juicer http://wiki.hydrogenaudio.org/index.php?title=Rubyripper#Installation_on_Ubuntu_8.04 For the die-hards that absolutely insist on using the gstreamer LAME plugin, please be aware that the workarounds in earlier posts in this thread are flawed. Most importantly, by setting vbr-max-bitrate=256 to values lower than 320, they disregard the following recommendation from the LAME man page: The use of -B is NOT RECOMMENDED. A 128 kbps CBR bitstream, because of the bit reservoir, can actually have frames which use as many bits as a 320 kbps frame. VBR modes minimize the use of the bit reservoir, and thus need to allow 320 kbps frames to get the same flexibility as CBR streams. The best combinations of flags I could come up with in my abovementioned experiment were: If your most important goal is to minimize the risk of audible MP3 artefacts: lame name=enc mode=0 vbr=4 vbr-min-bitrate=32 vbr-max-bitrate=320 vbr-quality=0 A good trade-off between file size and quality: lame name=enc mode=1 vbr=4 vbr-min-bitrate=32 vbr-max-bitrate=320 vbr-quality=4 Note that I don't really recommend using these settings, as they don't do LAME any justice. Again, if you are serious about your mp3s, go with rubyripper or wait for the issues to be fixed in gstreamer 0.11 -- Sound Juicer - MP3 quality doesn't change https://bugs.launchpad.net/bugs/195483 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 243617] Re: [upstream] [hardy] OpenOffice OpenGL transitions don't work on amd64 nvidia
Same problem here Linux 2.6.24-19-generic #1 SMP i686 GNU/Linux name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: NVIDIA Corporation server glx version string: 1.4 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, GLX_EXT_texture_from_pixmap, GLX_ARB_multisample, GLX_NV_float_buffer, GLX_ARB_fbconfig_float client glx vendor string: NVIDIA Corporation client glx version string: 1.4 client glx extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context, GLX_SGI_video_sync, GLX_NV_swap_group, GLX_NV_video_out, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_swap_control, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_EXT_fbconfig_packed_float, GLX_EXT_texture_from_pixmap, GLX_EXT_framebuffer_sRGB GLX version: 1.3 GLX extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_video_sync, GLX_SGI_swap_control, GLX_EXT_texture_from_pixmap, GLX_ARB_multisample, GLX_NV_float_buffer, GLX_ARB_fbconfig_float, GLX_ARB_get_proc_address OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce 6200 TurboCache(TM)/PCI/SSE2 OpenGL version string: 2.1.2 NVIDIA 169.12 -snip- -- [upstream] [hardy] OpenOffice OpenGL transitions don't work on amd64 nvidia https://bugs.launchpad.net/bugs/243617 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 148511] Re: /bin/arch command missing in gutsy
To avoid breaking 3rd party shell scripts, a /bin/arch shell script that invokes "uname -m" should be made part of util-linux . ** Changed in: util-linux (Ubuntu) Status: Won't Fix => New -- /bin/arch command missing in gutsy https://bugs.launchpad.net/bugs/148511 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 148511] Re: /bin/arch command missing in gutsy
Problem is, there are a lot of applications that come with shell scripts that use /bin/arch, such as xammp, project looking glass, and MOE (the Molecular Operating Environment). Eliminating /bin/arch breaks them all. I really think the right thing to do is making the shell script that invokes "uname -m" part of util-linux . Else you'll get a lot of complaints from people using 3rd party software that relies on /bin/arch ! -- /bin/arch command missing in gutsy https://bugs.launchpad.net/bugs/148511 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 81579] Re: Penguin commad crashes
This is a duplicate of Bug #76179 Here's a thorough analysis of the bug, including workaround: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=184437 The creators of penguin-command have incorporated said workaround in their version 1.6.11: http://user.cs.tu-berlin.de/~karlb/penguin-command/ Summary: the crash is caused by playing back a faulty music file, and the workaround consists of removing the file: sudo rm /usr/share/games/penguin-command/sound/pennight.mod -- Penguin commad crashes https://bugs.launchpad.net/bugs/81579 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 76179] Re: penguin-command dies randomly
Here's a thorough analysis of the bug, including workaround: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=184437 The creators of penguin-command have incorporated said workaround in their version 1.6.11: http://user.cs.tu-berlin.de/~karlb/penguin-command/ Summary: the crash is caused by playing back a faulty music file, and the workaround consists of removing the file: sudo rm /usr/share/games/penguin-command/sound/pennight.mod -- penguin-command dies randomly https://bugs.launchpad.net/bugs/76179 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 112092] Re: Bad substituted fonts in Feisty
This bug has caused severe problems for me, as I only discovered its existence 20 minutes before having to use a Feisty machine to give a presentation that was made on Edgy using a powerpoint template. I found no better solution than exporting it to PDF on an edgy machine and using that PDF file for the presentation. It was still not perfect and I yelled at people and started late. Foo, having a newer version of your operating system make a core application behave different in a way that it can't be used anymore would make even microsoft feel ashamed. After reading the present bug description, I reverted to my edgy fonts.conf, and the problem is now solved. However, not all end-users will find this solution or be able to apply it (in time). I think it is very important for Ubuntu's PR to solve this bug. -- Bad substituted fonts in Feisty https://bugs.launchpad.net/bugs/112092 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 84591] Re: feisty 20070210/herd5 persistent mode doesn't work
Looks like I've been a bit too optimistic. I found a Herd 3 image and applied the same procedure as described by Cal. The good news is that persistence works, and that the logs written onto casper-rw indicate that most of the hardware is correctly recognized and initialized. The bad new is that I've also seen some ugly error messages passing by, and that I don't get any login prompts in the virtual terminals. Which is really bad because X fails to start as well (that happens with all Ubuntu live CDs on my laptop). Sure, I could make a customized xorg.conf file on the casper-rw filesystem and see what happens, but as copying the vmlinuz and initrd.gz files is just a dirty hack, it may not merit further effort. Besides, I'm too tired to continue. Moreover, I discovered that my casper-rw partition is too small to make persistence really useful (gconf immediately fills it). Hope you guys can work out a cleaner solution for the persitence problem, though. I'm sure it would make a lot of people very happy. -- feisty 20070210/herd5 persistent mode doesn't work https://bugs.launchpad.net/bugs/84591 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 84591] Re: feisty 20070210/herd5 persistent mode doesn't work
Cal, that's interesting. The problem was not present in Feisty Herd 3. If someone could copy vmlinuz and initrd.gz from a Herd 3 CD to /usb and /usb/casper , it may cure the problem with less side-effects than you experienced. I might even be a viable workaround altogether. It's really annoying that there seems to be no way of getting my hands on a Herd 3 image. -- feisty 20070210/herd5 persistent mode doesn't work https://bugs.launchpad.net/bugs/84591 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 84591] Re: feisty 20070210/herd5 persistent mode doesn't work
Mike, if there's anything anyone can do to help you getting that iso on bittorrent, please ask. I'm going to mail a relative a live stick monday, in the hope of getting them to use Linux, and it would be great if they could use it in persistent mode. -- feisty 20070210/herd5 persistent mode doesn't work https://bugs.launchpad.net/bugs/84591 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
