[Bug 278261] Re: two xscreens -> gnome panel crashes

2008-12-02 Thread Brian Litzinger
I ran into this same problem on 2 machines I updated today.

I also ran into the 177 vs 173 problem.  Downgrading to 173 fixed the second 
screen desktop.
I run independent screens like most people writing here.

When I use an application launcher in the gnome panel to launch something the 
gnome-panel
becomes non-responsive and consumes 100% of one cpu.  'killall'ing it brings up 
another
gnome-panel which works so long as I do not launch something from the screen 1 
gnome-panel.

I can launch things from the gnome menu successfully, but launching from an 
custom application
launcher causes the lockup.

-- 
two xscreens -> gnome panel crashes
https://bugs.launchpad.net/bugs/278261
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in ubuntu.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


Re: [Bug 196429] Re: evince/evolution/gtk-print-dialog printing and system-config-printer fail when using client.conf with IP address for which there is no reverse look-up available

2008-03-10 Thread Brian Litzinger
On Sat, Mar 08, 2008 at 03:05:09PM -, Sebastien Bacher wrote:
> Could you describe easy steps to create the issue?

I assume you have some sort of non-network printer being served
by a cups server on machine 192.168.1.16 (any IP will do).

On a client machine

edit /etc/cups/client.conf so it reads

ServerName 192.168.1.16

Arrange for there to be no reverse DNS mapping for 192.168.1.16
on your client machine.

That would mean make sure it is not defined in /etc/hosts, and
that your DNS server has no reverse resolution for 192.168.1.16.
I would suggest getting rid of any forward resolution if you
want to be extra sure.

Make sure there are no caching DNS data tables laying about on
the client machine.

Basically you want this command

% host 192.168.1.16

to return

Host 16.1.186.192.in-addr.arpa not found: 3(NXDOMAIN)

on the client machine.

restart cupsys on the client machine.

Use the GTK print dialog from evince or the system menu
print configurator.  

The GTK print dialog will show a greyed out print button.

The print configurator will report an error reaching cups.

However, cups is working fine.  lpr and other non-GTK
dialog print code will all work.

> ** Changed in: gtk+2.0 (Ubuntu)
>  Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
>Status: Confirmed => Incomplete
> -- 
> evince/evolution/gtk-print-dialog printing and system-config-printer fail 
> when using client.conf with IP address for which there is no reverse look-up 
> available
> https://bugs.launchpad.net/bugs/196429
> You received this bug notification because you are a direct subscriber
> of the bug.
> 
> Status in Source Package "gtk+2.0" in Ubuntu: Incomplete
> Status in Source Package "system-config-printer" in Ubuntu: Confirmed
> 
> Bug description:
> I ran into the 'greyed out print button' in evince in gutsy 7.10.
> 
> I was working with a network printer and it worked via
> lpr and in fact any tool that did not rely on the GTK
> print dialog.
> 
> Evince and evolution were clearly broken.  As was the system
> printer configurator via the menu.  It kept dying after reporting
> an error connecting to cups.
> 
> I could use xpdf instead of evince and print fine.  I could
> also use the GTK dialog to print to a file and then send the
> file to the printer using any non-GTK tool.
> 
> In /etc/cups/client.conf I had put
> 
> ServerName 192.168.1.16
> 
> In the end the problem was that I did not have an entry
> in /etc/hosts for 192.168.1.16.
> 
> If I add an entry like
> 
> 192.168.1.16 printer.mydomain.tld printer
> 
> then everything works well including evince and evolution.
> 
> Without that entry or a similar one in /etc/hosts, all the programs
> that use the GTK print dialog malfunction and the system print
> configurator dies.
>

-- 
evince/evolution/gtk-print-dialog printing and system-config-printer fail when 
using client.conf with IP address for which there is no reverse look-up 
available
https://bugs.launchpad.net/bugs/196429
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs