Apologies. I mistakenly sent this orginally to Midi instead of
to the list.
On Sun August 29 2021 08:06:13 midi-pascal wrote:
> Since the last TDE stable upgrade (many months ago), the update-notifier
> applet is not available anymore.
You could check your /var/log/apt/... which usually goes back a
year to see if you can figure out which package got uninstalled
during the updgrade.
My guess would be package-update-indicator which is from Gnome
but works with other desktops.
--Mike
Hi all!
I just found that cannot adjust the subpixel hinting in the antialiasing settings (fonts) any more. It's always greyed out :(
Anybody has seen this, too, and maybe any idea what I can do to solve this?
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Hi all!
Just in case somebody runs into the same issue:
When you configure TDE so that
- it shuts down the computer when you log out
- should not show the logout dialog
chances are ksmserver segfaults on logout instead of shutting the computer down. If it happens to you check that in .trinity/share/config/ksmserverrc these two enries are set to "false":
[Logout]
doFancyLogout=false
showLogoutStatusDlg=false
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
Hello,
I am a long-time debian and TDE user, and just recently upgraded my
buster amd64 machine to bullseye. As part of this upgrade, I also
switch from stable builds to the preliminary stable builds of TDE. For
example, tdm-trinity is versioned to read this:
4:14.0.11~pre26-0debian11.0.0+7 . Essentially everything works as
expected so far. However, one very nagging problem I currently have is
that my sound does not work unless I am rooted. For example, if I issue
the command
aplay bark.au
where bark.au is a snippet sound file of a dog barking, it fails.
However, if I issue the command
sudo aplay bark.au
it works fine. Similar sound playing occurs with any sound-playing
app. For example mpg123, vlc, etc., all require a sudo or be logged in
as root to work.
I have looked all around the WWW to try to find a solution to this
problem. The most common solution is to make sure that user ids are in
the audio group in the /etc/group configuration file. Of course, I have
that, and have confirmed it. This is not a brand new installation after
all, but an upgrade.
Other common remedies I have tried are to fiddle with the pavucontrol
and alsamixer settings. My sound card does not show up in the
pavucontrol (pulse doesn't find my sound card), but DOES show up in the
alsamixer.
I have also looked at the debian sound wiki, and other sources to try to
fix this problem.
Then, I remembered that I often used this form to learn about debian way
back in the days when I first started using debian about 1994 or so.
Perhaps I can get some expert help. Maybe a source I can go down a list
of troubleshoot to nail this one down. It is obviously a permissions
issue (I also looked at device permissions, etc.).
I am not sure if this is a debian/11/bullseye problem of a TDE problem,
so I have cross-posted this help request to the debian-user mailing list
as well (without the TDE information since it is not supported there).
Just a bit puzzled and frustrated.
P.S.
BTW, my sound card is a C-Media, Xonor DG with chip set CMI8788 and uses
the oxygen HD audio driver.
lspci -v output corresponding:
05:02.0 Multimedia audio controller: C-Media Electronics Inc CMI8788
[Oxygen HD Audio]
Subsystem: ASUSTeK Computer Inc. CMI8786 (Xonar DG)
Flags: bus master, medium devsel, latency 64, IRQ 22, NUMA node 0
I/O ports at e800 [size=256]
Capabilities: [c0] Power Management version 2
Kernel driver in use: snd_oxygen
Kernel modules: snd_oxygen
Nothing has changed with the hardware, and I know the setup works. This
seems to be a permissions/software issue.
--
James D. Freels, Ph.D., P.E.
freelsjd(a)gmail.com
865-457-6742 (landline)
865-919-0320 (cell)
Hi! :-)
I installed lately at one of my systems, a fresh Devuan installation
with KDE (stable ver. Beowulf, x64, fully updated).
Then I tried installing the latest TDE (the official way).
At my 1st try (after installing and updating the GPG DEB package), I
tried (via Synaptic), installing the tdebase-trinity package, but
Synaptic refused and aborted, indicating broken packages and
dependencies.
OK. I closed it and opened Konsole -> went root (su -) and I tried apt
(apt install tdebase-trinity).
This time TDE installed properly, but KDE installation was removed
altogether (with the exception of some packages (like SDDM)).
I'm perfectly good with it, and I already (after backing it up),
formatted and reinstalled Devuan without any desktop this time and I
installed TDE on it.
Just out of curiosity, is it possible to install TDE alongside with KDE?
TIA! :-)
Giorgos.
Hello All,
There is routine maintenance scheduled at one of the hosting firms IDA uses
for Thursday, 26th August 2021, beginning at 1:00 AM UTC. The maintenance
window will be 4 hours with an expectation of at least 1 hour of server
unavailability.
Servers : Srv06, Srv09, & tde-mirror-01
Start Time: 2021-08-26 07:00 PM CST [US]
End Time : 2021-08-26 11:00 PM CST [US]
During the period of actual downtime, you will not be able to access your
website(s), your dashboard(s), or other services located on these servers.
We apologize for the late notice and the inconvenience.
Best Regards Everyone,
Michael
Internet Design Alliance, owner
http://inet-design.com/
Hours (US CST): Mon - Thur, 8am - 6pm | Fri, 8am - Noon
Emergency calls: 24x7
Hi, everybody! (I hope you hear Dr. Nick's voice when you read this line.)
My SDD boot . . . isn't booting.
Here's how it unfolded: I popped the side off the case so as to install a
couple of top-facing exhaust fans, controlled by the motherboard, bring
the total case fan count to five (two intake, three exhaust), because with
that many fans none ever really spins up, so the computer is next to
silent. That's all I did in there. I came nowhere near anything having to
do with any of the drives.
When I fired up the computer again I got the usual GRUB menu, the second
item of which was the 20.04-LTS installation on /dev/sdc1. I chose it.
And it booted forthwith -- to the 20.04-LTS installation on /dev/sda1. No
errors, nothing. Just booted the wrong drive.
The SDD (sdc) is working fine -- I can mount it, navigate in it, read and
write to it.
Any troubleshooting ideas that don't involve disassembly? This was working
fine yesterday and isn't today.
--
dep
Pictures: http://www.ipernity.com/doc/depscribe/album
Column: https://ofb.biz/author/dep/