Is there any specific reason for which this has not been marked invalid
and closed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597933
Title:
Atomicparsley package completely broken
To manage no
This bug was fixed upstream almost a year ago. It would be nice to see
this addressed in Ubuntu 16.04 LTS, which is still on libmagic1 version
5.25.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/174112
The fact that this was reported on 2014-09-04 and *still* has not been
fixed is unbelievable.
It seems related to (or the same as)
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1512992 , which was
opened on 2015-11-04 and has not been fixed yet either.
Only ten days ago was a fix proposed,
Public bug reported:
# lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
# apt-cache policy logwatch
logwatch:
Installed: 7.4.2-1ubuntu1
Candidate: 7.4.2-1ubuntu1
Version table:
*** 7.4.2-1ubuntu1 500
500 http://mirrors.digitalocean.com/ubuntu xenial/main amd
Thank you, François, I really appreciate it!
John Horne with the rkhunter project replied, and his suggestion does
indeed solve the problem for me, so we can go ahead and close this.
For some reason, I thought that rkhunter's ALLOW_SSH_ROOT_USER directive
wanted "PermitRootLogin", instead of Perm
I forgot to mention the most annoying aspect of the bug, which is that
there is no workaround.
If I change rkhunter's configuration file to use "permitrootlogin" (all
lower-case), somewhat unsurprisingly, the problem still occurs.
[09:34:26] Info: Found SSH /etc/ssh/sshd_config configuration file
Public bug reported:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.4 LTS
Release:14.04
Codename: trusty
# apt-cache policy rkhunter
rkhunter:
Installed: 1.4.0-3
Candidate: 1.4.0-3
Version table:
*** 1.4.0-3 0
500 ht
This bit me yet again, and this time, I had to add one more package to
the list (lib64z1-dev, which is simply the x64 equivalent of
lib32z1-dev, which we already knew to be problematic). The complete list
of packages to force-remove to resolve this is now:
sudo dpkg --purge --force-depends "gcc-mu
This issue may be the same as or related to
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1365375 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312917
Title:
package libc6-dev-i386 (not i
@Karthik
I agree; this is a particularly severe bug because it renders the entire
apt-get facility useless.
For what it's worth, even though the last command is the command that
"fixes" the issue, I believe it to be desirable to execute the previous
two commands, too, because those packages are p
To follow-up on my previous comment, I was able to work around this
"broken state" in aptitude by purging the offending packages with
"--force-depends":
dpkg --purge --force-depends "gcc-multilib"
dpkg --purge --force-depends "lib32z1-dev"
dpkg --purge --force-depends "libc6-dev-x32"
Now, I'm abl
Thanks for taking the time to report this, richud, and especially for
providing the attachments.
This bug bit me today, too.
Were you able to implement any sort of a workaround?
This seems like a significant problem to go unfixed since September,
2014.
Here's what happened, in my particular cas
** Package changed: ubuntu => dovecot (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1378446
Title:
dovecot-lda crashes (exits with status code 134) when message is
passed to pipe backend
Public bug reported:
I first reported this issue on the Dovecot mailing list, but nobody
there was able to help me identify the source of the problem (no less
how to fix it). And that's a pretty sharp group! Here's the full thread:
http://www.mail-archive.com/dovecot@dovecot.org/msg58938.html
I
I can only imagine how annoying this must be for admins who run a scan
more than once per day. This is an LTS release, folks. This is supposed
to be an enterprise-grade OS. Being warned about a root-kit, falsely, on
every scan is not something to be taken lightly. Many of us have wasted
lots of tim
I don't know how more people aren't complaining about this. I receive a
disconcerting email message every single day because of this bug.
The average user will have no idea what's causing this warning, either;
one has to dig into the detailed log file to find that this message
results from a faile
Thank you for the suggestion, cebe. I tried removing the "Pragma" header
just before sending the file to the user-agent, but this measure does
not correct the problem for me. I confirmed that the "Pragma" header is
indeed gone from the response (using Firebug), but I still receive the
error dialogs
Public bug reported:
# lsb_release -rd
Description:Ubuntu 10.04.4 LTS
Release:10.04
# apt-cache policy libapache2-mod-xsendfile
libapache2-mod-xsendfile:
Installed: 0.9-2
Candidate: 0.9-2
Version table:
*** 0.9-2 0
500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe
@Jeff:
The workaround is contained at the bottom of the initial report:
The only means by which I was able to remove the package was to fix
problem by editing "/var/lib/mailman/Mailman/mm_cfg.py" directly and
changing the line in question to:
DEFAULT_SERVER_LANGUAGE = 'en'
--
You received this
I have scoured the 'apt-get' documentation and am left to assume that
Ubuntu's Update Manager uses its own logic to allow for upgrading
packages selectively. This passage from apt-get's man-pages spells it
out clearly:
This is also the target to use if you want to upgrade one or more
already-insta
Thank you for the reply, James; it clarifies the issue.
Using 'apt-get upgrade' applied the package upgrades without causing
Apache to shutdown uncleanly, and the libapache2-mod-php5 package was
unaffected, so Apache restarted without issue. All is well.
Perhaps this is a question is more appropr
Public bug reported:
# lsb_release -rd
Description:Ubuntu 10.04.4 LTS
Release:10.04
# apt-cache policy apache2
apache2:
Installed: 2.2.14-5ubuntu8.9
Candidate: 2.2.14-5ubuntu8.9
Version table:
*** 2.2.14-5ubuntu8.9 0
500 http://us.archive.ubuntu.com/ubuntu/ lucid-update
Thanks, Robie. Given that your package version is identical to that
contained in the initial report, further research seems warranted.
Perhaps the package installation script attempts to obtain locale
information from the operating system in order to populate the
DEFAULT_SERVER_LANGUAGE value in t
Robie, if you will, what is the output of "apt-cache policy mailman" on
your system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904410
Title:
Mailman configuration script causes syntax error in
Public bug reported:
Summary of changes:
The code to which this comment refers causes numerous PHP warnings to be issued
each time the script is executed on systems on which PHP open_basedir
restrictions are in effect. If the location of the rrdtool executable were
defined as a configuration d
This patch resolves the issues identified in this report.
** Patch added: "Patch to resolve PHP warnings in amavis-stats"
https://bugs.launchpad.net/ubuntu/+source/amavis-stats/+bug/963254/+attachment/2923455/+files/963254.diff
--
You received this bug notification because you are a member o
Slight correction to previously-attached patch file.
** Patch removed: "Patch to resolve critical PHP errors in amavis-stats"
https://bugs.launchpad.net/ubuntu/+source/amavis-stats/+bug/677820/+attachment/2923186/+files/677820.diff
** Patch added: "Patch to resolve critical PHP errors in amav
The attached patch file resolves the issues described in this report.
** Patch added: "Patch to resolve critical PHP errors in amavis-stats"
https://bugs.launchpad.net/ubuntu/+source/amavis-stats/+bug/677820/+attachment/2923186/+files/677820.diff
--
You received this bug notification because
Public bug reported:
This package could not possibly have been tested before inclusion in
Ubuntu; nearly every aspect of the package is incorrect.
Summary of issues:
1.) amavis-stats is started with a Cron job, which, as described at
https://bugs.launchpad.net/ubuntu/+source/amavis-stats/+bug/47
Frantisek, the reason that amavis-stats stopped functioning correctly
after applying package updates is that your PHP version was upgraded.
amavis-stats relies on PHP's dl() function, which was removed from some
SAPIs in PHP 5.3 (see: http://www.php.net/manual/en/function.dl.php ).
The workaroun
Public bug reported:
It would be nice if Baobab had the ability to save or export disk usage
analysis results.
** Affects: baobab (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Again, same here on Ubuntu Server 10.04.
Like the others, fixed by executing the "update-locale" command, which
creates the file /etc/default/locale. This file appears not to exist
out-of-the-box.
The contents of this file are:
# File generated by update-locale
--
You received this bug notifi
Public bug reported:
# lsb_release -rd
Description:Ubuntu 10.04.2 LTS
Release:10.04
# apt-cache policy mailman
mailman:
Installed: 1:2.1.13-1ubuntu0.2
Candidate: 1:2.1.13-1ubuntu0.2
Version table:
*** 1:2.1.13-1ubuntu0.2 0
500 http://us.archive.ubuntu.com/ubuntu/ lucid-
This is fixed in version 0.73b1 on the author's site:
http://kde.maniatek.com/audex/download
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/614895
Title:
audex crashes when setting up new encoding pr
Audex was Segmentation Faulting for me when saving profiles or doing a Codec
Scan from the profile configuration window. After getting all the encoders that
Audex looks for installed and removing ~/.kde/share/config/audexrc, it no
longer Seg Faulted.
The encoders I needed to install are lame, fl
If you are using LAME as the encoder, a good work around is tagging files with
lame instead instead of letting Grip do it.
1. on the Config / ID3 Screen, turn off all ID3 tags
2. on the Config / Encode / Encoder screen, set
Encoder: lame
Encoder executable: /usr/bin/lame
Encoder com
Fixed in Banshee 0.12.0
** Changed in: banshee (Ubuntu)
Status: Confirmed => Fix Released
--
Banshee crashes if you try to delete a song that doesn't exist
https://bugs.launchpad.net/bugs/79636
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
** Changed in: banshee (Ubuntu)
Status: Unconfirmed => Confirmed
--
Banshee crashes if you try to delete a song that doesn't exist
https://bugs.launchpad.net/bugs/79636
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
Public bug reported:
Binary package hint: banshee
If a song is missing from your hard drive and you try to delete it
instead of merely removing it, Banshee crashes.
** Affects: banshee (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Banshee crashes if you try to delete a so
39 matches
Mail list logo
