Bug#868290: [virtualbox-dkms] Fails to build kernel module. File hm_vmx.h not found
Package: virtualbox-dkms Version: 5.1.22-dfsg-3 Severity: grave --- Please enter the report below this line. --- At moment of install virtualbox an virtualbox-dkms, compilation of vbox module fails because file /usr/src/virtualbox/-5.1.22/include/VBox/vmm/hm_vmx.h, which is present in version 5.1.18, does not exists. /var/lib/dkms/virtualbox/-5.1.22/build/make.log attached. --- System information. --- Architecture: Kernel: Linux 4.11.0-1-amd64 Debian Release: buster/sid 950 unstablewww.deb-multimedia.org 900 unstable-debug deb.debian.org 900 unstableftp.debian.org 800 experimentalftp.debian.org 500 stable people.debian.org 500 kali-rollinghttp.kali.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. ~$ cat /var/lib/dkms/virtualbox/5.1.22/build/make.log DKMS make.log for virtualbox-5.1.22 for kernel 4.11.0-1-amd64 (x86_64) dv jul 14 10:03:12 CEST 2017 make: se entra en el directorio '/usr/src/linux-headers-4.11.0-1-amd64' LD /var/lib/dkms/virtualbox/5.1.22/build/built-in.o LD /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/built-in.o CC [M] /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/linux/SUPDrv-linux.o CC [M] /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrv.o CC [M] /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrvGip.o CC [M] /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrvSem.o CC [M] /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrvTracer.o CC [M] /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPLibAll.o CC [M] /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/r0drv/alloc-r0drv.o CC [M] /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/r0drv/initterm-r0drv.o /var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrv.c:67:29: fatal error: VBox/vmm/hm_vmx.h: El fitxer o directori no existeix #include ^ compilation terminated. /usr/src/linux-headers-4.11.0-1-common/scripts/Makefile.build:299: fallo en las instrucciones para el objetivo '/var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrv.o' make[4]: *** [/var/lib/dkms/virtualbox/5.1.22/build/vboxdrv/SUPDrv.o] Error 1 make[4]: *** Se espera a que terminen otras tareas /usr/src/linux-headers-4.11.0-1-common/scripts/Makefile.build:558: fallo en las instrucciones para el objetivo '/var/lib/dkms/virtualbox/5.1.22/build/vboxdrv' make[3]: *** [/var/lib/dkms/virtualbox/5.1.22/build/vboxdrv] Error 2 /usr/src/linux-headers-4.11.0-1-common/Makefile:1509: fallo en las instrucciones para el objetivo '_module_/var/lib/dkms/virtualbox/5.1.22/build' make[2]: *** [_module_/var/lib/dkms/virtualbox/5.1.22/build] Error 2 Makefile:152: fallo en las instrucciones para el objetivo 'sub-make' make[1]: *** [sub-make] Error 2 Makefile:8: fallo en las instrucciones para el objetivo 'all' make: *** [all] Error 2 make: se sale del directorio '/usr/src/linux-headers-4.11.0-1-amd64' signature.asc Description: This is a digitally signed message part.
Bug#856948: [kmldonkey] Segfault at start/connect with server
Package: kmldonkey Version: 2.0.5+kde4.3.3-3+b1 --- Please enter the report below this line. --- On my system, Debian Sid up-to-date, I start mldonkey-server with a systemd user service (btw, it does not matter how mldonkey-server starts, kmldonkey keeps crashing even if mldonkey-server is a system service, user service, or started with a script). kmldonkey keeps crashing when it starts if server is running. It crashes too when I start kmldonkey, then start mldonkey-server and try to connect kmldonkey with server. Downgrade to version 2.0.5+kde4.3.3-3 makes kmldonkey work again. It does not matter if I use mldonkey-server from repositories or compiled here from CVS or GIT. Behaviour of kmldonkey is the same. --- System information. --- Architecture: Kernel: Linux 4.9.0-2-amd64 Debian Release: 9.0 950 unstablewww.deb-multimedia.org 900 unstable-debug deb.debian.org 900 unstableftp.debian.org 800 experimentalftp.debian.org 500 stable people.debian.org --- Package information. --- Depends(Version) | Installed -+-=== kde-runtime (>> 4:4.10) | 4:16.08.3-1 libc6 (>= 2.14) | libgcc1 (>= 1:3.0) | libkde3support4 (>= 4:4.3.4) | libkdecore5(>= 4:4.4.95) | libkdeui5 (>= 4:4.3.4) | libkfile4 (>= 4:4.3.4) | libkhtml5 (>= 4:4.3.4) | libkio5 (>= 4:4.3.4) | libkjsapi4 (>= 4:4.3.4) | libknotifyconfig4 (>= 4:4.3.4) | libkparts4 (>= 4:4.3.4) | libnepomuk4 (>= 4:4.3.4) | libnepomukutils4 (>= 4:4.5.85) | libphonon4 (>= 4:4.2.0) | libplasma3 (>= 4:4.4.4-2~) | libqt4-dbus (>= 4:4.5.3) | libqt4-network (>= 4:4.5.3) | libqt4-qt3support (>= 4:4.5.3) | libqt4-svg (>= 4:4.5.3) | libqt4-xml (>= 4:4.5.3) | libqtcore4(>= 4:4.7.0~beta1) | libqtgui4 (>= 4:4.8.0) | libsoprano4 (>= 2.1.1) | libstdc++6 (>= 5.2) | Recommends (Version) | Installed ==-+-=== mldonkey-server| 3.1.5-3+b1 Package's Suggests field is empty. Application: KMLDonkey (kmldonkey), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 ServerInfo::isConnected (this=this@entry=0x0) at ./libkmldonkey/serverinfo.cpp:137 #7 0x7fe3da48b2e2 in DonkeyProtocol::processMessage (this=0x55cfb2c31d30) at ./libkmldonkey/donkeyprotocol.cpp:545 #8 0x7fe3d5841660 in QMetaObject::activate (sender=sender@entry=0x55cfb2c49620, m=m@entry=0x7fe3da6ad280 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3567 #9 0x7fe3da4907bd in DonkeySocket::readyMessage (this=0x55cfb2c49620) at ./obj-x86_64-linux-gnu/libkmldonkey/donkeysocket.moc:107 #10 DonkeySocket::readMessage (this=0x55cfb2c49620) at ./libkmldonkey/donkeysocket.cpp:118 #11 0x7fe3d5841660 in QMetaObject::activate (sender=sender@entry=0x55cfb2c49620, m=m@entry=0x7fe3d5b909c0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3567 #12 0x7fe3d5890840 in QIODevice::readyRead (this=this@entry=0x55cfb2c49620) at .moc/release-shared/moc_qiodevice.cpp:104 #13 0x7fe3d7e9face in QAbstractSocketPrivate::canReadNotification (this=0x55cfb2c31eb0) at socket/qabstractsocket.cpp:654 #14 0x7fe3d7ea904d in QReadNotifier::event (this=, e=) at socket/qnativesocketengine.cpp:1151 #15 0x7fe3d64a954c in QApplicationPrivate::notify_helper (this=this@entry=0x55cfb2b2f4d0, receiver=receiver@entry=0x55cfb2fb70b0, e=e@entry=0x7ffc44edbed0) at kernel/qapplication.cpp:4570 #16 0x7fe3d64b052c in QApplication::notify (this=0x7ffc44edc230, receiver=0x55cfb2fb70b0, e=0x7ffc44edbed0) at kernel/qapplication.cpp:4356 #17 0x7fe3d72281ba in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #18 0x7fe3d582cf1d in QCoreApplication::notifyInternal (this=0x7ffc44edc230, receiver=0x55cfb2fb70b0, event=event@entry=0x7ffc44edbed0) at kernel/qcoreapplication.cpp:955 #19 0x7fe3d585de12 in QCoreApplication::sendEvent (event=0x7ffc44edbed0, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #20 socketNotifierSourceDispatch (source=0x55cfb2b2f370) at kernel/qeventdispatcher_glib.cpp:110 #21 0x7fe3d0bd07f7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7fe3d0bd0a60 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7fe3d0bd0b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7fe3d585d854 in
Bug#849334: [dnscrypt-proxy] dnscrypt-proxy fails to start due to incorrect configuration path on systemd service file
Package: dnscrypt-proxy Version: 1.8.1-3 Severity: serious --- Please enter the report below this line. --- Since last upgrade, Dnscrypt fails to start due search configuration file at path that does not exist. Service file (/lib/systemd/system/dnscrypt-proxy.service) has incorrect path on Exec line: ExecStart=/usr/sbin/dnscrypt-proxy /etc/dnscrypt-proxy/dnscrypt-proxy.conf and, on my system, since last update dnscrypt-proxy.conf is located at /etc/dnscrypt-proxy/dnscrypt-proxy.conf/dnscrypt-proxy.conf Service file after update: [Unit] Description=DNSCrypt client proxy Documentation=man:dnscrypt-proxy(8) Requires=dnscrypt-proxy.socket After=network.target Before=nss-lookup.target [Install] Also=dnscrypt-proxy.socket WantedBy=multi-user.target [Service] Type=notify NonBlocking=true User=_dnscrypt-proxy ExecStart=/usr/sbin/ dnscrypt-proxy /etc/dnscrypt-proxy/dnscrypt-proxy.conf Restart=always ProtectSystem=strict ProtectHome=true ProtectKernelModules=true ProtectKernelTunables=true ProtectControlGroups=true MemoryDenyWriteExecute=true RestrictRealtime=true Directory structure on disk: ~$ tree /etc/dnscrypt-proxy/ /etc/dnscrypt-proxy/└── dnscrypt-proxy.conf └── dnscrypt-proxy.conf Modifying incorrect path on systemd service file or moving config file to path in systemd service file makes dnscrypt work correctly again. --- System information. --- Architecture: Kernel: Linux 4.8.0-2-amd64 Debian Release: stretch/sid 950 unstablewww.deb-multimedia.org 900 unstable-debug deb.debian.org 900 unstableftp.debian.org 800 experimentalftp.debian.org 500 stable people.debian.org --- Package information. --- Depends (Version) | Installed ===-+- adduser | 3.115 lsb-base (>= 3.0-6) | 9.20161125 init-system-helpers (>= 1.18~) | 1.46 libc6 (>= 2.17) | libltdl7 (>= 2.4.6) | libsodium18 (>= 1.0.10) | libsystemd0 | Package's Recommends field is empty. Suggests(Version) | Installed =-+-=== resolvconf| signature.asc Description: This is a digitally signed message part.
Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 No. Precisely, the bug I'm reporting is that the package manager, plasma-discover, does not warn user about his intention to do that removing operation. So, the user never has notice about these changes and as far I know this situation can be considered as grave bug as it can lead to an unusable system. On 24 de setembre de 2016 18:22:16 CEST, Chris Lamb <la...@debian.org> wrote: >Ximo Baldó i Soriano wrote: > >> So... The ongoing Perl migration causes plasma-discover (or its >backend) to >> bypass user's decision to deinstall 347 packages from his system? > >There is no bypassing -- your package manager would have declared its >intention to remove all those packages. > > >Regards, > >-- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk > `- - -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -BEGIN PGP SIGNATURE- iHQEAREKADQtHFhpbW8gQmFsZMOzIGkgU29yaWFubyA8ZXNwaW5kYXJnYUBnbWFp bC5jb20+BQJX5quaAAoJEPLA9MdIi+gmFw0AoKDbA2+UIOSpIFEVbKlpl7xExwIU AJ0QscmFLR8Bp/p8/uhyRkc2SKOrNA== =xm9L -END PGP SIGNATURE-
Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation
El dissabte, 24 de setembre de 2016, a les 15:52:33 CEST, Chris Lamb va escriure: > Hi, > > > [plasma-discover] plasma-discover uninstalls packages during upgrades > > without asking for confirmation > This is due to the ongoing Perl migration. There was a mail sent to > debian-devel-announce but I believe it was unfortunately blocked. > > I'm closing your bug as this is not an issue that can be resolved by > plasma-discover, alas. :( > > > Regards, So... The ongoing Perl migration causes plasma-discover (or its backend) to bypass user's decision to deinstall 347 packages from his system? I Don't think so. If I run apt full-upgrade or aptitude full-upgrade (safe-upgrade makes upgrade packages blocked until it can be upgraded safely, as we know), both of them warn me about operations needed to do that full-upgrade, and, as it should be, ask me if I'm agree to do that or not. I think is a bug (or maybe a wrong default configuration) and not a consecuence of Perl (or some other) migration and, because of this, the bug should not be closed. Feel free to correct me if I'm wrong. signature.asc Description: This is a digitally signed message part.
Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation
Package: plasma-discover Version: 5.7.4-1 Severity: grave --- Please enter the report below this line. --- On my system running debian sid was, since last upgrade, 4 packages related to perl blocked due to dependencies. Tonight, just did an upgrade from plasma- discover and the result was a large number (about 340) of packages been deinstalled without any kind of warning or ask for confirmation, including packages needed for graphical environment like all xorg related packages. --- System information. --- Architecture: amd64 Kernel: Linux 4.7.0-1-amd64 Debian Release: stretch/sid 900 unstableftp.debian.org 800 experimentalftp.debian.org 500 unstable-debug deb.debian.org 500 stable people.debian.org --- Package information. --- Depends (Version) | Installed ==-+- appstream (>= 0.8) | 0.10.1-1 packagekit(>= 1.0) | 1.1.4-1 plasma-discover-common (= 5.7.4-1) | 5.7.4-1 libappstreamqt1| 0.10.1-1 libc6(>= 2.14) | libkf5archive5 (>= 4.96.0) | libkf5attica5 (>= 5.23.0) | libkf5configcore5 (>= 4.98.0) | libkf5configgui5 (>= 4.97.0) | libkf5configwidgets5 (>= 4.96.0) | libkf5coreaddons5 (>= 4.100.0) | libkf5crash5 (>= 5.15.0) | libkf5dbusaddons5 (>= 4.99.0) | libkf5declarative5 (>= 4.96.0) | libkf5i18n5(>= 4.97.0) | libkf5kiocore5 (>= 4.96.0) | libkf5kiowidgets5 (>= 4.96.0) | libkf5newstuff5(>= 5.23.0) | libkf5notifications5 (>= 5.3.0+git20141030.0311) | libkf5service-bin | libkf5service5 (>= 4.96.0) | libkf5widgetsaddons5 (>= 4.96.0) | libkf5xmlgui5 (>= 4.96.0) | libpackagekitqt5-0 | libqt5core5a (>= 5.6.0~beta) | libqt5dbus5(>= 5.4.0~) | libqt5gui5 (>= 5.6.0~beta) | libqt5qml5 (>= 5.1.0) | libqt5quick5(>= 5.0.2) | libqt5widgets5 (>= 5.4.0~) | libqt5xml5 (>= 5.4.0~) | libstdc++6(>= 4.5) | Recommends (Version) | Installed ==-+-=== software-properties-kde| 0.96.20.2-1 Package's Suggests field is empty. signature.asc Description: This is a digitally signed message part.
Bug#795884: [libkf5windowsystem5]
Package: libkf5windowsystem5 Version: 5.13.0-1 --- Please enter the report below this line. --- Please, change version of package with bug (from 5.12.0-1 to 5.13.0-1 which has this bug really) so apt-listbugs can manage it and prevents updates. As far I know, version 5.12.0-1 are no longer available in unstable repositories and reporting against this version makes apt-listbugs ignore it cause package are yet installed. --- System information. --- Architecture: amd64 Kernel: Linux 4.1.0-2-amd64 Debian Release: stretch/sid 950 unstableftp.deb-multimedia.org 900 unstableftp.debian.org 800 experimentalftp.debian.org 500 stable people.debian.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. signature.asc Description: This is a digitally signed message part.
Bug#647159: [plasma-widget-veromix] plasma-widget-veromix: Veromix doesn't work after upgrading python-qt4 to 4.8.6-1
Package: plasma-widget-veromix
Version: 0.13.1-1
--- Please enter the report below this line. ---
Veromix fails to start (as other python-based plasmoids like service-monitor
from kde-look.org), with trace from console:
plasmoidviewer(11663)/plasma main: setting FormFactor to planar
plasmoidviewer(11663)/plasma main: setting Location to floating
plasmoidviewer(11663)/plasma main: setting containment to null
plasmoidviewer(11663)/plasma main: setting auth policy
plasmoidviewer(11663)/libplasma Plasma::Corona::Corona: !!{} STARTUP TIME
30851021 Corona ctor start
plasmoidviewer(11663)/plasma main: just load applet
plasmoidviewer(11663)/plasma FullView::addApplet: adding applet veromix-
plasmoid in null
plasmoidviewer(11663)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying
to open ksycoca from /var/tmp/kdecache-panko/ksycoca4
plasmoidviewer(11663)/kdecore (services)
KServiceFactory::findServiceByDesktopPath: not found
plasmoidviewer(11663)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size
QSizeF(0, 0)
plasmoidviewer(11663)/libplasma Plasma::AppletPrivate::init: Check your
constructor! You probably want to be passing in a Service::Ptr or a
QVariantList with a valid storageid as arg[0].
plasmoidviewer(11663)/libplasma Plasma::PluginLoader::loadApplet: we have a
script using the python API
plasmoidviewer(11663)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size
QSizeF(0, 0)
plasmoidviewer(11663)/python (plugin)
KPythonPluginFactory::KPythonPluginFactory:
KPythonPluginFactory::KPythonPluginFactory()
plasmoidviewer(11663)/python (plugin) KPythonPluginFactory::initialize:
Initializing Python interpreter.
plasmoidviewer(11663)/python (plugin) KPythonPluginFactory::initialize:
Succesfully initialized Python interpreter.
plasmoidviewer(11663)/python (plugin) KPythonPluginFactory::create:
KPythonPluginFactory::create iface: Plasma::AppletScript
plasmoidviewer(11663)/python (plugin) KPythonPluginFactory::create: keyword to
be used for finding the plugin code:
plasma_scriptengine_python/pyappletscript.py
plasmoidviewer(11663)/python (plugin) KPythonPluginFactory::create: Path to
plugin code is:
/usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py
plasmoidviewer(11663)/python (plugin): Failed to import module
Traceback (most recent call last):
File /usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py,
line 22, in module
from PyKDE4.plasma import Plasma
RuntimeError: the PyQt4.QtCore module is version 1 but the PyKDE4.plasma
module requires version -1
plasmoidviewer(11663)/libplasma Plasma::loadEngine: Couldn't load script
engine for language python ! error reported: El servei «Estri en Python»
no proporciona cap interfície «Plasma::AppletScript» amb la paraula clau
«plasma_scriptengine_python/pyappletscript.py»
plasmoidviewer(11663)/libplasma Plasma::ContainmentPrivate::appletAppeared:
127 0
plasmoidviewer(11663)/libplasma Plasma::Corona::popupPosition: 0x8b99510
plasmoidviewer(11663)/plasma FullView::addApplet: connecting
plasmoidviewer(11663)/python (plugin)
KPythonPluginFactory::~KPythonPluginFactory:
KPythonPluginFactory::~KPythonPluginFactory()
The reported error is in Catalán languaje. Translation to english is:
The service 'Estri en Python' does not provide an interface
'Plasma::AppletScript' with keyword
'plasma_scriptengine_python/pyappletscript.py'
(Estri means widget/plasmoid)
--- System information. ---
Architecture: i386
Kernel: Linux 3.0.0-2-686-pae
Debian Release: wheezy/sid
950 unstablewww.debian-multimedia.org
900 unstableftp.debian.org
800 experimentalftp.debian.org
500 sid packages.enlightenment.org
100 experimental-snapshots qt-kde.debian.net
--- Package information. ---
Depends(Version) | Installed
-+-==
python (= 2.6.6-7~) | 2.7.2-9
plasma-scriptengine-python | 4:4.6.5-3
pulseaudio | 1.1-1
python-xdg | 0.19-3
python-qt4-dbus | 4.8.6-1
swh-plugins | 0.4.15+1-6
Package's Recommends field is empty.
Package's Suggests field is empty.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562979: amule: fails to upgrade
Same behavior here, but package fails to install the same way it fails to upgrade. Unpacking amule (from .../amule_2.2.6+debian0-1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/amule_2.2.6+debian0-1_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Processing triggers for menu ... Errors were encountered while processing: /var/cache/apt/archives/amule_2.2.6+debian0-1_i386.deb Same error too in package amule-utils_2.2.6+debian0-1_i386.deb but package amule-common_2.2.6+debian0-1_i386.deb install/upgrade correctly (think is relevant information, don't know)1 Debian Sid kernel 2.6.32-trunk-686 (2.6.32-3) Arch.: i386 (i686) /etc/apt/preferences: Package: * Pin: release a=unstable Pin-Priority: 900 Package: * Pin: release a=experimental Pin-Priority: 800 Locale: LANG=ca_ES.UTF-8 LC_CTYPE=ca_ES.UTF-8 /bin/sh -- /bin/bash -- Este missatge, i tota la informació adjunta, és confidencial i està protegit per la llei. No ha de copiar, reexpedir i / o revelar este missatge, total o parcialment, cense autorització de l'emissor. Si vosté no és un dels destinataris assenyalats, per favor informe l'emissor, i esborre i destruïsca l'original i totes les còpies del missatge. Abans d'imprimir aquest missatge, assegura't que cal fer-ho. Protegeix el medi ambient! signature.asc Description: This is a digitally signed message part.
