> Not sure if someone is interested, thus OT, but I just read Qt6 was released
>
> https://www.qt.io/product/qt6
>
>
> ____________________________________________________
> tde-devels mailing list -- devels(a)trinitydesktop.org
> To unsubscribe send an email to devels-leave(a)trinitydesktop.org
> Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydesk…
>
Cool.
Thanks
Kate
https://www.trustedcaptain.com/hvac-repair-services-near-me.html
If you don’t know how to get your hands on Cheap Air Conditioning Repair Near Me services then Don’t get tensed anymore just make a call on our 24*7 operational toll-free helpline number and we help you in getting dedicated HVAC Repair, installation & maintenance Services related to various heating brands and companies within no time. We have leading professionals on our platform who are available even in the odd hours to offer you the desired solutions. Our HVAC technicians have genuine experience in providing customer-oriented Heating And Air Conditioning services for commercial & residential places.
Since installing the TDE/Ubuntu 20.04.1 image (in a VirtualBox), it had
not displayed the GRUB boot menu, it displays a couple of lines (as if
it were a terminal window), then goes straight to the Ubuntu splash screen.
The beginning of the original /etc/default/grub file was:
GRUB_DEFAULT="0"
GRUB_TIMEOUT_STYLE="hidden"
GRUB_TIMEOUT="0"
GRUB_DISTRIBUTOR="`lsb_release -i -s 2> /dev/null || echo Debian`"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
I manually made the following changes:
* removed: GRUB_TIMEOUT_STYLE="hidden"
* made: GRUB_TIMEOUT="5"
then ran update-grub and rebooted. The GRUB menu now appears.
I would like to offer a friendly suggestion that for future TDE/Ubuntu
images, if this is possible to do, the default grub file not contain
GRUB_TIMEOUT_STYLE="hidden" and the GRUB_TIMEOUT entry be set to at
least 3.
Please note that I do not know if the original default items copied
above, is the actual standard for all Ubuntu images.
Ubuntu offers a package grub-customizer. When I looked at that, the
General settings indicated the GRUB menu was set to display, but it
seems that the GRUB_TIMEOUT_STYLE="hidden" entry overrides that and was
preventing it from displaying. After saving the settings in
grub-customizer, GRUB_TIMEOUT_STYLE="hidden" was still in /etc/default/grub.
Debian released version 10.7 yesterday and I decided to install Debian
on my other desktop directly, as I saw no need for two of the same
distro to be installed, as I'm not really testing anything.
Debian required a non-free firmware package for it to recognize the AMD
Radeon video and once that was installed and system rebooted, the
graphical desktop came up fine and I was then able to install Trinity.
When Debian 11 (bullseye) is officially released next year, is it best
to wait and upgrade everything (Debian and Trinity packages) at the same
time? I do not know if it is safe to upgrade just Debian to bullseye, if
the Trinity packages for bullseye were not yet available at the same
time. I am aware that Debian 10 is being supported for five years from
the date it was initially released.
Thanks in advance.
--
This message was sent using virtual technology.
Hi all,
to move forward on the list of service migrations, we have the sixth item
here - Weblate.
-- Migration status --
TDE Weblate Translation Workspace (TWTW) is a new service that was set up
on VPS. It is fully functional and therefore there is currently no need to
address its migration.
-- What needs to be done --
The second stage of TWTW integration is currently underway. This is adding
translations for desktop style files. Only modules that are built with
CMake are added, because merging translations into desktop files is not
done by some external magic script, but by intltool-merge during build.
We then envisage a third level of integration, for the translation of
documentation and manual pages. However, it will first require preparing
CMake macros to handle the documentation and to merge translations of the
documentation and manual pages during build.
If this proves to be useful, we can consider a TDE skin for TWTW. However,
this is a matter that currently has no priority.
-- More ideas and suggestions?
Does everything work fine with the TWTW?
Do you have any other ideas and suggestions?
Cheers
--
Slávek
Hi all,
the fifth service on the migration list is Bugzilla. For the Bugzilla, the
situation is significantly different, because we need to discuss here
before any steps are taken.
-- Migration status --
Bugzilla is on Tim's original infrastructure. Therefore, no one else can
manage the current instance. And there are various issues that we are
currently unable to resolve, such as problem with login when https is
used. So it definitely needs some change.
-- What needs to be done --
First of all, we need to discuss and decide whether we want to continue
using Bugzilla.
As mentioned earlier, TGW is now used as a comprehensive workspace. And
TGW contains Issues that can be used instead of bug reports in a separate
Bugzilla. There are several benefits to using Issues. Above all, Issues
are well integrated into the development workflow. It also provides good
comfort - for example, it is possible to use comment formatting to make it
more readable and clear. At the same time, it seems like a good idea to
use one problem reporting tool rather than two independent ones.
If we find a consensus that there is no significant reason to use Bugzilla,
we need to decide how to deal with existing bug reports. There are two
options:
1) Migrate Bugzilla to a new instance, which will be locked for adding new
bug reports. This can be done more easily. However, the problem remains
that there will continue to be two places for users to look for problem
reports.
2) Migrate bug reports from Bugzilla into Issues in TGW and then stop
Bugzilla completely. Although it is likely to be more difficult to do, I
think it would be a better solution.
-- More ideas and suggestions?
What is your opinion on Bugzilla migration?
Do you have any other ideas and suggestions?
Cheers
--
Slávek
I see no option to turn compositing on or off in KControl's display settings. Is
there one somewhere else? Does TDE never use it?
--
Evolution as taught in public schools, like religion,
is based on faith, not on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
Hi all!
I've an interesting problem: On my T14 the speakers are on hw:0 and are linked to the speaker-led (led on: mute, led-off: unmute - looks like a hardware thingie as toggling the led toggles the speaker). And there's a ghost-mic on hw:0 that looks like a loopback device from PCM-out to sound-input.
HDMI is on hw:1 and does nothing useful (no HDMI monitor attached).
The onboard mic is hw:2,0 - it's offically recognised as "asc" without any controls (not even on/off). It's also detached from the mic led - I can toggle the LED but the mic stays on.
Now kmix sees hw:0 and hw:1, but not hw:2 - and krec cannot capture sound. Audacity sees hw:0 + hw:1 + hw:2 and can record sound. Is there a trick to make TDE aware of that "asc" mic?
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
I am trying to change the screen background in Trinity's Konsole and not
having any luck.
In PCLinuxOS, it defaults to white text on a black screen.
Settings/Configure Konsole/Schema shows it's on 'Linux Colors'.
In both Debian and Ubuntu, it's the opposite, default is black text on a
white screen. The Schema setting in both, is on 'Black on Light Color'.
In all three, if I change the Schema to 'Transparent, Light Background'
and click Apply, nothing happens. If I exit Konsole and relaunch, the
Schema is back to 'Linux Colors' and 'Black on Light Color', respectively.
PCLinuxOS is the main (or 'host') OS installed on the hard drive, both
Debian and TDE Ubuntu are installed in VirtualBoxes.
Am I perhaps missing a step somewhere??
Thanks in advance.
Ed
Hi humans, AIs and others.
I'm having a little problem with net_applet in that it's not configurable as
user.
Obviously a perms problem but ran out of places to look.
It works normally as root.
Any suggestions?
Kate
