Bug#1063468: linux-image-6.1.0-17-amd64: Loud squeals/crackles from Steelseries 2 Channel HD Audio chipset after restarting from Windows 11

of the linux kernel. I have tested this problem within live environments of both Kubuntu 23.10 (kernel 6.5.0-9-generic) and Fedora 39 (kernel 6.5.6-300.fc39.x86_64). Again, this is whenever I restart from Windows 11. Please let me know if you need further information. Best regards Luke Laptop Specs

Bug#1055246: kde-config-plymouth: Does not appear in system settings

Package: kde-config-plymouth Version: 5.27.8-1 Severity: normal X-Debbugs-Cc: lfara...@debian.org Despite having Plymouth installed, no "Boot Splash Settings" panel appears in KCM, contrary to what is shown in https://screenshots.debian.net/package/kde- config-plymouth -- System Information:

Bug#1054875: /usr/bin/add-apt-repository: python3-launchpadlib required for apt-add-repository

Package: software-properties-common Version: 0.99.30-4 Severity: normal File: /usr/bin/add-apt-repository X-Debbugs-Cc: lfara...@debian.org Using the apt-add-repository command with a Launchpad PPA produces this unhelpful error: $ sudo add-apt-repository ppa:yuezk/globalprotect-openconnect

Bug#1036796: gwenview: Gwenview fails to show any app icons or thumbnails on fresh install

Package: gwenview Version: 4:22.12.3-1 Severity: important X-Debbugs-Cc: luke.ree...@gmail.com On a fresh bookworm install gwenview (with no existing configuration) fails to render any of the in-app icons or thumbnails for directories or images. This is reproducable across the i3 and xfce4

Bug#1030043: hplip-gui: traceback when launching hp-toolbox

On Tue, 7 Feb 2023 21:52:11 -0600 Ryan Thoryk wrote: Changing line 119 in /usr/share/hplip/base/password.py from: get_distro_std_name(os_name) to: get_distro_name() appears to fix the issue. With this change I see a different error when running hp-check: -Traceback (most recent call last):

Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: closed by Sylvestre Ledru (Re: Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

ah! some fascinating news (from another discussion) pulled up the fact that ADA converted to a Certification Mark, back in 1987 http://archive.adaic.com/pol-hist/policy/trademrk.txt In order to be a validated Ada compiler, a compiler must pass an extensive suite of programs called the Ada

Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: closed by Sylvestre Ledru (Re: Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

On Mon, Jul 18, 2022 at 11:06 AM Sylvestre Ledru wrote: > > This bug is fixed. i can see that you believe that to be true, otherwise you would not have closed it. what i am upset by is that you did not consider my opinion or insight to be worth consulting. i am deeply offended by that. l.

Bug#1013920: closed by Sylvestre Ledru (Re: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

reopen 1013920 sorry, Sylvestre, if you could possibly wait, on something this serious, for a response as to whether the fix is valid, that will avoid me having to spend my time reopening the issue or creating a second bugreport. On Mon, Jul 18, 2022 at 10:21 AM Debian Bug Tracking System

Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Mon, Jul 18, 2022 at 10:16 AM Sylvestre Ledru wrote: > > Thanks for bringing it to our attention, I have consulted with the Rust > foundation, we have agreed a change, we think this change solves it. ah! we may have

Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

i've opened up a second bug for gcc because it is also about to become affected, not in the same way, but in a worse way. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015242 whilst 50% of DFSG 2 is violated by the Rust Trademark (as it stands, with the new clauses), gcc is in an even worse

Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

https://developers.slashdot.org/story/22/07/17/0110250/gcc-rust-approved-by-steering-committee-beta-likely-next-april and now it becomes Unlawful for Debian to distribute gcc with patches, as well [without the explicit consent of the Mozilla Foundation, an action which is in direct violation of

Bug#1003824: Difference in current filename packaging conventions leads to downloads being ignored by apt

I also experience this problem; after running debdelta-upgrade I use this snippet (all on one line; not elegant) to fix up the files so that apt can find them: for i in /var/cache/apt/archives/*%*; do sudo mv -n "$i" `perl -e '$ARGV[0] =~ s/%(2b|7e)/chr(hex($1))/ge; print $ARGV[0]' "$i"`; done

Bug#993957: closed by Christoph Biedl (Re: Bug#993957: (no subject))

On Sun, May 29, 2022 at 12:16 PM Debian Bug Tracking System wrote: > #993957: schroot: fails with non-existent subdirectory > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate

Bug#991455: gitolite3: underscore in username causes corruption and incorrect behaviour

well, i just checked after upgrading to 3.6.11-2 and the repository in question has now *entirely disappeared* from the config! i've had to downgrade to 3.6.6-1 to get things functional (it's a live-running server) this does actually work, so during scheduled downtime moments i can switch to the

Bug#991455: gitolite3: underscore in username causes corruption and incorrect behaviour

i've created a test account, stupidly upgraded first so i cannot check the "broken" case. i will therefore use the original account with the underscore, however i need to ask a 3rd party to run the ssh command. the setup i have is quite comprehensive, 30 ssh keys 25 projects, it may be an

Bug#991455: gitolite3: underscore in username causes corruption and incorrect behaviour

Package: gitolite3 Version: 3.6.6-1 Severity: important Tags: upstream Dear Maintainer, i have used gitolite3 for many years, this is the first time i have ever had a major bug, and it involved a username with an underscore in it. ssh to the server reported "hello user" not "hello user_",

Bug#986887: linux-image-5.10.0-5-amd64: mpt3sas driver fails to initialize drives on LSI SAS2116 chipset without a queue depth workaround

Package: src:linux Version: 5.10.26-1 Severity: important Tags: upstream X-Debbugs-Cc: luke.ree...@gmail.com Dear Maintainer, I've upgraded from Buster to Bullseye and my external drive array using an LSI SAS2116 chipset (and the mpt3sas driver) stopped detecting all drives. There were no

Bug#718272: Processed: reopening 718272

to interactively prompt the user during upgrade. Maybe if softforks were turned into a runtime option, that could resolve that issue. What do you think? For reference, the meeting log: https://bitcoin.jonasschnelli.ch/ircmeetings/logs/bitcoin-core-dev/2021/bitcoin-core-dev.2021-01-07-19.00.moin.txt Luke

Bug#718272: Processed: reopening 718272

remains consensus-compatible, including NOT fixing any bugs without a proper consensus-compatibility audit. 2) Backport (at least) security fixes for Debian's security support period. Upstream, we generally only maintain releases for a year or so at most. Luke On Thursday 07 January 2021 13

Bug#974563: corosync unable to communicate with pacemaker 1.1.16-1+deb9u1 which contains the fix for CVE-2020-25654

On Sat, 14 Nov 2020 04:02:40 +0100 Markus Koschany wrote: Am Freitag, den 13.11.2020, 23:13 -0300 schrieb Alejandro Taboada: > Hello Markus, > > It doesn’t work. The output log is quite different. I throws a timeout and > just at the end the “unprivileged client crmd”. > See attached log.

Bug#968666: electrum: exception which prevents startup "Non keyword-only attributes not allowed after..."

On Wed, Aug 19, 2020 at 3:29 PM Tristan Seligmann wrote: > > Control: tags -1 - upstream > Control: forcemerge 968563 -1 > > On Wed, 19 Aug 2020 at 14:48, lkcl wrote: > > > > ValueError: Non keyword-only attributes are not allowed after a > > keyword-only attribute. Attribute in question:

Bug#968666: electrum: exception which prevents startup "Non keyword-only attributes not allowed after..."

On Wed, Aug 19, 2020 at 6:34 PM Tristan Seligmann wrote: > > the normal approach to this would be to release a version of the > > electrum packaging that specifically depends on that specific version > > of python3-attr or above. the following to go into debian/control: > > Yes, the next upload

Bug#962501: Unable to Reproduce

I have reinstalled my system, and I no longer can reproduce this issue. -- Luke Mezera

Bug#962501: gnome-terminal: Closing a terminal window at a root promt will crash the Gnome session.

Package: gnome-terminal Version: 3.30.2-2 Severity: normal Closing a terminal window at a root prompt will crash the Gnome session. * What led up to the situation? Open a Gnome-Terminal window sudo su - close window Click "Close Terminal" on the "Close this terminal?"

Bug#958723: ninja-build: ninja -t browse broken due to upstream bug; patch available

be sufficient without needing to wait for the upstream stable release which includes it. All the Best Luke -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System wrote: > #958166: python3-all: python3 can't import gmpy2 > Python3.7 is no longer supported in Debian Unstable and Testing and will be > removed shortly. if you were talking about python 3.6, there would be absolutely no problem,

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

here is a package that contains a build system that, unlike the python3-numpy team, relies exclusively on python3-all. like python3-gmpy2, note that it does not contain enumeration of the minor versions of python. its control file does not list multiple versions of python3, either, choosing

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

you do realise, scott, that python3-numpy has been forced into a position of bypassing the careless unthinking decision that you've made, by including the capability to manually enumerate and compile up multiple versions for different versions of python3? instead of closing the bugreport and

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the python3-all package: > > #958166: python3-all: python3 can't import gmpy2 > > It has been closed by Scott Kitterman . > > Their

Bug#958166: severity 958166 critical

after some consideration, i realised that the removal of python3.7 as a dependency from python3-all results in "unrelated software on the whole system break", and that this is reminiscent of the critical error made by ubuntu, over 10 years ago. 1 criticalmakes unrelated software on the

Bug#958166: Processed: severity 958166 critical

https://alioth-lists.debian.net/pipermail/python-modules-team/2020-April/066373.html we're starting to see additional evidence of the seriousness of this one. an attempt to (auto-) build python3-pythonmagick failed due to libboost-python however i just attempted it myself, and: * apt-get

Bug#958043: [critical] #958166 - python3-all has had python3.7 removed

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958166 this is serious enough to bring to a wider audience's attention, immediately. just as happened over 10 years ago, a mistake made by the ubuntu team making python-all depend on only a single version of python has just been repeated, in

Bug#958043: Acknowledgement (python3-gmpy2: import gmpy2 fails)

unfortunately, because of the way that python3-gmpy2 has been compiled, attempting to install an older version FORCE removes (or conflicts with) an existing installation of python 3.8. therefore if, as many people will have, they are transitioning from python 3.5 to 3.6, 3.6 to 3.7, 3.7 to 3.8,

Bug#955022: i915: Frequent graphics lockups; GPU HANG: ecode 9:1:0x00000000, hang on rcs0

ian 9.2.1-24)) #1 SMP Debian 5.4.13-1 (2020-01-19) [3]: https://gitlab.freedesktop.org/drm/intel/issues/673 [4]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395 Please let me know if there's any additional information I can provide. Cheers, Luke Faraone -- Package-specific i

Bug#949747: closed by Simon McVittie (Re: Bug#949747: gimp: dependency versions missing)

thank you simon, i've passed that on to christian. l.

Bug#864997: DEP-5 copyright checker

ake "initiative" if you know what i mean, there. thanks felix. l. On 12/14/19, Felix Lechner wrote: > Hi Luke, > >> so i wrote a program called copyright_check.py which covers every single >> possibility of what is correctly matched, what is incorrectly matched, >&g

Bug#940701: nautilus-dropbox: diff for NMU version 2019.02.14-0.1

includes a new orig.tar.bz. Note that I was engaging with Unit 193 on Mentors, please check that before NMUing next time. Cheers, Luke Faraone

Bug#932960: python-django doesn't fix a CVE and drops Python 2 support at the same time

at care about security support[2][3]. [1]: https://tracker.debian.org/news/1042323/accepted-python-django-2223-2-source-all-into-unstable/ [2]: https://www.debian.org/security/faq#testing [3]: https://wiki.debian.org/DebianTesting#Considerations Cheers, Luke Faraone signature.asc Description: OpenPGP digital signature

Bug#931710: [pkg-cryptsetup-devel] Bug#931710: Cryptroot-unlock Timeout on askpass

Hi Guilhem, This is the package; https://gitlab.com/kalilinux/packages/cryptsetup-nuke-keys seen as this is not a Debian related package causing the issue, I am happy if you want to close. Kind regards, Luke Flinders -Original Message- From: Guilhem Moulin Sent: 13 July 2019 03:46

Bug#931710: [pkg-cryptsetup-devel] Bug#931710: Cryptroot-unlock Timeout on askpass

Hi Guilhem, So have done some more testing and it seems that the removal of cryptsetup-nuke-password resolves the issue. I had however tested this before and had it all functioning. Hopefully this helps direct debugging a little better. Kind regards, Luke Flinders -Original Message

Bug#931710: [pkg-cryptsetup-devel] Bug#931710: Cryptroot-unlock Timeout on askpass

/sda1 during installation UUID=5264b2eb-3b0c-4b82-896b-c44b1dd5bae6 /boot ext2defaults 0 2 /dev/mapper/kali--vg-swap_1 noneswapsw 0 0 Kind regards, Luke Flinders -Original Message- From: Guilhem Moulin Sent: 09 July 2019 15

Bug#931710: Cryptroot-unlock Timeout on askpass

, Luke Flinders Security and Network Engineer IP Performance Ltd 1-3 Merietts Court, Long Ashton Business Park, Long Ashton, Bristol, BS41 9LW Office: +44 1275 393382 24/7 Support: +44 8708 409100 Email : lflind...@ip-performance.co.uk<mailto:lflind...@ip-performance.co.uk> [IPP Iogo news

Bug#929927: python-django: CVE-2019-12308: AdminURLFieldWidget XSS

acker/CVE-2019-12308 > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12308 > > [1] https://www.djangoproject.com/weblog/2019/jun/03/security-releases/ > > Luke, do you still plan to take this as discussed during the embargo?

Bug#929709: libgdbm6: file exists in libgdbm-dev as well as gdbm

On Fri, May 31, 2019 at 5:09 AM Dmitry Bogatov wrote: > > Unpacking libgdbm-dev:amd64 (1.18.1-4) ... > > dpkg: error processing archive > > /var/cache/apt/archives/libgdbm-dev_1.18.1-4_amd64.deb (--unpack): > > trying to overwrite '/usr/share/info/gdbm.info.gz', which is also in > > package

Bug#928190: /usr/bin/pip ImportError

Package: python-pip Version: 9.0.1-2+deb9u1 When I invoke `usr/bin/pip` i receive an error. $ /usr/bin/pip Traceback (most recent call last): File "/usr/bin/pip", line 9, in from pip import main ImportError: cannot import name main Changing `from pip import main` to `from pip._internal

Bug#915675: libasound2-data: Kernel 4.18 change breaks WD15 dock usb audio

eams git. But we have to find a solution > where kernels < 4.18 are working as well. Thats not that easy, > though. Since we're going with 4.19+ in Buster, if we can't find a config  that work in both >/<4.18, would it make sense to ship the config that'll work in the shipped kernel? Cheers, Luke Faraone signature.asc Description: OpenPGP digital signature

Bug#852199: Nix and non-standard-toplevel-dir

is the case with snapd, which uses `/snap` in all other distributions. We currently override it, but the issue was brought up in a bug report.[1] I think the same arguments apply to both Nix and snapd; but perhaps two is not yet numerous enough to warrant documenting in policy. [1]: http://bugs.d

Bug#911198: Browser console empty, all settings deactivated

On Thu, 1 Nov 2018 at 10:46, Carsten Schoenert wrote: > Am 17.10.18 um 12:59 schrieb Luke W Faraone: > > Invoking with ``thunderbird --start-debugger-server`` and using the > > Firefox WebIDE's remote debugger > > could you please give a small step by step how to reprodu

Bug#911198: Browser console empty, all settings deactivated

evtools/client/shared/vendor/react-redux.js ./source.filter:devtools/client/shared/vendor/react-test-renderer-shallow.js Cheers, Luke Faraone signature.asc Description: OpenPGP digital signature

Bug#909630: gitlab: no sysvinit scripts installed or available

On Wed, Sep 26, 2018 at 10:30 AM, Dmitry Smirnov wrote: > On Wednesday, 26 September 2018 3:05:32 PM AEST Luke Kenneth Casson Leighton > wrote: >> appreciated, dmitry: apologies, it catches me off-guard when things >> don't work. > > No worries. It would be nice t

Bug#909630: initscript found

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Sep 26, 2018 at 6:03 AM, Dmitry Smirnov wrote: > On Wednesday, 26 September 2018 2:10:09 PM AEST Luke Kenneth Casson Leighton > wrote: >> https://gitlab.com/gitlab-org/gitlab-ce/raw/master/lib/su

Bug#909630: gitlab: no sysvinit scripts installed or available

appreciated, dmitry: apologies, it catches me off-guard when things don't work. it was just that the decision to rail-road systemd in (which is software that itself is being developed incredibly unethically) - was itself made unethically (not thinking of the harm that could result, and without

Bug#909630: initscript found

https://gitlab.com/gitlab-org/gitlab-ce/raw/master/lib/support/init.d/gitlab this is semi-suitable: at least it has been possible to get things up and running, by removing the section starting "Script variable names" and relying on the entries in /etc/default/gitlab that are absolutely fine in

Bug#906027: shellcheck: unable to decommit memory: Invalid argument

Package: shellcheck Version: 0.4.4-4 In Debian 9, running shellcheck against a moderate-size file results in the error message shellcheck: unable to decommit memory: Invalid argument I can reproduce this with these commands: docker run -it debian:9 apt-get -y update apt-get -y

Bug#905407: ssh-keygen: Use new OpenSSH key format by default

Package: openssh-client Version: 1:7.7p1-3 Severity: wishlist File: /usr/bin/ssh-keygen The bcrypt KDF key format was released as part of OpenSSH 6.5 in 2014. It provides greater resistance against brute-force attacks on encrypted private keys, and is now widely compatible. We should use it by

Bug#901006: closed by Ben Hutchings (Re: Bug#901006: linux-image-4.16.0-2-amd64: "core has locked up" kernel messagee)

On Fri, Jun 8, 2018 at 2:27 AM, Debian Bug Tracking System wrote: > -- Forwarded message -- > From: Ben Hutchings > To: 901006-d...@bugs.debian.org > Cc: > Bcc: > Date: Fri, 08 Jun 2018 02:24:57 +0100 > Subject: Re: Bug#901006: linux-image-4.16.0-2-amd64: "core has locked up" >

Bug#900930: CVE-2018-10057 CVE-2018-10058

The severity is wrong on this. The first one is a very minor issue (only the admin can trigger it), and the second one is not a bug at all. On Wednesday 06 June 2018 21:01:42 Moritz Muehlenhoff wrote: > Package: bfgminer > Severity: grave > Tags: security > >

Bug#900377: git: Debian git package can now include git-p4 Perforce proxy

>> >> Cool! Is there a bug open to package p4 in Debian? > > Not as far as I know. I could start the ball rolling with a bug > report. I guess the question is how many people would actually use it. I've sent a support request to Perforce to see what they think of this. The BSD license means

Bug#827844: git: man git: dead link

Bug 827844 seems to have been fixed upstream. The link now in the man-page is: https://git.github.io/htmldocs/git.html Using git version 1:2.17.1-1. It looks like it was fixed by Jonathan: commit f79358279c4b447b1318a922e15705d2a00fc5a2 (origin/jn/preformatted-doc-url) Author: Jonathan Nieder

Bug#900377: git: Debian git package can now include git-p4 Perforce proxy

On 29 May 2018 at 22:21, Jonathan Nieder wrote: > forcemerge 715534 900377 > quit > > Hi, > > Luke Diamand wrote: > >> Originally the Debian git package included this tool, but it was removed >> in 2014 because - at the time - the Perforce command-li

Bug#884038: 884038: 2.15.x fails to fetch remote repository - introduced in d0c39a49ccb5dfe7feba4325c3374d99ab123c59?

I think this bug report may be about the same issue that I came across a while back here: https://www.spinics.net/lists/git/msg316628.html I found that the problem was "introduced" in d0c39a49ccb5dfe7feba4325c3374d99ab123c59, first released in 2.15.0 (as also noted in the bug). >revision.c:

Bug#900377: git: Debian git package can now include git-p4 Perforce proxy

in organizations where Perforce is in use for version control, but who would prefer to use the standard git frontend (and for whatever reason can't use Perforce's own git-fusion tool). Thanks Luke -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable

Bug#899372: procps update breaks firewall routing.

Package: procps Version: 2:3.3.9-9+deb8u1 Earlier today this security update to procps (and libprocps3) affected traffic handling on several of our 'jessie' firewalls. This was then resolved when we issued a 'shorewall restart'. On an affected firewall, tcpdump shows incoming packets hitting the

Bug#899220: Generating PNG graphs raises NotImplementedError

Package: wotsap Version: 0.7-5 Severity: normal ``` $ wget https://pgp.cs.uu.nl/archive/wot-0.2/latest.wot -O .wotsapdb $ wotsap -o foo.png 0C14A470 D4311E58 [… normal trust path output omitted…] Traceback (most recent call last): File "/usr/bin/wotsap", line 1903, in

Bug#895703: Continuous LIBUSB_ERROR_NO_DEVICE in journal after removing a Yubikey 4 (USB-C)

ifferent than "normal" USB. Yeah, attaching USB-C devices always generates xhci / pcieport spew in dmesg. (enclosed for curiosity) > Also please generate a "udevadm monitor" log. > Start "udevadm monitor --property" (no need to be root) > Plug the reader > U

Bug#895703: Continuous LIBUSB_ERROR_NO_DEVICE in journal after removing a Yubikey 4 (USB-C)

On Sun, Apr 15, 2018 at 6:01 PM, Ludovic Rousseau <ludovic.rouss...@free.fr> wrote: > Exact. > > Try with this new patch. > You will have to remove the previous patch, or start from the clean sources > first. Aha, now we have something. -- Luke Faraone;; Debian & Ubu

Bug#895703: Continuous LIBUSB_ERROR_NO_DEVICE in journal after removing a Yubikey 4 (USB-C)

Enclosed. Doesn't appear to have changed the output. On Sun, Apr 15, 2018 at 3:49 PM, Ludovic Rousseau <ludovic.rouss...@free.fr> wrote: > Le 15/04/2018 à 17:07, Luke W Faraone a écrit : >> >> On 15/04/18 12:05, Ludovic Rousseau wrote: >>> >>> - kill any

Bug#895703: Continuous LIBUSB_ERROR_NO_DEVICE in journal after removing a Yubikey 4 (USB-C)

On 15/04/18 12:05, Ludovic Rousseau wrote: > - kill any already running pcscd process > - run the newly compiler pcscd > $ sudo src/pcscd --foreground --debug --color | tee log.txt > > - connect the Yubikey 4 (USB-C) > - disconnect the device > - stop pcscd by Ctrl-C after the problem occurred >

Bug#895703: Continuous LIBUSB_ERROR_NO_DEVICE in journal after removing a Yubikey 4 (USB-C)

. This does not occur with a Yubikey Neo (USB 2.0). I was also able to replicate it on a fellow developer's XPS 13 9350. Please let me know if there is any other debugging information I can provide. Cheers, Luke Faraone -- System Information: Debian Release: buster/sid APT prefers unstable

Bug#892504: [PATCH] nspr: Please add support for the RISC-V architecture

On Fri, Mar 9, 2018 at 8:31 PM, Karsten Merker wrote: > There is one thing that I am a bit unsure about, though, and that > is Mozilla's use of WORD and DWORD in their size definitions as I > haven't found any documentation about that. hiya karsten, ok so someone from

Bug#891411: Acknowledgement (mailman critically (and unnecessarily) linked to apache2 (and not nginx))

On Mon, Feb 26, 2018 at 7:51 AM, Thijs Kinkhorst <th...@debian.org> wrote: > On Sun, February 25, 2018 12:13, Luke Kenneth Casson Leighton wrote: >> apologies, after downloading the source i noted that the debian/rules >> debian package. i've installed lighthttpd, disabled it

Bug#882149: python3-sqlalchemy-utils depends on python-arrow (and so python2)

Package: python3-sqlalchemy-utils Version: 0.32.14-2 Package python3-sqlalchemy-utils depends on python-arrow, the python2 package, and so can't be installed on a python3-only system. Should it depend on python3-arrow instead? Thanks!

Bug#718272: [Pkg-bitcoin-devel] Bug#718272: Bitcoin still not ready for stable release in Debian

On Friday 03 November 2017 1:27:24 PM Jonas Smedegaard wrote: > Quoting Luke Dashjr (2017-11-03 11:25:23) > > > On Friday 03 November 2017 9:10:37 AM you wrote: > >> I believe Bitcoin is now stable enough for stable release. > > > > Things have only gotte

Bug#718272: Bitcoin still not ready for stable release in Debian

On Friday 03 November 2017 9:10:37 AM you wrote: > I believe Bitcoin is now stable enough for stable release. Things have only gotten less stable upstream since 2013... What is the plan for getting security and protocol change updates backported to Debian stable? Luke

Bug#880039: beara fails without en_US.UTF-8 locale

o/Bear/commit/b5d831ea158a8eff0b5dcb3d863e0046528189e6) Without this commit it seems like any user of `bear` will have to have en_US.UTF-8 installed. Is there any possibilty debian can backport this fix, or do a version bump? All the Best Luke -- System Information: Debian Release: bus

Bug#879652: rpl has a python3 shebang but fails with NameError raw_input

100755 --- rpl +++ usr/bin/rpl @@ -5,12 +5,6 @@ try: import readline except ImportError: pass from stat import * -try: -raw_input -except NameError: -raw_input = input - - def show_license(*eat): print ("""rpl - replace strings in files Copyright (C) 2004-2

Bug#877370: Doesn't allow saying "do not print answers"

Package: purity-ng Version: 0.2.0-2.1 Severity: important purity-ng incorrectly checks the user's answer to the "should answers be printed" text, v.s. accepting "n" as an answer. -- System Information: Debian Release: 9.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500,

Bug#876065: Invalid upstream-signing-key

Package: yubico-piv-tool Version: 1.4.2-2 Severity: normal The file is in ASCII-armoured format, which is incorrect for `debian/upstream-signing-key.pgp`. The file should should instead be renamed to `debian/upstream/signing-key.asc`. $ uscan uscan: Newest version of yubico-piv-tool on remote

Bug#875719: Cannot install, depends on non-existant yubico-piv-tool >=1.4.3

Package: yubikey-piv-manager Version: 1.4.2-2 Severity: grave yubikey-piv-manager depends on yubico-piv-tool (>=1.4.3), but that package is not in the archive. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500,

Bug#872036: Acknowledgement (AH00060: seg fault or similar nasty error detected in the parent process)

ok so a little more info here: the segfault occurs *directly* after a logrotate-inspired signal is received. [Sat Aug 19 06:25:37.746265 2017] [mpm_event:notice] [pid 21345:tid 3074504512] AH00493: SIGUSR1 received. Doing graceful restart [Sat Aug 19 06:25:39.647852 2017] [core:notice] [pid

Bug#870211: Dead link: "Wiki help"

Package: nm.debian.org Severity: normal There's a link from /process/:id to the [wiki][1], but unfortunately it appears to be dead. I looked around and wasn't able to find the correct link target. [1]: https://wiki.debian.org/nm.debian.org/Process -- System Information: Debian Release:

Bug#861989: nautilus: Nautilus freezes/crashes when right clicking and selecting properties for 1 or more files

have done the hard reset and it will resolve itself if I leave my computer on for long enough. Thank you very much for your help. I am happy to have this bug now resolved. Regards Luke On Sat, Jun 17, 2017 at 6:21 AM, Jason Crain <ja...@inspiresomeone.us> wrote: > I forwarded this ups

Bug#861989: nautilus: Nautilus freezes/crashes when right clicking and selecting properties for 1 or more files

Hello Jason, Sorry for lack of reply. Been away from my computer. I can confirm that I do have a lot of photos in RAW format about 25Mb each. However once I have finished with the images I then move them to a external hard drive. I will hopefully run the commands tonight. Regards Luke On Fri

Bug#864829: screen reader stops speaking

On Thu, Jun 15, 2017 at 11:39:35PM AEST, Mika Hanhijärvi wrote: > I am using the Gnome desktop. > I have espeakup and Orca installed. I would like to use espeakup on console > and > Orca on desktop. I also would like to be able to switch between text mode > console and graphical nome desktop

Bug#864801: 'winetricks dotnet35' fails to download dotnetfx3.exe

Package: winetricks Version: 0.0+20170101-1 Severity: normal Tags: upstream Running `winetricks dotnet35` fails to download dotnetfx3.exe from the Internet Archive. -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental')

Bug#861989: nautilus: Nautilus freezes/crashes when right clicking and selecting properties for 1 or more files

Hello Jason, Sorry for the late reply - been under the pump. I have re-run the command. -- TERMINAL COMMANDS 001 -- luke@luk-main:~$ pkill nautilus luke@luk-main:~$ tracker-control -S Store: (tracker-control:1853): Tracker-CRITICAL **: Could not retrieve tracker-store status

Bug#861989: nautilus: Nautilus freezes/crashes when right clicking and selecting properties for 1 or more files

Hello Jason, I ran both commands as non-sudo and sudo respectively. -- START tracker-control -S -- luke@luk-main:~$ tracker-control -S Store: ^C luke@luk-main:~$ sudo tracker-control -S [sudo] password for luke: Store: 28 May 2017, 10:27:07: ✗ Store - Unavailable Miners: 28

Bug#862524: License Issue about Distributing NVIDIA's cuDNN library via Debian

Adding Maitreyi, who is the Product Manager for cuDNN. -Original Message- From: lumin [mailto:cdlumin...@gmail.com] Sent: Tuesday, May 23, 2017 11:43 PM To: debian-le...@lists.debian.org Cc: pkg-nvidia-de...@lists.alioth.debian.org; Daniel Stender; Luke Yeager; 862...@bugs.debian.org

Bug#847493: yubikey-piv-manager: diff for NMU version 1.3.0-1.1

-maintainer upload. + * Re-add PySide patch. + * Remove requires.txt requiring PySide (Closes: #847493) + + -- Luke W Faraone <lfara...@debian.org> Wed, 17 May 2017 02:08:22 + + yubikey-piv-manager (1.3.0-1) unstable; urgency=low [ Simon Josefsson ] diff -Nru yubikey-piv-manager

Bug#861989: nautilus: Nautilus freezes/crashes when right clicking and selecting properties for 1 or more files

Hello, The issue will occur on any particular type of file. I have created a video recording me replicating the bug using just a JPG. https://youtu.be/eUI2tVpZ6nY Regards Luke On Fri, May 12, 2017 at 5:36 AM, Jason Crain <ja...@inspiresomeone.us> wrote: > Control: tags -1 + moreinfo &

Bug#846548: patch for #846548

On Thu, 11 May 2017 20:33:41 -0700 Luke W Faraone <lfara...@debian.org> wrote: > On Thu, 11 May 2017 19:45:51 -0700 Luke W Faraone <lfara...@debian.org> > wrote: > > Attached is a patch to fix the path to the engine directory, and moves > > this library back to lib

Bug#846548: patch for #846548

On Thu, 11 May 2017 19:45:51 -0700 Luke W Faraone <lfara...@debian.org> wrote: > Attached is a patch to fix the path to the engine directory, and moves > this library back to libssl-dev. (it isn't clear to me from changelog or > git log why the move to 1.1 was originally reverted)

Bug#846548: patch for #846548

libssl-dev. (it isn't clear to me from changelog or git log why the move to 1.1 was originally reverted) -- Luke diff -Nru libp11-0.4.4/debian/changelog libp11-0.4.4/debian/changelog --- libp11-0.4.4/debian/changelog 2017-01-28 08:13:56.0 + +++ libp11-0.4.4/debian/changelog

Bug#861989: nautilus: Nautilus freezes/crashes when right clicking and selecting properties for 1 or more files

Package: nautilus Version: 3.14.1-2 Severity: important Dear Maintainer, Method ~~ 1.) Open up Nautilus 2.) Navigate to a folder where you want to find the file size of contents 3.) Select the file(s)/folder(s), right hand click 4.) Click on the option "Properties" in the menu Expected

Bug#858377: libblkmaker outdated in Debian

BFGMiner should work just fine with the git version of libblkmaker, and doesn't require libblkmaker to work correctly in many common cases. The simplest solution would be to simply bump libblkmaker.

Bug#860898: [Tts-project] Bug#860898: (no subject)

more of a hard requirement in the past. Luke

Bug#860789: Acknowledgement (freecad: import of openscad file turns "differences" into "unions")

ah: i hadn't spotted this: it would appear that a legitimate scad file is considered to be a syntax error by freecad's parser. Parser Loaded Start Parser Vector Vector Vector Vector Vector Matrix Syntax error in input! LexToken(SEMICOL,';',23,603) Vector Vector Vector Vector Matrix ('$fn', '100')

Bug#848895: Chromium freezes randomly

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Tue, Apr 18, 2017 at 4:08 AM, Michel Dänzer <mic...@daenzer.net> wrote: > On 18/04/17 11:55 AM, Luke Kenneth Casson Leighton wrote: >> On Tue, Apr 18, 2017 at 3:27 AM, Michel Dänzer <mic...@

Bug#848895: Chromium freezes randomly

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Tue, Apr 18, 2017 at 3:27 AM, Michel Dänzer wrote: >> far from being 100% reproducible when resizing glxgears under fvwm2 >> with DRI2, glxgears freezing is now 100% *un*reproducible. > > Please

Bug#848895: Chromium freezes randomly

ok so i ended up with an unancipated reboot, which meant i had an opportunity to test DRI3 and since setting Option DRI "3" in xorg.conf i have *not* encountered a *single* lock-up, not with chromium, nor glxgears, nor openscad. far from being 100% reproducible when resizing glxgears under

  1   2   3   4   5   6   7   8   9   10   >