from:"Garry Williams"

[kmail2] [Bug 485187] No Date In Message List or Message Preview Pane

2024-04-08 Thread Garry Williams

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

--- Comment #2 from Garry Williams  ---
Created attachment 168280
  --> https://bugs.kde.org/attachment.cgi?id=168280=edit
Message List + Preview No Date

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

[kmail2] [Bug 485187] No Date In Message List or Message Preview Pane

2024-04-08 Thread Garry Williams

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

--- Comment #3 from Garry Williams  ---
Created attachment 168281
  --> https://bugs.kde.org/attachment.cgi?id=168281=edit
Message Window

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

[kmail2] [Bug 485186] Message Preview Pane Headers Area Lost Background

2024-04-07 Thread Garry Williams

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

--- Comment #3 from Garry Williams  ---
(In reply to Laurent Montel from comment #2)
> Bug is in all messages ?

Yes.

It may be important to note that the headers are correct if I display the
message by hitting enter to open a message window.  It's only the preview pane
that displays incorrectly.

Both wayland and x11.

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

[kmail2] [Bug 485187] New: No Date In Message List or Message Preview Pane

2024-04-07 Thread Garry Williams

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

Bug ID: 485187
   Summary: No Date In Message List or Message Preview Pane
Classification: Applications
   Product: kmail2
   Version: 6.0.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

SUMMARY
Date is missing

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.2-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9370
ADDITIONAL INFORMATION

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

[kmail2] [Bug 485186] Message Preview Pane Headers Area Lost Background

2024-04-07 Thread Garry Williams

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

--- Comment #1 from Garry Williams  ---
Created attachment 168256
  --> https://bugs.kde.org/attachment.cgi?id=168256=edit
New Fancy Header Style

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

[kmail2] [Bug 485186] New: Message Preview Pane Headers Area Lost Background

2024-04-07 Thread Garry Williams

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

Bug ID: 485186
   Summary: Message Preview Pane Headers Area Lost Background
Classification: Applications
   Product: kmail2
   Version: 6.0.1
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

Created attachment 168255
  --> https://bugs.kde.org/attachment.cgi?id=168255=edit
Old Fancy Header Style

SUMMARY
Background has disappeared in the headers area (fancy header style).

See image files

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.2-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9370
ADDITIONAL INFORMATION

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

[kmail2] [Bug 480984] Composer Broken on Wayland

2024-04-02 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

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

--- Comment #6 from Garry Williams  ---
(In reply to Bug Janitor Service from comment #5)
> Dear Bug Submitter,
> 
> This bug has been in NEEDSINFO status with no change for at least
> 15 days. 

Oops.  I didn't reset the status.  See
https://bugs.kde.org/show_bug.cgi?id=480984#c2 and
https://bugs.kde.org/show_bug.cgi?id=480984#c3 and
https://bugs.kde.org/show_bug.cgi?id=480984#c4 .

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

[kmail2] [Bug 484481] Links In Preview Window No Longer Open New Browser Tab When Clicked

2024-03-25 Thread Garry Williams

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

--- Comment #1 from Garry Williams  ---
Interestingly, it looks like a plain text mail message that contains text that
looks like an http link and is made clickable by kmail does open a new tab
(without having to right click and select Open URL).  But that still changes
focus to the browser, which is a regression.  Links contained in html messages
seem to be the ones that do not click.

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

[kmail2] [Bug 484481] New: Links In Preview Window No Longer Open New Browser Tab When Clicked

2024-03-25 Thread Garry Williams

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

Bug ID: 484481
   Summary: Links In Preview Window No Longer Open New Browser Tab
When Clicked
Classification: Applications
   Product: kmail2
   Version: 6.0.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

HTTP links in the preview panel no longer open a new tab in my browser. 
Furthermore, if I right click a link in the preview window, I can click open
URL.  This immediately changes focus to my browser with the link in a new tab.

The previous behavior was to open the link in a new tab in the BACKGROUND
without changing focus.

STEPS TO REPRODUCE
1.  Navigate to a mail message that contains a hyperlink.
2.  Click the link.
3. 

OBSERVED RESULT
Nothing happens.

EXPECTED RESULT
Link should be loaded in the background in a new tab in browser already running
in session.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.1-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9370

ADDITIONAL INFORMATION

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

[kmail2] [Bug 480984] Composer Broken on Wayland

2024-03-18 Thread Garry Williams

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

--- Comment #4 from Garry Williams  ---
I suspect this bug is related to using an external editor instead of the
built-in kmail composer.  I have been configured to use vim to compose mail
messages in kmail for years.  I notice that when I close the editor, the
composer window is not updated with my edits.  If I  around to the
composer window again, it now shows the editor session I just closed.

I tested this and confirmed that specifying an external editor introduces this
bug.

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

[kmail2] [Bug 480984] Composer Broken on Wayland

2024-03-17 Thread Garry Williams

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

--- Comment #3 from Garry Williams  ---
I tried upgrading to f40, but no joy:

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.8.0-0.rc6.49.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9370

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

[kmail2] [Bug 480984] Composer Broken on Wayland

2024-03-17 Thread Garry Williams

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

--- Comment #2 from Garry Williams  ---
OK, I just checked again and the same problem is still there.

Start a new mail message; tab into Subject; type.  Typing is not echoed in the
Subject field.  It is present and is displayed when you tab out of Subject or
click somewhere else.

Fedora 39:
Operating System: Fedora Linux 39
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.7.7-200.fc39.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9370

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

[kmail2] [Bug 480984] New: Composer Broken on Wayland

2024-02-06 Thread Garry Williams

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

Bug ID: 480984
   Summary: Composer Broken on Wayland
Classification: Applications
   Product: kmail2
   Version: 5.24.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: composer
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

SUMMARY
Composer Subject field doesn't echo typing.  Click on, say To:, then tab to
Subject field and now can see typed text.


STEPS TO REPRODUCE
1. Start composer (new message)
2. Type in Subject: field
3. 

OBSERVED RESULT
No echo typed text

EXPECTED RESULT
Normal echo of typed text

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.12
Graphics Platform: Wayland
Graphics Processor: AMD Radeon Pro WX 2100

ADDITIONAL INFORMATION
Everything works fine in Plasma X11 session.
I also have kmail configured to use an external editor, if that makes any
difference.

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

[Akonadi] [Bug 479692] New: Cannot connect to agent instance with identifier 'akonadi_imap_resource_4', error message: ''

2024-01-12 Thread Garry Williams

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

Bug ID: 479692
   Summary: Cannot connect to agent instance with identifier
'akonadi_imap_resource_4', error message: ''
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: IMAP resource
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: akonadi_imap_resource (5.24.4 (23.08.4))

Qt Version: 5.15.12
Frameworks Version: 5.113.0
Operating System: Linux 6.6.11-200.fc39.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 39 (KDE Plasma)
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
Google Mail IMAP crashed when starting kmail after reboot.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Google Mail (gtwilliams) (akonadi_imap_resource), signal:
Segmentation fault

[KCrash Handler]
#4  0x7f3f18d7848e in QString::operator=(QString const&) () at
/lib64/libQt5Core.so.5
#5  0x7f3f1ae3398c in std::_Function_handler const&)::{lambda()#1}::operator()()
const::{lambda(bool)#1}>::_M_invoke(std::_Any_data const&, bool&&) () at
/lib64/libKPim5GAPICore.so.5
#6  0x7f3f1ae35907 in
QtPrivate::QFunctorSlotObject const&)::{lambda(bool)#1}, 1, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () at
/lib64/libKPim5GAPICore.so.5
#7  0x7f3f18ee9151 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#8  0x7f3f1a303814 in KWallet::Wallet::walletOpened(bool) () at
/lib64/libKF5Wallet.so.5
#9  0x7f3f18ee9151 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
#10 0x7f3f1a312228 in OrgKdeKWalletInterface::walletAsyncOpened(int, int)
() at /lib64/libKF5Wallet.so.5
#11 0x7f3f1a312902 in
OrgKdeKWalletInterface::qt_metacall(QMetaObject::Call, int, void**) () at
/lib64/libKF5Wallet.so.5
#12 0x7f3f1a1d438b in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) () at /lib64/libQt5DBus.so.5
#13 0x7f3f18edf9fb in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#14 0x7f3f19baeb95 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /lib64/libQt5Widgets.so.5
#15 0x7f3f18eb4e78 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /lib64/libQt5Core.so.5
#16 0x7f3f18eb8325 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /lib64/libQt5Core.so.5
#17 0x7f3f18f078cf in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () at /lib64/libQt5Core.so.5
#18 0x7f3f18091e5c in g_main_context_dispatch_unlocked.lto_priv () at
/lib64/libglib-2.0.so.0
#19 0x7f3f180ecf18 in g_main_context_iterate_unlocked.isra () at
/lib64/libglib-2.0.so.0
#20 0x7f3f1808fad3 in g_main_context_iteration () at
/lib64/libglib-2.0.so.0
#21 0x7f3f18f073b9 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib64/libQt5Core.so.5
#22 0x7f3f18eb383b in
QEventLoop::exec(QFlags) () at
/lib64/libQt5Core.so.5
#23 0x7f3f18ebbacb in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#24 0x55a2f9965d09 in main ()
[Inferior 1 (process 2766) detached]

Reported using DrKonqi

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

[konsole] [Bug 462615] Use KActionCollection::setDefaultShortcut(s) instead

2023-10-08 Thread Garry Williams

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

--- Comment #10 from Garry Williams  ---
I just upgraded to konsole5-23.08.1-1.fc38.x86_64 and this release fixes the
problem.

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

[kdeconnect] [Bug 446895] Desktop SMS Unresponsive

2023-05-09 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WORKSFORME  |---
 Status|NEEDSINFO   |REOPENED

--- Comment #6 from Garry Williams  ---
Just tested again and same result.  After re-opening the SMS application, I
cannot type in another message.  Furthermore, I see a message on my phone:
"This paired device is not reachable.  Make sure it is connected to your same
network."

The SMS application works until closing and reopening on my KDE desktop.

kdeconnectd-23.04.0-1.fc38.x86_64
kde-connect-libs-23.04.0-1.fc38.x86_64
kde-connect-23.04.0-1.fc38.x86_64

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

[kontact] [Bug 467921] New: Kontact Crash When Moving Through Messages in Message List Window

2023-03-29 Thread Garry Williams

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

Bug ID: 467921
   Summary: Kontact Crash When Moving Through Messages in Message
List Window
Classification: Applications
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

Application: kontact (5.22.80 (23.03.80))

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.8-200.fc37.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 37 (Thirty Seven)
DrKonqi: 5.27.3 [KCrashBackend]

-- Information about the crash:
When moving through the message window list, kontact (kmail) suddenly crashed.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault

[KCrash Handler]
#4  0x7f7cfc138df6 in KMime::Content::headerByType(char const*) const ()
from /lib64/libKPim5Mime.so.5
#5  0x7f7cfc13984e in KMime::Content::contentType(bool) () from
/lib64/libKPim5Mime.so.5
#6  0x7f7ca324d6cb in
MimeTreeParser::ObjectTreeParser::parseObjectTreeInternal(KMime::Content*,
bool) () from /lib64/libKPim5MimeTreeParser.so.5
#7  0x7f7ca324dbb6 in
MimeTreeParser::MessagePart::parseInternal(KMime::Content*, bool) () from
/lib64/libKPim5MimeTreeParser.so.5
#8  0x7f7c8011baca in
ApplicationGnuPGWKSFormatter::process(MimeTreeParser::Interface::BodyPart&)
const () from
/usr/lib64/qt5/plugins/pim5/messageviewer/bodypartformatter/messageviewer_bodypartformatter_application_gnupgwks.so
#9  0x7f7ca324d291 in
MimeTreeParser::ObjectTreeParser::processType(KMime::Content*,
MimeTreeParser::ProcessResult&, QByteArray const&) () from
/lib64/libKPim5MimeTreeParser.so.5
#10 0x7f7ca324d60e in
MimeTreeParser::ObjectTreeParser::parseObjectTreeInternal(KMime::Content*,
bool) () from /lib64/libKPim5MimeTreeParser.so.5
#11 0x7f7ca324d83f in
MimeTreeParser::ObjectTreeParser::parseObjectTree(KMime::Content*, bool) ()
from /lib64/libKPim5MimeTreeParser.so.5
#12 0x7f7ca340d33c in
MessageViewer::ViewerPrivate::parseContent(KMime::Content*) () from
/lib64/libKPim5MessageViewer.so.5
#13 0x7f7ca3419dc1 in MessageViewer::ViewerPrivate::updateReaderWin() ()
from /lib64/libKPim5MessageViewer.so.5
#14 0x7f7d532d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#15 0x7f7ca32313e2 in
MimeTreeParser::NodeHelper::update(MimeTreeParser::UpdateMode) () from
/lib64/libKPim5MimeTreeParser.so.5
#16 0x7f7d532d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#17 0x7f7ca3250d78 in
MimeTreeParser::VerifyDetachedBodyPartMemento::slotKeyListJobDone() () from
/lib64/libKPim5MimeTreeParser.so.5
#18 0x7f7d532d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#19 0x7f7ca2f46b29 in QGpgME::_detail::ThreadedJobMixin >, QString, GpgME::Error> >::slotFinished() () from
/lib64/libqgpgme.so.7
#20 0x7f7d532c8134 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#21 0x7f7d53faed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#22 0x7f7d5329d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#23 0x7f7d532a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#24 0x7f7d532eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#25 0x7f7d49bd5c7f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#26 0x7f7d49c2c118 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#27 0x7f7d49bd2f00 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#28 0x7f7d532ee5fa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#29 0x7f7d5329bf3a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#30 0x7f7d532a4002 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#31 0x560a617265f7 in main ()
[Inferior 1 (process 18183) detached]

Reported using DrKonqi

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

[konsole] [Bug 462615] Use KActionCollection::setDefaultShortcut(s) instead

2023-01-05 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

--- Comment #3 from Garry Williams  ---
Confirmed.

Kernel: 6.0.17-300.fc37.x86_64
X11
qt5-qtbase-common-5.15.7-1.fc37.noarch
konsole5-22.12.0-1.fc37.x86_64
VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa XT
[Radeon PRO WX 2100]

konsole[3611]: kf.xmlgui: Shortcut for action  "" "Show Quick Commands" set
with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s)
instead.
konsole[3611]: kf.xmlgui: Shortcut for action  "" "Show SSH Manager" set with
QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.

Interestingly, my laptop (Dell XPS-13) doesn't exhibit the same bug.  It has
exactly the same versions of everything and is also running X11 graphics.  Its
graphics adapter: VGA compatible controller: Intel Corporation UHD Graphics 620
(rev 07)

Let me know, if I can provide any other information.

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

[kmail2] [Bug 336878] Position in the message list is not preserved across restarts

2022-11-23 Thread Garry Williams

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

--- Comment #9 from Garry Williams  ---
I am not the original reporter, but I confirmed the bug.  I can report that the
bug seems to be fixed. 

kmail-22.08.1-1.fc37.x86_64

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

[kmail2] [Bug 373201] Message List Threading Intermittently Breaks

2022-10-31 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |FIXED
 Status|NEEDSINFO   |RESOLVED

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

[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle

2022-09-17 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC|gtwilli...@gmail.com|

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

[kalendar] [Bug 457120] Reminder Daemon crashing when Dismissing after startup

2022-09-05 Thread Garry Williams

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

--- Comment #3 from Garry Williams  ---
(In reply to Carl Schwan from comment #2)
> Please update kalendar to the latest version. This bugs were fixed in
> kalendarac 5.21.1

Thank you for looking at this, Carl.  But my system doesn't have kalendar or
kalendarac installed.  Here's what it looks like here:

$ rpm -qa|grep kalen
$ rpm -qa|grep calen
kf5-kcalendarcore-5.96.0-2.fc37.x86_64
kf5-kcalendarutils-22.04.3-2.fc37.x86_64
kf5-akonadi-calendar-22.04.3-2.fc37.x86_64
kf5-calendarsupport-22.04.3-2.fc37.x86_64
akonadi-calendar-tools-22.04.3-2.fc37.x86_64
$

I get no updates to any of these packages when I update; I am enabling the
updates-testing repo.

Now it may be significant that I am running f37, which is not yet released. 
Also, it may be that I identified the wrong bug to go with my crashes.

(I won't change the bug status until we get this sorted.  Please advise me how
to proceed.)

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

[kalendar] [Bug 457120] Reminder Daemon crashing when Dismissing after startup

2022-09-05 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

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

[kalendar] [Bug 457120] Reminder Daemon crashing when Dismissing after startup

2022-09-05 Thread Garry Williams

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

--- Comment #1 from Garry Williams  ---
Created attachment 151851
  --> https://bugs.kde.org/attachment.cgi?id=151851=edit
New crash information added by DrKonqi

kalendarac (5.20.3) using Qt 5.15.5

Dismiss reminder after login and crash.  Also, dismiss reminder after long idle
and several reminders have accumulated, then sometimes crash.  This backtrace 
is example of the latter.

-- Backtrace (Reduced):
#4  0x55bf5a2711d1 in KalendarAlarmClient::dismiss(AlarmNotification*) ()
#5  0x7feef89388b6 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#6  0x7feef97c9a67 in KNotification::close() () from
/lib64/libKF5Notifications.so.5
#7  0x7feef89388b6 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#8  0x7feef97c6c33 in KNotificationPlugin::finished(KNotification*) () from
/lib64/libKF5Notifications.so.5

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

[krunner] [Bug 457174] krunner Dialog Fails To Display

2022-07-27 Thread Garry Williams

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

--- Comment #4 from Garry Williams  ---
(In reply to Nate Graham from comment #3)
> please do report it to the
> Fedora folks! You can do so here: https://pagure.io/fedora-kde/SIG/issues

Thanks, again Nate.

https://pagure.io/fedora-kde/SIG/issue/228

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

[krunner] [Bug 457174] krunner Dialog Fails To Display

2022-07-27 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #2 from Garry Williams  ---
(In reply to Nate Graham from comment #1)
> Sounds like your KRunner theming may be broken. A few questions:
> 1. Does it reproduce with the default Breeze Plasma style?

Bingo!  I had previously selected "Fedora Thirty-Five" style for some reason
and didn't notice the problem soon enough to connect it with that change.

Thanks for the help.

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

[krunner] [Bug 457174] New: krunner Dialog Fails To Display

2022-07-26 Thread Garry Williams

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

Bug ID: 457174
   Summary: krunner Dialog Fails To Display
   Product: krunner
   Version: 5.25.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: gtwilli...@gmail.com
CC: alexander.loh...@gmx.de
  Target Milestone: ---

Created attachment 150933
  --> https://bugs.kde.org/attachment.cgi?id=150933=edit
Image From Top of Screen

SUMMARY

The krunner dialog refuses to display after Alt-F2 or Alt-SPACE or Run krunner
from main menu.  Instead, a squar, blank window shows up just below my panel
located on the top of my workspace.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

No log messages are produced aside from the original systemd "Starting
plasma-krunner.service - KRunner..." on first attempt after login.

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

[Akonadi] [Bug 444288] Akonadi "losing connection" to Google Calendars after some uptime / waking from sleep until either akonadictrl restart is used or Google Groupware is restarted in Korganizer.

2022-02-15 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

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

[kdeconnect] [Bug 446895] New: Desktop SMS Unresponsive

2021-12-12 Thread Garry Williams

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

Bug ID: 446895
   Summary: Desktop SMS Unresponsive
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: messaging-application
  Assignee: si...@ergotech.com
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

SUMMARY
Desktop SMS application becomes unresponsive after sending message(s) and then
close and open again.

Either the "waiting" icon keeps running without sending or it is impossible to
even get focus to the input field so that typing is impossible.

STEPS TO REPRODUCE
1. Open KDE Connect SMS
2. Send message
3. Close KDE Connect SMS
4. Open KDE Connect SMS

OBSERVED RESULT
After the second use, the application is unresponsive.

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: kdeconnectd-21.04.3-1.fc35.x86_64
(available in About System)
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I use Android with Pixel 3a phone.

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

[kontact] [Bug 404369] Sent Folder is not defined. Please set it before sending the mail.

2021-11-23 Thread Garry Williams

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

--- Comment #3 from Garry Williams  ---
And now I see that Configure -> Kmail -> Identities -> Advanced is the place to
set the folder.  My settings lost this when I deleted and recreated my Gmail
account.

This is not a bug.  (At least not from my point of view.)

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

[kontact] [Bug 404369] Sent Folder is not defined. Please set it before sending the mail.

2021-11-23 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

--- Comment #2 from Garry Williams  ---
Similar problem here.

kmail2 5.17.3 (21.04.3)

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

[kmail2] [Bug 414038] Whitespace in quoted lines not preserved, so some ASCII drawings are messed up.

2021-11-08 Thread Garry Williams

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

--- Comment #5 from Garry Williams  ---
(In reply to Laurent Montel from comment #2)
> it's how works all browser. It compress all space

Can we keep browser away from text E-mail?  There never has been a need to use
a browser on text.

That would fix this bug.

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

[kmail2] [Bug 443021] New: Message Marked Unread Again When New Mail Received

2021-09-27 Thread Garry Williams

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

Bug ID: 443021
   Summary: Message Marked Unread Again When New Mail Received
   Product: kmail2
   Version: 5.15.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

SUMMARY
Messages are often marked as unread after reading when new mail is received. 
This happens with Gmail account.


STEPS TO REPRODUCE
1. Read mail just before scanning for new mail
2. 
3. 

OBSERVED RESULT
Already-read mail gets marked as unread until selected again

EXPECTED RESULT
Read mail stays marked read while new messages show up.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 33
KDE Plasma Version: 5.20.5-1.fc33.x86_64
KDE Frameworks Version: 5.79.0-2.fc33.x86_64
Qt Version: 5.15.2-2.fc33.x86_64

ADDITIONAL INFORMATION
This is a long-standing problem that has been here for many years.

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

[konsole] [Bug 430036] konsole repeatedly losing no-toolbar setting

2021-07-29 Thread Garry Williams

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

--- Comment #30 from Garry Williams  ---
Just to be clear, I saw this bug come back after installing (from Fedora
updates-testing) konsole5-21.04.2-3.fc34 and konsole5-part-21.04.2-3.fc34.

I see the bug fixed by downgrading to konsole5-21.04.2-1.fc34 and
konsole5-part-21.04.2-1.fc34.

The bug is fixed in the -1 version and comes back in the -3 version.  I have
never seen a -2 version of either package.

(See my comment #27.)

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

[konsole] [Bug 430036] konsole repeatedly losing no-toolbar setting

2021-07-28 Thread Garry Williams

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

--- Comment #27 from Garry Williams  ---
(In reply to tcanabrava from comment #8)
> konsole has no code to manage toolbars,

Perhaps not, but...

I install konsole5-21.04.2-3.fc34 and konsole5-part-21.04.2-3.fc34 and the bug
comes back -- I cannot make the toolbars go away permanently.

I downgrade to konsole5-21.04.2-1.fc34 and konsole5-part-21.04.2-1.fc34 and the
toolbars are gone and do not come back.

No other change was made and I did this multiple times.

21.04.2-3.fc34 introduces the bug.  Downgrading fixes the bug.

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

[kmail2] [Bug 397825] [Wayland] Message viewer displays only a black rectangle

2021-07-08 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

--- Comment #40 from Garry Williams  ---
I can confirm the bug on Fedora f34 with kmail2 5.16.2 (20.12.2) and kf5
5.83.0-1.fc34.x86_64.

I reproduce the bug by switching to Calendar and then back to Mail in the
left-hand side icons in the kontact application.

The only way to restore the message pane is to completely quit (+q) and
restart.

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

[konsole] [Bug 430036] konsole repeatedly losing no-toolbar setting

2021-06-25 Thread Garry Williams

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

--- Comment #12 from Garry Williams  ---
(In reply to Garry Williams from comment #11)
> konsole version 21.04.2 fixed the problem for me.

Also, kf5-kxmlgui-5.83.0-1.fc34.x86_64

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

[konsole] [Bug 430036] konsole repeatedly losing no-toolbar setting

2021-06-25 Thread Garry Williams

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

--- Comment #11 from Garry Williams  ---
konsole version 21.04.2 fixed the problem for me.

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

[konsole] [Bug 438160] Toolbars Cannot Be Permanently Deleted

2021-06-25 Thread Garry Williams

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

--- Comment #2 from Garry Williams  ---
konsole version 21.04.2 fixed the problem for me.

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

[konsole] [Bug 438160] Toolbars Cannot Be Permanently Deleted

2021-06-06 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

Summary|Toolbars Cannot e   |Toolbars Cannot Be
   |Permanently Deleted |Permanently Deleted

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

[konsole] [Bug 438160] New: Toolbars Cannot e Permanently Deleted

2021-06-06 Thread Garry Williams

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

Bug ID: 438160
   Summary: Toolbars Cannot e Permanently Deleted
   Product: konsole
   Version: 21.04.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

SUMMARY
konsole used to start up without displaying any toolbars.  Now it always starts
with both "main" and "session" toolbars.

I now have to select Show Menu Bar so that I can right click in menu bar to
deselect the two toolbars and then unclick Settings -> Show Menu Bar.  But it
won't "remember" my preference now.

konsole used to let me eliminate all that unneeded real estate.  What happened?

STEPS TO REPRODUCE
1. Start knsole
2. 
3. 

OBSERVED RESULT
Tool bars take up valuable real estate at the top of the window.

EXPECTED RESULT
Tool bars are not present.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: plasma-workspace-5.21.90-4.fc34.x86_64
KDE Plasma Version: plasma-desktop-5.21.90-3.fc34.x86_64
KDE Frameworks Version: kf5-plasma-5.82.0-1.fc34.x86_64
kf5-frameworkintegration-5.82.0-1.fc34.x86_64
Qt Version: qt5-qtbase-5.15.2-15.fc34.x86_64

ADDITIONAL INFORMATION

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

[plasma-systemmonitor] [Bug 437114] Consider Restoring Old System Load Viewer Look and Function

2021-05-14 Thread Garry Williams

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

--- Comment #3 from Garry Williams  ---
Created attachment 138433
  --> https://bugs.kde.org/attachment.cgi?id=138433=edit
new screenshot

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

[plasma-systemmonitor] [Bug 437114] Consider Restoring Old System Load Viewer Look and Function

2021-05-14 Thread Garry Williams

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

--- Comment #2 from Garry Williams  ---
Created attachment 138432
  --> https://bugs.kde.org/attachment.cgi?id=138432=edit
old tooltip

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

[plasma-systemmonitor] [Bug 437114] Consider Restoring Old System Load Viewer Look and Function

2021-05-14 Thread Garry Williams

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

--- Comment #1 from Garry Williams  ---
Created attachment 138431
  --> https://bugs.kde.org/attachment.cgi?id=138431=edit
old screen shot

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

[plasma-systemmonitor] [Bug 437114] New: Consider Restoring Old System Load Viewer Look and Function

2021-05-14 Thread Garry Williams

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

Bug ID: 437114
   Summary: Consider Restoring Old System Load Viewer Look and
Function
   Product: plasma-systemmonitor
   Version: 5.21.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: gtwilli...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Created attachment 138430
  --> https://bugs.kde.org/attachment.cgi?id=138430=edit
old applet

SUMMARY
The System Load Viewer applet was dropped recently from Plasma and it is said
that System Monitor replaces it.

Please consider making System Monitor Sensor:Memory Usage and Individual Core
Usage look and function like the old System Load Viewer.

The new applets are not as compact as the old applet and do not deliver the
same information as the old applet.

The old applet using its "Compact bar", "CPUs separately", and "Set Colors
Manually" settings was compact and information-rich.  The CPU bar charts showed
total CPU and application, nice, system, and I/O wait in different colors.  The
memory bar showed application, buffers, and cache memory usage in different
colors.  Finally, the old applet showed various details in a tabular form in
its tooltip, which was very nice, if patched to be interactive to allow the
user time to take in the detail.

The new applet(s) put space between each bar chart and display a wide bar chart
for the memory usage.  This results in about twice as much space being taken
up.  There is no information about different memory usage or different CPU
usage using colors.  Indeed, the CPU charts are all different colors, providing
no useful information.  The tooltip simply displays the applet title -- no
details about the monitored resources.

I am attaching the old applet (in case you want to actually run it to see the
differences above), screen shots of the old monitor, the new monitor, and the
old tooltip.

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

[kwin] [Bug 435513] New: Vertical/Horizontal Maximize Window Doesn't Work

2021-04-08 Thread Garry Williams

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

Bug ID: 435513
   Summary: Vertical/Horizontal Maximize Window Doesn't Work
   Product: kwin
   Version: 5.21.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

SUMMARY
Both vertical and horizontal maximize window do not work.

STEPS TO REPRODUCE
1. Use shortcut keys to maximize (v or h) window
2. 
3. 

OBSERVED RESULT
Window remains unmaximized.

EXPECTED RESULT
Window maximizes in desired dimension (vertical or horizontal).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora F34
(available in About System)
KDE Plasma Version: 5.21.4-1
KDE Frameworks Version: 5.80.0-1
Qt Version: 5.15.2-15

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

[kwin] [Bug 435511] New: Window Placement Changed Leaving Empty Space on Left-hand Side (Wayland)

2021-04-08 Thread Garry Williams

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

Bug ID: 435511
   Summary: Window Placement Changed Leaving Empty Space on
Left-hand Side (Wayland)
   Product: kwin
   Version: 5.21.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

Created attachment 137434
  --> https://bugs.kde.org/attachment.cgi?id=137434=edit
Screenshot of Wrongly Positioned Window

SUMMARY
Window placement has changed from F33.  A new application window used to open
in the top, left-hand side of a workspace, if it was available.  Now it opens
offset to the right.  I see this new behavior with konsole.  I attach screen
shot illustrating new application window in a completely empty workspace.

STEPS TO REPRODUCE
1. Open konsole on empty workspace
2. 
3. 

OBSERVED RESULT
New application window is NOT flush left.

EXPECTED RESULT
New application window is flush left.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora F34
(available in About System)
KDE Plasma Version: 5.21.4-1
KDE Frameworks Version: 5.80.0-1
Qt Version: 5.15.2-15

ADDITIONAL INFORMATION
Settings->Window Management->Window Behavior->Advanced->Window
placement=Minimal Overlapping seems otherwise to operate correctly.

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

[Akonadi] [Bug 392742] akonadi imap crash

2020-12-17 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

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

[kdeplasma-addons] [Bug 366342] System Load Viewer Plasmoid shows only used memory including cache

2020-10-31 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED
 Ever confirmed|1   |0

--- Comment #12 from Garry Williams  ---
Forgot to change status after last comments added in response to NEEDSINFO.

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

[kdeplasma-addons] [Bug 397840] SystemLoadViewer Lost Memory Cache Display

2020-10-31 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

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

--- Comment #5 from Garry Williams  ---
Forgot to change status after last comments added in response to NEEDSINFO.

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

[Akonadi] [Bug 428448] New: Akonadi Refuses to Open mbox File in /var/spool/mail

2020-10-29 Thread Garry Williams

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

Bug ID: 428448
   Summary: Akonadi Refuses to Open mbox File in /var/spool/mail
   Product: Akonadi
   Version: 5.15.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: MBox Resource
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

SUMMARY
Define mbox account in /var/spool/mail/username and see error message when
restarting Settings -> Kmail -> Accounts -> Receiving.

Message is briefly visible in the Configure - Kontact dialog box from Settings
-> Kmail -> Accounts -> Receiving.  I have seen "No file specified." and
something like "Cannot read /var/spool/mail/garry".  It's hard to be accurate
because the error message only flashes on the screen briefly.  (That, in itself
is a bug that should be fixed.)

Add a sym link in home directory to /var/spool/mail/username and define mbox
resource using that file and now no error message, but...

kmail doesn't show all messages in mail box.

Kmail will not delete any messages in mail box.

Kmail won't show message has been read in the message list pane.


STEPS TO REPRODUCE
1. 
$ mail garry  # Any local user on this machine.
Subject: Test

Test
EOT
$

(The line that says "EOT" was produced by typing CTRL-D after enter key to
start new line.)

2. Define Mbox resource in Settings -> Kmail -> Accounts -> Receiving -> Add ->
Custom Account
2. 
3. 

OBSERVED RESULT
Doesn't work.

Send multiple messages.  Delete one in kmail.  Nothing works as expected.


EXPECTED RESULT
Works


SOFTWARE/OS VERSIONS

Fedora: 5.8.16-300.fc33.x86_64
Kmail: kmail2 5.15.1 (20.08.1)
KDE Frameworks 5.73.0
Qt 5.15.1 (built against 5.15.1)
The xcb windowing system

ADDITIONAL INFORMATION
As far as I know, this simple mail format has been broken in kmail for at least
10 years.  Perhaps won't fix?  Withdraw option altogether?

My work-around is to use the /usr/bin/mail command.  I believe that program was
originally released in UNIX and later in Linux well before 2000.  POSIX
standardized it as /usr/bin/mailx in 1997.  I am unaware of any bugs in that
program.  Perhaps it could serve as an example how to process a mbox resource?

I would be happy to assist in any way I can.

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

[kmail2] [Bug 428303] New: Threading Broken When Using Clone of Standard Mailing List

2020-10-26 Thread Garry Williams

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

Bug ID: 428303
   Summary: Threading Broken When Using Clone of Standard Mailing
List
   Product: kmail2
   Version: 5.13.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

SUMMARY
Message threading is broken when using a clone of Standard Mailing List
Aggregation.

Threading is flawless all the time when using Standard Mailing List
Aggregation.  Clone the aggregation and now new messages sometimes do not end
up threaded correctly and look like a new thread altogether.

All attributes are identical to shipped Standard Mailing List Aggregation.

As an aside, creating a brand new Aggregation with identical attributes also
results in broken threading.  It seems the only way to get flawless threading
is to use the built-in Standard Mailing List Aggregation.


STEPS TO REPRODUCE
1. Clone Standard Mailing List Aggregation
2. Select Clone for aggregation
3. 

OBSERVED RESULT
Some messages do not appear in their correct threads and end up being thread
leaders instead.


EXPECTED RESULT
Threading works as with the Standard Mailing List Aggregation.  (Since the
clone is identical in every respect that can be known from the UI.)

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 5.8.16-200.fc32.x86_64, kmail kmail2 5.13.2 (19.12.2)
(available in About System)

KDE Frameworks 5.73.0
Qt 5.14.2 (built against 5.14.2)
The xcb windowing system
plasma-desktop-5.18.5-2.fc32.x86_64


ADDITIONAL INFORMATION
This has been broken for quite a while now.  I do not know when it was
introduced.

I want to clone Standard Mailing List because I want threads expanded all the
time.  That option is not set in the shipped Standard Mailing List Aggregation
and it cannot be changed without cloning a new Aggregation.

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

[kdeplasma-addons] [Bug 366342] System Load Viewer Plasmoid shows only used memory including cache

2020-10-16 Thread Garry Williams

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

--- Comment #10 from Garry Williams  ---
(In reply to Nate Graham from comment #9)
> Is this still an issue or relevant with the new System Monitor applet in
> Plasma 5.19 and beyond?

See bug #397840.  This bug report is about an existing applet being changed for
no apparent reason.  Yes this report is relevant because comment #6 was was
never addressed before.  Bug #397840 contains a patch that fixes the problem in
this report, comment #6.

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

[kdeplasma-addons] [Bug 397840] SystemLoadViewer Lost Memory Cache Display

2020-10-16 Thread Garry Williams

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

--- Comment #3 from Garry Williams  ---
Created attachment 132428
  --> https://bugs.kde.org/attachment.cgi?id=132428=edit
Nice Tooltip Display With Original Applet

The patch attached allows the tooltip to remain displayed while it updates and
the user can take in all the data before it disappears like it does without the
patch.

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

[kdeplasma-addons] [Bug 397840] SystemLoadViewer Lost Memory Cache Display

2020-10-16 Thread Garry Williams

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

--- Comment #2 from Garry Williams  ---
Created attachment 132427
  --> https://bugs.kde.org/attachment.cgi?id=132427=edit
Patch To Restore Cache Display and Allow Hover

This simple patch restores the previous behavior of System Load Viewer.  This
applet is very simple to configure and duplicates the behavior we had even
before Plasma was introduced.  I fail to understand why it was changed.

The new System Monitor Sensor is very tedious and opaque with its
configuration.  It doesn't display the same information it its tooltip.

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

[kmail2] [Bug 414038] Whitespace in quoted lines not preserved, so some ASCII drawings are messed up.

2020-08-21 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

--- Comment #3 from Garry Williams  ---
Created attachment 131081
  --> https://bugs.kde.org/attachment.cgi?id=131081=edit
Text Messed Up In Message Viewer

There used to be an option to display messages without HTML trying to be
helpful.  I wonder if that option could be restored.  It would also fix the
attached problem.

Actual text behind attached screen shot:
>
> So it is fixed ?

Is not the first time that we need [1] , specially when rawhide bump
the number (f33 -> f34), I guess , is one thing that maybe fedora-
review should take care ... or mock itself :)

[1]
mock -r fedora-rawhide-x86_64 --scrub all

>
> --

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

[kde] [Bug 423119] dcopserver doesn't launch with XDG_RUNTIME_DIR set

2020-06-17 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

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

[kdeplasma-addons] [Bug 366342] System Load Viewer Plasmoid shows only used memory including cache

2019-08-11 Thread Garry Williams

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

--- Comment #8 from Garry Williams  ---
Created attachment 122065
  --> https://bugs.kde.org/attachment.cgi?id=122065=edit
Patch To Restore Cache Display and Allow Hover

I also submitted a patch to allow hovering on the load viewer so that
it wouldn't disappear until moving the mouse off of it.  That was
rejected on some consistency grounds -- not on its merit.

I, too didn't like the change here.  But it seems that no one agrees.
That being the case, I have been carrying my own patches to restore
the cache display and to allow hover to prevent the display from
closing.

Here are my patches, if you are interested.  I apply them (after
updates regress them) with the following commands (Fedora):

sudo patch
/usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/SystemLoadViewer.qml
ui/SystemLoadViewer.qml.patch
sudo patch
/usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/ui/ColorSettings.qml
ui/ColorSettings.qml.patch
sudo patch
/usr/share/plasma/plasmoids/org.kde.plasma.systemloadviewer/contents/config/main.xml
config/main.xml.patch

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

[Akonadi] [Bug 394839] pimitemtable.remoteid Column Too Small For Exchange Calendar Via davmail

2019-06-10 Thread Garry Williams

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

--- Comment #9 from Garry Williams  ---
You might check that innodb_large_prefix was deprecated in MySQL 5.7.7 and is
now removed from MySQL as of 8.0.0.

(My version happens to be 10.3.12-MariaDB on Fedora 30.)

I tried your patch on my mysql.conf file and got a fatal error on start-up
because of this.

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

[kmail2] [Bug 403159] Blank page on print and print preview

2019-05-10 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC|gtwilli...@gmail.com|

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

[kmail2] [Bug 387061] Large messages don't display in the viewer pane (eg. New Tumbleweed snapshot 20171117 released!)

2019-02-13 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

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

[kmail2] [Bug 403159] Blank page on print preview

2019-01-31 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

--- Comment #5 from Garry Williams  ---
Same on Fedora and also crashed kmail without a usable dump each time doing
File -> Print Preview:

Jan 31 15:26:55 ifr systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Jan 31 15:26:55 ifr systemd[1]: Started Process Core Dump (PID 17269/UID 0).
Jan 31 15:26:56 ifr systemd-coredump[17270]: Core file was truncated to
2147483648 bytes.
Jan 31 15:26:57 ifr abrt-dump-journal-core[955]: Failed to obtain all required
information from journald
Jan 31 15:26:57 ifr systemd-coredump[17270]: Process 16616 (kontact) of user
1000 dumped core.

 Stack trace of thread 16616:
 #0  0x7ff59b54f53f n/a (n/a)
Jan 31 15:27:00 ifr abrt-server[17279]: Error: No segments found in coredump
'./coredump'
Jan 31 15:27:01 ifr abrt-server[17279]: Can't open file 'core_backtrace' for
reading: No such file or directory
Jan 31 15:27:05 ifr abrt-notification[17320]: Process 16616 (kontact) crashed
in ??()

garry@ifr$ rpm -q kmail plasma-desktop qt5-qtbase
kmail-18.08.3-1.fc29.x86_64
plasma-desktop-5.14.4-2.fc29.x86_64
qt5-qtbase-5.11.3-1.fc29.x86_64

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

[Akonadi] [Bug 394839] pimitemtable.remoteid Column Too Small For Exchange Calendar Via davmail

2018-12-11 Thread Garry Williams

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

--- Comment #4 from Garry Williams  ---
(In reply to Erik Quaeghebeur from comment #3)
> That worked, but I get the same error as within the DB console of
> akonadiconsole:
> 
> > mysql> alter table pimitemtable modify column remoteId varchar(1024);
> > ERROR 1067 (42000): Invalid default value for 'atime'

I don't know what to tell you:

MariaDB [akonadi]> alter table pimitemtable modify column remoteId
varchar(1024);
Query OK, 0 rows affected (0.001 sec)
Records: 0  Duplicates: 0  Warnings: 0

MariaDB [akonadi]>

You might want to read

   
https://stackoverflow.com/questions/36882149/error-1067-42000-invalid-default-value-for-created-at

and similar references.

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

[Akonadi] [Bug 394839] pimitemtable.remoteid Column Too Small For Exchange Calendar Via davmail

2018-12-11 Thread Garry Williams

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

--- Comment #2 from Garry Williams  ---
(In reply to Erik Quaeghebeur from comment #1)
> @Garry I see that you are accessing the database directly. How do I go about
> doing that.

If you do a

ps -ef|grep mysql

command, you will see the --socket= parameter that you need to use when you
issue the mysql command.  If you simply do

mysql --socket=/tmp/akonadi-blah-blah

then, at the mysql prompt, do

use akonadi

you will be all set to alter the table as mentioned above.

It's disappointing that the developers have not seen fit to even acknowledge
this bug report.  At least you managed to find it.

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

[kdeplasma-addons] [Bug 397840] New: SystemLoadViewer Lost Memory Cache Display

2018-08-24 Thread Garry Williams

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

Bug ID: 397840
   Summary: SystemLoadViewer Lost Memory Cache Display
   Product: kdeplasma-addons
   Version: 5.13.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: systemloadviewer
  Assignee: plasma-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

Created attachment 114582
  --> https://bugs.kde.org/attachment.cgi?id=114582=edit
Screenshot of Former Appearance

The SystemLoadViewer widget has lost its display of cache memory.  It has shown
this since the beginning and now, all of a sudden, it's gone.

I have attached a screenshot that shows the former look this widget had.  The
green portion in the bar graph has been omitted in the latest version of this
applet.

Please restore the old behavior that has been there for years.

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

[kdeplasma-addons] [Bug 366342] System Load Viewer Plasmoid shows only used memory including cache

2018-08-16 Thread Garry Williams

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

Garry Williams  changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

--- Comment #6 from Garry Williams  ---
What's wrong with visually displaying cache (as green custom color like
before), but reporting without adding in cache (like before)?

It was not "wrong" and matched (visually) what top and others would report.

In other words, why hide the used cache?

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

[Akonadi] [Bug 394839] New: pimitemtable.remoteid Column Too Small For Exchange Calendar Via davmail

2018-05-29 Thread Garry Williams

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

Bug ID: 394839
   Summary: pimitemtable.remoteid Column Too Small For Exchange
Calendar Via davmail
   Product: Akonadi
   Version: 5.7.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

I was unable to configure an Exchange calendar via the davmail proxy because
the item ID was longer than the column length for the pimitemtable.remoteid
column (255).

The error resulted in log messages like this:

DATABASE ERROR:
  Error code: "1406"
  DB error:  "Data too long for column 'remoteId' at row 1"
  Error text: "Data too long for column 'remoteId' at row 1 QMYSQL3: Unable
to execute statement"
  Query: "INSERT INTO PimItemTable (rev, remoteId, remoteRevision, gid,
collectionId, mimeTypeId, datetime, atime, dirty, size) VALUES (:0, :1, :2, :3,
:4, :5, :6, :7, :8, :9)"

I turned on general_log in mysql to catch the error.

The fix was:

alter table pimitemtable modify column remoteId varchar(1024);

(I imagine that 1024 is larger than what is strictly needed, but it costs
nothing to specify it.)

The problem data looks like this:

   
http://localhost:1080/users/garry_willia...@comcast.com/calendar/AAMkADE0ZTY4YjY0LTM3ZmUtNGQ3Yy1hMzdjLTdlNTZlYjgzMTNkZgBGAABv2lgKJBYZRoOfK2MzkdgNBwCAS5PvJdbcTKxWQLEnWOAHAAENAACAS5PvJdbcTKxWQLEnWOAHAAAaQl7dAAA%3D.EML#04008200E00074C5B7101A82E008A059FC7E8054D201100067BF664FED94F14D8772488D96A9E4E92017-01-17T19:30:00+00:00

My pimitemtable now has this:

MariaDB [akonadi]> select length(remoteid) from pimitemtable where
length(remoteid) > 255;
+--+
| length(remoteid) |
+--+
|  361 |
|  361 |
|  361 |
|  361 |
|  361 |
|  361 |
|  361 |
|  363 |
|  363 |
+--+
9 rows in set (0.01 sec)

MariaDB [akonadi]>

And the calendar is finally working.

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

[Akonadi] [Bug 392742] New: akonadi imap crash

2018-04-04 Thread Garry Williams

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

Bug ID: 392742
   Summary: akonadi imap crash
   Product: Akonadi
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: server
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

Application: akonadiserver (5.7.3)

Qt Version: 5.9.4
Frameworks Version: 5.44.0
Operating System: Linux 4.15.14-300.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

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

I clicked the inbox to view new mail while I was viewing mail in another
folder.

-- Backtrace:
Application: Akonadi Server (akonadiserver), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f52acedd8c0 (LWP 1533))]

Thread 35 (Thread 0x7f5203fff700 (LWP 10056)):
#0  0x7f52aa8f2c6b in poll () from /lib64/libc.so.6
#1  0x7f52a5171e99 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f52a5171fac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f52ab748c4b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f52ab6f696a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f52ab5478ca in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f52ab54bde2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f52a8b3a50b in start_thread () from /lib64/libpthread.so.0
#8  0x7f52aa8fd16f in clone () from /lib64/libc.so.6

Thread 34 (Thread 0x7f5208ff9700 (LWP 9539)):
#0  0x7f52aa8f2c6b in poll () from /lib64/libc.so.6
#1  0x7f52a5171e99 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f52a5171fac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f52ab748c4b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f52ab6f696a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f52ab5478ca in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f52ab54bde2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7f52a8b3a50b in start_thread () from /lib64/libpthread.so.0
#8  0x7f52aa8fd16f in clone () from /lib64/libc.so.6

Thread 33 (Thread 0x7f52097fa700 (LWP 9486)):
#0  0x7f52aa90a1dc in __lll_lock_wait_private () from /lib64/libc.so.6
#1  0x7f52aa88720c in _int_free () from /lib64/libc.so.6
#2  0x55d0fdd472e3 in Akonadi::Server::ItemRetriever::buildQuery() const ()
#3  0x55d0fdd48ea9 in Akonadi::Server::ItemRetriever::exec() ()
#4  0x55d0fdd029ff in Akonadi::Server::FetchHelper::fetchItems() ()
#5  0x55d0fdcffdd1 in Akonadi::Server::Fetch::parseStream() ()
#6  0x55d0fdbd3710 in Akonadi::Server::Connection::slotNewData() ()
#7  0x7f52ab720637 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#8  0x7f52ab720513 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#9  0x7f52ac33eb53 in QAbstractSocketPrivate::emitReadyRead(int) () from
/lib64/libQt5Network.so.5
#10 0x7f52ac33ec04 in QAbstractSocketPrivate::canReadNotification() () from
/lib64/libQt5Network.so.5
#11 0x7f52ac34f8e1 in QReadNotifier::event(QEvent*) () from
/lib64/libQt5Network.so.5
#12 0x7f52ab6f7afa in doNotify(QObject*, QEvent*) () from
/lib64/libQt5Core.so.5
#13 0x7f52ab6f7be7 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#14 0x7f52ab7495af in socketNotifierSourceDispatch(_GSource*, int
(*)(void*), void*) () from /lib64/libQt5Core.so.5
#15 0x7f52a5171b77 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#16 0x7f52a5171f20 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#17 0x7f52a5171fac in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#18 0x7f52ab748c2f in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#19 0x7f52ab6f696a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#20 0x7f52ab5478ca in QThread::exec() () from /lib64/libQt5Core.so.5
#21 0x7f52ab54bde2 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#22 0x7f52a8b3a50b in start_thread () from /lib64/libpthread.so.0
#23 0x7f52aa8fd16f in clone () from /lib64/libc.so.6

Thread 32 (Thread 0x7f524700 (LWP 9478)):
[KCrash Handler]
#6  0x7f52aa83c660 in raise () from /lib64/libc.so.6
#7  0x7f52aa83dc41 in abort () from /lib64/libc.so.6
#8  0x7f52aa87ef17 in __libc_message () from /lib64/libc.so.6
#9  0x7f52aa88521a in malloc_printerr () from /lib64/libc.so.6
#10 0x7f52aa88700c in _int_free () from /lib64/libc.so.6
#11 0x7f52aa8896fa in _int_realloc

[kdelibs] [Bug 174354] Defaults to A4 paper, even though 'US Letter' is specified in settings

2018-01-24 Thread Garry Williams

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

--- Comment #25 from Garry Williams <gtwilli...@gmail.com> ---
It's not fixed.

Kmail 5.7.1 exhibits this behavior.

Both Okular (1.2.1) and Kmail always are set to print A4 no matter what I did
in the past.  Duplex mode is also forgotten from one print to the next.

This seems very broken since I set these options in the system and *all*
non-KDE applications respect my settings automatically.

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

[kdelibs] [Bug 174354] Defaults to A4 paper, even though 'US Letter' is specified in settings

2018-01-24 Thread Garry Williams

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

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

[digikam] [Bug 263347] print wizard ignores selected paper size, reverts to A4

2018-01-24 Thread Garry Williams

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

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

[kmail2] [Bug 389120] New: Message Preview Won't Scroll Properly on Space Character

2018-01-17 Thread Garry Williams

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

Bug ID: 389120
   Summary: Message Preview Won't Scroll Properly on Space
Character
   Product: kmail2
   Version: 5.7.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: UI
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

The message preview window used to scroll a page at a time by entering
a space character.  Once the bottom of the message was reached,
another space charater caused the selection of the next unread
message.

This behavior has been defined since forever.

Now, the only time the next unread message is selected is if the
current message doesn't overflow the preview window.

Also, the scroll a page at a time is broken.  If the message is more
than twice the vertical size of the preview window, the third space
character causes a scroll backwards!

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

[kmail2] [Bug 377355] Kmail2 does not reset scroll position in message preview/window

2018-01-17 Thread Garry Williams

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

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

[kontact] [Bug 364876] System log: kontact: Cannot open "/usr/share/zoneinfo/Eastern Standard Time"

2017-12-06 Thread Garry Williams

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

--- Comment #6 from Garry Williams <gtwilli...@gmail.com> ---
This bug went away for me.

kontact-17.08.3-1.fc27.x86_64

may have fixed it.  Two systems are now *not* complaining about "Cannot open". 
One uses gmail and the other uses davmail for Exchange.

I think this bug should now be closed.

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

[plasma4] [Bug 386180] New: CPU Frequency Display Incorrect

2017-10-25 Thread Garry Williams

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

Bug ID: 386180
   Summary: CPU Frequency Display Incorrect
   Product: plasma4
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: widget-systemloadviewer
  Assignee: plasma-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

Created attachment 108562
  --> https://bugs.kde.org/attachment.cgi?id=108562=edit
Screen shot of tooltip

CPU frequency value is displayed incorrectly on tooltip.

(It seems like it displays the maximum value instead of the currently scaled
value.)

plasma-desktop-5.10.5-1.fc27.x86_64
plasma-workspace-common-5.10.5-3.fc27.x86_64

This used to display properly in Fedora 26 versions.

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

[plasmashell] [Bug 381771] New: Plasma Crash

2017-06-28 Thread Garry Williams

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

Bug ID: 381771
   Summary: Plasma Crash
   Product: plasmashell
   Version: 5.9.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: gtwilli...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.5)

Qt Version: 5.7.1
Frameworks Version: 5.34.0
Operating System: Linux 4.11.6-201.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
- What I was doing when the application crashed:
I was closing a couple of applications on a virtual desktop.  These had been
open for several days and I no longer needed to use them.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f00ee5a1040 (LWP 1310))]

Thread 7 (Thread 0x7f0031545700 (LWP 1800)):
#0  0x7f00fb220ecd in poll () from /lib64/libc.so.6
#1  0x7f00f3fa9166 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f00f3fa927c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f00fc0276eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f00fbfd868a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f00fbe355e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f003303f2c7 in KCupsConnection::run() () from /lib64/libkcupslib.so
#7  0x7f00fbe399ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f00fa57373a in start_thread () from /lib64/libpthread.so.0
#9  0x7f00fb22ce0f in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7f0043e9c700 (LWP 1619)):
#0  0x7f00fb220ecd in poll () from /lib64/libc.so.6
#1  0x7f00f3fa9166 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f00f3fa927c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f00fc0276eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f00fbfd868a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f00fbe355e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f00ffa378b6 in QQuickPixmapReader::run() () from
/lib64/libQt5Quick.so.5
#7  0x7f00fbe399ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f00fa57373a in start_thread () from /lib64/libpthread.so.0
#9  0x7f00fb22ce0f in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f00d5602700 (LWP 1605)):
#0  0x7f00fa579460 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f0101af82f4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x7f0101af8339 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7f00fa57373a in start_thread () from /lib64/libpthread.so.0
#4  0x7f00fb22ce0f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f00d75c6700 (LWP 1603)):
#0  0x7f00fb220ecd in poll () from /lib64/libc.so.6
#1  0x7f00f3fa9166 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f00f3fa927c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f00fc0276eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f00fbfd868a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f00fbe355e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f00ff0ad4a5 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7f00fbe399ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f00fa57373a in start_thread () from /lib64/libpthread.so.0
#9  0x7f00fb22ce0f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f00dcefe700 (LWP 1521)):
#0  0x7f00fb220ecd in poll () from /lib64/libc.so.6
#1  0x7f00f3fa9166 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#2  0x7f00f3fa927c in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7f00fc0276eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#4  0x7f00fbfd868a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#5  0x7f00fbe355e3 in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x7f00ff0ad4a5 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#7  0x7f00fbe399ca in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#8  0x7f00fa57373a in start_thread () from /lib64/libpthread.so.0
#9  0x7f00fb22ce0f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f00ee59a700 (LWP 1359)):
#0  0x7f00fb220ecd in poll () from /lib64/libc.so.6
#1

[kmail2] [Bug 341114] Focus Jumps To Another Message Spontaneously When Server Refresh

2017-06-23 Thread Garry Williams

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

--- Comment #3 from Garry Williams <gtwilli...@gmail.com> ---
Still happens usually after a mail check is done on the interval I specified. 
Very irritating to be reading a message and have another message jumped to out
of the blue.

kmail-16.12.3-1.fc25.x86_64
kmail-libs-16.12.3-1.fc25.x86_64
$ kmail --version
kmail2 5.4.3
$

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

[kmail2] [Bug 336878] Position in the message list is not preserved across restarts

2017-06-23 Thread Garry Williams

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

--- Comment #4 from Garry Williams <gtwilli...@gmail.com> ---
(In reply to Denis Kurz from comment #2)
> This bug has never been confirmed for a KDE PIM version that is based on KDE
> Frameworks (5.x). Those versions differ significantly from the old 4.x
> series. Therefore, I plan to close it in around two or three months. In the
> meantime, it is set to WAITINGFORINFO to give reporters the oportunity to
> check if it is still valid. As soon as someone confirms it for a recent
> version (at least 5.1, ideally even more recent), I'll gladly reopen it.
> 
> Please understand that we lack the manpower to triage bugs reported for
> versions almost two years beyond their end of life.

This bug still persists.  It has never been corrected.  My current version is:

kmail-16.12.3-1.fc25.x86_64
kmail-libs-16.12.3-1.fc25.x86_64

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

[kmail2] [Bug 375445] KMail2 hangs with 100% CPU usage when trying to preview or read large emails from IMAP server

2017-03-23 Thread Garry Williams

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

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

[kmail2] [Bug 373201] Message List Threading Intermittently Breaks

2017-02-22 Thread Garry Williams

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

--- Comment #1 from Garry Williams <gtwilli...@gmail.com> ---
It's getting worse.  Now there's no way that I see to restore proper threading.
 Later E-mail messages that are part of a prior thread are not sorted properly.
 This looks like it's permanent -- no way to get the message list window to
sort threaded any more.

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

[kwin] [Bug 373358] New: Kwin Crash When Starting DE

2016-12-06 Thread Garry Williams

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

Bug ID: 373358
   Summary: Kwin Crash When Starting DE
   Product: kwin
   Version: 5.8.4
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.8.4)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.11-300.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

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

I simply logged in from sddm after a reboot and kwin crashed and the abrt
dialog appeared.  kwin restarted by the time I processed this bug report.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fccc4cb1940 (LWP 1082))]

Thread 7 (Thread 0x7fcca5245700 (LWP 1339)):
#0  0x7fccd7e7c460 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fccdd6c2bd4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from
/lib64/libQt5Script.so.5
#2  0x7fccdd6c2c19 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*)
() from /lib64/libQt5Script.so.5
#3  0x7fccd7e766ca in start_thread () from /lib64/libpthread.so.0
#4  0x7fccd5054f6f in clone () from /lib64/libc.so.6

Thread 6 (Thread 0x7fcca6388700 (LWP 1246)):
#0  0x7fccd7e7c460 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fcca713aad3 in radeon_drm_cs_emit_ioctl () from
/usr/lib64/dri/r600_dri.so
#2  0x7fcca713a217 in impl_thrd_routine () from /usr/lib64/dri/r600_dri.so
#3  0x7fccd7e766ca in start_thread () from /lib64/libpthread.so.0
#4  0x7fccd5054f6f in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fcca7fff700 (LWP 1239)):
[KCrash Handler]
#6  0x7fccd5da485f in QLockFilePrivate::tryLock_sys() () from
/lib64/libQt5Core.so.5
#7  0x7fccd5d51a6d in QLockFile::tryLock(int) () from
/lib64/libQt5Core.so.5
#8  0x7fccda841439 in KConfigIniBackend::lock() () from
/lib64/libKF5ConfigCore.so.5
#9  0x7fccda82b0e0 in KConfig::sync() () from /lib64/libKF5ConfigCore.so.5
#10 0x7fccb7355ea5 in
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) () from
/usr/lib64/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so
#11 0x7fccd5e28326 in QMetaObject::activate(QObject*, int, int, void**) ()
from /lib64/libQt5Core.so.5
#12 0x7fccd5e344d8 in QTimer::timerEvent(QTimerEvent*) () from
/lib64/libQt5Core.so.5
#13 0x7fccd5e2908b in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#14 0x7fccd664996c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#15 0x7fccd665 in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#16 0x7fccd5e0112a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#17 0x7fccd5e4e38b in QTimerInfoList::activateTimers() () from
/lib64/libQt5Core.so.5
#18 0x7fccd5e4c710 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#19 0x7fccd5e000ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#20 0x7fccd5c5d643 in QThread::exec() () from /lib64/libQt5Core.so.5
#21 0x7fccd5c61a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#22 0x7fccd7e766ca in start_thread () from /lib64/libpthread.so.0
#23 0x7fccd5054f6f in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fccb6210700 (LWP 1220)):
#0  0x7fccd50490d1 in ppoll () from /lib64/libc.so.6
#1  0x7fccd5e4b051 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /lib64/libQt5Core.so.5
#2  0x7fccd5e4c566 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7fccd5e000ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#4  0x7fccd5c5d643 in QThread::exec() () from /lib64/libQt5Core.so.5
#5  0x7fccdc91a735 in QQmlThreadPrivate::run() () from
/lib64/libQt5Qml.so.5
#6  0x7fccd5c61a1a in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#7  0x7fccd7e766ca in start_thread () from /lib64/libpthread.so.0
#8  0x7fccd5054f6f in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7fccb7d75700 (LWP 1174)):
#0  0x7fccd50490d1 in ppoll () from /lib64/libc.so.6
#1  0x7fccd5e4b051 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() from /lib64/libQt5Core.so.5
#2  0x7fccd5e4c566 in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#3  0x7fccd5e000ba in
QEventLoop::exec(QFlags) () from

[Akonadi] [Bug 348103] Thousands of empty messages with duplicate headers created in accounts

2016-12-03 Thread Garry Williams

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

 CC|gtwilli...@gmail.com|

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

[kontact] [Bug 351876] Crash Starting Kmail (Kontact)

2016-12-03 Thread Garry Williams

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

 Resolution|--- |LATER
 Status|UNCONFIRMED |RESOLVED

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

[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"

2016-12-03 Thread Garry Williams

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

 CC|gtwilli...@gmail.com|

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

[kmail2] [Bug 373201] New: Message List Threading Intermittently Breaks

2016-12-02 Thread Garry Williams

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

Bug ID: 373201
   Summary: Message List Threading Intermittently Breaks
   Product: kmail2
   Version: 5.3.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: message list
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com
  Target Milestone: ---

Threading frequently fails with newer messages not placed under the original
thread.

Here's how I perceive this problem:

Right click on Subject header in Message list and select Aggregation ->
Configure

Select Standard Mailing List

Click Groups & Threading

Select Perfect or Perfect and by References

Click OK

Now Message List is threaded correctly.

Wait for new messages to arrive.

Threading is now broken (sometimes).

Repeat steps above to restore correct threading.

I see this problem at work using an Exchange server proxied through an IMAP
proxy (davmail) and at home using Gmail directly.

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

[kontact] [Bug 364876] System log: kontact: Cannot open "/usr/share/zoneinfo/Eastern Standard Time"

2016-12-02 Thread Garry Williams

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #3 from Garry Williams <gtwilli...@gmail.com> ---
It's back with kontact-16.08.2-1.fc25.x86_64

kontact[9252]: Cannot open  "/usr/share/zoneinfo/Eastern Standard Time"

$ journalctl -b|grep -c 'Eastern Standard Time'
512
$

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

[kmail2] [Bug 341114] Focus Jumps To Another Message Spontaneously When Server Refresh

2016-11-11 Thread Garry Williams

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

--- Comment #2 from Garry Williams <gtwilli...@gmail.com> ---
This irritating bug persist to this day with kmail2 5.3.0 (Fedora rpm
kmail-16.08.2-1.fc24.x86_64).

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

[kmail2] [Bug 369416] regression: can no longer drag and drop email addresses from message headers

2016-10-17 Thread Garry Williams via KDE Bugzilla

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

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

[kmail2] [Bug 368378] Regression in kMail 5.3.x: Drag and drop of attachments from a received mail into the composer does not work any more

2016-10-17 Thread Garry Williams via KDE Bugzilla

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

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

[kmail2] [Bug 366652] Drag and drop attachments in Kmail has stopped working

2016-10-17 Thread Garry Williams via KDE Bugzilla

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

 CC||gtwilli...@gmail.com

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

[kmail2] [Bug 370980] New: Space Key Doesn't Show Next Unread Message

2016-10-16 Thread Garry Williams via KDE Bugzilla

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

Bug ID: 370980
   Summary: Space Key Doesn't Show Next Unread Message
   Product: kmail2
   Version: 5.3.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com

The space key has always paged the message until the bottom and then displays
the next unread message.  This behavior has been how kmail has worked since the
beginning, as far as I know.

Please restore this behavior.

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

[kmail2] [Bug 178697] Screen Geometry not Remembered Between Invocations

2016-09-24 Thread Garry Williams via KDE Bugzilla

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

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

[kontact] [Bug 364876] System log: kontact: Cannot open "/usr/share/zoneinfo/Eastern Standard Time"

2016-08-04 Thread Garry Williams via KDE Bugzilla

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

Garry Williams <gtwilli...@gmail.com> changed:

   What|Removed |Added

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

--- Comment #2 from Garry Williams <gtwilli...@gmail.com> ---
Seems to be fixed now also.

Sorry for the noise.

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

[kontact] [Bug 364876] New: System log: kontact: Cannot open "/usr/share/zoneinfo/Eastern Standard Time"

2016-06-28 Thread Garry Williams via KDE Bugzilla

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

Bug ID: 364876
   Summary: System log: kontact: Cannot open
"/usr/share/zoneinfo/Eastern Standard Time"
   Product: kontact
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: gtwilli...@gmail.com

Kontact constantly sends the same message to the system log.

$ journalctl -b|grep -c 'Eastern Standard Time'
1364
$

Reproducible: Always


Actual Results:  
Thousands of log messages daily.

Expected Results:  
No (or perhaps one) log message.

kontact-15.12.3-1.fc24.x86_64

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

94 matches

Mail list logo