Interesting. This issue was normally hidden by grub being hidden in the
first place, but once I enabled it and a reasonable timeout, I was able
to see it. Either way, I see it, I don't know what the potential
downside is to it not being there, or what hwmatch itself does.
--
You received this bug
I'm seeing this problem on linux 5.3.0-40-generic but with a different
error log:
[ 98.743076] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version:
43.2.23.17
[ 98.743079] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM
[ 98.743080] iwlwifi :00:14.3: Found debug configu
Is this bug ever going to be resolved? It's been active and unassigned
since 2013, and no resolution but this manual step, and it doesn't just
effect Ubuntu, but all Ubuntu-family distributions, Linux Mint,
elementary OS included.
I'm trying to make multi-boot USBs that I can pass out to new/exist
I also have this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758974
Title:
Indicator-multiload does not work properly 18.04
To manage notifications about this bug go to:
https://bugs.la
I also have this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786084
Title:
Indicator does not show as tray icon on 18.04
To manage notifications about this bug go to:
https://bugs.launc
This isn't "fixed". It's bandaided to change the copyright, author,and
bugs to, but does not actually document the tool at all.
Mountall in Ubuntu is custom unique to Ubuntu to work specifically with
upstart, and these need to be documented properly on how it operates,
what it emits, how it emits,
Adam, dug more into the lsb spec, and found this:
http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-
generic/iniscrptfunc.html
So, in technicality, the script does as specified under that
determination, making a pid file always outweight validity of any kind,
so this is a deb
Here's a run-down of the overall problem I'm seeing about how this is
being done, implicitly relying on pidfiles:
Say you're running apache by init.d scripts (which Ubuntu does), and it
uses status_of_proc to get the status:
status_of_proc -p /var/run/apache.pid $DAEMON $NAME
status_of_proc pass
No, actually, I'm following the LSB standards to the T.
You are correct in the fact, a process COULD be run under a different
name, and for those cases, status_of_proc should be able to be alerted
to that name, such as -n "processname", but pid files being weighted
more authority than an actual pr
Also noticed:
+if [ -e "$pidfile" -a ! -r "$pidfile" ]; then
Should be -f, then -r, not -e. It should exist AND be a regular file
(not a symlink, device node, pipe, etc)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Adam,
I looked at the patch #22, and though logically it's "accurate", but
it's not at the same time. If the pid file exists but doesn't have the
correct information, or any information, pidof should be failed back to
check if it literally is running or not directly, not just up and return
error
Well, according to ubuntu-bug -p lsb-base, it filed it on lsb because
lsb is the /source/ package. And why did you mark all the other packages
I had associated it to as invalid? They are /ALL/ effected by this exact
same thing, which is how I found it in the first place.
--
status_of_proc is retu
** Also affects: openvpn (Ubuntu)
Importance: Undecided
Status: New
--
status_of_proc is returning incorrect error code
https://bugs.launchpad.net/bugs/683640
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
** Also affects: dovecot (Ubuntu)
Importance: Undecided
Status: New
** Also affects: bind9 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: openbsd-inetd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: rsync (Ubuntu)
Importance: Undecided
This patch, applied to /lib/lsb/init-functions resolves the problem by:
1> Allowing pid detection to check directly by pid if the process is in fact
running.
2> Allowing pid detection to check for stale pid files.
3> Failing over to pidof detection to find the parent pid (ppid) of the process
if
As per LSB Init compliancy:
If the status action is requested, the init script will return the
following exit status codes.
0 program is running or service is OK
1 program is dead and /var/run pid file exists
2 program is dead and /var/lock lock file exists
3 program is no
This is related to bug:
https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/683640
--
status_of_proc is returning incorrect error code
https://bugs.launchpad.net/bugs/683650
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug effects:
https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/683650
--
status_of_proc is returning incorrect error code
https://bugs.launchpad.net/bugs/683640
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
--
status_of_proc is returning incorrect error code
https://bugs.launchpad.net/bugs/683650
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/listin
Public bug reported:
Executing /etc/init.d/dovecot fails with error code 4 when service is
not started.
As per lsb-init compliance:
If the status action is requested, the init script will return the following
exit status codes.
0 program is running or service is OK
1 program is dead
--
status_of_proc is returning incorrect error code
https://bugs.launchpad.net/bugs/683640
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/listin
Public bug reported:
Binary package hint: lsb
When status_of_proc is called with -p $PIDFILE and the service is not
presently started, error code 4 is always returned because the process
does not have the PID file existant until it is started, and it's
deleted after stopping.
This fails LSB comp
You might be right. It might have been added for testing the plugin with
a local server.
As for the libpq5 dependancy, I didn't notice that before, but you're
correct.
The overall problem may not be in rsyslog-pgsql itself, but in apt,
since 8.10, for automatically installing recommends. It's bee
Public bug reported:
Binary package hint: rsyslog-pgsql
rsyslog-pgsql only recommends postgresql, which is a virtual package in
include ALL of PostgreSQL, server, client, common, libs, etc..
rsyslog-pgsql should at the very minimum, depend on postgresql-client
(or postgresql-client-8.3), to oppe
Public bug reported:
Binary package hint: dbmail
Below, is the dpkg --configure -a output of a failed upgrade from 7.04
to 7.10's dbmail. It seems to be looking for create_user, which does not
exist.
Setting up dbmail (2.2.5-1ubuntu1) ...
/var/lib/dpkg/info/dbmail.postinst: 170: create_user: not
25 matches
Mail list logo
