Bug#979367: kodi: segfault when shutting down
On Wed, Jan 06, 2021 at 12:25:33PM +0100, Sebastian Ramacher wrote: > If you have other packages depending on ffmpeg or other libraries used > by kodi, this won't help. Check > https://wiki.debian.org/DebianMultimedia/FAQ on how to find all packages > installed from DMO and then you'll need to reinstall them with the > correct version. yes, I purged all -dmo packages from the system and reinstalled from debian testing/sid again. Sebastian
Bug#979367: kodi: segfault when shutting down
Hi! On Wed, Jan 06, 2021 at 10:49:34AM +, Vasyl Gello wrote: > I will build kodi against testing/amd64 today with a patch introducing null > checks in the PythonLanguageHook > and send you the link to the resulting deb file. In the meantime, can you > please upload the corefile? I want to check > if pointer to PyDict is null or not. If it is nulled, then it is a deference > bug but if it is non-null then we encountered an UaF. Great, thank you! I set `ulimit -S -c unlimited` and pressed shutdown. I can see that a core file is generated in /home/kodi but as soon as the kodi crashlog is written, the core file is removed. Do I need to enable something so that the core file is not deleted? I ran `find / -name core` but there seems to be no core file anywhere... It looks like that kodi is eating the file, see /usr/bin/kodi line 113. Is there a method to keep the core file (or is the only way to comment out the rm?) Sebastian
Bug#979367: kodi: segfault when shutting down
> Another thing that bothers me is that you mix dmo and official Debian > repository. yes these are leftovers... I now purged all dmo packages and reinstalled them from debian testing/sid. > > Can you please backup your Kodi profile and reinstall Kodi with only > dependencies from official Debian archive? Should an apt purge --autoremove && apt install do the same? However, on my cleaned system the segfault persists. I also tried to change the locale from de_AT.UTF8 to en_US.UTF8 but it does not matter. Sebastian
Bug#979367: kodi: segfault when shutting down
Hi! sure, I just started kodi and pressed shutdown. Should be the most minimal version possible. Sebastian On Tue, Jan 05, 2021 at 09:02:30PM +, Vasyl Gello wrote: > Hi Sebastian! > > Can you also attach kodi.log describing the crashed instance? Please check > for user name / IP address / URLs to avoid leaking sensitive info and attach > it to the reply. > > Thanks! > -- > Vasyl Gello > == > Certified SolidWorks Expert > > Mob.:+380 (98) 465 66 77 > > E-Mail: vasek.ge...@gmail.com > > Skype: vasek.gello > == > 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다 ## Kodi CRASH LOG ### SYSTEM INFO Date: Di 05 Jän 2021 22:17:22 CET Kodi Options: Arch: x86_64 Kernel: Linux 5.9.0-5-amd64 #1 SMP Debian 5.9.15-1 (2020-12-17) Release: Debian GNU/Linux ## END SYSTEM INFO ## ### STACK TRACE # => Core file: /home/kodi/core (2021-01-05 22:17:22.738685160 +0100) = [New LWP 714] [New LWP 687] [New LWP 686] [New LWP 684] [New LWP 688] [New LWP 693] [New LWP 694] [New LWP 702] [New LWP 696] [New LWP 695] [New LWP 703] [New LWP 704] [New LWP 705] [New LWP 678] [New LWP 685] [New LWP 706] [New LWP 716] [New LWP 707] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/lib/x86_64-linux-gnu/kodi/kodi.bin --standalone'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fea22e62f6b in PyModule_GetDict () from /lib/x86_64-linux-gnu/libpython3.9.so.1.0 [Current thread is 1 (Thread 0x7fe9ae7fc700 (LWP 714))] Thread 18 (Thread 0x7fe9ce7fc700 (LWP 707)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fe9ce7fae30, clockid=-830493312, expected=0, futex_word=0x556688e94a80) at ../sysdeps/nptl/futex-internal.h:323 #1 __pthread_cond_wait_common (abstime=0x7fe9ce7fae30, clockid=-830493312, mutex=0x556688e95eb0, cond=0x556688e94a58) at pthread_cond_wait.c:520 #2 __pthread_cond_clockwait (abstime=0x7fe9ce7fae30, clockid=-830493312, mutex=0x556688e95eb0, cond=0x556688e94a58) at pthread_cond_wait.c:677 #3 __pthread_cond_clockwait (cond=0x556688e94a58, mutex=0x556688e95eb0, clockid=-830493312, abstime=0x7fe9ce7fae30) at pthread_cond_wait.c:665 #4 0x556685eb07d2 in ?? () #5 0x556685eb0a74 in CTimer::Process() () #6 0x556685eacbc5 in CThread::Action() () #7 0x556685eae79e in ?? () #8 0x556685eaec29 in ?? () #9 0x7fea1f622ed0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7fea236f7ea7 in start_thread (arg=) at pthread_create.c:477 #11 0x7fea1f820d8f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fe9ad7fa700 (LWP 716)): #0 0x7fea1f81639f in __GI___poll (fds=0x7fe994000b60, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fea235d807a in ?? () from /lib/x86_64-linux-gnu/libavahi-common.so.3 #2 0x7fea235d7c01 in avahi_simple_poll_run () from /lib/x86_64-linux-gnu/libavahi-common.so.3 #3 0x7fea235d7dd8 in avahi_simple_poll_iterate () from /lib/x86_64-linux-gnu/libavahi-common.so.3 #4 0x7fea235d800d in avahi_simple_poll_loop () from /lib/x86_64-linux-gnu/libavahi-common.so.3 #5 0x7fea235d80d7 in ?? () from /lib/x86_64-linux-gnu/libavahi-common.so.3 #6 0x7fea236f7ea7 in start_thread (arg=) at pthread_create.c:477 #7 0x7fea1f820d8f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fe9ceffd700 (LWP 706)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fe9ceffbeb0, clockid=-822100560, expected=0, futex_word=0x556688f0dc30) at ../sysdeps/nptl/futex-internal.h:323 #1 __pthread_cond_wait_common (abstime=0x7fe9ceffbeb0, clockid=-822100560, mutex=0x556688ee1d70, cond=0x556688f0dc08) at pthread_cond_wait.c:520 #2 __pthread_cond_clockwait (abstime=0x7fe9ceffbeb0, clockid=-822100560, mutex=0x556688ee1d70, cond=0x556688f0dc08) at pthread_cond_wait.c:677 #3 __pthread_cond_clockwait (cond=0x556688f0dc08, mutex=0x556688ee1d70, clockid=-822100560, abstime=0x7fe9ceffbeb0) at pthread_cond_wait.c:665 #4 0x5566864adfb8 in PERIPHERALS::CEventScanner::Process() () #5 0x556685eacbc5 in CThread::Action() () #6 0x556685eae79e in ?? () #7 0x556685eaec29 in ?? () #8 0x7fea1f622ed0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7fea236f7ea7 in start_thread (arg=) at pthread_create.c:477 #10 0x7fea1f820d8f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7fea1299d700 (LWP 685)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7fea1299bde0, clockid=312065280, expected=0, futex_word=0x556688e8c128) at ../sysdeps/nptl/futex-internal.h:323 #1 __pthread_cond_wait_common (abstime=0x7fea1299bde0, clockid=31206528
Bug#979367: kodi: segfault when shutting down
Package: kodi-bin Version: 2:19.0~beta2+dfsg1-2 Severity: important Dear Maintainers, I have configured kodi in standalone mode using lightdm autologin feature and the kodi.desktop xsession. When I shutdown the PC using the kodi menu, kodi segfaults and thus lightdm restarts the session. I get the following kodi crashlog: ## Kodi CRASH LOG ### SYSTEM INFO Date: Di 05 Jän 2021 17:12:26 CET Kodi Options: Arch: x86_64 Kernel: Linux 5.9.0-5-amd64 #1 SMP Debian 5.9.15-1 (2020-12-17) Release: Debian GNU/Linux ## END SYSTEM INFO ## ### STACK TRACE # => Core file: /home/kodi/core (2021-01-05 17:12:26.002469806 +0100) = [New LWP 752] [New LWP 723] [New LWP 722] [New LWP 721] [New LWP 740] [New LWP 1199] [New LWP 731] [New LWP 743] [New LWP 725] [New LWP 733] [New LWP 744] [New LWP 715] [New LWP 730] [New LWP 754] [New LWP 1172] [New LWP 732] [New LWP 742] [New LWP 1171] [New LWP 741] [New LWP 724] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/lib/x86_64-linux-gnu/kodi/kodi.bin --standalone'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f4199894f6b in PyModule_GetDict () from /lib/x86_64-linux-gnu/libpython3.9.so.1.0 [Current thread is 1 (Thread 0x7f4134ff9700 (LWP 752))] Thread 20 (Thread 0x7f417bfff700 (LWP 724)): #0 0x7f4196249c67 in ioctl () at ../sysdeps/unix/syscall-template.S:120 #1 0x7f419a0887e2 in ?? () from /lib/x86_64-linux-gnu/libasound.so.2 #2 0x55a2655e81e9 in CAESinkALSA::AddPackets(unsigned char**, unsigned int, unsigned int) () #3 0x55a2655d105a in ActiveAE::CActiveAESink::OutputSamples(ActiveAE::CSampleBuffer*) () #4 0x55a2655d22a3 in ActiveAE::CActiveAESink::StateMachine(int, Actor::Protocol*, Actor::Message*) () #5 0x55a2655d2d54 in ActiveAE::CActiveAESink::Process() () #6 0x55a264cc2bc5 in CThread::Action() () #7 0x55a264cc479e in ?? () #8 0x55a264cc4c29 in ?? () #9 0x7f4196054ed0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f419a129ea7 in start_thread (arg=) at pthread_create.c:477 #11 0x7f4196252d8f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f414effd700 (LWP 741)): #0 0x7f419624839f in __GI___poll (fds=0x7f414effbeb0, nfds=1, timeout=100) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x55a264943cc2 in PERIPHERALS::CPeripheralBusUSB::WaitForUpdate() () #2 0x55a264943e70 in PERIPHERALS::CPeripheralBusUSB::Process() () #3 0x55a264cc2bc5 in CThread::Action() () #4 0x55a264cc479e in ?? () #5 0x55a264cc4c29 in ?? () #6 0x7f4196054ed0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7f419a129ea7 in start_thread (arg=) at pthread_create.c:477 #8 0x7f4196252d8f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f414cff9700 (LWP 1171)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7f414cff7e30, clockid=1291812224, expected=0, futex_word=0x55a267625484) at ../sysdeps/nptl/futex-internal.h:323 #1 __pthread_cond_wait_common (abstime=0x7f414cff7e30, clockid=1291812224, mutex=0x55a26761ac90, cond=0x55a267625458) at pthread_cond_wait.c:520 #2 __pthread_cond_clockwait (abstime=0x7f414cff7e30, clockid=1291812224, mutex=0x55a26761ac90, cond=0x55a267625458) at pthread_cond_wait.c:677 #3 __pthread_cond_clockwait (cond=0x55a267625458, mutex=0x55a26761ac90, clockid=1291812224, abstime=0x7f414cff7e30) at pthread_cond_wait.c:665 #4 0x55a264cc67d2 in ?? () #5 0x55a264cc6a74 in CTimer::Process() () #6 0x55a264cc2bc5 in CThread::Action() () #7 0x55a264cc479e in ?? () #8 0x55a264cc4c29 in ?? () #9 0x7f4196054ed0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f419a129ea7 in start_thread (arg=) at pthread_create.c:477 #11 0x7f4196252d8f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f414e7fc700 (LWP 742)): #0 futex_abstimed_wait_cancelable (private=0, abstime=0x7f414e7faeb0, clockid=1316990384, expected=0, futex_word=0x55a2689cfc98) at ../sysdeps/nptl/futex-internal.h:323 #1 __pthread_cond_wait_common (abstime=0x7f414e7faeb0, clockid=1316990384, mutex=0x55a2689cefb0, cond=0x55a2689cfc70) at pthread_cond_wait.c:520 #2 __pthread_cond_clockwait (abstime=0x7f414e7faeb0, clockid=1316990384, mutex=0x55a2689cefb0, cond=0x55a2689cfc70) at pthread_cond_wait.c:677 #3 __pthread_cond_clockwait (cond=0x55a2689cfc70, mutex=0x55a2689cefb0, clockid=1316990384, abstime=0x7f414e7faeb0) at pthread_cond_wait.c:665 #4 0x55a2652aee4d in PERIPHERALS::CPeripheralBus::Process() () #5 0x55a264cc2bc5 in CThread::Action() () #6 0x55a264cc479e in ?? () #7 0x55a264cc4c29 in ?? () #8 0x7f4196054ed0 in ?? () from /lib/x86_
Bug#964201: libshiboken2-dev: Wrong include path for CMake in INTERFACE_INCLUDE_DIRECTORIES
Package: libshiboken2-dev Version: 5.15.0-2 Severity: important Dear Maintainer! Similar to bug #949846, the include path in libshiboken is wrong. Using the same script as in the other bugreport, you can see the following output: -- Shiboken2Config: Using default python: .cpython-38-x86_64-linux-gnu -- Found PythonInterp: /usr/bin/python3 (found suitable version "3.8.3", minimum required is "3") -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found suitable version "3.8.3", minimum required is "3") -- SHIBOKEN_PYTHON_INCLUDE_DIRS computed to value: '/usr/include/python3.8' -- SHIBOKEN_PYTHON_LIBRARIES computed to value: '' -- libshiboken built for RelWithDebInfo CMake Error at CMakeLists.txt:6 (get_property): get_property could not find TARGET Shiboken2:libshiboken. Perhaps it has not yet been created. Shiboken2::libshiboken AUTOGEN_ORIGIN_DEPENDS = ON Shiboken2::libshiboken AUTOMOC_COMPILER_PREDEFINES = ON Shiboken2::libshiboken AUTOMOC_MACRO_NAMES = Q_OBJECT;Q_GADGET;Q_NAMESPACE Shiboken2::libshiboken AUTOMOC_PATH_PREFIX = ON Shiboken2::libshiboken BINARY_DIR = /home/reox/tmp/dfsdf Shiboken2::libshiboken BINARY_DIR = /home/reox/tmp/dfsdf Shiboken2::libshiboken BUILD_WITH_INSTALL_RPATH = OFF Shiboken2::libshiboken IMPORTED = TRUE Shiboken2::libshiboken IMPORTED_CONFIGURATIONS = RELWITHDEBINFO Shiboken2::libshiboken IMPORTED_GLOBAL = FALSE Shiboken2::libshiboken INSTALL_RPATH = Shiboken2::libshiboken INSTALL_RPATH_USE_LINK_PATH = OFF Shiboken2::libshiboken INTERFACE_INCLUDE_DIRECTORIES = /usr/lib/include/shiboken2;/usr/include/python3.8 Shiboken2::libshiboken NAME = Shiboken2::libshiboken Shiboken2::libshiboken POSITION_INDEPENDENT_CODE = True Shiboken2::libshiboken SKIP_BUILD_RPATH = OFF Shiboken2::libshiboken SOURCE_DIR = /home/reox/tmp/dfsdf Shiboken2::libshiboken SOURCE_DIR = /home/reox/tmp/dfsdf Shiboken2::libshiboken TYPE = SHARED_LIBRARY Shiboken2::libshiboken TYPE = SHARED_LIBRARY Shiboken2::libshiboken UNITY_BUILD_BATCH_SIZE = 8 -- Configuring incomplete, errors occurred! The include path should be /usr/include/shiboken2 instead of /usr/lib/include/shiboken2 Thank you! Best regards Sebastian -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libshiboken2-dev depends on: ii libshiboken2-py3-5.15 5.15.0-2 ii python3-dev3.8.2-3 ii shiboken2 5.15.0-2 libshiboken2-dev recommends no packages. libshiboken2-dev suggests no packages. -- no debconf information
Bug#959695: calculix-cgx: freeglut (cgx): Menu manipulation not allowed while menus in use.
Package: calculix-cgx Version: 2.11+dfsg-1+b1 Severity: important Dear Maintainers, cgx has some issue with the freeglut version. There are already very old bugreports like https://bugzilla.redhat.com/show_bug.cgi?id=1017551 which illustrate the problem. It is possible to downgrade to a very old version of freeglut, but that would mean to install a version from 2012. For example by downgrading to this version here: https://snapshot.debian.org/archive/debian/20120714T033241Z/pool/main/f/freeglut/freeglut3_2.6.0-4_amd64.deb I confirmed that it still works, downgrading indeed fixes the problem. The problem can be triggered as follows: $ cd /tmp $ cp /usr/share/doc/calculix-cgx-examples/examples/result.frd.gz . $ gunzip result.frd.gz $ cgx result.frd Left click, select Datasets -> 1 DISP Crash: freeglut (cgx): Menu manipulation not allowed while menus in use. Best regards, Sebastian -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.5.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages calculix-cgx depends on: ii freeglut3 2.8.1-5 ii libc6 2.30-4 ii libgcc-s1 [libgcc1] 10-20200418-1 ii libgcc1 1:10-20200418-1 ii libgl1 1.3.1-1 ii libgl1-mesa-glx 19.3.3-1 ii libglu1-mesa [libglu1] 9.0.1-1 ii libice6 2:1.0.9-2 ii libsm6 2:1.2.3-1 ii libsnl0 0.2.1.svn.18-1.1 ii libstdc++6 10-20200418-1 ii libx11-62:1.6.9-2 ii libxext62:1.3.3-1+b2 ii libxi6 2:1.7.9-1 ii libxmu6 2:1.1.2-2+b3 ii libxt6 1:1.1.5-1+b3 Versions of packages calculix-cgx recommends: pn netgen calculix-cgx suggests no packages. -- no debconf information
Bug#954329: paraview: opacity incorrectly handled by the debian bullseye(testing) package paraview-5.7
I can confirm this too. I also noted, that it works for example for 2D images (like PNG) but not for 3D data, for example VTK or MHD files. Neither mesh edges nor 3D surfaces work in opacity mode. I also downloaded the latest version (5.8) from kitware directly, which works correctly for all files. Best regards, Sebastian On Fri, 20 Mar 2020 11:38:49 +0100 (CET) Pierre Saramito wrote: > Package: paraview > Version: 5.7.0-4+b2 > Severity: normal > > Dear Maintainer, > > The opacity is not handled correctly by paraview-5.7 binary, > as packaged on bullseye(testing) distrib. > Here is a unix command that reproduces the bug: > > paraview --script=paraview-opacity-bug.py > > where the paraview-opacity-bug.py python script coulbe be downloaded at > > https://www-ljk.imag.fr/membres/Pierre.Saramito/tmp/paraview-opacity-bug.py > > This problem is specific to the debian package: the upstream paraview-5.7 > version is problem-free when I use the raw binary distributed by kitware: > > https://www.paraview.org/download/ > https://www.paraview.org/paraview-downloads/download.php?submit=Download&version=v5.7&type=binary&os=Linux&downloadFile=ParaView-5.7.0-osmesa-MPI-Linux-Python3.7-64bit.tar.gz > > > This opacity problem could perhaps be due to the mesa/opengl library, > as packaged by debian bullseye(testing) ? > > Best whishes, > > Pierre > > -- System Information: > Debian Release: bullseye/sid > APT prefers stable > APT policy: (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.4.0-4-amd64 (SMP w/4 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), > LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages paraview depends on: > ii libavcodec58 7:4.2.2-1+b1 > ii libavformat58 7:4.2.2-1+b1 > ii libavutil56 7:4.2.2-1+b1 > ii libc6 2.30-2 > ii libdouble-conversion3 3.1.5-5 > ii libexpat1 2.2.9-1 > ii libfreetype6 2.10.1-2 > ii libgcc-s1 [libgcc1] 10-20200312-2 > ii libgcc1 1:10-20200312-2 > ii libgdal26 3.0.4+dfsg-1 > ii libgl1 1.3.1-1 > ii libglew2.1 2.1.0-4+b1 > ii libhdf5-103 1.10.4+repack-11 > ii libjpeg62-turbo 1:1.5.2-2+b1 > ii liblz4-1 1.9.2-2 > ii liblzma5 5.2.4-1+b1 > ii libopenmpi3 4.0.2-5 > ii libpdal-base9 2.0.1+ds-1+b1
Bug#945581: vmdb2: grub fails on an LV image
Hi!
I found out that this helps to work around it:
- grub: bios
tag: root
console: serial
image-dev: "{{ image }}"
In the documentation it says "device", but seems to be wrong. (Compare
https://vmdb2-manual.liw.fi/#step-grub, lateron image-dev is mentioned)
I could successfully install it on a LV.
hth!
Sebastian
On Wed, 27 Nov 2019 12:55:27 +0100 Josip Rodin
wrote:
> Package: vmdb2
> Version: 0.13.2+git20190215-1
>
> Hi,
>
> I pre-created my LV using the same lvcreate syntax that doesn't work from
> within vmdb2 (see previous bug filed), and used with the invocation:
>
> % sudo vmdb2 foo-bar-1.vmdb.yml --image /dev/vg0/foo-bar-1-root --verbose
> --log=foo-bar-1.vmd.log
>
> The boot loader step in foo-bar-1.vmdb.yml was the default one from the
> manual:
>
> - grub: bios
> tag: root
> console: serial
Bug#949846: libpyside2-dev: Wrong include path for CMake in INTERFACE_INCLUDE_DIRECTORIES
Hello! I just created a pbuilder instance and pinned libshiboken2-dev and libpyside2-dev from experimental. So far the build runs smooth. Hence, I can confirm that this is fixed in the experimental version! Thank you very much! Sebastian On Sat, 25 Jan 2020 22:13:21 +0100 Gianfranco Costamagna wrote: > control: fixed -1 5.14.0-1~exp1 > control: close -1 > > Hello, > > its fixed in experimental and the fix will go in sid once the transition > starts! > > (please reopen if this isn't the case) > > G. > > On Sat, 25 Jan 2020 20:55:25 +0100 Sebastian Bachmann > wrote: > > Package: libpyside2-dev > > Version: 5.13.2-2.2+b1 > > Severity: normal > > > > Dear Maintainer! > > > > I noticed that my build fails because of this error: > > > > CMake Error in src/Gui/CMakeLists.txt: > > Imported target "PySide2::pyside2" includes non-existent path > > > > "/usr/lib/include/PySide2" > > > > in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: > > > > * The path was deleted, renamed, or moved to another location. > > > > * An install or uninstall procedure did not complete successfully. > > > > * The installation package was faulty and references files it does not > > provide. > > > > > > The correct path should be /usr/include/PySide2 and a quick check using the > > attached CMake script shows that indeed the wrong path is set: > > cmake .. > > -- PySide2Config: Using default python: .cpython-38-x86_64-linux-gnu > > [...] > > PySide2::pyside2 INTERFACE_INCLUDE_DIRECTORIES = /usr/lib/include/PySide2 > > [...] > > > > > > Best regards > > Sebastian > > > > > > > > -- System Information: > > Debian Release: bullseye/sid > > APT prefers testing > > APT policy: (990, 'testing'), (500, 'unstable') > > Architecture: amd64 (x86_64) > > Foreign Architectures: i386 > > > > Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores) > > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > > TAINT_UNSIGNED_MODULE > > Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), > > LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/dash
Bug#949846: libpyside2-dev: Wrong include path for CMake in INTERFACE_INCLUDE_DIRECTORIES
Package: libpyside2-dev
Version: 5.13.2-2.2+b1
Severity: normal
Dear Maintainer!
I noticed that my build fails because of this error:
CMake Error in src/Gui/CMakeLists.txt:
Imported target "PySide2::pyside2" includes non-existent path
"/usr/lib/include/PySide2"
in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include:
* The path was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and references files it does not
provide.
The correct path should be /usr/include/PySide2 and a quick check using the
attached CMake script shows that indeed the wrong path is set:
cmake ..
-- PySide2Config: Using default python: .cpython-38-x86_64-linux-gnu
[...]
PySide2::pyside2 INTERFACE_INCLUDE_DIRECTORIES = /usr/lib/include/PySide2
[...]
Best regards
Sebastian
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8),
LANGUAGE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libpyside2-dev depends on:
ii libpyside2-py3-5.13 5.13.2-2.2+b1
libpyside2-dev recommends no packages.
libpyside2-dev suggests no packages.
-- no debconf information
cmake_minimum_required(VERSION 3.3 FATAL_ERROR)
project(Test)
find_package(PySide2)
# From https://stackoverflow.com/a/34292622/446140
get_property(PYSIDE_INCLUDE_DIR TARGET PySide2::pyside2 PROPERTY
INTERFACE_INCLUDE_DIRECTORIES)
# Get all propreties that cmake supports
execute_process(COMMAND cmake --help-property-list OUTPUT_VARIABLE
CMAKE_PROPERTY_LIST)
# Convert command output into a CMake list
STRING(REGEX REPLACE ";" ";" CMAKE_PROPERTY_LIST "${CMAKE_PROPERTY_LIST}")
STRING(REGEX REPLACE "\n" ";" CMAKE_PROPERTY_LIST "${CMAKE_PROPERTY_LIST}")
function(print_properties)
message ("CMAKE_PROPERTY_LIST = ${CMAKE_PROPERTY_LIST}")
endfunction(print_properties)
function(print_target_properties tgt)
if(NOT TARGET ${tgt})
message("There is no target named '${tgt}'")
return()
endif()
foreach (prop ${CMAKE_PROPERTY_LIST})
string(REPLACE "" "${CMAKE_BUILD_TYPE}" prop ${prop})
# Fix
https://stackoverflow.com/questions/32197663/how-can-i-remove-the-the-location-property-may-not-be-read-from-target-error-i
if(prop STREQUAL "LOCATION" OR prop MATCHES "^LOCATION_" OR prop MATCHES
"_LOCATION$")
continue()
endif()
# message ("Checking ${prop}")
get_property(propval TARGET ${tgt} PROPERTY ${prop} SET)
if (propval)
get_target_property(propval ${tgt} ${prop})
message ("${tgt} ${prop} = ${propval}")
endif()
endforeach(prop)
endfunction(print_target_properties)
print_target_properties(PySide2::pyside2)
Bug#931082: netgen: Dead link in man 1 netgen
Package: netgen Version: 6.2.1804+dfsg1-3 Severity: minor Dear Maintainer! The manpage of netgen contains a link to http://www.mathcces.rwth- aachen.de/netgen/doku.php which appears to be dead. As far as I understand, the homepage of netgen is now https://ngsolve.org/ When greping for the URL in the netgen repo at sala.debian.org, I find other occurences too: $ git grep rwth-aachen.de debian/manpages/netgen.sgml:Homepage: http://www.mathcces.rwth- aachen.de/netgen/doku.php debian/manpages/ng_stl.1:Homepage: http://www.mathcces.rwth- aachen.de/netgen/doku.php debian/manpages/ng_vol.1:Homepage: http://www.mathcces.rwth- aachen.de/netgen/doku.php doc/ng4.tex:Aachen University, Germany (http://www.mathcces.rwth- aachen.de/netgen). doc/ng4.tex:http://www.mathcces.rwth-aachen.de/netgen best regards Sebastian Bachmann -- System Information: Debian Release: 10.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages netgen depends on: ii libc62.28-10 ii libgcc1 1:8.3.0-6 ii libgl1 1.1.0-1 ii libglu1-mesa [libglu1] 9.0.0-2.1+b3 ii libmetis55.1.0.dfsg-5+b2 ii libnglib-6.2.18046.2.1804+dfsg1-3 ii libocct-data-exchange-7.37.3.0+dfsg1-5 ii libocct-foundation-7.3 7.3.0+dfsg1-5 ii libocct-modeling-algorithms-7.3 7.3.0+dfsg1-5 ii libocct-modeling-data-7.37.3.0+dfsg1-5 ii libocct-ocaf-7.3 7.3.0+dfsg1-5 ii libocct-visualization-7.37.3.0+dfsg1-5 ii libopenmpi3 3.1.3-11 ii libpython3.7 3.7.3-2 ii libstdc++6 8.3.0-6 ii libtcl8.68.6.9+dfsg-2 ii libtk8.6 8.6.9-2 ii libx11-6 2:1.6.7-1 ii libxmu6 2:1.1.2-2+b3 ii tix 8.4.3-10 ii zlib1g 1:1.2.11.dfsg-1 netgen recommends no packages. Versions of packages netgen suggests: pn netgen-doc -- no debconf information
Bug#924300: libnglib-6.2.1804: ldconfig does not find netgen shared object files
Package: libnglib-6.2.1804 Version: 6.2.1804+dfsg1-3 Severity: normal Dear Maintainer, I used netgen to build FreeCAD but without setting LD_LIBRARY_PATH, FreeCAD's FEM workbench does not start up, as the required netgen libraries are not found by ldconfig: $ dpkg -L libnglib-6.2.1804:amd64 /. /usr /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/netgen /usr/lib/x86_64-linux-gnu/netgen/libcsg.so # ldconfig -p | grep libcsg # echo $? 1 It looks like the problem is, that netgen installs itself into the netgen folder but does not provide symlinks to the parent folder or a ld.so.conf. The problem can be worked around by starting FreeCAD with a LD_LIBRARY_PATH set to the netgen folder. regards Sebastian -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libnglib-6.2.1804 depends on: ii libc62.28-8 ii libgcc1 1:8.3.0-2 ii libgl1 1.1.0-1 ii libglu1-mesa [libglu1] 9.0.0-2.1 ii libmetis55.1.0.dfsg-5+b2 ii libocct-data-exchange-7.37.3.0+dfsg1-5 ii libocct-foundation-7.3 7.3.0+dfsg1-5 ii libocct-modeling-algorithms-7.3 7.3.0+dfsg1-5 ii libocct-modeling-data-7.37.3.0+dfsg1-5 ii libocct-ocaf-7.3 7.3.0+dfsg1-5 ii libocct-visualization-7.37.3.0+dfsg1-5 ii libopenmpi3 3.1.3-10 ii libpython3.7 3.7.2-3 ii libstdc++6 8.3.0-2 ii libtcl8.68.6.9+dfsg-2 ii libtk8.6 8.6.9-2 ii libx11-6 2:1.6.7-1 ii libxmu6 2:1.1.2-2 ii zlib1g 1:1.2.11.dfsg-1 libnglib-6.2.1804 recommends no packages. libnglib-6.2.1804 suggests no packages. -- no debconf information
Bug#914103: stlink-tools: man page shows wrong option style
Package: stlink-tools Version: 1.5.1+ds-1 Severity: minor Dear Maintainer, I noticed, that the man page shows all options with a single dash, while st-info requires double dashes to work. For example, st-info has the option "--probe" (shown in the examples section correctly), but the man pages says "-probe". When using "st-info -probe", the tool just exists with a status code of 0. The man page of st-util contains in the description hints to the options "-listen_port" and "-stlinkv1" which seems to be also replaced by the double dash variants. Best regards Sebastian Bachmann -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (700, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages stlink-tools depends on: ii libc6 2.27-8 ii libstlink11.5.1+ds-1 ii libusb-1.0-0 2:1.0.22-2 stlink-tools recommends no packages. stlink-tools suggests no packages. -- no debconf information
Bug#874727: closed by Anton Gladky (Bug#874727: fixed in coin3 3.1.4~abc9f50+dfsg2-1)
Sorry for the noise but I got 0.17 working... Not sure what the problem was (just reinstalled). The SVG import bug works as well in 0.17. You can also trigger it using the python console in FreeCAD: from xml.parsers import expat expat.ParserCreate() Program received signal SIGSEGV, Segmentation fault. #0 /lib/x86_64-linux-gnu/libc.so.6(+0x35fc0) [0x7f1690c36fc0] #1 /lib/x86_64-linux-gnu/libexpat.so.1(XML_SetHashSalt+0x1b) [0x7f168b4b595b] #2 /usr/lib/python2.7/lib-dynload/pyexpat.x86_64-linux-gnu.so(+0x75b0) [0x7f167c9785b0] #3 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x9327) [0x7f1694caaab7] #4 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x732) [0x7f1694ca1032] #5 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19) [0x7f1694ca1649] [...] It is still the same bug as described in the forum: https://forum.freecadweb.org/viewtopic.php?f=15&t=23380&p=190525&hilit=expat#p190172 I build a working coin version back then by simply removing all attemps to build the internal expat version. It looks like the flag --enable-system-expat does not enable system expat but still uses the internal version. hth! regards sebastian On Tue, 9 Oct 2018 10:55:12 +0200 Sebastian Bachmann wrote: > There is another method to trigger this bug: > > * Open FreeCAD > * File --> Open > * Select any SVG File, click Open > * Select "SVG as Geometry (importSVG)", click Select > > It crashes with a similar stacktrace: > > Program received signal SIGSEGV, Segmentation fault. > #0 /lib/x86_64-linux-gnu/libc.so.6(+0x35fc0) [0x7f11a255efc0] > #1 /lib/x86_64-linux-gnu/libexpat.so.1(XML_SetHashSalt+0x1b) [0x7f119968c95b] > #2 /usr/lib/python2.7/lib-dynload/pyexpat.x86_64-linux-gnu.so(+0x75b0) > [0x7f118d4f65b0] > #3 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x94d6) > [0x7f11a3b6cc66] > [...] > > Tested here with FreeCAD 0.18 Revision: 14928 (Git) > > I tried with .17 from experimental but it looks like that the SVG import was > not > supported in that version? > But this version is pretty much unusable. No UI elements other that the > menu bar loads and there are only 2 Workspaces available for me... > > regards > Sebastian > > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (990, 'testing'), (700, 'unstable'), (500, 'oldstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) > Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), > LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages libcoin80v5 depends on: > ii libc6 2.27-6 > ii libgcc1 1:8.2.0-7 > ii libgl1 1.1.0-1 > ii libice6 2:1.0.9-2 > ii libsm6 2:1.2.2-1+b3 > ii libstdc++6 8.2.0-7 > ii libx11-62:1.6.6-1 > ii libxext62:1.3.3-1+b2 > > libcoin80v5 recommends no packages. > > Versions of packages libcoin80v5 suggests: > ii libbz2-1.0 1.0.6-9 > ii libfreetype6 2.8.1-2 > pn libopenal0a > pn libsimage-dev > ii zlib1g 1:1.2.11.dfsg-1 >
Bug#874727: closed by Anton Gladky (Bug#874727: fixed in coin3 3.1.4~abc9f50+dfsg2-1)
There is another method to trigger this bug: * Open FreeCAD * File --> Open * Select any SVG File, click Open * Select "SVG as Geometry (importSVG)", click Select It crashes with a similar stacktrace: Program received signal SIGSEGV, Segmentation fault. #0 /lib/x86_64-linux-gnu/libc.so.6(+0x35fc0) [0x7f11a255efc0] #1 /lib/x86_64-linux-gnu/libexpat.so.1(XML_SetHashSalt+0x1b) [0x7f119968c95b] #2 /usr/lib/python2.7/lib-dynload/pyexpat.x86_64-linux-gnu.so(+0x75b0) [0x7f118d4f65b0] #3 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x94d6) [0x7f11a3b6cc66] [...] Tested here with FreeCAD 0.18 Revision: 14928 (Git) I tried with .17 from experimental but it looks like that the SVG import was not supported in that version? But this version is pretty much unusable. No UI elements other that the menu bar loads and there are only 2 Workspaces available for me... regards Sebastian -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (700, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcoin80v5 depends on: ii libc6 2.27-6 ii libgcc1 1:8.2.0-7 ii libgl1 1.1.0-1 ii libice6 2:1.0.9-2 ii libsm6 2:1.2.2-1+b3 ii libstdc++6 8.2.0-7 ii libx11-62:1.6.6-1 ii libxext62:1.3.3-1+b2 libcoin80v5 recommends no packages. Versions of packages libcoin80v5 suggests: ii libbz2-1.0 1.0.6-9 ii libfreetype6 2.8.1-2 pn libopenal0a pn libsimage-dev ii zlib1g 1:1.2.11.dfsg-1 On Mon, 8 Oct 2018 16:35:21 -0700 mlampert wrote: > I've attached an xml tool table. > > * start FreeCAD from the command line > * Create a new document > * switch to "Path" Workbench > * start "Path Manager" from the Path menu > * import attached tooltable (note the file type selection) > > You'll get: > Program received signal SIGSEGV, Segmentation fault. > #0 /lib/x86_64-linux-gnu/libc.so.6(+0x35fc0) [0x7f75fc00ffc0] > #1 /lib/x86_64-linux-gnu/libexpat.so.1(XML_SetHashSalt+0x1b) [0x7f75f584095b] > #2 /usr/lib/python2.7/lib-dynload/pyexpat.x86_64-linux-gnu.so(+0x75b0) > [0x7f75c08145b0] > #3 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x94d6) > [0x7f7602316c66] > #4 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x8e5f) > [0x7f76023165ef] > #5 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x8e5f) > [0x7f76023165ef] > #6 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x732) > [0x7f760230d032] > > > I don't think the file itself matters at all because it segfaults while > trying to initialise libexpat, but in case the attachment gets filtered, this > is the content: > > > > > automatically_generate_title="0" material="1" type="end_mill" > corner_radius="0" flat_radius="0" cutting_edge_angle="0" > cutting_edge_height="50.8" /> > > > automatically_generate_title="0" material="1" type="end_mill" > corner_radius="0" flat_radius="0" cutting_edge_angle="0" > cutting_edge_height="50.8" /> > > > automatically_generate_title="0" material="1" type="end_mill" > corner_radius="0" flat_radius="0" cutting_edge_angle="0" > cutting_edge_height="50.8" /> > > > automatically_generate_title="0" material="1" type="end_mill" > corner_radius="0" flat_radius="0" cutting_edge_angle="0" > cutting_edge_height="50.8" /> > > > automatically_generate_title="0" material="1" type="end_mill" > corner_radius="0" flat_radius="0" cutting_edge_angle="0" > cutting_edge_height="50.8" /> > > > > > > > On Fri, 5 Oct 2018 10:03:26 +0200 > Christoph Berg wrote: > > > Re: markus 2018-10-05 <20181004193807.40af399c@yolanda> > > > it's a packaging bug - libcoin is statically linked with libexpat, > > > and the version being used is outdated. So anything that uses > > > libcoin and libexpat will run into a segfault. > > > > > > I am not aware of any other application that uses libcoin. > > > > I noticed because PostGIS is affected via postgis B-D -> libsfcgal-dev > > -> libsfcgal-osg1 -> libopenscenegraph100v5 -> libcoin80v5. Looking > > at https://udd.debian.org/cgi-bin/autoremovals.cgi there's quite a few > > packages depending on coin3. So the question whether this affects > > freecad only or more packages is making quite a difference. > > > > Do you have a recipe on how to reproduce the bug with freecad from
Bug#886457: psi-plus: Segfault after hibernation
Package: psi-plus Version: 1.2.105-1 Severity: normal Dear Maintainer, I noticed, that sometimes after hibernation, psi-plus will segfault. It looks like, that this segfault is not reproducable all the time, but after several hibernations, I see the following line in the syslog: psi-plus[10404]: segfault at 7fffd3cecff8 ip 7f00b72a7662 sp 7fffd3ced000 error 6 in libc-2.25.so[7f00b722d000+199000] The backtrace from the core file (I had no dbgsyms installed...) #0 0x7f00b72a7662 in _int_malloc (av=av@entry=0x7f00b75cab00 , bytes=bytes@entry=25) at malloc.c:3321 #1 0x7f00b72a9864 in __GI___libc_malloc (bytes=25) at malloc.c:2892 #2 0x7f00b7f26982 in QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f00b7f29025 in QByteArray::reallocData(unsigned int, QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f00b810b666 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f00b8114391 in QMetaObject::normalizedSignature(char const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f00b81368d7 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f00b9c4a402 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #8 0x7f00b9c4bd68 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7f00b9c4c153 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7f00b9c4bd83 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 the lines #9 and #10 repeat until #95212 #95213 0x7f00b9c4ca9f in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #95214 0x7f00b81328c2 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #95215 0x7f00b92ac59c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #95216 0x7f00b92b3e64 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #95217 0x7f00b8103258 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #95218 0x7f00b81059cd in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #95219 0x7f00b815cac3 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #95220 0x7f00b50f1fa7 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #95221 0x7f00b50f21e0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #95222 0x7f00b50f226c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #95223 0x7f00b815c0ef in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #95224 0x7f00b81012aa in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #95225 0x7f00b810a214 in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #95226 0x561684788478 in main () regards sebastian -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages psi-plus depends on: ii libc6 2.25-5 ii libgcc1 1:7.2.0-18 ii libhunspell-1.6-0 1.6.2-1 ii libidn11 1.33-2.1 ii libminizip1 1.1-8+b1 ii libqca-qt5-2 2.1.3-1 ii libqca-qt5-2-plugins 2.1.3-1 ii libqt5concurrent5 5.9.2+dfsg-6 ii libqt5core5a 5.9.2+dfsg-6 ii libqt5dbus5 5.9.2+dfsg-6 ii libqt5gui55.9.2+dfsg-6 ii libqt5network55.9.2+dfsg-6 ii libqt5svg55.9.2-3 ii libqt5widgets55.9.2+dfsg-6 ii libqt5x11extras5 5.9.2-1 ii libqt5xml55.9.2+dfsg-6 ii libstdc++67.2.0-18 ii libx11-6 2:1.6.4-3 ii libxcb1 1.12-1 ii psi-plus-common 1.2.105-1 ii zlib1g1:1.2.8.dfsg-5 Versions of packages psi-plus recommends: ii psi-plus-l10n 1.2.105-1 ii psi-plus-plugins 1.2.105-1 ii psi-plus-sounds 1.2.105-1 ii sox 14.4.2-3 Versions of packages psi-plus suggests: ii xdg-utils 1.1.2-1 -- no debconf information
Bug#874727: libcoin80v5: Program using libcoin80v5 and any other library that uses lebexpat1 segfaults.
Dear Maintainer, I investigated in this bug as well, and found out that the --enable-system-expat flag in configure seems to not do the job. The expat library in src/xml/expat is still build and linked. It is also interessting, that I'm not able to build a working version of libcoin using a current buster/sid installation. It build fine, without any error, but starting FreeCAD segfaults immediatly on startup. I tried this on my desktop machine: $ apt-get source libcoin80v5 $ cd coin3-3.1.4~abc9f50+dfsg1/ $ dpkg-buildpackage -us -uc Then I set up a VM with the help of snapshot.debian.org and used the version of 21 May 2016 (which is the build date of the version in sid). I had to edit the Makefiles and remove the build of xml/expat but was then able to build a version with libexpat1 2.2.3 from current sid. I'm not sure why the flag --enable-system-expat does not disable the build of the internal expat library. Maybe this is intended? I'm also not sure if the removal of the internal expat library breaks some features in libcoin, as I have no idea how to test it. I hope this helps to resolve this bug quickly :) regards Sebastian On Sat, 09 Sep 2017 02:33:35 -0700 markus wrote: > Package: libcoin80v5 > Version: 3.1.4~abc9f50+dfsg1-2 > Severity: critical > Justification: breaks unrelated software > > Dear Maintainer, > > Due to the change in libexpat1 (since 2.2.0, currently at 2.2.3) the included > copy of it in libcoin results in segfaults of any program that uses > libexpat1. Specifically any program that uses xml from python and links > against libcoin will segfault. > > The stacktrace looks like it is a problem with libexpat1 leading to a > segfault in XML_SetHashSalt - however looking at that function there is no > way it could possibly segfault - unless of course the provided XMLParser > pointer does not actually point to what expat expects to be an XMLParser - > which is indeed the case because the XMLParser instance was created by a call > into lobcoin which is still on libexpat 2.2.0. > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (900, 'testing'), (750, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), > LANGUAGE=en_CA:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages libcoin80v5 depends on: > ii libc6 2.24-17 > ii libgcc1 1:7.2.0-3 > ii libgl1-mesa-glx [libgl1] 13.0.6-1+b2 > ii libice6 2:1.0.9-2 > ii libsm62:1.2.2-1+b3 > ii libstdc++67.2.0-3 > ii libx11-6 2:1.6.4-3 > ii libxext6 2:1.3.3-1+b2 > > libcoin80v5 recommends no packages. > > Versions of packages libcoin80v5 suggests: > ii libbz2-1.0 1.0.6-8.1 > ii libfreetype6 2.8-0.2 > pn libopenal0a > ii libsimage-dev 1.7.1~2c958a6.dfsg-4 > ii zlib1g 1:1.2.8.dfsg-5 > > -- no debconf information > > signature.asc Description: PGP signature
Bug#872540: libpython2.7-stdlib:amd64: Segfault with libexpat when using XML_SetHashSalt
Package: libpython2.7-stdlib Version: 2.7.13-4 Severity: normal Tags: patch Dear Maintainer, There is a bug in the XML_SetHashSalt function, which causes Segfaults when using for example FreeCAD, as seen here: https://forum.freecadweb.org/viewtopic.php?f=15&t=23380 This bug occours with libexpat1 >= 2.2.1. A possible workaround is, to downgrade to 2.2.0. There is already a merged patch for this in python: https://bugs.python.org/issue29682 Judging from the date of the python version in /usr/share/doc/libpython2.7-minimal/changelog.Debian.gz, this patch should be already included in Debian (the changelog says: "Update to 20170719 from the 2.7 branch.", and the patch was merged on 20170309). But it isn't. The version of Modules/pyexpat.c is from 2014. Is there a specific reason, that this patch was not included? thanks in advance! regards sebastian -- System Information: Debian Release: buster/sid APT prefers stable APT policy: (991, 'stable'), (990, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libpython2.7-stdlib:amd64 depends on: ii libbz2-1.01.0.6-8.1 ii libc6 2.24-14 ii libdb5.3 5.3.28-13 ii libexpat1 2.2.3-1 ii libffi6 3.2.1-6 ii libncursesw5 6.0+20170715-2 ii libpython2.7-minimal 2.7.13-4 ii libreadline7 7.0-3 ii libsqlite3-0 3.19.3-3 ii libssl1.1 1.1.0f-4 ii libtinfo5 6.0+20170715-2 ii mime-support 3.60 libpython2.7-stdlib:amd64 recommends no packages. libpython2.7-stdlib:amd64 suggests no packages. -- no debconf information
Bug#863483: kodi: Provide polkit file for shutdown actions for kodi-standalone
Source: kodi Version: 2:17.1+dfsg1-3 Severity: wishlist Dear Maintainer, to use kodi-standalone to a full extend, one need to add a polkit file to allow the kodi user to shutdown the machine. As the systemd service is also provided by the package, I think it would be good to provide this file as well or note it in the README (I was not able to find it). The content of the file /etc/polkit-1/localauthority/50-local.d/kodi.pkla should look like this: [kodi user] Identity=unix-user:kodi Action=org.freedesktop.login1.* ResultAny=yes ResultInactive=no ResultActive=yes See also http://www.richud.com/wiki/Ubuntu_Minimal_KODI_Install http://forum.kodi.tv/showthread.php?tid=165707 regards sebastian -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages kodi depends on: ii init-system-helpers 1.48 ii kodi-bin 2:17.1+dfsg1-3 ii kodi-data2:17.1+dfsg1-3 Versions of packages kodi recommends: ii kodi-visualization-spectrum 1.1.1-1 kodi suggests no packages. -- no debconf information
Bug#853252: freeglut3: Menu manipulation not allowed while menus in use
Package: freeglut3 Version: 2.8.1-3 Severity: normal Dear Maintainer(s), When using calculix-cgx, a finite element viewer, the tool crashes if selecting menu entries with the error message: freeglut (cgx): Menu manipulation not allowed while menus in use. The bug was already reported and fixed several years ago in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1017551 The bug is reproduceable as in the description of the bugreport in Fedora. If I downgrade freeglut3 to 2.6.0-4 (wheezy), cgx works normal. regards sebastian -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (600, 'testing'), (500, 'stable'), (500, 'oldstable'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages freeglut3 depends on: ii libc6 2.24-8 ii libgl1-mesa-glx [libgl1] 13.0.3-1 ii libx11-6 2:1.6.4-2 ii libxext6 2:1.3.3-1 ii libxi62:1.7.8-2 ii libxxf86vm1 1:1.1.4-1 freeglut3 recommends no packages. freeglut3 suggests no packages. -- no debconf information
Bug#804629: linux-image-amd64: Cannot mount LVM RAID1 file system at boot
Dear maintainer(s) and users affected by this bug, I was affected by this bug as well. The lvm was created as: lvcreate --type raid1 --name foo -L 50G bar with kernel 3.16.36-1+deb8u2 (yesterday). After an upgrade to 3.16.39-1 (today), the volume would not activate: [ 50.848231] md/raid1:mdX: active with 2 out of 2 mirrors [ 50.850482] mdX: invalid bitmap file superblock: bad magic [ 50.851611] mdX: bitmap file superblock: [ 50.851613] magic: [ 50.851615]version: 1431655765 [ 50.851616] uuid: ... [ 50.851618] events: 134 [ 50.851619] events cleared: 134 [ 50.851620] state: [ 50.851621] chunksize: 524288 B [ 50.851622] daemon sleep: 5s [ 50.851623] sync size: 52428800 KB [ 50.851624] max write behind: 0 [ 50.851627] mdX: failed to create bitmap (-22) [ 50.852809] device-mapper: table: 253:26: raid: Fail to run raid array [ 50.853940] device-mapper: ioctl: error adding target to table There was a second lv (also a --type raid1, but created earlier), that had some similar issue, but I was able to activate it partialy by using lvchange -a y --activationmode partial bar/otherfoo The other LV was not able to be activated even as degraded, thus I decided to rsync all files from one of the rimages and create a new one... HTH! regards sebastian signature.asc Description: OpenPGP digital signature
Bug#850278: connman: upgrade von 1.33-2 to 1.33-3 cleared /var/lib/connman
Package: connman Version: 1.33-3 Severity: important Dear Maintainer, after an upgrade of connman from version 1.33-2 to 1.33-3, the directory /var/lib/connman was removed, thus all my configurations are gone. I read nothing in the changelog about this behaviour, only that the statedir should be cleaned now on purge actions. If you need anything else, please reply! regards sebastian -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (1, 'experimental'), (1, 'unstable'), (1, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages connman depends on: ii dbus 1.10.14-1 ii init-system-helpers 1.46 ii iptables 1.6.0+snapshot20161117-4 ii libc62.24-8 ii libdbus-1-3 1.10.14-1 ii libglib2.0-0 2.50.2-2 ii libgnutls30 3.5.7-3 ii libreadline7 7.0-1 ii libxtables12 1.6.0+snapshot20161117-4 ii lsb-base 9.20161125 Versions of packages connman recommends: ii bluez 5.43-1 ii ofono 1.18-1 ii wpasupplicant 2.5-2+v2.4-3+b1 Versions of packages connman suggests: ii connman-vpn 1.33-3 -- no debconf information
Bug#822610: connman: man connmand lists options that are not valid
Hi!
Seems fine to me, I also could not find any more and --selftest is gone now.
regards
sebastian
On 09/02/2016 10:35 AM, Alexander Sack wrote:
> tags 822610 + confirmed patch
> thanks
>
> Hi Sebastian,
>
> I checked latest upstream trunk and seems this issue is still present
> even if only one option i could find in the source that is not in the
> manpage.
>
> The other way around seems to be fine now (e.g. no options referred to
> in manpage being not available at all).
>
> { "nobacktrace", 0, G_OPTION_FLAG_REVERSE,
> G_OPTION_ARG_NONE, &option_backtrace,
> "Don't print out backtrace information" },
>
>
> Does his patch look ok for you on the manpage front?
>
> diff --git a/doc/connman.8.in b/doc/connman.8.in
> index 9b71779..07e6ef5 100644
> --- a/doc/connman.8.in
> +++ b/doc/connman.8.in
> @@ -80,6 +80,9 @@ Never load these plugins. The option can be a
> pattern containing
> Wifi driver that WiFi/Supplicant should use. If this flag is omitted,
> then the value "nl80211,wext" is used by default.
> .TP
> +.BR \-n ", " \-\-nobacktrace
> +Don't print out backtrace information.
> +.TP
> .BR \-n ", " \-\-nodaemon
> Do not daemonize. This is useful for debugging, and directs log output to
> the controlling terminal in addition to syslog.
>
>
>
> 2016-04-25 17:42 GMT+02:00 Sebastian Bachmann :
>> Package: connman
>> Version: 1.21-1.2+b2
>> Severity: minor
>>
>> Dear Maintainer,
>> The manpage of connmand(8) lists options, that are not available on the
>> command
>> itself, like -t/--selftest and connmand --help shows options that are not in
>> the manpage, like -r, --nodnsproxy
>>
>> It would be kind to correct those options.
>>
>> regards
>> Sebastian Bachmann
>>
>>
>>
>> -- System Information:
>> Debian Release: stretch/sid
>> APT prefers testing
>> APT policy: (900, 'testing'), (1, 'unstable')
>> Architecture: amd64 (x86_64)
>> Foreign Architectures: i386
>>
>> Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
>> Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
>> Shell: /bin/sh linked to /bin/dash
>> Init: systemd (via /run/systemd/system)
>>
>> Versions of packages connman depends on:
>> ii dbus 1.10.8-1
>> ii init-system-helpers 1.29
>> ii libc62.22-6
>> ii libdbus-1-3 1.10.8-1
>> ii libglib2.0-0 2.48.0-1
>> ii libgnutls30 3.4.10-4
>> ii libreadline6 6.3-8+b4
>> ii libxtables11 1.6.0-2
>> ii lsb-base 9.20160110
>>
>> Versions of packages connman recommends:
>> ii bluez 5.36-1
>> ii ofono 1.15-3
>> ii wpasupplicant 2.3-2.3
>>
>> Versions of packages connman suggests:
>> pn indicator-network
>>
>> -- no debconf information
signature.asc
Description: OpenPGP digital signature
Bug#822558: Further information
Hi! I reinstalled my laptop with debian stretch and applied the same configuration there. It seems that fixes the issue. I'm running connman 1.32-0.1 now. Either it was fixed in this version or my laptop's setup was broken... regards sebastian On 09/02/2016 10:39 AM, Alexander Sack wrote: > tags 822558 + moreinfo > severity 822558 important > thanks > > Hi, > > by any chance did you check the latest version in sid/testing and > could that you still see those crashes there? > > - Alexander > > > 2016-04-25 20:28 GMT+02:00 Sebastian Bachmann : >> Hi! >> >> I tried some more things here: >> first of all i used systemd-sysv and found out that the same error >> happens there too. >> Then I added the config option "--config=/etc/connman/main.conf" to the >> systemd startup file /lib/systemd/system/connman.service. This seems to >> work after a reboot. >> >> The only problem I see, is that i can not restart connman via systemctl >> restart connman.service, without crashing it. >> The curious part ist, that it crashed before, even after a reboot and >> now it's not. >> >> So summarize what I did: >> >> using sysvinit >> 1) create the directory /etc/connman as root >> 2) create the file /etc/connman/main.conf as root with the content of >> the first mail >> 3) run /etc/init.d/connman restart >> 4) got the crash from above >> 5) reboot, connman would not start >> >> using systemd >> 1) create folder and config file (same as with sysvinit) >> 2) run systemctl restart connman.service >> 3) got the same crash again >> 4) reboot, connman would not start >> 5) Add explicit config option in service file >> 6) run systemctl restart connman.service again >> 7) connman would crash again >> 8) reboot: connman starts >> >> regards >> sebastian >> signature.asc Description: OpenPGP digital signature
Bug#823152: gqrx-sdr: dependency on libboost 1.54 is not met
Package: gqrx-sdr Version: 2.5.3-1 Severity: important Dear Maintainer, After starting gqrx, i get the following error message: $ gqrx gqrx: error while loading shared libraries: libboost_date_time.so.1.54.0: cannot open shared object file: No such file or directory And there are a few more libraries from the libboost package, that can not be found: $ ldd /usr/bin/gqrx [...] libboost_date_time.so.1.54.0 => not found libboost_filesystem.so.1.54.0 => not found libboost_program_options.so.1.54.0 => not found libboost_regex.so.1.54.0 => not found libboost_system.so.1.54.0 => not found libboost_thread.so.1.54.0 => not found libboost_unit_test_framework.so.1.54.0 => not found libboost_serialization.so.1.54.0 => not found [...] regards sebastian -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (800, 'stable'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gqrx-sdr depends on: ii libboost-program-options1.58.0 1.58.0+dfsg-5+b1 ii libboost-system1.58.0 1.58.0+dfsg-5+b1 ii libc6 2.22-7 ii libgcc1 1:5.3.1-14 ii libgnuradio-analog3.7.9 3.7.9.2-1 ii libgnuradio-audio3.7.9 3.7.9.2-1 ii libgnuradio-blocks3.7.9 3.7.9.2-1 ii libgnuradio-digital3.7.93.7.9.2-1 ii libgnuradio-fft3.7.93.7.9.2-1 ii libgnuradio-filter3.7.9 3.7.9.2-1 ii libgnuradio-osmosdr0.1.40.1.4-8 ii libgnuradio-pmt3.7.93.7.9.2-1 ii libgnuradio-runtime3.7.93.7.9.2-1 ii libpulse0 8.0-2 ii libqt5core5a5.5.1+dfsg-16+b1 ii libqt5gui5 5.5.1+dfsg-16+b1 ii libqt5network5 5.5.1+dfsg-16+b1 ii libqt5svg5 5.5.1-2 ii libqt5widgets5 5.5.1+dfsg-16+b1 ii libstdc++6 5.3.1-14 ii libvolk1.1 1.2.2-1 ii pulseaudio 8.0-2 gqrx-sdr recommends no packages. gqrx-sdr suggests no packages. -- no debconf information
Bug#822558: Further information
Hi! I tried some more things here: first of all i used systemd-sysv and found out that the same error happens there too. Then I added the config option "--config=/etc/connman/main.conf" to the systemd startup file /lib/systemd/system/connman.service. This seems to work after a reboot. The only problem I see, is that i can not restart connman via systemctl restart connman.service, without crashing it. The curious part ist, that it crashed before, even after a reboot and now it's not. So summarize what I did: using sysvinit 1) create the directory /etc/connman as root 2) create the file /etc/connman/main.conf as root with the content of the first mail 3) run /etc/init.d/connman restart 4) got the crash from above 5) reboot, connman would not start using systemd 1) create folder and config file (same as with sysvinit) 2) run systemctl restart connman.service 3) got the same crash again 4) reboot, connman would not start 5) Add explicit config option in service file 6) run systemctl restart connman.service again 7) connman would crash again 8) reboot: connman starts regards sebastian signature.asc Description: OpenPGP digital signature
Bug#822610: connman: man connmand lists options that are not valid
Package: connman Version: 1.21-1.2+b2 Severity: minor Dear Maintainer, The manpage of connmand(8) lists options, that are not available on the command itself, like -t/--selftest and connmand --help shows options that are not in the manpage, like -r, --nodnsproxy It would be kind to correct those options. regards Sebastian Bachmann -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages connman depends on: ii dbus 1.10.8-1 ii init-system-helpers 1.29 ii libc62.22-6 ii libdbus-1-3 1.10.8-1 ii libglib2.0-0 2.48.0-1 ii libgnutls30 3.4.10-4 ii libreadline6 6.3-8+b4 ii libxtables11 1.6.0-2 ii lsb-base 9.20160110 Versions of packages connman recommends: ii bluez 5.36-1 ii ofono 1.15-3 ii wpasupplicant 2.3-2.3 Versions of packages connman suggests: pn indicator-network -- no debconf information
Bug#822558: connmand crashes if a config file is present at /etc/connman/main.conf
Package: connman Version: 1.21-1.2+b2 Severity: important Dear Maintainer, I need to disable the automatic hostname change of connman, so i took a look at the manpage of connman.conf(5) which states, that a config file at /etc/connman/main.conf with the following content should do the trick: [General] AllowHostnameUpdates=false But instead, connman crashes now (reproduceable!) if the config file or even a empty folder called /etc/connman is present: Apr 25 13:06:26 cebalrai connmand[3706]: Connection Manager version 1.21 Apr 25 13:06:26 cebalrai connmand[3706]: Adding configuration tunet Apr 25 13:06:26 cebalrai connmand[3706]: Adding service configuration tunet Apr 25 13:06:26 cebalrai connmand[3706]: Adding configuration eduroam Apr 25 13:06:26 cebalrai connmand[3706]: Adding service configuration eduroam Apr 25 13:06:27 cebalrai connmand[3706]: Failed to bind UDP listener socket Apr 25 13:06:27 cebalrai connmand[3706]: Failed to bind UDP listener socket Apr 25 13:06:27 cebalrai connmand[3706]: Couldn't create listener for index 1 err -5 Apr 25 13:06:27 cebalrai connmand[3706]: Aborting (signal 11) [/usr/sbin/connmand] Apr 25 13:06:27 cebalrai connmand[3706]: backtrace Apr 25 13:06:27 cebalrai connmand[3706]: +++ The services tunet and eduroam are from my university wifi. I'm not sure if I do something terribly wrong but I checked the man page now several times and think the config is on the right place. Thanks for your help! regards sebastian -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (900, 'testing'), (1, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages connman depends on: ii dbus 1.10.8-1 ii init-system-helpers 1.29 ii libc62.22-6 ii libdbus-1-3 1.10.8-1 ii libglib2.0-0 2.48.0-1 ii libgnutls30 3.4.10-4 ii libreadline6 6.3-8+b4 ii libxtables11 1.6.0-2 ii lsb-base 9.20160110 Versions of packages connman recommends: ii bluez 5.36-1 ii ofono 1.15-3 ii wpasupplicant 2.3-2.3 Versions of packages connman suggests: pn indicator-network -- no debconf information
Bug#770999: Same issue for iPod Nano 7g
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, the same segfault happens when connecting a iPod Nano 7G: Program received signal SIGSEGV, Segmentation fault. 0x76cbae73 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (gdb) bt #0 0x76cbae73 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #1 0x76cbad9d in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #2 0x76cbaee4 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #3 0x76cbb08e in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #4 0x76d7fbac in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #5 0x75d99015 in g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x75dab061 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #7 0x75db3899 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x75db412f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x76ebd0fc in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #10 0x76d7cfbe in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #11 0x76d7edbc in gtk_main_do_event () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #12 0x768f78e2 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #13 0x75ac3fe7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x75ac4240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x75ac4562 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x76cf4090 in gtk_dialog_run () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #17 0x7fffd1cb274b in repository_ipod_init_set_model () from /usr/lib/x86_64-linux-gnu/gtkpod/librepository_editor.so #18 0x77babec3 in gp_load_ipod () from /usr/lib/x86_64-linux-gnu/libgtkpod.so.1 #19 0x77bc4596 in ?? () from /usr/lib/x86_64-linux-gnu/libgtkpod.so.1 #20 0x768c41f8 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #21 0x75ac4903 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x75ac3e9a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x75ac4240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x75ac4562 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x76d7df95 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #26 0x0040815f in main () It seems like something changed in the libgtk? regards sebastian -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWWauLAAoJEG/b2Mb5O1+LIEkQAI2a4RmmAR3RV7TOUfSHhWRt 1aGm5EZFOhkW75YE+pHor4XaCi3O2CrS2m7l6FiednGT6V82ugs2j4onjAXMwbgU iZoGjWMFP+qvD+27ptKcJy85ISPYsnQoeRSLtgUIEAwFig2KGzoSqMt6Sl89huYB KJqIA863bV5DkelOd+EfNPpsuueBbJfg6cKdHIWJvrIv6App99XhbhqQQkyfQmjt pBdTWmKjF1+FotUraYOwYuSC8Kb02KQo5Y2YVJ1XyaE2ZY2FzL3JXVT/o9rAbTOp 3ck4MFhlbQhT+Ha+sU5z3Y3RHr3DAOTbnFRr4jjAgIwk9T+rXdiYAmKFHjrswnUr tTWvJBLI8bNML2eKGQ/dh1zhrQ9Y2SfR8tjE7vxzXW5hRMsKFy82qedfwZmuaXx0 KqHeT7HScRWZHFKws9Izt3hAw0RjxPn2JbccfGTqvJOubRGWZZVDor1shNeOkLBZ AWAK09SNL6327wPV5Bdmyuf+jKLInth6ctgzTibRaJJ/e6cs/bBiB+8EFBmGK6RG 9qzgMyCKWOXQLape5+sHuOJ97BGXMv3t5IcGhd5t/WwWakNWzhCDRw4+fWmYEQ2Z 1nOgiHB7vEbP3+2bTxHYy/CjR5iKthx4+sKyepFFkT7Qb4Tp3dEBGXudxHzw2n7B NCg05Yaj1Nm4P8HBblic =DTDY -END PGP SIGNATURE-
Bug#778752: debirf installs wrong architecture of klibc-utils for initrd
Package: debirf
Version: 0.34
Severity: important
Tags: patch
When building on amd64 architecture and using the options
DEBIRF_ARCH=i386
DEBIRF_KERNEL_FLAVOUR=686-pae
debirf will copy the klibc.so and run-init from the host system, resulting in a
64bit binary inside a 32bit image (see line 180 and 181 in debirf).
A fix for this problem would be to install klibc-utils on the $DEBIRF_ROOT and
copy the files from there:
add klibc-utils to list of INCLUDE files for debootstrap and copy files from
$DEBIRF_ROOT
--- a/debirf
+++ b/debirf
@@ -42,7 +42,8 @@ export
DEVICE_ARCHIVE=${DEVICE_ARCHIVE:-/usr/share/debirf/devices.tar.gz}
export INCLUDE=\
busybox-static,\
gpgv,\
-less
+less,\
+klibc-utils
# list of packages to exclude from debootstrap
export EXCLUDE=\
@@ -178,8 +179,8 @@ create_initrd_nested() {
done
# copy in run-init and needed libraries
-cp -f /usr/lib/klibc/bin/run-init "$NEST_ROOT"/bin/
-cp -f /lib/klibc-* "$NEST_ROOT"/lib/
+cp -f "$DEBIRF_ROOT"/usr/lib/klibc/bin/run-init "$NEST_ROOT"/bin/
+cp -f "$DEBIRF_ROOT"/lib/klibc-* "$NEST_ROOT"/lib/
# symlink /lib64 if that is done on host
# FIXME: is this necessary?
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (900, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages debirf depends on:
ii apt 1.0.9.6
ii cpio 2.11+dfsg-4
ii debootstrap 1.0.66
ii fakechroot 2.17.2-1
ii fakeroot 1.20.2-1
ii klibc-utils 2.0.4-2
Versions of packages debirf recommends:
ii grub-common 2.02~beta2-20
ii lsb-release 4.1+Debian13+nmu1
ii syslinux-common 3:6.03+dfsg-5
ii xorriso 1.3.2-1.1
debirf suggests no packages.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770999: gdb bt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, sorry i totaly forgot to add information from gdb, which are probably more useful than the syslog. Program received signal SIGSEGV, Segmentation fault. 0x75e75e9d in g_type_check_value_holds () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (gdb) bt #0 0x75e75e9d in g_type_check_value_holds () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #1 0x753168f8 in ?? () from /usr/lib/x86_64-linux-gnu/libgpod.so.4 #2 0x7531b623 in itdb_parse () from /usr/lib/x86_64-linux-gnu/libgpod.so.4 #3 0x77baa55c in gp_import_itdb (old_itdb=old_itdb@entry=0x14fb6e0, type=, mp=0x14f8e00 "/run/user/1000/gvfs/afc:host=9378bbe3702d3aa44b002b0af7f69df93f3764d0", name_off=0x14f1a30 "/home/reox/.gtkpod/gtkpod_2.itdb", name_loc=name_loc@entry=0x0) at file_itunesdb.c:546 #4 0x77baaf98 in gp_merge_itdb (old_itdb=0x14fb6e0) at file_itunesdb.c:802 #5 gp_load_ipod (itdb=itdb@entry=0x14fb6e0) at file_itunesdb.c:920 #6 0x77bc2d16 in ad_timeout_cb (data=0x14c8430) at autodetection.c:280 #7 0x76942e78 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #8 0x75b7d613 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x75b7cb6d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x75b7cf48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x75b7d272 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x76dc8ba5 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #13 0x004080ef in main (argc=1, argv=0x7fffe168) at main.c:99 - - sebastian -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJUdgZkAAoJEAhgHfpCPcybXNAH/jK4uGWMk71rzj5hMBKFVM1o fCuVLFmPV5d05z7QgEHkSt6Z9yJY4RWVmMKgMHeNE4UEmMt8V90EyuMsvQoRCoiY Fm7rGzlY4+bWb00ajCZUxS9VlvGUQcsmyWKwV8iew42FeuR2mZm+0olcBK8RQK28 1iigpi00hLBpAYm53w/5R5Is0hDDej2Kh75cycx1jrFDe6JpXjKLvdg59nczJpuF xT6qtPwObSMiBptKYNonCl3ECiU5o3KAKTwgRleaHpU1lP1aisTYj/H7kg7zkmrp L6fLFIMvqoeck66TYp27TBjM6BkaqE1ZB6yWNnFJp4z6DZyugz9pfhlF9QYZ2mM= =Ln1A -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770999: gtkpod: Segfault when selecting new iPod
Package: gtkpod Version: 2.1.4-4 Severity: important Hi, I started gtkpod and it asked me to give the iPod Model. If I select the Model or even click on cancel, gtkpod crashes and gives me a segault. syslog: [ 504.678346] gtkpod[3092]: segfault at 1f0036 ip 7f4725ea2e9d sp 7fff6730d7c0 error 4 in libgobject-2.0.so.0.4200.0[7f4725e6f000+51000] [ 514.832865] gtkpod[3129]: segfault at 1f0036 ip 7fb444b27e9d sp 7fffea382980 error 4 in libgobject-2.0.so.0.4200.0[7fb444af4000+51000] [ 532.355169] gtkpod[3148]: segfault at 1f0036 ip 7f4a9ccdfe9d sp 7fff15aee440 error 4 in libgobject-2.0.so.0.4200.0[7f4a9ccac000+51000] [ 880.145632] gtkpod[3414]: segfault at 1f0036 ip 7fb178e20e9d sp 7fff419a2aa0 error 4 in libgobject-2.0.so.0.4200.0[7fb178ded000+51000] -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gtkpod depends on: ii gtkpod-data 2.1.4-4 ii libanjuta-3-0 2:3.14.0-1 ii libatk1.0-0 2.14.0-1 ii libatomicparsley0 2.1.4-4 ii libc6 2.19-13 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libclutter-1.0-01.20.0-1 ii libclutter-gtk-1.0-01.6.0-1 ii libcogl-pango20 1.18.2-3 ii libcogl-path20 1.18.2-3 ii libcogl20 1.18.2-3 ii libcurl3-gnutls 7.38.0-3 ii libdrm2 2.4.58-2 ii libegl1-mesa [libegl1-x11] 10.3.2-1 ii libflac81.3.0-2+b1 ii libgbm1 10.3.2-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgdl-3-5 3.14.0-2 ii libglib2.0-02.42.0-2 ii libgpod40.8.3-1.1+b1 ii libgstreamer-plugins-base0.10-0 0.10.36-2 ii libgstreamer0.10-0 0.10.36-1.5 ii libgtk-3-0 3.14.4-2 ii libgtkpod1 2.1.4-4 ii libid3tag0 0.15.1b-11 ii libimobiledevice4 1.1.6+dfsg-3.1 ii libjavascriptcoregtk-3.0-0 2.4.7-2 ii libjson-glib-1.0-0 1.0.2-1 ii libogg0 1.3.2-1 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libsoup2.4-12.48.0-1 ii libvorbis0a 1.3.4-2 ii libvorbisfile3 1.3.4-2 ii libwayland-client0 1.6.0-2 ii libwayland-cursor0 1.6.0-2 ii libwayland-egl1-mesa [libwayland-egl1] 10.3.2-1 ii libwayland-server0 1.6.0-2 ii libwebkitgtk-3.0-0 2.4.7-2 ii libx11-62:1.6.2-3 ii libxcomposite1 1:0.4.4-1 ii libxdamage1 1:1.1.4-2 ii libxext62:1.3.3-1 ii libxfixes3 1:5.0.1-2+b1 ii libxi6 2:1.7.4-1+b1 ii libxkbcommon0 0.4.3-2 ii libxml2 2.9.1+dfsg1-4 ii libxrandr2 2:1.4.2-1+b1 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages gtkpod recommends: ii id3v2 0.1.12-2.1 ii vorbis-tools 1.4.0-5 Versions of packages gtkpod suggests: pn faad ii lame 3.99.5+repack1-5 pn mp3gain ii perl 5.20.1-2 ii python 2.7.8-2 -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#751124: lvm2: "Unable to find cache pool LV" when adding cache volume
Package: lvm2 Version: 2.02.106-2 Severity: normal The Cache volume was created using lvconvert --type cache-pool --poolmetadata cebalrai-ssd/lv_cache_meta cebalrai- ssd/lv_cache The Cache volume shows up in "lvs" LV VG Attr LSize Pool Origin Data% Move Log Cpy%Syn home cebalrai-hdd -wi-ao 180.00g lv_cache cebalrai-ssd Cwi---C--- 5.00g root cebalrai-ssd -wi-ao 40.00g swap cebalrai-ssd -wi-ao 8.00g but it can not added to the volume $ lvconvert --type cache --cachepool cebalrai-ssd/lv_cache cebalrai-hdd/home Unable to find cache pool LV, cebalrai-ssd/lv_cache -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lvm2 depends on: ii dmsetup 2:1.02.85-1 ii init-system-helpers 1.18 ii initscripts 2.88dsf-53 ii libc6 2.18-7 ii libdevmapper-event1.02.1 2:1.02.85-1 ii libdevmapper1.02.12:1.02.85-1 ii libreadline5 5.2+dfsg-2 ii libudev1 204-8 ii lsb-base 4.1+Debian12 lvm2 recommends no packages. Versions of packages lvm2 suggests: pn thin-provisioning-tools -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673785: seems to be fixed in 3.4.15-1+b1
Hi, I don't know exacatly if the problem is fixed in this version but i can't complain any more about freezing windows. i also switched hardware from Core2Duo to i5 CPU and much more RAM... but as far as i can tell the problem was fixed. -sebastian signature.asc Description: Digital signature
Bug#716717: zenity: GLib-CRITICAL assertion failed on notification
Package: zenity Version: 3.8.0-1 Severity: minor I use zenity notifications in some scripts and get all the time this error message: (zenity:2783): GLib-CRITICAL **: g_strv_length: assertion `str_array != NULL' failed (zenity:2783): GLib-CRITICAL **: g_hash_table_unref: assertion `hash_table != NULL' failed Problem occours if using zenity --notification --text "something" or more options but not on other types of zenity (e.g. --calendar or --error) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (400, 'stable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages zenity depends on: ii libc6 2.17-7 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglib2.0-02.36.1-2build1 ii libgtk-3-0 3.4.2-6 ii libnotify4 0.7.5-2 ii libpango-1.0-0 1.32.5-5+b1 ii libwebkitgtk-3.0-0 1.8.1-3.4 ii libx11-62:1.6.0-1 ii zenity-common 3.8.0-1 zenity recommends no packages. zenity suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673785: awesome: Freezing and then unusable windows
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 no a custom config made by my own, you can get it here: http://git.42.lefant.net/gitweb/reox/awesomerc.git/tree but its mostly default, so just autostarts, tag names and stuff are adapted On 2012-05-21 15:17, Julien Danjou wrote: > On Mon, May 21 2012, Sebastian Bachmann wrote: > >> Awesome keeps freezing for me sometimes, after a few seconds the >> freeze is over but i cant do nothing more than use the current >> window. Awesome does not respond to any Mod Key Shortcut, so its >> impossible to switch between tags and windows, also i cant click >> any tags. The complete window manager seems to stuck somewhere. >> I dont see any log output or error message, so its hard to say >> whats broken. The freezing is undeterministic but more often in >> webbrowser (chromium, firefox) then in other applications. > > Are you using the default configuration file? > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPukEtAAoJEAhgHfpCPcybO90IALY0+YslyRkuCZ/xbmaYJ3XW duVb+wZp5RHTJ2hrCQ6RptUf+nNwOcSwEDnPUrTwPT2ekSI3+gT1xyJNcQYwmJhq RxxiaC1oeS/nvIgDXX6K4XYDJTGsZlBXmX3uLFtPFh2BCnJL2GEnEu9+4S9WTtN2 IwVCYTWyeRI//6CQpgEBcwnF9fvymCxnwEATI6OAPL2t2RlLzWFyykBDvR0CdCvN mBLn/tZww5Rr7YVp9Uq0LmLDs3dzJ3pNWn0K/bv616ugKCH9ullyoHMcCZxrvec8 fMRCNz8PYKmcQ+zgOI7IO+NgiHJppvphfXHPPJEIMbvlzkiUqJ7YkXXzXB3e7Xo= =98iu -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673785: awesome: Freezing and then unusable windows
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 no a custom config made by my own, you can get it here: http://git.42.lefant.net/gitweb/reox/awesomerc.git/tree but its mostly default, so just autostarts, tag names and stuff are adapted On 2012-05-21 15:17, Julien Danjou wrote: > On Mon, May 21 2012, Sebastian Bachmann wrote: > >> Awesome keeps freezing for me sometimes, after a few seconds the >> freeze is over but i cant do nothing more than use the current >> window. Awesome does not respond to any Mod Key Shortcut, so its >> impossible to switch between tags and windows, also i cant click >> any tags. The complete window manager seems to stuck somewhere. I >> dont see any log output or error message, so its hard to say >> whats broken. The freezing is undeterministic but more often in >> webbrowser (chromium, firefox) then in other applications. > > Are you using the default configuration file? > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPukElAAoJEAhgHfpCPcybZX8IAKe5eMsyc2/RfiuplGUalXnz mA9W+ch6HHdF/c6ecGVZUfyfSVF8FyRxnGxctnyxFEAPc7TB+6goQX7SBvWD52sa BlNxMMthc3B5Bp4GKN5pY3BU7xa3aI5VYtLoykNL5Kdwn0j6b/HBRRLQdmGVh6zH Wwq2B/sav1XuGAxQGfX7jBJMp8Mh0312lBPknKr7Lp4rme7YTYtzlrzLZNuhruSA v0tveXH78XspZm8Z1RmSBr0wvxEc8ENx+Iq8/HSU3MQiOaIJJMAvcYTZEX+Y2mEb RGejeofj7VW9nSroezZ2+XIp1VeHWarwTFYPZby0E6wcyGYjEPm024Gi/9OTa+I= =jVSh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673785: awesome: Freezing and then unusable windows
Package: awesome Version: 3.4.11-2 Severity: important Awesome keeps freezing for me sometimes, after a few seconds the freeze is over but i cant do nothing more than use the current window. Awesome does not respond to any Mod Key Shortcut, so its impossible to switch between tags and windows, also i cant click any tags. The complete window manager seems to stuck somewhere. I dont see any log output or error message, so its hard to say whats broken. The freezing is undeterministic but more often in webbrowser (chromium, firefox) then in other applications. -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (900, 'stable'), (800, 'testing'), (700, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages awesome depends on: ii dbus-x11 1.5.12-1 ii libc6 2.13-32 ii libcairo2 1.12.2-1 ii libdbus-1-3 1.5.12-1 ii libev41:4.11-1 ii libglib2.0-0 2.32.2-1 ii libimlib2 1.4.5-1 ii liblua5.1-0 5.1.5-1 ii libpango1.0-0 1.30.0-1 ii libstartup-notification0 0.12-1 ii libx11-6 2:1.4.99.901-2 ii libxcb-icccm4 0.3.8-1 ii libxcb-image0 0.3.8-1 ii libxcb-keysyms1 0.3.8-1 ii libxcb-randr0 1.8.1-1 ii libxcb-render01.8.1-1 ii libxcb-shape0 1.8.1-1 ii libxcb-shm0 1.8.1-1 ii libxcb-util0 0.3.8-2 ii libxcb-xinerama0 1.8.1-1 ii libxcb-xtest0 1.8.1-1 ii libxcb1 1.8.1-1 ii libxdg-basedir1 1.1.1-2 ii menu 2.1.46 Versions of packages awesome recommends: ii feh ii rlwrap 0.37-3 ii x11-xserver-utils 7.7~2 awesome suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#656231: icedove: Icedove does not display notifications in window manager notifier
Package: icedove Version: 8.0-2 Severity: normal Normaly the most notifications of icedove was shown in my window managers default notification bar. In this version this feature isnt anymore available and icedove opens own notification windows. This happens to all Error notifications, like Server not found, and not to the new message notification. I think these ones have ever been seperate. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-rc7-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove depends on: ii debianutils 4.1 ii fontconfig2.8.0-3 ii libasound21.0.24.1-4 ii libatk1.0-0 2.2.0-2 ii libc6 2.13-24 ii libcairo2 1.10.2-6.2 ii libdbus-1-3 1.4.16-1 ii libevent-2.0-52.0.16-stable-1 ii libffi5 3.0.10-3 ii libfontconfig12.8.0-3 ii libfreetype6 2.4.8-1 ii libgcc1 1:4.6.2-11 ii libgdk-pixbuf2.0-02.24.0-2 ii libglib2.0-0 2.30.2-4 ii libgtk2.0-0 2.24.8-2 ii libhunspell-1.3-0 1.3.2-4 ii libjpeg8 8c-2 ii libnspr4-0d 4.8.9-1 ii libnss3-1d3.13.1.with.ckbi.1.88-1 ii libpango1.0-0 1.29.4-2 ii libpixman-1-0 0.24.0-1 ii libsqlite3-0 3.7.9-3 ii libstartup-notification0 0.12-1 ii libstdc++64.6.2-11 ii libvpx0 0.9.7.p1-2 ii libx11-6 2:1.4.4-4 ii libxext6 2:1.3.0-3 ii libxrender1 1:0.9.6-2 ii libxt61:1.1.1-2 ii psmisc22.14-1 ii zlib1g1:1.2.3.4.dfsg-3 Versions of packages icedove recommends: ii hunspell-ar [hunspell-dictionary] 3.1-1 Versions of packages icedove suggests: ii libdbus-glib-1-2 0.98-1 ii libgconf2-4 3.2.3-1 ii libgnomevfs2-01:2.24.4-1 ii libgssapi-krb5-2 1.10+dfsg~beta1-2 ii libnotify40.7.4-1 ii ttf-lyx 2.0.2-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655159: wicd: Error while scanning hidden networks
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2012-01-08 23:00, David Paleino wrote: > I don't think, since I never saw that behaviour before :) me neither :D > > Are you able to manually connect to any of those networks? Is the NULL byte > actually part of the ESSID, i.e. you need to specify it, or is it just a > "placeholder" some access points/wireless cards use? I think it's just a Placeholder... > > What you say about the 4-bytes \x00 ESSID: I guess the network name had > four "normal" characters, and was hidden? How did you connect there? My Friends Network is called "NETZ", and it was hidden, yes... I needed several times to search for the network, but with the wicd-gtk ui it worked after i clicked twice or more often the "connect with hidden network" button. My other Method was to insert the necessary WPA Data into the /etc/wpa_supplicant/wpa_supplicant.conf and started wpa_supplicant by hand and then used dhclient to get an IP Address.. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPChLsAAoJEAhgHfpCPcybyMUH+wfTUSAgumuN3ZatDq6eUolx +/ytpdy8MPkrL0WrPNYaYajpc+RphlTeN3K5lfx4ptR9MsMaooiVMgDEfY0Qoq/x WDZUDtPu8kg8fZzLaY43cECfxgtdUQT98rYpt3Oj8xyYgA2NRUnOcaTKIo5pwa0G 7Cv0nyIJ/lhLJsPRM8Ii6VINsuWWSugaD4FVB8p5Bp/5d9kLacXScyJr3HfWeo5l 4Tb5KdEJ3SHX3i0TJdrKYgwrlT0nONuCsfs5DdriB5aUSZev7UqoDAiZR1CdxtiN rE1xaDc2JpPoQ3RRRNqFHEzaIMeb5WqduzFZDfNYDuLlFzzhTHcZZOXaueP81fk= =nPXD -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655159: wicd: Error while scanning hidden networks
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Let's try to investigate this further, maybe we can overcome the driver bug. > Do > you see \x00 only with hidden networks? Have you ever encountered a non-hidden > network with that NULL byte? I also see Hidden Networks here where the output of wicd is like this: 16 AC:67:06:10:C7:F0 1 I never saw a non-hidden Network with null bytes in there, but i cant confirm that, i can see about 20 Networks from my desk and if i put the laptop to the window i can see about 50, so maybe one of these Nullbyters isnt even hidden... > Are you sure that it the router isn't broadcasting '\x00'? If this latter one > is true, then I fear there won't be space for workarounds :( First i encountered this problem at a friends home network. The Network was hidden and all i could see was \x00\x00\x00\x00. The Network Name was exactly 4 Chars long. The second time was in a German ICE with Wireless, i think there is a internal network or something which is announced 20 times with different MAC Addresses and always called \x00. I think i see always exactly the length of the network SSID with \x00... is that a normal behaviour for AccessPoints? I dont know... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPChEDAAoJEAhgHfpCPcybdQIH/0vAIjgwhbOosnHoKlKKmLFV 4CAssGBWFzTsbhaLGQsI2Fg501bODk4eQfqc73/OzSism5a6EYOjfK2kfG7api2Z v00IzVD44rop05FuRKP0XonOLMv7sWuS3+I71HdnssQCk8EYm7rbGV2MMgEzmmuf 48aLH9FZF4H+JhL9AQPfI+3XK2wFpTK3c9swYYNWyWhkmN92k22On0h0gW7IpdM6 Aib1xnpqVLyMykJlPdsVfK7+BQEjN5L+CzbUblI4Cg8/e/5P4OCCkPzMXnEn/qqL zdHYKE0PN9hUB/NpUABwdPDrw+Y2FtQsBoHM+LScjPLeerQgrbwwu9pRAUC/1CM= =0Afh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#655159: wicd: Error while scanning hidden networks
Package: wicd Version: 1.7.1~b3-3 Severity: normal I now had this problem several times with different Networks, so i think its really a bug in the software rather than a bug with a special network. When i want to scan for networks (wicd-cli --wireless -l) I get this Error Message: # BSSID Channel ESSID Traceback (most recent call last): File "/usr/share/wicd/cli/wicd-cli.py", line 113, in wireless.GetWirelessProperty(network_id, 'essid')) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 143, in __call__ **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Python.TypeError: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 745, in _message_cb _method_reply_return(connection, message, method_name, signature, *retval) File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 252, in _method_reply_return reply.append(signature=signature, *retval) TypeError: expected string without null bytes I think the problem is caused by networks like this one here: Cell 22 - Address: 02:C8:40:35:A0:32 Channel:11 Frequency:2.462 GHz (Channel 11) Quality=21/70 Signal level=-89 dBm Encryption key:on ESSID:"\x00" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s Mode:Master Extra:tsf=0012094097ca Extra: Last beacon: 1960ms ago IE: Unknown: 000100 IE: Unknown: 010482848B96 IE: Unknown: 03010B IE: Unknown: 0706444520010D14 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : CCMP Authentication Suites (1) : PSK Preauthentication Supported Mostly all hidden Networks give their Name as \x00 in length of their name. To restart the wicd or my PC does not have any affect. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wicd-cli depends on: ii wicd-daemon 1.7.1~b3-3 Versions of packages wicd-cli recommends: ii sudo 1.8.3p1-2 wicd-cli suggests no packages. Versions of packages wicd depends on: ii wicd-daemon 1.7.1~b3-3 Versions of packages wicd-gtk depends on: ii python 2.7.2-9 ii python-glade2 2.24.0-2 ii python-gtk22.24.0-2 ii wicd-daemon1.7.1~b3-3 Versions of packages wicd-gtk recommends: ii gksu 2.0.2-6 ii python-notify 0.1.1-3 Versions of packages wicd-daemon depends on: ii adduser 3.113 ii dbus1.4.16-1 ii debconf 1.5.41 ii ethtool 1:3.1-1 ii iproute 2017-1 ii iputils-ping3:20101006-1+b1 ii isc-dhcp-client [dhcp3-client] 4.1.1-P1-17 ii lsb-base3.2-28 ii net-tools 1.60-24.1 ii psmisc 22.14-1 ii python 2.7.2-9 ii python-dbus 0.84.0-2 ii python-gobject 3.0.3-1 ii python-wicd 1.7.1~b3-3 ii wireless-tools 30~pre9-8 ii wpasupplicant 0.7.3-5 wicd-daemon recommends no packages. Versions of packages wicd-daemon suggests: ii pm-utils 1.4.1-8 Versions of packages python-wicd depends on: ii python 2.7.2-9 ii python2.6 2.6.7-4 ii python2.7 2.7.2-9 -- debconf information: * wicd/users: -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wicd depends on: ii wicd-cli [wicd-client] 1.7.1~b3-3 ii wicd-daemon 1.7.1~b3-3 ii wicd-gtk [wicd-client] 1.7.1~b3-3 wicd recommends no packages. wicd suggests no packages. Versions of packages wicd-cli depends on: ii wicd-daemon 1.7.1~b3-3 Versions of packages wicd-cli recommends: ii sudo 1.8.3p1-2 V
Bug#647503: wicd-gtk: Wrong Network Name is shown when connecting to another network
Package: wicd-gtk Version: 1.7.0+ds1-9 Severity: minor I mostly connect to different networks (e.g. my home network, university, another network, ...). I noticed, that when i connect to another network, the old network name is showned while connecting. As example: if i use the network "home" before and then connect to "university", i get the notification: "home: connecting" and then "university: connected". So obviously the old network name is still somewhere saved and used. -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wicd-gtk depends on: ii python 2.7.2-9 ii python-glade2 2.24.0-2 ii python-gtk22.24.0-2 ii wicd-daemon1.7.0+ds1-9 Versions of packages wicd-gtk recommends: ii gksu 2.0.2-6 ii python-notify 0.1.1-3 ii sudo 1.8.3p1-1 wicd-gtk suggests no packages. Versions of packages wicd depends on: ii wicd-daemon 1.7.0+ds1-9 Versions of packages wicd-cli depends on: ii wicd-daemon 1.7.0+ds1-9 Versions of packages wicd-cli recommends: ii sudo 1.8.3p1-1 Versions of packages wicd-daemon depends on: ii adduser 3.113 ii dbus1.4.16-1 ii debconf [debconf-2.0] 1.5.41 ii ethtool 1:3.0-1 ii iproute 20110629-1 ii iputils-ping3:20101006-1+b1 ii isc-dhcp-client [dhcp3-client] 4.1.1-P1-17 ii lsb-base3.2-28 ii net-tools 1.60-24.1 ii psmisc 22.14-1 ii python 2.7.2-9 ii python-dbus 0.84.0-2 ii python-gobject 2.28.6-5 ii python-wicd 1.7.0+ds1-9 ii wireless-tools 30~pre9-6 ii wpasupplicant 0.7.3-5 wicd-daemon recommends no packages. Versions of packages wicd-daemon suggests: ii pm-utils 1.4.1-8 Versions of packages python-wicd depends on: ii python 2.7.2-9 ii python2.6 2.6.7-4 ii python2.7 2.7.2-7 -- debconf information: * wicd/users: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645922: further information
Ah sorry i didnt read the changelog. When i start with --tray it works! BUT: then the response from the tray icon without tray option is wrong. If you click on it the main window should minimize and not create another window. signature.asc Description: This is a digitally signed message part
Bug#645922: wicd-gtk does not start anymore in tray only
Package: wicd-gtk Version: 1.7.0+ds1-7 Severity: normal Since a upgrade of wicd-gtk, the gtk client starts now as window, the tray icon is still visible but a click on it does not minimize the window to the tray, instead it opens up another wicd window. If i close the first spawned window, wicd is exiting. i think this is a bug or a not yet documented feature :) -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wicd-gtk depends on: ii python 2.7.2-9 ii python-glade2 2.24.0-2 ii python-gtk22.24.0-2 ii wicd-daemon1.7.0+ds1-7 Versions of packages wicd-gtk recommends: ii gksu 2.0.2-6 ii python-notify 0.1.1-3 ii sudo 1.8.2-2 wicd-gtk suggests no packages. Versions of packages wicd depends on: ii wicd-daemon 1.7.0+ds1-7 Versions of packages wicd-cli depends on: ii wicd-daemon 1.7.0+ds1-7 Versions of packages wicd-cli recommends: ii sudo 1.8.2-2 Versions of packages wicd-daemon depends on: ii adduser 3.113 ii dbus1.4.16-1 ii debconf [debconf-2.0] 1.5.41 ii iproute 20110629-1 ii iputils-ping3:20101006-1+b1 ii isc-dhcp-client [dhcp3-client] 4.1.1-P1-17 ii lsb-base3.2-28 ii net-tools 1.60-24.1 ii psmisc 22.14-1 ii python 2.7.2-9 ii python-dbus 0.84.0-2 ii python-gobject 2.28.6-5 ii python-wicd 1.7.0+ds1-7 ii wireless-tools 30~pre9-6 ii wpasupplicant 0.7.3-5 wicd-daemon recommends no packages. Versions of packages wicd-daemon suggests: ii pm-utils 1.4.1-8 Versions of packages python-wicd depends on: ii python 2.7.2-9 ii python-support 1.0.14 -- debconf information: * wicd/users: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
