Another potential reason could be https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=843160, but this seems to have been introduced in
systemd 231 while this bug report seems to have been written with
systemd 229 running.
** Bug watch added: Debian Bug tracker #843160
** Changed in: dphys-swapfile (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: dphys-swapfile (Ubuntu)
Assignee: (unassigned) => Axel Beckert (xtaran)
--
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 1496216 ***
https://bugs.launchpad.net/bugs/1496216
This is indeed a duplicate of #1496216. The timemout message is not
visible in the dpkg terminal output there, but in the journal error
messages.
** This bug has been marked a duplicate of bug 1496216
*** This bug is a duplicate of bug 1496216 ***
https://bugs.launchpad.net/bugs/1496216
JFTR: #1496216 is fixed now. Thanks for reporting this issue despite
being a duplicate, since it led me to the real cause.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
593 0EDE
** Tags added: bionic cosmic
** Changed in: dphys-swapfile (Ubuntu)
Status: New => Confirmed
** Bug watch added: Debian Bug tracker #906767
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906767
** Changed in: dphys-swapfile (Ubuntu)
Assignee: (unassigned) =>
** Changed in: dphys-swapfile (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788681
Title:
changed exit code for 'dc' in Ubuntu Bionic
To
Thanks for the bug report and feature idea/suggestion!
Not yet sure if that option should be really added to debsums (the
program), or be default inside the cron job(s) itself.
Note to myself: I see there's a lot of code duplication in the cron
jobs. (Never really looked at them since I took
issions recursively during
dist-upgrade?
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D
** Tags added: community-security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781295
Title:
CVE-2018-10895: Possible remote code execution via CSRF in
qute://settings
To manage notifications
*** This bug is a duplicate of bug 1781295 ***
https://bugs.launchpad.net/bugs/1781295
** This bug has been marked a duplicate of bug 1781295
CVE-2018-10895: Possible remote code execution via CSRF in qute://settings
--
You received this bug notification because you are a member of
This acutally seems to be an issue with the xchat package and flwm's
trigger trips over xchat's malformed .desktop file. The relevant line
from the DpkgTerminalLog.txt is:
Exec key for 'XChat IRC' contains '%F', '%U' or '%D' at the wrong place
A valid question is if flwm's trigger should bail
var/run/screen 0777 root utmp' > $override
I assume that this is nothing which would make sense to add to future
releases of Debian's screen package, or does it?
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, f
t 9 Oct 4 2016
> /lib/systemd/system/screen-cleanup.service -> /dev/null
Please also check the existence and contents of
/etc/tmpfiles.d/screen-cleanup.conf before and after upgrading.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' :
creen has been unpacked, but not configured.
Or did I understand your previous mail about screen in 16.04 being
2755?
Regards, Axel (not Alex)
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517
I can't reproduce this issue in a minimal Debian Unstable chroot, so it
might be an ubuntu-specific issue.
And https://github.com/cbbrowne/tpp/issues/9 looks unrelated for me:
Completely different error message, C linking error (Github) vs ruby
module location error (here).
** Bug watch added:
Meh, can't link this bug report to a CVE report as Launchpad claims that
"CVE-2018-10895 is not a valid CVE number". But it obviously is.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-10895
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Ok, since half an hour, Cosmic is fixed, probably due to the automatic
sync from Debian Unstable.
** Tags removed: cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781295
Title:
*** This bug is a security vulnerability ***
Public security bug reported:
qutebrowser 1.0.0 to 1.4.0 allows websites to change configuration
settings via the qute://settings page by using CSRF. E.g. via the editor
setting, this can very likely lead to a remote code execution. This has
been
Hi,
Rolf Leggewie wrote:
> Is this still an issue?
Depends. If you consider https://bugs.debian.org/137771 (as linked to
and marked as "fix released") to be the Debian-equivalent of this bug
report, it's fixed since 0.7.2-1 from September 2015.
Regards, Axel
--
,
** Bug watch added: Debian Bug tracker #895217
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895217
** Also affects: aptitude (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895217
Importance: Unknown
Status: Unknown
--
You received this bug notification
Regards, Axel (with his aptitude hat on)
--
,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D8
until then. Feel free to reassign or -- if you
can explain where the bug is -- reopen.
(Note: To me this rather looks like a not yet run postinst or similar
during a dist-upgrade.)
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
** Changed in: hobbit-plugins (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798557
Title:
xymon-client and snaps, client report gets red in disk,
disk and inode checks are from the xymon package, the misc check is
indeed from hobbit-plugins.
** Package changed: hobbit-plugins (Ubuntu) => xymon (Ubuntu)
** Also affects: hobbit-plugins (Ubuntu)
Importance: Undecided
Status: New
** Tags added: patch
--
You received this bug
Instead of looking at parts of the mount-point path, I implemented the
exclusion in both packages by completely ignoring squashfs mounts as
these are always read-only since it's a read-only file system. That way
we might also catch similar cases with other container formats which
also use
15.5-1 is part of Ubuntu since at least 16.04 LTS Xenial.
** Changed in: funcoeszz (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/518572
Title:
which case.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
-
** Changed in: backuppc (Ubuntu)
Status: New => In Progress
** Changed in: backuppc (Ubuntu)
Assignee: (unassigned) => Axel Beckert (xtaran)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Changed in: backuppc (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349031
Title:
ping6 is not configurable over web ui
To manage
symptoms in
the according Debian bug report at https://bugs.debian.org/906767
The issue was caused by a more picky dc (the command used to do the
calculations) which was erroring out when piping a "q" command into
it.
Hence marking as duplicate of #1788681.
Regards, Axe
ly merge all these bug reports.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593
*** This bug is a duplicate of bug 1775673 ***
https://bugs.launchpad.net/bugs/1775673
Axel Beckert wrote:
> No, if I remember correctly, "ruby-something" is the
> RedHat/Fedora/CentOS way of naming ruby library packages while
> Debian/Ubuntu uses "something-ruby&quo
** Also affects: tpp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: tpp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775673
Title:
e
Debian/Ubuntu uses "something-ruby".
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E
*** This bug is a duplicate of bug 1775673 ***
https://bugs.launchpad.net/bugs/1775673
Axel Beckert wrote:
> And https://github.com/cbbrowne/tpp/issues/9 looks unrelated for me:
> Completely different error message, C linking error (Github) vs ruby
> module location error (her
*** This bug is a duplicate of bug 1775673 ***
https://bugs.launchpad.net/bugs/1775673
** This bug has been marked a duplicate of bug 1775673
ruby-ncurses is broken in ubuntu 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is very likely https://bugs.debian.org/910317 ("QtWebEngine in
unstable is constantly crashing").
** Bug watch added: Debian Bug tracker #910317
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910317
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yes, this is a known, long-standing issue, tracked in Debian at
https://bugs.debian.org/509100 (and some more duplicates of that bug
report).
** Changed in: aptitude (Ubuntu)
Status: New => Confirmed
** Bug watch added: Debian Bug tracker #509100
Thanks for the bug report!
JFTR: The line in the subject is not the error message but only the
report _that_ something has failed. The actual error message is in
DpkgTerminalLog.txt and the cause is this:
Traceback (most recent call last):
File "/usr/share/wicd/daemon/wicd-daemon.py", line
aptitude-gtk is long gone. Even Ubuntu 12.04 LTS Precise has the
aptitude source package version (0.6.6-1 respectively 0.6.6-1ubuntu1)
with which the aptitude-gtk binary package was dropped.
And in case this issue was also present with aptitude-curses (which
remained), this issue is at least
zsh in Debian Unstable (5.6.2-1) seems to build fine if I exchange
libpcre3-dev by libpcre2-dev in Build-Depends and Build-Using (via
debian/rules).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ck to Incomplete. I'll revert that commit from the recent 5.6.2-2
upload.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-|
Why is network-manager running while wicd is being used? They likely
interfere which each other. Does this also happen if you stop network-
manager (i.e. "sudo service network-manager stop") and then connect to a
wifi with wicd?
(They're co-installable on purpose, to be able to switch between
** Changed in: xymon (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819378
Title:
package xymon 4.3.28-3build1 failed to install/upgrade:
** Changed in: xymon (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819378
Title:
package xymon 4.3.28-3build1 failed to install/upgrade: installed
l admin.
And this is actually a case we definitely need to handle better. I've
filed https://bugs.debian.org/924665 in Debian for that.
P.S.: Thanks to Thomas' variant of this issue, I became aware of the
fact that this issue might also happen if you just tried to clean up
your /etc/ from seemingly u
mands generally work on Linux, too. Point is just that they
don't undo things which have been commented out from .zshrc. Hence you
need to start a new zsh everytime you comment out or remove something
from your .zshrc.
Regards, Axel
--
,''`. | Axel Beckert , https://people.debi
u have debsums installed, does "debsums -e zsh-common" show any
modified files under /etc/zsh/? Because "zsh -f" also skips them (or
at least some of them).
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Develope
Hi Mohammad,
Mohammad Shoriful Islam Ronju wrote:
> ~/.zshenv is not there. debsums was not installed. I installed it and
> attached the output.
Thanks! Unfortunately I'm starting to run out of ideas what else could
cause this issue. :-(
Regards, Axel
--
,''`. | Axel B
> Also followed this tutorial but same result.
Which tutorial? There was no link except to the screen shot in your
message...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819949
Title:
ZSH not
overkill if you can use "which"
* The user shoudn't use usermod as root (sudo …) to change a user shell
but chsh (as you did).
* There's no need to reboot just to make a change of a user shell
effective.
Regards, Axel
--
,''`. | Axel Beckert , https://
Pull-request at upstream (with commits from someone with a canonical.com
e-mail address :-): https://github.com/aabc/ipt-netflow/pull/110
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813061
Title:
Attached a dkms.log from iptables-netflows-dkms 2.3-5 building against
linux-headers-5.0.0-3-generic and linux-libc-dev version 5.0.0-3.4.
Will report this issue to upstream.
** Attachment added: "dkms.log of building against linux 5.0.0-3.4"
Forwarded to upstream at https://github.com/aabc/ipt-netflow/issues/108
** Bug watch added: github.com/aabc/ipt-netflow/issues #108
https://github.com/aabc/ipt-netflow/issues/108
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think I found them at https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/unstable
** Changed in: iptables-netflow (Ubuntu)
Status: Incomplete => New
** Changed in: iptables-netflow (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you
Where can I get these linux-*-5.0.0-1.2 packages for debugging this
issue? Can't find them in a standard disco pbuilder chroot.
And unfortunately the above download links don't seem to contain
relevant artifacts like the DKMS build log.
** Changed in: iptables-netflow (Ubuntu)
Status: New
> > What do you exactly mean by "setting ZSH as the default shell"?
>
> I just mean using chsh to set the default login shell. /bin/sh is left
> unchanged.
JFTR: "default" is still the wrong term for this. There is only _one_
login shell per user. "default" always suggests that there are others
** Changed in: iptables-netflow (Ubuntu)
Assignee: (unassigned) => Axel Beckert (xtaran)
** Changed in: iptables-netflow (Ubuntu)
Status: Confirmed => In Progress
--
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 1830047 ***
https://bugs.launchpad.net/bugs/1830047
This has been fixed upstream in https://github.com/aabc/ipt-
netflow/commit/fd37b58a81c3df1f375fe784547b77b7a9d1ebc4.
I don't know if this also fixes compilation with kernel 5.2.
--
You received this bug
Compilation with kernel 5.1 has been fixed upstream in
https://github.com/aabc/ipt-
netflow/commit/fd37b58a81c3df1f375fe784547b77b7a9d1ebc4.
I don't know if this also fixes compilation with kernel 5.2 (i.e. if
#1827106 really is a duplicate of this bug).
--
You received this bug notification
zsh is not really fixed. Please see the changelog entry of 5.6.2-3 which
states:
* [92175749] Revert "Switch from the deprecated libpcre3 to the newer
(!) libpcre2." libpcre2 is not a drop-in replacement and not detected
by zsh's configure script. (Closes: #909084, reopens LP#1792544)
** Bug watch added: Debian Bug tracker #931794
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931794
** Also affects: fwupd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931794
Importance: Unknown
Status: Unknown
--
You received this bug notification because
@superm1: #1820768 looks completely unrelated to me. Additionally, this
still happens with 1.2.6-1 as currently in Debian Unstable.
This issue has been fixed upstream in
https://github.com/hughsie/fwupd/pull/1144 (Original upstream bug report
at https://github.com/hughsie/fwupd/issues/1139)
**
I'm sorry, but I can't reproduce this issue in a clean 18.04 chroot:
aptitude is installed at version 0.8.10-6ubuntu1, too, and has a
dependency on libsigc++-2.0-0v5 (version 2.10.0-2 installed as in your
case) which contains /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0.
And aptitude works for me.
** Changed in: aptitude (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851925
Title:
Fresh install of aptitude is broken - missing dependency?
To
rds, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
--
You received this bug notificat
I can confirm this behaviour with any hostname I tried (including e.g.
www.google.com).
The "problem" seems the interaction between links2 and "torsocks" (and
also "torify" which does more or less the same).
It surely not a DNS or TLD detection issue, because both, "links2
** Summary changed:
- FTBFS on Lucid with pbuilder or as user plus fakeroot: configure: WARNING:
unrecognized options: --without-smbmount
+ samba: FTBFS on Lucid with pbuilder or as user plus fakeroot: configure:
WARNING: unrecognized options: --without-smbmount
--
You received this bug
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1098531
Title:
Wrong path to global config files mentioned in man page
To manage notifications about this bug go to:
This has been fixed in 5.2-3ubuntu1 (i.e. with Yakkety) when these
ubuntu-specific changes were dropped:
* Drop yodl from Build-Depends.
* prebuild docs.
** Changed in: zsh (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
> There seems to be a fix on github... (since july 2018!)
Yes, and according to the fping version you mentioned, you're running
Ubuntu 18.04 Bionic from _April_ 2018. So that Ubuntu release was
released before the bug was fixed upstream.
Upgrading to a more recent version of Ubuntu will fix this
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860323
Title:
fping not working if ipv6 is disabled
To manage notifications about this bug go to:
installed" flag, e.g. via "apt-mark auto".
2. The installation image already contained these flags for some
reason, but since apt-get (and partially apt) doesn't automatically
remove these packages, the creator of the image didn't care about
these flags and this only surface
** Changed in: aptitude (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859314
Title:
aptitude deletes drivers manager(?)
To manage notifications about
It's not your .zshrc (which would be in your home directory) but the
system's /etc/zsh/zshrc which has been deleted and tried to compare.
This issue seems though unrelated to the deletion of /etc/zsh/zshrc,
with which at coped properly:
Configuration file '/etc/zsh/zshrc'
==> Deleted (by you or
Uploaded the fix to Debian Unstable. Should reach Ubuntu Groovy via
automatic sync from Debian Unstable.
** Changed in: fping (Ubuntu)
Status: New => Fix Committed
** Changed in: fping (Ubuntu)
Assignee: (unassigned) => Axel Beckert (xtaran)
--
You received this bug notifi
@paelzer: This does not sound like exiting the last shell inside the
screen session but closing the xterm/gnome-terminal/lxterminal etc. it
is running in. (Back to "New" for that.)
So in the end this sounds a lot like one of these annoying systemd bugs,
e.g. similar to
Nope. It's exactly as it should be for packages with a collection of
small tools like e.g. debian-goodies or devscripts:
* Dependencies of all or at least most tools are in Depends.
* Hard dependencies which just appear in one or very few tools are in
Recommends. (Other tools in the package are
debsums uses MD5 because dpkg uses MD5.
** Also affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #849377
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849377
** Also affects: debsums (Debian) via
On a first glance, this looks more like an issue in oh-my-zsh than in
zsh.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882366
Title:
After Installed Oh My Zsh, in taskbar shortcut icon widgets
Note: The cited commit and "fix" was in the package ruby, but the
problem in ruby-curses still exists as ruby only silenced the
deprecation warnings by default.
** Summary changed:
- irqtop emits a warning
+ ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0",
affects at
This is an issue in ruby-curses, not irqtop. See https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=958973
Interestingly this no more happens on Debian Unstable/Testing. This
seems to have fixed upstream a few months ago:
commit df3f52a6331f1a47af9933b77311a8650727d8d1
Author: nagachika
4.4.0-2 is in hirsute-proposed (and in Debian Testing).
** Changed in: backuppc (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.launchpad.net/bugs/1723392
Title:
I assume that since https://bugs.debian.org/910317 is fixed for a long
time, this issue is no more present either.
Please file a new bug report if you still can reproduce this (or seeming
identical) issues in recent versions of qutebrowser, e.g. 1.14.1 or
2.0.1 and above.
** Changed in:
Marking as "fix release" as Ubuntu already has 4.8.0-1.
** Changed in: screen (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.net/bugs/1915205
Title:
CVE-2020-9366
Actually this never made it into any LTS release as only 4.7.x versions
were affected and 18.04 has a 4.6.x version and 20.04 has 4.8.0.
** Bug watch added: Debian Bug tracker #950896
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950896
** Also affects: screen (Debian) via
** Bug watch added: Debian Bug tracker #18
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18
** Also affects: zsh (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=18
Importance: Unknown
Status: Unknown
--
You received this bug notification because
@crashbit-gmail: There was no update of zsh in Jammy so far. If an
update fixed this, it was not in zsh but maybe in a library. And indeed,
one day after this bug report, glibc 2.35 (as mentioned in the missing
symbol) got uploaded to jammy as well:
@alecos85: "No solution" is not true. That bug has been closed by the
reporter that upgrading qutebrowser to a more recent version has solved
the issue. (Although I suspect that actually an Qt upgrade in the same
timeframe was the real reason for this being fixed. See upstream's
comment in that
** Bug watch added: Debian Bug tracker #960384
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960384
** Also affects: qutebrowser (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960384
Importance: Unknown
Status: Unknown
--
You received this bug notification
ug report on qutebrowser's page.
Could help as well although I suspect that he will ask to try out
falkon as well. But maybe he knows a workaround (in case it's indeed a
Qt issue).
Regards, Axel
--
,''`. | Axel Beckert , https://people.debian.org/~abe/
: :' : | Debian Developer, ft
Seems to be an Ubuntu-only issue. Can't reproduce on Debian Unstable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960842
Title:
failed to load module `zsh/mathfunc':
** Package changed: aptitude (Ubuntu) => apt (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960727
Title:
When apt holds back updates, it fails to inform the user of the reason
To manage
If you can still reproduce this, can you run "aptitude-create-state-
bundle lp-1959485-crash-dist-upgrade.tbz2" and send me the resulting tar
ball?
(You probably need to upload the tar-ball somewhere as these can have a
size around several hundred megabytes. Not sure if Launchpad can host
such
Closing as fix-released since the fix should now be also in the most
recent Ubuntu LTS version (i.e. Ubuntu 20.04 LTS).
** Changed in: fping (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
601 - 695 of 695 matches
Mail list logo
