[akregator] [Bug 377607] Akregator minimum window width spans half the screen

2023-01-18 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=377607

--- Comment #4 from Metko  ---
Thanks for keeping track of this rather subtle issue. Now (version 5.19.3
(21.12.3)) the minimum width seems to have changed to 889 pixels, which is a
step forward but still away from my preferred standard width of about 700
pixels.

-- 
You are receiving this mail because:
You are watching all bug changes.

[akregator] [Bug 377607] Akregator minimum window width spans half the screen

2023-01-18 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=377607

Metko  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 441214] SMTP passwords aren't being saved

2022-01-12 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=441214

Metko  changed:

   What|Removed |Added

   Platform|Manjaro |openSUSE RPMs
 CC||metkome...@gmail.com

--- Comment #5 from Metko  ---
Confirming this for kmail2 5.19.1 (21.12.1) under openSUSE 15.3. Also tried
removing passwords from kwallet and the SMTP configuration, to no avail.
Starting kmail in the command line and sending the first email shows two
suspicious messages at the end (see below). Unfortunately, they are quite
uninformative. Also it's weird that the SMTP password is requested only upon
sending the first email after login; all subsequent emails are sent without
asking again for the password - until the next login.

[6025:6067:0112/091631.565475:ERROR:file_path_watcher_linux.cc(315)]
inotify_init() failed: Zu viele offene Dateien (24)
[6025:6025:0112/091631.568940:ERROR:proxy_config_service_linux.cc(607)]
inotify_init failed: Zu viele offene Dateien (24)
Cannot initialize model with data QJsonObject(). missing: QJsonValue(string,
"urls")
[6025:6025:0112/091631.940652:ERROR:proxy_config_service_linux.cc(607)]
inotify_init failed: Zu viele offene Dateien (24)
[6078:6092:0112/091632.005283:ERROR:file_path_watcher_linux.cc(315)]
inotify_init() failed: Zu viele offene Dateien (24)
We have an error during reading password  "Entry not found"
We have an error during reading password  "Entry not found"
 list count   1
[6025:6025:0112/092357.859324:ERROR:proxy_config_service_linux.cc(607)]
inotify_init failed: Zu viele offene Dateien (24)
Cannot initialize model with data QJsonObject(). missing: QJsonValue(string,
"urls")
org.kde.pim.liblanguagetoolplugin:  Error reply -  "Verbindung verweigert"
org.kde.pim.liblanguagetoolplugin: Error during loading languages from server :
 "Verbindung verweigert"
org.kde.pim.akonadicore: Received response with a different tag!
We have an error during reading password  "Entry not found"
We have an error during reading password  "Entry not found"

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 421501] New: Kontact crashes when mail saving attachment

2020-05-14 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=421501

Bug ID: 421501
   Summary: Kontact crashes when mail saving attachment
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

Application: kontact (5.14.0 (20.04.0))

Qt Version: 5.14.1
Frameworks Version: 5.70.0
Operating System: Linux 4.12.14-lp151.28.48-default x86_64
Windowing system: X11
Distribution: openSUSE Leap 15.1

-- Information about the crash:
- What I was doing when the application crashed: Right click on the attachment,
Save as..., crash. The attachment isn't saved.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3d07539000 (LWP 7698))]

Thread 19 (Thread 0x7f3c4b0a2700 (LWP 7829)):
#0  0x7f3d03d176db in poll () from /lib64/libc.so.6
#1  0x7f3cfd6651a9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f3cfd6652bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f3d048907eb in QEventDispatcherGlib::processEvents
(this=0x7f3c44000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f3d0482fd4a in QEventLoop::exec (this=this@entry=0x7f3c4b0a1c30,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7f3d04640657 in QThread::exec (this=) at
thread/qthread.cpp:536
#6  0x7f3d04641b2c in QThreadPrivate::start (arg=0x55f991657090) at
thread/qthread_unix.cpp:342
#7  0x7f3cffa384f9 in start_thread () from /lib64/libpthread.so.0
#8  0x7f3d03d21f2f in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7f3c571ee700 (LWP 7816)):
#0  0x7f3cffa3e87d in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f3cf3f1d96a in base::ConditionVariable::Wait () at
./../../3rdparty/chromium/base/synchronization/condition_variable_posix.cc:75
#2  0x7f3cf3f1e40c in base::WaitableEvent::TimedWaitUntil () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:235
#3  0x7f3cf3f1e51f in base::WaitableEvent::Wait () at
./../../3rdparty/chromium/base/synchronization/waitable_event_posix.cc:155
#4  0x7f3cf3ed9d58 in base::internal::WorkerThread::Delegate::WaitForWork
() at ./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:33
#5  0x7f3cf3ede319 in base::internal::WorkerThread::RunWorker () at
./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:317
#6  0x7f3cf3ede654 in base::internal::WorkerThread::RunSharedWorker () at
./../../3rdparty/chromium/base/task/thread_pool/worker_thread.cc:235
#7  0x7f3cf3f20595 in ThreadFunc () at
./../../3rdparty/chromium/base/threading/platform_thread_posix.cc:81
#8  0x7f3cffa384f9 in start_thread () from /lib64/libpthread.so.0
#9  0x7f3d03d21f2f in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7f3c5700 (LWP 7747)):
#0  0x7f3d03d176db in poll () from /lib64/libc.so.6
#1  0x7f3cfd6651a9 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f3cfd6652bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f3d048907eb in QEventDispatcherGlib::processEvents
(this=0x7f3c58000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f3d0482fd4a in QEventLoop::exec (this=this@entry=0x7f3c5fffec30,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#5  0x7f3d04640657 in QThread::exec (this=) at
thread/qthread.cpp:536
#6  0x7f3d04641b2c in QThreadPrivate::start (arg=0x55f98fe439e0) at
thread/qthread_unix.cpp:342
#7  0x7f3cffa384f9 in start_thread () from /lib64/libpthread.so.0
#8  0x7f3d03d21f2f in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7f3c6dfa8700 (LWP 7739)):
#0  0x7f3cfd6aafd4 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f3cfd6646fc in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f3cfd6650db in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f3cfd6652bc in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f3d048907eb in QEventDispatcherGlib::processEvents
(this=0x7f3c64000b10, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f3d0482fd4a in QEventLoop::exec (this=this@entry=0x7f3c6dfa7c30,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:225
#6  0x7f3d04640657 in QThread::exec (this=) at
thread/qthread.cpp:536
#7  0x7f3d04641b2c in QThreadPrivate::start (arg=0x55f99021ad30) at
thread/qthread_unix.cpp:342
#8  0x7f3cffa384f9 in start_thread () from /lib64/libpthread.so.0
#9  0x7f3d03d21f2f in clone () from /lib64/libc.so.6

Thread 15 (Thread 0x7f3c6e7a9700 (LWP 7738)):
#0  0x7f3cfd6aafd4 in g_mutex_unlock () from 

[Akonadi] [Bug 389209] New mails are not filtered

2018-11-27 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=389209

Metko  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #1 from Metko  ---
Works on a new install of Leap 15.0.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 387793] Leave messages on server doesn't work on POP3 account

2018-11-27 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387793

Metko  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Metko  ---
I'm using IMAP now, so I can't figure out whether this bug is still present.
Marking it as RESOLVED.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 387462] Limiting the CalDav fetch period results in no items

2018-11-27 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387462

Metko  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 387461] DAV groupware resource configuration dialog broken

2018-11-27 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387461

Metko  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 384464] Message window does not display Chinese characters

2018-11-27 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=384464

Metko  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 384464] Message window does not display Chinese characters

2018-11-27 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=384464

--- Comment #1 from Metko  ---
Resolved in 5.8.3. Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[akregator] [Bug 377607] Akregator minimum window width spans half the screen

2018-11-27 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=377607

--- Comment #2 from Metko  ---
Problem is back in 5.8.3. Effectively, Akregator is the application with the
largest width of all components in Kontact, making the Kontact window
excessively wide. Any ideas here?

-- 
You are receiving this mail because:
You are watching all bug changes.

[marble] [Bug 394517] the search-function has no results except if I search for big towns (Cannot parse osm nominatim result)

2018-05-31 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=394517

Metko  changed:

   What|Removed |Added

 CC||metkome...@gmail.com

--- Comment #5 from Metko  ---
Count me in! Nominatim search doesn't work for me either. Tested different
(older) versions of marble and different users on my computer, and invariably
got the same result: apart from city names, nothing is found in searches (e.g.
the example in the manual Baker Street, London). This behavior supports Kevin's
explanation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[akregator] [Bug 377607] Akregator minimum window width spans half the screen

2018-02-09 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=377607

--- Comment #1 from Metko <metkome...@gmail.com> ---
Version 5.7.2 in KDE Applications 17.12.2. solves this issue if akregator is
launched standalone. Thanks!
The problem persists however when it runs in kontact. Could this be solved too?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 389209] New: New mails are not filtered

2018-01-19 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=389209

Bug ID: 389209
   Summary: New mails are not filtered
   Product: Akonadi
   Version: 5.7.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Mail Filter Agent
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

After kmail has started, incoming emails sometimes don't get filtered. Also
"Apply filer" on an existing email doesn't do anything. However, after the
filter configuration dialog has been opened and closed once, filters work as
expected until starting kmail next time. Problem appears with POP3 as well as
IMAP accounts.

kmail 5.7.1
openSUSE Leap 42.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 388723] New: 'todo' tag on a mail gets lost when new email arrives

2018-01-09 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=388723

Bug ID: 388723
   Summary: 'todo' tag on a mail gets lost when new email arrives
   Product: kmail2
   Version: 5.7.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

Tagging an email in an IMAP account as 'todo' gets reset when new mail arrives.
Surprisingly, tagging it 'important' survives new email arrivals.
openSUSE Leap 42.3, kmail 5.7, Qt 5.10

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 388483] Setting up a GMail account hangs at "Checking token, This should take a moment"

2018-01-04 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=388483

--- Comment #2 from Metko <metkome...@gmail.com> ---
Qt5Core is at 5.10.0. Anything else that may help?

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 388484] New: Enable IMAP subscriptions other than mail in KDE applications

2018-01-03 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=388484

Bug ID: 388484
   Summary: Enable IMAP subscriptions other than mail in KDE
applications
   Product: Akonadi
   Version: 5.7.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: IMAP resource
  Assignee: chrig...@fastmail.fm
  Reporter: metkome...@gmail.com
CC: kdepim-b...@kde.org
  Target Milestone: ---

Besides email, IMAP accounts frequently offer calendars, contacts, notes etc.
Wouldn't it be great if these subscriptions would be accessible in the
corresponding KDE applications, i.e. korganizer, kontact, kjots/knotes?

For example, I'm using the OSX notes app to store notes in my IMAP account.
Whereas I can see those notes in kmail, there is no way to add or modify them
in KDE. A natural approach would be to use kjots, but unfortunately the akonadi
resource does not show up there.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 388483] New: Setting up a GMail account hangs at "Checking token, This should take a moment"

2018-01-03 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=388483

Bug ID: 388483
   Summary: Setting up a GMail account hangs at "Checking token,
This should take a moment"
   Product: kmail2
   Version: 5.7.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: config dialog
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

I tried to setup a kmail IMAP account that links to my gmail account. No matter
which options I choose during the configuration, it invariably hangs showring
the message "Schlüssel wir überprüft. Das kann einen Moment dauern". In
particular I tried:
- to disable PGP encryption and publishing the key
- generating a new key or using an existing one
- enabled "less secure apps" in my gmail account
- to configure the IMAP account manually, i.e. not using the service discovery
Any ideas what else to try?

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 387923] Calendar from DAVGroupware resource crashes KOrganizer

2017-12-28 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387923

--- Comment #5 from Metko <metkome...@gmail.com> ---
Purged finished todos from the DAVGroupware resource and there are nor more
crashes. I tried to bisect the list of finished todos to track down the item
that caused the crash, but didn't succeed. Apparently the crash occurs only
when the list is sufficiently long.

-- 
You are receiving this mail because:
You are watching all bug changes.

[akregator] [Bug 387581] akregator crashing on startup

2017-12-28 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387581

Metko <metkome...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 378011] KMail 5.4.3 Mailing list not resolved

2017-12-28 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=378011

Metko <metkome...@gmail.com> changed:

   What|Removed |Added

 CC||metkome...@gmail.com

--- Comment #23 from Metko <metkome...@gmail.com> ---
*** Bug 384697 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 384697] Mails are sent to the list's name rather than the addresses on the list

2017-12-28 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=384697

Metko <metkome...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Metko <metkome...@gmail.com> ---


*** This bug has been marked as a duplicate of bug 378011 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.

2017-12-22 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=388068

Metko <metkome...@gmail.com> changed:

   What|Removed |Added

 CC||metkome...@gmail.com

--- Comment #14 from Metko <metkome...@gmail.com> ---
(In reply to Frank Noack from comment #13)
> The patch from  https://phabricator.kde.org/D9476 works for me.

Is it possible to get a binary patch somewhere?

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 387923] Calendar from DAVGroupware resource crashes KOrganizer

2017-12-18 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387923

--- Comment #4 from Metko <metkome...@gmail.com> ---
I'd love to, but it's hard to imagine how. One would need a copy of my calendar
in owncloud, which should be imported to an owncloud account in the test setup.
Would you be able to do this? Some observations that may help instead:

1) As I wrote above, exporting and re-importing the calendar solved the
crashing behavior. However, todos were not imported (due to a malfunction of
the import function), so the calendar contents is not identical. Interestingly,
if you look at the stack trace above, you see that thread 1 crashed upon
displaying a todo.

2) Previously I found a temporary solution by running the current version of
korganizer with the (old) 17.04 version of libKF5eventview. The most recent
korganizer version is not compatible with that version though, which is why
this solution stopped working (and which made me file this bug). But it's
another indication that the bug most likely is in the code for viewing an
event.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 387923] Calendar from DAVGroupware resource crashes KOrganizer

2017-12-18 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387923

--- Comment #2 from Metko <metkome...@gmail.com> ---
(In reply to Metko from comment #1)
> Solved the problem by exporting all calendar entries and importing them to a
> newly created (CalDav-owncloud-) calendar.

Beware! Korganizer's import function does not import todos!

-- 
You are receiving this mail because:
You are watching all bug changes.

[akregator] [Bug 387581] akregator crashing on startup

2017-12-15 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387581

--- Comment #1 from Metko <metkome...@gmail.com> ---
Solved in KDE applications 17.12.0.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 387923] Calendar from DAVGroupware resource crashes KOrganizer

2017-12-15 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387923

--- Comment #1 from Metko <metkome...@gmail.com> ---
Solved the problem by exporting all calendar entries and importing them to a
newly created (CalDav-owncloud-) calendar.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Akonadi] [Bug 387461] DAV groupware resource configuration dialog broken

2017-12-15 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387461

--- Comment #1 from Metko <metkome...@gmail.com> ---
I figured out how to get past the first dialog: Enter the username, enter the
password, go back to the username, add a space, et voila - the 'Next' button is
enabled.

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 387923] New: Calendar from DAVGroupware resource crashes KOrganizer

2017-12-15 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387923

Bug ID: 387923
   Summary: Calendar from DAVGroupware resource crashes KOrganizer
   Product: korganizer
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

Application: korganizer (5.6.90 rc)

Qt Version: 5.9.3
Frameworks Version: 5.40.0
Operating System: Linux 4.4.92-31-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
- What I was doing when the application crashed:
Creating a DAVGroupware resource in KOrganizer and linking it to an owncloud
calendar works fine as long the application runs. Upon restartimg KOrganizer
though, it crashes. When removing the resource using akonadiconsole, KOrganizer
starts normally, and the whole cycle can be repeated.

The crash can be reproduced every time.

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

Thread 5 (Thread 0x7f7897fff700 (LWP 4296)):
#0  0x7f78b56a6899 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f78b5664b51 in g_main_context_query () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f78b566527f in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f78b566542c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f78bfd3721b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f78bfce445b in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f78bfb27e4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f78bfb2c70d in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f78b71fa744 in start_thread () from /lib64/libpthread.so.0
#9  0x7f78bf221aad in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f789cee4700 (LWP 4293)):
#0  0x7f78b7201a7c in __lll_lock_wait () from /lib64/libpthread.so.0
#1  0x7f78b71fc7fb in pthread_mutex_lock () from /lib64/libpthread.so.0
#2  0x7f78b6c69e4c in ?? () from /usr/X11R6/lib64/libGL.so.1
#3  0x7f78b6c6ed81 in ?? () from /usr/X11R6/lib64/libGL.so.1
#4  0x7f78b6c6f23b in ?? () from /usr/X11R6/lib64/libGL.so.1
#5  0x7f78af58a0f1 in ?? () from /usr/lib64/tls/libnvidia-tls.so.384.98
#6  0x7f78b56a5750 in ?? () from /usr/lib64/libglib-2.0.so.0
#7  0x7f78b5664e49 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#8  0x7f78b56652a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#9  0x7f78b566542c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#10 0x7f78bfd3721b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#11 0x7f78bfce445b in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#12 0x7f78bfb27e4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#13 0x7f78bfb2c70d in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#14 0x7f78b71fa744 in start_thread () from /lib64/libpthread.so.0
#15 0x7f78bf221aad in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f789e578700 (LWP 4292)):
#0  0x7f78bf21920d in poll () from /lib64/libc.so.6
#1  0x7f78b5665314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f78b566542c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f78bfd3721b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f78bfce445b in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f78bfb27e4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f78be7127c5 in ?? () from /usr/lib64/libQt5DBus.so.5
#7  0x7f78bfb2c70d in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#8  0x7f78b71fa744 in start_thread () from /lib64/libpthread.so.0
#9  0x7f78bf221aad in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f78a53d6700 (LWP 4291)):
#0  0x7f78bf21920d in poll () from /lib64/libc.so.6
#1  0x7f78b51ff3e2 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f78b5200fcf in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f78a7d62a19 in QXcbEventReader::run() () from
/usr/lib64/libQt5XcbQpa.so.5
#4  0x7f78bfb2c70d in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f78b71fa744 in start_thread () from /lib64/libpthread.so.0
#6  0x7f78bf221aad in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f78c3958940 (LWP 4290)):
[KCrash Handler]
#6  0x7f78bd869dd3 in greaterThan (node1=..., node2=...) at
/usr/src/debug/eventviews-17.11.90/src/todo/incidencetreemodel.cpp:48
#7  0x7f78bd872ec1 in
std::__unguarded_partition

[kmail2] [Bug 387793] New: Leave messages on server doesn't work on POP3 account

2017-12-11 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387793

Bug ID: 387793
   Summary: Leave messages on server doesn't work on POP3 account
   Product: kmail2
   Version: 5.6.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

For a POP3 account, I enabled "Leave fetched messages on server" and "number of
days"=30, but old meesages are being downloaded over and over again. They end
up as new messages in the incoming folder, duplicating the messages that are
already there. Doesn't matter if I specify number of days, megabytes, or number
of messages to keep. It seems as if kmail/akonadi don't remember which messages
already have been downloaded.

kmail 17.11.90
openLeap 42.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[akregator] [Bug 387581] New: akregator crashing on startup

2017-12-04 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387581

Bug ID: 387581
   Summary: akregator crashing on startup
   Product: akregator
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

Application: akregator (5.6.90 rc)

Qt Version: 5.9.3
Frameworks Version: 5.40.0
Operating System: Linux 4.4.92-31-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
- What I was doing when the application crashed:
Running akregator results in a segmentation fault. However, when the global
menu bar  configuration is changed from "export to mini program" to
"application" (in the system configuration), it starts normally.

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc6f9656980 (LWP 19920))]

Thread 21 (Thread 0x7fc64eb89700 (LWP 19952)):
#0  0x7fc6efb2e0bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc6e2bd2b4b in ?? () from /usr/lib64/libQt5Script.so.5
#2  0x7fc6e2bd2b79 in ?? () from /usr/lib64/libQt5Script.so.5
#3  0x7fc6efb29744 in start_thread () from /lib64/libpthread.so.0
#4  0x7fc6f5566aad in clone () from /lib64/libc.so.6

Thread 20 (Thread 0x7fc688ff9700 (LWP 19947)):
#0  0x7fc6f555e20d in poll () from /lib64/libc.so.6
#1  0x7fc6edd4d314 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7fc6edd4d42c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7fc6f5e6521b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7fc6f5e1245b in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7fc6f5c55e4a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7fc6f5c5a70d in QThreadPrivate::start(void*) () from
/usr/lib64/libQt5Core.so.5
#7  0x7fc6efb29744 in start_thread () from /lib64/libpthread.so.0
#8  0x7fc6f5566aad in clone () from /lib64/libc.so.6

Thread 19 (Thread 0x7fc6897fa700 (LWP 19946)):
#0  0x7fc6f555a28d in read () from /lib64/libc.so.6
#1  0x7fc6d69299c1 in pa_read () from
/usr/lib64/pulseaudio/libpulsecommon-11.1.so
#2  0x7fc6dda5a1ae in pa_mainloop_prepare () from /usr/lib64/libpulse.so.0
#3  0x7fc6dda5abc2 in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0
#4  0x7fc6dda5ac80 in pa_mainloop_run () from /usr/lib64/libpulse.so.0
#5  0x7fc6dda68dc6 in ?? () from /usr/lib64/libpulse.so.0
#6  0x7fc6d69586e8 in ?? () from
/usr/lib64/pulseaudio/libpulsecommon-11.1.so
#7  0x7fc6efb29744 in start_thread () from /lib64/libpthread.so.0
#8  0x7fc6f5566aad in clone () from /lib64/libc.so.6

Thread 18 (Thread 0x7fc689ffb700 (LWP 19945)):
#0  0x7fc6f5572eab in __lll_lock_wait_private () from /lib64/libc.so.6
#1  0x7fc6f5574a46 in __fprintf_chk () from /lib64/libc.so.6
#2  0x7fc6db2a2fdf in ?? () from /usr/lib64/libevent-2.0.so.5
#3  0x7fc6db2a31b7 in event_warn () from /usr/lib64/libevent-2.0.so.5
#4  0x7fc6db2a7468 in ?? () from /usr/lib64/libevent-2.0.so.5
#5  0x7fc6db293477 in event_base_loop () from /usr/lib64/libevent-2.0.so.5
#6  0x7fc6e659e4ae in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7fc6e659a262 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7fc6e65b5a98 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#9  0x7fc6e65cd6b6 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#10 0x7fc6e65c996d in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#11 0x7fc6efb29744 in start_thread () from /lib64/libpthread.so.0
#12 0x7fc6f5566aad in clone () from /lib64/libc.so.6

Thread 17 (Thread 0x7fc68a7fc700 (LWP 19944)):
#0  0x7fc6efb2e0bf in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc6e65c200a in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fc6e65c20c4 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#3  0x7fc6e659deed in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#4  0x7fc6e659a262 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#5  0x7fc6e65b5a98 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#6  0x7fc6e65cd6b6 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#7  0x7fc6e65c996d in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#8  0x7fc6efb29744 in start_thread () from /lib64/libpthread.so.0
#9  0x7fc6f5566aad in clone () from /lib64/libc.so.6

Thread 16 (Thread 0x7fc68affd700 (LWP 19943)):
#0  0x7fc6efb2e468 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fc6e65fa8e2 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fc6e65c209e in ?? () 

[kresources] [Bug 387462] New: Limiting the CalDav fetch period results in no items

2017-11-30 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387462

Bug ID: 387462
   Summary: Limiting the CalDav fetch period results in no items
   Product: kresources
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: groupdav
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

At the bottom of the dialog for manually configuring a CalDav resource, there
is a checkbox to limit the period from which to fetch items from the server.
The default is 3 months. No matter which value is entered there, when the box
is checked, no items are downloaded. Unchecking the box correctly downloads all
events.

kdepim-runtime 17.11.80-111.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kresources] [Bug 387461] New: DAV groupware resource configuration dialog broken

2017-11-30 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=387461

Bug ID: 387461
   Summary: DAV groupware resource configuration dialog broken
   Product: kresources
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: groupdav
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

In the first dialog that comes up when a new DAV groupware resource is created,
the buttons 'Next' and 'Back' are always disabled, no matter whether I enter
username and password or not. Strangely, hitting 'Cancel' takes me to the
dialog where I can manually configure the resource. Previously there was a list
from which I could select the server type to connect.

kdepim-runtime 17.11.80-111.2

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 384697] New: Mails are sent to the list's name rather than the addresses on the list

2017-09-14 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=384697

Bug ID: 384697
   Summary: Mails are sent to the list's name rather than the
addresses on the list
   Product: kmail2
   Version: 5.6.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

When an email is sent to a number of addresses, kmail allows one to save these
addresses as a list (using kontact, I guess). This is a very nice feature,
which doesn't work properly though. For if one selects this list as the
recipient of a new email, it is not replaced by the addresses on the list.
Instead, the email is (wrongly) sent to the name of the list.
My solution is to select each entry on the list seperately and add it as a
recipient, but this almost abandons the advantage of having lists. And don't
try to select several addresses at the list; it will crash the program.

(openSuSE Leap 42.3)

-- 
You are receiving this mail because:
You are watching all bug changes.

[korganizer] [Bug 336490] new journal is not created due to lack of the calendar, although events and to-do's are ok and calendar (google) exist

2017-09-12 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=336490

Metko <metkome...@gmail.com> changed:

   What|Removed |Added

 CC||metkome...@gmail.com

--- Comment #7 from Metko <metkome...@gmail.com> ---
Same here (openSUSE leap 42.3, korganizer 17.08.1). I use a DAV Groupware
resource and a web calendar. If I make the web calendar writable, I can select
it in the dialog for entering new journal entries. But the DAV resource does
not show up in the list. I know that it worked half a year ago.

What do you mean by "Now, when I built the new installation and did not have
time to delete the "personal calendar" journal started to work!"? Do your other
calendars show up in the list, or only the personal calendar?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 384464] New: Message window does not display Chinese characters

2017-09-07 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=384464

Bug ID: 384464
   Summary: Message window does not display Chinese characters
   Product: kmail2
   Version: 5.6.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

Chinese characters are not displayed in KMail's message window. I tried all
possible encodings (from the display menu) and different fonts, in particular
Chinese character fonts that display alright in every other KDE application.

Whe I answer the email, the cited text looks correct, so it's a problem of the
message viewer only (and not the composer window).

You can replicate it by sending yourself a message with some Chinese characters
from a webpage, for example.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 383840] DAV resource crashes kontact

2017-08-24 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=383840

Metko <metkome...@gmail.com> changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 383840] DAV resource crashes kontact

2017-08-24 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=383840

Metko <metkome...@gmail.com> changed:

   What|Removed |Added

  Component|general |calendar

--- Comment #1 from Metko <metkome...@gmail.com> ---
P.S.: The problem may be more related to displaying events in the standard
calendar rather than fetching them through the DAV resource. Two arguments: 1)
In aconadiconsole, which probably uses the same resource, the calendar items
look alright. 2) When clicking on the eye icon next to the calendar in
kontact/korganizer (with the resource itself disabled), the calendar also shows
alright in the pop-up window that appears. Only if the resource is enabled (in
the checkbox at the left), the program crashes.

-- 
You are receiving this mail because:
You are watching all bug changes.

[marble] [Bug 379284] Marble 2.2 (KDE Apps 17.*) doesn't find any of its maps, routers, plugins

2017-08-24 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=379284

Metko <metkome...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 383840] New: DAV resource crashes kontact

2017-08-22 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=383840

Bug ID: 383840
   Summary: DAV resource crashes kontact
   Product: kontact
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

Application: kontact (5.6.0)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.4.79-19-default x86_64
Distribution: "openSUSE Leap 42.3"

-- Information about the crash:
Switching from mail to calendar in contact, after a few seconds the application
crashes. Manually removing the DAV resource makes the calendar operational
again, but without the remote calendar of course. I can recreate the DAV
resource (for accessing an owncloud calendar) in the calendar, but as soon as I
switch to another program in kontact (e.g., mail) and back to the clanedar, it
crashes again.

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7d970bd780 (LWP 5096))]

Thread 28 (Thread 0x7f7c4bac4700 (LWP 5168)):
#0  0x7f7d93afa20d in poll () at /lib64/libc.so.6
#1  0x7f7d8db1d314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f7d8db1d42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f7d9461713b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f7d945c4c2b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d9440902a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d9440d74d in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f7d8fad4744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f7d93b02aad in clone () at /lib64/libc.so.6

Thread 27 (Thread 0x7f7c54145700 (LWP 5152)):
#0  0x7f7d93afa20d in poll () at /lib64/libc.so.6
#1  0x7f7d8db1d314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f7d8db1d42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f7d9461713b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f7d945c4c2b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d9440902a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d9440d74d in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f7d8fad4744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f7d93b02aad in clone () at /lib64/libc.so.6

Thread 26 (Thread 0x7f7c666ad700 (LWP 5130)):
#0  0x7f7d8db5e899 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f7d8db1c969 in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7f7d8db1d230 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7f7d8db1d42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7f7d9461713b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7f7d945c4c2b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7f7d9440902a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7f7d9440d74d in  () at /usr/lib64/libQt5Core.so.5
#8  0x7f7d8fad4744 in start_thread () at /lib64/libpthread.so.0
#9  0x7f7d93b02aad in clone () at /lib64/libc.so.6

Thread 25 (Thread 0x7f7c66eae700 (LWP 5129)):
#0  0x7f7d8db5e8b4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0
#1  0x7f7d8db1d1cd in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f7d8db1d42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f7d9461713b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f7d945c4c2b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d9440902a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d9440d74d in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f7d8fad4744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f7d93b02aad in clone () at /lib64/libc.so.6

Thread 24 (Thread 0x7f7c67d32700 (LWP 5128)):
#0  0x7f7d93afa20d in poll () at /lib64/libc.so.6
#1  0x7f7d8db1d314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7f7d8db1d42c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7f7d9461713b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7f7d945c4c2b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7f7d9440902a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7f7d9440d74d in  () at /usr/lib64/libQt5Core.so.5
#7  0x7f7d8fad4744 in start_thread () at /lib64/libpthread.so.0
#8  0x7f7d93b02aad in clone () at /lib64/libc.so.6

Thread 23 (Thread 0x7f7d1dffb700 (LWP 5127)):
#0  0x7f7d8fad90bf in pthread_cond_wait@@GLIBC_2.3.2 

[kmail2] [Bug 368350] folder full text search doesn't work : folder status always 'still not indexed'

2017-04-27 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=368350

Metko <metkome...@gmail.com> changed:

   What|Removed |Added

 CC||metkome...@gmail.com

--- Comment #9 from Metko <metkome...@gmail.com> ---
(In reply to Laurent Montel from comment #6)
> We fixed a lot of bug about it in 5.5.0.
> Could you test it please ?
> Regards

Version 5.5.0 (from KDE Applications 17.04) has the same problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[marble] [Bug 379284] New: Marble 2.2 (KDE Apps 17.*) doesn't find any of its maps, routers, plugins

2017-04-27 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=379284

Bug ID: 379284
   Summary: Marble 2.2 (KDE Apps 17.*) doesn't find any of its
maps, routers, plugins
   Product: marble
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: marble-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

On openSuSE 42.2, marble 2.2 (any of the KDE Applications 17 series) seems to
not find its data directories: There are no (default) maps (one can install new
ones though), no routing services and no plugins. Command line output is:

inotify_add_watch("/maps") failed: "No such file or directory"
Map theme file does not exist: ""
No plugins loaded. Please check if the plugins were installed in the correct
path, or if any errors occurred while loading plugins.
Start: MarblePart::readSettings()
Updating Settings ...
Shortcut for action  "" "Hide  Panels" set with QAction::setShortcut()! Use
KActionCollection::setDefaultShortcut(s) instead.

Version 2.0.2 (from KDE Applications 16.08) worked perfectly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[akregator] [Bug 377607] New: Akregator minimum window width spans half the screen

2017-03-14 Thread Metko
https://bugs.kde.org/show_bug.cgi?id=377607

Bug ID: 377607
   Summary: Akregator minimum window width spans half the screen
   Product: akregator
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: metkome...@gmail.com
  Target Milestone: ---

No matter which view mode is selected, I can't get the window narrower than 989
px, which takes half the screen on a 1920x1200 monitor. Interestingly the
individual panels (sources, article view etc.) can be made quite narrow, but
the application window itself can not. Could somebody please check the setting
for the window's minimum width? This also affects the window width when
akregator is run as a component in kontact.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 362258] regression: drop file in composer no longer adds attachment or asks what to do

2016-07-25 Thread Metko via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=362258

Metko <metkome...@gmail.com> changed:

   What|Removed |Added

 CC||metkome...@gmail.com

--- Comment #3 from Metko <metkome...@gmail.com> ---
Same here - trying to attach a file to an email by drag or copy/paste from
dolphin or konqueror inserts the URI instead of the file. Very annoying.
OpenLeap 42.1 , kmail 15.12.3,

-- 
You are receiving this mail because:
You are watching all bug changes.


[Akonadi] [Bug 255388] Kmail filters dont work in incoming mail

2016-03-30 Thread Metko via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=255388

Metko <metkome...@gmail.com> changed:

   What|Removed |Added

 CC||metkome...@gmail.com

--- Comment #109 from Metko <metkome...@gmail.com> ---
When kmail (5.1.2) is started after login (Leap 42.1), no filter is applied and
all new emails remain in the inbox folder (very annoying). Even manual
filtering and Ctrl+J don't work. My standard procedure then is to just open the
filter settings dialog (Einstellungen|Filter einrichten...) and close it
immediately with Ok, i.e. without changing anything. From then on filtering
works as expected. It seems like the whole filtering mechanism is only started
upon firing up the configuration dialog. Couldn't find this in the previous
comments, so maybe it's a clue for the developers.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Akonadi] [Bug 325224] CalDav doesn't read server items

2016-01-18 Thread Metko via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=325224

--- Comment #46 from Metko <metkome...@gmail.com> ---
I've been commenting on the DAVGroupware resource and its access to an owncloud
server via CalDAV. It seems that you try to get the iCal resource to work
(webcal://, http://). This one doesn't work for me either. It does work for
local files, but I can't subscribe to remote .ics files. But probably this is
the wrong thread to complain about this as it is explicitly on CalDAV.

-- 
You are receiving this mail because:
You are watching all bug changes.