Summary: | app-portage/portato-0.14 crashes while launching | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Robert Cabrera <robcab666> |
Component: | Third-Party Tools | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | gentoo, jokey |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=404973 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Disable default eix |
Description
Robert Cabrera
2010-05-12 03:14:16 UTC
Please enable debugging in /etc/portato/portato.cfg and launch portato from a console. Then please paste the output. (Btw: Python-3 is not supported) First off, I only tried using python-3 to see if it would work after failing to launch a half dozen tries with my default python interpretor, python-2.6. As you requested, here is the output after attempting to launch from konsole: ~ $ portato * Using 'kdesu' as su command. (__init__.py:120) kdesu(12393) KDESu::PtyProcess::exec: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/process.cpp : 295 ] Running "/bin/su" kdesu(12393) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/su.cpp : 259 ] Read line "Password: " kdesu(12393) KDESu::PtyProcess::exec: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/process.cpp : 295 ] Running "/bin/su" kdesu(12393) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/su.cpp : 259 ] Read line "Password: " kdesu(12393) KDESu::PtyProcess::WaitSlave: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/process.cpp : 381 ] Child pid 12603 kdesu(12393) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/su.cpp : 259 ] Read line "" kdesu(12393) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/su.cpp : 259 ] Read line "kdesu_stub" kdesu(12393) KDESu::PtyProcess::exec: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/process.cpp : 295 ] Running "/bin/su" kdesu(12393) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/su.cpp : 259 ] Read line "Password: " kdesu(12393) KDESu::PtyProcess::WaitSlave: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/process.cpp : 381 ] Child pid 12608 kdesu(12393) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/su.cpp : 259 ] Read line "" kdesu(12393) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.4.3/work/kdelibs-4.4.3/kdesu/su.cpp : 259 ] Read line "kdesu_stub" * Switching from 'UTF-8' to 'UTF-8'. (basic.py:40) * Starting Portato v. 0.14 (__init__.py:91) * Setting Portage System (__init__.py:64) * Using portage-2.2 (__init__.py:21) * External Warning: /usr/lib/portage/pym/portage/util/__init__.py:1121: DeprecationWarning: The 'myroot' parameter for portage.config.getvirtuals() is deprecated result = lazy_item.func(*pargs, **kwargs) (__init__.py:1121) * All prereqs matched. Fine :) (main.py:1877) * There is a menu-file for 'MainWindow'. Trying to load it. (basic.py:96) * Using database type 'EixSQLDatabase' (__init__.py:63) * Loading 'DB' session from /root/.portato/db.cfg. (session.py:70) * Cache file '/var/cache/eix' does not exist. Using default instead. (eix_sql.py:35) * Exception: Traceback (most recent call last): File "/usr/bin/portato", line 20, in <module> start() File "/usr/lib/python2.6/site-packages/portato/__init__.py", line 96, in start run() File "/usr/lib/python2.6/site-packages/portato/gui/__init__.py", line 29, in run m = MainWindow(s) File "/usr/lib/python2.6/site-packages/portato/gui/windows/main.py", line 477, in __init__ self.db = Database(self.cfg.get("type", section = "DATABASE")) File "/usr/lib/python2.6/site-packages/portato/db/__init__.py", line 32, in __new__ cls._the_instance = dbcls(cls._get_session()) File "/usr/lib/python2.6/site-packages/portato/db/eix_sql.py", line 42, in __init__ SQLDatabase.__init__(self, session) File "/usr/lib/python2.6/site-packages/portato/db/sql.py", line 80, in __init__ self.was_updated = self.updated() File "/usr/lib/python2.6/site-packages/portato/db/eix_sql.py", line 48, in updated mtime = os.stat(self.cache).st_mtime OSError: [Errno 2] No such file or directory: '/var/cache/eix' Portato version: 0.14 System: Gentoo Python version: 2.6.5 (release26-maint, May 12 2010, 11:33:08) [GCC 4.4.3] Used backend: Portage 2.2_rc67 Used database type: eixsql pygtk: 2.16.0 (using GTK+: 2.18.9) pygobject: 2.20.0 (using GLib: 2.22.5) (exception_handling.py:132) * Listener received: ['close'] (listener.py:45) * Subprocess finished (__init__.py:128) Then it crashed. I hope this helps. Until then I'm switching back to the previous version. Ciao Well - if you do not use eix, you should not install portato with the eix flag -- or at least change the database type in portato.cfg Three possibilities: - run eix-update (and always use eix-sync instead of 'emerge --sync') - use another backend type in portato.cfg - reinstall portato with USE=-eix Closed as invalid (In reply to comment #3) > Well - if you do not use eix, you should not install portato with the eix flag > -- or at least change the database type in portato.cfg > > Three possibilities: > > - run eix-update (and always use eix-sync instead of 'emerge --sync') > - use another backend type in portato.cfg > - reinstall portato with USE=-eix > > Closed as invalid > First, You don't have to be a smart-ass! Being rude is inappropriate and uncalled for! Second, as you can see from my make.conf I don't have eix enabled. I installed this version as I have every version since I started using it over a year ago with the default settings. Third, If every other version has installed and ran properly and this one doesn't, then it is either a regression or something has changed to make this no longer workable. Fourth, Previous versions DO NOT have an eix use flag, period! If this one now does, then the default should be for it to be disabled and turned on as and option! Not the other way around. There are many Gentoo users (perhaps most) who do not use eix because we don't subscribe to any external repositories. Bottom line: I will recompile without the eix use flag and try again. But the default setting should be Without eix enabled! (In reply to comment #4) > Second, as you can see from my make.conf I don't have eix enabled. I installed > this version as I have every version since I started using it over a year ago > with the default settings. I just didn't expect, that someone installs a software without checking which flags are used and what these flags do. > Fourth, Previous versions DO NOT have an eix use flag, period! If this one now > does, then the default should be for it to be disabled and turned on as and > option! Not the other way around. Nope - the usage of the eix database is (in my eyes) the major improvement over 0.13.1 and adds a couple of features. Additionally this is the one I do 95% of the tests on, so it is more stable than the other ones. > There are many Gentoo users (perhaps most) who do not use eix because we don't > subscribe to any external repositories. Ehm? eix is about fast searching (and it is one if the first tools I tell newcomers to install). It has per se nothing to do with external repositories (in fact: using eix-remote is not supported at all with portato) See: https://bugs.launchpad.net/portato/+bug/579632 Created attachment 231263 [details, diff]
Disable default eix
Ok - after thinking this through, I have to concede the point to you. As long as Portato does not handle a misconfiguration gracefully (ie. not just crashing), it should be disabled by default. It will be enabled by default in the future versions again.
Default eix has been removed. I think a warning or something similar would make sense anyway. In case /var/cache/eix doesn't exists let the user know that he should run "eix-update" first. So I'll leave this bug open until it has been fixed. First to Rene': I want to thank you for the time you have taken to read through and try to resolve this issue. I was frustrated with several personal issues beyond this one, and when I read your response thought your reply was curt, then over-reacted in my statement. That out of the way... I too use Portato primarily as a search tool, but also for finding what files an app may have installed, looking at and examining ebuilds, and for reading changelogs. I seldom use it for installing software, but when I do it's usually when lazy and need to unmask or add a specific use where it's convenient to not have to open an editor as root. I usually do look at use flags when installing updates and make adjustments accordingly, however default use changes generally don't cause an app to crash and I'm encouraged by your post as you now understand where I was coming from with this. It's my experience over the last 6+ years I've been running Gentoo that default changes in use flags generally add functionality or fix bugs, so I except them. I'm much more careful about use flag changes to apps where I desire a specific feature or function that I know I want / need. I'm not a programmer, a an IT pro, or a "techie". I'm a 47yo truck driver who's been a computer hobbyist for 25 years, many use changes are beyond the scope of my knowledge / expertise, which is why I generally choose the default settings for updates unless I know for sure to do otherwise. Finally to Christian: Thanks for thinking about this and chiming in, I agree that something like a warning would solve this in the future. Something along the lines of "You are installing with the use flag 'eix' enabled. Please run eix-update prior to running Portato or it will crash!" would go a long way towards resolving this. And to both of you: Thanks for your continued efforts in making Gentoo the truly awesome OS that it is! Ciao (In reply to comment #8) > First to Rene': I want to thank you for the time you have taken to read through > and try to resolve this issue. I was frustrated with several personal issues > beyond this one, and when I read your response thought your reply was curt, > then over-reacted in my statement. > > That out of the way... I too use Portato primarily as a search tool, but also > for finding what files an app may have installed, looking at and examining > ebuilds, and for reading changelogs. I seldom use it for installing software, > but when I do it's usually when lazy and need to unmask or add a specific use > where it's convenient to not have to open an editor as root. > > I usually do look at use flags when installing updates and make adjustments > accordingly, however default use changes generally don't cause an app to crash > and I'm encouraged by your post as you now understand where I was coming from > with this. It's my experience over the last 6+ years I've been running Gentoo > that default changes in use flags generally add functionality or fix bugs, so I > except them. I'm much more careful about use flag changes to apps where I > desire a specific feature or function that I know I want / need. > > I'm not a programmer, a an IT pro, or a "techie". I'm a 47yo truck driver who's > been a computer hobbyist for 25 years, many use changes are beyond the scope of > my knowledge / expertise, which is why I generally choose the default settings > for updates unless I know for sure to do otherwise. > > Finally to Christian: Thanks for thinking about this and chiming in, I agree > that something like a warning would solve this in the future. Something along > the lines of "You are installing with the use flag 'eix' enabled. Please run > eix-update prior to running Portato or it will crash!" would go a long way > towards resolving this. > > And to both of you: Thanks for your continued efforts in making Gentoo the > truly awesome OS that it is! > > Ciao > Above I meant "accept them", not "except them" in regards to 'use' changes. Sorry, I was driving half the night and haven't had enough coffee yet. Ciao Please see bug 404973 |