[Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 Installed 17.04 using minimal server install CD, wanted to use networkmanager to manage my interfaces, encountered this pesky bug. I had removed any mention of my wired interface in /etc/network/interfaces, and still it wouldn't show up in NetworkManager. If this is supposed to be default behavior, I do not approve. It is confusing and pretty hard to fix if you don't have the slightest idea where to look. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 561125] Re: WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()
Seems to happen in the minutes after booting. System does not become unstable. I'm running an asus eeepc 1005HA. -- WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90() https://bugs.launchpad.net/bugs/561125 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 473627] Re: Gwibber is too slow
** Changed in: gwibber (Ubuntu) Status: Fix Released = Fix Committed ** Changed in: gwibber (Ubuntu) Status: Fix Committed = Fix Released -- Gwibber is too slow https://bugs.launchpad.net/bugs/473627 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 416073] Re: [i965] [karmic][GM965] low intel graphics performance - again
Another vote for this: LSPCI returns: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GME Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) General sloppyness, worse with Firefox. I have UXA enabled in my xorg.conf, but I think that's default since Karmic? -- [i965] [karmic][GM965] low intel graphics performance - again https://bugs.launchpad.net/bugs/416073 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 360319] Re: [GM45] memory leak causes system to run out of memory (UXA/EXA)
Any estimate when this patch will be in the X-SWAT PPA ? -- [GM45] memory leak causes system to run out of memory (UXA/EXA) https://bugs.launchpad.net/bugs/360319 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 235550] [NEW] launching mpdscribble after Gnome removes desktop icons
Public bug reported: Binary package hint: mpdscribble After installing mpdscribble, gnome desktop icons don't show at first login. Logout - Login shows them. ** Affects: mpdscribble (Ubuntu) Importance: Undecided Status: New -- launching mpdscribble after Gnome removes desktop icons https://bugs.launchpad.net/bugs/235550 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 185470] Re: iwl3945 not functioning : microcode error
I updated from gutsy to hardy today, I've tried the following things: - http://ubuntuforums.org/showthread.php?p=4612681#post4612681 (didn't work) - booting to older kernel, and thus using ip() module : works So, the problem remains: I can see all Access Points in networkmanager, but connecting always fails. -- iwl3945 not functioning : microcode error https://bugs.launchpad.net/bugs/185470 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 204709] Re: [iwl3945] Intel 3945ABG wireless card stops working on Hardy upgrade
Commenting out udev rule doesn't work, but it sure fixed the wlan0_rename problem, and the little hang on bootup. -- [iwl3945] Intel 3945ABG wireless card stops working on Hardy upgrade https://bugs.launchpad.net/bugs/204709 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 204709] Re: [iwl3945] Intel 3945ABG wireless card stops working on Hardy upgrade
Confirmed ... commenting out udev rule - testing that now. -- [iwl3945] Intel 3945ABG wireless card stops working on Hardy upgrade https://bugs.launchpad.net/bugs/204709 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 210005] Re: iwl3945 fails at connecting to unprotected AP
** Attachment added: dmesg output during failure (blanked out my address) http://launchpadlibrarian.net/13008444/dmesg_output.txt -- iwl3945 fails at connecting to unprotected AP https://bugs.launchpad.net/bugs/210005 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 210005] [NEW] iwl3945 fails at connecting to unprotected AP
Public bug reported: Binary package hint: linux-ubuntu-modules-2.6.24-12-generic This is my controller: 04:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) iwconfig says: wlan0 IEEE 802.11g ESSID: Nickname: Mode:Managed Frequency:2.457 GHz Access Point: XX:XX:XX:XX:XX Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2346 B Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Worked fine in Gutsy (old kernel with ipw3945), has some quirks after I dist-upgraded to Hardy (new kernel with ilw3945). After fixing the wlan0/wlan0_rename bug described in #204709, the following still fails. I'm running a freshly reset Siemens Gigaset SE105 router, which is configured to serve as an open connection point. I can see the AP in my network manager network list, at good signal strength, but when I try to connect, it can't get authenticated. I've attached my DMESG output, which indicates something goes wrong. I get the same behaviour when I turn on WEP encryption. I tested the AP in windows and with the gutsy kernel version: all worked correctly and fast. Please note that this has nothing to do with the #185470 (iwl3945 microcode error) bug, my output is different. Also note that I can connect perfectly to my wireless router on campus, which also is an open AP. ** Affects: linux-ubuntu-modules-2.6.24 (Ubuntu) Importance: Undecided Status: New -- iwl3945 fails at connecting to unprotected AP https://bugs.launchpad.net/bugs/210005 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 146946] Re: [gutsy] Gnome settings daemon does randomly not work
I can confirm this too. Been using Gutsy for 2 weeks now, this is the first time it happened. Rebooting solved the problem. -- [gutsy] Gnome settings daemon does randomly not work https://bugs.launchpad.net/bugs/146946 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 152505] Re: gdmgreeter segfaults when XRandR is not available
Maybe this one is a duplicate of this too - not sure: https://bugs.launchpad.net/ubuntu/+bug/152780 -- gdmgreeter segfaults when XRandR is not available https://bugs.launchpad.net/bugs/152505 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 152208] Re: A recent (Oct 12) update b0rked my X setup
*** This bug is a duplicate of bug 152505 *** https://bugs.launchpad.net/bugs/152505 Maybe this one is related to this too: https://bugs.launchpad.net/ubuntu/+bug/152780 -- A recent (Oct 12) update b0rked my X setup https://bugs.launchpad.net/bugs/152208 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 152780] Re: Booting with only one screen powered on crashes X
Just tested with the new fglrx drivers / gdm that came as an update today, same problem. -- Booting with only one screen powered on crashes X https://bugs.launchpad.net/bugs/152780 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 152780] Re: Booting with only one screen powered on crashes X
Found a GDM error report which was made when I started up with only one screen powered on. ** Summary changed: - fglrx ati gutsy dual + Booting with only one screen powered on crashes X ** Tags added: ati dual fglrx gutsy ** Attachment added: gdm_error.txt http://launchpadlibrarian.net/10003819/gdm_error.txt -- Booting with only one screen powered on crashes X https://bugs.launchpad.net/bugs/152780 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 152780] Re: Booting with only one screen powered on crashes X
Sorry for the baltix GDM mess. I was just trying to add GDM to the related packages list. ** Also affects: gdm (Baltix) Importance: Undecided Status: New ** Changed in: baltix Sourcepackagename: gdm = None ** Changed in: baltix Status: New = Invalid -- Booting with only one screen powered on crashes X https://bugs.launchpad.net/bugs/152780 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 152780] fglrx ati gutsy dual
Public bug reported: What worked in feisty: fglrx driver + aticonfig --initial --dual-head ... = 2 attached monitors with each his own desktop. I have an ATI X1600 AGP 256 Mb card, with two screens attached (one AOC 7nlr and one Compaq V50, both CRT) Now, I've recently did a fresh install of Gusty. Here's how it went: -Default vesa drivers wouldn't let me set refresh rate higher than 60. Restricted drivers it was, then. -After rebooting, my X would not start. - After a long search, I found out that it did start when I just switched on my secondary monitor. I can perfectly switch it off during GDM, and work further happily on my primary screen. So in short: Screen 1 turned on, Screen 2 turned on: X starts, screen 2 in mirror mode, I can switch it off perfectly and work further, unless I need to go to the login screen again. Screen 1 turned on, Screen 2 turned off: X fails. Screen 1 turned on, Screen 2 detached: X starts and works perfectly. Here's my xorg.conf, which is a very simple one. # xorg.conf (xorg X Window System server configuration file) # # This file was generated by failsafeDexconf, using # values from the debconf database and some overrides to use vesa mode. # # You should use dexconf or another such tool for creating a real xorg.conf # For example: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files EndSection Section Module LoadGLcore Loadglx Loaddbe Loadv4l EndSection Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRules xorg Option XkbModel pc105 Option XkbLayout be EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 Option ZAxisMapping 4 5 Option Emulate3Buttons true EndSection Section Device Identifier Failsafe Device Boardname vesa Busid PCI:1:0:0 Driver fglrx Screen 0 EndSection Section Monitor Identifier Failsafe Monitor Vendorname AOC Modelname AOC SPECTRUM 7Nlr Horizsync 30.0-82.0 Vertrefresh 50.0-110.0 modeline [EMAIL PROTECTED] 25.2 640 656 752 800 480 490 492 525 -vsync -hsync modeline [EMAIL PROTECTED] 31.5 640 664 704 832 480 489 491 520 -vsync -hsync modeline [EMAIL PROTECTED] 31.5 640 656 720 840 480 481 484 500 -vsync -hsync modeline [EMAIL PROTECTED] 36.0 640 696 752 832 480 481 484 509 -vsync -hsync modeline [EMAIL PROTECTED] 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync modeline [EMAIL PROTECTED] 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync modeline [EMAIL PROTECTED] 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync modeline [EMAIL PROTECTED] 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync modeline [EMAIL PROTECTED] 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync modeline [EMAIL PROTECTED] 57.284 832 864 928 1152 624 625 628 667 -vsync -hsync modeline [EMAIL PROTECTED] 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync modeline [EMAIL PROTECTED] 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync modeline [EMAIL PROTECTED] 75.0 1024 1048 1184 1328 768 771 777 806 -vsync -hsync modeline [EMAIL PROTECTED] 65.0 1024 1048 1184 1344 768 771 777 806 -vsync -hsync modeline [EMAIL PROTECTED] 44.9 1024 1032 1208 1264 768 768 776 817 +hsync interlace +vsync modeline [EMAIL PROTECTED] 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync Gamma 1.0 EndSection Section Screen Identifier Default Screen Device Failsafe Device Monitor Failsafe Monitor Defaultdepth24 SubSection Display Depth 24 Modes [EMAIL PROTECTED] [EMAIL PROTECTED][EMAIL PROTECTED] EndSubSection EndSection Section ServerLayout Identifier Default Layout screen 0 Default Screen 0 0 Inputdevice Generic Keyboard Inputdevice Configured Mouse EndSection Section ServerFlags EndSection ** Affects: ubuntu Importance: Undecided Status: New -- fglrx ati gutsy dual https://bugs.launchpad.net/bugs/152780 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
