[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
I must be missing it; I see the bugs.txt which looks like output, but I don't see a patch attached? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: In Progress Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1502635] Re: bonded interface not starting automatically
Looking at the error above... I think I see one issue... in /sys/class/net/, bonding_masters is a file, not a folder. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: New Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1502635] [NEW] bonded interface not starting automatically
Public bug reported: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1502635 Title: bonded interface not starting automatically Status in network-manager package in Ubuntu: New Bug description: Upgraded over 15.04 to 15.10 Final Beta. Have a LACP bonded interface with two NICs. Using NetworkManager to handle the NIC bonding. After upgrading to 15.10, the bond0 interface no long auto starts when the system comes up. If I manually do a ifconfig bond0 up, it will start. As a workaround I added this to rc.local, but not sure where to look to see why it's failing in 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-12.14-generic 4.2.1 Uname: Linux 4.2.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 4 10:43:06 2015 InstallationDate: Installed on 2012-12-18 (1019 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JournalErrors: No journal files were found. -- No entries -- NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: syspath not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2015-10-03 (0 days ago) WifiSyslog: mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-10-03T20:26:36.767583 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1502635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared
Any hope that the bugs fixed in this thread may be related: http://www.reddit.com/r/Ubuntu/comments/2xowuc/looks_like_the_very_long_standing_nvidia_bug/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared Status in xorg package in Ubuntu: Incomplete Bug description: As requested in Bug #1310633 I'm opening a new bug. With a previous version of Ubuntu I already had this flickering. With additional options for the kernel module I was able to fix the flickering. options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0 With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the flickering reappeared although the line is still present in options.conf. Using modprobe --resolve-alias nvidia I found the correct driver module name which in my case is nvidia_331. Changing the module name in options.conf to nvidia_331 X doesn't start anymore. Removing the NVreg_ModifyDeviceFiles option X is starting again, but does not solve the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Tue Apr 29 21:09:41 2014 DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1521] InstallationDate: Installed on 2012-11-17 (528 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP EliteBook 8540w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CVD Ver. F.24 dmi.board.name: 1521 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 32.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8540w dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 29 21:06:04 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared
@penalvch many of us are using different hardware vendors so I don't believe this is an HP bios thing at all. I've got a GIGABYTE GA-Z77X- UP5 TH Z77 motherboard running the latest bios. My video card is a nVidia GeForce GTX 570 and I've been trying both release and beta NVIDIA binary drivers on with the same flickering problems (terminal being the worst offender) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared Status in xorg package in Ubuntu: Incomplete Bug description: As requested in Bug #1310633 I'm opening a new bug. With a previous version of Ubuntu I already had this flickering. With additional options for the kernel module I was able to fix the flickering. options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0 With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the flickering reappeared although the line is still present in options.conf. Using modprobe --resolve-alias nvidia I found the correct driver module name which in my case is nvidia_331. Changing the module name in options.conf to nvidia_331 X doesn't start anymore. Removing the NVreg_ModifyDeviceFiles option X is starting again, but does not solve the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Tue Apr 29 21:09:41 2014 DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1521] InstallationDate: Installed on 2012-11-17 (528 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP EliteBook 8540w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CVD Ver. F.24 dmi.board.name: 1521 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 32.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8540w dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 29 21:06:04 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
@Rob A - Thanks for the follow-up! I can confirm on 14.04 it's also working well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in “lightdm” package in Ubuntu: Confirmed Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes /usr/sbin/lightdm- session: 5: exec: init: not found - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to init in the .xsession-errors. First of them is init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1178505] Re: NetworkManager reverts all bond modes to balanced-rr
I just upgraded to 14.04, and can confirm I can configure thru Network Manager LACP and appears to be functioning correctly. I am no longer forced to use Round Robin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1178505 Title: NetworkManager reverts all bond modes to balanced-rr Status in “network-manager” package in Ubuntu: Triaged Bug description: Description:Ubuntu 13.04 Release:13.04 network-manager: Installed: 0.9.8.0-0ubuntu6 Candidate: 0.9.8.0-0ubuntu6 Version table: *** 0.9.8.0-0ubuntu6 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status I am attempting to use the new bonding interface in NetworkManager in 13.04. NetworkManager will not write any other mode than Round- robin to the configuration file. For example I can choose Active Backup when editing the bond, save and close the NetworkManager. When I open it again, the mode is once again set to Round-robin and not my previously checked Active Backup when I closed NetworkManager. Also if I edit /etc/NetworkManager/system-connections/Bond\ Connection\ 1 by hand to have any other mode, NetworkManager resets the value on open of the application. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu May 9 18:53:36 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-10-02 (219 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via ###.###.###.### dev bond0 proto static ###.###.###.###/24 dev bond0 proto kernel scope link src ###.###.###.### metric 5 169.254.0.0/16 dev eth0 scope link metric 1000 MarkForUpload: True NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: device path not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-05-09 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH bond0 slave 2 9fb3fe4a-b24f-4a97-84d6-b72bf7c3d8e3 802-3-ethernet1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/2 MSFF 6e10a816-5b2a-4e88-93c5-bf70483fe6a5 vpn 1360882873 Thu 14 Feb 2013 03:01:13 PM PSTnono /org/freedesktop/NetworkManager/Settings/1 Bond connection 1 57d726f0-663a-40f5-86da-96befb80dd77 bond 1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/0 bond0 slave 1 55b7fab4-00bd-4468-bcbf-123cfd12bcc8 802-3-ethernet1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/2 bond0 bond connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1178505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1178505] Re: NetworkManager reverts all bond modes to balanced-rr
Just installed a VM with the current 14.04 Beta that has NetworkManager 0.9.8.8 and it looks like the settings may be retained now (looks like may have been fixed in NM 0.9.8.4 looking at the release notes.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1178505 Title: NetworkManager reverts all bond modes to balanced-rr Status in “network-manager” package in Ubuntu: Triaged Bug description: Description:Ubuntu 13.04 Release:13.04 network-manager: Installed: 0.9.8.0-0ubuntu6 Candidate: 0.9.8.0-0ubuntu6 Version table: *** 0.9.8.0-0ubuntu6 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status I am attempting to use the new bonding interface in NetworkManager in 13.04. NetworkManager will not write any other mode than Round- robin to the configuration file. For example I can choose Active Backup when editing the bond, save and close the NetworkManager. When I open it again, the mode is once again set to Round-robin and not my previously checked Active Backup when I closed NetworkManager. Also if I edit /etc/NetworkManager/system-connections/Bond\ Connection\ 1 by hand to have any other mode, NetworkManager resets the value on open of the application. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu May 9 18:53:36 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-10-02 (219 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via ###.###.###.### dev bond0 proto static ###.###.###.###/24 dev bond0 proto kernel scope link src ###.###.###.### metric 5 169.254.0.0/16 dev eth0 scope link metric 1000 MarkForUpload: True NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: device path not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-05-09 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH bond0 slave 2 9fb3fe4a-b24f-4a97-84d6-b72bf7c3d8e3 802-3-ethernet1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/2 MSFF 6e10a816-5b2a-4e88-93c5-bf70483fe6a5 vpn 1360882873 Thu 14 Feb 2013 03:01:13 PM PSTnono /org/freedesktop/NetworkManager/Settings/1 Bond connection 1 57d726f0-663a-40f5-86da-96befb80dd77 bond 1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/0 bond0 slave 1 55b7fab4-00bd-4468-bcbf-123cfd12bcc8 802-3-ethernet1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/2 bond0 bond connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1178505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1178505] Re: NetworkManager reverts all bond modes to balanced-rr
Looking better: cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: down MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: slow Min links: 0 Aggregator selection policy (ad_select): stable bond bond0 has no active aggregator -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1178505 Title: NetworkManager reverts all bond modes to balanced-rr Status in “network-manager” package in Ubuntu: Triaged Bug description: Description:Ubuntu 13.04 Release:13.04 network-manager: Installed: 0.9.8.0-0ubuntu6 Candidate: 0.9.8.0-0ubuntu6 Version table: *** 0.9.8.0-0ubuntu6 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status I am attempting to use the new bonding interface in NetworkManager in 13.04. NetworkManager will not write any other mode than Round- robin to the configuration file. For example I can choose Active Backup when editing the bond, save and close the NetworkManager. When I open it again, the mode is once again set to Round-robin and not my previously checked Active Backup when I closed NetworkManager. Also if I edit /etc/NetworkManager/system-connections/Bond\ Connection\ 1 by hand to have any other mode, NetworkManager resets the value on open of the application. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu May 9 18:53:36 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-10-02 (219 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via ###.###.###.### dev bond0 proto static ###.###.###.###/24 dev bond0 proto kernel scope link src ###.###.###.### metric 5 169.254.0.0/16 dev eth0 scope link metric 1000 MarkForUpload: True NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: device path not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-05-09 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH bond0 slave 2 9fb3fe4a-b24f-4a97-84d6-b72bf7c3d8e3 802-3-ethernet1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/2 MSFF 6e10a816-5b2a-4e88-93c5-bf70483fe6a5 vpn 1360882873 Thu 14 Feb 2013 03:01:13 PM PSTnono /org/freedesktop/NetworkManager/Settings/1 Bond connection 1 57d726f0-663a-40f5-86da-96befb80dd77 bond 1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/0 bond0 slave 1 55b7fab4-00bd-4468-bcbf-123cfd12bcc8 802-3-ethernet1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/2 bond0 bond connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1178505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1178505] Re: NetworkManager reverts all bond modes to balanced-rr
I am still seeing this in 13.10 as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1178505 Title: NetworkManager reverts all bond modes to balanced-rr Status in “network-manager” package in Ubuntu: Triaged Bug description: Description:Ubuntu 13.04 Release:13.04 network-manager: Installed: 0.9.8.0-0ubuntu6 Candidate: 0.9.8.0-0ubuntu6 Version table: *** 0.9.8.0-0ubuntu6 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status I am attempting to use the new bonding interface in NetworkManager in 13.04. NetworkManager will not write any other mode than Round- robin to the configuration file. For example I can choose Active Backup when editing the bond, save and close the NetworkManager. When I open it again, the mode is once again set to Round-robin and not my previously checked Active Backup when I closed NetworkManager. Also if I edit /etc/NetworkManager/system-connections/Bond\ Connection\ 1 by hand to have any other mode, NetworkManager resets the value on open of the application. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu May 9 18:53:36 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-10-02 (219 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via ###.###.###.### dev bond0 proto static ###.###.###.###/24 dev bond0 proto kernel scope link src ###.###.###.### metric 5 169.254.0.0/16 dev eth0 scope link metric 1000 MarkForUpload: True NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: device path not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-05-09 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH bond0 slave 2 9fb3fe4a-b24f-4a97-84d6-b72bf7c3d8e3 802-3-ethernet1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/2 MSFF 6e10a816-5b2a-4e88-93c5-bf70483fe6a5 vpn 1360882873 Thu 14 Feb 2013 03:01:13 PM PSTnono /org/freedesktop/NetworkManager/Settings/1 Bond connection 1 57d726f0-663a-40f5-86da-96befb80dd77 bond 1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/0 bond0 slave 1 55b7fab4-00bd-4468-bcbf-123cfd12bcc8 802-3-ethernet1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/2 bond0 bond connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1178505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
Ok, I may have a workaround (not sure yet of any side effects or what else could be broken...) Since we did the symlink to /bin/init, this is what .Xsession looks like as we know: init: unity-gtk-module main process (3055) terminated with status 127 init: logrotate pre-start process (3053) terminated with status 127 init: dbus pre-start process (3056) terminated with status 127 init: ssh-agent pre-start process (3054) terminated with status 127 init: ssh-agent post-stop process (3062) terminated with status 127 If you look at ~/.cache/upstart as your LDAP based user, you'll notice in log files for dbus, etc for errors, sure enough the error is it can't find initctl: /proc/self/fd/9: 3: /proc/self/fd/9: initctl: not found /proc/self/fd/9: 3: /proc/self/fd/9: initctl: not found /proc/self/fd/9: 3: /proc/self/fd/9: initctl: not found I added a symlink from /sbin/initctl to /bin like we did with init, and I am now able to log in again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in “lightdm” package in Ubuntu: Confirmed Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes /usr/sbin/lightdm- session: 5: exec: init: not found - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to init in the .xsession-errors. First of them is init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
After I put in the symlink for initctl into /bin path above and could log in, I ran into an issue where I was having odd errors like not authorized in the disk tool, and Network settings within UI were inaccessible, etc This is beyond the other weird issues with the path stuff from above... I found an old bug here: https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/1162836 I had the same problem where after I finally logged in, my $PATH variable was a ways off from what the local user. Per that bug, I updated /etc/pam.d/common-session and made the following change the line: session sufficient pam_lsass.so to: session [success=ok default=ignore] pam_lsass.s After a reboot, my path was ok, and everything seems to be working as normal again. I am going to test removing the symlinks that were added, as I suspect with the path fixed, they may not be needed. I will report back what I find. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in “lightdm” package in Ubuntu: Confirmed Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes /usr/sbin/lightdm- session: 5: exec: init: not found - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to init in the .xsession-errors. First of them is init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
No symlinks needed for init or initctl and able to log in using pbis as a domain user with the common-session change. Is this a bug with Ubuntu or pbis? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in “lightdm” package in Ubuntu: Confirmed Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes /usr/sbin/lightdm- session: 5: exec: init: not found - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to init in the .xsession-errors. First of them is init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
Also noticed if I log in via terminal as a domain user, stop lighdm, run startx, desktop comes up (but no indicator panel on bar.) I should have also noted in the previous post I was on 13.04 and it worked fine, and didn't have any problems until upgrading to 13.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in “lightdm” package in Ubuntu: Incomplete Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes /usr/sbin/lightdm- session: 5: exec: init: not found - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to init in the .xsession-errors. First of them is init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
Hmm, I wonder if this could be some odd path issue, status 127 means command not found. Also would explain why we had to do the symbolic link for /sbin/init . $PATH getting squashed somehow? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in “lightdm” package in Ubuntu: Incomplete Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes /usr/sbin/lightdm- session: 5: exec: init: not found - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to init in the .xsession-errors. First of them is init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
I'm also seeing this on Gnome Ubuntu as well after staging up a VM to test it. I have to do the sym link to init, and then once i log in, get the black screen with a cursor. Not looking like a lightdm issue now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in “lightdm” package in Ubuntu: Confirmed Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes /usr/sbin/lightdm- session: 5: exec: init: not found - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to init in the .xsession-errors. First of them is init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228079] Re: Login issue: Lightdm + LDAP + Kerberos
I believe I am seeing the same problem. I use pbis-open for integration with Active DIrectory. If I log in as a local user, works fine. However if I login as a user on the domain, I see the identical problems and errors in the log as ernst-l. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1228079 Title: Login issue: Lightdm + LDAP + Kerberos Status in “lightdm” package in Ubuntu: Incomplete Bug description: lightdm 1.7.15-0ubuntu1, Ubuntu 13.10 - Local users can login without problems on command line and LightDM - Kerberos/LDAP authenticated users can login on command line - Kerberos/LDAP authenticated users cannot login with LigthDM. If you provide a valid user/password the screen gets blank before you return to the login screen. The .xession-errors includes /usr/sbin/lightdm- session: 5: exec: init: not found - If you add init to the users path (e.g., ln -s /sbin/init /bin/init) the user does no longer return back to LightDM but gets a blank screen. Several errors related to init in the .xsession-errors. First of them is init: Failed to spawn upstart-file-bridge main process: unable to execute: No such file or directory .xession-errors for both setup attached to this bug report No problems with Ubuntu 12.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.7.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Date: Fri Sep 20 12:21:13 2013 InstallationDate: Installed on 2013-09-20 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130917) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1228079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1178505] Re: NetworkManager reverts all bond modes to balanced-rr
Does anyone know a good work around? If I manual edit the config file for bond0 in /etc/NetworkManager/system-connections and set it to mode=802.3ad or mode=4, it keeps the change (obviously until I try to make a change in NetworkManager again), however interface is still set to round-robin regardless: cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: load balancing (round-robin) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1178505 Title: NetworkManager reverts all bond modes to balanced-rr Status in “network-manager” package in Ubuntu: Confirmed Bug description: Description:Ubuntu 13.04 Release:13.04 network-manager: Installed: 0.9.8.0-0ubuntu6 Candidate: 0.9.8.0-0ubuntu6 Version table: *** 0.9.8.0-0ubuntu6 0 500 http://us.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status I am attempting to use the new bonding interface in NetworkManager in 13.04. NetworkManager will not write any other mode than Round- robin to the configuration file. For example I can choose Active Backup when editing the bond, save and close the NetworkManager. When I open it again, the mode is once again set to Round-robin and not my previously checked Active Backup when I closed NetworkManager. Also if I edit /etc/NetworkManager/system-connections/Bond\ Connection\ 1 by hand to have any other mode, NetworkManager resets the value on open of the application. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu May 9 18:53:36 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-10-02 (219 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IpRoute: default via ###.###.###.### dev bond0 proto static ###.###.###.###/24 dev bond0 proto kernel scope link src ###.###.###.### metric 5 169.254.0.0/16 dev eth0 scope link metric 1000 MarkForUpload: True NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 2: device path not found X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-05-09 (0 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH bond0 slave 2 9fb3fe4a-b24f-4a97-84d6-b72bf7c3d8e3 802-3-ethernet1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/2 MSFF 6e10a816-5b2a-4e88-93c5-bf70483fe6a5 vpn 1360882873 Thu 14 Feb 2013 03:01:13 PM PSTnono /org/freedesktop/NetworkManager/Settings/1 Bond connection 1 57d726f0-663a-40f5-86da-96befb80dd77 bond 1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/0 bond0 slave 1 55b7fab4-00bd-4468-bcbf-123cfd12bcc8 802-3-ethernet1368150838 Thu 09 May 2013 06:53:58 PM PDTyes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/2 bond0 bond connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1178505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1138251] Re: Desktop wallpaper Colors Gradients will not change color
Workaround added in #6 works great, thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1138251 Title: Desktop wallpaper Colors Gradients will not change color Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: To reproduce - System Settings - Appearances - Background Colors Gradients - Set a new sold color What happens - Background remains black. This is the same for solid colors and gradients What should happen - Background should change to new color ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.03.01-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0 Uname: Linux 3.8.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Mar 1 17:43:58 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0446] NVIDIA Corporation GF108 [GeForce GT 540M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0446] InstallationDate: Installed on 2013-02-11 (18 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130210) MachineType: Dell Inc. Dell System XPS 15Z MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-8-generic root=UUID=93acc5a7-d531-4af3-a215-472a7bd065d6 ro acpi_backlight=vendor dell_laptop.backlight=0 quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 060G42 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd07/27/2011:svnDellInc.:pnDellSystemXPS15Z:pvr:rvnDellInc.:rn060G42:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS 15Z dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.03.01-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1138251/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
