Same thing here..wtf.
May 3 22:31:40 camview-pxe systemd[1]: Stopped Light Display Manager.
May 3 22:31:40 camview-pxe systemd[1]: Starting Detect the available GPUs and
deal with any system changes...
May 3 22:31:40 camview-pxe gpu-manager[599]: /etc/modprobe.d is not a file
May 3 22:31:40 c
Seems to be related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408
Memory management issues since a commit on a kernel revision somewhere for 4.11
or 4.12. I'm sticking to 4.10.0-28 until resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Hi guys. I'm experiencing problems with 4.13.0-36 on a cloud server
(x64) with dynamic ram management. The server is provisioned to use up
to 12GB of RAM, but it got so bad that only 1GB was visible, causing
everything to a halt while swap usage went through the roof. Could it be
related?
And here
Oh and I have also experienced random, unexplained OOM crashing of squid
process recently on two separate machines (one i386 and one amd64) which
seem to coincide in time with the upgrade from kernel 4.10 to 4.13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I mixed up the versions in my last post! xD2.6.1-3 is missing the
feature.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1449201
Title:
maildrop's auth option (-t) missing since vivid upgrade?
maildrop 2.7.1-1:
root@hostname:# maildrop -t
maildrop: Bad command line arguments, -h for help.
maildrop 2.7.1-3:
root@hostname:# maildrop -t
You didn't specify the location of Dovecot auth socket.
Fortunately didn't need to recompile from source, just using old rpm...
hopefully this can be fixe
Public bug reported:
Hi
I noticed a problem with mail delivery after upgrade to 15.04/vivid.
Inspection of the logs revealed the following:
/*
AD2C9383706 1981 Sun Apr 26 18:06:01 r...@domain.com
(temporary failure. Command output: /usr/bin/maildrop: Bad command line
arguments, -h for help
Possibly related to https://bugs.launchpad.net/ubuntu/+source/proftpd-
mod-vroot/+bug/1174305 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310591
Title:
MKD not working
To manage notifications
Wow. Excuse me for butting in but I cannot for the life of me comprehend
the retardation in calling this report "Invalid"? VLC has major problems
in this regard. If it's not the GUI spamming error messages as it tries
to play next item in playlist when a stream fails (because it doesn't
know how to
Thanks for implementing this fix. I have not had time to test it myself
yet
I do notice however that verification-needed has been removed already,
on the basis of 'reboot please' working. What about 'reboot now' -- does
this also work as expected? Remember that this bug report was
specifically ope
*** This bug is a duplicate of bug 1187808 ***
https://bugs.launchpad.net/bugs/1187808
Same here when trying to update today
apt hung at:
Setting up rsyslog (5.8.11-2ubuntu2.1) ...
killed the process, and install completed.
tried to run syslogd manually:
root@srv:~# rsyslogd -c5
*** Error
Welcome to Ubuntu 12.04.2 LTS (GNU/Linux 3.2.0-40-generic-pae i686)
root@host1:~# reboot now
The system is going down for reboot NOW!
Welcome to Ubuntu 13.04 (GNU/Linux 3.9.0-030900rc8-generic i686)
root@host2:~# reboot now
The system is going down to maintenance mode NOW!
(the same for shutdown)
That is the point though. If retaining conventions of the past is such an
important factor, then I wonder why I could (until recently, at least) issue
'shutdown now' or 'reboot now' on any machine running debian/ubuntu, and it
would complete a full power-off, or reset, respectively, each time...
Usage: shutdown [OPTION]... TIME [MESSAGE]
Bring the system down.
Usage: reboot [OPTION]...
Reboot the system.
Just out of curiousity. Why no 'time' for reboot? These commands are
similar in purpose, so one would expect that level of consistency
between them
I'll also be happy go back on my prev
'shutdown now' would typically shut the system down until recent updates
which also caused reboot now to enter single user mode. why would
'reboot' ever bring the system to single-user mode, even if the user
provides incorrect syntax? Incredibly unintuitive, not to mention
inconsistent. This is sti
Trying to configure my pure-ftpd server which relies on messages, and
the log window was empty. I've re-enabled it the way it should be, in
rsyslogv conf. /var/log/messages is an essential part of any unix
distro. What needs to happen is that the distinction between syslog and
messages needs to bec
Actually just exoerienced this same symptom on a machine running
12.04.2, on 'shutdown now' went into maintenance console. Is this normal
?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1174272
Title:
Public bug reported:
A forum thread has been opened first, describing the problem. For
reference, that forum thread can be found here:
http://ubuntuforums.org/showthread.php?t=2139160&p=12624806
Problem is described below:
When the command "reboot now" is issued:
root@server:~# reboot now
Broad
18 matches
Mail list logo
