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)
Debian has released version 11, bullseye. Should the current TDE
(buster) packages work with bullseye until the packages are updated?
Thanks.
--
Linux. A Continual Learning Experience.
TDE: R14.0.10 - Debian: 10.10 (amd64)
Greets, folks . . .
The nifty little WD 500gb SSD has arrived. I stuck it into a little USB
adapter device and seem to have succeeded in dd'ing my boot
partition. /dev/sda1, onto it. I have employed the appropriate utility to
give it a unique ID, and have labeled its first partition as BOOT. (My
home partition, on the existing /dev/sda, is labeled HOME, and /etc/fstab
are edited to mount LABEL=BOOT as / and LABEL=HOME as /home.)
If things weren't unnecessarily complicated, I could go into the bios and
tell it to boot from USB and check the thing before I mounted it
permanently. Ah, but . . . There's no nice, normal setting to set boot
order in the frigging bios! I can't tell it to just boot from USB and call
it a day. Instead, it offers a variety of choices that include booting
from a drive that has no operating system at all, so it's not smart or
anything like that.
I did update-grub on the existing hard drive installation and it saw and
added the SSD install. Here things get weird: sometimes it shows it and
sometimes it doesn't. Ubuntu in its wisdom has screwed around with the
GRUB2 menu. Initially it didn't't show up at all; after I dicked around
with it a little a few days ago I got it to appear. Even then, it isn't a
GRUB menu as we know it.
By fiddling around with the bios I can get a menu that contains the
SSD -- /dev/ssd1 -- to show up in the GRUB menu, but sometimes not. And
even then, if I select the SSD installation, it does fiddle a little with
the SSD on the way in, but boots to the /dev/sda1 install.
Now, this is especially problematic because the hard drive boot is, as I
mentioned, from /dev/sda1, while /home is /dev/sda3, so just yanking that
drive is not among the relatively convenient possibilities.
I'd like to boot from it, of course, for reasons including the ability to
run update-grub on it, so that the default boot would be from the SSD when
it is happily installed in the system. (After which I'd open a terminal
and again run update-grub so that GRUB would get everything in its final
configuration, with booting from the hard drive possible in case of SSD
failure.)
Any ideas? Prefarably as opposed to guesses?
--
dep
Pictures: http://www.ipernity.com/doc/depscribe/album
Column: https://ofb.biz/author/dep/
> I use a GTK 3 application ("Revolt" on Debian/Devuan) and its titlebar is
> so ugly. I tried to use my TDE style for it in "GTK Styles and Fonts" and
> it only makes it worse. GTK 2 applications look much nicer with Tqt3
> integration, but GTK 3... It's an eyesore no matter what, to say the
> least.This brings me to my question - is there any way to make GTK 3 apps
> integrate more nicely into TDE? I have gtk3-tqt-engine-trinity installed
> but there's only the default style available or use my TDE theme for it
> (which breaks it and makes it look worse).
For GTK3 I recommend installing the package "gtk3-nocsd". It will force GTK3
applications to refrain from drawing their own titlebar (client-side
decoration as the Gnome folks call it) and will restore the TDE titlebars
instead.
Secondly, I recommend the GTK2/3 theme "TraditionalOk" from the "mate-themes"
package of the Debian repositories, which gets quite close to TDE's Plastik
theme. Once installed, you should be able to select it for GTK3 in the "GTK
Styles and Fonts" panel of the control center.
Best regards,
Leskala
Hello!
For Window Behavior, I have
Modifier key + mouse wheel: "Raise/Lower"
This is a great feature which I use all of the time. However, the motion of the mouse wheel seems backwards to what the window actually does. When I pull the wheel towards me, the window moves lower in the stack, which means that it appears to move away from me. Of course, I've been using KDE 3.5/Trinity for ten years in this manner, so I have somewhat gotten used to it. :-) However, I think it would be fantastic to have the option to reverse the sense of the mouse wheel of this.
What do you think of adding a Lower/Raise option which functions the same as the current Raise/Lower, but with the reversed sense? I think this would be a more natural mapping, at least for some of us, and would not detract from anybody else's use of this functionality.
Sincerely,
Daniel.
Hi, all!
I am often connected and disconnecting an external monitor from my laptop. Whenever I do so (and sometimes when the laptop/KDE thinks I did, but I didn't) my various application windows are resized. They are often resized to be full-screen size, and often to minimal size. Either way is inconvenient. Is there a way to disable the resizing of windows when the screen geometry changes?
It would be convenient for the windows to be *moved* such that they are visible in the new geometry but not to be resized.
Sincerely,
Daniel.
Hello everyone :)
After seeing Q4OS with its big icons in Kicker's taskbar I've been searching
far and wide but haven't been able to figure out how to achieve this using
plain TDE on Debian. I managed to make the buttons themselves bigger by
adjusting '~/.trinity/share/config/ktaskbarrc' with:
[General]
MinimumButtonHeight=38
However, icons on the taskbar buttons stay small (16 px). Can somebody
enlighten me which setting Q4OS is using here to enlarge the icons on the
taskbar buttons? Or are they using a patched version of Kicker that is not
available on Debian?
Best regards,
Leskala
Hi all!
I'm working on a small program that unifies the color scheme over all configs of TDE. But I found something that I quite don't understand: .trinity/share/config/kdeglobals has a bunch of color definitions, but almost all are set to "invalid" in my config.
Does anybody know what these are good for - and why "colorScheme=" is empty?
Nik
excerpt with all sectionnames + color from ~/.trinity/share/config/kdeglobals:
[DesktopIcons]
ActiveColor=invalid
ActiveColor2=invalid
DefaultColor=invalid
DefaultColor2=invalid
DisabledColor=invalid
DisabledColor2=invalid
[General]
linkColor=140,140,255
visitedLinkColor=255,136,255
[KDE]
colorScheme=
[MainToolbarIcons]
ActiveColor=invalid
ActiveColor2=invalid
DefaultColor=invalid
DefaultColor2=invalid
DisabledColor=invalid
DisabledColor2=invalid
[PanelIcons]
ActiveColor=invalid
ActiveColor2=invalid
DefaultColor=invalid
DefaultColor2=invalid
DisabledColor=invalid
DisabledColor2=invalid
[SmallIcons]
ActiveColor=invalid
ActiveColor2=invalid
DefaultColor=invalid
DefaultColor2=invalid
DisabledColor=invalid
DisabledColor2=invalid
[ToolbarIcons]
ActiveColor=invalid
ActiveColor2=invalid
DefaultColor=invalid
DefaultColor2=invalid
DisabledColor=invalid
DisabledColor2=invalid
--
Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
