Bug#1013441: The bug affects (university) eduroam wpa-eap connections

2022-06-24 Thread Gianpaolo Cugola
I confirm that the bug affects NetworkManager wifi connections under sid, crashing wpa_supplicant with "munmap_chunk(): invalid pointer" message. As a workaround I reinstalled previous version 3.0.3-8 Let me know if I can help in any way. Thanks Gianpaolo

Bug#940839: Same bug with 2.4.4

2019-12-22 Thread Gianpaolo Cugola
Sorry, my mistake, I meant 2.4.3. G. On Sun, Dec 22, 2019 at 9:24 PM John Scott wrote: > Hello, > > > Same situation here with openshot 2.4.4 from debian sid. I have an intel > gpu. > OpenShot 2.4.4 isn't in Debian Sid yet. Where did you install it from? >

Bug#945170: libopenmpi-dev: libmca_common_verbs.so.40 and libmca_common_monitoring.so.50 missing

2019-11-20 Thread Gianpaolo Cugola
Package: libopenmpi-dev Version: 4.0.2-2 Severity: serious Justification: Policy 8.1 Dear Maintainer, apparently the libopenmpi-dev package miss the mentioned libraries. As a result each time a program compiled with openmpi is lauched a bunch of warning appear in the form: [xxx]

Bug#940839: Same bug with 2.4.4

2019-10-02 Thread Gianpaolo Cugola
Same situation here with openshot 2.4.4 from debian sid. I have an intel gpu.

Bug#907888: [Pkg-openssl-devel] Bug#907888: openssl: Breaks wpa_supplicant (and NetworkManager) which fail with error "ee key too small"

2018-09-04 Thread Gianpaolo Cugola
On Mon, 3 Sep 2018 22:24:29 +0200 Kurt Roeckx wrote: > The fix it to tell your administrator to use 2048 (or more) bit > keys. I assume there are certificates on both sides, so they both > need to get replaced. > > You can work around this issue by putting something like this in > your config

Bug#907888: opopenssl: Breaks wpa_supplicant (and NetworkManager) which fail with error "ee key too small"

2018-09-03 Thread Gianpaolo Cugola
Package: openssl Version: 1.1.1~~pre9-1 Severity: important Dear Maintainer, version 1.1.1~~pre9-1 of the openssl package breaks wpa_supplicant (and NetworkManager) when using EAP TLS connections. In particular, launching: > wpa_supplicant -dd -i wlp2s0 -c ./eduroam.conf where /eduroam.conf is:

Bug#766030: wine: error: unable to find wine executable. this shouldn't happen.

2014-10-20 Thread Gianpaolo Cugola
I confirm the bug and also confirm that the following downgrade: [DOWNGRADE] libwine:i386 1.6.2-13 - 1.6.2-8 [DOWNGRADE] libwine-print:i386 1.6.2-13 - 1.6.2-8 [DOWNGRADE] wine:i386 1.6.2-13 - 1.6.2-8 [DOWNGRADE] wine32:i386 1.6.2-13 - 1.6.2-8 solves the problem. Sincerely G. On Mon, 20 Oct

Bug#762162: crash

2014-09-22 Thread Gianpaolo Cugola
Dear Klaus, actually, as I mentioned in my bug report, the problem happens even if I start with a totally clean home, i.e., after removing ~/.config/geeqie ~/.local/share/geeqie and ~/.cache/geeqie. Sincerely G. On Sun, 21 Sep 2014 20:15:02 +0100 Klaus Ethgen kl...@ethgen.ch wrote:

Bug#762162: geeqie: segfault on startup

2014-09-21 Thread Gianpaolo Cugola
Same problem here. I am attaching the result of running: gdb -batch -n -ex run -ex bt -ex 'thread apply all bt full' --args geeqie before removing ~/.config/geeqie and ~/.local/share/geeqie and after removing them (and moviing to a folder containing images). Sincerely G. [Thread

Bug#665004: Confirmed for Dell Latitude E6420

2012-04-01 Thread Gianpaolo Cugola
Same problem here (Dell Latitude E6420). The suggested settings: VertScrollDelta = 5 HorizScrollDelta = 5 HorizHysteresis = 0 VertHysteresis = 0 makes things a bit more usable but previous version (1.5.0) is still much better: smoother and much more reliable. I reverted to 1.5.0 Sincerely

Bug#431917: libblkid1: mount -t auto blocks forever for usb devices

2007-07-05 Thread Gianpaolo Cugola
Package: libblkid1 Version: 1.40-1 Severity: important mount -t auto blocks forever when trying to mount a vfat formatted usb key with libblkid1_1.40-1. It works smoothly on the same key if either the key is formated with ext3 or if the previous version of libblkid1 is used (this is why I

Bug#372564: Workaround

2006-06-27 Thread Gianpaolo Cugola
I found a workaround for these two related bugs, i.e., 372564 and 372258. Apparently kwalletmanager works smoothly if launched without indicating any session, so you can either disable your session manager (via control center - kde components - session manager) or just exclude kwalletmanager