[kmail2] [Bug 324889] attached EPS images cannot be visualized within kmail

2013-09-13 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=324889

--- Comment #2 from jsar...@gmail.com ---
Ok, I see. I guess EPS files, as PDFs are not supported by qt, so they are not
shown up. 

It would be so cool that Kmail could interact with Okular to this respect (so
PDF, EPS, and even ODT files could be shown), but this is a feature request not
a bug.

Thanks for your fast and to the point response!

-- 
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


[kmail2] [Bug 324889] New: attached EPS images cannot be visualized within kmail

2013-09-13 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=324889

Bug ID: 324889
   Summary: attached EPS images cannot be visualized within kmail
Classification: Unclassified
   Product: kmail2
   Version: 4.11.1
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jsar...@gmail.com

I frequently receive e-mails with attached EPS images. I'd like to see them in
the e-mails but instead an icon is shown (with the forbidden symbol), so the
only way to see them is externally in the default EPS-associated application
(Gwenview in my case), by clicking the link or the icon as if one would like to
open the attached file.

Reproducible: Always

-- 
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


[kontact] [Bug 317692] icons on the left cannot be seen entirely on qtcurve style, a scrollbar appears instead

2013-04-01 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=317692

--- Comment #2 from jsar...@gmail.com ---
bug in launchpad:
https://bugs.launchpad.net/ubuntu/+source/kde-style-qtcurve/+bug/1162957

-- 
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


[kontact] [Bug 317692] icons on the left cannot be seen entirely on qtcurve style, a scrollbar appears instead

2013-04-01 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=317692

--- Comment #1 from jsar...@gmail.com ---
Created attachment 78553
  --> https://bugs.kde.org/attachment.cgi?id=78553&action=edit
screenshot

-- 
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


[kontact] [Bug 317692] New: icons on the left cannot be seen entirely on qtcurve style, a scrollbar appears instead

2013-04-01 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=317692

Bug ID: 317692
   Summary: icons on the left cannot be seen entirely on qtcurve
style, a scrollbar appears instead
Classification: Unclassified
   Product: kontact
   Version: 4.10.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jsar...@gmail.com

using oxygen icons appear correctly as usual, but with qtcurve only half of
them appear (left part). I have to maximize and minimize and then box
containing icons properly rescales to the icon size.

Reproducible: Always

Steps to Reproduce:
1. move from oxygen to qtcurve
2. open kontact
3.
Actual Results:  
half of the icons can be seen and a scrollbar appears

Expected Results:  
box should rescale to the icon size as it does in oxygen

there is this other bug I filled that may indicate something is wrong in how
qtcurve and boxes in kde interact:

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

it could be the bug is in qtcurve as well. I'm in the process of filling a bug
in launchpad for the qtcurve package (I actually don't know where upstream
qtcurve resides)

-- 
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


[kmail2] [Bug 313667] New: sent e-mail missing in 'Sent' folder

2013-01-21 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=313667

Bug ID: 313667
   Summary: sent e-mail missing in 'Sent' folder
Classification: Unclassified
   Product: kmail2
   Version: 4.9.98 RC3
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: jsar...@gmail.com

When Kmail quits while composing an e-mail, it nicely reappears next time you
start the application, so you can finish editing and send it. 

However, a copy of it is not saved in the 'Sent' folder (although it's received
by the people you sent it, and confirmed by receiving replies to that e-mail).

Reproducible: Always

Steps to Reproduce:
1. Write a new e-mail
2. Restart Kontact
3. Sent the e-mail
Actual Results:  
It's missing in the 'Sent' folder, so you lose the copy of the e-mail for your
own records

Expected Results:  
It should appear in the 'Sent' folder, as it usually happens when you send any
e-mail

This bug doesn't seem to be universal though, while it always happens with my
university disconnected IMAP account, it doesn't affect my gmail disconnected
IMAP account. I ignore why

-- 
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 312608] New: kmail thread sorting , aggregation - thread leader - most recent message , is not working right

2013-01-04 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=312608

Bug ID: 312608
   Summary: kmail thread sorting , aggregation - thread leader -
most recent message , is not working right
Classification: Unclassified
   Product: kmail2
   Version: 4.9.95 RC1
  Hardware: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-bugs@kde.org
  Reporter: jsar...@gmail.com

I suffer the same issue that was reported before in opensuse:

https://bugzilla.novell.com/show_bug.cgi?id=776519

I guess this should have been submitted to KDE directly:

In kmail, when you select in aggregation if you select most recent message as
thread leader, thread is still sorted from your first (oldest) message to you
last (newest). This only add thread to correct group according to last message
date.

My understanding is that thread in this case, shall be sorted from thread
leader.
For example
my last message - thread leader
 - message before
   - oldest (first) message

Existing behavior is either bug or there is missing option which will force
kmail to sort messages from newest message in thread.

Reproducible: Always

Steps to Reproduce:
1. kmail - configure - appearance - default aggregation - configure - groups &
threading - thread leader - select "most recent message"
2. check your message list (list of your emails)
Actual Results:  
messages in thread sorted from oldest (on top) to newest (on bottom)

Expected Results:  
messages in thread sorted from newest (on top) to oldest (on bottom)

thread is in correct position within another messages (not part of the thread)
(according to date). However, thread itself is sorted from oldest to newest.
What I'll expect is to have (within thread) newest on top.

-- 
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 299482] groupdav calendar sync fails with "unknown error code 0"

2012-05-15 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=299482

jsar...@gmail.com changed:

   What|Removed |Added

 CC||jsar...@gmail.com

--- Comment #12 from jsar...@gmail.com ---
Same here I reverted kdepim-runtime to 4.8.2a in kubuntu 12.04 and it got
fixed. I also filled a bug in launchpad about this bug:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/998179

I know that this doesn't bring much information but I didn't find a good (and
easy) way of following comments on this bug, other than commenting. It would be
great if there were a button of "follow me" in bugs.kde.org

I wonder if I should fill a bug for that...

-- 
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 288040] kmail2 fails to remove duplicate mails from folder

2012-01-18 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=288040





--- Comment #6 from2012-01-18 19:31:48 ---
I'm willing to collaborate to fix this issue from a user perspective if this
would help...

-- 
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 271660] "Remove duplicate Mails" doesn't work

2012-01-16 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=271660


jsar...@gmail.com changed:

   What|Removed |Added

 CC||jsar...@gmail.com




--- Comment #6 from2012-01-17 03:45:43 ---
I can confirm this bug in kde 4.8 rc2 (kubuntu 11.10)

-- 
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 288040] kmail2 fails to remove duplicate mails from folder

2012-01-16 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=288040


jsar...@gmail.com changed:

   What|Removed |Added

 CC||jsar...@gmail.com




--- Comment #5 from2012-01-17 03:44:53 ---
I'm suffering the same issues

-- 
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 259949] Kmail does not use all addressbooks for autocompletion

2012-01-09 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=259949


jsar...@gmail.com changed:

   What|Removed |Added

 CC||jsar...@gmail.com




--- Comment #47 from2012-01-09 16:14:53 ---
Same behavior here. I hope it is fixed soon :)

-- 
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 232121] Message marked as unread using dIMAP

2011-04-12 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=232121





--- Comment #3 from2011-04-13 03:39:41 ---
I just want to say that bug https://bugs.kde.org/show_bug.cgi?id=169177 is NOT
resolved. The thing is that this ONLY happens for GMAIL accounts, and I guess
Ruchir Brahmbhatt tried with other accounts.

-- 
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 169177] dIMAP: Moving a mail from one folder to another will set this mail's status to "unread"

2011-04-12 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=169177





--- Comment #3 from2011-04-13 03:33:45 ---
this bug is not resolved, there is more people suffering it:
https://bugs.kde.org/show_bug.cgi?id=232121

it may be related to how kmail manages gmail imap, as I could not see a similar
bug in, for instance, thunderbird

-- 
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 232121] Message marked as unread using dIMAP

2011-04-12 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=232121


jsar...@gmail.com changed:

   What|Removed |Added

 CC||jsar...@gmail.com




--- Comment #2 from2011-04-13 03:23:06 ---
same here, this is duplicate from this other bug:
https://bugs.kde.org/show_bug.cgi?id=169177

-- 
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 169177] dIMAP: Moving a mail from one folder to another will set this mail's status to "unread"

2011-04-12 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=169177


jsar...@gmail.com changed:

   What|Removed |Added

 CC||jsar...@gmail.com




--- Comment #2 from2011-04-13 01:55:53 ---
I'm suffering exactly the same thing, but only in gmail not in another
disconnected imap account. So it could be something related to the way gmail
moves e-mails between folders (or add tags to them)

-- 
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 257585] Kontact crashes on start

2011-04-08 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=257585





--- Comment #10 from2011-04-09 01:24:06 ---
I tried Kontact after my upgrade to Natty and I can confirm that bug
https://bugs.kde.org/show_bug.cgi?id=267717 is fixed. I guess these other
issues are also fixed although I didn't have them before...

-- 
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 257585] Kontact crashes on start

2011-03-15 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=257585





--- Comment #8 from2011-03-16 02:04:30 ---
In my case kontact crashes when using oxygen-transparent. At least in my case I
think it is related to the way kontact (maybe only in kubuntu, not sure)
manages transparency because I can use oxygen-transparent if I set the
configuration to completely opaque

-- 
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 267717] New: kontact crashes on startup when using oxygen-transparent

2011-03-05 Thread jsardid
https://bugs.kde.org/show_bug.cgi?id=267717

   Summary: kontact crashes on startup when using
oxygen-transparent
   Product: kontact
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: jsar...@gmail.com


Application: kontact (4.4.9)
KDE Platform Version: 4.6.1 (4.6.1)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-27-generic-phc x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
- What I was doing when the application crashed:

I had previously installed  and configured oxygen-transparent, then when I
start kontact it always crashes. If I change to oxygen, crashes disappear.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#6  QList (this=0x7faa60aa27c0) at
../../include/QtCore/../../src/corelib/tools/qlist.h:118
#7  QWidget::actions (this=0x7faa60aa27c0) at kernel/qwidget.cpp:3181
#8  0x7faa6182872e in DBusMenuExporterDBus::GetChildren (this=0x139dce0,
parentId=, names=) at
../3rdparty/dbusmenu-qt/src/dbusmenuexporterdbus_p.cpp:53
#9  0x7faa6183bc9a in DBusMenuExporterDBus::qt_metacall (this=0x139dce0,
_c=, _id=, _a=0x7fff310d1640) at
.moc/release-shared/moc_dbusmenuexporterdbus_p.cpp:106
#10 0x7faa5e8010ee in QDBusConnectionPrivate::deliverCall (this=, object=, msg=,
metaTypes=..., slotIdx=) at qdbusintegrator.cpp:919
#11 0x7faa5e8023cb in QDBusConnectionPrivate::activateCall (this=, object=0x139dce0, flags=4080, msg=...) at
qdbusintegrator.cpp:829
#12 0x7faa5e802bae in QDBusConnectionPrivate::activateObject (this=, node=, msg=..., pathStartPos=) at qdbusintegrator.cpp:1399
#13 0x7faa5e803108 in QDBusActivateObjectEvent::placeMetaCall
(this=0x1faab70) at qdbusintegrator.cpp:1493
#14 0x7faa60782bde in QObject::event (this=0x139dce0, e=0x7fff310d1330) at
kernel/qobject.cpp:1219
#15 0x7faa61153fdc in QApplicationPrivate::notify_helper (this=0xe77c80,
receiver=0x139dce0, e=0x1faab70) at kernel/qapplication.cpp:4396
#16 0x7faa61159aed in QApplication::notify (this=0x7fff310d23c0,
receiver=0x139dce0, e=0x1faab70) at kernel/qapplication.cpp:4277
#17 0x7faa61ee42c6 in KApplication::notify (this=0x7fff310d23c0,
receiver=0x139dce0, event=0x1faab70) at ../../kdeui/kernel/kapplication.cpp:311
#18 0x7faa60770cdc in QCoreApplication::notifyInternal
(this=0x7fff310d23c0, receiver=0x139dce0, event=0x1faab70) at
kernel/qcoreapplication.cpp:732
#19 0x7faa60773c22 in sendEvent (receiver=0x0, event_type=, data=0xe45380) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=, data=0xe45380) at kernel/qcoreapplication.cpp:1373
#21 0x7faa6079d653 in sendPostedEvents (s=0xe80dc0) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#22 postEventSourceDispatch (s=0xe80dc0) at
kernel/qeventdispatcher_glib.cpp:277
#23 0x7faa596cf342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x7faa596d32a8 in ?? () from /lib/libglib-2.0.so.0
#25 0x7faa596d345c in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#26 0x7faa6079d193 in QEventDispatcherGlib::processEvents (this=0xe44e90,
flags=) at kernel/qeventdispatcher_glib.cpp:415
#27 0x7faa61206a4e in QGuiEventDispatcherGlib::processEvents
(this=0x7fff310d1330, flags=) at
kernel/qguieventdispatcher_glib.cpp:204
#28 0x7faa6076fa02 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149
#29 0x7faa6076fdec in QEventLoop::exec (this=0x7fff310d2300, flags=) at
kernel/qeventloop.cpp:201
#30 0x7faa60773ebb in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:1009
#31 0x00403b4e in main (argc=, argv=) at ../../../kontact/src/main.cpp:224

This bug may be a duplicate of or related to bug 257585.

Possible duplicates by query: bug 257585.

Reported using DrKonqi

-- 
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