[Bug 102783] Re: Backlight not auto adjusting to power mode change
Thanks for the friendly response! I tried a live cd of alpha 4 and the auto dimming was working perfectly when unplugging/plugging in AC power. I did however notice things weren't exactly perfect - after manually readjusting the brightness to make it brighter when on battery power it would randomly dim itself again but I couldn't find any real pattern to it. Should I retest with the next alpha or is there somewhere I can look to provide a log of why its doing it? -- Backlight not auto adjusting to power mode change https://bugs.launchpad.net/bugs/102783 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 115002] Firefox opens new window instead of new tab
Public bug reported: Binary package hint: firefox Using Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty) Seems there is a bug within preferences - tabs - New pages should be opened in: Mine was set to a new tab (by default from memory?) however I was slowly going crazy wondering why new windows would often be opened instead of a new tab when following links. Forum search showed others experiencing this, along with the workaround for the preferences glitch: http://ubuntuforums.org/showthread.php?t=404993 Setting it to open in a new Window, then back to New Tab will the correctly set the about:config parameter browser.link.open_newwindow to 3 Another user reported that simply reclicking the already selected option of New Tab will also have the desired effect. ** Affects: firefox (Ubuntu) Importance: Undecided Status: Unconfirmed -- Firefox opens new window instead of new tab https://bugs.launchpad.net/bugs/115002 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 102783] Backlight not auto adjusting to power mode change
Public bug reported: Binary package hint: gnome-power-manager Running a fully up to date Feisty on a Compaq F503AU. Experiencing a small issue with power management in that when I remove AC power my backlight will not automatically dim. However if I suspend my laptop and wake it back up it will then detect there is no AC power and dim the backlight. Same for the reverse - if I now plug in AC power it wont automatically brighten the backlight, however if I suspend and wake again, it will detect there is AC power and brighten the backlight. So it seems its only really checking when waking up? I haven't tried Edgy on this laptop before so not sure if its a new bug. The battery applet pops up and notifies me Im running on battery power so it's obviously detecting it fine. Function keys to increase/decrease backlight work flawlessly (so its no biggy to manually readjust), as does suspend/resume - so very nearly 100% on the ACPI front for this laptop :) btw happy to upload any relevant logs or output of commands. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: Unconfirmed -- Backlight not auto adjusting to power mode change https://bugs.launchpad.net/bugs/102783 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 99291] fails to detect nVidia GeForce Go 6100
Public bug reported: Binary package hint: restricted-manager Using 0.17 lspci | grep VGA 00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express Bridge (rev a2) lspci -n | grep 0300 00:05.0 0300: 10de:0247 (rev a2) ** Affects: restricted-manager (Ubuntu) Importance: Undecided Status: Unconfirmed -- fails to detect nVidia GeForce Go 6100 https://launchpad.net/bugs/99291 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87748] Re: Easy-Codec-Installation shows only-supported-applications by default (and no codecs)
One of the first things I tested when I installed the beta was the Easy- Codec-Installation as I've been interested and following its development. I tried what I thought the average new user might experience - I double clicked and mp3 file. I was happy to not see the usual non helpful totem error appear, and to see the Add/Remove Applications dialogue load and start searching. Unfortunately the search returned nothing. Not exactly a helpful first time experience as the below user found when discussing this in the forums: Quote: Usually, when I doubleclick on an mp3 file in Nautilus it starts searching for appropriate application and then Add/Remove Applications dialog pops up, there is 0.10:decoder-audio/mpeg in search box and on the bottom of the dialog it says There is no matching application available. A few times it wasn't searching for anything and just told me that I need a MPEG-1 Layer 3 (MP3) decoder in order to play file. Nothing else. It didnt take me long to realise that the show option box was by default set to Supported Ubuntu applications (thats from memory) I know I had to change it to All available applications for the codecs to appear. After I informed them of this on the forum they then replied: Somehow I never noticed that option box in Add/Remove dialog! So it seems it's not the most intuitive - I always thought this about that default search option for gnome-app-install in previous releases but assumed it was made that way to encourage people only to install supported/stable packages but always felt it was a bit misleading for new users. Time to review this perhaps? -- Easy-Codec-Installation shows only-supported-applications by default (and no codecs) https://launchpad.net/bugs/87748 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93209] Re: Fails to detect Nvidia 3D driver
same here on my laptop with a nvidia GeForce Go 6100 00:05.0 VGA compatible controller: nVidia Corporation C51 PCI Express Bridge (rev a2) 00:05.0 0300: 10de:0247 (rev a2) 0.12 attached above didn't seem to fix it. -- Fails to detect Nvidia 3D driver https://launchpad.net/bugs/93209 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86666] Re: Feisty crashes after grub if usplash enabled (amd64)
just to confirm that I also experienced this with the Beta release. Adding vga=792 to the appropriate pleces in /boot/grub/menu.lst did the trick for me. My laptop is an AMD64 with a nvidia GeForce Go 6100 but I am running 32 bit Feisty, so maybe this isnt the right bug to comment on. The 32 bit live CD would hang for me if I just let it load with defaults, but if I specified a resolution using F4 it would load. -- Feisty crashes after grub if usplash enabled (amd64) https://launchpad.net/bugs/8 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94690] Vista NTFS partition unbootable after resize
Public bug reported: I tried to install Edgy on a new laptop (Compaq Presario F503au) that came preloaded with Vista. I figured I would do my usual thing and just shrink the NTFS partition during install so I can dual boot. I don't remember getting an error message but it seems the resize rendered my Vista partition unbootable, it would just hang halfway through booting, and I couldn't even get into Safe Mode etc. I smuggly grabbed my recovery DVD I made before the install thinking this would save me, but even that would hang during boot. Grub picked up the recovery partition but also no dice booting that. Couple that with the fact that HP/Compaq dont give you the Vista install media and xorg on Edgy now couldnt detect my screen after the install, I was left with one dead new laptop. In the end I managed to to get the recovery parition to work by using the edgy live cd to delete the corrupted vista NTFS parition and recreating a new clean NTFS partition - I figured it would need a working partition to restore to. Anyway after some quick forum searching I found these threads: http://ubuntuforums.org/showthread.php?t=386850 http://ubuntuforums.org/showthread.php?t=383132 I thought more people might've experienced this - is it possible to confirm that resizing a Vista NTFS partition during install with Edgy will kill Vista? If so there really should be a warning on the download page for Edgy as more and more people will be getting Vista with their new machines (although Im aware this might help fix Bug #1 ;) ). Im hoping the new version of ntfsresize shipping with Feisty mentioned in Bug #86231 with a similar problem will fix this. ** Affects: linux-ntfs (Ubuntu) Importance: Undecided Status: Unconfirmed -- Vista NTFS partition unbootable after resize https://launchpad.net/bugs/94690 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94690] Re: Vista NTFS partition unbootable after resize
** Description changed: I tried to install Edgy on a new laptop (Compaq Presario F503au) that came preloaded with Vista. I figured I would do my usual thing and just - shrink the NTFS partition during install so I can dual boot. I don't - remember getting an error message but it seems the resize rendered my - Vista partition unbootable, it would just hang halfway through booting, - and I couldn't even get into Safe Mode etc. + shrink the NTFS partition during install so I can dual boot. In + hindsight I was quite naive, as no doubt NTFS has changed a lot under + Vista. I don't remember getting an error message but it seems the + resize rendered my Vista partition unbootable, it would just hang + halfway through booting, and I couldn't even get into Safe Mode etc. I smuggly grabbed my recovery DVD I made before the install thinking this would save me, but even that would hang during boot. Grub picked up the recovery partition but also no dice booting that. Couple that with the fact that HP/Compaq dont give you the Vista install media and xorg on Edgy now couldnt detect my screen after the install, I was left with one dead new laptop. In the end I managed to to get the recovery parition to work by using the edgy live cd to delete the corrupted vista NTFS parition and recreating a new clean NTFS partition - I figured it would need a working partition to restore to. Anyway after some quick forum searching I found these threads: http://ubuntuforums.org/showthread.php?t=386850 http://ubuntuforums.org/showthread.php?t=383132 I thought more people might've experienced this - is it possible to confirm that resizing a Vista NTFS partition during install with Edgy will kill Vista? If so there really should be a warning on the download page for Edgy as more and more people will be getting Vista with their new machines (although Im aware this might help fix Bug #1 ;) ). Im hoping the new version of ntfsresize shipping with Feisty mentioned in Bug #86231 with a similar problem will fix this. ** Tags added: vista -- Vista NTFS partition unbootable after resize https://launchpad.net/bugs/94690 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69176] No notification in Ubiquity for bad sectors
Public bug reported: Installing Edgy on an IBM A22m Thinkpad, Ubiquity would seemingly hang when either: a) attempting to resize an NTFS partition for the install or b) halfway though copying files if / partition already created before running desktop installer Looking in syslog I noticed ubiquity was detecting bad sectors on the HDD, but it does not relay this information to the end user. Using the alternate CD for the install, a large red box will appear telling the user that the HDD is bad, as opposed to just hanging. I think notifying the user via the UI that bad sectors have been found would at least help the user know why the installer has hung. Oddly enough Windows will happily install and run on this HDD, even though chkdsk will consistently find errors/bad sectors.. I guess Linux is a little more picky on what it will install on? ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: Unconfirmed -- No notification in Ubiquity for bad sectors https://launchpad.net/bugs/69176 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69176] Re: No notification in Ubiquity for bad sectors
attached is the syslog from an install that attempted to resize the NTFS partion of /dev/hda1 ** Attachment added: syslog http://librarian.launchpad.net/4940201/syslog -- No notification in Ubiquity for bad sectors https://launchpad.net/bugs/69176 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48077] Re: Running nvidia-glx-config enable breaks X.
Same thing here (fully updated edgy), sudo nvidia-glx-config enable generated a bad xorg.conf breaking X. It set the wrong BusID to the same bad value as others mention : PCI:0:5:0 - mine is supposed to be PCI:2:0:0 It also completely lost all my monitor resolutions, setting to the same low defaults as above. I now remember this also happened with Dapper - installing nvidia drivers using this same method walked flawlessly with Hoary, Warty and Breezy over the years Its a fairly major breakage, and I've got quite common hardware so I would think it would be more common than this... vid card: NV17 [GeForce4 MX 440] mobo: Gigabyte GA 7N400 PRO2 (nForce 2) -- Running nvidia-glx-config enable breaks X. https://launchpad.net/bugs/48077 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48077] Re: Running nvidia-glx-config enable breaks X.
actually Bug #44379 reporter also has nForce2 board (rubs chin) -- Running nvidia-glx-config enable breaks X. https://launchpad.net/bugs/48077 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58956] default depth too high in xorg.conf for Neomagic MagicGraph 256AV
Public bug reported: After installing xubuntu on an old 390X IBM Thinkpad, the display was very slow updating, with scrolling and window moving painfully glitchy. This behaviour was not evident in Windows XP on this laptop, nor other Linux distros. The laptop has a (according to xorg.conf) NeoMagic Corporation NM2200 [MagicGraph 256AV] using the neomagic driver and on my install was configured to use a DefaultDepth of 24bit. After checking another distros install on this hardware(in which this display updated smoothly) I noticed its default depth was set to 16. I then modified xorg.conf to DefaultDepth 16 in xubuntu, restarted X and now display is smooth. After googling it seems the chip does support 24bit, however the performance is poor. Therefore I think default should be 16 for this chip as often xubuntu is suggested as a good distro for lower spec machines, but initial impressions are that the hardware is not up to it. I believe this chipset may be quite common with older laptops. ** Affects: Ubuntu Importance: Untriaged Status: Unconfirmed -- default depth too high in xorg.conf for Neomagic MagicGraph 256AV https://launchpad.net/bugs/58956 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
