Bug#995449: fuseiso9660: does not handle spaces in imagefile
Package: fuseiso9660 Version: 0.3-2 Severity: normal Dear Maintainer, * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? $ fuseiso9660 INV.DHL202038658530\ \,PDF.iso isotest fuse: unknown option `PDF.iso' * What was the outcome of this action? Nothing was mounted and an error message was shown. * What outcome did you expect instead? No error message and in the directory isotest should be a weird windows executable. $ cp INV.DHL202038658530\ \,PDF.iso inv.iso $ fuseiso9660 inv.iso isotest $ ls isotest/ 'INV.DHL202038658530 ,PDF.exe' -- System Information: Debian Release: 11.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fuseiso9660 depends on: ii fuse3 [fuse] 3.10.3-2 ii libc6 2.31-13 ii libcdio19 2.1.0-2 ii libfuse2 2.9.9-5 ii libiso9660-11 2.1.0-2 ii zlib1g 1:1.2.11.dfsg-2 fuseiso9660 recommends no packages. fuseiso9660 suggests no packages.
Bug#987727: [Pkg-auth-maintainers] Bug#987727: fido2-tools: does not find available fido2 tokens
Hi Taowa, On Wed, 28 Apr 2021 12:08:28 -0400 Taowa wrote: > Control: severity -1 wishlist > > Hi Andreas, > > As far as I can tell, fido2-tools only speaks USB (and has experimental > support for NFC, but...): > > > libfido2 provides library functionality and command-line tools to > > communicate with a FIDO device over USB, and to verify attestation and > > assertion signatures. > (https://developers.yubico.com/libfido2/) > > Setting this bug to "wishlist" severity, and I'll look into whether this > is something upstream might want to support. > hmm, ok, seems to be part of libfido2. But the package fido2-tools itself has no documentation about that limitation. I would expect something like that in the manpage Regards, Andreas
Bug#987727: fido2-tools: does not find available fido2 tokens
Package: fido2-tools
Version: 1.5.0-2~bpo10+1
Severity: important
Dear Maintainer,
* What led up to the situation?
I paired a FIDO2 device via bluetoothctl
FIDO service is available and found:
$ mdbus2 -s org.bluez /org/bluez/hci0/dev_D0_CF_5E_06_F9_C4/service002d
org.freedesktop.DBus.Properties.GetAll org.bluez.GattService1
({'UUID': <'fffd--1000-8000-00805f9b34fb'>, 'Device': , 'Primary': , 'Includes': <@ao
[]>},)
* What exactly did you do (or not do) that was effective (or
ineffective)?
I tried to list the available devices via fido2-token -L and tried to get
information about these devices via fido2-token -I
* What was the outcome of this action?
$ fido2-token -L
$ fido2-token -I D0:CF:5E:06:F9:C4
fido2-token: fido_dev_open D0:CF:5E:06:F9:C4: FIDO_ERR_INTERNAL
* What outcome did you expect instead?
I expected to see the list of available FIDO2 devices and information
about that particular device. NB: I would expect better documentation in the
manpage how to properly specify a device in the commandline parameters.
-- System Information:
Debian Release: 10.9
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fido2-tools depends on:
ii libc6 2.28-10
ii libcbor00.5.0+dfsg-2
ii libfido2-1 1.5.0-2~bpo10+1
ii libssl1.1 1.1.1d-0+deb10u6
ii libudev1241-7~deb10u7
fido2-tools recommends no packages.
fido2-tools suggests no packages.
-- no debconf information
Bug#780776: blueman does not request passkey
Am Fri, 27 Mar 2015 13:03:18 +0100 schrieb Christopher Schramm deb...@cschramm.eu: Hi Andreas, did you check a current upstream version? I checked upstream. Same problem. To see what's going on in blueman (if anything), we need the output from blueman-applet. See https://github.com/blueman-project/blueman/wiki/Troubleshooting for information on this. I have also done some more analysis on that. The problem is related to any agent which does not say it has a keyboard (aka registering as KeyboardOnly or KeyboardDisplay) in combination with that particular device. blueman registers always as DisplayYesNo, so the bug here is that blueman does not say it has a keyboard (which is usually the case). Regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#780776: blueman does not request passkey
Package: blueman Version: 1.99~alpha1-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? blueman-applet was running in the mate panel. Then a program did a connect() on a l2cap socket with cid set to ATT_CID and BT_SECURITY set to high. * What was the outcome of this action? connect() gave a EINPROGRESS error nothing pops up from blueman that requests for a passkey, the peripheral does not display one. using bluetoothctl instead works by entering at its prompt: [bluetooth]# agent KeyboardOnly Agent registered [bluetooth]# default-agent Default agent request successful [NEW] Device XX:XX:XX:XX:XX:XX Request passkey [agent] Enter passkey (number in 0-99): * What outcome did you expect instead? blueman should popup a window asking for a passkey as bluetoothctl did on the console. *** End of the template - remove these template lines *** -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages blueman depends on: ii bluez 5.23-2+b1 ii dbus1.8.16-1 ii gir1.2-appindicator3-0.10.4.92-3.1 ii gir1.2-gconf-2.03.2.6-3 ii gir1.2-gdkpixbuf-2.02.31.1-2+b1 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gtk-3.0 3.14.5-1 ii gir1.2-notify-0.7 0.7.6-2 ii gir1.2-pango-1.01.36.8-3 ii gnome-icon-theme3.12.0-1 ii libatk1.0-0 2.14.0-1 ii libbluetooth3 5.23-2+b1 ii libc6 2.19-15 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libglib2.0-02.42.1-1 ii libgtk-3-0 3.14.5-1 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpulse-mainloop-glib0 5.0-13 ii libpython2.72.7.9-2 ii librsvg2-common 2.40.5-1 ii libstartup-notification00.12-4 ii mate-notification-daemon [notification-daemon] 1.8.1-3 ii notification-daemon 0.7.6-2 ii obex-data-server0.4.5-1+b4 ii python 2.7.8-4 ii python-dbus 1.2.0-2+b3 ii python-gi 3.14.0-1 ii python-gi-cairo 3.14.0-1 Versions of packages blueman recommends: ii policykit-1 0.105-8 blueman 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#510348: dillo2.0 fltk package
Hi, just to introduce myself. I'm the creator of that package on http://misc.andi.de1.cc/dillo I have provided that one so that debian users can quickly install dillo. It is not the cleanest way to create a debian package,.. but the quickest. I did not use pbuilder. Because I do not know what's the clean way with fltk2 (since it is a snapshot ...) I decided to not package it and I just did the usual ./configure make make install for the fltk snapshot before starting dpkg-buildpackage. And yes, the build dependencies are wrong (gtk is of course no build dependancy). I just took the old debian diff and changed it as less as needed. Greetings Andreas Kemnade signature.asc Description: PGP signature
