[Akonadi] [Bug 472335] New: Slow startup to desktop at login

[Thomas Mitterfellner]

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

Bug ID: 472335
   Summary: Slow startup to desktop at login
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: tho...@mitterfellner.at
CC: c...@carlschwan.eu
  Target Milestone: ---

It seems that there has been a regression with desktop startup after login at
some point. This has been really fast, almost immediate, maybe 2-4 s after
entering my credentials but now it takes ~15 s for the desktop to show.
The version I'm using is 5.27.4 on openSUSE Leap 15.5.

This duration is not shorter when I just log out and log in again.

Caveat: I am not sure this is due to akonadi but in my journalctl -b output I
get many akonadi messages over the course of 10 s (I pressed Enter on the login
screen at 19:40:01):

Jul 17 19:40:05 x akonadi_control[4223]: Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Jul 17 19:40:05 x akonadiserver[4238]: org.kde.pim.akonadiserver: Starting up
the Akonadi Server...
Jul 17 19:40:06 x kalendarac[4276]: akonadi.collectionattributetable   
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.collectionmimetyperelation 
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.collectionpimitemrelation  
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.collectiontable
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.flagtable  
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.mimetypetable  
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.parttable  
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.parttypetable  
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.pimitemflagrelation
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.pimitemtable   
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.pimitemtagrelation 
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.relationtable  
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.relationtypetable  
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.resourcetable  
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.schemaversiontable 
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.tagattributetable  
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.tagremoteidresourcerelationtable   
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.tagtable   
   OK
Jul 17 19:40:06 x kalendarac[4276]: akonadi.tagtypetable   
   OK
Jul 17 19:40:06 x akonadiserver[4238]: org.kde.pim.akonadiserver: Running DB
initializer
Jul 17 19:40:06 x akonadiserver[4238]: org.kde.pim.akonadiserver: DB
initializer done
Jul 17 19:40:06 x akonadiserver[4238]: Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Jul 17 19:40:06 x akonadi_control[4223]: org.kde.pim.akonadicontrol: Akonadi
server is now operational.
Jul 17 19:40:06 x akonadiserver[4238]: org.kde.pim.akonadiserver: New
notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7fbcb4003f20) )
Jul 17 19:40:06 x akonadiserver[4238]: org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7fbcb4003f20) identified as
"ETMCalendarMonitor - 94885386041040"
Jul 17 19:40:07 x akonadiserver[4238]: org.kde.pim.akonadiserver: New
notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7fbcb40555b0) )
Jul 17 19:40:07 x akonadiserver[4238]: org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7fbcb40555b0) identified as
"AgentBaseChangeRecorder - 94373361138464"
Jul 17 19:40:08 x akonadiserver[4238]: org.kde.pim.akonadiserver: New
notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7fbcb4015440) )
Jul 17 19:40:08 x akonadiserver[4238]: org.kde.pim.akonadiserver: New
notification connection (registered as
Akonadi::Server::NotificationSubscriber(0x7fbcb405a4b0) )
Jul 17 19:40:08 x akonadiserver[4238]: org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7fbcb4015440) identified as
"AgentBaseChangeRecorder - 94813301524080"
Jul 17 19:40:08 x akonadiserver[4238]: org.kde.pim.akonadiserver: Subscriber
Akonadi::Server::NotificationSubscriber(0x7fbcb405a4b0) identified as
"AgentBaseChangeRecorder - 94820412118752"
Jul 17 19:40:08 x akonadiserver[4238]: org.kde.pim.akonadiserver: New
notification connection (registered as

[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock

[Thomas Mitterfellner]

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

--- Comment #69 from Thomas Mitterfellner  ---
I had misunderstood the sudo udevadm trigger -s input the whole time! I thought
that the settings were *lost* when I issue this command while the *correct*
settings are operational. But indeed, when I do sudo udevadm trigger -s input
*while the wrong settings* are in place, I get the expected settings!

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

[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock

[Thomas Mitterfellner]

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

--- Comment #43 from Thomas Mitterfellner  ---
(In reply to Nate Graham from comment #29)
> Those of you experiencing the issue, does it also happen if you run `sudo
> udevadm trigger -s input`? We have another bug about that (Bug 414559) and I
> wonder if something changed recently to trigger that condition more often.

No, when I do "sudo udevadm trigger -s input", my touchpad settings work just
fine, so I'm not sure whether https://bugs.kde.org/show_bug.cgi?id=450528 is
actually a duplicate of the issues dealt with here..
Is there anything I could do to help elucidating what the problem is in my case
(as described in the other bug report, my problem is that touchpad settings are
kind of "un-applied" after a restart although they are kind of remembered, so I
have to manually go to the touchpad settings and hit apply there, after which
everything works as expected).

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

[systemsettings] [Bug 450528] New: Touchpad settings are not remembered after restart

[Thomas Mitterfellner]

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

Bug ID: 450528
   Summary: Touchpad settings are not remembered after restart
   Product: systemsettings
   Version: 5.24.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_touchpad
  Assignee: plasma-b...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

Each time I reboot, my touchpad settings (synaptics driver) are lost. The
configuration module shows "Active settings don't match saved settings." just
as described here: https://github.com/clearlinux/distribution/issues/8743

When I hit Apply, my settings are there again, but I wonder why they are lost
in the first place.

Possible duplicate but from earlier version:
https://bugs.kde.org/show_bug.cgi?id=342861

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

[kwin] [Bug 354964] any 3d effect causes flashing artifacts

[Thomas Mitterfellner]

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

--- Comment #21 from Thomas Mitterfellner  ---
I haven't experienced this problem in a long time. So from my point of view
this issue can be closed.

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

[kdeconnect] [Bug 435385] New: Crash when also running BubbleUPnP

[Thomas Mitterfellner]

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

Bug ID: 435385
   Summary: Crash when also running BubbleUPnP
   Product: kdeconnect
   Version: unspecified
  Platform: Android
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

The kdeconnect android app (version 1.16) keeps crashing immediately when the
BubbleUPnP app
(https://play.google.com/store/apps/details?id=com.bubblesoft.android.bubbleupnp)
is also active. When I close BubbleUPnP, I can open the kdeconnect app again.

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

[frameworks-kio] [Bug 359027] Add possibility to dereference symlinks during copy/move jobs

[Thomas Mitterfellner]

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

Thomas Mitterfellner  changed:

   What|Removed |Added

 CC||tho...@mitterfellner.at

--- Comment #5 from Thomas Mitterfellner  ---
Is there any chance this gets implemented? I frequently need to copy the
targets of symlinks to a FAT file system which doesn't support symlinks, of
course. I have to do it via command line; cp automatically does the right thing
– even better than adding the option (IMO, others might disagree) would be if
krusader could detect the target file system does not support symlinks somehow
and dereference the symlinks automatically, just like cp seems to do.

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

[plasmashell] [Bug 433680] Popup closes if cursor is hovering over "Mount and Open" button for a newly- attached device at the moment when the applet icon returns to normal

[Thomas Mitterfellner]

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

--- Comment #7 from Thomas Mitterfellner  ---
I do not even need to hover the dialog for it to close, but it seems that _I
have to move the mouse_. I could not get the dialog close automatically when I
did a task switch without using Alt+Tab, i.e. only using clicks, even when I
moved the mouse after the dialog opened. But when I did Alt+Tab,
unplugged/replugged and kept the mouse unmoved, the dialog stayed opened
_until_ I moved the mouse.

Disclaimer: all these observations might be me trying to search for a pattern
in random data, but at least for the few (10-15) times I tried it now, my
predictions _seemed_ to hold.

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

[plasmashell] [Bug 433680] Keep popped-up notifications open when mouse hovers over it

[Thomas Mitterfellner]

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

--- Comment #4 from Thomas Mitterfellner  ---
Created attachment 136214
  --> https://bugs.kde.org/attachment.cgi?id=136214=edit
Screencast

I tried to show the behavior in a video (see attachment)

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

[plasmashell] [Bug 433680] Keep popped-up notifications open when mouse hovers over it

[Thomas Mitterfellner]

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

--- Comment #3 from Thomas Mitterfellner  ---
OK, I've tried this now a few times and it seems that it does not always behave
that way, only under some circumstances as it seems. But what I can report is
that it definitely says Disks & Devices at the top.

My observations:
1. Plug in disk
2. The device notifier symbol in the systray turns into a blue exclamation mark
(just like a notification) while the Disks & Devices dialog appears
3. I hover the mouse over it (even with the focus highlight for some of the
items in the dialog being activated) but after some 5 seconds the exclamation
mark changes back to the original icon again with the dialog disappearing
4. Unplug-replug
5. The dialog appears, this time I click into it, and it stays
7. Focus to browser via mouse, the dialog disappears (good)
6. Unplug-replug
7. The dialog appears it stays again without any interaction from my side
8. Task switch via Alt+Tab
9. Unplug-replug
10. Dialog shows but disappears again after some time

To sum up: having given focus to the dialog seems to initiate a state that has
it staying open while a task switch using Alt+Tab seems to reset the behavior
to a disappearing dialog.

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

[plasmashell] [Bug 433680] New: Keep popped-up notifications open when mouse hovers over it

[Thomas Mitterfellner]

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

Bug ID: 433680
   Summary: Keep popped-up notifications open when mouse hovers
over it
   Product: plasmashell
   Version: 5.21.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Notifications
  Assignee: k...@privat.broulik.de
  Reporter: tho...@mitterfellner.at
CC: plasma-b...@kde.org
  Target Milestone: 1.0

It would be helpful if a freshly popped-up notification could stay open as long
as the mouse hovers over it (cf.
https://bugs.kde.org/show_bug.cgi?id=188831#c5).

The reason I'm requesting this is mainly because of the device notifier popup
that you see when you connect a new device: it closes after the specified
amount of time (default is 5 s) while I'm trying to interact with it, e.g.
searching for the desired device's mount button.

Maybe it's possible to pause the "closing countdown" while the mouse is
hovering over the fresh popup and continue when the mouse leaves the popup
again (or reset the counter while hovering)? I hope the SDK makes it possible
to implement this behavior. Maybe in the options a checkbox near the "Hide
after" input field like a checkbox "Pause countdown during mouse-over" could
also be added?

I know the workaround is to quickly click somewhere into the popup to give it
the focus, but, you know, click-economy (o;

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

[kdeconnect] [Bug 425134] Call notification still shows when call has been answered

[Thomas Mitterfellner]

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

--- Comment #2 from Thomas Mitterfellner  ---
The "Receive notifications" (from the other device an display them on Android)
plugin is disabled in the app.

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

[kdenlive] [Bug 427334] New: Composite effects get lost upon timeline zone extraction

[Thomas Mitterfellner]

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

Bug ID: 427334
   Summary: Composite effects get lost upon timeline zone
extraction
   Product: kdenlive
   Version: 20.04.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

SUMMARY
I have a project with several video/audio tracks from which I want to delete a
zone using the timeline zone extraction. Now two of the video tracks contain
composite effects but these get lost upon extraction (hitting Shift-X). It was
quite some effort to get those compositing effects for the tracks right, so it
would be nice if the compositing effects could be preserved when extracting the
zone, i.e. if their length could be cut by the length of the extracted zone
(with all the keyframing data _outside_ of the extracted zone preserved).

I managed to restore the composite effects after the timeline zone extraction
by copying them to the clipboard and to some text documents and then re-insert
them manually to the respective tracks and re-position them, but I think the
workflow  would be easier if the GUI could do that automatically.

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

[kdeconnect] [Bug 425134] New: Call notification still shows when call has been answered

[Thomas Mitterfellner]

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

Bug ID: 425134
   Summary: Call notification still shows when call has been
answered
   Product: kdeconnect
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

SUMMARY
When I get a call on my android phone, the call notification with the option to
mute the call appears on the desktop, which is fine but it stays there even
when the call has been answered on the phone which does not make sense as I
cannot mute the call anymore anyway.

kdeconnect version: 20.04.2


STEPS TO REPRODUCE
1. Call the paired android device
2. Answer call on phone

OBSERVED RESULT
The call notification with the option to mute the call appears on the desktop,
and it stays there even when the call has been answered on the phone. 

EXPECTED RESULT
The dialog should be synchronized with the phone as it does not apply anymore
once I answer or reject the call on the phone.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: OpenSuse 15.2
(available in About System)
KDE Plasma Version: 5.19.3
KDE Frameworks Version: 5.72.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION

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

[plasmashell] [Bug 416732] Plasma crashes at startup after libraries update

[Thomas Mitterfellner]

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

Thomas Mitterfellner  changed:

   What|Removed |Added

 CC||tho...@mitterfellner.at

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

[plasmashell] [Bug 416732] Plasma crashes at startup after libraries update

[Thomas Mitterfellner]

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

--- Comment #7 from Thomas Mitterfellner  ---
Created attachment 125577
  --> https://bugs.kde.org/attachment.cgi?id=125577=edit
New crash information added by DrKonqi

plasmashell (5.17.90) using Qt 5.14.0

- What I was doing when the application crashed:
Happens at each plasma startup since I've done an update.

-- Backtrace (Reduced):
#6  0x7f8cd010c050 in QLocale::toString(QDateTime const&,
QLocale::FormatType) const (this=0x559d320e31f0, dateTime=...,
format=QLocale::LongFormat) at text/qlocale.cpp:2186
#7  0x7f8cd25f6d62 in
QQmlDateExtension::method_toLocaleString(QV4::FunctionObject const*, QV4::Value
const*, QV4::Value const*, int) (b=, thisObject=,
argv=0x7f8cb9da3550, argc=2) at
/usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/qml/qml/qqmllocale.cpp:126
#8  0x7f8cd24a2dd3 in QV4::FunctionObject::call(QV4::Value const*,
QV4::Value const*, int) const (argc=, argv=,
thisObject=, this=) at
/usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/include/QtQml/5.14.0/QtQml/private/../../../../../src/qml/jsruntime/qv4functionobject_p.h:202
#9  0x7f8cd24a2dd3 in QV4::Moth::VME::interpret(QV4::CppStackFrame*,
QV4::ExecutionEngine*, char const*) (frame=0x7ffcc1760160,
engine=0x559d2f0d4ee0, code=0x7f8c82c52ee2 "H\002\022") at
/usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:744
#10 0x7f8cd24a6146 in QV4::Moth::VME::exec(QV4::CppStackFrame*,
QV4::ExecutionEngine*) (frame=frame@entry=0x7ffcc1760160,
engine=engine@entry=0x559d2f0d4ee0) at
/usr/src/debug/libqt5-qtdeclarative-5.14.0-lp151.3.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:453

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

[kdeconnect] [Bug 409046] New: Each message notification yields 6 plasma notification popups

[Thomas Mitterfellner]

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

Bug ID: 409046
   Summary: Each message notification yields 6 plasma notification
popups
   Product: kdeconnect
   Version: 1.3.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: messaging-application
  Assignee: si...@ergotech.com
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

SUMMARY
Per SMS message I receive on my phone, I get 6 identical plasma popup
notifications from the kdeconnect telephony plugin 

STEPS TO REPRODUCE
1. Receive an SMS (e.g. an TAN from ebanking

OBSERVED RESULT
Two stacked popup notifications with the same content (the SMS containing the
TAN). I can click on the x of the lower popup 6 times until all the identical
popups are gone. In the "new notifications" icon, however, only one message is
displayed as being new.

EXPECTED RESULT
Only one popup notification should be displayed.

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.16.1
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.4

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

[kdeconnect] [Bug 409043] New: Enhancement: mark message as read from notification dialog

[Thomas Mitterfellner]

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

Bug ID: 409043
   Summary: Enhancement: mark message as read from notification
dialog
   Product: kdeconnect
   Version: 1.8
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: plasmoid
  Assignee: albertv...@gmail.com
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

When I get plasma notifications that a message has arrived on my phone from
kdeconnect, I'd like to be able to mark the message as read from the
notification popup (just like I would be in the android notification popup).
This would be useful e.g. if I make a couple of ebanking transactions and get a
TAN via SMS for each transaction. I read number in the notification popup,
enter it in the browser and then the message is irrelevant, so I would not have
to go through those obsolete messages on my phone anymore.

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

[kdenlive] [Bug 406985] Zooming/scrolling with touchpad is too sensitive

[Thomas Mitterfellner]

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

--- Comment #1 from Thomas Mitterfellner  ---
Patch submitted for review: https://phabricator.kde.org/D20873

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

[kdenlive] [Bug 406985] New: Zooming/scrolling with touchpad is too sensitive

[Thomas Mitterfellner]

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

Bug ID: 406985
   Summary: Zooming/scrolling with touchpad is too sensitive
   Product: kdenlive
   Version: 18.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: User Interface
  Assignee: j...@kdenlive.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

Just like in a couple of other applications, scrolling/zooming the track window
using the touchpad is too sensitive, e.g. CTRL+two-finger-scrolling for zooming
to a certain defined magnification is almost impossible. In the other
applications this was solved by accumulating a delta until a defined value is
surpassed before scrolling.

See:
okular: https://bugs.kde.org/show_bug.cgi?id=377128
(https://cgit.kde.org/okular.git/commit/?id=7a50ce0edfc9be8bd23441e52a4f3a0c60f7e60f)

gwenview: https://bugs.kde.org/show_bug.cgi?id=378584
(https://cgit.kde.org/gwenview.git/commit/?id=c4a84dad6292b9c7918bec8d7ed33114d3758730)

krita: https://bugs.kde.org/show_bug.cgi?id=378586
(https://cgit.kde.org/krita.git/commit/?id=390f8d72a559575e7179287acc6d238c7b36a3bb)

KDE Plasma Version: 5.15.3

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

[kwin] [Bug 400038] Problems w/KDE Desktop when waking from sleep with proprietary Nvidia Drivers Installed

[Thomas Mitterfellner]

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

--- Comment #5 from Thomas Mitterfellner  ---
Created attachment 119030
  --> https://bugs.kde.org/attachment.cgi?id=119030=edit
New crash information added by DrKonqi

kwin_x11 (5.15.3) using Qt 5.12.2

- What I was doing when the application crashed:
Wake from suspend; while the laptop was suspended, some time in the night, I
heard the sound that indicates that the power is disconnected (the cable may
have slipped out). After waking from suspend, the login screen looked somewhat
like the backdrop had been exchanged for a stretched chessboard.

-- Backtrace (Reduced):
#6  0x7fd95f61b36f in _mm_stream_si128(long long __vector(2)*, long long
__vector(2)) (__B=..., __A=0x7fd92d3bd260) at
/usr/lib64/gcc/x86_64-suse-linux/7/include/emmintrin.h:1473
#7  0x7fd95f61b36f in KWin::WindowQuadList::makeInterleavedArrays(unsigned
int, KWin::GLVertex2D*, QMatrix4x4 const&) const
(this=this@entry=0x7e5abb70, type=type@entry=7,
vertices=vertices@entry=0x7fd92d3bd260, textureMatrix=...) at
/usr/src/debug/kwin5-5.15.3-lp150.287.3.x86_64/libkwineffects/kwineffects.cpp:1165
#8  0x7fd92dd1eaca in KWin::SceneOpenGL2Window::performPaint(int, QRegion,
KWin::WindowPaintData) (this=this@entry=0x556a8dd584b0, mask=mask@entry=2,
region=..., data=...) at
/usr/src/debug/kwin5-5.15.3-lp150.287.3.x86_64/plugins/scenes/opengl/scene_opengl.cpp:1438
#9  0x7fd92dd26183 in
KWin::SceneOpenGL2::performPaintWindow(KWin::EffectWindowImpl*, int, QRegion,
KWin::WindowPaintData&) (this=, w=,
mask=, region=..., data=...) at
/usr/src/debug/kwin5-5.15.3-lp150.287.3.x86_64/plugins/scenes/opengl/scene_opengl.cpp:1059
#10 0x7fd92dd262b7 in
KWin::SceneOpenGL2::finalDrawWindow(KWin::EffectWindowImpl*, int, QRegion,
KWin::WindowPaintData&) (this=this@entry=0x556a8dca72e0,
w=w@entry=0x556a8dd4b550, mask=mask@entry=2, region=..., data=...) at
/usr/src/debug/kwin5-5.15.3-lp150.287.3.x86_64/plugins/scenes/opengl/scene_opengl.cpp:1041

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

[kwin] [Bug 400038] Problems w/KDE Desktop when waking from sleep with proprietary Nvidia Drivers Installed

[Thomas Mitterfellner]

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

Thomas Mitterfellner  changed:

   What|Removed |Added

 CC||tho...@mitterfellner.at

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

[kio-extras] [Bug 403813] New: Copying and renaming via sftp:// fails

[Thomas Mitterfellner]

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

Bug ID: 403813
   Summary: Copying and renaming via sftp:// fails
   Product: kio-extras
   Version: 18.12.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: SFTP
  Assignee: plasma-b...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

I connect to my server via sftp://, e.g. from krusader. When I copy a file,
transferring the file works, but automatic renaming of the file on the server
from file.ext.part to file.ext fails with this error message:

"Could not rename partial file sftp://myuser@my.server/path/file.ext. Please
check permissions"

When I manually try to rename it, I get:

"Access denied to sftp://myuser@my.server/path/file.ext.;

The permissions are perfectly fine, which I see when I ssh to the server:

-rw-r--r-- 1 myuser myuser 115124 Jan 31 19:42 file.ext.part

I also cannot create or edit text files on the fly over sftp (was always
working).

Note that everything works as expected when I use fish:// from krusader, e.g.
to copy fish://myuser@my.server/path/file.ext. Strangely enough, this has been
working for YEARS without any problem with sftp:// after it had failed using
fish://; now it's the other way round.

STEPS TO REPRODUCE
1. connect via sftp:// from krusader
2. copy a file
3. 

OBSERVED RESULT
Error message and copied file with extension .part

EXPECTED RESULT
Copied file with original extension

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 399758] New: Panel not updated after resume from suspend

[Thomas Mitterfellner]

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

Bug ID: 399758
   Summary: Panel not updated after resume from suspend
   Product: plasmashell
   Version: 5.13.90
  Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: 1.0

Sometimes when I resume from suspend, the panel is not updated anymore. E.g.
the clock is stuck, hovering items in the task bar does not highlight them etc.
When I change anything in the composition settings and hit apply, the panel
functions normally again. Not sure if that's related but the "show mouse"
effect also has a visual glitch: the pngs used for the rotating rings are no
more transparent but have a white background. That, however, is not cured after
changing settings.
I'm using the proprietary nvidia driver (380.95).

Might be related to https://bugs.kde.org/show_bug.cgi?id=385607 ?

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

[kdeconnect] [Bug 399223] New: Contents of SD Card cannot be listed but subfolders' contents can

[Thomas Mitterfellner]

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

Bug ID: 399223
   Summary: Contents of SD Card cannot be listed but subfolders'
contents can
   Product: kdeconnect
   Version: 1.8
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: android-application
  Assignee: albertv...@gmail.com
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

SUMMARY
When I try to browse the contents of my sd card on my android phone from my
linux desktop (kdeconnect-kde version 1.3.0) I cannot see its contents. When I
do a 

ls /run/user/1000/aa321541a9e62340/storage/-

on the command line, I get an Operation not permitted.

When I enter the name of a know subfolder on the sd card I can see its
contents, however. Listing the contents of the sd card is possible without
problems when I manually connect to sshd (OpenSSH_7.8p1) manually started in a
Termux session. See also this stackexchange question:
https://android.stackexchange.com/questions/201886/how-can-i-list-the-contents-of-my-sd-card-over-ssh?noredirect=1#comment258421_201886
Could this be a permissions problem or a problem with the sshd version used by
the kdeconnect android app?  

STEPS TO REPRODUCE
1. Open device in Dolphin
2. Browse to SD card

OBSERVED RESULT
No content shown

EXPECTED RESULT
Contents of SD should be shown

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[KScreen] [Bug 395901] New: Setting gamma for individual screens does not work

[Thomas Mitterfellner]

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

Bug ID: 395901
   Summary: Setting gamma for individual screens does not work
   Product: KScreen
   Version: 5.13.1
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm
  Assignee: se...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

I have two screens set up: my laptop's screen and an external monitor connected
via HDMI. The "sync screens" checkbox is not checked, but strangely, the combo
box is greyed and only shows "Screen 1" despite the Display section of the
configuration module showing both monitors. Consequently, both screens are
affected when I drag the slider.

Am I misunderstanding what is written here:
https://docs.kde.org/trunk5/en/kde-workspace/kcontrol/kgamma5/index.html –
should it actually be possible to set the gamma for each display individually
when I use two screens with only one graphics card? Is there a difference
between a "screen", a "display" and a "monitor" in that context or are they
same? If that should actually work, what can I do to debug it (provide debug
info)?

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

[kdeconnect] [Bug 395452] New: Browsing: listing subdirectories of internal/external storage does not work

[Thomas Mitterfellner]

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

Bug ID: 395452
   Summary: Browsing: listing subdirectories of internal/external
storage does not work
   Product: kdeconnect
   Version: 1.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

When I browse my device (Motorola, Android 7) using Dolphin, I cannot see the
subdirectories neither the ones of the internal storage
(/run/user/1000/aa321541a9e62340/storage/emulated/0/) nor of the SD card
(/run/user/1000/aa321541a9e62340/storage/6365-6131/).
However, when I manually enter a subdirectory's name I know exists (e.g.
/run/user/1000/aa321541a9e62340/storage/6365-6131/Download/), I can see its
contents and browse its subdirectories without problems.

When I do an ls on one of the unbrowsable directories, I get:

ls: reading directory '/run/user/1000/aa321541a9e62340/storage/6365-6131':
Operation not permitted

The generic links to the pictures, both on internal and external storage, work
as they lead to subdirectories.

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Thomas Mitterfellner]

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

--- Comment #83 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
I just updated to 5.11.4 and want to confirm that the crash when closing the
Virtualbox settings dialog does not happen anymore. Thanks for the fix!

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

[systemsettings] [Bug 385557] New: Crash when hovering over an item while typing into search field

[Thomas Mitterfellner]

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

Bug ID: 385557
   Summary: Crash when hovering over an item while typing into
search field
   Product: systemsettings
   Version: 5.11.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

The new Systemsettings dialog crashes when I do this:
1) Hover over "Workspace Theme" in the left column
2) Quickly type "cla" on the Keyboard 

Slowly typing c, l, a does not crash the program.

Backtrace:

#0  MenuItem::name (this=this@entry=0x0)
at /usr/src/debug/systemsettings-5.11.0/core/MenuItem.cpp:108
#1  0x7fc937ac2763 in ToolTipManager::generateToolTipLine
(this=this@entry=0x21d0760, 
item=item@entry=0x7ffdb0da51c0, toolTip=toolTip@entry=0x2974360,
iconSize=..., 
comment=comment@entry=true)
at
/usr/src/debug/systemsettings-5.11.0/sidebar/ToolTips/tooltipmanager.cpp:174
#2  0x7fc937ac2d52 in ToolTipManager::createTipContent
(this=this@entry=0x21d0760, 
item=...) at
/usr/src/debug/systemsettings-5.11.0/sidebar/ToolTips/tooltipmanager.cpp:146
#3  0x7fc937ac2ee0 in ToolTipManager::showToolTip (this=0x21d0760,
menuItem=...)
at
/usr/src/debug/systemsettings-5.11.0/sidebar/ToolTips/tooltipmanager.cpp:129
#4  0x7fc937ac2fe7 in ToolTipManager::prepareToolTip (this=)
at
/usr/src/debug/systemsettings-5.11.0/sidebar/ToolTips/tooltipmanager.cpp:120
#5  0x7fc95c236883 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib64/libQt5Core.so.5.9.2
#6  0x7fc95c243827 in QTimer::timeout(QTimer::QPrivateSignal) ()
   from /usr/lib64/libQt5Core.so.5.9.2
#7  0x7fc95c243b02 in QTimer::timerEvent(QTimerEvent*) ()
   from /usr/lib64/libQt5Core.so.5.9.2
#8  0x7fc95c2378f4 in QObject::event(QEvent*) () from
/usr/lib64/libQt5Core.so.5.9.2
#9  0x7fc95ddb5cbc in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
   from /usr/lib64/libQt5Widgets.so.5.9.2
#10 0x7fc95ddbca10 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib64/libQt5Widgets.so.5.9.2
#11 0x7fc95c20cd25 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
   from /usr/lib64/libQt5Core.so.5.9.2
#12 0x7fc95c25d44e in QTimerInfoList::activateTimers() ()
   from /usr/lib64/libQt5Core.so.5.9.2
#13 0x7fc95c25da91 in timerSourceDispatch(_GSource*, int (*)(void*), void*)
()
   from /usr/lib64/libQt5Core.so.5.9.2
#14 0x7fc955b4d134 in g_main_context_dispatch () from
/usr/lib64/libglib-2.0.so.0
#15 0x7fc955b4d388 in ?? () from /usr/lib64/libglib-2.0.so.0
#16 0x7fc955b4d42c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#17 0x7fc95c25ddbc in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5.9.2
#18 0x7fc95c20b01b in
QEventLoop::exec(QFlags) ()
   from /usr/lib64/libQt5Core.so.5.9.2
#19 0x7fc95c2135e4 in QCoreApplication::exec() () from
/usr/lib64/libQt5Core.so.5.9.2
#20 0x0040c238 in main (argc=1, argv=)
at /usr/src/debug/systemsettings-5.11.0/app/main.cpp:62

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

[kwin] [Bug 330954] ~100% CPU usage when switching to text console

[Thomas Mitterfellner]

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

--- Comment #39 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
For what it's worth: I cannot reproduce this problem with kwin 5.10.95 anymore.

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

[gwenview] [Bug 378584] Zooming with CTRL+Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

--- Comment #15 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
> Your username is mitterfellner with that, you should be able to reset your
> password in https://identity.kde.org/index.php?r=site/passwordReset

Thanks! Never would I have guessed that username (really!). I was now able to
log in to phabricator. Thanks also for pushing the commit to Applications!

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

[gwenview] [Bug 378584] Zooming with CTRL+Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

--- Comment #11 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
No chance. I cannot log in to phabricator. Could you (or someone who has
access) please submit it? (KDE identity doesn't let me in, I cannot register as
my address is already taken, I cannot reset my password)

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

[gwenview] [Bug 378584] Zooming with CTRL+Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

--- Comment #10 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Tested with mouse wheel. Works as expected as far as I can tell. I'll try to
submit it.

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

[gwenview] [Bug 378584] Zooming with CTRL+Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

--- Comment #8 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
I've adapted the okular solution and it seems to work as expected. Please
review/test the attached patch. I'd be happy to see the fix in the next
gwenview version.

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

[gwenview] [Bug 378584] Zooming with CTRL+Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

--- Comment #7 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Created attachment 107764
  --> https://bugs.kde.org/attachment.cgi?id=107764=edit
Patch to fix ctrl-scroll behavior via touchpad

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

[gwenview] [Bug 378584] Zooming with CTRL+Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

--- Comment #4 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Well, only kind of. Did you have a look at the bug report I linked? The problem
is not really the increment. It is that it is almost impossible to select a
particular increment. Zooming in 100% steps is not optimum, but I'd be ok, if I
could reliably CRTL-Zoom there using the touchpad. That is not possible. The
increment would probably have to be 0.1%-1% to be somewhat usable.

So I beg you: please have a look at the linked okular bug report and check the
solution presented there. Or, alternatively, compare the krita bug report at
https://bugs.kde.org/show_bug.cgi?id=378586 - they also fixed it already.

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

[krita] [Bug 378586] Zooming with Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

--- Comment #2 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Unfortunately, I'm not into the details of scrolling event handling. All I know
is that is seems to work e.g. in scribus but doesn't e.g. in gwenview. I don't
know whether they have special code treating the scrolling event in scribus,
but from the other bug report it seems they've added some special code to
okular.
Anyway, I agree that if it's possible to fix it upstream, it should be done
there, but I wouldn't know what exactly to report there.

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

[Powerdevil] [Bug 378976] New: Crash after resume from suspend

[Thomas Mitterfellner]

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

Bug ID: 378976
   Summary: Crash after resume from suspend
   Product: Powerdevil
   Version: 5.9.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-de...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

I'm not 100% sure why it happened, all that I know is that I had the my system
suspended for quite some time and maybe the battery was drained. When I
resumed, I saw a crash symbol in the system tray and shortly after that
plasmashell also crashed.

Backtrace:

#0  0x7f7c858f28d7 in __GI_raise (sig=11) at
../sysdeps/unix/sysv/linux/raise.c:55
#1  0x7f7c876e8b14 in KCrash::defaultCrashHandler(int) () at
/usr/lib64/libKF5Crash.so.5
#2  0x7f7c858f2950 in  () at /lib64/libc-2.22.so
#3  0x7f7c874b54d3 in QHash::erase(QHash::const_iterator) (this=this@entry=0x1fad390, it=it@entry=...)
at /usr/include/qt5/QtCore/qhash.h:857
#4  0x7f7c874ade5e in PowerDevil::Core::onResumingFromIdle() (i=...,
this=0x1fad390)
at /usr/include/qt5/QtCore/qset.h:197
#5  0x7f7c874ade5e in PowerDevil::Core::onResumingFromIdle() (i=...,
this=0x1fad390)
at /usr/include/qt5/QtCore/qset.h:193
#6  0x7f7c874ade5e in PowerDevil::Core::onResumingFromIdle()
(this=this@entry=0x1fad310)
at /usr/src/debug/powerdevil-5.9.4/daemon/powerdevilcore.cpp:798
#7  0x7f7c874b0218 in PowerDevil::Core::loadProfile(bool)
(this=this@entry=0x1fad310, force=force@entry=false) at
/usr/src/debug/powerdevil-5.9.4/daemon/powerdevilcore.cpp:346
#8  0x7f7c874b3cb8 in
PowerDevil::Core::onAcAdapterStateChanged(PowerDevil::BackendInterface::AcAdapterState)
(this=0x1fad310, state=PowerDevil::BackendInterface::Plugged)
at /usr/src/debug/powerdevil-5.9.4/daemon/powerdevilcore.cpp:624
#9  0x7f7c874cf15b in PowerDevil::Core::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=, _c=,
_id=, _a=)
at
/usr/src/debug/powerdevil-5.9.4/build/daemon/powerdevilcore_automoc.dir/moc_powerdevilcore_SR3RJSZTCRXVIY.cpp:226
#10 0x7f7c862780d5 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib64/libQt5Core.so.5.8.0
#11 0x7f7c874ce06e in
PowerDevil::BackendInterface::acAdapterStateChanged(PowerDevil::BackendInterface::AcAdapterState)
(this=this@entry=0x1fdef30,
_t1=_t1@entry=PowerDevil::BackendInterface::Plugged)
at
/usr/src/debug/powerdevil-5.9.4/build/daemon/powerdevilcore_automoc.dir/moc_powerdevilback_I25NWGJZD7ADF4.cpp:250
#12 0x7f7c874ab0bb in
PowerDevil::BackendInterface::setAcAdapterState(PowerDevil::BackendInterface::AcAdapterState)
(this=this@entry=0x1fdef30,
state=state@entry=PowerDevil::BackendInterface::Plugged)
at
/usr/src/debug/powerdevil-5.9.4/daemon/powerdevilbackendinterface.cpp:142
#13 0x7f7c701d4251 in PowerDevilUPowerBackend::slotPropertyChanged()
(this=0x1fdef30)
at
/usr/src/debug/powerdevil-5.9.4/daemon/backends/upower/powerdevilupowerbackend.cpp:640
#14 0x7f7c701d4399 in PowerDevilUPowerBackend::onPropertiesChanged(QString
const&, QMap const&, QStringList const&) (this=, ifaceName=..., changedProps=..., invalidatedProps=...)
at
/usr/src/debug/powerdevil-5.9.4/daemon/backends/upower/powerdevilupowerbackend.cpp:652
#15 0x7f7c701e3814 in PowerDevilUPowerBackend::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) (_o=_o@entry=0x1fdef30,
_c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=12,
_a=_a@entry=0x7ffc9b0f0810)
at
/usr/src/debug/powerdevil-5.9.4/build/daemon/backends/powerdevilupowerbackend_automoc.dir/moc_powerdevilupow_HYK6MXZV2XCI6O.cpp:144
#16 0x7f7c701e3ee3 in
PowerDevilUPowerBackend::qt_metacall(QMetaObject::Call, int, void**)
(this=0x1fdef30, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x7ffc9b0f0810)
at
/usr/src/debug/powerdevil-5.9.4/build/daemon/backends/powerdevilupowerbackend_automoc.dir/moc_powerdevilupow_HYK6MXZV2XCI6O.cpp:205
#17 0x7f7c866c249b in  () at /usr/lib64/libQt5DBus.so.5
#18 0x7f7c86279886 in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5.8.0
#19 0x7f7c8625030c in QCoreApplication::notify(QObject*, QEvent*) () at
/usr/lib64/libQt5Core.so.5.8.0
#20 0x7f7c86250245 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
()
at /usr/lib64/libQt5Core.so.5.8.0
#21 0x7f7c862522a3 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) ()
at /usr/lib64/libQt5Core.so.5.8.0
#22 0x7f7c8629f043 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) ()
at /usr/lib64/libQt5Core.so.5.8.0
#23 0x7f7c7fcbc134 in g_main_context_dispatch () at
/usr/lib64/libglib-2.0.so.0
#24 0x7f7c7fcbc388 in  () at /usr/lib64/libglib-2.0.so.0
#25 0x7f7c7fcbc42c in g_main_context_iteration () at

[krita] [Bug 378586] New: Zooming with Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

Bug ID: 378586
   Summary: Zooming with Two-finger-scrolling is too sensitive
   Product: krita
   Version: 3.1.2
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

Version: 3.1.2
When I zoom in and out of an image using Two-finger-scrolling on the touchpad,
this goes way too fast/much too sensitive, so it is almost impossible to get to
a desired magnification.

Please have a look at https://bugs.kde.org/show_bug.cgi?id=377128 as this one
seems to be almost the same problem.

(I reported a similar problem for gwenview:
https://bugs.kde.org/show_bug.cgi?id=378584)

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

[gwenview] [Bug 378584] Zooming with CTRL+Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

--- Comment #1 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
I forgot: this is for version 16.08.2, KDE Frameworks 5.32.0, Qt 5.8.0 (built
against 5.8.0), the xcb windowing system

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

[gwenview] [Bug 378584] New: Zooming with CTRL+Two-finger-scrolling is too sensitive

[Thomas Mitterfellner]

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

Bug ID: 378584
   Summary: Zooming with CTRL+Two-finger-scrolling is too
sensitive
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: tho...@mitterfellner.at
CC: myr...@kde.org
  Target Milestone: ---

When I zoom in and out of an image using CTRL+Two-finger-scrolling on the
touchpad, this goes way too fast/much too sensitive, so it is almost impossible
to get to a desired magnification.

Please have a look at https://bugs.kde.org/show_bug.cgi?id=377128 as this one
seems to be almost the same problem.

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

[Touchpad-KCM] [Bug 378583] New: Touchpad settings do not have an effect on qt applications

[Thomas Mitterfellner]

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

Bug ID: 378583
   Summary: Touchpad settings do not have an effect on qt
applications
   Product: Touchpad-KCM
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: plasma-applet
  Assignee: rajeeshknamb...@gmail.com
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

This affects version 5.9.4 (I cannot select this as versions numbers are only
available up to 5.5.5).

When I change the touchpad two-finger scrolling distance setting in the
configuration dialog, hit Apply and test the settings in the Testing area, they
do not seem to have any effect (same for settings like Reverse scrolling).
However, the values are written correctly to touchpadrc and I can see the
effect of the setting immediately when I test it in Firefox or a qt Application
like Scribus. Only after I close the System Settings and open them again, the
changed settings do show an effect.

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Thomas Mitterfellner]

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

--- Comment #46 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Leap 42.2 but with the latest packages from the kdf5/qt5 repos
http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_42.2/
and http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_42.2/
I did
zypper ar
http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_42.2/
kdf5
zypper ar
http://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Leap_42.2/ qt5
and then
zypper dup --from kdf5 --from qt5

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Thomas Mitterfellner]

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

--- Comment #43 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
First off, although we already established that, it does not depend on intel
graphics as the crash happens here with an nvidia GPU.

"it only happens on older systems or on systems under stress at that time. The
quite often mentioned VMware and virtual box could verify the stress situation:
resources are passed to the VM and taken away from the main system."

My system is indeed older but the "under stress at that time" is definitely not
true. My system is almost idle, the virtual machine isn't even running and the
crash reliably happens when I close the configuration dialog of virtualbox-qt
5.1.8 (openSUSE, qt 5.7.1).

I ran xev > kwin_crash_xev.txt while triggering the crash; since I don't what's
of interest to you, I'll attach the whole output.

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

[kwin] [Bug 363224] Kwin crashes from time to time (this time using Virtual Machine Manager)

[Thomas Mitterfellner]

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

--- Comment #42 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Created attachment 103591
  --> https://bugs.kde.org/attachment.cgi?id=103591=edit
xev output

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

[plasmashell] [Bug 374390] Icons overflow boundaries of Folder View widget

[Thomas Mitterfellner]

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

--- Comment #4 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
I updated my distribution now to openSUSE Leap 42.2 and now the folder widget
is OK again. From my point of view, this one can be closed.

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

[plasmashell] [Bug 374713] iconSize in plasma-org.kde.plasma.desktop-appletsrc is disregarded

[Thomas Mitterfellner]

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

--- Comment #2 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Yes, you are absolutely right; I added iconSize=3 under
[Containments][60][General] then it worked. 

Sorry for the false alarm.

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

[plasmashell] [Bug 374713] New: iconSize in plasma-org.kde.plasma.desktop-appletsrc is disregarded

[Thomas Mitterfellner]

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

Bug ID: 374713
   Summary: iconSize in plasma-org.kde.plasma.desktop-appletsrc is
disregarded
   Product: plasmashell
   Version: 5.8.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: 1.0

Created attachment 103274
  --> https://bugs.kde.org/attachment.cgi?id=103274=edit
Config file

Changing the value of iconSize in plasma-org.kde.plasma.desktop-appletsrc does
not seem to have an effect. When I change the default value in
/usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/config/main.xml
however, the icon sizes change appropriately.
Note that I've also tried this with fresh config file (mine seems to have
gotten cluttered for some reason).

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

[kwin] [Bug 374649] New: KWin crashes when closing the virtualbox settings dialog

[Thomas Mitterfellner]

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

Bug ID: 374649
   Summary: KWin crashes when closing the virtualbox settings
dialog
   Product: kwin
   Version: 5.8.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

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

When I close the settings dialog of virtualbox-qt 5.0.26, KWin crashes.

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

[plasmashell] [Bug 374390] Icons overflow boundaries of Folder View widget

[Thomas Mitterfellner]

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

--- Comment #2 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Created attachment 103143
  --> https://bugs.kde.org/attachment.cgi?id=103143=edit
Config file

Added my plasma-org.kde.plasma.desktop-appletsrc.

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

[frameworks-kwidgetsaddons] [Bug 374390] New: Icons overflow boundaries of Folder View widget

[Thomas Mitterfellner]

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

Bug ID: 374390
   Summary: Icons overflow boundaries of Folder View widget
   Product: frameworks-kwidgetsaddons
   Version: 5.29.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: cf...@kde.org
  Reporter: tho...@mitterfellner.at
CC: kdelibs-b...@kde.org
  Target Milestone: ---

Created attachment 103112
  --> https://bugs.kde.org/attachment.cgi?id=103112=edit
Video showing the problem

The icons show in the Folder View widgets extend to the desktop space beyond
the boundaries of the widget, e.g. say the folder widget's boundaries are from
coordinates X1,Y1 to X2,Y2, the icons even show in the space at coordinates >X2
and >Y2. During resizing of the widgets, however, the icons only show within
the borders of the widget. When releasing the resize icon, the icons show again
in the area they shouldn't be (see attached video).

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

[plasmashell] [Bug 373865] plasmashell crashes on usb disconnect

[Thomas Mitterfellner]

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

--- Comment #2 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Is there anything I can do to help track down the cause of this?
Should I submit the data or a bug report for those kwin crashes (I saved data
for one of them)? 
[I'm a bit reluctant to report bugs which I cannot reproduce (I tried but
couldn't find anything that triggers either of those crashes reliably), but I'm
getting crashes frequently (kvmserver, plasmashell, kwin) recently, seemingly
in connection with my dual monitor setup; or maybe it's just that I'm doing
different stuff when I have two monitors connected.]

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

[plasmashell] [Bug 373865] New: plasmashell crashes on usb disconnect

[Thomas Mitterfellner]

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

Bug ID: 373865
   Summary: plasmashell crashes on usb disconnect
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: tho...@mitterfellner.at
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.1.36-41-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
I have a dual monitor setup where the external monitor is connected to the
laptop and has an usb hub to which mouse and keyboard are connected. When I
disconnect that hub from the laptop, sometimes I get this crash. The laptop
screen is turned off, if that matters; I'm writing this because I also had
other crashes in connection with the monitor (kwin crashed twice, also not 100%
reproducible) when I turned the monitor off (with gwenview in fullscreen mode).

The crash can be reproduced sometimes.

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

Thread 11 (Thread 0x7fd9a70f0700 (LWP 16808)):
#0  0x7fda7e12a03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x26e9070) at
thread/qwaitcondition_unix.cpp:143
#2  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x272e720, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fda82e8875b in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fda82e8a5d5 in  () at /usr/lib64/libQt5Quick.so.5
#5  0x7fda7f01c7f9 in QThreadPrivate::start(void*) (arg=0x272e6a0) at
thread/qthread_unix.cpp:368
#6  0x7fda7e1260a4 in start_thread () at /lib64/libpthread.so.0
#7  0x7fda7e92502d in clone () at /lib64/libc.so.6

Thread 10 (Thread 0x7fd9adc1f700 (LWP 16807)):
#0  0x7fda7e12a03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x24cf820) at
thread/qwaitcondition_unix.cpp:143
#2  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0x24cf2b0, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fda82e8875b in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fda82e8a5d5 in  () at /usr/lib64/libQt5Quick.so.5
#5  0x7fda7f01c7f9 in QThreadPrivate::start(void*) (arg=0x24cf230) at
thread/qthread_unix.cpp:368
#6  0x7fda7e1260a4 in start_thread () at /lib64/libpthread.so.0
#7  0x7fda7e92502d in clone () at /lib64/libc.so.6

Thread 9 (Thread 0x7fd9af011700 (LWP 16802)):
#0  0x7fda7e91cbfd in poll () at /lib64/libc.so.6
#1  0x7fda799f8e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fda799f8f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fda7f2229eb in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x7fd9a80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7fda7f1d22db in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fd9af010dd0, flags=..., flags@entry=...) at
kernel/qeventloop.cpp:212
#5  0x7fda7f017fca in QThread::exec() (this=) at
thread/qthread.cpp:507
#6  0x7fd9b0439cf7 in KCupsConnection::run() () at
/usr/lib64/libkcupslib.so
#7  0x7fda7f01c7f9 in QThreadPrivate::start(void*) (arg=0x23d79a0) at
thread/qthread_unix.cpp:368
#8  0x7fda7e1260a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fda7e92502d in clone () at /lib64/libc.so.6

Thread 8 (Thread 0x7fd9c60d7700 (LWP 16783)):
#0  0x7fda7e12a03f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(time=18446744073709551615, this=0x1258fc0) at
thread/qwaitcondition_unix.cpp:143
#2  0x7fda7f01d46b in QWaitCondition::wait(QMutex*, unsigned long)
(this=, mutex=0xd86b10, time=18446744073709551615) at
thread/qwaitcondition_unix.cpp:215
#3  0x7fda82e8875b in  () at /usr/lib64/libQt5Quick.so.5
#4  0x7fda82e8a5d5 in  () at /usr/lib64/libQt5Quick.so.5
#5  0x7fda7f01c7f9 in QThreadPrivate::start(void*) (arg=0xd86a90) at
thread/qthread_unix.cpp:368
#6  0x7fda7e1260a4 in start_thread () at /lib64/libpthread.so.0
#7  0x7fda7e92502d in clone () at /lib64/libc.so.6

Thread 7 (Thread 0x7fd9c6ff7700 (LWP 16782)):
#0  0x7fda7e91cbfd in poll () at /lib64/libc.so.6
#1  0x7fda799f8e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fda799f8f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  

[kwin] [Bug 372264] New: Full desktop zoom shows unzoomed translucent artifacts for translucent elements

[Thomas Mitterfellner]

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

Bug ID: 372264
   Summary: Full desktop zoom shows unzoomed translucent artifacts
for translucent elements
   Product: kwin
   Version: 5.8.3
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tho...@mitterfellner.at
  Target Milestone: ---

Created attachment 102150
  --> https://bugs.kde.org/attachment.cgi?id=102150=edit
Screenshot showing the artifact

The full desktop zoom (Zoom Factor: 2.0, Mouse Pointer: scale, Mouse Tracking:
proportional) shows semi-transparent artifacts seemingly caused by not scaling
and panning graphical the translucency part of elements like the task panel,
tool tips, or popups (non-classical windows, like the calender or the volume
info that pops up when I hit the volume keys),.
Thus, e.g. with a task panel at the bottom, upon zooming, one gets a
semi-transparent stripe spanning the bottom of the screen having the height of
the panel. The height of that translucent stripe stays the same with increasing
magnification, i.e. does not scale proportionally.
When I hover over some items in the systray, I get translucent rectangles the
size the pop-up would have been had I not zoomed. These don't move, i.e. stay
at the position of the unzoomed element even when panning.

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

[plasmashell] [Bug 364541] Icons in system tray popup are too small

[Thomas Mitterfellner]

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

--- Comment #6 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
I found here:
https://forum.kde.org/viewtopic.php?f=289=131736=c2949ae23a5898dc5b401abd4977014a=30#p365350
that this can actually be configured now (not obvious, but anyway).
In

~/.config/plasma-org.kde.plasma.desktop-appletsrc

I added a line

itenSize=2 

under the section

[Containments][19][General]

(It was not present in my case). The number in the [] might be different in
your case.

>From my point of view, this could be closed or resolved as a duplicate of
https://bugs.kde.org/show_bug.cgi?id=364431.

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

[plasmashell] [Bug 364541] Icons in system tray popup are too small

[Thomas Mitterfellner]

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

Thomas Mitterfellner <tho...@mitterfellner.at> changed:

   What|Removed |Added

 CC||tho...@mitterfellner.at

--- Comment #5 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Created attachment 102148
  --> https://bugs.kde.org/attachment.cgi?id=102148=edit
Systray screenshot

Indeed, it is very hard to identify the tiny icons for me as I am visually
impaired (in KDE 4, the readability was much better). From an accessibility
point of view, it would be highly desirable if there was an option to increase
their size, or rather decrease the whitespace, i.e. padding/margin/border size.

Is there a possibility to do this manually, i.e. by changing some configuration
file?

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

[frameworks-kinit] [Bug 360162] Segfault at startup (just after login)

[Thomas Mitterfellner via KDE Bugzilla]

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

--- Comment #1 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Created attachment 97713
  --> https://bugs.kde.org/attachment.cgi?id=97713=edit
Backtrace of the crash

This is on plasma 5.5.5, the debug info package is called
kinit-debuginfo-5.19.0-85.1.x86_64.

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

[systemsettings] [Bug 360108] Angle for circular scrolling on touchpad interpreted differently than in kde4 (conversion deg > rad missing)

[Thomas Mitterfellner via KDE Bugzilla]

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

--- Comment #2 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
I figured out a workaround now. I put a setscroll.desktop file into
~/.config/autostart which calls a script which executes 
synclient VertScrollDelta=106
synclient HorizScrollDelta=106

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

[systemsettings] [Bug 360108] Angle for circular scrolling on touchpad interpreted differently than in kde4 (conversion deg > rad missing)

[Thomas Mitterfellner via KDE Bugzilla]

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

--- Comment #1 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
I just found that this is a duplicate of
https://bugs.kde.org/show_bug.cgi?id=359460. I could not work around this by
putting a script which calls synclient VertScrollDelta=106 into
.config/plasma-workspace/env. I would be really glad if this could be fixed
quickly as it makes two-finger and circular scrolling almost
unusable/unconfigurable.

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

[systemsettings] [Bug 360110] New: Maximum (Horiz|Vert)ScrollDelta too low or no conversion taking place

[Thomas Mitterfellner via KDE Bugzilla]

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

Bug ID: 360110
   Summary: Maximum (Horiz|Vert)ScrollDelta too low or no
conversion taking place
   Product: systemsettings
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_mouse
  Assignee: unassigned-b...@kde.org
  Reporter: tho...@mitterfellner.at
CC: unassigned-b...@kde.org

In the touchpad configuration, the maximum Delta for two finger scrolling which
can be set is 10 mm. But this results in an insanely sensitive two-finger
scrolling. In kde4, I had values of 106 (whatever the unit?) for both,
horizontal and vertical scroll delta.
It seems that no conversion of the mm to whatever unit synclient requires is
done when writing the config. This is possibly related to
https://bugs.kde.org/show_bug.cgi?id=360108. It seems to be a general thing
that the units show in the GUI are not converted for use in synclient.

Reproducible: Always

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

[systemsettings] [Bug 360108] New: Angle for circular scrolling on touchpad interpreted differently than in kde4 (conversion deg > rad missing)

[Thomas Mitterfellner via KDE Bugzilla]

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

Bug ID: 360108
   Summary: Angle for circular scrolling on touchpad interpreted
differently than in kde4 (conversion deg > rad
missing)
   Product: systemsettings
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_mouse
  Assignee: unassigned-b...@kde.org
  Reporter: tho...@mitterfellner.at
CC: unassigned-b...@kde.org

The angle for circular scrolling is shown to be in degrees in the control
module (and is written as-is to the synclient), however, the mouse-over text
says it's in radians.
This results in virtually non-working circular scrolling when I enter the
values I was used to from kde4. E.g. I had 5.76° there (quite sensitive), but
when I set this in plasma 5, I had to make a lot of turns for the scrolling to
move a tiny bit.
So essentially, the conversion between degree and radian is missing.

Reproducible: Always

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

[kwin] [Bug 359586] Effects dialog crashes when clicking the 'movie icon'

[Thomas Mitterfellner via KDE Bugzilla]

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

--- Comment #7 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
I'm using openSUSE Leap 42.1 but I did a distribution upgrade from 13.2, so
maybe that's the reason for the mixed symbols. Unfortunately, I don't know what
I have to uninstall and whether it would actually be possible because of some
applications depending on kde4 libs still.

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

[kwin] [Bug 359586] Effects dialog crashes when clicking the 'movie icon'

[Thomas Mitterfellner via KDE Bugzilla]

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

--- Comment #2 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
That's the strange thing: I don't get this dialog offering me to make a
backtrace. I have the debuginfo/symbols of kwin installed and I tried to run it
from gdb, but the traceback I got (~50 levels; the longest traceback I had seen
so far) does not look very useful to me. Could you give me instructions on how
to get a useful backtrace (or was the gdb method OK?)?

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

[kwin] [Bug 359586] New: Effects dialog crashes when clicking the 'movie icon'

[Thomas Mitterfellner via KDE Bugzilla]

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

Bug ID: 359586
   Summary: Effects dialog crashes when clicking the 'movie icon'
   Product: kwin
   Version: 5.5.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tho...@mitterfellner.at

Running kcmshell5 kwineffects and clicking on one of the movie icons leads to a
segfault.
Unfortunately, I don't even know what that icon should do, supposedly a
preview?

Reproducible: Always

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

[kwin] [Bug 359583] Transparency of menu during invert effect does not match the one with invert effect off

[Thomas Mitterfellner via KDE Bugzilla]

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

--- Comment #3 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Indeed, disabling the contrast effect solves that problem. And yes, it's a full
screen inversion. But I sometimes also use the window inversion.

Thanks for the quick response!

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

[kwin] [Bug 359583] Transparency of menu during invert effect does not match the one with invert effect off

[Thomas Mitterfellner via KDE Bugzilla]

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

Thomas Mitterfellner <tho...@mitterfellner.at> changed:

   What|Removed |Added

 CC||tho...@mitterfellner.at

--- Comment #1 from Thomas Mitterfellner <tho...@mitterfellner.at> ---
Created attachment 97307
  --> https://bugs.kde.org/attachment.cgi?id=97307=edit
Picture demonstrating the problem

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

[kwin] [Bug 359583] New: Transparency of menu during invert effect does not match the one with invert effect off

[Thomas Mitterfellner via KDE Bugzilla]

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

Bug ID: 359583
   Summary: Transparency of menu during invert effect does not
match the one with invert effect off
   Product: kwin
   Version: 5.5.4
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: effects-various
  Assignee: kwin-bugs-n...@kde.org
  Reporter: tho...@mitterfellner.at

When I invert screen colors, the start menu has too high a transparency making
it hard to read if there's text behind it. Also, the entries on the panel
including the systray are barely readable due to lacking contrast. I'try to
attach a picture demonstrating that.

The interesting thing is: I *think* it wasn't like that from the start but I'm
not 100% sure. I think it became like this at some point when I was using the
Show Mouse effect. Unfortunately. I cannot confirm this as it seems to be
persistent also after rebooting (which is why I'm unsure whether it hasn't been
like that from the beginning).



Reproducible: Always




I added kwin support info here: https://paste.kde.org/pqim8h9pk

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