[Bug 1301015] Re: Networking does not restart

2016-06-05 Thread Hayjumper
Additionally, the ifdown/ifup method does not load certain changes (e.g.
IP address) properly, and often breaks networking when such changes are
made.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301015

Title:
  Networking does not restart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1301015] Re: Networking does not restart

2015-12-09 Thread Hayjumper
The command in comment #8 *should* do this in a single exec resource:

sudo ifdown --exclude=lo -a && sudo ifup --exclude=lo -a

However, I have found this does not actually work either for any
significant config change (e.g. IP address change, gateway change).  In
fact, the command above frequently causes networking to stop working in
such cases.

The only way I've found that works is to reboot the server;
NetworkManager is not an option when doing text-based network config.
Other distros using upstart do not seem to have this problem.  It's a
shame that Canonical hasn't seen fit to address this, and its cost them
my employer's (albeit meager) support budget.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301015

Title:
  Networking does not restart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1278193] Re: logrotate skip the rotation of many files under /var/log due to bad group ownership

2015-05-22 Thread Hayjumper
#8 is a good analysis...  this change breaks manually running logrotate
with a specific file as argument.  It doesn't seem to affect automatic
rotation due to the su line in /etc/logrotate.conf.

Seems that making root:syslog the default for all logrotate scripts
would fix this behavior, as would reverting ownership of /var/log to
root:root.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1278193

Title:
  logrotate skip the rotation of many files under /var/log due to bad
  group ownership

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1278193/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1301015] Re: Networking does not restart

2015-03-26 Thread Hayjumper
I second rgtaylor's request.  This additionally has great impact on
automated build scripts  systems (in my case, Foreman/puppet) which
need a way to make networking changes (such as new IP address)  apply
those changes, often on systems for which console access is (at best)
inconvenient due to location, etc.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301015

Title:
  Networking does not restart

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1307778] Re: getent group on trusty returns only local groups

2015-03-23 Thread Hayjumper
I also confirm this issue for Trusty with v. 4.1.6.  It seems that the
order in which the gids are evaluated is crtical, in that NO groups
(including those with valid gids) are resolved after the first incidence
of a group with missing gid, and therefore group memberships after this
are simply missing.  This ordering seems consistent for a given user,
but varies between users.

I was able to apply the upstream patch to the 4.1.6 source package which
is current in Trusty.  Recompiling  reapplying the samba packages
resolved the issue.  The patch is quite simple (4 lines)  it would be
nice if this could be backported to trusty (and utopic?) at some point;
would be especially useful to prevent future updates to these packages
from (re)breaking gid resolution.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1307778

Title:
  getent group on trusty returns only local groups

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1307778] Re: getent group on trusty returns only local groups

2015-03-23 Thread Hayjumper
I also confirm this issue for Trusty with v. 4.1.6.  It seems that the
order in which the gids are evaluated is crtical, in that NO groups
(including those with valid gids) are resolved after the first incidence
of a group with missing gid, and therefore group memberships after this
are simply missing.  This ordering seems consistent for a given user,
but varies between users.

I was able to apply the upstream patch to the 4.1.6 source package which
is current in Trusty.  Recompiling  reapplying the samba packages
resolved the issue.  The patch is quite simple (4 lines)  it would be
nice if this could be backported to trusty (and utopic?) at some point;
would be especially useful to prevent future updates to these packages
from (re)breaking gid resolution.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307778

Title:
  getent group on trusty returns only local groups

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307778/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1073728] Re: software sources window takes long time to open with little user feedback

2013-07-19 Thread Hayjumper
The referenced fix has to do with the clarity of an error message, not
the startup performance of the package.  Based on comments above and my
own testing, the fix does not affect the subject of this bug report.
Recommend this bug be set to Open or at least Won't Fix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073728

Title:
  software sources window takes long time to open with little user
  feedback

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1073728/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 451571] Re: usplash hangs with kernel Ubuntu 2.6.31-14.46-generic, works with 2.6.31-13

2010-01-01 Thread Hayjumper
Apologies if it is improper to comment here... just wanted to mention
that I was also affected by this bug.  I worked around it by editing the
/etc/usplash.conf file (as directed by the Debugging Usplash wiki link
above) and changing the resolution from the default (1920x1080, which is
the correct native rez of my current monitor) to 1024x768.

After making this edit and running 'sudo-updateinitramfs' as directed by
the config file comments, I am able to successfully display logo from
the command line via 'sudo usplash'.  I re-enabled splash in grub config
 ran update-grub; my system now boots successfully with splash screen
enabled.

Perhaps there is some problem with the default 1920x1080 widescreen
resolution when running usplash.  1024x768 standard 4:3 resolution
works, I did not try any other resolution.  Hoping this will be helpful
to others affected by this bug...

-- 
usplash hangs with kernel Ubuntu 2.6.31-14.46-generic, works with 2.6.31-13
https://bugs.launchpad.net/bugs/451571
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