WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Appbrowser error handling  (Read 2922 times)

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7183
    • My Community Forum
Appbrowser error handling
« on: September 20, 2010, 11:36:40 PM »
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.


Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9730
Re: Appbrowser error handling
« Reply #1 on: September 21, 2010, 02:37:48 AM »
dep file corrected.

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7183
    • My Community Forum
Re: Appbrowser error handling
« Reply #2 on: September 21, 2010, 03:14:31 AM »
dep file corrected.

Thanks. However this post is not about the dep bug but appbrowser.
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9730
Re: Appbrowser error handling
« Reply #3 on: September 21, 2010, 03: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.

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7183
    • My Community Forum
Re: Appbrowser error handling
« Reply #4 on: September 21, 2010, 04:20:45 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 :)
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9730
Re: Appbrowser error handling
« Reply #5 on: September 21, 2010, 04:22:58 AM »
It's all good.  :)

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: Appbrowser error handling
« Reply #6 on: September 21, 2010, 09:32:50 AM »
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.
10+ Years Contributing to Linux Open Source Projects.

Offline Jason W

  • Administrator
  • Hero Member
  • *****
  • Posts: 9730
Re: Appbrowser error handling
« Reply #7 on: September 21, 2010, 10:46:55 AM »
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.

Offline roberts

  • Administrator
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: Appbrowser error handling
« Reply #8 on: September 22, 2010, 02:51:18 PM »
Appbrowser via tce-load adjustment made and tested against provided use case.
10+ Years Contributing to Linux Open Source Projects.