[kmail2] [Bug 466124] kmail preview pane empty on wayland nvidia

[Max Schwarz]

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

Max Schwarz  changed:

   What|Removed |Added

 CC||max.schw...@online.de

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 452507] Item details no longer shown in sidebar

[Max]

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

Max  changed:

   What|Removed |Added

 CC||maksv...@ya.ru

--- Comment #1 from Max  ---
I confirm one
korganizer 5.20.0 (22.04.0)
Operating System: Gentoo
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.15.32 (64-bit)
Graphics Platform: X11

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 441846] Tags duplicated with copy an event

[Max]

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

--- Comment #11 from Max  ---
(In reply to gjditchfield from comment #6)
> 
> This patch creates PLAIN tags, merges them with existing tags, and
> does not dirty the editor.
> 
> M  +11   -5src/incidencecategories.cpp
> 
> https://invent.kde.org/pim/incidenceeditor/commit/
> 5bf2e967dcd709658a2fae58cfaecb5a04693b2f

Today I've updated Akonadi to 20.8.2 and Korganizer to 15.18.2. It looks like
all works as expected. Thank you very much.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 441846] Tags duplicated with copy an event

[Max]

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

--- Comment #10 from Max  ---
Korganizer is my main planner app.
With Manjaro updated up to KO 5.18.1 and kde-frameworks 5.86 the duplication
appears on opening any events details dialog. 

The screenshots demonstrate changing of tag editor state after cold start and
opening event dialog

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 441846] Tags duplicated with copy an event

[Max]

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

--- Comment #9 from Max  ---
Created attachment 142109
  --> https://bugs.kde.org/attachment.cgi?id=142109=edit
Tag Editor state after open an event dialog

Tag Editor state after open an event dialog

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 441846] Tags duplicated with copy an event

[Max]

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

--- Comment #8 from Max  ---
Created attachment 142108
  --> https://bugs.kde.org/attachment.cgi?id=142108=edit
Tag Editor state after cold start

Tag Editor state after cold start

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 441846] Tags duplicated with copy an event

[Max]

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

--- Comment #7 from Max  ---
Created attachment 142107
  --> https://bugs.kde.org/attachment.cgi?id=142107=edit
KO state after cold start

KO state after cold start

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 441846] Tags duplicated with copy an event

[Max]

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

--- Comment #2 from Max  ---
In due rolling down to KO 5.17.3 now I can't test KO 5.18.1

With tag "05-АДМ" it gave up to 5 duplicated tags (dup tag) in Tag Editor
The  "02-ГРЖ" tag generated one dup tag
Perhaps it's depended on locale (used ru_RU)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 441846] New: Tags duplicated with copy an event

[Max]

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

Bug ID: 441846
   Summary: Tags duplicated with copy an event
   Product: korganizer
   Version: 5.18.1
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: agendaview (weekview)
  Assignee: kdepim-bugs@kde.org
  Reporter: maksv...@ya.ru
  Target Milestone: ---

SUMMARY
Duplicated tags appear in Tag Editor after I've copied and pasted an event with
assigned tag.

After that events with duplicated tag don't colored with tag's color in agenda
view. Them colored with calendar color

STEPS TO REPRODUCE
1. Check only one tag in Tag Manager (ex. "01")
2. Create event
3. Assign tag "01" to the event
4. Copy event with tag and past one in calendar
5. Check Tag Manager. There should be two tags "01"

OBSERVED RESULT


EXPECTED RESULT
Only one tag after copy event

SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
KDE Grear: 21.08.0
Kernel Version: 5.10.60-gentoo-dist (64-bit)
Graphics Platform: X11

Korganizer: 5.18

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 429344] All Mail Accounts (on KMail) crashed after latest updates

[Max Schwarz]

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

--- Comment #6 from Max Schwarz  ---
Created attachment 133727
  --> https://bugs.kde.org/attachment.cgi?id=133727=edit
another backtrace

Running on KDE Neon Testing (20.04).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 429344] All Mail Accounts (on KMail) crashed after latest updates

[Max Schwarz]

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

Max Schwarz  changed:

   What|Removed |Added

 CC||m...@x-quadraht.de

--- Comment #5 from Max Schwarz  ---
I think I have the same problem, akonadi_imap_resource keeps crashing with
"stack smashing detected". My backtrace looks very similar, I'll try to attach
it. Why do you suspect MySQL?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 412751] Invalid RRULE in Timezone Component with libical 3.0.6

[Max]

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

--- Comment #16 from Max  ---
(In reply to Allen Winter from comment #15)
> I tried:
>  * setting my system timezone to Europe/Berlin 
>  * creating the incidence using Europe/Berlin timezones on the dates
> 
> neither helped.  I still cannot see a calendar with vtimezones and rrules
> 
> maybe another timezone ? what timezones are you guys using?

My timezone is Asia/Irkutsk.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 412751] Invalid RRULE in Timezone Component with libical 3.0.6

[Max]

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

--- Comment #14 from Max  ---
I think this one isn't related to caldav. I don't use caldav, but set timezone.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 412751] Invalid RRULE in Timezone Component

[Max]

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

--- Comment #6 from Max  ---
I've found in my .ics files this "RRULE:ERROR: No Value"string too
Kernel: 5.2.17-gentoo x86_64
kde-apps/korganizer-19.08.2
kde-apps/akonadi-calendar-19.08.2
kde-frameworks/kcalendarcore-5.63.0

I added file with error string "RRULE:ERROR: No Value"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 412751] Invalid RRULE in Timezone Component

[Max]

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

Max  changed:

   What|Removed |Added

 CC||maksv...@ya.ru

--- Comment #5 from Max  ---
Created attachment 123331
  --> https://bugs.kde.org/attachment.cgi?id=123331=edit
file with error string "RRULE:ERROR: No Value"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 396339] [Kmail] Main and status toolbars options not remembered

[Max]

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

--- Comment #3 from Max  ---
sorry i meant KMainWindow not QMainWindow

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 396339] [Kmail] Main and status toolbars options not remembered

[Max]

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

Max  changed:

   What|Removed |Added

 Resolution|DUPLICATE   |---
 Ever confirmed|0   |1
 CC||max...@smoothware.net
 Status|RESOLVED|REOPENED

--- Comment #2 from Max  ---
KMail does saveMainWindowSettings() from mainwindow destructor:
https://cgit.kde.org/kmail.git/tree/src/kmmainwin.cpp#n99

That code should probably be moved to QMainWindow::closeEvent()

void KMMainWin::closeEvent(QCloseEvent *event)
{
QMainWindow::closeEvent(event);
if(event->isAccepted()) {
... saveMainWindowSettings() ...
}
}

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 374780] Huge memory usage just for the calendar with korgac and ical resource

[Max]

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

--- Comment #9 from Max <maksv...@ya.ru> ---
With kde-apps/korganizer-18.04.0 kde-apps/akonadi-18.04.0 my calendars shrink
from 6MB to 433KB and 1.3MB to 73 KB.
I think issue has been solved.
Thank developers so much

P.S. Kde-apps 18.04.0, kde-frameworks 5.45, gentoo

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Akonadi] [Bug 389670] New: CalDav crash when deleting altered instance of recurring event

[Max Pixel]

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

Bug ID: 389670
   Summary: CalDav crash when deleting altered instance of
recurring event
   Product: Akonadi
   Version: 5.5.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: k...@m-pixel.com
  Target Milestone: ---

Application: akonadi_davgroupware_resource (5.5.2)

Qt Version: 5.6.2
Frameworks Version: 5.32.0
Operating System: Linux 4.4.112-2.gaf1ac1a-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
- What I was doing when the application crashed:
1. I added a new CalDAV account (Fastmail to be exact)
2. I explored the interface, and added a journal entry to see how that worked
3. I assigned colors to a few of the calendars
4. I selected an event from the Week view; this event was an instance of a
recurring series, one which I had modified to be on a Wednesday at 10am instead
of the usual Tuesday at 9am
5. I pressed the delete key. A confirmation dialog appeared, asking if I was
sure that I wanted to delete the event. I thought it was strange that it didn't
ask me if I wanted to delete the whole series, or just the one occurrence, but
I went ahead and allowed it.

- Unusual behavior I noticed:
Immediately after confirming the deletion, a notification appeared regarding a
CalDAV related service crashing. Then, the event reappeared as its typical
Tuesday @ 9am.

-- Backtrace:
Application: DAV groupware resource (akonadi_davgroupware_resource), signal:
Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f22ba9e7940 (LWP 21634))]

Thread 4 (Thread 0x7f2289d6e700 (LWP 21640)):
#0  0x7f22b53993fd in read () at /lib64/libc.so.6
#1  0x7f22aecb7750 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f22aec76e49 in g_main_context_check () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f22aec772a8 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7f22aec7742c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#5  0x7f22b5ebf1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#6  0x7f22b5e6cbfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#7  0x7f22b5ca7f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#8  0x7f22b5caca29 in  () at /usr/lib64/libQt5Core.so.5
#9  0x7f22af194724 in start_thread () at /lib64/libpthread.so.0
#10 0x7f22b53a5c1d in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7f228a56f700 (LWP 21637)):
#0  0x7f22b539d37d in poll () at /lib64/libc.so.6
#1  0x7f22aec77314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f22aec7742c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f22b5ebf1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f22b5e6cbfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f22b5ca7f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f22b5caca29 in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f22af194724 in start_thread () at /lib64/libpthread.so.0
#8  0x7f22b53a5c1d in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7f228ad70700 (LWP 21636)):
#0  0x7f22b539d37d in poll () at /lib64/libc.so.6
#1  0x7f22aec77314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f22aec7742c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f22b5ebf1ab in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f22b5e6cbfb in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f22b5ca7f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f22b6ef3295 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x7f22b5caca29 in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f22af194724 in start_thread () at /lib64/libpthread.so.0
#9  0x7f22b53a5c1d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f22ba9e7940 (LWP 21634)):
[KCrash Handler]
#6  0x7f22ba108c01 in  () at /usr/lib64/libKPimKDAV.so.5
#7  0x7f22ba1105f9 in KDAV::EtagCache::removeEtag(QString const&) () at
/usr/lib64/libKPimKDAV.so.5
#8  0x0044e2f9 in  ()
#9  0x7f22b5e98de3 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#10 0x7f22b6c85cf2 in KJob::result(KJob*, KJob::QPrivateSignal) () at
/usr/lib64/libKF5CoreAddons.so.5
#11 0x7f22b6c86a1f in KJob::finishJob(bool) () at
/usr/lib64/libKF5CoreAddons.so.5
#12 0x7f22ba102382 in KDAV::DavItemModifyJob::itemRefreshed(KJob*) () at
/usr/lib64/libKPimKDAV.so.5
#13 0x7f22b5e98de3 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5
#14 0x7f22b6c85cf2 in KJob::result(KJob*, KJob::QPrivateSignal) () at

[korganizer] [Bug 389365] New: KOrganizer Crashed When Trying to Open .ics File

[Max]

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

Bug ID: 389365
   Summary: KOrganizer Crashed When Trying to Open .ics File
   Product: korganizer
   Version: 5.7.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: maxy_da...@lycos.com
  Target Milestone: ---

Application: korganizer (5.7.0)

Qt Version: 5.9.2
Frameworks Version: 5.42.0
Operating System: Linux 4.14.13-300.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

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

I downloaded an .ics file with Firefox, and tried to open it with KOrganizer.
It immediately crashed.

-- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7e2cd7f940 (LWP 20077))]

Thread 5 (Thread 0x7f7dfd333700 (LWP 20083)):
#0  0x7f7e236da36b in poll () from /lib64/libc.so.6
#1  0x7f7e18c0eed9 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f7e18c0efec in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f7e2454535b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f7e244f30ea in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f7e243448ba in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f7e24348b92 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f7e1dd8761b in start_thread () from /lib64/libpthread.so.0
#8  0x7f7e236e691f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f7dfdb34700 (LWP 20080)):
#0  0x7f7e236f5c01 in clock_gettime () from /lib64/libc.so.6
#1  0x7f7e24544bd1 in qt_gettime() () from /lib64/libQt5Core.so.5
#2  0x7f7e24543719 in QTimerInfoList::updateCurrentTime() () from
/lib64/libQt5Core.so.5
#3  0x7f7e24543b15 in QTimerInfoList::timerWait(timespec&) () from
/lib64/libQt5Core.so.5
#4  0x7f7e2454503c in timerSourcePrepareHelper(GTimerSource*, int*) () from
/lib64/libQt5Core.so.5
#5  0x7f7e245450de in timerSourcePrepare(_GSource*, int*) () from
/lib64/libQt5Core.so.5
#6  0x7f7e18c0e439 in g_main_context_prepare () from
/lib64/libglib-2.0.so.0
#7  0x7f7e18c0ee0b in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#8  0x7f7e18c0efec in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#9  0x7f7e2454535b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#10 0x7f7e244f30ea in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#11 0x7f7e243448ba in QThread::exec() () from /lib64/libQt5Core.so.5
#12 0x7f7e24348b92 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#13 0x7f7e1dd8761b in start_thread () from /lib64/libpthread.so.0
#14 0x7f7e236e691f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f7dfed45700 (LWP 20079)):
#0  0x7f7e18c54419 in g_mutex_lock () from /lib64/libglib-2.0.so.0
#1  0x7f7e18c0efd8 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#2  0x7f7e2454535b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7f7e244f30ea in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#4  0x7f7e243448ba in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x7f7e25d46479 in QDBusConnectionManager::run() () from
/lib64/libQt5DBus.so.5
#6  0x7f7e24348b92 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f7e1dd8761b in start_thread () from /lib64/libpthread.so.0
#8  0x7f7e236e691f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f7e05c77700 (LWP 20078)):
#0  0x7f7e236da36b in poll () from /lib64/libc.so.6
#1  0x7f7e1c356fe7 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x7f7e1c358dda in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x7f7e07dd9a49 in QXcbEventReader::run() () from
/lib64/libQt5XcbQpa.so.5
#4  0x7f7e24348b92 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#5  0x7f7e1dd8761b in start_thread () from /lib64/libpthread.so.0
#6  0x7f7e236e691f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f7e2cd7f940 (LWP 20077)):
[KCrash Handler]
#6  0x7f7e2b8d9ef5 in
EventViews::AgendaView::placeDecorations(QList&,
QDate const&, QWidget*, bool) () from /lib64/libKF5EventViews.so.5
#7  0x7f7e2b8de2ab in EventViews::AgendaView::createDayLabels(bool) () from
/lib64/libKF5EventViews.so.5
#8  0x7f7e2b8def50 in EventViews::AgendaView::init(QDate const&, QDate
const&) () from /lib64/libKF5EventViews.so.5
#9  0x7f7e2b8df383 in
EventViews::AgendaView::AgendaView(QSharedPointer const&,
QDate const&, QDate const&, bool, bool, QWidget*) 

[korganizer] [Bug 374780] Huge memory usage just for the calendar with korgac and ical resource

[Max]

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

--- Comment #7 from Max <maksv...@ya.ru> ---
Gentoo. Korganizer ver 5.7.1, KDE Frameworks 5.42.0, Qt 5.9.3

I think my problem gained by same issue
I noticed my calendar on 1050 events got 6.5Mb when was added to korganizer
5.7.1
The ics file was filled with "RDATE;VALUE=DATE-TIME:" entries.
Earch event had timezone differed from UTC.
I deleted all akonadi files and configs, cleaned up the ics-file. One was
filled up again.
When I tried to add a calendar with UTC timezone events. The size of ics file
wasn't changed.
Now I looking up for a workaround this issue
I added sample files with UTC and non UTC timezone

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 374780] Huge memory usage just for the calendar with korgac and ical resource

[Max]

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

--- Comment #6 from Max <maksv...@ya.ru> ---
Created attachment 110084
  --> https://bugs.kde.org/attachment.cgi?id=110084=edit
non UTC ics file

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 374780] Huge memory usage just for the calendar with korgac and ical resource

[Max]

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

--- Comment #5 from Max <maksv...@ya.ru> ---
Created attachment 110083
  --> https://bugs.kde.org/attachment.cgi?id=110083=edit
UTC ics file

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 374780] Huge memory usage just for the calendar with korgac and ical resource

[Max]

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

--- Comment #4 from Max <maksv...@ya.ru> ---
Created attachment 110082
  --> https://bugs.kde.org/attachment.cgi?id=110082=edit
start ics file

-- 
You are receiving this mail because:
You are the assignee for the bug.

[korganizer] [Bug 374780] Huge memory usage just for the calendar with korgac and ical resource

[Max]

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

Max <maksv...@ya.ru> changed:

   What|Removed |Added

 CC||maksv...@ya.ru

--- Comment #3 from Max <maksv...@ya.ru> ---
I think my problem gained by same issue
I noticed my calendar on 1050 events got 6.5Mb when was added to korganizer 5.7
Earch event had timezone deferred

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 356879] New: "MD5 checksum MISMATCH!" error message

[Max Sydorenko via KDE Bugzilla]

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

Bug ID: 356879
   Summary: "MD5 checksum MISMATCH!" error message
   Product: akregator
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: maxim.starga...@gmail.com

Akregator version 15.08.3
Akregator floods logs while apdating feeds  with messages like this:

гру 18 18:36:59 SLE akregator[30986]: log_akregator: Couldn't reach favicon
service. Request favicon for  QUrl("http://feeds.feedburner.com/;)  failed
гру 18 18:36:59 SLE kdeinit5[21531]: MD5 checksum MISMATCH! Expected:
"UJIc8xLbf88hRmrq2RoyPw==" , Got: "UJIc8xLbf88hRmrq2RoyPw"
гру 18 18:36:59 SLE kdeinit5[30659]: kf5.kded: could not find kded module with
id "favicons"
гру 18 18:36:59 SLE kdeinit5[30659]: kf5.kded: attempted to load an invalid
module.
гру 18 18:36:59 SLE kdeinit5[30659]: kf5.kded: Failed to load module for 
"favicons"
гру 18 18:36:59 SLE kdeinit5[30659]: kf5.kded: could not find kded module with
id "favicons"
гру 18 18:36:59 SLE kdeinit5[30659]: kf5.kded: attempted to load an invalid
module.
гру 18 18:36:59 SLE kdeinit5[30659]: kf5.kded: Failed to load module for 
"favicons"


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

[kdepim] [Bug 349353] error building kdepim (KF5 port) with undefined reference to PimCommon::SyntaxHighlighterBase

[Max Sydorenko]

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

--- Comment #7 from Max Sydorenko maxim.starga...@gmail.com ---
Unfortunately I still can not build kdepim, I uninstalled old kdepim, built all
kdepim requirements from git and still getting 
/usr/bin/ld: warning: libmailcommon.so.5, needed by
../calendarsupport/libcalendarsupportcollectionpage.so.4.80.0, not found
and subsequent errors in libcalendarsupportcollectionpage.so

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

[akregator] [Bug 193780] Closing akregator causes crash (incl. Kontact-with-akregator)

[Max Sydorenko]

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

Max Sydorenko maxim.starga...@gmail.com changed:

   What|Removed |Added

 CC||maxim.starga...@gmail.com

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

[Akonadi] [Bug 334480] marking tasks as complete is not synced to google tasks

[Max]

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

Max ma...@mail15.com changed:

   What|Removed |Added

 CC||ma...@mail15.com

--- Comment #2 from Max ma...@mail15.com ---
I have the same problem every time.
After sync task marked as uncomplited again.

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

[kleopatra] [Bug 316353] New: kleopatra (and kmail) create empty signatures if the private key is stored on a gnupg smartcard

[Max Resch]

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

Bug ID: 316353
   Summary: kleopatra (and kmail) create empty signatures if the
private key is stored on a gnupg smartcard
Classification: Unclassified
   Product: kleopatra
   Version: 2.1.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: resch@gmail.com
CC: m...@kde.org

kleopatra creates empty detached signature files, although the correct key is
selected in the sign-wizard, and the wizard returns successfully. The private
signing key is stored on a gnupg smartcard.

A look into the gpg-agent log reviles that kleopatra communicates successfully
with gpg-agent (the pin entry and everything works) but in the end the wrong
key for signing is requested (gpg card hold a signing and an authentication key
and the requested key is for some reason the authentication key)

If you use the gpg commandline tool the same happens unless you use the
--local-user switch or a key with an exclamation mark in the end.

Probably for the same reason kmail is not able to create a signature (the
signature part of the email empty)

Reproducible: Always

Steps to Reproduce:
1. Insert the smartcard
2. Select file - sign
3. Use the wizard, it runs correctly but the detached signature file is empty
(0 Bytes)
Actual Results:  
An empty (0 Byte) file is created instead of the expected gnupg detached
signature file.

Expected Results:  
I expected a detached signature file to be created:
As if I had run
$ gpg -s -d -u key-id! file

If this is a gnupg configuration error on my side it would be nice if the
signing process fails.

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

[kleopatra] [Bug 316353] kleopatra (and kmail) create empty signatures if the private key is stored on a gnupg smartcard

[Max Resch]

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

Max Resch resch@gmail.com changed:

   What|Removed |Added

 CC||resch@gmail.com

-- 
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 301625] kmail crashes during startup (segfault)

[Max Lin]

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

Max Lin max@gmx.com changed:

   What|Removed |Added

 CC||max@gmx.com

-- 
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 277705] KMail crashes if nepomuk is enabled

[Max Lin]

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

Max Lin max@gmx.com changed:

   What|Removed |Added

 CC||max@gmx.com

-- 
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 264861] Google calendar and contacts don't work

[Max]

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





--- Comment #28 from Max hazica gmail com  2011-03-28 10:46:30 ---
Thanks mu3en and yartsa. Works for me too. So it is fixed upstream.

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

[Bug 264861] Google calendar and contacts don't work

[Max]

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


Max maxlis...@gmail.com changed:

   What|Removed |Added

 CC||maxlis...@gmail.com




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

[Bug 264861] Google calendar and contacts don't work

[Max]

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





--- Comment #19 from Max hazica gmail com  2011-03-11 09:08:12 ---
Created an attachment (id=57854)
 -- (http://bugs.kde.org/attachment.cgi?id=57854)
Akonadi Server error while adding gcal resource

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

[Bug 264861] Google calendar and contacts don't work

[Max]

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





--- Comment #20 from Max hazica gmail com  2011-03-11 09:09:03 ---
Sorry about the split post. I have attached the akonadiserver.error file after
all.

(In reply to comment #18)
 Can only confirm the bug with Kubuntu 10.10 and KDE 4.6. Never tried it with
 4.5, but in 4.6 i can't even add the google calendar resource straight away.
 Instead I create an empty resource first, then add the gcal plugin; results as
 described above.
 
 Any developer feedback?
 
 Thanks

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

[Bug 264861] Google calendar and contacts don't work

[Max]

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


Max haz...@gmail.com changed:

   What|Removed |Added

 CC||haz...@gmail.com




--- Comment #18 from Max hazica gmail com  2011-03-11 08:58:25 ---
Can only confirm the bug with Kubuntu 10.10 and KDE 4.6. Never tried it with
4.5, but in 4.6 i can't even add the google calendar resource straight away.
Instead I create an empty resource first, then add the gcal plugin; results as
described above.

Any developer feedback?

Thanks

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

[Bug 185544] Kontact is sometimes started twice and crashes when closing the 2nd instance

[Max Rohland]

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


Max Rohland rohland@googlemail.com changed:

   What|Removed |Added

 CC|rohland@googlemail.com  |




-- 
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 226050] New: Kontact chrashed while closing

[Max Rohland]

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

   Summary: Kontact chrashed while closing
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: rohland@googlemail.com


Application: kontact (4.4 rc2)
KDE Platform Version: 4.3.98 (KDE 4.3.98 (KDE 4.4 RC3)) release 218
Qt Version: 4.6.1
Operating System: Linux 2.6.31.8-0.1-desktop x86_64
Distribution: openSUSE 11.2 (x86_64)

-- Information about the crash:
I have started Kontact twice, because Kontact was already active and after
closing both, the application chrashed

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  KMKernel::abortMailCheck (this=0x0) at
/usr/src/debug/kdepim-4.3.98/kmail/kmkernel.cpp:2442
#6  0x7f80df1320cc in KMailPart::~KMailPart (this=0x1387d50,
__in_chrg=value optimized out, __vtt_parm=value optimized out) at
/usr/src/debug/kdepim-4.3.98/kmail/kmail_part.cpp:139
#7  0x7f80f71e0bde in KontactInterface::Plugin::~Plugin() () from
/usr/lib64/libkontactinterface.so.4
#8  0x7f80dfe101a5 in KMailPlugin::~KMailPlugin (this=0x0, __in_chrg=value
optimized out, __vtt_parm=value optimized out)
at /usr/src/debug/kdepim-4.3.98/kontact/plugins/kmail/kmail_plugin.cpp:159
#9  0x7f80f77859ef in Kontact::MainWindow::~MainWindow (this=0x12a8360,
__in_chrg=value optimized out, __vtt_parm=value optimized out)
at /usr/src/debug/kdepim-4.3.98/kontact/src/mainwindow.cpp:258
#10 0x7f80f6070b5d in QObject::event(QEvent*) () from
/usr/lib64/libQtCore.so.4
#11 0x7f80f54755ef in QWidget::event(QEvent*) () from
/usr/lib64/libQtGui.so.4
#12 0x7f80f58354db in QMainWindow::event(QEvent*) () from
/usr/lib64/libQtGui.so.4
#13 0x7f80f6a84c23 in KXmlGuiWindow::event(QEvent*) () from
/usr/lib64/libkdeui.so.5
#14 0x7f80f541fc9c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQtGui.so.4
#15 0x7f80f542627b in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQtGui.so.4
#16 0x7f80f69bdba6 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libkdeui.so.5
#17 0x7f80f6060dfc in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQtCore.so.4
#18 0x7f80f6063577 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#19 0x7f80f608a7e3 in ?? () from /usr/lib64/libQtCore.so.4
#20 0x7f80ed87cdee in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#21 0x7f80ed8807b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x7f80ed8808e0 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#23 0x7f80f608a323 in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /usr/lib64/libQtCore.so.4
#24 0x7f80f54cddce in ?? () from /usr/lib64/libQtGui.so.4
#25 0x7f80f605f712 in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib64/libQtCore.so.4
#26 0x7f80f605faec in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib64/libQtCore.so.4
#27 0x7f80f606383b in QCoreApplication::exec() () from
/usr/lib64/libQtCore.so.4
#28 0x00403ed7 in main (argc=value optimized out, argv=value
optimized out) at /usr/src/debug/kdepim-4.3.98/kontact/src/main.cpp:221

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

[Bug 219657] New: Kontact chrashed while startup

[Max Rohland]

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

   Summary: Kontact chrashed while startup
   Product: kontact
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: rohland@googlemail.com


Application that crashed: kontact
Version of the application: 4.3.4
KDE Version: 4.3.4 (KDE 4.3.4) release 2
Qt Version: 4.6.0
Operating System: Linux 2.6.31.5-0.1-desktop x86_64
Distribution: openSUSE 11.2 (x86_64)

What I was doing when the application crashed:
I have started Kontact after login. while loading, it has chrashed. After
restart, it works.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f9678d07750 (LWP 4732))]

Thread 2 (Thread 0x7f965d22d910 (LWP 4738)):
#0  0x7f96724852cd in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f967751d5d2 in QWaitCondition::wait(QMutex*, unsigned long) () from
/usr/lib64/libQtCore.so.4
#2  0x7f9677512a19 in ?? () from /usr/lib64/libQtCore.so.4
#3  0x7f967751c6b5 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x7f967248065d in start_thread () from /lib64/libpthread.so.0
#5  0x7f967627e14d in clone () from /lib64/libc.so.6
#6  0x in ?? ()

Thread 1 (Thread 0x7f9678d07750 (LWP 4732)):
[KCrash Handler]
#5  operator!= (value=value optimized out, this=value optimized out) at
/usr/include/QtCore/qbasicatomic.h:69
#6  detach (value=value optimized out, this=value optimized out) at
/usr/include/QtCore/qmap.h:172
#7  find (value=value optimized out, this=value optimized out) at
/usr/include/QtCore/qmap.h:565
#8  findJob (value=value optimized out, this=value optimized out) at
/usr/src/debug/kdepim-4.3.4/kmail/imapaccountbase.h:180
#9  KMail::ListJob::slotListEntries (value=value optimized out, this=value
optimized out) at /usr/src/debug/kdepim-4.3.4/kmail/listjob.cpp:189
#10 0x7f966175ed97 in KMail::ListJob::qt_metacall (this=0x1a461b0,
_c=InvokeMetaMethod, _id=value optimized out, _a=0x7fffe0e320c0) at
/usr/src/debug/kdepim-4.3.4/build/kmail/listjob.moc:78
#11 0x7f96776222b3 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib64/libQtCore.so.4
#12 0x7f9674de9804 in KIO::ListJob::entries(KIO::Job*, QListKIO::UDSEntry
const) () from /usr/lib64/libkio.so.5
#13 0x7f9674df7ea7 in ?? () from /usr/lib64/libkio.so.5
#14 0x7f9674df823a in KIO::ListJob::qt_metacall(QMetaObject::Call, int,
void**) () from /usr/lib64/libkio.so.5
#15 0x7f96776222b3 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib64/libQtCore.so.4
#16 0x7f9674eaf115 in KIO::SlaveInterface::listEntries(QListKIO::UDSEntry
const) () from /usr/lib64/libkio.so.5
#17 0x7f9674eb2b9d in KIO::SlaveInterface::dispatch(int, QByteArray const)
() from /usr/lib64/libkio.so.5
#18 0x7f9674eaf4f3 in KIO::SlaveInterface::dispatch() () from
/usr/lib64/libkio.so.5
#19 0x7f9674ea22cd in KIO::Slave::gotInput() () from /usr/lib64/libkio.so.5
#20 0x7f9674ea43ec in KIO::Slave::qt_metacall(QMetaObject::Call, int,
void**) () from /usr/lib64/libkio.so.5
#21 0x7f96776222b3 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib64/libQtCore.so.4
#22 0x7f9674dbd6a7 in ?? () from /usr/lib64/libkio.so.5
#23 0x7f9674dbd7cd in KIO::Connection::qt_metacall(QMetaObject::Call, int,
void**) () from /usr/lib64/libkio.so.5
#24 0x7f967761f209 in QObject::event(QEvent*) () from
/usr/lib64/libQtCore.so.4
#25 0x7f96769d3bcc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib64/libQtGui.so.4
#26 0x7f96769da1ed in QApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libQtGui.so.4
#27 0x7f9677fb0f26 in KApplication::notify(QObject*, QEvent*) () from
/usr/lib64/libkdeui.so.5
#28 0x7f967760f53c in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/libQtCore.so.4
#29 0x7f9677611cb7 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#30 0x7f9677638fd3 in ?? () from /usr/lib64/libQtCore.so.4
#31 0x7f966fbf2dde in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#32 0x7f966fbf67a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#33 0x7f966fbf68d0 in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#34 0x7f9677638b13 in
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) ()
from /usr/lib64/libQtCore.so.4
#35 0x7f9676a8094e in ?? () from /usr/lib64/libQtGui.so.4
#36 0x7f967760de52 in
QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib64/libQtCore.so.4
#37 0x7f967760e22c in
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from
/usr/lib64/libQtCore.so.4
#38 

[Bug 215169] New: Kontact crashes while startup

[Max Rohland]

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

   Summary: Kontact crashes while startup
   Product: kontact
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: rohland@googlemail.com


Application that crashed: kontact
Version of the application: 4.3.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic x86_64
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
The current source language is auto; currently c.
[KCrash Handler]
#5  0x7fba6dddbcca in Kontact::Plugin::part (this=0x206f970) at
../../kontactinterfaces/plugin.cpp:186
#6  0x7fba57d23bb6 in KMailUniqueAppHandler::newInstance (this=value
optimized out) at ../../../../kontact/plugins/kmail/kmail_plugin.cpp:208
#7  0x7fba6ddde0f9 in Kontact::UniqueAppHandler::newInstance
(this=0x2079390, asn_id=value optimized out, args=...) at
../../kontactinterfaces/uniqueapphandler.cpp:128
#8  0x7fba6ddde164 in Kontact::UniqueAppHandler::qt_metacall
(this=0x2079390, _c=QMetaObject::InvokeMetaMethod, _id=34011504,
_a=0x7fff7a74ee60) at ./uniqueapphandler.moc:73
#9  0x7fba6a267ad4 in QDBusConnectionPrivate::deliverCall (this=value
optimized out, object=value optimized out, msg=value optimized out,
metaTypes=..., slotIdx=value optimized out)
at qdbusintegrator.cpp:891
#10 0x7fba6a268c69 in QDBusConnectionPrivate::activateCall (this=value
optimized out, object=0x2079390, flags=272, msg=...) at
qdbusintegrator.cpp:796
#11 0x7fba6a2692d5 in QDBusConnectionPrivate::activateObject (this=value
optimized out, node=..., msg=value optimized out, pathStartPos=value
optimized out) at qdbusintegrator.cpp:1370
#12 0x7fba6a2697c8 in QDBusActivateObjectEvent::placeMetaCall
(this=0x1cb4ce0) at qdbusintegrator.cpp:1464
#13 0x7fba6c1460f9 in QObject::event (this=0x2079390, e=0x1cb4ce0) at
kernel/qobject.cpp:
#14 0x7fba6ca56efc in QApplicationPrivate::notify_helper (this=0x1b6f790,
receiver=0x2079390, e=0x1cb4ce0) at kernel/qapplication.cpp:4056
#15 0x7fba6ca5e1ce in QApplication::notify (this=0x7fff7a74fa70,
receiver=0x2079390, e=0x1cb4ce0) at kernel/qapplication.cpp:4021
#16 0x7fba6d68de56 in KApplication::notify (this=0x7fff7a74fa70,
receiver=0x2079390, event=0x1cb4ce0) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x7fba6c136c2c in QCoreApplication::notifyInternal
(this=0x7fff7a74fa70, receiver=0x2079390, event=0x1cb4ce0) at
kernel/qcoreapplication.cpp:610
#18 0x7fba6c13780a in QCoreApplication::sendEvent (receiver=0x0,
event_type=value optimized out, data=0x1b3c080) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=value
optimized out, data=0x1b3c080) at kernel/qcoreapplication.cpp:1247
#20 0x7fba6c15f533 in QCoreApplication::sendPostedEvents (s=value
optimized out) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#21 postEventSourceDispatch (s=value optimized out) at
kernel/qeventdispatcher_glib.cpp:210
#22 0x7fba659b1bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#23 0x7fba659b5588 in ?? () from /lib/libglib-2.0.so.0
#24 0x7fba659b56b0 in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#25 0x7fba6c15f1a6 in QEventDispatcherGlib::processEvents (this=0x1b3bcb0,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:327
#26 0x7fba6caeb4be in QGuiEventDispatcherGlib::processEvents
(this=0x206f970, flags=value optimized out) at
kernel/qguieventdispatcher_glib.cpp:202
#27 0x7fba6c135532 in QEventLoop::processEvents (this=value optimized
out, flags=) at kernel/qeventloop.cpp:149
#28 0x7fba6c135904 in QEventLoop::exec (this=0x7fff7a74f9b0, flags=) at
kernel/qeventloop.cpp:201
#29 0x7fba6c137ab9 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#30 0x00403f47 in main (argc=value optimized out, argv=value
optimized out) at ../../../kontact/src/main.cpp:218

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

[Bug 212261] New: Kontact chrashes while clicking on Korganizer Reminderclient Icon

[Max Rohland]

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

   Summary: Kontact chrashes while clicking on Korganizer
Reminderclient Icon
   Product: kontact
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: rohland@googlemail.com


Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic x86_64
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
The current source language is auto; currently c.
[KCrash Handler]
#5  0x0065006f in ?? ()
#6  0x7f4e1e5c504b in QWidget::show (this=0x2728ad0) at
/usr/include/qt4/QtGui/qwidget.h:473
#7  Kontact::UniqueAppHandler::newInstance (this=0x2728ad0) at
../../kontactinterfaces/uniqueapphandler.cpp:137
#8  0x7f4e1e5c50f9 in Kontact::UniqueAppHandler::newInstance
(this=0x2728ad0, asn_id=value optimized out, args=...) at
../../kontactinterfaces/uniqueapphandler.cpp:128
#9  0x7f4e1e5c5164 in Kontact::UniqueAppHandler::qt_metacall
(this=0x2728ad0, _c=QMetaObject::InvokeMetaMethod, _id=40608448,
_a=0x7fff5a7772b0) at ./uniqueapphandler.moc:73
#10 0x7f4e1aa4dad4 in QDBusConnectionPrivate::deliverCall (this=value
optimized out, object=value optimized out, msg=value optimized out,
metaTypes=..., slotIdx=value optimized out)
at qdbusintegrator.cpp:891
#11 0x7f4e1aa4ec69 in QDBusConnectionPrivate::activateCall (this=value
optimized out, object=0x2728ad0, flags=272, msg=...) at
qdbusintegrator.cpp:796
#12 0x7f4e1aa4f2d5 in QDBusConnectionPrivate::activateObject (this=value
optimized out, node=..., msg=value optimized out, pathStartPos=value
optimized out) at qdbusintegrator.cpp:1370
#13 0x7f4e1aa4f7c8 in QDBusActivateObjectEvent::placeMetaCall
(this=0x3077b60) at qdbusintegrator.cpp:1464
#14 0x7f4e1c92d0f9 in QObject::event (this=0x2728ad0, e=0x3077b60) at
kernel/qobject.cpp:
#15 0x7f4e1d23defc in QApplicationPrivate::notify_helper (this=0x2247f60,
receiver=0x2728ad0, e=0x3077b60) at kernel/qapplication.cpp:4056
#16 0x7f4e1d2451ce in QApplication::notify (this=0x7fff5a777ec0,
receiver=0x2728ad0, e=0x3077b60) at kernel/qapplication.cpp:4021
#17 0x7f4e1de74ab6 in KApplication::notify (this=0x7fff5a777ec0,
receiver=0x2728ad0, event=0x3077b60) at ../../kdeui/kernel/kapplication.cpp:302
#18 0x7f4e1c91dc2c in QCoreApplication::notifyInternal
(this=0x7fff5a777ec0, receiver=0x2728ad0, event=0x3077b60) at
kernel/qcoreapplication.cpp:610
#19 0x7f4e1c91e80a in QCoreApplication::sendEvent (receiver=0x0,
event_type=value optimized out, data=0x221a080) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=value
optimized out, data=0x221a080) at kernel/qcoreapplication.cpp:1247
#21 0x7f4e1c946533 in QCoreApplication::sendPostedEvents (s=value
optimized out) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#22 postEventSourceDispatch (s=value optimized out) at
kernel/qeventdispatcher_glib.cpp:210
#23 0x7f4e16197bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x7f4e1619b588 in ?? () from /lib/libglib-2.0.so.0
#25 0x7f4e1619b6b0 in g_main_context_iteration () from
/lib/libglib-2.0.so.0
#26 0x7f4e1c9461a6 in QEventDispatcherGlib::processEvents (this=0x2219cb0,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:327
#27 0x7f4e1d2d24be in QGuiEventDispatcherGlib::processEvents
(this=0x225fc70, flags=value optimized out) at
kernel/qguieventdispatcher_glib.cpp:202
#28 0x7f4e1c91c532 in QEventLoop::processEvents (this=value optimized
out, flags=) at kernel/qeventloop.cpp:149
#29 0x7f4e1c91c904 in QEventLoop::exec (this=0x7fff5a777e00, flags=) at
kernel/qeventloop.cpp:201
#30 0x7f4e1c91eab9 in QCoreApplication::exec () at
kernel/qcoreapplication.cpp:888
#31 0x00403f47 in main (argc=value optimized out, argv=value
optimized out) at ../../../kontact/src/main.cpp:218

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

[Bug 203688] KMail/Kontact crashes while while moving mail to subfolder

[Max Rohland]

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





--- Comment #2 from Max Rohland rohland max googlemail com  2009-08-16 
19:43:36 ---
I have installed  kdepim-dbg and willl try to reproduce the crash

-- 
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 203688] New: KMail/Kontact crashes while while moving mail to subfolder

[Max R .]

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

   Summary: KMail/Kontact crashes while while moving mail to
subfolder
   Product: kontact
   Version: unspecified
  Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: rohland@googlemail.com


Application that crashed: kontact
Version of the application: 4.3.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-14-generic x86_64
Distribution: Ubuntu 9.04

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  QCoreApplication::postEvent (receiver=0x3425510, event=0x2b4fe90,
priority=0) at kernel/qcoreapplication.cpp:1012
#6  0x7f1112551b02 in ?? () from /usr/lib/libkmailprivate.so.4
#7  0x7f1112554de7 in ?? () from /usr/lib/libkmailprivate.so.4
#8  0x7f1125c81ea2 in QMetaObject::activate (sender=0x31619d0,
from_signal_index=value optimized out, to_signal_index=7, argv=0x1) at
kernel/qobject.cpp:3113
#9  0x7f11262c0512 in KJob::result (this=0x3425510, _t1=0x31619d0) at
/build/buildd/kde4libs-4.3.0/obj-x86_64-linux-gnu/kdecore/kjob.moc:188
#10 0x7f11262c088f in KJob::emitResult (this=0x31619d0) at
/build/buildd/kde4libs-4.3.0/kdecore/jobs/kjob.cpp:304
#11 0x7f11280d4330 in KIO::SimpleJob::slotFinished (this=0x31619d0) at
/build/buildd/kde4libs-4.3.0/kio/kio/job.cpp:477
#12 0x7f11280d47e3 in KIO::TransferJob::slotFinished (this=0x31619d0) at
/build/buildd/kde4libs-4.3.0/kio/kio/job.cpp:948
#13 0x7f11280cf5d5 in KIO::TransferJob::qt_metacall (this=0x31619d0,
_c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff33727af0)
at /build/buildd/kde4libs-4.3.0/obj-x86_64-linux-gnu/kio/jobclasses.moc:343
#14 0x7f1125c81ea2 in QMetaObject::activate (sender=0x296f850,
from_signal_index=value optimized out, to_signal_index=8, argv=0x1) at
kernel/qobject.cpp:3113
#15 0x7f1128190a91 in KIO::SlaveInterface::dispatch (this=0x296f850,
_cmd=104, rawdata=value optimized out) at
/build/buildd/kde4libs-4.3.0/kio/kio/slaveinterface.cpp:175
#16 0x7f112818d5e2 in KIO::SlaveInterface::dispatch (this=0x296f850) at
/build/buildd/kde4libs-4.3.0/kio/kio/slaveinterface.cpp:91
#17 0x7f1128180163 in KIO::Slave::gotInput (this=0x296f850) at
/build/buildd/kde4libs-4.3.0/kio/kio/slave.cpp:322
#18 0x7f11281823c8 in KIO::Slave::qt_metacall (this=0x296f850,
_c=QMetaObject::InvokeMetaMethod, _id=244, _a=0x7fff33727f10) at
/build/buildd/kde4libs-4.3.0/obj-x86_64-linux-gnu/kio/slave.moc:76
#19 0x7f1125c81ea2 in QMetaObject::activate (sender=0x182ec80,
from_signal_index=value optimized out, to_signal_index=4, argv=0x1) at
kernel/qobject.cpp:3113
#20 0x7f112809d801 in KIO::ConnectionPrivate::dequeue (this=0x294ef20) at
/build/buildd/kde4libs-4.3.0/kio/kio/connection.cpp:82
#21 0x7f112809dc5a in KIO::Connection::qt_metacall (this=0x182ec80,
_c=QMetaObject::InvokeMetaMethod, _id=244, _a=0x32384f0)
at /build/buildd/kde4libs-4.3.0/obj-x86_64-linux-gnu/kio/connection.moc:73
#22 0x7f1125c7c5d8 in QObject::event (this=0x182ec80, e=0x2bec170) at
kernel/qobject.cpp:
#23 0x7f11267eaf4d in QApplicationPrivate::notify_helper (this=0x1510350,
receiver=0x182ec80, e=0x2bec170) at kernel/qapplication.cpp:4056
#24 0x7f11267f318a in QApplication::notify (this=0x7fff33728970,
receiver=0x182ec80, e=0x2bec170) at kernel/qapplication.cpp:4021
#25 0x7f1127bef71b in KApplication::notify (this=0x7fff33728970,
receiver=0x182ec80, event=0x2bec170) at
/build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:302
#26 0x7f1125c6c6ac in QCoreApplication::notifyInternal
(this=0x7fff33728970, receiver=0x182ec80, event=0x2bec170) at
kernel/qcoreapplication.cpp:610
#27 0x7f1125c6d31a in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x14df850) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#28 0x7f1125c95e03 in postEventSourceDispatch (s=value optimized out) at
../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#29 0x7f111f3bd20a in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#30 0x7f111f3c08e0 in ?? () from /usr/lib/libglib-2.0.so.0
#31 0x7f111f3c0a7c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#32 0x7f1125c95a8f in QEventDispatcherGlib::processEvents (this=0x14df0a0,
flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:327
#33 0x7f1126883bdf in QGuiEventDispatcherGlib::processEvents
(this=0x3425510, flags=value optimized out) at
kernel/qguieventdispatcher_glib.cpp:202
#34 0x7f1125c6af42 in QEventLoop::processEvents (this=value optimized
out, flags={i = 863144080}) at kernel/qeventloop.cpp:149
#35 0x7f1125c6b314 in QEventLoop::exec (this=0x7fff337288d0, flags={i =
863144160}) at 

[Bug 193116] printing copies doesnt work

[Max]

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


Max knucks...@gmail.com changed:

   What|Removed |Added

 CC||knucks...@gmail.com




--- Comment #2 from Max knuckster gmail com  2009-05-20 10:05:21 ---
I second this. Okular prints only one copy. This bug persists in KDE 4.2.3.

-- 
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 189376] New: Exit from application via Akregator tray icon leads to crash

[Max]

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

   Summary: Exit from application via Akregator tray icon leads to
crash
   Product: kontact
   Version: 1.4
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: kolotil...@gmail.com


Version:   1.4 (using KDE 4.2.0)
OS:Linux
Installed from:Ubuntu Packages

The bug was found on Kubuntu 8.10, 2.6.27-14-generic
KDE 4.2.0
Kontact 1.4

Steps to reproduce:
1. Start Kontact
2. Choose Feed Reader in main window (a tray icon will appear)
3. Right click on this icon - Quit
You'll get a fatal error occured message:
Tha application Kontact (kontact) crashed and caused the signal 6 (SIGABRT)

Backtrace details:
Thread 1 (Thread 0xb4a896c0 (LWP 15074)):
[KCrash Handler]
#6 0xb7f3d430 in __kernel_vsyscall ()
#7 0xb591f8a0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb5921268 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb591872e in __assert_fail () from /lib/tls/cmov/libc.so.6
#10 0xb147a34c in KMKernel::self () from /usr/lib/libkmailprivate.so.4
#11 0xb155186c in kmcrashHadler () from /usr/lib/libkmailprivate.so.4
#12 0xb6cf863a in KCrash::defaultCrashHadler () from /usr/lib/libkdeui.so.5
#13 signal hadler called
#14 0xb7f3d430 in __kernel_vsyscall ()
#15 0xb591f8a0 in raise () from /lib/tls/i686/cmov/libc.so.6
#16 0xb5921268 in abort () from /lib/tls/i686/cmov/libc.so.6
#17 0xb595d16d in ?? from /lib/tls/i686/cmov/libc.so.6
#18 0xb5963454 in ?? from /lib/tls/i686/cmov/libc.so.6
#19 0xb5965267 in ?? from /lib/tls/i686/cmov/libc.so.6
#20 0xb5965544b6 in free () from /lib/tls/i686/cmov/libc.so.6
#21 0xb5b410b1 in operator delete () from /usr/lib/libstdc++.so.6
#22 0xb651ad91 in ?? () from /usr/lib/libQtGui.so.4
#23 0xb5cd3d9e in QObject::~Qobject () from /usr/lib/libQtCore.so.4
#24 0xb61c7b0f in QWidget::~QWidget () from /usr/lib/libQtGui.so.4
#25 0xb6519921 in QMainWindow::~QmainWindow () from /usr/lib/libQtGui.so.4
#26 0xb6d6b849 in KMainWindow::~KMainWindow () from /usr/lib/libKdeui.so.5
#27 0xb6dae3c7 in KXmlGuiWindow::~KXmlGuiWindow () from /usr/lib/libKdeui.so.5
#28 0xb70c5688 in KParts::MainWindow::~MainWindow () from
/usr/lib/libKparts.so.4
#29 0xb77d5ef7 in Kontact::Core::~Core () from
/usr/lib/libkontactinterfaces.so.4
#30 0xb77f30ec in Kontact::MainWindow::~MainWindow () from
/usr/lib/libkontactprivate.so.4
#31 0x0804c0ae in _start ()

-- 
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 170539] New: Selecting multiple files with mouse to insert an attachement inserts them twice

[Max De Berraly]

http://bugs.kde.org/show_bug.cgi?id=170539

   Summary: Selecting multiple files with mouse to insert an
attachement inserts them twice
   Product: kmail
   Version: unspecified
  Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: GUI
AssignedTo: kdepim-bugs@kde.org
ReportedBy: [EMAIL PROTECTED]


Version:(using KDE 4.1.1)
OS:Linux
Installed from:Ubuntu Packages

1. Open kmail kde4
2. Compose a new mail
3. Add an attachment, for example file1 and file2 in folder1
5. Select files by clicking and holding in an empty zone and move the mouse
over the files
6. Then you see that the dialog box recorder those files to open :
file1.jpg file1.jpg file2.jpg file2.jpg
instead of 
file1.jpg file2.jpg


-- 
Configure bugmail: http://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 32400] Sort by last / newest mail in thread

[Max]

--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.
 
http://bugs.kde.org/show_bug.cgi?id=32400 




--- Additional Comments From keymone gmail com  2008-08-08 14:42 ---
i vote for it
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs