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
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#376 by Rava » 24 Dec 2015, 20:15

And another update

Silly my was wrong, http://sourceforge.net/projects/usm/files/ does indeed give sha1 and md5 checksum info, and I confirmed that both the md5sums of my local txz or xzm are okay, same as on sourceforge:

Code: Select all

c3a445d65751f0ef9a32aa6c466d4e20  usm-latest-0.0-noarch-1.txz
280a9db46ee87397d44a293a2731394f  usm-latest-0.0-noarch-1.xzm
Cheers!
Yours Rava

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#377 by Rava » 14 Feb 2016, 23:22

So, I started up another system and removed my local settings prior starting and updating usm, and alas! all worked as it should, I was finally able to download graphicsmagix with all dependencies. The strange thing, I don't have a single setup file related to usm in my local settings, so a random other setting must somehow mess up usm's behaviour, but I cannot figure out what that can be... :wall:
Cheers!
Yours Rava

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

Re: USM bug reports

Post#378 by Ed_P » 14 Feb 2016, 23:34

Rava wrote: so a random other setting must somehow mess up usm's behaviour, but I cannot figure out what that can be... :wall:
In some versions of USM there were problems with "white" files. Maybe your settings have some.

viewtopic.php?f=81&t=3501&p=25182#p25178
viewtopic.php?f=81&t=3501&p=25151#p25162
viewtopic.php?f=81&t=3501&p=25151#p25178

They can be manually deleted.
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5455
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM bug reports

Post#379 by brokenman » 16 Feb 2016, 11:16

In some versions of USM there were problems with "white" files.
This is misinformation. USM has nothing to do with whiteout files. If the problem is related to whiteout files then the version of USM is irrelevant.
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#380 by Rava » 16 Feb 2016, 15:45

Ed_P, I don't use any save.dat, so that cannot be the issue.
I checked: not a single '.wh.*' file in my local settings module,

Brokenman, how do you suggest I narrow down my issue? I don't want to have to remove my local settings, and only apply one changed file at a time, checking if usm still works okay after that, and then apply the next of my local settings, cause that would take days to accomplish...
Cheers!
Yours Rava

User avatar
brokenman
Site Admin
Site Admin
Posts: 5455
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM bug reports

Post#381 by brokenman » 16 Feb 2016, 22:16

I don't want to have to remove my local settings, and only apply one changed file at a time, checking if usm still works okay after that, and then apply the next of my local settings, cause that would take days to accomplish.
I can't think of another way to find out what is causing the trouble. It is exactly what I do all the time to track down problems. Not always one by one. You can group changes and then isolate the problem in a matter of hours.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Slaxmax
Contributor
Contributor
Posts: 403
Joined: 03 Jan 2013, 09:51
Distribution: KDE4
Location: Campinas Brazil https://goo.gl/yrxwKi

Re: USM bug reports

Post#382 by Slaxmax » 21 Feb 2016, 01:43

I have updated usm database but
In http://mirrors.slackware.com/slackware/ ... slackware/
exist packages available that do not appear in usm

for example in repo exist mesa-11.1.1-i586-1.txz

but in usm

Code: Select all

root@porteus:/home/guest# usm -s mesa

mesa-9.1.7-i486-1.txz was found in slackware [downgrade]
Packages found:   1 

Use:   usm -i <package>  for more info
Use:   usm -g <package>  to download
mesa 9.1.7?
“DNA is like a computer program but far, far more advanced than any software ever created.”
― Bill Gates, The Road Ahead

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

Re: USM bug reports

Post#383 by Bogomips » 21 Feb 2016, 01:52

^ Link is Slackwar Current, is it not? AFAIK usm only does up to 14.1 :Search:
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
Slaxmax
Contributor
Contributor
Posts: 403
Joined: 03 Jan 2013, 09:51
Distribution: KDE4
Location: Campinas Brazil https://goo.gl/yrxwKi

Re: USM bug reports

Post#384 by Slaxmax » 21 Feb 2016, 01:53

you are correct
“DNA is like a computer program but far, far more advanced than any software ever created.”
― Bill Gates, The Road Ahead

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

USM Fatal Error LIBS.TXT

Post#385 by Ed_P » 31 Oct 2016, 23:31

Could not find, when attempting to download alien flashplayer update.
Ed

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

Re: USM bug reports

Post#386 by Ed_P » 01 Nov 2016, 02:37

May not matter. Current flashplayer for Linux is 643 and the highest USM has is only 637. A dying system. :(
Ed

rchase
Samurai
Samurai
Posts: 154
Joined: 10 Jan 2016, 17:26
Distribution: Porteus 3.2.2 xfce x64
Location: Denver, Colorado

Re: USM bug reports

Post#387 by rchase » 01 Nov 2016, 15:16

Ed_P wrote:May not matter. Current flashplayer for Linux is 643 and the highest USM has is only 637. A dying system. :(
I certainly hope that Flash is dying!

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

Re: USM bug reports

Post#388 by Ed_P » 05 Nov 2016, 05:58

from=/ISOs/Porteus-RazorQT-v3.0.1-i486-nu.iso

Code: Select all

sh-4.2# usm -u all
 Starting alien database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE

gzip: /var/usm/alien/CHECKSUMS.md5.gz: not in gzip format
          

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while usm was running:                       
 
FATAL ERROR!
usm update_database 213
Could not decompress: CHECKSUMS.md5.gz
 
============================================================================== 


sh-4.2# 
Ed

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#389 by Rava » 15 Nov 2016, 07:21

Ed_P wrote:from=/ISOs/Porteus-RazorQT-v3.0.1-i486-nu.iso

Code: Select all

Could not decompress: CHECKSUMS.md5.gz
 
Please find this CHECKSUMS.md5.gz and use file CHECKSUMS.md5.gz and tell us what kind of file that really is.

I had this error as well in the past, turned out that the file was not really gzipped, but either not compressed or used a different compressor and had the wrong file ending.

It would help when you could tell what kind of file we deal with.

@brokenman:
When any file error occurs, it should be easily implemented to have a error function, that executes e.g. "file $ERROR-FILENAME" and the user would get an useful info what kind of file that really was, and when he posts the screenshot you would get the info ASAP as well...
Cheers!
Yours Rava

User avatar
brokenman
Site Admin
Site Admin
Posts: 5455
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM bug reports

Post#390 by brokenman » 15 Nov 2016, 13:56

What would you suggest?

The information given is sufficient for me to understand. Perhaps not so for a user.

Code: Select all

gzip: /var/usm/alien/CHECKSUMS.md5.gz: not in gzip format
FATAL ERROR!
usm update_database 213
Could not decompress: CHECKSUMS.md5.gz
Either the file format changed or the download was interrupted resulting in a file that is corrupt.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Post Reply