Custom Query (121 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (4 - 6 of 121)

1 2 3 4 5 6 7 8 9 10 11 12
Ticket Resolution Summary Owner Reporter
#122 invalid QPDFVIEW don't print on printer attached with socket (network printer) in CUPS Anchieri
Description

A years ago, I've acquired a new printer; HP OFFICEJET PRO 8610 that's a network printer with a USB port attachement. Recently a few week ago, I have decided to use it as a network instead of USB and so I installed it as a new Net printer under CUPS. If I print using USB port QPDFVIEW print immediately but if want print using the Net version the CUPS wait with msg: the printer is not responding. I have also LUCIDE that I use to print with CUPS, it print with all the two type of connection, USB or NET.

#121 fixed qpdfview can not print files with umlauts in file name diver andib
Description

qpdfview 0.4.16 with current netlabs-rel & netlabs-exp packages (running on heavily updated eCS2.1DE).

File names with umlauts can not be printed. F.i. trying to print _test_ü.pdf leads to a dialog "Warnung - Konnte >>T:/Temp/_test2_ü.pdf<< nicht drucken". File attached.

The same file copied to _test2.pdf prints fine.

#120 fixed PSI v0.16-dev-20150213 - crashes when entering IM message diver darcio
Description

I have been using PSI for a number of years. Some time ago I updated to 0.16.3, which was working quite nicely.

Recently however I discovered that as soon as I attmept to respond to an IM msg and start typing my response the app crashes. This only happens as I enter a response, the apps does not have a problem showing me the IM msg that was sent to me.

Through debugging all I have been able to determine is that as soon as the 2nd character of my response is being entered the app crashes, otherwise, if just a single character is entered it is fine.

I have not been able to narrow this down to anything else. All the pre-reqs listed in the readme are installed. My YUM/RPM uses the pentium4 platform.

1 2 3 4 5 6 7 8 9 10 11 12
Note: See TracQuery for help on using queries.