[kaddressbook] [Bug 290249] address label printing on sticky labels

[Simon Oosthoek]

https://bugs.kde.org/show_bug.cgi?id=290249

--- Comment #2 from Simon Oosthoek  ---
> --- Comment #1 from Laurent Montel  ---
> Do you have screenshot that you want that we implement ?
> 

It's been a while since I reported this, I'd have to dig into it again
and at this time I don't have a very high priority to do so (3 children
to take care of as well ;-)

I think it would be a natural addition to an address database tool to be
able to print them onto labels, as that's one of the most useful places
for adresses to be printed on (apart from mail-merge letters and such).

Cheers

Simon

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 290249] New: address label printing on sticky labels

[Simon Oosthoek]

https://bugs.kde.org/show_bug.cgi?id=290249

   Summary: address label printing on sticky labels
   Product: kaddressbook
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: printing
AssignedTo: kdepim-bugs@kde.org
ReportedBy: s.oosth...@xs4all.nl
CC: to...@kde.org


Version:   unspecified (using KDE 4.7.3) 
OS:Linux

In all the time I've used Linux on the desktop (since 1996) I've sometimes
tried to print labels from a linux program and particularly from the
kaddressbook database of addresses, but it's always (on the rare occasions I
need it) so hard to do it becomes an obstacle and the temptation to use a paper
addressbook comes up again. Mostly I have experience with kbarcode to do this,
but it's a horror to use!

Reproducible: Didn't try



Expected Results:  
I would like kaddressbook (because that's where I keep my addresses) to have an
option to print addresses on labels. Apparently this is a feature that is
either hard to implement or no developer has ever stumbled upon the need to get
this done properly ;-)

There are a couple of steps I'd expect:
- selecting which addresses to print
- a way to select which fields to print and approximately where on the label
(order and row in printed form)
- a way to describe the layout of the label paper (nr of rows/columns and
offsets) (I don't believe in kbarcode's method of choosing from a huge set of
predifined label sheets/brands)
- perhaps font settings
- Optionally repeating one address many times or each address once.


I can imagine several ways to implement this, one is to include it into
kaddressbook's print feature.

Another is to create a separate module for kde/qt to print on labels and
kaddressbook to interface with this. This should make it easier to create other
programs to print stuff on labels, but perhaps more work?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 287305] akregator crashes when browsing a review from tweakers.net

[Simon Oosthoek]

https://bugs.kde.org/show_bug.cgi?id=287305





--- Comment #1 from Simon Oosthoek   2011-11-23 10:46:33 
---
BTW, the full URL was

http://tweakers.net/nieuws/78267/nvidia-toont-android-ice-cream-sandwich-op-transformer-prime.html

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs

[Bug 287305] New: akregator crashes when browsing a review from tweakers.net

[Simon Oosthoek]

https://bugs.kde.org/show_bug.cgi?id=287305

   Summary: akregator crashes when browsing a review from
tweakers.net
   Product: akregator
   Version: 4.7.2
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: s.oosth...@xs4all.nl


Application: akregator (4.7.2)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-13-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:
I was viewing a new item (a review on tweakers.net) and akregator segfaulted on
me, twice!

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f7c298407a0 (LWP 2884))]

Thread 4 (Thread 0x7f7bfbd49700 (LWP 2899)):
#0  0x7f7c215d0e39 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f7c215d1dfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f7c215d2792 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7bff1559cb in ?? () from /usr/lib/gio/modules/libdconfsettings.so
#4  0x7f7c215f72b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f7c21aa3efc in start_thread (arg=0x7f7bfbd49700) at
pthread_create.c:304
#6  0x7f7c263f589d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x in ?? ()

Thread 3 (Thread 0x7f7bfed37700 (LWP 2901)):
#0  __pthread_mutex_unlock_usercnt (mutex=, decr=) at pthread_mutex_unlock.c:52
#1  __pthread_mutex_unlock (mutex=0x44a7248) at pthread_mutex_unlock.c:290
#2  0x7f7c215d1d79 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f7c215d2792 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f7bffc9b516 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5  0x7f7c215f72b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f7c21aa3efc in start_thread (arg=0x7f7bfed37700) at
pthread_create.c:304
#7  0x7f7c263f589d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8  0x in ?? ()

Thread 2 (Thread 0x7f7bfd480700 (LWP 2928)):
#0  0xff60017b in ?? ()
#1  0x7f7bfd47fad0 in ?? ()
#2  0x7fff351ff7e7 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7f7c298407a0 (LWP 2884)):
[KCrash Handler]
#6  0x7f7c23b7e392 in khtml::RenderMedia::eventFilter (this=0x3f9eb48,
o=0x7f7bf4107d00, e=0x7fff35114e80) at
../../khtml/rendering/render_media.cpp:81
#7  0x7f7c26fb5c88 in
QCoreApplicationPrivate::sendThroughObjectEventFilters (this=,
receiver=0x7f7bf4107d00, event=0x7fff35114e80) at
kernel/qcoreapplication.cpp:902
#8  0x7f7c279b63ef in notify_helper (e=0x7fff35114e80,
receiver=0x7f7bf4107d00, this=0x1101f40) at kernel/qapplication.cpp:4482
#9  QApplicationPrivate::notify_helper (this=0x1101f40,
receiver=0x7f7bf4107d00, e=0x7fff35114e80) at kernel/qapplication.cpp:4458
#10 0x7f7c279bb291 in QApplication::notify (this=0x7fff35115840,
receiver=0x7f7bf4107d00, e=0x7fff35114e80) at kernel/qapplication.cpp:4365
#11 0x7f7c286ca126 in KApplication::notify (this=0x7fff35115840,
receiver=0x7f7bf4107d00, event=0x7fff35114e80) at
../../kdeui/kernel/kapplication.cpp:311
#12 0x7f7c26fb5afc in QCoreApplication::notifyInternal
(this=0x7fff35115840, receiver=0x7f7bf4107d00, event=0x7fff35114e80) at
kernel/qcoreapplication.cpp:787
#13 0x7f7c279b6cab in sendEvent (event=0x7fff35114e80, receiver=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#14 QApplicationPrivate::dispatchEnterLeave (enter=0x7f7bf4107d00,
leave=) at kernel/qapplication.cpp:2810
#15 0x7f7c27a3587b in QApplication::x11ProcessEvent (this=0x7fff35115840,
event=0x7fff35115420) at kernel/qapplication_x11.cpp:3686
#16 0x7f7c27a5e412 in x11EventSourceDispatch (s=0x110aa10, callback=0,
user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#17 0x7f7c215d1a5d in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x7f7c215d2258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x7f7c215d2429 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x7f7c26fe0ed6 in QEventDispatcherGlib::processEvents (this=0x10d0170,
flags=) at kernel/qeventdispatcher_glib.cpp:422
#21 0x7f7c27a5e07e in QGuiEventDispatcherGlib::processEvents
(this=, flags=) at
kernel/qguieventdispatcher_glib.cpp:204
#22 0x7f7c26fb4cf2 in QEventLoop::processEvents (this=,
flags=...) at kernel/qeventloop.cpp:149
#23 0x7f7c26fb4ef7 in QEventLoop::exec (this=0x7fff351157f0, flags=...) at
kernel/qeventloop.cpp:201
#24 0x7f7c26fb9789 in QCoreApplication::exec () at
kernel/qcoreappli