[KClock] [Bug 480389] Panel icon doesn't do anything on clicking

[leon pollak]

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

leon pollak  changed:

   What|Removed |Added

 CC||le...@plris.com

--- Comment #6 from leon pollak  ---
Voting +100 for icon to open the application - too annoying to go to krunner
and type...

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

[KClock] [Bug 478236] New Alarm dialogue is still in 12 hour format after enabling 24 hour format

[leon pollak]

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

leon pollak  changed:

   What|Removed |Added

 CC||le...@plris.com

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

[digikam] [Bug 475840] Theme icons and text have gone dark on a dark background

[Leon Loberman]

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

--- Comment #5 from Leon Loberman  ---
Hi Gilles

I'm not sure how to reproduce it.  I can do so by manually going in to the
icon settings but I didn't do that to cause the original issue. I must have
done some kind of keyboard combination but I don't know what - sorry.

Best

Leon


On Mon, 23 Oct 2023 at 06:49,  wrote:

> https://bugs.kde.org/show_bug.cgi?id=475840
>
> caulier.gil...@gmail.com changed:
>
>What|Removed |Added
>
> 
>  CC||caulier.gil...@gmail.com
>
> --- Comment #4 from caulier.gil...@gmail.com ---
> @Leon
>
> The digiKam 8.2.0 pre-release for MacOS is avaialble for testing :
>
> https://files.kde.org/digikam/
>
> Problem still reproducible on your computer ?
>
> Thanks in advance
>
> Gilles Caulier
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[digikam] [Bug 475840] Theme icons and text have gone dark on a dark background

[Leon Loberman]

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

--- Comment #2 from Leon Loberman  ---
Thanks Maik

Setting that and Icons to Breeze seems to have done the trick. Looking better
now.

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

[digikam] [Bug 475840] New: Theme icons and text have gone dark on a dark background

[Leon Loberman]

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

Bug ID: 475840
   Summary: Theme icons and text have gone dark on a dark
background
Classification: Applications
   Product: digikam
   Version: 8.1.0
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Usability-Themes
  Assignee: digikam-bugs-n...@kde.org
  Reporter: l...@loberman.net
  Target Milestone: ---

Created attachment 162430
  --> https://bugs.kde.org/attachment.cgi?id=162430=edit
Screenshot showing dark icons

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1.  Select Settings/Themes/Default 

OBSERVED RESULT
Icons and text are dark

EXPECTED RESULT
Icons and text should be on a grey background?

SOFTWARE/OS VERSIONS

macOS: Ventura 13.6
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 5.106.0
Qt Version: 5.15.10

ADDITIONAL INFORMATION
This may have been caused by an inadvertent key combination but I don't know
what I did :-(
Switching to different themes will give me visible text and icons but I rather
preferred the default.
I've tried using White Balance but that gives me the same issue.
Tried switching icon theme in preferences/miscellaneous/appearance but no
difference

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

[apper] [Bug 473498] New: Apper crashes after update

[Leon]

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

Bug ID: 473498
   Summary: Apper crashes after update
Classification: Applications
   Product: apper
   Version: 1.0.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dantt...@gmail.com
  Reporter: supp...@bb-services.co.za
  Target Milestone: ---

Application: apper (1.0.0)

Qt Version: 5.15.10
Frameworks Version: 5.108.0
Operating System: Linux 6.4.10-200.fc38.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 38 (KDE Plasma)
DrKonqi: 5.27.6 [KCrashBackend]

-- Information about the crash:
when an update finishes and it re-checks, it crashes

The crash can be reproduced every time.

-- Backtrace:
Application: Apper (apper), signal: Segmentation fault

[KCrash Handler]
#4  0x7f10eaf708a3 in QHash::erase(QHash::const_iterator) () from
/usr/lib64/apper/libapper_private.so
#5  0x7f10eaf6ce4b in PackageModel::clearSelectedNotPresent() () from
/usr/lib64/apper/libapper_private.so
#6  0x5646e1fd3ace in Updater::getUpdatesFinished() ()
#7  0x7f10e94e8461 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#8  0x7f10eaee04d8 in
PackageKit::Transaction::finished(PackageKit::Transaction::Exit, unsigned int)
() from /lib64/libpackagekitqt5.so.1
#9  0x7f10eaedf668 in PackageKit::Transaction::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libpackagekitqt5.so.1
#10 0x7f10e94e85e8 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#11 0x7f10eaeed1d8 in
OrgFreedesktopPackageKitTransactionInterface::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libpackagekitqt5.so.1
#12 0x7f10eaeedf02 in
OrgFreedesktopPackageKitTransactionInterface::qt_metacall(QMetaObject::Call,
int, void**) () from /lib64/libpackagekitqt5.so.1
#13 0x7f10e9ed438b in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5
#14 0x7f10e94ded0b in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#15 0x7f10ea1aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#16 0x7f10e94b4188 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#17 0x7f10e94b7635 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#18 0x7f10e9506c3f in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#19 0x7f10e7f1348c in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#20 0x7f10e7f71648 in g_main_context_iterate.isra () from
/lib64/libglib-2.0.so.0
#21 0x7f10e7f10b13 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#22 0x7f10e9506729 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#23 0x7f10e94b2b4b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#24 0x7f10e94baddb in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#25 0x5646e1fc7dec in main ()
[Inferior 1 (process 50984) detached]

The reporter indicates this bug may be a duplicate of or related to bug 413282,
bug 418428, bug 424953, bug 437291.

Reported using DrKonqi

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

[krusader] [Bug 471272] New: Nice to have an ability to divide each panel into two columns as it is done in Midnight Commander.

[leon pollak]

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

Bug ID: 471272
   Summary: Nice to have an ability to divide each panel into two
columns as it is done in Midnight Commander.
Classification: Applications
   Product: krusader
   Version: 2.8.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: le...@plris.com
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

It will be nice to have an ability to divide each panel into two columns as it
is done in Midnight Commander.
Today a lot of the space is not used while may be used as the MC does.

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

[plasmashell] [Bug 469810] When using non-password auth method, always show the UI in the lock screen without having to move the mouse first

[Ray Leon]

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

--- Comment #2 from Ray Leon  ---
It seems like unlimited timeouts / timeouts greater than 99 seconds are
currently broken in pam_fprintd
(https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/147), so this might
not be fixable at the moment.

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

[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable

[Ray Leon]

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

--- Comment #4 from Ray Leon  ---
(In reply to Ray Leon from comment #3)
> Clicking anywhere on the "Night color temperature" slider in System Settings
> (and then closing without saving) also seems to reset it.

Should've read more than the last comment. Sorry for the duplicate lol

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

[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable

[Ray Leon]

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

--- Comment #3 from Ray Leon  ---
Clicking anywhere on the "Night color temperature" slider in System Settings
(and then closing without saving) also seems to reset it.

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

[kwin] [Bug 468295] 5.27.4 Night color remains on at sunrise, can't disable

[Ray Leon]

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

Ray Leon  changed:

   What|Removed |Added

 CC||maxwellleon55...@gmail.com

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

[kscreenlocker] [Bug 469810] New: Allow unlocking without pressing Enter or moving the mouse (for passwordless authentication)

[Ray Leon]

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

Bug ID: 469810
   Summary: Allow unlocking without pressing Enter or moving the
mouse (for passwordless authentication)
Classification: Plasma
   Product: kscreenlocker
   Version: 5.27.5
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: maxwellleon55...@gmail.com
  Target Milestone: ---

SUMMARY
I've recently set up fingerprint authentication with the KDE lock screen, but I
still need to get to the password entry screen by moving the mouse before
fingerprint authentication starts working. It'd be nice if I could just press
on the fingerprint reader in order to unlock the screen.

STEPS TO REPRODUCE
1. Set up fprintd and add 'auth sufficient pam_fprintd.so' to /etc/pam.d/kde
2. Lock the screen
3. Try to use the fingerprint reader without using the mouse

OBSERVED RESULT
Screen should unlock if fingerprint matches

EXPECTED RESULT
I have to disturb the screen somehow before I can unlock it.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux (rolling)
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Graphics Platform: Wayland

ADDITIONAL INFORMATION
Here's my `/etc/pam.d/kde`:
```
#%PAM-1.0

authsufficient  pam_fprintd.so
authinclude system-login

account include system-login

passwordinclude system-login

session include system-login
```

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

[krusader] [Bug 465820] Krusader and FTP connections

[Leon]

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

Leon  changed:

   What|Removed |Added

 CC||supp...@bb-services.co.za

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

[krusader] [Bug 465820] Krusader and FTP connections

[Leon]

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

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

krusader (2.8.0 "A New Day") using Qt 5.15.8

Unstable connections, like on cellular networks is probale contributing factor

-- Backtrace (Reduced):
#4  0x7f923bb5e0f0 in vtable for QObjectPrivate () from
/lib64/libQt5Core.so.5
#6  0x55617311814e in ListPanelFunc::doRefresh() ()
#7  0x7f923b8d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#8  0x7f923b8d421e in QTimer::timeout(QTimer::QPrivateSignal) () from
/lib64/libQt5Core.so.5
#9  0x7f923b8c7fc5 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5

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

[krusader] [Bug 468323] New: Crashes whiel deleting large directories

[Leon]

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

Bug ID: 468323
   Summary: Crashes whiel deleting large directories
Classification: Applications
   Product: krusader
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: supp...@bb-services.co.za
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

Application: krusader (2.8.0 "A New Day")

Qt Version: 5.15.8
Frameworks Version: 5.104.0
Operating System: Linux 6.2.9-200.fc37.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 37 (KDE Plasma)
DrKonqi: 5.27.4 [KCrashBackend]

-- Information about the crash:
When connections are not fast, probability of crashes are high

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault

[KCrash Handler]
#4  0x in ?? ()
#5  0x7fe0aa6c7d45 in QObject::property(char const*) const () from
/lib64/libQt5Core.so.5
#6  0x7fe0abbc7774 in KUiServerV2JobTracker::registerJob(KJob*) () from
/lib64/libKF5JobWidgets.so.5
#7  0x7fe0abbc47cc in
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) () from /lib64/libKF5JobWidgets.so.5
#8  0x7fe0aa6d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#9  0x7fe0aa6d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x7fe0ab1e0843 in QDBusServiceWatcher::serviceOwnerChanged(QString
const&, QString const&, QString const&) () from /lib64/libQt5DBus.so.5
#11 0x7fe0ab1e1182 in QDBusServiceWatcher::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libQt5DBus.so.5
#12 0x7fe0ab1e163b in QDBusServiceWatcher::qt_metacall(QMetaObject::Call,
int, void**) () from /lib64/libQt5DBus.so.5
#13 0x7fe0ab1920bb in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5
#14 0x7fe0aa6c8134 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#15 0x7fe0ab3aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#16 0x7fe0aa69d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#17 0x7fe0aa6a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#18 0x7fe0aa6eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#19 0x7fe0a8f16c7f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#20 0x7fe0a8f6d118 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#21 0x7fe0a8f13f00 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#22 0x7fe0aa6ee5fa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#23 0x7fe0aa69bf3a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#24 0x55c8ac1099dd in DefaultFileSystem::refreshInternal(QUrl const&, bool)
()
#25 0x55c8ac19a25e in FileSystem::scanOrRefresh(QUrl const&, bool) [clone
.constprop.0] ()
#26 0x55c8ac10df2b in FileSystemProvider::refreshFilesystems(QUrl const&,
bool) ()
#27 0x7fe0aa6d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#28 0x55c8ac103d40 in
QtPrivate::QFunctorSlotObject const&)::{lambda()#1}, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
#29 0x7fe0aa6d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#30 0x7fe0abb4c449 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib64/libKF5CoreAddons.so.5
#31 0x7fe0abb51edb in KJob::finishJob(bool) () from
/lib64/libKF5CoreAddons.so.5
#32 0x7fe0abb51f8e in KJob::kill(KJob::KillVerbosity) () from
/lib64/libKF5CoreAddons.so.5
#33 0x7fe0aa6d0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#34 0x7fe0abbc6c23 in
OrgKdeJobViewV3Interface::qt_metacall(QMetaObject::Call, int, void**) () from
/lib64/libKF5JobWidgets.so.5
#35 0x7fe0ab1920bb in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5
#36 0x7fe0aa6c8134 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#37 0x7fe0ab3aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#38 0x7fe0aa69d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#39 0x7fe0aa6a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#40 0x7fe0aa6eeb07 in postEventSourceDispatch(_GSource*, int 

[digikam] [Bug 467333] Error on exiftool install on Win10 64bit

[Leon Loberman]

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

Leon Loberman  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

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

[digikam] [Bug 467333] Error on exiftool install on Win10 64bit

[Leon Loberman]

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

--- Comment #2 from Leon Loberman  ---
(In reply to caulier.gilles from comment #1)
> Open the Windows task manager and kill all exiftool instances running in
> background.
> 
> Best
> 
> Gilles Caulier

Thank you Gilles - confirmed as resolution

Leon

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

[digikam] [Bug 467333] Error on exiftool install on Win10 64bit

[Leon Loberman]

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

Leon Loberman  changed:

   What|Removed |Added

 CC||l...@loberman.net

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

[digikam] [Bug 467333] New: Error on exiftool install on Win10 64bit

[Leon Loberman]

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

Bug ID: 467333
   Summary: Error on exiftool install on Win10 64bit
Classification: Applications
   Product: digikam
   Version: unspecified
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Metadata-ExifTool
  Assignee: digikam-bugs-n...@kde.org
  Reporter: l...@loberman.net
  Target Milestone: ---

Created attachment 157272
  --> https://bugs.kde.org/attachment.cgi?id=157272=edit
Screenshot of Error on exiftool install on Win10 64bit

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Installing 7.10.0 on Windows 10 64-bit
2. Get the attached failure
3. Ignore allows install to continue


OBSERVED RESULT
Exif data still seems to work after install

EXPECTED RESULT
Should install without error?

SOFTWARE/OS VERSIONS
Windows: 10 64-bit


ADDITIONAL INFORMATION

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

[krusader] [Bug 465820] New: Krusader and FTP connections

[Leon]

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

Bug ID: 465820
   Summary: Krusader and FTP connections
Classification: Applications
   Product: krusader
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: supp...@bb-services.co.za
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

Application: krusader (2.8.0 "A New Day")

Qt Version: 5.15.8
Frameworks Version: 5.102.0
Operating System: Linux 6.1.10-200.fc37.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 37 (KDE Plasma)
DrKonqi: 5.26.5 [KCrashBackend]

-- Information about the crash:
When using FTP and network is not stabel, krusader becomes unstable or crashes

The crash can be reproduced every time.

-- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault

[KCrash Handler]
#4  0x55abdf463e70 in ?? ()
#5  0x7fb821ac7d45 in QObject::property(char const*) const () from
/lib64/libQt5Core.so.5
#6  0x7fb822fec794 in KUiServerV2JobTracker::registerJob(KJob*) () from
/lib64/libKF5JobWidgets.so.5
#7  0x7fb822fe97fc in
QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*,
void**, bool*) () from /lib64/libKF5JobWidgets.so.5
#8  0x7fb821ad0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#9  0x7fb821ad0e96 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x7fb8225e0843 in QDBusServiceWatcher::serviceOwnerChanged(QString
const&, QString const&, QString const&) () from /lib64/libQt5DBus.so.5
#11 0x7fb8225e1182 in QDBusServiceWatcher::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libQt5DBus.so.5
#12 0x7fb8225e163b in QDBusServiceWatcher::qt_metacall(QMetaObject::Call,
int, void**) () from /lib64/libQt5DBus.so.5
#13 0x7fb8225920bb in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5
#14 0x7fb821ac8134 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#15 0x7fb8227aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#16 0x7fb821a9d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#17 0x7fb821aa0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#18 0x7fb821aeeb07 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#19 0x7fb820319cbf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#20 0x7fb82036f598 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#21 0x7fb820316f40 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#22 0x7fb821aee5fa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#23 0x7fb821a9bf3a in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#24 0x7fb821aa4002 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#25 0x55abdc8cc16f in main ()
[Inferior 1 (process 114937) detached]

Reported using DrKonqi

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

[krusader] [Bug 427570] Krusader crashes on unstable connections

[Leon]

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

Leon  changed:

   What|Removed |Added

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

--- Comment #6 from Leon  ---
I changed my inline editor to Kdevelop a few months ago, and it seems that it
crashes less. It did die again a few days ago, but I was unable to replicate it
now. I tried to simulate connection issues, but till now has not crashed. In
all, it does appear to crash less now. I will have to work with it hard again
and report when it crashes.

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

[okular] [Bug 449717] When zooming with 2 fingers on a touchscreen, Okular also scrolls through the document, causing me to lose my place.

[Ray Leon]

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

--- Comment #5 from Ray Leon  ---
(In reply to andreas.naumann from comment #3)
> In you videos, you show two pages side by side. Does it help, if you disable
> the "continous view" and show only one page? 
> In that configuration, okular stays at the page and zooms only.
> 
> If I enable the view mode "overview", I get your behavior.  In that
> configuration, I would rather ask, what zoom in means to the developer.  
> Looks to me, like okular increases the view starting from the upper left
> corner. 
> 
> It would feel more natural, if okular zooms into the area next to the finger
> position. Do we know the mouse position, when zooming?

Sorry for the late response. Disabling continuous view doesn't solve the
problem, although I guess it makes it easier to manage since the view's only
moving around on one page if that makes sense.
I also think you're right about the 'increasing view from the upper left
corner' part.

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

[kdevelop] [Bug 457542] New: KDevelop crash when "Apply the Settings"

[Leon Lee Ann]

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

Bug ID: 457542
   Summary: KDevelop crash when "Apply the Settings"
   Product: kdevelop
   Version: 5.5.0
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: leon.lee@gmail.com
  Target Milestone: ---

Application: kdevelop (5.5.0)

Qt Version: 5.12.8
Frameworks Version: 5.68.0
Operating System: Linux 5.11.15-051115-generic x86_64
Windowing system: X11
Distribution: Ubuntu 20.04.4 LTS

-- Information about the crash:
1.run KDevelop(with pick up a session)
2.Create a new session
3.Settings -> Configure Kdevelop
4.Plugins -> Uncheck "Clang-Tidy Support" and "Clazy Support"
5.Don't click "OK" or "Apply"
6.Switch to "Source Formatter" category in same window
7.Now a dialog will pop up automatically to ask us wether "Apply" or "Discard"
the changes
8.Click "Apply"
crashed!

The crash can be reproduced every time.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9141023940 (LWP 3861394))]

Thread 40 (Thread 0x7f90896f8700 (LWP 3861551)):
#0  0x7f914b78699f in __GI___poll (fds=0x7f90800282f0, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f9141b951d6 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7f9141b86841 in pa_mainloop_poll () from
/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7f9141b86ec3 in pa_mainloop_iterate () from
/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f9141b86f70 in pa_mainloop_run () from
/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f9141b9511d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f91416e972c in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#7  0x7f9148bc1609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f914b793133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 39 (Thread 0x7f9088ef7700 (LWP 3861456)):
#0  0x7f9148308909 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f914830929b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f91483094a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f914bd28453 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f914bccf3ab in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f914bb07785 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9089769679 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#7  0x7f914bb089d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f9148bc1609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f914b793133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 38 (Thread 0x7f908a47f700 (LWP 3861440)):
#0  0x7f914b78699f in __GI___poll (fds=0x7f907c0025e0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f914830936e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f91483094a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f914bd28453 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f914bccf3ab in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f914bb07785 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f914bb089d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9148bc1609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f914b793133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 37 (Thread 0x7f908b5ce700 (LWP 3861432)):
#0  0x7f914b78699f in __GI___poll (fds=0x7f90840029e0, nfds=1,
timeout=10378) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f914830936e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f91483094a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f914bd28453 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f914bccf3ab in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f914bb07785 in QThread::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f914bb089d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9148bc1609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f914b793133 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 36 (Thread 0x7f90b1ffb700 (LWP 3861430)):
#0  __GI___libc_read (nbytes=16, buf=0x7f90b1ffaa30, fd=18) at

[apper] [Bug 437291] Apper crashes after finishing update

[Leon]

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

Leon  changed:

   What|Removed |Added

 CC||supp...@bb-services.co.za

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

[apper] [Bug 437291] Apper crashes after finishing update

[Leon]

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

--- Comment #2 from Leon  ---
Created attachment 150382
  --> https://bugs.kde.org/attachment.cgi?id=150382=edit
New crash information added by DrKonqi

apper (1.0.0) using Qt 5.15.2

- What I was doing when the application crashed:
Simply run an update. After the update is done and attempting to load the list
again. it crashes

-- Backtrace (Reduced):
#4  0x7fc179322737 in QHashData::nextNode(QHashData::Node*) () from
/lib64/libQt5Core.so.5
#5  0x7fc17afd787a in QHash::erase(QHash::const_iterator) () from
/usr/lib64/apper/libapper_private.so
#6  0x7fc17afd3e4b in PackageModel::clearSelectedNotPresent() () from
/usr/lib64/apper/libapper_private.so
#7  0x5563b6070ace in Updater::getUpdatesFinished() ()
#8  0x7fc1794da7d9 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5

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

[apper] [Bug 414047] Apper crashes when applying updates

[Leon]

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

Leon  changed:

   What|Removed |Added

 CC||supp...@bb-services.co.za

--- Comment #11 from Leon  ---
Created attachment 148294
  --> https://bugs.kde.org/attachment.cgi?id=148294=edit
Saved crash info

Crashes after updates applied

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

[okular] [Bug 449717] When zooming with 2 fingers on a touchscreen, Okular also scrolls through the document, causing me to lose my place.

[Ray Leon]

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

--- Comment #2 from Ray Leon  ---
This appears to only happen in browse mode (not when text selection or
highlight are selected)

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

[kdeconnect] [Bug 449719] KDE Connect crashes when opening a message

[Ray Leon]

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

--- Comment #7 from Ray Leon  ---
make code blocks?

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

[kdeconnect] [Bug 449719] KDE Connect crashes when opening a message

[Ray Leon]

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

--- Comment #6 from Ray Leon  ---
Thanks, I think that fixed it!
Changing "ConversationAddress sender = message.addresses().first();" in
conversationmodel.cpp to 
`
>ConversationAddress sender;
>if (!message.addresses().isEmpty()) {
>sender = message.addresses().first();
>}
`
seems to prevent the crashing.
I don't really know how to commit the changes though, would you mind doing
that?
P.S. how do you

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

[kdeconnect] [Bug 449719] KDE Connect crashes when opening a message

[Ray Leon]

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

--- Comment #3 from Ray Leon  ---
(In reply to Nathan from comment #2)
> I have this issue all the time, and right now I need it more than ever as I
> dropped my phone last weekend which smashed the display. Now KDE Connect is
> the only way I can access the data on my old phone but because of this major
> bug I am unable to access the sms conversations. I have noticed that this
> issue seems to 'build up'. For example if I open a small length
> conversation, they will display fine but will segfault opening a second. If
> I open a large one it will immediately segfault

This mirrors what I've been experiencing

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

[kdeconnect] [Bug 449719] KDE Connect crashes when opening a message

[Ray Leon]

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

--- Comment #1 from Ray Leon  ---
Actual backtrace: 
Thread 1 "kdeconnect-sms" received signal SIGSEGV, Segmentation fault.
ConversationModel::createRowFromMessage(ConversationMessage const&, int) [clone
.constprop.0] (this=this@entry=0x7fffe0003f20, message=..., pos=0) at
/usr/src/debug/kdeconnect-kde-21.12.2/smsapp/conversationmodel.cpp:145
145ConversationAddress sender = message.addresses().first();
(gdb) backtrace
#0  ConversationModel::createRowFromMessage(ConversationMessage const&, int)
[clone .constprop.0] (
this=this@entry=0x7fffe0003f20, message=..., pos=0)
at /usr/src/debug/kdeconnect-kde-21.12.2/smsapp/conversationmodel.cpp:145
#1  0x555699f5 in ConversationModel::handleConversationUpdate (msg=...,
this=0x7fffe0003f20)
at /usr/src/debug/kdeconnect-kde-21.12.2/smsapp/conversationmodel.cpp:189
#2  ConversationModel::qt_static_metacall (_o=0x7fffe0003f20, _c=, _id=, 
_a=0x7fffdaf0) at
/usr/src/debug/build/smsapp/kdeconnect-sms_autogen/EWIEGA46WW/moc_conversationmodel.cpp:161
#3  0x76484ddf in ?? () from /usr/lib/libQt5Core.so.5
#4  0x77f6e481 in
OrgKdeKdeconnectDeviceConversationsInterface::conversationUpdated (_t1=..., 
this=) at
/usr/src/debug/build/interfaces/conversationsinterface.moc:265
#5  OrgKdeKdeconnectDeviceConversationsInterface::qt_static_metacall
(_o=0x567a7510, _c=, 
_id=, _a=0x7fffdc40) at
/usr/src/debug/build/interfaces/conversationsinterface.moc:138
#6  0x77f5b873 in
OrgKdeKdeconnectDeviceConversationsInterface::qt_metacall (_a=0x7fffdc40,
_id=4, 
_c=QMetaObject::InvokeMetaMethod, this=0x567a7510)
at /usr/src/debug/build/interfaces/conversationsinterface.moc:223
#7  DeviceConversationsDbusInterface::qt_metacall (this=0x567a7510,
_c=QMetaObject::InvokeMetaMethod, 
_id=, _a=0x7fffdc40)
at
/usr/src/debug/build/interfaces/kdeconnectinterfaces_autogen/EWIEGA46WW/moc_dbusinterfaces.cpp:958
#8  0x7746afae in ?? () from /usr/lib/libQt5DBus.so.5
#9  0x76477e76 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#10 0x76ec61a6 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#11 0x7645416a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#12 0x76454c69 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) ()
   from /usr/lib/libQt5Core.so.5
#13 0x7649b548 in ?? () from /usr/lib/libQt5Core.so.5
#14 0x74d64f13 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#15 0x74dbb0d9 in ?? () from /usr/lib/libglib-2.0.so.0
#16 0x74d62485 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#17 0x7649f44a in
QEventDispatcherGlib::processEvents(QFlags) ()
   from /usr/lib/libQt5Core.so.5
#18 0x7644c44b in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#19 0x76457b97 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#20 0x555603ef in main (argc=, argv=0x7fffe218)
at /usr/src/debug/kdeconnect-kde-21.12.2/smsapp/main.cpp:87

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

[kdeconnect] [Bug 449719] New: KDE Connect crashes when opening a message

[Ray Leon]

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

Bug ID: 449719
   Summary: KDE Connect crashes when opening a message
   Product: kdeconnect
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: messaging-application
  Assignee: si...@ergotech.com
  Reporter: maxwellleon55...@gmail.com
  Target Milestone: ---

Created attachment 146359
  --> https://bugs.kde.org/attachment.cgi?id=146359=edit
Video of the aforementioned crash.

SUMMARY
When opening a conversation in the KDE Connect messages app, the app segfaults.


STEPS TO REPRODUCE
1. Hook up KDE Connect to your Android phone (I have a Samsung Galaxy S21
running Android 12)
2. Open the KDE Connect SMS app and click on a conversation

OBSERVED RESULT

qrc:/qml/ChatMessage.qml:109: TypeError: Cannot read property 'length' of
undefined
qrc:/qml/SendingArea.qml:69:17: QML TextArea: Possible anchor loop detected on
fill.

Thread 1 "kdeconnect-sms" received signal SIGSEGV, Segmentation fault.


EXPECTED RESULT
Conversation opens.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux x86_64, with all packages up to date
(available in About System)
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Backtrace (and additional stuff):
> gdb kdeconnect-sms
> 
GNU gdb (GDB) 11.2
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kdeconnect-sms...
Reading symbols from /usr/lib/debug/usr/bin/kdeconnect-sms.debug...
(gdb) run
Starting program: /usr/bin/kdeconnect-sms 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x70af2640 (LWP 802069)]
[New Thread 0x702f1640 (LWP 802070)]
[New Thread 0x7fffefaf0640 (LWP 802071)]
[New Thread 0x7fffee11d640 (LWP 802072)]
[New Thread 0x7fffde1f1640 (LWP 802073)]
[New Thread 0x7fffdd9f0640 (LWP 802074)]
[New Thread 0x7fffdd1ef640 (LWP 802075)]
[New Thread 0x7fffdc9ee640 (LWP 802076)]
[New Thread 0x7fffd17d1640 (LWP 802077)]
[New Thread 0x7fffd0fd0640 (LWP 802078)]
[New Thread 0x7fffbbfff640 (LWP 802079)]
qrc:/qml/ConversationList.qml:51: TypeError: Cannot read property 'text' of
null
qrc:/qml/ConversationList.qml:267: TypeError: Cannot read property 'text' of
null
qrc:/qml/ConversationList.qml:267: TypeError: Cannot read property 'text' of
null
qrc:/qml/ConversationList.qml:51: TypeError: Cannot read property 'text' of
null
no addresses! "A"
no addresses! "Should I bring anything?"
no addresses! ""
[New Thread 0x7fffbb7fe640 (LWP 802081)]
[New Thread 0x7fffbaffd640 (LWP 802082)]
[New Thread 0x7fffba5fc640 (LWP 802083)]
file:///usr/lib/qt/qml/org/kde/kirigami.2/templates/InlineMessage.qml:261:9:
QML ActionToolBar: Binding loop detected for property "atBottom"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so" Error: "Cannot load library
/usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so: (libaspell.so.15: cannot open
shared object file: No such file or directory)"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library
/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: cannot open
shared object file: No such file or directory)"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: "Cannot load library
/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so: (libvoikko.so.1: cannot open
shared object file: No such file or directory)"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so" Error: "Cannot load library
/usr/lib/qt/plugins/kf5/sonnet/sonnet_aspell.so: (libaspell.so.15: cannot open
shared object file: No such file or directory)"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so" Error: "Cannot load library
/usr/lib/qt/plugins/kf5/sonnet/sonnet_hspell.so: (libhspell.so.0: cannot open
shared object file: No such file or directory)"
kf.sonnet.core: Sonnet: Unable to load plugin
"/usr/lib/qt/plugins/kf5/sonnet/sonnet_voikko.so" Error: 

[okular] [Bug 449717] When zooming with 2 fingers on a touchscreen, Okular also scrolls through the document, causing me to lose my place.

[Ray Leon]

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

Ray Leon  changed:

   What|Removed |Added

 Attachment #146357|0   |1
is obsolete||

--- Comment #1 from Ray Leon  ---
Created attachment 146358
  --> https://bugs.kde.org/attachment.cgi?id=146358=edit
Video transcoded to .webm. Apologies, I skimmed the bug reporting guidelines a
bit too fast.

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

[okular] [Bug 449717] New: When zooming with 2 fingers on a touchscreen, Okular also scrolls through the document, causing me to lose my place.

[Ray Leon]

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

Bug ID: 449717
   Summary: When zooming with 2 fingers on a touchscreen, Okular
also scrolls through the document, causing me to lose
my place.
   Product: okular
   Version: 21.12.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: maxwellleon55...@gmail.com
  Target Milestone: ---

Created attachment 146357
  --> https://bugs.kde.org/attachment.cgi?id=146357=edit
Video of me zooming in and out on a digital copy of a textbook

SUMMARY
When zooming on a multi-page document with touchscreen gestures, Okular also
scrolls through the document rather than staying in place.


STEPS TO REPRODUCE
1. Use a device with a Wacom touchscreen (I have a Lenovo Yoga c940)
2. Open a document with multiple pages in Okular.
3. Try to zoom using two fingers on the touchscreen.

OBSERVED RESULT
Other pages on the document zoom by. Zooming out increases the page number,
while zooming in increases.

EXPECTED RESULT
The document stays on the same page, as it does when zooming with ctrl + / ctrl
-

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux x86_64, with all packages up-to-date
(available in About System)
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
ADDITIONAL INFORMATION

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

[systemsettings] [Bug 449176] New: Generic error message if background service fails to start

[Leon De Andrade]

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

Bug ID: 449176
   Summary: Generic error message if background service fails to
start
   Product: systemsettings
   Version: 5.23.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_kded
  Assignee: molken...@kde.org
  Reporter: leondeandr...@hotmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
When a background service failed there is no hint for the user in general. If
the user goes into systemsettings and try to run the failed service a generic
message pops up "Failed to start service". 
There is no hint what went wrong exactly or how to get more infos.


STEPS TO REPRODUCE
1. Have a failed service
2. Observe after a restart of the system that is not started automatically in
the system settings (and there is no hint for the user other than there)
3. Start the previously failed service

OBSERVED RESULT

Generic error message

EXPECTED RESULT

First of all after a restart a system message that my service failed. These
system service might or might not be important. And users usually don't monitor
the systemsettings background services page to see that not service failed. 

If a service failed then I would like to have a non generic error message. Or
at least some hint on how to find more interesting infos why the system service
actually failed. 

ADDITIONAL INFOS 

In my case this happended with kcm-wacomtablet . When I went to the wacom kcm
it told me the "wacom service was not running" and I should enable it in the
kcm background service. In this tab I observed that wacom service was in deed
not running even though it should start automatically after a boot. 
I then tried to manually run it by pressing the "run button". Then the error
message "Failed to start service" popped up. I had no idea why it failed and
also no idea where to get more information. I didn't even know what the "Wacom
tablet control daemon" is. Maybe a systemd service? No idea. No further
information. 

After some system updates and in particular a kernel update and a reboot it
magically worked. So I can't reproduce the error right now anymore and attach a
screenshot. 

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

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

[plasmashell] [Bug 443923] New: plasma crashes playing Minecraft.

[Rafael Jurado Leon]

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

Bug ID: 443923
   Summary: plasma crashes playing Minecraft.
   Product: plasmashell
   Version: 5.23.0
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: rajule...@hotmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.23.0)

Qt Version: 5.15.3
Frameworks Version: 5.87.0
Operating System: Linux 5.11.0-37-generic x86_64
Windowing System: X11
Distribution: KDE neon User - Plasma 25th Anniversary Edition
DrKonqi: 5.23.0 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed: I was playing
minecraft.sometimes crashes.may be old computer core 2 duo or low ram 4gb.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[New LWP 1189]
[New LWP 1266]
[New LWP 1267]
[New LWP 1268]
[New LWP 1269]
[New LWP 1312]
[New LWP 1313]
[New LWP 1315]
[New LWP 1378]
[New LWP 5084]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7fa5e7d27aff in __GI___poll (fds=0x7ffdd4a30a78, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
[Current thread is 1 (Thread 0x7fa5e3e7c9c0 (LWP 1138))]

Thread 11 (Thread 0x7fa5a4d33700 (LWP 5084)):
#0  __GI___libc_read (nbytes=10, buf=0x7fa5a4d32a1e, fd=27) at
../sysdeps/unix/sysv/linux/read.c:26
#1  __GI___libc_read (fd=27, buf=0x7fa5a4d32a1e, nbytes=10) at
../sysdeps/unix/sysv/linux/read.c:24
#2  0x7fa5a6e95975 in pa_read () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#3  0x7fa5a6f19416 in pa_mainloop_prepare () from
/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7fa5a6f19eb4 in pa_mainloop_iterate () from
/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7fa5a6f19f70 in pa_mainloop_run () from
/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7fa5a6f2811d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7fa5a6ec472c in ?? () from
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
#8  0x7fa5e7005609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7fa5e7d34293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 10 (Thread 0x7fa5a642e700 (LWP 1378)):
#0  __GI___poll (fds=0x7fa598006120, nfds=1, timeout=3216553) at
../sysdeps/unix/sysv/linux/poll.c:27
#1  0x7fa5e65d336e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa5e65d34a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa5e82f75eb in QEventDispatcherGlib::processEvents
(this=0x7fa598000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fa5e829b87b in QEventLoop::exec (this=this@entry=0x7fa5a642dba0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#5  0x7fa5e80b5292 in QThread::exec (this=) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#6  0x7fa5a650e07c in KCupsConnection::run() () from
/lib/x86_64-linux-gnu/libkcupslib.so
#7  0x7fa5e80b642c in QThreadPrivate::start (arg=0x55d9af2f38d0) at
thread/qthread_unix.cpp:329
#8  0x7fa5e7005609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7fa5e7d34293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7fa5c770b700 (LWP 1315)):
#0  0x7fa5e700dc5b in __GI___pthread_getspecific (key=4) at
pthread_getspecific.c:31
#1  0x7fa5e65fd044 in g_thread_self () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa5e65d23e0 in g_main_context_acquire () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa5e65d3225 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fa5e65d34a3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7fa5e82f75eb in QEventDispatcherGlib::processEvents
(this=0x7fa5a800ad70, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#6  0x7fa5e829b87b in QEventLoop::exec (this=this@entry=0x7fa5c770aba0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:141
#7  0x7fa5e80b5292 in QThread::exec (this=this@entry=0x55d9ae763c90) at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#8  0x7fa5e9c603ba in QQuickPixmapReader::run (this=0x55d9ae763c90) at
util/qquickpixmapcache.cpp:1024
#9  0x7fa5e80b642c in QThreadPrivate::start (arg=0x55d9ae763c90) at
thread/qthread_unix.cpp:329
#10 0x7fa5e7005609 in start_thread (arg=) at
pthread_create.c:477
#11 0x7fa5e7d34293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7fa5c7fff700 (LWP 1313)):
#0  __GI___libc_read (nbytes=16, buf=0x7fa5c7ffe9d0, fd=18) at
../sysdeps/unix/sysv/linux/read.c:26
#1  

[Bluedevil] [Bug 420100] Can't send file over bluetooth

[Leon]

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

Leon  changed:

   What|Removed |Added

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

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

[Bluedevil] [Bug 420100] Can't send file over bluetooth

[Leon]

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

--- Comment #3 from Leon  ---
I checked and obexd was installed. Re-tested using share and send files options
and it seems to be working. The error no loger appears. will mark as fixed

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

[kde] [Bug 431396] Render Issues in Control bar

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #7 from Leon De Andrade  ---
The issue is not fixed for me. I'm on 5.22.1 and Frameworks 5.83.0

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

[krusader] [Bug 437343] Last Modified Timestamp becomes current date and time during copy

[Leon]

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

Leon  changed:

   What|Removed |Added

Summary|Last Modified Timestamp |Last Modified Timestamp
   |becaomes current date and   |becomes current date and
   |time during copy|time during copy

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

[krusader] [Bug 437343] New: Last Modified Timestamp becaomes current date and time during copy

[Leon]

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

Bug ID: 437343
   Summary: Last Modified Timestamp becaomes current date and time
during copy
   Product: krusader
   Version: 2.7.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: synchronize
  Assignee: krusader-bugs-n...@kde.org
  Reporter: supp...@bb-services.co.za
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

SUMMARY
When copying a file over to a ftp or sftp site, the modification time becomes
the current date and time


STEPS TO REPRODUCE
1. Modify a file
2. Copy file over FTP or SFTP
3. 

OBSERVED RESULT
The last modification timestamp becomes the current date and time

EXPECTED RESULT
The last modified timestamp should remain the same for a copy procedure

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 33
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Copying from an  FTP/SFTP location to the local directories produces the same
effect. There is no setting clearly visible that seems to be able to change
this behaviour.

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

[kwin] [Bug 431396] Render Issues in Control bar

[Leon De Andrade]

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

--- Comment #4 from Leon De Andrade  ---
Created attachment 138185
  --> https://bugs.kde.org/attachment.cgi?id=138185=edit
Same Issue in Akira (GTK, Vala)

I found another application with this issue. It's like Planner as well a Vala
GTK Application.

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

[dolphin] [Bug 435539] New: Doplhin crashes while creating a new folder on FTP drive

[Leon]

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

Bug ID: 435539
   Summary: Doplhin crashes while creating a new folder on FTP
drive
   Product: dolphin
   Version: 20.12.2
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: supp...@bb-services.co.za
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (20.12.2)

Qt Version: 5.15.2
Frameworks Version: 5.79.0
Operating System: Linux 5.11.7-200.fc33.x86_64 x86_64
Windowing system: X11
Distribution: Fedora 33 (KDE Plasma)

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

1. Accessed and FTP location
2. Selected to create new folder (using F10, or using right-click, does not
matter)
3. Dolphin the creates a whole bunch of notification pop-ups
4. It then tells me the folder already exists (which it doesn't)
5. Repeating the processed crashes dolphin

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  0x7f2e67a67189 in QLineEdit::text() const () from
/lib64/libQt5Widgets.so.5
#5  0x7f2e68b56c48 in
QtPrivate::QFunctorSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone .lto_priv.0] ()
from /lib64/libKF5KIOFileWidgets.so.5
#6  0x7f2e66dfa386 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#7  0x7f2e67f1e1c0 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib64/libKF5CoreAddons.so.5
#8  0x7f2e67f22e8b in KJob::finishJob(bool) () from
/lib64/libKF5CoreAddons.so.5
#9  0x7f2e66dfa386 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x7f2e686ba5ed in KIO::SlaveInterface::dispatch(int, QByteArray const&)
() from /lib64/libKF5KIOCore.so.5
#11 0x7f2e686b305d in KIO::SlaveInterface::dispatch() () from
/lib64/libKF5KIOCore.so.5
#12 0x7f2e686bc7a2 in KIO::Slave::gotInput() () from
/lib64/libKF5KIOCore.so.5
#13 0x7f2e66dfa386 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#14 0x7f2e66df2d1e in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#15 0x7f2e67923ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#16 0x7f2e66dcabd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#17 0x7f2e66dcd8c7 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#18 0x7f2e66e17c27 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#19 0x7f2e64d72a9f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#20 0x7f2e64dc4a98 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#21 0x7f2e64d6fe73 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#22 0x7f2e66e176f3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#23 0x7f2e66dc957b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#24 0x7f2e66dd11b4 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#25 0x7f2e68f0ad5e in kdemain () from /lib64/libkdeinit5_dolphin.so
#26 0x7f2e68d101e2 in __libc_start_main () from /lib64/libc.so.6
#27 0x5640b98160ae in _start ()
[Inferior 1 (process 306898) detached]

The reporter indicates this bug may be a duplicate of or related to bug 433701.

Possible duplicates by query: bug 435427, bug 435346, bug 435209, bug 435159,
bug 434860.

Reported using DrKonqi

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

[systemsettings] [Bug 434086] System settings started to crashed after update

[Leon]

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

Leon  changed:

   What|Removed |Added

 CC||lnsilc...@gmail.com

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

[kdenlive] [Bug 413470] kdenlive crashes when editing a text clip

[Leon]

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

Leon  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #7 from Leon  ---
Could not replicate the error with latest updates. Fixed

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

[systemsettings] [Bug 413134] Night color conflicts with color correction

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

 CC||leondeandr...@hotmail.com

--- Comment #15 from Leon De Andrade  ---
Can confirm this as well. Just opening Compositor sometimes disabled it and
just opening gamma always disabled it.
Even if these conflict (and it's therefore cantfix), it should happen when you
change something and not just by opening the settings page.

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

[kwin] [Bug 431396] Render Issues in Control bar

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

Version|5.20.5  |5.21.0

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

[kwin] [Bug 431396] Render Issues in Control bar

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #3 from Leon De Andrade  ---
Hi, 
sorry for the late answer. Unfortunately installing these packages didn't
resolve the issue. 
Furthermore, I also found out that the issue is X11 only. I don't have that
problem on wayland.

Any other ideas?

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

[kdenlive] [Bug 413470] kdenlive crashes when editing a text clip

[Leon]

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

--- Comment #5 from Leon  ---
I tested from my side and could not re-produce a crash anymore. If another can
confirm and happy it could be marked as fixed.

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

[krusader] [Bug 431731] New: Krusader crashes with FTP

[Leon]

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

Bug ID: 431731
   Summary: Krusader crashes with FTP
   Product: krusader
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: krusader-bugs-n...@kde.org
  Reporter: supp...@bb-services.co.za
CC: krusader-bugs-n...@kde.org
  Target Milestone: ---

Application: krusader (2.7.2 "Peace of Mind")

Qt Version: 5.15.2
Frameworks Version: 5.78.0
Operating System: Linux 5.10.7-200.fc33.x86_64 x86_64
Windowing system: X11
Distribution: Fedora 33 (KDE Plasma)

-- Information about the crash:
- What I was doing when the application crashed:
1. Connected to an FTP drive
2. Transferring files
3. Continues for a while until it crashes with internal server error

The crash can be reproduced every time.

-- Backtrace:
Application: Krusader (krusader), signal: Segmentation fault

[KCrash Handler]
#4  0x7f7755d43c2f in QUrl::QUrl(QUrl const&) () from
/lib64/libQt5Core.so.5
#5  0x7f775726fce0 in KIO::CopyJobPrivate::skip(QUrl const&, bool) () from
/lib64/libKF5KIOCore.so.5
#6  0x7f7757273b42 in
KIO::CopyJobPrivate::processFileRenameDialogResult(QList::iterator
const&, KIO::RenameDialog_Result, QUrl const&, QDateTime const&) () from
/lib64/libKF5KIOCore.so.5
#7  0x7f775727b0e9 in
QtPrivate::QFunctorSlotObject,
void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) [clone
.lto_priv.0] () from /lib64/libKF5KIOCore.so.5
#8  0x7f7755dfe386 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#9  0x7f775724f5e1 in
KIO::AskUserActionInterface::askUserSkipResult(KIO::RenameDialog_Result, KJob*)
() from /lib64/libKF5KIOCore.so.5
#10 0x7f7755dfe386 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#11 0x7f7756a877b2 in QDialog::finished(int) () from
/lib64/libQt5Widgets.so.5
#12 0x7f7755dfe386 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#13 0x7f7756978316 in QAbstractButton::clicked(bool) () from
/lib64/libQt5Widgets.so.5
#14 0x7f7756978cde in QAbstractButtonPrivate::emitClicked() () from
/lib64/libQt5Widgets.so.5
#15 0x7f775697a673 in QAbstractButtonPrivate::click() () from
/lib64/libQt5Widgets.so.5
#16 0x7f775697a855 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
from /lib64/libQt5Widgets.so.5
#17 0x7f77568c9b1e in QWidget::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#18 0x7f7756888ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#19 0x7f775688feeb in QApplication::notify(QObject*, QEvent*) () from
/lib64/libQt5Widgets.so.5
#20 0x7f7755dcebd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#21 0x7f775688eefa in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
from /lib64/libQt5Widgets.so.5
#22 0x7f77568e2375 in QWidgetWindow::handleMouseEvent(QMouseEvent*) () from
/lib64/libQt5Widgets.so.5
#23 0x7f77568e56be in QWidgetWindow::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#24 0x7f7756888ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#25 0x7f7755dcebd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#26 0x7f775620a143 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /lib64/libQt5Gui.so.5
#27 0x7f77561eb8cc in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib64/libQt5Gui.so.5
#28 0x7f774468b47e in xcbSourceDispatch(_GSource*, int (*)(void*), void*)
() from /lib64/libQt5XcbQpa.so.5
#29 0x7f775459096f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#30 0x7f77545e2758 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#31 0x7f775458dd43 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#32 0x7f7755e1b6f3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#33 0x7f7755dcd57b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#34 0x7f7755dd51b4 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#35 0x555ddc6d9297 in main ()
[Inferior 1 (process 9086) detached]

Possible duplicates by query: bug 411883, bug 383528, bug 367789, bug 361006,
bug 347300.

Reported using DrKonqi

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

[dolphin] [Bug 431722] New: Dolphin Crashes while using WebDAV

[Leon]

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

Bug ID: 431722
   Summary: Dolphin Crashes while using WebDAV
   Product: dolphin
   Version: 20.08.3
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: supp...@bb-services.co.za
CC: kfm-de...@kde.org
  Target Milestone: ---

Application: dolphin (20.08.3)

Qt Version: 5.15.2
Frameworks Version: 5.78.0
Operating System: Linux 5.10.7-200.fc33.x86_64 x86_64
Windowing system: X11
Distribution: Fedora 33 (KDE Plasma)

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

1. Created WebDav network connection
2. Accessed folder
Dolphin pops up errors and crashes

-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault

[KCrash Handler]
#4  0x7f92098b9182 in QLineEdit::text() const () from
/lib64/libQt5Widgets.so.5
#5  0x7f920a98ff92 in
QtPrivate::QFunctorSlotObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from
/lib64/libKF5KIOFileWidgets.so.5
#6  0x7f9208c4c386 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#7  0x7f9209d6f9d0 in KJob::result(KJob*, KJob::QPrivateSignal) () from
/lib64/libKF5CoreAddons.so.5
#8  0x7f9209d7461b in KJob::finishJob(bool) () from
/lib64/libKF5CoreAddons.so.5
#9  0x7f9208c4c386 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x7f920a508c7a in KIO::SlaveInterface::error(int, QString const&) ()
from /lib64/libKF5KIOCore.so.5
#11 0x7f920a508487 in KIO::SlaveInterface::dispatch(int, QByteArray const&)
() from /lib64/libKF5KIOCore.so.5
#12 0x7f920a50099d in KIO::SlaveInterface::dispatch() () from
/lib64/libKF5KIOCore.so.5
#13 0x7f920a509f52 in KIO::Slave::gotInput() () from
/lib64/libKF5KIOCore.so.5
#14 0x7f9208c4c386 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#15 0x7f9208c44d1e in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#16 0x7f9209775ec3 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#17 0x7f9208c1cbd8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#18 0x7f9208c1f8c7 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#19 0x7f9208c69c27 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#20 0x7f9206bc896f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#21 0x7f9206c1a758 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#22 0x7f9206bc5d43 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#23 0x7f9208c696f3 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#24 0x7f9208c1b57b in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#25 0x7f9208c231b4 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#26 0x7f920ad431d5 in kdemain () from /lib64/libkdeinit5_dolphin.so
#27 0x7f920ab4c1e2 in __libc_start_main () from /lib64/libc.so.6
#28 0x5595e49810ae in _start ()
[Inferior 1 (process 2018) detached]

Possible duplicates by query: bug 431519, bug 431303, bug 431277, bug 431077,
bug 430998.

Reported using DrKonqi

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

[kwin] [Bug 431396] Render Issues in Control bar

[Leon De Andrade]

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

--- Comment #1 from Leon De Andrade  ---
Created attachment 134712
  --> https://bugs.kde.org/attachment.cgi?id=134712=edit
Here is firefox with this issue (Note: I can't reproduce this, it's from
another user)

I just attached a second screenshot with the same issue (so it looks) in
Firefox. It's not a screenshot from me though, Firefox just works normal for
me. 

Also, neither me nor the user with the firefox issue (according to what he
said) uses some style configuration. Just the normal breeze theme.

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

[kwin] [Bug 431396] New: Render Issues in Control bar

[Leon De Andrade]

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

Bug ID: 431396
   Summary: Render Issues in Control bar
   Product: kwin
   Version: 5.20.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: leondeandr...@hotmail.com
  Target Milestone: ---

Created attachment 134710
  --> https://bugs.kde.org/attachment.cgi?id=134710=edit
Show controls button of Planner

SUMMARY

In some applications (which are not qt as far as I can tell) the title bar is
rendered incorrectly. The buttons look quite weird. 

Where does it happen? 
- https://github.com/alainm23/planner 

There was once a discussion in a kde telegram group, where other people
reported such issues with gtk applications like firefox. But I only have a
problem with planner. 

STEPS TO REPRODUCE
1. Open up an application, where this happens


OBSERVED RESULT

See Screenshot for example the close button, which has this white area below
it.  


EXPECTED RESULT

Just a normal looking titlebar


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 428219] Timeout not displayed correctly and not working correctly

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

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

--- Comment #3 from Leon De Andrade  ---
Was fixed by the mentioned merge request. Thanks!

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

[digikam] [Bug 429119] New: Convert RAW to DNG tool adds text to caption field

[Leon Loberman]

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

Bug ID: 429119
   Summary: Convert RAW to DNG tool adds text to caption field
   Product: digikam
   Version: 7.1.0
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: BatchQueueManager-RAWProcessing
  Assignee: digikam-bugs-n...@kde.org
  Reporter: l...@loberman.net
  Target Milestone: ---

SUMMARY
Whenever I use the BQM tool to convert RAW to DNG, it puts 'charset=Ascii' or
'charset=unicode' into the caption field if the RAW caption field is empty

STEPS TO REPRODUCE
1. Add a RAW (NEF) file with no caption to the BQM queue
2. Select Convert RAW to DNG tool
3. Run the queue
4. View the DNG file caption data

OBSERVED RESULT
'charset=Ascii' or 'charset=unicode' in the caption field

EXPECTED RESULT
blank caption field

SOFTWARE/OS VERSIONS
Windows: x
macOS: x
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 428219] Timeout not displayed correctly and not working correctly

[Leon De Andrade]

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

--- Comment #2 from Leon De Andrade  ---
Presumably fixed by
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/448. Will test
it as soon as it's released.

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

[krusader] [Bug 427570] Krusader crashes on unstable connections

[Leon]

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

Leon  changed:

   What|Removed |Added

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

--- Comment #4 from Leon  ---
Information provided

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

[plasmashell] [Bug 428219] New: Timeout not displayed correctly and not working correctly

[Leon De Andrade]

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

Bug ID: 428219
   Summary: Timeout not displayed correctly and not working
correctly
   Product: plasmashell
   Version: 5.20.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: k...@privat.broulik.de
  Reporter: leondeandr...@hotmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 132712
  --> https://bugs.kde.org/attachment.cgi?id=132712=edit
Timeout visual is just dashed

SUMMARY

When I get a notification the visual of the timeout looks weird (see
Screenshot) and it's also not working correctly. As soon as I hover over the
close button, the timeout timer resets. 

STEPS TO REPRODUCE
1. Send a notications
2. Optionally hover over the close button

OBSERVED RESULT

The timeout indicator is a very small dotted line, almost not visible and
doesn't progress very smoothly. 

Additionally, it will reset itself if you hover over the close icon. 


EXPECTED RESULT

The indicator looks like usual (a blue not dotted outline, which is good
visible). 

The timer won't reset if you hover over the close button.

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

[plasmashell] [Bug 427690] System Tray widget has no padding between icons

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

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

--- Comment #4 from Leon De Andrade  ---
Can reproduce, the spacing is odd with 24px but fine with 22px and 26px

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

[plasmashell] [Bug 427690] System Tray widget has no padding between icons

[Leon De Andrade]

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

--- Comment #3 from Leon De Andrade  ---
Created attachment 132426
  --> https://bugs.kde.org/attachment.cgi?id=132426=edit
No spacing 24px

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

[plasmashell] [Bug 427690] System Tray widget has no padding between icons

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

 CC||leondeandr...@hotmail.com

--- Comment #2 from Leon De Andrade  ---
Created attachment 132425
  --> https://bugs.kde.org/attachment.cgi?id=132425=edit
Normal Looking 22px

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

[krusader] [Bug 427570] Krusader crashes on unstable connections

[Leon]

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

--- Comment #2 from Leon  ---
It is not really very visible when it goes wrong. There would just be this
notification (sad face) that pops up to say something went wrong and I should
report it. Plasma continues as normal, and krusader does not crash or close. I
can still perform some tasks, except on any open editors or trying to reconnect
to any servers. that portion of krusader is not ok anymore after the poppup. If
it has any other adverse effects on the plasma shell, I have not come across it
yet. It does not look like it, but it could be affected in an area where I do
not access or feel it. But clearly plasma is not happy in some area. It could
be that whatever happens has an adverse effect on krusader, but maybe krusader
is just an unfortunate victim, and not the cause.

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

[plasmashell] [Bug 427570] New: Krusader crashes on unstable connections

[Leon]

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

Bug ID: 427570
   Summary: Krusader crashes on unstable connections
   Product: plasmashell
   Version: 5.18.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: supp...@bb-services.co.za
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.18.5)

Qt Version: 5.14.2
Frameworks Version: 5.73.0
Operating System: Linux 5.8.13-200.fc32.x86_64 x86_64
Windowing system: X11
Distribution: Fedora 32 (KDE Plasma)

-- Information about the crash:
- What I was doing when the application crashed:
Edditing files over ftp connections

- Unusual behavior I noticed:
When connections are unstable or internet connections drops, the application
will crash. it normally happens when you press save and the saving takes long.

The application does not recover even if you re-open the file. The app has to
be closed, and re-opened,  to refresh the FTP listing, and then normal
operations continues. I only see it do this when connection issues on the
routers occur. These connecions issues are normally brief, like a few seconds,
and then all else continues, but Krusader begins to experience anamolies.

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

Thread 27 (Thread 0x7fcb8b587700 (LWP 7771)):
#0  0x7fcc38da24cc in read () from /lib64/libc.so.6
#1  0x7fcbebd11335 in pa_read () from
/usr/lib64/pulseaudio/libpulsecommon-13.99.so
#2  0x7fcbebfd1566 in pa_mainloop_prepare () from /lib64/libpulse.so.0
#3  0x7fcbebfd2004 in pa_mainloop_iterate () from /lib64/libpulse.so.0
#4  0x7fcbebfd20c0 in pa_mainloop_run () from /lib64/libpulse.so.0
#5  0x7fcbebfe031d in thread () from /lib64/libpulse.so.0
#6  0x7fcbebd3f5cc in internal_thread_func () from
/usr/lib64/pulseaudio/libpulsecommon-13.99.so
#7  0x7fcc385ad432 in start_thread () from /lib64/libpthread.so.0
#8  0x7fcc38db1913 in clone () from /lib64/libc.so.6

Thread 26 (Thread 0x7fcb8bfff700 (LWP 7161)):
#0  0x7fcc385b3e92 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fcc39137dab in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt5Core.so.5
#2  0x7fcbe755bde8 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () from /lib64/libKF5ThreadWeaver.so.5
#3  0x7fcbe755fdcc in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#4  0x7fcbe755b066 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#5  0x7fcbe755fe29 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#6  0x7fcbe755b066 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#7  0x7fcbe755fe29 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#8  0x7fcbe755b066 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#9  0x7fcbe755fe29 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#10 0x7fcbe755b066 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#11 0x7fcbe755fe29 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#12 0x7fcbe755b066 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#13 0x7fcbe755fe29 in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) ()
from /lib64/libKF5ThreadWeaver.so.5
#14 0x7fcbe755b066 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from
/lib64/libKF5ThreadWeaver.so.5
#15 0x7fcbe755d778 in ThreadWeaver::Thread::run() () from
/lib64/libKF5ThreadWeaver.so.5
#16 0x7fcc39132690 in QThreadPrivate::start(void*) () from
/lib64/libQt5Core.so.5
#17 0x7fcc385ad432 in start_thread () from /lib64/libpthread.so.0
#18 0x7fcc38db1913 in clone () from /lib64/libc.so.6

Thread 25 (Thread 0x7fcba4b2b700 (LWP 7160)):
#0  0x7fcc385b3e92 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7fcc39137dab in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib64/libQt5Core.so.5
#2  0x7fcbe755bde8 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () 

[dolphin] [Bug 427194] Mixed monochrome and preview folders in details mode

[Leon De Andrade]

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

--- Comment #1 from Leon De Andrade  ---
Btw. this is happens for all folders with images in it afaik

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

[dolphin] [Bug 427194] New: Mixed monochrome and preview folders in details mode

[Leon De Andrade]

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

Bug ID: 427194
   Summary: Mixed monochrome and preview folders in details mode
   Product: dolphin
   Version: 20.08.1
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: view-engine: details mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: leondeandr...@hotmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 132038
  --> https://bugs.kde.org/attachment.cgi?id=132038=edit
Colorful and monochrome folder icons mixed

SUMMARY

In details mode in dolphin, icon usually are monochrome if the icon size is
small enough.
I experienced though that some turn into these blue preview folders as soon as
an image is in the folder.

STEPS TO REPRODUCE
1. Open dolphin & activate details mode
2. Add some folder without a preview and some with (e.g. have images in it)  
3. Make the icons smaller, so they become monochrome eventually

OBSERVED RESULT

The preview folders won't be monochrome

EXPECTED RESULT

All folder become monochrome. Another option would be that none of the folder
become monochrome, but I find the preview folder hardly usefull when the icon
size is too small, so I would prefer Option 1.

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

[kdevelop] [Bug 427167] New: Can NOT config custom-compiler

[Leon Lee Ann]

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

Bug ID: 427167
   Summary: Can NOT config custom-compiler
   Product: kdevelop
   Version: 5.5.0
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: leon.lee@gmail.com
  Target Milestone: ---

SUMMARY
In the configuration of KDevelop, the feature about adding customized
manual-compilers do nothing.

STEPS TO REPRODUCE
1. Open the dialog box of "Configure -- KDevelop";
2. Select the "C/C++ Compilers" entry in the left list;
3. Add a "Manual Compiler", e.g GCC;
4.Save and Apply.

OBSERVED RESULT
Re-open the config dialog window, the compiler entry that we added just now
disappeared!!!

EXPECTED RESULT
The compiler entry should be saved .

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Kubuntu 20.04.1
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION

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

[kinfocenter] [Bug 427078] No energy information on a desktop pc

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

Summary|No energy information on|No energy information on a
   |Arch Linux  |desktop pc

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

[kinfocenter] [Bug 427078] New: No energy information on Arch Linux

[Leon De Andrade]

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

Bug ID: 427078
   Summary: No energy information on Arch Linux
   Product: kinfocenter
   Version: 5.19.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Energy Information
  Assignee: k...@privat.broulik.de
  Reporter: leondeandr...@hotmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 131989
  --> https://bugs.kde.org/attachment.cgi?id=131989=edit
Empty energy information, no warnings

SUMMARY

There is no energy information on my desktop pc and no warning, what could be
wrong.

STEPS TO REPRODUCE
1. Open Enegry Information on a desktop pc


OBSERVED RESULT

Page is just empty

EXPECTED RESULT

To see energy information or at least have some kind of warning (for example:
Only supported for battery devices)

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

[systemsettings] [Bug 426821] New: Global Shortcut conflicts with another user's conf

[Leon Lee Ann]

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

Bug ID: 426821
   Summary: Global Shortcut conflicts with another user's conf
   Product: systemsettings
   Version: 5.18.5
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_khotkeys
  Assignee: k...@michael-jansen.biz
  Reporter: leon.lee@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
Global Shortcut conflicts with another user's conf.

STEPS TO REPRODUCE
1. Install a fresh Kubuntu 20.04.1, and during installation process, create the
default user(user0) by means of the installer of the Kubuntu;
2. Install all upgrades in Discover Software Center(up to 2020/09/21);
3. Create a normal user(user1) by means of "adduser" command in cli;
4.Login with user0, setup a global shortcut "Meta+K" for startting Kate;
5.Login with user1, setup a global shortcut(whatever) for startting Kate;
6.Test user1's shortcut.

OBSERVED RESULT
The shortcut for user1 will not work!
If we remove the shortcut entry of startting Kate for user0, then the ones for
user1 works again!

EXPECTED RESULT
Any shortcuts should NOT conflict with ones of another users.

SOFTWARE/OS VERSIONS
Linux: Kubuntu 20.04.1
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

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

[KAccounts] [Bug 425807] New: Setting up Nextcloud account won't work

[Leon De Andrade]

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

Bug ID: 425807
   Summary: Setting up Nextcloud account won't work
   Product: KAccounts
   Version: 20.08
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ad...@leinir.dk
  Reporter: leondeandr...@hotmail.com
  Target Milestone: ---

SUMMARY

When setting up my server address a popup opens with "This site cannot be
reached"

STEPS TO REPRODUCE
1. I add a new nextcloud account via system settings
2. I type in my server address https://myServer:port/nextcloud
3. A popup opens with this site
(https://vmd42712.contaboserver.net:8443/nextcloud//index.php/login/flow)
cannot be reached

OBSERVED RESULT

A popup with the site cannot be reached. It seems to me like the url is not
correct. After "nextcloud" a double slash is added ... this can't be correct?

EXPECTED RESULT

The site can be reached and I can login into nextcloud

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

[okular] [Bug 424963] Search doesn't recieve focus

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

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

--- Comment #10 from Leon De Andrade  ---
Always forget to set the status

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

[okular] [Bug 424963] Search doesn't recieve focus

[Leon De Andrade]

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

--- Comment #9 from Leon De Andrade  ---
I do use plasma 5.194 and I only use breeze stuff at the moment.

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

[okular] [Bug 424963] Search doesn't recieve focus

[Leon De Andrade]

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

--- Comment #7 from Leon De Andrade  ---
hmm can there still be something done? Some further information I can provide?

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

[okular] [Bug 424963] Search doesn't recieve focus

[Leon De Andrade]

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

--- Comment #4 from Leon De Andrade  ---
Hi, 
sorry for the long wait. I forgot about it.

I uploaded a video, but it's kinda hard to see I guess, because you don't see ,
where and what I click. 

So here is a short desciption of what I did: 
1. Open up the search bar with ctrl + f
2. Type in "Hello"
3. Search for it by pressing enter
4. Click somewhere on the document, so the search bar loses focus (notice the
blue line disappearing)
5. Go to the search bar and select the text. This is the important step to
actually reproduce it I think. 
- Mark by dragging the mouse not double click
- Don't select the search bar before you select the text. Just go with your
mouse on the search bar without clicking and select directly by dragging. 
6. Press the delete key and observe that it scroll on the page instead of
deleting the text 

Compare it with the behaviour of double clicking the text for selection. Doing
it like this, the search bar actually gains focus. With my way, the search bar
doesn't get focus. 

I hope this was clear enough, it's not so easy to describe

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

[okular] [Bug 424963] Search doesn't recieve focus

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

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

--- Comment #5 from Leon De Andrade  ---
Information provided

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

[okular] [Bug 424963] Search doesn't recieve focus

[Leon De Andrade]

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

--- Comment #3 from Leon De Andrade  ---
Created attachment 130996
  --> https://bugs.kde.org/attachment.cgi?id=130996=edit
video of behaviour

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

[frameworks-baloo] [Bug 422008] Baloo is stuck in an indexing loop

[Leon De Andrade]

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

--- Comment #12 from Leon De Andrade  ---
I looked into journalctl and there were a couple of informations repeating
every few seconds.

Invalid encoding. Ignoring "/home/leon/Downloads/Telegram
Desktop/BitVis_0.0.8/zebra.bin":

After deleting this file, baloo is still stuck, but the cpu usage had dropped
massively! So it seems like the "Ignoring" doesn't work so well.

baloo_file_extractor[3542]: org.kde.baloo.engine: PostingDB::put MDB_BAD_TXN:
Transaction must abort, has a child, or is invalid
baloo_file_extractor[3542]: org.kde.baloo.engine: PositionDB::put MDB_BAD_TXN:
Transaction must abort, has a child, or is invalid

Then these two messages appear like 20 times and repeat every few seconds. I
guess these are the culprit for the loop. Does this help you?

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

[okular] [Bug 424963] New: Search doesn't recieve focus

[Leon De Andrade]

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

Bug ID: 424963
   Summary: Search doesn't recieve focus
   Product: okular
   Version: 1.10.3
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: leondeandr...@hotmail.com
  Target Milestone: ---

SUMMARY

Selecting text in the search of okular doesn't give the search bar focus if you
select by holding the left mouse button (and not double click)


STEPS TO REPRODUCE
1. Open the search
2. Type something in it
3. Click somewhere else, so the search bar loses focus
4. Try to remove the text in the search bar (It's important that you don't do
double click, but actually select the text by holding the left mouse button)

OBSERVED RESULT

I jump a few lines back in the document


EXPECTED RESULT

The search bar would gain focus and the search text would be deleted like it
does when you double click the text to select it.


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[frameworks-baloo] [Bug 422008] Baloo is stuck in an indexing loop

[Leon De Andrade]

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

--- Comment #11 from Leon De Andrade  ---
Still there! Everytime I reboot my pc baloo starts and won't stop ... is there
anything I can more do to help fixing this bug?

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

[kmymoney] [Bug 423885] New: Cannot delete a loan account when created (No transactions)

[Leon Solis Jr]

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

Bug ID: 423885
   Summary: Cannot delete a loan account when created (No
transactions)
   Product: kmymoney
   Version: 4.6.4
  Platform: Windows CE
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: leonsbests...@gmail.com
  Target Milestone: ---

SUMMARY
Cannot delete a loan account when created (No transactions)

STEPS TO REPRODUCE
1. create a Liability loan account
2. Right click on account
3. look at drop down list

OBSERVED RESULT No "delete account" available (grey drop down item)


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 423318] Application launcher appears in wrong corner

[Leon Teichroeb]

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

--- Comment #4 from Leon Teichroeb  ---
My display setup:

Global scale:1.0
Resolution:  3440x1440 @ 75 Hz
Forced font DPI: 110

The second monitor runs at a standard 1920x1080 @ 60 Hz

The issue does not appear with the high-res monitor alone.

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

[plasmashell] [Bug 423318] Application launcher appears in wrong corner

[Leon Teichroeb]

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

--- Comment #2 from Leon Teichroeb  ---
Further testing seems to confirm that the dual monitor setup is triggering the
bug.

The dual monitor setup in combination with any driver (nvidia 440.82/ 435.21,
noveau) is still suffering from the issue.

When unplugging the second (upper, smaller) monitor and rebooting the system,
the menu returns to normal.

Additionally this bug does not just affect the application launcher as can be
seen in the additional screenshots.
This changes the scope, and I am not sure which component the bug directly
applies to.

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

[plasmashell] [Bug 423318] Application launcher appears in wrong corner

[Leon Teichroeb]

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

--- Comment #1 from Leon Teichroeb  ---
Created attachment 129578
  --> https://bugs.kde.org/attachment.cgi?id=129578=edit
Audio volume tray wrong placement.

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

[plasmashell] [Bug 423318] New: Application launcher appears in wrong corner

[Leon Teichroeb]

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

Bug ID: 423318
   Summary: Application launcher appears in wrong corner
   Product: plasmashell
   Version: 5.18.5
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: bigleo...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 129563
  --> https://bugs.kde.org/attachment.cgi?id=129563=edit
Desktop screenshot showing incorrect launcher position.

SUMMARY
After having recently reinstalled Manjaro, the application launcher has started
appearing in the wrong corner. This was never the case before.
This bug occurs reliably after a system restart, and ceases after restarting
plasmashell.
The panel is (to my knowledge) unmodified, except for having enabled auto-hide.
I am running a vertical dual monitor setup.

Another thing to note: The system suffers from instability with the nvidia
driver, so the compositor tab in system settings shows that the fallback to
non-OpenGL compositing is activated.


STEPS TO REPRODUCE
Appears initially upon every reboot.
Can be fixed by restarting plasmashell.

OBSERVED RESULT
The application launcher always appears in the upper left corner after
rebooting the system.

EXPECTED RESULT
The application launcher should appear in the lower left corner, as it does
after restarting plasmashell.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:   5.6.16-1-MANJARO
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0
Nvidia drivers: linux56-nvidia-440xx / 440.82-18

ADDITIONAL INFORMATION
-Panel auto-hiding is enabled
-Dual monitor setup

This is my first bug report. Constructive criticism is appreciated :)

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

[plasmashell] [Bug 421038] Vertically misaligned battery icon in panel

[Leon De Andrade]

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

--- Comment #6 from Leon De Andrade  ---
Can confirm, it's fixed.

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

[frameworks-baloo] [Bug 422008] Baloo is stuck in an indexing loop

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

   Platform|Appimage|Archlinux Packages
 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #10 from Leon De Andrade  ---
No, it's not sorry. I must have clicked the wrong one, I'm on arch.

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

[kdenlive] [Bug 423083] New: Inadequate error instructions

[Leon Arundell]

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

Bug ID: 423083
   Summary: Inadequate error instructions
   Product: kdenlive
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Documentation
  Assignee: ttg...@gmail.com
  Reporter: leon.arund...@yahoo.com
  Target Milestone: ---

SUMMARY

When I try to import a project, I get a message to install OpenTimelineIO
(which I have done) and to "check the scripts are installed in a directory
listed in PATH environment variable."

It does not explain how to identify or locate a "script," how to install it in
a directory listed in PATH environment variable, or in which directory it may
be safely installed


STEPS TO REPRODUCE
1. From the menu, select "File > Import project"
2. Error message appears:
Could not find "otioconvert" script.
You need to install OpenTimelineIO,
through your package manager if available,
or by "pip3 install opentimelineio",
and check the scripts are installed in a directory listed in PATH environment
variable

3. Install OpenTimelineIO

4. Repeat above.

4. From the menu, select Settings > Configure kdenlive > MLT environment

OBSERVED RESULT

A list of potential PATH directories

EXPECTED RESULT



SOFTWARE/OS VERSIONS
Linux Ubuntu 20.04 LTS

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

[plasmashell] [Bug 422728] New: No data displayed after rewrite

[Leon De Andrade]

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

Bug ID: 422728
   Summary: No data displayed after rewrite
   Product: plasmashell
   Version: 5.19.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Monitor
  Assignee: notm...@gmail.com
  Reporter: leondeandr...@hotmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 129187
  --> https://bugs.kde.org/attachment.cgi?id=129187=edit
Two monitor widgets (different display styles)

SUMMARY

There is no cpu data or any other data (which you can select)in the monitor
widget since the 5.19 update.

STEPS TO REPRODUCE
1. Add a monitor widget 

OBSERVED RESULT

No data, just empty charts 

EXPECTED RESULT

data should be displayed. The system load viewer still works and shows the data
correctly


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.19
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[frameworks-baloo] [Bug 422008] Baloo is stuck in an indexing loop

[Leon De Andrade]

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

Leon De Andrade  changed:

   What|Removed |Added

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

--- Comment #8 from Leon De Andrade  ---
Additional infos provided

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

[lattedock] [Bug 422405] Selection Color in global menu in "Smart" mode unreadable

[Leon De Andrade]

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

--- Comment #4 from Leon De Andrade  ---
Ah okay nice, I didn't know that. That in fact solves the issue.

I still think it can be considered as a bug (with rather low priority after
your clarification) and maybe there is the possibilty to auto disable that
feature automatically for widgets that don't support it? Actually it would
probably be the best to not make it configurable at all, but just determine it
automatically (I suppose you can programmatically check if the widget supports
it?)

As a second possibilty (or even in addition to the previous) add a note similar
to the one "For best results install the kwin color script" to warn about this?

These are just suggestion though to improve the UX of latte.I feel like you got
offended by my last comment, it's hard to tell from text though, if that's the
case that is certainly not my intention.

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

[lattedock] [Bug 422405] Selection Color in global menu in "Smart" mode unreadable

[Leon De Andrade]

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

--- Comment #2 from Leon De Andrade  ---
Can support what?

I'm not sure if the problem is clear. The global menu works just fine with
latte in normal color mode, no problem at all. It just doesn't work in "smart"
mode ... I'm not exactly sure what should happen with global menu (ideally) in
"smart" mode, but when it's not possible due to technical limitations, I would
expect it to work normal at least? Or is there any reasoning why the selection
color can't be normal in that mode?

I would try it myself with AppMenu to see what you mean, but for some reason it
doesn't show up under my widgets after having installed it.

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

[lattedock] [Bug 422405] New: Selection Color in global menu in "Smart" mode unreadable

[Leon De Andrade]

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

Bug ID: 422405
   Summary: Selection Color in global menu in "Smart" mode
unreadable
   Product: lattedock
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: leondeandr...@hotmail.com
  Target Milestone: ---

Created attachment 129018
  --> https://bugs.kde.org/attachment.cgi?id=129018=edit
shows white selection color

SUMMARY
Selection color in global menu is unreadable if you're in smart mode. If I
click on a menu entry it's white instead of the normal blue (like the text
itself, which makes it unreadable)

STEPS TO REPRODUCE
1. Dark latte panel (haven't tested for other colors)
2. Global Menu
3. Smart color activated
4. click on a menu entry in global menu 

OBSERVED RESULT
The selection color is white as the text 

EXPECTED RESULT
It should be blue as in the other modes.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[lattedock] [Bug 421038] Vertically misaligned battery icon in panel

[Leon De Andrade]

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

--- Comment #3 from Leon De Andrade  ---
Created attachment 129017
  --> https://bugs.kde.org/attachment.cgi?id=129017=edit
Perfect with plasma panel

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

[lattedock] [Bug 421038] Vertically misaligned battery icon in panel

[Leon De Andrade]

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

--- Comment #2 from Leon De Andrade  ---
No I don't.

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

[frameworks-baloo] [Bug 422008] Baloo is stuck in an indexing loop

[Leon De Andrade]

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

--- Comment #6 from Leon De Andrade  ---
Created attachment 128762
  --> https://bugs.kde.org/attachment.cgi?id=128762=edit
crash, maybe relevant

Just now baloo crashed, I'm not sure though if it's related or any helpful.

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

[frameworks-baloo] [Bug 422008] Baloo is stuck in an indexing loop

[Leon De Andrade]

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

--- Comment #5 from Leon De Andrade  ---
15 mins later:

date && stat /home/leon/untitled/mainwindow.ui && balooshow
/home/leon/untitled/mainwindow.ui
Mo 25. Mai 09:23:37 CEST 2020
  File: /home/leon/untitled/mainwindow.ui
  Size: 536 Blocks: 8  IO Block: 4096   regular file
Device: 806h/2054d  Inode: 8522113 Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/leon)   Gid: (  985/   users)
Access: 2020-05-24 21:09:23.932741559 +0200
Modify: 2020-05-24 21:09:22.442695158 +0200
Change: 2020-05-24 21:09:22.452695469 +0200
 Birth: 2020-05-24 21:09:22.442695158 +0200
36602196627818502 2054 8522113 /home/leon/untitled/mainwindow.ui
Mtime: 1590347362 2020-05-24T21:09:22
Ctime: 1590347362 2020-05-24T21:09:22


df -T /home/
Filesystem Type 1K-blocks  Used Available Use% Mounted on
/dev/sda6  ext4 296389012 120828708 160434864  43% /home

df -T /home/leon/Downloads/
Filesystem Type 1K-blocks  Used Available Use% Mounted on
/dev/sda6  ext4 296389012 120828712 160434860  43% /home

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

[frameworks-baloo] [Bug 422008] Baloo is stuck in an indexing loop

[Leon De Andrade]

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

--- Comment #4 from Leon De Andrade  ---
So today it started again, after a restart. Maybe there is connection to
restarting my system, will investigate that further.

As yesterday it lists the most recent files 

/home/leon/untitled/mainwindow.ui:

date && stat /home/leon/untitled/mainwindow.ui && balooshow
/home/leon/untitled/mainwindow.ui

Mo 25. Mai 08:59:52 CEST 2020
  File: /home/leon/untitled/mainwindow.ui
  Size: 536 Blocks: 8  IO Block: 4096   regular file
Device: 806h/2054d  Inode: 8522113 Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/leon)   Gid: (  985/   users)
Access: 2020-05-24 21:09:23.932741559 +0200
Modify: 2020-05-24 21:09:22.442695158 +0200
Change: 2020-05-24 21:09:22.452695469 +0200
 Birth: 2020-05-24 21:09:22.442695158 +0200
36602196627818502 2054 8522113 /home/leon/untitled/mainwindow.ui
Mtime: 1590347362 2020-05-24T21:09:22
Ctime: 1590347362 2020-05-24T21:09:22

df -T /home/

Filesystem Type 1K-blocks  Used Available Use% Mounted on
/dev/sda6  ext4 296389012 120827480 160436092  43% /home

df -T /home/leon/Downloads/

Filesystem Type 1K-blocks  Used Available Use% Mounted on
/dev/sda6  ext4 296389012 120827540 160436032  43% /home




date && stat /home/leon/untitled/mainwindow.ui && balooshow
/home/leon/untitled/mainwindow.ui

Mo 25. Mai 09:01:25 CEST 2020
  File: /home/leon/untitled/mainwindow.ui
  Size: 536 Blocks: 8  IO Block: 4096   regular file
Device: 806h/2054d  Inode: 8522113 Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/leon)   Gid: (  985/   users)
Access: 2020-05-24 21:09:23.932741559 +0200
Modify: 2020-05-24 21:09:22.442695158 +0200
Change: 2020-05-24 21:09:22.452695469 +0200
 Birth: 2020-05-24 21:09:22.442695158 +0200
36602196627818502 2054 8522113 /home/leon/untitled/mainwindow.ui
Mtime: 1590347362 2020-05-24T21:09:22
Ctime: 1590347362 2020-05-24T21:09:22

df -T /home/
Filesystem Type 1K-blocks  Used Available Use% Mounted on
/dev/sda6  ext4 296389012 120827548 160436024  43% /home

df -T /home/leon/Downloads/

Filesystem Type 1K-blocks  Used Available Use% Mounted on
/dev/sda6  ext4 296389012 120827040 160436532  43% /home


date && stat /home/leon/untitled/mainwindow.ui && balooshow
/home/leon/untitled/mainwindow.ui

Mo 25. Mai 09:07:19 CEST 2020
  File: /home/leon/untitled/mainwindow.ui
  Size: 536 Blocks: 8  IO Block: 4096   regular file
Device: 806h/2054d  Inode: 8522113 Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/leon)   Gid: (  985/   users)
Access: 2020-05-24 21:09:23.932741559 +0200
Modify: 2020-05-24 21:09:22.442695158 +0200
Change: 2020-05-24 21:09:22.452695469 +0200
 Birth: 2020-05-24 21:09:22.442695158 +0200
36602196627818502 2054 8522113 /home/leon/untitled/mainwindow.ui
Mtime: 1590347362 2020-05-24T21:09:22
Ctime: 1590347362 2020-05-24T21:09:22

df -T /home/
Filesystem Type 1K-blocks  Used Available Use% Mounted on
/dev/sda6  ext4 296389012 120827828 160435744  43% /home

df -T /home/leon/Downloads/

Filesystem Type 1K-blocks  Used Available Use% Mounted on
/dev/sda6  ext4 296389012 120827832 160435740  43% /home

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

[frameworks-baloo] [Bug 422008] Baloo is stuck in an indexing loop

[Leon De Andrade]

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

--- Comment #3 from Leon De Andrade  ---
Okay I will, once I notice it again. 

Which reminds me that I probably should say that if I suspend baloo and try to
continue it later (not sure how much later) it won't.

If I just download something new, it will index normally and go back to Idle
(Powersave).

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

[frameworks-baloo] [Bug 422008] New: Baloo is stuck in an indexing loop

[Leon De Andrade]

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

Bug ID: 422008
   Summary: Baloo is stuck in an indexing loop
   Product: frameworks-baloo
   Version: 5.70.0
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: stefan.bru...@rwth-aachen.de
  Reporter: leondeandr...@hotmail.com
  Target Milestone: ---

Created attachment 128743
  --> https://bugs.kde.org/attachment.cgi?id=128743=edit
baloo stuck

SUMMARY

Baloo tries to index the same files (sucessfully) over and over again.
See the screenshots, about 20 files are indexed forever. 
The files seem to be my most recent ones.

STEPS TO REPRODUCE
I'm not sure, I have problems with baloo since ever on different machines. It's
the first time I actually checked what the problem is.

Please tell me if I can provide more debug information.

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

[lattedock] [Bug 421038] New: Vertically misaligned battery icon in panel

[Leon De Andrade]

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

Bug ID: 421038
   Summary: Vertically misaligned battery icon in panel
   Product: lattedock
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: leondeandr...@hotmail.com
  Target Milestone: ---

Created attachment 128159
  --> https://bugs.kde.org/attachment.cgi?id=128159=edit
Shows a top panel with the misaligned battery icon

SUMMARY

The battery icon is not aligned properly.


STEPS TO REPRODUCE
1. Add a panel (top / bottom)
2. Add the battery widget
3. Possibly add more widgets (like netword, audio) to see the difference

OBSERVED RESULT

The battery icon is vertically misaligned (it's sticking to the top, no matter
if you have a bottom or top panel).


EXPECTED RESULT

The battery icon should be aligned in the center.

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