You are not logged in.
Hello:
... thank you all for your suggestions and your kindly help.
You're welcome.
If there are no more questions/issues, you can mark your post as solved.
Best,
A.
Hello:
... Macbook Pro 9.1 Mid 2012 2.3GHz.
Right ...
I repeat: if the box runs as expected, there may be nothing wrong.
Linux works around most all of the 'quirks' the BIOS 'cut&paste' brigades produce.
The [dmesg] printout just informs the user of what the system is doing.
That is exactly what it is there for, along with all the other log files available in Linux.
But I am not a fan of suppressing boot time printout.
You may be choosing to ignore some new glitch that could (eventually) come up.
The thing is to get used to the stuff that will never go away because ACPI / BIOS is not precisely top notch.
ie: it was not written to work with (most) OSs that your Intel box could run.
Once the version of the Apple OS intended for that hardware booted with no errors, the task was finished.
That said, do have a look at this video*: https://www.youtube.com/watch?v=YhNg-dSIA9k
It is quite recent and comments seem to be quite favourable.
* I have only skimmed across it, may have valuable information, hardware wise.
Best,
A.
Hello:
... new (old) computer ...
... everything seems to be working.
The system booting and working as expected (?) is a good sign.
Most times [ACPI] warnings are the result of Linux having worked around a badly written BIOS and just informative.
The same can be said by many other 'errors' or 'warnings' present in the [dmesg] output.
Q: Is your BIOS up to date?
ie: last available version.
That said, for anyone to be able to help with your questions, you would have to supply more information.
eg:
- Devuan version installed (please post result of [uname -a])
- full [dmesg] and a short description of the hardware you are installing it on.
- output of [lspci]
- output of [lsusb]
It would seem that your hardware is 'Apple' fare, notorious for not being precisely Linux friendly.
Particularly with respect to motherboard components.
Have you checked on-line as to the degree of compatibility of your specific box with Linux?
eg: T1/T2 chip, touchpads, keyboards, Wi-Fi, sound, webcams and other hardware such as PM sensors/fans.
Best,
A.
Hello:
Just to confirm:
... tried it with xterm and it works.
Does not work with [xfce-terminal], [lxterminal] or [tilix].
Best,
A.
Hello:
... stop immediately to post AI slop ...
... you can't curate ...
... posted it because it looks convincing.
Note taken.
Will not happen again.
That said, please do read the whole bit, especially these caveats*:
Never used [wall] or [lightdm].
... and only to see if an [AI] answer can be (?) useful ...
... this is just a test), out of curiosity I searched ...
* my fault, I should I have posted [CAVEAT] in capital letters somewhere.
Having made clear that I did not use [wall] or [lightdm], how could it possibly look convincing to me?
I did not look like anything but AI generated stuff, something I disclosed from the start of my post.
As such, my intention was for someone else (ie: who actually knew about the subject) to opine so that a check against what this AI thing actually spewed could be made.
Actually thought it was a good idea. 8^°
Best,
A.
Hello:
Never used [wall] or [lightdm].
I am a [SLiM] enthusiast on a single-user WS.
That said and only to see if an [AI] answer can be (?) useful (I do not like it nor do I use it, this is just a test), out of curiosity I searched with Google and it came up with this without giving me an option to avoid it:
Terms used: [lightdm traps wall message]
Reply:
If your system hangs, delays, or traps a wall broadcast message when LightDM is active, it is typically because LightDM's greeter session listens to standard system log channels or terminal broadcasts, but lacks a standard terminal emulator to output the text cleanly.
Why the Trap Happens
Greeter Isolation:
LightDM's greeter runs under its own isolated unprivileged account (lightdm). If a system event (like a scheduled shutdown) fires a wall message, the system tries to inject it into all open pseudo-terminals (/dev/pts/*).TTY/STDOUT Redirection:
The lightdm user owns a sub-process session that grabs TTY streams. Because it lacks a proper graphical notification daemon to catch terminal broadcasts, the text stream can buffer natively or loop inside systemd's logs (journalctl -u lightdm)
There's more, but this may get you on your way.
I am not sure about getting it done while using [lightdm].
Best,
A.
Hello:
... download a suitable version from the repo, all files required, and install it with apt/apt-get or dpkg -i ...
Right.
... a look at the Devuan Package View ...
... two packages in the repo, both 7.4.7-1 plus a Debian patch.
... 7.4.7-1+deb12u13 and 7.4.7-1+deb12u14.
... so you should be able to get back to deb12u13
Thank you for taking the time to look that up.
Much obliged.
In the few hours I have been working with it, I have seen that [OpenOffice] starts up, open and saves the same spreadsheet noticeably faster, does not have any (obvious) UI bugs and is working as well as expected.
Just a couple of things to get used to because "muscle memory" (eg: [BackSpace] to delete content from a cell instead of [Delete] which generates a pop-up with options) but nothing important enough to consider going back to [LibreOffice].
On top of that, I do think it has more 'nice-looking' appeal. 8^P
Best,
A.
Hello:
... that version from LO directly and install it ...
Yes, I was asking about using the version from the repository and not the one from LO.
I am usually reluctant to install from outside the repository, but I have done it a few times without issues.
That said, it is my impression (YMMV) that the devs at LO are not on the right path.
The "nice-looking graphics over speed" bit from the [readme] file sealed the deal for [OpenOffice], at least for the foreseable future on my Daedalus system.
I don't need "nice looking" software, I need "reliable and properly working" software.
Who knows what other compromises these chaps are willing to accept to achieve their goal.
What's next?
"By default, LibreOffice favours nice-looking graphics over accurate, repeatable calculations with reproducible results"?
Once again, thanks for your input.
Best,
A.
Hello:
...now we know what the priorities are for the [LibreOffice] development team.
I am hard pressed to get some documents/spreadsheets finished by Monday so decided cut my losses and purge all of [LibreOffice] from my system and install [OpenOffice].
Installation was a breeze, seems to work properly out of the box, did not bitch about anything and opened my spreadsheets without failing in any, both [*.xls] and [*.ods]. I expect that it will be the same with [*.doc] and [*.odt], have not tried yet.
And most gratifying: the problem with [LibreOffice] is not present in [OpenOffice]. 8^D
So, unless something tragic happens, it will be [OpenOffice] from now on.
I really do not need the grief and waste of time this last issue brought me.
Much less if the cause was [LibreOffice] favouring "nice-looking graphics" over a properly working UI.
So I will mark this one as solved.
Thanks to all those who pitched in.
Best,
A.
Hello:
Will report back once the deed is done.
Much to my chagrin, the problem I reported in the OP remains.
And my search for a solution only found that it comes from as far as five/six years ago.
I managed to use [synaptic] to remove the installation without much problem.
Settings are still there as I did not purge.
Now, while I was looking into the different uncompressed directories still present in [/tmp], inside the main one I came across a file labelled [README_en-US] which (rather unsurprisingly) had this neat little tidbit:
----------------------------------------------------------------------
Graphic Performance
----------------------------------------------------------------------By default, LibreOffice favours nice-looking graphics over speed. If you experience slow graphics, switching off 'Tools - Options - LibreOffice - View - Use Anti-Aliasing' may help.
So, now we know what the priorities are for the [LibreOffice] development team. 8^°
TL;DR: slow and quirky but nice-looking.
No, switching off 'Tools - Options - LibreOffice - View - Use Anti-Aliasing' did not help.
Q: how can I tell [apt] to install one of the previous versions?
ie: one or two versions before the current one in the Daedalus repository.
Best,
A.
Hello:
... catch up to latest advancements. maybe not even needed ...
Indeed ...
The 'latest' advancements.
The scourge of IT by another name.
Unjustified "advancements", things no one asked for or needed.
Soon they will add video editing capabilities to it and it will be even more "advanced".
Enshitiffication and bloat just for the sake of it.
Or maybe for the sake of being as much as [MS-Office] as possible?
If I had to choose, the Linux equivalent of the stand alone [MS-Word 6.0] (over 26 years after it was EOL'd.) would still be more than enough for me. I should have a copy somewhere.
Best,
A.
Hello:
Thanks so much for the prompt reply.
... pinning isn't required.
... disable search for updates ...
Good.
That is how I work with unregistered [Master PDF Editor 5].
Have not had to resort to my XPSP3 VM / Adobe Pro 7.0 for the longest while.
7.6.7.2 is the latest version ...
... had it on Daedalus ...
... happy with what I have ...
Good to know.
... use Writer and Calc ...
... rest is installed but not used.
Same here.
When I need to send someone a document it is in in [*.pdf], [*.doc] or [*.txt].
If a spreadsheet (not often) it is in [*.xls] usually because of whoever receives it does not use [OpenOffice].
When [*.xls] and [*.doc] it is in [MS-Office 97] format.
It would be great if Open Office could be purged of unused stuff.
ie: only install what is needed.
... download three packages ...
... extract the contents to /tmp.
... in this case from 7.4 to 7.6, you need to remove the old stuff ...
Settings remain in place.
Seems easy enough.
Q: is language pack needed if I have my box running in english? ie: en_GB
Right.
Will try that and see how it goes.
Hopefully the problem I am having now (and did not have before) will not be present.
Will report back once the deed is done.
Thank you very much for your help.
Best,
A.
Hello:
When LO 7.4 came out ...
I cannot remember what the previous version was.
ie: 7.4.7.1?
... there were some voices that said it was not the best.
I have not been happy with OpenOffice for a good while now.
I managed because I could, but this problem is really very annoying.
Have lost a lot of time (in shrt supply at the moment) trying to find a fix.
... downloaded the latest 7.6 version and that works fine.
I could try but I could also roll back to the known.
Even the inteface has changed.
eg:
In the previous version I could see a progress bar when it autosaved or I saved a file I was working on.
For whatever reason, that is now gone.
Seems that visual indication of a file being saved is no longer important.
> ... not using the LO version from the repo.
I see.
I'd say my options would be:
1. find a way to safely roll back to the previous repository version (or the one before it) and pin it.
2. install a newer version from the LO repository and pin it, say 7.6.7.2?
Opinion?
Seems that enshittifacion is in full force all over the IT world, if it continues at this pace, we are doomed.
Thanks for your input.
Best,
A.
Hello:
... have preferred the "openoffice" ...
I have never liked the idea of an 'office suite'.
Would have preferred Linux have stand alone applications like eons ago when you could install MS Word and Excel separately and not have to deal with a behemoth.
That said, I have used LibreOffice since I moved to Linux and it has worked well most of the time, having OpenOffice and LibreOffice side by side seems a complication.
The main problem I see (in all) these 'suite' things is bloat, bloat and more bloat.
The issue I have probably has roots there.
Best,
A.
Hello:
Hmm ....
OK.
For the very first time in over nine years:
- bump>
I have not been able to find anything but complaints about this on the web.
Any ideas?
<bump -
If not, how to properly roll back to the previous version of LibreOffice.
Best,
A.
Hello:
... must not be connected properly.
Don't use this type of hardware but it should (?) behave as any other BT harware.
eg: BT mouse with a USB receiver plugged in.
There may be more information in /var/log/[fill-in]
ie: [dmesg] and then [kern.log], [syslog], [messages] and [lsusb].
1. Boot the box without the [thinguies/USB whatever] plugged in.
2. Plug them in and check what [dmesg] tells you.
3. That should give you some data wrt the hardware.
Check to see what [lsusb] says.
Maybe it is a driver/configuration/pairing issue.
Edit:
A fast check on-line found that the earbuds have to be paired manually.
The lack of [systemd] in Devuan is (most probably) the key.
Maybe that the Huawei management apps are not Linux-able?
Google for [HUAWEI FreeBuds SE 4 ANC linux] and [HUAWEI FreeBuds SE 4 ANC linux Devuan].
Best,
A.
Hello:
Since the last LO upgrade (to 7.4.7.2?) I find that my scrolling (via the up/down/left/right keys) has become a nuisance.
If I press the [up] or [down] key to move to another cell it does so but slow so that when I let off the key, the scrolling continues and ends up further than I needed, like if it filled a buffer.
Quite annoying, to put it mildly.
Does not seem to happen in LibreOffice Writer.
I have not been able to find anything but complaints about this on the web.
Any ideas?
Best,
A.
Hello:
... has the option to set the BOM marker ...
... more likely that a text file will be displayed correctly somewhere else.
I'll have to look that BOM thing up.
That said, my *.txt/*.conf/etc. files are (in all probability) not going anywhere.
Save maybe one of my other Linux systems. 8^)
I agree, [Featherpad] seems fine for what I usually do.
Worst case scenario, I'll always have [MCedit].
It also renders all the accented characters correctly.
Thanks for your input.
Best,
A.
Hello:
If it helps ...
*Everything* helps.
That is what the forum is about. 8^)
Mousepad has good support for different encodings ...
I installed [featherpad] from the Devuan repository and it seems to be working as needed.
I (think) I have everything correctly set to UTF-8 which will do.
I see it has more than what I need but it is lightweight and did not pull in anything strange.
Seems there are quite a few Qt libraries in my system.
... lacks many encodings ...
My needs are circumscribed to the accented vowels I posted previously+the ES [ñ/Ñ].
The rest of the characters provided by the KB are a bonus.
· ½ ¬ { [ ] } \
¬ ¡ ⅛ £ $ ⅜ ⅝ ⅞ ™ ± ° æ ß ð đ ŋ ħ ĸ ł ~
Æ ẞ Ð ª Ŋ Ħ Ł { } \ « » ¢ „ “ ” µ • · | © ‚ ‘ ’ º × ÷Just have to remember where they are.
So I don't have to cut/paste from the web when I need ©, ™, ± or fractions. 8^°
Thanks for your input.
Best,
A.
Hello:
There's mousepad ...
... featherpad if you don't mind pulling in ...
I'll have a look, thanks.
... use geany most of the time.
Too much for me.
It is a programmer's editor but I need *just* a text editor so as not to have to pull up LibreOffice Writer for such a simple task.
Interesting that there being *so* many Linux text editors, one would think that the hallowed 'choice' would have generated just *one* for simple everyday text edition for the common folk such as I.
Best,
A.
Hello:
Thanks for the prompt reply.
... this way, but I don't know if it has what you need.
No, it does not have the characters I need.
My kb has these characteristics:
$ cat /etc/default/keyboard
# KEYBOARD CONFIGURATION FILE
# Consult the keyboard(5) manual page.
# Set for IBM 82G3294 Model 'M'
#
XKBMODEL="pc105"
XKBLAYOUT="latam"
XKBVARIANT="deadtilde"
XKBOPTIONS="lv3:ralt_switch,terminate:ctrl_alt_bksp"
BACKSPACE="guess"With those settings I can type all the characters I need with locale=[en_GB.UTF+8] on my keyboard which has a Latin American Spanish QWERTY layout, using the [AltGr] key:
á é í ó ú - Á É Í Ó Ú
à è ì ò ù - À È Ì Ò Ù
â ê î ô û - Â Ê Î Ô Û
ä ë ï ö ü - Ä Ë Ï Ö Ü
There are a lot more which I do not use but are surely useful:
¬ ¡ ⅛ £ $ ⅜ ⅝ ⅞ ™ ± ˛
| @ · ~ ½ { [ ] } \ ¸ and others ...
The thing is that I can type the accented characters in and they will render properly but when I try to save the file, I get the popup with the complaint.
I am resorting to [l3afpad] because [X File Writer], part of [XFE], a really nice and compact desktop agnostic file manager, has some issue I cannot solve and typing the characters usong [AltGR] is not working.
It would seem that there is some sort of conflict (sez AI):
In Linux, FOX Toolkit applications may fail to process the AltGr key due to X11 modifier mapping issues, missing Mod5 configuration, or environment translation conflicts.
and
In Devuan running XFCE, the AltGr failure occurs because XFCE uses its own internal daemon (xfce4-keyboard-settings) to manage layouts. This frequently overrides standard X11 system properties and fails to pass the third-level modifier (Mod5) down to lightweight or legacy UI toolkits like FOX Toolkit.
As a result, every application works with [AltGR] with the exception of [XFW].
[L3afpad] does not seem to have had any updates in over 10 years.
Any ideas?
Best,
A.
Hello:
Anyone here use [l3afpad]?
https://pkginfo.devuan.org/cgi-bin/pack … .18.1.11-4
Accented characters get me this pop-up:
Can't convert codeset to 'ANSI_X3.4-1968'
There seems to be no options to fix this (?).
Best,
A.
Hello:
... need to install libreoffice-gnome ...
Seeing that I do not use [gnome-desktop], I don't think I can come up with a reason to need [libreoffice-gnome].
... and do not exclude Recommends to get libreoffice-gtk3 ...
Right.
Thanks for searching (and finding) the cause of this.
It would seem that someone at the [Libre Office] dependencies department is not paying attention to what they are doing.
Have a good week-end. 8^)
Best,
A.
Hello:
I type on LO Writer in languages requiring the use of special characters:
ie:
Ccute/grave accents, circumflex or diaeresis/umlauts on vowels - [á é í ó ú] [à è ì ò ù] [â ê î ô û] [ä ë ï ö ü] and so on.
For some reason, after one of the last LO upgrades, this [using the AltGr key] stopped working.
Much to my chagrin, the answer came through the Google 'AI' thing and not as a post by anyone using LO.
TL;DR:
Make sure that you have the [libreoffice-gtk3] package installed, if it is not, the [AltGr key] stops working.
rant
How come this did not come included with the bloody #$%& LO upgrade?
/rant
Best,
A.
Hello:
See: https://dev1galaxy.org/viewtopic.php?pid=24694#p24694 and the rest of the thread.
I seem to recall that nvidia-persistenced is a *suggested* package, not sure.
Best,
A.