[korganizer] [Bug 404679] Korganizer crashes on startup

2019-02-26 Thread Kishore Gopalakrishnan
https://bugs.kde.org/show_bug.cgi?id=404679

--- Comment #1 from Kishore Gopalakrishnan  ---
With debug symbols for qt5

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

Thread 5 (Thread 0x7f7b9edee700 (LWP 31220)):
#0  0x7f7bae84c7a4 in read () from /usr/lib/libc.so.6
#1  0x7f7baa409971 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f7baa45a0b0 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7f7baa45b4e6 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7f7baa45b62e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7f7baed9fd04 in QEventDispatcherGlib::processEvents
(this=0x7f7b8c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x7f7baed48b2c in QEventLoop::exec (this=this@entry=0x7f7b9ededd60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7f7baeb8c569 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7f7baeb8d96c in QThreadPrivate::start (arg=0x558b3fc35710) at
thread/qthread_unix.cpp:361
#9  0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0
#10 0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0x7f7b9f5ef700 (LWP 31213)):
#0  0x7f7bae850c21 in poll () from /usr/lib/libc.so.6
#1  0x7f7baa45b540 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f7baa45b62e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#3  0x7f7baed9fd04 in QEventDispatcherGlib::processEvents
(this=0x7f7b94000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f7baed48b2c in QEventLoop::exec (this=this@entry=0x7f7b9f5eed60,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#5  0x7f7baeb8c569 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#6  0x7f7baeb8d96c in QThreadPrivate::start (arg=0x558b3fbb4d20) at
thread/qthread_unix.cpp:361
#7  0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0
#8  0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0x7f7ba4995700 (LWP 31208)):
#0  0x7f7bae84c7a4 in read () from /usr/lib/libc.so.6
#1  0x7f7baa409971 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x7f7baa45a0b0 in g_main_context_check () from
/usr/lib/libglib-2.0.so.0
#3  0x7f7baa45b4e6 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x7f7baa45b62e in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#5  0x7f7baed9fd04 in QEventDispatcherGlib::processEvents
(this=0x7f7b98000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x7f7baed48b2c in QEventLoop::exec (this=this@entry=0x7f7ba4994d30,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:140
#7  0x7f7baeb8c569 in QThread::exec (this=this@entry=0x7f7bae541080
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
../../include/QtCore/../../src/corelib/global/qflags.h:120
#8  0x7f7bae4c5ba6 in QDBusConnectionManager::run (this=0x7f7bae541080
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#9  0x7f7baeb8d96c in QThreadPrivate::start (arg=0x7f7bae541080 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:361
#10 0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0
#11 0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0x7f7ba5b5c700 (LWP 31207)):
#0  0x7f7bae850c21 in poll () from /usr/lib/libc.so.6
#1  0x7f7baa3d0630 in ?? () from /usr/lib/libxcb.so.1
#2  0x7f7baa3d22db in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#3  0x7f7ba6711949 in QXcbEventQueue::run (this=0x558b3fae4a60) at
qxcbeventqueue.cpp:228
#4  0x7f7baeb8d96c in QThreadPrivate::start (arg=0x558b3fae4a60) at
thread/qthread_unix.cpp:361
#5  0x7f7baca57a9d in start_thread () from /usr/lib/libpthread.so.0
#6  0x7f7bae85bb23 in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f7ba6b77200 (LWP 31206)):
[KCrash Handler]
#6  std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x51) at
/usr/include/c++/8.2.1/bits/atomic_base.h:390
#7  QAtomicOps::load (_q_value=...) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:227
#8  QBasicAtomicInteger::load (this=0x51) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:103
#9  QtPrivate::RefCount::ref (this=0x51) at
../../include/QtCore/../../src/corelib/tools/qrefcount.h:55
#10 QString::QString (other=..., this=0x7fffd9d9ce90) at
../../include/QtCore/../../src/corelib/tools/qstring.h:958
#11 QTimeZonePrivate::Data::Data (this=0x7fffd9d9ce90) at
tools/qtimezoneprivate_p.h:81
#12 QTzTimeZonePrivate::previousTransition (this=0x558b3fc4ad90,
beforeMSecsSinceEpoch=2879) at 

[kmail2] [Bug 404863] New: KMail should use UTF-8 as default encoding

2019-02-26 Thread Aurélien Murith
https://bugs.kde.org/show_bug.cgi?id=404863

Bug ID: 404863
   Summary: KMail should use UTF-8 as default encoding
   Product: kmail2
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: composer
  Assignee: kdepim-bugs@kde.org
  Reporter: aurelien.mur...@net-c.be
  Target Milestone: ---

Unless you manually change the encoding settings, KMail will send messages
using US-ASCII if possible, then ISO-8859-1 and will only use UTF-8 when using
ISO-8859-1 is not possible.

Since UTF-8 has been a de facto standard for years, the use of ISO-8859-1
sometimes causes a few problems. For example, I regularly send messages to a
mailing list. The list server automatically adds a few lines of text at the
bottom of my messages, using UTF-8 encoding. The result is that those added
lines appear broken, because their encoding does not match the one of my
messages, which is ISO-8859-1.

I cannot see why it would be better to keep using ISO-8859-1 instead of UTF-8,
so I think KMail should now default to UTF-8. This is what most other mail
clients do.

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

[kontact] [Bug 222878] kontact process does not exit after closing kontact window in every case

2019-02-26 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=222878

boris.big...@hotmail.com changed:

   What|Removed |Added

 CC||boris.big...@hotmail.com

--- Comment #40 from boris.big...@hotmail.com ---
Still happens with kontact 5.10.2 using kde frameworks 5.55.0.

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

[kontact] [Bug 404765] left click on a link => kontact-akregator crash

2019-02-26 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=404765

Wolfgang Bauer  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||wba...@tmo.at
 Resolution|--- |DUPLICATE

--- Comment #1 from Wolfgang Bauer  ---
Same backtrace as bug#399570:

(In reply to Philippe ROUBACH from comment #0)
> Thread 1 (Thread 0x7fc20fd95900 (LWP 8015)):
> [KCrash Handler]
> #6  QString::isNull (this=0x68) at /usr/include/qt5/QtCore/qstring.h:822
> #7  QtWebEngineCore::ProfileAdapter::httpUserAgent (this=0x0) at
> /usr/src/debug/libqt5-qtwebengine-5.12.1-lp150.3.1.x86_64/src/core/
> profile_adapter.cpp:287
> #8  0x7fc1fb87ddd8 in QtWebEngineCore::WebContentsAdapter::initialize
> (this=this@entry=0x5562d519e930, site=site@entry=0x0) at
> /usr/src/debug/libqt5-qtwebengine-5.12.1-lp150.3.1.x86_64/src/core/
> web_contents_adapter.cpp:470
> #9  0x7fc1fb87e62c in QtWebEngineCore::WebContentsAdapter::loadDefault
> (this=this@entry=0x5562d519e930) at
> /usr/src/debug/libqt5-qtwebengine-5.12.1-lp150.3.1.x86_64/src/core/
> web_contents_adapter.cpp:568

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

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

[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab

2019-02-26 Thread Wolfgang Bauer
https://bugs.kde.org/show_bug.cgi?id=399570

Wolfgang Bauer  changed:

   What|Removed |Added

 CC||philippe.roub...@free.fr

--- Comment #4 from Wolfgang Bauer  ---
*** Bug 404765 has been marked as a duplicate of this bug. ***

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

[kmail2] [Bug 404850] New: Archiving of mails in kmail folders doesn't work - collection does not exist

2019-02-26 Thread piedro
https://bugs.kde.org/show_bug.cgi?id=404850

Bug ID: 404850
   Summary: Archiving of mails in kmail folders doesn't work -
collection does not exist
   Product: kmail2
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-bugs@kde.org
  Reporter: piedro.kul...@gmail.com
  Target Milestone: ---

SUMMARY

The attempt to archive even a single mail does result in a "collection does not
exist" error.



STEPS TO REPRODUCE
1. create a fresh user account with default settings 
2. add an standard email account (also apllies to gmail accounts) 
3. right click on any message in any folder and chose archive (make sure you've
set an accessible archive folder before!)

OBSERVED RESULT
you get a  notification saying "Collection can't be fetched. collection doesn't
exist." 

EXPECTED RESULT
Obviously: move mail to designated archive folder


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: Arch linux, fully updated 
(available in About System)
KDE Plasma Version: Plasma 5.15.1
KDE Frameworks Version: KDE 18.12.1 

Qt Version: 

ADDITIONAL INFORMATION

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

[Akonadi] [Bug 352502] .local/share/local-mail has to be the top level of local folders!

2019-02-26 Thread piedro
https://bugs.kde.org/show_bug.cgi?id=352502

--- Comment #4 from piedro  ---
Now this is still present and unsolved in KDE 18.12.1! 

Creating the hidden directory list OUTSIDE the designated local mail folder is
a serious bug. 

In connection with the bug of akonadi creating folders BEFORE the user confirms
or intentionally chooses the Mail folder location recreates empty directory
list folders over and over again and messes up the local folder in kmail. 

Because of this subfolders change their name, are recreated, disappear and get
moved within the system. It's the source of a whole bunch of problems people
complain about. 

Well as nobody seems to read these bug reports this will stay like this I
guess. 

And that's exactly one reason why kmail is unusable for many people cause you
can't even use an archive subfodler in local folders... 

Keep up the good work! 

p.

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

[kmail] [Bug 65954] crash: failed attempt to create imap folder on server creates orphan folder in folder treeview

2019-02-26 Thread weakbit
https://bugs.kde.org/show_bug.cgi?id=65954

weakbit  changed:

   What|Removed |Added

 CC||volker.h...@gmail.com

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

[akregator] [Bug 399570] Akregator crashes after clicking on link in an open tab

2019-02-26 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=399570

Christophe Giboudeaux  changed:

   What|Removed |Added

 CC||aus...@essex-tech.com

--- Comment #3 from Christophe Giboudeaux  ---
*** Bug 404815 has been marked as a duplicate of this bug. ***

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

[akregator] [Bug 404815] akgregator crashes when clicking a link in an article

2019-02-26 Thread Christophe Giboudeaux
https://bugs.kde.org/show_bug.cgi?id=404815

Christophe Giboudeaux  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Christophe Giboudeaux  ---
(partial) bt when following these steps:

#0  0x7fb1d2838f9f in QtWebEngineCore::ProfileAdapter::httpUserAgent()
const () from /usr/lib64/libQt5WebEngineCore.so.5
#1  0x7fb1d2861398 in
QtWebEngineCore::WebContentsAdapter::initialize(content::SiteInstance*) () from
/usr/lib64/libQt5WebEngineCore.so.5
#2  0x7fb1d286adb8 in ?? () from /usr/lib64/libQt5WebEngineCore.so.5

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

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