[systemsettings] [Bug 157272] disable system notification for all applications should be possible (as in kde 3.5.x) (disable sounds for all apps)

2016-07-15 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=157272

--- Comment #27 from Jan-Matthias Braun  ---
Sooo... sorry for going against the line here, but I do not think, that this
button resolves the issue, just follows the suggestion from comment 8. As new
events pop up from time from time, and some have a default sound set, this does
not "disable system notification for all applications".

Such an option would hopefully suppress all sounds set in new events, too.
Probably not by removing the configured sound, but by just never playing any
sounds for notifications.

My opinion. Still thanks for the button!

Jan

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

[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds

2016-07-04 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363741

--- Comment #13 from Jan-Matthias Braun  ---
it looks like my problem is somehow related to akonadi/kmail producing and not
coping with invalid xapian searches.

Right now, I have not seen another akonadi crash. The search that was crashing
akonadi had a debug output representation (using the qdebug overload of
operator << on term()) over half a screen, i.e., many lines with many many
columns. I have no Idea where it came from -- and now it is gone.

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

[Akonadi] [Bug 363741] akonadi server 16.04.2: crashing every few seconds

2016-07-04 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363741

--- Comment #12 from Jan-Matthias Braun  ---
Okay, I was able to remove a very reproducible crash (with the above mentioned
segfault) during startup of akonadi (without any client running) by removing a
search from the search folder in kmail. Since then, it is running for at least
eight minutes (!) now and I haven't seen a SEGV up to now.

By the way, is it normal, that different searches have the same name? In the
logs I am seeing the
Executing search "foo-1186278907-bar"
lines. And the crashing search had the same name, as the search running before,
which was much, much simpler. And checking now I see, that different searches
often have the same search name in the logs, although from time to time the
name seems to change.

Revisiting older logs, the crash always happend with a reused search-name. But
I cannot tell if it was the same search, always, because only now I went to
instrument the code around the backtrace end in the akonadi-search code
(xapian/xapiansearchstore.cpp:177) with lots of output.

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

[Akonadi] [Bug 363741] akonadi server 16.04.1: crashing every few seconds

2016-07-01 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363741

--- Comment #11 from Jan-Matthias Braun  ---
I do see the same backtrace for xapian 1.3.7.

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

[Akonadi] [Bug 363741] akonadi server 16.04.1: crashing every few seconds

2016-07-01 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363741

--- Comment #10 from Jan-Matthias Braun  ---
Ok, I have seen this one three times in a row, now,

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

[Akonadi] [Bug 363741] akonadi server 16.04.1: crashing every few seconds

2016-07-01 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363741

--- Comment #9 from Jan-Matthias Braun  ---
Connecting into the running process indeed provides a better backtrace,
although -- why? :-)

Here it is:
#0  0x in ?? ()
#1  0x7f6ef42d333b in ExternalPostList::ExternalPostList
(this=0x7f6f0835a170, db=..., source_=, factor_=, 
matcher=0x7f6f137fcd30) at matcher/externalpostlist.cc:40
#2  0x7f6ef41e6d6b in Xapian::Internal::QueryPostingSource::postlist
(this=, qopt=0x7f6f137fc650, factor=1)
at api/queryinternal.cc:739
#3  0x7f6ef41e50a1 in Xapian::Query::Internal::postlist_sub_xor
(this=, ctx=..., qopt=, 
factor=) at api/queryinternal.cc:634
#4  0x7f6ef41e6553 in Xapian::Internal::QueryBranch::do_or_like
(this=this@entry=0x7f6f0807b490, ctx=..., 
qopt=qopt@entry=0x7f6f137fc650, factor=factor@entry=1,
elite_set_size=elite_set_size@entry=0, first=first@entry=1)
at api/queryinternal.cc:1186
#5  0x7f6ef41e6b1a in Xapian::Internal::QueryAndMaybe::postlist
(this=0x7f6f0807b490, qopt=0x7f6f137fc650, factor=1)
at api/queryinternal.cc:1550
#6  0x7f6ef42d35fa in LocalSubMatch::get_postlist (this=0x7f6f0807af50,
matcher=0x7f6f137fcd30, total_subqs_ptr=0x7f6f137fc7bc)
at matcher/localsubmatch.cc:204
#7  0x7f6ef42d9a51 in MultiMatch::get_mset (this=this@entry=0x7f6f137fcd30,
first=first@entry=0, maxitems=10, 
check_at_least=check_at_least@entry=10, mset=..., stats=...,
mdecider=0x0, sorter=0x0) at matcher/multimatch.cc:419
#8  0x7f6ef41d55e1 in Xapian::Enquire::Internal::get_mset
(this=0x7f6f0807ad10, first=, maxitems=, 
check_at_least=, check_at_least@entry=0,
rset=rset@entry=0x0, mdecider=0x0) at api/omenquire.cc:548
#9  0x7f6ef41d5924 in Xapian::Enquire::get_mset
(this=this@entry=0x7f6f137fd050, first=, maxitems=, 
check_at_least=check_at_least@entry=0, rset=rset@entry=0x0, mdecider=0x0)
at api/omenquire.cc:906
#10 0x7f6ee05e968d in Akonadi::Search::XapianSearchStore::exec
(this=0x7f6ef009bf50, query=...)
at
/var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./xapian/xapiansearchstore.cpp:177
#11 0x7f6f12df8065 in Akonadi::Search::Query::exec
(this=this@entry=0x7f6f137fd2c0)
at
/var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./core/query.cpp:252
#12 0x7f6f180fff7d in SearchPlugin::search (this=,
akonadiQuery=..., collections=..., mimeTypes=...)
at
/var/tmp/portage/kde-apps/akonadi-search-16.04.49./work/akonadi-search-16.04.49./akonadiplugin/searchplugin.cpp:348
#13 0x0055b4eb in Akonadi::Server::SearchRequest::searchPlugins
(this=this@entry=0x7f6f137fd900)
at
/var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchrequest.cpp:112
#14 0x0055b893 in Akonadi::Server::SearchRequest::exec
(this=this@entry=0x7f6f137fd900)
at
/var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchrequest.cpp:123
#15 0x00444788 in Akonadi::Server::SearchManager::updateSearchImpl
(this=0x27003f0, collection=..., cond=)
at
/var/tmp/portage/kde-apps/akonadi-16.04.49./work/akonadi-16.04.49./src/server/search/searchmanager.cpp:350
#16 0x7f6f1f8deaa9 in QObject::event (this=0x27003f0, e=) at
kernel/qobject.cpp:1263
#17 0x7f6f1f8b2b5b in doNotify (event=0x7f6f08031ea0, receiver=0x27003f0)
at kernel/qcoreapplication.cpp:1063
#18 QCoreApplication::notify (event=, receiver=,
this=) at kernel/qcoreapplication.cpp:1049
#19 QCoreApplication::notifyInternal2 (receiver=0x27003f0,
event=event@entry=0x7f6f08031ea0) at kernel/qcoreapplication.cpp:988
#20 0x7f6f1f8b526b in QCoreApplication::sendEvent (event=0x7f6f08031ea0,
receiver=) at kernel/qcoreapplication.h:231
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0,
event_type=event_type@entry=0, data=0x2700600)
at kernel/qcoreapplication.cpp:1649
#22 0x7f6f1f8b56d8 in QCoreApplication::sendPostedEvents
(receiver=receiver@entry=0x0, event_type=event_type@entry=0)
at kernel/qcoreapplication.cpp:1503
#23 0x7f6f1f9063f3 in postEventSourceDispatch (s=0x7f6f080012d0) at
kernel/qeventdispatcher_glib.cpp:276
#24 0x7f6f1dd2eb17 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#25 0x7f6f1dd2f4f8 in g_main_context_iterate.isra () from
/usr/lib64/libglib-2.0.so.0
#26 0x7f6f1dd2f68c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#27 0x7f6f1f9067ff in QEventDispatcherGlib::processEvents
(this=0x7f6f080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x7f6f1f8b0b1a in QEventLoop::exec (this=this@entry=0x7f6f137fde80,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#29 0x7f6f1f6d2214 in QThread::exec (this=) at
thread/qthread.cpp:507
#30 0x7f6f1f6d6e78 in QThreadPrivate::start (arg=0x27004c0) at
thread/qthread_unix.cpp:344
#31 0x7f6f1ee5c434 in

[Akonadi] [Bug 363741] akonadi server 16.04.1: crashing every few seconds

2016-06-30 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363741

Jan-Matthias Braun  changed:

   What|Removed |Added

 CC||jan_br...@gmx.net

--- Comment #8 from Jan-Matthias Braun  ---
Hi!

I am seeing similar behaviour since 16.04.x, and checked up to 16.04.2 and
16.04-git.
I am using qt 5.7, xapian 1.4, frameworks 5.23, and mariadb 10.1.14 on gentoo,
too.

One of my backtraces looks like this and is only partially usable:
0: akonadiserver() [0x4ac960]
1: akonadiserver() [0x4acc5f]
2: /lib64/libc.so.6(+0x33250) [0x7f025e5b3250]
3: /usr/lib64/libxapian.so.30(+0x1b2508) [0x7f0248531508]
4: /usr/lib64/libxapian.so.30(+0x7554b) [0x7f02483f454b]
5:
/usr/lib64/libxapian.so.30(_ZNK6Xapian5Query8Internal20postlist_sub_or_likeERNS_8Internal9OrContextEP14QueryOptimiserd+0x21)
[0x7f02483f1e21]
6: /usr/lib64/libxapian.so.30(+0x745a3) [0x7f02483f35a3]
7: /usr/lib64/libxapian.so.30(+0x74e1a) [0x7f02483f3e1a]
8: /usr/lib64/libxapian.so.30(+0x1b266a) [0x7f024853166a]
9: /usr/lib64/libxapian.so.30(+0x1c2991) [0x7f0248541991]
10:
/usr/lib64/libxapian.so.30(_ZNK6Xapian7Enquire8Internal8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE+0x1c1)
[0x7f02483dd8f1]
11:
/usr/lib64/libxapian.so.30(_ZNK6Xapian7Enquire8get_msetEjjjPKNS_4RSetEPKNS_12MatchDeciderE+0x24)
[0x7f02483ddc34]
12:
/usr/lib64/libKF5AkonadiSearchXapian.so.5(_ZN7Akonadi6Search17XapianSearchStore4execERKNS0_5QueryE+0x8b6)
[0x7f02481725d6]
13:
/usr/lib64/libKF5AkonadiSearchCore.so.5(_ZN7Akonadi6Search5Query4execEv+0x245)
[0x7f0258235a55]
14: /usr/lib64/qt5/plugins/akonadi/akonadi_search_plugin.so(+0x400c)
[0x7f025844000c]
15: akonadiserver() [0x4cba6f]
16: akonadiserver() [0x44aaa8]
17: akonadiserver() [0x4835d0]
18: /usr/lib64/libQt5Core.so.5(_ZN7QObject5eventEP6QEvent+0xe9)
[0x7f025e085aa9]
19:
/usr/lib64/libQt5Core.so.5(_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent+0xfb)
[0x7f025e059b5b]
20:
/usr/lib64/libQt5Core.so.5(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x2db)
[0x7f025e05c26b]
21: /usr/lib64/libQt5Core.so.5(+0x2de3f3) [0x7f025e0ad3f3]
22: /usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x297) [0x7f025c86eb17]
23: /usr/lib64/libglib-2.0.so.0(+0x294f8) [0x7f025c86f4f8]
24: /usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f025c86f68c]
25:
/usr/lib64/libQt5Core.so.5(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x5f)
[0x7f025e0ad7ff]
26:
/usr/lib64/libQt5Core.so.5(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xfa)
[0x7f025e057b1a]
27: /usr/lib64/libQt5Core.so.5(_ZN7QThread4execEv+0xb4) [0x7f025de79214]
28: /usr/lib64/libQt5Core.so.5(+0xaee78) [0x7f025de7de78]
29: /lib64/libpthread.so.0(+0x7434) [0x7f025d99c434]
30: /lib64/libc.so.6(clone+0x6d) [0x7f025e667ded]

Now I have installed all debug symbols, but now I can only see mini-backtraces
with even less information:
0: akonadiserver() [0x572666]
1: akonadiserver() [0x572982]
2: /lib64/libc.so.6(+0x33250) [0x7fa0e1fe9250]

which leaves me at a loss for useful info. (I am not even getting dr konqi, I
have to grab the debug info from the akonadi logs.)

I am using a bunch of imap-servers including one akonadi-ews account. I have
contacts and calendars in owncloud. These seem to get disabled all the while.

What can I do to improve debugging information?

Cheers,

Jan

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

[amarok] [Bug 333745] Amarok exports unreadable playlists for other players...

2016-05-19 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=333745

--- Comment #18 from Jan-Matthias Braun  ---
Created attachment 99086
  --> https://bugs.kde.org/attachment.cgi?id=99086=edit
Fix the encoding in m3u exports using QUrl::path().

I had no luck using the FullyDecode-flag when using toString(), the flags were
only partially removed. While I would prefer to have full urls, I am now using
path(). With path(), the %-encodings are removed (FullyDecode is the default
for this function).
The m3u-exporter seems to check if the track is a file or not, thus the patch
should not change stream urls. But for other exporters, this check would have
to be implemented.

Probably, this helps developers who know what they are doing. :-)

Cheers,

Jan

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

[amarok] [Bug 333745] Amarok exports unreadable playlists for other players...

2016-05-19 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=333745

Jan-Matthias Braun  changed:

   What|Removed |Added

 CC||jan_br...@gmx.net

--- Comment #17 from Jan-Matthias Braun  ---
Created attachment 99076
  --> https://bugs.kde.org/attachment.cgi?id=99076=edit
Non-problem-solving ugly script to remove the url quoting.

Hi!

I would describe this attachment as non-helpful in terms of solving the
problem. But it will take a problematic m3u and overwrite (ignorantly write)
another file with the suffix "_unquoted.m3u" without any checks. So no
guarantees whatsoever.

If I had time to dig into the problem---but python is so awfully convenient...

Cheers,

Jan

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

[systemsettings] [Bug 157272] disable system notification for all applications should be possible (as in kde 3.5.x) (disable sounds for all apps)

2016-05-17 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=157272

--- Comment #23 from Jan-Matthias Braun  ---
Thanks David, this will make fighting the state of art a lot easier!

But I have a question/remark: So this button will only disable currently
activated sounds? It will not disable sound-output for the application in
general? This means, if a new event gets defined and has a default sound
configured, then it will not be disabled?

I want to make a statement for a general solution to silence notifications, as
there are situations when you do want to be able to play sounds, but do
generally not want your applications to be noisy. In my special use case this
covers every situation -- granted, others might be more selective. And every
now and then, I do notice in the worst possible circumstances, that a new audio
notification was created and enabled by default, which I have to search for
manually to be able to disable it.

Therefore, disabling all sounds with a button makes working against the
mechanism easier, but it is not a solution if sound notifications are generally
not acceptable (e.g., in offices or conference rooms with other people) and
muting the whole system is neither a solution.

I understand, that the current setup does not allow to suppress all audio
notifications at once?
Would one have to patch every single application? I would have assumed, that
all KDE applications use the same API for notifications, so that a global
enable/disable flag should be possible. Does someone already know where to
look?

Cheers,

Jan

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

[frameworks-ki18n] [Bug 363111] ki18n 5.22.0 compile fails with 'translation_found' was not declared in this scope

2016-05-15 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363111

Jan-Matthias Braun  changed:

   What|Removed |Added

  Attachment #98998|0   |1
is obsolete||

--- Comment #1 from Jan-Matthias Braun  ---
Created attachment 98999
  --> https://bugs.kde.org/attachment.cgi?id=98999=edit
Patch v2: make the first use of translation_found the definition.

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

[frameworks-ki18n] [Bug 363111] New: ki18n 5.22.0 compile fails with 'translation_found' was not declared in this scope

2016-05-15 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=363111

Bug ID: 363111
   Summary: ki18n 5.22.0 compile fails with 'translation_found'
was not declared in this scope
   Product: frameworks-ki18n
   Version: 5.22.0
  Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: caslav.i...@gmx.net
  Reporter: jan_br...@gmx.net
CC: kdelibs-b...@kde.org

Created attachment 98998
  --> https://bugs.kde.org/attachment.cgi?id=98998=edit
Fix the compile by moving the definition before the #ifdef.

The variable translation_found is defined in the else branch of the #ifdef
_LIBGETTEXT_HAVE_VARIABLE_SIZE_ARRAYS block in gettext.h before line 180, but
used unconditionally in line 180.

The compile fails with
/var/tmp/portage/kde-frameworks/ki18n-5.22.0/work/ki18n-5.22.0/src/gettext.h:180:9:
error: 'translation_found' was not declared in this scope
 translation_found = !(translation == msg_ctxt_id || translation ==
msgid_plural);
 ^

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

[Akonadi] [Bug 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders

2016-02-22 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=351814

--- Comment #28 from Jan-Matthias Braun  ---
Okay, I think I have answered my own question: It is there and therefore I
should better open a new but.

Please excuse the noise... :-/

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

[Akonadi] [Bug 351814] Kmail 15.08 will not sync Outlook365 IMAP Folders

2016-02-21 Thread Jan-Matthias Braun via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=351814

--- Comment #27 from Jan-Matthias Braun  ---
Hi! I do have the impression that this issue came back with 15.12.: My outlook
imap is not syncing anymore. 

Does somebody else see the same behaviour? Can the fix somehow have evaded
going into 15.12 or should I open a new bug report?

All the best,

Jan

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