Hi,
definitely it isn't an iceweasel problem but
some kind of libc. Printing works perfectly
on 32 bit skole WS.
Regards
Giorgio
On Fri, Aug 28, 2015 at 03:03:42PM +0200, Giorgio Pioda wrote:
> Hi,
>
> on Jessie/Skole both Icedove and Iceweasel chrash
> upon printing. Any idea or hint?
>
>
Some news from this front.
Apparently the problem is raised in the KDE display manager
since printing from Gnome3/Iceweasel works.
I've the neat impression that iceweasel tries to open
a popup window for the printing menu and this lead to
the crash.
I'll investigate further. Any idea howto
Hi,
> valgrind iceweasel
Starting iceweasel with valgrind give direcly a crash,
with a lot of errors and at least 2 memory leaks,
no way to reach the printing menu, thus...
Regards
--
Giorgio Pioda - Sysadmin SPSE-Tenero
Cell +41 79 629 20 63
Tel +41 58 468 62 48
Fax +41 58 468 61 98
Here the xsession-errors.log about iceweasel crash in kde
http://pastebin.com/RpfRu0pp
Regards
Giorgio
--
Giorgio Pioda - Sysadmin SPSE-Tenero
Cell +41 79 629 20 63
Tel +41 58 468 62 48
Fax +41 58 468 61 98
On Fri, Aug 28, 2015 at 11:03:37PM +0200, Petter Reinholdtsen wrote:
> [Giorgio Pioda]
> > Nothing improves
> >
> > here gdb output
> >
> > http://pastebin.com/UHzNwiHd
>
> When running gdb like that, try issuing the 'bt' command
here:
http://pastebin.com/19XW8fEv
Regards
--
Giorgio Pioda -
Hi,
on Jessie/Skole both Icedove and Iceweasel chrash
upon printing. Any idea or hint?
Best regards
Giorgio
--
Giorgio Pioda - Sysadmin SPSE-Tenero
Cell +41 79 629 20 63
Tel +41 58 468 62 48
Fax +41 58 468 61 98
On Fri, Aug 28, 2015 at 04:48:53PM +0200, Wolfgang Schweer wrote:
On Fri, Aug 28, 2015 at 04:39:16PM +0200, Giorgio Pioda wrote:
On Fri, Aug 28, 2015 at 04:26:15PM +0200, Wolfgang Schweer wrote:
On Fri, Aug 28, 2015 at 03:03:42PM +0200, Giorgio Pioda wrote:
on Jessie/Skole both
On Fri, Aug 28, 2015 at 03:03:42PM +0200, Giorgio Pioda wrote:
on Jessie/Skole both Icedove and Iceweasel chrash
upon printing. Any idea or hint?
Over here it just works in both cases on a VirtualBox test network with
a printer on the host network configured as a JetDirect printer. So
On Fri, Aug 28, 2015 at 04:26:15PM +0200, Wolfgang Schweer wrote:
On Fri, Aug 28, 2015 at 03:03:42PM +0200, Giorgio Pioda wrote:
on Jessie/Skole both Icedove and Iceweasel chrash
upon printing. Any idea or hint?
Over here it just works in both cases on a VirtualBox test network with
On Fri, Aug 28, 2015 at 04:39:16PM +0200, Giorgio Pioda wrote:
On Fri, Aug 28, 2015 at 04:26:15PM +0200, Wolfgang Schweer wrote:
On Fri, Aug 28, 2015 at 03:03:42PM +0200, Giorgio Pioda wrote:
on Jessie/Skole both Icedove and Iceweasel chrash
upon printing. Any idea or hint?
Over
On Fri, Aug 28, 2015 at 05:24:27PM +0200, Giorgio Pioda wrote:
To setup printing I had to put BrowsePoll=www:631 in
/etc/cups-browsed.conf otherwise the queues on tjener were not
visible.
Please try the printer detection using /etc/cups/client.conf (on the ws)
instead of using
On Fri, Aug 28, 2015 at 06:07:25PM +0200, Wolfgang Schweer wrote:
On Fri, Aug 28, 2015 at 05:24:27PM +0200, Giorgio Pioda wrote:
To setup printing I had to put BrowsePoll=www:631 in
/etc/cups-browsed.conf otherwise the queues on tjener were not
visible.
Please try the printer
[Giorgio Pioda]
Nothing improves
here gdb output
http://pastebin.com/UHzNwiHd
When running gdb like that, try issuing the 'bt' command into gdb to get
a backtrace from the crash location in the program.
Also, try installing valgrind and running the browser using
valgrind iceweasel
to
On Fri, Aug 28, 2015 at 05:14:09PM +0200, Giorgio Pioda wrote:
it looks like bug #709197.
Indeed starting iceweasel in safe-mode during printing crash I get
the following error
GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size ==0' failed
Running 'iceweasel --safe-mode'
14 matches
Mail list logo
