USM bug reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
User avatar
brokenman
Site Admin
Site Admin
Posts: 5436
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM bug reports

Post#301 by brokenman » 18 Feb 2015, 14:45

I will probably move the files off sourceforge for the next release. Thanks for the report. I was also having trouble with being denied login last week. Seems they may be under attack.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: USM bug reports

Post#302 by Rava » 20 Feb 2015, 21:24

brokenman wrote:Seems they may be under attack.
Most probably, since I found a site reporting the same error end of Jan, 2015...
Cheers!
Yours Rava

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: [FAA]USM bug reports

Post#303 by ElectriQT » 26 Feb 2015, 19:56

brokenman wrote:Ok so something in your changes modules may be affecting the LIBS.TXT file. I remember there was a problem in 3.0.1 at some stage with whiteout files.

Wiping USM out manually will not help if the problem is indeed in your save modules as they may overwrite the USM file (I don't know your module layout so it is hard to tell).
-I wiped, it did help. :-)
It Works OK now.
Not in root/usm/local/ , There it is just the "libs.txt" in my folder /local/
(libs.txt , in lowercase letters it is, but I tried rename it with highcases-letters also, no changes. )

Code: Select all

This folder (root/usm/local/) should not exist and most definitely LIBS.TXT should be in uppercase. How did it become lowercase? 
/root/usm/ was our experiment to make it more persistent with the databases when our drive "letter" keep changing when swappng around on different HW, But I am not sure if that has anything to do with this error, as I did that /root/usm weeks after the first LIBS-errors.

How did it become lowerboxletters?
-yes, good question.. I can promise it was not done by me. :-)
Yes I think you need to start again with a fresh system and add your changes modules back one at a time until you find the one causing the problem. If you don't do this then the problem will never be found. Also make sure your USM module you downloaded is the last thing to be loaded. Perhaps name it zz-usm-3.1.7-noarch-1.xzm

OK, I will name it ÖÖ-usm-3.1.7 then, ötherwise it is nöt the very läst letter in the Älphäbet here :-)
we have 6 more than you, I assume. The åäö and ÅÄÖ, hehe..

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: [FAA]USM bug reports

Post#304 by Rava » 01 Mar 2015, 16:34

ElectriQT wrote:OK, I will name it ÖÖ-usm-3.1.7 then, ötherwise it is nöt the very läst letter in the Älphäbet here :-)
we have 6 more than you, I assume. The åäö and ÅÄÖ, hehe..
It is not about how your local alphabet sorts stuff, but how that is done at bootup. I am sure this is handled via busybox.

And as you can see, Linux has now the same annoying way in sorting files like Windoze, at least my XFCe Porteus does that since years.

Usually, 1,2,3...11,12...99,100 are sorted like in the alphabet. But Windoze and also now most Linux (in the GUI at least) sort it with discarding leading zero, and read it as numbers till the first alphabet character appears:.

So, 002 is not at the very beginning, but after 1 and prior 3. and 00918a is read as number 918, then alphabet sorting, so 2010z would come after 00918a or 918a,, since one is sorted as "number" 2010, and all the others are read/sorted as "number" 918...

Since you cannot be sure how busybox does the reading / sorting, I suggest you name it in a numerical way, like 990-name being the last ones... Just my 0,02€.

BTW, seems you lack üÜ and ß. :twisted:
Cheers!
Yours Rava

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: [FAA]USM bug reports

Post#305 by ElectriQT » 01 Mar 2015, 18:53

So, 002 is not at the very beginning, but after 1 and prior 3. and 00918a is read as number 918, then alphabet sorting, so 2010z would come after 00918a or 918a,, since one is sorted as "number" 2010, and all the others are read/sorted as "number" 918...
-Aha,
So its not the first letter, its the full "number-value" that counts ?
"2010" will be a larger sum, and will be put after "918", not sorted on the first "2.."
They ignore zeroes, and read the full number as a "value" ?
Since you cannot be sure how busybox does the reading / sorting, I suggest you name it in a numerical way, like 990-name being the last ones... Just my 0,02€.
Mmm, OK. I Will have this in mind in the future and try to double-check my work, thank you.
BTW, seems you lack üÜ and ß. :twisted:
ûes ït sëams så. :-)
But it is still there if I just hold down AltGr when selecting the lowbox "s" = ß.

Where is this ß letter used normally?
(I assume it is like a speed-format for any dual "s" in words,)
and where is it placed in the normal alphabet, -should it be sorted as a small "s" in computer programs ?

User avatar
Rava
Contributor
Contributor
Posts: 1319
Joined: 11 Jan 2011, 02:46
Distribution: Porteus 3.1.0 x86-64 XFCe
Location: Germany

Re: [FAA]USM bug reports

Post#306 by Rava » 01 Mar 2015, 22:48

ElectriQT wrote:So its not the first letter, its the full "number-value" that counts ?
"2010" will be a larger sum, and will be put after "918", not sorted on the first "2.."
They ignore zeroes, and read the full number as a "value" ?
Indeed, at least when you use the GUI program and sort via "name"
To show you how it looks in Port 3.1 XFCe I would have to use a screenshot / jpeg since I hardly can copy such info as text, since the console / terminals not do such nonsense...

At least to me it's nonsense, and buggy, I often have the issue with randomly named files, and when these are images and I browse them all, and then rename or move some, I often run into the issue that 90-95% of the files (or less) are sorted like I explained above, but when all in a sudden files with just characters, and only numbers in the end or middle, but never at the beginning are there then the image browser and the GUI file browser are confused, and no longer show the same order.
Could be that this is a bug in my favourite image viewer, viewnior, but I am too lazy to cross check that weird behaviour is GPicView does the same, cause it is not helpful in determine which one does the issue. And yes, viewnior sure shows the images sorted by name, but it also uses that weird "numbering" logic...

Mmm, OK. I Will have this in mind in the future and try to double-check my work, thank you.
Just my 2 cents, mind you, but such silly copying of senseless Windoze behaviour results, at least in this case, just in bugs.



[off topic]
Where is this ß letter used normally?
(I assume it is like a speed-format for any dual "s" in words,)
and where is it placed in the normal alphabet, -should it be sorted as a small "s" in computer programs ?
Depends. I am with the old German spelling from 1901, since the new one is quite messed up, and quite some German large newspaper companies went back to old spelling as well...

Some words are just spelled with an "ß". Or have been in the old spelling from 1901, like "weiß", or "das" vs "daß", they changed the last one into "dass", but that's as awful as having now Delfin instead of Delphin. *shudders in horror*
[/off topic]
Cheers!
Yours Rava

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: USM bug reports

Post#307 by Ed_P » 10 Mar 2015, 19:39

Tried to download the latest 31.5 x64 Firefox module from slackwarepatches and salix using USM's GUI and got the Message: Fatal Error. LIBS.TXT window followed by the Processing: Brokenman needs to update database. Could not find LIBS.TXT window.

Updated the databases, which appeared to indicate the LIB.TXT file was being updated, closed USM GUI, reopened USM, retried the downloads, same result.

The LIBS.TXT file does exist in /mnt/live/memory/changes/var/usm/slackwarepatches and /mnt/live/memory/changes/var/usm/salix.
Ed

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: USM bug reports

Post#308 by ElectriQT » 10 Mar 2015, 23:08

Ed_P wrote:Tried to download the latest 31.5 x64 Firefox module from slackwarepatches and salix using USM's GUI and got the Message: Fatal Error. LIBS.TXT window followed by the Processing: Brokenman needs to update database. Could not find LIBS.TXT window.

Updated the databases, which appeared to indicate the LIB.TXT file was being updated, closed USM GUI, reopened USM, retried the downloads, same result.

The LIBS.TXT file does exist in /mnt/live/memory/changes/var/usm/slackwarepatches and /mnt/live/memory/changes/var/usm/salix.
1. Hm, The Firefox in USM "slackwarepatches" is 32bit. Right?
@Brokenman: Maybe a future usm should check for the "486" / "686" in some way, and default it marked in bold or something at the one we already do have installed? Or show us the latest version and the correct 32 or 64 bit choice at top of the list?

(I guess a 64bit system will run 32bit applications(?), but probably not run at all with 64 bit wide applications on a 32bit OS. )

2. Did you try the "trick" I talked about?
A workaround for me was to un-check the "resolve dependencies" box in the usm:s (GUI) front page
(..But by now you probably already have updated your Firefox by a manual download from slackware or so?)

3. I finally had to wipe all of my usm-places, with help from Brokenmans instructions that he had written here. (in some other conversation) and then I installed a new one, that did help me to get USM in 32bit LXQT 3.01 to work ok.
Not sure it was 100% the same problem as you have now, but LIBS-error was one of them..

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: USM bug reports

Post#309 by Ed_P » 11 Mar 2015, 00:53

ElectriQT wrote:1. Hm, The Firefox in USM "slackwarepatches" is 32bit. Right?
Nope. x64 bit version. It matches the version that I'm running.
Ed_P wrote:Tried to download the latest 31.5 x64 Firefox module
2. Did you try the "trick" I talked about?
A workaround for me was to un-check the "resolve dependencies" box in the usm:s (GUI) front page
No, I didn't see it.
(..But by now you probably already have updated your Firefox by a manual download from slackware or so?)

No.
3. I finally had to wipe all of my usm-places, with help from Brokenmans instructions that he had written here. (in some other conversation) and then I installed a new one, that did help me to get USM in 32bit LXQT 3.01 to work ok.
Not sure it was 100% the same problem as you have now, but LIBS-error was one of them..
I'm not sure either. I've been having problems with USM for sometime. viewtopic.php?f=117&t=3205&start=270#p31332 But my posts are either ignored or deleted so...
Ed

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: USM bug reports

Post#310 by ElectriQT » 11 Mar 2015, 08:41

Ed_P wrote:
ElectriQT wrote:1. Hm, The Firefox in USM "slackwarepatches" is 32bit. Right?
Nope. x64 bit version. It matches the version that I'm running.
aha, in my 32bit PorteusLXQT 3.01 & USM (V3.17) both the 64 and 32 bit programs found are shown to me, as "installed", but from slackwarepatches it is only a 32bit version shown in USM. Hmm, OK, Good, So then it is already a normal thing that USM actually does.? Than i'm sorry about that unnecessary "new" usm-feature suggestion Hehe.

2. Did you try the "trick" I talked about?
A workaround for me was to un-check the "resolve dependencies" box in the usm:s (GUI) front page
No, I didn't see it.
Ok, its on the same page, as your comment. Here:
viewtopic.php?f=117&t=3205&start=270#p31263

Oki, it is not easy to keep up with all messages everywhere
-So did it help now to uncheck the [box] before downloading Firefox and flash?

ElectriQT
Samurai
Samurai
Posts: 115
Joined: 10 Nov 2013, 12:02
Distribution: LXDE3.5Manjaro, LXDE3.01-32bit
Location: Sweden

Re: USM bug reports

Post#311 by ElectriQT » 11 Mar 2015, 08:53

I'm not sure either. I've been having problems with USM for sometime. viewtopic.php?f=117&t=3205&start=270#p31332 But my posts are either ignored or deleted so...
Well, people that have *a lot* to do, some must work to earn money for example :-)
I would not say ignored, I did read it for example,

Time & total personal workload is probably the main problem, and probably a huge one.
it would be nice to have a lot more really competent people from the other Linux world involved in this fantastic project, I dont understand why it is not so. But Time is probably the main reason for that also.

(also, I dont always get it when you write, sometimes is a bit "encrypted" with shortforms, wiwryf and things like that, English is not my native language. I'm Still learning.. :-)

Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: USM bug reports

Post#312 by Bogomips » 11 Mar 2015, 19:26

@ElectiQT

jimwg has been experiencing fairly similar problems to yours with USM. viewtopic.php?f=81&t=4344 & viewtopic.php?f=81&t=4335&start=15#p31576
He needs to purge his system of USM, for one thing. Perhaps you can give him the benefit of your experience. As he says he's a non-techie, he would require some hand-holding :)
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: USM bug reports

Post#313 by Ed_P » 12 Mar 2015, 05:27

ElectriQT wrote:So did it help now to uncheck the [box] before downloading Firefox and flash?
As a matter of fact it did. Thank you. :beer: But I only did it for FireFox, I already had a Flash 442 module.
(also, I dont always get it when you write, sometimes is a bit "encrypted" with shortforms, wiwryf and things like that, English is not my native language. I'm Still learning.. :-)
I'm sorry. The shortcuts I usually use are:

FYI = For Your Information
FWIW =For What Its Worth
IMO = In My Opinion
IMHO = In My Humble Opinion
LOL = Laughing Out Loud

If you encounter any others let me know and I will spell them out.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: USM bug reports

Post#314 by Ed_P » 12 Mar 2015, 23:00

This output might shed some light on the USM LIBS.TXT missing error.

Code: Select all

guest@porteus:~$ ls -gR /var/usm  
/var/usm:
total 0
drwxr-xr-x 2 root 75 Mar 12 00:41 alien/
drwxr-xr-x 2 root 21 Mar 12 00:54 local/              <<<<<<<<<<<<<<<<<<< !!
drwxr-xr-x 2 root 75 Mar 12 00:41 ponce/
drwxr-xr-x 2 root 75 Mar 12 00:41 salix/
drwxr-xr-x 2 root 28 Mar 12 00:42 sbo/
drwxr-xr-x 2 root 75 Mar 12 00:42 slackware/
drwxr-xr-x 2 root 75 Mar 12 00:42 slackwarepatches/
drwxr-xr-x 2 root 75 Mar 12 00:41 slacky/

/var/usm/alien:
total 424
-rw-r--r-- 1 root 167464 Mar 11 11:20 CHECKSUMS.md5
-rw-r--r-- 1 root  44833 Mar 12 00:41 LIBS.TXT
-rw-r--r-- 1 root  81287 Mar 12 00:41 OPTIFEST
-rw-r--r-- 1 root 137949 Mar 12 00:41 PACKAGES.TXT

/var/usm/local:                                    <<<<<<<<<<<<<<<<<<  !!
total 224
-rw-r--r-- 1 root 226434 Mar 12 00:54 libs.txt     <<<<<<<<<<<<<<<<<<  !!

/var/usm/ponce:
total 756
-rw-r--r-- 1 root 181279 Jan 21 01:32 CHECKSUMS.md5
-rw-r--r-- 1 root 258504 Mar 12 00:41 LIBS.TXT
-rw-r--r-- 1 root  56800 Mar 12 00:41 OPTIFEST
-rw-r--r-- 1 root 268119 Jan 21 01:32 PACKAGES.TXT

/var/usm/salix:
total 704
-rw-r--r-- 1 root  74130 Mar  3 15:48 CHECKSUMS.md5
-rw-r--r-- 1 root 142423 Mar 12 00:41 LIBS.TXT
-rw-r--r-- 1 root  62661 Mar 12 00:41 OPTIFEST
-rw-r--r-- 1 root 434039 Mar 12 00:41 PACKAGES.TXT

/var/usm/sbo:
total 2432
-rw-r--r-- 1 root 2489955 Mar 12 00:42 SLACKBUILDS.TXT

/var/usm/slackware:
total 1352
-rw-r--r-- 1 root 263541 Nov  3  2013 CHECKSUMS.md5
-rw-r--r-- 1 root 298678 Mar 12 00:42 LIBS.TXT
-rw-r--r-- 1 root 152124 Mar 12 00:42 OPTIFEST
-rw-r--r-- 1 root 663291 Mar 12 00:42 PACKAGES.TXT

/var/usm/slackwarepatches:
total 152
-rw-r--r-- 1 root 59741 Mar  5 17:04 CHECKSUMS.md5
-rw-r--r-- 1 root 18973 Mar 12 00:42 LIBS.TXT
-rw-r--r-- 1 root 31436 Mar 12 00:42 OPTIFEST
-rw-r--r-- 1 root 40606 Mar  5 17:04 PACKAGES.TXT

/var/usm/slacky:
total 576
-rw-r--r-- 1 root 155127 Feb 22 23:01 CHECKSUMS.md5
-rw-r--r-- 1 root  82555 Mar 12 00:41 LIBS.TXT
-rw-r--r-- 1 root  50143 Mar 12 00:41 OPTIFEST
-rw-r--r-- 1 root 291929 Feb 22 23:00 PACKAGES.TXT
guest@porteus:~$ 
So what's creating the /var/usm/local/libs.txt file? I'd post it but its about 7000 lines like these:

Code: Select all

/usr/lib/gtk-3.0/3.0.0/immodules/im-am-et.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-cedilla.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-cyrillic-translit.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-inuktitut.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-ipa.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-multipress.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-thai.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-ti-er.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-ti-et.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-viqr.so
/usr/lib/gtk-3.0/3.0.0/immodules/im-xim.so
/usr/lib/gtk-3.0/3.0.0/printbackends/libprintbackend-cups.so
/usr/lib/gtk-3.0/3.0.0/printbackends/libprintbackend-file.so
/usr/lib/gtk-3.0/3.0.0/printbackends/libprintbackend-lpr.so
/usr/lib/gtk-3.0/3.0.0/theming-engines/libadwaita.so
/usr/lib/gtk-2.0/2.10.0/engines/libadwaita.so
/usr/lib/gtk-2.0/2.10.0/engines/libpixmap.so
/usr/lib/gtk-2.0/2.10.0/engines/libsvg.so
/usr/lib/gtk-2.0/2.10.0/immodules/im-am-et.so
All referencing .so files.
Ed

User avatar
Ed_P
Contributor
Contributor
Posts: 3058
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: USM bug reports

Post#315 by Ed_P » 13 Mar 2015, 20:26

Ed_P wrote: So what's creating the /var/usm/local/libs.txt file?
USM GUI 3.1.7 when the Resolve Dependencies option is enabled.
Ed

Post Reply