Cannot load ooimpress and Qtiplot if network is off - related to cups, problem/solution found in client.conf

Bug #137614 reported by john
4
Affects Status Importance Assigned to Milestone
cupsys (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: cupsys

Apparent Cause:
  This only happens when i am using my laptop at home, connected to dsl
  at work it goes fine, connected to another network

Description:
  OOimpress tries to load a file and hangs. Could be any file, file does not has any internet link. Strace gives no useful information
  QtiPlot does not open at all.

Workaround:
I could repair it commenting out the line at /etc/cups/client.conf
# ServerName 1......

Seems that, not finding printer server, the application did not want to start. I donno where exactly this bug comes from, but i imagine it is from cups, cupsys.
Is there some better solution? I still want to use the printer server.
regards

strace from QtiPlot:
[...]
connect(13, {sa_family=AF_INET, sin_port=htons(631), sin_addr=inet_addr("1xx.xx.xx.xx")}, 16) = 0
[6x] time(NULL) = 1189024489
send(13, "POST / HTTP/1.1\r\nContent-Length:"..., 137, 0) = 137
[6x] time(NULL) = 1189024489
send(13, "\1\1@\2\0\0\0\1\1G\0\22attributes-charset\0\5"..., 414, 0) = 414
poll([{fd=13, events=POLLIN, revents=POLLIN}], 1, 1000) = 1
recv(13, "", 2048, 0) = 0
close(13) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 13
setsockopt(13, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
setsockopt(13, SOL_TCP, TCP_NODELAY, [1], 4) = 0
fcntl64(13, F_SETFD, FD_CLOEXEC) = 0
connect(13, {sa_family=AF_INET, sin_port=htons(631), sin_addr=inet_addr("1xx.xx.xx.xx")}, 16 <unfinished ...>
[...]

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. There has been no communication for over two months, I am setting the report to incomplete until the needed information can be attached.

It would be helpful to attach the cupsys log: This is a file where CUPSYS writes information about what it is doing. Almost all printing problems can be diagnosed from the error log, so it is the first place to look to start solving problems. To be useful, you must change the logging level:

   1.Select "System" -> "Administration" -> "Printing" in the main menu of your desktop. The printer setup tool system-config-printer will open. Select "Server Settings" in the list on the left. Then check the check box "Save debugging information for troubleshooting" and click "Apply".
   2. In /etc/cups/cupsd.conf, find the line "LogLevel ..."; change it to" LogLevel debug"; save.
   3. 'sudo /etc/init.d/cupsys restart'
   4. Try to print something.
   5. Add /var/log/cups/error_log as an attachment to the bug report.

Changed in cupsys:
assignee: nobody → charlie-tca
status: New → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) 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 cupsys:
assignee: charlie-tca → nobody
status: Incomplete → Invalid
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.