clicompanion-devs team mailing list archive

[David Caro <801906@xxxxxxxxxxxxxxxxxx>]

This is caused by a corrupted config file
(~/.config/clicompanion/config), when it reads the config from there, it
expects to find an integer, but instead it founds nothing, a config file
like this causes it:

  1 [terminal]
  2 scrollb = 
  3 colorf = #FFFFFF
  4 colorb = #000000
  5 encoding = UTF-8

Tested it and it does not solve the problem, also problems whith the
other config values when are incorrect or empty.

-- 
You received this bug notification because you are a member of CLI
Companion Development Team, which is subscribed to CLI Companion.
https://bugs.launchpad.net/bugs/801906

Title:
  clicompanion crashes on start with ValueError in _get()

Status in CLI Companion:
  Fix Committed

Bug description:
  In https://answers.launchpad.net/clicompanion/+question/162693, jpalsu
  (https://launchpad.net/~q-launchpad-vers-64-9ox-net) reported that
  running clicompanion in a Terminal window inside a GNOME session on an
  Ubuntu 10.04 Lucid system crashes, producing this output:

  using locale in system
  Traceback (most recent call last):
    File "/usr/bin/clicompanion", line 56, in <module>
      run()
    File "/usr/lib/pymodules/python2.6/clicompanionlib/view.py", line 406, in run
      main_window = MainWindow()
    File "/usr/lib/pymodules/python2.6/clicompanionlib/view.py", line 361, in __init__
      tabs.add_tab(self, self.notebook)
    File "/usr/lib/pymodules/python2.6/clicompanionlib/tabs.py", line 54, in add_tab
      self.update_term_config(_vte)
    File "/usr/lib/pymodules/python2.6/clicompanionlib/tabs.py", line 123, in update_term_config
      config_scrollback = config.getint('terminal', 'scrollb')
    File "/usr/lib/python2.6/ConfigParser.py", line 340, in getint
      return self._get(section, int, option)
    File "/usr/lib/python2.6/ConfigParser.py", line 337, in _get
      return conv(self.get(section, option))
  ValueError: invalid literal for int() with base 10: ''

  There is a slight resemblance here to the traceback in bug 748878, but
  they don't seem to be the same crash. Line numbers are different, this
  traceback has some calls that one doesn't have, and that crash is an
  IndexError rather than a ValueError.

To manage notifications about this bug go to:
https://bugs.launchpad.net/clicompanion/+bug/801906/+subscriptions