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/
I did a regular softrware update on my boot drive -- the SSD
at /dev/sdc1 -- and got this:
Configuration file '/etc/grub.d/10_linux'
==> Deleted (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** 10_linux (Y/I/N/O/D/Z) [default=N] ?
I did "D" but have no clue as to what is right here. After looking at it
for a few minutes and ending up no more enlightened than I was when I
started, I kept the default. The first line of the thing is
+# grub-mkconfig helper script.
It contains things such as
+# Default to disabling partition uuid support to maintian compatibility
with
+# older kernels.
+GRUB_DISABLE_LINUX_PARTUUID=${GRUB_DISABLE_LINUX_PARTUUID-true}
Ought I have let it install? It seems a bad idea, but that is totally a
guess.
--
dep
Pictures: http://www.ipernity.com/doc/depscribe/album
Column: https://ofb.biz/author/dep/
/Apparently, my emails from Caramail/GMX aren't making it to the list,
so I've subscribed using a different e-mail. I hope this resolves
whatever the issue is/was.//
//
//This e-mail was sent earlier this afternoon via Caramail/GMX and never
made it to the list./
-------- Forwarded Message --------
Subject: Re: [tde-users] Re: Debian 11 released
Date: Thu, 19 Aug 2021 12:47:48 -0400
From: Edward
To: users(a)trinitydesktop.org
On 8/18/21 8:19 AM, deloptes wrote:
> Edward wrote:
>
>>> Debian has released version 11, bullseye. Should the current TDE
>>> (buster) packages work with bullseye until the packages are updated?
>>>
>>> Thanks.
>> Confirming the TDE desktop (buster) came up fine, after upgrading Debian
>> to bullseye.
> It is not recommended to use packages compiled for buster on the bullseye.
> While most of the code would work, there is no guarantee that things
> are not
> broken.
> You better use TDE for bullseye instead (replace buster with bullseye in
> your source.list).
This is what I've done, I'm now using the stable preliminary builds of
the TDE packages for Bullseye. I commented out the original repo lines
for Buster in the /etc/apt/sources.list file.
Ed
--
Linux. A Continual Learning Experience.
TDE: R14.0.11-pre - Debian: 11 (amd64)
On 8/16/21 3:55 AM, Michele Calgaro wrote:
> On 2021/08/16 12:36:08 AM, Edward wrote:
>> On 8/15/21 10:15 AM, Edward wrote:
>>> Debian has released version 11, bullseye. Should the current TDE
>>> (buster) packages work with bullseye until the packages are updated?
>>>
>>> Thanks.
>>
>> Confirming the TDE desktop (buster) came up fine, after upgrading Debian
>> to bullseye.
>>
>>
>
> Hi Edward,
> you could use PSB packages for bullseye ;-) so you also get rolling
> updates of the changes
> that will go into the next release.
>
> https://wiki.trinitydesktop.org/Preliminary_Stable_Builds
Hi Michele,
Thank you for this information.
I went this route and added the lines to apt/etc/sources.list. Apt
successfully retrieved and installed the R14.0.11-pre packages and it
also resolved the binutils issue. The first desktop is working
perfectly. I will do the same on my other desktop.
The original 'buster' entries for 14.0.10 were left as they were in the
sources.list file.
Ed
--
Linux. A Continual Learning Experience.
TDE: R14.0.11-pre - Debian: 11 (amd64)