date:20210301

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

Bug ID: 433841
   Summary: Confusing shortcuts on right click on panel
   Product: plasmashell
   Version: 5.21.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: ddascalescu+...@gmail.com
  Target Milestone: 1.0

Created attachment 136313
  --> https://bugs.kde.org/attachment.cgi?id=136313&action=edit
Confusing shortcuts when editing the panel

I'm unclear about the shortcuts displayed when right clicking the panel:

* Configure Task Manager / Alt+D, S - brings up Alternative Widgets instead
* Add Widgets / Alt+D, A - works
* Edit Panel / Alt+D, Alt+S - brings up Alternative Widgets instead

Why the need for Alt+D anyway? Pressing just `S` or `A` does bring up the
Alternative Widgets and Add Widgets pages.

Another note: the accelerators aren't underlined until I press Alt. But they
*are* triggered before pressing Alt. For example, right clicking on the panel
and pressing 'C' does bring up the Task Manager Settings dialog.

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

[plasmashell] [Bug 433840] New: Panel appears on secondary screen after returning to X11 from Wayland

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

Bug ID: 433840
Summary: Panel appears on secondary screen after returning to
X11 from Wayland
Product: plasmashell
Version: 5.21.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Panel
Assignee: plasma-b...@kde.org
Reporter: ddascalescu+...@gmail.com
Target Milestone: 1.0

Created attachment 136312
--> https://bugs.kde.org/attachment.cgi?id=136312&action=edit
Screenshot of the dual-monitor setup

My laptop is connected to an external monitor, which I have set as the primary
screen. The taskbar (panel) was appearing correctly onto that screen, until (I
think) I tried out Wayland. Under Wayland, the panel appeared on the laptop. I
might have disconnected the laptop from the monitor; I don't recall precisely.
After learning that Wayland doesn't have the concept of a "primary screen" (to
the chagrin of many users[1]), I edited the panel and dragged it onto the
external monitor.

Due to numerous glitches in Wayland, I decided to go back to X11. I rebooted
and logged in under X11. Now the panel appears on the laptop, even though the
external monitor is set as primary. If I set the laptop as primary, the panel
moves onto the external monitor.

[1]:
https://www.reddit.com/r/kde/comments/k7wa2d/how_do_i_set_the_primary_monitor_on_kde_wayland/
https://www.reddit.com/r/kde/comments/ae8czw/plasma_wayland_works_great_but_how_do_i_set_a/
https://www.reddit.com/r/kde/comments/ak3gfa/primary_monitor_with_wayland/

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

[valgrind] [Bug 432801] Valgrind 3.16.1 reports a jump based on uninitialized memory somehow related to clang and signals

2021-03-01 Thread Eyal

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

--- Comment #14 from Eyal  ---
A possible solution in Valgrind:
https://github.com/eyal0/valgrind/commit/899ea491e358013579f87e443beff0a30c69e348

This improves Valgrind's check for definedness when doing 32x4 SIMD signed
greater than.  It solves the problem for the test case below.  If you can,
consider testing if it solves the problem for your original code.

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

[Breeze] [Bug 433839] New: Firefox browser showing wrong title bar button when maximized

2021-03-01 Thread Mohammed Sameer

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

Bug ID: 433839
   Summary: Firefox browser showing wrong title bar button when
maximized
   Product: Breeze
   Version: 5.21.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: gtk theme
  Assignee: uhh...@gmail.com
  Reporter: glifwen...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 136311
  --> https://bugs.kde.org/attachment.cgi?id=136311&action=edit
firefox maximized

SUMMARY
Firefox browser showing wrong title bar button for "restore down" action.

STEPS TO REPRODUCE
1. open firefox browser
2. disable title bar through "customize" option
3. maximize firefox window

OBSERVED RESULT
when maximized firefox is showing wrong title bar button for "restore down"
action.

EXPECTED RESULT
correct button shown for "restore down" action.

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.

[kscreenlocker] [Bug 408493] Desktop briefly visible before lock screen appears

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

k...@trummer.xyz changed:

   What|Removed |Added

 CC||k...@trummer.xyz

--- Comment #9 from k...@trummer.xyz ---
(In reply to Nate Graham from comment #5)
> Can anyone else confirm the same behavior?

It happens on amdgpu with kernel parameter "amdgpu.dc=0" set.
The default "amdgpu.dc=1" doesn't have the issue (but other problems).

Operating System: openSUSE Tumbleweed 20210223
KDE Plasma Version: 5.21.0
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2
Kernel Version: 5.10.16-1-default
OS Type: 64-bit
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: Radeon RX 570 Series

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

[digikam] [Bug 433822] DigiKam doesn't read extended (xattr) attributes

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

--- Comment #3 from Maik Qualmann  ---
If you only want to use Baloo, you can switch off reading of the rating tags in
the advanced metadata settings, then we will only read Baloo.

Maik

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

[systemsettings] [Bug 433721] System settings crashes when asked to clear activity data

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

--- Comment #1 from oled...@yahoo.com ---
Created attachment 136310
  --> https://bugs.kde.org/attachment.cgi?id=136310&action=edit
New crash information added by DrKonqi

systemsettings5 (5.21.1) using Qt 5.15.2

- What I was doing when the application crashed:

Clearing activity history from Workspace Behavior > Activities > Privacy

-- Backtrace (Reduced):
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#5  0x7f07b06c3859 in __GI_abort () at abort.c:79
[...]
#7  0x7f07ae7bd570 in _dbus_warn_check_failed () from
/lib/x86_64-linux-gnu/libdbus-1.so.3
#8  0x7f07ae7acde2 in dbus_message_new_method_call () from
/lib/x86_64-linux-gnu/libdbus-1.so.3
#9  0x7f07afbb7047 in q_dbus_message_new_method_call (method=0x55e359e6c418
"Introspect", interface=0x7f07a400ade8 "org.freedesktop.DBus.Introspectable",
path=0x7f07a400ad58 "/ActivityManager/Resources / Scoring", bus_name=) at qdbus_symbols_p.h:381

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

[systemsettings] [Bug 433721] System settings crashes when asked to clear activity data

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

oled...@yahoo.com changed:

   What|Removed |Added

 CC||oled...@yahoo.com

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

[digikam] [Bug 433822] DigiKam doesn't read extended (xattr) attributes

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

--- Comment #2 from Maik Qualmann  ---
We won't change this behavior either, Baloo is deactivated by default and we
actually wanted to remove it completely. Even if the stability has improved in
the current KF5 versions, Baloo has brought us many bug reports with crashes
over the years.

Maik

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

[digikam] [Bug 433822] DigiKam doesn't read extended (xattr) attributes

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

Maik Qualmann  changed:

   What|Removed |Added

 CC||metzping...@gmail.com

--- Comment #1 from Maik Qualmann  ---
Reading the Baloo information works without any problems. Just tested here.
However, Baloo has the lowest (last) priority. If digiKam finds a valid rating
in the metadata, it will be used, even if it is a zero rating.

Maik

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

[ksysguard] [Bug 433838] New: System monitor crashes after terminating a zombie Gwenview

2021-03-01 Thread Vince LaConte

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

Bug ID: 433838
   Summary: System monitor crashes after terminating a zombie
Gwenview
   Product: ksysguard
   Version: 5.19.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: vi...@id.iit.edu
CC: plasma-b...@kde.org
  Target Milestone: ---

Application: ksysguard (5.19.5)

Qt Version: 5.14.2
Frameworks Version: 5.74.0
Operating System: Linux 5.8.0-43-generic x86_64
Windowing system: X11
Distribution: Ubuntu 20.10

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

Gwenview has a history of crashing on my system (I keep using it because even
with multiple crashes per session it's a damn useful little app), and sometimes
fails to exit fully afterwards. When I use System Monitor to find and issue
either SIGTERM or SIGKILL -- often with a keyboard SHIFT-DEL -- a significant %
of the time, maybe 20-25% of the time, System Monitor crashes immediately after
successful termination of Gwenview. 

I believe one or two other apps have caused a similar ksysguard crash before,
but I failed to note which. I will pay more attention next time and submit
further info if warranted.

-- Backtrace:
Application: System Monitor (ksysguard), signal: Segmentation fault

[KCrash Handler]
#4  0x7fae41ec6d2d in operator==(QString const&, QString const&) (s1=...,
s2=...) at text/qstring.cpp:3383
#5  0x7fae42d96e79 in QLabel::setText(QString const&) (this=0x56234c0b6250,
text=...) at widgets/qlabel.cpp:287
#6  0x7fae43b039db in TopLevel::answerReceived(int, QList
const&) (this=0x56234c3a8990, id=, answerList=...) at
./gui/ksysguard.cpp:466
#7  0x7fae43846122 in KSGRD::SensorAgent::processAnswer(char const*, int)
(this=0x56234c3eed30, buf=, buflen=) at
./ksgrd/SensorAgent.cpp:91
#8  0x7fae4384c325 in KSGRD::SensorShellAgent::msgRcvd()
(this=0x56234c3eed30) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:208
#9  0x7fae4205a2e6 in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7ffd6961b450, r=0x56234c3eed30, this=0x56234c13a340) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#10 doActivate(QObject*, int, void**) (sender=0x56234c010620,
signal_index=15, argv=argv@entry=0x7ffd6961b450) at kernel/qobject.cpp:3870
#11 0x7fae42054068 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=, m=m@entry=0x7fae422adde0
, local_signal_index=local_signal_index@entry=6,
argv=argv@entry=0x7ffd6961b450) at kernel/qobject.cpp:3930
#12 0x7fae41f919c1 in
QProcess::readyReadStandardOutput(QProcess::QPrivateSignal) (this=, _t1=...) at .moc/moc_qprocess.cpp:367
#13 0x7fae41f9711d in
QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*)
(this=0x56234c134cc0, channel=0x56234c134dd0) at io/qprocess.cpp:1057
#14 0x7fae41f97675 in QProcessPrivate::_q_canReadStandardError()
(this=) at io/qprocess.cpp:1084
#15 QProcess::qt_static_metacall(QObject*, QMetaObject::Call, int, void**)
(_o=, _c=, _id=,
_a=0x7ffd6961b600) at .moc/moc_qprocess.cpp:210
#16 0x7fae4205a320 in doActivate(QObject*, int, void**)
(sender=0x56234c3fb550, signal_index=3, argv=argv@entry=0x7ffd6961b600) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:395
#17 0x7fae42054068 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) (sender=sender@entry=0x56234c3fb550, m=m@entry=0x7fae422b01c0
,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd6961b600)
at kernel/qobject.cpp:3930
#18 0x7fae4205d8b5 in QSocketNotifier::activated(int,
QSocketNotifier::QPrivateSignal) (this=this@entry=0x56234c3fb550,
_t1=, _t2=...) at .moc/moc_qsocketnotifier.cpp:141
#19 0x7fae4205dc51 in QSocketNotifier::event(QEvent*) (this=0x56234c3fb550,
e=0x7ffd6961b700) at kernel/qsocketnotifier.cpp:266
#20 0x7fae42c60013 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x56234c3fb550, e=0x7ffd6961b700) at
kernel/qapplication.cpp:3685
#21 0x7fae420241ca in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x56234c3fb550, event=0x7ffd6961b700) at
../../include/QtCore/../../src/corelib/kernel/qobject.h:153
#22 0x7fae4207c425 in socketNotifierSourceDispatch(GSource*, GSourceFunc,
gpointer) (source=0x56234b74b8b0) at kernel/qeventdispatcher_glib.cpp:107
#23 0x7fae396d74db in g_main_dispatch (context=0x7fae28005000) at
../../../glib/gmain.c:3325
#24 g_main_context_dispatch (context=0x7fae28005000) at
../../../glib/gmain.c:4016
#25 0x7fae396d7788 in g_main_context_iterate
(context=context@entry=0x7fae28005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4092
#26 0x7fae396d7853 in g_main_context_iteration (context=

[kwin] [Bug 430771] Turning off monitor in Wayland session causes strange fonts and missing icons on the panel

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

--- Comment #4 from jo...@disroot.org ---
Hi thought i'd give an update:

- KDE Plasma 5.21 doesn't appear to fix this issue.
- This issue only seems to happen on the APU of the AMD Athlon 200GE, cannot
reproduce on another AMD graphics card.
- Logging out and in or rebooting is the only way to temporarily fix the issue.

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

[digikam] [Bug 433732] Google Maps labelled "For development purposes only"

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

--- Comment #6 from Maik Qualmann  ---
Yes, our access to Google Maps already existed before 2018, until then it was
not necessary to store a payment option. Google requires that a payment option
is stored, credit card, PayPal or the like, even if there are no monthly
payments. Without a valid payment option, access to Google Maps will be
prevented.

Maik

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

[kwin] [Bug 433837] New: Can't copy text from Window matching Description

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

Bug ID: 433837
   Summary: Can't copy text from Window matching Description
   Product: kwin
   Version: 5.21.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: ddascalescu+...@gmail.com
  Target Milestone: ---

Created attachment 136309
  --> https://bugs.kde.org/attachment.cgi?id=136309&action=edit
I wanted to copy the exact "org.kde.plasmawindowed" text for another bug

SUMMARY


STEPS TO REPRODUCE
1. Invoke the window context menu (Alt+F3)
2. More Actions
3. Configure Special Window Settings
3. Try to copy the "Description" text

OBSERVED RESULT
Can select the text, but Ctrl+C or Ctrl+Insert doesn't copy it to the
clipboard, and there is no context menu to copy it


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.21.1.
KDE Frameworks Version: 5.79.0
Qt Version: 5.12.5

ADDITIONAL INFORMATION
Wayland

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

[kmenuedit] [Bug 433644] Calculator not present among Utilities

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

--- Comment #4 from Dan Dascalescu  ---
Created attachment 136308
  --> https://bugs.kde.org/attachment.cgi?id=136308&action=edit
What opens for 'Calculator'

No, KCalc is not installed. The running application is
`org.kde.plasmawindowed`.

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

[plasmashell] [Bug 433836] New: Windows don't remember position and sometimes size under Wayland

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

Bug ID: 433836
   Summary: Windows don't remember position and sometimes size
under Wayland
   Product: plasmashell
   Version: 5.21.1
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: ddascalescu+...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

I was happy to see that in Plasma 5.21, all windows remembered their size &
position. That was using X11.

Now under Wayland, I see that windows have started not to remember their
geometry:
* Dolphin always starts at 0, 0 in a small window
* Same for the KDE Menu Editor
* Same for Konsole
* Krusader remembers its size, but the position is again 0, 0
* PoliciKit KDE1 shows up in the bottom right corner

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.12.5

-- 
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

2021-03-01 Thread 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.

[drkonqi] [Bug 433835] New: Dolphin crash required gdb, which was already installed

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

Bug ID: 433835
   Summary: Dolphin crash required gdb, which was already
installed
   Product: drkonqi
   Version: 5.21.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: backtraceparsing
  Assignee: plasma-b...@kde.org
  Reporter: ddascalescu+...@gmail.com
  Target Milestone: ---

Created attachment 136307
  --> https://bugs.kde.org/attachment.cgi?id=136307&action=edit
Screenshot

Dolphin crashed while reading the DCIM directory from my phone. The crash
report window asked me to "install the debugger application" then click Reload.
`gdb` was already installed, and clicking Reload didn't have any effect after
running `sudo apt install gdb`.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.21.1
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Wayland

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

[digikam] [Bug 433732] Google Maps labelled "For development purposes only"

2021-03-01 Thread Kurpfaelzer

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

--- Comment #5 from Kurpfaelzer  ---
(In reply to Maik Qualmann from comment #2)
> From March 1st, the Google Maps map will work again.
> 
> Maik

Is there another issue with Google Maps or why does the label still appear?
Stephan

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

[kde] [Bug 433834] Neochat fails on any https to http redirects

2021-03-01 Thread idoitprone

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

--- Comment #1 from idoitprone  ---
Here is the steps to reproduce

STEPS TO REPRODUCE
1. Create a matrix instance that redirects between http and https
2. Create an account
3. Open neochat
4. Attempt to login with @username:domain.tld
5. Neochat throws errors

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

[kde] [Bug 433834] New: Neochat fails on any https to http redirects

2021-03-01 Thread idoitprone

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

Bug ID: 433834
   Summary: Neochat fails on any https to http redirects
   Product: kde
   Version: unspecified
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: monkeyboy...@yahoo.com
  Target Milestone: ---

SUMMARY

I have a self hosted webiste that redirects
https://domain.tld/.well-known/matrix/client ->
http://www.domain.tld/.well-known/matrix/client ->
https://www.domain.tld/.well-known/matrix/client ->
https://matrix.domain.tld/.well-client/matrix/client. May I ask why neochat
requires https to be used throughout the entire chain even if the final url has
https? 

curl -iL 'www.domain.tld/.well-known/matrix/client'
HTTP/1.1 301 Moved Permanently
Server: CloudFront
Date: Tue, 02 Mar 2021 04:13:55 GMT
Content-Type: text/html
Content-Length: 183
Connection: keep-alive
Location: https://www.domain.tld/.well-known/matrix/client
X-Cache: Redirect from cloudfront
Via: 1.1 d3f9b7e35643700c8f2c0d4716ce0574.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: LAX3-C4
X-Amz-Cf-Id: qbND_DjOc34c1opCxloPBqiR2jkMaHf5_ue8Qs1xHp9vlrj9lgCpw==

HTTP/2 301 
content-length: 0
location: http://matrix.domain.tld/.well-known/matrix/client
date: Tue, 02 Mar 2021 04:10:07 GMT
server: AmazonS3
x-cache: Hit from cloudfront
via: 1.1 12a5bcdb54ede5fbaec3241h3c798939.cloudfront.net (CloudFront)
x-amz-cf-pop: LAX3-C4
x-amz-cf-id: 7aILZVPleHe6ApG7NwibhAv_wrmyFDxKnZDHI9rNSKPnPG2rR8TQ==
age: 230

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Tue, 02 Mar 2021 04:13:56 GMT
Content-Type: text/html
Content-Length: 162
Connection: keep-alive
Location: https://matrix.domain.tld/.well-known/matrix/client

HTTP/2 200 
server: nginx
date: Tue, 02 Mar 2021 04:13:56 GMT
content-type: application/json
content-length: 632
last-modified: Sat, 28 Nov 2020 15:16:09 GMT
etag: "5fc269b9-278"
expires: Tue, 02 Mar 2021 08:13:56 GMT
cache-control: max-age=14400
access-control-allow-origin: *
accept-ranges: bytes

{
"m.homeserver": {
"base_url": "https://matrix.domain.tld";
}
,
"m.identity_server": {
"base_url": "https://matrix.domain.tld";
}
,
"m.integrations": {
"managers": [
{
"api_url":
"https://dimension.domain.tld/api/v1/scalar";,
"ui_url":
"https://dimension.domain.tld/element";
}
]
}
,
"io.element.jitsi": {
"preferredDomain": "jitsi.domain.tld"
},
"im.vector.riot.jitsi": {
"preferredDomain": "jitsi.domain.tld"
}
,
"io.element.e2ee": {
"default": true,
"secure_backup_required": false,
"secure_backup_setup_methods": []
},
"im.vector.riot.e2ee": {
"default": true
}
}

STEPS TO REPRODUCE
1. 
2. 
3. 

neochat 
Both point size and pixel size set. Using pixel size.
qrc:/qml/main.qml:254:5: QML Connections: Detected function "onRoomJoined" in
Connections element. This is probably intended to be a signal handler but no
signal of the target matches the name.
Both point size and pixel size set. Using pixel size.
qrc:/imports/NeoChat/Page/WelcomePage.qml:35:5: QML Connections: Implicitly
defined onFoo properties in Connections are deprecated. Use this syntax
instead: function onFoo() { ... }
qrc:/imports/NeoChat/Panel/RoomDrawer.qml:64: TypeError: Cannot read property
'isFavourite' of null
qrc:/imports/NeoChat/Panel/RoomDrawer.qml:67: TypeError: Cannot read property
'isFavourite' of null
qrc:/imports/NeoChat/Panel/RoomDrawer.qml:62: TypeError: Cannot read property
'isFavourite' of null
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.jobs: Sent GET https://domain.t/.well-known/matrix/client
quotient.jobs: "GetWellknownJob" stopped without ready network reply
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.jobs: Sent GET https://domain.tl/.well-known/matrix/client
QHttpNetworkConnectionPrivate::_q_hostLookupFinished could not de-queue
request, failed to report HostNotFoundError
quotient.jobs: No valid HTTP headers from GET
https://domain.tl/.well-known/matrix/client
quotient.jobs: "GetWellknownJob" status NetworkError: Host domain.tl not found
quotient.jobs: "GetWellknownJob": retry #1 in 5 s
quotient.jobs: "GetWellknownJob" stopped with empty network reply
quotient.jobs: Sent GET https://domain.tld/.well-known/matrix/client
quotient.jobs: 302 <- GET http://www.domain.tld/.well-known/matrix/client
quotient.jobs: "GetWellknownJob" status NetworkError: Insecure redirect
quotient.jobs: "GetWellknownJob": retry #1 in 5 s
quotient.jobs: Sent GET https://domain.tld/.well-known/matrix

[krita] [Bug 431865] Crash when copying blank paint layer

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

tomtomtomreportin...@gmail.com changed:

   What|Removed |Added

 CC||twiceisfo...@gmail.com

--- Comment #9 from tomtomtomreportin...@gmail.com ---
*** Bug 433832 has been marked as a duplicate of this bug. ***

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

[krita] [Bug 433832] Crashes when deleting a new layer