[kate] [Bug 412502] Auto Completion is Broken for Variables in Kate & KWrite
https://bugs.kde.org/show_bug.cgi?id=412502 --- Comment #6 from 3ndymion <3ndym...@protonmail.com> --- Got the reverted fix with the Arch Linux KDE updates yesterday. Thank you very much for this. : ) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413155] The screen locker is broken after latest KDE updates.
https://bugs.kde.org/show_bug.cgi?id=413155 --- Comment #2 from 3ndymion <3ndym...@protonmail.com> --- OK, thanks for letting me know. I can see that the world map screen locker is broken as soon as its activated, but maybe that's already known too??? The other options seem to be OK so far, so I'll just use those & wait for the next updates. Thanks again. : ) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 413155] New: The screen locker is broken after latest KDE updates.
https://bugs.kde.org/show_bug.cgi?id=413155 Bug ID: 413155 Summary: The screen locker is broken after latest KDE updates. Product: kscreenlocker Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: 3ndym...@protonmail.com CC: bhus...@gmail.com Target Milestone: --- Created attachment 123325 --> https://bugs.kde.org/attachment.cgi?id=123325=edit The journalctl log when the screen locker started. The "broken" msg came on around 14:13. SUMMARY The latest KDE updates seem to have broken the screen locker. After the screen locker starts, it eventually crashes. Sometimes it happens after a few minutes, sometimes after a lot of minutes. When it crashes, the screen goes black & has a "broken" message saying this: Screen locker is broken and unlocking is not possible anymore. In order to unlock, switch to a virtual terminal Ctrl+Alt+F2 and execute loginctl unlock-session 2. Afterwards switch back to the running session Ctrl+Alt+F1 STEPS TO REPRODUCE 1. Let the screen locker come on. 2. 3. OBSERVED RESULT The screen locker crashes after a random amount of time. It always crashes eventually. EXPECTED RESULT The screen locker should stay on without crashing. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux Kernel Version: 5.3.6-arch1-1-ARCH (available in About System) KDE Plasma Version: 5.17.0 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION In my case, I have the screen locker set to slideshow. It changes images every 10 seconds. It works fine displaying & showing the images, but eventually, it will crash & show the "broken" message described above. I'm including an attachment of the journalctl log after the screen locker started. The screen locker was working like normal until it crashed & showed the "broken" message at around 14:13. I logged back in about 2 minutes later. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 412502] New: Auto Completion is Broken for Variables in Kate & KWrite
https://bugs.kde.org/show_bug.cgi?id=412502
Bug ID: 412502
Summary: Auto Completion is Broken for Variables in Kate &
KWrite
Product: kate
Version: 19.08.1
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kwrite-bugs-n...@kde.org
Reporter: 3ndym...@protonmail.com
Target Milestone: ---
SUMMARY
Ever since the last update, auto completion no longer works for variables. It
works fine when typing normal words, but not for variables. For example, if I
have 3 variables anywhere in the file, named varONE, varTWO, & varTHREE, I can
type "var" anywhere in the file, & the auto completion list will pop up showing
the 3 variable names. However, if I type "$var", or "${var", nothing happens.
The auto completion pop up does not show up.
STEPS TO REPRODUCE
1. Type any variable with the dollar ($) sign.
2.
3.
OBSERVED RESULT
The auto completion list does not pop up when typing any variable with the
dollar sign.
EXPECTED RESULT
The auto completion list should pop up when typing any variable with the dollar
sign.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: 5.3.1-arch1-1-ARCH
(available in About System)
KDE Plasma Version: 5.16.5
KDE Frameworks Version: 5.62.0
Qt Version: 5.13.1
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 409380] Formatting by KSyntaxHighlighting::SyntaxHighlighter of normal text seems to be dropped partially (Qt >=5.13.0/5.12.4)
https://bugs.kde.org/show_bug.cgi?id=409380 --- Comment #4 from 3ndymion <3ndym...@protonmail.com> --- I just realized... from looking at the screen close & at a different angle, I can see that the text preview actually is there. It is indeed nearly white text on a white background. I never realized that until just now. But I guess that's what you were saying in your explanation. My apologies, I had a bit of trouble understanding everything you wrote. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 409380] Formatting by KSyntaxHighlighting::SyntaxHighlighter of normal text seems to be dropped partially (Qt >=5.13.0/5.12.4)
https://bugs.kde.org/show_bug.cgi?id=409380 3ndymion <3ndym...@protonmail.com> changed: What|Removed |Added CC||3ndym...@protonmail.com --- Comment #3 from 3ndymion <3ndym...@protonmail.com> --- Hi. Sorry I took so long. I think the most I could do to help here is to confirm what you already know. It is indeed the color scheme that is related to this problem. I always use Breeze Dark, but when I switched back to normal Breeze with the bright colors, I opened up a new Dolphin window, & suddenly, the text file previews work perfectly fine again. Since I don't like looking into the sun, I put it back on Breeze Dark, & now, the text previews no longer work again. Could it possibly be a case of trying to render white text on a white background somehow??? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 408985] Power management fails to notify of low & critical battery, & fails to take critical action
https://bugs.kde.org/show_bug.cgi?id=408985 --- Comment #2 from 3ndymion <3ndym...@protonmail.com> --- Very cool. I will wait for it then. Thank you very much. : ) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 408986] New: Previews for plain text files no longer work.
https://bugs.kde.org/show_bug.cgi?id=408986 Bug ID: 408986 Summary: Previews for plain text files no longer work. Product: dolphin Version: 19.04.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: 3ndym...@protonmail.com Target Milestone: --- SUMMARY The previews for plain text files no longer work. These are the previews that show when you hover the mouse cursor over a file. They suddenly broke about a month or 2 ago. They work fine for other files, such as shell scripts, but they only show a blank page preview for any plain text file, such as textfile.txt, or even just textfile (no extension). If I change the file name to textfile.sh, the preview works fine. Previews are set for text files in Dolphin preferences. I tried unchecking & checking it again, but the problem persists. Clicking the preview button at the top does not fix it, nor does changing the size of the icons. Clicking show preview in Adjust view properties does not fix it either. STEPS TO REPRODUCE 1. Hover mouse cursor over text file icon. 2. 3. OBSERVED RESULT The preview popup shows a blank page. EXPECTED RESULT The preview popup should show a preview of the text in the file. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 5.1.12-arch1-1-ARCH (available in About System) KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 408985] New: Power management fails to notify of low & critical battery, & fails to take critical action
https://bugs.kde.org/show_bug.cgi?id=408985 Bug ID: 408985 Summary: Power management fails to notify of low & critical battery, & fails to take critical action Product: Powerdevil Version: 5.16.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: 3ndym...@protonmail.com Target Milestone: --- SUMMARY The power management service no longer shows notifications about low battery or critical battery levers. It also fails to take the action set for critical level. In my case, I have low level set to 20%, critical set to 10%, & critical action set to hibernate. This has worked fine for years, but stopped working about a week ago. I tried changing some settings & notifications & saving them, but the problem persists. No log messages from powerdevil are shown in journalctl at these times either. STEPS TO REPRODUCE 1. Let the battery drain down. 2. 3. OBSERVED RESULT No notifications or critical actions as stated above. EXPECTED RESULT Notification should be shown at or below the low battery level, & the critical battery level. Action should be taken at critical level. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.16.1 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 363771] deactivate "Aufklappmenue"
https://bugs.kde.org/show_bug.cgi?id=363771 --- Comment #6 from 3ndymion <3ndymio...@gmail.com> --- I have this problem in Arch Linux with KDE as well. I don't know if this would be helpful info or not, but when I choose to disable the popup, another popup message appears, but it stays minimized down in the taskbar. It does not ever pop up, or maximize, or come into focus on its own. You have to maximize it manually to see it, if you even noticed that it appeared. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396210] Disable This Popup option causes plasma to crash.
https://bugs.kde.org/show_bug.cgi?id=396210 --- Comment #6 from 3ndymion <3ndymio...@gmail.com> --- (In reply to Roman Gilg from comment #5) > Check the bug report Kai referenced as duplicate. There is more information > and you can provide more there instead of this one here. OK, I'll head over there. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396210] Disable This Popup option causes plasma to crash.
https://bugs.kde.org/show_bug.cgi?id=396210 --- Comment #4 from 3ndymion <3ndymio...@gmail.com> --- (In reply to Roman Gilg from comment #2) > I have never seen this popup before as well. How did you open Dolphin? Is it > somehow embedded into a widget? Or did you open it just from Launcher/ > command line? > > The seg fault itself seems to be a problem in Qt. Hi. I just double click on the icon to open Dolphin. I haven't done anything special. I've been using Arch Linux with KDE for a couple of months, & then, it just all of a sudden started happening one day. I have no idea why. It still happens regularly. A strange thing is that, when you click the option to disable it, a popup message appears, but it doesn't actually pop up. The popup message stays closed down in the taskbar & out of focus. You have to maximize it manually to ever see it. You might not even know that it appeared. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396210] Disable This Popup option causes plasma to crash.
https://bugs.kde.org/show_bug.cgi?id=396210 --- Comment #1 from 3ndymion <3ndymio...@gmail.com> --- Created attachment 113783 --> https://bugs.kde.org/attachment.cgi?id=113783=edit A picture showing the popup menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396210] New: Disable This Popup option causes plasma to crash.
https://bugs.kde.org/show_bug.cgi?id=396210 Bug ID: 396210 Summary: Disable This Popup option causes plasma to crash. Product: plasmashell Version: 5.13.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: 3ndymio...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.13.2) Qt Version: 5.11.1 Frameworks Version: 5.47.0 Operating System: Linux 4.17.3-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: When I try to copy a file in Dolphin, either with the right-click menu "copy" or with Control-C, a pop up menu appears, showing Kate, Kwrite, & a couple of other things. One of the options is "Disable This Popup". Choosing that option causes plasma to completely crash. This popup menu seems to be part of the clipboard. I have never seen this before. I don't know why this strange popup suddenly started appearing, but it is very annoying. Copying a file does not require an extra popup menu after copying the file. Any help on how to get rid of this, & fixing the bug, would be greatly appreciated. Thanks. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcd8ed65dc0 (LWP 9874))] Thread 8 (Thread 0x7fccc11cc700 (LWP 10131)): #0 0x7fcd87e7bea9 in poll () at /usr/lib/libc.so.6 #1 0x7fcd819e6523 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fcd819e663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fcd88798054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fcd8874394c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fcd8858ca99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fccc3b7e1da in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7fcd88596b45 in () at /usr/lib/libQt5Core.so.5 #8 0x7fcd87735075 in start_thread () at /usr/lib/libpthread.so.0 #9 0x7fcd87e8653f in clone () at /usr/lib/libc.so.6 Thread 7 (Thread 0x7fccd4a5f700 (LWP 10033)): #0 0x7fcd819e3332 in () at /usr/lib/libglib-2.0.so.0 #1 0x7fcd819e5983 in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #2 0x7fcd819e644e in () at /usr/lib/libglib-2.0.so.0 #3 0x7fcd819e663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x7fcd88798054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fcd8874394c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fcd8858ca99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #7 0x7fcd8c50223b in () at /usr/lib/libQt5Quick.so.5 #8 0x7fcd88596b45 in () at /usr/lib/libQt5Core.so.5 #9 0x7fcd87735075 in start_thread () at /usr/lib/libpthread.so.0 #10 0x7fcd87e8653f in clone () at /usr/lib/libc.so.6 Thread 6 (Thread 0x7fcce30fb700 (LWP 9959)): #0 0x7fcd8773affc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcce368d124 in () at /usr/lib/dri/i965_dri.so #2 0x7fcce368ce18 in () at /usr/lib/dri/i965_dri.so #3 0x7fcd87735075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fcd87e8653f in clone () at /usr/lib/libc.so.6 Thread 5 (Thread 0x7fcd6dfae700 (LWP 9950)): #0 0x7fcd8773affc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fcd8e44eaac in () at /usr/lib/libQt5Script.so.5 #2 0x7fcd8e44eac9 in () at /usr/lib/libQt5Script.so.5 #3 0x7fcd87735075 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fcd87e8653f in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fcd6700 (LWP 9930)): #0 0x7fcd87e77934 in read () at /usr/lib/libc.so.6 #1 0x7fcd81a2bed1 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fcd819e5ff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fcd819e64c6 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fcd819e663e in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fcd88798054 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fcd8874394c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fcd8858ca99 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fcd8c0859c9 in () at /usr/lib/libQt5Qml.so.5 #9 0x7fcd88596b45 in () at /usr/lib/libQt5Core.so.5 #10 0x7fcd87735075 in start_thread () at /usr/lib/libpthread.so.0 #11 0x7fcd87e8653f in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fcd75eab700 (LWP 9917)): #0 0x7fcd88797fa0 in () at /usr/lib/libQt5Core.so.5
[konsole] [Bug 365893] Clear scrollback and reset leaves the terminal screen completely blank.
https://bugs.kde.org/show_bug.cgi?id=365893 --- Comment #6 from 3ndymion <3ndymio...@gmail.com> --- (In reply to Ahmad Samir from comment #5) > FTR, for a long time Konsole has had a (hackish) way to redraw the prompt > after using e.g. `reset` or the menu item "Clear scrollback and reset". Have > a look at: > https://bugs.kde.org/show_bug.cgi?id=149562#c1 > > and the relevant commit: > https://cgit.kde.org/konsole.git/commit/ > ?id=d346a2ccad3950dad5ec137edce27e2930d536d6 > > and a follow up to that code to make it work with e.g. zsh: > https://cgit.kde.org/konsole.git/commit/ > ?id=ccfc3f859c5695cc08895570efd0831db0d3b9b0 Hi!!! Thanks for the good info. That's very interesting to see. It's good to know that it has stayed fixed for quite some time now. I'm currently using an outdated Fedora 25 KDE with Konsole 16.12.3, & even that one is working fine. The prompt returns to the screen as it should. Although it is a hackish way of doing it, it works, & I am happy. Thanks again!!! : ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373559] OSDs (On Screen Displays) are Broken
https://bugs.kde.org/show_bug.cgi?id=373559 --- Comment #2 from 3ndymion <3ndymio...@gmail.com> --- (In reply to Marco Martin from comment #1) > this has been recently fixed in master Very cool. Thank you!!! : ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373559] New: OSDs (On Screen Displays) are Broken
https://bugs.kde.org/show_bug.cgi?id=373559 Bug ID: 373559 Summary: OSDs (On Screen Displays) are Broken Product: plasmashell Version: master Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Look & Feel package Assignee: plasma-b...@kde.org Reporter: 3ndymio...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 I discovered a somewhat unimportant bug related to the taskbar being set to auto-hide. It breaks the OSDs (on screen displays). When the volume or screen brightness button is pressed, the OSD does not display. This is what I've discovered about it so far: if (taskbar = showing) OSDs work. if (taskbar != showing) OSDs are broken. if (any notification = showing) OSDs work. It does not matter if the taskbar is set to auto-hide or show always. As long as it is currently showing on the screen, the OSDs will display as they're supposed to. Notifications seem to affect the OSDs in the same way. -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 373558] New: Allowed User Names are Limited
https://bugs.kde.org/show_bug.cgi?id=373558 Bug ID: 373558 Summary: Allowed User Names are Limited Product: user-manager Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcontrol module Assignee: j...@jriddell.org Reporter: 3ndymio...@gmail.com Target Milestone: --- In trying out KDE again & trying to change my user avatar, I discovered that this new User Manager imposes a new restriction on the system. Specifically, it's this: "The user name must start with a letter." I guess I'm probably the only person that would run into this. : ( I use my screen name on my computer as well. The older versions of KDE (& Fedora) never had an issue with this. I realize that I can still use "kcmshell4 useraccount" to change the avatar, but that method is already long deprecated. I don't want to end up getting locked out. I think that whatever /etc/passwd can understand should be acceptable to User Manager as well. May I request that this new restriction be lifted??? I'll like, love you guys forever, or something. ^_^ -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 373557] New: Gwenview Crashes On "Zoom to Fit"
https://bugs.kde.org/show_bug.cgi?id=373557 Bug ID: 373557 Summary: Gwenview Crashes On "Zoom to Fit" Product: gwenview Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: 3ndymio...@gmail.com CC: myr...@kde.org Target Milestone: --- Application: gwenview (16.08.2) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.12-300.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: When viewing a picture, pressed "Zoom to Fit". Gwenview closed saying that it crashed. Happens every time I press "Zoom to Fit", whether it's through the menu or by pressing "F" on the keyboard. The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0e2937fe80 (LWP 6544))] Thread 3 (Thread 0x7f0e1d514700 (LWP 6546)): #0 0x7f0e37947ab2 in timerSourcePrepare(_GSource*, int*) () from /lib64/libQt5Core.so.5 #1 0x7f0e2f845699 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f0e2f84607b in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f0e2f84626c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f0e37947d8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f0e378f90ba in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f0e37756643 in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f0e37ffd7a9 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #8 0x7f0e3775aa1a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f0e355676ca in start_thread () from /lib64/libpthread.so.0 #10 0x7f0e36b4df6f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f0e1e87e700 (LWP 6545)): #0 0x7f0e36b4200d in poll () from /lib64/libc.so.6 #1 0x7f0e34369d10 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7f0e3436baa9 in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7f0e226eda19 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7f0e3775aa1a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7f0e355676ca in start_thread () from /lib64/libpthread.so.0 #6 0x7f0e36b4df6f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f0e2937fe80 (LWP 6544)): [KCrash Handler] #6 0x7f0e36a7b92f in raise () from /lib64/libc.so.6 #7 0x7f0e36a7d52a in abort () from /lib64/libc.so.6 #8 0x7f0e36abf260 in __libc_message () from /lib64/libc.so.6 #9 0x7f0e36aca948 in _int_malloc () from /lib64/libc.so.6 #10 0x7f0e36acbf74 in malloc () from /lib64/libc.so.6 #11 0x7f0e373bba88 in operator new(unsigned long) () from /lib64/libstdc++.so.6 #12 0x7f0e37c786b2 in QImageData::create(QSize const&, QImage::Format) () from /lib64/libQt5Gui.so.5 #13 0x7f0e37c7885b in QImage::QImage(int, int, QImage::Format) () from /lib64/libQt5Gui.so.5 #14 0x7f0e37ca48c5 in QRasterPlatformPixmap::resize(int, int) () from /lib64/libQt5Gui.so.5 #15 0x7f0e37ca1c1c in QPlatformPixmap::create(int, int, QPlatformPixmap::PixelType) () from /lib64/libQt5Gui.so.5 #16 0x7f0e37c9b6f7 in QPixmap::doInit(int, int, int) () from /lib64/libQt5Gui.so.5 #17 0x7f0e3ebefabd in Gwenview::RasterImageView::updateFromScaler(int, int, QImage const&) () from /lib64/libgwenviewlib.so.5 #18 0x7f0e37921326 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #19 0x7f0e3ec56f71 in Gwenview::ImageScaler::scaledRect(int, int, QImage const&) () from /lib64/libgwenviewlib.so.5 #20 0x7f0e3ec13197 in Gwenview::ImageScaler::scaleRect(QRect const&) () from /lib64/libgwenviewlib.so.5 #21 0x7f0e3ec137f7 in Gwenview::ImageScaler::doScale() () from /lib64/libgwenviewlib.so.5 #22 0x7f0e3ebee5a4 in Gwenview::RasterImageView::updateBuffer(QRegion const&) () from /lib64/libgwenviewlib.so.5 #23 0x7f0e3ebee713 in Gwenview::RasterImageView::onZoomChanged() () from /lib64/libgwenviewlib.so.5 #24 0x7f0e3ebe1095 in Gwenview::AbstractImageView::setZoom(double, QPointF const&, Gwenview::AbstractImageView::UpdateType) () from /lib64/libgwenviewlib.so.5 #25 0x7f0e3ebe6ec2 in Gwenview::DocumentView::setZoomToFit(bool) () from /lib64/libgwenviewlib.so.5 #26 0x7f0e3ec5a96c in Gwenview::DocumentView::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libgwenviewlib.so.5 #27 0x7f0e37920ff1 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #28 0x7f0e38d1dfd2 in QAction::toggled(bool) ()
[kwin] [Bug 365892] Windows snap to the wrong position when the bottom panel is set to auto-hide
https://bugs.kde.org/show_bug.cgi?id=365892 --- Comment #6 from 3ndymion <3ndymio...@gmail.com> --- I'm trying KDE again & got this update. It works great now. Thank you very much!!! :D :D :D -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365892] Windows snap to the wrong position when the bottom panel is set to auto-hide
https://bugs.kde.org/show_bug.cgi?id=365892 --- Comment #3 from 3ndymion <3ndymio...@gmail.com> --- Hi!!! Even if it cannot be fixed, thank you very much for at least looking at this. : ) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 365893] Clear scrollback and reset leaves the terminal screen completely blank.
https://bugs.kde.org/show_bug.cgi?id=365893 --- Comment #2 from 3ndymion <3ndymio...@gmail.com> --- (In reply to Egmont Koblinger from comment #1) > Works as intended. > > There's no way the app running inside the terminal could possibly know that > the terminal's contents have been tampered with by some other means, not > initiated by the app (that is, the shell in this case). > > Workarounds (such as injecting a Ctrl-L or Enter keypress) are bound to > cause much more severe problems in other situations. > > If this really bothers you, you can execute the "clear" command instead, or > manually press Enter or Ctrl-L after clearing the screen. Hi, & thanks for responding. I don't quite understand what you mean by "app running inside the terminal". It is the Konsole terminal that I was referring to. This problem did not occur in KDE4. Now in KDE5, it exists. I don't know how it was done before (in terms of programming), but the screen definitely should not remain complete blank without the prompt after clearing it. It should at least give you the prompt back. Other systems do not have this problem. It may seem right to you as a developer, but to anybody & everybody else who actually uses the system, it is definitely broken. There are many other bug reports about this exact issue that have gone unresolved, or have been closed, saying that the problem must be dealt with at the source, which is here. Leaving the screen with no prompt definitely gives the user the impression that the OS is broken & full of bugs. It's basically breaking something that was not broken, & then calling it fixed. The developers working on KDE (perhaps yourself included) are working very hard to create an awesome system for everyone to use. But when something like this happens, it's like punching them in the face. What is all the hard work for when new, avoidable problems are created & refused to be fixed??? The "clear" command only moves the existing text up past the top of the screen. It is not the same as what this option does. As a user, I don't know how it should work behind the scenes in the code, but all I know is that it did indeed work correctly in the past, & now it does not. There are many ignored bug reports that attest to this fact. I kindly & humbly ask you or any KDE developer that sees this to please resolve this issue. I don't know how it should or should not be done in the code, but the screen should definitely return the user prompt when the screen is cleared. I'm not even asking for myself, as I currently do not use KDE, although I might try it again for Fedora 25. No, instead, I'm asking on behalf of all of the people who do use KDE, whether it be on Fedora, Suse, or whatever. KDE5 is really shaping up nicely from the way it started out. It would be a terrible shame to keep such a blemish like this on what is intended to be a beautiful & problem-free system. Please do consider it. Thank you for looking. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 365893] New: Clear scrollback and reset leaves the terminal screen completely blank.
https://bugs.kde.org/show_bug.cgi?id=365893 Bug ID: 365893 Summary: Clear scrollback and reset leaves the terminal screen completely blank. Product: konsole Version: 16.04.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: 3ndymio...@gmail.com In the Konsole terminal emulator, whenever you do "clear scrollback and reset", either through the menu option or by pressing Control Shift K, the screen will remain completely blank. The prompt is not there. It will reappear whenever you press another key. Reproducible: Always Steps to Reproduce: 1. Go to "View". 2. Choose "Clear Scrollback and Reset". 3. Or press Control+Shift+K Actual Results: Screen remains completely blank. Expected Results: The username prompt should be showing. Running Fedora 24 KDE. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 365892] New: Windows snap to the wrong position when the bottom panel is set to auto-hide
https://bugs.kde.org/show_bug.cgi?id=365892 Bug ID: 365892 Summary: Windows snap to the wrong position when the bottom panel is set to auto-hide Product: kwin Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: 3ndymio...@gmail.com This bug happens when the task manager / bottom panel is set to auto-hide. When moving any window towards the bottom of the screen, the window will snap to the position that the panel would be at if the panel was showing (not hiding). If the panel is currently hiding, windows should not snap to the position that the panel would be at when it is open. Or, in other words, windows should not snap to something that's not there. Reproducible: Always Steps to Reproduce: 1. Set panel to auto-hide. 2. Move windows toward the panel once it is hidden. 3. Actual Results: Window snaps to the position that the panel was at when it was showing, even if the panel is already hiding. Expected Results: Window will continue to move freely towards the edge of the screen. Since panel is hiding, it will only snap to the edge of the screen. Running Fedora 24 KDE. Problem has been present ever since switch to KDE5. -- You are receiving this mail because: You are watching all bug changes.
