Bug#484575: nagios-nrpe-plugin is missing IPv6-Support
Should this be closed? 2.15 is in jessie and IPv6 is working fine for me. ~David
Bug#822870: libiscsi2: Please update to new upstream release 1.15.0
Package: libiscsi2 Version: 1.12.0-2 Severity: wishlist Dear Maintainer, 1.15.0 was released a couple of months ago [1], and it would be nice to get it added to Debian. In particular it's used for qemu's iSCSI support which needs that version for proper handling of timeouts. Overall there don't seem to be any packaging changes necessary, although I am not sure how the soname changes should be evaluated. I can share my updated packaging but the changes are so minimal that I doubt it's worth the effort (I just removed the patches and updated the package name to reflect the new so version). ~David [1]: https://github.com/sahlberg/libiscsi/releases -- System Information: Debian Release: 8.3 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-0.bpo.1-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages libiscsi2 depends on: ii libc6 2.19-18+deb8u3 ii multiarch-support 2.19-18+deb8u3 libiscsi2 recommends no packages. libiscsi2 suggests no packages. -- no debconf information
Bug#819961: nslcd: package upgrade fails in postinst due to uncommon characters in bindpw config parameter
Package: nslcd Version: 0.9.4-3+deb8u1 Severity: important Hi, the latest package update broke on my system: ---SNIP--- # apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libicu48 Use 'apt-get autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up nslcd (0.9.4-3+deb8u1) ... sed: -e expression #1, char 87: unterminated address regex dpkg: error processing package nslcd (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of libnss-ldapd:amd64: libnss-ldapd:amd64 depends on nslcd (>= 0.9.0) | nslcd-2; however: Package nslcd is not configured yet. Package nslcd-2 is not installed. Package nslcd which provides nslcd-2 is not configured yet. dpkg: error processing package libnss-ldapd:amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libpam-ldapd:amd64: libpam-ldapd:amd64 depends on nslcd (>= 0.9.0) | nslcd-2; however: Package nslcd is not configured yet. Package nslcd-2 is not installed. Package nslcd which provides nslcd-2 is not configured yet. dpkg: error processing package libpam-ldapd:amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: nslcd libnss-ldapd:amd64 libpam-ldapd:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) ---SNAP-- This seems to be because the postinst script uses sed to update the config file using sed, and my "bindpw" contains a ']' character. I am not sure what the best solution is here, since there are a number of characters which are interpreted as regex special characters. But the package upgrade failing like this doesn't seem an acceptable state either. I know it's a weird password character but the generator program I used at the time tried to be extra secure, I guess. ~David -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.1.16-x86_64-jb1 (SMP w/3 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 nslcd depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 ii libc6 2.19-18+deb8u4 ii libgssapi-krb5-2 1.12.1+dfsg-19+deb8u2 ii libldap-2.4-2 2.4.40+dfsg-1+deb8u2 Versions of packages nslcd recommends: ii bind9-host [host] 1:9.9.5.dfsg-9+deb8u6 ii ldap-utils 2.4.40+dfsg-1+deb8u2 iu libnss-ldapd [libnss-ldap] 0.9.4-3+deb8u1 iu libpam-ldapd [libpam-ldap] 0.9.4-3+deb8u1 pn nslcd-utils ii unscd [nscd]0.51-1+b2 Versions of packages nslcd suggests: pn kstart -- debconf information: * nslcd/ldap-uris: ldap://localhost/ nslcd/xdm-needs-restart: nslcd/ldap-sasl-realm: nslcd/ldap-starttls: false nslcd/ldap-cacertfile: /etc/ssl/certs/ca-certificates.crt nslcd/ldap-binddn: uid=pam,ou=sysusers,dc=de,dc=mcbf,dc=net nslcd/ldap-reqcert: nslcd/ldap-auth-type: simple nslcd/ldap-sasl-mech: * libraries/restart-without-asking: false nslcd/ldap-sasl-authzid: * nslcd/ldap-base: dc=de,dc=mcbf,dc=net nslcd/ldap-sasl-krb5-ccname: /var/run/nslcd/nslcd.tkt * nslcd/restart-services: saslauthd postgresql exim4 dovecot danted cron nslcd/ldap-sasl-authcid: * nslcd/restart-failed: nslcd/disable-screensaver: nslcd/ldap-sasl-secprops:
Bug#806842: lldb: Broken lldb man page
Package: lldb Version: 1:3.6-32 Severity: normal Dear Maintainer, the man page of lldb just contains: DESCRIPTION ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. build-llvm/Release/bin/lldb: error while loading shared libraries: liblldb-3.6.so: cannot open shared object file: No such file or directory I was expecting a little more information here :-) ~David -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lldb depends on: ii lldb-3.6 1:3.6.2-3 lldb recommends no packages. lldb suggests no packages. -- no debconf information
Bug#801921: gdm3: Broken greeter, maybe Unable to init server: Could not connect: Connection refused
Package: gdm3 Version: 3.18.0-2 Severity: normal Dear Maintainer, I ran a dist-upgrade yesterday (2015-10-14), shut down, and on booting today it just fails with the strange graphical prompt "Oh no! Something has gone wrong." and a 'Log Out' button even though I'm not logged in yet and just expected to see the greeter. I can't find anything useful in the logs. The output of `journalctl -f` after starting the gdm3 service is attached below. I installed lightdm instead, and it works without any issues. Let me know if there's something I can try to debug this. Thanks, ~David ---SNIP--- Oct 15 23:12:54 alucardo sudo[2817]: squisher : TTY=pts/1 ; PWD=/home/squisher ; USER=root ; COMMAND=/bin/systemctl gdm3 start Oct 15 23:12:54 alucardo sudo[2817]: pam_unix(sudo:session): session opened for user root by squisher(uid=0) Oct 15 23:12:54 alucardo sudo[2817]: pam_unix(sudo:session): session closed for user root Oct 15 23:12:58 alucardo sudo[2839]: squisher : TTY=pts/1 ; PWD=/home/squisher ; USER=root ; COMMAND=/bin/systemctl start gdm3 Oct 15 23:12:58 alucardo sudo[2839]: pam_unix(sudo:session): session opened for user root by squisher(uid=0) Oct 15 23:12:58 alucardo polkitd(authority=local)[1652]: Registered Authentication Agent for unix-process:2840:41106 (system bus name :1.47 [/usr/bin/pkttyagent --notify-fd 4 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Oct 15 23:12:58 alucardo systemd[1]: Starting GNOME Display Manager... Oct 15 23:12:58 alucardo systemd[1]: Started GNOME Display Manager. Oct 15 23:12:58 alucardo sudo[2839]: pam_unix(sudo:session): session closed for user root Oct 15 23:12:58 alucardo polkitd(authority=local)[1652]: Unregistered Authentication Agent for unix-process:2840:41106 (system bus name :1.47, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Oct 15 23:12:58 alucardo gdm-launch-environment][2866]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) Oct 15 23:12:58 alucardo systemd[1]: Created slice user-108.slice. Oct 15 23:12:58 alucardo systemd[1]: Starting User Manager for UID 108... Oct 15 23:12:58 alucardo systemd-logind[1263]: New session c3 of user Debian-gdm. Oct 15 23:12:58 alucardo systemd[2882]: pam_unix(systemd-user:session): session opened for user Debian-gdm by (uid=0) Oct 15 23:12:58 alucardo systemd[1]: Started Session c3 of user Debian-gdm. Oct 15 23:12:58 alucardo systemd[2882]: Reached target Sockets. Oct 15 23:12:58 alucardo systemd[2882]: Removed slice Root Slice. Oct 15 23:12:58 alucardo systemd[2882]: Reached target Timers. Oct 15 23:12:58 alucardo systemd[2882]: Reached target Paths. Oct 15 23:12:58 alucardo systemd[2882]: Reached target Basic System. Oct 15 23:12:58 alucardo systemd[2882]: Reached target Default. Oct 15 23:12:58 alucardo systemd[2882]: Startup finished in 20ms. Oct 15 23:12:58 alucardo systemd[1]: Started User Manager for UID 108. Oct 15 23:12:58 alucardo console-kit-daemon[1837]: (process:2892): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Oct 15 23:12:58 alucardo console-kit-daemon[1837]: (process:2894): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Oct 15 23:12:58 alucardo console-kit-daemon[1837]: (process:2895): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Oct 15 23:12:58 alucardo gnome-session[2899]: Entering running state Oct 15 23:12:58 alucardo gnome-session[2899]: Unable to init server: Could not connect: Connection refused Oct 15 23:12:58 alucardo gnome-session[2899]: ** (gnome-session-failed:2905): WARNING **: Cannot open display: Oct 15 23:12:59 alucardo gdm-launch-environment][2866]: pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm Oct 15 23:12:59 alucardo gdm3[2854]: GdmDisplay: display lasted 1.332457 seconds Oct 15 23:12:59 alucardo systemd-logind[1263]: Removed session c3. Oct 15 23:12:59 alucardo gdm3[2854]: Child process -2896 was already dead. Oct 15 23:12:59 alucardo gdm3[2854]: Child process 2866 was already dead. Oct 15 23:12:59 alucardo gdm3[2854]: Unable to kill session worker process Oct 15 23:12:59 alucardo console-kit-daemon[1837]: (process:2914): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed Oct 15 23:12:59 alucardo systemd[1]: Stopping User Manager for UID 108... Oct 15 23:12:59 alucardo systemd[2882]: Created slice Root Slice. Oct 15 23:12:59 alucardo systemd[2882]: Stopped target Default. Oct 15 23:12:59 alucardo systemd[2882]: Stopped target Basic System. Oct 15 23:12:59 alucardo systemd[2882]: Stopped target Paths. Oct 15 23:12:59 alucardo systemd[2882]: Stopped target Timers. Oct 15 23:12:59 alucardo systemd[2882]: Reached target Shutdown. Oct 15 23:12:59 alucardo systemd[2882]: Starting Exit the Session... Oct 15 23:12:59 alucardo systemd[2882]: Stopped target Sockets. Oct 15 23:12:59 alucardo
Bug#801240: ceph: Logrotate reload is broken (at least with systemd)
Package: ceph
Version: 0.94.3-1
Severity: important
Tags: patch
Dear Maintainer,
the logrotate script tries to detect the init system, but fails with
systemd because it finds invoke-rc.d, which is installed by default.
Upstream fixed this already in a pretty universal way (commit
c1b28591a2ba55abd644186938d440fc90743f15), could you please
include the attached patch with the next upload?
Thanks,
~David
-- System Information:
Debian Release: 8.2
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
diff --git a/src/logrotate.conf b/src/logrotate.conf
index 1833d55..50e7ee8 100644
--- a/src/logrotate.conf
+++ b/src/logrotate.conf
@@ -4,25 +4,7 @@
compress
sharedscripts
postrotate
-if which invoke-rc.d > /dev/null 2>&1 && [ -x `which invoke-rc.d` ]; then
-invoke-rc.d ceph reload >/dev/null
-elif which service > /dev/null 2>&1 && [ -x `which service` ]; then
-service ceph reload >/dev/null
-fi
-# Possibly reload twice, but depending on ceph.conf the reload above may be a no-op
-if which initctl > /dev/null 2>&1 && [ -x `which initctl` ]; then
-for daemon in osd mon mds ; do
- find -L /var/lib/ceph/$daemon/ -mindepth 1 -maxdepth 1 -regextype posix-egrep -regex '.*/[A-Za-z0-9]+-[A-Za-z0-9._-]+' -printf '%P\n' \
-| while read f; do
-if [ -e "/var/lib/ceph/$daemon/$f/done" -o -e "/var/lib/ceph/$daemon/$f/ready" ] && [ -e "/var/lib/ceph/$daemon/$f/upstart" ] && [ ! -e "/var/lib/ceph/$daemon/$f/sysvinit" ]; then
- cluster="${f%%-*}"
- id="${f#*-}"
-
- initctl reload ceph-$daemon cluster="$cluster" id="$id" 2>/dev/null || :
-fi
- done
-done
-fi
+killall -q -1 ceph-mon ceph-mds ceph-osd || true
endscript
missingok
notifempty
Bug#799814: obnam tries to use fuse.Fuse, while the jessie version seems to be called fuse.FUSE
Package: obnam
Version: 1.8-1
Severity: important
Dear Maintainer,
I just installed obnam, and it seems to be completely broken in jessie?
Seems like a quick fix, but I wonder if I'm doing something wrong or is
really noone using it in jessie?
~David
(2095)-walter:~% obnam
CRITICAL:root:Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 174, in _run
self.enable_plugins()
File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 503, in
enable_plugins
for plugin in self.pluginmgr.plugins:
File "/usr/lib/python2.7/dist-packages/cliapp/pluginmgr.py", line 75, in
plugins
self._plugins = self.load_plugins()
File "/usr/lib/python2.7/dist-packages/cliapp/pluginmgr.py", line 112, in
load_plugins
for plugin in self.load_plugin_file(pathname):
File "/usr/lib/python2.7/dist-packages/cliapp/pluginmgr.py", line 132, in
load_plugin_file
('.py', 'r', imp.PY_SOURCE))
File "/usr/lib/python2.7/dist-packages/obnamlib/plugins/fuse_plugin.py", line
212, in
class ObnamFuse(fuse.Fuse):
AttributeError: 'module' object has no attribute 'Fuse'
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 174, in _run
self.enable_plugins()
File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 503, in
enable_plugins
for plugin in self.pluginmgr.plugins:
File "/usr/lib/python2.7/dist-packages/cliapp/pluginmgr.py", line 75, in
plugins
self._plugins = self.load_plugins()
File "/usr/lib/python2.7/dist-packages/cliapp/pluginmgr.py", line 112, in
load_plugins
for plugin in self.load_plugin_file(pathname):
File "/usr/lib/python2.7/dist-packages/cliapp/pluginmgr.py", line 132, in
load_plugin_file
('.py', 'r', imp.PY_SOURCE))
File "/usr/lib/python2.7/dist-packages/obnamlib/plugins/fuse_plugin.py", line
212, in
class ObnamFuse(fuse.Fuse):
AttributeError: 'module' object has no attribute 'Fuse'
% python
Python 2.7.9 (default, Mar 1 2015, 12:57:24)
[GCC 4.9.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import fuse
>>> help(fuse)
>>> f = fuse.FUSE()
Traceback (most recent call last):
File "", line 1, in
TypeError: __init__() takes at least 3 arguments (1 given)
>>> fuse.FUSE
>>>
-- System Information:
Debian Release: 8.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages obnam depends on:
ii libc6 2.19-18
ii python2.7.9-1
ii python-cliapp 1.20140719-1
ii python-fuse 2:0.2.1-10
ii python-larch 1.20131130-1
ii python-paramiko 1.15.1-1
ii python-tracing0.8-1
ii python-ttystatus 0.23-1
obnam recommends no packages.
obnam suggests no packages.
-- no debconf information
Bug#770283: xfburn: No longer found in Stretch
retitle 770283 xfburn crashes when adding Data Composition files on ppc (32bit) severity 770283 normal tags 770283 + wontfix jessie thanks Hi Dan, thanks for the report! My guess is that gtk fixed something, but we'll probably never find out... great to hear that the situation has improved for you though! ~David On 2015-08-17 01:07, Dan DeVoto wrote: Package: xfburn Followup-For: Bug #770283 Dear Maintainer, I no longer experience this bug in 0.5.4-1 in Debian Stretch. Everything seems fine now. Regards, Dan -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 4.1.0-1-powerpc 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 xfburn depends on: ii libburn41.3.2-1.1 ii libc6 2.19-19 ii libexo-1-0 0.10.6-1 ii libgdk-pixbuf2.0-0 2.31.5-1 ii libglib2.0-02.44.1-1.1 ii libgstreamer-plugins-base1.0-0 1.4.5-2 ii libgstreamer1.0-0 1.4.5-2 ii libgtk2.0-0 2.24.28-1 ii libgudev-1.0-0 230-2 ii libisofs6 1.3.2-1.1 ii libxfce4ui-1-0 4.12.1-2 ii libxfce4util7 4.12.1-2 xfburn recommends no packages. xfburn suggests no packages. -- no debconf information
Bug#791491: lives: Crashes on startup
On 2015-07-11 10:24, Sebastian Ramacher wrote: On 2015-07-05 10:29:47, David Mohr wrote: LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect image_stabilizer, line 4 LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect motion_analyser, line 4 ** Gtk:ERROR:/build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c:609:tick_cb: assertion failed: (priv-pulse2 priv-pulse1) I'm unable to reproduce the issue. Are you using a special theme or something that could mess with GTK+? I selected NOX in xfce4-settings-manager. AFAIK that's gtk2 though, gtk3 applications have this ugly white/grayish theme. I don't know of a better way to check. lives 2.4.0~ds0-1 should hit the archive any minute. Is this issue reproducible with the new upstream version? I don't see it yet, will report on it later. When reporting crashes, please include details of your operating system, distribution, and the LiVES version (2.2.8) and any information shown below: #0 0x7fb3543974c9 in __libc_waitpid (pid=873, stat_loc=stat_loc@entry=0x7ffefeee664c, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40 #1 0x7fb357057433 in g_on_error_stack_trace (prg_name=0x1104700 /usr/lib/lives/lives-exe) at /tmp/buildd/glib2.0-2.44.1/./glib/gbacktrace.c:252 #2 0x0041ecd8 in () #3 0x7fb3543978d0 in signal handler called () #4 0x7fb35400d107 in __GI_raise (sig=sig@entry=6) #5 0x7fb35400e4e8 in __GI_abort () at abort.c:89 #6 0x7fb3570a7b55 in g_assertion_message (domain=domain@entry=0x7fb358d4b527 Gtk, file=file@entry=0x7fb358d9b2b0 /build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c, line=line@entry=609, func=func@entry=0x7fb358d9b4b7 tick_cb, message=message@entry=0x2a47ec0 assertion failed: (priv-pulse2 priv-pulse1)) at /tmp/buildd/glib2.0-2.44.1/./glib/gtestutils.c:2356 #7 0x7fb3570a7bea in g_assertion_message_expr (domain=0x7fb358d4b527 Gtk, file=0x7fb358d9b2b0 /build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c, line=609, func=0x7fb358d9b4b7 tick_cb, expr=optimized out) #8 0x7fb358c1ae6e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #9 0x7fb358d0cf44 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #10 0x7fb357358504 in _g_closure_invoke_va (closure=0x145aec0, return_value=0x0, instance=0x11052c0, args=0x7ffefeee70c8, n_params=optimized out, param_types=0x0) at /tmp/buildd/glib2.0-2.44.1/./gobject/gclosure.c:831 #11 0x7fb357371fa7 in g_signal_emit_valist (instance=instance@entry=0x11052c0, signal_id=signal_id@entry=139, detail=detail@entry=0, var_args=var_args@entry=0x7ffefeee70c8) at /tmp/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3214 #12 0x7fb357372e4a in g_signal_emit_by_name (instance=0x11052c0, detailed_signal=0x7fb358792414 update) #13 0x7fb35872c3bc in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #14 0x7fb35871bcf8 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #15 0x7fb3570825e3 in g_timeout_dispatch (source=0x154f690, callback=optimized out, user_data=optimized out) #16 0x7fb357081b4d in g_main_context_dispatch (context=0x10bd3f0) #17 0x7fb357081b4d in g_main_context_dispatch (context=context@entry=0x10bd3f0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #18 0x7fb357081f20 in g_main_context_iterate (context=context@entry=0x10bd3f0, block=block@entry=0, dispatch=dispatch@entry=1, self=optimized out) #19 0x7fb357081fcc in g_main_context_iteration (context=0x10bd3f0, may_block=0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3869 #20 0x0041d531 in () #21 0x004b6b34 in () #22 0x00423b74 in () #23 0x00424b3f in () #24 0x7fb357081b4d in g_main_context_dispatch (context=0x10bd3f0) #25 0x7fb357081b4d in g_main_context_dispatch (context=context@entry=0x10bd3f0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #26 0x7fb357081f20 in g_main_context_iterate (context=0x10bd3f0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) #27 0x7fb357082242 in g_main_loop_run (loop=0x11046a0) #28 0x7fb358bc6a85 in gtk_main () #29 0x00417421 in main () Please install lives-dbg and libgtk-3-0-dbg so that we know what the missing bits are. Ah yes, should've done that right away. Funny thing is that with the two -dbg packages installed, I don't get a backtrace anymore! (2120)-alucardo:~/tmp/lives% lives -debug LiVES 2.2.8 Copyright 2002-2015 Gabriel Finch (salsa...@gmail.com) and others. LiVES comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details. LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect image_stabilizer, line 4 LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect motion_analyser
Bug#791491: lives: Crashes on startup
Running it directly in gdb allows me to get a backtrace: Reading symbols from /usr/lib/lives/lives-exe...Reading symbols from /usr/lib/debug/.build-id/4b/89b56dd51625e18b580231f82597f040d7c029.debug...done. done. (gdb) run Starting program: /usr/lib/lives/lives-exe [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffe71d4700 (LWP 29544)] LiVES 2.2.8 Copyright 2002-2015 Gabriel Finch (salsa...@gmail.com) and others. LiVES comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details. LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect image_stabilizer, line 4 LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect motion_analyser, line 4 ** Gtk:ERROR:/build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gtk/gtkprogressbar.c:609:tick_cb: assertion failed: (priv-pulse2 priv-pulse1) Program received signal SIGABRT, Aborted. 0x72b9a107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) thread apply all bt Thread 2 (Thread 0x7fffe71d4700 (LWP 29544)): #0 0x72c4253d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x75bc9ebc in g_main_context_iterate (priority=2147483647, n_fds=2, fds=0x7fffe00010c0, timeout=-1, context=0x10597e0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:4103 #2 0x75bc9ebc in g_main_context_iterate (context=0x10597e0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3803 #3 0x75bca242 in g_main_loop_run (loop=0x1059770) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:4002 #4 0x761c0af6 in gdbus_shared_thread_func (user_data=0x10597b0) at /tmp/buildd/glib2.0-2.44.1/./gio/gdbusprivate.c:274 #5 0x75bf0955 in g_thread_proxy (data=0x1046ca0) at /tmp/buildd/glib2.0-2.44.1/./glib/gthread.c:764 #6 0x72f160a4 in start_thread (arg=0x7fffe71d4700) at pthread_create.c:309 #7 0x72c4b07d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x77f18a80 (LWP 29522)): #0 0x72b9a107 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x72b9b4e8 in __GI_abort () at abort.c:89 #2 0x75befb55 in g_assertion_message (domain=domain@entry=0x778777a7 Gtk, file=file@entry=0x778c7570 /build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gtk/gtkprogressbar.c, line=line@entry=609, func=func@entry=0x778c __FUNCTION__.52871 tick_cb, message=message@entry=0x29da860 assertion failed: (priv-pulse2 priv-pulse1)) at /tmp/buildd/glib2.0-2.44.1/./glib/gtestutils.c:2356 #3 0x75befbea in g_assertion_message_expr (domain=domain@entry=0x778777a7 Gtk, file=file@entry=0x778c7570 /build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gtk/gtkprogressbar.c, line=line@entry=609, func=func@entry=0x778c __FUNCTION__.52871 tick_cb, expr=expr@entry=0x778a027d priv-pulse2 priv-pulse1) at /tmp/buildd/glib2.0-2.44.1/./glib/gtestutils.c:2371 #4 0x7774706e in tick_cb (widget=0x123e1c0 [GtkProgressBar], frame_clock=optimized out, user_data=optimized out) at /build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gtk/gtkprogressbar.c:609 #5 0x778391b4 in gtk_widget_on_frame_clock_update (frame_clock=0x10992c0 [GdkFrameClockIdle], widget=0x123e1c0 [GtkProgressBar]) at /build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gtk/gtkwidget.c:5299 #6 0x75e9f504 in _g_closure_invoke_va (closure=0x13e9660, return_value=0x0, instance=0x10992c0, args=0x7fffc618, n_params=optimized out, param_types=0x0) at /tmp/buildd/glib2.0-2.44.1/./gobject/gclosure.c:831 #7 0x75eb8fa7 in g_signal_emit_valist (instance=instance@entry=0x10992c0, signal_id=signal_id@entry=139, detail=detail@entry=0, var_args=var_args@entry=0x7fffc618) at /tmp/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3214 #8 0x75eb9e4a in g_signal_emit_by_name (instance=instance@entry=0x10992c0, detailed_signal=detailed_signal@entry=0x772bc654 update) at /tmp/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3401 #9 0x7725644c in gdk_frame_clock_paint_idle (data=0x10992c0) at /build/gtk+3.0-VSpacm/gtk+3.0-3.16.5/./gdk/gdkframeclockidle.c:380 zsh: segmentation fault gdb /usr/lib/lives/lives-exe It crashed when the startup window said Loading realtime effect plugins... Not sure why the bt kills gdb... (but fyi, no other odd crashes on my system). ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791964: gdm3: upgrade causes X session to be terminated
On 2015-07-10 10:46, Michael Biebl wrote: Am 10.07.2015 um 18:38 schrieb Josh Triplett: On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote: * Systemd has been fixed in v222 to no longer kill services on reload if BusName is set, so drop that part from 92_systemd_unit.patch. but that is EXACTLY what happened to me right now, in the middle of Right. Subsequent reloads of gdm3.service should no longer kill gdm3.service though. So this was indeed fixed in v222 but there seems to be a specific issue for the upgrade path. Once gdm3 has been restarted, a reload no longer causes it to be killed. Note, though, that it doesn't help for systemd to be upgraded first. Even if running the new systemd 222, upgrading gdm3 kills the active session. Well, that's exactly what I said, right? apt used this order on my system: 2015-07-09 12:05:33 status installed systemd:amd64 222-1 [...] 2015-07-09 12:05:46 status installed gdm3:amd64 3.14.2-1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791964: gdm3: upgrade causes X session to be terminated
Package: gdm3 Version: 3.14.2-1 Severity: normal Dear Maintainer, the changelog reads: * Systemd has been fixed in v222 to no longer kill services on reload if BusName is set, so drop that part from 92_systemd_unit.patch. but that is EXACTLY what happened to me right now, in the middle of doing some work. That's highly unacceptable IMHO. I ran an apt-get upgrade, and suddenly my X session closed and I was brought back to the gdm login screen. Pretty busy right now, but do let me know what could help to pinpoint this issue and I'll try to provide more details. ~David -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gdm3 depends on: ii accountsservice 0.6.40-2 ii adduser 3.113+nmu3 ii awesome [x-window-manager]3.5.6-1 ii dconf-cli 0.24.0-2 ii dconf-gsettings-backend 0.24.0-2 ii debconf [debconf-2.0] 1.5.56 ii gir1.2-gdm3 3.14.2-1 ii gnome-session-bin 3.16.0-1 ii gnome-settings-daemon 3.16.2-3 ii gnome-shell 3.16.3-1 ii gsettings-desktop-schemas 3.16.1-1 ii libaccountsservice0 0.6.40-2 ii libaudit1 1:2.4.2-1 ii libc6 2.19-18 ii libcanberra-gtk3-00.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-02.31.4-2 ii libgdm1 3.14.2-1 it libglib2.0-0 2.44.1-1.1 ii libglib2.0-bin2.44.1-1.1 iu libgtk-3-03.16.5-1 ii libpam-modules1.1.8-3.1 ii libpam-runtime1.1.8-3.1 ii libpam-systemd222-1 ii libpam0g 1.1.8-3.1 ii librsvg2-common 2.40.9-2 ii libselinux1 2.3-2+b1 ii libsystemd0 222-1 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.3-1 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-1 ii libxrandr22:1.4.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 iu metacity [x-window-manager] 1:3.17.2-4 ii mutter [x-window-manager] 3.16.3-1 ii policykit-1 0.105-10 ii rxvt [x-terminal-emulator]1:2.7.10-6 ii ucf 3.0030 ii x11-common1:7.7+9 ii x11-xserver-utils 7.7+4 ii xfce4-session [x-session-manager] 4.12.1-3 ii xfce4-terminal [x-terminal-emulator] 0.6.3-1+b2 ii xfwm4 [x-window-manager] 4.12.3-1 ii xterm [x-terminal-emulator] 318-2 Versions of packages gdm3 recommends: ii at-spi2-core 2.16.0-1 ii desktop-base 8.0.2 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+2 ii xserver-xephyr 2:1.17.2-1 ii xserver-xorg 1:7.7+9 ii zenity 3.16.3-1 Versions of packages gdm3 suggests: pn gnome-orcanone ii libpam-gnome-keyring 3.16.0-4 -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#791491: lives: Crashes on startup
Package: lives Version: 2.2.8~ds0-1 Severity: grave Justification: renders package unusable Dear Maintainer, just wanted to give lives a shot, but it crashes immediately after the startup dialog made some progress: % lives -debug LiVES 2.2.8 Copyright 2002-2015 Gabriel Finch (salsa...@gmail.com) and others. LiVES comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details. LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect image_stabilizer, line 4 LiVES info: Invalid effect farneback_analyserfarneback_analysersalsaman1 found in compound effect motion_analyser, line 4 ** Gtk:ERROR:/build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c:609:tick_cb: assertion failed: (priv-pulse2 priv-pulse1) Unfortunately LiVES crashed. Please report this bug at http://sourceforge.net/tracker/?group_id=64341atid=507139 Thanks. Recovery should be possible if you restart LiVES. When reporting crashes, please include details of your operating system, distribution, and the LiVES version (2.2.8) and any information shown below: #0 0x7fb3543974c9 in __libc_waitpid (pid=873, stat_loc=stat_loc@entry=0x7ffefeee664c, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:40 #1 0x7fb357057433 in g_on_error_stack_trace (prg_name=0x1104700 /usr/lib/lives/lives-exe) at /tmp/buildd/glib2.0-2.44.1/./glib/gbacktrace.c:252 #2 0x0041ecd8 in () #3 0x7fb3543978d0 in signal handler called () #4 0x7fb35400d107 in __GI_raise (sig=sig@entry=6) #5 0x7fb35400e4e8 in __GI_abort () at abort.c:89 #6 0x7fb3570a7b55 in g_assertion_message (domain=domain@entry=0x7fb358d4b527 Gtk, file=file@entry=0x7fb358d9b2b0 /build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c, line=line@entry=609, func=func@entry=0x7fb358d9b4b7 tick_cb, message=message@entry=0x2a47ec0 assertion failed: (priv-pulse2 priv-pulse1)) at /tmp/buildd/glib2.0-2.44.1/./glib/gtestutils.c:2356 #7 0x7fb3570a7bea in g_assertion_message_expr (domain=0x7fb358d4b527 Gtk, file=0x7fb358d9b2b0 /build/gtk+3.0-8FBlWQ/gtk+3.0-3.16.4/./gtk/gtkprogressbar.c, line=609, func=0x7fb358d9b4b7 tick_cb, expr=optimized out) #8 0x7fb358c1ae6e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #9 0x7fb358d0cf44 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #10 0x7fb357358504 in _g_closure_invoke_va (closure=0x145aec0, return_value=0x0, instance=0x11052c0, args=0x7ffefeee70c8, n_params=optimized out, param_types=0x0) at /tmp/buildd/glib2.0-2.44.1/./gobject/gclosure.c:831 #11 0x7fb357371fa7 in g_signal_emit_valist (instance=instance@entry=0x11052c0, signal_id=signal_id@entry=139, detail=detail@entry=0, var_args=var_args@entry=0x7ffefeee70c8) at /tmp/buildd/glib2.0-2.44.1/./gobject/gsignal.c:3214 #12 0x7fb357372e4a in g_signal_emit_by_name (instance=0x11052c0, detailed_signal=0x7fb358792414 update) #13 0x7fb35872c3bc in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #14 0x7fb35871bcf8 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #15 0x7fb3570825e3 in g_timeout_dispatch (source=0x154f690, callback=optimized out, user_data=optimized out) #16 0x7fb357081b4d in g_main_context_dispatch (context=0x10bd3f0) #17 0x7fb357081b4d in g_main_context_dispatch (context=context@entry=0x10bd3f0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #18 0x7fb357081f20 in g_main_context_iterate (context=context@entry=0x10bd3f0, block=block@entry=0, dispatch=dispatch@entry=1, self=optimized out) #19 0x7fb357081fcc in g_main_context_iteration (context=0x10bd3f0, may_block=0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3869 #20 0x0041d531 in () #21 0x004b6b34 in () #22 0x00423b74 in () #23 0x00424b3f in () #24 0x7fb357081b4d in g_main_context_dispatch (context=0x10bd3f0) #25 0x7fb357081b4d in g_main_context_dispatch (context=context@entry=0x10bd3f0) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3737 #26 0x7fb357081f20 in g_main_context_iterate (context=0x10bd3f0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) #27 0x7fb357082242 in g_main_loop_run (loop=0x11046a0) #28 0x7fb358bc6a85 in gtk_main () #29 0x00417421 in main () -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lives depends on: ii frei0r-plugins1:1.4-dmo4 ii imagemagick 8:6.8.9.9-5 ii libasound21.0.28-1 ii libatk1.0-0
Bug#788904: systemd fails to activate vg on crypt device after upgrade to 215-17+deb8u1
close 788904 thanks On 2015-06-16 00:19, Michael Biebl wrote: Am 16.06.2015 um 08:12 schrieb Michael Biebl: Am 16.06.2015 um 06:35 schrieb David Mohr: I have a crypto device which I use as a physical volume for LVM. After upgrading to systemd 215-17+deb8u1 my system fails to boot, because `vgchange -ay` is not run after the crypto device is set up (which [..] Please let me know if I can help to fix this, since I think that's a pretty bad regression. I assume you had 215-17 installed before the upgrade. Can you downgrade to that version again? The changes in 215-17+deb8u1 do not look like they could be related to your problem, but let's verify if the downgrade actually helps. downgrade both systemd and udev to be sure. Hm, I'm guessing it was a race condition... I tried several times and I couldn't reproduce the issue. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787367: Acknowledgement (udev: 220-2 does not create /dev/disk/by-uuid link (required for system mounting) for filesystem on a bcache device)
Forwarded: http://lists.freedesktop.org/archives/systemd-devel/2015-May/032610.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787322: bcache-tools: bcache array undetected by probe and does not appear in /dev/disk/by-uuid thus breaking boot
severity 787322 normal reassign 787322 udev merge 787322 787367 affects 787367 bcache-tools thanks Thanks Matthew for the report! Your analysis is correct (and thanks for providing a workaround). See the patch that I included in #787367 if you want to fix udev. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786941: lmbench: config-run writes and results uses config file in /usr/lib
Package: lmbench
Version: 3.0-a9-1.1
Severity: important
Tags: patch
Dear Maintainer,
patches/02_paths.dpatch doesn't update config-run and results correctly,
from config-run:
C=${BINDIR}/bin/$OS/`${SCRIPTSDIR}/config`
which means the config file gets written to /usr/lib/lmbench...
lmbench-run uses a sensible location, so I moved that path into
$BIN_DIR/config, and updated lmbench-run, config-run and results
accordingly.
Please see the attached patch which updates 02_paths.
Sorry about the git noise, but this is too annoying manually (maybe
quilt would be a better option than dpatch?)
Thanks,
~David
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lmbench depends on:
ii gcc 4:4.9.2-4
ii libc6 2.19-18
ii libc6-dev [libc-dev] 2.19-18
ii perl 5.20.2-6
Versions of packages lmbench recommends:
ii lmbench-doc 3.0-a9-1.1
lmbench suggests no packages.
-- no debconf information
diff --git a/lmbench-run b/lmbench-run
index c699897..fc9b211 100644
--- a/lmbench-run
+++ b/lmbench-run
@@ -10,7 +10,7 @@ SCRIPTSDIR=$BINDIR/scripts
RESULTSDIR=$DATADIR/results
SRCDIR=$SHAREDIR/src
export SHAREDIR DATADIR BINDIR SCRIPTSDIR RESULTSDIR SRCDIR
-CONFIG=$DATADIR/config/`$SCRIPTSDIR/config`
+CONFIG=`$SCRIPTSDIR/config`
runuid=`id -u`
diff --git a/patches/02_paths.dpatch b/patches/02_paths.dpatch
index be7a4b9..04b542e 100755
--- a/patches/02_paths.dpatch
+++ b/patches/02_paths.dpatch
@@ -5,9 +5,25 @@
## DP: No description.
@DPATCH@
-diff -urNad lmbench-3.0~/lmbench-3.0-a9/scripts/config-run lmbench-3.0/lmbench-3.0-a9/scripts/config-run
lmbench-3.0~/lmbench-3.0-a9/scripts/config-run 2005-09-04 05:04:28.0 -0600
-+++ lmbench-3.0/lmbench-3.0-a9/scripts/config-run 2006-03-21 17:50:36.0 -0700
+diff --git a/lmbench-3.0-a9/scripts/config b/lmbench-3.0-a9/scripts/config
+index b58cb60..2a50513 100755
+--- a/lmbench-3.0-a9/scripts/config
b/lmbench-3.0-a9/scripts/config
+@@ -1,7 +1,8 @@
+ #!/bin/sh
++DATADIR=/var/lib/lmbench
+
+ UNAME=`uname -n 2/dev/null`
+ if [ X$UNAME = X ]
+-then echo CONFIG
+-else echo CONFIG.$UNAME
++then echo $DATADIR/config/CONFIG
++else echo $DATADIR/config/CONFIG.$UNAME
+ fi
+diff --git a/lmbench-3.0-a9/scripts/config-run b/lmbench-3.0-a9/scripts/config-run
+index f620c15..b20252a 100755
+--- a/lmbench-3.0-a9/scripts/config-run
b/lmbench-3.0-a9/scripts/config-run
@@ -3,7 +3,10 @@
# Configure parameters for lmbench.
# %I% %E% %@%
@@ -20,7 +36,7 @@ diff -urNad lmbench-3.0~/lmbench-3.0-a9/scripts/config-run lmbench-3.0/lmbench-3
L='='
echo $L;
catEOF;
-@@ -36,20 +39,20 @@
+@@ -132,20 +135,20 @@ export LMBENCH_SCHED
echo $L; echo ;
echo Hang on, we are calculating your timing granularity.
@@ -47,7 +63,7 @@ diff -urNad lmbench-3.0~/lmbench-3.0-a9/scripts/config-run lmbench-3.0/lmbench-3
export LOOP_O
echo OK, it looks like your benchmark loop costs $LOOP_O usecs.
echo
-@@ -164,7 +167,7 @@
+@@ -177,7 +180,7 @@ then
fi
if [ X$MB = X ]
then $ECHON Probing system for available memory: $ECHOC
@@ -56,7 +72,7 @@ diff -urNad lmbench-3.0~/lmbench-3.0-a9/scripts/config-run lmbench-3.0/lmbench-3
fi
TOTAL_MEM=$MB
MB=`echo \( $MB \* 7 \) / 10 | bc 2/dev/null`
-@@ -192,9 +195,9 @@
+@@ -205,9 +208,9 @@ fi
# Certain machines tend to barf when you try and bcopy 8MB.
# Figure out how much we can use.
echo Checking to see if you have $MB MB; please wait for a moment...
@@ -69,7 +85,7 @@ diff -urNad lmbench-3.0~/lmbench-3.0-a9/scripts/config-run lmbench-3.0/lmbench-3
if [ `expr $SYNC_MAX \* $MB` -gt `expr $TOTAL_MEM` ]
then
MB=`expr $TOTAL_MEM / $SYNC_MAX`
-@@ -210,8 +213,8 @@
+@@ -223,8 +226,8 @@ then echo Warning: you have only ${MB}MB available memory.
fi
echo Hang on, we are calculating your cache line size.
@@ -80,7 +96,7 @@ diff -urNad lmbench-3.0~/lmbench-3.0-a9/scripts/config-run lmbench-3.0/lmbench-3
export LINE_SIZE
echo OK, it looks like your cache line is $LINE_SIZE bytes.
echo
-@@ -459,7 +462,7 @@
+@@ -479,7 +482,7 @@ EOF
then
for i in $disks
do if [ -r $i ]
@@ -89,7 +105,7 @@ diff -urNad lmbench-3.0~/lmbench-3.0-a9/scripts/config-run lmbench-3.0/lmbench-3
if [ $? -eq 1 ]
then echo Must be root to run disk benchmarks.
echo Root is needed to flush the buffer cache
-@@ -564,7 +567,7 @@
+@@ -584,7 +587,7 @@ fi
echo $L
echo
echo Calculating mhz, please wait for a moment...
@@ -98,7 +114,7 @@ diff -urNad
Bug#774797: initramfs-tools: Include bcache.ko by default
severity 774797 wishlist retitle 774797 bcache support in the installer (most importantly include bcache.ko) thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774797: initramfs-tools: Include bcache.ko by default
Sorry for getting back so late on this issue. On 2015-01-07 11:46, Andreas Kloeckner wrote: I'm therefore suggesting that at the very least bcache.ko (and perhaps also bcache-tools) should be made part of the default initramfs image. I totally agree. /usr/share/initramfs-tools/hooks: bcache This file exists on your system and does install bcache.ko into the initrd: % lsinitramfs /boot/initrd.img-3.16.0-4-amd64 | grep bcache lib/modules/3.16.0-4-amd64/kernel/drivers/md/bcache lib/modules/3.16.0-4-amd64/kernel/drivers/md/bcache/bcache.ko lib/modules/3.16.0-4-amd64/kernel/fs/mbcache.ko lib/udev/probe-bcache lib/udev/rules.d/69-bcache.rules lib/udev/bcache-register Maybe the initramfs somehow did not get updated on your system? ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774797: initramfs-tools: Include bcache.ko by default
On 2015-05-02 16:58, Andreas Kloeckner wrote: That does exist, and it appears to be doing its job, but it comes from the bcache-tools package. That's not entirely what I'm talking about though. I'm more concerned about an annoying bootstrap issue that I've faced multiple times when installing Debian onto a bcache volume. Here's what I currently have to do: - Format as bcache using some live system - Reboot into d-i. - From within the debian installer, unpack bcache.ko out of the installer's kernel .deb, insmod it. - Register the bcache, install to it. - Reboot into the new system. Oops, boot fails, because there's no bcache.ko. Back to a live system, drop the right bcache.ko into /boot, reboot, insmod it, register the bcache, boot. (*) - Then install bcache-tools, and things start looking up. (*) This step is the most annoying, and what I'd like to see fixed. Alternatively, if d-i understood that I'm installing onto bcache and installed bcache-tools, my problem would also be solved... Ah, yes, so it's all about the installer. That was not obvious to me from the original bug report. Ideally I'd like to see full installer support but I don't know how much effort is involved. It is something that has been on my personal TODO list, and will get tackled sometimes now that jessie is out of the door. Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770283: debugging 32bit crashes (or lack thereof)
Hi, unfortunately I don't have any good ideas of debugging these 32bit issues. Since it seems to be an issue in how xfburn uses gtk, it won't be easy to find. Some of the gtk code is pretty messy, I admit that, but cleaning it up is a major project. And right now for a lack of time, and small number of 32bit users, I don't think it'll happen. I hate to say that, but it's the realistic answer right now. Thomas, thanks as always for your time to get to the root of the problem! I very much appreciate it. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780319: major regression
Hi, I would like to add that with initramfs-tools 0.116 and lvm2 2.02.111-2 the following fstab entry was mounted just fine during boot when using systemd: /dev/vg0/usr/usrxfs rw,relatime,nodev 0 2 This is a really annoying regression for us. I'm wondering if there would be issue to resolve the /dev/VG/LV path into exactly those components, and then to run the vgchange. After all, this is a valid path in /dev in a running system. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780481: grub2-common: next_entry is not reset in grubenv on boot
Package: grub2-common
Version: 2.02~beta2-21
Severity: minor
Dear Maintainer,
grub-reboot sets next_entry in /boot/grub/grubenv. Usually this variable
is reset on boot, but that has not been happening for a while now. I
think it's related to uefi, because on my jessie laptop it seems to work
fine with grub2-pc.
When I use grub-reboot I expect to only boot into the selection _once_,
and not every time.
Thanks,
~David
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/dm-0 / ext4 rw,noatime,discard,errors=remount-ro,commit=30,data=ordered 0 0
/dev/sdb3 /boot/efi vfat
rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro
0 0
/dev/mapper/vg0-libvirtimg /var/lib/libvirt/images jfs rw,relatime 0 0
/dev/bcache0 /home ext4 rw,noatime,discard,commit=15,data=ordered 0 0
/dev/bcache0 /srv/torrents ext4 rw,noatime,discard,commit=15,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/disk/by-id/ata-ST2000DL003-9VT166_5YD10B5A
(hd1) /dev/disk/by-id/ata-Zalman_S64GB_WWW--E94
(hd2) /dev/disk/by-id/ata-ST1500DL003-9VT16L_5YD20TRG
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ ${next_entry} ] ; then
set default=${next_entry}
set next_entry=
save_env next_entry
set boot_once=true
else
set default=${saved_entry}
fi
if [ x${feature_menuentry_id} = xy ]; then
menuentry_id_option=--id
else
menuentry_id_option=
fi
export menuentry_id_option
if [ ${prev_saved_entry} ]; then
set saved_entry=${prev_saved_entry}
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z ${boot_once} ]; then
saved_entry=${chosen}
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod lvm
insmod ext2
set
root='lvmid/RjKUeG-3qSL-cf1a-2b02-cogH-Lb2z-GiqBSZ/yZguv8-E0Jc-baGj-xCQA-9Lwo-Smnl-RVY6fL'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='lvmid/RjKUeG-3qSL-cf1a-2b02-cogH-Lb2z-GiqBSZ/yZguv8-E0Jc-baGj-xCQA-9Lwo-Smnl-RVY6fL'
271eabf2-2806-4cab-a250-0d9db82b877a
else
search --no-floppy --fs-uuid --set=root 271eabf2-2806-4cab-a250-0d9db82b877a
fi
font=/usr/share/grub/unicode.pf2
fi
if loadfont $font ; then
set gfxmode=1024x768
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ ${recordfail} = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/02_custom_uefi ###
insmod efi_gop
insmod efi_uga
insmod font
if loadfont ${prefix}/unicode.pf2
then
insmod gfxterm
set gfxmode=auto
set gfxpayload=keep
#set gfxpayload=text # no effect on NVRM error, and no console output
terminal_output gfxterm
fi
### END /etc/grub.d/02_custom_uefi ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod lvm
insmod ext2
set
root='lvmid/RjKUeG-3qSL-cf1a-2b02-cogH-Lb2z-GiqBSZ/yZguv8-E0Jc-baGj-xCQA-9Lwo-Smnl-RVY6fL'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='lvmid/RjKUeG-3qSL-cf1a-2b02-cogH-Lb2z-GiqBSZ/yZguv8-E0Jc-baGj-xCQA-9Lwo-Smnl-RVY6fL'
271eabf2-2806-4cab-a250-0d9db82b877a
else
search --no-floppy --fs-uuid --set=root 271eabf2-2806-4cab-a250-0d9db82b877a
fi
insmod png
if background_image /usr/share/images/desktop-base/lines-grub-1920x1080.png;
then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload=${1}
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
--class os $menuentry_id_option
'gnulinux-simple-271eabf2-2806-4cab-a250-0d9db82b877a' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod lvm
insmod ext2
set
Bug#779153: Packaged php 5.4.38
Hi, please consider reviewing my packaging: http://de.mcbf.net/~squisher/debian/php/php5_5.4.38-0.dsc A couple of patches seem to have been adopted upstream, and I had to add one minor fix for the crypt config.m4. Thank you for your hard work! ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779153: php5: Please package new upstream version 5.4.38 because of CVE-2015-0273
Package: php5 Version: 5.4.36-0+deb7u3 Severity: normal Dear Maintainer, I'm a little concerned that there doesn't seem to be much activity to package php 5.4.38 which came out with the following announcement about a week ago: This release fixes several bugs and addresses CVE-2015-0235 and CVE-2015-0273. All PHP 5.5 users are encouraged to upgrade to this version. This affects squeeze as well, but I have no idea if a patch is available for 5.3. https://security-tracker.debian.org/tracker/CVE-2015-0273 Is there a particular reason for this delay? Thanks, ~David -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.12.20-x86_64-jb1 (SMP w/3 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages php5 depends on: ii libapache2-mod-php5 5.4.36-0+deb7u3 ii php5-common 5.4.36-0+deb7u3 ii php5-fpm 5.4.36-0+deb7u3 php5 recommends no packages. php5 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#767569: systemd - please update documentation
Hi, I think that's because now systemd is used and smartmontools ships with a .service file instead of relying on the LSB compatibility layer. My guess all that is required is to correct README.Debian and place some notice into /etc/default/smartmontools. I do wonder though: was it intentional that now smartd is enabled by default, whereas it was disabled by default pre-systemd? Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774643: verify_active_connections is not present in ruby-activerecord 4.1.8
On 2015-02-02 20:11, micah wrote:
David Mohr b...@da.mcbf.net writes:
Is noone using puppet in jessie with storeconfigs? That seems really
odd
to me...
Unfortunately, all my puppet recipes are on nothing newer than wheezy
right now, and need some serious tending to before they can get to
using
the newer version so I haven't had the ability to test this out :o
It doesn't matter what kind of recipe you have. I tried it with a dummy
catalog and a random exec {} -- it will fail as soon as you set
storeconfigs = true
in puppet.conf
So it's fairly easy to reproduce. Btw the only suggestion I have
received from ask.puppetlabs.com is to downgrade the package :-(
~David
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774643: verify_active_connections is not present in ruby-activerecord 4.1.8
I'm also struggling to understand what the issue is. I need storedconfigs, but puppetdb is not packaged, and it seems that the version of activerecord in jessie is too new for puppet, because according to http://apidock.com/rails/ActiveRecord/Base/verify_active_connections!/class that method isn't available anymore. However, google doesn't return much at all about this problem. I asked about this at puppetlabs: http://ask.puppetlabs.com/question/15610/current-activerecords-breaks-puppet-with-storeconfigs/ (link currently awaiting moderation). Let's see if someone offers some insight! Is noone using puppet in jessie with storeconfigs? That seems really odd to me... Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774865: 5.7p3, epoch
Hi, thanks for getting the new version into experimental! However, there's already a new version released: http://openntpd.org/txt/release-5.7p3.txt Another question: why keep the YMD-Version scheme? I'd think it'd be better to increment epoch and use 1:5.7p3 ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773539: ifupdown: Please return exit status 1 when up command fails (unconfigured interface affects network-manager)
Package: ifupdown Version: 0.7.50 Severity: normal Dear Maintainer, please consider returning exit status 1 when the up command of an interface fails. Since the interface is not marked as configured, network-manager will think there is no connectivity and programs interacting with NM won't work (for example pidgin). My situation was that I wanted to turn on jumbo frames for my network bridge, and I mistakenly added the up commands in the wrong order: up ifconfig br0 mtu 9000 up ifconfig eth0 mtu 9000 Now on the next reboot network-manager thought I was offline. The reason for that was a little difficult to debug because systemd thought everything was just fine: no error was reported from /etc/init.d/networking. Since my computer boots up too fast to watch the initialization messages, I didn't notice the error there either. And I did not suspect ifup as the culprit because I did have a working network access. Yes, the man page mentions that this is expected behavior. But given that it is difficult to debug, and there is real breakage when network-manager is used, I think that it would be preferable to actually return an error. Thanks, ~David -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifupdown depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-58 ii iproute 1:3.16.0-2 ii iproute2 3.16.0-2 ii libc62.19-13 ii lsb-base 4.1+Debian13+nmu1 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.1-5 Versions of packages ifupdown suggests: ii net-tools 1.60-26+b1 ii ppp2.4.6-3 pn rdnssd 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#769612: unblock: bcache-tools/1.0.7-1
On 2014-12-03 14:56, Jack Douglas wrote: I appreciate your additional input, but I'm afraid it doesn't persuade me to change my mind. If the maintainer is on the ball, it could be in jessie- backports very soon after release. That's a very gracious reply, and I'm grateful that you gave it further consideration even if the answer remains no :) I second that, and thank you Jack for the help. Let's shoot for a quick upload to jessie-backports! ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729924: Ping
Hi, I just wanted to say that this is an active issue for me. I am developing code in Python 3, and python-mode etc don't work when started with Python 2 since then they don't recognize the Python 3 syntax. While Python 2 is still in widespread use, Python 3 usage is rising and it is a shame that vim can't handle it out of the box. I don't have time to actively work on this issue, but I'd be more than happy to test any patches. Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767257: grub-choose-default: Please upgrade to upstream version 1.1
Package: grub-choose-default Version: 1.1-1 Severity: wishlist Dear Maintainer, please upgrade to the newer upstream version 1.1 which supports grub2 (which would close #714276). I can help with the packaging if required. Thanks! ~David -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages grub-choose-default depends on: ii libatk1.0-0 2.14.0-1 ii libc62.19-12 ii libcairo21.14.0-2 ii libfontconfig1 2.11.0-6.1 ii libfreetype6 2.5.2-2 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-0 2.42.0-2 ii libgtk2.0-0 2.24.25-1 ii libpango-1.0-0 1.36.8-2 ii libpangocairo-1.0-0 1.36.8-2 ii libpangoft2-1.0-01.36.8-2 Versions of packages grub-choose-default recommends: ii grub-efi 2.02~beta2-15 grub-choose-default 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#762036: nut-nutrition: File conflict with nut-nutrition-data on upgrade
Package: nut-nutrition Version: 20.1-1 Severity: important Dear Maintainer, I just ran a dist-upgrade and it fails on nut-nutrition-data: Selecting previously unselected package nut-nutrition-data. Preparing to unpack .../nut-nutrition-data_20.1-1_all.deb ... Unpacking nut-nutrition-data (20.1-1) ... dpkg: error processing archive /var/cache/apt/archives/nut-nutrition-data_20.1-1_all.deb (--unpack): trying to overwrite '/usr/share/nut-nutrition/WEIGHT.lib', which is also in package nut-nutrition 19.2-1 Of course there is an easy workaround: $ dpkg -r nut-nutrition apt-get install nut-nutrition Thanks, ~David -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nut-nutrition depends on: ii libc6 2.19-11 ii nut-nutrition-data 20.1-1 nut-nutrition recommends no packages. nut-nutrition 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#708132: bcache-tools ITP
About the licensing copyright: I emailed Gabriel and Kent Overstreet on 2014-06-02 but did not get a reply. I admit though that I didn't follow up afterwards. On 2014-09-17 05:55, Robie Basak wrote: As far as I know this is the status of the git trees: 1) http://evilpiepirate.org/git/bcache-tools.git Original sources, no changes in a while. 2) git://github.com/g2p/bcache-tools.git First clone by Gabriel, contains work and bugfixes to the bcache-tools userland and some initial Debian packaging. 3) git://github.com/squisher/bcache-tools.git My work on Debian packaging. I set Vcs-Git to g2p's version instead of mine because that seems to be the most active upstream repository. I thought this was relevant for uscan, but obviously I was wrong (as was pointed out on mentors.debian.net). 4) git://github.com/basak/bcache-tools.git Vcs-Git points to 2 (g2p). I also noted that the github branches seem to contain commits to the upstream source, too, that aren't present in the upstream repository (1). I thought that (1) is historic at this point and considered (2) the upstream. I did not verify that though. I would suggest to co-maintain the package on https://alioth.debian.org/projects/collab-maint I think it would be easiest to upload, since I think it's good to go and this will at least result in a definitive packaging state that we can work from. Fine by me. In the meantime, I think branch 3 contained everything, so I cloned that one to add my two commits. To keep Vcs-Git correct g2p should pull my commits, or else we can change Vcs-Git. Right, see above. So in summary: 1) Define and agree maintainers. I'd like to get my feet wet and co-maintain, if you're interested. 2) g2p to pull my commits, or we agree to change Vcs-Git, or we drop Vcs-Git for now. I'd say point it at 3) or at collab-maint, if that's where the packaging ends up being. 3) Upload. Either my colleague (James Page) can do it as he's already reviewed the packaging itself, or someone else. Let me know if there are any objections to James uploading. Bernd Zeimetz, I added him to the CC, was willing to sponsor the package once it was ready. But since he has been pretty busy recently, I don't think he'll object to James uploading. I definitely don't; it'd be awesome to get this finally into the official repository! 4) Sort out which trees are canonical upstream and packaging branches, and push all commits to those places. I very much agree. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#484974: ntpdate's ip-up script runs even for virtual interfaces
Package: ntpdate Version: 1:4.2.6.p5+dfsg-3.1 Followup-For: Bug #484974 Dear Maintainer, I also think this is a problem, specially on hosts with a lot of alias interfaces. This may possibly be related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=647465 and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649692 I attached a patch to fix it. Thanks, ~David -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ntpdate depends on: ii dpkg 1.17.13 ii libc62.19-10 ii libssl1.0.0 1.0.1i-2 ii netbase 5.2 Versions of packages ntpdate recommends: ii lockfile-progs 0.1.17 ntpdate suggests no packages. -- no debconf information --- /etc/network/if-up.d/ntpdate~ 2014-09-02 18:01:01.0 +0200 +++ /etc/network/if-up.d/ntpdate2014-09-02 18:50:34.0 +0200 @@ -16,6 +16,11 @@ exit 0 fi +# Check if an alias interface is being brought up. If so, don't do anything. +if echo $IFACE | grep -q : ; then + exit 0 +fi + # Check whether ntpdate was removed but not purged; it's useless to wait for # it in that case. if [ ! -x /usr/sbin/ntpdate-debian ] [ -d /usr/sbin ]; then
Bug#484974: #484974
tag 484974 patch thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708132: bcache-tools ITP
Hi Robie, thanks for checking in! It's good to know there is interest. I think I have the package in pretty good shape, see https://github.com/squisher/bcache-tools/tree/debian-mentors . Bernd (bzed) was the sponsor for when Gabriel uploaded to mentors. That's not visible anymore because the package was once removed due to inactivity. He is still willing to sponsor the package, but has been pretty busy as of lately. My current hung-up is that I'm fighting with a smart card setup on sid to do the signing since the reader in my lenovo turned out to be flaky. So the version on debian-mentors is lacking some improvements which you can see on github. So my current todo is: 1. get gpg to work with my smartcard 2. get a collab-maint account 3. upload new version to mentors Lintian is pretty happy, and it's not a particularly complicated package, so I think once I get 1. out of the way, the rest should move more quickly. I'm open to co-maintaining, if anyone wants to jump in and help. ~David P.S. I'll forward this to bzed so that he can chime in if need be. On 2014-05-30 09:57, Robie Basak wrote: Gabriel, David, I'd like to help with getting this package into Debian. What is this waiting on right now, please, and how can I help speed things up? I'd also like to see bcache-tools in Ubuntu, and I see that Gabriel is already maintaining a PPA on Launchpad. I am not a DD (but can poke several), but I can sponsor packages into Ubuntu. I can upload to Ubuntu ahead of a Debian upload if things are held up at the Debian end, but I'd prefer to see the package going in via Debian. I see a recent upload to mentors by David. Is this currently a candidate for upload, or there more work to be done? Do you need a sponsor, or do you have someone looking it already? On a separate (not-really-Debian) note, it'd be great to see somebody maintaining bcache-tools stable releases in Ubuntu for bugfixes and so on. Gabriel (or anyone else), if you're interested, I'd be happy to sponsor these or otherwise coordinate against your PPA with you, rather than step on your toes. Robie -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748253: aspell-de fails to install because /var/lib/aspell doesn't exist
Package: aspell-de Version: 20131206-3 Severity: grave Justification: renders package unusable Dear Maintainer, I'm upgrading aspell-de from 20131206-2 to 20131206-3 and get the following error message: % sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 52 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up aspell-de (20131206-3) ... /var/lib/dpkg/info/aspell-de.postinst: 58: /var/lib/dpkg/info/aspell-de.postinst: cannot create /var/lib/aspell/de.compat: Directory nonexistent dpkg: error processing package aspell-de (--configure): subprocess installed post-installation script returned error exit status 2 Processing triggers for dictionaries-common (1.23.2) ... Errors were encountered while processing: aspell-de E: Sub-process /usr/bin/dpkg returned an error code (1) ~David -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aspell-de depends on: ii aspell 0.60.7~20110707-1 ii dictionaries-common 1.23.2 aspell-de recommends no packages. aspell-de 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#748253: aspell-de fails to install because /var/lib/aspell doesn't exist
Hi Roland, On 2014-05-15 10:24, Roland Rosenfeld wrote: On Thu, 15 May 2014, David Mohr wrote: Package: aspell-de Version: 20131206-3 Severity: grave Justification: renders package unusable I'm upgrading aspell-de from 20131206-2 to 20131206-3 and get the following error message: /var/lib/dpkg/info/aspell-de.postinst: 58: /var/lib/dpkg/info/aspell-de.postinst: cannot create /var/lib/aspell/de.compat: Directory nonexistent You're right, there is a problem when you have no other aspell dictionary package installed and upgrade from older aspell-de versions to 20131206-3. I'll try to fix this soon (seems to be necessary to create /var/lib/aspell in postinst and not only preinst, since it would otherwise be removed when the old aspell-de package is removed). As a quick work around just install aspell-de again, this should work without a problem (at least on my system). Installing aspell-en also fixed it; I guess because I didn't have it installed before. Danke, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745588: ITP: grub-choose-default -- A GUI for easily changing the default in grub2
Package: wnpp Severity: wishlist Owner: David Mohr b...@da.mcbf.net * Package name: grub-choose-default Version : 1.1 Upstream Author : David Mohr da...@mcbf.net * URL : http://de.mcbf.net/david/grubchoosedefault/ * License : GPL Programming Lang: C Description : A GUI for easily changing the default in grub2 A GUI for changing the default for grub2, either permanently or for the next reboot only. It is specially useful for making one time excursion to another OS and safely returning to the Debian homeland on the next reboot. It can be considered a GUI version of grub-set-default and grub-reboot. I think it is feasible to maintain this package by myself: I am the author, the package is fairly simple, and the grub config is not likely to change frequently. A while back I published Ubuntu packages at https://launchpad.net/~bugs-da/+archive/grub-choose-default/ which I would use as a basis for the Debian packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691151: CC
[I reopened the bug, but I didn't realize I had to explicitly cc to have my reasoning be accessible, sorry] Even if the mounts are equivalent at the kernel level, there certainly is information lost compared to the mtab in squeeze: namely where within the filesystem the bind mount originates. Example: david@feline:~/ mount | grep '/home ' /dev/mapper/vghs-home on /home type ext4 (rw) david@feline:~/ sudo mount -o bind /home/david/tmp /mnt david@feline:~/ cat /proc/mounts | grep 'vghs-home' /dev/mapper/vghs-home /home ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 /dev/mapper/vghs-home /mnt ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0 The 2nd entry is for the bind mount. In squeeze the mtab contained: /home/david/tmp on /mnt type none (rw,bind) So how do I figure out that /mnt refers to '/tmp' inside the device /dev/mapper/vghs-home in wheezy? Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714298: python-pyhyphen: Example from the README fails to work
Package: python-pyhyphen Version: 1.0~beta1-2 Severity: important Dear Maintainer, please run this short script, adapted from the README, which fails to work. #!/usr/bin/env python from hyphen import Hyphenator from hyphen.dictools import * import traceback for lang in ['de_DE', 'fr_FR', 'en_UK', 'ru_RU']: try: if not is_installed(lang): install(lang) except OSError, e: print traceback.format_exc() install(lang) #EOF I get the following output: % ./pyhyphen-test.py Traceback (most recent call last): File ./pyhyphen-test.py, line 9, in module if not is_installed(lang): File /usr/lib/python2.7/dist-packages/hyphen/dictools.py, line 29, in is_installed return (language in list_installed(directory)) File /usr/lib/python2.7/dist-packages/hyphen/dictools.py, line 19, in list_installed return [d[5:-4] for d in os.listdir(directory) OSError: [Errno 2] No such file or directory: '$path' Traceback (most recent call last): File ./pyhyphen-test.py, line 13, in module install(lang) File /usr/lib/python2.7/dist-packages/hyphen/dictools.py, line 48, in install s = urllib2.urlopen(url).read() File /usr/lib/python2.7/urllib2.py, line 127, in urlopen return _opener.open(url, data, timeout) File /usr/lib/python2.7/urllib2.py, line 396, in open protocol = req.get_type() File /usr/lib/python2.7/urllib2.py, line 258, in get_type raise ValueError, unknown url type: %s % self.__original ValueError: unknown url type: $repohyph_de_DE.dic Thanks, ~David -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages python-pyhyphen depends on: ii libc6 2.17-5 ii python 2.7.5-2 ii python2.6 2.6.8-2 ii python2.7 2.7.5-6 python-pyhyphen recommends no packages. python-pyhyphen suggests no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610214: mumble - Segmentation fault on first startup
Package: mumble Version: 1.2.3-349-g315b5f5-2.2 Followup-For: Bug #610214 Dear Maintainer, I don't use mumble on Linux very frequently, but just a week or two ago it was working and now I get the crash on start-up. I have the same behavior as previous reporters with strace and gdb: in both those cases there is no crash. But I can get a backtrace (attached below). Note that I'm using pulseaudio, and not alsa. I get the same crash whether I have an existing configuration file (with pulse configured) or not. ~David % gdb mumble core GNU gdb (GDB) 7.6-debian Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/bin/mumble...Reading symbols from /usr/lib/debug/usr/bin/mumble...done. done. [New LWP 729] [New LWP 730] warning: Could not load shared library symbols for linux-vdso.so.1. Do you need set solib-search-path or set sysroot? [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff91a0 Core was generated by `mumble'. Program terminated with signal 11, Segmentation fault. #0 0x7fa93b412410 in snd_config_iterator_next () from /usr/lib/x86_64-linux-gnu/libasound.so.2 (gdb) bt #0 0x7fa93b412410 in snd_config_iterator_next () from /usr/lib/x86_64-linux-gnu/libasound.so.2 #1 0x7fa93b41d59c in snd_device_name_hint () from /usr/lib/x86_64-linux-gnu/libasound.so.2 #2 0x7fa93dae3fbf in ALSAEnumerator::ALSAEnumerator (this=0x7fa93eae7ee0) at ALSAAudio.cpp:192 #3 0x7fa93dae4764 in ALSAInit::initialize (this=optimized out) at ALSAAudio.cpp:94 #4 0x7fa93da3f3f9 in DeferInit::run_initializers () at Global.cpp:179 #5 0x7fa93d986dc9 in main (argc=1, argv=optimized out) at main.cpp:273 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mumble depends on: ii gconf2 3.2.6-1 ii libasound2 1.0.27.1-1 ii libavahi-client3 0.6.31-2 ii libavahi-common3 0.6.31-2 ii libavahi-compat-libdnssd1 0.6.31-2 ii libc6 2.17-5 ii libg15daemon-client1 1.9.5.3-8.2 ii libgcc11:4.8.1-3 ii libgl1-mesa-glx [libgl1] 9.1.3-6 ii libopus0 1.1~alpha+20130512-1 ii libprotobuf7 2.4.1-3 ii libpulse0 4.0-2 ii libqt4-dbus4:4.8.4+dfsg-4 ii libqt4-network 4:4.8.4+dfsg-4 ii libqt4-sql 4:4.8.4+dfsg-4 ii libqt4-sql-sqlite 4:4.8.4+dfsg-4 ii libqt4-svg 4:4.8.4+dfsg-4 ii libqt4-xml 4:4.8.4+dfsg-4 ii libqtcore4 4:4.8.4+dfsg-4 ii libqtgui4 4:4.8.4+dfsg-4 ii libsndfile11.0.25-5 ii libspeechd20.7.1-6.2 ii libspeex1 1.2~rc1-7 ii libspeexdsp1 1.2~rc1-7 ii libssl1.0.01.0.1e-3 ii libstdc++6 4.8.1-3 ii libx11-6 2:1.6.0-1 ii libxi6 2:1.6.1-1+deb7u1 ii lsb-release4.1+Debian12 Versions of packages mumble recommends: ii speech-dispatcher 0.7.1-6.2 Versions of packages mumble suggests: pn mumble-server 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#711153: mumble-server: Please package v1.2.4
Source: mumble-server Severity: wishlist Dear Maintainer, please consider packaging v1.2.4 which was released on June 2nd. I couldn't find a link to a source tarball, but there is a tag in git: https://github.com/mumble-voip/mumble.git Thank you very much! ~David -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676883: moreinfo
root@(none):/# ls -l total 64 drwxr-xr-x 2 nobody nogroup 4096 May 3 02:15 bin drwxr-xr-x 2 nobody nogroup 4096 May 3 02:16 boot drwxr-xr-x 14 root root2620 May 6 20:41 dev drwxr-xr-x 63 nobody nogroup 4096 May 3 02:16 etc drwxr-xr-x 2 nobody nogroup 4096 Dec 14 12:56 home lrwxrwxrwx 1 nobody nogroup 29 May 3 02:16 initrd.img - boot/initrd.img-3.2.0-4-amd64 drwxr-xr-x 13 nobody nogroup 4096 May 3 02:15 lib drwxr-xr-x 2 nobody nogroup 4096 May 3 02:14 lib64 drwxr-xr-x 2 nobody nogroup 4096 May 3 02:13 media drwxr-xr-x 2 nobody nogroup 4096 Dec 14 12:56 mnt drwxr-xr-x 2 nobody nogroup 4096 May 3 02:13 opt dr-xr-xr-x 56 root root 0 May 6 20:41 proc drwx-- 4 nobody nogroup 4096 May 6 20:05 root drwxr-xr-x 9 root root 320 May 6 20:41 run drwxr-xr-x 2 nobody nogroup 4096 May 3 02:15 sbin drwxr-xr-x 2 nobody nogroup 4096 Jun 10 2012 selinux drwxr-xr-x 2 nobody nogroup 4096 May 3 02:13 srv drwxr-xr-x 13 root root 0 May 6 20:41 sys drwxrwxrwt 2 nobody nogroup 4096 May 3 02:16 tmp drwxr-xr-x 10 nobody nogroup 4096 May 3 02:13 usr drwxr-xr-x 11 nobody nogroup 4096 May 3 02:13 var lrwxrwxrwx 1 nobody nogroup 26 May 3 02:16 vmlinuz - boot/vmlinuz-3.2.0-4-amd64 mount says: xx.xx.xx.6:/srv/fai/nfsroot on / type nfs4 (ro,relatime,vers=4,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=xx.xx.xx.24,minorversion=0,local_lock=none,addr=xx.xx.xx.6) The workaround /srv/nfs4 134.95.9.128/25(fsid=0,ro,no_subtree_check) works; that is nfs3 is used and now all directories are properly owned by root. It's too bad the rest of fai still fails ;-). ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#681248: pdns-server: Fatal error: Trying to set unexisting parameter 'gmysql-host'
I just wanted to chime in with my 2c: It is terrible to intentionally break a configuration on upgrade! When I do a fresh install, then it is common to do work to get the package running (nicely, or at all). I expect some degree of manual intervention. But on upgrade, when there aren't any significant upstream changes (not sure if that's entirely true for pdns squeeze-wheezy, but this change isn't dependent on upstream anyway) I _do_not_ expect to have to touch the configuration. I am always very grateful for Debian providing such great upgrade compatibility. That's why I agree with juha that this is a bad change. It will make many people unhappy when they upgrade pdns. Isn't there a way to conditionally include a conffile? The reference to the debian manual sounded like no though. If that really is the case, I could possibly write a patch for postinst, if there's a change to get it included. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632758: Previously unaffected drives now affected?
Hi, since this bug report is still open: If I recall correctly, Seagate previously reported that my drive was not affected, but now according to the serial # checker and the FAQ document, it is affected. Part Number:9BX154-303 Model Number:ST3500320ASFamily:BARRACUDA Barracuda 7200.11 Firmware Update Important SD1A11-Mar-11 - http://knowledge.seagate.com/articles/en_US/FAQ/207951en Since smartmontools (5.42+svn3561-3) correctly displayed the warning maybe this bug can be closed? Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#646625: autofs5: auto.net and -hosts do not handle nfs4 shares
Package: autofs
Version: 5.0.7-3
Followup-For: Bug #646625
Dear Maintainer,
I can confirm that this bug still exists and is fixed as the reported
described by the auto.net script in #533893.
Since I just wasted a bunch of time not only because of the misleading
nfs4 line in the existing auto.net script, but _also_ because of a
misleading MOUNT_NFS_DEFAULT_PROTOCOL option in /etc/defaults/autofs, I
fixed up auto.net to respect the afaik unused MOUNT_NFS_DEFAULT_PROTOCOL
option.
Thanks,
~David
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.6.0 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages autofs depends on:
ii libc6 2.13-35
ii libxml22.8.0+dfsg1-6
ii multiarch-support 2.13-35
ii ucf3.0025+nmu3
Versions of packages autofs recommends:
ii kmod 9-2
ii module-init-tools 9-2
ii nfs-common 1:1.2.6-3
autofs suggests no packages.
-- debconf-show failed
--- etc/auto.net~ 2012-11-06 01:28:05.573318889 -0700
+++ etc/auto.net 2012-11-06 11:58:36.118165043 -0700
@@ -11,36 +11,45 @@
# add nonstrict to make it OK for some filesystems to not mount
# choose one of the two lines below depending on the NFS version in your
# environment
-opts=-fstype=nfs,hard,intr,nodev,nosuid
-#opts=-fstype=nfs4,hard,intr,nodev,nosuid,async
-# Showmount comes in a number of names and varieties. showmount is
-# typically an older version which accepts the '--no-headers' flag
-# but ignores it. kshowmount is the newer version installed with knfsd,
-# which both accepts and acts on the '--no-headers' flag.
-#SHOWMOUNT=kshowmount --no-headers -e $key
-#SHOWMOUNT=showmount -e $key | tail -n +2
-
-for P in /bin /sbin /usr/bin /usr/sbin
-do
- for M in showmount kshowmount
+[ -f /etc/default/autofs ] . /etc/default/autofs
+
+if [ -z $MOUNT_NFS_DEFAULT_PROTOCOL -o $MOUNT_NFS_DEFAULT_PROTOCOL == 3 ]; then
+ # Showmount comes in a number of names and varieties. showmount is
+ # typically an older version which accepts the '--no-headers' flag
+ # but ignores it. kshowmount is the newer version installed with knfsd,
+ # which both accepts and acts on the '--no-headers' flag.
+ #SHOWMOUNT=kshowmount --no-headers -e $key
+ #SHOWMOUNT=showmount -e $key | tail -n +2
+
+ for P in /bin /sbin /usr/bin /usr/sbin
do
- if [ -x $P/$M ]
- then
- SMNT=$P/$M
- break
- fi
+ for M in showmount kshowmount
+ do
+ if [ -x $P/$M ]
+ then
+SMNT=$P/$M
+break
+ fi
+ done
done
-done
-[ -x $SMNT ] || exit 1
+ [ -x $SMNT ] || exit 1
+
+ # Newer distributions get this right
+ SHOWMOUNT=$SMNT --no-headers -e $key
-# Newer distributions get this right
-SHOWMOUNT=$SMNT --no-headers -e $key
+ $SHOWMOUNT | LC_ALL=C cut -d' ' -f1 | LC_ALL=C sort -u | \
+ awk -v key=$key -v opts=$opts -- '
+ BEGIN { ORS=; first=1 }
+ { if (first) { print opts; first=0 }; print \\\n\t $1, key : $1 }
+ END { if (!first) print \n; else exit 1 }
+ ' | sed 's/#/\\#/g'
+ opts=-fstype=nfs,hard,intr,nodev,nosuid
+else
+ # NFSv4
+ opts=-fstype=nfs4,hard,intr,nodev,nosuid,async
+
+ echo $opts $key:/
+fi
-$SHOWMOUNT | LC_ALL=C cut -d' ' -f1 | LC_ALL=C sort -u | \
- awk -v key=$key -v opts=$opts -- '
- BEGIN { ORS=; first=1 }
- { if (first) { print opts; first=0 }; print \\\n\t $1, key : $1 }
- END { if (!first) print \n; else exit 1 }
- ' | sed 's/#/\\#/g'
Bug#521178: fakeroot: doesn't work with ACLs
Hi, I would also like to see this issue fixed. I can confirm the bug on a squeeze host using a backported fakeroot 1.18.4-2 . The scenario where I find ACLs useful is a shared build host where several people have access. I set up default ACLs to give everyone write permissions, and now (in theory) everyone can build packages out of the same build tree without having to resort to something like sudo chown Example: $ fakeroot cp -p README README.copy cp: preserving permissions for `README.copy': Operation not supported $ getfacl README # file: README # owner: foo # group: foo user::rw- group::r-- group:src:rw- mask::rw- other::r-- $ getfacl README.copy # file: README.copy # owner: david # group: david user::rw- group::r-x #effective:r-- group:src:rwx #effective:rw- mask::rw- other::r-- Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667740: Comment
Hi, I just wanted to add that when this bug is triggered, unbound will work, but it will fail to correctly resolve dnssec secured domains. So unless you have special client support, it looks like these domains just don't resolve correctly which is very confusing. Ideas to resolve this bug: Run unbound-anchor with - NM - dhcpclient Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679515: Please apply
Dear Maintainers, it would be great if you could apply this small patch, since it solves a lot of headaches in HA setups. The problem only occurs under load, which means it's difficult to debug since it's not necessarily easy to reproduce. If you think that any sleeping by default is not acceptable, then just set the default to 0 in both files. At least people then have a hint that a sleep may be necessary. Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679515: iscsitarget: init script fails to wait before unloading module during stop
Package: iscsitarget
Version: 1.4.20.2-10
Severity: normal
Tags: patch
Hi,
on busy machines unloading the iscsitarget module is not immediately
possible after stopping the userspace daemon. The attached patch
introduces a flexible sleep time before unloading the module.
This is specially important on HA setups where open files may cause a
failover to fail.
Thanks,
~David
-- System Information:
Debian Release: 6.0.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages iscsitarget depends on:
ii libc6 2.11.3-2 Embedded GNU C Library: Shared lib
ii lsb-base3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii procps 1:3.2.8-9/proc file system utilities
Versions of packages iscsitarget recommends:
pn iscsitarget-modulenone (no description available)
Versions of packages iscsitarget suggests:
pn iscsitarget-dkms none (no description available)
pn iscsitarget-sourcenone (no description available)
--- a/debian/iscsitarget.init 2012-06-29 09:55:32.287495190 +
+++ b/debian/iscsitarget.init 2012-06-29 10:01:53.227992044 +
@@ -19,6 +19,7 @@
. /lib/lsb/init-functions # log_{warn,failure}_msg
ISCSITARGET_ENABLE=false
+ISCSITARGET_MAX_SLEEP=3
ISCSITARGET_DEFAULTS_FILE=/etc/default/iscsitarget
if [ -s $ISCSITARGET_DEFAULTS_FILE ]; then
. $ISCSITARGET_DEFAULTS_FILE
@@ -91,9 +92,17 @@
RETVAL=$?
if [ $RETVAL = 0 ] ; then
- log_daemon_msg Removing iSCSI enterprise target modules:
- modprobe -r iscsi_trgt
- RETVAL=$?
+ for i in $(seq $ISCSITARGET_MAX_SLEEP); do
+ log_daemon_msg Removing iSCSI enterprise target
modules:
+ # give iet some time to finish processing
+ sleep 1
+ modprobe -r iscsi_trgt
+ RETVAL=$?
+ if [ $RETVAL = 0 ]; then
+ break
+ fi
+ done
+
modprobe -r crc32c 2/dev/null
if [ $RETVAL = 0 ]; then
log_end_msg 0
--- a/debian/iscsitarget.default2012-06-29 09:58:10.215578518 +
+++ b/debian/iscsitarget.default2012-06-29 09:58:33.208716552 +
@@ -1,4 +1,5 @@
ISCSITARGET_ENABLE=false
+ISCSITARGET_MAX_SLEEP=3
# ietd options
Bug#653221: Does not find files after media_dir configuration change
On Mon, 2012-02-20 at 09:53 +0100, Benoît Knecht wrote: tag 653221 pending thanks David Mohr wrote: On Tue, 14 Feb 2012 16:40:30 +0100, Benoît Knecht wrote: David Mohr wrote: I also encountered this bug. At the very least, this should be mentioned in a README.Debian. This behavior is documented in minidlna.conf(5). IMHO, and this may not be completely according to the manual, README.Debian should make the users live easier. Sure it's in the man page, but wouldn't it be worth the small effort to make it easily accessible if that saves the average user some time? OK, so I've added a comment in the default minidlna.conf, warning users that changing media_dir should be followed by a complete rebuild of the database. Now they'd have to try pretty hard not to see this piece of information... That sounds like an excellent solution. Thank you for you effort! ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#653221: Does not find files after media_dir configuration change
Hi Benoît On Tue, 14 Feb 2012 16:40:30 +0100, Benoît Knecht wrote: Hi David, David Mohr wrote: I also encountered this bug. At the very least, this should be mentioned in a README.Debian. This behavior is documented in minidlna.conf(5). IMHO, and this may not be completely according to the manual, README.Debian should make the users live easier. Sure it's in the man page, but wouldn't it be worth the small effort to make it easily accessible if that saves the average user some time? I propose the following: Cache the values of media_dir in the init script so that on start-up -R can be run automatically when media_dir changes. Doesn't sound like a good fix to me, people who run minidlna manually will get a different behavior, which I think is bad. This issue has been reported here and upstream before (see #626835), but upstream marked it as invalid and I don't think it's worth patching for Debian. To me it'd be worth it to patch the init script, but you are right that it'd be better to tackle upstream. If I only had some time... It's actually 'force-reload'; you can also run 'minidlna -R' directly, or remove the database file by hand. Oops. Maybe that should go into a CC to the bug. Unless you have suggestions on improving the documentation, I will close this bug and merge it with #626835. Well, you didn't seem to like my suggestion ;-). Hence the case made above. Otherwise a merge is fine by me. Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660169: xfce4-settings: Setting keyboard layout broken
Package: xfce4-settings Version: 4.8.3-2 Severity: important Dear Maintainers, long time no see! An upgrade today broke the setting of keyboard layouts. My guess is libxklavier 5.1 - 5.2 is to blame. In .xsession-errors I see: Error:No Symbols named dvorak-alt-intl in the include file de Exiting Abandoning symbols file (null) Error:No Symbols named altgr-intl in the include file de Exiting Abandoning symbols file (null) These errors appear when I click on the different layouts in the keyboard settings. Some google revealed this check, which does seem fine (I have three layouts defined): % xprop -root | grep XKB _XKB_RULES_NAMES(STRING) = evdev, pc105, us,us,de, dvorak-alt-intl,altgr-intl,, Thanks, ~David -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xfce4-settings depends on: ii libc6 2.13-26 ii libcairo2 1.10.2-6.2 ii libdbus-1-3 1.4.18-1 ii libexo-1-0 0.6.2-3 ii libgdk-pixbuf2.0-0 2.24.1-1 ii libglib2.0-02.30.2-6 ii libgtk2.0-0 2.24.9-2 ii libnotify4 0.7.4-1 ii libpango1.0-0 1.29.4-2 ii libx11-62:1.4.4-4 ii libxcursor1 1:1.1.12-1 ii libxfce4ui-1-0 4.8.1-1 ii libxfce4util4 4.8.2-1 ii libxfconf-0-2 4.8.1-1 ii libxi6 2:1.4.5-1 ii libxklavier16 5.2-1 ii libxrandr2 2:1.3.2-2 ii xfconf 4.8.1-1 Versions of packages xfce4-settings recommends: ii x11-utils 7.6+4 ii xfce4-volumed 0.1.13-2+b1 xfce4-settings 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#653221: Does not find files after media_dir configuration change
Package: minidlna Version: 1.0.21+dfsg-1.1 Followup-For: Bug #653221 I also encountered this bug. At the very least, this should be mentioned in a README.Debian. I propose the following: Cache the values of media_dir in the init script so that on start-up -R can be run automatically when media_dir changes. To anyone reading this bug report, doing a force-restart on the init script will cause minidlna to rebuild the database and recognize new media_dir entries. Sincerely, David Mohr -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages minidlna depends on: ii adduser3.113+nmu1 ii gawk 1:3.1.8+dfsg-0.1 ii libavformat53 5:0.10-0.0 ii libavutil515:0.10-0.0 ii libc6 2.13-26 ii libexif12 0.6.20-2 ii libflac8 1.2.1-6 ii libid3tag0 0.15.1b-10 ii libjpeg8 8d-1 ii libogg01.2.2~dfsg-1 ii libsqlite3-0 3.7.9-3 ii libvorbis0a1.3.2-1.1 ii mawk 1.3.3-16 minidlna recommends no packages. minidlna suggests no packages. -- Configuration Files: /etc/minidlna.conf changed [not included] -- 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#559302: Merge with #354055 ?
Hi, I'm pretty sure this is the same bug as #354055 ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354055 ). Can someone please merge it? ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#592312: Note for using the debian config files with 0.4
Hi, with the squeeze freeze I manually upgraded to 0.4 but kept the debian configuration files around. It took me a while to debug why the upgrade test was failing, but then I found out that for 0.4 you have replace the include_once (...) call in db.inc.php by include (...) Just a note to anyone else upgrading. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#545896: Please apply patch
Hi, I can confirm both the problem and the patch while working with a squeeze system. Maintainer, please apply this patch already since it severely breaks heartbeat installations. Heartbeat uses the init scripts to monitor the state of the system services and (correctly) freaks out when receiving return codes that indicate errors. Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589738: iscsitarget: Stop tries to unload the module before ietd has finished exiting
Package: iscsitarget Version: 1.4.20.1-3 Severity: normal Tags: patch /etc/init.d/iscsitarget stop first shuts down ietd, then unloads the module. Unloading the module fails because the module is still in use for some reason. Sleeping briefly after quitting the daemon allows to reliably unload the module. See also the attached patch. ~David -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.34 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iscsitarget depends on: ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip ii procps1:3.2.8-9 /proc file system utilities Versions of packages iscsitarget recommends: ii iscsitarg 1.4.20.1-3+2.6.34-10.00.Custom iSCSI Enterprise Target module for Versions of packages iscsitarget suggests: ii iscsitarget-source1.4.20.1-3 iSCSI Enterprise Target kernel mod -- Configuration Files: /etc/default/iscsitarget changed [not included] /etc/iet/ietd.conf [Errno 13] Permission denied: u'/etc/iet/ietd.conf' /etc/init.d/iscsitarget changed [not included] -- no debconf information --- iscsitarget.orig2010-07-20 15:42:31.0 +0200 +++ iscsitarget 2010-07-20 15:45:32.0 +0200 @@ -84,6 +84,9 @@ fi # ugly, but pid file is not removed by ietd rm -f $PID_FILE + + # give ietd time to shut down, otherwise the module won't unload + sleep 1 # check if the module is loaded at all lsmod | grep -q iscsi_trgt
Bug#589738: Acknowledgement (iscsitarget: Stop tries to unload the module before ietd has finished exiting)
retitle Unloading the module during stop fails and the start of restart is not executed thanks I forgot to mention a crucial fact: Since the module unloading fails, the init script exits. This is bad when you're doing a restart: only the stopping part is performed, not the start part. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#559055: Please upload 2.2.0
Hi, I can only repeat the request to please upload the new release. Thank you! ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564133: xorg-server-core build failure also on 1.7.5.902
On Thu, Mar 18, 2010 at 4:44 PM, Brice Goglin brice.gog...@ens-lyon.org wrote: David Mohr wrote: Hi, I'm still getting the build failure for the xorg core on 1.7.5.902. LINK Xdmx /usr/bin/ld: ../../os/.libs/libos.a(backtrace.o): in function xorg_backtrace:../../os/backtrace.c:47: error: undefined reference to 'dladdr' collect2: ld returned 1 exit status Do you use binutils-gold ? Yes! I totally forgot about that, thanks for asking. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564133: xorg-server-core build failure also on 1.7.5.902
Hi, I'm still getting the build failure for the xorg core on 1.7.5.902. LINK Xdmx /usr/bin/ld: ../../os/.libs/libos.a(backtrace.o): in function xorg_backtrace:../../os/backtrace.c:47: error: undefined reference to 'dladdr' collect2: ld returned 1 exit status Can anyone help please? Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#564133: Still exists in 1.7.5-1
Hi, I'm encountering the same bug, but on the i386 arch. Any idea how to proceed? Obviously there are ways to build this package, since it is in the repository :-). Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#444837: Please include the patch for this bug
Hi, I just wanted to both confirm the problem, and that the patch works fine. I actually fixed the problem myself, and was about to submit the patch, when I found this report. (Obviously) it was exactly the same solution. It would be great if this could get included on the next update! Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549551:
Hi, I have also been following this bug. I think Steve wrote things down pretty nicely, just see one small comment below. On Sun, Nov 29, 2009 at 1:44 PM, Steve Dodier sidnio...@gmail.com wrote: [SNIP] Also, xscreensaver has a GUI for modifying some of these settings; Alright. But, be it a GUI or a CLI, an interface is meant to change settings *when it is used*, and certainly not to regularly change them again *in the background, without user consent*; You may not agree with me on this but I think pretty much everyone would. It sounds perfectly normal to me that when data used by an app changes, then the app has to adapt to these changes instead of bluntly reverting them to it's convenience. There can be incompatibilities between applications, but I think the actual problem here is that xscreensaver reverts the settings instead of changing it's own internal data to reflect external changes. I'd say the solution is much more simple - it would be nice if xscreensaver had an option, be it in the GUI, cli or compile-time only, to not touch DPMS settings. That should be much simpler to implement than any monitoring (which would have the race conditions mentioned earlier). It would be great for i.e. xfce users to see this implemented. They could continue to use the screensaver they trust, while being able to modify settings using tools from their DE. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556702: Patch submitted upstream
Hi, I submitted a patch upstream: http://bugzilla.xfce.org/show_bug.cgi?id=5996 ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556708: Patch submitted upstream
Hi, I submitted a patch upstream which fixes the problem: http://bugzilla.xfce.org/show_bug.cgi?id=5997 ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555849: Workaround
As a workaround you can delete ~/.config/deluge/ipc/deluge-gtk.lock, after which deluge should start again. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#542899: os-prober: please add a man page
Package: os-prober Version: 1.30 Severity: normal Please add a man page to os-prober. There is no help option, there is no documentation at all in /usr/share/doc, and it was very unclear to me if all it did was output the info on stdout, or also write something to disk so grub-pc can make use of it. Thanks. ~David -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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#520048: Apply the patch please?
I can confirm the bug, and that the patch is working. It'd be great to get it applied, because when I use rubber as a compile command in latex, it switches to the error location in rubber every time I run it... Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537322: rubber: Please update to snapshot version 20080323
Package: rubber Version: 1.1-2.2 Severity: wishlist Please update to the snapshot version 20080323. I've been using it on gentoo without any issues, and there are certainly bugs in the 1.1 version (i.e. with the index module). Thanks, ~David -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages rubber depends on: ii python 2.5.4-2 An interactive high-level object-o ii python-support 1.0.3 automated rebuilding support for P ii tetex-bin 2007.dfsg.2-4 TeX Live: teTeX transitional packa ii texlive-latex-base 2007.dfsg.2-4 TeX Live: Basic LaTeX packages rubber recommends no packages. Versions of packages rubber suggests: ii imagemagick7:6.5.1.0-1.1 image manipulation programs pn sam2p none(no description available) pn transfig none(no description available) -- no debconf information -- debsums errors found: debsums: checksum mismatch rubber file /usr/share/rubber/rubber/util.py -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#520048: Updated packaging files
Attached is a patch of the patch posted by Neil Mayhew integrated into the Debian build system. This should make it easy for anyone who wishes to package the changes themselves, or for any Debian devs to create a non-maintainer upload. Thanks! diff -uNr debian.org/changelog debian/changelog --- debian.org/changelog 2009-07-16 18:46:27.0 -0600 +++ debian/changelog 2009-07-16 18:52:53.0 -0600 @@ -1,3 +1,10 @@ +rubber (1.1-2.3) unstable; urgency=low + + * Non-maintainer upload. + * Use hashlib instead of md5 module (closes: #520048) + + -- David Mohr squis...@alucardo.nd.mcbf.net Thu, 16 Jul 2009 18:11:24 -0600 + rubber (1.1-2.2) unstable; urgency=medium * Non-maintainer upload. diff -uNr debian.org/control debian/control --- debian.org/control 2009-07-16 18:46:27.0 -0600 +++ debian/control 2009-07-16 18:37:59.0 -0600 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Emmanuel Beffara m...@beffara.org Uploaders: Baruch Even bar...@debian.org -Build-Depends: debhelper (= 5.0.37.2) +Build-Depends: debhelper (= 5.0.37.2), quilt Build-Depends-Indep: python, texinfo, python-support (=0.5.3) XB-Python-Version: all Standards-Version: 3.8.0 diff -uNr debian.org/patches/01-hashlib.patch debian/patches/01-hashlib.patch --- debian.org/patches/01-hashlib.patch 1969-12-31 17:00:00.0 -0700 +++ debian/patches/01-hashlib.patch 2009-07-16 18:26:09.0 -0600 @@ -0,0 +1,20 @@ +--- rubber-1.1/src/util.py 2009-07-16 18:12:33.0 -0600 rubber-1.1/src/util.py.new 2009-07-16 18:12:46.0 -0600 +@@ -5,7 +5,7 @@ + by the modules for various tasks. + + +-import md5 ++import hashlib + import os, stat, time + import imp + import re, string +@@ -19,7 +19,7 @@ + + Compute the MD5 sum of a given file. + +- m = md5.new() ++ m = hashlib.md5() + file = open(fname) + for line in file.readlines(): + m.update(line) diff -uNr debian.org/patches/series debian/patches/series --- debian.org/patches/series 1969-12-31 17:00:00.0 -0700 +++ debian/patches/series 2009-07-16 18:29:01.0 -0600 @@ -0,0 +1 @@ +01-hashlib.patch diff -uNr debian.org/rules debian/rules --- debian.org/rules 2009-07-16 18:46:27.0 -0600 +++ debian/rules 2009-07-16 18:22:50.0 -0600 @@ -12,6 +12,7 @@ build-stamp: settings.py dh_testdir + dh_quilt_patch $(MAKE) touch build-stamp @@ -20,6 +21,7 @@ dh_testroot rm -f build-stamp -$(MAKE) distclean + dh_quilt_unpatch dh_clean install: build
Bug#525572: For completeness' sake
Even with the updated package, I had to remove ~/.pulse for the volume to not be muted after boot. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532077: audacious: Playlist menu doesn't work
On Sat, Jun 27, 2009 at 12:57 AM, Fabrice Lorrainfabrice.lorr...@free.fr wrote: John Lindgren a écrit : I don't suppose either of you still have a copy of the old configuration? John Lindgren Nope, sorry. Unfortunately same here... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532077: it is a gdk bug
Hi, I found out that it is a bug in gdk, see # 580511 in the gtk / gnome bugzilla. So nothing is wrong with audacious after all in regards to the gtk critical. Just the incompatibility of config files between v1 and v2 happened here too, I couldn't look at the playlist until I deleted my configuration directory. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#532077: Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed
(audacious2:7539): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed Hmm. We don't call gdk_x11_atom_to_xatom_for_display in Audacious as far as I know, but I will have someone more familiar with the skins interface look at it. Hi, I just came across this same error in a program of mine, and happened to notice it in audacious2 today too. I dug a bit deeper, and this code is usually not called directly. I.e. a call to gtk_dialog_run() can cause this, as it calls gdk_window_set_modal_hint () which a few levels down translates to a call to gdk_x11_atom_to_xatom_for_display (). I just have no clue why the lookup for a cached atom returns null. I also noticed bug # 533128 , where someone noted that this only happens on dual head machines (I am on dual head too). How about the reporter for this bug? Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531214: audacious: Display is not save with the session manager
Package: audacious
Version: 1.5.1-4.1
Severity: normal
Tags: patch
Audacious does not save the DISPLAY variable with the session manager. As a
result, when saving the session with audacious on i.e. :0.1, it will respawn
on :0.0.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.29-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages audacious depends on:
ii audacious-plugins 1.5.1-2.1 Base plugins for audacious
ii dbus 1.2.14-2 simple interprocess messaging syst
ii gtk2-engines-pixbuf 2.16.1-2 Pixbuf-based theme for GTK+ 2.x
ii libatk1.0-0 1.26.0-1 The ATK accessibility toolkit
ii libaudclient1 1.5.1-4.1 audacious dbus remote control libr
ii libaudid3tag1 1.5.1-4.1 audacious id3 tag manipulation lib
ii libc6 2.9-13 GNU C Library: Shared libraries
ii libcairo2 1.8.6-2+b1 The Cairo 2D vector graphics libra
ii libdbus-1-3 1.2.14-2 simple interprocess messaging syst
ii libdbus-glib-1-2 0.80-4 simple interprocess messaging syst
ii libfontconfig12.6.0-3generic font configuration library
ii libfreetype6 2.3.9-4.1 FreeType 2 font engine, shared lib
ii libglib2.0-0 2.20.1-2 The GLib library of C routines
ii libgtk2.0-0 2.16.1-2 The GTK+ graphical user interface
ii libice6 2:1.0.5-1 X11 Inter-Client Exchange library
ii libmcs1 0.7.1-1Abstraction library to store confi
ii libmowgli10.6.1-1a high performance development fra
ii libpango1.0-0 1.24.2-1 Layout and rendering of internatio
ii libsamplerate00.1.7-2audio rate conversion library
ii libsm62:1.1.0-2 X11 Session Management library
ii libx11-6 2:1.2.1-1 X11 client-side library
Versions of packages audacious recommends:
ii audacious-plugins-extra 1.5.1-2.1 Various extra plugins for audaciou
ii unzip 6.0-1 De-archiver for .zip files
audacious suggests no packages.
-- no debconf information
diff -u -N -r audacious-1.5.1.org/src/audacious/signals.c audacious-1.5.1/src/audacious/signals.c
--- audacious-1.5.1.org/src/audacious/signals.c 2008-05-23 16:00:34.0 -0600
+++ audacious-1.5.1/src/audacious/signals.c 2009-05-30 15:58:07.0 -0600
@@ -257,14 +257,28 @@
static void
signal_session_quit_cb(EggSMClient *client, gpointer user_data)
{
+gchar *argv[2];
+
g_print(Session quit requested. Saving state and shutting down.\n);
+
+argv[0] = audacious;
+argv[1] = g_strdup_printf (--display=%s, gdk_display_get_name (gdk_display_get_default()));
+egg_sm_client_set_restart_command (client, 2, argv);
+
aud_quit();
}
static void
-signal_session_save_cb(EggSMClient *client, const char *state_dir, gpointer user_data)
+signal_session_save_cb(EggSMClient *client, GKeyFile *state_file, gpointer user_data)
{
+gchar *argv[2];
+
g_print(Session save requested. Saving state.\n);
+
+argv[0] = audacious;
+argv[1] = g_strdup_printf (--display=%s, gdk_display_get_name (gdk_display_get_default()));
+egg_sm_client_set_restart_command (client, 2, argv);
+
aud_config_save();
}
#endif
Bug#491138: Did it ever reach experimental?
Hi, with audacious 2.0.1 officially released, was the audacious2 package ever uploaded? I can't seem to find it on the package search. Maybe now is a good time to revive this and upload it? I'd certainly appreciate it! :-) Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519055: bridge-utils: Default route set for the wrong interface when configuring with dhcp
On Sun, Mar 15, 2009 at 6:30 AM, Santiago Garcia Mantinan ma...@debian.org wrote: Yes, NetworkManager and its gnome client are running. But I remember reading just recently that under Debian it is patched such that it only picks up on auto interfaces. In fact, in the nm-applet I only see br0, not eth2, and when I go into the settings (I've not really looked at it / used it before, just somehow found its way onto my system) it says br0 - never under wired connections. Of all the info you are giving me... the most suspicious part is this, as I don't use gnome I don't know how it works or what it does, but I've seen several network managers do really weird things. So if you could somehow disable this, either by uninstalling that part of gnome or by disabling it or not running gnome for some time just to see if things would work that way and that way determine if the gnome guys can somehow be responsable for this and ask them to help on this. Heh, I am not even running gnome. But network-manager got pulled in on some update, and xfce is a bit too compatible sometimes it seems, as it was then automatically added to my session... Since I have absolutely no need for this on my machine, I removed it and woosh, everything works just as expected. Now I _only_ see br0 up, and thus of course no route (or ip address for that matter) on eth2. Aside from that the only other noteworthy package I use (this is on a desktop btw), is virtualbox - which was also the reason I setup the bridge. But, aside from loading the vobxnetflt module, this problem occurs before I start virtualbox. Thanks for pointing this out, I know virtualbox, but I don't know what vboxnetflt does, so if you can explain this a little bit, it would be great. For what I know virtualbox loads its modules on startup, so even though I doubt it can be responsable for this, It could be, as it is doing things on our startup. How are you using this? I mean... For completeness' sake, I'll answer the rest of these, though the problem is solved. 1- you are loading the vbox modules and not running virtualbox and already seing this bug, right? Yes, exactly. The virtualbox modules don't get autoloaded for some reason, so I add them to /etc/modules. 2- how are you using virtualbox, why are you using a bridge with it? Please elaborate a bit on your network setup (you use eth2 bound to br0, how about eth0, eth1, ... how does virtualbox relate to the network interfaces, attaches using nat, host interface, ... and which interface it uses, ...) eth0 is non-existant due to udev persistent rules. eth1 is the onboard network card, but it's not connected to anything. eth2 is an intel gigabit card. I'm using the bridge so that my virtualbox instances can operate like regular machines on my network. They'll get a dhcp address from my server etc - it really is an easy way to get networking up and runnnig in virtualbox. 3- add any other thing you think could help us here :-) Sorry, I'm not being of much help here, but I don't know what can be causing all this, I'm trying to get enough info so that I can try to setup something similar here that replicates the problem so that I can trace it. =) You certainly were helpful! Now if you have the time and energy, it'd be interesting if you can duplicate the error with network-manager (should be quick to install and deinstall again, it does not depend on much afaik). Then maybe this bug could get reassigned to network-manager, because it clearly is missbehaving. Thanks, ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519055: bridge-utils: Default route set for the wrong interface when configuring with dhcp
On Wed, Mar 11, 2009 at 12:47 PM, Santiago Garcia Mantinan ma...@debian.org wrote: If you don't have eth2 mentioned on your interfaces other than on the bridge_ports line then you must have it somewhere else. I'm thinking about some daemon doing dirty things, I would do a grep -r eth2 /etc and see what that accounts for. The grep only showed some commented lines in interfaces (I will delete them and see if they caused some effect although they were commented out). Aside from that only udev persistency rules, and one hit in a xend-config.sxp.dpkg-old (I don't have xen installed anymore). What dhcp client do you have installed? can you have a look at its config? Any network daemons running? maybe something related to gnome or kde? Yes, NetworkManager and its gnome client are running. But I remember reading just recently that under Debian it is patched such that it only picks up on auto interfaces. In fact, in the nm-applet I only see br0, not eth2, and when I go into the settings (I've not really looked at it / used it before, just somehow found its way onto my system) it says br0 - never under wired connections. I'm running dhcp3-client 3.1.1-6, AFAIK that's the only one I have installed. Trimming of comments, I think I have only the stock config: ---snip--- option rfc3442-classless-static-routes code 121 = array of unsigned integer 8; request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, domain-search, host-name, netbios-name-servers, netbios-scope, interface-mtu, rfc3442-classless-static-routes; ---snap--- I have some entries in the enter/exit hooks, but all from packages, nothing custom. I don't think this is a but on bridge-utils but on your setup, but I'd like to know what is hapenning for the next time this happens to anybody else. Thanks, I appreciate it that you're interested in helping out anyway! I'm running a custom .26 kernel, but I just checked my config and it has IP_PNP not set (kernel level autoconfiguration), which as far as I know is the only option that does ip address assignment. Aside from that the only other noteworthy package I use (this is on a desktop btw), is virtualbox - which was also the reason I setup the bridge. But, aside from loading the vobxnetflt module, this problem occurs before I start virtualbox. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519174: [Pkg-xfce-devel] Bug#519174: Bug#519174: Menu hotkey ^W used to 2 different menu entries
On Tue, Mar 10, 2009 at 7:16 PM, Dave Witbrodt dawit...@sbcglobal.net wrote: Yves-Alexis Perez wrote: On mar, 2009-03-10 at 16:14 -0400, Dave Witbrodt wrote: Opening Thunar and clicking on the File menu reveals that both the Open New Window and Close menu entries are using Ctrl-W as their shortcut. This cannot be user error, since I have never played with redefining keyboard shortcuts on this system. Could you retry with a fresh user and/or fresh config? Because by default “Open new window” is bound to Ctrl+N. So I really think there is user interaction here :/ You seem to be right, but I am baffled about how it could happen. I already have a second user account on the system, so I logged out and logged into the 2nd account. The menu hotkeys are correct in the 2nd account: ^N for Open New Window, and ^W for Close. It looks like there is no bug in the Debian packages. Could you tell me what file contains user-specific hotkey settings? I would like to run 'diff' to see what else is messed up. Since I have never attempted to alter the hotkeys (at the moment, I don't even know how to change the ^W back to ^N !), I am dumbfounded about how this even happened. With GTK one can just hover the mouse over the menu item, and press the desired key combination to change the shortcut. I don't know where they are stored, but it's easy to fix, just select Open New Window, and press CTRL-N to reset it to the correct shortcut. Yes, this is a feature, not a bug ;-). ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519055: bridge-utils: Default route set for the wrong interface when configuring with dhcp
Package: bridge-utils Version: 1.4-5 Severity: important I'm configuring a bridge with dhcp. It used to work just fine, but recently the default interface gets set for the wrong interface. My /etc/network/interfaces contains exactly: ---snip--- auto lo iface lo inet loopback auto br0 iface br0 inet dhcp bridge_ports eth2 bridge_fd 2.5 ---snap--- After booting the default route is now set for eth2, not for br0. I think it used to be that it would always get set for both interfaces, which seemed to work fine. Both interfaces are up with the same ip address, exactly as before when it used to work fine. I think this broke sometimes after lenny was released, but I'm not certain, sorry. Let me know if I can somehow help debug this problem. Thanks, ~David -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bridge-utils depends on: ii libc6 2.9-4 GNU C Library: Shared libraries Versions of packages bridge-utils recommends: ii ifupdown 0.6.8+nmu1 high level tools to configure netw bridge-utils 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#517020: [Pkg-xfce-devel] Bug#517020: Bug#517020: thunar: potential exploits via application launchers
On Wed, Feb 25, 2009 at 12:08 AM, Michael Gilbert michael.s.gilb...@gmail.com wrote: On Wed, 25 Feb 2009 07:44:33 +0100 Yves-Alexis Perez wrote: Can you point me to your patch to the specs? And your patch to the code? i understand that there's going to be a lot of work involved, and its easy for me to submit the problem, and hard for you to fix it. i truely do appreciate that. and i also understand that you're a volunteer, so technically, you don't really have to do anything if you don't want to. i'm just trying to help get the ball rolling. are [1],[2] the spec you are refering to? [1] http://portland.freedesktop.org/xdg-utils-1.0/xdg-desktop-icon.html [2] http://portland.freedesktop.org/xdg-utils-1.0/xdg-desktop-menu.html Correct me if I'm wrong, but I think the point is that these specs do NOT mention the supposed fix that was getting talked about in the references on the bug report. A consensus is formed once the specs are updated - then the fix should be implemented. Notably there is no need to rush here because Thunar already behaves extremely well - and does NOT manage the desktop. So the issue is completely different than with KDE and GNOME. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517029: libburn4: Please upload newer version
Package: libburn4 Version: 0.5.5-0.1 Severity: wishlist The libburn version in sid is quite outdated. In particular there has been a bug fixed in 0.5.6, which gets triggered by some people using xfburn. Now with the freeze lifted, can you please update the version? Thanks! -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libburn4 depends on: ii libc6 2.7-18 GNU C Library: Shared libraries libburn4 recommends no packages. libburn4 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#509030: [Pkg-xfce-devel] Bug#509030: xfce4-terminal: Window decoration are not drawn even when enabled
On Wed, Dec 17, 2008 at 10:52 AM, john.lindg...@tds.net wrote: Package: xfce4-terminal Version: 0.2.8-5 Severity: grave I am attaching a screenshot that shows the problem better than any description. In the screenshot, compositing is enabled to show the outline of the window, but the problem happens just the same with or without compositing. It'd be good to know what theme you are using, and also if the same error occurs with other themes. ~David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#502882: exo-utils: more permissions problems
That xfburn bug you dug up has nothing to do with your problem, it's a very outdated report that I'm going to close right now. Xfburn btw. does work fine now in that situation, and it will automatically unmount the media if HAL is present (and I assume without HAL thunar probably doesn't do automounting). So possibly this is a bug you should file against brasero? The Thunar author has mentioned it several times that he doesn't think it makes much sense to present the unmount option to the user for removable media, so that's unlikely to change anyways. ~David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#496584: [Pkg-xfce-devel] Bug#496584: xfce4-session: Sometimes asks for password on shutdown
It seems like you have dbus installed. I don't know what the precedence is, but AFAIK dbus can be used to initiate the shutdown. Have you changed anything there? Maybe you can check if dbus is running when it asks for a password, and when it doesn't? ~David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#429165: fixed
Thanks for the suggestion. I had been wanting to do that for a while, now it's done! :-). Fixed in rev.. 5226. ~David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494267: xscreensaver: ignores second X screen
Package: xscreensaver Version: 5.05-3 Severity: normal After upgrading to 5.05, xscreensaver ignores my second X screen. I'm running an old style dual head setup, so I have :0.0 and :0.1. With 5.03 xscreensaver was watching input on both screens, and would start a screensaver on both. With 5.05 (and actually also 5.06), it ignores :0.1, although it says it is running: ---SNIP--- [EMAIL PROTECTED]:~/src/xscreensaver-5.06/driver$ xscreensaver xscreensaver: 22:52:56: already running on display :0.1 (window 0x462) from process 30648 ([EMAIL PROTECTED]). [EMAIL PROTECTED]:~/src/xscreensaver-5.06/driver$ echo $DISPLAY :0.1 [EMAIL PROTECTED]:~/src/xscreensaver-5.06/driver$ ---SNAP--- Some extra info: Output from `xscreensaver -verbose -debug -log xscreensaver.log': ---SNIP--- ## xscreensaver: 22:30:11: logging to log.txt at Thu Aug 7 22:30:11 2008 ## xscreensaver 5.05, copyright (c) 1991-2008 by Jamie Zawinski [EMAIL PROTECTED]. xscreensaver: 22:30:11: Warning: running in DEBUG MODE. Be afraid. Note that in debug mode, the xscreensaver window will only cover the left half of the screen. (The idea is that you can still see debugging output in a shell, if you position it on the right side of the screen.) Debug mode is NOT SECURE. Do not run with -debug in untrusted environments. xscreensaver: 22:30:11: running as squisher/squisher (1000/1000) xscreensaver: 22:30:11: in process 22009. xscreensaver: 22:30:11: running on display :0.0 xscreensaver: 22:30:11: vendor is The X.Org Foundation, 10402000. xscreensaver: 22:30:11: useful extensions: xscreensaver: 22:30:11: MIT Screen-Saver (disabled at compile time) xscreensaver: 22:30:11: Shared Memory xscreensaver: 22:30:11: Double-Buffering xscreensaver: 22:30:11: Power Management xscreensaver: 22:30:11: GLX xscreensaver: 22:30:11: XF86 Video-Mode xscreensaver: 22:30:11: Resize-and-Rotate xscreensaver: 22:30:11: screen 0 non-colormapped depths: 0 24. xscreensaver: 22:30:11: screens in use: 1 xscreensaver: 22:30:11:0/0: 1280x1024+0+0 (default) xscreensaver: 22:30:11: rejected screens: 1 xscreensaver: 22:30:11: 1001/1: 1280x1024+0+0 (default) -- duplicate of 0 xscreensaver: 22:30:11: selecting RANDR events xscreensaver: 22:30:11: consulting /proc/interrupts for keyboard activity. xscreensaver: 22:30:11: 0: visual 0x21 (TrueColor, depth: 24, cmap: default) xscreensaver: 22:30:11: resetting stderr xscreensaver: 22:30:11: 0: saver window is 0xc2. xscreensaver: 22:30:11: selecting events on extant windows... done. xscreensaver: 22:30:11: awaiting idleness. xscreensaver: 22:30:11: starting idle_timer (60, 144553288) xscreensaver: 22:30:11: 0: pointer moved: off screen - 423,826. xscreensaver: 22:30:11: killing idle_timer (60, 144553288) xscreensaver: 22:30:11: starting idle_timer (60, 144553288) xscreensaver: 22:30:11: checking wall clock for hibernation (0:00:00). xscreensaver: 22:30:13: 0: ButtonPress on 0xc9 at 316,573. xscreensaver: 22:30:13: killing idle_timer (60, 144553288) xscreensaver: 22:30:13: starting idle_timer (60, 144553288) xscreensaver: 22:30:14: 0: spawning xscreensaver-demo in pid 22023. xscreensaver: 22:30:14: killing idle_timer (60, 144553288) xscreensaver: 22:30:14: starting idle_timer (60, 144553288) xscreensaver-demo: 22:30:14: /usr/share/xscreensaver/config/molecule.xml: duplicate switch -fps xscreensaver: 22:30:16: 0: pointer moved: 423,826 - 1260,517 (837,309; 837/1=837). xscreensaver: 22:30:16: killing idle_timer (60, 144553288) xscreensaver: 22:30:16: starting idle_timer (60, 144553288) xscreensaver: 22:30:16: checking wall clock for hibernation (0:00:05). xscreensaver: 22:30:17: got SIGCHLD xscreensaver: 22:30:17: waitpid(-1) == 22023 xscreensaver: 22:30:17: 0: child pid 22023 (xscreensaver-demo) exited normally. xscreensaver: 22:30:17: waitpid(-1) == -1 (10) ---SNAP--- stdout from version 5.03 `xscreensaver -verbose', which is working fine: ---SNIP--- xscreensaver 5.03, copyright (c) 1991-2006 by Jamie Zawinski [EMAIL PROTECTED]. xscreensaver: running as squisher/squisher (1000/1000) xscreensaver: in process 24200. xscreensaver: 22:41:46: 0: xscreensaver-gl-helper: GL visual is 0x24. xscreensaver: 22:41:46: 1: xscreensaver-gl-helper: GL visual is 0x13C. xscreensaver: 22:41:46: running on display :0.0 (2 screens). xscreensaver: 22:41:46: vendor is The X.Org Foundation, 10402000. xscreensaver: 22:41:46: useful extensions: xscreensaver: 22:41:46: MIT Screen-Saver -- not supported at compile time! xscreensaver: 22:41:46: Shared Memory xscreensaver: 22:41:46: Double-Buffering xscreensaver: 22:41:46: Power Management xscreensaver: 22:41:46: GLX xscreensaver: 22:41:46: XF86 Video-Mode xscreensaver: 22:41:46: Resize-and-Rotate xscreensaver: 22:41:46: screen 0
Bug#493315: [Pkg-xfce-devel] Bug#493315: xfburn: Could have a copy optical media option
Uhm, this is already on the TODO list. No need to open any wishlists for those items :-). And feel free to contribute to the libburnia project, which I would prefer to use, but doesn't yet have this functionality. ~David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491480: [Pkg-xfce-devel] Bug#491480: I can confirm the bug
Works just fine here in sid (which has the same package version as lenny). I do have hddtemp installed with setuid bit so I can run it with my regular user, maybe that's a factor in the crash? The proper way to set the setuid bit on the binary is by using 'dpkg-reconfigure hddtemp', can you try that and see if the crash still occurrs? ~David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489336: fixed upstream
This bug should have been fixed in version 0.3.1. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487591: vlc : no suitable decoder module for fourcc XVID
Duplicate of #483000, please merge. Solution can be found in that bug report. On Wed, Jun 25, 2008 at 9:09 PM, David Mohr [EMAIL PROTECTED] wrote: I can confirm this bug, same version of vlc produces the same error for DIVX fourcc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486543: [Pkg-audacious-maintainers] Bug#486543: audacious: Audacious segfaults on start
I had the same problem, and here the solution was also to remove audacious-crossfade, as Alex Malinovich suggested. My guess is that I once got it from http://www.debian-multimedia.org , but the package is not in their repository either anymore. I know that other repositories don't have to get supported by debian, although a conflict for audacious-crossfade would probably prevent a lot of people from having to look up bug reports :-). Thanks, ~David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#487591: vlc : no suitable decoder module for fourcc XVID
I can confirm this bug, same version of vlc produces the same error for DIVX fourcc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486424: xfburn: icon cache is not updated after installation
Package: xfburn Version: 0.3.0-2 Severity: normal postinst and postrm should call gtk-update-icon-path /usr/share/icons/hicolor or similar. Otherwise the installed icons don't show up inside of xfburn. Thanks! -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xfburn depends on: ii libatk1.0-01.22.0-1 The ATK accessibility toolkit ii libburn4 0.4.4-1 library to provide CD/DVD writing ii libc6 2.7-11GNU C Library: Shared libraries ii libcairo2 1.6.4-2 The Cairo 2D vector graphics libra ii libdbus-1-31.2.1-2 simple interprocess messaging syst ii libexo-0.3-0 0.3.4-7 Library with extensions for Xfce ii libfontconfig1 2.5.93-1 generic font configuration library ii libfreetype6 2.3.5-1+b1FreeType 2 font engine, shared lib ii libglib2.0-0 2.16.3-2 The GLib library of C routines ii libgtk2.0-02.12.9-4 The GTK+ graphical user interface ii libhal-storage10.5.11-1 Hardware Abstraction Layer - share ii libhal10.5.11-1 Hardware Abstraction Layer - share ii libisofs6 0.6.2.1-1 library to create ISO9960 images ii libpango1.0-0 1.20.2-2 Layout and rendering of internatio ii libpixman-1-0 0.10.0-2 pixel-manipulation library for X a ii libpng12-0 1.2.27-1 PNG library - runtime ii libthunar-vfs-1-2 0.9.0-9 VFS abstraction used in thunar ii libx11-6 2:1.0.3-7 X11 client-side library ii libxfce4util4 4.4.2-2 Utility functions library for Xfce ii libxfcegui4-4 4.4.2-4 Basic GUI C functions for Xfce4 ii libxrender11:0.9.4-1 X Rendering Extension client libra ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime xfburn recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#481086: [Pkg-xfce-devel] Bug#481086: xfce4-panel: plugins ignore multiscreen environment
On Thu, May 15, 2008 at 12:27 AM, Yves-Alexis Perez [EMAIL PROTECTED] wrote: On mar, 2008-05-13 at 09:41 -0600, David Mohr wrote: Some plugins ignore the screen they are on in a multiscreen (i.e. :0.0 and :0.1) display, and always launch on the primary screen. Attached is a patch that fixes that problem. It is already in svn, see r26937 in the 4_4 branch. Does this patch fixes #408534/#470227 too? Unfortunately, no. These fixes are just for the plugins, the appearing on the wrong screen issue did not occur with the panel itself. Hopefully later this summer I can have a look at these bugs though, thanks for pointing them out. Since I'm using that multi-screen setup maybe we can make some progress on them. ~David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
