stable/current bug reports

Pithium · 04-03-2022, 01:31 AM

Quote:

Originally Posted by PartiZan

I can do that locally, not a big deal.

Trying to suggest things to improve is something toxic now... Well, what I can say is go to my black list for your stupidity.

That's too bad. I tried to give you the benefit of the doubt here, but apparently you are determined to start fights and keep doubling down on your mistake. Oh well...

chrisretusn · 04-03-2022, 01:32 AM

Quote:

Originally Posted by Pithium

And FWIW, I've been poking at the way slackpkg info <pkg> displays info on my screen and there is definitely room for improvement. It's not broken, but when viewing info for a package that exists in multiple repos (I'm using slackpkg+) things get pretty messy. There's definitely room for discussion on improving that output because right now it hurts my brain..

Code:

root@vapyr:~# slackpkg info mesa-compat32


NOTICE: pkglist is older than 24h; you are encouraged to re-run 'slackpkg update'

PACKAGE NAME:  mesa-compat32-21.3.5-x86_64-2compat32.txz
PACKAGE LOCATION:  ./x-compat32
PACKAGE SIZE (compressed):  20005 K
PACKAGE SIZE (uncompressed):  200780 K
PACKAGE DESCRIPTION:
mesa-compat32: mesa-compat32 (a 3-D graphics library)
mesa-compat32:
mesa-compat32: Mesa is a 3-D graphics library with an API very similar to that of
mesa-compat32: another well-known 3-D graphics library. The Mesa libraries are used
mesa-compat32: by X to provide both software and hardware accelerated graphics.
mesa-compat32:
mesa-compat32: Mesa was written by Brian Paul.
mesa-compat32:
mesa-compat32: Homepage: https://www.mesa3d.org
mesa-compat32:
mesa-compat32: This package contains 32-bit compatibility binaries.

PACKAGE NAME:  mesa-compat32-21.3.5-x86_64-2compat32.txz
PACKAGE LOCATION:  ./slackware64-compat32/x-compat32
PACKAGE SIZE (compressed):  41988 K
PACKAGE SIZE (uncompressed):  200780 K
PACKAGE DESCRIPTION:
mesa-compat32: mesa-compat32 (a 3-D graphics library)
mesa-compat32:
mesa-compat32: Mesa is a 3-D graphics library with an API very similar to that of
mesa-compat32: another well-known 3-D graphics library. The Mesa libraries are used
mesa-compat32: by X to provide both software and hardware accelerated graphics.
mesa-compat32:
mesa-compat32: Mesa was written by Brian Paul.
mesa-compat32:
mesa-compat32: Homepage: https://www.mesa3d.org
mesa-compat32:
mesa-compat32: This package contains 32-bit compatibility binaries.


Package:    mesa-compat32-21.3.5-x86_64-2compat32
Repository: compat32
Path:       ./x-compat32/mesa-compat32-21.3.5-x86_64-2compat32.txz
Url:        http://192.168.0.13/mirror/slackware/multilib/15.0/x-compat32/mesa-compat32-21.3.5-x86_64-2compat32.txz

Package:    mesa-compat32-21.3.5-x86_64-2compat32
Repository: multilib
Path:       ./slackware64-compat32/x-compat32/mesa-compat32-21.3.5-x86_64-2compat32.txz
Url:        https://taper.alienbase.nl/people/alien/multilib/15.0/slackware64-compat32/x-compat32/mesa-compat32-21.3.5-x86_64-2compat32.txz

My brain has better things to do than parse large blocks of machine readable text. I have a computer to handle those mundane tasks.

There is something wrong with your setup or how you installed. I use slackpkg with slackpkg+, this is what I get.

Code:

~# slackpkg info mesa-compat32

PACKAGE NAME:  mesa-compat32-21.3.8-x86_64-1compat32.txz
PACKAGE LOCATION:  ./slackware64-compat32/x-compat32
PACKAGE SIZE (compressed):  42008 K
PACKAGE SIZE (uncompressed):  200850 K
PACKAGE DESCRIPTION:
mesa-compat32: mesa-compat32 (a 3-D graphics library)
mesa-compat32:
mesa-compat32: Mesa is a 3-D graphics library with an API very similar to that of
mesa-compat32: another well-known 3-D graphics library. The Mesa libraries are used
mesa-compat32: by X to provide both software and hardware accelerated graphics.
mesa-compat32:
mesa-compat32: Mesa was written by Brian Paul.
mesa-compat32:
mesa-compat32: Homepage: https://www.mesa3d.org
mesa-compat32:
mesa-compat32: This package contains 32-bit compatibility binaries.


Package:    mesa-compat32-21.3.8-x86_64-1compat32
Repository: multilib
Path:       ./slackware64-compat32/x-compat32/mesa-compat32-21.3.8-x86_64-1compat32.txz
Url:        file://home/non-slack/multilib/current/slackware64-compat32/x-compat32/mesa-compat32-21.3.8-x86_64-1compat32.txz

Pithium · 04-03-2022, 01:43 AM

@chrisretusn I have alienbob's repo added as "multilib" , and then a local "compat32" repo with higher priority. I run massconvert32 to make my own packages and store them on my own NAS. I set this up back when alienbob's server was struggling and I was getting insane download times.

slackpkg seems to put every package in the same PACKAGES.TXT file and slackpkg info just prints every instance of that package. So in my case, compat32 packages end up have 2 instances with one of them being masked.

I can see how this might be jarring since it deviates from how 'slackpkg search' displays similar info. Not at all a bug, and certainly not the result of negligence** by whoever wrote that particular feature. It's just ugly

** OP needs to check the dictionary definition of negligent. It's such a rude word to use in any open source context and he really doesn't seem to get it.

chrisretusn · 04-03-2022, 01:59 AM

Quote:

Originally Posted by Pithium

@chrisretusn I have alienbob's repo added as "multilib" , and then a local "compat32" repo with higher priority. I run massconvert32 to make my own packages and store them on my own NAS. I set this up back when alienbob's server was struggling and I was getting insane download times.

ah okay, I sort of suspected something like this. Your output is simply reporting what you have. Makes perfect sense.

My use case. I use a sync (manual run using a batch file "update.multilib.sh") of alienbob's multilib locally.

bassmadrigal · 04-03-2022, 12:44 PM

Quote:

Originally Posted by Pithium

Relax with the declarations of intent. You aren't a slackpkg dev and your name isn't credited at the top of the script

If you read through the code, there is no way to think they didn't purposefully strip anything off everything but the package name.

Quote:

Originally Posted by PartiZan

This was not intentional for sure; It was written and forgotten. It's not by design, but by negligence.

How can you read the code and not say it was intentional? They even pass it through the cutpkg awk script, which only has one function, to remove everything from the variable except for the package name. The developer(s) specifically chose to remove everything but the package name when searching PACKAGES.TXT.

Now, if you have a better solution, they might be willing to change how slackpkg info functions, but the way it currently functions was written purposefully to remove everything but the package name and use that for parsing the PACKAGES.TXT.

Quote:

Originally Posted by PartiZan

Trying to suggest things to improve is something toxic now... Well, what I can say is go to my black list for your stupidity.

You're not suggesting something to improve, you're saying something is broken.

Those are two wildly different things. One is considered an enhancement and the other is considered a bug. You've definitely been considering this a bug when it is obvious it isn't. If you had decided to push for an improvement, that might've been received differently.

xunilq · 04-11-2022, 09:43 PM

Quote:

Originally Posted by xunilq

Report of wireshark behavior over Kernel 5.17.0

Wireshark doesn't show packets over Monitor Mode on wlan0

/var/log/syslog no messages related

/var/log/messages:

Code:

kernel: device wlan0 left promiscuous mode

Kernel 5.15.27, works fine on monitor mode, difference on log:

Code:

kernel: device wlan0 entered promiscuous mode
kernel: device wlan0 left promiscuous mode

My Wlan device:

Code:

AR9565 Wireless Network Adapter (rev 01)

-----------------------------

PS for possible googlers, the monitor checkbox on wireshark doesn't work. i have set monitor mode like this:

Code:

ip link set wlan0 down
iw dev wlan0 set type monitor
ip link set wlan0 up

Fixed with 5.17.2

steve4lqdo · 04-14-2022, 10:20 AM

Regarding suspend/resume issues on AMD based Lenovo ThinkPad T495, the issue seems to be resolved with the combination of kernel-generic-5.17.3-x86_64-1 and kernel-firmware-20220411_f219d61.

marav · 04-14-2022, 11:33 AM

Quote:

Originally Posted by steve4lqdo

Regarding suspend/resume issues on AMD based Lenovo ThinkPad T495, the issue seems to be revolved with the combination of kernel-generic-5.17.3-x86_64-1 and kernel-firmware-20220411_f219d61.

I would also like to share my experience on this subject
My hibernation/resume problem was solved by switching from eLilo to grub
I think this is something to consider

steve4lqdo · 04-14-2022, 11:43 AM

Have been using Grub all along as I dual boot Slackware64-current and Linux Mint 19.3. Recent kernel upgrade solved the AMD based suspend/resume for me (in Slackware - Mint was used briefly recently to be able to suspend/resume, but now back to Slackware, again ;-).

steve4lqdo · 04-14-2022, 11:46 AM

Quote:

Originally Posted by steve4lqdo

Have been using Grub all along as I dual boot Slackware64-current and Linux Mint 19.3. Recent kernel upgrade solved the AMD based suspend/resume for me (in Slackware - Mint was used briefly recently to be able to suspend/resume, but now back to Slackware, again ;-).

Apologies - should have used the Quote option on my prior post - Newbie!

ttk · 04-14-2022, 04:40 PM

EDITED: D'OH! Disregard, I see there's already an update that fixes this :-}

Git security vulnerability announced:

https://github.blog/2022-04-12-git-s...ity-announced/

Mentions two CVE. CVE-2022-24765 appears relevant to Slackware when used in a multi-user environment, but the other CVE is Windows-specific.