Ah, it seems to be just U2D which I was testing earlier today. I too can file all the bugs I want against ’unity’, but if I try `ubuntu-bug unity-2d` all I get is the ”third party package” error. Reproduced this also in a clean VM to be sure.
With Unity updated from the PPA, you cannot file bugs against it using ubuntu-bug, you’ll just get an error message saying ”Please remove any third party package and try again.” You can still file bugs directly on Launchpad using the browser, but then the report won’t have the logs attached to it.
More accurate upstream target; previous was fixed but didn’t fix the issue reported here.
This has been fixed upstream ages ago, how come the fix never made it to Ubuntu? I’m using up-to-date Precise and this is still an issue: scrollwheel still browses between pictures instead of panning the current picture.
Confirming the issue of not being able to get rid of indicator-messages apart from uninstalling it system-wide, but not agreeing with stuffing the menu with another item just for solving this. IMHO Indicator-messages should be de-/selectable in Startup Applications preferences (like indicator-multiload for instance is).
According to an answer on Ask Ubuntu [1], blacklisting all message-providers should hide indicator-messages altogether, but this doesn’t seem to work in 12.04, apparently because status-providers (which are different from message-providers) are still using the menu. (U1 Control Panel also seems to still occupy it despite being blacklisted.)
I’ve even tried overriding indicator-messages’ dbus service file with a hackish solution [2], but the envelope still insists on appearing (though without the associated menu).
* [1] http://askubuntu.com/a/15616/34756
* [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544483#42
jani@amilo:~$ LC_ALL=C aptitude show linux-image-3.2.0-14-generic-pae | grep ”more then”
Geared toward 32 bit desktop systems with more then 4GB RAM.
I believe the fix is to ’s/more then/more than/’ in DEBIAN/control.
Hi komputes.
The difference between a normal boot and a recovery mode boot is (among other things) in the parameters that are passed on to the Linux kernel. A normal boot uses Kernel Based Mode-setting (KMS) whereas in recovery mode KMS is turned off by default to make sure it causes no problems in case recovery mode is needed.
From the Release Notes of Ubuntu 10.04:
”Ubuntu 10.04 LTS enables the new kernel-mode-setting (KMS) technology by default on most common video chipsets. While this is a major step forward for the graphics architecture in Ubuntu, in some rare cases KMS will prevent your video output from working correctly, or from working at all. If you need to disable KMS, you can do so by booting with the nomodeset option.” https://wiki.ubuntu.com/LucidLynx/ReleaseNotes#Working_around_bugs_in_the_new_kernel_video_architecture
I believe the nomodeset parameter is behind the low graphics mode you’re seeing in recovery mode and therefore intentional, as visually unappealing as it may be.
I have two computers affected by this and one that is not, each running Precise. I’ve tracked down the cause, but I’m not sure which of the components involved (friendly-recovery, resolvconf, postfix and upstart) is the culprit, so I’ll file this for friendly-recovery which is at least severly affected. Feel free to correct the target with better insight.
Steps to reproduce:
0. Have the ’postfix’ and ’resolvconf’ packages installed.
1. Boot into recovery mode.
What happens:
The boot proceeds in nonsplash (text) mode, but in the end the recovery menu fails to show up. Instead the graphical greeter is brought up.
What I expect to happen:
For the recovery menu to show up so I can use it.
The cause:
For debugging this, I first enabled logging for friendly-recovery.conf. That log implicated resolvconf, so I enabled logging for resolvconf, and that in turn revealed this:
cp: cannot create regular file `/var/spool/postfix/etc/resolv.conf’: Read-only file system
So I checked, and indeed postfix wasn’t there on my laptop which wasn’t affected. It seems that due to the read-only file system, the resolvconf upstart job fails, which in turn leads to the resolvconf-dependent friendly-recovery job to also fail.
The workaround:
Uninstall postfix if you can afford to.
Bug #751265 describes the symptom: when VLC uses Pulseaudio for audio output, the sound from it becomes garbled after playing for a while, with heavy digital artefacts and echoing. Comment #23 in that report suggests modifying /etc/pulse/default.pa so that load-module module-udev-detect is followed by tsched=0. I’ve done that, and with it VLC seems to work fine with Pulseaudio. Furthermore, in comment #30 @David Henningsson prompted us suffering from this and with the tsched=0 workaround working to file our own reports for each specific hardware. This is my report.
I believe apport adds data about the hardware automatically. I’ll add to that that for me this only occurs with the Radeon HDMI output; through the analog output (via headphones) the audio works fine. As Bug #864735 describes, Radeon audio is off by default in recent kernels, but I’ve re-enabled it by passing the radeon.audio=1 kernel commandline parameter.
If I switch to ALSA output for VLC (without tsched=0), VLC audio goes mute after a while. After some time of silence it sort of fast forwards itself to get up to sync with the video again. This keeps repeating, so it’s not really a workaround.
After selecting netroot from the friendly menu, I do get root but no network: only the loop interface is up. This happens even though the laptop has in fact both wired and wireless net, both of which do work on the system after a normal boot.
If I run ifconfig eth0 up and dhclient eth0 on the prompt, the wired interface comes up fine, so that’s a workaround.
Bug #572426 seems to have been repurposed for something that could make this a duplicate of that. Bug #868748 also describes something similar, but this isn’t just about not getting an IP address; the interfaces (apart from lo) aren’t brough up automatically at all.