Bug 315487 - Snap on send to. Crash.
Summary: Snap on send to. Crash.
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-20 03:00 UTC by Doug McGarrett
Modified: 2022-01-21 12:58 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 7.6.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Doug McGarrett 2013-02-20 03:00:19 UTC
Summary pretty much says it.  Using PCLOS KDE 2012.12 (32 bit). Kernel; 3.2.18-pclos2.pae.bfs
System:  Foxconn mobo, G41MXE; CPU: Intel Celeron E3400@2.6GHz. Memory: 8GB; Video: GeForce GTX 550 Ti (NVidia).  This mobo is 14 months old, the video card a bit less than a year old.
To reiterate: I snap on KSnapshot, which I have in the panel (systray) and set it for rectangular area. Take new snapshot. Outline the area. Push Enter. Mouse to "Send to" CRASH. Bug report thing comes up. I have installed the backtrace gizmo, but the bugreporter says that the trace is not enough, so here I am. (Tell me how to save the trace and send it to you.)


Reproducible: Always

Steps to Reproduce:
1. Just do like I described.  Yes it happens every time. 
2.
3.
Actual Results:  
Bug report box comes up. Since the bug report screen doesn't like my backtrace, I can't fo any
further.

Expected Results:  
The software should open a menu, which includes "send to printer."  this worked on all previous versions of the distro.  PCLOS is up to date, via Synaptic. Another version of PCLOS on another
computer, which came from an earlier install, but is also up to date, does not crash and works
normally.

I depend on KSnapshot to copy parts of graphical browser files as well as portions of long
threads in the Forum.  This is very important to me.  I don't know of any work-around, even
a clumsy one. It will severely limit my use of pclos on this machine, and I don't know of another
Linux distro that I am as comfortable with, having used PCLOS since 2010, after having 
problems with SuSE, that I used for several years earlier.
Comment 1 Doug McGarrett 2013-02-20 03:08:09 UTC
On 02/19/2013 10:00 PM, Doug McGarrett wrote:
> https://bugs.kde.org/show_bug.cgi?id=315487
>
>              Bug ID: 315487
>             Summary: Launch KSnapshot. Select rectangular region. Outline
>                      region. Push enter. Snap on send to. Crash.
>      Classification: Unclassified
>             Product: ksnapshot
>             Version: 0.8.2
>            Platform: Other
>                  OS: Linux
>              Status: UNCONFIRMED
>            Severity: grave
>            Priority: NOR
>           Component: general
>            Assignee: rich@kde.org
>            Reporter: dmcgarrett@optonline.net
>
> Summary pretty much says it.  Using PCLOS KDE 2012.12 (32 bit). Kernel;
> 3.2.18-pclos2.pae.bfs
> System:  Foxconn mobo, G41MXE; CPU: Intel Celeron E3400@2.6GHz. Memory: 8GB;
> Video: GeForce GTX 550 Ti (NVidia).  This mobo is 14 months old, the video card
> a bit less than a year old.
> To reiterate: I snap on KSnapshot, which I have in the panel (systray) and set
> it for rectangular area. Take new snapshot. Outline the area. Push Enter. Mouse
> to "Send to" CRASH. Bug report thing comes up. I have installed the backtrace
> gizmo, but the bugreporter says that the trace is not enough, so here I am.
> (Tell me how to save the trace and send it to you.)
>
>
> Reproducible: Always
>
> Steps to Reproduce:
> 1. Just do like I described.  Yes it happens every time.
> 2.
> 3.
> Actual Results:
> Bug report box comes up. Since the bug report screen doesn't like my backtrace,
> I can't fo any
> further.
>
> Expected Results:
> The software should open a menu, which includes "send to printer."  this worked
> on all previous versions of the distro.  PCLOS is up to date, via Synaptic.
> Another version of PCLOS on another
> computer, which came from an earlier install, but is also up to date, does not
> crash and works
> normally.
>
> I depend on KSnapshot to copy parts of graphical browser files as well as
> portions of long
> threads in the Forum.  This is very important to me.  I don't know of any
> work-around, even
> a clumsy one. It will severely limit my use of pclos on this machine, and I
> don't know of another
> Linux distro that I am as comfortable with, having used PCLOS since 2010, after
> having
> problems with SuSE, that I used for several years earlier.
>
I don't know if the original of this got to you, so I'm forwarding the 
copy that was (only?) sent to me.
BTW: Workaround is "Save to" and then open file in Gwenview, but the 
copy is not quite as sharp.
Also, have to look for picture. Not satisfactory.
Comment 2 Jekyll Wu 2013-02-20 03:19:05 UTC
You are probably mixing incompatible binaries from different repos.
Comment 3 Doug McGarrett 2013-02-20 03:48:08 UTC
On 02/19/2013 10:19 PM, Jekyll Wu wrote:
> https://bugs.kde.org/show_bug.cgi?id=315487
>
> Jekyll Wu <adaptee@gmail.com> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>            Component|general                     |general
>              Version|0.8.2                       |unspecified
>             Assignee|rich@kde.org                |kde-imaging@kde.org
>              Product|ksnapshot                   |kipiplugins
>
> --- Comment #2 from Jekyll Wu <adaptee@gmail.com> ---
> You are probably mixing incompatible binaries from different repos.
>
I have nluug selected for both the repos, which I believe is the present
recommendation from PCLOS. I have kept abreast of upgrades, and,
in fact, just looked to see if there was another one this afternoon, but
there was not. I don't have any choice as to what files the repos send
me, unless you tell me one specific file, and there is another source for
that one. How do you suggest that I proceed?

--Doug McGarrett
Comment 4 caulier.gilles 2013-02-20 06:02:19 UTC

*** This bug has been marked as a duplicate of bug 306693 ***
Comment 5 caulier.gilles 2022-01-21 12:58:40 UTC
Fixed with https://bugs.kde.org/show_bug.cgi?id=306693