Yes, the songs are transmitted to your headphones, but that's over a paired Bluetooth connection between the headphone and the phone. And there's no cost to that. You only pay for the data transmitted to your smart device over the phone company's network by way of using the app.
https://spacebarcounter.org
Merry Christmas to everyone here, and thanks for all your help and everything that I and others have learned here this year. This is a unique and welcoming community, which is very rare anymore.
Best to you all.
dep
Pictures: http://www.ipernity.com/doc/depscribe/album
Column: https://ofb.biz/author/dep/
Hello,
Before, I h ad a down right, taskbar, a graphic interface
to manage the ethernet and wlan network.
Now, this iinterface has disappeared.
I use NetworkManager.
How to find again this very practical interface ?
I'am on Debian 12.
Thanks.
Happy Party of New Year tonight.
André
Hi all!
Could sombody please check if this happens on their systems, too:
- open kmail
- select a multipart message
- print the message (cups or pdf-file)
On my system a progress dialog appears and kmail is stuck. On the console I get these errors forever (well, till I kill kmail):
[2024/12/30 18:04:19.436] Fatal Error in TT flags
[2024/12/30 18:04:21.374] Fatal Error in TT flags
[2024/12/30 18:04:21.782] Fatal Error in TT flags
[2024/12/30 18:04:22.191] Fatal Error in TT flags
...
I have seen this some months before but the problem disappeared without my doing Now it's back.
kmail version is 14.2.0~pre121-0debian13.0.0+4
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Hi Folks:
This has long been a thorn in my side. I love Trinity btw!!! Everytime I try to go to install it on Debian I run into an issue with the package desktop -base. Hasn't anyone else has this issue?
Thanks
John
Hi everyone,
I'm on Q4OS (Debian-based) with Trinity Desktop, and as per title, I have a weird issue since I started using Q4OS back in May, and I still haven't been able to solve it: in some (not all) applications, instead of some kind of characters (more specifically, emojis and italics) tofu boxes appear, and I already installed fonts-noto with all its dependencies.
I opened this thread in the Q4OS Support Forum: https://www.q4os.org/forum/viewtopic.php?pid=27828#p27828 and they told me it's a Trinity related bug, as it also happens on a pure Debian fresh install with TDE.
How can it be solved?
TIA
First, thanks everybody for seeing me through the boot crisis. It does seem
to have been the bios settings. Boots reliably now. As to the unattended
shutdown, still don't know. It hasn't happened since. We'll see.
Second, I've been fiddling with keyboards -- almost got a *new* Model F,
but got and am happy with the improved Unicomp Mini Model F. (Details here
for anyone who is interested: https://ofb.biz/safari/article/1272.html )
It has Windows keys -- the nice people at Unicomp are sending me blank
replacements.
I thought that TDE had a native keyboard remapper. I see that Grome does,
in their little trick utilities package. There's also something
called "Input Remapper." But I'd just as soon remain consistent if
possible. The KControl keyboard setting seems to offer only whether the
numlock is on.
So, is there a TDE keyboard mapping utility? If not, anyone have any
experience with something else? (Not counting the commandline. I like it,
but not in this case.)
Thanks!
--
dep
Pictures: http://www.ipernity.com/doc/depscribe/album
Column: https://ofb.biz/author/dep/
My regular desktop died, and I have to purchase a new one.
I will be getting an ASUS Mini PC PN41, which is a rebranded Intel NUC:
- Intel Celeron N4500
- 4GB RAM
- 128GB SSD
Which distro should I use in order to install TDE?
Requirements:
- Keep it simple. I can use commandline tools but prefer not to have to.
- I would prefer to avoid systemd based systems.
My experience with systemd is that it really struggles to perform on
low-powered fanless mini PCs like the Intel NUC boxes.
Looking at the list here
https://wiki.trinitydesktop.org/Category:Documentation#Installing_from_a_Pa…
I *think* that Devuan is the only officially supported distro that is
systemd-less. Is this correct?
Would anyone like to comment or make any other suggestions, before I go
ahead with a Devuan install?
Thanks in advance,
Steve
Greetings, one and all.
Not even remotely a TDE problem, but you lot are known to throw a float to a drowning man even if he fell off some other boat.
System is an Asus vanilla AMD-64 running Debian Trixie and TDE Testing. Was running fine, long uptimes. Got up yesterday to an exploded reboot, so something had taken place during the night. Did a power-off reboot. Now it booted to the point of /dev/sda1 clean. Tried a reboot from grub using linux advanced mode. Once I got it to boot all the way in rescue mode. Fiddled around, found nothing wrong, rebooted. That's the last time I saw TDE.
Poking around, I saw a case similar to mine in which it was suggested that the bios needed upgrading. I looked, and the date on my bios was in 2013, leading ne to think it was possible that this was true, even though I'd changed nothing since it had been booting just fine. So on another machine I d/led the latest bios file and flashed it. Which of course wiped all my settings because bioses seem to be dumb.
Now, when I start the machine it of course has the bios banner, and then grub, and then:
ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x[many zeros]/0x1 (20240322/tbfadt-611)
amd_pstate: the_CPC object is not present in SBIOS or ACPI disabled
r8169 0000:05:00.0: can't disable ASPM; OS doesn't have ASPM control
/dev/sda1: recovering journal
/dev/sda1: clean, 435913/4579328 files, 5183079/18310546 blocks
If I do a warm reboot, it dies at the bios banner. After a minute it tells me the boot device (normal hard drive) is not supported and to set the comparability mode, press F1 to set it. Which I do, and bext boot gives me:
grub>
Which is no use at all so I reboot and now again have a normal grub menu. This time I select Advanced mode for my Linux boot. Now it boots happily along. And I can boit into Debian, TDE, the whole works, though now I am in rescue mode (which looks and acts just like any ordinary boot).
Which is where I am now. In slight terror it will crash again, but otherwise wondering how I can proceed to make things normal again,
Anyone have any ideas?
dep
Pictures: http://www.ipernity.com/doc/depscribe/album
Column: https://ofb.biz/author/dep/
