[plasmashell] [Bug 445368] New: Crash during shutdown/log out/standby

2021-11-11 Thread Jan Schubert
https://bugs.kde.org/show_bug.cgi?id=445368

Bug ID: 445368
   Summary: Crash during shutdown/log out/standby
   Product: plasmashell
   Version: 5.23.2
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: janschub...@outlook.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.23.2)

Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.14-1-default x86_64
Windowing System: Wayland
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.2 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Every time I log into the system KDE presents me with this crash report. This
only happens under wayland. X11 works.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6  0x7f15e8c35800 in QScreen::name (this=this@entry=0x5624f31ab270) at
kernel/qscreen.cpp:195
#7  0x5624f24dfb73 in ShellCorona::load (this=) at
/usr/src/debug/plasma5-workspace-5.23.2-1.1.x86_64/shell/shellcorona.cpp:683
#8  0x7f15e87e7043 in QtPrivate::QSlotObjectBase::call (a=0x7ffdbcb8f400,
r=0x5624f33d8b30, this=0x5624f33e4010) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9  doActivate (sender=0x5624f3359e60, signal_index=4,
argv=0x7ffdbcb8f400) at kernel/qobject.cpp:3886
#10 0x7f15e87e050f in QMetaObject::activate (sender=,
m=m@entry=0x7f15eaa76560, local_signal_index=local_signal_index@entry=1,
argv=argv@entry=0x7ffdbcb8f400) at kernel/qobject.cpp:3946
#11 0x7f15eaa522f1 in KActivities::Consumer::serviceStatusChanged
(this=, _t1=) at
/usr/src/debug/kactivities5-5.87.0-1.1.x86_64/build/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_consumer.cpp:253
#12 0x7f15e87e7043 in QtPrivate::QSlotObjectBase::call (a=0x7ffdbcb8f540,
r=0x5624f3359e60, this=0x5624f3360350) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x5624f33597c0, signal_index=11,
argv=0x7ffdbcb8f540) at kernel/qobject.cpp:3886
#14 0x7f15e87e050f in QMetaObject::activate
(sender=sender@entry=0x5624f33597c0, m=m@entry=0x7f15eaa76620
,
local_signal_index=local_signal_index@entry=8, argv=argv@entry=0x7ffdbcb8f540)
at kernel/qobject.cpp:3946
#15 0x7f15eaa63312 in KActivities::ActivitiesCache::serviceStatusChanged
(_t1=KActivities::Consumer::Running, this=0x5624f33597c0) at
/usr/src/debug/kactivities5-5.87.0-1.1.x86_64/build/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_activitiescache_p.cpp:412
#16 KActivities::ActivitiesCache::setAllActivities (this=0x5624f33597c0,
_activities=...) at
/usr/src/debug/kactivities5-5.87.0-1.1.x86_64/src/lib/activitiescache_p.cpp:270
#17 0x7f15eaa56677 in
KActivities::ActivitiesCache::passInfoFromReply, void
(KActivities::ActivitiesCache::*)(QList const&)> (f=, watcher=0x5624f3385430, this=0x5624f33597c0) at
/usr/src/debug/kactivities5-5.87.0-1.1.x86_64/src/lib/activitiescache_p.cpp:180
#18 KActivities::ActivitiesCache::setAllActivitiesFromReply
(watcher=0x5624f3385430, this=0x5624f33597c0) at
/usr/src/debug/kactivities5-5.87.0-1.1.x86_64/src/lib/activitiescache_p.cpp:195
#19 KActivities::ActivitiesCache::qt_static_metacall (_o=0x5624f33597c0,
_c=, _id=, _a=) at
/usr/src/debug/kactivities5-5.87.0-1.1.x86_64/build/src/lib/KF5Activities_autogen/EWIEGA46WW/moc_activitiescache_p.cpp:201
#20 0x7f15e87e7078 in doActivate (sender=0x5624f3385430,
signal_index=3, argv=0x7ffdbcb8f7b0) at kernel/qobject.cpp:3898
#21 0x7f15e87e050f in QMetaObject::activate (sender=,
m=m@entry=0x7f15e92525e0 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdbcb8f7b0)
at kernel/qobject.cpp:3946
#22 0x7f15e9232fff in QDBusPendingCallWatcher::finished (this=, _t1=) at .moc/moc_qdbuspendingcall.cpp:158
#23 0x7f15e87dcfee in QObject::event (this=0x5624f3385430,
e=0x5624f31e1180) at kernel/qobject.cpp:1314
#24 0x7f15e9549a7f in QApplicationPrivate::notify_helper (this=, receiver=0x5624f3385430, e=0x5624f31e1180) at
kernel/qapplication.cpp:3632
#25 0x7f15e87b09fa in QCoreApplication::notifyInternal2
(receiver=0x5624f3385430, event=0x5624f31e1180) at
kernel/qcoreapplication.cpp:1064
#26 0x7f15e87b3a47 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x5624f3181110) at
kernel/qcoreapplication.cpp:1821
#27 0x7f15e8808853 in postEventSourceDispatch (s=s@entry=0x5624f31c5c00) at
kernel/qeventdispatcher_glib.cpp:277
#28 0x7f15e6b15d4f in g_main_dispatch (context=0x5624f31ce730) at
../glib/gmain.c:3381
#29 g_main_context_dispatch (context=0x5624f31ce730) at ../glib/gmain.c:4099
#30 0x7f15e6b160d8 in g_main_context_iterate

[krita] [Bug 445367] Adding a bundle with resource duplicated in disabled bundle disables the resource

2021-11-11 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=445367

--- Comment #1 from Dmitry Kazakov  ---
The user can neither import this resource manually using "Import Resource". The
resource will be disabled.

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

[systemsettings] [Bug 442289] System Settings Crashes When Applying Changes in Screen Edges (Settings are Still Applied)

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=442289

omarsa...@gmail.com changed:

   What|Removed |Added

 CC||omarsa...@gmail.com

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

[systemsettings] [Bug 442289] System Settings Crashes When Applying Changes in Screen Edges (Settings are Still Applied)

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=442289

--- Comment #3 from omarsa...@gmail.com ---
Created attachment 143473
  --> https://bugs.kde.org/attachment.cgi?id=143473=edit
New crash information added by DrKonqi

systemsettings5 (5.22.5) using Qt 5.15.2

- What I was doing when the application crashed:
Adjusting screen edges, crashes instantly after hitting apply. Settings still
get applied. On Wayland.

-- Backtrace (Reduced):
#4  0x7ff2d915c6a4 in
QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*,
unsigned int, QString const&, unsigned int) () from
/lib64/libQt5WaylandClient.so.5
#5  0x7ff2d91491b9 in
QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&,
unsigned int) () from /lib64/libQt5WaylandClient.so.5
#6  0x7ff2d9165af3 in QtWayland::wl_registry::handle_global(void*,
wl_registry*, unsigned int, char const*, unsigned int) () from
/lib64/libQt5WaylandClient.so.5
#7  0x7ff2d69fbc04 in ffi_call_unix64 () from /lib64/libffi.so.6
#8  0x7ff2d69fb108 in ffi_call () from /lib64/libffi.so.6

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

[krita] [Bug 445367] New: Adding a bundle with resource duplicated in disabled bundle disables the resource

2021-11-11 Thread Dmitry Kazakov
https://bugs.kde.org/show_bug.cgi?id=445367

Bug ID: 445367
   Summary: Adding a bundle with resource duplicated in disabled
bundle disables the resource
   Product: krita
   Version: git master (please specify the git hash!)
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Resource Management
  Assignee: krita-bugs-n...@kde.org
  Reporter: dimul...@gmail.com
  Target Milestone: ---

SUMMARY

When the user adds a bundle with a resource that is present in some other
bundle, this resource becomes disabled. It doesn't even matter if the existing
bundle it disabled or not.

STEPS TO REPRODUCE

1. Export "y) Texture Reptile" preset into a separate bundle and name it
"reptile.bundle"
2. Import "reptile.bundle" into Krita
3. Disable "Krita 4 Resources" bundle

OBSERVED RESULT

"y) Texture Reptile" preset is not available in any GUI, even though it is
present in a non-disabled bundle

EXPECTED RESULT

"y) Texture Reptile" is available in the GUI as long as it is present in at
least one non-disable bundle

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

[digikam] [Bug 445345] When creating a new tag with a comma, the tag is truncated

2021-11-11 Thread Jan van Bekkum
https://bugs.kde.org/show_bug.cgi?id=445345

--- Comment #4 from Jan van Bekkum  ---
Thanks, clear!

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

[kwin] [Bug 442947] Some text in the Overview effect is blurry

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=442947

--- Comment #2 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin/-/merge_requests/1650

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

[skrooge] [Bug 445263] Version 2.26, import using Woob aborted,error

2021-11-11 Thread forum
https://bugs.kde.org/show_bug.cgi?id=445263

--- Comment #1 from fo...@guicar.fr  ---
I' ve installed same version with  PPA distribution and working well so issue
is may be related to the app image.

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

[kmail2] [Bug 423426] POP3 setup wizard defaults to unencrypted connections.

2021-11-11 Thread Laurent Montel
https://bugs.kde.org/show_bug.cgi?id=423426

--- Comment #9 from Laurent Montel  ---
Ok I need to fix wizard pop3 .
I work on it

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

[krita] [Bug 441959] Soft Proofing on krita 5 (beta 1) still has glitches, but now triggered by transparencies

2021-11-11 Thread Lynx3d
https://bugs.kde.org/show_bug.cgi?id=441959

Lynx3d  changed:

   What|Removed |Added

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

--- Comment #6 from Lynx3d  ---
Perfect, closing this bug then.

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

[lattedock] [Bug 439472] Latte dock crashes when attempting to add widgets

2021-11-11 Thread Brier
https://bugs.kde.org/show_bug.cgi?id=439472

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

latte-dock (0.10.3) using Qt 5.15.3

- What I was doing when the application crashed:

Adding widgets to the Latte Dock. This does not happen every time, but quite
frequently.

-- Backtrace (Reduced):
#4  0x7fd106f7e284 in QSGTexture::setFiltering(QSGTexture::Filtering) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7fd106fb5a3f in
QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState
const&, QSGMaterial*, QSGMaterial*) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7fd106f991b9 in
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*)
() from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7fd106f9eb7d in QSGBatchRenderer::Renderer::renderBatches() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7fd106f9f26a in QSGBatchRenderer::Renderer::render() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5

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

[lattedock] [Bug 439472] Latte dock crashes when attempting to add widgets

2021-11-11 Thread Brier
https://bugs.kde.org/show_bug.cgi?id=439472

Brier  changed:

   What|Removed |Added

 CC||brierjcr...@protonmail.com

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

[kwin] [Bug 445366] New: Pinned windows are not always on top

2021-11-11 Thread Petr Kejval
https://bugs.kde.org/show_bug.cgi?id=445366

Bug ID: 445366
   Summary: Pinned windows are not always on top
   Product: kwin
   Version: git-stable-Plasma/5.22
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: compositing
  Assignee: kwin-bugs-n...@kde.org
  Reporter: petr.kejv...@gmail.com
  Target Milestone: ---

SUMMARY
Pinned windows are not always on top.

STEPS TO REPRODUCE
1. Start any application which should be set to "keep above others". In this
example, start VLC.
2. Right click on window decoration -> other activities -> keep above others
3. Start any fullscreen application. For example use Firefox browser and press
F11.

OBSERVED RESULT
Fullscreen application is shown.

EXPECTED RESULT
Fullscreen application and window with "keep above others" should be shown at
screen. Window should be on top of fullscreen application.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro - KDE edition
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2
X11 windowing system

ADDITIONAL INFORMATION

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

[Smb4k] [Bug 442187] Smb4K 3.1.0 still has frustrating, old usability glitches and bugs (explained in description). Kills usability.

2021-11-11 Thread Alexander Reinholdt
https://bugs.kde.org/show_bug.cgi?id=442187

--- Comment #23 from Alexander Reinholdt  ---
Git commit 0187849ec06324ec37ac3fc0da4bd9cad2e863d5 by Alexander Reinholdt.
Committed on 12/11/2021 at 06:18.
Pushed by areinholdt into branch 'master'.

Refactored the bookmark menu to overcome the same glitch the shares menu
suffered from.
This is still work in progress.

M  +11   -10   core/smb4kbookmarkhandler.cpp
M  +14   -0core/smb4kbookmarkhandler.h
M  +506  -249  smb4k/smb4kbookmarkmenu.cpp
M  +42   -12   smb4k/smb4kbookmarkmenu.h

https://invent.kde.org/network/smb4k/commit/0187849ec06324ec37ac3fc0da4bd9cad2e863d5

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

[kdeconnect] [Bug 432643] kdeconnect slowing down system shutdown

2021-11-11 Thread Eduardo
https://bugs.kde.org/show_bug.cgi?id=432643

--- Comment #23 from Eduardo  ---
That's great!

Are you planning to submit a merge request?

Do you know if there is a reason for plasmashell requesting another instance of
kdeconnectd after the first one just died?  If there is no reason, maybe we
should patch this end as well.

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

[krita] [Bug 445365] New: The parameters are not reset when resetting the brush

2021-11-11 Thread thetwo
https://bugs.kde.org/show_bug.cgi?id=445365

Bug ID: 445365
   Summary: The parameters are not reset when resetting the brush
   Product: krita
   Version: 5.0.0-beta2
  Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Brush engines
  Assignee: krita-bugs-n...@kde.org
  Reporter: 310732...@qq.com
  Target Milestone: ---

Created attachment 143471
  --> https://bugs.kde.org/attachment.cgi?id=143471=edit
REPRODUCE

STEPS TO REPRODUCE
1. select a brush and modify it
2. reset the brush

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

[kde] [Bug 445364] New: Crash When Akonadi is Checking in the Background

2021-11-11 Thread Aaron Nixon
https://bugs.kde.org/show_bug.cgi?id=445364

Bug ID: 445364
   Summary: Crash When Akonadi is Checking in the Background
   Product: kde
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: aaron.ni...@gmail.com
  Target Milestone: ---

Application: akonadi_ews_resource (5.19.40 (22.03.40))
 (Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.15.0-gentoo-x86_64 x86_64
Windowing System: X11
Distribution: "Gentoo Base System release 2.8"
DrKonqi: 5.23.80 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
Just browsing the web, this happens after it's been running a while, usually
hours after login.

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Omicron (akonadi_ews_resource), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6  0x55ad2996c7d0 in QString::QString(QString const&) (other=, this=) at /usr/include/qt5/QtCore/qstring.h:1093
#7  EwsSettingsBase::eventSubscriptionId() const (this=) at
/usr/src/debug/kde-apps/kdepim-runtime-/kdepim-runtime-_build/resources/ews/ewssettingsbase.h:626
#8  EwsSubscriptionManager::start() (this=0x0) at
/usr/src/debug/kde-apps/kdepim-runtime-/kdepim-runtime-/resources/ews/ewssubscriptionmanager.cpp:48
#9  0x55ad2995da3b in EwsResource::rootFolderFetchFinished(KJob*)
(this=, job=) at
/usr/include/qt5/QtCore/qscopedpointer.h:116
#10 0x7f8eadc3d84e in  () at /usr/lib64/libQt5Core.so.5
#11 0x7f8eb6b52033 in KJob::result(KJob*, KJob::QPrivateSignal)
(this=this@entry=0x55ad2d01ed50, _t1=, _t1@entry=0x55ad2d01ed50,
_t2=...) at
/usr/src/debug/kde-frameworks/kcoreaddons-/kcoreaddons-_build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#12 0x7f8eb6b5352b in KJob::finishJob(bool) (this=0x55ad2d01ed50,
emitResult=) at
/usr/src/debug/kde-frameworks/kcoreaddons-/kcoreaddons-/src/lib/jobs/kjob.cpp:98
#13 0x7f8eadc3d84e in  () at /usr/lib64/libQt5Core.so.5
#14 0x7f8eb6b52033 in KJob::result(KJob*, KJob::QPrivateSignal)
(this=this@entry=0x55ad2cf8b520, _t1=, _t1@entry=0x55ad2cf8b520,
_t2=...) at
/usr/src/debug/kde-frameworks/kcoreaddons-/kcoreaddons-_build/src/lib/KF5CoreAddons_autogen/include/moc_kjob.cpp:633
#15 0x7f8eb6b5352b in KJob::finishJob(bool) (this=0x55ad2cf8b520,
emitResult=) at
/usr/src/debug/kde-frameworks/kcoreaddons-/kcoreaddons-/src/lib/jobs/kjob.cpp:98
#16 0x7f8eadc3d84e in  () at /usr/lib64/libQt5Core.so.5
#17 0x7f8eb6f6cc06 in KIO::SlaveInterface::dispatch(int, QByteArray const&)
(this=0x55ad2b068960, _cmd=, rawdata=...) at
/usr/src/debug/kde-frameworks/kio-/kio-/src/core/slaveinterface.cpp:149
#18 0x7f8eb6f6b259 in KIO::SlaveInterface::dispatch() (this=0x55ad2b068960)
at
/usr/src/debug/kde-frameworks/kio-/kio-/src/core/slaveinterface.cpp:78
#19 0x7f8eb6f6f91a in KIO::Slave::gotInput() (this=0x55ad2b068960) at
/usr/src/debug/kde-frameworks/kio-/kio-/src/core/slave.cpp:336
#20 0x7f8eadc3d84e in  () at /usr/lib64/libQt5Core.so.5
#21 0x7f8eadc358ee in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#22 0x7f8eae7b764f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#23 0x7f8eadc0a548 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#24 0x7f8eadc0d9ea in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#25 0x7f8eadc5daf3 in  () at /usr/lib64/libQt5Core.so.5
#26 0x7f8ea902fc8b in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#27 0x7f8ea902ff38 in  () at /usr/lib64/libglib-2.0.so.0
#28 0x7f8ea902ffef in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#29 0x7f8eadc5d5aa in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#30 0x7f8eadc08ff3 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#31 0x7f8eb6b547ce in KJob::exec() (this=this@entry=0x55ad2d126a10) at
/usr/include/qt5/QtCore/qflags.h:121
#32 0x55ad2996c438 in EwsSubscriptionManager::cancelSubscription()
(this=0x55ad2d101000) at
/usr/src/debug/kde-apps/kdepim-runtime-/kdepim-runtime-/resources/ews/ewssubscriptionmanager.cpp:66
#33 0x55ad2996e087 in EwsSubscriptionManager::~EwsSubscriptionManager()
(this=0x55ad2d101000, __in_chrg=) at
/usr/src/debug/kde-apps/kdepim-runtime-/kdepim-runtime-/resources/ews/ewssubscriptionmanager.cpp:42
#34 0x55ad2996e159 in EwsSubscriptionManager::~EwsSubscriptionManager()
(this=0x55ad2d101000, __in_chrg=) at

[kmymoney] [Bug 444555] error when try to save file after modifying sort order and adding entries to the ledger or just change date of one entry

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=444555

twhpi...@hotmail.com changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |NOT A BUG
 Status|NEEDSINFO   |RESOLVED

--- Comment #3 from twhpi...@hotmail.com ---
Did not realize wrong directory was chosen to save the file

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

[kwin] [Bug 445259] Several Chromium-based browsers suddenly fail to bring up their browser windows on Wayland

2021-11-11 Thread Sok Ann Yap
https://bugs.kde.org/show_bug.cgi?id=445259

Sok Ann Yap  changed:

   What|Removed |Added

 CC||sok...@gmail.com

--- Comment #2 from Sok Ann Yap  ---
This started happening to me after upgrading to kwin-5.23.3.

Chromium works fine on ozone/wayland again, after backing out these 2 commits:
- e2f9f35c (wayland: Check workspace position when preferred deco mode changes)
- ceec4e50 (wayland: Fix wayland windows growing after toggling decorations)

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

[konsole] [Bug 445363] New: Konsole leaks memory when used as a part [LSAN]

2021-11-11 Thread Waqar Ahmed
https://bugs.kde.org/show_bug.cgi?id=445363

Bug ID: 445363
   Summary: Konsole leaks memory when used as a part [LSAN]
   Product: konsole
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: waqar@gmail.com
  Target Milestone: ---

SUMMARY

LSAN reports leaks when using konsole inside another application (e.g., kate).
May be false positives but I felt it necessary to report them at least.

Indirect leak of 840 byte(s) in 1 object(s) allocated from:
#0 0x5651f576e779 in operator new(unsigned long)
(/home/waqar/kde/usr/bin/kate+0x283779)
#1 0x7ff2b2531c38 in QMenu::QMenu(QWidget*)
(/usr/lib/libQt5Widgets.so.5+0x2e8c38)
#2 0x7ff2b3fd635e in KXMLGUI::BuildHelper::createContainer(QWidget*, int,
QDomElement const&, QAction*&, KXMLGUIBuilder**)
/home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory_p.cpp:780:38
#3 0x7ff2b3fd2898 in
KXMLGUI::BuildHelper::processContainerElement(QDomElement const&, QString
const&, QString const&)
/home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory_p.cpp:723:30
#4 0x7ff2b3fd1cb3 in KXMLGUI::BuildHelper::processElement(QDomElement
const&) /home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory_p.cpp:529:9
#5 0x7ff2b3fd18c3 in KXMLGUI::BuildHelper::build(QDomElement const&)
/home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory_p.cpp:515:9
#6 0x7ff2b3fd30c9 in
KXMLGUI::BuildHelper::processContainerElement(QDomElement const&, QString
const&, QString const&)
/home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory_p.cpp:768:41
#7 0x7ff2b3fd1cb3 in KXMLGUI::BuildHelper::processElement(QDomElement
const&) /home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory_p.cpp:529:9
#8 0x7ff2b3fd18c3 in KXMLGUI::BuildHelper::build(QDomElement const&)
/home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory_p.cpp:515:9
#9 0x7ff2b3fb7ae9 in KXMLGUIFactory::addClient(KXMLGUIClient*)
/home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory.cpp:253:36
#10 0x7ff29efdd0dd in
Konsole::SessionController::showDisplayContextMenu(QPoint const&)
/home/waqar/kde/src/utilities/konsole/src/session/SessionController.cpp:1765:18
#11 0x7ff29f01810e in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(Konsole::SessionController::*)(QPoint const&)>::call(void
(Konsole::SessionController::*)(QPoint const&), Konsole::SessionController*,
void**) /usr/include/qt/QtCore/qobjectdefs_impl.h:152:13
#12 0x7ff29f017e2e in void QtPrivate::FunctionPointer::call, void>(void (Konsole::SessionController::*)(QPoint const&),
Konsole::SessionController*, void**)
/usr/include/qt/QtCore/qobjectdefs_impl.h:185:13
#13 0x7ff29f017a46 in QtPrivate::QSlotObject,
void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*)
/usr/include/qt/QtCore/qobjectdefs_impl.h:418:17
#14 0x7ff2b16ea8c4  (/usr/lib/libQt5Core.so.5+0x2fa8c4)
#15 0x7ff29ec83426 in Konsole::TerminalDisplay::configureRequest(QPoint
const&)
/home/waqar/kde/build/utilities/konsole/src/konsoleprivate_autogen/DRAQINE3W2/moc_TerminalDisplay.cpp:580:5
#16 0x7ff29eecb046 in
Konsole::TerminalDisplay::mousePressEvent(QMouseEvent*)
/home/waqar/kde/src/utilities/konsole/src/terminalDisplay/TerminalDisplay.cpp:1226:20
#17 0x7ff2b23e7fcd in QWidget::event(QEvent*)
(/usr/lib/libQt5Widgets.so.5+0x19efcd)

Indirect leak of 840 byte(s) in 1 object(s) allocated from:
#0 0x5651f576e779 in operator new(unsigned long)
(/home/waqar/kde/usr/bin/kate+0x283779)
#1 0x7ff2b2531c38 in QMenu::QMenu(QWidget*)
(/usr/lib/libQt5Widgets.so.5+0x2e8c38)
#2 0x7ff2b3fd635e in KXMLGUI::BuildHelper::createContainer(QWidget*, int,
QDomElement const&, QAction*&, KXMLGUIBuilder**)
/home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory_p.cpp:780:38
#3 0x7ff2b3fd2898 in
KXMLGUI::BuildHelper::processContainerElement(QDomElement const&, QString
const&, QString const&)
/home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory_p.cpp:723:30
#4 0x7ff2b3fd1cb3 in KXMLGUI::BuildHelper::processElement(QDomElement
const&) /home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory_p.cpp:529:9
#5 0x7ff2b3fd18c3 in KXMLGUI::BuildHelper::build(QDomElement const&)
/home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory_p.cpp:515:9
#6 0x7ff2b3fb7ae9 in KXMLGUIFactory::addClient(KXMLGUIClient*)
/home/waqar/kde/src/frameworks/kxmlgui/src/kxmlguifactory.cpp:253:36
#7 0x7ff29efdd0dd in
Konsole::SessionController::showDisplayContextMenu(QPoint const&)
/home/waqar/kde/src/utilities/konsole/src/session/SessionController.cpp:1765:18
#8 0x7ff29f01810e in QtPrivate::FunctorCall,
QtPrivate::List, void, void
(Konsole::SessionController::*)(QPoint const&)>::call(void
(Konsole::SessionController::*)(QPoint const&), Konsole::SessionController*,
void**) 

[systemsettings] [Bug 444525] can't always choose a different splash screen than global theme

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=444525

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[systemsettings] [Bug 444569] Keyboard layout shortcuts activate wrong language [regression]

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=444569

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[krita] [Bug 441959] Soft Proofing on krita 5 (beta 1) still has glitches, but now triggered by transparencies

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=441959

Bug Janitor Service  changed:

   What|Removed |Added

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

--- Comment #5 from Bug Janitor Service  ---
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.

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

[frameworks-kwindowsystem] [Bug 443160] Cannot move cursor to absolute left of screen

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=443160

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kdenlive] [Bug 442235] Replacement of one effect by another in the latest version.

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=442235

Bug Janitor Service  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |WORKSFORME
 Status|NEEDSINFO   |RESOLVED

--- Comment #5 from Bug Janitor Service  ---
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!

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

[kmymoney] [Bug 444555] error when try to save file after modifying sort order and adding entries to the ledger or just change date of one entry

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=444555

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[KScreen] [Bug 444526] Resolution of external 4k monitor sometimes changes to FHD

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=444526

--- Comment #4 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[systemsettings] [Bug 444520] Baloo content indexing resurrects itself after being killed *and* disabled

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=444520

--- Comment #2 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[plasmashell] [Bug 444416] sometimes plasma unusable when copening a window in tackbar

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=16

--- Comment #6 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[Discover] [Bug 444246] cant update packages via discover

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=444246

--- Comment #9 from Bug Janitor Service  ---
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

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

[plasmashell] [Bug 445362] New: Every time on boot, plasma crashes on secondary monitor

2021-11-11 Thread Brier
https://bugs.kde.org/show_bug.cgi?id=445362

Bug ID: 445362
   Summary: Every time on boot, plasma crashes on secondary
monitor
   Product: plasmashell
   Version: 5.23.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: brierjcr...@protonmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.23.3)

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

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

Simply booting my PC.


- Unusual behavior I noticed:

Every time I boot my PC into KDE Neon, the secondary monitor's instance of
Plasma crashes. I have tried changing the secondary monitor to the primary, but
to no avail.

The crash can be reproduced every time.

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

[New LWP 1507]
[New LWP 1516]
[New LWP 1551]
[New LWP 1552]
[New LWP 1553]
[New LWP 1554]
[New LWP 1555]
[New LWP 1557]
[New LWP 1558]
[New LWP 1559]
[New LWP 1560]
[New LWP 1561]
[New LWP 1562]
[New LWP 1563]
[New LWP 1564]
[New LWP 1565]
[New LWP 1566]
[New LWP 1567]
[New LWP 1568]
[New LWP 1569]
[New LWP 1710]
[New LWP 1807]
[New LWP 1808]
[New LWP 1810]
[New LWP 1833]
[New LWP 1840]
[New LWP 1841]
[New LWP 2122]
[New LWP 2123]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f52c26c8aff in __GI___poll (fds=0x7ffd495cc938, nfds=1, timeout=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
__preamble__
drkonqi_qmltrace_thread:1
Failed to do pygdbmi parsing: No module named 'pygdbmi'
frame={level="0",func="placeToolBox",file="/usr/share/plasma/packages/org.kde.desktoptoolbox/contents/ui/ToolBoxRoot.qml",fullname="/usr/share/plasma/packages/org.kde.desktoptoolbox/contents/ui".
-
(beware that frames may have been optimized out)

[Current thread is 1 (Thread 0x7f52be81d9c0 (LWP 1493))]

Thread 30 (Thread 0x7f52619ec700 (LWP 2123)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5652008e7750) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5652008e7700,
cond=0x5652008e7728) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5652008e7728, mutex=0x5652008e7700) at
pthread_cond_wait.c:638
#3  0x7f52c2a5d5cb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f52c46c6c24 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f52c46c7099 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f52c2a5745c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f52c19a6609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f52c26d5293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 29 (Thread 0x7f5252bd7700 (LWP 2122)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x565200a3adb0) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x565200a3ad60,
cond=0x565200a3ad88) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x565200a3ad88, mutex=0x565200a3ad60) at
pthread_cond_wait.c:638
#3  0x7f52b6833e7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f52b6833a7b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f52c19a6609 in start_thread (arg=) at
pthread_create.c:477
#6  0x7f52c26d5293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 28 (Thread 0x7f521e7fc700 (LWP 1841)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x5651ffa7e2b0) at ../sysdeps/nptl/futex-internal.h:183
#1  __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5651ffa7e260,
cond=0x5651ffa7e288) at pthread_cond_wait.c:508
#2  __pthread_cond_wait (cond=0x5651ffa7e288, mutex=0x5651ffa7e260) at
pthread_cond_wait.c:638
#3  0x7f52c2a5d5cb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f52c46c6c24 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f52c46c7099 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f52c2a5745c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f52c19a6609 in start_thread (arg=) at
pthread_create.c:477
#8  0x7f52c26d5293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7f521effd700 (LWP 1840)):
#0  futex_wait_cancelable (private=, expected=0,
futex_word=0x565200813a60) at ../sysdeps/nptl/futex-internal.h:183
#1  

[krita] [Bug 445361] New: Animation Playback Lag

2021-11-11 Thread GreenCrystal19
https://bugs.kde.org/show_bug.cgi?id=445361

Bug ID: 445361
   Summary: Animation Playback Lag
   Product: krita
   Version: 5.0.0-beta2
  Platform: macOS (DMG)
OS: macOS
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Animation
  Assignee: krita-bugs-n...@kde.org
  Reporter: greencrystal2...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1.  Create a semi-complex animation where frames change from one image to a
completely different image/shot (of a different character, image file, ect.)
2.  Play the animation using the play button in the timeline

OBSERVED RESULT
When transitioning from two completely different frames/images, the viewer will
lag; even, vertically orientated rectangular chunks of the previous frame will
show up on the current frame. The frame will play properly if the animation is
paused (not stopped, paused). This bug makes timing complex scenes/transitions
rather difficult, and the animation itself is a bit uncomfortable to watch.
EXPECTED RESULT
The frame should transition instantly and completely from one frame to the
next, without feedback/residue (for lack of a better word) from the previous
frame.

SOFTWARE/OS VERSIONS
macOS: 11.6 

ADDITIONAL INFORMATION
The rest of the 5.0 beta works almost perfectly for animation purposes. =)

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

[systemsettings] [Bug 444864] Poor UI for configuring label to be displayed over flag

2021-11-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=444864

Nate Graham  changed:

   What|Removed |Added

   Target Milestone|1.0 |---
   Keywords|regression  |usability
Summary|Can't display label over|Poor UI for configuring
   |flag anymore|label to be displayed over
   ||flag
Product|plasmashell |systemsettings
  Component|Keyboard Layout |kcm_keyboard

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

[plasmashell] [Bug 444864] Can't display label over flag anymore

2021-11-11 Thread David Chmelik
https://bugs.kde.org/show_bug.cgi?id=444864

--- Comment #6 from David Chmelik  ---
I was able to add label Ελ where the flag was displayed but the letters
weren't, so this isn't actually a bug, but as you said, hard to find...

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

[digikam] [Bug 445360] New: Ability to Rename files with random value

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445360

Bug ID: 445360
   Summary: Ability to Rename files with random value
   Product: digikam
   Version: 7.3.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Import-Rename
  Assignee: digikam-bugs-n...@kde.org
  Reporter: vit...@protonmail.com
  Target Milestone: ---

Hi everyone

In Digikam when we rename files with import or rename them with BQM, we can
chose metadata values or incremental values and not random values. It can be
limited. 
For example when i import landscapes pictures into my landscapes folder i can
only use the date values as namming pattern because all others choice will
result in duplicates.

It can be useful to include random namming (UUID v1/2/4 can be cool) for people
who have folders of memes or theme-related photos and use Tags/metadata to find
files instead of files names.


EXPECTED RESULT
Be able to rename files with random value Like UUIDv4 and/or others random
value generators.


ADDITIONAL INFORMATION
English isn't my first language, i'm sorry if there is faults. And it's also my
first bug report here, i'm sorry if i have done mistakes.

Thx if you take this proposal into consideration.

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

[plasmashell] [Bug 444864] Can't display label over flag anymore

2021-11-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=444864

--- Comment #5 from Nate Graham  ---
Sorry. "KCM" == "KDE Control Module" == "Page in System Settings"

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

[frameworks-kdeclarative] [Bug 417636] Title rows of QML KCMs fade in and out, but others don't

2021-11-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=417636

--- Comment #13 from Nate Graham  ---
You're welcome!

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

[plasmashell] [Bug 444864] Can't display label over flag anymore

2021-11-11 Thread David Chmelik
https://bugs.kde.org/show_bug.cgi?id=444864

--- Comment #4 from David Chmelik  ---
I don't know what KCM is--in technical writing you're supposed to define
abbreviations before you use them, no matter how simple, if they haven't been
used before.

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

[frameworks-kdeclarative] [Bug 417636] Title rows of QML KCMs fade in and out, but others don't

2021-11-11 Thread Oliver Beard
https://bugs.kde.org/show_bug.cgi?id=417636

--- Comment #12 from Oliver Beard  ---
Thanks Nate, this bug was a particular eyesore.

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

[systemsettings] [Bug 445359] New: System Settings Crashes When Applying changes to Virtual Desktops

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445359

Bug ID: 445359
   Summary: System Settings Crashes When Applying changes to
Virtual Desktops
   Product: systemsettings
   Version: 5.22.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: magicsoupb...@vivaldi.net
  Target Milestone: ---

Application: systemsettings5 (5.22.5)

Qt Version: 5.15.2
Frameworks Version: 5.87.0
Operating System: Linux 5.14.16-301.fc35.x86_64 x86_64
Windowing System: Wayland
Drkonqi Version: 5.22.5
Distribution: Fedora Linux 35 (KDE Plasma)

-- Information about the crash:
- What I was doing when the application crashed: Adding an additional desktop
in the Virtual Desktops setting. I had the application open on an external
monitor. The monitor had a resolution of 1920x1080, my laptop had a different
resolution of 2256x1504 with fractional scaling set at 150%. This was in
Wayland.

- Custom settings of the application: added second desktop named Desktop 2

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f22293bd940
(LWP 3068))]
[KCrash Handler]
#6  0x7f222bf176a4 in QWaylandClientExtensionPrivate::handleRegistryGlobal
(data=0x55db19af7f80, registry=0x55db166073f0, id=47, interface=..., version=1)
at global/qwaylandclientextension.cpp:67
#7  0x7f222bf041b9 in QtWaylandClient::QWaylandDisplay::registry_global
(this=, id=, interface=..., version=) at
/usr/src/debug/qt5-qtwayland-5.15.2-14.fc35.x86_64/src/client/qwaylanddisplay.cpp:397
#8  0x7f222bf20af3 in QtWayland::wl_registry::handle_global
(data=0x55db16603490, object=, name=47, interface=0x55db18ee1150
"org_kde_kwin_blur_manager", version=1) at
/usr/src/debug/qt5-qtwayland-5.15.2-14.fc35.x86_64/src/client/qwayland-wayland.cpp:94
#9  0x7f22297b6c04 in ffi_call_unix64 () at ../src/x86/unix64.S:76
#10 0x7f22297b6108 in ffi_call (cif=cif@entry=0x7ffef73781d0, fn=, rvalue=, rvalue@entry=0x0,
avalue=avalue@entry=0x7ffef73782a0) at ../src/x86/ffi64.c:525
#11 0x7f222be71d10 in wl_closure_invoke
(closure=closure@entry=0x55db18ee1070, target=,
target@entry=0x55db166073f0, opcode=opcode@entry=0, data=,
flags=) at ../src/connection.c:1018
#12 0x7f222be7241b in dispatch_event (display=display@entry=0x55db166072a0,
queue=, queue=) at ../src/wayland-client.c:1452
#13 0x7f222be7260c in dispatch_queue (queue=0x55db16607370,
display=0x55db166072a0) at ../src/wayland-client.c:1598
#14 wl_display_dispatch_queue_pending (display=0x55db166072a0,
queue=0x55db16607370) at ../src/wayland-client.c:1840
#15 0x7f222befc6a3 in QtWaylandClient::QWaylandDisplay::flushRequests
(this=0x55db16603480) at
/usr/src/debug/qt5-qtwayland-5.15.2-14.fc35.x86_64/src/client/qwaylanddisplay.cpp:222
#16 0x7f222e50b3f0 in doActivate (sender=0x55db166377b0,
signal_index=3, argv=0x7ffef7378570) at kernel/qobject.cpp:3898
#17 0x7f222e506327 in QMetaObject::activate
(sender=sender@entry=0x55db166377b0, m=m@entry=0x7f222e7b0460
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffef7378570)
at kernel/qobject.cpp:3946
#18 0x7f222e50db4a in QSocketNotifier::activated
(this=this@entry=0x55db166377b0, _t1=..., _t2=, _t3=...) at
.moc/moc_qsocketnotifier.cpp:178
#19 0x7f222e50e363 in QSocketNotifier::event (this=0x55db166377b0,
e=0x7ffef7378670) at kernel/qsocketnotifier.cpp:302
#20 0x7f222f0b0443 in QApplicationPrivate::notify_helper (this=, receiver=0x55db166377b0, e=0x7ffef7378670) at
kernel/qapplication.cpp:3632
#21 0x7f222e4d7798 in QCoreApplication::notifyInternal2
(receiver=0x55db166377b0, event=0x7ffef7378670) at
kernel/qcoreapplication.cpp:1064
#22 0x7f222e5295ff in socketNotifierSourceDispatch (source=0x55db16649090)
at kernel/qeventdispatcher_glib.cpp:107
#23 0x7f222c27333f in g_main_dispatch (context=0x55db166683e0) at
../glib/gmain.c:3381
#24 g_main_context_dispatch (context=0x55db166683e0) at ../glib/gmain.c:4099
#25 0x7f222c2c82b8 in g_main_context_iterate.constprop.0
(context=context@entry=0x55db166683e0, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#26 0x7f222c2709e3 in g_main_context_iteration (context=0x55db166683e0,
may_block=1) at ../glib/gmain.c:4240
#27 0x7f222e528b78 in QEventDispatcherGlib::processEvents
(this=0x55db1668e940, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#28 0x7f222e4d61a2 in QEventLoop::exec (this=this@entry=0x7ffef73788e0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#29 0x7f222e4de6e4 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#30 0x55db153ff58c in 

[kwin] [Bug 432104] stylus/pen input does not work on window decorations

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=432104

--- Comment #5 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin/-/merge_requests/1647

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

[krita] [Bug 445337] Resource storages are not checked and trigger a safe assert if invalid

2021-11-11 Thread amyspark
https://bugs.kde.org/show_bug.cgi?id=445337

amyspark  changed:

   What|Removed |Added

   Assignee|krita-bugs-n...@kde.org |a...@amyspark.me
 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED

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

[kdeconnect] [Bug 445358] New: Crash in Notification::createKNotification() when receiving an SMS

2021-11-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=445358

Bug ID: 445358
   Summary: Crash in Notification::createKNotification() when
receiving an SMS
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: n...@kde.org
  Target Milestone: ---

Application: kdeconnectd (21.04.1)
 (Compiled from sources)
Qt Version: 5.15.2
Frameworks Version: 5.85.0
Operating System: Linux 5.14.16-201.fc34.x86_64 x86_64
Windowing System: Wayland
Drkonqi Version: 5.22.5
Distribution: "Fedora release 34 (Thirty Four)"

-- Information about the crash:
I received an SMS on my Android phone which is connected to my PC with KDE
Connect

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault

[KCrash Handler]
#4  0x in ?? ()
#5  0x7fe89ae46d42 in QObjectPrivate::connectImpl(QObject const*, int,
QObject const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int
const*, QMetaObject const*) () from /lib64/libQt5Core.so.5
#6  0x7fe89ae4706d in QObject::connectImpl(QObject const*, void**, QObject
const*, void**, QtPrivate::QSlotObjectBase*, Qt::ConnectionType, int const*,
QMetaObject const*) () from /lib64/libQt5Core.so.5
#7  0x7fe885f8ffbe in Notification::createKNotification(NetworkPacket
const&) () from /usr/lib64/qt5/plugins/kdeconnect/kdeconnect_notifications.so
#8  0x7fe885f9091d in NotificationsPlugin::receivePacket(NetworkPacket
const&) () from /usr/lib64/qt5/plugins/kdeconnect/kdeconnect_notifications.so
#9  0x7fe89c30a5e1 in Device::privateReceivedPacket(NetworkPacket const&)
() from /lib64/libkdeconnectcore.so.21
#10 0x7fe89ae4d3a9 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#11 0x7fe89c2fb3e1 in LanDeviceLink::dataReceived() () from
/lib64/libkdeconnectcore.so.21
#12 0x7fe89ae4d3a9 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#13 0x7fe89c2f3b24 in SocketLineReader::dataReceived() () from
/lib64/libkdeconnectcore.so.21
#14 0x7fe89ae4d3a9 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#15 0x7fe89a5f7ab5 in QSslSocketBackendPrivate::transmit() () from
/lib64/libQt5Network.so.5
#16 0x7fe89ae4d3f0 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#17 0x7fe89a5b1a1f in QAbstractSocketPrivate::canReadNotification() () from
/lib64/libQt5Network.so.5
#18 0x7fe89a5c4b49 in QReadNotifier::event(QEvent*) () from
/lib64/libQt5Network.so.5
#19 0x7fe89b982443 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#20 0x7fe89ae19798 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#21 0x7fe89ae6b5ff in socketNotifierSourceDispatch(_GSource*, int
(*)(void*), void*) () from /lib64/libQt5Core.so.5
#22 0x7fe8992844cf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#23 0x7fe8992d84f8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#24 0x7fe899281c03 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#25 0x7fe89ae6ab78 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#26 0x7fe89ae181a2 in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#27 0x7fe89ae206e4 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#28 0x560859db7fdd in main ()
[Inferior 1 (process 439226) detached]

Report to https://bugs.kde.org/

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

[systemsettings] [Bug 440493] Add an option for whether to enable or disable Bluetooth adapters at session start

2021-11-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=440493

Nate Graham  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|CONFIRMED   |RESOLVED

--- Comment #31 from Nate Graham  ---
Hmm, there is a "PrepareForShutdown" method, and a "PrepareForSleep" method,
but nothing about logout that I can see. Still investigating.

However all of this is getting a bit far from the original request, which was
implemented. If it has a bug in it, that should ideally be tracked with a
seaprate bug report. Can I ask you to file a new bug report that is only about
the issue of state not being saved on logout? You can mention whatever details
you want from this bug report, and link them using the "See Also" field.
Thanks!

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

[digikam] [Bug 445307] Unable to recover digiKam data on ubuntu 20.04 with Mysql server 8.0.27

2021-11-11 Thread Gerry Matte
https://bugs.kde.org/show_bug.cgi?id=445307

--- Comment #3 from Gerry Matte  ---
Thank you Maik for your suggestions.
I was able to generate a startup log and during the process the original error
window displayed again.  See attachment.   

That error suggested I try again "with an empty database."  So I deleted the 33
MySql tables in my "Pictures" database, rebooted so the active debug variable
was dropped, and then ran digiKam again - it successfully rebuilt the tables
and then queried me for my pictures collection.  After processing my pictures,
digiKam was fully operational.

I did however lose the three hours of facial recognition data . but I can
redo that process some other time.

It bothers me however that a MySql backup file could not be used to
successfully restore digiKam's database.  Since the MySql server resides on my
Linux root partition and I keep my user data on a different "home" partition
(where my backups reside) perhaps digiKam should be given the ability to save
and restore database backups itself.   Can you consider this as a feature
request for a future version ?

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

[digikam] [Bug 445307] Unable to recover digiKam data on ubuntu 20.04 with Mysql server 8.0.27

2021-11-11 Thread Gerry Matte
https://bugs.kde.org/show_bug.cgi?id=445307

--- Comment #2 from Gerry Matte  ---
Created attachment 143470
  --> https://bugs.kde.org/attachment.cgi?id=143470=edit
digiKam Error Message trying to access MySql gatabase

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

[okular] [Bug 444168] zooming wrong

2021-11-11 Thread Amnon
https://bugs.kde.org/show_bug.cgi?id=444168

--- Comment #20 from Amnon  ---
@ Albert Astals Cid:

After a lot of looking around I finally got flatpak to install Okular Version
21.08.3 on my machine. 

Snap does not support it -- their latest is version 20.12.3. 

Thanks for your gracious assistance.

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

[kwin] [Bug 443224] Kwin puts titlebar wrongly in some java apps

2021-11-11 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=443224

Nate Graham  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Ever confirmed|1   |0
  Component|platform-x11-nested |wayland-generic
 Resolution|WAITINGFORINFO  |---

--- Comment #10 from Nate Graham  ---
OK, it could be an app-specific issue, or it would be a wayland-specific
regression. Or an element of both.

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

[Elisa] [Bug 445357] use media-default-album instead of media-optical-audio icons

2021-11-11 Thread andreas_k
https://bugs.kde.org/show_bug.cgi?id=445357

--- Comment #1 from andreas_k  ---
Created attachment 143469
  --> https://bugs.kde.org/attachment.cgi?id=143469=edit
media-default-album

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

[Elisa] [Bug 445357] New: use media-default-album instead of media-optical-audio icons

2021-11-11 Thread andreas_k
https://bugs.kde.org/show_bug.cgi?id=445357

Bug ID: 445357
   Summary: use media-default-album instead of media-optical-audio
icons
   Product: Elisa
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: matthieu_gall...@yahoo.fr
  Reporter: andrea...@abwesend.de
  Target Milestone: ---

SUMMARY
The media-optical-audio icon from the device folder was designed to show an
optical media (cd) with audio tracks on it. Elisa use this icons if there is no
album cover available. 

I suggest to use media-default-album icon.
1. it's designed as album icon if there is no album cover available
2. it look good
3. there is also media-default-track icon which can be used in the track view

I can submit the patch to Elisa, but want to use first the bugtracker for
discussion.

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

[plasmashell] [Bug 445356] New: Virtual desktop shortcuts are hard to find.

2021-11-11 Thread Lucas
https://bugs.kde.org/show_bug.cgi?id=445356

Bug ID: 445356
   Summary: Virtual desktop shortcuts are hard to find.
   Product: plasmashell
   Version: 5.23.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Pager
  Assignee: h...@kde.org
  Reporter: l...@hotmail.com.br
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY
Virtual desktop shortcuts are hard to find

STEPS TO REPRODUCE
1.  Right click the pager applet and go to its settings
or
2. Right click the pager applet and select Configure Virtual Desktops

OBSERVED RESULT
There are no options to configure the keyboard shortcuts to change virtual
desktops

EXPECTED RESULT
A section of settings to configure keyboard shortcuts, or a link pointing to
the configuration.

SOFTWARE/OS VERSIONS
Operating System: Manjaro
KDE Plasma Version: 5.23
KDE Frameworks Version: 5.87
Qt Version: 5.15

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

[Akonadi] [Bug 445355] Google Groupware regularly crashes with no interaction from user

2021-11-11 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=445355

Justin Zobel  changed:

   What|Removed |Added

   Platform|Other   |Fedora RPMs

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

[Akonadi] [Bug 445355] New: Google Groupware regularly crashes with no interaction from user

2021-11-11 Thread Justin Zobel
https://bugs.kde.org/show_bug.cgi?id=445355

Bug ID: 445355
   Summary: Google Groupware regularly crashes with no interaction
from user
   Product: Akonadi
   Version: 5.17.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: Google Resource
  Assignee: dvra...@kde.org
  Reporter: justin.zo...@gmail.com
CC: kdepim-b...@kde.org
  Target Milestone: ---

Application: Google Groupware (justin.zo...@gmail.com)
(akonadi_google_resource), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = {}}
[KCrash Handler]
#6  __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7  0x7f3b51c968c3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8  0x7f3b51c496b6 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9  0x7f3b51c337d3 in __GI_abort () at abort.c:79
#10 0x7f3b520fd45b in qt_message_fatal (message=...,
context=...) at global/qlogging.cpp:1914
#11 QMessageLogger::fatal (this=this@entry=0x7ffddbac9a78,
msg=msg@entry=0x7f3b523bc028 "ASSERT failure in %s: \"%s\", file %s, line %d")
at global/qlogging.cpp:893
#12 0x7f3b520fc8be in qt_assert_x (where=, what=, file=, line=) at global/qglobal.cpp:3366
#13 0x7f3b53dd84e3 in Akonadi::ResourceBase::collectionsRetrieved
(this=0x7ffddbaca2a0, collections=...) at
/tmp/akonadi/src/agentbase/resourcebase.cpp:749
#14 0x55c8c074b297 in GoogleResource::collectionsRetrievedFromHandler
(this=0x7ffddbaca2a0, collections=...) at
/usr/src/debug/kdepim-runtime-21.04.3-1.fc35.x86_64/resources/google-groupware/googleresource.cpp:387
#15 0x55c8c0765c73 in operator() (job=0x55c8c117fd60,
__closure=0x55c8c1123600) at
/usr/src/debug/kdepim-runtime-21.04.3-1.fc35.x86_64/resources/google-groupware/calendarhandler.cpp:116
#16 QtPrivate::FunctorCall,
QtPrivate::List, void, CalendarHandler::retrieveCollections(const
Akonadi::Collection&):: >::call (arg=,
f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#17 QtPrivate::Functor,
1>::call, void> (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#18 QtPrivate::QFunctorSlotObject, 1,
QtPrivate::List, void>::impl(int, QtPrivate::QSlotObjectBase *,
QObject *, void **, bool *) (which=, this_=0x55c8c11235f0,
r=, a=, ret=) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#19 0x7f3b523263a9 in QtPrivate::QSlotObjectBase::call (a=0x7ffddbac9da0,
r=, this=0x55c8c11235f0) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#20 doActivate (sender=0x55c8c117fd60, signal_index=3,
argv=0x7ffddbac9da0) at kernel/qobject.cpp:3886
#21 0x7f3b52321327 in QMetaObject::activate (sender=,
m=m@entry=0x7f3b534c3080 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffddbac9da0)
at kernel/qobject.cpp:3946
#22 0x7f3b534b1fd3 in KGAPI2::Job::finished (this=,
_t1=) at
/usr/src/debug/libkgapi-21.04.3-1.fc35.x86_64/redhat-linux-build/src/core/KPimGAPICore_autogen/include/moc_job.cpp:214
#23 0x7f3b5231cf09 in QObject::event (this=0x55c8c117fd60,
e=0x55c8c11b2f00) at kernel/qobject.cpp:1314
#24 0x7f3b52ec0443 in QApplicationPrivate::notify_helper (this=, receiver=0x55c8c117fd60, e=0x55c8c11b2f00) at
kernel/qapplication.cpp:3632
#25 0x7f3b522f2798 in QCoreApplication::notifyInternal2
(receiver=0x55c8c117fd60, event=0x55c8c11b2f00) at
kernel/qcoreapplication.cpp:1064
#26 0x7f3b522f5d06 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55c8c0eb0120) at
kernel/qcoreapplication.cpp:1821
#27 0x7f3b523440d7 in postEventSourceDispatch (s=0x55c8c10d0100) at
kernel/qeventdispatcher_glib.cpp:277
#28 0x7f3b5041933f in g_main_dispatch (context=0x7f3b38005000) at
../glib/gmain.c:3381
#29 g_main_context_dispatch (context=0x7f3b38005000) at ../glib/gmain.c:4099
#30 0x7f3b5046e2b8 in g_main_context_iterate.constprop.0
(context=context@entry=0x7f3b38005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#31 0x7f3b504169e3 in g_main_context_iteration (context=0x7f3b38005000,
may_block=1) at ../glib/gmain.c:4240
#32 0x7f3b52343b78 in QEventDispatcherGlib::processEvents
(this=0x55c8c10ccb10, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#33 0x7f3b522f11a2 in QEventLoop::exec (this=this@entry=0x7ffddbaca1d0,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#34 0x7f3b522f96e4 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#35 0x7f3b53dd6ce2 in Akonadi::ResourceBase::init (r=...) at
/tmp/akonadi/src/agentbase/resourcebase.cpp:555
#36 0x55c8c0751c96 in Akonadi::ResourceBase::init
(argc=, argv=0x7ffddbaca2a0) at
/usr/include/KF5/AkonadiAgentBase/resourcebase.h:183
#37 0x7f3b51c34560 in __libc_start_call_main

[Breeze] [Bug 418547] "Audio CDs" and "CDDB retrieval" kcms are represented by the same icon

2021-11-11 Thread andreas_k
https://bugs.kde.org/show_bug.cgi?id=418547

--- Comment #6 from andreas_k  ---
https://invent.kde.org/multimedia/audiocd-kio/-/merge_requests/

feel free to review the MR.

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

[kontact] [Bug 162270] Summary View: Display event parameters

2021-11-11 Thread Allen Winter
https://bugs.kde.org/show_bug.cgi?id=162270

Allen Winter  changed:

   What|Removed |Added

 CC||win...@kde.org

--- Comment #2 from Allen Winter  ---
for the 21.12 release I  added printing the location in parenthesis after the
summary:  eg. "Party time (my friend's house)"

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

[kpat] [Bug 445273] Solver declares a solvable Freecell game unsolvable

2021-11-11 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=445273

Albert Astals Cid  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |WORKSFORME

--- Comment #8 from Albert Astals Cid  ---
Ok, i guess your version is too old.

Anyhow, now loading that game, i get "Kings only" as a setting, and then the
solver is correct, you can't win the game because you can't do the 10 of spades
movement.

My guess is in old versions we had not properly synced what you could do with
what the solver thought you could do.

I am closing this, please reopen the  issue if you find in such situation
again.

Also if you're running a remotely recent operating system you may want to
install KPat from https://flathub.org/apps/details/org.kde.kpat which will give
you a newer version.

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

[kpat] [Bug 445273] Solver declares a solvable Freecell game unsolvable

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445273

--- Comment #7 from l...@kseiler.de ---
No, I don't have this setting. See the screenshot I just attached.

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

[Breeze] [Bug 418864] tray icon request gajim

2021-11-11 Thread andreas_k
https://bugs.kde.org/show_bug.cgi?id=418864

andreas_k  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #9 from andreas_k  ---
I'm sorry but gajim has an inbuild icon theme for the different status, so it's
not possible to use the icons from the breeze-icon repository in the system
tray.

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

[kpat] [Bug 445273] Solver declares a solvable Freecell game unsolvable

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445273

--- Comment #6 from l...@kseiler.de ---
Created attachment 143468
  --> https://bugs.kde.org/attachment.cgi?id=143468=edit
menu bar

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

[kpat] [Bug 445273] Solver declares a solvable Freecell game unsolvable

2021-11-11 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=445273

--- Comment #5 from Albert Astals Cid  ---
You don't have this?

https://i.imgur.com/tijCGxM.png

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

[okular] [Bug 444168] zooming wrong

2021-11-11 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=444168

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #19 from Albert Astals Cid  ---
We read your emails be it any state the bug is, I'm just particularly ignoring
them.

It's not my problem that you're using a distribution that doesn't ship updated
versions.

We fixed the bug (or we think we did) in 21.08.3, now if the new version is not
available because of the decisions you have taken in regards to which operating
system you use, that's a you problem, not a me problem. If you're really in a
huge need to get this fixed you can always try to compile Okular yourself or
change to a distribution that ships an updated Okular
https://okular.kde.org/download/

Stop marking this bug as not fixed (unless you update to something that is
actually Okular 21.08.3 or newer and still have the problem)

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

[kpat] [Bug 445273] Solver declares a solvable Freecell game unsolvable

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445273

--- Comment #4 from l...@kseiler.de ---
I don't seem to have an "Empty Stack fill" setting in my game - at least I
can't find it. 
But the game allows me to place any card on an empty stack (in this case the 10
of spades).

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

[kinfocenter] [Bug 400079] kinfocenter should show more information about your hardware from `dmidecode`

2021-11-11 Thread Brian Kaye
https://bugs.kde.org/show_bug.cgi?id=400079

--- Comment #9 from Brian Kaye  ---
On my system (Fedora 34) the directory " /sys/devices/virtual/dmi/id" contains
much of the system information that might be displayed in kinfocenter. Some
items like the serial number need authorization. The  little script below
displays the contents. Some info is probably not useful. Other systems my have
the info in different locations. So maybe there is no need to run the dmidecode
command. There is a "power" subdirectory but I am not sure of the contents yet.

DIR="/sys/devices/virtual/dmi/id/*"
for i in ${DIR}; do  if ! [ -d $i ]; then echo -ne ${i} "\t"; cat ${i}; fi;
done

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

[kpat] [Bug 445273] Solver declares a solvable Freecell game unsolvable

2021-11-11 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=445273

Albert Astals Cid  changed:

   What|Removed |Added

 Resolution|--- |WAITINGFORINFO
 CC||aa...@kde.org
 Status|REPORTED|NEEDSINFO

--- Comment #3 from Albert Astals Cid  ---
Can you confirm that when you load this game, in Settings -> Empty Stack fill
it says "Kings only"?

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

[okular] [Bug 444168] zooming wrong

2021-11-11 Thread Amnon
https://bugs.kde.org/show_bug.cgi?id=444168

--- Comment #18 from Amnon  ---

And once more, flatpack and snap do not work for me -- snap offers OKULAR
20.12.3 and ...

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

[digikam] [Bug 445349] Feature request: Small additional preview pane at 100% zoom, in sidebar of preview window

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445349

--- Comment #4 from caulier.gil...@gmail.com ---
And look also the railway available on the bottom / right corner of the canvas.
A bottom is available to enable the view, where you can select the 100% area
visible from the image. 

GIlles Caulier

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

[okular] [Bug 444168] zooming wrong

2021-11-11 Thread Amnon
https://bugs.kde.org/show_bug.cgi?id=444168

Amnon  changed:

   What|Removed |Added

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

--- Comment #17 from Amnon  ---
ps. I can't send you an email and you don't seem to read comments on closed
tickets. So I have no choice but to repoen it...

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

[okular] [Bug 444168] zooming wrong

2021-11-11 Thread Amnon
https://bugs.kde.org/show_bug.cgi?id=444168

--- Comment #16 from Amnon  ---

Can you please tell me how to install that very new version?
I have tried searching up and down and came up with nothing. 
(In fact, as I asked a few days ago, telling me which lines to fix in which
config file is enough)

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

[digikam] [Bug 445349] Feature request: Small additional preview pane at 100% zoom, in sidebar of preview window

2021-11-11 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=445349

Maik Qualmann  changed:

   What|Removed |Added

   Severity|normal  |wishlist

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

[digikam] [Bug 445349] Feature request: Small additional preview pane at 100% zoom, in sidebar of preview window

2021-11-11 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=445349

--- Comment #3 from Maik Qualmann  ---
I agree with Gilles, a section can be selected in the 100% image preview view.
The section is retained when the image is changed and the sharpness can be
assessed perfectly. I don't see where the little image in the right sidebar
should be an advantage.

Maik

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

[calligracommon] [Bug 445343] Calligra snap installation issues

2021-11-11 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=445343

Albert Astals Cid  changed:

   What|Removed |Added

  Component|general |general
 CC||j...@jriddell.org,
   ||sit...@kde.org
Product|www.kde.org |calligracommon
   Assignee|kde-...@kde.org |calligra-bugs-n...@kde.org

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

[okular] [Bug 444168] zooming wrong

2021-11-11 Thread Albert Astals Cid
https://bugs.kde.org/show_bug.cgi?id=444168

Albert Astals Cid  changed:

   What|Removed |Added

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

--- Comment #15 from Albert Astals Cid  ---
You have *not* installed the latest version as anyone comparing version numbers
can see 21.08.1 is smaller than 21.08.3 so *obviously* you don't have a version
where the issue is fixed.

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

[Breeze] [Bug 418864] tray icon request gajim

2021-11-11 Thread andreas_k
https://bugs.kde.org/show_bug.cgi?id=418864

--- Comment #8 from andreas_k  ---
Needed icons are at
https://github.com/gajim/gajim/tree/master/gajim/data/icons/hicolor

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

[digikam] [Bug 416744] Changes are not saved after deleting face rectangle from picture

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=416744

--- Comment #16 from spam-recei...@web.de ---
This is scheduled for 7.4.0. When will the release be available?

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

[valgrind] [Bug 445354] New: arm64 backend: incorrect code emitted for doubleword CAS

2021-11-11 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=445354

Bug ID: 445354
   Summary: arm64 backend: incorrect code emitted for doubleword
CAS
   Product: valgrind
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: vex
  Assignee: jsew...@acm.org
  Reporter: jsew...@acm.org
CC: m...@klomp.org
  Target Milestone: ---

The sequence of instructions emitted by the arm64 backend for doubleword
compare-and-swap is incorrect.  This could lead to incorrect simulation of the
AArch8.1 atomic instructions (CASP, at least), and causes failures in the
upcoming fix for v8.0 support for LD{,A}XP/ST{,L}XP in bug 444399.  In the
worst case it can cause segfaulting in the generated code, because it could
jump backwards unexpectedly far.

The problem is the sequence emitted for ARM64in_CASP:

* the jump offsets are incorrect, both for `bne out` (x 2) and `cbnz w1, loop`.

* using w1 to hold the success indication of the stxp instruction trashes the
  previous value in x1.  But the value in x1 is an output of ARM64in_CASP,
  hence one of the two output registers is corrupted.  That confuses any code
  downstream that want to inspect those values to find out if the transaction
  succeeded or not.

The fixes are to

* fix the branch offsets

* use a different register to hold the stxp success indication.  w3 is a
  convenient check.

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

[okular] [Bug 444168] zooming wrong

2021-11-11 Thread Amnon
https://bugs.kde.org/show_bug.cgi?id=444168

Amnon  changed:

   What|Removed |Added

Version|20.12.3 |21.08.1

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

[okular] [Bug 444168] zooming wrong

2021-11-11 Thread Amnon
https://bugs.kde.org/show_bug.cgi?id=444168

Amnon  changed:

   What|Removed |Added

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

--- Comment #14 from Amnon  ---

I have just installed the latest: 
 Okular Version 21.08.1

from:
https://ubuntu.pkgs.org/21.04/kubuntu-backports-amd64/okular_21.08.1-1ubuntu3~ubuntu21.04~ppa1_amd64.deb.html

yet the zoom is still wrong...

Please help.

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

[okular] [Bug 444168] zooming wrong

2021-11-11 Thread Amnon
https://bugs.kde.org/show_bug.cgi?id=444168

--- Comment #13 from Amnon  ---
Created attachment 143467
  --> https://bugs.kde.org/attachment.cgi?id=143467=edit
new screenshot

showing wrong zoom after installing latest version of okular

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

[kwin] [Bug 442362] xwayland: Add local user to xhost

2021-11-11 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=442362

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #4 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin/-/merge_requests/1646

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

[plasmashell] [Bug 435989] Plasma Wayland crashes in QtWaylandClient::QWaylandWindow::handleScreensChanged() when using combined (direct) HDMI and DisplayLink outputs

2021-11-11 Thread Mikaela Szekely
https://bugs.kde.org/show_bug.cgi?id=435989

Mikaela Szekely  changed:

   What|Removed |Added

 CC||mikaela.szek...@qyriad.me

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

[plasmashell] [Bug 445344] High RAM memory consumption

2021-11-11 Thread Mikaela Szekely
https://bugs.kde.org/show_bug.cgi?id=445344

Mikaela Szekely  changed:

   What|Removed |Added

 CC||mikaela.szek...@qyriad.me

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

[Breeze] [Bug 422880] Inkscape Icons are not consistent with dark breeze theme

2021-11-11 Thread medin
https://bugs.kde.org/show_bug.cgi?id=422880

--- Comment #5 from medin  ---
Inkscape suffered from both native UI and icons themes that make the interface
looks so much big with incomplete icons, so the idea (like how Gimp solved the
same problem) was to implement their own theme for small laptop screens which
called "Minwaita", and also the ability to create customized icons based on
user selected colors which is called "Multicolor" icon theme.

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

[krita] [Bug 445329] Krita crashes when closing the "Configure Krita" dialogue with the "X" close icon

2021-11-11 Thread Ahab Greybeard
https://bugs.kde.org/show_bug.cgi?id=445329

--- Comment #3 from Ahab Greybeard  ---
On that Configure Krita window, I don't have the 'maximise' and 'minimise'
buttons, only the 'X' button.
This may be related to my OS and/or desktop manager, I don't know.

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

[Breeze] [Bug 422880] Inkscape Icons are not consistent with dark breeze theme

2021-11-11 Thread medin
https://bugs.kde.org/show_bug.cgi?id=422880

--- Comment #4 from medin  ---
(In reply to andreas_k from comment #3)

If you want to see the problem, in Preferences>Interface>Themeing, select "Use
System icons" as icon theme and disable "Disable symbolic icons". And you
should use KDE desktop not GNOME to see clearly the exact behavior.

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

[krita] [Bug 445329] Krita crashes when closing the "Configure Krita" dialogue with the "X" close icon

2021-11-11 Thread Timo Gurr
https://bugs.kde.org/show_bug.cgi?id=445329

--- Comment #2 from Timo Gurr  ---
Created attachment 143466
  --> https://bugs.kde.org/attachment.cgi?id=143466=edit
krita_segfault.png

Attaching screenshot to illustrate / make clear which button I'm referring to.

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

[plasmashell] [Bug 438839] Wayland - turning monitor off and back on causes plasmashell to make invalid xdgshell request and crash

2021-11-11 Thread miku84
https://bugs.kde.org/show_bug.cgi?id=438839

--- Comment #46 from miku84  ---
(In reply to Leyenda from comment #45)
> Kde neon testing edition
> frameworks 5.88
> kde plasma 5.23.3
> qt 5.15.3
> 
> With Plasma 5.23.3, when I turn off and on my screen, now desktop survives,
> al panel stay in place and working (they were gone before), although kde or
> qt apps opened (I'm not sure, apps like dolphin or system settings) remain
> open but they become non-responsive and grey and need to be closed.
> 
> But its a step forward.

Yes, for example clementine playpack freezes after screen comes back. It feels
to me like the panel is not the old one, but it is a new one created when there
is no panel (see the panel drawing animation, it starts the animation later,
the screen is the first).

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

[krita] [Bug 445350] Convert to selection mask remove my backup layer, making the editing process really unsafe

2021-11-11 Thread Ahab Greybeard
https://bugs.kde.org/show_bug.cgi?id=445350

--- Comment #3 from Ahab Greybeard  ---
Yes, the Clone layer is converted to a selection mask and applied to the
original Background layer.
This does not alter the contents of the Background layer.

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

[lattedock] [Bug 444984] Latte dock autohides on an empty desktop even though "autohide" isn't enabled, "dodge active" enabled only

2021-11-11 Thread Kalzi
https://bugs.kde.org/show_bug.cgi?id=444984

--- Comment #7 from Kalzi  ---
(In reply to Michail Vourlakos from comment #6)
> Are you sure you are using Latte 0.10.3?
> If you run latte-dock -v in command prompt what version does it show?

Yes, I'm sure. I have 0.10.3 installed.

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

[krita] [Bug 445350] Convert to selection mask remove my backup layer, making the editing process really unsafe

2021-11-11 Thread Hoang Duy Tran
https://bugs.kde.org/show_bug.cgi?id=445350

--- Comment #2 from Hoang Duy Tran  ---
I just redo it with 'CLONING' and the result is identical

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

[plasmashell] [Bug 445353] small icons in systray

2021-11-11 Thread Guido
https://bugs.kde.org/show_bug.cgi?id=445353

Guido  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |INTENTIONAL

--- Comment #1 from Guido  ---
ok, solved, there was a "margin separator"

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

[krita] [Bug 445350] Convert to selection mask remove my backup layer, making the editing process really unsafe

2021-11-11 Thread Ahab Greybeard
https://bugs.kde.org/show_bug.cgi?id=445350

Ahab Greybeard  changed:

   What|Removed |Added

 CC||ahab.greybe...@hotmail.co.u
   ||k

--- Comment #1 from Ahab Greybeard  ---
Note: You didn't clone the Backround layer, you Duplicated it.
When you convert a layer to a selection mask, it's converted to a mask and
applied to the layer below, as a selection mask.

So, it was applied to the original Background layer that you'd made invisible
and locked.

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

[plasmashell] [Bug 445353] New: small icons in systray

2021-11-11 Thread Guido
https://bugs.kde.org/show_bug.cgi?id=445353

Bug ID: 445353
   Summary: small icons in systray
   Product: plasmashell
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: guido.iod...@gmail.com
CC: mate...@gmail.com
  Target Milestone: 1.0

Created attachment 143465
  --> https://bugs.kde.org/attachment.cgi?id=143465=edit
systray

I had big icons in systray before I reset plasmashell... I tried in the config
dialog but has only small or adaptive size

iconSize=... workaround doesn't work 

I checked also
/usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/config/main.xml

and the property isn't present.

How i can have bigger icons in the tray as before the reset?

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

[kwin] [Bug 445115] kwin under wayland drops frames when mousing across window edges

2021-11-11 Thread Michael Marley
https://bugs.kde.org/show_bug.cgi?id=445115

--- Comment #1 from Michael Marley  ---
Some further investigation reveals that this bug affects Broadwell GPUs but
does not affect Skylake or Coffeelake.  I haven't been able to test Haswell
yet.  The latency-vs.-smoothness control has no effect.

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

[kwin] [Bug 443224] Kwin puts titlebar wrongly in some java apps

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=443224

--- Comment #9 from lucbo...@gmail.com ---
Yes, both Dbeaver and Eclipse are centered and don't show the title bar

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

[krita] [Bug 445329] Krita crashes when closing the "Configure Krita" dialogue with the "X" close icon

2021-11-11 Thread Ahab Greybeard
https://bugs.kde.org/show_bug.cgi?id=445329

Ahab Greybeard  changed:

   What|Removed |Added

 CC||ahab.greybe...@hotmail.co.u
   ||k

--- Comment #1 from Ahab Greybeard  ---
I don't see a crash or any entries in the log or terminal when trying this on a
Debian 10 system running appimages from 4.4.8 onwards.

Note re. Step 4: I don't have a 'minimise' or 'maximise' along the top, only
the 'X' button.

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

[digikam] [Bug 445345] When creating a new tag with a comma, the tag is truncated

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445345

caulier.gil...@gmail.com changed:

   What|Removed |Added

 CC||caulier.gil...@gmail.com

--- Comment #3 from caulier.gil...@gmail.com ---
I second Maik here...

Gilles Caulier

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

[digikam] [Bug 445349] Feature request: Small additional preview pane at 100% zoom, in sidebar of preview window

2021-11-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445349

caulier.gil...@gmail.com changed:

   What|Removed |Added

Version|unspecified |7.4.0
 CC||caulier.gil...@gmail.com

--- Comment #2 from caulier.gil...@gmail.com ---
Preview canvas can be already switched to 100% with a button from status bar,
near zoom slider. It's not enough ?

Gilles Caulier

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

[krita] [Bug 445336] Resource system doesn't purge resources whose storage has been removed

2021-11-11 Thread amyspark
https://bugs.kde.org/show_bug.cgi?id=445336

amyspark  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED
   Assignee|krita-bugs-n...@kde.org |a...@amyspark.me

--- Comment #2 from amyspark  ---
No, in d032070993d45cca216c7f8c319eac65e4253aea it seems you forgot to account
for storage deletion. It was also overlooked on
abe84bc3c63a290e79525a0021fa11b4cb05926, so every time one tried to add a tag
whose storage was deleted, the uniqueness constraints would fail.

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

[lattedock] [Bug 444984] Latte dock autohides on an empty desktop even though "autohide" isn't enabled, "dodge active" enabled only

2021-11-11 Thread Michail Vourlakos
https://bugs.kde.org/show_bug.cgi?id=444984

--- Comment #6 from Michail Vourlakos  ---
Are you sure you are using Latte 0.10.3?
If you run latte-dock -v in command prompt what version does it show?

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

[Breeze] [Bug 422880] Inkscape Icons are not consistent with dark breeze theme

2021-11-11 Thread andreas_k
https://bugs.kde.org/show_bug.cgi?id=422880

--- Comment #3 from andreas_k  ---
can please someone else check the bug report. I have Inkscape 1.1 flatpack and
there are predefined icons which are nice, but the inkscape flatpack package
didn't use breeze-icons from system theme.

Inkscape 1.1.1 (3bf5ae0d25, 2021-09-20)
GLib version: 2.70.0
GTK version:  3.24.30
glibmm version:   2.66.1
gtkmm version:3.24.5
libxml2 version:  2.9.12
libxslt version:  1.1.34
Cairo version:1.16.0
Pango version:1.48.10
HarfBuzz version: 3.0.0
Poppler version:  21.09.0
OS version:   GNOME 41 (Flatpak runtime)

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

  1   2   3   >