Bug#1030926: libvirt-daemon-system: Wrong AppArmor definition for /usr/bin/qemu-system-i386
Package: libvirt-daemon-system
Version: 9.0.0-1
Severity: normal
X-Debbugs-Cc: malahee...@gmx.fr
Dear maintainer,
/usr/bin/qemu-system-i386 is included in /etc/apparmor.d/abstractions/libvirt-
qemu. But because it is just a wrapper, the real binary is /usr/libexec/qemu-
system-i386. Once you are trying to run an i386 VM, libvirt report "internal
error: process exited while connecting to monitor: /usr/bin/qemu-system-i386:
29: exec: /usr/libexec/qemu-system-i386: Permission denied".
The obvious solution is to add this binary to "abstractions" and reload
apparmor.
Not sure if it as an upstream bug or related to Debian package. We didn't use
this i386 machine for a while, it worked previously...
dmesg:
[ 926.819853] audit: type=1400 audit(1675940937.111:42): apparmor="DENIED"
operation="exec" profile="libvirt-e66e81f4-a0de-417a-b8f7-6d699f1108e7"
name="/usr/libexec/qemu-system-i386" pid=5543 comm="qemu-system-i38"
requested_mask="x" denied_mask="x" fsuid=64055 ouid=0
libvirtd.log:
2023-02-09 11:08:57.016+: starting up libvirt version: 9.0.0, package: 1
(Andrea Bolognani Sat, 28 Jan 2023 17:03:53 +0100), qemu
version: 7.2.0Debian 1:7.2+dfsg-2, kernel: 6.1.0-3-amd64, hostname: big-
pc.home.
ca
LC_ALL=C \
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin \
HOME=/var/lib/libvirt/qemu/domain-3-2k.windows.malaheene \
XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-3-2k.windows.malaheene/.local/share
\
XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-3-2k.windows.malaheene/.cache \
XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-3-2k.windows.malaheene/.config \
/usr/bin/qemu-system-i386 \
-name guest=2k.windows.malaheenee.ca,debug-threads=on \
-S \
-object '{"qom-
type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-3-2k.windows.malaheene/master-
key.aes"}' \
-machine pc-i440fx-1.4,usb=off,vmport=off,dump-guest-core=off,memory-
backend=pc.ram \
-accel kvm \
-cpu pentium3,hv-time=on,hv-relaxed=on,hv-vapic=on,hv-spinlocks=0x1fff \
-m 256 \
-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":268435456}' \
-overcommit mem-lock=off \
-smp 1,sockets=1,cores=1,threads=1 \
-uuid e66e81f4-a0de-417a-b8f7-6d699f1108e7 \
-no-user-config \
-nodefaults \
-chardev socket,id=charmonitor,fd=31,server=on,wait=off \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime,driftfix=slew \
-global kvm-pit.lost_tick_policy=delay \
-no-hpet \
-no-shutdown \
-global PIIX4_PM.disable_s3=1 \
-global PIIX4_PM.disable_s4=1 \
-boot strict=on \
-device '{"driver":"pci-ohci","id":"usb","bus":"pci.0","addr":"0x3"}' \
-device '{"driver":"virtio-serial-pci","id":"virtio-
serial0","bus":"pci.0","addr":"0x7"}' \
-global isa-fdc.bootindexA=1 \
-blockdev
'{"driver":"file","filename":"/home/libvirt/pool/2k.windows.qcow2","aio":"native","node-
name":"libvirt-3-storage","cache":{"direct":true,"no-flush":false},"auto-read-
only":true,"discard":"unmap"}' \
-blockdev '{"node-name":"libvirt-3-format","read-
only":false,"cache":{"direct":true,"no-
flush":false},"driver":"qcow2","file":"libvirt-3-storage","backing":null}' \
-device '{"driver":"ide-
hd","bus":"ide.0","unit":0,"drive":"libvirt-3-format","id":"ide0-0-0","bootindex":3,"write-
cache":"on"}' \
-device '{"driver":"ide-
cd","bus":"ide.1","unit":0,"id":"ide0-1-0","bootindex":2}' \
-device '{"driver":"floppy","unit":0,"id":"fdc0-0-0"}' \
-netdev '{"type":"tap","fd":"32","id":"hostnet0"}' \
-device
'{"driver":"rtl8139","netdev":"hostnet0","id":"net0","mac":"52:54:00:10:06:02","bus":"pci.0","addr":"0x5"}'
\
-chardev spicevmc,id=charchannel0,name=vdagent \
-device '{"driver":"virtserialport","bus":"virtio-
serial0.0","nr":1,"chardev":"charchannel0","id":"channel0","name":"com.redhat.spice.0"}'
\
-device '{"driver":"usb-tablet","id":"input2","bus":"usb.0","port":"1"}' \
-audiodev '{"id":"audio1","driver":"spice"}' \
-spice port=5900,addr=127.0.0.1,disable-ticketing=on,image-
compression=off,seamless-migration=on \
-k en-us \
-device '{"driver":"cirrus-vga","id":"video0","bus":"pci.0","addr":"0x4"}' \
-device
'{"driver":"AC97","id":"sound0","audiodev":"audio1","bus":"pci.0","addr":"0x6"}'
\
-chardev spicevmc,id=charredir0,name=usbredir \
-device '{"driver":"usb-
redir","chardev":"charredir0","id":"redir0","bus":"usb.0","port":"2"}' \
-chardev spicevmc,id=charredir1,name=usbredir \
-device '{"driver":"usb-
redir","chardev":"charredir1","id":"redir1","bus":"usb.0","port":"3"}' \
-device '{"driver":"virtio-balloon-
pci","id":"balloon0","bus":"pci.0","addr":"0x8"}' \
-sandbox
on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2023-02-09 11:08:57.016+: Domain id=3 is tainted: deprecated-config
(machine type 'pc-i440fx-1.4')
/usr/bin/qemu-system-i386: 29: exec: /usr/libexec/qemu-system-i386: Permission
denied
2023-02-09 11:08:57.152+: shutting down, reason=failed
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500,
[Pkg-utopia-maintainers] Bug#1006332: firewalld: Impossible to use outbound policies
Package: firewalld Severity: important Tags: patch upstream X-Debbugs-Cc: malahee...@gmx.fr Dear Maintainer, In the current version of firewalld it is impossible to use outbound policy. If such policy uses a service or port based on tcp/udp, connection is not established. Reported and fixed in upstream (version 0.9.5). Upstream issue: https://github.com/firewalld/firewalld/issues/705 Patch: https://github.com/firewalld/firewalld/commit/72aa112a314bc8c74679e357242c9187a3efe719 Will it be possible to fix it in Bullseye ? Thank you! -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-11-amd64 (SMP w/2 CPU threads) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firewalld depends on: ii dbus 1.12.20-2 ii gir1.2-glib-2.0 1.66.1-1+b1 pn gir1.2-nm-1.0 pn iptables ii policykit-1 0.105-31+deb11u1 ii python3 3.9.2-3 pn python3-dbus pn python3-firewall ii python3-gi3.38.0-2 pn python3-nftables Versions of packages firewalld recommends: pn ipset ___ Pkg-utopia-maintainers mailing list Pkg-utopia-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
Bug#1006332: firewalld: Impossible to use outbound policies
Package: firewalld Severity: important Tags: patch upstream X-Debbugs-Cc: malahee...@gmx.fr Dear Maintainer, In the current version of firewalld it is impossible to use outbound policy. If such policy uses a service or port based on tcp/udp, connection is not established. Reported and fixed in upstream (version 0.9.5). Upstream issue: https://github.com/firewalld/firewalld/issues/705 Patch: https://github.com/firewalld/firewalld/commit/72aa112a314bc8c74679e357242c9187a3efe719 Will it be possible to fix it in Bullseye ? Thank you! -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-11-amd64 (SMP w/2 CPU threads) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firewalld depends on: ii dbus 1.12.20-2 ii gir1.2-glib-2.0 1.66.1-1+b1 pn gir1.2-nm-1.0 pn iptables ii policykit-1 0.105-31+deb11u1 ii python3 3.9.2-3 pn python3-dbus pn python3-firewall ii python3-gi3.38.0-2 pn python3-nftables Versions of packages firewalld recommends: pn ipset
Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring
Hello Simon, Thank you for your efforts! > Do you have the dbus-user-session package installed? I had to install it. Indeed, it helps - now gnome-keyring is working fine with latest package version of libglib. > If you rely on the ability to have a separate D-Bus session bus per > X11 display for the same uid, then you can't use dbus-user-session > permanently, because it represents a different model where each uid has > only one instance of the D-Bus session bus. For my "testing" setup it is ok. But I'm asking myself - is it only gnome-keyring affected or this "security hardening" could break other GNOME/MATE parts? dbus-x11 is a strict dependency of mate-session-manager/gnome-session-bin, while dbus-user-session is not even suggested... -- Best Regards, Charles Malaheenee
Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring
Hello Simon, Thank you for your efforts! > Do you have the dbus-user-session package installed? I had to install it. Indeed, it helps - now gnome-keyring is working fine with latest package version of libglib. > If you rely on the ability to have a separate D-Bus session bus per > X11 display for the same uid, then you can't use dbus-user-session > permanently, because it represents a different model where each uid has > only one instance of the D-Bus session bus. For my "testing" setup it is ok. But I'm asking myself - is it only gnome-keyring affected or this "security hardening" could break other GNOME/MATE parts? dbus-x11 is a strict dependency of mate-session-manager/gnome-session-bin, while dbus-user-session is not even suggested... -- Best Regards, Charles Malaheenee
Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring
Hello Simon, Thank you for the attention to this bug! Our DE is Mate. Probably, the problem is related to the mix of components ? Here is the output (I do not remember to have to change the permissions of gnome-keyring-daemon): ls -l /usr/bin/gnome-keyring-daemon -rwxr-xr-x 1 root root 1143712 Mar 11 2020 /usr/bin/gnome-keyring-daemon getcap /usr/bin/gnome-keyring-daemon /usr/bin/gnome-keyring-daemon cap_ipc_lock=ep In journalctl there are a lot messages from systemd or dbus-daemon, like "dbus-daemon[970]: [session uid=1000 pid=968] Successfully activated service 'org.mate.panel.applet.ClockAppletFactory'" or "systemd[902]: Started Sound Service." Concerning gnome-keyring-daemon, here is the output of journalctl for all possible package versions: (version 2.66.4-3, bug appears) Jan 30 14:26:13 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid Jan 30 14:26:13 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: The SSH agent was already initialized Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: The PKCS#11 component was already initialized Jan 30 14:26:39 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid (version 2.66.4-1, no bug) Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The Secret Service was already initialized Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The SSH agent was already initialized Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The PKCS#11 component was already initialized (version 2.66.4-3+revert981420targeted, no bug) Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: GLib-GIO: Not suppressing use of DBUS_SESSION_BUS_ADDRESS because not setuid, even though AT_SECURE Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The Secret Service was already initialized Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The SSH agent was already initialized Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The PKCS#11 component was already initialized (version 2.66.4-3+revert981420dbus, no bug) Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The Secret Service was already initialized Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The SSH agent was already initialized Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The PKCS#11 component was already initialized (version 2.66.4-3+revert981420dbus, no bug) Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The Secret Service was already initialized Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The SSH agent was already initialized Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The PKCS#11 component was already initialized Hope this helps. -- Best Regards, Charles Malaheenee
Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring
Hello Simon, Thank you for the attention to this bug! Our DE is Mate. Probably, the problem is related to the mix of components ? Here is the output (I do not remember to have to change the permissions of gnome-keyring-daemon): ls -l /usr/bin/gnome-keyring-daemon -rwxr-xr-x 1 root root 1143712 Mar 11 2020 /usr/bin/gnome-keyring-daemon getcap /usr/bin/gnome-keyring-daemon /usr/bin/gnome-keyring-daemon cap_ipc_lock=ep In journalctl there are a lot messages from systemd or dbus-daemon, like "dbus-daemon[970]: [session uid=1000 pid=968] Successfully activated service 'org.mate.panel.applet.ClockAppletFactory'" or "systemd[902]: Started Sound Service." Concerning gnome-keyring-daemon, here is the output of journalctl for all possible package versions: (version 2.66.4-3, bug appears) Jan 30 14:26:13 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid Jan 30 14:26:13 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: The SSH agent was already initialized Jan 30 14:26:14 big-pc gnome-keyring-daemon[920]: The PKCS#11 component was already initialized Jan 30 14:26:39 big-pc gnome-keyring-daemon[920]: couldn't connect to dbus session bus: Cannot spawn a message bus when setuid (version 2.66.4-1, no bug) Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The Secret Service was already initialized Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The SSH agent was already initialized Jan 31 18:13:23 big-pc gnome-keyring-daemon[2054]: The PKCS#11 component was already initialized (version 2.66.4-3+revert981420targeted, no bug) Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: GLib-GIO: Not suppressing use of DBUS_SESSION_BUS_ADDRESS because not setuid, even though AT_SECURE Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The Secret Service was already initialized Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The SSH agent was already initialized Jan 31 18:31:57 big-pc gnome-keyring-daemon[924]: The PKCS#11 component was already initialized (version 2.66.4-3+revert981420dbus, no bug) Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The Secret Service was already initialized Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The SSH agent was already initialized Jan 31 18:36:50 big-pc gnome-keyring-daemon[920]: The PKCS#11 component was already initialized (version 2.66.4-3+revert981420dbus, no bug) Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The Secret Service was already initialized Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The SSH agent was already initialized Jan 31 18:39:09 big-pc gnome-keyring-daemon[905]: The PKCS#11 component was already initialized Hope this helps. -- Best Regards, Charles Malaheenee
Bug#981420: libglib2.0-0: gnome-keyring unable to unlock login keyring
Package: libglib2.0-0 Version: 2.66.4-1 Severity: important Tags: upstream X-Debbugs-Cc: malahee...@gmx.fr Dear maintainer, After the recent update of libglib2.0 to 2.66.4-3, gnome-keyring is not able to unlock "Login" keyring. For example, it does not allow to unlock saved ssh keys automatically; ssh/ssh-agent starts to ask for a password in CLI instead of fancy popup window. The downgrading to 2.66.4-1 solves the problem. Could you take a look? Thank you! -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libglib2.0-0 depends on: ii libc62.31-9 ii libffi7 3.3-5 ii libmount12.36.1-6 ii libpcre3 2:8.39-13 ii libselinux1 3.1-2+b2 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages libglib2.0-0 recommends: hi libglib2.0-data 2.66.4-1 ii shared-mime-info 2.0-1 ii xdg-user-dirs 0.17-2 libglib2.0-0 suggests no packages. -- no debconf information
Bug#978131: Fw: Re: Bug#978131: qemu-system-x86: Segfault when starting a VM
Hello Michael, Indeed, no issues with installed qemu-system-gui. Thank you for pointing out. Sorry to bother you. -- Best Regards, Charles Malaheenee
Bug#978131: qemu-system-x86: Segfault when starting a VM
Hello Michael, Well, my hardware is pretty old (Core2Quad Q9400, G35, 8GB of RAM) but it is still doing whatever I need. Please, find attached log for testing with different configurations. The VM fails to boot with SPICE devices connected (console and graphics). -- Best Regards, Charles Malaheenee board.log Description: Binary data
Bug#978131: qemu-system-x86: Segfault when starting a VM
Package: qemu-system-x86 Version: 1:5.2+dfsg-2 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: malahee...@gmx.fr Dear Maintainer, Not sure is it related with qemu itself, but suddenly a launch of a VM through libvirt fails with a standard error message: virsh # start board.debian.malaheenee.ca error: Failed to start domain board.debian.malaheenee.ca error: internal error: qemu unexpectedly closed the monitor The syslog has a "segfault" message: Dec 26 06:57:45 big-pc kernel: [ 564.377369] qemu-system-x86[2278]: segfault at 28 ip 55e80f667dfc sp 7ffeb92c06e0 error 6 in qemu- system-x86_64[55e80f476000+4df000] Dec 26 06:57:45 big-pc kernel: [ 564.377382] Code: 00 48 8d 3d 7e 50 31 00 48 8b 08 31 c0 e8 cc bc ff ff 4c 8b 2d 15 ec 71 00 e9 42 ff ff ff 48 8d 3d 92 26 45 00 e8 c4 bb ff ff 40 28 01 00 00 00 e9 73 fc ff ff 48 8d 35 19 bb 3b 00 48 8d 3d Initially I thought it is because of the kernel, because last week it worked (that's why the kernel is 5.9.0-4-amd64). I can do more test if needed. Best regards, Charles -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qemu-system-x86 depends on: ii ipxe-qemu 1.0.0+git-20190125.36a4c85-5 ii libaio1 0.3.112-9 ii libc6 2.31-6 ii libcapstone4 4.0.2-3 ii libfdt1 1.6.0-1 ii libgcc-s1 10.2.1-3 ii libglib2.0-0 2.66.4-1 ii libgnutls30 3.7.0-3 ii libibverbs1 32.0-1+b1 ii libjpeg62-turbo 1:2.0.5-1.1 ii libnettle83.6-2 ii libnuma1 2.0.12-1+b1 ii libpixman-1-0 0.40.0-1 ii libpmem1 1.10-1 ii libpng16-16 1.6.37-3 ii librdmacm132.0-1+b1 ii libsasl2-22.1.27+dfsg-2 ii libseccomp2 2.5.1-1 ii libslirp0 4.4.0-1 ii libudev1 247.2-2 ii liburing1 0.7-3 ii libusb-1.0-0 2:1.0.24-2 ii libvdeplug2 4.0.1-2 ii libxendevicemodel14.14.0+88-g1d1d1f5391-2 ii libxenevtchn1 4.14.0+88-g1d1d1f5391-2 ii libxenforeignmemory1 4.14.0+88-g1d1d1f5391-2 ii libxengnttab1 4.14.0+88-g1d1d1f5391-2 ii libxenmisc4.144.14.0+88-g1d1d1f5391-2 ii libxenstore3.04.14.0+88-g1d1d1f5391-2 ii libxentoolcore1 4.14.0+88-g1d1d1f5391-2 ii qemu-system-common1:5.2+dfsg-2 ii qemu-system-data 1:5.2+dfsg-2 ii seabios 1.14.0-2 ii zlib1g1:1.2.11.dfsg-2 Versions of packages qemu-system-x86 recommends: pn ovmf pn qemu-system-gui ii qemu-utils 1:5.2+dfsg-2 Versions of packages qemu-system-x86 suggests: pn qemu-block-extra ii qemu-system-data [sgabios] 1:5.2+dfsg-2 ii samba 2:4.13.3+dfsg-1 pn vde2 -- no debconf information
Bug#978131: qemu-system-x86: Segfault when starting a VM
Package: qemu-system-x86 Version: 1:5.2+dfsg-2 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: malahee...@gmx.fr Dear Maintainer, Not sure is it related with qemu itself, but suddenly a launch of a VM through libvirt fails with a standard error message: virsh # start board.debian.malaheenee.ca error: Failed to start domain board.debian.malaheenee.ca error: internal error: qemu unexpectedly closed the monitor The syslog has a "segfault" message: Dec 26 06:57:45 big-pc kernel: [ 564.377369] qemu-system-x86[2278]: segfault at 28 ip 55e80f667dfc sp 7ffeb92c06e0 error 6 in qemu- system-x86_64[55e80f476000+4df000] Dec 26 06:57:45 big-pc kernel: [ 564.377382] Code: 00 48 8d 3d 7e 50 31 00 48 8b 08 31 c0 e8 cc bc ff ff 4c 8b 2d 15 ec 71 00 e9 42 ff ff ff 48 8d 3d 92 26 45 00 e8 c4 bb ff ff 40 28 01 00 00 00 e9 73 fc ff ff 48 8d 35 19 bb 3b 00 48 8d 3d Initially I thought it is because of the kernel, because last week it worked (that's why the kernel is 5.9.0-4-amd64). I can do more test if needed. Best regards, Charles -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qemu-system-x86 depends on: ii ipxe-qemu 1.0.0+git-20190125.36a4c85-5 ii libaio1 0.3.112-9 ii libc6 2.31-6 ii libcapstone4 4.0.2-3 ii libfdt1 1.6.0-1 ii libgcc-s1 10.2.1-3 ii libglib2.0-0 2.66.4-1 ii libgnutls30 3.7.0-3 ii libibverbs1 32.0-1+b1 ii libjpeg62-turbo 1:2.0.5-1.1 ii libnettle83.6-2 ii libnuma1 2.0.12-1+b1 ii libpixman-1-0 0.40.0-1 ii libpmem1 1.10-1 ii libpng16-16 1.6.37-3 ii librdmacm132.0-1+b1 ii libsasl2-22.1.27+dfsg-2 ii libseccomp2 2.5.1-1 ii libslirp0 4.4.0-1 ii libudev1 247.2-2 ii liburing1 0.7-3 ii libusb-1.0-0 2:1.0.24-2 ii libvdeplug2 4.0.1-2 ii libxendevicemodel14.14.0+88-g1d1d1f5391-2 ii libxenevtchn1 4.14.0+88-g1d1d1f5391-2 ii libxenforeignmemory1 4.14.0+88-g1d1d1f5391-2 ii libxengnttab1 4.14.0+88-g1d1d1f5391-2 ii libxenmisc4.144.14.0+88-g1d1d1f5391-2 ii libxenstore3.04.14.0+88-g1d1d1f5391-2 ii libxentoolcore1 4.14.0+88-g1d1d1f5391-2 ii qemu-system-common1:5.2+dfsg-2 ii qemu-system-data 1:5.2+dfsg-2 ii seabios 1.14.0-2 ii zlib1g1:1.2.11.dfsg-2 Versions of packages qemu-system-x86 recommends: pn ovmf pn qemu-system-gui ii qemu-utils 1:5.2+dfsg-2 Versions of packages qemu-system-x86 suggests: pn qemu-block-extra ii qemu-system-data [sgabios] 1:5.2+dfsg-2 ii samba 2:4.13.3+dfsg-1 pn vde2 -- no debconf information
Bug#916594: webext-umatrix: Can not load configuration from backup
Package: webext-umatrix Version: 1.3.14+dfsg-2 Severity: important Dear Maintainer, With freshly installed extension, it can not restore a backup from file. After the message "...uMatrix will restart" the extension is silently dies with no error message. In the Browser Console it shows: TypeError: dmp.diff_cleanupSemantic is not a function[Learn More] merge.js:553:5 getDiff moz- extension://f08d0589-c2c1-4748-8fd1-d0509d6a1cb5/lib/codemirror/addon/merge/merge.js:553:5 init moz- extension://f08d0589-c2c1-4748-8fd1-d0509d6a1cb5/lib/codemirror/addon/merge/merge.js:44:19 CodeMirror.MergeView moz- extension://f08d0589-c2c1-4748-8fd1-d0509d6a1cb5/lib/codemirror/addon/merge/merge.js:474:15 moz- extension://f08d0589-c2c1-4748-8fd1-d0509d6a1cb5/js/user-rules.js:70:17 moz- extension://f08d0589-c2c1-4748-8fd1-d0509d6a1cb5/js/user-rules.js:28:2 The backup file has been created from the same version, but installed from Mozilla Addons. Best regards, Charles Malaheenee -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-2-amd64 (SMP w/4 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 webext-umatrix depends on: ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-1 ii fonts-roboto-hinted 2:0~20160106-2 ii libjs-codemirror 5.19.0-1 ii libjs-punycode 1.3.2-2 ii publicsuffix 20181108.2228-1 Versions of packages webext-umatrix recommends: ii firefox-esr 60.4.0esr-1 webext-umatrix suggests no packages. -- no debconf information
[Pkg-mozext-maintainers] Bug#916594: webext-umatrix: Can not load configuration from backup
Package: webext-umatrix Version: 1.3.14+dfsg-2 Severity: important Dear Maintainer, With freshly installed extension, it can not restore a backup from file. After the message "...uMatrix will restart" the extension is silently dies with no error message. In the Browser Console it shows: TypeError: dmp.diff_cleanupSemantic is not a function[Learn More] merge.js:553:5 getDiff moz- extension://f08d0589-c2c1-4748-8fd1-d0509d6a1cb5/lib/codemirror/addon/merge/merge.js:553:5 init moz- extension://f08d0589-c2c1-4748-8fd1-d0509d6a1cb5/lib/codemirror/addon/merge/merge.js:44:19 CodeMirror.MergeView moz- extension://f08d0589-c2c1-4748-8fd1-d0509d6a1cb5/lib/codemirror/addon/merge/merge.js:474:15 moz- extension://f08d0589-c2c1-4748-8fd1-d0509d6a1cb5/js/user-rules.js:70:17 moz- extension://f08d0589-c2c1-4748-8fd1-d0509d6a1cb5/js/user-rules.js:28:2 The backup file has been created from the same version, but installed from Mozilla Addons. Best regards, Charles Malaheenee -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-2-amd64 (SMP w/4 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 webext-umatrix depends on: ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-1 ii fonts-roboto-hinted 2:0~20160106-2 ii libjs-codemirror 5.19.0-1 ii libjs-punycode 1.3.2-2 ii publicsuffix 20181108.2228-1 Versions of packages webext-umatrix recommends: ii firefox-esr 60.4.0esr-1 webext-umatrix suggests no packages. -- no debconf information ___ Pkg-mozext-maintainers mailing list Pkg-mozext-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-mozext-maintainers
Bug#916593: webext-umatrix: Add Chromium support
Package: webext-umatrix Version: 1.3.14+dfsg-2 Severity: wishlist Dear Maintainer, We suggest to add support for Chromium browser as for webext-ublock-origin (another extension of the same author). Best regards, Charles Malaheenee -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-2-amd64 (SMP w/4 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 webext-umatrix depends on: ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-1 ii fonts-roboto-hinted 2:0~20160106-2 ii libjs-codemirror 5.19.0-1 ii libjs-punycode 1.3.2-2 ii publicsuffix 20181108.2228-1 Versions of packages webext-umatrix recommends: ii firefox-esr 60.4.0esr-1 webext-umatrix suggests no packages. -- no debconf information
[Pkg-mozext-maintainers] Bug#916593: webext-umatrix: Add Chromium support
Package: webext-umatrix Version: 1.3.14+dfsg-2 Severity: wishlist Dear Maintainer, We suggest to add support for Chromium browser as for webext-ublock-origin (another extension of the same author). Best regards, Charles Malaheenee -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-2-amd64 (SMP w/4 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 webext-umatrix depends on: ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-1 ii fonts-roboto-hinted 2:0~20160106-2 ii libjs-codemirror 5.19.0-1 ii libjs-punycode 1.3.2-2 ii publicsuffix 20181108.2228-1 Versions of packages webext-umatrix recommends: ii firefox-esr 60.4.0esr-1 webext-umatrix suggests no packages. -- no debconf information ___ Pkg-mozext-maintainers mailing list Pkg-mozext-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-mozext-maintainers
Bug#916279: qemu-system-common
Hello! Just for diversity - English text :) dpkg: error processing archive /tmp/apt-dpkg-install-3L8qhF/00-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc-base/qemu-system-doc', which is also in package qemu-system-data 1:2.12+dfsg-3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-3L8qhF/00-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) As temporary solution - rollback to 2.12. -- Best Regards, Charles Malaheenee
Bug#916279: qemu-system-common
Hello! Just for diversity - English text :) dpkg: error processing archive /tmp/apt-dpkg-install-3L8qhF/00-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb (--unpack): trying to overwrite '/usr/share/doc-base/qemu-system-doc', which is also in package qemu-system-data 1:2.12+dfsg-3 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /tmp/apt-dpkg-install-3L8qhF/00-qemu-system-common_1%3a3.1+dfsg-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) As temporary solution - rollback to 2.12. -- Best Regards, Charles Malaheenee
Bug#904256: webext-ublock-origin: Add /etc/chromium.d/ublock-origin
Package: webext-ublock-origin
Version: 1.16.6+dfsg-1.1
Severity: normal
Tags: upstream
Dear Maintainer,
We propose to add a file "/etc/chromium.d/ublock-origin" from old chromium-
ublock-origin package to make this new one usable out-of-th-box with Chromium
too.
Probably, it is better to create this file with post-install script if Chromium
is installed.
The file contents:
#!/bin/sh
export CHROMIUM_FLAGS="${CHROMIUM_FLAGS} --load-
extension=/usr/share/chromium/extensions/ublock-origin"
Best regards,
Charles Malaheenee
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500,
'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.17.0-1-amd64 (SMP w/4 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 webext-ublock-origin depends on:
ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-1
Versions of packages webext-ublock-origin recommends:
ii chromium 67.0.3396.87-1
ii firefox-esr 52.9.0esr-1
webext-ublock-origin suggests no packages.
-- no debconf information
Bug#872983: Do not depend on openbox-menu
As temporary solution just 'hold' the old package with apt-mark. Dear maintainer, why we are need to have something in our systems that we do not use? Debian is a construction set, not bundle :) -- Best Regards, Charles Malaheenee
Bug#852302: ipxe-qemu: Crash with QEMU newer than 2.6
H-m, after last update of Qemu (1:2.8+dfsg-3) suddenly it works. We'll keep an eye on it. -- Best Regards, Charles Malaheenee
Bug#852302: ipxe-qemu: Crash with QEMU newer than 2.6
Sorry Bastian, we don't understand your logic. You have the confirmed bug, but you can't reproduce it. What you propose? Buy a new hardware? Use an old version of QEMU? Or build ipxe ourselves? -- Best Regards, Charles Malaheenee
Bug#852302: ipxe-qemu: Crash with QEMU newer than 2.6
We have qemu 2.8 (1:2.8+dfsg-1) and ipxe-qemu (1.0.0+git-20161027.b991c67-1) With this versions, we attempt to run virt-install with pxe option and got a messages in logs like this: 2017-01-23 11:45:17.987+: starting up libvirt version: 2.5.0, package: 3 (Guido Günther <a...@sigxcpu.org> Fri, 23 Dec 2016 16:18:12 +0100), qemu version: 2.8.0(Debian 1:2.8+dfsg-1), hostname: big-pc.home LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin QEMU_AUDIO_DRV=none /usr/bin/qemu-system-x86_64 -name guest=git.debian.decelles.ca,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-git.debian.decelles./master-key.aes -machine pc-i440fx-2.8,accel=kvm,usb=off,dump-guest-core=off -cpu core2duo,-vmx -m 512 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 03a68d52-2249-4c61-b1f1-0a5b666f6317 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-git.debian.decelles./monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-reboot -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/home/libvirt/pool/git.debian.qcow2,format=qcow2,if=none,id=drive-virtio-disk 0 -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=2 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:10:01:13,bus=pci.0,addr=0x2,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-3-git.debian.decelles./org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on char device redirected to /dev/pts/3 (label charserial0) KVM internal error. Suberror: 1 emulation failure EAX=e010 EBX=00a0 ECX=2e70 EDX=000a38b8 ESI=1ffa2fe0 EDI=1fed EBP= ESP=7b92 EIP=06a1 EFL=0087 [--S--PC] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 00c09300 CS =9c48 0009c480 00809b00 SS = 00809300 DS =9ccc 0009ccc0 00c09300 FS = 00c09300 GS = 00c09300 LDT= 8200 TR = 8b00 GDT= IDT= 03ff CR0=0010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=00 16 66 9c 66 60 0f a8 0f a0 06 1e 16 0e fa 2e 8e 1e 86 06 <0f> ae 06 20 1d 0f 01 0e 16 1d 0f 01 06 10 1d fc 66 b9 38 00 00 00 66 ba 10 02 00 00 66 68 2017-01-23T11:45:30.186063Z qemu-system-x86_64: terminating on signal 15 from pid 483 (/usr/sbin/libvirtd) 2017-01-23 11:45:30.386+: shutting down, reason=destroyed So, It may be fixed with newest ipxe, not only with qemu itself. -- Best Regards, Charles Malaheenee
Bug#852302: ipxe-qemu: Crash with QEMU newer than 2.6
Package: ipxe-qemu Version: 1.0.0+git-20161027.b991c67-1 Severity: normal Tags: upstream Dear Maintainer, It's not possible to PXE boot in QEMU at all. When we choose --pxe option in virt-install (or virt-manager), the machine moves to a paused state immediately after the 'starting PXE rom execution...' message appears. More information can be found here: https://bugs.launchpad.net/qemu/+bug/1623276/ As mentioned at the link above, build a new version from git (http://lists.ipxe.org/pipermail/ipxe-devel/2016-November/005244.html) solves the problem. Best regards, Malaheenee -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- debconf-show failed
Bug#833645: libteam-utils: Missing dbus rules
Ooops! A typo in steps to reproduce. Instead of 'con del' it should read 'con down'. Sorry. -- Best Regards, Charles Malaheenee
Bug#833645: libteam-utils: Missing dbus rules
We suggest to add rules in ‘/etc/dbus-1/system.d/teamd.conf’.
The text of error message is :
Aug 27 06:24:03 deb-build NetworkManager[2920]: [1472293443.3106]
device (team0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Aug 27 06:24:03 deb-build NetworkManager[2920]: [1472293443.3497]
device (team0): Activation: (team) started teamd [pid 3433]...
Aug 27 06:24:03 deb-build NetworkManager[2920]: [1472293443.3913]
devices added (path: /sys/devices/virtual/net/team0, iface: team0)
Aug 27 06:24:03 deb-build NetworkManager[2920]: [1472293443.3921]
device added (path: /sys/devices/virtual/net/team0, iface: team0): no ifupdown
configuration found.
Aug 27 06:24:03 deb-build NetworkManager[2920]: This program is not intended to
be run as root.
Aug 27 06:24:03 deb-build NetworkManager[2920]: TX balancing disabled.
Aug 27 06:24:03 deb-build NetworkManager[2920]: dbus: Failed to acquire
org.libteam.teamd.team0: org.freedesktop.DBus.Error.AccessDenied: Connection
":1.42" is not allowed to own the service "org.libteam.teamd.team0" due to
security policies in the configuration file
Aug 27 06:24:03 deb-build NetworkManager[2920]: Failed to expose dbus name.
Aug 27 06:24:03 deb-build NetworkManager[2920]: teamd_init() failed.
Aug 27 06:24:03 deb-build kernel: [ 348.441312] team0: Mode changed to
"loadbalance"
Aug 27 06:24:03 deb-build NetworkManager[2920]: Failed: Invalid argument
Aug 27 06:24:03 deb-build NetworkManager[2920]: [1472293443.4331]
device (team0): teamd process quit unexpectedly; failing activation
Aug 27 06:24:03 deb-build NetworkManager[2920]: [1472293443.4331]
device (team0): state change: prepare -> failed (reason 'teamd-control-failed')
[40 120 56]
Steps to reproduce:
(suppose that the system has 2 network cards)
apt-get install network-manager libteam-utils
nmcli con del enp0s8
nmcli con del enp0s9
nmcli c a con-name team0 type team ifname team0 config '{"runner": {"name":
"loadbalance"}}'
nmcli c m team0 connection.autoconnect-slaves 1
nmcli c a con-name team0-eth1 type team-slave ifname enp0s8 master team0
nmcli c a con-name team0-eth2 type team-slave ifname enp0s9 master team0
nmcli c u team0
--
Best Regards,
Charles Malaheenee
Bug#834889: jwm: New version 2.3.6
Package: jwm Version: 2.3.5-2 Severity: wishlist Tags: upstream Dear Maintainer! A new version of jwm has been released 2016-08-12. This release includes some features, like aerosnap or task-list styles. Can you build it asap, please? Thank you Best regards, Malaheenee P.S. Yes, I've built it already, but 'make install' isn't Debian-way :) -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages jwm depends on: ii libc62.23-4 ii libcairo21.14.6-1+b1 ii libfribidi0 0.19.7-1 ii libglib2.0-0 2.48.1-3 ii libjpeg62-turbo 1:1.5.0-1 ii libpng16-16 1.6.24-2 ii librsvg2-2 2.40.16-1 ii libx11-6 2:1.6.3-1 ii libxext6 2:1.3.3-1 ii libxft2 2.3.2-1 ii libxinerama1 2:1.1.3-1+b1 ii libxmu6 2:1.1.2-2 ii libxpm4 1:3.5.11-1+b1 ii libxrender1 1:0.9.9-2 ii xterm [x-terminal-emulator] 325-1 Versions of packages jwm recommends: pn menu Versions of packages jwm suggests: pn x11-apps -- no debconf information
Bug#833645: libteam-utils: Missing dbus rules
Package: libteam-utils Version: 1.24-1 Severity: important Tags: upstream Dear Maintainer! We suggest to add by default dbus rules for teamd binary, that fails to start trying to own a connection. This rules are the part of upstream package: https://github.com/jpirko/libteam/blob/master/teamd/dbus/teamd.conf. Best regards, Malaheenee -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libteam-utils depends on: ii libc6 2.23-4 ii libdaemon00.14-6 ii libdbus-1-3 1.10.8-1 ii libjansson4 2.7-5 ii libteam5 1.24-1 ii libteamdctl0 1.24-1 libteam-utils recommends no packages. libteam-utils suggests no packages. -- no debconf information
Bug#826579: onboard: Failed to start without gir1.2-atspi-2.0
Package: onboard
Version: 1.2.0-1
Severity: grave
Tags: newcomer
Justification: renders package unusable
Dear Maintainer,
As described in title, without installed 'gir1.2-atspi-2.0' onboard fails to
start with python error like this:
Traceback (most recent call last):
File "/usr/bin/onboard", line 35, in
from Onboard.OnboardGtk import OnboardGtk as Onboard
File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 35, in
require_gi_versions()
File "/usr/lib/python3/dist-packages/Onboard/Version.py", line 28, in
require_gi_versions
gi.require_version('Atspi', '2.0')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 102, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Atspi not available
We suggest to move 'gir1.2-atspi-2.0' from 'Recommends' to 'Depends'.
Best regards,
Malahenee
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Foreign Architectures: amd64
Kernel: Linux 4.5.0-2-686-pae (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 onboard depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1
ii gir1.2-appindicator3-0.1 0.4.92-4
ii gir1.2-gdkpixbuf-2.0 2.34.0-1
ii gir1.2-glib-2.0 1.48.0-2
ii gir1.2-gtk-3.0 3.20.6-1
ii gir1.2-pango-1.0 1.40.1-1
ii iso-codes3.68-1
ii libc62.22-9
ii libcairo-gobject21.14.6-1+b1
ii libcairo21.14.6-1+b1
ii libcanberra0 0.30-3
ii libdconf10.26.0-1
ii libgcc1 1:6.1.1-4
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libglib2.0-0 2.48.1-1
ii libgtk-3-0 3.20.6-1
ii libhunspell-1.4-01.4.1-2
ii libpango-1.0-0 1.40.1-1
ii libpangocairo-1.0-0 1.40.1-1
ii librsvg2-common 2.40.15-1
ii libstdc++6 6.1.1-4
ii libx11-6 2:1.6.3-1
ii libxi6 2:1.7.6-1
ii libxkbfile1 1:1.0.9-2
ii libxtst6 2:1.2.2-1+b1
ii onboard-common 1.2.0-1
ii python3 3.5.1-3
ii python3-cairo1.10.0+dfsg-5+b1
ii python3-dbus 1.2.4-1
ii python3-gi-cairo 3.20.1-1
pn python3.5:any
Versions of packages onboard recommends:
ii gir1.2-atspi-2.0 2.20.2-1
pn onboard-data
ii xdg-utils 1.1.1-1
Versions of packages onboard suggests:
pn mousetweaks
-- no debconf information
Bug#826579: onboard: Failed to start without gir1.2-atspi-2.0
Package: onboard
Version: 1.2.0-1
Severity: grave
Tags: newcomer
Justification: renders package unusable
Dear Maintainer,
As described in title, without installed 'gir1.2-atspi-2.0' onboard fails to
start with python error like this:
Traceback (most recent call last):
File "/usr/bin/onboard", line 35, in
from Onboard.OnboardGtk import OnboardGtk as Onboard
File "/usr/lib/python3/dist-packages/Onboard/OnboardGtk.py", line 35, in
require_gi_versions()
File "/usr/lib/python3/dist-packages/Onboard/Version.py", line 28, in
require_gi_versions
gi.require_version('Atspi', '2.0')
File "/usr/lib/python3/dist-packages/gi/__init__.py", line 102, in
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace Atspi not available
We suggest to move 'gir1.2-atspi-2.0' from 'Recommends' to 'Depends'.
Best regards,
Malahenee
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: i386 (i686)
Foreign Architectures: amd64
Kernel: Linux 4.5.0-2-686-pae (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 onboard depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1
ii gir1.2-appindicator3-0.1 0.4.92-4
ii gir1.2-gdkpixbuf-2.0 2.34.0-1
ii gir1.2-glib-2.0 1.48.0-2
ii gir1.2-gtk-3.0 3.20.6-1
ii gir1.2-pango-1.0 1.40.1-1
ii iso-codes3.68-1
ii libc62.22-9
ii libcairo-gobject21.14.6-1+b1
ii libcairo21.14.6-1+b1
ii libcanberra0 0.30-3
ii libdconf10.26.0-1
ii libgcc1 1:6.1.1-4
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libglib2.0-0 2.48.1-1
ii libgtk-3-0 3.20.6-1
ii libhunspell-1.4-01.4.1-2
ii libpango-1.0-0 1.40.1-1
ii libpangocairo-1.0-0 1.40.1-1
ii librsvg2-common 2.40.15-1
ii libstdc++6 6.1.1-4
ii libx11-6 2:1.6.3-1
ii libxi6 2:1.7.6-1
ii libxkbfile1 1:1.0.9-2
ii libxtst6 2:1.2.2-1+b1
ii onboard-common 1.2.0-1
ii python3 3.5.1-3
ii python3-cairo1.10.0+dfsg-5+b1
ii python3-dbus 1.2.4-1
ii python3-gi-cairo 3.20.1-1
pn python3.5:any
Versions of packages onboard recommends:
ii gir1.2-atspi-2.0 2.20.2-1
pn onboard-data
ii xdg-utils 1.1.1-1
Versions of packages onboard suggests:
pn mousetweaks
-- no debconf information
Bug#823122: pasystray: Change dependancy to adwaita-icon-theme
Hi Scott, Yes, it is obsolete since april 2014: https://mail.gnome.org/archives/desktop-devel-list/2014-April/msg00086.html 3 different themes (gnome-icon-theme, it's symbolic version and gnome-cursors) were merged into one: adwaita-icon-theme. -- Best Regards, Charles Malaheenee
Bug#823122: pasystray: Change dependancy to adwaita-icon-theme
Package: pasystray Version: 0.5.2-1 Severity: normal Tags: upstream Dear Maintainer, I suggest to replace the dependency of the obsolete package 'gnome-icon-theme' to it's newer analog 'adwaita-icon-theme'. This helps to avoid unneeded dependencies. Best regards, Malaheenee -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pasystray depends on: ii gnome-icon-theme 3.12.0-1 ii libatk1.0-0 2.20.0-1 ii libavahi-client3 0.6.32~rc+dfsg-1 ii libavahi-common3 0.6.32~rc+dfsg-1 ii libavahi-glib1 0.6.32~rc+dfsg-1 ii libc62.22-7 ii libcairo-gobject21.14.6-1+b1 ii libcairo21.14.6-1+b1 ii libgdk-pixbuf2.0-0 2.34.0-1 ii libglib2.0-0 2.48.0-1 ii libgtk-3-0 3.20.3-1 ii libnotify4 0.7.6-2 ii libpango-1.0-0 1.40.1-1 ii libpangocairo-1.0-0 1.40.1-1 ii libpulse-mainloop-glib0 8.0-2+b2 ii libpulse08.0-2+b2 ii libx11-6 2:1.6.3-1 pasystray recommends no packages. Versions of packages pasystray suggests: pn paman pn paprefs ii pavucontrol 3.0-3+b2 pn pavumeter pn pulseaudio-module-zeroconf -- no debconf information
Bug#820158: lilyterm: Non-switchable transparency with vte-2.91
Package: lilyterm Version: 0.9.9.4-4 Severity: important Tags: upstream Dear Maintainer, Since update to vte-2.91 the window opacity became non-switchable – even if it set ‘transparent_background = 0’ or ‘transparent_window = 0’, the opacity is always active (at least with openbox & compton) or give black background. Also, icons in the right-click menu had vanished. Best regards, Malaheenee -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.4.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lilyterm depends on: ii libc6 2.22-5 ii libgdk-pixbuf2.0-0 2.32.3-1.2 ii libglib2.0-02.48.0-1 ii libgtk2.0-0 2.24.30-1.1 ii libpango-1.0-0 1.38.1-1 ii libvte9 1:0.28.2-5+b1 ii libx11-62:1.6.3-1 lilyterm recommends no packages. lilyterm suggests no packages.
Bug#800876: squid: Build 3.5.10 with ssl-bump fixes
Package: squid Version: 3.5.7-1 Severity: normal Tags: upstream Dear Maintainer! In new squid reelease was fixed annoying bug with ssl-bump (http://bugs.squid- cache.org/show_bug.cgi?id=4330). Can you build new version asap? Thank you. Best Regards, Malaheenee -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages squid depends on: ii adduser 3.113+nmu3 ii libc62.19-22 ii libcap2 1:2.24-12 ii libcomerr2 1.42.13-1 ii libdb5.3 5.3.28-11 ii libecap3 1.0.1-2 ii libexpat12.1.0-7 ii libgcc1 1:5.2.1-21 ii libgnutls-deb0-283.3.18-1 ii libgssapi-krb5-2 1.13.2+dfsg-2 ii libk5crypto3 1.13.2+dfsg-2 ii libkrb5-31.13.2+dfsg-2 ii libldap-2.4-22.4.42+dfsg-2 ii libltdl7 2.4.2-1.11 ii libnetfilter-conntrack3 1.0.4-1 ii libnettle6 3.1.1-4 ii libpam0g 1.1.8-3.1 ii libsasl2-2 2.1.26.dfsg1-14 ii libstdc++6 5.2.1-21 ii libxml2 2.9.2+zdfsg1-4 ii logrotate3.8.7-2 ii lsb-base 9.20150917 ii netbase 5.3 ii squid-common 3.5.7-1 squid recommends no packages. Versions of packages squid suggests: pn resolvconf pn smbclient pn squid-cgi pn squid-purge pn squidclient pn ufw pn winbindd -- no debconf information
Bug#789472: psi-plus: Fail to login in gtalk with new qca2-ossl
Package: psi-plus Version: 0.16.330-1+b1 Severity: normal Tags: upstream Dear Maintainer, Since update of libqca2-plugin-ossl (replaced by libqca2-plugins) psi-plus is unable to connect with google-talk services with error like unknown ssl connection. Temporary solution - hold old libqca2 package. Best regards, Malaheenee -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages psi-plus depends on: ii libaspell15 0.60.7~20110707-3 ii libc62.19-18 ii libgcc1 1:5.1.1-9 ii libidn11 1.30-1 ii libqca2 2.1.0.3-3 ii libqt4-dbus 4:4.8.7+dfsg-1 ii libqt4-network 4:4.8.7+dfsg-1 ii libqt4-svg 4:4.8.7+dfsg-1 ii libqt4-xml 4:4.8.7+dfsg-1 ii libqtcore4 4:4.8.7+dfsg-1 ii libqtgui44:4.8.7+dfsg-1 ii libstdc++6 5.1.1-9 ii libx11-6 2:1.6.3-1 ii libxss1 1:1.2.2-1 ii psi-plus-common 0.16.330-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages psi-plus recommends: pn libqca2-plugin-ossl none ii psi-plus-l10n0.16.330-1 pn psi-plus-plugins none ii psi-plus-sounds 0.16.330-1 pn sox none Versions of packages psi-plus suggests: pn libqca2-plugin-gnupg none ii xdg-utils 1.1.0~rc1+git20111210-7.4 -- 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#773495: docker.io: Build new version with security patches
Package: docker.io Version: 1.3.2~dfsg1-1 Severity: grave Tags: upstream security Justification: user security hole Dear Maintainers, Long time ago there was a new version - 1.4 (and now 1.4.1) with several security corrections - http://docs.docker.com/v1.4/release-notes/. I suggest to build it ASAP. Best regards, Malaheenee -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages docker.io depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.22 ii iptables 1.4.21-2+b1 ii libapparmor1 2.9.0-3 ii libc62.19-13 ii libdevmapper1.02.1 2:1.02.90-2 ii libsqlite3-0 3.8.7.2-1 ii perl 5.20.1-3 Versions of packages docker.io recommends: pn aufs-toolsnone ii ca-certificates 20141019 pn cgroupfs-mount | cgroup-lite none ii git 1:2.1.3-1 ii xz-utils 5.1.1alpha+20120614-2+b3 Versions of packages docker.io suggests: pn btrfs-tools none pn debootstrap none pn lxc none pn rinsenone -- 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
[Secure-testing-team] Bug#773495: docker.io: Build new version with security patches
Package: docker.io Version: 1.3.2~dfsg1-1 Severity: grave Tags: upstream security Justification: user security hole Dear Maintainers, Long time ago there was a new version - 1.4 (and now 1.4.1) with several security corrections - http://docs.docker.com/v1.4/release-notes/. I suggest to build it ASAP. Best regards, Malaheenee -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages docker.io depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.22 ii iptables 1.4.21-2+b1 ii libapparmor1 2.9.0-3 ii libc62.19-13 ii libdevmapper1.02.1 2:1.02.90-2 ii libsqlite3-0 3.8.7.2-1 ii perl 5.20.1-3 Versions of packages docker.io recommends: pn aufs-toolsnone ii ca-certificates 20141019 pn cgroupfs-mount | cgroup-lite none ii git 1:2.1.3-1 ii xz-utils 5.1.1alpha+20120614-2+b3 Versions of packages docker.io suggests: pn btrfs-tools none pn debootstrap none pn lxc none pn rinsenone -- no debconf information ___ Secure-testing-team mailing list Secure-testing-team@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/secure-testing-team
Bug#773495: docker.io: Build new version with security patches
Package: docker.io Version: 1.3.2~dfsg1-1 Severity: grave Tags: upstream security Justification: user security hole Dear Maintainers, Long time ago there was a new version - 1.4 (and now 1.4.1) with several security corrections - http://docs.docker.com/v1.4/release-notes/. I suggest to build it ASAP. Best regards, Malaheenee -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages docker.io depends on: ii adduser 3.113+nmu3 ii init-system-helpers 1.22 ii iptables 1.4.21-2+b1 ii libapparmor1 2.9.0-3 ii libc62.19-13 ii libdevmapper1.02.1 2:1.02.90-2 ii libsqlite3-0 3.8.7.2-1 ii perl 5.20.1-3 Versions of packages docker.io recommends: pn aufs-toolsnone ii ca-certificates 20141019 pn cgroupfs-mount | cgroup-lite none ii git 1:2.1.3-1 ii xz-utils 5.1.1alpha+20120614-2+b3 Versions of packages docker.io suggests: pn btrfs-tools none pn debootstrap none pn lxc none pn rinsenone -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770661: evince-gtk: Change dependency to adwaita-icon-theme
Package: evince-gtk Version: 3.14.1-1 Severity: normal Tags: upstream Dear maintainer! Since 3.14 GNOME has new adwaita-icon-theme, dependecy of gnome-icon-theme feel annoying. This bug also closely related with #496250 and #650122. I think that is more usable to change dependecy and sets this icon theme in recommended section. Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages evince-gtk depends on: ii evince-common 3.14.1-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-13 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libevdocument3-4 3.14.1-1 ii libevview3-3 3.14.1-1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.1-1 ii libgtk-3-0 3.14.5-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libxml22.9.2+dfsg1-1 ii shared-mime-info 1.3-1 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages evince-gtk recommends: pn dbus-x11 none Versions of packages evince-gtk suggests: pn gvfs none pn nautilus none ii poppler-data 0.4.7-1 ii unrar 1:5.0.10-1 -- 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#763736: Consider adding mpv-ffmpeg using ffmpeg instead of libav
Package: mpv Version: 0.6.2-2 Followup-For: Bug #763736 Sorry for stupid suggestion, but why not to try add alternative dependencies? Like as libavcodec56 | libavcodec-ffmpeg56? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mpv depends on: ii libasound2 1.0.28-1 ii libass5 0.10.2-3 ii libavcodec566:11-2 ii libavdevice55 6:11-2 ii libavfilter56:11-2 ii libavformat56 6:11-2 ii libavresample2 6:11-2 ii libavutil54 6:11-2 ii libbluray1 1:0.6.2-1 ii libbs2b03.1.0+dfsg-2.1 ii libc6 2.19-13 ii libcdio-cdda1 0.83-4.2 ii libcdio-paranoia1 0.83-4.2 ii libcdio13 0.83-4.2 ii libdvdnav4 5.0.1-1 ii libdvdread4 5.0.0-1 ii libegl1-mesa [libegl1-x11] 10.3.2-1 ii libenca01.16-1 ii libgl1-mesa-glx [libgl1]10.3.2-1 ii libguess1 1.2-1 ii libjack-jackd2-0 [libjack-0.116]1.9.10+20140719git3eb0ae6a~dfsg-2 ii libjpeg62-turbo 1:1.3.1-10 ii liblcms2-2 2.6-3+b2 ii liblircclient0 0.9.0~pre1-1.1 ii liblua5.2-0 5.2.3-1.1 ii libmpg123-0 1.20.1-2 ii libpulse0 5.0-13 ii libquvi70.4.1-2.1 ii libsdl2-2.0-0 2.0.2+dfsg1-5 ii libswscale3 6:11-2 ii libuuid12.25.2-2 ii libva-glx1 1.4.1-1 ii libva-x11-1 1.4.1-1 ii libva1 1.4.1-1 ii libvdpau1 0.8-3 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 libx11-62:1.6.2-3 ii libxext62:1.3.3-1 ii libxinerama12:1.1.3-1 ii libxkbcommon0 0.4.3-2 ii libxrandr2 2:1.4.2-1 ii libxss1 1:1.2.2-1 ii libxv1 2:1.0.10-1 ii zlib1g 1:1.2.8.dfsg-2 mpv recommends no packages. mpv 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#763736: Consider adding mpv-ffmpeg using ffmpeg instead of libav
Package: mpv Version: 0.6.2-2 Followup-For: Bug #763736 Sorry for stupid suggestion, but why not to try add alternative dependencies? Like as libavcodec56 | libavcodec-ffmpeg56? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_CA.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mpv depends on: ii libasound2 1.0.28-1 ii libass5 0.10.2-3 ii libavcodec566:11-2 ii libavdevice55 6:11-2 ii libavfilter56:11-2 ii libavformat56 6:11-2 ii libavresample2 6:11-2 ii libavutil54 6:11-2 ii libbluray1 1:0.6.2-1 ii libbs2b03.1.0+dfsg-2.1 ii libc6 2.19-13 ii libcdio-cdda1 0.83-4.2 ii libcdio-paranoia1 0.83-4.2 ii libcdio13 0.83-4.2 ii libdvdnav4 5.0.1-1 ii libdvdread4 5.0.0-1 ii libegl1-mesa [libegl1-x11] 10.3.2-1 ii libenca01.16-1 ii libgl1-mesa-glx [libgl1]10.3.2-1 ii libguess1 1.2-1 ii libjack-jackd2-0 [libjack-0.116]1.9.10+20140719git3eb0ae6a~dfsg-2 ii libjpeg62-turbo 1:1.3.1-10 ii liblcms2-2 2.6-3+b2 ii liblircclient0 0.9.0~pre1-1.1 ii liblua5.2-0 5.2.3-1.1 ii libmpg123-0 1.20.1-2 ii libpulse0 5.0-13 ii libquvi70.4.1-2.1 ii libsdl2-2.0-0 2.0.2+dfsg1-5 ii libswscale3 6:11-2 ii libuuid12.25.2-2 ii libva-glx1 1.4.1-1 ii libva-x11-1 1.4.1-1 ii libva1 1.4.1-1 ii libvdpau1 0.8-3 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 libx11-62:1.6.2-3 ii libxext62:1.3.3-1 ii libxinerama12:1.1.3-1 ii libxkbcommon0 0.4.3-2 ii libxrandr2 2:1.4.2-1 ii libxss1 1:1.2.2-1 ii libxv1 2:1.0.10-1 ii zlib1g 1:1.2.8.dfsg-2 mpv recommends no packages. mpv suggests no packages. -- no debconf information ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#762682: spacefm: Crash after update of libglib2.0-0
Package: spacefm Severity: normal Dear Maintainer, Spacefm won't run with message Attempt to unlock mutex that was not locked. Googling gets information, that is related with new version libglib2.0-0. In launchapd people suggest delete any gdk_threads_init () in sources. Perhaps, it is possible to make a patch for main.c? Same bug attempts to gtk-verison of reportbug, Temporal solution - install spacefm-gtk3 and use reportbug -u text Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.16-2-686-pae (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to ru_RU.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages spacefm depends on: ii dbus 1.8.8-1 ii desktop-file-utils0.22-1 ii libc6 2.19-11 ii libcairo2 1.12.16-5 ii libgdk-pixbuf2.0-02.30.8-1 ii libglib2.0-0 2.42.0-1 ii libgtk2.0-0 2.24.24-1 ii libpango-1.0-01.36.7-1 ii libpangocairo-1.0-0 1.36.7-1 ii libstartup-notification0 0.12-4 ii libudev1 215-4 ii libx11-6 2:1.6.2-3 ii shared-mime-info 1.3-1 ii spacefm-common0.9.4-1 Versions of packages spacefm recommends: pn udisks | udisks2 none Versions of packages spacefm suggests: ii eject 2.1.5+deb1+cvs20081104-13.1 pn gksunone pn ktsuss none pn lsofnone ii sshfs 2.5-1 ii udevil 0.4.3-1 ii wget1.15-1+b1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757079: gxkb: Build 'trunk' version
Package: gxkb Version: 0.6-1 Severity: wishlist Tags: upstream Dear Maintainer, Since gxkb has trunk version with new features , like as user path to flags new path to config file, I think that is usable to build new version from 'trunk'. Thanks. Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gxkb depends on: ii libatk1.0-0 2.12.0-1 ii libc62.19-7 ii libcairo21.12.16-2 ii libfontconfig1 2.11.0-5 ii libfreetype6 2.5.2-1 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-0 2.40.0-3 ii libgtk2.0-0 2.24.24-1 ii libpango-1.0-0 1.36.3-1 ii libpangocairo-1.0-0 1.36.3-1 ii libpangoft2-1.0-01.36.3-1 ii libwnck222.30.7-1 ii libxklavier165.2.1-1 gxkb recommends no packages. gxkb 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#757080: lilyterm: Lilyterm not use system locale
Package: lilyterm Version: 0.9.9.4-2 Severity: minor Tags: upstream Dear Maintainer, Lilyterm won't use ystem locale in gtk-interface (not VTE!). I try with fr- FR.UTF-8 ru-RU.UTF-8, but it always show english menu etc. Best regadrs, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lilyterm depends on: ii libc6 2.19-7 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-02.40.0-3 ii libgtk2.0-0 2.24.24-1 ii libpango-1.0-0 1.36.3-1 ii libvte9 1:0.28.2-5 ii libx11-62:1.6.2-2 lilyterm recommends no packages. lilyterm 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#756609: lilyterm: Changes dependency to libvte-2.90-9
Package: lilyterm Version: 0.9.9.4-1 Severity: normal Tags: upstream Dear Maintainer, Thank you for your job. I think that is better to change dependency on libvte9 to libvte-2.90-9 with newer version. Also, in package description missed Provides section, like as Provides: x -terminal-emulator. Best Regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages lilyterm depends on: ii libc6 2.19-7 ii libgdk-pixbuf2.0-0 2.30.7-1 ii libglib2.0-02.40.0-3 ii libgtk2.0-0 2.24.24-1 ii libpango-1.0-0 1.36.3-1 ii libvte9 1:0.28.2-5 ii libx11-62:1.6.2-2 lilyterm recommends no packages. lilyterm 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#739863: libwine: fail to run winecfg without .wine dir
Package: libwine Version: 1.6.2-7 Severity: important Tags: upstream Dear Maintainer, When I try to run winecfg after install wine on new machine or after deleting of .wine dir, I received an error: winecfg cat: /home/malaheenee/.wine/system.reg: File not found /usr/bin/winecfg: 32: exec: winecfg.exe: not found I'm not sure, but it appeaers with two last updates. Thank you for solving our problems. Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libwine depends on: ii libasound21.0.27.2-3 ii libc6 2.18-1 ii libexif12 0.6.21-1 ii libgl1-mesa-glx [libgl1] 9.2.2-1 ii libglu1-mesa [libglu1]9.0.0-2 ii libgphoto2-6 2.5.3.1-1 ii libgphoto2-port10 2.5.3.1-1 ii liblcms2-22.5-1 ii libldap-2.4-2 2.4.31-1+nmu2+b1 ii libmpg123-0 1.18.0-1 ii libopenal11:1.14-4 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxml2 2.9.1+dfsg1-3 ii multiarch-support 2.18-1 ii zlib1g1:1.2.8.dfsg-1 Versions of packages libwine recommends: ii fonts-liberation 1.07.3-3 ii libxcursor1 1:1.1.14-1 Versions of packages libwine suggests: ii cups-bsd 1.7.1-5 pn wine-doc none -- 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#738714: volumeicon-alsa: build new upstream version 0.5.0
Package: volumeicon-alsa Version: 0.4.6-2 Severity: wishlist Tags: upstream Dear Maintainer, I suggest to build new version of volumeicon-alsa. It has many useful changes: Use the same volume mapping as alsamixer. Allow the specification of an alternate name to use for config file via the command-line option `--config'. Added `--with-default-mixerapp' configure option. Added french translation. Added option for transparent slider background. Ported to GTK 3. Fix hanging / 100% CPU usage when pulseaudio is killed. Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages volumeicon-alsa depends on: ii alsa-base 1.0.25+3 ii libasound2 1.0.27.2-3 ii libc6 2.17-97 ii libgdk-pixbuf2.0-0 2.28.2-1+b1 ii libglib2.0-02.36.4-1 ii libgtk2.0-0 2.24.22-1 ii libnotify4 0.7.6-1 ii libx11-62:1.6.2-1 volumeicon-alsa recommends no packages. Versions of packages volumeicon-alsa suggests: pn alsamixergui | aumix-gtk | kmix | gnome-alsamixer none ii notification-daemon0.7.6-1 ii xfce4-notifyd [notification-daemon]0.2.4-2 -- 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#738632: icedtea-netx: split javaws 6 7 to different packages
Package: icedtea-netx Version: 1.4.2-1 Severity: wishlist Tags: upstream Dear Maintainer, I suggest to split package to icedtea-6-netx and icedtea-7-netx (or similar) to avoid have 2 different versions of javaws on the user's machines. I use now openjdk-7, but until I run update-alternatives (yes, I don't use default-jre), javaws by default sets to version 6. On top of everything, why I must have unused version on my desktop? Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedtea-netx depends on: ii icedtea-netx-common 1.4.2-1 ii openjdk-7-jre7u51-2.4.5-2 icedtea-netx recommends no packages. icedtea-netx 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#738664: initramfs-tools: remove all kernels while purge
Package: initramfs-tools
Version: 0.115
Severity: critical
Tags: upstream
Justification: breaks the whole system
Dear Maintainer,
When I try to purge iniramfs-tools in jessie/sid, it also removes all installed
kernels without standard warnings (like sysvinit):
---
sudo aptitude purge initramfs-tools
Les paquets suivants seront ENLEVÉS :
initramfs-tools{p} [0.115]
0 paquets mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à
jour.
Il est nécessaire de télécharger 0 o d'archives. Après dépaquetage, 334 ko
seront libérés.
Les paquets suivants ont des dépendances non satisfaites :
linux-image-3.12-1-686-pae : Dépend: initramfs-tools (= 0.110~) mais il ne
sera pas installé. ou
linux-initramfs-tool qui est un paquet
virtuel
Les actions suivantes permettront de résoudre ces dépendances :
Supprimer les paquets suivants :
1) linux-image-3.12-1-686-pae
2) linux-image-686-pae
Accepter cette solution ? [Y/n/q/?] y
Les paquets suivants seront ENLEVÉS :
initramfs-tools{p} [0.115] libuuid-perl{u} [0.05-1] linux-base{u} [3.5]
linux-image-3.12-1-686-pae{a} [3.12.9-1]
linux-image-686-pae{a} [3.12+55]
0 paquets mis à jour, 0 nouvellement installés, 5 à enlever et 0 non mis à
jour.
Il est nécessaire de télécharger 0 o d'archives. Après dépaquetage, 108 Mo
seront libérés.
Voulez-vous continuer ? [Y/n/?] n
---
I think that is very dangerous for simple users - after deleting strange
packages their systems fails to boot.
Best regards,
Malaheenee
-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 3.0M Feb 11 18:44 /boot/initrd.img-3.12-1-686-pae
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.12-1-686-pae
root=UUID=0ae21b3d-1e37-4de4-bbc5-69fe18afec37 ro quiet
-- resume
RESUME=UUID=a08ed0d9-d715-400e-8bfb-6a7f600130c8
-- /proc/filesystems
ext3
ext2
ext4
fuseblk
-- lsmod
Module Size Used by
cpuid 12583 0
usb_storage43324 0
cpufreq_conservative13872 2
pci_stub 12397 1
vboxpci22738 0
vboxnetadp 25431 0
vboxnetflt 27112 0
vboxdrv 236389 3 vboxnetadp,vboxnetflt,vboxpci
rfcomm 32155 14
bnep 17184 2
uinput 17068 1
loop 21960 0
fuse 68789 1
btusb 21248 0
bluetooth 195092 22 bnep,btusb,rfcomm
hid_generic12369 0
usbhid 39650 0
hid76882 2 hid_generic,usbhid
joydev 16847 0
uvcvideo 69768 0
videobuf2_vmalloc 12720 1 uvcvideo
videobuf2_memops 12471 1 videobuf2_vmalloc
videobuf2_core 34683 1 uvcvideo
videodev 90700 2 uvcvideo,videobuf2_core
media 17840 2 uvcvideo,videodev
sg 25573 0
sr_mod 21563 0
cdrom 34540 1 sr_mod
iTCO_wdt 12727 0
iTCO_vendor_support12585 1 iTCO_wdt
coretemp 12734 0
psmouse76428 0
snd_hda_codec_si305412662 1
serio_raw 12737 0
pcspkr 12531 0
evdev 17136 23
lpc_ich16616 0
ata_generic12450 0
snd_hda_codec_realtek40686 1
arc4 12480 2
firewire_ohci 34856 0
radeon 1193388 2
iwl394553405 0
snd_hda_intel 34991 6
iwlegacy 45729 1 iwl3945
mac80211 389428 2 iwl3945,iwlegacy
snd_hda_codec 126872 3
snd_hda_codec_realtek,snd_hda_codec_si3054,snd_hda_intel
ata_piix 25240 0
snd_hwdep 12906 1 snd_hda_codec
ttm55501 1 radeon
drm_kms_helper 35231 1 radeon
mfd_core 12537 1 lpc_ich
firewire_core 51080 1 firewire_ohci
r852 17265 0
sm_common 16469 1 r852
nand 47833 2 r852,sm_common
nand_ecc 12447 1 nand
nand_ids8209 1 nand
mtd36923 2 nand,sm_common
crc_itu_t 12331 1 firewire_core
r592 17143 0
ehci_pci 12432 0
uhci_hcd 26364 0
memstick 13432 1 r592
ehci_hcd 43678 1 ehci_pci
sdhci_pci 17643 0
sdhci 26483 1 sdhci_pci
mmc_core 79303 2 sdhci,sdhci_pci
cfg80211 343711 3 iwl3945,iwlegacy,mac80211
snd_pcm69546 4 snd_hda_codec_si3054,snd_hda_codec,snd_hda_intel
drm 194291 4 ttm,drm_kms_helper,radeon
snd_page_alloc 12882 2 snd_pcm,snd_hda_intel
usbcore 138045 7
btusb,uhci_hcd,uvcvideo,usb_storage,ehci_hcd,ehci_pci,usbhid
asus_laptop22309 0
i2c_algo_bit
Bug#738664: initramfs-tools: remove all kernels while purge
Package: initramfs-tools
Version: 0.115
Severity: critical
Tags: upstream
Justification: breaks the whole system
Dear Maintainer,
When I try to purge iniramfs-tools in jessie/sid, it also removes all installed
kernels without standard warnings (like sysvinit):
---
sudo aptitude purge initramfs-tools
Les paquets suivants seront ENLEVÉS :
initramfs-tools{p} [0.115]
0 paquets mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à
jour.
Il est nécessaire de télécharger 0 o d'archives. Après dépaquetage, 334 ko
seront libérés.
Les paquets suivants ont des dépendances non satisfaites :
linux-image-3.12-1-686-pae : Dépend: initramfs-tools (= 0.110~) mais il ne
sera pas installé. ou
linux-initramfs-tool qui est un paquet
virtuel
Les actions suivantes permettront de résoudre ces dépendances :
Supprimer les paquets suivants :
1) linux-image-3.12-1-686-pae
2) linux-image-686-pae
Accepter cette solution ? [Y/n/q/?] y
Les paquets suivants seront ENLEVÉS :
initramfs-tools{p} [0.115] libuuid-perl{u} [0.05-1] linux-base{u} [3.5]
linux-image-3.12-1-686-pae{a} [3.12.9-1]
linux-image-686-pae{a} [3.12+55]
0 paquets mis à jour, 0 nouvellement installés, 5 à enlever et 0 non mis à
jour.
Il est nécessaire de télécharger 0 o d'archives. Après dépaquetage, 108 Mo
seront libérés.
Voulez-vous continuer ? [Y/n/?] n
---
I think that is very dangerous for simple users - after deleting strange
packages their systems fails to boot.
Best regards,
Malaheenee
-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 3.0M Feb 11 18:44 /boot/initrd.img-3.12-1-686-pae
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.12-1-686-pae
root=UUID=0ae21b3d-1e37-4de4-bbc5-69fe18afec37 ro quiet
-- resume
RESUME=UUID=a08ed0d9-d715-400e-8bfb-6a7f600130c8
-- /proc/filesystems
ext3
ext2
ext4
fuseblk
-- lsmod
Module Size Used by
cpuid 12583 0
usb_storage43324 0
cpufreq_conservative13872 2
pci_stub 12397 1
vboxpci22738 0
vboxnetadp 25431 0
vboxnetflt 27112 0
vboxdrv 236389 3 vboxnetadp,vboxnetflt,vboxpci
rfcomm 32155 14
bnep 17184 2
uinput 17068 1
loop 21960 0
fuse 68789 1
btusb 21248 0
bluetooth 195092 22 bnep,btusb,rfcomm
hid_generic12369 0
usbhid 39650 0
hid76882 2 hid_generic,usbhid
joydev 16847 0
uvcvideo 69768 0
videobuf2_vmalloc 12720 1 uvcvideo
videobuf2_memops 12471 1 videobuf2_vmalloc
videobuf2_core 34683 1 uvcvideo
videodev 90700 2 uvcvideo,videobuf2_core
media 17840 2 uvcvideo,videodev
sg 25573 0
sr_mod 21563 0
cdrom 34540 1 sr_mod
iTCO_wdt 12727 0
iTCO_vendor_support12585 1 iTCO_wdt
coretemp 12734 0
psmouse76428 0
snd_hda_codec_si305412662 1
serio_raw 12737 0
pcspkr 12531 0
evdev 17136 23
lpc_ich16616 0
ata_generic12450 0
snd_hda_codec_realtek40686 1
arc4 12480 2
firewire_ohci 34856 0
radeon 1193388 2
iwl394553405 0
snd_hda_intel 34991 6
iwlegacy 45729 1 iwl3945
mac80211 389428 2 iwl3945,iwlegacy
snd_hda_codec 126872 3
snd_hda_codec_realtek,snd_hda_codec_si3054,snd_hda_intel
ata_piix 25240 0
snd_hwdep 12906 1 snd_hda_codec
ttm55501 1 radeon
drm_kms_helper 35231 1 radeon
mfd_core 12537 1 lpc_ich
firewire_core 51080 1 firewire_ohci
r852 17265 0
sm_common 16469 1 r852
nand 47833 2 r852,sm_common
nand_ecc 12447 1 nand
nand_ids8209 1 nand
mtd36923 2 nand,sm_common
crc_itu_t 12331 1 firewire_core
r592 17143 0
ehci_pci 12432 0
uhci_hcd 26364 0
memstick 13432 1 r592
ehci_hcd 43678 1 ehci_pci
sdhci_pci 17643 0
sdhci 26483 1 sdhci_pci
mmc_core 79303 2 sdhci,sdhci_pci
cfg80211 343711 3 iwl3945,iwlegacy,mac80211
snd_pcm69546 4 snd_hda_codec_si3054,snd_hda_codec,snd_hda_intel
drm 194291 4 ttm,drm_kms_helper,radeon
snd_page_alloc 12882 2 snd_pcm,snd_hda_intel
usbcore 138045 7
btusb,uhci_hcd,uvcvideo,usb_storage,ehci_hcd,ehci_pci,usbhid
asus_laptop22309 0
i2c_algo_bit
Bug#738664: initramfs-tools: remove all kernels while purge
Package: initramfs-tools
Version: 0.115
Severity: critical
Tags: upstream
Justification: breaks the whole system
Dear Maintainer,
When I try to purge iniramfs-tools in jessie/sid, it also removes all installed
kernels without standard warnings (like sysvinit):
---
sudo aptitude purge initramfs-tools
Les paquets suivants seront ENLEVÉS :
initramfs-tools{p} [0.115]
0 paquets mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à
jour.
Il est nécessaire de télécharger 0 o d'archives. Après dépaquetage, 334 ko
seront libérés.
Les paquets suivants ont des dépendances non satisfaites :
linux-image-3.12-1-686-pae : Dépend: initramfs-tools (= 0.110~) mais il ne
sera pas installé. ou
linux-initramfs-tool qui est un paquet
virtuel
Les actions suivantes permettront de résoudre ces dépendances :
Supprimer les paquets suivants :
1) linux-image-3.12-1-686-pae
2) linux-image-686-pae
Accepter cette solution ? [Y/n/q/?] y
Les paquets suivants seront ENLEVÉS :
initramfs-tools{p} [0.115] libuuid-perl{u} [0.05-1] linux-base{u} [3.5]
linux-image-3.12-1-686-pae{a} [3.12.9-1]
linux-image-686-pae{a} [3.12+55]
0 paquets mis à jour, 0 nouvellement installés, 5 à enlever et 0 non mis à
jour.
Il est nécessaire de télécharger 0 o d'archives. Après dépaquetage, 108 Mo
seront libérés.
Voulez-vous continuer ? [Y/n/?] n
---
I think that is very dangerous for simple users - after deleting strange
packages their systems fails to boot.
Best regards,
Malaheenee
-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 3.0M Feb 11 18:44 /boot/initrd.img-3.12-1-686-pae
-- /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.12-1-686-pae
root=UUID=0ae21b3d-1e37-4de4-bbc5-69fe18afec37 ro quiet
-- resume
RESUME=UUID=a08ed0d9-d715-400e-8bfb-6a7f600130c8
-- /proc/filesystems
ext3
ext2
ext4
fuseblk
-- lsmod
Module Size Used by
cpuid 12583 0
usb_storage43324 0
cpufreq_conservative13872 2
pci_stub 12397 1
vboxpci22738 0
vboxnetadp 25431 0
vboxnetflt 27112 0
vboxdrv 236389 3 vboxnetadp,vboxnetflt,vboxpci
rfcomm 32155 14
bnep 17184 2
uinput 17068 1
loop 21960 0
fuse 68789 1
btusb 21248 0
bluetooth 195092 22 bnep,btusb,rfcomm
hid_generic12369 0
usbhid 39650 0
hid76882 2 hid_generic,usbhid
joydev 16847 0
uvcvideo 69768 0
videobuf2_vmalloc 12720 1 uvcvideo
videobuf2_memops 12471 1 videobuf2_vmalloc
videobuf2_core 34683 1 uvcvideo
videodev 90700 2 uvcvideo,videobuf2_core
media 17840 2 uvcvideo,videodev
sg 25573 0
sr_mod 21563 0
cdrom 34540 1 sr_mod
iTCO_wdt 12727 0
iTCO_vendor_support12585 1 iTCO_wdt
coretemp 12734 0
psmouse76428 0
snd_hda_codec_si305412662 1
serio_raw 12737 0
pcspkr 12531 0
evdev 17136 23
lpc_ich16616 0
ata_generic12450 0
snd_hda_codec_realtek40686 1
arc4 12480 2
firewire_ohci 34856 0
radeon 1193388 2
iwl394553405 0
snd_hda_intel 34991 6
iwlegacy 45729 1 iwl3945
mac80211 389428 2 iwl3945,iwlegacy
snd_hda_codec 126872 3
snd_hda_codec_realtek,snd_hda_codec_si3054,snd_hda_intel
ata_piix 25240 0
snd_hwdep 12906 1 snd_hda_codec
ttm55501 1 radeon
drm_kms_helper 35231 1 radeon
mfd_core 12537 1 lpc_ich
firewire_core 51080 1 firewire_ohci
r852 17265 0
sm_common 16469 1 r852
nand 47833 2 r852,sm_common
nand_ecc 12447 1 nand
nand_ids8209 1 nand
mtd36923 2 nand,sm_common
crc_itu_t 12331 1 firewire_core
r592 17143 0
ehci_pci 12432 0
uhci_hcd 26364 0
memstick 13432 1 r592
ehci_hcd 43678 1 ehci_pci
sdhci_pci 17643 0
sdhci 26483 1 sdhci_pci
mmc_core 79303 2 sdhci,sdhci_pci
cfg80211 343711 3 iwl3945,iwlegacy,mac80211
snd_pcm69546 4 snd_hda_codec_si3054,snd_hda_codec,snd_hda_intel
drm 194291 4 ttm,drm_kms_helper,radeon
snd_page_alloc 12882 2 snd_pcm,snd_hda_intel
usbcore 138045 7
btusb,uhci_hcd,uvcvideo,usb_storage,ehci_hcd,ehci_pci,usbhid
asus_laptop22309 0
i2c_algo_bit
Bug#737704: Thanks a lot
Thanks a lot, Markus! It works!
Bug#737704: xarchiver: file not found when open archive from pcmanfm/spacefm
Package: xarchiver Version: 1:0.5.2+20130119+dfsg-4 Severity: normal Tags: upstream Dear Maintainer, When I'm trying to open any archive file from pcmanfm/spacefm I got message Error to open file file:///blah-blah.zip: File not found, whereas it successfully opens with xarchiver himself. I'm not sure, in what version this shows up, but it seems that with last update. Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xarchiver depends on: ii libc6 2.17-97 ii libgdk-pixbuf2.0-0 2.28.2-1+b1 ii libglib2.0-02.36.4-1 ii libgtk2.0-0 2.24.22-1 ii libpango-1.0-0 1.36.0-1+b1 Versions of packages xarchiver recommends: ii bzip2 1.0.6-5 ii p7zip-full 9.20.1~dfsg.1-4 ii unzip 6.0-10 ii xdg-utils 1.1.0~rc1+git20111210-7 ii xz-utils5.1.1alpha+20120614-2 Versions of packages xarchiver suggests: pn arj none pn lhasa none pn rar none pn rpm none pn unarnone pn unrar-free none ii zip 3.0-8 -- 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#737089: wine32: build with new libwine-gecko-2.21
Package: wine32 Version: 1.6.2-5 Severity: normal Tags: upstream Dear Maintainer, Please, could you build wine with new libwine-gecko-2.21, because old dependency anyway useless - winecfg suggests to install newer versions from site Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wine32 depends on: ii libc6 2.17-97 ii libwine1.6.2-5 ii libwine-gecko-1.4 1.4+dfsg1-3 ii x11-utils 7.7+1 wine32 recommends no packages. wine32 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
[pkg-wine-party] Bug#737089: wine32: build with new libwine-gecko-2.21
Package: wine32 Version: 1.6.2-5 Severity: normal Tags: upstream Dear Maintainer, Please, could you build wine with new libwine-gecko-2.21, because old dependency anyway useless - winecfg suggests to install newer versions from site Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wine32 depends on: ii libc6 2.17-97 ii libwine1.6.2-5 ii libwine-gecko-1.4 1.4+dfsg1-3 ii x11-utils 7.7+1 wine32 recommends no packages. wine32 suggests no packages. -- no debconf information ___ pkg-wine-party mailing list pkg-wine-party@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-wine-party
Bug#736776: wine32: Error in update-alternatives
Package: wine32 Version: 1.6.2-3 Severity: normal Tags: upstream Dear Maintainer, Thanks a lot for resolving our bugs, but we have another. During the installation of last version, aptitude's output have 2 strings with errors: Preparing to unpack .../wine32_1.6.2-3_i386.deb ... update-alternatives: erreur: pas d'alternatives pour wine update-alternatives: erreur: pas d'alternatives pour wineserver Unpacking wine32 (1.6.2-3) over (1.6.2-2+b1) ... I think that is not critical, but inexperienced users can be discouraged. Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages wine32 depends on: ii libc6 2.17-97 ii libwine1.6.2-3 ii libwine-gecko-1.4 1.4+dfsg1-3 ii x11-utils 7.7+1 wine32 recommends no packages. wine32 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
[Pkg-phototools-devel] Bug#736221: Bug closed
Bug closed, but why no changes of its page? ___ Pkg-phototools-devel mailing list Pkg-phototools-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-phototools-devel
Bug#736221: Bug closed
Bug closed, but why no changes of its page?
Bug#736220: libwine: build with new libgphoto2 (2.5.2-2)
Package: libwine Version: 1.6.2-2 Severity: normal Tags: upstream Dear Maintainer, Since that gphoto2 change version to 2.5.2 (libgphoto2-6 and libgphoto2-port-10), I think that it is necessary to build wine with new libraries to avoid to have 2 versions of the same library on user's machines. Regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libwine depends on: ii libasound21.0.27.2-3 ii libc6 2.17-97 ii libexif12 0.6.21-1 ii libgl1-mesa-glx [libgl1] 9.2.2-1 ii libglu1-mesa [libglu1]9.0.0-2 ii libgphoto2-2 2.4.14-2.4 ii libgphoto2-port0 2.4.14-2.4 ii liblcms2-22.2+git20110628-2.3+b1 ii libldap-2.4-2 2.4.31-1+nmu2+b1 ii libmpg123-0 1.16.0-1 ii libopenal11:1.14-4 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxml2 2.9.1+dfsg1-3 ii multiarch-support 2.17-97 ii zlib1g1:1.2.8.dfsg-1 Versions of packages libwine recommends: ii libxcursor1 1:1.1.14-1 pn ttf-liberation none Versions of packages libwine suggests: pn wine-doc none -- 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#736221: darktable: build with new libgphoto2 (2.5.2-2)
Package: darktable Version: 1.4-2 Severity: normal Tags: upstream Dear Maintainer, Since that gphoto2 change version to 2.5.2 (libgphoto2-6 and libgphoto2-port-10), I think that it is necessary to build wine with new libraries to avoid to have 2 versions of the same library on user's machines. Regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages darktable depends on: ii gtk2-engines 1:2.20.2-3 ii libatk1.0-0 2.10.0-2 ii libc6 2.17-97 ii libcairo2 1.12.16-2 ii libcolord11.0.6-1 ii libcurl3-gnutls 7.34.0-1 ii libexiv2-12 0.23-1 ii libflickcurl0 1.25-1 ii libgcc1 1:4.8.2-14 ii libgdk-pixbuf2.0-02.28.2-1+b1 ii libgl1-mesa-glx [libgl1] 9.2.2-1 ii libglib2.0-0 2.36.4-1 ii libglu1-mesa [libglu1]9.0.0-2 ii libgnome-keyring0 3.8.0-2 ii libgomp1 4.8.2-14 ii libgphoto2-2 2.4.14-2.4 ii libgphoto2-port0 2.4.14-2.4 ii libgtk2.0-0 2.24.22-1 ii libice6 2:1.0.8-2 ii libilmbase6 1.0.1-6 ii libjpeg8 8d-2 ii libjs-prototype 1.7.1-3 ii libjs-scriptaculous 1.9.0-2 ii libjson-glib-1.0-00.16.2-1 ii liblcms2-22.2+git20110628-2.3+b1 ii liblensfun0 0.2.8-1 ii liblua5.2-0 5.2.3-1 ii libopenexr6 1.6.1-7 ii libpango-1.0-01.36.0-1+b1 ii libpangocairo-1.0-0 1.36.0-1+b1 ii libpng12-01.2.49-5 ii librsvg2-22.40.0-1 ii libsdl1.2debian 1.2.15-8 ii libsm62:1.2.1-2 ii libsoup2.4-1 2.44.2-1 ii libsqlite3-0 3.8.2-1 ii libstdc++64.8.2-14 ii libtiff5 4.0.3-7 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxml2 2.9.1+dfsg1-3 ii zlib1g1:1.2.8.dfsg-1 darktable recommends no packages. darktable 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#736222: rawstudio: build with new libgphoto2 (2.5.2-2)
Package: rawstudio Version: 2.0-1.1 Severity: normal Tags: upstream Dear Maintainer, Since that gphoto2 change version to 2.5.2 (libgphoto2-6 and libgphoto2-port-10), I think that it is necessary to build rawstudio with new libraries to avoid to have 2 versions of the same library on user's machines. Regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages rawstudio depends on: ii gconf-service 3.2.6-1 ii libatk1.0-0 2.10.0-2 ii libc6 2.17-97 ii libcairo2 1.12.16-2 ii libcurl3-gnutls 7.34.0-1 ii libdbus-1-3 1.8.0-1 ii libexif12 0.6.21-1 ii libexiv2-12 0.23-1 ii libfftw3-3 3.3.3-7 ii libfontconfig1 2.11.0-2 ii libfreetype62.5.2-1 ii libgcc1 1:4.8.2-14 ii libgconf-2-43.2.6-1 ii libgdk-pixbuf2.0-0 2.28.2-1+b1 ii libglib2.0-02.36.4-1 ii libgphoto2-22.4.14-2.4 ii libgphoto2-port02.4.14-2.4 ii libgtk2.0-0 2.24.22-1 ii libjpeg88d-2 ii liblcms11.19.dfsg-1.2+b1 ii liblensfun0 0.2.8-1 ii libpango1.0-0 1.36.0-1+b1 ii libsqlite3-03.8.2-1 ii libstdc++6 4.8.2-14 ii libtiff43.9.7-3 ii libx11-62:1.6.2-1 ii libxml2 2.9.1+dfsg1-3 rawstudio recommends no packages. rawstudio 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#736221: darktable: build with new libgphoto2 (2.5.2-2)
There are one error: please, reade darktable instead of 'wine'. Sorry for my inattention, I submitted 3 bugs in different packages.
Bug#735533: libwine: fonts-liberation instead of ttf-liberation in Recommends
Package: libwine Version: 1.6.2-2 Severity: minor Tags: upstream Dear Maintainer, Since the ttf-liberation was replaced by fonts-liberation, I think that's more utile to replace it in Recommends section. This replacement allows to avoid installation unneeded dummy packages. Best regards, Malaheenee -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.12-1-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libwine depends on: ii libasound21.0.27.2-3 ii libc6 2.17-97 ii libexif12 0.6.21-1 ii libgl1-mesa-glx [libgl1] 9.2.2-1 ii libglu1-mesa [libglu1]9.0.0-2 ii libgphoto2-2 2.4.14-2.4 ii libgphoto2-port0 2.4.14-2.4 ii liblcms2-22.2+git20110628-2.3+b1 ii libldap-2.4-2 2.4.31-1+nmu2+b1 ii libmpg123-0 1.16.0-1 ii libopenal11:1.14-4 ii libx11-6 2:1.6.2-1 ii libxext6 2:1.3.2-1 ii libxml2 2.9.1+dfsg1-3 ii multiarch-support 2.17-97 ii zlib1g1:1.2.8.dfsg-1 Versions of packages libwine recommends: ii libxcursor1 1:1.1.14-1 pn ttf-liberation none Versions of packages libwine suggests: pn wine-doc none -- 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 811745] Re: Whole system freeze after safely remove external usb drive
I confirm the same problem happening on a Asus F3Sr running a fully- updated 10.04.2. System freeze after safely remove Transcend StoreJet 25 mobile (320G, NTFS). As other users have confirmed, rolling the kernel back to 2.6.32-32 fixes the problem. Temporary decision if you want use kernel 2.6.32-33 - using Gnome applet Disk mounting (I'm not sure in name of this applet, beacuse I use Russian locale). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/811745 Title: Whole system freeze after safely remove external usb drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/811745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
