debconf frontend went away -- kde-ui

Bug #52682 reported by Wayne Brown
214
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Traceback (most recent call last):
  File "/usr/bin/ubiquity", line 130, in ?
    install(sys.argv[1])
  File "/usr/bin/ubiquity", line 55, in install
    ret = wizard.run()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 309, in run
    self.progress_loop()
  File "/usr/lib/python2.4/site-packages/ubiquity/frontend/kde-ui.py", line 520, in progress_loop
    ret = dbfilter.run_command(auto_process=True)
  File "/usr/lib/python2.4/site-packages/ubiquity/filteredcommand.py", line 128, in run_command
    self.start(auto_process=auto_process)
  File "/usr/lib/python2.4/site-packages/ubiquity/filteredcommand.py", line 45, in start
    self.db = DebconfCommunicator(PACKAGE, cloexec=True)
  File "/usr/lib/python2.4/site-packages/debconf.py", line 125, in __init__
    write=self.dccomm.tochild)
  File "/usr/lib/python2.4/site-packages/debconf.py", line 48, in __init__
    self.setUp(title)
  File "/usr/lib/python2.4/site-packages/debconf.py", line 51, in setUp
    self.version = self.version(2)
  File "/usr/lib/python2.4/site-packages/debconf.py", line 60, in <lambda>
    lambda *args, **kw: self.command(command, *args, **kw))
  File "/usr/lib/python2.4/site-packages/debconf.py", line 81, in command
    status = int(status)
ValueError: invalid literal for int():

Revision history for this message
John Vivirito (gnomefreak) wrote :

Thanks for taking the time to report this bug. Unfortunately, we are
not able to fix and find the bug because your description of the bug
didn't have enough information in it. Can you please attach a copy of /var/log/installer/syslog, /var/log/syslog, and /var/log/partman.

Changed in ubiquity:
status: Unconfirmed → Needs Info
Revision history for this message
Henrik Nilsen Omma (henrik) wrote : Re: debconf frontend went away

Hi, Just following up on this bug. Will you be able to provide these log files? (you will have to repeat the install attempt with the same Live CD to get them) Without the logs we will not be able to follow up this issue further. Thanks.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Several similar bugs with tracebacks ending in 'ValueError: invalid literal for int():' have been marked as duplicated of this one. We do not yet fully understand the root cause of this class of bugs and this symptom may indeed represent several underlying causes.

If you are an original reporter of this bug (and receive this note by email), we would still very much appreciate log files from the crash if you are able to reproduce it. If so please attach the files to your original bug and un-link it as a duplicate. Thanks!

Bug triagers see https://wiki.ubuntu.com/DebuggingUbiquity/DupCandidates for details on the process of determining duplicates for ubiquity.

Revision history for this message
philotech (philotech) wrote :

My installer crashed while attempting a kubuntu 6.10 install. My crash may be due to different reasons, but seems similar enough to post here.

Set up included preparing a dual boot config laid out on /dev/hda1:
partition1(primary)=xp 11.74GB
partition2(extended)=
               hda5=/boot 128MB
               hda6=swap 512MB
               hda7=/ 5.0GB
               hda8=/home 57GB
Traceback output:
               Traceback (most recent call last):
  File "/usr/lib/ubiquity/ubiquity/frontend/kde-ui.py", line 1361, in watch_debconf_fd_helper_read
    self.debconf_callbacks[source](source, debconf_condition)
  File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", line 178, in process_input
    self.status = self.wait()
  File "/usr/lib/ubiquity/ubiquity/filteredcommand.py", line 112, in wait
    self.cleanup()
  File "/usr/lib/ubiquity/ubiquity/components/console_setup.py", line 271, in cleanup
    print >>newconfig, line
IOError: [Errno 28] No space left on device

I've also attached files for the version of the installer used since no syslog was found in /var/log/installer; /var/log/syslog and /var/log/partman

I hope this bug report is more helpful in resolving the bug which may be a caused by some wider issue with the installer.

Thanks for all you do.

Revision history for this message
philotech (philotech) wrote :

I posted the above comment. Since it seems only one attachment at a time is allowed the other two will follow.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.