[konsole] [Bug 447830] Reflow broken for strings without newline
https://bugs.kde.org/show_bug.cgi?id=447830 --- Comment #2 from Eric Armbruster --- Created attachment 145054 --> https://bugs.kde.org/attachment.cgi?id=145054&action=edit third Sorry for the spam but I did not know how I could add multiple attachments otherwise. how it should be = first.png four characters missing = second.png -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447830] Reflow broken for strings without newline
https://bugs.kde.org/show_bug.cgi?id=447830 --- Comment #1 from Eric Armbruster --- Created attachment 145053 --> https://bugs.kde.org/attachment.cgi?id=145053&action=edit four characters missing second attachment -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447830] New: Reflow broken for strings without newline
https://bugs.kde.org/show_bug.cgi?id=447830 Bug ID: 447830 Summary: Reflow broken for strings without newline Product: konsole Version: 21.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: eric1.armbrus...@gmail.com Target Milestone: --- Created attachment 145052 --> https://bugs.kde.org/attachment.cgi?id=145052&action=edit how it should be SUMMARY Konsole reflow is broken for strings without newline STEPS TO REPRODUCE 1. echo -n eyJhbGciOiJIUzI1NiJ9.eyJyb2xlcyI6W3siYXV0aG9yaXR5IjoiRElTUEFUQ0hFUiJ9XSwidXNlci1pZCI6IjYxY2MxYjkyODgwYTRlN2E5OGRmNDY2NyIsInN1YiI6ImFzZS1kZWxpdmVyeUBtYWZsbzMyMS5kZSIsImlzcyI6ImFzZTMzcHJvamVjdCIsImlhdCI6MTY0MTEzMDg1NSwiZXhwIjoxNjQxMTQ4ODU1fQ.KCUJwq8HVDFFKQjoUgzJziaDImy6yZywD_a1TccMB-8 (this jwt token does not contain production data) (first.png) 2. Press Ctrl + Left Arrow-> some characters went missing (second.png). Notice the last four characters are missing aswell. 3. Expand the window to the right again with the mouse -> all characters go missing (third.png) If you echo with trailing newline the same string and test with steps from above again reflow works as expected. OBSERVED RESULT reflow swallows a bunch of chars EXPECTED RESULT reflow should not swallow chars SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.12-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 447470] Grub menu tiny on high DPI display
https://bugs.kde.org/show_bug.cgi?id=447470 Eric Edlund changed: What|Removed |Added CC||j...@jriddell.org, ||neon-b...@kde.org, ||sit...@kde.org Product|kcm_grub2 |neon Assignee|konstantinos.smanis@gmail.c |neon-b...@kde.org |om | Component|General |Live/Install images --- Comment #2 from Eric Edlund --- (In reply to Bart from comment #1) Thank you. Changing that line does solve the problem. Just realized I'm barking up the wrong tree though, I'm after automating this on system installation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447477] Panel disappears after interacting with applet in tablet mode
https://bugs.kde.org/show_bug.cgi?id=447477 Eric Edlund changed: What|Removed |Added Flags||Usability+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447432] Cursor size inconsistent between windows on hi DPI display wayland
https://bugs.kde.org/show_bug.cgi?id=447432 Eric Edlund changed: What|Removed |Added Flags||Wayland+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447432] Cursor size inconsistent between windows on hi DPI display wayland
https://bugs.kde.org/show_bug.cgi?id=447432 --- Comment #1 from Eric Edlund --- Cursor size is set to 36 to reproduce. I had to reboot to update the size. When size is 48, the cursor is the same size on all windows. -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 443573] Problems with update of battery values
https://bugs.kde.org/show_bug.cgi?id=443573 Eric Donkersloot changed: What|Removed |Added CC||eric.donkersl...@gmail.com --- Comment #4 from Eric Donkersloot --- The bug described at comment #2 is still present on my system, confirmed on 5.23.4 Operating System: openSUSE Tumbleweed 20211222 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.8-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447477] New: Panel disappears after interacting with applet in tablet mode
https://bugs.kde.org/show_bug.cgi?id=447477 Bug ID: 447477 Summary: Panel disappears after interacting with applet in tablet mode Product: plasmashell Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ericedlund2...@gmail.com Target Milestone: 1.0 SUMMARY I'm on a 2 in 1 laptop and when I have it in tablet mode the bottom task panel is shown. Then after I interact with an applet, like pressing the battery applet to change brightness, the bar hides and I have to unfold my computer to get it back. STEPS TO REPRODUCE 1. Enter tablet mode 2. Interact with applet on dock OBSERVED RESULT Panel hides after interaction EXPECTED RESULT Panel remains visible. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 5.23 User Edition (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 447476] New: Polish - Panel not done composing when shown for the first time
https://bugs.kde.org/show_bug.cgi?id=447476 Bug ID: 447476 Summary: Polish - Panel not done composing when shown for the first time Product: plasmashell Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: ericedlund2...@gmail.com Target Milestone: 1.0 SUMMARY When I boot to the desktop, the panel automatically shows up before its done composing. STEPS TO REPRODUCE 1. Login to plasma session 2. Watch panel appear OBSERVED RESULT The applets item on the panel is initially displayed in the middle of the panel then slid to the right where it belongs. EXPECTED RESULT All panel items are in the correct position before the panel shows for the first time. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 5.23 User Edition (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447472] New: Animation into and out of grid view with multiple windows is jerky
https://bugs.kde.org/show_bug.cgi?id=447472 Bug ID: 447472 Summary: Animation into and out of grid view with multiple windows is jerky Product: kwin Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: effects-desktop-grid Assignee: kwin-bugs-n...@kde.org Reporter: ericedlund2...@gmail.com Target Milestone: --- SUMMARY When a desktop has multiple windows, immediately before and after the animation that gracefully pulls/pushes the user back to look at the grid, the windows are redrawn seemingly arbitrarily. STEPS TO REPRODUCE 0. Set desktop grid zoom duration to 1000 so its easy to see 1. Have multiple windows in a desktop 2. Use your shortcut to go into grid view 3. Go back to the desktop OBSERVED RESULT When zooming out, windows are instantly redrawn to their sorted position on the screen, then gracefully slid to their final position. When zooming in, windows are slid to incorrect positions, then instantly redrawn to their real positions once the animations over. EXPECTED RESULT Windows are gracefully slid to and from their actual positions during the animation. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 5.23 User Edition (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 447471] New: Pixelated boot screen on hi DPI display
https://bugs.kde.org/show_bug.cgi?id=447471 Bug ID: 447471 Summary: Pixelated boot screen on hi DPI display Product: Breeze Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Plymouth Assignee: plasma-b...@kde.org Reporter: ericedlund2...@gmail.com CC: sit...@kde.org Target Milestone: --- Created attachment 144832 --> https://bugs.kde.org/attachment.cgi?id=144832&action=edit Image of boot screen SUMMARY The boot screen (image attached) is pixelated on my 144 DPI display. STEPS TO REPRODUCE 1. Boot KDE Neon on hi DPI sidplay OBSERVED RESULT The boot screen is blurry. It appears to be scaled correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 5.23 User Edition (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kcm_grub2] [Bug 447470] New: Grub menu tiny on high DPI display
https://bugs.kde.org/show_bug.cgi?id=447470 Bug ID: 447470 Summary: Grub menu tiny on high DPI display Product: kcm_grub2 Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: General Assignee: konstantinos.sma...@gmail.com Reporter: ericedlund2...@gmail.com Target Milestone: --- Created attachment 144831 --> https://bugs.kde.org/attachment.cgi?id=144831&action=edit Image of the grub menu SUMMARY I have a hi DPI display (144) and the grub menu is not scaling. (see picture) STEPS TO REPRODUCE 1. Boot to grub menu on hi dpi display OBSERVED RESULT The menu is tiny. The text is clear, but ignoring dpi. EXPECTED RESULT A menu that doesn't hurt to read SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon User Edition 5.23 (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447469] New: After display scale is reverted the scale slider is not updated to old setting
https://bugs.kde.org/show_bug.cgi?id=447469 Bug ID: 447469 Summary: After display scale is reverted the scale slider is not updated to old setting Product: systemsettings Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: ericedlund2...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY After display scale is reverted the scale slider is not updated to old setting STEPS TO REPRODUCE 1. Display Configuration menu in settings 2. Change scale and apply 3. Revert changes OBSERVED RESULT The scale slider isn't updated SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE NEON 5.23 (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447467] New: Xwayland windows blurry on hi DPI display wayland
https://bugs.kde.org/show_bug.cgi?id=447467 Bug ID: 447467 Summary: Xwayland windows blurry on hi DPI display wayland Product: kwin Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ericedlund2...@gmail.com Target Milestone: --- SUMMARY xwayland windows more blurry when I set global scale farther from 100% STEPS TO REPRODUCE 1. On hi DPI display, set global scale to 150 or 200% (on wayland session) 2. Open Chrome window, or even the system task bar OBSERVED RESULT The window is blurry EXPECTED RESULT The window isn't blurry SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.23 User edition (available in About System) KDE Plasma Version: 2.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447465] New: Xwayland windows blurry on hi DPI display wayland
https://bugs.kde.org/show_bug.cgi?id=447465 Bug ID: 447465 Summary: Xwayland windows blurry on hi DPI display wayland Product: kwin Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ericedlund2...@gmail.com Target Milestone: --- Created attachment 144829 --> https://bugs.kde.org/attachment.cgi?id=144829&action=edit Pictures of system at different scales. Application in background is musescore but same effect happening on other windows. SUMMARY xwayland windows more blurry when I set global scale farther from 100% STEPS TO REPRODUCE 1. On hi DPI display, set global scale to 150 or 200% (on wayland session) 2. Open Chrome window, or even the system task bar OBSERVED RESULT The window is blurry EXPECTED RESULT The window isn't blurry SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.23 User edition (available in About System) KDE Plasma Version: 2.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447432] Cursor size inconsistent between windows on hi DPI display wayland
https://bugs.kde.org/show_bug.cgi?id=447432 Eric Edlund changed: What|Removed |Added CC||ericedlund2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447432] New: Cursor size inconsistent between windows on hi DPI display wayland
https://bugs.kde.org/show_bug.cgi?id=447432 Bug ID: 447432 Summary: Cursor size inconsistent between windows on hi DPI display wayland Product: kwin Version: 5.23.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: ericedlund2...@gmail.com Target Milestone: --- Created attachment 144810 --> https://bugs.kde.org/attachment.cgi?id=144810&action=edit Pictures of over system vs other window SUMMARY I'm on an Acer Spin 5 with a 144 dpi display using wayland. The cursor scale is inconsistent. STEPS TO REPRODUCE 1. Using breeze cursor theme on Hi DPI display (144) 2. Move cursor from a chrome window (or Firefox, or spotify) to the desktop (or the system settings app, or krunner) OBSERVED RESULT Cursor becomes larger on system apps. EXPECTED RESULT Cursor size remains consistent SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon 5.23 User Edition (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447207] New: Touchpad config fails to save "Disable touchpad when typing"
https://bugs.kde.org/show_bug.cgi?id=447207 Bug ID: 447207 Summary: Touchpad config fails to save "Disable touchpad when typing" Product: systemsettings Version: 5.23.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: subscri...@blackbrook.org Target Milestone: --- SUMMARY If I change the state of this checkbox and click apply, then exit and reopen the config menu, the state of the checkbox is reverted to what it was before my change. Other config params in the touchpad config do save, like "Maximum time for double tap." It also fails to write the parameter "DisableOnKeyboardActivity" to ~/.config/touchpadrc, though it seems to read this parameter as the state of the checkbox reflects this being set "=true" or "=false". STEPS TO REPRODUCE 1. Open Input Devices in System Settings 2. Choose touchpad 3. Choose Enable/Disable Touchpad tab 4. Change state of Disable touchpad when typing checkbox 5. Click Apply 6. Close window 7. Reopen, following steps 1 - 3 again. OBSERVED RESULT The state of the checkbox has reverted to before the change made EXPECTED RESULT The checkbox state remains, and is reflected in a change to ~/.config/touchpadrc SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.23.4 (openSuse Tumbleweed) (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 447195] New: Turning phone screen off kills the app
https://bugs.kde.org/show_bug.cgi?id=447195 Bug ID: 447195 Summary: Turning phone screen off kills the app Product: kdeconnect Version: unspecified Platform: Other OS: iOS Status: REPORTED Severity: normal Priority: NOR Component: ios-application Assignee: lucas.w...@tuta.io Reporter: dio.eri...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open the app on iOS 2. Refresh Discovery 3. Device shows on desktop app, can see battery level. 4. Turn phone screen off 5. Can’t se battery level anymore. OBSERVED RESULT Can’t interact with the phone if the screen is turned off (i. e. leaving it on the table next to me) EXPECTED RESULT Being able to see battery level and send commands/files even when on standby. SOFTWARE/OS VERSIONS Windows: Windows 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Mouse control is choppy but I’m not sure if this should be reported as a bug. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 446896] New: Crashed when installing Dolphin plugins from apps.kde.org
https://bugs.kde.org/show_bug.cgi?id=446896
Bug ID: 446896
Summary: Crashed when installing Dolphin plugins from
apps.kde.org
Product: Discover
Version: 5.23.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Flatpak Backend
Assignee: lei...@leinir.dk
Reporter: eric1.armbrus...@gmail.com
CC: aleix...@kde.org, jgrul...@redhat.com
Target Milestone: ---
SUMMARY Discover crashed when installing Dolphin Plugins from apps.kde.org
STEPS TO REPRODUCE
1. Go to https://apps.kde.org/dolphin_plugins/
2. Select "Install on Linux"
3. Select Discover in Firefox to handle the request.
OBSERVED RESULT
Discover crashed. Here is my system information:
EXPECTED RESULT
Discover does not crash
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20211209
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
Kernel Version: 5.15.6-1-default (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics
Memory: 14.4 GiB of RAM
Graphics Processor: AMD RENOIR
ADDITIONAL INFORMATION
Could not report this via Dr. Konqi, because apparently Discover is not a KDE
application (I will file a separate bug for that). This is just as an info that
this might be a duplicate, even though I did some searching.
Application: plasma-discover (5.23.4)
Qt Version: 5.15.2
Frameworks Version: 5.88.0
Operating System: Linux 5.15.6-1-default x86_64
Windowing System: X11
Distribution: "openSUSE Tumbleweed"
DrKonqi: 5.23.4 [KCrashBackend]
-- Information about the crash:
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 FlatpakBackend::findSource(_FlatpakInstallation*, QString const&) const
(origin=..., installation=0x7faba4012f30 [FlatpakInstallation],
this=0x5567d98fa100) at
/usr/src/debug/discover-5.23.4-1.1.x86_64/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:113
#7 FlatpakBackend::getAppForInstalledRef(_FlatpakInstallation*,
_FlatpakInstalledRef*) const (this=0x5567d98fa100, installation=0x7faba4012f30
[FlatpakInstallation], ref=0x7fab8434ecd0 [FlatpakInstalledRef]) at
/usr/src/debug/discover-5.23.4-1.1.x86_64/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:352
#8 0x7fabbc0318bd in operator() (__closure=0x5567d988b790) at
/usr/src/debug/discover-5.23.4-1.1.x86_64/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:1276
#9 QtPrivate::FunctorCall, QtPrivate::List<>, void,
FlatpakBackend::search(const AbstractResourcesBackend::Filters&)::
>::call (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#10 QtPrivate::Functor, 0>::call,
void> (arg=, f=...) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#11 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>,
void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *)
(which=, this_=0x5567d988b780, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#12 0x7fac39242fee in QObject::event(QEvent*) (this=0x5567d98fa100,
e=0x5567d9b7c5f0) at kernel/qobject.cpp:1314
#13 0x7fac3a46da7f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5567d98fa100, e=0x5567d9b7c5f0) at
kernel/qapplication.cpp:3632
#14 0x7fac392169fa in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5567d98fa100, event=0x5567d9b7c5f0) at
kernel/qcoreapplication.cpp:1064
#15 0x7fac39219a47 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) (receiver=0x0, event_type=0, data=0x5567d93fc050) at
kernel/qcoreapplication.cpp:1821
#16 0x7fac3926e853 in postEventSourceDispatch(GSource*, GSourceFunc,
gpointer) (s=s@entry=0x5567d94e9b50) at kernel/qeventdispatcher_glib.cpp:277
#17 0x7fac379e5d4f in g_main_dispatch (context=0x7fac2c005000) at
../glib/gmain.c:3381
#18 g_main_context_dispatch (context=0x7fac2c005000) at ../glib/gmain.c:4099
#19 0x7fac379e60d8 in g_main_context_iterate
(context=context@entry=0x7fac2c005000, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4175
#20 0x7fac379e618f in g_main_context_iteration (context=0x7fac2c005000,
may_block=1) at ../glib/gmain.c:4240
#21 0x7fac3926ded4 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5567d94e5490, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#22 0x7fac392153fb in
QEventLoop::exec(QFlags)
(this=this@entry=0x7ffd4c97faa0, flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#23 0x7fac3921d6e0 in QCoreApplication::exec() () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#24 0x7fac3966718c in QGuiApplication::exec() () at
kernel/qguiapplication.cpp:1867
#25 0x7fac3a46d9f5 in QApplication::exec() ()
[kmines] [Bug 446780] New: Losing a game should produce a new random grid
https://bugs.kde.org/show_bug.cgi?id=446780 Bug ID: 446780 Summary: Losing a game should produce a new random grid Product: kmines Version: 4.0.21081 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dim...@gmail.com Reporter: johne...@waf.io CC: kde-games-b...@kde.org Target Milestone: --- SUMMARY After losing a game, "Reset the Game" gives the exact same grid again. It is therefore trivial to make a high score by memorizing the grid or taking a screenshot. The grid should be randomized. STEPS TO REPRODUCE 1. Lose a game, then remember which cells have mines 2. Select "Yes" on the dialog "Reset the Game" 3. Click one of the previous cells where mines are located. The grid is exactly the same, and the game is immediately lost. OBSERVED RESULT After losing a game, there is never a new grid. To generate a new grid, one should switch to a game with a different difficulty level and then back to the previous difficulty. EXPECTED RESULT Randomize the grid. The method `void MineFieldItem::resetMines()` should probably call `MineFieldItem::generateField` (or a some other method that reads `random`). SOFTWARE/OS VERSIONS Linux Kubuntu Impish KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446195] New: Plasmashell crashes after changing the wallpaper from slideshow to plain color
https://bugs.kde.org/show_bug.cgi?id=446195 Bug ID: 446195 Summary: Plasmashell crashes after changing the wallpaper from slideshow to plain color Product: plasmashell Version: 5.22.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: johne...@waf.io Target Milestone: 1.0 STEPS TO REPRODUCE 1. Right-click on the desktop, configure the wallpaper to a folder view to a slideshow (1 hour for example), apply and close the dialog 2. Right-click on the desktop, configure the wallpaper to a plain color (keep the folder view), apply and close the dialog 3. Right-click on the desktop: plasma crashes OBSERVED RESULT Crash in plasmashell EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.22.5 on Ubuntu 21.10 (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.12.5 ADDITIONAL INFORMATION #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140405159598464) at pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140405159598464) at pthread_kill.c:80 #2 __GI___pthread_kill (threadid=140405159598464, signo=signo@entry=6) at pthread_kill.c:91 #3 0x7fb2a3b30476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7fb2a3b167b7 in __GI_abort () at abort.c:79 #5 0x7fb2a3db3a31 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #6 0x7fb2a3dbf4ec in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7fb2a3dbf557 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7fb2a3dbf7f9 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7fb2a3fbcf85 in qBadAlloc() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb2a3fbf834 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fb2a4ed9e80 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7fb2a4ed9f81 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fb2a4f07769 in QWidget::insertAction(QAction*, QAction*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7fb2a4f078b6 in QWidget::addActions(QList) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7fb29c526797 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #16 0x7fb29c5275de in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/plasma/scriptengines/plasma_appletscript_declarative.so #17 0x7fb2a5c213c8 in QQuickItem::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #18 0x7fb2a4ece6b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7fb2a41e616a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fb2a5c3dd56 in QQuickWindowPrivate::deliverMatchingPointsToItem(QQuickItem*, QQuickPointerEvent*, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #21 0x7fb2a5c3eef7 in QQuickWindowPrivate::deliverPressOrReleaseEvent(QQuickPointerEvent*, bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #22 0x7fb2a5c3fced in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #23 0x7fb2a5c40f6f in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #24 0x7fb2a45d7515 in QWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #25 0x7fb2a4ece6b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7fb2a41e616a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7fb2a45cb257 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #28 0x7fb2a45a09bc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #29 0x7fb29f12bb9e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #30 0x7fb2a26218bb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #31 0x7fb2a2674f08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #32 0x7fb2a261f003 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x7fb2a423f548 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7fb2a41e4a9b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7fb2a41ed024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #36 0x560145d53e0c in ?? () #37 0x7fb2a3b17fd0 in __libc_start_call_main (main=main@entry=0x560145d52ec
[Discover] [Bug 445698] Upon clicking the "Updates Available" system tray icon, Discover loads and gets the updates. The list of updates repeatedly "blinks" or refreshes. Clicking "Update All" or "Che
https://bugs.kde.org/show_bug.cgi?id=445698 --- Comment #3 from Eric R --- I tried to generate one at the time with the Crash Report tool, but it didn't. The crash hasn't happened for about a week, and I have done a couple of successful updates since then, including one just now. I read the link about backtraces, and I made sure I have GDM and coredumctl installed. coredumpctl didn't get me anything just now. So, if it happens again, I'll try to get you a backtrace or a coredump so you have something to work with. Meanwhile, it seems that I can work around this on the command line with `pkcon update`, `flatpak update`, and `snap refresh`. Recently, I have seen at least a couple other people asking on Reddit about this same behavior, I think in r/kde or r/kdeneon IIRC. I don't think any of them had any more info than I do, though. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445698] Upon clicking the "Updates Available" system tray icon, Discover loads and gets the updates. The list of updates repeatedly "blinks" or refreshes. Clicking "Update All" or "Che
https://bugs.kde.org/show_bug.cgi?id=445698 --- Comment #1 from Eric R --- Update: I also couldn’t update with pkcon. Pkcon seemed to hang and “sit and spin” for about a half-hour at the “Running” phase of the update. I updated my flatpaks on the command line, and then I tried pkcon again, and pkcon still seemed stuck. So I tried Discover again, and it worked. It seemed to install the updates unusually quickly. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 445698] New: Upon clicking the "Updates Available" system tray icon, Discover loads and gets the updates. The list of updates repeatedly "blinks" or refreshes. Clicking "Update All" or
https://bugs.kde.org/show_bug.cgi?id=445698 Bug ID: 445698 Summary: Upon clicking the "Updates Available" system tray icon, Discover loads and gets the updates. The list of updates repeatedly "blinks" or refreshes. Clicking "Update All" or "Check for Updates" doesn't seem to do anything. Product: Discover Version: 5.23.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: aer0...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 143694 --> https://bugs.kde.org/attachment.cgi?id=143694&action=edit Discover's Updates list repeatedly refreshing SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Click "Updates" in system tray 2. Wait for Discover to get updates OBSERVED RESULT Discover's Updates list blinks/refreshes repeatedly. Clicking "Update All" does nothing. Discover eventually crashes. EXPECTED RESULT Discover's Updates list shows, and allows user to click the "Update All" button to update packages. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.23.3 (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445100] New: Wake the screen when backspace is pressed
https://bugs.kde.org/show_bug.cgi?id=445100 Bug ID: 445100 Summary: Wake the screen when backspace is pressed Product: plasmashell Version: 5.22.5 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: johne...@waf.io CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY Wake the screen and show the password prompt when the backspace key is pressed STEPS TO REPRODUCE 1. lock the screen 2. press the backspace key 3. nothing appears (except confusion) OBSERVED RESULT The screen stays off and the password prompt does not appear EXPECTED RESULT The prompt for the entering the password should appear (it happens with the escape, shift or control keys). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.22.5 (Kubuntu Impish) (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION I do not always lock my screen, and I usually have a terminal running. Typing the password directly can accidentally enter it in unwanted apps, so I press the backspace key instead (which works on many other systems and screen lockers). While the backspace is really the one that I miss, I believe that any other key should also activate the screen locker. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 444725] New: Inserting ShuttleXpress into USB port while Kdenlive runnign causes kdenlive to crash
https://bugs.kde.org/show_bug.cgi?id=444725 Bug ID: 444725 Summary: Inserting ShuttleXpress into USB port while Kdenlive runnign causes kdenlive to crash Product: kdenlive Version: 21.08.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ericsbinarywo...@gmail.com Target Milestone: --- SUMMARY As part of my previous bug report, I wanted to check the ShuttleXpress in a different USB port in case that was the cause of the issue. I disconnected it from one port and put it into another and that caused Kdenlive to crash. STEPS TO REPRODUCE 1. Have ShuttleXpress plugged into USB port 2. Have Kdenlive running 3. Disconnect ShuttleXpress 4. Plus ShuttleXpress into new USB port OBSERVED RESULT Kdenlive crashes EXPECTED RESULT Kdenlive doesn't crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION previous bug I mention is bug #444724 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 444724] New: ShuttleXpress buttons do not work
https://bugs.kde.org/show_bug.cgi?id=444724 Bug ID: 444724 Summary: ShuttleXpress buttons do not work Product: kdenlive Version: 21.08.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ericsbinarywo...@gmail.com Target Milestone: --- SUMMARY ShuttleXpress jog wheels both work, but buttons do not work. They are defined in the settings. They worked in the past. STEPS TO REPRODUCE 1. Define actions for buttons on the ShuttleXpress 2. Attempt to use them within Kdenlive 3. Nothing happens OBSERVED RESULT Pushing buttons does nothing EXPECTED RESULT Whatever the buttons were defined to do SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 444136] New: Konsole window upon reload has vertical height too small on my 3 monitor setup with panel in middle screen
https://bugs.kde.org/show_bug.cgi?id=444136 Bug ID: 444136 Summary: Konsole window upon reload has vertical height too small on my 3 monitor setup with panel in middle screen Product: konsole Version: 21.08.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: ericrfonta...@hotmail.com Target Milestone: --- Created attachment 142686 --> https://bugs.kde.org/attachment.cgi?id=142686&action=edit how Konsole looks when I reopen it SUMMARY Konsole window upon reload has vertical height too small on my 3 monitor setup with panel in middle screen. STEPS TO REPRODUCE Glitch happens when I have konsole's "Remember Window Size" checked in preferences (as is default), but doesn't happen if I unchecked that setting. I have a 3-monitor setup*: - Screen 0: DP 1080x1920 (vertical orientation on right) - Screen 1: HDMI 1280x1024 (on left) - Screen 2: DVI-D 2560x1600 (primary in middle, with panel) The first time I opened Konsole, it is fine. However upon reopening it, the glitch happens... OBSERVED RESULT When konsole is closed, the file .config/konsolerc is created with what I believe are buggy settings: [Desktop Entry] DefaultProfile=Profile 1.profile [MainWindow] DVI-D-0 DisplayPort-0 HDMI-A-0 XPosition 2560x1600=2269 DVI-D-0 DisplayPort-0 HDMI-A-0 YPosition 2560x1600=29 RestorePositionForNextInstance=false State=/wD9BTcYBAQICPwBAgIWAG0AYQBpAG4AVABvAG8AbABCAGEAcgEA/wAAHABzAGUAcwBzAGkAbwBuAFQAbwBvAGwAYgBhAHIBAAAFD/8AAA== StatusBar=Disabled ToolBarsMovable=Disabled At this point if I open konsole again, its window height is very short...can only see about half a row of the terminal (see attached konsole-resize.png). However if I delete that konsolerc file before opening konsole again, it displays fine. So the bug seems to be in how this file is saved when I have my particular monitor setup. *for reference here is output of xrandr (which I configured using KDE's Display Configuration gui) so you know exactly my screen settings: Screen 0: minimum 320 x 200, current 4920 x 1920, maximum 16384 x 16384 DisplayPort-0 connected 1080x1920+3840+0 left (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.00*+ 59.94 1680x1050 59.95 1600x900 60.00 1280x1024 75.0260.02 1440x900 59.89 1280x800 59.81 1152x864 75.00 1280x720 60.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 640x480 75.0072.8166.6760.0059.94 720x400 70.08 HDMI-A-0 connected 1280x1024+0+576 (normal left inverted right x axis y axis) 375mm x 300mm 1280x1024 60.02*+ 75.02 1920x1080 60.0050.0059.94 1280x800 60.02 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 DVI-D-0 connected primary 2560x1600+1280+0 (normal left inverted right x axis y axis) 641mm x 401mm 2560x1600 59.86* 1280x800 59.91 EXPECTED RESULT Konsole remembers my window size. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.23 User Edition (fresh install https://files.kde.org/neon/images/user/20211014-1524/neon-user-20211014-1524.iso) on Linux v5.11.0-38-generic (#42~20.04.1-Ubuntu SMP Tue Sep 28 20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux) KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I login to KDE plasma with X as is the default, not wayland. I can work around the bug by simply disabling that checkmark in preferences to remember window size. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 --- Comment #4 from Eric Fontaine --- Created attachment 142646 --> https://bugs.kde.org/attachment.cgi?id=142646&action=edit New crash information added by DrKonqi plasmashell (5.23.1) using Qt 5.15.3 - What I was doing when the application crashed: did another update and reboot and same crash -- Backtrace (Reduced): #4 0x7f50a87647c4 in Plasma::WindowThumbnail::updatePaintNode (this=0x55a2ddf09ee0, oldNode=, updatePaintNodeData=) at ./src/declarativeimports/core/windowthumbnail.cpp:327 #5 0x7f5103ced380 in QQuickWindowPrivate::updateDirtyNode (this=0x55a2db25e880, item=0x55a2ddf09ee0) at items/qquickwindow.cpp:3872 #6 0x7f5103cedc3b in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x55a2db25e880) at items/qquickwindow.cpp:3617 #7 0x7f5103cef330 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x55a2db25e880) at items/qquickwindow.cpp:524 #8 0x7f5103c8ce97 in QSGRenderThread::sync (this=this@entry=0x55a2dc63f8a0, inExpose=inExpose@entry=false, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:647 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 --- Comment #3 from Eric Fontaine --- Created attachment 142645 --> https://bugs.kde.org/attachment.cgi?id=142645&action=edit New crash information added by DrKonqi plasmashell (5.23.1) using Qt 5.15.3 - What I was doing when the application crashed: did another update and rebooted and got the same exact crash when mousing over the bottom panel on my fresh 23.1 install. -- Backtrace (Reduced): #4 0x7ff9501647c4 in Plasma::WindowThumbnail::updatePaintNode (this=0x55fd51b251b0, oldNode=, updatePaintNodeData=) at ./src/declarativeimports/core/windowthumbnail.cpp:327 #5 0x7ff98c694380 in QQuickWindowPrivate::updateDirtyNode (this=0x55fd4ec3bed0, item=0x55fd51b251b0) at items/qquickwindow.cpp:3872 #6 0x7ff98c694c3b in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x55fd4ec3bed0) at items/qquickwindow.cpp:3617 #7 0x7ff98c696330 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x55fd4ec3bed0) at items/qquickwindow.cpp:524 #8 0x7ff98c633e97 in QSGRenderThread::sync (this=this@entry=0x55fd4efcf930, inExpose=inExpose@entry=false, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:647 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 --- Comment #2 from Eric Fontaine --- Created attachment 142643 --> https://bugs.kde.org/attachment.cgi?id=142643&action=edit New crash information added by DrKonqi plasmashell (5.23.1) using Qt 5.15.3 - What I was doing when the application crashed: same thing I did in my last crash, though I had now installed updates and rebooted. It seems the botttom panel is cursed somehow. -- Backtrace (Reduced): #4 0x7f271818f7c4 in Plasma::WindowThumbnail::updatePaintNode (this=0x559e27ab2eb0, oldNode=, updatePaintNodeData=) at ./src/declarativeimports/core/windowthumbnail.cpp:327 #5 0x7f2766d76380 in QQuickWindowPrivate::updateDirtyNode (this=0x559e263124e0, item=0x559e27ab2eb0) at items/qquickwindow.cpp:3872 #6 0x7f2766d76c3b in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x559e263124e0) at items/qquickwindow.cpp:3617 #7 0x7f2766d78330 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x559e263124e0) at items/qquickwindow.cpp:524 #8 0x7f2766d15e97 in QSGRenderThread::sync (this=this@entry=0x559e266ed100, inExpose=inExpose@entry=false, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:647 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 Eric Fontaine changed: What|Removed |Added CC||ericrfonta...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 --- Comment #1 from Eric Fontaine --- Created attachment 142641 --> https://bugs.kde.org/attachment.cgi?id=142641&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444068] New: fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button
https://bugs.kde.org/show_bug.cgi?id=444068 Bug ID: 444068 Summary: fresh install KDE neon testing 23.1, bottom panel chrashes whenever I try to press bottom-left button Product: plasmashell Version: 5.23.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ericrfonta...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.23.1) Qt Version: 5.15.3 Frameworks Version: 5.88.0 Operating System: Linux 5.11.0-38-generic x86_64 Windowing System: X11 Distribution: KDE neon Testing Edition DrKonqi: 5.23.1 [CoredumpBackend] -- Information about the crash: - What I was doing when the application crashed: fresh install KDE neon testing 23.1, all I had done was setup my 3 monitors with display and add Konsole and chromium to bottom panel. Whenever I press bottom left button, the panel crashes. The crash can be reproduced every time. -- Backtrace (Reduced): #3 0x7f81442b37c4 in Plasma::WindowThumbnail::updatePaintNode (this=0x561d4b2b85a0, oldNode=, updatePaintNodeData=) at ./src/declarativeimports/core/windowthumbnail.cpp:327 #4 0x7f81893da380 in QQuickWindowPrivate::updateDirtyNode (this=0x561d4a012bb0, item=0x561d4b2b85a0) at items/qquickwindow.cpp:3872 #5 0x7f81893dac3b in QQuickWindowPrivate::updateDirtyNodes (this=this@entry=0x561d4a012bb0) at items/qquickwindow.cpp:3617 #6 0x7f81893dc330 in QQuickWindowPrivate::syncSceneGraph (this=this@entry=0x561d4a012bb0) at items/qquickwindow.cpp:524 #7 0x7f8189379e97 in QSGRenderThread::sync (this=this@entry=0x561d4a4c6b60, inExpose=inExpose@entry=false, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:647 Possible duplicates by query: bug 444015, bug 437811, bug 435618, bug 430276, bug 427426. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 119539] Request: Support for multiple genres / artists / composers / etc.
https://bugs.kde.org/show_bug.cgi?id=119539 --- Comment #63 from Eric S --- That problem in inherent to using any character for separating values. You just happen to be able to think of an example for "/" but there is no reason an artist, genre, etc could not have a comma in their name. In fact, here's one that occurred to me before finishing this comment. "Peter, Paul and Mary." But whether or not we can think of example for a character is irrelevant, it is always going to be potential for any character, and so the user will need a way to elect whether or not a given character is used that way, and a either way for a user to escape such characters in their metadata or a way to list exclusions, or some such solution. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 141991] custom metadata readout and creation (id3v2)
https://bugs.kde.org/show_bug.cgi?id=141991 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #13 from Eric S --- If this were implemented would the ability to search on such custom fields automatically come with it, or should that be another feature request? I'd love to be able to search by conductor. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 119539] Request: Support for multiple genres / artists / composers / etc.
https://bugs.kde.org/show_bug.cgi?id=119539 Eric S changed: What|Removed |Added CC||subscri...@blackbrook.org --- Comment #61 from Eric S --- Use of slash (/) is very common for separating multiple artist names also, e.g. "Alice / Bob" -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 443747] New: Konsole crashes on Wayland resume from sleep
https://bugs.kde.org/show_bug.cgi?id=443747 Bug ID: 443747 Summary: Konsole crashes on Wayland resume from sleep Product: konsole Version: 20.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: eric.d.can...@gmail.com Target Milestone: --- Application: konsole (20.12.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.0-37-generic x86_64 Windowing System: Wayland Drkonqi Version: 5.21.4 Distribution: Ubuntu 21.04 -- Information about the crash: - What I was doing when the application crashed: I resumed my Wayland session from sleep, and Konsole crashed immediately. As part of this resume, I changed the input sources of my two monitors. It seems that re-engaging with the two displays sometimes causes problems (Plasma panels move around my desktop, eg.). The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7f2ee1250864 in __GI_abort () at abort.c:79 #6 0x7f2ee14a6c77 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2edc3d3d39 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #8 0x7f2edc3e2f9a in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #9 0x7f2ee1706600 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f2ee1709be3 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f2ee170a413 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f2ee0612783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f2ee16ce7ba in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2ee1728e05 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f2edf2af8eb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f2edf302d28 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7f2edf2ad023 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f2ee1728204 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f2ee16cd11b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7f2ee16d5604 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f2ee1a3c95f in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_konsole.so #22 0x7f2ee1252565 in __libc_start_main (main=0x558ebcc0a320, argc=3, argv=0x7ffedd7243a8, init=, fini=, rtld_fini=, stack_end=0x7ffedd724398) at ../csu/libc-start.c:332 #23 0x558ebcc0a35e in _start () [Inferior 1 (process 1827) detached] The reporter indicates this bug may be a duplicate of or related to bug 421115. Possible duplicates by query: bug 440777, bug 440619, bug 440257, bug 436327, bug 432327. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 399249] Add support for scrobbling to last.fm
https://bugs.kde.org/show_bug.cgi?id=399249 Eric Mesa changed: What|Removed |Added Version|0.3.0 |21.08.1 --- Comment #6 from Eric Mesa --- still an issue on 21.08 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442166] wipe effect not applied when rendering in windows
https://bugs.kde.org/show_bug.cgi?id=442166 --- Comment #2 from e...@loquiz.com --- Hi, thanks for the comment. I had updated the app from previous version. uninstalling the app and deleting the directory (just in case) and then installing version 21.08.1 again fixed the issue. So it was a problem with my setup. The issue is fully resolved for me. Thanks and sorry for making noise too early. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442166] New: wipe effect not applied when rendering in windows
https://bugs.kde.org/show_bug.cgi?id=442166 Bug ID: 442166 Summary: wipe effect not applied when rendering in windows Product: kdenlive Version: 21.08.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: e...@loquiz.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. create a project 2. add two videos overlapping 3. add wipe effect OBSERVED RESULT wipe effect shows inside KDE, but after rendering with MP4-H264 profile it does not show wipe effect. Issue appears in 21.08.0 and 21.08.1 windows versions both standalone and installed. It works correctly on 21.04 version EXPECTED RESULT wipe effect added to rendered outcome as well. SOFTWARE/OS VERSIONS Windows: 10 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.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #18 from Eric Moret --- I can still reproduce this problem with latest build as of 9/1/2021 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861
--- Comment #45 from Eric Donkersloot ---
I'm affected as well. Unfortunately this happens most of the time when logging
in and it's a huge deal breaker for me. My Lenovo X1carbon gen6 is connected to
an external 27" Dell monitor but has its own internal panel disabled
("clamshell mode"). Let me know if I have to provide moer information.
Operating System: Arch Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.13.13-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15,5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Eric Donkersloot changed: What|Removed |Added CC||eric.donkersl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #15 from Eric Moret --- Sorry for a noob question, how can I test this change? Should I wait for the next version of Digikam to come out or is there a better/faster way? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 440991] Upgrade to Kernel 5.11.0-25 with Nvidia 340.108 Fails to Show UI Login
https://bugs.kde.org/show_bug.cgi?id=440991 --- Comment #1 from Eric R --- Hi. I found [this thread on the Nvidia Linux Dev Forums] (https://forums.developer.nvidia.com/t/nvidia-340-108-driver-kernel-5-11-support/182663) ...that points out incompatibility between nvidia-340.108 and the 5.11.x kernel. I will report my bug there. It looks like Nvidia has been notified, but they don't seem to be doing anything about it at the moment. I have uninstalled `nvidia-340` and gone back to the nouveau driver, and all seems well in Neon 5.22.4 with the 5.11.0-27 kernel (updated since I reported this). I don't know if any further action is required here, other than watching for an update to nvidia-340. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 --- Comment #7 from Eric Moret --- Created attachment 140898 --> https://bugs.kde.org/attachment.cgi?id=140898&action=edit Terminal Output macOS 11.5.2, Digikam 7.3.0, network path not working -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 438845] The storage location of this image is currently not available
https://bugs.kde.org/show_bug.cgi?id=438845 Eric Moret changed: What|Removed |Added CC||eric.mo...@gmail.com --- Comment #5 from Eric Moret --- I have the same problem running on macOS BigSur 11.5.2 with Digikam 7.3.0. The workaround described in https://bugs.kde.org/show_bug.cgi?id=438845#c4 is only fixing it temporarily. A more reliable way to access network share from MacOS would be better. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436939] startkde: "Could not start Plasma session" xmessage in Wayland session in VirtualBox
https://bugs.kde.org/show_bug.cgi?id=436939 Eric R changed: What|Removed |Added CC||aer0...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 440991] Upgrade to Kernel 5.11.0-25 with Nvidia 340.108 Fails to Show UI Login
https://bugs.kde.org/show_bug.cgi?id=440991 Eric R changed: What|Removed |Added CC||aer0...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 440991] New: Upgrade to Kernel 5.11.0-25 with Nvidia 340.108 Fails to Show UI Login
https://bugs.kde.org/show_bug.cgi?id=440991 Bug ID: 440991 Summary: Upgrade to Kernel 5.11.0-25 with Nvidia 340.108 Fails to Show UI Login Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: aer0...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Today I updated Neon 5.22.4, using Discover, and after the installation(s) and reboot(s), laptop froze on Neon startup splash. I was able to Alt-F2 to log in via CLI. I found a [thread on the Neon forums](https://forum.kde.org/viewtopic.php?f=309&t=172175&sid=683dca1e932bc55ef0216b2f1b9c2539) that suggested there is a problem with the Nvidia 340.108 driver under Kernel 5.11.0-25, and to use the Grub menu to boot to Kernal 5.8.0-63 instead. This workaround has allowed me to log into Plasma. STEPS TO REPRODUCE 1. Apply current updates in Discover 2. Allow machine to install and reboot OBSERVED RESULT Neon Boot Splash freezes, but I can Alt-F2 to the CLI. EXPECTED RESULT Expected to be able to log in via GUI/Plymouth login screen SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.13.3 ADDITIONAL INFORMATION sudo inxi -Fxxx: https://bin.privacytools.io/?66a914c115f9d56f#2J19XX2qKhZmjtwFA1zHMyeS4LyeAcM5E51MdeHMNJhk Please let me know if I can provide more info. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440857] Keybinding for mouse mark effect cannot be changed
https://bugs.kde.org/show_bug.cgi?id=440857 --- Comment #1 from Eric Armbruster --- Sorry, for the misinformation above. Clearly cannot read. The keybinding is documented in the settings page. However, it it cannot be changed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440857] Keybinding for mouse mark effect cannot be changed
https://bugs.kde.org/show_bug.cgi?id=440857 Eric Armbruster changed: What|Removed |Added Summary|Keybinding for mouse mark |Keybinding for mouse mark |effect is undocumented and |effect cannot be changed |cannot be changed | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440857] New: Keybinding for mouse mark effect is undocumented and cannot be changed
https://bugs.kde.org/show_bug.cgi?id=440857 Bug ID: 440857 Summary: Keybinding for mouse mark effect is undocumented and cannot be changed Product: kwin Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: eric1.armbrus...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Enable mouse mark effect in systemsettings. 2. Found by accident that the keybinding for mouse mark is to keep Meta + Shift pressed. OBSERVED RESULT In the effect's settings page there is no keybinding listed to enable this effect. Thus it is not documented and cannot be changed. EXPECTED RESULT The keybinding should be listed in the effect's settings page such that it is documented and can be changed. 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.
[kde] [Bug 438536] Using right click on a Desktop icon will show the context menu on the other monitor
https://bugs.kde.org/show_bug.cgi?id=438536 Eric Putney changed: What|Removed |Added Resolution|UPSTREAM|--- CC||ericrput...@gmail.com Ever confirmed|1 |0 Status|RESOLVED|REPORTED --- Comment #7 from Eric Putney --- I see that this issue has to do with Qt and/or X11, but here's an interesting detail on this bug's behavior. I have two monitors of different sizes, my primary (right) monitor is 3440x1440, my left monitor is 2560x1440. Right-clicking anywhere on my primary monitor makes the context menu appear exactly 2560 pixels to the left of where I clicked, so it's using the horizontal size of my left non-primary monitor as the offset. The only reason why the context menu has been showing up in the "right place" on a different monitor is because most people have the same sized monitor, so the offset moves it by exactly one monitor's length. If I right click an icon on the far right side of my right monitor, it opens on the same monitor but way on the left side (2560 pixels to the left). I hope this helps someone somewhere with the debugging process. Also this is my first post, I clicked something in the status dropdown menu but I'm not really sure how that works. Apologies if I accidentally changed the bug status. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 440281] New: opening yakuake pulls me back to another activity, negating the point of yakuake
https://bugs.kde.org/show_bug.cgi?id=440281 Bug ID: 440281 Summary: opening yakuake pulls me back to another activity, negating the point of yakuake Product: yakuake Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: ericsbinarywo...@gmail.com Target Milestone: --- SUMMARY Since upgrading to Fedora 34, when I trigger Yakuake to drop down it takes me to whatever activity I opened it in. That defeats the purpose, might as well have Konsoles in every activity, then. Version is 21.04.2 which I don't see as a selection option for the version here in Bugzilla. This is under X11. STEPS TO REPRODUCE 1. launch yakuake 2. open dropdown 3. to to another activity 4. launch dropdown - it takes you back to the first activity (may not happen at first after reboot, but eventually happens every time once it starts happening) OBSERVED RESULT EXPECTED RESULT For it to stay in the same activity SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 34 (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440088] New: With multiple screens widgets change around randomly and backgrounds are lost
https://bugs.kde.org/show_bug.cgi?id=440088 Bug ID: 440088 Summary: With multiple screens widgets change around randomly and backgrounds are lost Product: plasmashell Version: 5.22.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: ericsbinarywo...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I have 4 monitors hooked up to my Linux computer running KDE Plasma 5 on Fedora 34. 2 monitors are DP and 2 are HDMI. When I turn monitors off and then back on, the widgets show up randomly on different screens. Also, some of the monitors lose their background. It either becomes black or the default KDE background for 5.22.3 - looks like a geometric mountain and lake. STEPS TO REPRODUCE 1. Have multiple monitors connected 2. set up your plasmoids and desktop backgrounds per screen 3. Turn off the screens 4. Turn the screens back on OBSERVED RESULT Widgets have moved to a random monitor and backgrounds are all messed up EXPECTED RESULT For things to remain where I put them SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 34 KDE Plasma 5.22.3 (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Kernel versio: 5.12.15-300 Graphics Platform: Wayland Processor: 8 x AMD FX-8320 Memory: 24 GB Graphics: Radeon RX 580 -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 422033] Break never counts down to zero in Wayland
https://bugs.kde.org/show_bug.cgi?id=422033 Eric Mesa changed: What|Removed |Added CC||ericsbinarywo...@gmail.com --- Comment #5 from Eric Mesa --- Adding that this also happens on Fedora 34 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 438217] New: Bib text not found
https://bugs.kde.org/show_bug.cgi?id=438217 Bug ID: 438217 Summary: Bib text not found Product: kile Version: 2.9.93 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: nosoyerop...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Bib text not found 2. Latex can not compile 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 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.
[kde] [Bug 436939] New: startkde: "Could not start Plasma session" xmessage in Wayland session in VirtualBox
https://bugs.kde.org/show_bug.cgi?id=436939 Bug ID: 436939 Summary: startkde: "Could not start Plasma session" xmessage in Wayland session in VirtualBox Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: aer0...@gmail.com Target Milestone: --- Application: kde-open5 (5.21.3) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.12-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.3 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I had just installed Fedora 34 Plasma in a VM in VirutualBox. I added the Guest Additions CD to the VM, and I was mounting the CD when the session went black, and showed an xmessage dialog with the message "startkde: Could not start Plasma session." I am running a Wayland session. FWIW, the host is Ubuntu MATE 20.04.2 Also FWIW, I saw this a few times during installation, and using an Xsession worked better. - Unusual behavior I noticed: The black screen with xmessage dialog described above. Thanks! The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KIO Client (kde-open5), signal: Aborted [KCrash Handler] #4 0x7f7884b6e292 in raise () from /lib64/libc.so.6 #5 0x7f7884b578a4 in abort () from /lib64/libc.so.6 #6 0x7f7884fd042d in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #7 0x7f78810d6ef3 in QtWaylandClient::QWaylandDisplay::checkError() const [clone .cold] () from /lib64/libQt5WaylandClient.so.5 #8 0x7f78810e56fa in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #9 0x7f78851ce4fd in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7f78851ea6d2 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #11 0x7f788519c9b2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #12 0x7f78851a4544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #13 0x55c9322474f5 in main () [Inferior 1 (process 2370) detached] Possible duplicates by query: bug 436863, bug 435427, bug 433524, bug 432084, bug 431077. Reported using DrKonqi This report was filed against 'kde' because the product 'kde-open5' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436080] New: Fonts look garbled when configuring audio devices
https://bugs.kde.org/show_bug.cgi?id=436080 Bug ID: 436080 Summary: Fonts look garbled when configuring audio devices Product: systemsettings Version: 5.21.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_pulseaudio Assignee: now...@gmail.com Reporter: eric.donkersl...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 137824 --> https://bugs.kde.org/attachment.cgi?id=137824&action=edit Audio devices settings SUMMARY STEPS TO REPRODUCE 1. Right click on the audio icon in the system tray 2. Choose "Configure audio devices" 3. Right click on the "Configure" button OBSERVED RESULT Fonts & dialog boxes look garbled (see screenshot) EXPECTED RESULT Crisp fonts and dialog boxes SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.11.16-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 434892] konsole crash when open
https://bugs.kde.org/show_bug.cgi?id=434892 --- Comment #5 from eric --- Ok I have tried deleting my ~/.config/konsolerc and now konsole opens just fine. I believe the issue was my default konsole profile had the setting to "randomly adjust colors for each session" under Edit Color Scheme. If I create a new profile in konsole settings and use "randomly adjust colors" then set it as default it causes the same crash behavior. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 434892] konsole crash when open
https://bugs.kde.org/show_bug.cgi?id=434892 --- Comment #4 from eric --- I would like to add that I've now installed the debug symbols for a full report. Konsole crashes immediately on opening every single time under both xorg and wayland on my Intel Kaby Lake laptop w/ intel graphics: Application: konsole (20.12.2) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.12-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.3 Distribution: "Fedora release 34 (Thirty Four)" -- Backtrace: Application: Konsole (konsole), signal: Aborted [KCrash Handler] #4 0x7f5b7ffb1292 in raise () from /lib64/libc.so.6 #5 0x7f5b7ff9a8a4 in abort () from /lib64/libc.so.6 #6 0x7f5b7fe72c78 in std::__replacement_assert (__file=, __line=, __function=, __condition=) at /usr/include/c++/11/x86_64-redhat-linux/bits/c++config.h:2648 #7 0x7f5b7ff1548f in std::piecewise_linear_distribution::param_type::_M_initialize (this=0x7ffee1fdec90) at /usr/include/c++/11/bits/random.tcc:3055 #8 0x7f5b7ff1c5af in std::piecewise_linear_distribution::piecewise_linear_distribution > (__fw=..., __bl=..., this=0x7ffee1fdec90) at /usr/include/c++/11/bits/random.h:5867 #9 Konsole::ColorScheme::colorEntry (this=0x7ffee1fdec90, index=, randomSeed=3791514576) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/colorscheme/ColorScheme.cpp:322 #10 0x7f5b7fecea29 in Konsole::ColorScheme::getColorTable (randomSeed=209784833, table=0x7ffee1fe0150, this=0x55f018787b90) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/colorscheme/ColorScheme.cpp:339 #11 Konsole::TerminalDisplay::applyProfile (this=0x55f01871baa0, profile=...) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/terminalDisplay/TerminalDisplay.cpp:3118 #12 0x7f5b7fe8633b in Konsole::ViewManager::applyProfileToView (this=0x55f01849efb0, view=0x55f01871baa0, profile=...) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/ViewManager.cpp:832 #13 0x7f5b7fe8e84b in Konsole::ViewManager::createView (this=0x55f01849efb0, session=session@entry=0x55f018521070) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/ViewManager.cpp:675 #14 0x7f5b8074d82e in Konsole::MainWindow::createSession (this=this@entry=0x55f0184539e0, profile=..., directory=...) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/MainWindow.cpp:512 #15 0x7f5b80753a64 in Konsole::Application::newInstance (this=0x7ffee1fe0730) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/Application.cpp:235 #16 0x7f5b8075e918 in kdemain (argc=, argv=) at /usr/src/debug/konsole5-20.12.2-1.fc34.x86_64/src/main.cpp:235 #17 0x7f5b7ff9bb75 in __libc_start_main () from /lib64/libc.so.6 #18 0x55f017bb136e in _start () [Inferior 1 (process 204868) detached] Report to https://bugs.kde.org/ (In reply to tcanabrava from comment #1) > Created attachment 137035 [details] > attachment-11681-0.html > > we are missing important information from your backtrace, can you install > the debug symbols? > > > On Wed, Mar 24, 2021 at 4:18 PM guy wrote: > > > https://bugs.kde.org/show_bug.cgi?id=434892 > > > > Bug ID: 434892 > >Summary: konsole crash when open > >Product: konsole > >Version: 20.12.2 > > Platform: Fedora RPMs > > OS: Linux > > Status: REPORTED > > Keywords: drkonqi > > Severity: crash > > Priority: NOR > > Component: general > > Assignee: konsole-de...@kde.org > > Reporter: guy.car...@gmail.com > > Target Milestone: --- > > > > Application: konsole (20.12.2) > > > > Qt Version: 5.15.2 > > Frameworks Version: 5.80.0 > > Operating System: Linux 5.11.8-300.fc34.x86_64 x86_64 > > Windowing System: X11 > > Drkonqi Version: 5.21.3 > > Distribution: Fedora 34 (KDE Plasma Prerelease) > > > > -- Information about the crash: > > - What I was doing when the application crashed: > > > > After I've upgrade frm F33 to F34 beta consloe crash when try to start it. > > > > The crash can be reproduced every time. > > > > -- Backtrace: > > Application: Konsole (konsole), signal: Aborted > > > > [KCrash Handler] > > #4 0x7f12bba2e292 in raise () from /lib64/libc.so.6 > > #5 0x7f12bba178a4 in abort () from /lib64/libc.so.6 > > #6 0x7f12bb8efc78 in std::__replacement_assert(char const*, int, char > > const*, char const*) () from /lib64/libkonsoleprivate.so.20 > > #7 0x7f12bb99248f in > > std::piecewise_linear_distribution::param_type::_M_initialize() () > > from > > /lib64/libkonsoleprivate.so.20 > > #8 0x7f12bb9995af in Konsole::ColorScheme::colorEntry(in
[ksmserver] [Bug 434369] Login after logout hangs for 3 minutes
https://bugs.kde.org/show_bug.cgi?id=434369 Eric Donkersloot changed: What|Removed |Added CC||eric.donkersl...@gmail.com --- Comment #11 from Eric Donkersloot --- This is a truly annoying bug, any updates on this? I'm having this issue on a fresh KDE Neon install: Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.8.0-48-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 435035] New: Cannot authorize Google because "browser may be not be secure"
https://bugs.kde.org/show_bug.cgi?id=435035 Bug ID: 435035 Summary: Cannot authorize Google because "browser may be not be secure" Product: Akonadi Version: 5.15.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Gmail resource Assignee: dvra...@kde.org Reporter: ericsbinarywo...@gmail.com CC: kdepim-b...@kde.org Target Milestone: --- SUMMARY In KOrganizer calendars window when trying to sign into Google account oauth, after I put in my gmail address I cannot put in my password because it says "this browser or app may not be secure" STEPS TO REPRODUCE 1. Go to the Korganizer settings 2. Go to calendar tab 3. Click to either add or modify an existing Gmail account 4. click on configure next to the account. 5. Put in gmail address 6. get error OBSERVED RESULT Cannot complete oauth EXPECTED RESULT Complete oauth so that Korganizer can talk to Google Calendar SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 152285] Searching/Querying in Krugal, there will be quite a few error that pop up.
https://bugs.kde.org/show_bug.cgi?id=152285 Eric Aguiar changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 208121] incorrect space characters in pdf form
https://bugs.kde.org/show_bug.cgi?id=208121 --- Comment #29 from eric --- (In reply to Justin Zobel from comment #28) > If this bug is no longer persisting or relevant please change the status to > resolved. The problem mentioned in comment #27 has not disappeared. Currently I'm using: okular 1.11.1, kde frameworks 5.74.0 and Qt 5.15.1. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 352667] I am using a sony DSC100, which has the date/time set correctly. If I import using Dolphin then the date time info shown in properties is correct, ie same as camera, HOWEVER in
https://bugs.kde.org/show_bug.cgi?id=352667 --- Comment #2 from Eric P Adler --- I use a DSC100 and import using Shotwell, (I like the way the program organises everything into folders for me) and I haven't experienced any problem with date/time. On Tue, 9 Mar 2021 at 04:32, Justin Zobel wrote: > https://bugs.kde.org/show_bug.cgi?id=352667 > > --- Comment #1 from Justin Zobel --- > Thank you for the bug report. > > As this report hasn't seen any changes in 5 years or more, we ask if you > can > please confirm that the issue still persists. > > If this bug is no longer persisting or relevant please change the status to > resolved. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417994] Typing boxes stop taking input until next restart
https://bugs.kde.org/show_bug.cgi?id=417994 Eric changed: What|Removed |Added CC||emun...@mgebm.net --- Comment #6 from Eric --- I am having this same issue as well and it started with my update to Ubuntu 20.10. If I kill the ibus applet I loose the ability to send keyboard input to any QT application search box. However GTK applications seem to be fine. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 410743] shmat() calls for 32-bit programs fail when running in 64-bit valgrind
https://bugs.kde.org/show_bug.cgi?id=410743 --- Comment #5 from Eric Reischer --- FYI that patch resolves the bug, but it looks like it hasn't made it into the mainline branch yet. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432166] Spinbox in annotation tool of Spectacle looks different
https://bugs.kde.org/show_bug.cgi?id=432166 Eric Armbruster changed: What|Removed |Added Assignee|m...@baloneygeek.com |eric1.armbrus...@gmail.com --- Comment #4 from Eric Armbruster --- Oh I just noticed I only looked at the horizontal alignment inconsistency, which was obvious to me from the image. I will look into fixing the border as well. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 432166] Spinbox in annotation tool of Spectacle looks different
https://bugs.kde.org/show_bug.cgi?id=432166 Eric Armbruster changed: What|Removed |Added CC||eric1.armbrus...@gmail.com --- Comment #3 from Eric Armbruster --- https://github.com/ksnip/kImageAnnotator/pull/203 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428830] App responds very slowly to any input on Wayland
https://bugs.kde.org/show_bug.cgi?id=428830 --- Comment #8 from Eric Armbruster --- Can confirm. The issue is no longer present on Wayland (Plasma 5.21 Beta). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 400336] Black with visible cursor when undocking from thunderbolt dock
https://bugs.kde.org/show_bug.cgi?id=400336 Eric Gustavsson changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Eric Gustavsson --- Hi! I've moved to a T490s and am now using a thunderbolt hub instead of a dock. I presume the two are different in how they operate. Since no one else has commented I will presume it's fixed, I can't add more info as I don't have the T480s anymore -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 430827] problème sur opération répartie
https://bugs.kde.org/show_bug.cgi?id=430827 --- Comment #11 from Eric NOYON --- I think it's juste a change on the default layout with addition of one more column "etiquette" interposed beetwen "note" and the column amount, so the amounts where not visible. I had tried to string the columns but not at the good place 😖 Thanks for your help Le dim. 27 déc. 2020 à 01:02, Jack a écrit : > https://bugs.kde.org/show_bug.cgi?id=430827 > > Jack changed: > >What|Removed |Added > > > Status|NEEDSINFO |RESOLVED > Resolution|WAITINGFORINFO |NOT A BUG > > --- Comment #10 from Jack --- > Was the problem just a change in the default layout so some columns were > off > the right side of the window, requiring scrolling to see them? Might > there be > something to report to the Ubuntu packagers, or was this just on a small > screen? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 430827] problème sur opération répartie
https://bugs.kde.org/show_bug.cgi?id=430827 --- Comment #9 from Eric NOYON --- OK , It's fine Thank you Le sam. 26 déc. 2020 à 22:52, Eric NOYON a écrit : > I'l try and let you know > > Le sam. 26 déc. 2020 à 22:40, Thomas Baumgart > a écrit : > >> https://bugs.kde.org/show_bug.cgi?id=430827 >> >> --- Comment #7 from Thomas Baumgart --- >> Why don't you use the scroll bar at the bottom and move it over to the >> right >> and adjust the columns in the headings? >> >> -- >> You are receiving this mail because: >> You reported the bug. > > -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 430827] problème sur opération répartie
https://bugs.kde.org/show_bug.cgi?id=430827 --- Comment #8 from Eric NOYON --- I'l try and let you know Le sam. 26 déc. 2020 à 22:40, Thomas Baumgart a écrit : > https://bugs.kde.org/show_bug.cgi?id=430827 > > --- Comment #7 from Thomas Baumgart --- > Why don't you use the scroll bar at the bottom and move it over to the > right > and adjust the columns in the headings? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 430827] problème sur opération répartie
https://bugs.kde.org/show_bug.cgi?id=430827 --- Comment #6 from Eric NOYON --- When I open a split transaction already registered, the first column is "catégorie" as usual, the second "note" as usual and the third is "Étiquette" instead of the column for the amount. That bug is very new. Since I updated Ubuntu, yesterday white the last Version 20.04.1 LTA I join a picture of a split transaction Le sam. 26 déc. 2020 à 19:36, Jack a écrit : > https://bugs.kde.org/show_bug.cgi?id=430827 > > --- Comment #5 from Jack --- > I think you need to create the attachment at bugs.kde.org. I do not think > attachments to email replies get attached to the bug. Also, if replying by > email, please do not quote the entire message, as your entire message > (including any quoted text) becomes the next comment to the bug. Thanks. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 430827] problème sur opération répartie
https://bugs.kde.org/show_bug.cgi?id=430827 --- Comment #4 from Eric NOYON --- When I open a split transaction already registered, the first column is "catégorie" as usual, the second "note" as usual and the third is "Étiquette" instead of the column for the amount. That bug is very new. Since I updated Ubuntu, yesterday white the last Version 20.04.1 LTA I join a picture of a split transaction Le sam. 26 déc. 2020 à 16:34, Jack a écrit : > https://bugs.kde.org/show_bug.cgi?id=430827 > > --- Comment #3 from Jack --- > As Thomas said, you need to provide a more detailed explanation of what you > see. Can you describe what happens when you try to look at the details of > an > existing split transaction? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 430827] problème sur opération répartie
https://bugs.kde.org/show_bug.cgi?id=430827 --- Comment #2 from Eric NOYON --- The fact is that the dysfonction of split transaction appared today after the updating of ubuntu Le sam. 26 déc. 2020 à 14:43, Thomas Baumgart a écrit : > https://bugs.kde.org/show_bug.cgi?id=430827 > > Thomas Baumgart changed: > >What|Removed |Added > > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Thomas Baumgart --- > From your message I read with my remaining french skills and the help of > Google > translate (https://translate.google.com/) that it is impossible to create > split > transactions, something I cannot duplicate at all. > > Without further details about your problem, this is hard to analyze/fix. > Please > explain in detail, what is broken in KMyMoney. > > In case this is more a user question than a bug report, please consult the > forum at https://forum.kde.org/viewforum.php?f=69 or the user mailing list > https://mail.kde.org/mailman/listinfo/kmymoney > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 430827] New: problème sur opération répartie
https://bugs.kde.org/show_bug.cgi?id=430827 Bug ID: 430827 Summary: problème sur opération répartie Product: kmymoney Version: 5.0.8 Platform: unspecified OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: ecano...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Impossible de répartir des sommes lors d'une opération répartie ou même de lire laa répartition des sommes d'une opération répartie déjà saisie -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 430680] New: rkward process continues after exiting program
https://bugs.kde.org/show_bug.cgi?id=430680 Bug ID: 430680 Summary: rkward process continues after exiting program Product: rkward Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: rkward-de...@kde.org Reporter: majzo...@umsl.edu Target Milestone: --- SUMMARY Built rkward from source (git, as of today. build info below). After starting rkward and exiting the program the rkward process continues and has to be shut down by hand with "kill -HUP". STEPS TO REPRODUCE 1. start rkward 2. quit rkward from either the menu or the close button on the top right of the window OBSERVED RESULT rkward process is still running EXPECTED RESULT rkward exits and there are no processes running SOFTWARE/OS VERSIONS Operating System: Fedora 33 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.2 Kernel Version: 5.9.14-200.fc33.x86_64 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790 CPU @ 3.60GHz Memory: 31.2 GiB of RAM Graphics Processor: AMD CEDAR ---Session Info--- -- Frontend -- RKWard version: 0.7.2z+0.7.3+devel1 KDE Frameworks version (runtime): 5.75.0 KDE Frameworks version (compile time): 5.75.0 Qt version (runtime): 5.15.2 Qt version (compile time): 5.15.2 Using QtWebKit for HTML rendering Local config directory: /home/ehm/.config RKWard storage directory: /home/ehm/.rkward/ Backend version (as known to the frontend): 4.0.3 Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.frontend -- Backend -- Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.rbackend R version (compile time): 4.0.3 (2020-10-10 r79318) R runtime session info: R version 4.0.3 (2020-10-10) Platform: x86_64-redhat-linux-gnu (64-bit) Running under: Fedora 33 (Workstation Edition) Matrix products: default BLAS/LAPACK: /usr/lib64/libflexiblas.so.3.0 locale: [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 [5] LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 [7] LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 [9] LC_ADDRESS=en_US.UTF-8LC_TELEPHONE=en_US.UTF-8 [11] LC_MEASUREMENT=en_US.UTF-8LC_IDENTIFICATION=en_US.UTF-8 attached base packages: [1] stats graphics grDevices utils datasets methods base other attached packages: [1] rkward_0.7.3 loaded via a namespace (and not attached): [1] compiler_4.0.3 tools_4.0.3 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 419018] dolphin lags when there is a lot of mounted directory
https://bugs.kde.org/show_bug.cgi?id=419018 --- Comment #2 from Eric BURGHARD --- Some discussion on reddit related to this bug https://www.reddit.com/r/kde/comments/hrtzyg/how_to_exclude_overlayfs_mounts_from_showing_in/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 429997] Inserting Zones into the project bin causes a crash when selecting zone or clip
https://bugs.kde.org/show_bug.cgi?id=429997 --- Comment #9 from Eric Mesa --- Here is the youtube link to the crash and how it happens: https://youtu.be/9vujOeLkVwM Attached is the file I open. I attach the file because it looks like if I do it from scratch, it appears to work in the nightly. But still crashes when opening old file, even if doing a save-as to try and get it into the new format. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 429997] Inserting Zones into the project bin causes a crash when selecting zone or clip
https://bugs.kde.org/show_bug.cgi?id=429997 --- Comment #8 from Eric Mesa --- Created attachment 134237 --> https://bugs.kde.org/attachment.cgi?id=134237&action=edit kdenlive file causing issues this is the file I open in the video I will link to in the next comment -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 429997] Inserting Zones into the project bin causes a crash when selecting zone or clip
https://bugs.kde.org/show_bug.cgi?id=429997 --- Comment #6 from Eric Mesa --- Yes, the problem is no adding the clip. THe problem is making clips and then trying to add it in. I can make a video if I'm badly describing what's going on here. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 429997] Inserting Zones into the project bin causes a crash when selecting zone or clip
https://bugs.kde.org/show_bug.cgi?id=429997 --- Comment #4 from Eric Mesa --- I couldn't find any short clips where it didn't work. So here is a dropbox link with one of the files confirmed to be giving me trouble: https://www.dropbox.com/s/r3qhexl5r3avsuz/%23ExtraLife%20Eric%20Plays%20Super%20Mario%20Strikers%20Ep%2001%20-%20Relearning%20the%20Game.mkv?dl=0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 429997] Inserting Zones into the project bin causes a crash when selecting zone or clip
https://bugs.kde.org/show_bug.cgi?id=429997 --- Comment #2 from Eric Mesa --- Tried yesterday's nightly. Same issue. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 372496] Support tmux control mode
https://bugs.kde.org/show_bug.cgi?id=372496 Eric Kjeldergaard changed: What|Removed |Added CC||kjeld...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 430093] Webm high quality worse with Quality at highest setting (recent regression)
https://bugs.kde.org/show_bug.cgi?id=430093 --- Comment #1 from Eric Mesa --- I did a few more tests and I would like to modify the issue slightly. A lower quality bar does not improve the quality. However, switching from webm to mp4 produces the quality I'd expect. These are all under the "Generic" set of output. That is to say, WebM (VP8/Vorbis) and Mp4 (H264/AAC). For more concrete example of how wrong thigns are with Webm: Before I had this issue, I created a 34 minute video with WebM slider at highest quality. The file size was 2.0GB. After having this issue, I created a 40 minute video with WebM at the highest quality. It was 303 MB. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 430093] New: Webm high quality worse with Quality at highest setting (recent regression)
https://bugs.kde.org/show_bug.cgi?id=430093 Bug ID: 430093 Summary: Webm high quality worse with Quality at highest setting (recent regression) Product: kdenlive Version: 20.08.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: ericsbinarywo...@gmail.com Target Milestone: --- SUMMARY Created a Webm with quality slider all the way to the right and the quality looks horrendous. Very pixelated. This wasn't happened a few days ago before I updated to the latest. This is on flatpak so I don't know if the change is from kdenlive or the ffmpeg in flatpak, but the issue kind of seems similar to what was mentioned https://bugs.kde.org/show_bug.cgi?id=357153, but that's a super old bug. So I think this is a regression or a change in hw ffmpeg is interpreting the slider. I put critical because no one wants to wait 2 hour for a render to end up with a shit quality video. STEPS TO REPRODUCE 1. Setup kdenlive with your video 2. Tell it to render webm 3. Set quality slider to the highest setting 4. render OBSERVED RESULT Very, very splotchy video with bad quality EXPECTED RESULT Really awesome video with great quality SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 32 (available in About System) KDE Plasma Version: 5? KDE Frameworks Version: 5.76 Qt Version: 5.15.2 ADDITIONAL INFORMATION using flatpak -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 429997] New: Inserting Zones into the project bin causes a crash when selecting zone or clip
https://bugs.kde.org/show_bug.cgi?id=429997 Bug ID: 429997 Summary: Inserting Zones into the project bin causes a crash when selecting zone or clip Product: kdenlive Version: 20.08.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ericsbinarywo...@gmail.com Target Milestone: --- SUMMARY I'd been using this for nearly a year now and loving it, but in both 20.08.3 and the previous version, I take a clip and, while in "Logging window" I set a start and end and then ctrl-I to make clips. Then I got to the "Editing window". When I click on either the zone or the clip to import it, the whole thing crashes. Problem persists in Kdenlive nightly that I downloaded on 2020-12-02. STEPS TO REPRODUCE 1. Import a clip 2. Set start and end times 3. Hit ctl-I to make zones 4. Click on the zone clip or the parent clip 5. Kdenlive crashes OBSERVED RESULT Kdenlive crashes EXPECTED RESULT Kdenlive does not crash SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Using Flatpak version (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION With the nightly Appimage - here's what it dumped to the terminal: Invalid metadata for "avcolour_space" Failed to parse "avcolour_space" Invalid metadata for "avcolor_space" Failed to parse "avcolor_space" Invalid metadata for "avdeinterlace" Failed to parse "avdeinterlace" Invalid metadata for "swscale" Failed to parse "swscale" Invalid metadata for "swresample" Failed to parse "swresample" Invalid metadata for "audiochannels" Failed to parse "audiochannels" Invalid metadata for "audioconvert" Failed to parse "audioconvert" Invalid metadata for "data_feed" Failed to parse "data_feed" Invalid metadata for "imageconvert" Failed to parse "imageconvert" Invalid title/identifier for "crop_detect" Failed to parse "crop_detect" Invalid metadata for "telecide" Failed to parse "telecide" Invalid metadata for "deinterlace" Failed to parse "deinterlace" Unknown asset "avfilter.acompressor" Unknown asset "avfilter.aecho" Unknown asset "avfilter.agate" Unknown asset "avfilter.atadenoise" Unknown asset "avfilter.bwdif" Unknown asset "avfilter.chromashift" Unknown asset "avfilter.colorhold" Unknown asset "avfilter.deblock" Unknown asset "avfilter.dedot" Unknown asset "avfilter.deflate" Unknown asset "avfilter.derain" Unknown asset "avfilter.doubleweave" Unknown asset "avfilter.field" Unknown asset "avfilter.framestep" Unknown asset "avfilter.fspp" Unknown asset "avfilter.graphmonitor" Unknown asset "avfilter.hqdn3d" Unknown asset "avfilter.inflate" Unknown asset "avfilter.lagfun" Unknown asset "avfilter.random" Unknown asset "avfilter.removegrain" Unknown asset "avfilter.rgbashift" Unknown asset "avfilter.separatefields" Unknown asset "avfilter.shuffleplanes" Unknown asset "avfilter.sr" Unknown asset "avfilter.tmix" Unknown asset "avfilter.w3fdif" Unknown asset "avfilter.weave" Unknown asset "avfilter.yadif" Unknown asset "frei0r.baltan" Unknown asset "frei0r.bgsubtract0r" Unknown asset "frei0r.bigsh0t_eq_mask" Unknown asset "frei0r.bigsh0t_eq_to_rect" Unknown asset "frei0r.bigsh0t_hemi_to_eq" Unknown asset "frei0r.bigsh0t_rect_to_eq" Unknown asset "frei0r.bigsh0t_stabilize_360" Unknown asset "frei0r.bigsh0t_transform_360" Unknown asset "frei0r.delay0r" Unknown asset "frei0r.delaygrab" Unknown asset "frei0r.facebl0r" Unknown asset "frei0r.facedetect" Unknown asset "frei0r.lightgraffiti" Unknown asset "frei0r.lightgraffiti" Unknown asset "movit.blur" Unknown asset "movit.sharpen" Unknown asset "movit.diffusion" Unknown asset "movit.flip" Unknown asset "movit.glow" Unknown asset "movit.lift_gamma_gain" Unknown asset "movit.mirror" Unknown asset "movit.opacity" Unknown asset "movit.rect" Unknown asset "movit.saturation" Unknown asset "movit.unsharp_mask" Unknown asset "movit.vignette" Unknown asset "movit.white_balance" Unknown asset "region" Unknown asset "timewarp" Unknown asset "avfilter.subtitles" Unknown asset "opencv.tracker" Unknown asset "opencv.tracker" evdev ioctl: Inappropriate ioctl for device QWidget::setMinimumSize: (effect_list/QDockWidget) Negative sizes (0,-1) are not possible QWidget::setMinimumSize: (transition_list/QDockWidget) Negative sizes (0,-1) are not possible QWidget::setMinimumSize: (effect_list/QDockWidget) Negative sizes (0,-1) are not possible QWidget::setMinimumSize: (transition_list/QDockWidget) Negative sizes (0,-1) are not possible LOCALE: Document uses "." as decimal point and "C" as locale Searching for locale: Found QLocale(Warlpiri, Latin, Australia) with match type 1 Model size of -3 is less than 0 === LOADING SUBCLIP WITH RATING: 0 , TAGS: "" === LOADING SUBCLIP WITH RATING: 0 , TAGS: "" === LOADING SUBCLIP WITH RATING: 0 , TAGS: "" === LOADING
[ksmserver] [Bug 359651] Dangling user processes after KDE session crash
https://bugs.kde.org/show_bug.cgi?id=359651 Eric Donkersloot changed: What|Removed |Added CC||eric.donkersl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424488] Log out then login causes plasmashell to crashes
https://bugs.kde.org/show_bug.cgi?id=424488 Eric Donkersloot changed: What|Removed |Added CC||eric.donkersl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 429416] New: Upload to multiple flickr albums
https://bugs.kde.org/show_bug.cgi?id=429416 Bug ID: 429416 Summary: Upload to multiple flickr albums Product: digikam Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Plugin-WebService-Flickr Assignee: digikam-bugs-n...@kde.org Reporter: ericsbinarywo...@gmail.com Target Milestone: --- SUMMARY I would appreciate the ability to add photos to multiple flickr albums when uploading. A photo may, for example, go in both the Christmas 2020 and Portrait albums. Adding this ability would make the plugin equal to the website when it comes to uploading photos and albums. STEPS TO REPRODUCE 1. Select photos 2. choose to export to flickr 3. Choose 1 or more albums for this batch of photos to be added to OBSERVED RESULT Does not happen yet, this is a wishlist item. EXPECTED RESULT Be able to select multiple albums to upload to. SOFTWARE/OS VERSIONS irrelevant? ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429196] kf.plasma.core: findInCache with a lastModified timestamp of 0 is deprecated message makes system lags.
https://bugs.kde.org/show_bug.cgi?id=429196 Eric Donkersloot changed: What|Removed |Added CC||eric.donkersl...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 428830] App responds very slowly to any input on Wayland
https://bugs.kde.org/show_bug.cgi?id=428830 Eric Armbruster changed: What|Removed |Added CC||eric1.armbrus...@gmail.com --- Comment #1 from Eric Armbruster --- I can confirm this on Wayland as well. Operating System: Arch Linux KDE Plasma Version: 5.20.2 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.9.6-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425421] [Wayland] Log out causes the CPU utilization to jump to 100%
https://bugs.kde.org/show_bug.cgi?id=425421 Eric Armbruster changed: What|Removed |Added CC||eric1.armbrus...@gmail.com --- Comment #3 from Eric Armbruster --- I can reproduce this as well. Running on 5.20 with Wayland. -- You are receiving this mail because: You are watching all bug changes.
