Program crashed on start

[Marek Bardoński]

Traceback (most recent call last):
  File "/usr/local/bin/clicompanion", line 56, in <module>
    run()
  File "/usr/local/lib/python2.7/dist-packages/clicompanionlib/view.py", line 392, in run
    main_window = MainWindow()
  File "/usr/local/lib/python2.7/dist-packages/clicompanionlib/view.py", line 268, in __init__
    treeview.set_model(self.liststore)

[boo (boo-vtemax)]

some trouble after last python updates

Traceback (most recent call last):
  File "/usr/bin/clicompanion", line 37, in <module>
    run()
  File "/usr/lib/pymodules/python2.6/clicompanionlib/view.py", line 278, in run
    main_window = MainWindow()
  File "/usr/lib/pymodules/python2.6/clicompanionlib/view.py", line 156, in __init__
    self.update(liststore)
  File "/usr/lib/pymodules/python2.6/clicompanionlib/view.py", line 75, in update
    commandplus = l[0], l[1]
IndexError: list index out of range

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

Trying to run the version from nightlys 1.0-4~ppa1~Lucid in Lucid won't start...

Get the same error as "boo" reports on 4.4.11 today is 9.5.11 ?

This matter is not settled yet?

btw: I've tested it in Natty-Kubuntu where it runs like charm.

[Marek Bardoński (bdfhjk)]

If this problem is still active, I look after it.

@Flames_in_Paradise - Did You try use actual version from repository?

@duanedesign - Did You packed last version?

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

@bdfhjk

Well, I installed V 1.0-4~ppa1~Lucid into Lucid-Gnome Version via Synatiptic. On my Machine all LTS updates were installed.

and as mentioned I still get exactelly the same errors as "boo" reported on 04-04-11 which is different from the initial bug-report.

Should I rather open a new bug-report ?

With the current stable version 1.0-3.1~ppa~all.deb there are no probs.

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

Well, bug-status states clearly "Fix commited" and not "Fix Released", yet. Just learned a new thing. ;_)

Besides, forget to mention: A nifty little piece of helpful software!

[Marek Bardoński (bdfhjk)]

Don't worry, duanedesign will release new version soon.

Thanks for your report.

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

Correction: Forgot to mention: A nifty little piece of helpful SW!

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

@ boo: reverted status back to "fix commited", which is not exactely the same as "fix released", but also a little more than confirmed.

@ bdhfhjk: tks 4 yr pretty fast reactions!

[Duane Hinnen (duanedesign)]

Having some issues packaging the new release will get them sorted ASAP and have a new release out very soon.

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

No need for hurry. Think Debian. When it's ready, it's done, Tks 4 replying. Can hardly wait to have them internationalized man-pages locally incorporarated.

The separation into stable-testing & nightlies is pretty neat, so far. Nightlies are not ideal 4 everyone (my very personal opinion).

[Eliah Kagan (degeneracypressure)]

There's a new bug (bug 801906) which slightly resembles this bug, and could easily be confused with this bug, but careful examination of the tracebacks shows it's probably a different bug.

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

Any news when the fix will get established, finally?

[Eliah Kagan (degeneracypressure)]

Folks: Please thoroughly read the descriptions of bug statuses at https://help.launchpad.net/Bugs/Statuses and http://blog.launchpad.net/general/of-bugs-and-statuses. I am setting this back to Fix Committed, as bdfhjk is a CLI Companion developer and had set it to that, indicating that the fix had been written, committed to the revision control system, and is available for testing, but has not yet been released for general use.

The Incomplete status is only appropriate when a bug report does not contain enough information for a developer to work toward fixing it. That does not seem to be the case here.

The status should probably not be changed again, except by CLI Companion developers. But if you know something I don't and feel you must change the status again, then please comment justifying the change in detail, as I am doing now.

An incorrect bug status can sometimes create confusion, delaying progress on a bug for a very long time.

[Flames_in_Paradise (ellisistfroh-deactivatedaccount)]

A bug with importance high, not getting fixed half a year after the fix has been commited should, in my opinion, get reported to security team. In order to have the ppa disabled. This is a harm to trust in the system of user/programmer responsibilities.

Seriously why should users wish to file a bug if nothing happens?

So would do I know, what anybody else can't see from within the history of this bugreporting-

Excuses for mistaking the bug-status in this case - Promise: I'll not be doing this again

[Eliah Kagan (degeneracypressure)]

What security team? Security teams are project-specific? Are you proposing to report a project to its own security team?

Since you're referring to the PPA, I presume you are thinking of the Ubuntu security team. But PPA's are unsupported and the Ubuntu project explicitly disclaims responsibility for their safety or quality. The entire point of PPA's is to provide easy access to software, or versions of software, that do *not* meet the requirements for inclusion in Ubuntu releases.

Finally, this is not a security bug, is it?

"Seriously why should users wish to file a bug if nothing happens?"

Because often something happens. That you have not gotten your desired level of response for this bug does not mean that it is irrational to file other bugs. However, it is certainly true that users such as you and me will direct our resources toward projects in accordance with what we perceive the benefits to be. So neither is it irrational, I think, for you to decide to support projects that respond more quickly to bug reports.

On the other hand, it is not really true that nothing has happened here. Just considerably less than you would have liked has happened. (And I do not mean that as a criticism.)

[Eliah Kagan (degeneracypressure)]

This bug is indicated to affect 4 people. Has anyone else tested the fix and confirmed that it does not work, or found that it does?

[Marek Bardoński (bdfhjk)]

Hi all!

Thanks for your comments.

Sorry for long delay, but I'm currently have many work with other projects.

Please remember, that clicompanion isn't a official part of ubuntu distribution yet. Before that, we will fix this bug.

 Marek Bardoński
 Clicompanion Dev. Team

[David Caro (dcaro)]

I tried to reproduce this error but was unable to, I'm closing it, if the bug persists for someone, please reopen and provide a little more info (python version, distribution, etc).

David