Printop doesn't start

Bug #55785 reported by Vassilis Pandis
2
Affects Status Importance Assigned to Milestone
printop (Debian)
Fix Released
Unknown
printop (Ubuntu)
Invalid
Medium
MOTU

Bug Description

I try to start printop, and this is what I get. This is with printop 1.12-6, on edgy.

Error in startup script: can't read "printcap_list": no such variable
    while executing
"foreach i $printcap_list {
    lappend tmpname_list [lindex $i 0]}"
    (procedure "insert_buttons" line 12)
    invoked from within
"insert_buttons $path $type $this_printer_menu $pattern"
    ("button" arm line 8)
    invoked from within
"switch -exact -- [lindex $line 1] {
            button {
              set pattern [lindex $line 2]
              set path [lindex $line 3]
              if {($path!="")} {
                set..."
    ("printer" arm line 2)
    invoked from within
"switch -exact -- [lindex $line 0] {
        printer {
          switch -exact -- [lindex $line 1] {
            button {
              set pattern [lindex $line 2]
              set pat..."
    invoked from within
"if [catch {open $configfile r} fileID] {
        return 0
} else {
# Zeilennummer auf 0 setzen (fuer Fehlerausgabe: wo ist der Fehler?)
set line_no 0
# solan..."
    (procedure "read_configs" line 10)
    invoked from within
"read_configs $type $this_printer_menu $appcfg"
    (procedure "build_printer_menu" line 18)
    invoked from within
"build_printer_menu choosequeue $main_printer_menu_button.m"
    (procedure "ShowWindow." line 175)
    invoked from within
"ShowWindow."
    (file "/usr/bin/printop" line 2310)

Revision history for this message
Vassilis Pandis (pandisv) wrote :

I found a similar issue in the Debian BTS as well...

Changed in printop:
status: Unknown → Needs Info
Revision history for this message
Vassilis Pandis (pandisv) wrote :

I can confirm this on current Edgy as well.

Changed in printop:
importance: Untriaged → Medium
status: Unconfirmed → Confirmed
Changed in printop:
assignee: nobody → motu
Revision history for this message
Vassilis Pandis (pandisv) wrote :

Still an issue with 1.12-8 on i386 Feisty.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 alpha?

Changed in printop:
status: Confirmed → Incomplete
Revision history for this message
Andreas Moog (ampelbein) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in printop (Ubuntu):
status: Incomplete → Invalid
Changed in printop (Debian):
status: Incomplete → Fix Released
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.