You are not logged in.
Hello:
... bought a laptop ...
Nice ...
What brand?
What model?
... after installing Devuan ...
Good ...
Which release?
Beowulf?
Chimaera?
... does not recognize the Mediatek MT7961 wifi network card.
Right ...
For anyone here to be able to help you, it is absolutely necessary that you provide your hardware/software information.
If it were at all possible to do it just with what you have posted, we'd all be making loads of money as advisors on the LSE/NYSE. 8^D
ie: you have to do your homework before posting to ask for help.
Please open a terminal and do:
~$ uname -a~$ lspci | grep -i wireless~$ sudo dmesg | grep -i driverPost the output.
That would be a good start for someone to be able to help you.
That said, the Mediatek MT7961 card probably needs firmware-misc-non-free package or the MT7921 kernel module present from version 5.12 onwards.
See:
https://miloserdov.org/?p=6899
and
https://pkginfo.devuan.org/cgi-bin/poli … e&x=submit
Best,
A.
Hello:
And my request of respectful and purposeful dialogue does indeed apply to everyone.
+1
Thank you for that.
A.
Hello:
Does that help?
Hmm ...
Not really.
My question was:
Just what #$%&'¿ does Chromium want with a keyring PW?
Any idea as to what is going on?
You did not answer it.
Search engines are usually quicker than asking on forums ...
Maybe, depends.
I was not looking for quicker.
I asked here on Dev1 because I use Devuan Linux, the issue affects Devuan+Chromium and probably affects quite a few Devuan users.
The solution/explanation (if found) will eventually be posted here and will be available to Devuan users searching for it here.
All that does not come with quicker.
Now, if my doing so results in your getting your knickers in a twist, annoys you or in any way upsets your fragile peace of mind, please do consider disregarding my question: you are under no obligation whatsoever to answer it.
... you should probably learn how to use them.
Like I have said in another opportunity: I value your opinions, expertise and the help provided to me more than once.
That has not changed.
But it seems that you insist on acting up and in doing so do yourself a great disservice.
You are in no position to presume to be able to lecture me on learning anything, so please don't.
Best,
A.
Hello:
I run Devuan Beowulf on a backported kernel:
~$ uname -a
Linux devuan 5.10.0-0.deb10.16-amd64 #1 SMP Debian 5.10.127-2~bpo10+1 (2022-07-28) x86_64 GNU/Linux
~$ Due to issues sound when uisng jitsi with Palemoon, Firefox and LibreWolf I had no choice but to turn to Chromium, which I would not have installed otherwise.
A problem I have encountered is that when I load it, I get a pop-up asking for a PW, with this text and layout ...
Unlock Login Keyring
The login keyring did not get unlocked when you logged into your computer
Password: [ ]
... and until I actually cancel it, the rest of my desktop is totally unreponsive.
ie: the only thing I can do is move my mouse pointer and click Cancel or Unlock and to make it go away I have to repeatedly click Cancel as it pop up again three or four times.
This issue was brought up here at Dev1 up a couple of years ago with no solution found.
https://dev1galaxy.org/viewtopic.php?id=3429
It is really annoying, I am logged in as a user belonging to all the groups I need to belong to:
~$ groups
groucho adm lp mail dialout fax cdrom floppy tape sudo audio dip www-data backup video plugdev staff users crontab netdev lpadmin scanner saned fuse powerdev
~$ So ...
Just what #$%&'¿ does Chromium want with a keyring PW?
Any idea as to what is going on?
Thanks in advance.
A.
Hello:
Got this in my mailbox this afternoon.
----
This release fixes an invalid event type mask in XTestSwapFakeInput which was inadvertently changed from octal 0177 to hexadecimal 0x177 in the fix
for CVE-2022-46340.
It also includes backports for a couple of fixes in XQuartz and fixes for XKB (noticeably for CVE-2022-3550 and CVE-2022-3551).
Jeremy Huddleston Sequoia (1):
xquartz: Fix some formatting
John D Pell (1):
XQuartz: stub: Call LSOpenApplication instead of fork()/exec()
Olivier Fourdan (1):
xserver 21.1.6
Peter Hutterer (3):
xkb: proof GetCountedString against request length attacks
xkb: fix some possible memleaks in XkbGetKbdByName
Xext: fix invalid event type mask in XTestSwapFakeInput
---
https://xorg.freedesktop.org/archive/in … 1.6.tar.gz
SHA256: 6f9c73ccc50e2731adac17671c8e33687738c8cd556b49ecb9f410ce7217be11 xorg-server-21.1.6.tar.gz
PGP: https://xorg.freedesktop.org/archive/in … tar.gz.sig
https://xorg.freedesktop.org/archive/in … 1.6.tar.xz
SHA256: 1eb86ed674d042b6c8b1f9135e59395cbbca35ed551b122f73a7d8bb3bb22484 xorg-server-21.1.6.tar.xz
PGP: https://xorg.freedesktop.org/archive/in … tar.xz.sig
---
Best,
A.
Hello:
... a useful piece of software.
Not to contradict you or wanting to polemise any further, but I'd say that depends heavily on the what for aspect.
Some brillantly written worms and trojans will also fit into the "useful piece of software" slot.
But ...
... administrating a highly secure multi-user system ...
... you would have a very secure and properly segmented/firewalled network with strictly vetted users with assigned security clearances on a per case basis.
You do not need to have zeitgeist installed to have highly secure multi-user system.
But while I can understand your point of view, I don't agree with it and insist:
There's no need for zeitgeist to be in any Linux repository, much less Devuan's.
So let's agree to disagree. 8^)
Best,
A.
Hello:
... don't install it then.
I think you are missing the point.
By a mile or so.
... is not installed by default in any of the desktop environments ...
Yes, as of today.
As you can surely gather, that list can change and expand to a great many other packages within the Linux ecosystem.
Very quickly.
... seems to be a complete non-issue.
I beg to differ.
The point being that a package such as this one does not have a place or reason to be in any Linux repository.
Much less in Devuan's repositories.
Not only that, but there is code in the source to send user data to a remote server over unencrypted HTTP
https://gitlab.freedesktop.org/zeitgeist/zeitgeist/-/blob/main/datahub/telepathy-observer.vala#L33
In the same way that Wednesday night's sushi has no place or reason to be in your refrigerator because you expect no one will eat it.
Or will try to find the receipt from the delivery chap to see when it was purchased/delivered before taking a bite and getting scombroid poisoning.
... a list of the packages which will pull in zeitgeist ...
Thanks for the heads-up. 8^)
But until pungentweasel posted his warning and you posted this list, here at Dev1 no one knew all this was happening.
As well as most if not all Linux users who installed budgie, cairo-dock, diodon etc. and ignored this fact.
Unless they read your post or done the research to find out.
ie: find out that this crap was being pulled in when they installed their chosen xxyyzz application.
Which is something that a Linux user should not have to do when they install an application from a trusted source such as their distribution's repository.
Why?
Because (up to yesterday) no one in their right mind would have thought that a Linux repository would have this crap available for installation.
... tinfoil consumers can use this file ...
... will stop any zeitgeist packages from ever being installed.
Done.
Thanks. 8^)
Note to devs:
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Please consider banning zeitgeist from the Devuan repository.
Consequently, any application that requires zeitgeist to be installed to work properly should be sanitized just like any application that needs systemd to be present but can work without it.
And if it cannot be sanitized, it should also be banned.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Best,
A.
Hello:
They don't have time to sift though thousands of packages, so it's understandable.
Yes, I agree.
But it would seem that it skipped both Debian and Devuan devs.
And the devs of other distributions that have it.
... should be blacklisted ...
... personal user data to an insecure remote server.
... affect some other packages that depend on it though.
Then any other package that depends on it should also be banned from Devuan.
I cannot stress this enough:
----> This is not an issue to be taken lightly <----
It is an infection which has actually originated from inside the Linux ecosystem.
Unbelievable.
An infection that, in my opinion, has taken root thanks to the slow but constant erosion of the basic principles Linux was built on.
ie: Do one thing and do it well
Gnome tracker is much more difficult to deal with because of its integration with GTK.
Get the point I am attempting to make above?
Integration? Then off with it's ugly head, I say.
Integration is nothing but the negation of the Unix/Linux philosophy as put forth by Doug McIlroy et al.
Has the widespread implementation of systemd not raised enough flags yet?
... surprised that a system like this doesn't already exist as a standard practice across all of linux.
Indeed.
So am I.
Very (very) much so.
Best,
A.
Hello:
Thanks for the heads up.
Indeed ...
Thanks a lot. 8^)
... checked my Refracta Chimaera install ...
I don't have it in my Beowulf either.
But that's not the point.
The tracker service can be disabled and masked.
The point is that, independently of whether it can be disabled/masked, such a package has no place in the Debian/Devuan repositories.
Anyone know how it is that it got there?
And most important, how it eluded proper scrutiny from the devs?
I'd say it has to be banned.
A.
Hello:
Got this in my mailbox this morning.
---
This release fixes 6 recently reported security vulnerabilities in various extensions.
The CVE numbers are:
CVE-2022-46340, CVE-2022-46341, CVE-2022-46342, CVE-2022-46343,
CVE-2022-46344, and CVE-2022-4283
For details on the these issues please see the security advisory here:
https://lists.x.org/archives/xorg-annou … 03302.html
https://xorg.freedesktop.org/archive/in … 1.5.tar.gz
PGP: https://xorg.freedesktop.org/archive/in … tar.gz.sig
https://xorg.freedesktop.org/archive/in … 1.5.tar.xz
PGP: https://xorg.freedesktop.org/archive/in … tar.xz.sig
---
Best,
A.
Hello:
I wonder how the poster will fair ...
Right ...
It would seem that those of us who had something to say have already said it and in the best possible way.
Whether it made any sense or helped at all is up to the OP and how he processes it.
But beyond that, there's no need to keep picking on the chap.
I'd like to think that we are better than that.
Best,
A.
Hello:
... appears to have very few dependencies ...
... less likely to make a mess than trying to install the chimarea binary package ...
I marked this thread as solved as I was able to update lynis without much ado or issues.
It runs properly as far as I can see, at least for the time being.
The solution is here.
Basically it involves importing a key and adding the CISOfy software repository to /etc/apt/sources.list.
Will eventually look into chkrootkit to see it the same thing can be done.
It looks like rkhunter has probably been abandoned so I will remove it.
Best,
A.
Hello:
...lynis appears to have very few dependencies ...
... amenable to a simple local backport
Thanks for the heads up.
I'll check it out.
... some change that you need ...
I really don't know if I need it.
Because I don't know how much the threat scenario has evolved.
If it has evolved (high probability), goes to reason that newer version would address it.
... just "newer must be better"?
Me? 8^D
Been in this far too long for that.
... could just dist-upgrade to stable.
Yes, I could.
But first I have to make 100% sure my nvidia cards will work properly and I will still be able to use slim and wicd, among other old stuff I have installed and then comfortably get rid of the POS that Xfce is slowly turning into to get myself a set up like what Phillip Newborough's #! Waldorf* was.
* which I think should be the default template for both Devuan desktop-live and installer-iso versions.
... going to sooner or later ...
Yes, I know. 8^°
Thanks a lot for your input.
Best,
A.
Hello:
Every so often and maybe not as regularly as I should, I run chkrootkit, rkhunterand lynis.
Always come up clean, or so it seems.
This is what I have installed:
~$ apt-cache policy chkrootkit && apt-cache policy rkhunter && apt-cache policy lynis
chkrootkit:
Installed: 0.52-3+b10
Candidate: 0.52-3+b10
Version table:
*** 0.52-3+b10 500
500 http://deb.devuan.org/merged beowulf/main amd64 Packages
100 /var/lib/dpkg/status
rkhunter:
Installed: 1.4.6-5
Candidate: 1.4.6-5
Version table:
*** 1.4.6-5 500
500 http://deb.devuan.org/merged beowulf/main amd64 Packages
500 http://deb.devuan.org/merged beowulf/main i386 Packages
100 /var/lib/dpkg/status
lynis:
Installed: 2.6.2-1
Candidate: 2.6.2-1
Version table:
*** 2.6.2-1 500
500 http://deb.devuan.org/merged beowulf/main amd64 Packages
500 http://deb.devuan.org/merged beowulf/main i386 Packages
100 /var/lib/dpkg/status
~$ Now, when I check available versions on-line I find that lynis seems to be the one with most active development, the latest version being 3.0.8 from last June while chkrootkit latest is at version 0.55 from June last year.
See https://cisofy.com/downloads/lynis/ and http://www.chkrootkit.org/
By comparison, rkhunter version 1.4.6 does not seem to have had any work done since 1.4.6 (2018).
See https://rkhunter.sourceforge.net/
My Beowulf installation runs on a backported kernel:
~$ uname -a
Linux devuan 5.10.0-0.deb10.16-amd64 #1 SMP Debian 5.10.127-2~bpo10+1 (2022-07-28) x86_64 GNU/Linux
~$ But there are no Beowulf backports to any of these tools, not even for lynis but the Chimaera repository has version 3.0.2-1 available.
Would it work on my backported system?
If so, how can I install it without making a mess?
Thanks in advance.
Best,
A.
Hello:
... With all due respect.
... mole on my lawn would be ...
I have followed this thread on and off, more than anything out of curiosity and to see just how far it would go.
There's not much to add to the more than suitable/correct answers you have received, save this:
I take personal exception to the tone in your posts, which I consider both unwarranted and absolutely out of place.
I would appreciate your showing more respect to those who volunteer their time and efforts to keep both Devuan and this site working.
I'm sure my words represent the opinion of an overwhelming majority here at Dev1, so please do take them into account.
And stop behaving like a five year old.
Best,
A.
Hello:
... Chimaera ...
Right.
... kernel version is not really relevant here, is it? ...
No.
But I like to see what the output says, just habit.
deb http://deb.devuan.org/merged chimaera main contrib non-free deb http://deb.devuan.org/merged chimaera-updates main contrib non-free deb http://deb.devuan.org/devuan chimaera-proposed-updates main contrib non-free deb http://deb.devuan.org/merged chimaera-security main contrib non-free deb http://deb.devuan.org/merged chimaera-backports main contrib non-free
Seems correct.
I would not use devuan chimaera-proposed-updates, because proposed.
Obviously, YMMV.
I think the explanation could be here.
Devuan has a network of package repository mirrors in place. The mirror network is accessible using the FQDN "deb.devuan.org" via http NOT https. Country Codes (CC) are currently unavailable but a specific mirror from the list can be accessed using the corresponding BaseURL.
The list is here.
There is/maybe some issue with FQDN "deb.devuan.org" and how/when it connects to debian.bio.lmu.de.
You could be able to solve the problem by following the suggestion above.
ie: ... a specific mirror from the list can be accessed ...
Best,
A.
Hello:
... boot in console mode then "startx".
... no "X" involved yet.
The first thing I'd do would be to check the logs.
/var/log/Xorg.0.log in particular.
I use a pair of older nvidia cards (Quadro FX580) with three monitors and legacy 340.108 drivers from nvidia.
Although it is supposed to be able to work without it, I have never been able to do it without a properly configured xorg.conf.
To the extent of using the same xorg.conf for the last seven years or so and over three different distributions.
With Devuan since 2017.
Best,
A.
Hello:
... remind my colleagues of the ancient optimization algorithm ...
... assembly of the kernel for specific conditions ...
+1
With all the crap permanently being crammed into the kernel (much of it without comment), compiling the kernel will eventually become a must do for many.
ie: you end up finding out about them long after the fact when you have look at dmesg or system logs, something I do often.
That's what they are there for.
... an example ...
... modules in the kernel waiting for apparmor and tomoyo.
... have neither one nor the other, why load them ...
Well ...
Probably because there are quite a bit of aspiring Poetterings amidst the Debian devs/maintainers.
Fortunately there are ways to avoid loading them, for the time being.
... already played enough in the compilation ...
I never got around to doing that.
Too much time and energy needed.
A.
Hello:
Thanks ...
You're welcome.
Sorry, doesn't take long ...
No need.
Absolutely no one is born knowing. 8^)
The code and /code bits have to be put between brackets ie: [ ], like all the other ones you see at the top following "Post a reply - ".
Find your post with the terminal output, click on Edit and add the flags.
You can also select multiple lines (ie: paint) and click on the flag you want to use and all that you painted will start and end with the proper flag.
Best,
A.
Hello:
THanks ...
You're welcome.
output here ...
Right.
But first I'll ask you to edit your previous post so that the terminal output is seen as code.
That way it is easier to see and check separately from the text.
To do that, you have to add the code and /code tags to the start and end (respectively) of the output you copied/pasted on the screen.
Do a preview and check if it is seen like this:
Linux devuan 4.19.0-22-amd64 #1 SMP Debian 4.19.260-1 (2022-09-29) x86_64 GNU/LinuxBest,
A.
Hello:
Linux newbie ...
Right.
Most important when asking for assistance is to provide as much information as possible.
Devuan is mostly what people ask about here.
But it could be Devuan Chimaera 4.0 (stable) or Devuan Beowulf 3.0 (oldstable) or maybe an older version.
It would be a start in the right direction but not enough.
No one here can see your deskop (eventually but not just yet) so they will need to know a bit more than that ... 8^°
So, for starters, please post the terminal printout result of this:
~$ uname -aAnd these:
~$ apt list | grep installed | grep desk~$ sudo dmesg | grep -i "error\|warning\|fail\|segfault\|fatal\|not"All the information you post will enable those who can help you to actually be able to do it.
Best,
A.
Edit: grammar, syntax, etc.
Hello:
Is it really needed to have boot command security=none ?
... was not aware of this extra step.
You would be if you had taken the time to read the whole thread. 8^D
Check if you have some other stuff called tomoyo, another gift from the Debian devs.
You have to add security=none to the kernel command line to avoid that one.
Best,
A.
Hello:
so, solution here is remove apparmor?
What is wrong with apparmor?
Please take a few minutes and read the thread and the content of the links posted.
As I see it, both questions have already been answered.
As always, YMMV.
Best,
A.
Hello:
What about
apt remove apparmor
Yes.
But then you upgrade the kernel and there it is again.
At least that's what happens to me (Beowulf with backported kernel) when I upgrade the kernel.
Even though my kernel command line clearly says apparmor=0 (!)
What I always do is purge apparmor after the upgrade and before rebooting and make sure the kernel comand line has not been edited.
[root@devuan ~]# apt purge apparmor
If it is now a module, one sure way is to blacklist it.
Check if you have some other stuff called tomoyo, another gift from the Debian devs.
You have to add security=none to the kernel command line to avoid that one.
See these two three posts:
https://dev1galaxy.org/viewtopic.php?id=2630
https://dev1galaxy.org/viewtopic.php?id=4329
https://dev1galaxy.org/viewtopic.php?id=4750
Best,
A.