
2025-09-20 04:33:09
@… another bug report (i know i know i'm sorry :P)
https://www.desmog.com seems to have been bridged fine up until sometime this month, and now it's suddenl…
@… another bug report (i know i know i'm sorry :P)
https://www.desmog.com seems to have been bridged fine up until sometime this month, and now it's suddenl…
@… another bug report/suggestion, two actually.
#1: comma separated tags/categories in RSS feeds aren't interpreted as separate tags, but as one big long tag
#2: possibly add hashtag search to bridgy web. you can retrieve a list of posts matching a searched hashtag from most instances (iirc), it might be nice to set this up for …
another pixelfed question for all the pixelfed admins:
for messages, you have inbox, sent and filtered.
I really don't understand how the "filtered" works. there are really (not spam) messages, even to some accounts I WROTE FIRST... @… - can you clarify? else I need to fill out another bug report on github
I was trying to package #FlexiBLAS for #Gentoo, and to be honest, it doesn't look that good.
The first red flag is lack of an open bug tracker. Apparently, there is the tracker on GitLab that's limited to "members of their group and selected external contributors", but it doesn't seem to be used much. So it's "send us an email", and wonder how many people sent us the same bug report before.
The git repository is currently at something tagged 3.4.80 that seems to be prerelease, and its build system is quite broken. Not exactly the best path to verify that the bugs you are hitting are still there.
Now, upstream seems to insist on either using vendored netlib #LAPACK, or statically linking to the system library (we don't install the static libraries). Apparently I can specify the shared libraries instead, but it doesn't work — and it's unclear to me whether it doesn't work because I'm using the shared libraries, or because it doesn't support my LAPACK version. If I build LAPACK without deprecated symbols, it refuses to load it at runtime because of missing symbols. And if I build it with deprecated symbols, it fails to find some symbols at CMake time.
Honestly, I feel like I've spent too much time on this project already, especially given that its future is entirely unclear to me — the current git is quite broken, I have no clue how many issues were reported already and whether my bug reports will receive any reply. It definitely doesn't fare well for a package that we might start to rely heavily on. We don't want a cathedral there.
https://www.mpi-magdeburg.mpg.de/projects/flexiblas
https://gitlab.mpi-magdeburg.mpg.de/software/flexiblas-release
cats doing defect triage
"if report unclear, push off countertop"
"nothng is higher-pri than wet food"
"if bug, eat it"
Collective Recourse for Generative Urban Visualizations
Rashid Mushkani
https://arxiv.org/abs/2509.11487 https://arxiv.org/pdf/2509.11487
Leveraging Large Language Model for Information Retrieval-based Bug Localization
Moumita Asad, Rafed Muhammad Yasir, Armin Geramirad, Sam Malek
https://arxiv.org/abs/2508.00253 …
Interesting debian-user find:
The YouDao plugin of the stardict-plugin package on Debian by default captures the X selection buffer — which can be FROM OTHER APPS — and sends the entire text, unencrypted, to remote servers, without telling the user that it will do this.
The maintainer has marked this bug as "wishlist" because they consider the mention of this in the package description to be sufficient warning.
The package can be pulled in as a Recommends.
Does anyone know why Vimium doesn't seem to "click" on the mastodon web interface any more? I don't use mastodon in the browser often enough to know exactly when this changed. I'd like to understand the problem well enough to know how to report the bug to either mastodon or vimium, does anyone have any insights please? I know @… recently did upgrade the interface, is it that? #a11y #mastodon
If you run Debian 13 systemd-networkd bridging you are going to have a very bad day if you do a stable update of systemd
(It will segfault leaving you with no network)
Update: as pointed out by Colin you also have to be using VLANs.
https://bugs.debian.org/cgi-bin/bugrep
Bug Whispering: Towards Audio Bug Reporting
Elena Masserini, Daniela Micucci, Leonardo Mariani
https://arxiv.org/abs/2509.00785 https://arxiv.org/pdf/2509.…
Bug report here if anyone wants to track or comment on it #a11y
I got this bug report on Friday.
"According to POSIX, the time.h header must declare pid_t as declared in sys/types.h."
This morning, CI is finally happy with the patch series:
19 patches. 21 files changed, 1964 insertions( ), 993 deletions(-)
And I got to learn all about the 'getdate' function. Sometimes I feel like bringing light to the darker corners of the POSIX spec may not always be the wisest path.
Learning Software Bug Reports: A Systematic Literature Review
Guoming Long, Jingzhi Gong, Hui Fang, Tao Chen
https://arxiv.org/abs/2507.04422 https://
@… thanks, I added to upstream <https://bugs.kde.org/show_bug.cgi?id=505552>; and drew attention to the downstream report.
hm. non-invisible rope. That may be worth filing a bug report for the helmet
#Monsterdon
Can I get a Fedora user to test something on ngscopeclient for me?
Download the latest RPM from GitHub Actions CI (specifically the CI package, not one you've compiled yourself and install it.
Does it report a plausible version number
1) in the package itself
2) in the title bar
3) in the about dialog?
Just fixed a bug causing empty strings to appear instead of version numbers in the Debian CI builds and I'm not sure if Fedora was impacted too. It use…
In http://rachelbythebay.com/w/2025/09/11/debtz/ Rachel complains about a change in the Debian tzdata package that changed behaviour of PostgreSQL in a surprising way, without a NEWS item for the package update nor a warning in the release notes.
Here is the Debian bug report:
writing a bug report on a Saturday evening because a library I'm using doesn't have software tests and neither do I 😡
#Python world be like:
"Oh, hi, we wrote a new library implementing this spec."
"Hey, it looks like it doesn't conform to the spec, it doesn't pass the examples from it."
"Oh, you're right, we'll fix it ASAP."
…and that was over 3 years ago.
And yet projects keep adding a dependency on this library which has a single "pre-alpha" release 3.5 years ago and whose very first bug report points out it's incorrect.
TriagerX: Dual Transformers for Bug Triaging Tasks with Content and Interaction Based Rankings
Md Afif Al Mamun, Gias Uddin, Lan Xia, Longyu Zhang
https://arxiv.org/abs/2508.16860
Commit Stability as a Signal for Risk in Open-Source Projects
Elijah Kayode Adejumo, Brittany Johnson, Mariam Guizani
https://arxiv.org/abs/2508.02487 https://
Is Your Automated Software Engineer Trustworthy?
Noble Saji Mathews, Meiyappan Nagappan
https://arxiv.org/abs/2506.17812 https://arxi…