** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-36177
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914474
Title:
wolfssl: Please update 20.10 (groovy) to version 4.6.0
To manage
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914474
Title:
wolfssl: Please update 20.10 (groovy) to version 4.6.0
To manage no
Fixed in
https://salsa.debian.org/lintian/lintian/commit/6c9387b2758ccea243ce852afc8253ddab7a206a
Test case using 'focal' release in prior commit:
https://salsa.debian.org/lintian/lintian/commit/0224baacb5b89f0dc8b66b4d80d77e955dbc4cc4
--
You received this bug notification because you are a me
Please attach the *.changes file for that particular upload.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1862787
Title:
inconsistent-maintainer error not applicable to Ubuntu
To manage notificati
I am the Debian maintainer of this package and believe the issue was
resolved. Closing this bug.
** Changed in: libgsm (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
I am the Debian maintainer of this package and believe the issue was
resolved. Closing this bug.
** Changed in: libgsm (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I am the Debian maintainer of this package and believe the issue was
resolved. Closing this bug.
** Changed in: libgsm (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
I am the Debian maintainer of this package and believe the issue was
resolved. Closing this bug.
** Changed in: libgsm (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I am the Debian maintainer of this package and believe the issue was
resolved. Closing this bug.
** Changed in: libgsm (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
The issue is pam-related. It was caused by a proposed fix for the
following bug
https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/927828
This report is probably not related to the cron package and should be
closed.
--
You received this bug notification because you are a member of Ubun
The proposed fix of changing [default=1] to [default=0] in '/etc/pam.d
/common-session-noninteractive' causes problems with 'cron'.
Cron jobs are no longer executed. Syslog entry says 'CRON[process id]:
Permission denied'.
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Upon upgrade to Precise from Oneiric, my custom cron jobs stopped
working.
Custom entries in '/etc/crontab' result in these errors:
Apr 19 14:59:01 hostname CRON[5898]: Permission denied
Apr 19 14:59:01 hostname CRON[5899]: Permission denied
Jobs in '/var/spool/cron/crontab
My /usr/bin/python is managed by alternatives.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/96897
Title:
0.1.9 fails to install on feisty
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: kernel-package (Ubuntu)
Status: New => Invalid
** Description changed:
+ EDIT: Upon closer inspection, the mipsel files are so much out of date
+ that they should be completely adjusted. Marked the bug as invalid
+ since I could not figure out how to delete it.
+
+
Bin
** Summary changed:
- faulty kimagedest causes internal package error
+ setting kimage causes internal package error (with fix)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729972
Title:
setting k
Public bug reported:
Binary package hint: kernel-package
Description:Ubuntu 10.10
Release:10.10
kernel-package:
Installed: 12.033
Candidate: 12.033
Version table:
*** 12.033 0
500 http://us.archive.ubuntu.com/ubuntu/ maverick/universe amd64
Packages
100 /var/l
A few months ago, I was so frustrated that I played around with other
distributions. Suse had similar X problems. Fedora only booted in
text mode. After many hours of trying, I now have a Ubuntu combo w/o
lockups.
It would be nice to know if there are alternatives. Perhaps you could
let us kno
Tim,
Thank you for your advice. Are you also still running the old
2.6.34-v9patch kernel from Brian Rogers? Why don't I need the updated
modules from Glasenhardt's '855gm-fix' like everyone else?
Anyone following the new instructions in the sticky is taken to Brian's new
kernel 2.6.35rc4-131-ge
Darxus,
Please try this before you buy a new computer:
My graphics performance seems a bit sluggish at times (but I also have a
slow network). My system is stable with a 1680x1050 resolution on
82845G/GL. Crashes have pretty much stopped. Every once in a while my
system freezes when I try to l
My original bug report was probably filed in error. Over the past two
years, I came to the conclusion that the problems were caused by the
exceptional amount of space taken up by the ppms but not by a bug within
xpdf or poppler.
The status will be marked as invalid.
** Changed in: xpdf (Ubuntu)
Public bug reported:
Binary package hint: hostap-utils
On a lucid install from beta2 cd subsequently upgraded to 10.04,
installing 'hostap-utils' leads to a soft lockup during boot every time.
Because of lucid's parallel boot procedure, it was difficult to identify
the offending package. Howeve
The x-retro package worked well for a day. Then there were a couple of
crashes in rapid succession. One thing is definitely better: The X
server restarts and offers to run in low res mode. So no more zebra
stripes. I can also get to the gettys.
I can supply more information next time if someo
My 845G also still crashes with the white stripes after setting
'i915.modeset=0'. Please let me know if I can contribute to the testing
of any workarounds.
Only have one computer though, so no SSH.
--
MASTER: [i845] GPU lockup (apport-crash) (Should KMS be blacklisted?)
https://bugs.launchpad.n
Okay I need to apologize again. This is my first time filing a bug
report. The man page for my version of pdfimages refers to XPDF but the
version actually installed is from poppler. So I filed against the
wrong package but don't know how to fix it.
Package: poppler-utils
Status: install ok ins
I was a little hasty in reporting this bug. It is not certain that
pdfimages enters an infinite loop. It could be that the PPM images take
up exceptional amounts of space. In my case, I aborted pdfimages after
it created 1.9GB of images from a PDF 11MB in size. Using -j did not
create any JPGs.
Public bug reported:
Binary package hint: xpdf
xpdf's pdfimages enters an infinite loop and extracts the same images
over and over again, until the drive runs out of space. Happened to me
twice on commercially produced PDFs. Unfortunately, the documents are
confidential. Email me and I will se
26 matches
Mail list logo
