[policykit-kde-agent-1] [Bug 485407] polkit-kde-agent crashes with nullptr
https://bugs.kde.org/show_bug.cgi?id=485407 Norbert Pfeiler changed: What|Removed |Added CC||norbert.pfeiler+bugs.kde.or ||g...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #27 from Norbert Preining --- Sorry again, with properly applied patch 369c3cbd7d843b6ce2901adf8b464158f84759a1 I cannot reproduce the failure :-( Sorry for the noise! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #26 from Norbert Preining --- Wait ... I blindly copied a test run to the PKGBUILD and it contained --dry-run ... let me rerun the test without the revert and see if it works Sorry for the confusion, now when I tried to add the other patch for reverting I found the --dry-run -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #23 from Norbert Preining --- (In reply to fanzhuyifan from comment #22) > Do you have any core-testing and extra-testing enabled, by the way? No, only default repositories (core,extra,multilib) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #21 from Norbert Preining --- (In reply to fanzhuyifan from comment #20) > I am on arch linux, using Qt 6.7 (with all the testing repos enabled > including kde-unstable). Hmmm, looking at https://archlinux.org/packages/?sort==KDE-Unstable it seems only Qt is updated there at the moment. I am a bit nervous going to a beta version of Qt since this is my work computer. Do you think this is purely depending on Qt updated to 6.7? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #19 from Norbert Preining --- Created attachment 166925 --> https://bugs.kde.org/attachment.cgi?id=166925=edit kwin x11 offset even with patch applied screencast -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #18 from Norbert Preining --- (In reply to fanzhuyifan from comment #15) > Could you share the steps with which you could still reproduce the problem? > A screencast would be ideal. I attach one > Are you still seeing this for all windows on X11? I tested konsole and system settings, both in screencast to be seen. That is based on Arch Linux kwin 6.0.1-3 with 369c3cbd7d843b6ce2901adf8b464158f84759a1.patch applied. Build log shows: > ==> Making package: kwin 6.0.1-3.1 (Mon 11 Mar 2024 08:55:03 AM JST) > ==> Checking runtime dependencies... > ==> Checking buildtime dependencies... > ==> Retrieving sources... > -> Found kwin-6.0.1.tar.xz > -> Found kwin-6.0.1.tar.xz.sig > -> Found 369c3cbd7d843b6ce2901adf8b464158f84759a1.patch > ==> Validating source files with sha256sums... > kwin-6.0.1.tar.xz ... Passed > kwin-6.0.1.tar.xz.sig ... Skipped > 369c3cbd7d843b6ce2901adf8b464158f84759a1.patch ... Passed > ==> Verifying source file signatures with gpg... > kwin-6.0.1.tar.xz ... Passed > ==> Extracting sources... > -> Extracting kwin-6.0.1.tar.xz with bsdtar > ==> Starting build()... > checking file src/utils/xcbutils.h > checking file src/workspace.cpp > Hunk #1 succeeded at 3020 (offset -1 lines). > -- The C compiler identification is GNU 13.2.1 > ... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482687] On X11, pointer position offset after moving window outside the left edge of screen space
https://bugs.kde.org/show_bug.cgi?id=482687 --- Comment #14 from Norbert Preining --- (In reply to fanzhuyifan from comment #8) > Git commit 369c3cbd7d843b6ce2901adf8b464158f84759a1 by Yifan Zhu. > Committed on 08/03/2024 at 19:34. > Pushed by fanzhuyifan into branch 'Plasma/6.0'. > > utils/xcbutils: Don't call toXNative with unsigned integer > > Instead use signed integers, to prevent the implicit cast from unsigned > integers to qreal. [..] > https://invent.kde.org/plasma/kwin/-/commit/ > 369c3cbd7d843b6ce2901adf8b464158f84759a1 I pulled this patch into a local build of kwin on Arch, but it did *NOT* fix the misbehaviour. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482956] Edge browser window receives events despite being shown in different position
https://bugs.kde.org/show_bug.cgi?id=482956 --- Comment #2 from Norbert Preining --- Created attachment 166780 --> https://bugs.kde.org/attachment.cgi?id=166780=edit Screencast showing the misbehaviour -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482956] Edge browser window receives events despite being shown in different position
https://bugs.kde.org/show_bug.cgi?id=482956 Norbert Preining changed: What|Removed |Added Summary|Cannot move Edge browser|Edge browser window |window out of the left |receives events despite |border |being shown in different ||position -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482956] Cannot move Edge browser window out of the left border
https://bugs.kde.org/show_bug.cgi?id=482956 --- Comment #1 from Norbert Preining --- I forgot to add an important information: That is an X11 session, not wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482956] New: Cannot move Edge browser window out of the left border
https://bugs.kde.org/show_bug.cgi?id=482956 Bug ID: 482956 Summary: Cannot move Edge browser window out of the left border Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: norb...@preining.info Target Milestone: --- SUMMARY When I move the edge browser window out of the screen to the left, it is drawn as being out of it, but mouse actions are taken as if the windows has not moved out but got stuck with the window left border on the left border of the screen. Also mouse inputs to the window are misplaced as seen in the second part of the attached video. The moment I click the mouse, the window pops to its "assumed" (wrong) position. STEPS TO REPRODUCE 1. move edge browser window out of the left edge 2. click on the frame or somewhere around the position where there can be interaction 3. OBSERVED RESULT Window frame and window content reacts despite the window being in different position EXPECTED RESULT Not doing this. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION nvidia graphic card -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype
https://bugs.kde.org/show_bug.cgi?id=475479 Norbert changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #18 from Norbert --- Fixed with plasma 6.0.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #18 from Norbert --- Thank you for your help, i am now able to work properly again. I have created an Issue on Evdi Github: https://github.com/DisplayLink/evdi/issues/459 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #16 from Norbert --- To clear up my bad English. 1. With the `KWIN_DRM_NO_AMS=1` Variable, all Displays work correctly and does not freeze or reconnect anymore. This includes using all DP and HDMI ports on the docking station and the in build Laptop HDMI at once. 2. Some times ago(~Plasma6 Beta 2), one frozen Display would freeze the whole session, now only the causing Display is frozen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #15 from Norbert --- Hi, with `KWIN_DRM_NO_AMS=1` It works now without any issues, I noticed since the latest kwin update even without Variable, kwin does not freeze anymore on the working display outputs. It works even better than with xorg because the input latency is noticeably lower. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #13 from Norbert --- This time I did not manage to get kscreen to detect the outputs. I hope the drm_info from the unfrozen state helps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #12 from Norbert --- Created attachment 165803 --> https://bugs.kde.org/attachment.cgi?id=165803=edit drm_info when the docking station(lenovo dud9011d1) is pluged in on the plasma6 kwin wayland session and the session is working This time, I've managed to get the drm_info output when the session is in an unfrozen state. It froze after 2 seconds again. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #11 from Norbert --- (In reply to Norbert from comment #8) > Created attachment 165800 [details] > drm_info when the docking station(lenovo dud9011d1) is pluged in on tthe > plasma6 kwin wayland session > > I could not find a difference between Wayland with and without the dock, but > there is more on the kwin session. > Displaylink is using the evdi module to work. I wanted to say, that there are more outputs visible on the kwin x11 sessions output. Which is weird because kscreen in the Wayland session is able to detect the DisplayLink Monitors. I will attach the kscreen output as well -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #10 from Norbert --- Created attachment 165802 --> https://bugs.kde.org/attachment.cgi?id=165802=edit drm_info on the plasma6 kwin wayland session without a dock -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 Norbert changed: What|Removed |Added Attachment #165604|0 |1 is obsolete|| Attachment #165605|0 |1 is obsolete|| --- Comment #9 from Norbert --- Created attachment 165801 --> https://bugs.kde.org/attachment.cgi?id=165801=edit drm_info when the docking station(lenovo dud9011d1) is pluged in on tthe plasma6 kwin x11 session -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #8 from Norbert --- Created attachment 165800 --> https://bugs.kde.org/attachment.cgi?id=165800=edit drm_info when the docking station(lenovo dud9011d1) is pluged in on tthe plasma6 kwin wayland session I could not find a difference between Wayland with and without the dock, but there is more on the kwin session. Displaylink is using the evdi module to work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #7 from Norbert --- Thank you, I will. Unfortunately I have access to the dock only once a week, I will be back on next Tuesday. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #5 from Norbert --- Created attachment 165605 --> https://bugs.kde.org/attachment.cgi?id=165605=edit with the dock connected -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #4 from Norbert --- Created attachment 165604 --> https://bugs.kde.org/attachment.cgi?id=165604=edit without the dock connected -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #3 from Norbert --- I was not able to get the information in an unfrozen state in plasma6, I will attach two logs, once without the dock connected, and the second with the dock connected display enabled but frozen. The Logs are nearly identical, and it looks like it does not load the display at all. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 --- Comment #64 from Norbert Preining --- (In reply to David Edmundson from comment #61) > Can someone who can reproduce test a patch: > > change > ddca_get_display_info_list2(true, ); > > to > ddca_get_display_info_list2(false, ); Hi David, yes that worked, after installing ddcutil2 and rebuilding with this patch attached on my Arch machine, powerdevil did start properly ``` Jan 15 12:50:01 bulldog systemd[1786]: Starting Powerdevil... Jan 15 12:50:01 bulldog org_kde_powerdevil[9507]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" Jan 15 12:50:01 bulldog org_kde_powerdevil[9507]: org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed Jan 15 12:50:01 bulldog libddcutil[9507]: Initializing libddcutil. ddcutil version: 2.0.0, shared library: /usr/lib/libddcutil.so.5.0.0 Jan 15 12:50:01 bulldog libddcutil[9507]: Library initialization complete. Jan 15 12:50:03 bulldog systemd[1786]: Started Powerdevil. Jan 15 12:50:03 bulldog org_kde_powerdevil[9507]: org.kde.powerdevil: Handle button events action could not check for screen configuration Jan 15 12:50:03 bulldog org_kde_powerdevil[9507]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware" ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype
https://bugs.kde.org/show_bug.cgi?id=475479 Norbert changed: What|Removed |Added Version|5.27.8 |5.27.10 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #17 from Norbert --- Please ignore my previous comment about plasmashell, it has nothing to do with this issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #16 from Norbert --- Created attachment 164854 --> https://bugs.kde.org/attachment.cgi?id=164854=edit Plasmashell log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #15 from Norbert --- I have figured out this happens when I add the systray applet to the plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #1 from Norbert --- Plasma 6 Beta 2 no improvements. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #14 from Norbert --- Plasma 6 Beta 2 no improvements. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 478551] New: No connection resumes while phone screen is off
https://bugs.kde.org/show_bug.cgi?id=478551 Bug ID: 478551 Summary: No connection resumes while phone screen is off Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: norbert.rybi...@gmx.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- No connection resumes when phone display is off. The phone automatically resumes connection when the display is turned on, even before unlocking. STEPS TO REPRODUCE: 1. install KDE Connect on a computer running Kubuntu 2. install KDE Connect on an Android phone 3. pair the computer with the phone 4. log out of the Kubuntu system 5. lock the phone 6. log in to Kubuntu OBSERVED RESULT: KDE Connect on the computer is not connected to the phone. EXPECTED RESULT: Automatic connection at computer login. SOFTWARE/OS VERSIONS Computer Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 KDE Connect Version: 23.08.1 Phone Poco F3 Android Version: 13 KDE Connect Version: 1.29.0 ADDITIONAL INFORMATION 1. with the display off, the phone does not send or receive UDP packets on port 1716 (kdeconnect-cli --refresh command on the computer does not give the expected result) - checked with the tcpdump command 2. with the display off, TCP port 1716 on the phone is open - checked with the netcat command 3. turning on the phone's display - just displaying the lock screen, restores the connection, the phone sends UDP packets on port 1716 - - checked with the tcpdump command 4. the application on the phone has all possible permissions granted, is excluded from power saving, location always available (not only when the app is open). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype
https://bugs.kde.org/show_bug.cgi?id=475479 Norbert changed: What|Removed |Added Attachment #162228|0 |1 is obsolete|| Attachment #162280|0 |1 is obsolete|| --- Comment #13 from Norbert --- Created attachment 163480 --> https://bugs.kde.org/attachment.cgi?id=163480=edit Latest core dump -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #12 from Norbert --- Created attachment 163479 --> https://bugs.kde.org/attachment.cgi?id=163479=edit Latest service log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #11 from Norbert --- I recently performed a clean reinstallation of my system, opting for the default Plasma configuration. However, I've been experiencing even more frequent crashes, particularly when clicking within the plasma panel or when an app is opened from a minimized state, causing a change in focus. After these crashes, I've noticed an error message that was not present before: ``` QtDBus: cannot relay signals from parent QObject(0x55930eaa11c0 "") unless they are emitted in the object's thread QThread(0x55930e720268 "libinput-connection"). Current thread is QThread(0x55930e69bf10 ""). ``` The Core Dump also indicates: ``` QV4::MemoryManager::sweep(bool, void (*)(char const*)) () at /usr/lib/libQt5Qml.so.5 ``` Here are the system specifications at the time: - Operating System: ArchLinux (25.11.2023) - Kernel: 6.6.2 - KDE Plasma Version: 5.27.9 - KDE Frameworks Version: 5.112.0 - Qt Version: 5.15.11 I'll attach the latest core dump and journal log for further analysis. I suspect the frequent crashes, particularly when interacting with the plasma panel or changing focus, could be linked to my multi-monitor setup with varying refresh rates, resolutions, and scaling. Additionally, my RX 7900XTX graphics card might be contributing to these issues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype
https://bugs.kde.org/show_bug.cgi?id=475479 Norbert changed: What|Removed |Added Summary|kwin_wayland regularly |kwin_wayland regularly |crashes with Unable to |crashes with Unable to |handle unregistered |handle unregistered |datatype 'KWin::Output* |datatype -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 --- Comment #34 from Norbert --- (In reply to WiseLord from comment #15) > One more related issue: > > 1. Quick tile a window to the left or write, it doesn't matter. > 2. Swtich to another desktop (e.g., from 1 to 2) > 3. Quick tile one more window. > 4. Resize 2nd window > 5. Get back to desktop 1. > > You'll see that 1st window also was suddenly resizes. > > I don't think it's an expected behaviour. Resizing windows belonging to one > desktop should not impact on windows on other desktops. Also experiencing this one. Most definetly a bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Split does not reset to its original value once "adjacent quick-tiled windows" configuration ceases to exist
https://bugs.kde.org/show_bug.cgi?id=465937 Norbert changed: What|Removed |Added CC||norbertzpil...@gmail.com --- Comment #33 from Norbert --- To me there should be a config option for this 2 things (probably separately): - quick tiling forced to 50% width - disable of any width change to other windows I used to use it as follows: - quick tile both windows to 50% - resize them to ~75% to still allow quick switching (click on the backgrounded window) and having reasonable work space. Now this workflow is broken (seems not only for me). Please add config options for these. We don't want to be forced to do anything. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype 'KWin::Output*
https://bugs.kde.org/show_bug.cgi?id=475479 Norbert changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 Norbert changed: What|Removed |Added CC||sandw...@archworks.co Keywords||multiscreen, wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] New: kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922
Bug ID: 475922
Summary: kwin_wayland freeze loop on DisplayLink connection
Classification: Plasma
Product: kwin
Version: 5.27.8
Platform: Archlinux
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: sandw...@archworks.co
Target Milestone: ---
SUMMARY
Kwin_wayland freezes if Monitors are plugged in over a DisplayLink connection.
It sometimes works for a second then freezes and sometimes reinitialize the
monitors in loop.
The laptop in Use is a Lenovo ThinkBook 14 G3 with an AMD GPU, the Monitors are
connected to a Lenovo Docking station, that connects over USB-C and the
DisplayLink protocol to the laptop.
The following kernel drivers were needed on X11 "evdi" and "displaylink"
This matter is important since Plasma 6 is coming and many Users utilize
DisplayLink docks in a Work environment.
I have two monitors:
1. 1920x1080 75hz Scaling 100% (Main)
2. 1920x1080 75hz Scaling 100%
STEPS TO REPRODUCE
1. Start Plasma Wayland Session
2. Connect Monitors with the Docking Station
3. Plug in the Docking station to the laptop using DisplayLink
OBSERVED RESULT
Display turn on, and sometimes work for 1-2 seconds, then the image gets
static.
Laptop Screen still responsive, but most of the time the session freezes.
Sometime
SOFTWARE/OS VERSIONS
Kernel: 6.5.8 or 6.1.59
Linux/KDE Plasma: ArchLinux (21.10.2023)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
ADDITIONAL INFORMATION
Some time ago, it worked with this Bug that was fixed in this issue:
https://bugs.kde.org/show_bug.cgi?id=414626
I was not able to produce a crash, so there is no traceback or dump
OUTPUT of systemctl --user status plasma-kwin_wayland.service
```
● plasma-kwin_wayland.service - KDE Window Manager
Loaded: loaded (/usr/lib/systemd/user/plasma-kwin_wayland.service; static)
Active: active (running) since Tue 2023-10-17 11:06:13 CEST; 4min 0s ago
Main PID: 1094 (kwin_wayland_wr)
Tasks: 24 (limit: 4217)
Memory: 69.1M
CPU: 11.231s
CGroup:
/user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service
├─1094 /usr/bin/kwin_wayland_wrapper --xwayland
├─1098 /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0
--xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority
/run/user/1000/xauth_vhLxZV --xwayland
└─1147 /usr/bin/Xwayland :1 -auth /run/user/1000/xauth_vhLxZV
-listen 50 -listen 51 -displayfd 42 -rootless -wm 45
Oct 17 11:10:04 NMO-14G3 kwin_wayland_wrapper[1098]: MESA-LOADER: failed to
retrieve device information
Oct 17 11:10:04 NMO-14G3 kwin_wayland_wrapper[1098]: MESA-LOADER: failed to
retrieve device information
Oct 17 11:10:04 NMO-14G3 kwin_wayland_wrapper[1098]: kmsro: driver missing
Oct 17 11:10:07 NMO-14G3 kwin_wayland[1098]: QMetaProperty::read: Unable to
handle unregistered datatype 'KWin::Output*' for property
'KWin::XdgToplevelWindow::output'
Oct 17 11:10:07 NMO-14G3 kwin_wayland[1098]: QMetaProperty::read: Unable to
handle unregistered datatype 'QVector' for property
'KWin::XdgToplevelWindow::desktops'
Oct 17 11:10:07 NMO-14G3 kwin_wayland[1098]: js: alwaysopenonactivescreen:
window {
"objectName": "",
"bufferGeometry": {
"x": 96,
"y": 0,
"width": 1728,
"height": 815,
"left": 96,
"right": 1824,
"top": 0,
"bottom": 815
},
"pos": {
"x": 96,
"y": 0
},
"size": {
"width": 1728,
"height": 815
},
"x": 96,
"y": 0,
"width": 1728,
"height": 815,
"opacity": 1,
"screen": 0,
"rect": {
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype 'KWin::Output*
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #9 from Norbert --- Just a second later, it crashed again, this time with the same backtrace as my first attachment. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype 'KWin::Output*
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #8 from Norbert --- Created attachment 162280 --> https://bugs.kde.org/attachment.cgi?id=162280=edit backtrace with all thirdpart Kwin Scripts and Effects disabled -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype 'KWin::Output*
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #7 from Norbert --- Unfortunately, that's not the case. I have uninstalled all Effects. What changed is that I don't get any Errors from `systemctl status` anymore. I had some Kwin Scripts before like `Sticki Windows Snapping` and `resotreToScreen`. And the backtrace is marginally different. So maybe the case is a different now. Before I could trash the session in one minute, now it can take even 5 minutes. It only happens by moving, spawning and max/minimizing Applications. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype 'KWin::Output*
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #5 from Norbert --- FYI: I have a second integrated AMD GPU, there is no display connected to it, but it is being recognized by mesa. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype 'KWin::Output*
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #4 from Norbert --- Hi, I have attached the Backtrace, this kind of looks like an OpenGL issue or something? I have an AMD RX7900XTX using Mesa 23.2.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype 'KWin::Output*
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #3 from Norbert --- Created attachment 162228 --> https://bugs.kde.org/attachment.cgi?id=162228=edit kwin_wayladn backtrace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] kwin_wayland regularly crashes with Unable to handle unregistered datatype 'KWin::Output*
https://bugs.kde.org/show_bug.cgi?id=475479 --- Comment #1 from Norbert --- Please let me know if any additional info is required. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475479] New: kwin_wayland regularly crashes with Unable to handle unregistered datatype 'KWin::Output*
https://bugs.kde.org/show_bug.cgi?id=475479
Bug ID: 475479
Summary: kwin_wayland regularly crashes with Unable to handle
unregistered datatype 'KWin::Output*
Classification: Plasma
Product: kwin
Version: 5.27.8
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: multiscreen, wayland
Severity: crash
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: sandw...@archworks.co
Target Milestone: ---
Flags: Wayland+
SUMMARY
Kwin_wayland crashes when Applications are being moved or opened, this does not
happen every time, but if I will move and resize an application then it
certainly will quick
I have two monitors with different refresh rate and resolutions:
1. 3440x1440 160hz Scaling 135% (Main)
2. 1920x1080 144hz Scaling 100%
STEPS TO REPRODUCE
1. Start Plasma Wayland Session
2. Open an Application
3. Move it around between two screens
4. Resize it
OBSERVED RESULT
Kwin crashes everything goes black and restarts, all applications were closed
and not restarted.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: ArchLinux (11.10.2023)
(available in About System)
KDE Plasma Version: 5.27.8
KDE Frameworks Version: 5.110.0
Qt Version: 5.15.11
ADDITIONAL INFORMATION
I use the Wobbly Windows and Magic Lamp effect.
OUTPUT of systemctl --user status plasma-kwin_wayland.service
```
Oct 11 19:28:43 ReRe kwin_wayland[139832]: QMetaProperty::read: Unable to
handle unregistered datatype 'KWin::Output*' for property
'KWin::XdgToplevelWindow::output'
Oct 11 19:28:43 ReRe kwin_wayland[139832]: QMetaProperty::read: Unable to
handle unregistered datatype 'QVector' for property
'KWin::XdgToplevelWindow::desktops'
Oct 11 19:28:43 ReRe kwin_wayland[139832]: js: alwaysopenonactivescreen: window
{
"objectName": "",
"bufferGeometry": {
"x": 1920,
"y": 51,
"width": 2548,
"height": 787,
"left": 1920,
"right": 4468,
"top": 51,
"bottom": 838
},
"pos": {
"x": 1920,
"y": 51
},
"size": {
"width": 2548,
"height": 787
},
"x": 1920,
"y": 51,
"width": 2548,
"height": 787,
"opacity": 1,
"screen": 1,
"rect": {
"x": 0,
"y": 0,
"width": 2548,
"height": 787,
"left": 0,
"right": 2548,
"top": 0,
"bottom": 787
},
"resourceName": "yakuake",
"resourceClass":
"org.kde.yakuake",
"windowRole": "",
"desktopWindow": false,
"dock": false,
"toolbar": false,
"menu": false,
"normalWindow": true,
"dialog": false,
"splash": false,
"utility": false,
"dropdownMenu": false,
"popupMenu": false,
"tooltip": false,
"notification": false,
"criticalNotification": false,
[kwin] [Bug 472794] Lag on wayland
https://bugs.kde.org/show_bug.cgi?id=472794 Norbert Pfeiler changed: What|Removed |Added Version|5.27.6 |5.27.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472794] Lag on wayland
https://bugs.kde.org/show_bug.cgi?id=472794 Norbert Pfeiler changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Norbert Pfeiler --- (In reply to Nate Graham from comment #3) > Do the Present Windows and Desktop Grid effects exhibit the same issue? they do PS: Regarding the »freezing« vs. »lagging« distinction – I used »freeze« to convey a complete, albeit temporary, halt in function of the complete UI. In my view, it’s not synonymous with mere lagging. I can’t move my cursor, it’s not only the animation itself that has an issue. Trying to use my desktop with that, »freeze« felt more apt to describe it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463465] Importing large H256 videos (150GB+) causing constant crashing.
https://bugs.kde.org/show_bug.cgi?id=463465 --- Comment #2 from Norbert --- Hallo @farid I can confirm with my current version of KdenLive 23.08.1, it is not crashing any more. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472794] temporary freezes on wayland
https://bugs.kde.org/show_bug.cgi?id=472794 Norbert Pfeiler changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Norbert Pfeiler --- i have this bound to the windows key opening animation: i’m moving my cursor in circles holding down the windows key: no lag letting go of the windows key: - ~0.5s lag (cursor doesn’t move) - animation starts, proceeds and ends (most of the time smoothly) - ~1s of normal behavior (moving cursor shows highlights hovered windows) - another ~0.5s lag - from now on hover works fine without lags - however, adding or removing a letter from the search that filters any of the windows (requiring an animation) always lags <0.5s - on the very first input the letter also appears twice (doesn’t happen after removing all the letters and typing it again) closing animation: holding down the windows key: no lag letting go of the windows key: - animation starts, proceeds somewhat unsmooth and ends - ~1s of normal behavior - 2s of freeze i have 4k and FHD+ screens with 10+3 windows open, atm running on amdgpu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472794] New: temporary freezes on wayland
https://bugs.kde.org/show_bug.cgi?id=472794 Bug ID: 472794 Summary: temporary freezes on wayland Classification: Plasma Product: kwin Version: 5.27.6 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: norbert.pfeiler+bugs.kde@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. toggle overview (doesn’t matter if by key or screen corner) OBSERVED RESULT lags before and during animation freeze 1 second after animation is done EXPECTED RESULT no lags SOFTWARE/OS VERSIONS KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION no issue on X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463897] Kinetic Scrolling [Wishlist]
https://bugs.kde.org/show_bug.cgi?id=463897 Norbert changed: What|Removed |Added CC||norbertzpil...@gmail.com --- Comment #2 from Norbert --- Also other apps don't have it. Probably GTK ones too. I'd implement it as a system-wide solution. Just like "reverse scrolling direction" setting. It's naive to think every single program on your system is going to implement kinetic scrolling. And imagine setting acceleration factor for all of them individually... It is surely a regression from Xorg+Synaptics experience. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463465] Importing large H256 videos (150GB+) causing constant crashing.
https://bugs.kde.org/show_bug.cgi?id=463465 Norbert changed: What|Removed |Added Summary|Constant Crashing when |Importing large H256 videos |importing h256 Videos |(150GB+) causing constant |150GB+ |crashing. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 463465] New: Constant Crashing when importing h256 Videos 150GB+
https://bugs.kde.org/show_bug.cgi?id=463465 Bug ID: 463465 Summary: Constant Crashing when importing h256 Videos 150GB+ Classification: Applications Product: kdenlive Version: git-master Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: norbert.moraw...@archgang.com Target Milestone: --- SUMMARY: *** KdenLive crashes every time I try to import 20 H.256 video files totaling 300GB. It crashes after about 150GB have been imported. I have 32GB of RAM, but only saw 20GB utilization before the crash. This was tested on lates ArchLinux vanilla Package and the git-master build. *** STEPS TO REPRODUCE: 1. Start KDE 2. Import Big mkv files (about 20GB per File) OBSERVED RESULT: It freeze/crashe after about 9/23 were imported SOFTWARE/OS VERSIONS: KdenLive: 23.03.70 (2646520063f5ee0b9dff8d0e949d3edb82dbc541) Linux/KDE Plasma: ArchLinux 6.1.1 x64 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 SPECS: CPU: Ryzen 9 7950X GPU: RX 6900 XT RAM: 2x16GB DDR5 6000Mhz (swappines=10) Session: X11 DEBUG: ''' Thread 1 "kdenlive" received signal SIGSEGV, Segmentation fault. 0x74cdfcab in QMutex::lock() () from /usr/lib/libQt5Core.so.5 (gdb) bt #0 0x74cdfcab in QMutex::lock() () at /usr/lib/libQt5Core.so.5 #1 0x74e8c37f in QCoreApplicationPrivate::lockThreadPostEventList(QObject*) () at /usr/lib/libQt5Core.so.5 #2 0x74e8d502 in QCoreApplication::postEvent(QObject*, QEvent*, int) () at /usr/lib/libQt5Core.so.5 #3 0x55a846f1 in TaskManager::slotCancelJobs(QVector) (this=0x566ff298, exceptions=...) at /home/sandwich/Stuff/Git/kdenlive/src/jobs/taskmanager.cpp:152 #4 0x55eb3b2c in Core::cleanup() (this=0x566ff280) at /home/sandwich/Stuff/Git/kdenlive/src/core.cpp:1329 #5 0x55bd5acb in ProjectManager::closeCurrentDocument(bool, bool) (this=0x56c177a0, saveChanges=true, quit=true) at /home/sandwich/Stuff/Git/kdenlive/src/project/projectmanager.cpp:328 #6 0x55eee570 in MainWindow::queryClose() (this=0x56aec410) at /home/sandwich/Stuff/Git/kdenlive/src/mainwindow.cpp:963 #7 0x776d27ed in KMainWindow::closeEvent(QCloseEvent*) () at /usr/lib/libKF5XmlGui.so.5 #8 0x55f02641 in MainWindow::closeEvent(QCloseEvent*) (this=0x56aec410, event=0x7fffc8d0) at /home/sandwich/Stuff/Git/kdenlive/src/mainwindow.cpp:2520 #9 0x761af348 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7770427e in KXmlGuiWindow::event(QEvent*) () at /usr/lib/libKF5XmlGui.so.5 #11 0x76178b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #12 0x74e8cf98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #13 0x761ae03e in QWidgetPrivate::close_helper(QWidgetPrivate::CloseMode) () at /usr/lib/libQt5Widgets.so.5 #14 0x761d02f7 in () at /usr/lib/libQt5Widgets.so.5 #15 0x76178b1c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #16 0x74e8cf98 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #17 0x7594086f in QGuiApplicationPrivate::processCloseEvent(QWindowSystemInterfacePrivate::CloseEvent*) () at /usr/lib/libQt5Gui.so.5 #18 0x759289a5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #19 0x7fffeff2f710 in () at /usr/lib/libQt5XcbQpa.so.5 #20 0x7351687b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #21 0x7356dc89 in () at /usr/lib/libglib-2.0.so.0 #22 0x73515132 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #23 0x74ed7c4c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #24 0x74e8573c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #25 0x74e90269 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #26 0x55638173 in main(int, char**) (argc=1, argv=0x7fffdc88) at /home/sandwich/Stuff/Git/kdenlive/src/main.cpp:345 ''' -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460608] New: No longer can run MOZ_USE_XINPUT2=1 /usr/lib/firefox/firefox in app
https://bugs.kde.org/show_bug.cgi?id=460608 Bug ID: 460608 Summary: No longer can run MOZ_USE_XINPUT2=1 /usr/lib/firefox/firefox in app Classification: Plasma Product: plasmashell Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: plasma-b...@kde.org Reporter: norbertzpil...@gmail.com CC: k...@privat.broulik.de, mvourla...@gmail.com Target Milestone: 1.0 SUMMARY *** It used to work. I know this is a bad example as I can put it in /etc/environment BUT with setting 'XDG_CONFIG_HOME it isn't that easy. *** STEPS TO REPRODUCE 1. Edit firefox application 2. Write `MOZ_USE_XINPUT2=1 /usr/lib/firefox/firefox` in program 3. Run firefox by clicking on it OBSERVED RESULT Error shows up: `execvp: No such file or directory` EXPECTED RESULT Firefox runs with env variable set SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Kernel Version: 6.0.1-arch2-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 Manufacturer: ASUSTeK COMPUTER INC. Product Name: X510UQ System Version: 1.0 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 416113] Akonadi crashes when switching between folder
https://bugs.kde.org/show_bug.cgi?id=416113 --- Comment #2 from Norbert Blobel --- (In reply to Justin Zobel from comment #1) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" when > replying. Thank you! Hello, I no longer use kontakt and kmail. It is no longer stable and usable enough for day to day work. I have switched to thunderbird. Regards Norbert -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 453890] Umount icon unnecessarily shown for internal drives
https://bugs.kde.org/show_bug.cgi?id=453890 --- Comment #25 from Norbert --- Additionally on my system the icon is not shown but I can click it, and it asks for password. KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[libqapt] [Bug 354477] virtual dependencies are not handled
https://bugs.kde.org/show_bug.cgi?id=354477 Norbert Lederbauer changed: What|Removed |Added CC||n.lederba...@tsn.at --- Comment #3 from Norbert Lederbauer --- Since the installation of Kubuntu 22.04 qApt makes problems. When I install a current package always comes the message "Error. Cannot satisfy dependencies", even if exactly this package is already installed. Version 3.0.5-1ubuntu1 The packages can be installed via the console without problems (if you know the code) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453890] Umount icon shown on internal drives
https://bugs.kde.org/show_bug.cgi?id=453890 --- Comment #2 from Norbert --- Simple tick box would be enough -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453890] New: Umount icon shown on internal drives
https://bugs.kde.org/show_bug.cgi?id=453890 Bug ID: 453890 Summary: Umount icon shown on internal drives Product: dolphin Version: 22.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: folders Assignee: dolphin-bugs-n...@kde.org Reporter: norbertzpil...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 148882 --> https://bugs.kde.org/attachment.cgi?id=148882=edit Icon shown SUMMARY Dolphin displays umount icon on every drive under Devices. Is there a way to hide it for internal (nonremovable) drives? STEPS TO REPRODUCE 1. Have some partition mounted for ex. via fstab 2. Open dolphin 3. Icon shows. OBSERVED RESULT Icon shows EXPECTED RESULT Icon hidden for permanent drives SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 451396] double language
https://bugs.kde.org/show_bug.cgi?id=451396 --- Comment #10 from Norbert Lederbauer --- Thank you for your comment. But if I were so good at translating, I wouldn't need a german edition of the program. Writing comments can be made with translators. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 451396] double language
https://bugs.kde.org/show_bug.cgi?id=451396 --- Comment #8 from Norbert Lederbauer --- @Alvin Wong Please read the complete history, specially comment 6. Please note, that not everybody in this world speaks English, so a correct localisation is helpful. Krita Version: 5.0.2 Languages: de, de, fr, de, de, fr, de, de, fr, de, fr, de_AT, de Hidpi: true -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 452218] Reports implicit declarations despite code compiles without warnings
https://bugs.kde.org/show_bug.cgi?id=452218 --- Comment #3 from Norbert --- Adding `#define __USE_POSIX 1` before `#include ` sometimes fixes the issue. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 452218] Reports implicit declarations despite code compiles without warnings
https://bugs.kde.org/show_bug.cgi?id=452218 --- Comment #2 from Norbert --- Created attachment 147930 --> https://bugs.kde.org/attachment.cgi?id=147930=edit Compiles without errors/warnings -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 452218] Reports implicit declarations despite code compiles without warnings
https://bugs.kde.org/show_bug.cgi?id=452218 --- Comment #1 from Norbert --- Created attachment 147929 --> https://bugs.kde.org/attachment.cgi?id=147929=edit Errors visible -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 452218] New: Reports implicit declarations despite code compiles without warnings
https://bugs.kde.org/show_bug.cgi?id=452218
Bug ID: 452218
Summary: Reports implicit declarations despite code compiles
without warnings
Product: kdevelop
Version: 5.7.211203
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Problem reporter
Assignee: kdevelop-bugs-n...@kde.org
Reporter: norbertzpil...@gmail.com
Target Milestone: ---
SUMMARY
The code is marked as invalid or warnings are listed.
STEPS TO REPRODUCE
1. Insert sample code.
2. Watch the errors
3. Compile code without warnings or errors
OBSERVED RESULT
Lots of errors and warining despite correct includes
EXPECTED RESULT
No warnings or errors
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.24.3
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
Sample code used:
```c
#include
#include
#include
#define SIGNAL SIGUSR1
void action_handler(int sig, siginfo_t *info, void *ucontext) {
printf("received signal %d\n", sig);
exit(0);
}
int main(int argc, char** argv) {
struct sigaction sa;
sigaction(SIGNAL, NULL, );
sa.sa_sigaction = action_handler;
sigaction(SIGNAL, , NULL);
raise(SIGNAL);
while(1);
return 0;
}
```
--
You are receiving this mail because:
You are watching all bug changes.
[kio-extras] [Bug 412257] kiod5 doesn't release usb device when it is not in use
https://bugs.kde.org/show_bug.cgi?id=412257 --- Comment #20 from Norbert Preining --- (In reply to Harald Sitter from comment #11) > The unplugging and plugging back in should be fixed in master. There were > caching problems. Unfortunately it is not. I am running Arch Linux with the latest released KDE packages, and unplugging and replugging a mtp ebook reader does not help. The device contents is shown, but I cannot copy files to the device. I need to kill the kiod as always to get rw access to the device again. A typical example is Calibre (which I use a lot) which has a "Release" button for the device. Something similar should be included in Dolphin and "Removable Devices". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 451396] double language
https://bugs.kde.org/show_bug.cgi?id=451396 --- Comment #6 from Norbert Lederbauer --- Main language in German Fallback language in French -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 451396] double language
https://bugs.kde.org/show_bug.cgi?id=451396 --- Comment #3 from Norbert Lederbauer --- Created attachment 147467 --> https://bugs.kde.org/attachment.cgi?id=147467=edit sreenshot 2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 451396] double language
https://bugs.kde.org/show_bug.cgi?id=451396 --- Comment #2 from Norbert Lederbauer --- Created attachment 147466 --> https://bugs.kde.org/attachment.cgi?id=147466=edit Screenshots Screenshot from the main window and from the filter-dialog -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 451396] New: double language
https://bugs.kde.org/show_bug.cgi?id=451396 Bug ID: 451396 Summary: double language Product: krita Version: 5.0.2 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: n.lederba...@tsn.at Target Milestone: --- SUMMARY double language NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Although I installed the krita-l10n package and set the main language to German, parts of the GUI still appear in the second language (e.g. English). This is not a hindrance but quite unpleasant. STEPS TO REPRODUCE 1. Install package krita-l10n 2. Set the main and the fallback language (German) 3. restart the program OBSERVED RESULT two languages appear EXPECTED RESULT one unique language SOFTWARE/OS VERSIONS Linux/KDE Plasma: kubuntu 20/04 LTS (available in About System) KDE Plasma Version: 5.18.8 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Kernel Version: 5.4.0-104-generic OS Type: 64-bit Processors: 8 × AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx Memory: 6,8 GiB -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450777] (un)shading broken, window has a way too small size after unshading
https://bugs.kde.org/show_bug.cgi?id=450777 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #1 from Norbert Preining --- I cannot reproduce this on Arch with 5.24.2 running over X11. Are you using Wayland? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 --- Comment #8 from Norbert Preining --- Like Thomas I can confirm that on Debian/unstable with my own OBS builds (frameworks 5.91, plasma 5.24.1), as well as with Arch builds, the strange misplaced clicks can be reproduced with e.g. ksnip in the same way as described above (right click ..) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 --- Comment #6 from Norbert Preining --- The "misplaced-mouse-click" is still present on Plasma 5.24.1 / Arch The Debian packages are built ATM. The context menu will need confirmation from a user of my Debian packages, I will inquire. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 --- Comment #5 from Norbert Preining --- I will retest with 5.24.1 and report back, will need 1-2 days to have the packages ready. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 --- Comment #2 from Norbert Preining --- One more comment concerning reproducibility with ksnip: Interestingly it only happens when I **right** click and select "Open Editor" When I just simply click on the tray icon of ksnip it also shows the editor, but then the misplaced click is not reproducible, while in the former case (right click) it is 100% reproducible. The same is the case with Steam, Right-click actions only trigger a misplaced click, not left-click actions on the tray. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 --- Comment #1 from Norbert Preining --- Additional comment concerning the "Misplaced click": No need for binary programs, I can reproduce this with ksnip: - right-click on ksnip tray icon, select "Open editor" - click on the Window decoration X to close it to the tray icon - click on any icon in the taskbar Observed result: the ksnip editor reappears Expected result: the application of the clicked icon appears -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450287] New: system tray icon behavior partially broken from 5.23.90 to 5.24.0
https://bugs.kde.org/show_bug.cgi?id=450287 Bug ID: 450287 Summary: system tray icon behavior partially broken from 5.23.90 to 5.24.0 Product: plasmashell Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: norb...@preining.info CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY Since the update from 5.23.90 to 5.24 (both tried on Arch Linux and Debian unstable), the system tray icons behave strange in some ways: - minimizing some windows to tray icons, then click on *any* icon on the task bar pops up the context menu of the systray icon - some applications (known: anydesk) lost their systray icon context menu A similar bug was present in 5.22.90 and fixed for 5.23, but something seems to have creeped in again between 5.23.90 and 5.24.0 final release STEPS TO REPRODUCE Misplaced click 1. start steam, maximize it 2. click on the top bar X to minimize it to tray icon 3. click on the icon of any application in the task bar 4. the context menu of the steam tray icon pops up (far from the actual mouse pointer location!) (If needed, I can try to capture a screen shot of that) Lost context menu 1. Install anydesk 2. right/left click on the systray icon 3. no context menu is shown ADDITIONAL COMMENTS The same behavior appeared with both frameworks 5.90 and 5.91, so it seems not to depend on that. Also, the same behavior is shown on Arch Linux (packages made by Arch maintainers) as well as my own OBS builds of KDE/Plasma for Debian, so on two independent builds. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.9-zen1-0.1-zen-custom (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 62.8 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 447241] New: Terminal is striped immediately after dropping down yakuake terminal
https://bugs.kde.org/show_bug.cgi?id=447241 Bug ID: 447241 Summary: Terminal is striped immediately after dropping down yakuake terminal Product: yakuake Version: 21.12.0 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: norb...@preining.info Target Milestone: --- Created attachment 144687 --> https://bugs.kde.org/attachment.cgi?id=144687=edit Screenshot of the striped yakuake SUMMARY *** When dropping down yakuake and before the first refresh of the terminal, yakuake shows stripes on Intel graphics hardware. STEPS TO REPRODUCE 1. open yakuake (press F12) 2. stripes are shown (see attached screenshot) 3. do Ctrl-L, or open a curses program and the stripes are gone. This is repeatable every time yakuake is re-opened after it was hidden. OBSERVED RESULT stripes EXPECTED RESULT no stripes SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.10+futex+zstd+intel+wine+ (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-10610U CPU @ 1.80GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445675] New: Rendering widescreen 16:9 format to DVD always adds black bars
https://bugs.kde.org/show_bug.cgi?id=445675 Bug ID: 445675 Summary: Rendering widescreen 16:9 format to DVD always adds black bars Product: kdenlive Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: norb...@preining.info Target Milestone: --- SUMMARY It is not possible to render to widescreen DVD (NTSC) without adding black bars at top bottom, despite input data is 16:9. All renderings to DVD (VOB) result in 4:3 rendered video with black bars, which, when shown on a normal modern TV, results in wrong aspect ratio. STEPS TO REPRODUCE 1. create a project in some 16:9 format 2. render to SD/DVD OBSERVED RESULT output contains black bars at top bottom EXPECTED RESULT correctly encoded video that shows full screen (filling the full screen) of a 16:9 TV SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Changing the Project format to NTSC widescreen does not help, rendering to DVD again creates black bars. Changing the project to DVD, black bars are already added in the preview. What I currently do is: * render to 16:9 mp4 high quality * use videotrans' movie-to-dvd with the respective options -m ntsc -q high -a 16:9 -M * use dvdauthor to create the dvd structure using the previously created vob file * burn -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 444461] New: gwenview shows old file content when underlying file has changed
https://bugs.kde.org/show_bug.cgi?id=61 Bug ID: 61 Summary: gwenview shows old file content when underlying file has changed Product: gwenview Version: 21.08.2 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: norb...@preining.info Target Milestone: --- SUMMARY When the underlying file is changed, gwenview does not update the displayed image, albeit the thumbnail changes. STEPS TO REPRODUCE 1. cd $(mktemp -d) 2. cp ~/photo1.jpg test.jpg 3. gwenview . & at this stage gwenview shows the thumbnail of test.jpg, and double-click on the thumbnail shows the content of photo1.jpg 4. Press ESC - return to directory view 5. cp ~/photo2.jpg test.jpg at this moment, the thumbnail is updated to show the content of photo2.jpg as thumbnail for test.jpg 6. double click on test.jpg this shows the content of photo1.jpg and not photo2.jpg OBSERVED RESULT old file content is shown EXPECTED RESULT new file content is shown SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442758] Some apps' tray icons don't have context menu anymore
https://bugs.kde.org/show_bug.cgi?id=442758 --- Comment #7 from Norbert Preining --- @David I can confirm that the proposed merge request fixes the issue, thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442775] Extra margins introduced upon printing
https://bugs.kde.org/show_bug.cgi?id=442775 --- Comment #4 from Norbert Preining --- Thanks Nate, I can confirm here that by selecting "Force rasterizing" the correct page is produced. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442775] Extra margins introduced upon printing
https://bugs.kde.org/show_bug.cgi?id=442775 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #1 from Norbert Preining --- I can confirm this on Debian/unstable with okular 21.08.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442758] New: some applications don't have context menu anymore
https://bugs.kde.org/show_bug.cgi?id=442758 Bug ID: 442758 Summary: some applications don't have context menu anymore Product: plasmashell Version: 5.22.90 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: norb...@preining.info CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY Some applications, e.g., virt-manager, don't have right-click context menus anymore since upgrade from 5.22.5 to 5.22.90 STEPS TO REPRODUCE 1. start virt-manager 2. right click on the virt-manager icon OBSERVED RESULT no context menu is shown EXPECTED RESULT context menu with defined and running machines etc SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Debian GNU/Linux KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 441957] kleopatra: Creates unsafe ~/.gnupg when not already present
https://bugs.kde.org/show_bug.cgi?id=441957 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #1 from Norbert Preining --- Same on Debian, and same with 20.12 - 21.04 - 21.08 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 438017] Drawer generates a thin line on its window edge that consumes clicks without triggering any action
https://bugs.kde.org/show_bug.cgi?id=438017 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440992] main toolbar and session toolbar always visible if "remember window size" is unchecked
https://bugs.kde.org/show_bug.cgi?id=440992 --- Comment #4 from Norbert Junghenn --- (In reply to Ahmad Samir from comment #3) > It's most likely bug 430036, if you test with the latest commits in the > release/21.08 branch and you still see the issue described in this report, > feel free to reopen. > > FWIW, and email was sent to the distributions KDE mailing list notifying > distro packagers of those commits. > > *** This bug has been marked as a duplicate of bug 430036 *** Ok, you won. Bye. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440992] main toolbar and session toolbar always visible if "remember window size" is unchecked
https://bugs.kde.org/show_bug.cgi?id=440992 Norbert Junghenn changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 440992] main toolbar and session toolbar always visible if "remember window size" is unchecked
https://bugs.kde.org/show_bug.cgi?id=440992 Norbert Junghenn changed: What|Removed |Added CC||norbert.jungh...@gmail.com --- Comment #2 from Norbert Junghenn --- (In reply to Paul Worrall from comment #1) > > *** This bug has been marked as a duplicate of bug 430036 *** It is not. With konsole 21.08.0-1 the main toolbar is always visible and always in mode “Text alongside Icons”. Turning toolbar off, changing mode - all gone after exit and new start. Just for curiosity: Is there any form of testing done before konsole is released? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439719] New: I did my thing and once crashed out of Plasma
https://bugs.kde.org/show_bug.cgi?id=439719
Bug ID: 439719
Summary: I did my thing and once crashed out of Plasma
Product: plasmashell
Version: 5.22.2
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: norbertcserpnya...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
Application: plasmashell (5.22.2)
Qt Version: 5.15.2
Frameworks Version: 5.83.0
Operating System: Linux 5.13.0-1-default x86_64
Windowing System: X11
Drkonqi Version: 5.22.2
Distribution: "openSUSE Tumbleweed"
-- Information about the crash:
- What I was doing when the application crashed:
I was doing maintenance on the system when this incident happened, I think I
removed the application through the terminal.
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f5ed46f6880
(LWP 1577))]
[KCrash Handler]
#6 std::__uniq_ptr_impl >::_M_ptr (this=0x10) at
/usr/include/c++/11/bits/unique_ptr.h:173
#7 std::unique_ptr >::get (this=0x10) at
/usr/include/c++/11/bits/unique_ptr.h:422
#8 std::unique_ptr >::operator-> (this=0x10) at
/usr/include/c++/11/bits/unique_ptr.h:416
#9 qGetPtrHelper > const>
(ptr=std::unique_ptr = {...}) at
/usr/include/qt5/QtCore/qglobal.h:1135
#10 KService::d_func (this=0x0) at
/usr/src/debug/kservice-5.83.0-1.1.x86_64/src/services/kservice.h:608
#11 KService::isApplication (this=0x0) at
/usr/src/debug/kservice-5.83.0-1.1.x86_64/src/services/kservice.cpp:862
#12 0x7f5ea5964f09 in AppEntry::actions (this=0x5568f919a980) at
/usr/include/qt5/QtCore/qshareddata.h:161
#13 0x7f5ea5978154 in KAStatsFavoritesModel::Private::data
(this=0x7ffc55b69610, this@entry=0x5568f91071e0, item=..., role=role@entry=265)
at
/usr/src/debug/plasma5-workspace-5.22.2.1-1.1.x86_64/applets/kicker/plugin/kastatsfavoritesmodel.cpp:354
#14 0x7f5ea596eeb1 in PlaceholderModel::data (this=,
index=..., role=265) at
/usr/src/debug/plasma5-workspace-5.22.2.1-1.1.x86_64/applets/kicker/plugin/placeholdermodel.cpp:129
#15 0x7f5ed608bc7f in QModelIndex::data (arole=265, this=0x7ffc55b696e0) at
/usr/include/qt5/QtCore/qabstractitemmodel.h:460
#16 QQmlDMAbstractItemModelData::value (role=265, this=0x5568f7c23260) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.2.x86_64/src/qmlmodels/qqmladaptormodel.cpp:414
#17 QQmlDMCachedModelData::metaCall (this=0x5568f7c23260, call=,
id=, arguments=0x7ffc55b69790) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.2.x86_64/src/qmlmodels/qqmladaptormodel.cpp:282
#18 0x7f5ed85c5fe6 in QQmlPropertyData::readProperty
(property=0x7ffc55b69770, target=0x5568f7c23260, this=0x5568f9118528) at
../../include/QtQml/5.15.2/QtQml/private/../../../../../../src/qml/qml/qqmlpropertydata_p.h:357
#19 loadProperty (v4=0x5568f51be130, object=0x5568f7c23260, property=...) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.2.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:176
#20 0x7f5ed85e5f75 in QV4::Moth::VME::interpret (frame=0x7ffc55b69990,
engine=0x5568f51be130, code=0x7f5ea4cff67e ":\025H\003\344") at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.2.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:638
#21 0x7f5ed85ea7d7 in QV4::Moth::VME::exec
(frame=frame@entry=0x7ffc55b69990, engine=engine@entry=0x5568f51be130) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.2.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:463
#22 0x7f5ed857ea10 in QV4::ArrowFunction::virtualCall (fo=,
thisObject=, argv=, argc=) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.2.x86_64/src/qml/jsruntime/qv4functionobject.cpp:528
#23 0x7f5ed85f936a in QV4::FunctionObject::call (argc=2,
argv=0x7f5ec9011580, thisObject=0x7f5ec9011568, this=0x7ffc55b69a38) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.2.x86_64/src/qml/jsruntime/qv4functionobject_p.h:202
#24 QV4::Runtime::CallPropertyLookup::call (engine=0x5568f51be130, base=...,
index=, argv=0x7f5ec9011580, argc=2) at
/usr/src/debug/libqt5-qtdeclarative-5.15.2+kde29-1.2.x86_64/src/qml/jsruntime/qv4runtime.cpp:1460
#25 0x7f5ea7cfc6e1 in ?? ()
#26 0x in ?? ()
[Inferior 1 (process 1577) detached]
Possible duplicates by query: bug 418844, bug 413349, bug 411378, bug 411089,
bug 308053.
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 359932] Okular is very slow at opening some EPUB's
https://bugs.kde.org/show_bug.cgi?id=359932 Norbert Preining changed: What|Removed |Added CC||norb...@preining.info --- Comment #22 from Norbert Preining --- I can confirm the same behavior on Debian/unstable with Plasma 5.22.2, Okular 21.04.2, all native (no flatpak or other systems). I tried other viewers (mupdf, calibre ebook, atril) all of which worked without hiccup and much faster. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439108] Python files with "class" word in the beginning are classified as "text/x-modelica" (Modelica model)
https://bugs.kde.org/show_bug.cgi?id=439108 --- Comment #2 from Norbert --- Done. https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/164 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439108] New: Python files with "class" word in the beginning are classified as "text/x-modelica" (Modelica model)
https://bugs.kde.org/show_bug.cgi?id=439108 Bug ID: 439108 Summary: Python files with "class" word in the beginning are classified as "text/x-modelica" (Modelica model) Product: dolphin Version: 21.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: norbertzpil...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When the first line of Python file contains "class" keyword it's being recognized as Modelica model file not a Python file. When I leave 1st line empty and second line has class keyword it's normal. STEPS TO REPRODUCE 1. Create new python file, for ex. test.py 2. Type "class" in file and save it 3. The file changes icon and is recognized as text/x-modelica (Modelica model) OBSERVED RESULT Python file shown as Modelica model. EXPECTED RESULT Python file shown as Python file no matter the content. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.22.0 (but it started a while ago) KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
