[plasmashell] [Bug 491228] New: Always visible left panel + dodge windows top panel = graphical / size issues
https://bugs.kde.org/show_bug.cgi?id=491228 Bug ID: 491228 Summary: Always visible left panel + dodge windows top panel = graphical / size issues Classification: Plasma Product: plasmashell Version: 6.1.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: jcor...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 172258 --> https://bugs.kde.org/attachment.cgi?id=172258=edit two panels + krunner= top panel partially black SUMMARY Always visible left panel + dodge windows top panel = graphical (flickering / partly black) / size issues STEPS TO REPRODUCE 1. Create a panel on the left of the display, set it to full size, centered, always visible 2. Create another panel on top of the display, set it to full size, centered, windows can dodge 3. Open krunner or enter panel edit mode OBSERVED RESULT The right side of the top panel flickers and (sometimes) turns black. The top panel placement is a bit off (it is not placed on the absolute left but then its right side is wider than the screen) EXPECTED RESULT No flickering (like if I put both panels in "dodge windows" or if I put one panel on top and the other at the bottom of the display) Consistent sizing SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Standard Fedora on a Thinkpad T480s (Intel 620) ADDITIONAL INFORMATION I tried removing some applets (especially on the top panel) but the problem remains. It disappear however when putting one panel on top and another one at the bottom. It also disappears if I put two panels in "dodge windows". Thanks for KDE / Plasma. When we report that kind of buglets, it speaks volume for the quality of your work!!! -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 487889] New: Kaddressbook maps Google Contacts phone number fields incorrectly
https://bugs.kde.org/show_bug.cgi?id=487889 Bug ID: 487889 Summary: Kaddressbook maps Google Contacts phone number fields incorrectly Classification: Applications Product: kaddressbook Version: 6.1.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: qrf4c5...@mozmail.com Target Milestone: --- Created attachment 170046 --> https://bugs.kde.org/attachment.cgi?id=170046=edit Kaddressbook Google Contacts Comparison SUMMARY Kaddressbook incorrectly maps Google Contact phone number fields within Kaddressbook. e.g. "Mobile" is mapped to "Home", "Home" is mapped to "Work". This occurs whether a contact is imported, created or edited, Kaddressbook changes the field mapping. It is only within Kaddressbook the field mappings are shown incorrectly, when contacts are viewed at contacts.google.com the mapped values are correct. See the attached images. STEPS TO REPRODUCE 1. In Kaddressbook > select "Add New Addressbook" > choose "Google Groupware" and add Google account. OBSERVED RESULT 1. All imported contacts have their phone number fields mapped to the wrong values. i.e. "Mobile" is mapped to "Home", "Home" is mapped to "Work". 2. Editing these fields within Kaddressbook to show the correct value has no effect with the changes only persisting for around one second before reverting. 3. When a new contact is created within Kaddressbook, the mapped fields for phone numbers do not persist within Kaddressbook upon save. e.g. "Mobile" gets remapped to "Home". This remapping only occurs within Kaddressbook however and when viewed at contacts.google.com the mappings are shown correctly as they were entered. i.e. The initial "Mobile" field in Kaddressbook before Kaddressbook changes it is correctly mapped to "Cell" at contacts.google.com EXPECTED RESULT Field mappings remain correct and consistent between Kaddressbook and contacts.google.com SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 480185] Kdeconnect daemon crashes at startup, and reinitianting the service
https://bugs.kde.org/show_bug.cgi?id=480185 Joel Oliver changed: What|Removed |Added CC||oliverjoel1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 480181] KDE Connect crashes after update to Frameworks 5.114.0
https://bugs.kde.org/show_bug.cgi?id=480181 Joel Oliver changed: What|Removed |Added CC||oliverjoel1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 479080] New: Keyboard shortcut "New Note from Clipboard" doesn't paste clipboard content anymore unless another note is present on the desktop.
https://bugs.kde.org/show_bug.cgi?id=479080 Bug ID: 479080 Summary: Keyboard shortcut "New Note from Clipboard" doesn't paste clipboard content anymore unless another note is present on the desktop. Classification: Applications Product: knotes Version: 5.24.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: qrf4c5...@mozmail.com CC: myr...@kde.org Target Milestone: --- SUMMARY *** STEPS TO REPRODUCE 1. Copy text to clipboard. 2. Invoke keyboard shortcut to launch new Knote using the clipboard contents. OBSERVED RESULT 1. If no other notes are present on the desktop, an EMPTY new Knote is launched 2. If another note instance is open on the desktop, a new Knote is launched this time using the clipboard contents in the body section as usual. EXPECTED RESULT 1. That irrespective of whether another note is present on the desktop or not, the keyboard shortcut launches a new Knote instance using the clipboard contents in the note body. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-2-MANJARO (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477590] Many "Filesystem not responding" notifications on boot
https://bugs.kde.org/show_bug.cgi?id=477590 Joel Oliver changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Joel Oliver --- Todays update to KDE Frameworks to 5.112.0 has solved the issue. Quick fix, Thank you devs! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474509] Plasma crashes when receiving desktop notifications
https://bugs.kde.org/show_bug.cgi?id=474509 Joel changed: What|Removed |Added CC||joel...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474509] Plasma crashes when receiving desktop notifications
https://bugs.kde.org/show_bug.cgi?id=474509 --- Comment #2 from Joel --- Created attachment 163594 --> https://bugs.kde.org/attachment.cgi?id=163594=edit New crash information added by DrKonqi plasmashell (5.27.9) using Qt 5.15.11 Crashed while receiving multiple desktop notifications within a second of each other -- Backtrace (Reduced): #4 0x7f9946207eeb in dri2_wl_swap_buffers_with_damage (disp=, draw=0x7f98f412b100, rects=0x0, n_rects=0) at ../src/egl/drivers/dri2/platform_wayland.c:1662 #5 0x7f99461f8cb4 in dri2_swap_buffers (disp=0x564ae94979b0, surf=0x7f98f412b100) at ../src/egl/drivers/dri2/egl_dri2.c:1881 #6 0x7f99461f0aad in eglSwapBuffers (dpy=, surface=0x7f98f412b100) at ../src/egl/main/eglapi.c:1433 #7 0x7f9949f720d9 in QtWaylandClient::QWaylandGLContext::swapBuffers(QPlatformSurface*) (this=0x564af098fd70, surface=) at ../../../../hardwareintegration/client/wayland-egl/qwaylandglcontext.cpp:502 #8 0x7f994f038ca3 in QSGRenderThread::syncAndRender(QImage*) (this=this@entry=0x564aec3ac610, grabImage=grabImage@entry=0x0) at /usr/src/debug/qtdeclarative-everywhere-src-5.15.11+kde30/src/quick/scenegraph/qsgthreadedrenderloop.cpp:869 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477590] Many "Filesystem not responding" notifications on boot
https://bugs.kde.org/show_bug.cgi?id=477590 --- Comment #2 from Joel Oliver --- Created attachment 163519 --> https://bugs.kde.org/attachment.cgi?id=163519=edit sudo df -ha -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477590] Many "Filesystem not responding" notifications on boot
https://bugs.kde.org/show_bug.cgi?id=477590 --- Comment #1 from Joel Oliver --- Created attachment 163518 --> https://bugs.kde.org/attachment.cgi?id=163518=edit /etc/fstab -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477590] Many "Filesystem not responding" notifications on boot
https://bugs.kde.org/show_bug.cgi?id=477590 Joel Oliver changed: What|Removed |Added CC||oliverjoel1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477590] New: Many "Filesystem not responding" notifications on boot
https://bugs.kde.org/show_bug.cgi?id=477590 Bug ID: 477590 Summary: Many "Filesystem not responding" notifications on boot Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: oliverjoel1...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 163517 --> https://bugs.kde.org/attachment.cgi?id=163517=edit Screenshot of notifications SUMMARY Running 6.7-rc2 kernel last week (Sunday Nov 19) had no problems. Upgrade to 6.7-rc3 today and reboot showed many "Filesystem is not responding, Filesystem mounted at xxx is not responding" messages. Tried older kernel from last week that worked and it doesn't, so it seems kernel has nothing to do with problem. Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.7-rc3 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series Manufacturer: ASUS *** 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. Boot system, after KDE desktop shows, in about 9 seconds, the notifications of many "Filesystem not responding" messages appear. 2. Open Dolphin. All filesystems seems to be mounted and OK. 3. Reboot, same notifications appear. OBSERVED RESULT No ill effects are appareant. Everything works as before, as all mounted filesystems are fine in Dolphin. This is a 2+ year old install that never had this experience. I compile and update to the lastest kernel every week. Reverting to older kernels that didn't have this problem doesn't change anything. EXPECTED RESULT No "false" notifications of "Filesystem not responding" on boot. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.27 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION : Attached -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 475649] Data loss when syncing Google contacts to Kaddressbook due to missing fields, wrong mapping and edits not saving.
https://bugs.kde.org/show_bug.cgi?id=475649 Joel changed: What|Removed |Added CC||qrf4c5...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 475649] New: Data loss when syncing Google contacts to Kaddressbook due to missing fields, wrong mapping and edits not saving.
https://bugs.kde.org/show_bug.cgi?id=475649 Bug ID: 475649 Summary: Data loss when syncing Google contacts to Kaddressbook due to missing fields, wrong mapping and edits not saving. Classification: Applications Product: kaddressbook Version: 5.24.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: qrf4c5...@mozmail.com CC: to...@kde.org Target Milestone: --- SUMMARY 1. Google >> Kaddressbook - many fields are not synced e.g. address, notes, etc. and those that are get mapped to the wrong tags. e.g. "mobile" gets mapped to "home". 2. Kaddressbook >> Google - new contact. Fields are mapped correctly to Google but don't stick on Kaddressbook e.g. "Mobile" gets switched to "Home" 3. Kaddressbook >> Google - changed contact. The wrongly mapped tags in Kaddressbook from 1. and 2. now get mapped to Google. Any tags changed in Kaddressbook don't stick as in 2. The fields missing in Kaddressbood from Step 1 get deleted on Google. STEPS TO REPRODUCE 1. Kaddressbook (or Kontact) >> add address book >> Google Groupware >> authorize >> sync >> compare Kaddressbook entries with Google contacts. 2. Kaddressbook >> create new contact with field name=Test1 and phone1=1234-567890 >> tag phone1 as "mobile" >> save and sync. 3. Compare the uploaded Google contacts version with the one in Kaddressbook. 4. Google contacts >> create new contact with fields name=Test2, phone1=0987-654321, address= >> tag phone1 as "mobile" >> save, sync to Kaddressbook and compare both versions. 4 Kaddressbook >> edit the synced contact "Test2" >> add new field phone2=2244-345678 and tag as "other" >> save, sync compare as before. OBSERVED RESULT 1. All contacts synced to Kaddressbook are missing fields such as address, notes, location, etc,. The fields that were synced have incorrectly mapped tags. e.g. "Home" instead "Mobile". Changing the tag back to "Mobile" doesn't stick, Kaddressbook reverts it back to "Home" after approx 1 second. The version on Google doesn't change. 2. With the new contact "Test1", Kaddressbook changes the "Mobile" tag to "Home" approx 1 second after saving however the Google version displays it correctly of "Mobile". 3. Kaddressbook changes the "Mobile" tag of the new "Test2" contact to "Home" immediately on download and the address field is missing. 4. Kaddressbook changes the "Other" tag to either "Home" or "Work" after editing the "Test2" contact. On Google the "Other" tag syncs correctly but the address field, missing in Kaddressbook due to the previous sync error, now gets deleted. EXPECTED RESULT That all fields get synced and mapped to the correct tags in both the Google and Kaddressbook versions, that edits made in one version are correctly reflected in the other and that no data gets deleted due to sync or mapping errors. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.8 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.1.55-1-MANJARO (64-bit) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 475169] New: Latte dock crashes when opening steam
https://bugs.kde.org/show_bug.cgi?id=475169
Bug ID: 475169
Summary: Latte dock crashes when opening steam
Classification: Plasma
Product: lattedock
Version: 0.10.8
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: application
Assignee: mvourla...@gmail.com
Reporter: d3f4altn...@proton.me
Target Milestone: ---
Application: latte-dock (0.10.8)
Qt Version: 5.15.10
Frameworks Version: 5.110.0
Operating System: Linux 6.5.5-arch1-1 x86_64
Windowing System: X11
Distribution: "Arch Linux"
DrKonqi: 5.27.8 [KCrashBackend]
-- Information about the crash:
Latte dock crashes when opening steam and also when closing steam
The crash can be reproduced every time.
-- Backtrace:
Application: Latte Dock (latte-dock), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 QScopedPointer
>::operator->() const (this=0x8, this=) at
/usr/include/qt/QtCore/qscopedpointer.h:116
#7 qGetPtrHelper > >(QScopedPointer >&) (ptr=..., ptr=) at
/usr/include/qt/QtCore/qglobal.h:1151
#8 QSGTexture::d_func() (this=0x0) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgtexture.h:57
#9 QSGTexture::setFiltering(QSGTexture::Filtering) (this=0x0,
filter=QSGTexture::Linear) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgtexture.cpp:576
#10 0x7fed689bb630 in
QSGOpaqueTextureMaterialShader::updateState(QSGMaterialShader::RenderState
const&, QSGMaterial*, QSGMaterial*) (this=0x7fec9c3589c0, state=...,
newEffect=0x7fec9c81df30, oldEffect=0x0) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/util/qsgtexturematerial.cpp:90
#11 0x7fed689a464e in
QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch const*)
(batch=0x7fec9c75d180, this=0x7fec9c823150) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3089
#12 QSGBatchRenderer::Renderer::renderMergedBatch(QSGBatchRenderer::Batch
const*) (this=0x7fec9c823150, batch=0x7fec9c75d180) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:3018
#13 0x7fed689a7e3e in QSGBatchRenderer::Renderer::renderBatches()
(this=0x7fec9c823150) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4055
#14 0x7fed689ac8f1 in QSGBatchRenderer::Renderer::render() (this=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4369
#15 0x7fed68994535 in QSGRenderer::renderScene(QSGBindable const&)
(bindable=, this=0x7fec9c823150) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgrenderer.cpp:264
#16 QSGRenderer::renderScene(QSGBindable const&) (this=0x7fec9c823150,
bindable=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgrenderer.cpp:220
#17 0x7fed689fbbfc in QSGOpenGLLayer::grab() (this=0x7fec9c81cc10) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/qsgopengllayer.cpp:447
#18 0x7fed689f3ae6 in QSGOpenGLLayer::updateTexture() (this=0x7fec9c81cc10)
at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/qsgopengllayer.cpp:187
#19 0x7fed68b4fcc7 in QQuickOpenGLShaderEffectMaterial::updateTextures()
const (this=0x7fec9c821360) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/items/qquickopenglshadereffectnode.cpp:477
#20 0x7fed68994c39 in QSGRenderer::preprocess() (this=0x7fec9c005050) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgrenderer.cpp:337
#21 0x7fed689944fc in QSGRenderer::renderScene(QSGBindable const&)
(bindable=warning: RTTI symbol for class 'QSGRenderer::renderScene(unsigned
int)::B' is not a type
..., this=0x7fec9c005050) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgrenderer.cpp:238
#22 QSGRenderer::renderScene(QSGBindable const&) (this=0x7fec9c005050,
bindable=warning: RTTI symbol for class 'QSGRenderer::renderScene(unsigned
int)::B' is not a type
...) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgrenderer.cpp:220
#23 0x7fed689949d4 in QSGRenderer::renderScene(unsigned int)
(this=, fboId=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/coreapi/qsgrenderer.cpp:212
#24 0x7fed689edf25 in
QSGDefaultRenderContext::renderNextFrame(QSGRenderer*, unsigned int)
(this=0x55bdbcf4b6b0, renderer=0x7fec9c005050, fboId=) at
/usr/src/debug/qt5-declarative/qtdeclarative/src/quick/scenegraph/qsgdefaultrendercontext.cpp:228
#25 0x7fed68a4c001 in QQuickWindowPrivate::renderSceneGraph(QSize const&,
QSize const&) (this=0x55bdbce25d30, size=,
surfaceSize=) at
[plasmashell] [Bug 474509] New: Plasma crashes when receiving desktop notifications
https://bugs.kde.org/show_bug.cgi?id=474509 Bug ID: 474509 Summary: Plasma crashes when receiving desktop notifications Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: joel...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.7) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.4.12-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: Plasma crashes when I receive several desktop notifications at the same time. They briefly pop-up on the screen then Plasma crashes and restarts The crash can be reproduced sometimes. -- Backtrace (Reduced): #3 0x7f5779ecb00b in dri2_wl_swap_buffers_with_damage (disp=, draw=0x7f55881b4c80, rects=0x0, n_rects=0) at ../src/egl/drivers/dri2/platform_wayland.c:1651 #4 0x7f5779ebbb74 in dri2_swap_buffers (disp=0x563e5f9c0c30, surf=0x7f55881b4c80) at ../src/egl/drivers/dri2/egl_dri2.c:1880 #5 0x7f5779eb3ced in eglSwapBuffers (dpy=, surface=0x7f55881b4c80) at ../src/egl/main/eglapi.c:1468 [...] #9 0x7f578050987b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib64/libQt5Core.so.5 [...] #12 0x7f5780b890b5 in QWindow::event(QEvent*) () at /lib64/libQt5Gui.so.5 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 474509] Plasma crashes when receiving desktop notifications
https://bugs.kde.org/show_bug.cgi?id=474509 --- Comment #1 from Joel --- Created attachment 161614 --> https://bugs.kde.org/attachment.cgi?id=161614=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473020] Lock screen crashes when screen is locked and screen sleeps
https://bugs.kde.org/show_bug.cgi?id=473020 --- Comment #4 from Joel --- Created attachment 160940 --> https://bugs.kde.org/attachment.cgi?id=160940=edit Plasmashell debug log output I've attached the output from the command `$ WAYLAND_DEBUG=1 plasmashell > log.txt 2>&1` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 473020] Lock screen crashes when screen is locked and screen sleeps
https://bugs.kde.org/show_bug.cgi?id=473020 --- Comment #2 from Joel --- (In reply to Vlad Zahorodnii from comment #1) > Can you provide wayland debug log for plasmashell? Run plasmashell as follows > >WAYLAND_DEBUG=1 plasmashell > log.txt 2>&1 > > reproduce the crash, and post the output here How would I run this command since Plasma starts automatically? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 473020] New: Plasma crashes when screen is locked and screen sleeps
https://bugs.kde.org/show_bug.cgi?id=473020 Bug ID: 473020 Summary: Plasma crashes when screen is locked and screen sleeps Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: joel...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.7) Qt Version: 5.15.10 Frameworks Version: 5.108.0 Operating System: Linux 6.4.6-1-default x86_64 Windowing System: Wayland Distribution: "openSUSE Tumbleweed" DrKonqi: 5.27.7 [CoredumpBackend] -- Information about the crash: The crash happens when the screen is locked and I'm not using my computer. 5 minutes after the screen locks, the screen will power down. When that happens, the screen will come back on with the crash lock screen showing The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault PID: 23254 (plasmashell) UID: 1000 (joel) GID: 1000 (joel) Signal: 11 (SEGV) Timestamp: Fri 2023-08-04 18:25:45 PDT (7min ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (joel) Boot ID: f1579bfc3e924e5d9147ca804cff8ddc Machine ID: 7bfae4d3aef2467b9202798be97ed2ec Hostname: localhost.localdomain Storage: /var/lib/systemd/coredump/core.plasmashell.1000.f1579bfc3e924e5d9147ca804cff8ddc.23254.169119874500.zst (present) Size on Disk: 82.7M Message: Process 23254 (plasmashell) of user 1000 dumped core. Stack trace of thread 23254: #0 0x7eff0c297f28 pthread_sigmask@GLIBC_2.2.5 (libc.so.6 + 0x94f28) #1 0x7eff0c24154d sigprocmask (libc.so.6 + 0x3e54d) #2 0x7eff0ec7487b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x587b) #3 0x7eff0ec76d33 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x7d33) #4 0x7eff0c241330 __restore_rt (libc.so.6 + 0x3e330) #5 0x7eff0cf5f44c _ZNKSt13__atomic_baseIiE4loadESt12memory_order (libQt5Gui.so.5 + 0x15f44c) #6 0x7eff0e32d013 _ZN15QtWaylandClient14QWaylandWindow20handleScreensChangedEv (libQt5WaylandClient.so.5 + 0x88013) #7 0x7eff0cb257a2 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x3257a2) #8 0x7eff0dd21962 ffi_call_unix64 (libffi.so.8 + 0x7962) #9 0x7eff0dd1e2df ffi_call_int (libffi.so.8 + 0x42df) #10 0x7eff0dd20f26 ffi_call (libffi.so.8 + 0x6f26) #11 0x7eff0eef4a23 wl_closure_invoke (libwayland-client.so.0 + 0x7a23) #12 0x7eff0eef5203 dispatch_event (libwayland-client.so.0 + 0x8203) #13 0x7eff0eef5494 dispatch_queue (libwayland-client.so.0 + 0x8494) #14 0x7eff0eef7f8f wl_display_roundtrip_queue (libwayland-client.so.0 + 0xaf8f) #15 0x7eff0e32d21a _ZN15QtWaylandClient14QWaylandWindow20handleScreensChangedEv (libQt5WaylandClient.so.5 + 0x8821a) #16 0x7eff0cb257a2 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x3257a2) #17 0x7eff0dd21962 ffi_call_unix64 (libffi.so.8 + 0x7962) #18 0x7eff0dd1e2df ffi_call_int (libffi.so.8 + 0x42df) #19 0x7eff0dd20f26 ffi_call (libffi.so.8 + 0x6f26) #20 0x7eff0eef4a23 wl_closure_invoke (libwayland-client.so.0 + 0x7a23) #21 0x7eff0eef5203 dispatch_event (libwayland-client.so.0 + 0x8203) #22 0x7eff0eef5494 dispatch_queue (libwayland-client.so.0 + 0x8494) #23 0x7eff0eef7f8f wl_display_roundtrip_queue (libwayland-client.so.0 + 0xaf8f) #24 0x7eff0e32d21a _ZN15QtWaylandClient14QWaylandWindow20handleScreensChangedEv (libQt5WaylandClient.so.5 + 0x8821a) #25 0x7eff0cb257a2 _ZN9QtPrivate15QSlotObjectBase4callEP7QObjectPPv (libQt5Core.so.5 + 0x3257a2) #26 0x7eff0dd21962 ffi_call_unix64 (libffi.so.8 + 0x7962) #27 0x7eff0dd1e2df ffi_call_int (libffi.so.8 + 0x42df) #28 0x7eff0dd20f26 ffi_call (libffi.so.8 + 0x6f26) #29 0x7eff0eef4a23 wl_closure_invoke (libwayland-client.so.0 + 0x7a23) #30 0x7eff0eef5203 dispatch_event (libwayland-client.so.
[okular] [Bug 445573] Okular consumes an enormous amount of Memory (it reached over 1Gb today
https://bugs.kde.org/show_bug.cgi?id=445573 Joel Köper changed: What|Removed |Added CC||j...@joelkoeper.de -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 468060] Google Contacts still not working as of Kaddressbook 5.22.3 OR Kalendar 22.12.3 despite reported as fixed. Google address book not added
https://bugs.kde.org/show_bug.cgi?id=468060 Joel changed: What|Removed |Added Summary|Google Contacts still not |Google Contacts still not |working as of Kaddressbook |working as of Kaddressbook |5.22.3 OR Kalendar 22.12.3 |5.22.3 OR Kalendar 22.12.3 |despite reported as fixed. |despite reported as fixed. |Google address book inot|Google address book not |added |added -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 468060] New: Google Contacts still not working as of Kaddressbook 5.22.3 OR Kalendar 22.12.3 despite reported as fixed. Google address book inot added
https://bugs.kde.org/show_bug.cgi?id=468060 Bug ID: 468060 Summary: Google Contacts still not working as of Kaddressbook 5.22.3 OR Kalendar 22.12.3 despite reported as fixed. Google address book inot added Classification: Applications Product: kaddressbook Version: 5.22.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: qrf4c5...@mozmail.com CC: to...@kde.org 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 Kaddressbook or Kalendar 2. Open ”Contacts” from the tool bar 3. Add a new address book and choose ”Google groupware - Google calendar, contacts and task from KDE” 4. Give the required permissions to the Google account for Akonadi services OBSERVED RESULT Nothing happened EXPECTED RESULT To see Google contacts address book added and synchronized with Contacts in Kaddressbook and/or Kalendar SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Plasma (available in About System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Google address book still not added in either Kaddressbook or Kalendar despite Volker's blog from 08.03.2023 reporting this as fixed. ref: https://www.volkerkrause.eu/2023/03/08/kde-pim-january-february-2023.html -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467922] New: kde settings crashed.
https://bugs.kde.org/show_bug.cgi?id=467922 Bug ID: 467922 Summary: kde settings crashed. Classification: Applications Product: systemsettings Version: 5.27.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: joel.zetterl...@protonmail.com Target Milestone: --- Application: systemsettings (5.27.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.8-300.fc38.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 38 (KDE Plasma Prerelease) DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: was changing teaming in setting and all of sudden it crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Systeminställningar (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f1698762f2f in QFontconfigDatabase::setupFontEngine(QFontEngineFT*, QFontDef const&) const () from /lib64/libQt5XcbQpa.so.5 #5 0x7f1698763952 in QFontconfigDatabase::fontEngine(QFontDef const&, void*) () from /lib64/libQt5XcbQpa.so.5 #6 0x7f16ab82a54b in loadEngine(int, QFontDef const&, QtFontFamily*, QtFontFoundry*, QtFontStyle*, QtFontSize*) [clone .isra.0] () from /lib64/libQt5Gui.so.5 #7 0x7f16ab82abca in QFontDatabase::findFont(QFontDef const&, int, bool) () from /lib64/libQt5Gui.so.5 #8 0x7f16ab82b838 in QFontDatabase::load(QFontPrivate const*, int) () from /lib64/libQt5Gui.so.5 #9 0x7f16ab800de3 in QFontPrivate::engineForScript(int) const () from /lib64/libQt5Gui.so.5 #10 0x7f16ab831575 in QTextEngine::fontEngine(QScriptItem const&, QFixed*, QFixed*, QFixed*) const () from /lib64/libQt5Gui.so.5 #11 0x7f16ab832f1f in QTextEngine::shapeText(int) const () from /lib64/libQt5Gui.so.5 #12 0x7f16ab845bc7 in QTextLine::layout_helper(int) () from /lib64/libQt5Gui.so.5 #13 0x7f16a94c60d5 in QQuickTextPrivate::setLineGeometry(QTextLine&, double, double&) () from /lib64/libQt5Quick.so.5 #14 0x7f16a94c6eb8 in QQuickTextPrivate::setupTextLayout(double*) () from /lib64/libQt5Quick.so.5 #15 0x7f16a94c90b2 in QQuickTextPrivate::updateSize() () from /lib64/libQt5Quick.so.5 #16 0x7f16a94ca883 in QQuickTextPrivate::updateLayout() () from /lib64/libQt5Quick.so.5 #17 0x7f16a8f2626b in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib64/libQt5Qml.so.5 #18 0x7f16a8eb80c1 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from /lib64/libQt5Qml.so.5 #19 0x7f16a8eb86d0 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /lib64/libQt5Qml.so.5 #20 0x7f16a8eb1cd4 in QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) () from /lib64/libQt5Qml.so.5 #21 0x7f16a951d5c5 in QQuickLoaderPrivate::_q_sourceLoaded() () from /lib64/libQt5Quick.so.5 #22 0x7f16a8f2626b in QQmlObjectCreator::finalize(QQmlInstantiationInterrupt&) () from /lib64/libQt5Qml.so.5 #23 0x7f16a8eb80c1 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () from /lib64/libQt5Qml.so.5 #24 0x7f16a8eb86d0 in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /lib64/libQt5Qml.so.5 #25 0x7f16a8eb1cd4 in QQmlComponent::create(QQmlIncubator&, QQmlContext*, QQmlContext*) () from /lib64/libQt5Qml.so.5 #26 0x7f16a951d5c5 in QQuickLoaderPrivate::_q_sourceLoaded() () from /lib64/libQt5Quick.so.5 #27 0x7f16a951e8d2 in QQuickLoader::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/libQt5Quick.so.5 #28 0x7f16a8f18ddd in QObjectPointerBinding::write(QV4::Value const&, bool, QFlags) () from /lib64/libQt5Qml.so.5 #29 0x7f16a8f1aa1d in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) () from /lib64/libQt5Qml.so.5 #30 0x7f16a8f181a5 in QQmlBinding::update(QFlags) () from /lib64/libQt5Qml.so.5 #31 0x7f16a8ef39d7 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib64/libQt5Qml.so.5 #32 0x7f16ab2e81c0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #33 0x7f16a8e97e78 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libQt5Qml.so.5 #34 0x7f16a8f18b21 in QObjectPointerBinding::write(QV4::Value const&, bool, QFlags) () from /lib64/libQt5Qml.so.5 #35 0x7f16a8f1aa1d in QQmlNonbindingBinding::doUpdate(QQmlJavaScriptExpression::DeleteWatcher const&, QFlags, QV4::Scope&) () from /lib64/libQt5Qml.so.5 #36 0x7f16a8f181a5 in QQmlBinding::update(QFlags) () from /lib64/libQt5Qml.so.5 #37 0x7f16a8ef39d7 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib64/libQt5Qml.so.5 #38 0x7f16ab2e81c0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #39 0x7f16a951f07d in
[plasma-nm] [Bug 448153] Unable to access the VPN network in double authentication mode (anyConnect SAML/SSO)
https://bugs.kde.org/show_bug.cgi?id=448153 --- Comment #8 from Joel Holdsworth --- Note that the Rahul's other patch to OpenConnect is also required to successfully connect to the VPN. * 0e82c937: Do not add 'single-sign-on' to the capabilities list for AnyConnect auth requests -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 448153] Unable to access the VPN network in double authentication mode (anyConnect SAML/SSO)
https://bugs.kde.org/show_bug.cgi?id=448153 --- Comment #7 from Joel Holdsworth --- I backported Rahul's patches the following patches to v5.26.5 on my system, and I can confirm that this fixes the issue: * 408cca64: Add support for openconnect_set_external_browser_callback introduced in openconnect v9.0 (libopenconnect 5.8) using QDesktopServices * 4654501e: Remove UB parameter passing to va_list argument in OpenconnectAuthWorkerThread::openUri * f7bb3a1f: Add support for SAML based authentication when using OpenConnect VPN * 7e7690db: Clean up braceless single line conditionals in openconnectauthworkerthread.cpp -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 --- Comment #3 from Joel Busch --- I see the same behaviour on my Fedora 37 with kde-connect 22.12.1-1.fc37 trying to connect to Android 12.1 with KDE Connect 1.21.1 from F-Droid. In journalctl I see the following line that seems relevant: Jan 21 15:26:09 hal9000 kdeconnectd[2038]: QDBusAbstractAdaptor: Cannot relay signal SftpPlugin::packetReceived(NetworkPacket): Unregistered input type in parameter list: NetworkPacket -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 419897] Error when accessing filesystem. sshfs finished with exit code 1
https://bugs.kde.org/show_bug.cgi?id=419897 Joel Busch changed: What|Removed |Added CC||joel.bu...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 448153] Unable to access the VPN network in double authentication mode (anyConnect SAML/SSO)
https://bugs.kde.org/show_bug.cgi?id=448153 Joel Holdsworth changed: What|Removed |Added CC||j...@airwebreathe.org.uk --- Comment #5 from Joel Holdsworth --- I also work at a company with forced SSO. I can test any experimental code. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 457952] Reminder dismiss crash
https://bugs.kde.org/show_bug.cgi?id=457952 --- Comment #1 from Joel Ray Holveck --- Created attachment 151592 --> https://bugs.kde.org/attachment.cgi?id=151592=edit New crash information added by DrKonqi kalendarac (5.20.3) using Qt 5.15.4 Crashes every time I dismiss a scheduled reminder -- Backtrace (Reduced): #6 0x7fedc35249af in QtPrivate::QSlotObjectBase::call (a=0x7fff4e6355c0, r=0x7fff4e635f00, this=0x5612543b9c60) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #7 doActivate (sender=0x5612543b8070, signal_index=9, argv=0x7fff4e6355c0) at kernel/qobject.cpp:3886 #8 0x7fedc4499b17 in KNotification::close() () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #9 0x7fedc35249af in QtPrivate::QSlotObjectBase::call (a=0x7fff4e6356f0, r=0x7fedc44d8090, this=0x5612543c1cd0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x5612543c12a0, signal_index=3, argv=0x7fff4e6356f0) at kernel/qobject.cpp:3886 -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 457952] Reminder dismiss crash
https://bugs.kde.org/show_bug.cgi?id=457952 Joel Ray Holveck changed: What|Removed |Added CC||jo...@piquan.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Joel changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=353975| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display (no wallpaper, can't get a context menu on right-click)
https://bugs.kde.org/show_bug.cgi?id=353975 Joel changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=371717| -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435507] New install digiKam 7.2 on Windows Error opening database
https://bugs.kde.org/show_bug.cgi?id=435507 --- Comment #15 from Joel --- Can I give a suggestion, that in this scenario that the user is doing a new installation, after having removed an old version, that the prompt also explains that if there is no pre-existing database to use, the user must delete the digikamrc file manually? As of now, there is no way the user would be able to figure this out. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435507] New install digiKam 7.2 on Windows Error opening database
https://bugs.kde.org/show_bug.cgi?id=435507 --- Comment #12 from Joel --- (In reply to Maik Qualmann from comment #11) > Use digiKam-7.3.0. Delete C:\Users\%USERNAME%\AppData\Local\digikamrc. And > start again with the initial setup. You canceled an initial setup, a config > exists but the database does not yet exist. The error message is intended to > give the user an opportunity to enter the correct path in the event of later > problems with the database. > > Maik The only contents in C:\Users\%USERNAME%\AppData\Local\digikamrc is an empty directory called "cache". I also tried uninstalling digiKam and re-installing, and the same error occurs. Are there any other files somewhere that can be manually removed? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435507] New install digiKam 7.2 on Windows Error opening database
https://bugs.kde.org/show_bug.cgi?id=435507 --- Comment #10 from Joel --- Please do not close this issue...There is still a problem here. It looks like the only reason the OP was able to get digiKam started was they happened to have db files from an old digiKam installation laying around. I'm trying to install digiKam for first time on Windows 10. I'm attaching the dialog that pops up "The Sqlite core database was not found, please set the correct location in the next dialog" The next dialog allows a folder to be selected on my hard drive. However, no matter what folder I choose, it just continues to loop back to the first dialog "The sqlite core database was not found..." So it is impossible to get digiKam to open up at this moment, on a new install on Windows 10. Is there any other information I can provide that would help troubleshoot this bug? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435507] New install digiKam 7.2 on Windows Error opening database
https://bugs.kde.org/show_bug.cgi?id=435507 --- Comment #9 from Joel --- Created attachment 142599 --> https://bugs.kde.org/attachment.cgi?id=142599=edit Select sqlite database location -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435507] New install digiKam 7.2 on Windows Error opening database
https://bugs.kde.org/show_bug.cgi?id=435507 Joel changed: What|Removed |Added CC||j...@szwarga.com --- Comment #8 from Joel --- Created attachment 142598 --> https://bugs.kde.org/attachment.cgi?id=142598=edit The sqlite core database was not found -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 434730] Screen shot taken at a prior time is shown in preview when "Prc Sc" is pressed for the first time instead on the screen shot of the current screen
https://bugs.kde.org/show_bug.cgi?id=434730 --- Comment #2 from Joel Anil Chacko --- Created attachment 136946 --> https://bugs.kde.org/attachment.cgi?id=136946=edit The screen of which the screen shot was taken in background and the resultant screen shot shown as preview in spectacle I have tried taking the screen shot from the latest version of spectacle "spectacle 21.07.70". The result was as shown in the attachment. The screen shot preview shown is that of a konsole window which I had taken at a prior time. I had pressed the "Prc Sc" button while on brave browser homepage, which can be seen in the background of the attachment. I had to repeat taking new screen shot 3 to 4 times for the screen shot of the brave homepage to come. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 434730] New: Screen shot taken at a prior time is shown in preview when "Prc Sc" is pressed for the first time instead on the screen shot of the current screen
https://bugs.kde.org/show_bug.cgi?id=434730 Bug ID: 434730 Summary: Screen shot taken at a prior time is shown in preview when "Prc Sc" is pressed for the first time instead on the screen shot of the current screen Product: Spectacle Version: 20.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: joelanilcha...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY The first screen shot taken when "Prt Sc" button is pressed will not be shown. Instead, the preview shown in the spectacle window will that of a screen shot taken at a prior time. Once the spectacle window is open after the first press of the "Prt Sc" button, the next screen shot taken will be that of the current screen. STEPS TO REPRODUCE 1. Press Prt Sc 2. Focus on Spectacle Window 3. Observe sreenshot preview OBSERVED RESULT The screen shot preview shown is that of the previous screenshot taken instead of current screen EXPECTED RESULT The screen shot preview shown should have been that of the current screen SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux Manjaro Version: 20.2.1 KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION It has also been observed that, the first screen shot taken the spectacle application without pressing the "Prt Sc", will also give a screen shot taken at a prior time. The screen shot of the current screen will only be taken at the second try. -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 186872] kopete don't respect kde proxy settings
https://bugs.kde.org/show_bug.cgi?id=186872 Joel changed: What|Removed |Added CC|joel.porq...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 433932] Bluetooth system tray mouseover sometimes shows wrong device
https://bugs.kde.org/show_bug.cgi?id=433932 Joel Ray Holveck changed: What|Removed |Added CC||jo...@piquan.org, ||n...@kde.org --- Comment #1 from Joel Ray Holveck --- This may be related to 422691 (which was closed in the 5.19 branch). Adding Nate to the cc list. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 433932] New: Bluetooth system tray mouseover sometimes shows wrong device
https://bugs.kde.org/show_bug.cgi?id=433932 Bug ID: 433932 Summary: Bluetooth system tray mouseover sometimes shows wrong device Product: Bluedevil Version: 5.20.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: system tray Assignee: now...@gmail.com Reporter: jo...@piquan.org CC: plasma-b...@kde.org Target Milestone: --- I haven't worked out specific steps-to-reproduce, since I don't know how to make a simple repro case for something that relies on Bluetooth devices. I currently have two BT devices paired with my computer: an "Intuos BT M" tablet, and a "Nvidia Controller v01.04" gamepad. The tablet is rarely connected, but the gamepad usually stays connected for long periods, including reboots. Often, if I hover my mouse over the Bluetooth icon in the KDE System Tray, it will say "Bluetooth: Intuos BT M connected" (referring to the tablet), even though only the gamepad is connected. If I click on the Bluetooth icon, the list of devices correctly puts the gamepad under "Connected" and the tablet under "Available"; the only place I see the wrong device is in the mouseover. It doesn't seem to affect anything concrete. I think (but haven't been able to verify formally) that it almost always is wrong when I start the computer; however, if the gamepad disconnects and later reconnects, then the mouseover stays correct for the remainder of the session. This is using the default Bluetooth system tray icon, the one that shows up in "System Tray Settings" as "Bluetooth (Automatic load)" (which I have set to "Show When Relevant", with no keybindings). I think that's part of Bluedevil; let me know if I misfiled the bug. I'm sorry I don't have steps-to-reproduce. I'm hoping the bug will be evident on inspection, but if you need me to experiment, let me know. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 333803] Kmix popup window appears on second screen, not primary monitor.
https://bugs.kde.org/show_bug.cgi?id=333803 Joel changed: What|Removed |Added CC|joel.porq...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 --- Comment #41 from Joel Teixeira --- (In reply to Raul Laasner from comment #40) > (In reply to Joel Teixeira from comment #38) > Thank you for the suggestion! I was seriously considering giving up Firefox > for Chrome. The most annoying thing for me was not the faulty coloring but > how much narrower the scroll bars were. That made web surfing much harder. The same here Raul, I'm glad the suggestion helped. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 --- Comment #38 from Joel Teixeira --- (In reply to Nate Graham from comment #37) > There is currently no workaround. We're looking into reverting the change > until the underlying GTK issue is fixed. Thank you Nate, wasn't sure since I saw on other threads ppl talking about downgrading gtk libs. For the time being IMO the best option is to use default theme on GTK application setting. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 412078] Hovering on checkboxes or comboboxes changes their color to black
https://bugs.kde.org/show_bug.cgi?id=412078 Joel Teixeira changed: What|Removed |Added CC||joel...@gmail.com --- Comment #36 from Joel Teixeira --- Same problem here. Not sure if it was mentioned but you not even need to open an GTK3 aplication to reproduce this issue. On KDE Settings / GTK Application Style (preview) its possible to see it. Is there any workaround besides change de theme to default/Emacs? Operating System: Arch Linux KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 Kernel Version: 5.3.7-arch1-2-ARCH OS Type: 64-bit Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 15,5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 352626] When Focus Stealing is High, System Tray popup windows are blocked if an active window is present where they would appear
https://bugs.kde.org/show_bug.cgi?id=352626 Joel Aufrecht changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Joel Aufrecht --- >> David Edmundson 2015-10-12 13:00:22 UTC >> If I turn Focus Stealing Prevention down from High to Medium, the windows >> work normally. > including being in the right place? I just tried to repro with the latest, Ubuntu 18.04, kwin 5.12.6, and the bug is still present, but the failure mode is slightly different. Steps to Reproduce: 1) Change focus stealing to High 2) Open a window, like Firefox or Konsole 3) Click on the network icon in the system tray on the taskbar at the bottom of the screen Actual Results: The taskbar becomes completely unresponsive. Clicking anywhere on it, from the system tray to the start menu, has no effect, and it does not autohide. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394717] New: Plasma crashed at login start
https://bugs.kde.org/show_bug.cgi?id=394717 Bug ID: 394717 Summary: Plasma crashed at login start Product: plasmashell Version: 5.12.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: c...@carlosjoel.net CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.12.5) Qt Version: 5.11.0 Frameworks Version: 5.46.0 Operating System: Linux 4.16.11-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: Login to my PC user account, plasma started and 5 seconds later it crashes and started again. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4d1dc83c80 (LWP 711))] Thread 15 (Thread 0x7f4c5e781700 (LWP 882)): #0 0x7f4d171f9667 in ioctl () at /usr/lib/libc.so.6 #1 0x7f4cf1c2c7ec in () at /usr/lib/libnvidia-glcore.so.390.59 #2 0x7f4cf1c2d977 in () at /usr/lib/libnvidia-glcore.so.390.59 #3 0x7f4cf1c2e143 in () at /usr/lib/libnvidia-glcore.so.390.59 #4 0x7f4cf2d44232 in () at /usr/lib/libGLX_nvidia.so.0 #5 0x7f4cf1917584 in () at /usr/lib/libnvidia-glcore.so.390.59 #6 0x7f4cf183859e in () at /usr/lib/libnvidia-glcore.so.390.59 #7 0x7f4cf2d3ace1 in () at /usr/lib/libGLX_nvidia.so.0 #8 0x7f4d0681e569 in () at /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so #9 0x7f4d183316f0 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #10 0x7f4d1b69c198 in () at /usr/lib/libQt5Quick.so.5 #11 0x7f4d1b69ff08 in () at /usr/lib/libQt5Quick.so.5 #12 0x7f4d17912b95 in () at /usr/lib/libQt5Core.so.5 #13 0x7f4d16ab1075 in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f4d1720253f in clone () at /usr/lib/libc.so.6 Thread 14 (Thread 0x7f4c23fff700 (LWP 879)): #0 0x7f4d16ab6ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4d1791334c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f4d1b69fcdd in () at /usr/lib/libQt5Quick.so.5 #3 0x7f4d1b69ff4c in () at /usr/lib/libQt5Quick.so.5 #4 0x7f4d17912b95 in () at /usr/lib/libQt5Core.so.5 #5 0x7f4d16ab1075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f4d1720253f in clone () at /usr/lib/libc.so.6 Thread 13 (Thread 0x7f4c39257700 (LWP 878)): #0 0x7f4d16ab6ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4d1791334c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f4d1b69fcdd in () at /usr/lib/libQt5Quick.so.5 #3 0x7f4d1b69ff4c in () at /usr/lib/libQt5Quick.so.5 #4 0x7f4d17912b95 in () at /usr/lib/libQt5Core.so.5 #5 0x7f4d16ab1075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f4d1720253f in clone () at /usr/lib/libc.so.6 Thread 12 (Thread 0x7f4c3a311700 (LWP 877)): #0 0x7f4d171fd0f9 in syscall () at /usr/lib/libc.so.6 #1 0x7f4cf2d3c335 in () at /usr/lib/libGLX_nvidia.so.0 #2 0x7f4cf2d3bfc3 in () at /usr/lib/libGLX_nvidia.so.0 #3 0x7f4cf196a163 in () at /usr/lib/libnvidia-glcore.so.390.59 #4 0x7f4cf196a236 in () at /usr/lib/libnvidia-glcore.so.390.59 #5 0x7f4cf191758c in () at /usr/lib/libnvidia-glcore.so.390.59 #6 0x7f4cf183859e in () at /usr/lib/libnvidia-glcore.so.390.59 #7 0x7f4cf2d3ace1 in () at /usr/lib/libGLX_nvidia.so.0 #8 0x7f4d0681e569 in () at /usr/lib/qt/plugins/xcbglintegrations/libqxcb-glx-integration.so #9 0x7f4d183316f0 in QOpenGLContext::swapBuffers(QSurface*) () at /usr/lib/libQt5Gui.so.5 #10 0x7f4d1b69c198 in () at /usr/lib/libQt5Quick.so.5 #11 0x7f4d1b69ff08 in () at /usr/lib/libQt5Quick.so.5 #12 0x7f4d17912b95 in () at /usr/lib/libQt5Core.so.5 #13 0x7f4d16ab1075 in start_thread () at /usr/lib/libpthread.so.0 #14 0x7f4d1720253f in clone () at /usr/lib/libc.so.6 Thread 11 (Thread 0x7f4c3ad12700 (LWP 876)): #0 0x7f4d16ab6ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4d1791334c in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib/libQt5Core.so.5 #2 0x7f4d1b69fcdd in () at /usr/lib/libQt5Quick.so.5 #3 0x7f4d1b69ff4c in () at /usr/lib/libQt5Quick.so.5 #4 0x7f4d17912b95 in () at /usr/lib/libQt5Core.so.5 #5 0x7f4d16ab1075 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7f4d1720253f in clone () at /usr/lib/libc.so.6 Thread 10 (Thread 0x7f4c3b613700 (LWP 875)): #0 0x7f4d16ab6ffc in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7f4d1791334c in QWaitCondition::wait(QMutex*, unsigned long) () at
[Spectacle] [Bug 390415] Feature request - Spectacle - Save to file and clipboard
https://bugs.kde.org/show_bug.cgi?id=390415 --- Comment #7 from Joel Teixeira <joel...@gmail.com> --- (In reply to Henrik Fehlauer from comment #5) > Thanks Joel, that's interesting: I'm using Spectacle by starting it, > choosing options and then taking a screenshot. After this, I can just press > the shortcuts I mentioned, right inside Spectacle. > > To me it sounds like you are using the hotkeys only, you get the "Screenshot > taken" notification without starting the application window first. That was > the essential information missing from your bug report ;) Sorry, my mistake. Should have mentioned. Indeed I use it most of the time with just Printscreen key to "region+save output file" with that script at the moment. I use Ctrl+Printscreen to call the Gui when I want something different. > From the notification, you should be able to just drag the image to wherever > you want. For a keyboard-only workflow, D9117 will bring improvements, and > we have other bugs open to expose the shortcuts more prominently to the user. Yes, in case I can make it stay longer before it hides it should be a workaround as well. Thanks for the tip. > I could imagine having a more flexible saving/copying/exporting pipeline > would be useful, but this would probably involve a more thorough change in > Spectacle. I'm also hesitant to allow uploading a screenshot to the internet > after a single keypress, we'd need at least some sort of confirmation dialog. I don't upload images, I just gave an example of tools that allow it. And yes, I totally agree with you. Upload everything automatically would light many red lights on privacy side. > I'll leave the bug open for now, but don't hold your breath for quick > progress. This needs more design work. Thank you, I really appreciate it. I'm not a programmer my self but I do have an idea how much hard work must be done before a feature like this be designed, implemented, tested... so on. My dirty workaround is serving me well for my needs. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 390415] Feature request - Spectacle - Save to file and clipboard
https://bugs.kde.org/show_bug.cgi?id=390415 --- Comment #4 from Joel Teixeira <joel...@gmail.com> --- (In reply to Nate Graham from comment #3) > I heavily use the workflow you mention in macOS: > > Hit Command-Shift-4 to invoke a rectangular region screenshot from anywhere, > then hold down control while you drag your box, and boom, I have a > screenshot in the clipboard, suitable for pasting into a chat window or > wherever else I'd like. This workflow is tracked by Bug 375382, with a patch > undergoing review patch: https://phabricator.kde.org/D9117 > > But for this workflow, of what use is it to *also* save the screenshot to > disk somewhere? The whole point here is to quickly get a screenshot into > your clipboard. It seems like also saving it to disk would just lead to a > lot of clutter, no? What's the use case? Hi Nate, unfortunatelly I'm not familiar with MacOS but is good to know it offers similar function. You understood right, my goal is to quickly have that region I crop on my hard drive and at the same time on clipboard for a miscelaneous usage cases. I don't see as a clutter at all since, just for instance, many programs apply compression on the pictures after paste. Eg, whatsapp messenger. CherryTree when resizing after paste and so on. Having a centralized, full quality, date organized of all the screenshots I took seems like a very good practice and still uses so little of nowadays storages devices. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 390415] Feature request - Spectacle - Save to file and clipboard
https://bugs.kde.org/show_bug.cgi?id=390415 --- Comment #2 from Joel Teixeira <joel...@gmail.com> --- Hi Henrik, thanks for your input. About "Ctrl + C", "Ctrl+S" being quick: I use screenshot mostly for region screenshots (not fullscreen) to paste on other programs like CherryTree, telegram. Following this recommendation I would probably need to take the screenshot (region), open the file on a image viewer, control+c, alternate to destination program (telegram, email, libreoffice writer...) and control+V. Maybe I'm there's short path for this, in this case please let me know. Doesn't seem quick to me but being relative, let's say, would it still be quick considering 50 screenshots? See, the alterante method, I press the printscreen key, select region, and it's already there, saved on my disk and ready to paste wherever I need. We have free (lightscreen) and comercial (greenshot on mac) tools already providing this feature. But I, particularly, don't want to use those. I would like to use Spectacle for that. About "What if someone wants "Export to Imgur, save to clipboard and print" as a new combination?" I'd say, it would make Spectacle even better. Both tools mentioned above already offers auto save+clipboard+imgurl out of the box. But then again, I would love to see this feature on Spectacle not on them. Doesn't need to be a default option, but on the user side is just a checkbox. My particular use case: Like I said, I use it mostly for regions and paste direct on CherryTree (sometimes telegram, whastapp...). Opening the saved file just add unnecessery steps on my workflow. The path on clipboard doesn't seem to help in anyway as well. Looking for a workaround for this, I found tons of posts on forums, articles and et cetera. So doesn't seem to be a particular scenario but needed by many people out there. If you need evidence of demand, to justify the need, I can provide N sources to you. My dirty workaround, saved as sstime.sh and linked to Printscreen key. #!/bin/bash export sstime="/home/username/Pictures/screenshots/`date '+%Y-%m-%d %H_%M_%S'`.png"; spectacle -nbr -o "$sstime" && xclip -sel clip -t image/png "$sstime" && notify-send "Screenshot saved in ~/Pictures/screenshots" -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 390415] New: Feature request - Spectacle - Save to file and clipboard
https://bugs.kde.org/show_bug.cgi?id=390415 Bug ID: 390415 Summary: Feature request - Spectacle - Save to file and clipboard Product: Spectacle Version: 17.12.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: joel...@gmail.com Target Milestone: --- Please add a feature/option to save to file and clipboard at the same time. Not sure if it's relevant but just to mention one app that offer this feature on another platform is Greenshot. Would love to have it on spectacle as well. Thank you, Joel Teixeira -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 385100] Moving window to another activity
https://bugs.kde.org/show_bug.cgi?id=385100 Joel <joel.porq...@gmail.com> changed: What|Removed |Added CC||joel.porq...@gmail.com --- Comment #1 from Joel <joel.porq...@gmail.com> --- I've been encountering a similar behavior for a long time (maybe since I've started using activities but I don't exactly remember). Moving a window from Activity A to Activity B requires two steps: - First, move it to All Activities (note that clicking on Activity B in the menu moves the window to All Activities anyway) - Second, move it to Activity B I don't know if https://bugs.kde.org/show_bug.cgi?id=382802 is a duplicate of this bug too. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 382605] Exported video has lag or stutter on 4k
https://bugs.kde.org/show_bug.cgi?id=382605 --- Comment #1 from Joel G <joel.gi...@gmail.com> --- @jb I have now come to learn that this lag is an experience of my laptop and not reporduceable in other computers which better handle 4K video files. I am not familiar with graphic stack in linu but I wonder if Wayland has sth to do with it. Regardless, this has now proven to be unrelated to Kdenlive. This bug can be disregarded. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 382605] New: Exported video has lag or stutter on 4k
https://bugs.kde.org/show_bug.cgi?id=382605 Bug ID: 382605 Summary: Exported video has lag or stutter on 4k Product: kdenlive Version: 17.04.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: joel.gi...@gmail.com Target Milestone: --- When working with high quality photos for timelapse projects, once the video has been exported, the output video has a feeling of lag or stutter. As if several frames had been dropped. I've been using 5184x3456 JPG images to create timelapses. Ideally I try to use 4k UHD projects but more often than not (maybe 80% of the time) the video results in a lagged or stutter artifiact mostly at the beginning of the video. This unwanted playback diminishes at 2k (around 10%), and is not present at FullHD (1080). I have not made enough tests to decide if having edits (saturation, sharpen, curves) have a significant effect on the results above but I believe so. I can say that FPSs doesn't seem to affect this problem though. I have ~20 different set of timelapse photos to put together, I've been able to notice this pattern very consistently. Whenever the 4k attempt has artifacts I go down to 2k to go around it but it effectively means I'm not able to output reliable 4k videos. Not sure how to provide debug logs but will keep an eye on this in case someone can provide some instructions. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 355410] Scroll speed of QML scroll area is too slow with the xf86-input-libinput driver
https://bugs.kde.org/show_bug.cgi?id=355410 Joel <joel.porq...@gmail.com> changed: What|Removed |Added CC||joel.porq...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 379493] New: Kwin Crashes rarely on pinentry dialog
https://bugs.kde.org/show_bug.cgi?id=379493 Bug ID: 379493 Summary: Kwin Crashes rarely on pinentry dialog Product: kwin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: jv...@altsci.com Target Milestone: --- Created attachment 105333 --> https://bugs.kde.org/attachment.cgi?id=105333=edit Kwin crash data I wrote a mail client that uses gpgme to handle PGP. On rare occasion (1/50 or so decryption/signs) kwin will crash as pinentry pops up. The crash handler comes up and I save the crash information. I am happy to help debug this issue as it is blocking release of my mail client. I hope very much that someone will be able to find a reliable repro this issue or fix it. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377708] KMail doesn't remember to render in HTML
https://bugs.kde.org/show_bug.cgi?id=377708 --- Comment #5 from Joel Koreth <joelsy...@gmail.com> --- (In reply to Allen Winter from comment #1) > It may be the same thing I am seeing. If you don't have the "show HTML bar" > option set then you won't see the HTML. > > configure->appearance->message window->show html bar must be set else I > don't see the HTML version of the message. You mean the HTML Sidebar? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377708] KMail doesn't remember to render in HTML
https://bugs.kde.org/show_bug.cgi?id=377708 Joel Koreth <joelsy...@gmail.com> changed: What|Removed |Added Platform|Neon Packages |openSUSE RPMs --- Comment #4 from Joel Koreth <joelsy...@gmail.com> --- (In reply to Laurent Montel from comment #2) > It works fine here. > What is you kmail version ? 5.4.3 (Although this bug has been present for previous versions) When you mean it works fine, have you toggled the Security -> Reading -> 'Prefer HTML to plain text', closed, relaunched kontact/kmail to find that it renders html messages without any additional work? Because in my case ill need to retoggle the Security -> Reading -> 'Prefer HTML to plain text' for Kmail to render an html message. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 377708] New: KMail doesn't remember to render in HTML
https://bugs.kde.org/show_bug.cgi?id=377708 Bug ID: 377708 Summary: KMail doesn't remember to render in HTML Product: kmail2 Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: joelsy...@gmail.com Target Milestone: --- Even if in Security -> Reading -> 'Prefer HTML to plain text' is toggled. On next startup KMail will open messages in plain text mode. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377674] New: WARNING_README.txt in home folder
https://bugs.kde.org/show_bug.cgi?id=377674 Bug ID: 377674 Summary: WARNING_README.txt in home folder Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: joelsy...@gmail.com Target Milestone: --- File showed up Sunday, March 12, 2017. File contains - "Important Warning!!! Don't create or copy files inside this folder manually, they are managed by the Akonadi framework!" I did add Google Calendars that day and maybe 2 email accounts if that helps. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376731] Odd numbering and listing of desktops.
https://bugs.kde.org/show_bug.cgi?id=376731 --- Comment #9 from Joel Koreth <joelsy...@gmail.com> --- Sorry to bother but has there been any conclusion for this? I know it's a small paper cut but for a user it's an odd to thing to see out of the box for a default naming convention. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 377409] New: On first launch, Kontact crahes due to a creation of collection inbox bug
https://bugs.kde.org/show_bug.cgi?id=377409 Bug ID: 377409 Summary: On first launch, Kontact crahes due to a creation of collection inbox bug Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: joelsy...@gmail.com Target Milestone: --- On first launch the following dialogs pop up Kontact Screen Pops up Account Wizard and a Error dialog "The Email program encountered a fatal error and will terminate now. The error was: Could not create collection inbox, resourceId: 3" Program Crashes on any other button click -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376731] Odd numbering and listing of desktops.
https://bugs.kde.org/show_bug.cgi?id=376731 --- Comment #6 from Joel Koreth <joelsy...@gmail.com> --- On Monday, February 20, 2017 8:55:18 PM CST you wrote: > https://bugs.kde.org/show_bug.cgi?id=376731 > > Martin Gräßlin <mgraess...@kde.org> changed: > >What|Removed |Added > > Component|general |core > > --- Comment #5 from Martin Gräßlin <mgraess...@kde.org> --- > I don't think colons or a hyphen would improve it in the general case. It > could be still looking weird especially in right to left languages. > > Personally I would say the numbers in the beginning need to go. But they are > also used as accelerators. What does used as accelerators mean? I also believe it is best if the numbers are completely removed due to the redundancy from the default settings. A user will be confused about the point of the naming convention if by default it's move to "1: Desktop 1" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376731] Odd numbering and listing of desktops.
https://bugs.kde.org/show_bug.cgi?id=376731 --- Comment #2 from Joel Koreth <joelsy...@gmail.com> --- (In reply to kishore96 from comment #1) > There is an option to change the names assigned to virtual desktops. I'm > assuming this behaviour is there so that if the desktop name is changed, it > can display '$desktop_number $desktop_name' I know this is a weird question to ask but are you a mallu? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 376731] New: Odd numbering and listing of desktops.
https://bugs.kde.org/show_bug.cgi?id=376731 Bug ID: 376731 Summary: Odd numbering and listing of desktops. Product: kwin Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: joelsy...@gmail.com Target Milestone: --- Right Click on an applications's window. Hover over to move to desktop. The options listed for me are - All Desktops 1 Desktop 1 2 Desktop 2 3 Desktop 3 4 Desktop 4 5 Desktop 5 6 Desktop 6 Plasma Version : 5.83 Frameworks Version : 5.26 Possibly related to : https://bugs.kde.org/show_bug.cgi?id=376730 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376730] Move to Desktop duplicates desktop name
https://bugs.kde.org/show_bug.cgi?id=376730 --- Comment #1 from Joel Koreth <joelsy...@gmail.com> --- Possibly related to : https://bugs.kde.org/show_bug.cgi?id=376731 -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 365370] Cannot set a todo list from google calendar as default calendar for saving to do's
https://bugs.kde.org/show_bug.cgi?id=365370 Joel Koreth <joelsy...@gmail.com> changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376730] New: Move to Desktop duplicates desktop name
https://bugs.kde.org/show_bug.cgi?id=376730 Bug ID: 376730 Summary: Move to Desktop duplicates desktop name Product: plasmashell Version: master Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: joelsy...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Right Click an application in the task manager Hover over dialog to "Move to Desktop" The options listed are - Move to Current Desktop All Desktops 1 Desktop Desktop 1 2 Desktop Desktop 2 3 Desktop Desktop 3 4 Desktop Desktop 4 5 Desktop Desktop 5 6 Desktop Desktop 6 Plasma Version : 5.83 Frameworks Version : 5.26 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 374304] New: manual entry of numbers below root tag in tag hierarchy
https://bugs.kde.org/show_bug.cgi?id=374304 Bug ID: 374304 Summary: manual entry of numbers below root tag in tag hierarchy Product: digikam Version: 5.3.0 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Tags Assignee: digikam-de...@kde.org Reporter: ruprechtj...@gmail.com Target Milestone: --- I am tagging a large number of wildlife photos in which I need to identify the number of individuals of each species in each photo. I currently have a tag hierarchy similar to the reduced version below, in which I tag the species, then the number of individuals of that species in each photo: -species 1 -1 individual -2 individuals -... -50 individuals -species 2 -1 individual -2 individuals -... -50 individuals etc... It is very cumbersome to have so many tags for the number of individuals of each species because the tag tree becomes extremely large. I suggest an option for manual entry of numbers below a root tag. Then one could do something like this: -species 1 - (manual entry of a number) -species 2 - (manual entry of a number) etc... This would greatly streamline the tagging process for users requiring to change the number of objects below a root tag in each photo without having a huge list of tags. Thanks for the consideration, and all the great work on this software! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 374125] New: Setting a Google To do calendar for display in clock causes desktop to crash.
https://bugs.kde.org/show_bug.cgi?id=374125 Bug ID: 374125 Summary: Setting a Google To do calendar for display in clock causes desktop to crash. Product: plasmashell Version: 5.8.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: joelsy...@gmail.com Target Milestone: 1.0 Setting a Google To Do Calendar for display in the Digital Clock widget with the PIM Calendar plugin causes it to quickly take up all available memory and crash within 5 minutes. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373902] New: Sweeper Icon Missing From Title Bar
https://bugs.kde.org/show_bug.cgi?id=373902 Bug ID: 373902 Summary: Sweeper Icon Missing From Title Bar Product: Breeze Version: 5.8.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: joelsy...@gmail.com CC: kain...@gmail.com Target Milestone: --- Plasma : 5.8.4 KDE Frameworks : 5.29.0 Qt Version : 5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 366491] kdeconnect destroy dolphin
https://bugs.kde.org/show_bug.cgi?id=366491 --- Comment #2 from Joel Koreth <joelsy...@gmail.com> --- Resolved duplicate of https://bugs.kde.org/show_bug.cgi?id=368367 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365358] Dolphin crashed after UI freeze after trying to send an email via Kmail
https://bugs.kde.org/show_bug.cgi?id=365358 --- Comment #2 from Joel Koreth <joelsy...@gmail.com> --- Duplicate of https://bugs.kde.org/show_bug.cgi?id=334640 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365358] Dolphin crashed after UI freeze after trying to send an email via Kmail
https://bugs.kde.org/show_bug.cgi?id=365358 Joel Koreth <joelsy...@gmail.com> changed: What|Removed |Added CC||joelsy...@gmail.com --- Comment #1 from Joel Koreth <joelsy...@gmail.com> --- I can't reproduce this on my end. Enviroment info- Version 16.08.3 KDE Frameworks 5.28.0 Qt 5.7.0 (built against 5.7.0) Distro : openSUSE Tumbleweed 20161128 Snapshot A UI freeze may indicate a more widespread problem in your system (especially with 2 unrelated products), is this constantly reproducible for you? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362260] Dolphin crashed
https://bugs.kde.org/show_bug.cgi?id=362260 --- Comment #2 from Joel Koreth <joelsy...@gmail.com> --- Possible resolved duplicate of https://bugs.kde.org/show_bug.cgi?id=208916 or https://bugs.kde.org/show_bug.cgi?id=206812. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 364621] Dolphin crashes when one drags a device into the file window
https://bugs.kde.org/show_bug.cgi?id=364621 Joel Koreth <joelsy...@gmail.com> changed: What|Removed |Added CC||joelsy...@gmail.com --- Comment #1 from Joel Koreth <joelsy...@gmail.com> --- Hey I can't reproduce this on my end. If a device is dragged to the file window, on my machine at least, dolphin has a menu asking the user whether the user wants to copy it over, link it, or cancel. Possibly fixed? Environment info Version 16.08.3 KDE Frameworks 5.28.0 Qt 5.7.0 (built against 5.7.0) Distro : openSUSE Tumbleweed 20161128 Snapshot -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 366491] kdeconnect destroy dolphin
https://bugs.kde.org/show_bug.cgi?id=366491 Joel Koreth <joelsy...@gmail.com> changed: What|Removed |Added CC||joelsy...@gmail.com --- Comment #1 from Joel Koreth <joelsy...@gmail.com> --- I can't reproduce this on my end. Is this crash instantaneous after opening a connection to an Android filesystem through kdeconnect for you or is it at random while browsing or moving? Environment info Version 16.08.3 KDE Frameworks 5.28.0 Qt 5.7.0 (built against 5.7.0) Distro : openSUSE Tumbleweed 20161128 Snapshot Title needs to be updated to kdeconnect crashes dolphin. Possibly Related [kdeconnect uses sftp to access android filesystems] https://bugs.kde.org/show_bug.cgi?id=364677 https://bugs.kde.org/show_bug.cgi?id=370370 https://bugs.kde.org/show_bug.cgi?id=362843 https://bugs.kde.org/show_bug.cgi?id=359936 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362260] Dolphin crashed
https://bugs.kde.org/show_bug.cgi?id=362260 Joel Koreth <joelsy...@gmail.com> changed: What|Removed |Added CC||joelsy...@gmail.com --- Comment #1 from Joel Koreth <joelsy...@gmail.com> --- I can't reproduce this on my end. Environment info Version 16.08.3 KDE Frameworks 5.28.0 Qt 5.7.0 (built against 5.7.0) Distro : openSUSE Tumbleweed 20161128 Snapshot Title needs to be updated to "Dolphin crashed while mounting two volumes in a split view." or something similar instead of this generic one. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 361788] Show Menubar check box toggle can become the inverse of the menubar's actual state, menubar flicker
https://bugs.kde.org/show_bug.cgi?id=361788 Joel Koreth <joelsy...@gmail.com> changed: What|Removed |Added CC||joelsy...@gmail.com --- Comment #1 from Joel Koreth <joelsy...@gmail.com> --- I can confirm on my machine. Machine specs - Version 16.08.3 KDE Frameworks 5.28.0 Qt 5.7.0 (built against 5.7.0) Distro : openSUSE Tumbleweed 20161128 Snapshot The issue does go away like Tara said by just closing and opening Dolphin and so this is a minor glitch -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 364342] KRunner crash by Akonadi's PIMContactsRunner
https://bugs.kde.org/show_bug.cgi?id=364342 Joel Koreth <joelsy...@gmail.com> changed: What|Removed |Added CC||joelsy...@gmail.com --- Comment #18 from Joel Koreth <joelsy...@gmail.com> --- *** Bug 368669 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368669] Krunner crashes while using the calculator plugin
https://bugs.kde.org/show_bug.cgi?id=368669 Joel Koreth <joelsy...@gmail.com> changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #3 from Joel Koreth <joelsy...@gmail.com> --- (In reply to Denis Kurz from comment #1) > Joel, can you please check if this still happens with the Contacts runner > disabled? You can disable it by opening krunner, clicking on the settings > button left of krunner's text field, and unchecking "Contacts" > (alternatively, "System settings" -> "Search" -> "Contacts"). I think that > this is a duplicate of bug 364342, which is fixed in KDE Applications > 16.08.1. It seems unrelated at first glance, but crashing during simple > calculations is how the bug manifested for me, too. > > If krunner still crashes with the Contacts runner disabled, please add a > stack trace and state the version of your KDE Applications. The crashing > component might not be part of the Plasma suite. Hey Denis, You are right this is a duplicate of bug 364342 and krunner does not crash anymore with the Contacts plugin disabled although like you said it was an odd thing to cause crashing with calculations. I put the status of the bug as resolved and duplicate of 364342. *** This bug has been marked as a duplicate of bug 364342 *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 368669] New: Krunner crashes while using the calculator plugin
https://bugs.kde.org/show_bug.cgi?id=368669 Bug ID: 368669 Summary: Krunner crashes while using the calculator plugin Product: krunner Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: calculator Assignee: k...@privat.broulik.de Reporter: joelsy...@gmail.com Note : I have plasma 5.7.4 with openSUSE Tumbleweed but it is not an option in the version above Doing any calculations (example : 2+2) results in krunner crashing Reproducible: Always Steps to Reproduce: 1. open krunner 2. type 2+2 with calculator plugin enabled 3. enjoy the crashing Actual Results: Crashing but result is calculated successfully before disappearing Expected Results: The result should be displayed as usual -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #66 from Joel <jo...@dabbles-n-doodads.com> --- Playing with this a bit more I found this works best for me, killall plasmashell; nohup plasmashell >/dev/null 2>&1 & Now I can close the terminal when done and it does not create an ever growing nohup.out file. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #65 from Joel <jo...@dabbles-n-doodads.com> --- typo, killall plasmashell && nohup plasmashell -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #64 from Joel <jo...@dabbles-n-doodads.com> --- I tried this and it does seem to work. I had to add nohup so I could close the terminal window. killall pasmashell && nohup plasmashell -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 365370] Cannot set a todo list from google calendar as default calendar for saving to do's
https://bugs.kde.org/show_bug.cgi?id=365370 Joel Koreth <joelsy...@gmail.com> changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 365370] New: Cannot set a todo list from google calendar as default calendar for saving to do's
https://bugs.kde.org/show_bug.cgi?id=365370 Bug ID: 365370 Summary: Cannot set a todo list from google calendar as default calendar for saving to do's Product: korganizer Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: todoview Assignee: korganizer-de...@kde.org Reporter: joelsy...@gmail.com I set new events and to do's be added to a standard calendar in korg settings. I set my google to do list as my default calendar but it still asks for which calendar to save when creating a new to do. Reproducible: Always Steps to Reproduce: 1. Go to Korganizer settings 2. Under General and Save Tab 3. Set to do's and events be added to standard calendar 4. set a to do list as a default calendar 5. Cry in frustration as the program still asks for which calendar to save in. Actual Results: The program still asks for which calendar to save in when creating new to do's Expected Results: The programs should have added new to do's to the default calendar without additional confirmation which the KDE4x Korg still does wonderfully I use openSUSE Tumbleweed and have had problems sending emails in Kmail with an error message about an invalid dbus response but will create another report for that. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 --- Comment #32 from Joel <jo...@dabbles-n-doodads.com> --- I just went back and looked more at my missing program launchers. What I found is that a new blank panel was overlaying the original. When I deleted the panel, the one I set up with the launchers was underneath. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 353975] Black screen on second display.
https://bugs.kde.org/show_bug.cgi?id=353975 Joel <jo...@dabbles-n-doodads.com> changed: What|Removed |Added CC||jo...@dabbles-n-doodads.com --- Comment #31 from Joel <jo...@dabbles-n-doodads.com> --- Another with the same issue ( and more ). Logging out and back in usually fixes the unresponsive black screen. I have the added issue of any program launchers I've added to the panel or favorites seem to be gone for good. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362916] New: Plasma crashes while leaving session
https://bugs.kde.org/show_bug.cgi?id=362916 Bug ID: 362916 Summary: Plasma crashes while leaving session Product: plasmashell Version: 5.6.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: joelsy...@gmail.com Plasma crashes while leaving session. After clicking log out for example, Plasma hangs up and then crashes but quickly comes back and resumes logging out Reproducible: Always Steps to Reproduce: 1.Click Logout from the Application menu 2.Wait 3.Crashes 4. Comes back and Logs out Actual Results: Crashing Expected Results: Plasma should not crash -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 360627] New: Adding Dropbox account gives: This app has reached its user limit
https://bugs.kde.org/show_bug.cgi?id=360627 Bug ID: 360627 Summary: Adding Dropbox account gives: This app has reached its user limit Product: storageservicemanager Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: onelove.nyahbi...@gmail.com After trying to add my dropbox account i got the following message: "This app has reached its user limit. Contact the app developer and ask them to use the Dropbox API App Console to increase their app's user limit." Can this be fixed? Reproducible: Always Steps to Reproduce: 1.open Storage Service Manager 2.configure-add account-dropbox 3.sign-in Actual Results: This app has reached its user limit. Contact the app developer and ask them to use the Dropbox API App Console to increase their app's user limit. Expected Results: the software should of verified the dropbox account currently have googledrive yousendit and box accounts added succesfully... only problem is with dropbox. -- You are receiving this mail because: You are watching all bug changes.
[storageservicemanager] [Bug 360628] New: Yousendit should be renamed to hightail
https://bugs.kde.org/show_bug.cgi?id=360628 Bug ID: 360628 Summary: Yousendit should be renamed to hightail Product: storageservicemanager Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mon...@kde.org Reporter: onelove.nyahbi...@gmail.com The YouSendIt account service should be renamed to Hightail for accuracy purposes. Reproducible: Always YouSendIt changed its name to Hightail since 2013. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 359520] Dolphin crashes when trying to copy a file
https://bugs.kde.org/show_bug.cgi?id=359520 Joel Koreth <joelsy...@gmail.com> changed: What|Removed |Added CC||joelsy...@gmail.com --- Comment #1 from Joel Koreth <joelsy...@gmail.com> --- I can confirm this on Opensuse Leap on 5.5.95 with KF5 and KDE Application and KDE Extra repos enabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359440] New: Plasma shell crash
https://bugs.kde.org/show_bug.cgi?id=359440 Bug ID: 359440 Summary: Plasma shell crash Product: plasmashell Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: joelsy...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Using Intellij and Vivaldi - Unusual behavior I noticed: Perhaps some lack fluidity with some effects? - Custom settings of the application: Using the newest AMD Driver along with newest "stable" plasma from the kf5 and kde extra repos in opensuse Leap -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1e6f5a77c0 (LWP 14766))] Thread 12 (Thread 0x7f1e5a345700 (LWP 14769)): #0 0x7f1e68a42c1d in poll () at /lib64/libc.so.6 #1 0x7f1e6d9e1422 in () at /usr/lib64/libxcb.so.1 #2 0x7f1e6d9e300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f1e5cafe3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f1e6914132f in () at /usr/lib64/libQt5Core.so.5 #5 0x7f1e6823e0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f1e68a4b04d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f1e531c5700 (LWP 14776)): #0 0x7f1e68a3eced in read () at /lib64/libc.so.6 #1 0x7f1e650fab60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1e650b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1e650b9df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f1e650b9f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f1e69373d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f1e6931ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f1e6913c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f1e6c486df8 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f1e6914132f in () at /usr/lib64/libQt5Core.so.5 #10 0x7f1e6823e0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f1e68a4b04d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f1e433a5700 (LWP 14777)): #0 0x7f1e68a3eced in read () at /lib64/libc.so.6 #1 0x7f1e650fab60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1e650b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1e650b9df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f1e650b9f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f1e69373d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f1e6931ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f1e6913c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f1e6c486df8 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7f1e6914132f in () at /usr/lib64/libQt5Core.so.5 #10 0x7f1e6823e0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f1e68a4b04d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f1e41add700 (LWP 14778)): #0 0x7f1e68a42c1d in poll () at /lib64/libc.so.6 #1 0x7f1e650b9e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1e650b9f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1e69373d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f1e6931ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f1e6913c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f1e6c486df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f1e6914132f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f1e6823e0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f1e68a4b04d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f1e3a4bd700 (LWP 14779)): #0 0x7f1e6824205f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1e6ec7986b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f1e6ec79899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f1e6823e0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f1e68a4b04d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f1db32c5700 (LWP 14781)): #0 0x7f1e68a42c1d in poll () at /lib64/libc.so.6 #1 0x7f1e650b9e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1e650b9f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1e69373d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f1e6931ad53 in QEventLoop::exec(QFlags) () at
[plasmashell] [Bug 359438] New: Kwin & Plasma Crash
https://bugs.kde.org/show_bug.cgi?id=359438 Bug ID: 359438 Summary: Kwin & Plasma Crash Product: plasmashell Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: joelsy...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Resizing a Window - Custom settings of the application: I have the AMD Driver installed and am using the latest plasma from KF5 and KDE Extra repos. I had OpenGL 3.1 enabled as the compositor instead of 2.0? The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe3fe3ec7c0 (LWP 1722))] Thread 19 (Thread 0x7fe3e9185700 (LWP 1723)): #0 0x7fe3f7882c1d in poll () at /lib64/libc.so.6 #1 0x7fe3fc821422 in () at /usr/lib64/libxcb.so.1 #2 0x7fe3fc82300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fe3eb93e3c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fe3f7f8132f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fe3f707e0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fe3f788b04d in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7fe3e1fbd700 (LWP 1744)): #0 0x7fe3f787eced in read () at /lib64/libc.so.6 #1 0x7fe3f3f3ab60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe3f3ef in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe3f3ef9df8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe3f3ef9f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe3f81b3d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe3f815ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fe3f7f7c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fe3fb2c6df8 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7fe3f7f8132f in () at /usr/lib64/libQt5Core.so.5 #10 0x7fe3f707e0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7fe3f788b04d in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7fe3d21dd700 (LWP 2304)): #0 0x7fe3f7f79c4f in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #1 0x7fe3f81b3cb5 in () at /usr/lib64/libQt5Core.so.5 #2 0x7fe3f3ef94ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe3f3ef9d80 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe3f3ef9f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fe3f81b3d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe3f815ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fe3f7f7c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fe3fb2c6df8 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7fe3f7f8132f in () at /usr/lib64/libQt5Core.so.5 #10 0x7fe3f707e0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7fe3f788b04d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7fe3d0925700 (LWP 2306)): #0 0x7fe3f3f3bd14 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fe3f3ef989b in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe3f3ef9df8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe3f3ef9f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fe3f81b3d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe3f815ad53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fe3f7f7c61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fe3fb2c6df8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fe3f7f8132f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fe3f707e0a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fe3f788b04d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fe3c931d700 (LWP 2324)): #0 0x7fe3f708205f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe3fdab986b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fe3fdab9899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fe3f707e0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fe3f788b04d in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fe3420e5700 (LWP 2343)): #0 0x7fe3f787eced in read () at /lib64/libc.so.6 #1 0x7fe3f3f3ab60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe3f3ef in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe3f3ef9df8 in () at
[systemsettings] [Bug 359411] New: Changing Buttons on Window Decorations Sometimes
https://bugs.kde.org/show_bug.cgi?id=359411 Bug ID: 359411 Summary: Changing Buttons on Window Decorations Sometimes Product: systemsettings Version: 5.5.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: joelsy...@gmail.com Application: systemsettings5 (5.5.4) Qt Version: 5.5.1 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Changing Buttons on Window Decorations Sometimes - Unusual behavior I noticed: Changing window size was choppy and didn't resize correctly - Custom settings of the application: AMD Driver Installation Opensuse KDE Extra and KF5 repos enabled and vedored changed too The crash can be reproduced sometimes. -- Backtrace: Application: System Settings (systemsettings5), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd707b36780 (LWP 25765))] Thread 5 (Thread 0x7fd6f6918700 (LWP 25766)): #0 0x7fd703815c1d in poll () at /lib64/libc.so.6 #1 0x7fd7005ac422 in () at /usr/lib64/libxcb.so.1 #2 0x7fd7005ae00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fd6f92d93c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fd703f1432f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd6ffd210a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd70381e04d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fd6e20b6700 (LWP 25769)): #0 0x7fff1fdf3d33 in clock_gettime () #1 0x7fd70382ac9d in clock_gettime () at /lib64/libc.so.6 #2 0x7fd703fc57d6 in () at /usr/lib64/libQt5Core.so.5 #3 0x7fd7041453b9 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #4 0x7fd704145945 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd704146b5e in () at /usr/lib64/libQt5Core.so.5 #6 0x7fd6ff7fc4ad in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #7 0x7fd6ff7fcd80 in () at /usr/lib64/libglib-2.0.so.0 #8 0x7fd6ff7fcf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #9 0x7fd704146d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7fd7040edd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #11 0x7fd703f0f61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #12 0x7fd702479df8 in () at /usr/lib64/libQt5Qml.so.5 #13 0x7fd703f1432f in () at /usr/lib64/libQt5Core.so.5 #14 0x7fd6ffd210a4 in start_thread () at /lib64/libpthread.so.0 #15 0x7fd70381e04d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fd6d99b0700 (LWP 25770)): #0 0x7fd6ffd2505f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd703f1534b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fd70294725b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7fd7029476f3 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7fd703f1432f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd6ffd210a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd70381e04d in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fd6d91af700 (LWP 25771)): #0 0x7fd6ff83ecf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd6ff7fc8fc in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd6ff7fcdf8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd6ff7fcf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd704146d8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd7040edd53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd703f0f61a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fd702479df8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fd703f1432f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fd6ffd210a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fd70381e04d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fd707b36780 (LWP 25765)): [KCrash Handler] #6 0x7fd70376e187 in raise () at /lib64/libc.so.6 #7 0x7fd70376f538 in abort () at /lib64/libc.so.6 #8 0x7fd703b77b8d in __gnu_cxx::__verbose_terminate_handler() () at /usr/lib64/libstdc++.so.6 #9 0x7fd703b75bf6 in () at /usr/lib64/libstdc++.so.6 #10 0x7fd703b75c41 in () at /usr/lib64/libstdc++.so.6 #11 0x7fd703b75ea6 in __cxa_rethrow () at /usr/lib64/libstdc++.so.6 #12 0x7fd7040a1a0b in () at /usr/lib64/libQt5Core.so.5 #13 0x7fd70409cddc in QAbstractItemModel::endMoveRows() () at /usr/lib64/libQt5Core.so.5 #14 0x7fd6e2eae40f in () at /usr/lib64/qt5/plugins/kcm_kwindecoration.so #15 0x7fd6e2eaeef3
[kxkb] [Bug 355602] Custom XKB layout set through xkbcomp keeps being reset
https://bugs.kde.org/show_bug.cgi?id=355602 --- Comment #1 from Joel <joel.porq...@gmail.com> --- I forgot to add in the bug description that my custom xkb layout is installed through an autostart script. I played a bit more with it and found that the script is executed but is quickly overridden when Plasma starts. Basically, I created a script that performs the xkb modification and also touches a file in my home. After logging into Plasma, the file is created in my home but the xkb modification is not effective. If I relaunch the script by itself, I get my custom xkb layout. My guess is that my custom layout run by the autostart script is quickly erased by a another layout configuration from Plasma. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 355602] Autostart script with custom XKB layout is erased when logging in
https://bugs.kde.org/show_bug.cgi?id=355602 Joel <joel.porq...@gmail.com> changed: What|Removed |Added Summary|Custom XKB layout set |Autostart script with |through xkbcomp keeps being |custom XKB layout is erased |reset |when logging in Product|kxkb|systemsettings Component|general |kcm_autostart -- You are receiving this mail because: You are watching all bug changes.
