Bug#996670: libkdecorations2-5v5 migrated to testing too early breaking Plasma
Package: libkdecorations2-5v5 Version: 4:5.23.0-2 Severity: critical Justification: breaks the whole system Dear Maintainer, as of 2021-10-17T06:09:05+00:00 Debian testing contains 4:5.23.0-2, although the rest of Plasma is still on 5.21. Therefore, apt update installs libkdecorations2-5v5=4:5.23.0-2 which breaks login and renders the computer useless for normal users. A downgrade to version 4:5.21.5-2 fixes the problem. Of course, you could also argue that normal users should not run testing and I am sure this bug gets fixed implicitly when the rest of Plasma migrates, so severity normal would also be sensible, depending on how you look at it. Fixing these kind of transition problems can safe a lot of users' time and therefore encourage more advanced users to run testing and report real bugs early on and therefore reduce freeze time. This is closely related to #974112, but as #974112 is specific to an older transition, I wanted to create a generic bug report. I am not sure, how the fix ideally should look like, but it most likely includes either a (versioned) dependency or a conflict. Kind regards Patrick -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (900, 'stable-security'), (900, 'testing'), (800, 'stable'), (500, 'unstable-debug'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de:en_US Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libkdecorations2-5v5 depends on: ii libc6 2.32-4 ii libkdecorations2private8 4:5.21.5-2 ii libkf5i18n5 5.86.0-1 ii libqt5core5a 5.15.2+dfsg-12 ii libqt5gui55.15.2+dfsg-12 ii libstdc++611.2.0-9 libkdecorations2-5v5 recommends no packages. libkdecorations2-5v5 suggests no packages. -- no debconf information
Bug#992760: ksystemtray: cannot be started, wrong version
Hi, > > ii libkf5plasma5 5.78.0-3 > > The problem is that this packages (and several others) from the > frameworks are not updated. > > I guess we have to introduce a breaks somewhere ... this incompatibility > is somehow surprising, because it is not documented in the CMakeList > files - at least as far I see... > > > So better wait for a newer version... > > No, wait for all frameworks being updated ... if you do not want to wait: apt install -t unstable $(apt list --installed | grep 5.78.0-3 | cut -d/ -f1) did the trick for me. Of course you need testing and unstable in /etc/apt/sources.list and an appropriate Pin-Priority in /etc/apt/preferences in order that this makes any sense (e.g. 900 for testing and 400 for unstable). This installed the following four packages: libkf5plasmaquick5 libkf5runner5 libkf5plasma5 plasma-framework The only other packages my system finds with apt list | grep 5.78.0-3 are libkf5plasma-dev libkf5plasma-doc libkf5runner-dev libkf5runner-doc qml- module-org-kde-runnermodel I hope this helps adding a versioned dependency or introducing a breaks. Thanks a lot, Norbert and all the relevant Debian maintainers, for all your work regarding KDE software packaging in Debian. The improved availability is more than welcome! Kind regards Patrick signature.asc Description: This is a digitally signed message part.
Bug#891957: netbeans no starting "loading module" modules.netbinox NullPointerException
Hi, > I suspect this is because of the recent update of libequinox-osgi-java. your suspicion is correct. Downgrading libequinox-osgi-java with > apt install libequinox-osgi-java/stable fixes the issue (although it removes eclipse if that is not downgraded as well). Kind regards Patrick signature.asc Description: This is a digitally signed message part.
Bug#744753: Fix for anacron (running on resume under systemd)
Hi Michael, That means, depending on the timing, anacron-resume.service might be triggered just before suspend not on resume, and it's not guaranteed that anacron has finished before systemd-sleep is called. I don't think the patch was intended this way? thanks for the analysis. Is there are reason for not reopening the bug? Patrick signature.asc Description: This is a digitally signed message part.
Bug#744753: anacron: Anacron not triggered when system resumes under systemd
Of course, my proposed patches would requires that the machine is turned on at xx:00 at least once a day. Although that patch is much better than the current behavior, I don't think that the solution is general enough. It's perfectly legitimate to use a device only for some minutes every time it's powered on. And it's probably not that uncommon for such devices that they are used at a regular time, e.g. after work or something like that. This time frame might contain a xx:00 or not. As anacron performs jobs like backups and installing security updates, it's unacceptable, that it's pure luck (from a user's point of view) whether anacron runs or not. Thus, either a resume hook or changing anacron from a one-shot program to a daemon is needed. When using init.d the decision was to use a hook, so it would probably make sense to do the same with systemd. Kind regards Patrick -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772630: closed by Andrey Rahmatullin w...@debian.org (Re: Bug#772630: obsolete libupnp?)
Issue is a false positive then, as Dario said. I've build package on my machine (Debian Jessie, amd64). Yes, thanks for the information. Executing apt-get -b source djmount in a newly created directory works indeed, while apt-get source djmount cd djmount-0.71 ./configure make cd .. apt-get source -b djmount does not work. But I suppose the latter one is not required to work. Thanks for everybody's help. Regards Patrick signature.asc Description: This is a digitally signed message part.
Bug#701680: Segfault when attempting to read a file
If anyone could tell me how to build djmount with debug information (a simple ./configure; make does not work, see #772630 for the details), I think I can produce a more useful stack trace. Kind regards Patrick signature.asc Description: This is a digitally signed message part.
Bug#772630: djmount fails to build from source
Package: djmount Version: 0.71-6 Severity: serious Justification: Policy 4.9 (Package does not successfully run build) Dear Maintainer, djmount FTBFS on Jessie (amd64) during linking. The last warning before the error: fuse_main.c: In function ‘main’: fuse_main.c:621:2: warning: implicit declaration of function ‘UpnpSetLogFileNames’ [-Wimplicit-function-declaration] UpnpSetLogFileNames (/dev/null, /dev/null); The error: /usr/bin/ld: log.o: relocation R_X86_64_32 against `.bss' can not be used when making a shared object; recompile with -fPIC log.o: error adding symbols: Bad value collect2: error: ld returned 1 exit status Makefile:477: recipe for target 'djmount' failed Kind regards Patrick -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing'), (800, 'stable'), (500, 'testing-proposed-updates'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages djmount depends on: ii fuse2.9.3-15+b1 ii libc6 2.19-13 ii libfuse22.9.3-15+b1 ii libtalloc2 2.1.1-2 ii libupnp61:1.6.19+git20141001-1 djmount recommends no packages. djmount suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#769325: mediatomb: Mediatomb does not work with systemd
Package: mediatomb Version: 0.12.1-7 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, version 0.12.1-7 does not start when using systemd without a useable error message: Process: 2788 ExecStart=/usr/bin/mediatomb -d -u $MT_USER -g $MT_GROUP -P /run/mediatomb.pid -l $MT_LOGFILE -m $MT_HOME -f $MT_CFGDIR -p $MT_PORT -e $MT_INTERFACE (code=exited, status=0/SUCCESS) Process: 2785 ExecStartPre=/sbin/ifconfig $MT_INTERFACE allmulti (code=exited, status=0/SUCCESS) Process: 2782 ExecStartPre=/sbin/route add -net 239.0.0.0 netmask 255.0.0.0 $MT_INTERFACE (code=exited, status=0/SUCCESS) Process: 2779 ExecStartPre=/bin/grep -q MT_USER /etc/default/mediatomb (code=exited, status=0/SUCCESS) Main PID: 2789 (code=exited, status=1/FAILURE) Even if it started, it wouldn't work, as it does not read the configuration file /etc/mediatomb/config.xml, which can be seen in /lib/systemd/system/mediatomb.service: ExecStart=/usr/bin/mediatomb -d -u $MT_USER -g $MT_GROUP -P /run/mediatomb.pid -l $MT_LOGFILE -m $MT_HOME -f $MT_CFGDIR -p $MT_PORT -e $MT_INTERFACE Additionally, it does not seem to make sense to have /etc/default/mediatomb, as nearly all options are duplicates of options in /etc/mediatomb/config.xml. It is completely unclear to a normal user which value is used, if the values of both files differ. Mediatomb had working systemd support before these changes had been applied. These changes should thus probably be reverted. Alternatively, /etc/default/mediatomb should be deleted and /lib/systemd/system/mediatomb.service should be changed into [Unit] Description=UPnP MediaServer After=NetworkManager-wait-online.service network.target [Service] Type=forking PIDFile=/run/mediatomb.pid ExecStart=/usr/bin/mediatomb -d -c /etc/mediatomb/config.xml -P /run/mediatomb.pid [Install] WantedBy=multi-user.target Kind regards Patrick -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'stable'), (500, 'testing-proposed-updates'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mediatomb depends on: ii chromium [www-browser] 38.0.2125.101-3 ii iceweasel [www-browser] 31.2.0esr-3 ii konqueror [www-browser] 4:4.14.2-1 ii mediatomb-daemon 0.12.1-7 ii rekonq [www-browser] 2.4.2-0ubuntu2 ii w3m [www-browser]0.5.3-19 mediatomb recommends no packages. mediatomb suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764798: RE: Bug#764798: grub2: Grub rescue shell with RAID 6 mdadm over 8 disks
On Thu, 23 Oct 2014 18:20:00 -0500 Mike ctrl...@yahoo.com wrote:
Greetings, anything else needed from me?
Thanks.
This is complete guessing, but could the file, util/deviceiter.c, i.e. the
iteration over devices, have something to do with it? In version
grub2-2.02~beta2, there is this block beginning in line 713 (inside of an
#ifdef __linux__):
/* ATARAID disks. */
for (i = 0; i 8; i++)
{
[...]
}
Interestingly, there is a similar block starting in line 645
/* IDE disks. */
for (i = 0; i 96; i++)
{
[...]
}
which might explain why this problem has not been detected/fixed beforehand.
There weren't probably a lot of users with more than 96 IDE disks …
This can be completely wrong, but if you already have a test setup, you might
get the package (apt-get build-dep grub2; apt-get source grub2) change the
value, rebuild the package (fakeroot dpkg-buildpackage -b -uc -us should
work), install (dpkg -i ...) and test it.
Kind regards
Patrick
signature.asc
Description: This is a digitally signed message part.
Bug#766796: konqueror: Konqueror is vulnerable to the Poodle attack
Package: konqueror Version: 4:4.14.1-1 Severity: grave Tags: security Justification: user security hole Dear Maintainer, according to https://www.poodletest.com/ Konqueror is still vulnerable to the Poodle attack. If this is only fixable in KHTML or WebKit, please move the bug there. As all the other major browsers plan to deactivate SSLv3 support in the near future, Konqueror should probably do so as well for Jessie. Kind regards Patrick -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (800, 'stable'), (500, 'testing-proposed-updates'), (400, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages konqueror depends on: ii install-info5.2.0.dfsg.1-4 ii kde-baseapps-bin4:4.14.1-1 ii kde-baseapps-data 4:4.14.1-1 ii kde-runtime 4:4.14.1-1+b1 ii libc6 2.19-11 ii libkactivities6 4:4.13.3-1 ii libkcmutils44:4.14.1-1+b1 ii libkde3support4 4:4.14.1-1+b1 ii libkdecore5 4:4.14.1-1+b1 ii libkdesu5 4:4.14.1-1+b1 ii libkdeui5 4:4.14.1-1+b1 ii libkfile4 4:4.14.1-1+b1 ii libkhtml5 4:4.14.1-1+b1 ii libkio5 4:4.14.1-1+b1 ii libkonq5abi14:4.14.1-1 ii libkonqsidebarplugin4a 4:4.14.1-1 ii libkparts4 4:4.14.1-1+b1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-qt3support 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libqt4-xml 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-2 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-2+b1 ii libstdc++6 4.9.1-16 ii libx11-62:1.6.2-3 Versions of packages konqueror recommends: ii dolphin 4:4.14.1-1 ii kfind4:4.14.1-1 ii konqueror-nsplugins 4:4.14.1-1 ii kpart-webkit 1.3.4-1 Versions of packages konqueror suggests: ii konq-plugins 4:4.14.1-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686495: libpcre3: Very large value for re_nsub
Package: libpcre3 Version: 1:8.30-5 Severity: grave Tags: patch Justification: causes non-serious data loss Dear Maintainer, when compiling the regular expression regex_t rx; regcomp(rx, ^(\\(\\))? *(.*)$, 0) I get the large value 140733193388034 for rx.re_nsub. As this value is often used afterwards in malloc this normally leads to the termination of the programm (either because of the segfault or due to the assumption of no free memory), so unsaved data gets lost. The problem is well known (http://www.exim.org/lurker/message/20120822.143744.147fd5d2.de.html) and a patch exists (http://bugs.exim.org/attachment.cgi?id=586). I can confirm that the patch works. Please consider applying the patch. Cheers Patrick -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500, 'stable-updates'), (400, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/6 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libpcre3 depends on: ii libc6 2.13-35 ii multiarch-support 2.13-35 libpcre3 recommends no packages. libpcre3 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
