Bug#774149: Cannot reproduce
Hi Dima, I'm using Debian/Stable only, therefore I cannot test this on Debian/Sid. My guess is, that there might be a change in ntfs-3g or systemd to fix this. best regards, Jürgen
Bug#774149: fixing the stable package
Hi all, the Patch from Christian works for me as well with one exception. I had to remove the file /lib/udev/rules.d/usbmount.rules after creating /etc/udev/rules.d/usbmount.rules. If I do not remove the original file, usbmount is called twice which leads to a double mount of the usb flash drive: $mount|grep sdd1 /dev/sdd1 on /media/usb1 type ext2 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,user_xattr,acl) /dev/sdd1 on /media/usb2 type ext2 (rw,nosuid,nodev,noatime,nodiratime,errors=continue,user_xattr,acl) I've successfully tested ext2, vfat and ntfs based usb flash drives so far using this patch. I guess this is the systemd way to get this done. As far as I understood Christians patch, this adds a dependency to systemd (since it is using systemd-escape). I am not sure if this is the *best* way to do. How to deal with systems using sysvinit or upstart? best regards, Jürgen Am 04.12.2015 um 17:41 schrieb Faheem Mitha: > > [CCs to suitable-seeming people. If you are getting this email via the > BTS too, sorry about the noise, but the BTS really should say who is > subscribed.] > > Hi, > > The patch by Christian Weinberger fixes the problem for me, though I > don't really understand it. > > It seems this bug breaks usbmount in stable, at least for me, and (it > seems) others too. Is this a candidate for a stable fix? I'm willing to > make a fix and do an upload if there is someone out there who will > sponsor me. Or should I submit a pull request? And if so, where? > > Oh, but first, could we get come concensus that the Christian patch is > the correct way to go? It looks good to me, but I don't understand the > context well enough to say. > > Regard, Faheem Mitha >
Bug#774149: Workaround working
Hi Rogério I would really appreciate if you keep usbmount alive. The idea of a small tool to daemonize mount sounds interesting, but this is one point where I am not sure. I've read an article about udev, where it was stated, that udev should not start a daemon directly, but should use systemd to do it. Adding a dependency to systemd gives the project a complexity and political level I don't like. This was the point where I started on thinking about using at to do the job. To complete your question: This bug only affects fuse based filesystems on my side. best regards, Jürgen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774149: udisks2
Hello, Thanks for the reply. I don't think you can cover all functionality with udisks2. I got the same problem as shirish. I was thinking about a udev rule to issue the udisksctrl command, but I need to know the filesystem type before the mount to be able to specify different mount options on vfat than on ntfs or ext2. This leads to a more complex script which will basically look like usbmount, I think. Besides, I do not like the way udisks2 is creating the mountpoints. I'd like my flash drive on /media/usb0 and not some unpredictable /media/username/unpredictable_strange_flash_drive_name best regards, Jürgen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774149: Workaround using at
Hello,
I've got the same problem here on my system. I did a little research and
it seems, that udev is killing the mount.ntfs process after a few seconds.
I've created a litte nasty workaround using at. I think it would be a
much better way to tell udev to not kill the mount process, but I have
no clue about udev.
--- usbmount.orig 2015-06-24 20:48:29.027693081 +0200
+++ usbmount2015-06-24 20:40:57.137418335 +0200
@@ -136,7 +136,8 @@
# Mount the filesystem.
log info executing command: mount -t$fstype
${options:+-o$options} $DEVNAME $mountpoint
- mount -t$fstype ${options:+-o$options} $DEVNAME
$mountpoint
+ echo mount -t$fstype ${options:+-o$options}
$DEVNAME $mountpoint /usr/share/usbmount/helper.sh
+at -f /usr/share/usbmount/helper.sh now
# Determine vendor and model.
vendor=
best regards,
Jürgen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#404912: (no subject)
logging off from KDE logging in back again resolved the issue. thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#404912: problem still exists
Oh, the problem still exists. After logging off and loggin in again, printing works fine a few times, but after a few minutes (e.g. 10 minutes) of working (using kmail, akregator, iceweasel, flock konsole, konqueror and vmware) the problem reappears. Logging off/on fixes the problem again, but loggin off/on before each print job is annoying :-) Jürgen Braun
Bug#409032: kdeprint: kprinter doesn't print, only shows error message
Package: kdeprint Version: 4:3.5.5a.dfsg.1-5 Severity: normal *** Please type your report below this line *** when trying to print a postscript file to a printerqueue on cups, there only appears the message: Fehler beim Drucken der Dateien (Error while printing files) and the a dialog box with the message: Fehler bei der Druckausgabe. Das System meldet: Abhängiger Druckprozess kann nicht gestartet werden. cupsdoprint -P 'Local4100' -J kw3.ps' -H 'localhost:631' -o ' copies=1 multiple-document-handling=separate-documents-collated-copies' appears. Doing a cupsdoprint -P Local4100 kw3.ps works. Maybe the command line options passed to cupsdoprint from kprinter are wrong. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-jb Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages kdeprint depends on: ii enscript 1.6.4-11 Converts ASCII text to Postscript, ii kdelibs4c2a4:3.5.5a.dfsg.1-5 core libraries and binaries for al ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii libgcc11:4.1.1-21GCC support library ii libqt3-mt 3:3.3.7-3 Qt GUI Library (Threaded runtime v ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii poster 1:19990428-8 Create large posters out of PostSc ii psutils1.17-24 A collection of PostScript documen Versions of packages kdeprint recommends: ii evince [postscript-viewe 0.4.0-5 Document (postscript, pdf) viewer ii gnome-gv [postscript-vie 1:2.12.0-2 GNOME PostScript viewer ii gs-esp [postscript-viewe 8.15.3.dfsg.1-1 The Ghostscript PostScript interpr ii gs-gpl [postscript-viewe 8.54.dfsg.1-5 The GPL Ghostscript PostScript int ii gv [postscript-viewer] 1:3.6.2-3 PostScript and PDF viewer for X ii kghostview [postscript-v 4:3.5.5-2 PostScript viewer for KDE -- no debconf information -- Freundliche Gruesse Juergen Braun Senior System Consultant IQDoQ GmbH Document Management Company of MATERNA Theodor-Heuss-Strasse 59, 61118 Bad Vilbel Geschäftsführung: Werner Schäfer, Dr. Winfried Materna, Helmut an de Meulen Amtsgericht Frankfurt am Main HRB 72517 phone: +49 6101 806 223 fax: +49 6101 806 590 mobile: +49 175 2624437 [EMAIL PROTECTED] http://www.iqdoq.de
Bug#397635: kmail: reply fails when original sender address contains umlaut AND comma
Package: kmail Version: 4:3.5.5.dfsg.1-1 Severity: important *** Please type your report below this line *** When replying to a mail that has an original sender name that contains an umlaut AND a comma, the recipients of the newly generated mail is broken into two parts. example: sender-address Braun, Jürgen [EMAIL PROTECTED] gets broken to Braun Jürgen [EMAIL PROTECTED] in two separate To: Fields. That leads to an email that is send to Jürgen at the right address and to Braun with an incorrect Mail-Address. When the name doesn't contain an umlaut, everything is fine When the name contains an umlaut but doesn't contain a comma, everything works fine too. The problem only exist if the Name contains an umlaut AND a comma. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-jb Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages kmail depends on: ii kdebase-kio-plugins4:3.5.5a-2core I/O slaves for KDE ii kdelibs4c2a4:3.5.5a.dfsg.1-2 core libraries and binaries for al ii kdepim-kio-plugins 4:3.5.5-1 KDE pim I/O Slaves ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libaudio2 1.8-2 The Network Audio System (NAS). (s ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries ii libfontconfig1 2.4.1-2 generic font configuration library ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-19GCC support library ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libkcal2b 4:3.5.5-1 KDE calendaring library ii libkdepim1a4:3.5.5-1 KDE PIM library ii libkleopatra1 4:3.5.5-1 KDE GnuPG interface libraries ii libkmime2 4:3.5.5-1 KDE MIME interface library ii libkpimidentities1 4:3.5.5-1 KDE PIM user identity information ii libksieve0 4:3.5.5-1 KDE mail/news message filtering li ii libmimelib1c2a 4:3.5.5-1 KDE mime library ii libpng12-0 1.2.8rel-7PNG library - runtime ii libqt3-mt 3:3.3.7-1 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-19 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-2 X11 client-side library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft22.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-3 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library ii perl 5.8.8-6.1 Larry Wall's Practical Extraction ii zlib1g 1:1.2.3-13compression library - runtime Versions of packages kmail recommends: ii procmail 3.22-16Versatile e-mail processor -- no debconf information -- Freundliche Gruesse Juergen Braun Senior System Consultant IQDoQ GmbH Document Management Company of MATERNA Theodor-Heuss-Strasse 59 * 61118 Bad Vilbel * Germany phone: +49 6101 806 223 * fax: +49 6101 806 590 mobile: +49 175 2624437 * [EMAIL PROTECTED] http://www.iqdoq.com * http://www.iqdoq.de
Bug#383290: [Pkg-cups-devel] Bug#383290: cupsys: after an update the socket backend isn't available any longer
Am Sonntag, 20. August 2006 11:05 schrieb Kenshi Muto: At Wed, 16 Aug 2006 12:47:20 +0200, Jürgen Braun wrote: After updating cupsys, the socket backend isn't any longer in /usr/lib/cups/backend. It still exists in /usr/lib/cups/backend-available, but the symbolic link is missing. So every printer that uses the socket backend gets disabled when used the first time. Hm, interesting. Can you remember which cupsys version you upgrade from? No, can't remember what version I upgraded, but I do upgrade/dist-upgrade minimum once a week. 1.2.1-4 to 1.2.2-1 has not any changes around debconf. 1.2.1-3 had a change because I added SNMP backend, but I can't believe it cause an error. * cupsys/backend: ipp, lpd, parallel, usb Maybe you know because you're using Unstable, dpkg-reconfigure cupsys and enable socket will back socket backend again. I know the command but haven't run this for a long time. The system was installed 6 years ago, upgraded to Unstable and hold up-to-date. I run the command and now I saw the choice to enable/disable available backends and in my configuration (or is it default???) the socket backend is not activated. I use this printer with the socket backend not very often, so maybe the backend isn't available since a longer time (since the last change around debconf??) and the last time I missed the backend, I created the link manually. I think you can close the bug. Thanks, -- Freundliche Gruesse Juergen Braun Senior System Consultant IQDoQ GmbH Document Management Company of MATERNA Theodor-Heuss-Strasse 59 * 61118 Bad Vilbel * Germany phone: +49 6101 806 223 * fax: +49 6101 806 590 mobile: +49 175 2624437 * [EMAIL PROTECTED] http://www.iqdoq.com * http://www.iqdoq.de
Bug#383290: cupsys: after an update the socket backend isn't available any longer
Subject: cupsys: after an update the socket backend isn't available any longer Package: cupsys Version: 1.2.2-1 Severity: important *** Please type your report below this line *** After updating cupsys, the socket backend isn't any longer in /usr/lib/cups/backend. It still exists in /usr/lib/cups/backend-available, but the symbolic link is missing. So every printer that uses the socket backend gets disabled when used the first time. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-jb Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED] o) Versions of packages cupsys depends on: ii adduser 3.96Add and remove users and groups ii cupsys-common1.2.2-1 Common UNIX Printing System(tm) - ii debconf [debconf-2.0]1.5.3 Debian configuration management sy ii gs-esp 8.15.2.dfsg.1-1 The Ghostscript PostScript interpr ii libacl1 2.2.41-1Access control list shared library ii libc62.3.6-19GNU C Library: Shared libraries ii libcupsimage21.2.2-1 Common UNIX Printing System(tm) - ii libcupsys2 1.2.2-1 Common UNIX Printing System(tm) - ii libdbus-1-2 0.62-4 simple interprocess messaging syst ii libgnutls13 1.4.2-1 the GNU TLS library - runtime libr ii libldap2 2.1.30-13+b1OpenLDAP libraries ii libpam0g 0.79-3.2Pluggable Authentication Modules l ii libpaper11.1.19 Library for handling paper charact ii libslp1 1.2.1-5 OpenSLP libraries ii lsb-base 3.1-14 Linux Standard Base 3.1 init scrip ii patch2.5.9-4 Apply a diff file to an original ii perl-modules 5.8.8-6.1 Core Perl modules ii procps 1:3.2.7-2 /proc file system utilities ii xpdf-utils [poppler-util 3.01-9 Portable Document Format (PDF) sui ii zlib1g 1:1.2.3-13 compression library - runtime Versions of packages cupsys recommends: ii cupsys-client 1.2.2-1 Common UNIX Printing System(tm) - ii foomatic-filters3.0.2-20060712-1 linuxprinting.org printer support ii smbclient 3.0.23b-1a LanManager-like simple client fo -- debconf information: cupsys/raw-print: true cupsys/lpr-backend-setuid: false cupsys/ports: 631 * cupsys/backend: ipp, lpd, parallel, usb cupsys/portserror: cupsys/browse: true -- Freundliche Gruesse Juergen Braun Senior System Consultant IQDoQ GmbH Document Management Company of MATERNA Theodor-Heuss-Strasse 59 * 61118 Bad Vilbel * Germany phone: +49 6101 806 223 * fax: +49 6101 806 590 mobile: +49 175 2624437 * [EMAIL PROTECTED] http://www.iqdoq.com * http://www.iqdoq.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380096: dirvish: execution via crontab doesn't work
Package: dirvish Version: 1.2.1-0.1 Severity: important When executing the cronjob /etc/dirvish/dirvish-cronjob via cron, no backup is created because the script reports sh: dirvish: command not found Either /usr/sbin is not in the $PATH of the cron daemon or /usr/sbin/dirvish-runall should call dirvish with it's absolute pathname. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-jb Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages dirvish depends on: ii libtime-modules-perl 2003.1126-2 Various Perl modules for time/date ii libtime-period-perl 1.20-8 Perl library for testing if a time ii perl 5.8.8-6 Larry Wall's Practical Extraction ii perl-modules 5.8.8-6 Core Perl modules ii rsync2.6.8-2 fast remote file copy program (lik Versions of packages dirvish recommends: ii ssh 1:4.3p2-2 Secure shell client and server (tr -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
