-
AuthorSearch Results
-
June 28, 2019 at 12:11 pm #23978
In reply to: oFono plugin for connman?
MemberHJ
Ok, but without cmcc not sure how to add the APN. It isnt going to tether without correct APN for my cell network. But looks like have more searching and reading to do. By way I did open connman and it apparently saw the phone as it let me click to try tethering. But without an APN, it cant tether. And of course no silly experiment without a suitable punishment. I can now no longer use AntiX cause whatever happened, it hosed the ability to involve the DNS server for gnome-ppp. Oh I can ping numerical address, but cant resolve names. During gnome-ppp connection it finds the cell network DNS servers (they lock out any but their own), just cant use them. I can see what gnome-ppp does cause I have to start it from root terminal. Shows in terminal what its doing.
June 26, 2019 at 11:32 am #23901In reply to: Is Screenlight working in AntiX 19, 32bit?
MemberHJ
Xecure is certainly thorough and has very succinct way of putting the facts. Meaning he went lot more in depth and says it lot more clearly than I do. So apparently this all depends on the hardware. My hardware just definitely isnt supported by Backlight Brightness (no controller found) and seems not to be by Screenlight. At least that script works for me. Though still experimenting with it, doesnt seem to hold the settings on reboot.
June 25, 2019 at 3:09 pm #23869In reply to: Is Screenlight working in AntiX 19, 32bit?
Forum AdminSamK
Are you using 32bit version?
Yes, 32bit and 64bit.
I might ask when does changing configuration file manually make it invalid?
You have misinterpreted. Post #23845.
The results you obtained are invalid.
It is the results you posted that are invalid not the file.
The way you did it did not allow the immediate change of the screen to occur. Because Screenlight was prevented from working correctly the results obtained are invalid.
Backlight Brightness is still in menu but you click on it and get error that “controller not found”.
That cannot be reproduced here. Backlight Brightness launches via the menu OK and works correctly. It is an indication that at least part of the problem may be local to your system.
…slowly adjusting it one way or other on the fly.
When you see it working correctly it will become apparent this is also the way for Screenlight.
But honestly no reason for me to lie to you about it.
No one has suggested this other than you.
June 24, 2019 at 5:41 pm #23790In reply to: Trying to use i3wm
Anonymous
A couple package names may have changed since the date of dolphin_oracles video(s)… but the videos certainly mention (and show) several xserver related packages which are absent from the list you posted. I don’t know which packages comprise the complete set of “bare minimum required for xserver//xsession”. I grabbed at suggesting “dbus-x11” was missing, but apparently other requisite packages are still absent.
June 24, 2019 at 1:11 pm #23782In reply to: The "Tiny Panel Bar" Thread
Anonymous
xlunch
Yah, as featured in the latest Slax release
~~ that sprung to mind when I read the comments which sprung up in the “splasht tests need” topic.Its datastore is “static”, so
not really usefulnon-ideal unless you would craft an apt-get post-install hook, toward automating the chore of adding/removing eyecons (ay-yai-yaicons?) to its datastore. Tomas has posted a suitable updater script to github, but AFAICT he hasn’t created a package for xlunch. (In other words, he apparently adds xlunch + updater manually while assembling the distro.)ay-yai-yaicons?
The unappealing attribute of xlunch, IMO, is that it’s even MORE dumbed-down than the typical {menu,launcher,finder} widgets we see across various linux desktop environments. It provides no “hint” (aka Comment= line, from the associated .desktop file) ~~ so, if someone acting as a distro curator intends to utilize xlunch, you’re shouldered with deciding whether/where/how to assure the .desktop files are populated with “meaningful” Name= namestrings. Otherwise your users are at the mercy of, subject to the discretion of, upstream’s labelnames. Also, based on my experience while supporting pre-adolescent users and seniors… confusion reigns if/when the system “theming” changes, whisking away and replacing the grown-familiar set of ay-yai-yaicons.So, in a nutshell, I do not recommend use of xlunch.
word-wrap
ped label
names are
quite a u
sability i
mpedimentJune 23, 2019 at 5:23 pm #23740In reply to: Interesting distribution
MemberHJ
Thanks for the gui, works great. By way I downloaded deb from here: http://mxrepo.com/MX15packages.html and installed with package manager. It installs and even creates a desktop icon (clock) though not on desktop, had to move the icon there.
I know nothing of mxlinux, but apparently closely related to AntiX. And it mentioned Mepis. I remember Mepis. Long time ago.
June 20, 2019 at 9:27 pm #23565In reply to: removing drivers to trim memory usage
ModeratorBobC
I hate to say this, but something I tried fixed it, but I don’t know which, because nothing was apparent at the time, and when I rebooted, the time in setup was off by 5 hours, so I fixed that, and now its correct in antiX, and apt-get update works, so I’m now able to add or remove packages again.
LOL, I haven’t rebooted into Windoze, yet….
June 20, 2019 at 2:04 pm #23532In reply to: antiX-19-b1-full and tsplash tests needed.
Forum AdminSamK
Off Topic
NoClue, you’re very opinionated. But that does not make you right.
I’m not ‘very opinionated’ — I’m 100.001 % right (as mostly — experience shows but yes, you can’t know that and so, you’re excused).
If I state something here, be it on a matter of design or like here, on a matter of energy efficiency — it’s based on solid and proven arguments — it’s NOT just ‘my opinion’.
@noClue
Opinionated does not refer to whether or not you are expressing your opinion. It refers to the manner in which you make your posts. It means Characterized by conceited assertiveness and dogmatism.
‘an arrogant and opinionated man’Ref: Opinionated
https://www.lexico.com/en/definition/opinionatedYour reply to seaken64 could not prove his point more clearly.
You have been advised on more than one occasion to avoid making immoderate posts. Your behaviour is disrupting the forum and inconsiderate of other forum users. If you are unwilling to moderate your postings you should carefully consider whether the antiX forum is a suitable place for you.
Have you stopped moderating here in antiX forum?!
No we have not.
We are a very small team. There are a few moderators who visit as time permits and some devs who try to mod and dev when they can. The more time we devs spend on matters like this the less we are able to spend on developing antiX.
The approach to forum moderation has been one of laissez faire. It works well when members are respectful and express themselves moderately. The antiX forum used to be the most welcoming and considerate forum available. In my opinion it has become less so over the last five or six years. Members have become less tolerant, quicker to express anger, and make flippant remarks rather than engage in meaningful discussions.
Attributing those changes to new members alone would be a mistake. It is regrettable that some long-term members reply to posts in a manner that raises the temperature by goading the poster. Keeping posts neutral in tone, and avoiding derision disguised as humour will help return the forum to being the most hospitable one available.
The forum is a much better and more productive place when everyone is less immoderate, adopts self discipline, and respects the differing capabilities of other members.
- This reply was modified 3 years, 10 months ago by SamK.
June 20, 2019 at 12:10 am #23459In reply to: antiX-19-b1-full and tsplash tests needed.
Anonymous
@seaken64
I’m not ‘very opinionated’ — I’m 100.001 % right (as mostly — experience shows but yes, you can’t know that and so, you’re excused).
About old computers, (lack of) 30$ and energy efficiency …
Many years ago, I had a gaming PC that was consuming some 450 W during gaming.
Modern DESKTOP PC with ONBOARD graphics an 45 W that replaced it, is much better performer (for those ultra-old games an overkill on performance) — much speedier and efficient too.
All the electrical energy that a computer uses eventually ends up as heat, and most of it heats up the room in which it’s running (which, during summer months, is increasing air-conditioning costs too!). Also, older PCs are typically less energy-efficient than modern ones. That energy efficiency is not only depending on HW but, it also depends on SW!
“A typical desktop computer complete with fan, mainstream CPU and a graphics card can easily use 150 watts of power even when it is idle. For most home server applications where the machine isn’t allowed to go to sleep you can multiply that by about 9,000 hours in a year. That means the apparently innocent machine stuck in the corner is consuming well over 1,000 Kilowatt hours per year. Depending on the situation that may be over 10% of your total electric use. If the machine is tricked out with high-end graphics cards it may be even more. Depending on your rates that can mean as much as $200 per year in extra electricity costs.”
https://www.extremetech.com/computing/97763-is-your-old-computer-costing-you-more-than-you-think
Just try to compare a ‘cheapo’ from the supermarket, some Pentium Gold (Atom Successor), 6W TDP with its 2~4 cores and 4GB RAM with some ancient 166 MHz, 256 MB RAM and 95W monstrosity.
You gain nothing by using it. It’ll be slow, it’ll be inefficient … and NOT using it would buy you a new ‘cheapo’ very soon.
That ‘supermarket toy’ will blow away your ‘junkputer’ in just about any use case scenario.
Quick-Tipps on saving energy:
“The resulting savings range from $10-100 per computer annually.”
https://www.stateelectronicschallenge.net/pdf/sec_computer_power_management_guide.pdf
June 16, 2019 at 5:48 pm #23151In reply to: Trinity Desktop Environment
Member
mattkingusa
Well, over the last 4 weeks I have purchased a stick of 512 that did not work and then a 256mb x 2 kit from the same ebay seller but that kit did not work either. So at the moment I am stuck with 128. I have a PIII 700Mhz but my gpu can’t even do opengl. I installed quake II from the CD and installed Half Life but they both fail because the gpu can’t do opengl. Unless I am incorrect and just don’t have the proper drivers installed. It has an 8MB AGP Rage Mobility gpu. Anyway, I have found a stick of 256MB on newegg for like $13 USD. But I am waiting to hear back from the ebay seller to see if I can return the other ram first. The ram that’s in there is 64MB x 2 at the moment. But the system won’t boot with any other ram, and if I put the wrong stick in the wrong side it won’t boot either. Apparently it has to have ram stick a in slot a and ram stick b in slot b. Not sure.
June 14, 2019 at 1:18 pm #22993In reply to: antiX-19-b1-full (64 and 32 bit) available
Forum Admin
BitJam
With boot options, I still haven’t tested what “wicd” and “nowicd” options do.
They do nothing. We should have removed them. Were you booting via UEFI so the selection was in a text menu?
Will they now enable/disable Connman instead of WICD (no longer installed) so that ceni works properly, or are they to be changed for “connman” and “noconnman” in the future?
You can disable the connman service with the “disable=c” option (add “c” to the list of letters after “disable=”).
WIfi not working with Connman in first start
I had difficulty running connmanctl from the command line. I needed to make a little cheat sheet of the commands I need to run after I started connmanctl:
agent on enable wifi services connect wifi_<tab>Perhaps there are similar hoops you need to jump through in the GUI version so you don’t need to reboot. I’d love to add this small cheat sheet somewhere but I’m not sure where the best place is. I’m lost without it.[/quote]
Tsplash experience
No fails from tsplash for now. On laptop perfect. I really like it very much.
First time booting with the liveUSB on my tablet (which is slow but with an enormous screen resolution), in the step after loading to RAM, I think it displays “Start Init”, the screen went totally black. I waited for about 20 seconds and decided to see what was going on.
I hit ALT+F1 (as the tsplash screen recommended before it went black to see more info). The terminal was there (so all well) and the last command displayed said “waiting for /dev to fully populate”. I returned to the black screen with ALT+F10 and after a few seconds, the tsplash screen returned (I believe that with a change of resolution). So everything was good.Alas, this is one weakness of the tsplash system. I can explain why it does this but I don’t have a quick or easy way to fix it. The root of the problem is that we try to keep the live system “lean and mean”. To that end we put as little extra stuff in the live initrd as possible because almost all of this already exists in the linuxfs file. IIRC the Debian initrd is 26M (or maybe larger) while our live initrd is only 4.3M. A major reason for this is we don’t include: udev, video drivers, video driver firmware, internet drivers, or internet driver firmware.
We rely on the udev service to load video (and other drivers) when it runs. By now most video drivers now are KMS (kernel mode setting or ‘modesetting”). This means the graphics driver also handles the virtual consoles. When these drivers load the console screen jumps around, can often get garbled, and the resolution often changes. This looks like s**t and was one of our main motivations to write tsplash.
We added a little code to the udev init.d script so when it starts, we first blank the screen. Then when it is done we unblank (redraw) the screen and say “udev done” or something like that. This does a great job at hiding all the jumping about and garble, but, as you know, the udev script can sometimes hang while waiting for /dev/ to populate so we end up with apparently hanging and a blank screen.
One way I tried to get around this (a bit) was to create a udev rule to redraw the tsplash screen when a new framebuffer is used. This would at least minimize the time the screen is blank and, if we are lucky, could give you a splash screen while we are waiting for udev if a KMS video driver gets loaded before udev hangs.
There were several problems with the udev rule so I finally dropped it but with some more work I might be able to add it back. Currently the tsplash screen is on tty10. In order to run a program to draw on tty10, I need to call it with the “openvt” command although I might be able to do the same thing with some IO redirection. But, for some reason, I’m not allowed to call openvt from a udev rule. Another problem is that the framebuffer gets set at least twice in rapid succession when the video driver loads (I don’t know why) so the usual case has three calls to redraw the screen in rapid succession, two from the udev rule and then the third from the end of the udev script (in case no KMS driver was loaded so our udev rule was never triggered).
So, for now, we are stuck with displaying a blank screen when udev hangs. I *might* be able to handle this better in the future but it might take some work and it might not make a difference. So for now, this falls into the “known bug” category.
Fantastic work, guys!
Thanks!
Context is worth 80 IQ points -- Alan Kay
June 12, 2019 at 12:53 am #22793In reply to: Synaptic question
Anonymous
Apparently, something more needs to be done?
There’s nothing we end-users can do.
The fault lies with the code (and underlying decisions/rationale) within the “apt” package.
The fault affects multiple code paths within multiple progs (incl. aptitude and synaptic) which utilize libapt.
The earlier “fixit” you are remembering, that fixed only one scenario & we users of “stable” repository were resigned to doing that b/c the fixed, updated, version(s) at the time were not deemed “security-related” so were not sent to debian-backports.apt drops privileges for SOME of its subprocesses (RunAs user: _apt)
and
apt creates, and will recreate if missing,
the /var/cache/apt/archives/partial/ _and_ /var/lib/apt/lists/partial/ directories
and, confoundingly
(yet the apt package maintainers INSIST it correct and desirable to do so)
sets permissions @700 (aka “drwx——“) for those directories.Counfounding or asinine? It’s your call…
Although the parent directories are set world-readable,
the devs insist that the subdirectory named “partial” (shall not be owned by root and) shall not be world-readable.========================
In the words of one of the maintainers (scraped from a bug ticket):
“It’s just a warning that [it] will not drop the privileges, to avoid failing with the operation.”3 yrs ago, another DD (debian developer) named Raphael Hertzog
suggested the following, hopefully clearer, verbiage:
” W: ‘%s’ can’t be created by user ‘_apt’, continuing the download as root instead. ”Most of the code commits (my notes contain commit+bugticket URLs across 4yrs)
have been made by David Kalnischkies, and about 2yrs ago he started “getting pissy” in his responses (and commit messages).
Below, I’m quoting a msg which accompanied a commit which simply changed the verbiage (NOT the behavior)
from
Can’t drop privileges for downloading as file ‘%s’ couldn’t be accessed by user ‘%s’.
to
Download is performed unsandboxed as root as file ‘%s’ couldn’t be accessed by user ‘%s’.Note: This is a warning about disabling a security feature. It is supposed to be scary as we are disabling a security feature and we
can’t just be silent about it! Downloads really shouldn’t happen any longer as root to decrease the attack surface – but if a warning
causes that much uproar, consider what an error would do…The old WARNING message:
| W: Can’t drop privileges for downloading as file ‘foobar’ couldn’t be
| accessed by user ‘_apt’. – pkgAcquire::Run (13: Permission denied)
is frequently (incorrectly) considered to be an error message indicating that the download didn’t happen which isn’t the case, it was performed,
but without all the security features enabled we could have used if run from some other place…The word “unsandboxed” is chosen as the term ‘sandbox(ed)’ is a common encounter in feature lists/changelogs and more people are hopefully able
to make the connection to ‘security’ than it is the case for ‘privilege dropping’ which is more correct, but far less known.Closes: #813786
LP: #1522675When a given call to an apt:: procedure returns an error, like this
apt-pkg/acquire.cc#L97
synaptic is just dutifully presenting a dialog window to display whatever msg string.
We could fork synaptic and mod the code so that it suppresses the dialog in the where this exact message string is received, but… (lather, rinse, repeat)June 10, 2019 at 8:23 am #22747In reply to: Synaptic question
Member
wildstar84
I remember creating the “_apt” user a while back in a previous attempt to fix this error, as someone else had said this was the problem. Anyway, it wasn’t and isn’t. Apparently, something more needs to be done? Here’s what I have so far:
Attachments:
June 2, 2019 at 7:45 pm #22457In reply to: Conky and old laptop
Memberwoodlark
My bad! I completely ignored the fact that an external monitor (with very different resolution) was plugged into the laptop. Apparently this messed up conky, although everything else seemed to be working. Unplugging the external monitor and rebooting solved the problem.
BTW: How do I edit the title of the thread to add [SOLVED]?
May 29, 2019 at 12:26 pm #22278In reply to: Workspace Buttons
Memberwoodlark
noClue: You are on to something! It is theme related. I went through all of the other themes and the buttons were all the same size. Interestingly, when I went back to my original theme, the problem was gone. Apparently reinitializing the the theme cured it.
Thanks to you and BobC for your help.
-
AuthorSearch Results
