Your message dated Sat, 17 Oct 2026 17:05:29 +0200
with message-id <[email protected]>
and subject line Re: Bug#1121872: Bug on Debian 13 Trixie - Cinnamon - Nemo
6.4.5
has caused the Debian Bug report #1121872,
regarding cinnamon: authentication dialog not shown when double-clicking a
volume that needs a password in nemo
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1121872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121872
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: Nemo
Version: 6.4.5
Severity: minor
Bug Description:
When you access "My Computer" with Nemo, if you find listed disks that are not
mounted at boot, you cannot access them by double-clicking on them.
You need to right-click and choose "Move up" to bypass the problem, or access
it via the left sidebar.
Thank you to correct this as soon as possible.
Best regards.
Philippe
--- End Message ---
--- Begin Message ---
Version: 6.4.12-1
Hi Philippe,
I removed David Zeuthen from Cc. I suppose you added him because he
wrote the initial part of that code (for GNOME Shell, back in 2010), but
he isn't involved in Cinnamon's copy, which the Cinnamon developers have
maintained separately, and I don't want him to receive unwanted mail.
Please avoid adding people who are not involved. And if it was for those
LLM analyses, let it go: rough LLM analyses made in a simple chat should
be avoided for bug reports and contributions, as I was partly trying to
explain in my previous message.
As for the bug, I'm closing it with version 6.4.12-1, where the fix is
already present (Debian testing/unstable). The bug tracker keeps track
of versions, so it will still show as affecting Debian 13 (6.4.10-2).
But closing it doesn't mean the fix will be in Debian 13.8: as I wrote,
a Debian 13 update just for this is not planned for now.
About LLMs, since you asked: getting memories and skills written by
others might help a little, but not significantly. What matters is that
the person using LLMs really understands how they work, and has some
experience in the things they do with them, in order to check the
results. It's better to learn and write your own memories and skills,
based on what you need to do, knowing exactly what is in them and why;
that also helps to notice when the LLM doesn't follow them or is having
problems.
An essential thing to understand is that LLMs are less reliable than
normal software. Apart from bugs and hardware problems, normal software
produces a predictable result; LLMs, on the contrary, make mistakes much
more often, and may also not follow instructions and memories. Besides
that, you have to give them everything they need to have more context
and reliable data: the more they rely only on their internal memory and
training, the worse it gets. Having them run tests also helps a lot to
reduce the problems in what they produce (without tests the results tend
to be poor), and then you still need human review, preferably by someone
with at least some experience.
As for test environments, you have to state in the global memories that
tests must not be done on the host but in the environments prepared for
them (can be useful use llm on different device and remote connect to
it), and take the time to prepare and test those environments. I
prepared chroots, Docker containers and virtual machines with
libvirt/KVM, but it's up to each person to choose based on what they
need and what they have experience with (for checks, and also for part
of the manual tests in the same environments).
I also don't give LLMs access to my mail; for my GitHub account I
created a read-only token, and I don't let them make commits (also in
local). Even when they help me write or improve commit messages, mails,
GitHub messages and so on, I always send them by hand, after checking
them myself and, if needed, changing them again. That's also because
translations of what I write in Italian have got worse since all
translators started using LLMs: they change too much, sometimes cutting
too much, adding things, or even ending up with the opposite meaning.
Anyway, I think it's better to end this here, to avoid off-topic
messages on the bug.
Best regards,
Fabio
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
