We have some servers that host git mirrors accessed via SSH that are
affected by this. Restarting systemd-logind via cron every 5 minutes
works for us (no full system restart necessary.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bug confirmed fixed with python-
setproctitle_1.0.1-1ubuntu1.14.04.2_amd64.deb.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When python-setproctitle is installed alongside mod_wsgi and the wsgi
application imports setproctitle it causes apache to segfault every time
a request comes in to that wsgi vhost.
GDB output:
Program terminated with signal SIGSEGV, Segmentation fault.
#0 fix_argv
+1 - the attached patch works for us and (IMO) a bug like this should be
squashed from an LTS ASAP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312421
Title:
Cannot rebuild dahdi-dkms
@Shane
Yes - it appears you are correct and I was in error in my previous
comment. The source file lib/facter/processor.rb does not make use of
Thread::Exclusive (except for Windows), but lib/facter/util/processor.rb
does, so it's necessary to patch that file also.
--
You received this bug
@Shane
Yes - it appears you are correct and I was in error in my previous
comment. The source file lib/facter/processor.rb does not make use of
Thread::Exclusive (except for Windows), but lib/facter/util/processor.rb
does, so it's necessary to patch that file also.
--
You received this bug
@Robie Basak
The copy of memory.rb that you linked in your update does contain the
fix (removal of require 'thread' etc.) I just checked out the tag
1.7.0 and found the commit
(https://github.com/puppetlabs/facter/commit/9ff4453b2f0843df887ae1ec2098a4336291df0c).
Note: that commit is only for
I just did some digging and found that processor.rb isn't affected in
versions 1.6.5 (precise) or 1.6.9. So, commit
9ff4453b2f0843df887ae1ec2098a4336291df0c is the only necessary one to
cherry-pick here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
@Robie Basak
The copy of memory.rb that you linked in your update does contain the
fix (removal of require 'thread' etc.) I just checked out the tag
1.7.0 and found the commit
(https://github.com/puppetlabs/facter/commit/9ff4453b2f0843df887ae1ec2098a4336291df0c).
Note: that commit is only for
I just did some digging and found that processor.rb isn't affected in
versions 1.6.5 (precise) or 1.6.9. So, commit
9ff4453b2f0843df887ae1ec2098a4336291df0c is the only necessary one to
cherry-pick here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I found a bug with Facter that's affecting the version distributed with
12.04. Upstream bug report here:
http://projects.puppetlabs.com/issues/12723 This makes puppet completely
unusable for us unless this change is applied.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to facter in Ubuntu.
https://bugs.launchpad.net/bugs/986973
Title:
Facter bug causes puppet to become a zombie
To manage notifications about this bug go to:
Public bug reported:
I found a bug with Facter that's affecting the version distributed with
12.04. Upstream bug report here:
http://projects.puppetlabs.com/issues/12723 This makes puppet completely
unusable for us unless this change is applied.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986973
Title:
Facter bug causes puppet to become a zombie
To manage notifications about this bug go to:
Public bug reported:
Currently the stock my.cnf included in the package mysql-common
specifies that an error log is created at /var/log/mysql/error.log. The
logrotate conf file /etc/logrotate.d/mysql-server (part of mysql-
server-5.1) doesn't take this file into account so it can continue to
grow
I just took a look at upstream (Debian) and the my.conf files in both
oldstable (Lenny) and stable (Squeeze) do not manually specify an error
log file. This is correct behavior as understood by the logrotate conf
file.
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
- Currently the stock my.cnf included in the package mysql-common
- specifies that an error log is created at /var/log/mysql/error.log. The
- logrotate conf file /etc/logrotate.d/mysql-server (part of mysql-
- server-5.1) doesn't take this file into account so it can
Hi Ben,
This isn't a bug that affects running processes. It's a packaging bug.
Thanks
** Changed in: mysql-5.1 (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-5.1 in Ubuntu.
Public bug reported:
Currently the stock my.cnf included in the package mysql-common
specifies that an error log is created at /var/log/mysql/error.log. The
logrotate conf file /etc/logrotate.d/mysql-server (part of mysql-
server-5.1) doesn't take this file into account so it can continue to
grow
I just took a look at upstream (Debian) and the my.conf files in both
oldstable (Lenny) and stable (Squeeze) do not manually specify an error
log file. This is correct behavior as understood by the logrotate conf
file.
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
- Currently the stock my.cnf included in the package mysql-common
- specifies that an error log is created at /var/log/mysql/error.log. The
- logrotate conf file /etc/logrotate.d/mysql-server (part of mysql-
- server-5.1) doesn't take this file into account so it can
Hi Ben,
This isn't a bug that affects running processes. It's a packaging bug.
Thanks
** Changed in: mysql-5.1 (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 567016 ***
https://bugs.launchpad.net/bugs/567016
Just adding another me too here. Using 10.04 w/ all updates
(2.6.32-24-generic #39) my machine is unusable with the RTL 8172
wireless card turned on. It randomly locks up my machine - sometimes
within minutes
I can't believe that this bug is going to make it into Karmic final :( I
just helped a friend of mine get rid of his spyware ridden Windows
install by installing Karmic RC remotely and fully updated it. I was sad
to hear that the screen was flickering when it restarted. I tried the
HAL patch
I appologize for not reading this entire bug report because I feel
vehement about posting my opinion on the plugin. I realize that some of
my concerns may have been addressed already. I am merely posting them as
another vote for how bad of an idea this plugin is.
Please obliterate this plugin.
I'm here to add my concern for this bug. I'm currently using a jaunty
netbook with a 1024x600 resolution and resizing windows naturally
(using my cursor on a window edge) is almost always an absolute chore if
not impossible. On my 1920x1200 desktop computer it's not quite as
difficult with my
Hello all - I've experienced this problem also. I forked my sudoers file
(didn't use visudo to edit it) so I had to boot into recovery mode to
edit it. As soon as I ran visudo the system hard locked and had to be
shut down. Upon next bootup /etc/sudoers was a 0B file.
I'll guess I'll try to not
*** This bug is a duplicate of bug 64531 ***
I have the same problem. It causes a rather annoying spike every few
seconds in my CPU usage graph (I use the ksysguard taskbar tool). It
seems that one of the apt-index-watch processes runs normally and
another one launches and dies every few seconds.
28 matches
Mail list logo
