[Bug 1650890] Re: package dphys-swapfile 20100506-1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
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 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843160 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650890 Title: package dphys-swapfile 20100506-1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dphys-swapfile/+bug/1650890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1496216] Re: package dphys-swapfile 20100506-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** 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. https://bugs.launchpad.net/bugs/1496216 Title: package dphys-swapfile 20100506-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dphys-swapfile/+bug/1496216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650890] Re: package dphys-swapfile 20100506-1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
*** 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 package dphys-swapfile 20100506-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650890 Title: package dphys-swapfile 20100506-1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dphys-swapfile/+bug/1650890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650890] Re: package dphys-swapfile 20100506-1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
*** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650890 Title: package dphys-swapfile 20100506-1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dphys-swapfile/+bug/1650890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788681] Re: changed exit code for 'dc' in Ubuntu Bionic
Hi Wladimir, Wladimir Mutel wrote: > in Ubuntu Xenial : > $ lsb_release -rdc ; echo 1 1 + p q | dc ; echo $? > Description:Ubuntu 16.04.4 LTS > Release:16.04 > Codename: xenial > 2 > 0 > > in Ubuntu Bionic : > $ lsb_release -rdc ; echo 1 1 + p q | dc ; echo $? > Description:Ubuntu 18.04.1 LTS > Release:18.04 > Codename: bionic > 2 > 1 > > This change causes some scripts using 'dc' to fail, most importantly, > 'dphys-swapfile' Thanks for that bug report. This might be the cause for https://bugs.debian.org/906767 which I'm currently trying to fix. > which for some ironic reason uses 'dc' instead of 'echo > $((...))' for its calculations. That's upstream's decision. And since I know that upstream also runs rather old Unices, I assume it's because $(( ... )) might not be available in all shells. According to https://en.wikipedia.org/wiki/Comparison_of_command_shells#cite_ref-57 it should though be available in all relevant shells since 1992. The relevant change in dc seems to be from 1.3 to 1.4: Detects and reports on any output errors; exits non-success. The fix seems simple: Drop the "q": ~ → echo 1 1 + p q | dc ; echo $? 2 1 ~ → echo 1 1 + p | dc ; echo $? 2 0 Will have to check if that's indeed the cause for https://bugs.debian.org/906767, but will do a new upload to Debian Unstable in either case. Someone else will need to take care of a regression fix for bionic though. 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 ** 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) => Axel Beckert (xtaran) ** Changed in: dphys-swapfile (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/1788681 Title: changed exit code for 'dc' in Ubuntu Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bc/+bug/1788681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788681] Re: changed exit code for 'dc' in Ubuntu Bionic
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bc/+bug/1788681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789570] Re: debsums runs concurrently with unattended-upgrades which leads to false positives
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 over that package.) Might be an idea to clean up and deduplicate them a little bit. This would also make it easier to add such a feature to the cron job (in case me or the Debian Perl Team decides that that's the proper place to implement this). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789570 Title: debsums runs concurrently with unattended-upgrades which leads to false positives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debsums/+bug/1789570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1761997] Re: /var/run needs mode 777 in bionic
Hi Brian,
Brian Murray wrote:
> + 2) rm /etc/cron.daily/mlocate (this'll ensure you get a conffile prompt)
> + 3) ssh to Ubuntu 16.04 system so the release upgrade is run in screen
> + 4) run do-release-upgrade -d
> + 5) wait for the conffile prompt from mlocate
> + 6) ssh to the Ubuntu 16.04 system being upgraded
> + 7) sudo -i
> + 8) run screen -rd
> +
> + With the version of screen in the release pocket you'll receive the
> + following error:
> +
> + root@clean-xenial-amd64:~# screen -rd
> + Directory '/run/screen' must have mode 777.
Thanks for the detailed explanations.
This sounds a little bit like screen being already unpacked, but not
yet configured. But there must be more than that…
Can you check what permissions /run/screen actually has at that point?
What I don't understand is: Since screen is already running at that
point, /run/screen should already exist with the proper permissions
from either /etc/tmpfiles.d/screen-cleanup.conf or from
/etc/init.d/screen-cleanup from 16.04's screen package. And according
to the changelog (in Debian at least), nothing in the maintainer
scripts changed between 4.3.1-2 and 4.6.2-1. And git log shows only
two commits since June 2015 (where /etc/tmpfiles.d/ support was
finalized), of which one just renames the files and the other one
replaces /var/run/ with /run/ — which both should be defacto noop with
regards to their logic.
Does any other package modify /run/'s permissions 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 1D89 9593 0EDE
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761997
Title:
/var/run needs mode 777 in bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1761997/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781295] Re: CVE-2018-10895: Possible remote code execution via CSRF in qute://settings
** 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qutebrowser/+bug/1781295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782456] Re: [CVE] Remote code execution due to CSRF on the qute://settings page
*** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782456 Title: [CVE] Remote code execution due to CSRF on the qute://settings page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qutebrowser/+bug/1782456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782639] Re: package flwm 1.02+git2015.10.03+7dbb30-6 failed to install/upgrade: installed flwm package post-installation script subprocess returned error exit status 255
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 out in such situations. Maybe it should just skip such files and issue a warning like the other two warnings about wrong encoding in .desktop files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782639 Title: package flwm 1.02+git2015.10.03+7dbb30-6 failed to install/upgrade: installed flwm package post-installation script subprocess returned error exit status 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flwm/+bug/1782639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1761997] Re: /var/run needs mode 777 in bionic
Hi, Brian Murray wrote: > Ah I think it (the tmpfile isn't created) because /usr/bin/screen is > 2755 in Ubuntu 16.04 but 755 in Ubuntu 18.04. Here's the change between > the two releases. Ah! That's due to switching to use libutempter. We're getting quite close to the issue. I though wonder how to fix that for Bionic in the best way. Maybe adding something like this to screen.preinst (not postinst): perms="`stat -c%a /usr/bin/screen`" override=/etc/tmpfiles.d/screen-cleanup.conf if [ $perms -eq 2755 ]; then chmod 0777 /var/run/screen [ -f $override ] || echo 'd /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, 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761997 Title: /var/run needs mode 777 in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1761997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1761997] Re: /var/run needs mode 777 in bionic
Hi Brian,
Brian Murray wrote:
> /run/screen has the following permissions
>
> drwxrwxr-x 3 root utmp60 Jul 19 06:06 screen
Thanks. This is indeed not the expected setting.
> screen-cleanup is a masked service in response to bug 1462692, so the
> permissions of /run/screen are never changed in Ubuntu 16.04.
Hrm, but 4.3.1-2build1 in 16.04 should also already have generated
/etc/tmpfiles.d/screen-cleanup.conf during postinst. (That was fixed
in the same upload as #1462692.)
And 16.04 already had systemd as default if not only init system.
> bdmurray@clean-xenial-amd64:~$ sudo service screen-cleanup status
> [sudo] password for bdmurray:
> ● screen-cleanup.service
>Loaded: masked (/dev/null; bad)
>Active: inactive (dead)
> bdmurray@clean-xenial-amd64:~$ ls -lh
> /lib/systemd/system/screen-cleanup.service
> lrwxrwxrwx 1 root root 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/
: :' : | 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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761997
Title:
/var/run needs mode 777 in bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1761997/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1761997] Re: /var/run needs mode 777 in bionic
Hi Brian, Brian Murray wrote: > Alex - I don't think that will work because when the new version of > screen is unpacked the permissions are 755, so the check would need to > be for 755, not 2755. No. I said into _pre_inst, not postinst, so that everything is in place and fixed when screen 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 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761997 Title: /var/run needs mode 777 in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1761997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783564] Re: There is no Ncurses-Ruby package installed which is needed by TPP
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: github.com/cbbrowne/tpp/issues #9 https://github.com/cbbrowne/tpp/issues/9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783564 Title: There is no Ncurses-Ruby package installed which is needed by TPP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpp/+bug/1783564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781295] Re: CVE-2018-10895: Possible remote code execution via CSRF in qute://settings
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qutebrowser/+bug/1781295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781295] Re: CVE-2018-10895: Possible remote code execution via CSRF in qute://settings
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: CVE-2018-10895: Possible remote code execution via CSRF in qute://settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qutebrowser/+bug/1781295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781295] [NEW] CVE-2018-10895: Possible remote code execution via CSRF in qute://settings
*** 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 fixed in 1.4.1 uploaded to Debian Unstablea few hours ago. Patches for earlier releases are available upstream. Details at upstream and OSS security: http://www.openwall.com/lists/oss-security/2018/07/11/7 https://github.com/qutebrowser/qutebrowser/issues/4060 Introduced in: https://github.com/qutebrowser/qutebrowser/commit/ffc29ee (v1.0.0) Fixed in: https://github.com/qutebrowser/qutebrowser/commit/43e58ac865ff862c2008c510fc5f7627e10b4660 (v1.4.1) Ubuntu is affected in Bionic (1.1.1-1) and Cosmic (1.4.0-1). ** Affects: qutebrowser (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic ** 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/1781295 Title: CVE-2018-10895: Possible remote code execution via CSRF in qute://settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qutebrowser/+bug/1781295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 75332] Re: aptitude has private package holds, should use dpkg
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 -- ,''`. | 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 1D89 9593 0EDE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/75332 Title: aptitude has private package holds, should use dpkg To manage notifications about this bug go to: https://bugs.launchpad.net/update-manager/+bug/75332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1370416] Re: Security updates are not marked as security
** 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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370416 Title: Security updates are not marked as security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1370416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1370416] Re: Security updates are not marked as security
Hi, Rolf Leggewie wrote: > I would look into pinning, can this possibly help here? No, this has nothing to do with pinning at all. This is a known issue with aptitude. Have a look at the function is_security() in src/generic/apt/apt.cc: aptitude only regards as security update if the repository is from security.debian.org or security.*.debian.org, at least in Debian. So I assume that Ubuntu patches those lines towards security.ubuntu.com as used in his German sources.list. But his "central" sources.list doesn't have security.ubuntu.com anywhere. He uses e.g. "deb http://archive.ubuntu.com/ubuntu trusty-security main restricted" there. And hence it's not recognised. I thought there was an upstream (Debian) bug report about that (as I am aware of the issue :-), but I couldn't find it on a first glance. Will file one and link it here. 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 1D89 9593 0EDE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1370416 Title: Security updates are not marked as security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1370416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761997] Re: /var/run needs mode 777 in bionic
Steve Langasek wrote: > I believe this is a bug in screen. The postinst script has code to > handle the changed requirements for /run/screen permissions, but then > immediately afterwards a debhelper code snippet runs which clobbers them > again. I currently don't see that clobbering, at least not in Debian: The maintainer-written code creates /etc/tmpfiles.d/screen-cleanup.conf in most cases. It also links /lib/systemd/system/screen-cleanup.service to /dev/null. debhelper-generated code seems to create /usr/lib/tmpfiles.d/screen-cleanup.conf — which is overridden by /etc/tmpfiles.d/screen-cleanup.conf if it exists. If it is not created because neither of the two conditions in the maintainer code is given, I don't see how something which is not created can be clobbered. So please elaborate where you see the bug in screen's postinst. Setting to "invalid" 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/ : :' : | 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: screen (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761997 Title: /var/run needs mode 777 in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1761997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798557] Re: xymon-client and snaps, client report gets red in disk, inode, misc states
** 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, inode, misc states To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hobbit-plugins/+bug/1798557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798557] Re: xymon-client and snaps, client report gets red in disk, inode, misc states
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 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, inode, misc states To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hobbit-plugins/+bug/1798557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798557] Re: xymon-client and snaps, client report gets red in disk, inode, misc states
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 squashfs. Thanks for the bug report! ** Changed in: xymon (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, inode, misc states To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hobbit-plugins/+bug/1798557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518572] Re: Update funcoeszz version
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: Update funcoeszz version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/funcoeszz/+bug/518572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1800280] [NEW] Setting ZSH as the default shell causes various issues because it doesn't source /etc/profile
Hi Martin,
Martin wrote:
> When setting ZSH as the default shell, /etc/profile is never sourced
What do you exactly mean by "setting ZSH as the default shell"?
A) Using it as login shell for a specific user.
B) Letting the /bin/sh symlink point to it.
Case B is definitely not supported and explicitly discouraged by
upstream.
> /etc/profile.d/apps-bin-path.sh adds /var/lib/snapd/desktop to
> XDG_DATA_DIRS. Setting the default shell to ZSH means that desktop
> environments suddenly can't launch snap packages.
This sounds more like case B to me.
> Arch Linux's zsh package has `emulate sh -c 'source /etc/profile'` in
> /etc/zsh/zprofile. Either Ubuntu's zsh package should do the same (or
> something similar), or Ubuntu must put important environment variable
> stuff somewhere else and have only bash-specific stuff in /etc/profile
> and /etc/profile.d.
IMHO the latter needs to happen. Zsh upstream does not source
/etc/profile and users won't expect it to do that and doing it will
probably cause other user irritations and unexcpected subtle side
effects.
See https://tanguy.ortolo.eu/blog/article25/shrc for reference what
each shell loads in 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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800280
Title:
Setting ZSH as the default shell causes various issues because it
doesn't source /etc/profile
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1800280/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349031] Re: ping6 is not configurable over web ui
** 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.net/bugs/1349031 Title: ping6 is not configurable over web ui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1349031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349031] Re: ping6 is not configurable over web ui
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc/+bug/1349031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795289] Re: dphys-swapfile will not re-calculate swap file size or re-install
*** This bug is a duplicate of bug 1788681 *** https://bugs.launchpad.net/bugs/1788681 Hi, Launchpad Bug Tracker wrote: > A commenter there suggested I file this as a bug because Ubuntu > doesn't execute the /bin/sh script correctly. Well, that's not exactly precise... > I have made modifications to the sh script and now it works. I doubt that it works now, i.e. that the correct calculations are done now. It seems to just no more exit on failure anymore and hence hides the actual problem (which IMHO is worse). > It appears that sudo apt install dphys-swapfile runs the /bin/sh > scripts correctly on Ubuntu 18.04 > > However on re-use of the /sbin/dphys-swapfile the /bin/sh arithmitic > calculations fail. That's probably because it takes different code paths depending on the swap file already existing or not. > After putting some echo debugs around the place and after inspecting the > code, I notice that re-calculations should have echoed out a lot more > text when using the setup/install parameters. After more debugging I > noticed that it is the lines with arithmitic calculations that are > exiting out/erring out. Correct. _They_ are _erroring_ out, not /bin/sh. /bin/sh just exits due to the error of something it called because it has been told so with "set -e". > So what I did is changed the shebang from /bin/sh to /bin/bash and added > let in front of all the lines with calculations. The "let" is probably what makes the error go away because it probably doesn't pass the exit code and hence dphys-swapfile doesn't exit anymore on error in the calculations. > Underneath is a copy of my fixed dphys-swapfile script from /sbin/dphys- > swapfile you need to edit this with sudo. Please just send in a diff of your changes the next time. Anyways, looking at https://askubuntu.com/q/1079860 this shows the same symptoms as #1788681 (which has been reported against 18.04, but so far only been fixed in cosmic with the upload of dphys-swapfile/20100506-5) respectively the more detailed 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, 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 ** This bug has been marked a duplicate of bug 1788681 changed exit code for 'dc' in Ubuntu Bionic ** Bug watch added: Debian Bug tracker #906767 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906767 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795289 Title: dphys-swapfile will not re-calculate swap file size or re-install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dphys-swapfile/+bug/1795289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1783564] Re: There is no Ncurses-Ruby package installed which is needed by TPP
*** This bug is a duplicate of bug 1775673 *** https://bugs.launchpad.net/bugs/1775673 Hi John, John Flood wrote: > Unfortunately, the link to ncurses-ruby in the error message (http > ://ncurses-ruby.berlios.de/) doesn't work, but this one does: Yes, the BerliOS code hosting is dead for quite some years now. > https://github.com/sup-heliotrope/ncursesw-ruby That's also what the ruby-ncurses package has set as Homepage. > However, I had trouble installing it until I ran > > sudo apt-get install ruby-dev zlib1g-dev liblzma-dev > > as recommended here: > > https://stackoverflow.com/questions/44239377/cant-install-rails-on- > linux-failed-to-build-gem-native-extension-with-ruby-2 > > Then "gem install ncursesw" worked (after cloning the above github > repository) and I could open the sample files for tpp. That's interesting. So since the ruby-ncurses package is built from the same source (just maybe a different version), it's either a bug in the version shipped with Ubuntu 18.04 or something in the way Ubuntu builds that package. (As mentioned before: I can't reproduce this in Debian Unstable where Ubuntu takes most of the packages, at least tpp, from.) And if you look at https://bugs.launchpad.net/ubuntu/+source/ruby-ncurses you probably see the reason for it: #1775673 ruby-ncurses is broken in ubuntu 18.04 #1787763 ruby-ncurses is broken: try ruby -e 'require "ncurses"' Will probably 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 0EDE ** 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 Ubuntu. https://bugs.launchpad.net/bugs/1783564 Title: There is no Ncurses-Ruby package installed which is needed by TPP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpp/+bug/1783564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1783564] Re: There is no Ncurses-Ruby package installed which is needed by TPP
*** 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". Actually it's vice-versa, but you probably got the idea anyways. :-) 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783564 Title: There is no Ncurses-Ruby package installed which is needed by TPP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpp/+bug/1783564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775673] Re: ruby-ncurses is broken in ubuntu 18.04
** 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: ruby-ncurses is broken in ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-ncurses/+bug/1775673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1783564] Re: There is no Ncurses-Ruby package installed which is needed by TPP
Hi John,
John Flood wrote:
> Synaptic installed "ruby-ncurses", but the message refers to "ncurses-
> ruby"! Is that an issue?
No, if I remember correctly, "ruby-something" is the
RedHat/Fedora/CentOS way of naming ruby library packages while
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 C09E 1D89 9593 0EDE
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783564
Title:
There is no Ncurses-Ruby package installed which is needed by TPP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tpp/+bug/1783564/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1783564] Re: There is no Ncurses-Ruby package installed which is needed by TPP
*** 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 (here). Must correct myself here: It seems that tpp thinks it can't find the ncurses bindings if it can't load them, even if they are there, but broken. Nevertheless, since the above case is on Arch Linux, it might have the same cause as on Ubuntu, but this issue is distribution-specific since it's not present in the current upstream (or development versions) and hence needs to be fixed per distribution, e.g. by patching or, if sufficient, by recompiling ruby-ncurses. 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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783564 Title: There is no Ncurses-Ruby package installed which is needed by TPP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpp/+bug/1783564/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787763] Re: ruby-ncurses is broken: try ruby -e 'require "ncurses"'
*** 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 Ubuntu. https://bugs.launchpad.net/bugs/1787763 Title: ruby-ncurses is broken: try ruby -e 'require "ncurses"' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-ncurses/+bug/1787763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796034] Re: lubuntu 18.10 falkon nouveau test on qutebrowser crashed with SIGSEGV in __GI_____strtoul_l_internal()
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 is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796034
Title:
lubuntu 18.10 falkon nouveau test on qutebrowser crashed with SIGSEGV
in __GI_strtoul_l_internal()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qutebrowser/+bug/1796034/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793903] Re: aptitude build-dep fails on virtual packages
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 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509100 ** Also affects: aptitude (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509100 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793903 Title: aptitude build-dep fails on virtual packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1793903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804442] Re: package wicd-daemon 1.7.4+tb2-6 failed to install/upgrade: installed wicd-daemon package post-installation script subprocess returned error exit status 1
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 1954, in main(sys.argv) File "/usr/share/wicd/daemon/wicd-daemon.py", line 1798, in main os.chmod(backup_location, 0644) OSError: [Errno 2] No such file or directory: '/var/lib/wicd/resolv.conf.orig' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804442 Title: package wicd-daemon 1.7.4+tb2-6 failed to install/upgrade: installed wicd-daemon package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wicd/+bug/1804442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604750] Re: aptitude-gtk will not display Ubuntu changelogs
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 fixed with Ubuntu 16.04.5 LTS Xenial: → aptitude changelog aptitude | head -2 Get: Changelog of aptitude aptitude (0.7.4-2ubuntu2) xenial; urgency=high Hence closing. ** Changed in: aptitude (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/604750 Title: aptitude-gtk will not display Ubuntu changelogs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/604750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
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. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792544] Re: demotion of pcre3 in favor of pcre2
Hi, Andreas Hasenack wrote: > I've seen the wget debian change, but just switching builddeps from pcre3-dev > to pcre2-dev and rebuilding isn't enough. The package ends up not finding > pcre and doesn't enable it: > checking for PCRE... no > checking pcre.h usability... no > checking pcre.h presence... no > checking for pcre.h... no > ... > Libs: -luuid -lidn2 -lnettle -lgnutls -lz -lpsl > > So while the package builds, it's not using pcre. > > I tried to switch apache, and while I could make it find pcre2-config and use > it, pcre2 has different libraries than pcre3: > pcre3-config --libs: -lpcre > pcre2-config --libs: no such parameter > > In pcre2, we have --libs8, --libs-posix, --libs32 and --libs16, but no > --libs. Is this a bug in pcre2-config? Indeed, same for zsh: checking for pcre-config... no checking pcre.h usability... no checking pcre.h presence... no checking for pcre.h... no checking for pcre_compile... no checking for pcre_study... no checking for pcre_exec... no [...] ../../Test/V07pcre.ztst: starting. ../../Test/V07pcre.ztst: skipped (the zsh/pcre module is not available) → Back 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 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE ** Changed in: zsh (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 in favor of pcre2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812778] Re: internet connection randomly stops working
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 them, but they shouldn't be running at the same time.) ** Changed in: wicd (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/1812778 Title: internet connection randomly stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wicd/+bug/1812778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819378] Re: package xymon 4.3.28-3build1 failed to install/upgrade: installed xymon package post-installation script subprocess returned error exit status 1
** 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: installed xymon package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1819378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819378] Re: package xymon 4.3.28-3build1 failed to install/upgrade: installed xymon package post-installation script subprocess returned error exit status 1
** 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 xymon package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1819378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819378] Re: package xymon 4.3.28-3build1 failed to install/upgrade: installed xymon package post-installation script subprocess returned error exit status 1
Dear Sukhvir,
thanks for your bug report.
sukhvir wrote:
> I was trying to install xymon on ubuntu 18.4 lts, I am getting following
> error.
> chgrp: cannot access 'critical.cfg': No such file or directory
> chgrp: cannot access 'critical.cfg.bak': No such file or directory
> dpkg: error processing package xymon (--configure):
> installed xymon package post-installation script subprocess returned error
> exit status 1
[...]
> modified.conffile..etc.xymon.alerts.cfg: [deleted]
> modified.conffile..etc.xymon.analysis.cfg: [deleted]
> modified.conffile..etc.xymon.cgioptions.cfg: [deleted]
> modified.conffile..etc.xymon.client-local.cfg: [deleted]
> modified.conffile..etc.xymon.columndoc.csv: [deleted]
> modified.conffile..etc.xymon.combo.cfg: [deleted]
> modified.conffile..etc.xymon.critical.cfg: [deleted]
> modified.conffile..etc.xymon.critical.cfg.bak: [deleted]
> modified.conffile..etc.xymon.graphs.cfg: [deleted]
This is caused by the following (IMHO rather uncommon) case that
* the package xymon had been installed beforehand (not explicitly
mentioned, but obvious due to the deleted conffiles),
* has been removed again (but not purged, otherwise dpkg wouldn't know
about the conffiles),
* then someone deleted /etc/xymon/ manually (otherwise not all
conffiles would have been deleted),
* and tried to install xymon again.
Removing /etc/xymon/ (or any other conffile of any other package)
without purging ("apt-get purge" or "apt-get remove --purge") a
package makes dpkg think that the system administrator on purpose
remove these conffiles and hence respects this decision and doesn't
unpack them again.
While having removed _all_ conffiles manually without purging the
package, too, is theoretically a valid setup, it's nevertheless a
broken setup and breakage has to be expected then IMHO with most
packages.
So I'm not sure if I really should add support to the xymon package
for such a broken environment.
This breakage is btw. easily fixed: Do an "apt-get purge xymon" before
installing the package again. Be aware that this may also remove
monitoring data previously collected with xymon.
Thomas wrote:
> coping critical.cfg to critical.cfg.bak bypassed the error.
I think Thomas' case is slightly different, alone because in the above
case critical.cfg had been deleted, too. I actually expect further
breakage in the above case even if critical.cfg and critical.cfg.bak
are restored.
But Back to Thomas' case:
I though must admit that the file "critical.cfg.bak" (and _only_ that
file) doesn't really look like being relevant and might be deleted by
a local 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 unnecessary backup files.
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
** Bug watch added: Debian Bug tracker #924665
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924665
--
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
xymon package post-installation script subprocess returned error exit
status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1819378/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1819949] Re: ZSH not working
Hi Mohammad, Mohammad Shoriful Islam Ronju wrote: > Running "zsh -f" works fine. Ok. > However comment out all the lines on .zshrc file still didn't work. You need to start a new zsh to test those changes, i.e. open a new terminal or starting zsh from bash. > I'm attaching "/usr/share/bug/zsh 3>&1" commands output here. Thanks. Nothing suspicious on a first glance. > Note: Is there any way to source changed .zshrc file? Tried ". > ~/.zshrc" and "source ~/.zshrc" nothing worked. I use those commands > in mac. These commands 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.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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819949 Title: ZSH not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1819949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1819949] Re: ZSH not working
Hi Mohammad, Mohammad Shoriful Islam Ronju wrote: > Yeah tried opening new terminal every time when commented out a line. > Finally logged out and logged in to check. No luck :( Does a ~/.zshenv exist, too? That one gets sourced before .zshrc (and can change the path for .zshrc). If you 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 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819949 Title: ZSH not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1819949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1819949] Re: ZSH not working
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 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819949 Title: ZSH not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1819949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819949] Re: ZSH not working
> 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 working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1819949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1819949] Re: ZSH not working
Hi Mohammad, Mohammad Shoriful Islam Ronju wrote: > https://linuxhint.com/install_zsh_shell_ubuntu_1804/ Ok, according to this tutorial(*) that prompt in your screenshot is the default prompt from oh-my-zsh -- which doesn't come from any official Ubuntu repo. So please disable oh-my-zsh first and see if that fixes the issue already. If that doesn't fix the issue, please check if running "zsh -f" (disables the parsing of .zshrc; call it e.g. from bash) still shows the issue. If "zsh -f" shows the issue, there is definitively a bug, either in zsh or the terminal. (Since zsh seems to start at least and does not crash, it might also be a terminal issue.) If "zsh -f" works fine, you need to start commenting lines from your .zshrc until the issue vanishes. The last line you commented out then likely caused the issue. If that line is known, one can continue to figure out why that line causes this issue. It might also be helpful if you could post the output of "/usr/share/bug/zsh 3>&1" to see which other packages on your system provide zsh-sourced files. Footnotes: (*) IMHO this tutotal is crap: * "whereis" is 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://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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819949 Title: ZSH not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1819949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2
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: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2
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" https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+attachment/5236406/+files/iptables-netflow-dkms_2.3-5_dkms.log -- 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: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2
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. https://bugs.launchpad.net/bugs/1813061 Title: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813061 Title: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2
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 => Incomplete -- 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: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800280] Re: Setting ZSH as login shell causes various issues because it doesn't source /etc/profile
> > 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 to use if you don't like the default value. But there is none. The "default login shell" is still bash because that's what new users get as their login shell _by default_. I changed the title of the bug report accordingly as it just confused me again. ** Summary changed: - Setting ZSH as the default shell causes various issues because it doesn't source /etc/profile + Setting ZSH as login shell causes various issues because it doesn't source /etc/profile -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800280 Title: Setting ZSH as login shell causes various issues because it doesn't source /etc/profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1800280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813061] Re: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2
** 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. https://bugs.launchpad.net/bugs/1813061 Title: iptables-netflow 2.3-5 ADT test failure with linux 5.0.0-1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1813061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827106] Re: iptables-netflow 2.3-5ubuntu1 ADT test failure with linux 5.1.0-1.1
*** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827106 Title: iptables-netflow 2.3-5ubuntu1 ADT test failure with linux 5.1.0-1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1827106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830047] Re: iptables-netflow 2.3-5ubuntu1 ADT test failure with linux 5.2.0-0.1
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830047 Title: iptables-netflow 2.3-5ubuntu1 ADT test failure with linux 5.2.0-0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1830047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
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) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832377] Re: Cannot handle firmware requirement not-child
** 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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832377 Title: Cannot handle firmware requirement not-child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1832377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832377] Re: Cannot handle firmware requirement not-child
@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) ** Bug watch added: github.com/hughsie/fwupd/issues #1139 https://github.com/hughsie/fwupd/issues/1139 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832377 Title: Cannot handle firmware requirement not-child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1832377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851925] Re: Fresh install of aptitude is broken - missing dependency?
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. Can you run "dpkg -C libsigc++-2.0-0v5" to check if all files of that package are there and undamaged? ** Changed in: aptitude (Ubuntu) Status: Invalid => Incomplete -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1851925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851925] Re: Fresh install of aptitude is broken - missing dependency?
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1851925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1851925] Re: Fresh install of aptitude is broken - missing dependency?
Hi, NeilGreenwood wrote: > That was indeed the problem, which is why i marked this bug as invalid. Yeah, sorry, your second mail and my question crossed each other. I only read your second mail after I'd sent my mail. That's also why I corrected the state afterwards. 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 -- 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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1851925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853458] Re: "host not found" when navigating to dev.lemmy.ml
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 https://dev.lemmy.ml/communities/page/1; as well as "links2 -socks-proxy localhost:9050 -only-proxies 1 https://dev.lemmy.ml/communities/page/1; (which is the official way of using links2 with Tor). And "tor-resolve dev.lemmy.ml" works as expected, too. It is though currently unclear to me, _why_ links2 doesn't seem to work with "torsocks" or "torify". ** Changed in: links2 (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/1853458 Title: "host not found" when navigating to dev.lemmy.ml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/links2/+bug/1853458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920968] Re: samba: FTBFS on Lucid with pbuilder or as user plus fakeroot: configure: WARNING: unrecognized options: --without-smbmount
** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920968 Title: samba: FTBFS on Lucid with pbuilder or as user plus fakeroot: configure: WARNING: unrecognized options: --without-smbmount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/920968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098531] Re: Wrong path to global config files mentioned in man page
** 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: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1098531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098531] Re: Wrong path to global config files mentioned in man page
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 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: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1098531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860323] Re: fping not working if ipv6 is disabled
> 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 as this is fixed in package version 4.1-1 and all later and supported versions of Ubuntu do have at least 4.2-1. So this bug is more or less fixed—also in Ubuntu—from the general point of view. It's just not fixed in Ubuntu 18.04 Bionic. But since this neither a severe nor a security issue, chances that the fix gets backported to 18.04 are not very high. ** Bug watch added: Debian Bug tracker #891704 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891704 ** Also affects: fping (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891704 Importance: Unknown Status: Unknown -- 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: https://bugs.launchpad.net/ubuntu/+source/fping/+bug/1860323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860323] Re: fping not working if ipv6 is disabled
** 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: https://bugs.launchpad.net/ubuntu/+source/fping/+bug/1860323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1859314] [NEW] aptitude deletes drivers manager(?)
Hi, Launchpad Bug Tracker wrote: > 4) script doing autojob (renewing packages since you are connected > to internet. Can you provide this script? Or is it a part of some package? There's a chance that this is the culprit. > 5) aftermath (after instalation) instal aptitude because some pro > said "aptitude is better than apt" If that is true or untrue depends heavily on your use-case and can't be said generally. Both tools have their adavantages and disadvantages. (Saying this with my aptitude package maintainer hat on.) Which tool is better suited for you depends mostly on this things: * If you want - a TUI, or - want to manually interfere with dependency resolution, or - want to be able to match packages with patterns on package properties, or - want to use debtags to select or find package, then aptitude is the right tool for you. But these features come with one drawback: aptitude takes a moment to read (and later save) all the data it needs to provide these features, i.e. it's the slowest of the mentioned tools. * If you prefer - solely the commandline, - prefer a fast program, and - don't want to change the proposed dependency resolutions, and - don't care about a still occasionally changing UI, CLI and output format, then apt (the command) is for you. * If you want to - have a stable UI, CLI and output format - script things, - don't need aptitude's pattern matching for that, and - prefer fast programs then apt-get, apt-cache and friends (from the apt package) are the best tools for you. Additionally the defaults for all three options are slightly different, especially wrt. to automatically removing packages, but also wrt. progress bars, colored output, stable UI/API, etc. > 7) try to install mc --> aptitude install mc > 8) aptitude offering you to UNinstall all proprietary drivers while u just > want to install mc ... One difference between apt-get, apt and aptitude (with default settings) is that apt-get does not remove unused packages automatically but just warns about them. aptitude uninstalls them by default and apt IIRC does something inbetween. In all tools, this setting can be changed, either on the commandline, in configuration files and in aptitude also in the TUI. But the main question in this case is: _What_ marked those drivers as "automatically installed"? None of the tools does this unless these packages were pulled in as a dependency while installing other packages or if the admin explicitly set this flag. (They all share the same database for these flags.) So something must have set that "automatically installed" flag, otherwise aptitude wouldn't have removed them automatically. This can also be seen in the occurrences of "NOT USED" in the provided log. I currently see only two possibilities: 1. The above mentioned, but unknown script fiddled with the "automatically 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 surfaced when aptitude was used. 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 -- 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 this bug go to: https://bugs.launchpad.net/aptitude/+bug/1859314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859314] Re: aptitude deletes drivers manager(?)
** 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 this bug go to: https://bugs.launchpad.net/aptitude/+bug/1859314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873423] Re: package zsh-common 5.8-3ubuntu1 failed to install/upgrade: conffile difference visualiser subprocess returned error exit status 127
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 by a script) since installation. ==> Package distributor has shipped an updated version. It seems not a zsh issue at all but a general release upgrade issue which just happened to happen while handling conffiles of the package zsh-common: *** zshrc (Y/I/N/O/D/Z) [default=N] ? d sh: 1: pager: not found diff: standard output: Broken pipe So for some reason, /usr/bin/pager (or /bin/pager or so) was not available during the release upgrade. /usr/bin/pager is usually /etc/alternatives/pager. Unfortunately, I have not really an idea against which package this could have caused. Reassigning to ubuntu- release-upgrader-core for now. ** Package changed: zsh (Ubuntu) => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873423 Title: package zsh-common 5.8-3ubuntu1 failed to install/upgrade: conffile difference visualiser subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1873423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875242] Re: Do not fail if using fping6 with -6 flag
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875242 Title: Do not fail if using fping6 with -6 flag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fping/+bug/1875242/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900008] Re: Sessions of screen does not keep running in background
@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 https://bugs.debian.org/825394, especially with these systemd messages. Could though also be the terminal itself, depending on which terminal is actually being used. Never heard of such a case so far, though. So in which terminal did this happen? (Might though validate an "Incomplete" again for this question. Unsure.) ** Changed in: screen (Ubuntu) Status: Incomplete => New ** Changed in: screen (Ubuntu) Status: New => Incomplete ** Changed in: screen (Ubuntu) Status: Incomplete => New ** Bug watch added: Debian Bug tracker #825394 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/198 Title: Sessions of screen does not keep running in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888280] Re: dctrl-tools should be dependency of debian-goodies
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 still usable then and if you only need them, there must to be a way to not install dependencies of the other, unused tools.) * Optional dependencies of any tool are just in Suggests. Besides: * Recommends are installed by default. As you've shown, you explicitly need to disable them to get into that situation. And as the documentation (at least Debian's) says: You're then on your own if something doesn't work because of that. * The package description explains very verbose which tool needs which of the Recommends and Suggests. ** Changed in: debian-goodies (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888280 Title: dctrl-tools should be dependency of debian-goodies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-goodies/+bug/1888280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883983] Re: MD5 is comprehensively broken at this point
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 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849377 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #540215 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540215 ** Also affects: debhelper (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540215 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883983 Title: MD5 is comprehensively broken at this point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debsums/+bug/1883983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882366] Re: After Installed Oh My Zsh, in taskbar shortcut icon widgets dont have icons and can't open.
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 dont have icons and can't open. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1882366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907932] Re: irqtop emits a warning
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 least irqtop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907932 Title: ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0", affects at least irqtop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1907932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907932] Re: irqtop emits a warning
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 Date: 2020-09-29 22:43:25 +0900 merge revision(s) 996af2ce086249e904b2ce95ab2fcd1de7d757be: [Backport #16345] [Backport #17000] Disable deprecation warning by the default [Feature #16345] And `-w` option turns it on. That commit likely made it into ruby 2.7.2, which hit Debian Unstable in mid-October 2020. Nevertheless this obviously needs to be fixed in ruby-curses. ** Bug watch added: Debian Bug tracker #958973 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958973 ** Also affects: ruby-curses (Ubuntu) Importance: Undecided Status: New ** Also affects: ruby-curses (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958973 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907932 Title: ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0", affects at least irqtop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables-netflow/+bug/1907932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723392] Re: Please update backuppc to 4.x release (now 4.2.1) - major improvements and lots of bugfixes
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: Please update backuppc to 4.x release (now 4.2.1) - major improvements and lots of bugfixes To manage notifications about this bug go to: https://bugs.launchpad.net/backuppc/+bug/1723392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796034] Re: lubuntu 18.10 falkon nouveau test on qutebrowser crashed with SIGSEGV in __GI_____strtoul_l_internal()
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: qutebrowser (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/1796034 Title: lubuntu 18.10 falkon nouveau test on qutebrowser crashed with SIGSEGV in __GI_strtoul_l_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qutebrowser/+bug/1796034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915205] Re: CVE-2020-9366
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1915205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915205] Re: 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 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950896 Importance: Unknown Status: Unknown -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1915205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** 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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960842] Re: failed to load module `zsh/mathfunc': /lib/x86_64-linux-gnu/libm.so.6
@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: https://launchpad.net/ubuntu/+source/glibc/2.35-0ubuntu1 Weird that zsh was already built against it before it reached jammy — that looks like weird buildd setup in Ubuntu — but still had a dependency on "libc6 (>= 2.34)". Nevertheless the latter might be the actual bug, but then again, it might be an issue in debhelper or so. There though might be other causes. I though still kinda doubt that this is cause by zsh's build system. -- 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': /lib/x86_64-linux-gnu/libm.so.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1960842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963276] Re: Qutebrowser not launching on arm64
@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 report.) Hint: Don't rely on external mailing list archives when reading Debian bug reports. Read the bug report in Debian's Bug Tracking System directly: https://bugs.debian.org/960384 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963276 Title: Qutebrowser not launching on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1963276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963276] Re: Qutebrowser not launching on arm64
** 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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963276 Title: Qutebrowser not launching on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1963276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1963276] Re: Qutebrowser not launching on arm64
Hi,
avdzm wrote:
> I saw on debian uses a newer version than what is on ubuntu mate's repo.
Right, I noticed this, too. (Was surprised how old the version in
20.04 is. But then again there were indeed a lot of qutebrowser
releases since early 2020.)
For Debian I could have been able to help out with Backports, but for
Ubuntu someone else would need to do that (in case it would have
helped in your case, too).
> So I have tried downloading source code for qutebrowser
> https://github.com/qutebrowser/qutebrowser/archive/refs/tags/v2.4.0.tar.gz
> run "setup.py install" runs successfully, but fails to launch with the same
> error message.
>
> CRITICAL: Could not initialize GLX
Thanks for testing this. Indeed interesting that this still shows up
with 2.4.0. This points towards the issue being indeed in the Qt
version of Ubuntu 20.04.
Have you tried upstream's suggestion in the Debian bug report and
installed and tried another web browser with the same rendering
engine, e.g. "falkon"?
If falkon fails with the same error, the cause of the issue is not in
qutebrowser. (But it is obviously affected nevertheless.)
> I'll post a bug 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, 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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963276
Title:
Qutebrowser not launching on arm64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1963276/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960842] Re: failed to load module `zsh/mathfunc': /lib/x86_64-linux-gnu/libm.so.6
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': /lib/x86_64-linux-gnu/libm.so.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1960842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960727] Re: When apt holds back updates, it fails to inform the user of the reason
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959485] Re: reproducible crash in jammy
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 big files as attachement to bug reports.) ** Changed in: aptitude (Ubuntu) Status: New => Incomplete ** Summary changed: - reproducible crash in jammy + reproducible crash in jammy: Uncaught exception: ../../src/ui.cc:1549: void auto_fix_broken(): Assertion "resman->resolver_exists()" failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959485 Title: reproducible crash in jammy: Uncaught exception: ../../src/ui.cc:1549: void auto_fix_broken(): Assertion "resman->resolver_exists()" failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1959485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860323] Re: fping not working if ipv6 is disabled
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. https://bugs.launchpad.net/bugs/1860323 Title: fping not working if ipv6 is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fping/+bug/1860323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
