v12 printer related crashes
With Bricscad v12 the printing subsystem seems to crash Bricscad. On some files the program will just crash instantly when trying to open the file, on others it will crash first when trying to go to the print dialog. Always crashing with a segmentation fault.
I am on Arch Linux, kernel 3.3.3-1, bricscad v12.1.23 pro, amd fx-8150 cpu, amd radeon 6700 gpu, catalyst.
I have the following (possibly related) packages installed:
cups-pdf 2.6.1-1
lib32-libcups 1.5.2-1
catalyst version 12.1
xorg-server 1.11.4-1
I have tried to set cups-pdf as default printer, as well as uninstalling any Microsoft fonts, but without success.
Anyone has similar issues or any suggestions?
Best regards
0
Comments
-
I have the same problem but only with machin run amd64 with GTK3 (Wheezy)
I try Bricscad V12 on machins with GTK2 (ubuntu 10.40 amd64, GPU NVidia and Skeeze amd64, GPU NVidia) and i d'ont have this problem.
Bricscad V11 run correctly with GTK3 and GPU Radeon 6xxx
I think that the problem comes with GTK3 with amd64 or x86 and/or Catalyst (I d'ont make this test with GTK3 on x386 with GPU Radeon or GTK3 with GPU NVidia)
Best Regards0 -
Thank you for the reply.
I never solved my problem with segfaults when entering the print dialog. Ended up installing the, officially supported, ubuntu 12.04 32-bit kernel on my workstation and built a lightweight system from it. (Not very fond of full and heavy gnome/unity environment, the reason why I used Arch Linux) With this setup BricsCAD works like a charm.
/Best regards
0 -
Have the same issue. After send drawing to the printer, the program crash and close itself. Have an gforce card with noveau drivers on 12.04 ubuntu system. Tell me if you need to send some file to the forum to check.0
-
This is what program display when execute it from command line and sent drawing to printer: bricscadv12
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 55
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 56
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 59
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 58
nvfx_screen_get_param:95 - Warning: unknown PIPE_CAP 30
Violación de segmento (`core' generado)
Wish to add a log file, but i can't find it
0 -
It does seem to be related to the video driver. Perhaps you could try installing the proprietary driver, I understand this is easy to do in Ubuntu.
I've been using Bricscad since v.10 and this only happened once with a beta version IINM. All but one of my systems are openSUSE + nvidia driver, except for one machine with ATI fglrx.0 -
Not sure the video drivers are to blame.
On my 32bit debian testing box, bricscad doesn't crash here, but I have to press continue in gdb twice to get the print/layout dialog to open:
[code]Program received signal SIGPIPE, Broken pipe.
0xb7fe2424 in __kernel_vsyscall ()
(gdb) bt
#0 0xb7fe2424 in __kernel_vsyscall ()
#1 0xaeb98fc8 in send () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#2 0xaea43d7e in ?? () from /usr/lib/i386-linux-gnu/libcups.so.2
#3 0xaea44381 in httpFlushWrite () from /usr/lib/i386-linux-gnu/libcups.so.2
#4 0xaea46b78 in ?? () from /usr/lib/i386-linux-gnu/libcups.so.2
#5 0xaea5f65d in cupsSendRequest () from /usr/lib/i386-linux-gnu/libcups.so.2
#6 0xaea60094 in cupsDoIORequest () from /usr/lib/i386-linux-gnu/libcups.so.2
#7 0xaea603fb in cupsDoRequest () from /usr/lib/i386-linux-gnu/libcups.so.2
#8 0xaea3c78b in _cupsGetDests () from /usr/lib/i386-linux-gnu/libcups.so.2
#9 0xaea3d7e5 in cupsGetDests2 () from /usr/lib/i386-linux-gnu/libcups.so.2
#10 0xaea3db53 in cupsGetDests () from /usr/lib/i386-linux-gnu/libcups.so.2
#11 0xb7f9c176 in ut::getSystemPrinters(OdArray >&) () from /opt/bricsys/bricscad/v12/libutils.so
#12 0xb77d3bd0 in ca::PlotterConfigurations::reload() ()
from /opt/bricsys/bricscad/v12/libcadapp.so
#13 0xb77d465e in ca::PlotterConfigurations::PlotterConfigurations() ()
from /opt/bricsys/bricscad/v12/libcadapp.so
#14 0xb6e7cbc8 in cmd_print(ca::CaDoc*) ()
from /opt/bricsys/bricscad/v12/libcommands.so
#15 0xb7680acd in ca::InternalCommand::execute(OdEdCommandContext*) ()
from /opt/bricsys/bricscad/v12/libcadapp.so
#16 0xb52adbe0 in OdEdCommandStackImpl::executeCommand(OdEdCommand*, OdEdCommandContext*) () from /opt/bricsys/bricscad/v12/libTD_Root.so
#17 0xb7677cb3 in ca::CommandProcessor::execCommand(OdEdCommand*, bool&, bool)
() from /opt/bricsys/bricscad/v12/libcadapp.so
#18 0xb767b5db in ca::CommandProcessor::execStr(OdString&, bool, OdEdCommand*, bool, ca::Alias*) () from /opt/bricsys/bricscad/v12/libcadapp.so
#19 0xb767bea0 in ca::CommandProcessor::processString(OdString const&) ()
from /opt/bricsys/bricscad/v12/libcadapp.so
#20 0xb767c12c in ca::CommandProcessor::processNextCmdItem(int) ()
from /opt/bricsys/bricscad/v12/libcadapp.so
#21 0xb767c277 in ca::CommandProcessor::processIdle() ()
from /opt/bricsys/bricscad/v12/libcadapp.so
#22 0xb767c3c0 in ca::CommandProcessor::main() ()
from /opt/bricsys/bricscad/v12/libcadapp.so
#23 0xb767c4b7 in ca::CommandProcessor::start() ()
from /opt/bricsys/bricscad/v12/libcadapp.so
#24 0xb767c615 in ca::CommandProcessor::mainWorkFlowProc(void*) ()
from /opt/bricsys/bricscad/v12/libcadapp.so
#25 0xade76d39 in ?? () from /opt/bricsys/bricscad/v12/libpth.so.20
#26 0xaeb04eeb in makecontext () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#27 0xaeaf6371 in sigemptyset () from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#28 0xaeba4c66 in pthread_mutex_unlock ()
from /lib/i386-linux-gnu/i686/cmov/libc.so.6
#29 0x00000021 in ?? ()
#30 0x08dd4790 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) c
Continuing[/code]
(After pressing c, the same thing repeats)
Guess it is a nightmare for devs to keep up with the steady pace of change in our beloved linux...0
This discussion has been closed.