[Bug 198476] Re: [REGRESSION] Impossible to change LCD brightness on Thinkpad R61/T61/X61
I have also had this problem on my T61 (X3100 graphics), the fix is to add 'options thinkpad_acpi brightness_enable=1' to /etc/modprobe.d/options. brightness changing is very laggy/slow, but it works perfectly. -- [REGRESSION] Impossible to change LCD brightness on Thinkpad R61/T61/X61 https://bugs.launchpad.net/bugs/198476 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 191413] Re: network manager 'turns on' wired interface with static IP, causing it to be ifuped upon resume from sleep/hibernate
** Attachment added: interfaces http://launchpadlibrarian.net/12710794/interfaces -- network manager 'turns on' wired interface with static IP, causing it to be ifuped upon resume from sleep/hibernate https://bugs.launchpad.net/bugs/191413 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 191413] Re: network manager 'turns on' wired interface with static IP, causing it to be ifuped upon resume from sleep/hibernate
** Attachment added: syslog http://launchpadlibrarian.net/12710831/syslog -- network manager 'turns on' wired interface with static IP, causing it to be ifuped upon resume from sleep/hibernate https://bugs.launchpad.net/bugs/191413 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 191413] Re: network manager 'turns on' wired interface with static IP, causing it to be ifuped upon resume from sleep/hibernate
here's the routing tables also: before: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 134.173.192.0 * 255.255.224.0 U 0 00 wlan0 link-local * 255.255.0.0 U 1000 00 wlan0 default Wireless.Router 0.0.0.0 UG0 00 wlan0 after: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 134.173.56.0* 255.255.248.0 U 0 00 eth0 link-local * 255.255.0.0 U 1000 00 eth0 default Banshee.ST.HMC. 0.0.0.0 UG10000 eth0 default Wireless.Router 0.0.0.0 UG0 00 wlan0 default Banshee.ST.HMC. 0.0.0.0 UG10000 eth0 -- network manager 'turns on' wired interface with static IP, causing it to be ifuped upon resume from sleep/hibernate https://bugs.launchpad.net/bugs/191413 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 182250] Re: Can we turn off debug network-manager debug output
I would also love to have this option. I have usplash disabled, so on boot network manager spills huge amounts of text onto the when it starts, making it impossible to see anything else that is going on. -- Can we turn off debug network-manager debug output https://bugs.launchpad.net/bugs/182250 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 191413] [NEW] network manager 'turns on' wired interface with static IP, causing it to be ifuped upon resume from sleep/hibernate
Public bug reported: Binary package hint: network-manager in ubuntu 7.10 gutsy, I have the wired interface (eth0) set to a static IP, but not set to ifup automatically at boot as it is not normally connected. When network manager starts, it 'turns on' eth0, meaning I can see it in ifconfig, but it has no IP address or anything of that sort. Network manager then continues to bring up and connect the wireless interface (wlan0) automatically. So far so good. However, upon suspend/resume, eth0 is ifuped, and attempts to connect to the network, which there is none as it is not connected. The problem with this is that eth0 now has an entry in my routing table, which causes any address on the local network to fail to work (verified by cups failing to print, nautilus cannot connect via smb/ssh, etc.). Addresses outside the local network still work. This is due to the way the /etc/acpi/suspend.d/55 -down-interfaces.sh script works. The acpi script read what interfaces are active by looking at the output of ifconfig. Thus, it sees the supposedly 'up' eth0, and marks it as an interface to bring back on resume. Sure enough, upon resume /etc/acpi/resume.d/62-ifup.sh happily brings eth0 back up, causing the trouble outlined above. It seems to me that the way to fix this is to make network-manager not 'turn on' network interfaces it does not control. I presume the purpose of turning it on is so that NM can sense when a cable is plugged in, however this is unnecessary if NM is not managing the interface, and I expect it might save a miniscule amount of power as well. alternatively, the acpi fiup/down scripts could be made to check for the presence of a cable (or an ip?) and only ifdown/ifup those interfaces that do have one. I have verified this on two different laptops, one an HP Pavilion dv4000 with 10/100 ethernet and intel 2200bg wifi, and the other a lenovo thinkpad t61 with gigabit ethernet and intel 4965abgn wifi. I hypothesize that the reason I experience this particular phenomenon with the routing is because in this case the wired and wireless networks are on separate subnets (255.255.248.0 and 255.255.224.0 respectively), so the routing works differently than it would in most cases, where they would use the same subnet. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- network manager 'turns on' wired interface with static IP, causing it to be ifuped upon resume from sleep/hibernate https://bugs.launchpad.net/bugs/191413 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 129910] Re: tty[1-6] are active but display nothing in Gutsy
With kernel 2.6.22-13 I can get the tty's working again with: sudo modprobe fbcon sudo modprobe vga16fb I can confirm that this does bring back the terminals, but at only 800x600px. -- tty[1-6] are active but display nothing in Gutsy https://bugs.launchpad.net/bugs/129910 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
Re: [Bug 129910] Re: tty[1-6] are active but display nothing in Gutsy
On 10/6/07, MOM2007 [EMAIL PROTECTED] wrote: on my virtual pc installation i fixed the problem with the following steps: 1. sudo vi /etc/initramfs-tools/modules and add fbcon and vesafb so my /etc/initramfs-tools/modules looks like: fbcon vesafb 2. sudo update-initramfs -u 3. sudo vi /etc/modprobe.d/blacklist-framebuffer change the line blacklist vesafb to # blacklist vesafb 4. reboot and everything is fine HTH MOM This works perfectly for me, thanks! -- tty[1-6] are active but display nothing in Gutsy https://bugs.launchpad.net/bugs/129910 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 122421] Re: Unable to purge package
I can also replicate this behovior, the only way to purge ubuntu-modules is to reinstall the corresponding linux-image before removal. (or remove the postrm in /var/lib/dpkg but that's nasty). Also, bug 138552 appears to be a duplicate of this: https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu- modules-2.6.22/+bug/138552 -- Unable to purge package https://bugs.launchpad.net/bugs/122421 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 135613] Re: Framebuffer consoles no not work in gutsy
I also have this problem, on an Intel 915GM graphics chip. Framebuffer works fine without vga=, but with it, just blackness. Xorg still works fine at full resolution. -- Framebuffer consoles no not work in gutsy https://bugs.launchpad.net/bugs/135613 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 135613] Re: Framebuffer consoles no not work in gutsy
Forum thread on this issue: http://ubuntuforums.org/showthread.php?p=3331275 Adding fbcon to /etc/initramfs-tools/modules as suggested in the thread fixes it for me. -- Framebuffer consoles no not work in gutsy https://bugs.launchpad.net/bugs/135613 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 124513] compiz does not install cube.h and scale.h
Public bug reported: Binary package hint: compiz In compiz_0.5.1+git20070703-0ubuntu2, the cube.h and scale.h header files are not installed into the compiz-dev package. This causes building of compiz-fusion-plugins-main and -extra to fail, in the scaleaddons and cubereflection plugins respectively. I discovered this while trying to backport them to feisty using pbuilder, but I have checked the gutsy compiz-dev package and it also does not have the cube.h or scale.h files, and it also appears that scaleaddons and cubereflection are not built in their respective packages, even though their .xml description file is. ** Affects: compiz (Ubuntu) Importance: Undecided Status: New -- compiz does not install cube.h and scale.h https://bugs.launchpad.net/bugs/124513 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 93701] Re: Evince: Printing a password protected pdf is not possible
It's not fixed in feisty, I have this exact same problem. Printing to pdf/ps and then printing that works fine, but it really shouldn't be necessary to do that. -- Evince: Printing a password protected pdf is not possible https://bugs.launchpad.net/bugs/93701 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 90749] Re: Deluge 0.5 in feisty
I have to agree. 0.4, while functional, has some serious flaws. Upgrading to 0.5 would be a significant improvement, even with bugs. -- Deluge 0.5 in feisty https://launchpad.net/bugs/90749 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56850] Re: After restart b and n keys do not work, dell latitude d610
No, this issue does not seem to affect me anymore. I am using edgy now. -- After restart b and n keys do not work, dell latitude d610 https://launchpad.net/bugs/56850 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56850] Re: After restart b and n keys do not work, dell latitude d610
I also have this exact problem, except wiht the b and f keys. I'm using an HP pavilion dv4000. -- After restart b and n keys do not work, dell latitude d610 https://launchpad.net/bugs/56850 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
