Tiny Core Linux

Tiny Core Base => TCB Bugs => Topic started by: bmarkus on September 21, 2010, 02:36:40 AM

Title: Appbrowser error handling
Post by: bmarkus on September 21, 2010, 02:36:40 AM

Trying to install kismet.tcz on a clean TC 3.0 with appbrowser it hangs loading wireless-KERNEL-tinycore.tcz Dependency list is faulty:

Quote

wireless-KERNEL-tinycore.tcz
ncurses.tcz
libnl.tcz

so wireless-KERNEL-tinycore.tcz converted to wireless-2.6.33.3-tinycore-tinycore.tcz which doesn't exist. This is not handled by appbrowser. Appbrowser window can't be closed. Hitting ESC window is cleaned to wined but stays frozen, only text in title bar upper left corner application name.

What is strange after that exittc is crasing with segfault. Do not know why, but they are both fltk applications. Other fltk tools were not tested.

Title: Re: Appbrowser error handling
Post by: Jason W on September 21, 2010, 05:37:48 AM

dep file corrected.

Title: Re: Appbrowser error handling
Post by: bmarkus on September 21, 2010, 06:14:31 AM

Quote from: Jason W on September 21, 2010, 05:37:48 AM

dep file corrected.

Thanks. However this post is not about the dep bug but appbrowser.

Title: Re: Appbrowser error handling
Post by: Jason W on September 21, 2010, 06:46:17 AM

But you did mention the dep file bug, and listed the contents of the as being faulty.  I simply stated it was corrected.  Which is information I think Robert would like to know before proceeding further.

Title: Re: Appbrowser error handling
Post by: bmarkus on September 21, 2010, 07:20:45 AM

Quote from: Jason W on September 21, 2010, 06:46:17 AM

But you did mention the dep file bug, and listed the contents of the as being faulty.  I simply stated it was corrected.  Which is information I think Robert would like to know before proceeding further.

Thats fine, thanks again for correction :)

Title: Re: Appbrowser error handling
Post by: Jason W on September 21, 2010, 07:22:58 AM

It's all good.  :)

Title: Re: Appbrowser error handling
Post by: roberts on September 21, 2010, 12:32:50 PM

Indeed. Thanks Jason for not letting kismet stay broken.
Use cases and/or sample data for testing purposes is appreciated and will get its due diligence.
Hopefully too, the extension audit script will include testing for this case.

Title: Re: Appbrowser error handling
Post by: Jason W on September 21, 2010, 01:46:55 PM

Up to now I basically manually determined if the deps that have KERNEL in the names in the dep files are missing or present in the repo.  But I will add a test for either 32 bit or 64 bit presence of the deps that are kernel module extensions in the audit routine, echoing an error if neither exists in the repo.

Title: Re: Appbrowser error handling
Post by: roberts on September 22, 2010, 05:51:18 PM

Appbrowser via tce-load adjustment made and tested against provided use case.