[plasmashell] [Bug 368431] New: Plasma crash

2016-09-07 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=368431

Bug ID: 368431
   Summary: Plasma crash
   Product: plasmashell
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: benjamin.slabb...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-42-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
restarted computer and plasma crashed. only second screen working. main (built
in) display not working.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa073f61800 (LWP 1692))]

Thread 3 (Thread 0x7fa05cf5e700 (LWP 1715)):
#0  0x7fa06e711b1d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fa06b4be1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa06b4be2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa06f03b29b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa06efe175a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa06edff3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa071627f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa06ee042be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa06def36aa in start_thread (arg=0x7fa05cf5e700) at
pthread_create.c:333
#9  0x7fa06e71d13d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fa04db20700 (LWP 1732)):
#0  0x7fa06e711b1d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7fa06b4be1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa06b4be2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa06f03b29b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa06efe175a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa06edff3d4 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa071627f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa06ee042be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa06def36aa in start_thread (arg=0x7fa04db20700) at
pthread_create.c:333
#9  0x7fa06e71d13d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fa073f61800 (LWP 1692)):
[KCrash Handler]
#6  0x7fa06e64b1c7 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:55
#7  0x7fa06e64ce2a in __GI_abort () at abort.c:89
#8  0x7fa06ea6fb7d in __gnu_cxx::__verbose_terminate_handler() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x7fa06ea6d9c6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x7fa06ea6da11 in std::terminate() () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x7fa06ea6e55f in __cxa_pure_virtual () from
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x7fa06f2f37ca in QPlatformScreen::physicalSize() const () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#13 0x7fa06f32c212 in QScreen::physicalSize() const () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#14 0x7fa06f32c2c9 in QScreen::physicalDotsPerInch() const () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#15 0x7fa07211bb6b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#16 0x7fa06f01478a in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x7fa06f309dbf in QWindow::screenChanged(QScreen*) () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#18 0x7fa06f30acb5 in QWindowPrivate::emitScreenChangedRecursion(QScreen*)
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x7fa06f30dcf3 in QWindowPrivate::setTopLevelScreen(QScreen*, bool) ()
from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#20 0x7fa06f30de85 in QWindow::screenDestroyed(QObject*) () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#21 0x7fa06f014617 in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7fa06f01502f in QObject::destroyed(QObject*) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7fa06f01c19a in QObject::~QObject() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7fa06f32c0c9 in QScreen::~QScreen() () from
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#25 0x7fa06f2f3d49 in

[rkward] [Bug 365174] New: Crashed on start

2016-07-06 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=365174

Bug ID: 365174
   Summary: Crashed on start
   Product: rkward
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: rkward-de...@kde.org
  Reporter: bwbe...@yahoo.com

Application: rkward (0.6.5)
KDE Platform Version: 4.14.21
Qt Version: 4.8.7
Operating System: Linux 4.6.3-300.fc24.x86_64 x86_64
Distribution: "Fedora release 24 (Twenty Four)"

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

I just clicked the icon to start the application and it crashed.  Nothing else
going on.

-- Backtrace:
Application: RKWard (rkward), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x7f6afcd48e50 in  ()
#7  0x7f6b23d6f3ef in QFactoryLoader::instance(QString const&) const () at
/lib64/libQtCore.so.4
#8  0x7f6b22aadce1 in QIcon::addFile(QString const&, QSize const&,
QIcon::Mode, QIcon::State) () at /lib64/libQtGui.so.4
#9  0x7f6b22aae02a in QIcon::QIcon(QString const&) () at
/lib64/libQtGui.so.4
#10 0x55dcac16017c in RKStandardIcons::initIcons() ()
#11 0x55dcac02bc54 in RKWardMainWindow::RKWardMainWindow() ()
#12 0x55dcac01 in main ()

Reported using DrKonqi

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

[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

2016-06-15 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=354056

Ben  changed:

   What|Removed |Added

 CC|c...@bnavigator.de  |

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

[KScreen] [Bug 353637] Cannot enable second monitor in Display Configuration

2016-05-14 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=353637

Ben  changed:

   What|Removed |Added

 CC||benja...@heisig.name

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

[KScreen] [Bug 360926] Waking up notebook after undocking from a multi-monitor setup creates an impossible kscreen configuration

2016-05-14 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=360926

Ben  changed:

   What|Removed |Added

 CC||benja...@heisig.name

--- Comment #4 from Ben  ---
I've recently experienced the same behavior on my Lenovo T-450s and a docking
station with Kubuntu 16.04 LTS (Plasma 5.5).

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

[kmymoney] [Bug 362384] Cannot enter transaction with postdate prior to account's opening date error

2016-04-27 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362384

--- Comment #2 from Ben  ---
(In reply to Jack from comment #1)
> The "account" can be either the account in which you are entering the
> transaction, or the category to which you are assigning the transaction. 
> Remember, KMM treats categories internally as accounts.  If you can change
> the category after entering the transaction, and the transaction date is
> prior to the opening date of the category, that should probably count as a
> bug.  Categories generally get opening dates of the date they were created,
> which does lead to this error.

Ahh, I didn't realize that. I don't know why a category would have a opening
date associated with it aka be treated like an account, but changing the date
of the category to an earlier date does seem to fix my problem, thnx!

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

[kmymoney] [Bug 362384] New: Cannot enter transaction with postdate prior to account's opening date error

2016-04-27 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=362384

Bug ID: 362384
   Summary: Cannot enter transaction with postdate prior to
account's opening date error
   Product: kmymoney
   Version: unspecified
  Platform: MS Windows
OS: MS Windows
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: kmymoney-de...@kde.org
  Reporter: wellness...@gmail.com

Trying to manually enter a few transactions into a liability account with an
opening date in 2008, but sometimes it won't let me, telling me that I "Cannot
enter transaction with postdate prior to account's opening date", which seems
to be happening for anything entered prior to 01/01/2016! I can get it to work
if I enter a new transaction, enter the payment 'date' and 'amount' first and
save it, and then go back and edit the 'from' and 'category' after the fact. If
I try to enter all 4 at once, I get the error and can't save the transaction.

Reproducible: Sometimes

Steps to Reproduce:
See above.

Actual Results:  
See above.

Expected Results:  
Allow me to enter all transactions after account open date in 2008!

None.

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

[Akonadi] [Bug 351701] akonadi resources doesn't wait for kwallet5 with gpg key to open in 15.08.0

2016-03-22 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=351701

Ben  changed:

   What|Removed |Added

 CC||c...@bnavigator.de

--- Comment #2 from Ben  ---
I think this is related to Bug #339767
Developer says he will "eventually fix it". Really hoping he will some day.

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

[kwalletmanager] [Bug 326646] Password to unlock the kde wallet should not time out so fast

2016-03-22 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=326646

--- Comment #4 from Ben  ---
okay, it's only 2 and a half years

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

[kwalletmanager] [Bug 326646] Password to unlock the kde wallet should not time out so fast

2016-03-22 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=326646

Ben  changed:

   What|Removed |Added

 CC||c...@bnavigator.de

--- Comment #3 from Ben  ---
3 and a half years and this is still an issue with kwallet5
See also Bug https://bugs.kde.org/show_bug.cgi?id=339767

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

[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

2016-03-12 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=354056

Ben  changed:

   What|Removed |Added

 CC||c...@bnavigator.de

--- Comment #29 from Ben  ---
You can select "Automatically compact folders" in the Advanced Tab of the IMAP
Ressource.

This will instruct KMail to send the EXPUNGE command and you will get rid of
the greyed out messages.

Why you cannot tell kmail to not display messages marked as deleted is beyond
my understanding though. That should be standard.

Also, boo to the kmail developers, who failed to respond properly to this bug
report in weeks. And it is not the only report I noticed this behaviour. Is
there any active development in kmail?

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

[kmail2] [Bug 355195] date and time are ambiguous when replying to and forwarding messages (no timezone information)

2016-01-09 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=355195

--- Comment #3 from Ben  ---
(In reply to kolAflash from comment #2)
> Actually I'd prefer to see the timezone offset (e.g. +0800). Especially
> because I'm mailing with people in different timezones

> this seems to be the better way instead of recalculating everything to my 
> local timezone without
> any attached timezone information.

As i understand from reading the source in templateparser.cpp  this is actually
the desired behavior of the %OTIME and %OTIMELONG pattern. But somehow the
timezone information is passed either missing or passed incorrectly. I do not
see whether this is a problem with the KMime library, templateparser or
somewhere else in the kdepim infrastructure. Maybe it's Akonadi while providing
the message?

Someone with a working debug environment should look into it. I currently do
not have such a environment running.

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

[kmail2] [Bug 355195] date and time are ambiguous when replying to and forwarding messages (no timezone information)

2016-01-04 Thread Ben via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=355195

Ben  changed:

   What|Removed |Added

 CC||c...@bnavigator.de

--- Comment #1 from Ben  ---
I too ran accross this bug.
These bugs also seem to suffer from the same problem:
https://bugs.kde.org/show_bug.cgi?id=341909
https://bugs.kde.org/show_bug.cgi?id=308444

Steps to reproduce:
1. Find a mail in your inbox, that has a "Date:" header different from your
Local Timezone.
Local Timezone: CET
Mail with header "Date: Sun, 27 Dec 2015 15:20:55 -0800"

2. Create custom template for reply (or edit a default one):
TIME %TIME
DATE %DATE
DATEEN %DATEEN
TIMELONG %TIMELONG
TIMELONGEN %TIMELONGEN

OHEADER: %OHEADER="Date"
OTIME %OTIME
ODATE %ODATE
ODATEEN %ODATEEN
OTIMELONG %OTIMELONG
OTIMELONGEN %OTIMELONGEN

3. Reply to the mail with your custom template.

Actual Results:
TIME 00:36
DATE Dienstag, 5. Januar 2016
DATEEN Tuesday, 5 January 2016
TIMELONG 00:36:43 CET
TIMELONGEN 00:36:43 CET

OHEADER: Sun, 27 Dec 2015 15:20:55 -0800
OTIME 15:20
ODATE Sonntag, 27. Dezember 2015
ODATEEN Sunday, 27 December 2015
OTIMELONG 15:20:55 CET
OTIMELONGEN 15:20:55 CET

Expected Results (CET is UTC+1):
TIME 00:36
DATE Dienstag, 5. Januar 2016
DATEEN Tuesday, 5 January 2016
TIMELONG 00:36:43 CET
TIMELONGEN 00:36:43 CET

OHEADER: Sun, 27 Dec 2015 15:20:55 -0800
OTIME 00:20
ODATE Montag, 28. Dezember 2015
ODATEEN Monday, 28 December 2015
OTIMELONG 00:20:55 CET
OTIMELONGEN 00:20:55 CET


Also, there should be a template pattern family like %OTIMELONGUTC:
OHEADER: Sun, 27 Dec 2015 15:20:55 -0800
OTIMEUTC: 23:20
ODATEUTC Sunday, 27 December 2015
OTIMELONGUTC 23:20:55 UTC

The datetime is corretly displayed in the message list view. And the fancy
message header in the message view.


I run Archlinux
KMail Version 5.1
KDE Frameworks 5.18-0
Qt 5.5.1

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