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:
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
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
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.
@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
@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 +
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
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,
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:
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
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)
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
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.
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
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
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
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
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
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
19 matches
Mail list logo
