[krita] [Bug 477265] Watercolor brushes no longer render
https://bugs.kde.org/show_bug.cgi?id=477265 Nikolay changed: What|Removed |Added CC||nemi...@gmail.com --- Comment #1 from Nikolay --- Created attachment 163950 --> https://bugs.kde.org/attachment.cgi?id=163950&action=edit How the brush works in version 5.2.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477265] Watercolor brushes no longer render
https://bugs.kde.org/show_bug.cgi?id=477265 --- Comment #2 from Nikolay --- Created attachment 163951 --> https://bugs.kde.org/attachment.cgi?id=163951&action=edit How the brush works in version 5.2.1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 477265] Watercolor brushes no longer render
https://bugs.kde.org/show_bug.cgi?id=477265 --- Comment #3 from Nikolay --- I tried to figure it out. It seems that the "dark replacement" overlay mode for masked brushes does not work correctly -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480998] In KDE Neon testing external monitor with a capability of 120 hz displays only 60 when trying to set 120.
https://bugs.kde.org/show_bug.cgi?id=480998 --- Comment #2 from Nikolay --- (In reply to Zamundaaa from comment #1) > Could you describe in more detail what the problem is? Do the display > settings only allow you to go up to 60Hz, or can you set it to 120Hz but the > monitor shows that it's only doing 60Hz, or does it actually go to 120Hz but > feels slower than it should? > > Also, what exact laptop are you using? In default mode external monitor use 2560x1440@60 it works, but when I try switch to 2560x1440@120 monitor frozen about 3 seconds, firefox crashed and monitor anyway in 60 gz mode Laptop is asus rog flow x13 2023 with amd ryzem 7940hs and 780m graphics. drm info - https://drive.google.com/file/d/1q4pVVL36NOhZXQhXJQenMkFmVBX_ArJi/view?usp=sharing drm info in Fedora 39 gnome when it works properly - https://drive.google.com/file/d/1ESA4P03WMiMz_41LrZnWsLp-64waLYuL/view?usp=sharing And I see problems with graphics in 165 gz internal monitor in 60 gz on external it's ok video - https://drive.google.com/file/d/12p-dErQNivp0LI8KwWN4ZyQjBu4hWjr8/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480995] In KDE Neon testing native monitor display only one color on rog flow x13 with right display of external monitor
https://bugs.kde.org/show_bug.cgi?id=480995 --- Comment #6 from Nikolay --- (In reply to fanzhuyifan from comment #2) > Waiting for photos and the output of drm_info Can you see the problem? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480998] In KDE Neon testing external monitor with a capability of 120 hz displays only 60 when trying to set 120.
https://bugs.kde.org/show_bug.cgi?id=480998 --- Comment #4 from Nikolay --- (In reply to Zamundaaa from comment #3) > Okay. Could you try again with KWIN_DRM_PREFER_COLOR_DEPTH=24 in > /etc/environment ? Thanks! It works, my external monitor is now working correctly at 120 Hz, but the internal monitor still displays graphical errors when I switch virtual desktops or the dock at the bottom changes its position -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480998] In KDE Neon testing external monitor with a capability of 120 hz displays only 60 when trying to set 120.
https://bugs.kde.org/show_bug.cgi?id=480998 --- Comment #5 from Nikolay --- (In reply to Zamundaaa from comment #3) > Okay. Could you try again with KWIN_DRM_PREFER_COLOR_DEPTH=24 in > /etc/environment ? Internal monitor works without bugs when I switch from 165 gz to 96 or less -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480995] New: In KDE Neon testing native monitor display only one color on rog flow x13 with right display of external monitor
https://bugs.kde.org/show_bug.cgi?id=480995 Bug ID: 480995 Summary: In KDE Neon testing native monitor display only one color on rog flow x13 with right display of external monitor Classification: Plasma Product: kwin Version: 5.93.0 Platform: Neon OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: plastininiko...@yandex.ru Target Milestone: --- SUMMARY *** In KDE Neon testing native monitor display only one color on rog flow x13 with right display of external monitor *** STEPS TO REPRODUCE 1. launch KDE Neon with 165 ghz 2. wait a bit 3. see crush OBSERVED RESULT native monitor is filled with one summary color of desktop wallpapers EXPECTED RESULT Normal monitor behavior SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.93 KDE Neon Version: neon-testing-20240206-0538 Qt Version: 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480998] New: In KDE Neon testing external monitor with a capability of 120 hz displays only 60 when trying to set 144.
https://bugs.kde.org/show_bug.cgi?id=480998 Bug ID: 480998 Summary: In KDE Neon testing external monitor with a capability of 120 hz displays only 60 when trying to set 144. Classification: Plasma Product: kwin Version: 5.93.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: plastininiko...@yandex.ru Target Milestone: --- SUMMARY *** In KDE Neon testing external monitor with a capability of 120 ghz displays only 60 when trying to set 144. Right behaviour in windows 11 and fedora 39 gnome. *** STEPS TO REPRODUCE 1. Connect an external monitor to laptop with 120 hz via USB4 type C to the display port 2. Switch refresh rate to 120 hz. OBSERVED RESULT only 60 hz EXPECTED RESULT 120 hz SOFTWARE/OS VERSIONS Windows 11: work macOS: work Linux: Fedora 39 (gnome) work KDE Neon Version: neon-testing-20240206-0538 don't work -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480998] In KDE Neon testing external monitor with a capability of 120 hz displays only 60 when trying to set 120.
https://bugs.kde.org/show_bug.cgi?id=480998 Nikolay changed: What|Removed |Added Summary|In KDE Neon testing |In KDE Neon testing |external monitor with a |external monitor with a |capability of 120 hz|capability of 120 hz |displays only 60 when |displays only 60 when |trying to set 144. |trying to set 120. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480995] In KDE Neon testing native monitor display only one color on rog flow x13 with right display of external monitor
https://bugs.kde.org/show_bug.cgi?id=480995 --- Comment #3 from Nikolay --- Hmm, this bug has not appeared again, but there are graphic artifacts when i scroll virtual desktops and manipulate with windows drm info - https://drive.google.com/file/d/1q4pVVL36NOhZXQhXJQenMkFmVBX_ArJi/view?usp=sharing video - https://drive.google.com/file/d/123YZEX578uiq5puMds5LGqv8tZBdkXvq/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480995] In KDE Neon testing native monitor display only one color on rog flow x13 with right display of external monitor
https://bugs.kde.org/show_bug.cgi?id=480995 --- Comment #4 from Nikolay --- I see this bug again. This appears when i use hdr on the external monitor video - https://drive.google.com/file/d/12IOz3b4hIkbjr7oA01uTzf7dmLpXFqqF/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480995] In KDE Neon testing native monitor display only one color on rog flow x13 with right display of external monitor
https://bugs.kde.org/show_bug.cgi?id=480995 --- Comment #5 from Nikolay --- when I tried to watch the video and turned on the built-in plasma player, the system started displaying two monitors, but I couldn't manipulate the computer at all. Only move the cursor at 3 fps. Video - https://drive.google.com/file/d/12M8c2Fl1nsMRk237hO3f5Y5Rnn6bFnnB/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443227] New: The keyboard layout does not change through the tray using the mouse
https://bugs.kde.org/show_bug.cgi?id=443227 Bug ID: 443227 Summary: The keyboard layout does not change through the tray using the mouse Product: kwin Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: ko...@cyfra.ua Target Milestone: --- SUMMARY I am using 3 keyboard layouts (English, Ukrainian, Russian) and most of the time I am using two keyboard layouts (English and Ukrainian or English and Russian). To quickly change the keyboard layout I use the "Spare Layout" option (All Settings -> Input Devices -> Keyboard -> Layouts -> Spare Layouts). If I need to change a pair of keyboard layouts I using mouse and tray. Over the past few months, the keyboard layout with the mouse has not changed at all. The menu opens and responds to keys, but does not change the keyboard layout. STEPS TO REPRODUCE 1. Add more than two keyboard layouts 2. Turn on "Spare Layouts" and set "Main Layout count" to 2 3. Check "Spare Layouts" (Switching must be between two keyboard layouts) 4. Click right button of the mouse on the tray with languages 5. Select the spare language with the mouse and press the left button of the mouse 6. Check tray icon, must be with symbol/flag of new language 7. Now one of the languages will be replaced by a new one and again you can switch between the two keyboard layouts OBSERVED RESULT Language is not changing and icon too with the mouse EXPECTED RESULT Renewal of the ability to change the keyboard layout with the mouse and with the ability to change the backup layout SOFTWARE/OS VERSIONS Fedora release 34 (Thirty Four) KDE Plasma Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION kwin-libs-5.22.5-1.fc34.x86_64 kwin-common-5.22.5-1.fc34.x86_64 kwin-x11-5.22.5-1.fc34.x86_64 kwin-wayland-5.22.5-1.fc34.x86_64 kwin-5.22.5-1.fc34.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 444133] Transparent border around maximized windows when shadows are enabled
https://bugs.kde.org/show_bug.cgi?id=444133 Nikolay changed: What|Removed |Added CC||nikolaj1...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 440659] RDP closing
https://bugs.kde.org/show_bug.cgi?id=440659 NIkolay changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from NIkolay --- (In reply to Andrey E. from comment #2) > Created attachment 140680 [details] > KRDC windows doesn't have RDP option > Привет, я решил проблему. 1) Удалил все remmina, krdc, xfreerdp, конфиги от этих приложений. 2) Накатил заново KRDC, Remmina 3) Добавил подключение с базовыми настройками. Только адрес, логин и пароль. 4) На телефоне android проверил подключение через Microsoft Remote Desktop, нашёл ошибку с сертификатом, меня тупо из-за него не пускало. Но в логах нигде этого не было. Все настройки перепробовал. ;-) -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 440659] RDP closing
https://bugs.kde.org/show_bug.cgi?id=440659 NIkolay changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #6 from NIkolay --- (In reply to Andrey E. from comment #5) > (In reply to NIkolay from comment #3) > > (In reply to Andrey E. from comment #2) > > > Created attachment 140680 [details] > > > KRDC windows doesn't have RDP option > > > > > Привет, я решил проблему. > > 1) Удалил все remmina, krdc, xfreerdp, конфиги от этих приложений. > > На всякий случай спрошу по-английски: > Where can I find all config files required for deleting? > I tried to uninstall and reinstall KRDC (I didn't have Remmina), but RDP > option still doesn't appear. включи видимость скрытых папок, пути: (тут у меня было freerdp) /home/user/.config/ (тут у меня было KRDC и remmina) /home/user/.local/share/ sudo apt-get purge krdc sudo apt-get purge freerdp2-x11 sudo apt autoremove Первая удалит KRDC с конфигами. Вторая удалит xfreerdp с конфигами. Третья удалит остатки мусора компонентов не использующихся. После этого установи через Discover KRDC из Flatpak. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 440659] New: RDP closing
https://bugs.kde.org/show_bug.cgi?id=440659 Bug ID: 440659 Summary: RDP closing Product: krdc Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: texgas...@ya.ru CC: aa...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Select RDP, enter url or ip. 2. Double click for connected 3. Wait... OBSERVED RESULT RDP Connectwindow connect closing. EXPECTED RESULT RDP Connected. Window shows Remote Desktop. SOFTWARE/OS VERSIONS Операционная система: KDE neon 5.22 Версия KDE Plasma: 5.22.4 Версия KDE Frameworks: 5.84.0 Версия Qt: 5.15.3 Версия ядра: 5.11.0-25-generic (64-бита) Графическая платформа: X11 Процессоры: 4 × Intel® Core™ i3 CPU 540 @ 3.07GHz Память: 5,8 ГиБ ОЗУ Графический процессор: GeForce GT 730/PCIe/SSE2 ADDITIONAL INFORMATION RDP broken disconnect every connect. VNC normal. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447175] New: Any icons at the right side of demo titlebar in the titlebar settings are shifted right too much.
https://bugs.kde.org/show_bug.cgi?id=447175 Bug ID: 447175 Summary: Any icons at the right side of demo titlebar in the titlebar settings are shifted right too much. Product: systemsettings Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: kolya007.kl...@gmail.com Target Milestone: --- Created attachment 144645 --> https://bugs.kde.org/attachment.cgi?id=144645&action=edit observed result SUMMARY Any icons at the right side of demo titlebar in the titlebar settings are shifted right too much. STEPS TO REPRODUCE 1. Open settings application 2. Open appearance menu 3. Open window decorations submenu 4. Open titlebar icons tab 5. Remove all icons to the icons grid 6. Try to drag any icon to the right side of titlebar 7. Observe the result OBSERVED RESULT My 3 titlebar icons (minimize icon, maximize icon, close icon) are shifted right too much. Real titlebar at any window works as expected. EXPECTED RESULT My 3 titlebar icons (minimize icon, maximize icon, close icon) should be placed at the end of titlebar, but visible and not overflowed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Kubuntu 21.10 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-23-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 13.5 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447175] Any icons at the right side of demo titlebar in the titlebar settings are shifted right too much.
https://bugs.kde.org/show_bug.cgi?id=447175 Nikolay changed: What|Removed |Added Version|unspecified |5.22.5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 462238] New: There is no Cyrillic alphabet in the file request window
https://bugs.kde.org/show_bug.cgi?id=462238 Bug ID: 462238 Summary: There is no Cyrillic alphabet in the file request window Classification: Applications Product: krita Version: 5.1.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: nemi...@gmail.com Target Milestone: --- Created attachment 154022 --> https://bugs.kde.org/attachment.cgi?id=154022&action=edit screenshot of the encoding problem 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 *** I open the file request window. Folders with Cyrillic characters are not displayed. This does not work in any window that reads local files. Menu: File - Open. Меnu: Setup - Resource library management - IMPORT. Menu: Setup - Resource management - Import of sources. EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/ Ubuntu Studio (jammy), Gnome 42.5 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 417911] New: references disappear
https://bugs.kde.org/show_bug.cgi?id=417911 Bug ID: 417911 Summary: references disappear Product: krita Version: 4.2.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tools/Reference Images Assignee: krita-bugs-n...@kde.org Reporter: nemi...@gmail.com Target Milestone: --- Created attachment 126190 --> https://bugs.kde.org/attachment.cgi?id=126190&action=edit Opened the file and switched to another composition SUMMARY Hello. I use the reference image tool tool and the Compositions at the same time. Compositions of 7 pieces (a convenient thing, I draw a storyboard). So, when you first open the file, all the refs are in place, but if you switch to another composition and use the zoom, the refs are erased and can no longer be used. STEPS TO REPRODUCE 1. Open file containing refs and compositions 2. Go from one song to another 3. Zoom in OBSERVED RESULT Refs will disappear EXPECTED RESULT Continue to use refs SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 395242] New: after trying to send a report about crash of plasmashell
https://bugs.kde.org/show_bug.cgi?id=395242 Bug ID: 395242 Summary: after trying to send a report about crash of plasmashell Product: drkonqi Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: backtraceparsing Assignee: unassigned-b...@kde.org Reporter: nikolayr2...@gmail.com Target Milestone: --- after trying to send a report about crash of plasmashell -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 372170] New: Kontact-Kmail (Kolab account) crash at massive message moving to another imap folder
https://bugs.kde.org/show_bug.cgi?id=372170 Bug ID: 372170 Summary: Kontact-Kmail (Kolab account) crash at massive message moving to another imap folder Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: nikolay.brookst...@nextnetworks.eu Target Milestone: --- Application: kontact (5.3.0 (QtWebEngine)) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.6-300.fc25.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: 1. Choose my Kolab account in Kmail tab in Kontact 2. Select several mail threads in "Inbox" 3. Move them to another imap folder at the same account and server 4. Crash -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f26e58a5940 (LWP 2448))] Thread 46 (Thread 0x7f25505d8700 (LWP 19271)): #0 0x7f26f53c5809 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f26f9913222 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f26f9922558 in base::PosixDynamicThreadPool::WaitForTask() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f26f9922a8d in base::(anonymous namespace)::WorkerThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f26f991bc5c in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f26f53bf6ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f26fd66af6f in clone () at /lib64/libc.so.6 Thread 45 (Thread 0x7f254e5d4700 (LWP 19119)): #0 0x7f26f53c5809 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f26f9913222 in base::ConditionVariable::TimedWait(base::TimeDelta const&) () at /lib64/libQt5WebEngineCore.so.5 #2 0x7f26f9922558 in base::PosixDynamicThreadPool::WaitForTask() () at /lib64/libQt5WebEngineCore.so.5 #3 0x7f26f9922a8d in base::(anonymous namespace)::WorkerThread::ThreadMain() () at /lib64/libQt5WebEngineCore.so.5 #4 0x7f26f991bc5c in base::(anonymous namespace)::ThreadFunc(void*) () at /lib64/libQt5WebEngineCore.so.5 #5 0x7f26f53bf6ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f26fd66af6f in clone () at /lib64/libc.so.6 Thread 44 (Thread 0x7f25515da700 (LWP 15012)): #0 0x7f26f53c5460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f25d94c8e23 in JSC::GCThread::waitForNextPhase() () at /lib64/libQt5WebKit.so.5 #2 0x7f25d94c8eb0 in JSC::GCThread::gcThreadMain() () at /lib64/libQt5WebKit.so.5 #3 0x7f25d97cf151 in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #4 0x7f26f53bf6ca in start_thread () at /lib64/libpthread.so.0 #5 0x7f26fd66af6f in clone () at /lib64/libc.so.6 Thread 43 (Thread 0x7f2598102700 (LWP 15011)): #0 0x7f26f53c5460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f25d94c8e23 in JSC::GCThread::waitForNextPhase() () at /lib64/libQt5WebKit.so.5 #2 0x7f25d94c8eb0 in JSC::GCThread::gcThreadMain() () at /lib64/libQt5WebKit.so.5 #3 0x7f25d97cf151 in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #4 0x7f26f53bf6ca in start_thread () at /lib64/libpthread.so.0 #5 0x7f26fd66af6f in clone () at /lib64/libc.so.6 Thread 42 (Thread 0x7f26ccbef700 (LWP 15010)): #0 0x7f26f53c5460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f25d94c8e23 in JSC::GCThread::waitForNextPhase() () at /lib64/libQt5WebKit.so.5 #2 0x7f25d94c8eb0 in JSC::GCThread::gcThreadMain() () at /lib64/libQt5WebKit.so.5 #3 0x7f25d97cf151 in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #4 0x7f26f53bf6ca in start_thread () at /lib64/libpthread.so.0 #5 0x7f26fd66af6f in clone () at /lib64/libc.so.6 Thread 41 (Thread 0x7f2597901700 (LWP 15009)): #0 0x7f26f53c5460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f25d94c7fdc in JSC::BlockAllocator::blockFreeingThreadMain() () at /lib64/libQt5WebKit.so.5 #2 0x7f25d97cf151 in WTF::wtfThreadEntryPoint(void*) () at /lib64/libQt5WebKit.so.5 #3 0x7f26f53bf6ca in start_thread () at /lib64/libpthread.so.0 #4 0x7f26fd66af6f in clone () at /lib64/libc.so.6 Thread 40 (Thread 0x7f2598dd6700 (LWP 15008)): #0 0x7f26f53c5460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f25d97a78b6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /lib64/libQt5WebKit.so.5 #2 0x7f25d97a78d9 in () at /lib64/libQt5WebKit.so.5 #3 0x7f26f53bf6ca in start_thread () a
[kontact] [Bug 372170] Kontact-Kmail (Kolab account) crash at massive message moving to another imap folder
https://bugs.kde.org/show_bug.cgi?id=372170 Nikolay Brookstein changed: What|Removed |Added Version|unspecified |5.3.0 CC||nikolay.brookstein@nextnetw ||orks.eu -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 372210] New: Ark chrashed at rar extraction from dolphin
https://bugs.kde.org/show_bug.cgi?id=372210 Bug ID: 372210 Summary: Ark chrashed at rar extraction from dolphin Product: ark Version: 16.08.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: nikolay.brookst...@nextnetworks.eu CC: rthoms...@gmail.com Target Milestone: --- Application: ark (16.08.2) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.6-300.fc25.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: 1. open with dolphin a directory with the rar archive 2. select rar archive 3. right mous button 4. Extract -> Extract archive here, autodetect subfolder 5. crash -- Backtrace: Application: Ark (ark), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f208b3e6480 (LWP 9283))] Thread 3 (Thread 0x7f2077fff700 (LWP 9285)): #0 0x7f209614c00d in poll () at /lib64/libc.so.6 #1 0x7f2090214156 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f209021426c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f2096f51d8b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f2096f030ba in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f2096d60643 in QThread::exec() () at /lib64/libQt5Core.so.5 #6 0x7f20981287a9 in QDBusConnectionManager::run() () at /lib64/libQt5DBus.so.5 #7 0x7f2096d64a1a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f2094b296ca in start_thread () at /lib64/libpthread.so.0 #9 0x7f2096157f6f in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f20800ab700 (LWP 9284)): #0 0x7f209614c00d in poll () at /lib64/libc.so.6 #1 0x7f208f908d10 in _xcb_conn_wait () at /lib64/libxcb.so.1 #2 0x7f208f90aaa9 in xcb_wait_for_event () at /lib64/libxcb.so.1 #3 0x7f2084751a19 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #4 0x7f2096d64a1a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f2094b296ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f2096157f6f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f208b3e6480 (LWP 9283)): [KCrash Handler] #6 0x7f209608592f in raise () at /lib64/libc.so.6 #7 0x7f209608752a in abort () at /lib64/libc.so.6 #8 0x7f20969c74fd in __gnu_cxx::__verbose_terminate_handler() () at /lib64/libstdc++.so.6 #9 0x7f20969c52a6 in () at /lib64/libstdc++.so.6 #10 0x7f20969c52f1 in () at /lib64/libstdc++.so.6 #11 0x7f20969c5509 in () at /lib64/libstdc++.so.6 #12 0x7f2096d4af42 in () at /lib64/libQt5Core.so.5 #13 0x7f2096dde47d in QString::reallocData(unsigned int, bool) () at /lib64/libQt5Core.so.5 #14 0x7f2096ddea84 in QString::append(QString const&) () at /lib64/libQt5Core.so.5 #15 0x7f207c361862 in CliPlugin::handleLine(QString const&) () at /usr/lib64/qt5/plugins/kerfuffle/kerfuffle_cliunarchiver.so #16 0x7f209bac2c64 in Kerfuffle::CliInterface::readStdout(bool) () at /lib64/libkerfuffle.so.16 #17 0x7f2096f2aff1 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #18 0x7f2096e5d008 in QProcessPrivate::tryReadFromChannel(QProcessPrivate::Channel*) () at /lib64/libQt5Core.so.5 #19 0x7f2096e5d370 in QProcess::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () at /lib64/libQt5Core.so.5 #20 0x7f2096f2aff1 in QMetaObject::activate(QObject*, int, int, void**) () at /lib64/libQt5Core.so.5 #21 0x7f2096f9ad7e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /lib64/libQt5Core.so.5 #22 0x7f2096f37102 in QSocketNotifier::event(QEvent*) () at /lib64/libQt5Core.so.5 #23 0x7f209774c96c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #24 0x7f2097754111 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #25 0x7f2096f0412a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #26 0x7f2096f5269f in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #27 0x7f2090213e42 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #28 0x7f20902141c0 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #29 0x7f209021426c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #30 0x7f2096f51d6f in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #31 0x7f2096f030ba in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #32 0x7f209ba9d8a2 in Kerfuffle::Archive::listIfNotListed() () at /lib64/libkerfuffle.so.16 #33 0x7f209ba9d8d
[ark] [Bug 372210] Ark chrashed at rar extraction from dolphin
https://bugs.kde.org/show_bug.cgi?id=372210 --- Comment #2 from Nikolay Brookstein --- Yes it chrashes every time. (Have just tried again) I am using [unar.x86_64 1.10.1-1.fc25 @fedora] as the rar extractor. I can not attach archive here direct (227,7 MB > 4 MB), but I have uploaded it at my cloud instance, and here is the link: https://datacloud.nextnetworks.eu/index.php/s/6xszdJX48JKT8oX (this link will be valid till 15-11-2016) -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 372210] Ark chrashed at rar extraction from dolphin
https://bugs.kde.org/show_bug.cgi?id=372210 Nikolay Brookstein changed: What|Removed |Added CC||nikolay.brookstein@nextnetw ||orks.eu -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives
https://bugs.kde.org/show_bug.cgi?id=372210 --- Comment #4 from Nikolay Brookstein --- Thanks for your fast reaction! If I can help you to fix this bug, just say. I am not a super hacker but have some C++/Qt knowledge. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives
https://bugs.kde.org/show_bug.cgi?id=372210 --- Comment #7 from Nikolay Brookstein --- What is the difference between unrar and unar approaches? It is really strange, to get over 3 GB memory allocation fo a ~240MB file. It looks like coner case or a totally inefficient implementation from unar side. Probably Ark just need a better backend error detection, and a bug is in unar. Or I am wrong here? (That are just my thoughts, I am not an expert in rar/unar/unrar) P.S. I will look in a source file tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives
https://bugs.kde.org/show_bug.cgi?id=372210 --- Comment #10 from Nikolay Brookstein --- I have just created a bug report at the unarchiver bug tracker: https://bitbucket.org/WAHa_06x36/theunarchiver/issues/919/unarchiver-crash-while- trying-to-open-or Elvis, "Archive too big" is probably some how confusing. Possibly "Archive can not be extracted due to insufficient free memory"? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives
https://bugs.kde.org/show_bug.cgi?id=372210 --- Comment #11 from Nikolay Brookstein --- oops, the same URl without line break: https://bitbucket.org/WAHa_06x36/theunarchiver/issues/919/unarchiver-crash-while-trying-to-open-or -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives
https://bugs.kde.org/show_bug.cgi?id=372210 Nikolay Brookstein changed: What|Removed |Added URL||https://bitbucket.org/WAHa_ ||06x36/theunarchiver/issues/ ||919/unarchiver-crash-while- ||trying-to-open-or -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives
https://bugs.kde.org/show_bug.cgi?id=372210
--- Comment #13 from Nikolay Brookstein ---
No problem, without bug reports bugs will never be fixed ^_^
As far as I have understood, KDE/Plasma/KF are all Qt based,
so why you are using 'i18n("Blabla")' instead of 'tr("Blabla")'
Btw, you are the main maintainer of Ark right now?
If yes, some offtopic question from my side, is it possible to make a progress
indication in Ark, or the current architecture is not sutable for the such kind
of functionality?
--
You are receiving this mail because:
You are watching all bug changes.
[ark] [Bug 372210] [unarchiver] Crash while trying to open or extract big archives
https://bugs.kde.org/show_bug.cgi?id=372210 --- Comment #15 from Nikolay Brookstein --- (In reply to Christoph Feck from comment #14) > Our translation infrastructure is based on GNU 'gettext'; we do not use the > Qt translation system. Thank you for the clarification. Is gettext technically better than the Qt translation system? What is the reason of using it? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 462695] Power management sometimes stops working?
https://bugs.kde.org/show_bug.cgi?id=462695 Nikolay Stoynov changed: What|Removed |Added CC||arvig...@gmail.com Summary|Power management sometimes |Power management sometimes |stops working |stops working? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 462695] Automatic DisplayPort screen dimming/sleep and system sleep stops working on Wayland
https://bugs.kde.org/show_bug.cgi?id=462695 --- Comment #45 from Nikolay Stoynov --- I have the same issue with Nobara (Fedora based). I reported it [here](https://gitlab.com/GloriousEggroll/nobara-images/-/issues/96) TLDR; ```sh kf.idletime: Could not find any system poller plugin QObject::connect(AbstractSystemPoller, KIdleTime): invalid nullptr parameter QObject::connect(AbstractSystemPoller, KIdleTime): invalid nullptr parameter org.kde.powerdevil: Handle button events action could not check for screen configuration ``` Appears not to be a bug from KDE itself. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460469] New: System monitor has fallen back to software rendering on Lenovo Legion 5 17ACH6
https://bugs.kde.org/show_bug.cgi?id=460469 Bug ID: 460469 Summary: System monitor has fallen back to software rendering on Lenovo Legion 5 17ACH6 Classification: Plasma Product: plasma-systemmonitor Version: unspecified Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: jing...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Nvidia driver 515.65.01 OS: Ubuntu 22.04.1 LTS x86_64 Host: 82K0 Legion 5 17ACH6 Kernel: 5.15.0-50-generic WM: KWin Theme: Adwaita [GTK3] Icons: Adwaita [GTK3] CPU: AMD Ryzen 5 5600H with Radeon Graphics (12) @ 4.280GHz GPU: NVIDIA GeForce RTX 3050 Mobile -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 460469] System monitor has fallen back to software rendering on Lenovo Legion 5 17ACH6
https://bugs.kde.org/show_bug.cgi?id=460469 --- Comment #2 from Nikolay Fedorov --- Hi. Default installation OS: Kubuntu 22.04.1 LTS x86_64 X11 I've installed the NVida driver from the nvidia site, instead of Ubuntu provided. Now the system monitor works fine. but I've got new issues :) Best Regards. On Sun, Oct 16, 2022, 4:18 AM Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=460469 > > Nate Graham changed: > >What|Removed |Added > > > CC||n...@kde.org > Version|unspecified |5.18.7 > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Nate Graham --- > Can you provide some more information? Does anything else on the system use > software rendering? Are you using Wayland or X11? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480421] Icons-only task manager often messes up rendering resulting in either 1-2 pixels wide icons or icons about 4 times as small as they should be
https://bugs.kde.org/show_bug.cgi?id=480421 Nikolay Stoynov changed: What|Removed |Added CC||arvig...@gmail.com --- Comment #9 from Nikolay Stoynov --- Created attachment 167892 --> https://bugs.kde.org/attachment.cgi?id=167892&action=edit Mangled panel icons Not sure if related, but sometimes panel items get messed up like this. This is not even my screenshot - someone else reported this on reddit as well. As a temporary workaround, I just go into Edit Mode and exit. My guess is that it may have something to do with applets that dynamically appear/disappear (example: [Application Title Bar](https://store.kde.org/p/2135509)), Global Menu), or calculate size dynamically (Spacer, Icons-Only Task). My panel configuration is: Application Title Bar, Global Menu, Spacer, Icon-Only Tasks, Spacer, Notification area -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436778] New: When saving to JPG, white squares appear inside the image
https://bugs.kde.org/show_bug.cgi?id=436778 Bug ID: 436778 Summary: When saving to JPG, white squares appear inside the image Product: krita Version: 4.4.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: bavkunov...@gmail.com Target Milestone: --- Created attachment 138243 --> https://bugs.kde.org/attachment.cgi?id=138243&action=edit file "as displayed" after export SUMMARY STEPS TO REPRODUCE 1. File->Export 2. With any further settings for exporting to JPG, the file is obtained with "white squares" (must be a single fill) OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436778] When saving to JPG, white squares appear inside the image
https://bugs.kde.org/show_bug.cgi?id=436778 --- Comment #2 from Nikolay Bavkunov --- Created attachment 138244 --> https://bugs.kde.org/attachment.cgi?id=138244&action=edit white color is selected in the settings -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436778] When saving to JPG, white squares appear inside the image
https://bugs.kde.org/show_bug.cgi?id=436778 --- Comment #3 from Nikolay Bavkunov --- The export settings are set to white. File (* kra) does not contain transparency -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436778] When saving to JPG, white squares appear inside the image
https://bugs.kde.org/show_bug.cgi?id=436778 Nikolay Bavkunov changed: What|Removed |Added Resolution|NOT A BUG |--- Assignee|krita-bugs-n...@kde.org |bavkunov...@gmail.com Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #4 from Nikolay Bavkunov --- Created attachment 138245 --> https://bugs.kde.org/attachment.cgi?id=138245&action=edit File *KRA -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 436778] When saving to JPG, white squares appear inside the image
https://bugs.kde.org/show_bug.cgi?id=436778 --- Comment #5 from Nikolay Bavkunov --- The export settings are set to white. File (* kra) does not contain transparency сб, 8 мая 2021 г. в 18:15, Halla Rempt : > https://bugs.kde.org/show_bug.cgi?id=436778 > > Halla Rempt changed: > >What|Removed |Added > > > Resolution|--- |NOT A BUG > Status|REPORTED|RESOLVED > CC||ha...@valdyas.org > > --- Comment #1 from Halla Rempt --- > JPEG doesn't support transparancy, so it needs to save with a background > color. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412596] ViewSplitter is not destroyed
https://bugs.kde.org/show_bug.cgi?id=412596 --- Comment #13 from Nikolay Zlatev --- (In reply to Kurt Hindenburg from comment #12) > Git commit c33eba8c60b99d00cd73c400d23b6f338ef32a85 by Kurt Hindenburg, on > behalf of Carlos Alves. > Committed on 02/11/2020 at 18:14. > Pushed by hindenburg into branch 'master'. > > Fix konsole crashes when rearranging split views > > I'll try to explain here what I saw in this bug. > Following the BUG instructions, drag the terminal[2] and drop > (here the "drop event" starts) > -> the dragged terminal "ViewSplitter" become scheduled for deletion, > but it will only happens when it is in event loop. > -> And of course it is not in event loop yet, it is still the > "drop event" and it call the "addTerminalDisplay" to add the dragged > terminal to a "ViewSplitter". > -> This makes count() counts this scheduled for deletion "ViewSplitter" > and goes to the wrong "if". > -> It adds the "ViewSplitter" with the terminals into a > "marked for deletion" one, finishes the "drop event" and enters > event loop (a crash without a memleak! everything in the tab > is properly deleted). > Related: bug 411741 > FIXED-IN: 20.12 > > M +4-0src/widgets/ViewSplitter.cpp > > https://invent.kde.org/utilities/konsole/commit/ > c33eba8c60b99d00cd73c400d23b6f338ef32a85 This commit doesn't fix the issue described here Parent tree Breeze::WidgetExplorer::eventFilter widget: 0x557e59a12c10 (Konsole::TerminalDisplay) parent: 0x557e59d8db80 (Konsole::ViewSplitter) parent: 0x557e59cc6800 (Konsole::ViewSplitter) parent: 0x557e599aeb10 (Konsole::ViewSplitter) parent: 0x557e59925c90 (Konsole::ViewSplitter) parent: 0x557e59926070 (Konsole::ViewSplitter) parent: 0x557e595eb2f0 (Konsole::ViewSplitter) parent: 0x557e59b450a0 (Konsole::ViewSplitter) parent: 0x557e59aa0c80 (Konsole::ViewSplitter) parent: 0x557e59a00230 (Konsole::ViewSplitter) parent: 0x557e5984ada0 (Konsole::ViewSplitter) parent: 0x557e59970f30 (Konsole::ViewSplitter) parent: 0x557e599c28c0 (Konsole::ViewSplitter) parent: 0x557e5962a530 (Konsole::ViewSplitter) parent: 0x557e5946ba10 (QStackedWidget) parent: 0x557e59424510 (Konsole::TabbedViewContainer) parent: 0x557e594143e0 (Konsole::MainWindow) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 343034] KMail insists on offline mode, even when network connection is available
https://bugs.kde.org/show_bug.cgi?id=343034 --- Comment #19 from Nikolay Shaplov --- Sorry, I do not have spare laptop to test this now. But if you have, you can try to remove network-manager and install wicid, for Wi-Fi usage. If you will be able to make kmail work after wicid goes offline and then online, then problem, the way I knew it, is no longer there... -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412596] ViewSplitter is not destroyed
https://bugs.kde.org/show_bug.cgi?id=412596 --- Comment #2 from Nikolay Zlatev --- (In reply to Kurt Hindenburg from comment #1) > What are you using that shows those lines? Breeze::WidgetExplorer::eventFilter https://github.com/KDE/breeze/blob/master/kstyle/debug/breezewidgetexplorer.cpp https://github.com/KDE/breeze/blob/master/kstyle/breeze.kcfg#L181 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412596] ViewSplitter is not destroyed
https://bugs.kde.org/show_bug.cgi?id=412596 --- Comment #3 from Nikolay Zlatev --- Also I think this is the reason for https://bugs.kde.org/show_bug.cgi?id=411741 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412596] ViewSplitter is not destroyed
https://bugs.kde.org/show_bug.cgi?id=412596
--- Comment #5 from Nikolay Zlatev ---
"how complex is to simplify" (best sentence ever)
Most complex thing for any developer :) :) :)
pseudo code idea
void afterTerminalDetached () {
if (this->childrenCount == 1 && this->child(0).class == "ViewSplitter") {
auto child = this->child(0);
this->parent().swap(this, child);
}
}
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 412596] ViewSplitter is not destroyed
https://bugs.kde.org/show_bug.cgi?id=412596 --- Comment #7 from Nikolay Zlatev --- Created attachment 123271 --> https://bugs.kde.org/attachment.cgi?id=123271&action=edit ugly patch Working ugly patch/hack Also this fix/resolve #411741 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412596] ViewSplitter is not destroyed
https://bugs.kde.org/show_bug.cgi?id=412596 --- Comment #9 from Nikolay Zlatev --- Created attachment 123276 --> https://bugs.kde.org/attachment.cgi?id=123276&action=edit Patch v2 This is one of the ugliest code i have wrote. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411387] Split View crash with keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=411387 --- Comment #7 from Nikolay Zlatev --- (In reply to Kurt Hindenburg from comment #6) > the null check looks reasonable even though I can't it to crash here with > any theme. The "+1" is worrisome as it appears to be theme specific. const auto handleWidth = parentSplitter->handleWidth() <= 1 ? 4 :... "? 4" is also worrisome :) In fact this "4" constant prevent konsole to crash under "Breeze" theme. When handleWidth = parentSplitter->handleWidth(); is used, konsole crash under all themes. I have tested with "const auto handleWidth = parentSplitter->handleWidth() + 3;" and everything seems to work fine. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411387] Split View crash with keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=411387 --- Comment #9 from Nikolay Zlatev --- > // Find the theme's splitter width + extra space to find valid terminal >const auto handleWidth = > parentSplitter->style()->pixelMetric(QStyle::PM_SplitterWidth) + 2; On Breeze handleWidth is now "3" (1 + 2) and konsole crash. That why I have used "+3" (min handleWidth=4, 1 + 3) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411387] Split View crash with keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=411387 Nikolay Zlatev changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #12 from Nikolay Zlatev --- ... pixelMetric(QStyle::PM_SplitterWidth) + 2 "+2" is not enough for Breeze breeze.h Breeze::Metrics::Splitter_SplitterWidth = 1; https://github.com/KDE/breeze/blob/master/kstyle/breezestyle.cpp#L615 QT docs If you set handleWidth to 1 or 0, the actual grab area will grow to overlap a few pixels of its respective widgets. https://doc.qt.io/qt-5/qsplitter.html#handleWidth-prop I don't known if there is a method to get "grab area" size. P.S. Breeze::WidgetExplorer::eventFilter returns 5 for width -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411387] Split View crash with keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=411387
--- Comment #13 from Nikolay Zlatev ---
// Find the theme's splitter width + extra space to find valid terminal
// https://doc.qt.io/qt-5/qsplitter.html#handleWidth-prop
// By default, this property contains a value
// that depends on the user's platform and style preferences.
//
// If you set handleWidth to 1 or 0,
// the actual grab area will grow to overlap a few
// pixels of its respective widgets.
const auto handleWidth = parentSplitter->handleWidth() + 3;
P.S.
pixelMetric(QStyle::PM_SplitterWidth)
always returns theme value not actual rendered size
I have tested on Breeze
app->setStyleSheet(QStringLiteral("QSplitter::handle {width: 8px; height: 8px;
border: 1px solid red}"));
in main.cpp
pixelMetric(QStyle::PM_SplitterWidth) returns 1
handleWidth() returns 10 (width+border*2)
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 411387] Split View crash with keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=411387 --- Comment #14 from Nikolay Zlatev --- Breeze handleWidth = ...pixelMetric(QStyle::PM_SplitterWidth) + 2; ++ || | 0 | || ++ || | 1 | || ++ || | 2 | | IN FOCUS | ++ CTRL + UP Expected: 1 to be in focus Result: 0 is in focus (qobject_cast(targetSplitter->widget(0));) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411387] Split View crash with keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=411387 --- Comment #16 from Nikolay Zlatev --- (In reply to Kurt Hindenburg from comment #15) > Ok thanks for testing - I misunderstood what is going on - to be clear > "const auto handleWidth = parentSplitter->handleWidth() + 3;" works for all > your testing? yes works fine. > > Also, are you not getting crashes when you do splits? 412020 Only with Oxygen (I will post in 412020) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412020] Certain style/themes cause Konsole split to create new window
https://bugs.kde.org/show_bug.cgi?id=412020 Nikolay Zlatev changed: What|Removed |Added CC||n...@astrapaging.com --- Comment #4 from Nikolay Zlatev --- I have tested with Breeze, kvantum, Oxygen, Windows, Fusion This issue appear only on Oxygen, and only with compositor enabled. If compositor is disabled everything works fine. Maybe this is Oxygen/Kwin problem. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 412596] New: ViewSplitter is not destroyed
https://bugs.kde.org/show_bug.cgi?id=412596 Bug ID: 412596 Summary: ViewSplitter is not destroyed Product: konsole Version: master Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: split-view Assignee: konsole-de...@kde.org Reporter: n...@astrapaging.com Target Milestone: --- ViewSplitter is not destroyed after all TerminalDisplay are closed. STEPS TO REPRODUCE 1. Split +-+ | | | Terminal 0 | | | +--+--+ | | | |Terminal 1|Terminal 2| | | | +--+--+ 2. Close Terminal 0 3. Close Terminal 1 OBSERVED RESULT Parent tree after few iterations widget: 0x55a584096c10 (Konsole::TerminalDisplay) parent: 0x55a583fb4490 (Konsole::ViewSplitter) parent: 0x55a58411d350 (Konsole::ViewSplitter) parent: 0x55a583fb3b20 (Konsole::ViewSplitter) parent: 0x55a5841548d0 (Konsole::ViewSplitter) parent: 0x55a583f93920 (Konsole::ViewSplitter) parent: 0x55a584171990 (Konsole::ViewSplitter) parent: 0x55a58360 (Konsole::ViewSplitter) parent: 0x55a58410cf10 (Konsole::ViewSplitter) parent: 0x55a58405a350 (Konsole::ViewSplitter) parent: 0x55a583d59ab0 (QStackedWidget) parent: 0x55a583d14b10 (Konsole::TabbedViewContainer) parent: 0x55a583d05ce0 (Konsole::MainWindow) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 410640] New: Updating work directory after agreeing to save previous project confuses
https://bugs.kde.org/show_bug.cgi?id=410640 Bug ID: 410640 Summary: Updating work directory after agreeing to save previous project confuses Product: kdenlive Version: 18.08.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: nikolay.kapy...@gmail.com Target Milestone: --- SUMMARY While consecutively opening and modifying multiple projects in different folders, I'd like, when I click "Open project", for the Open dialog to show the last opened file's folder. When the action of opening is followed by a "the project has been changed, do you want to save" dialog, the lookup folder for the next opened file will be that of the previously saved project file, not the last opened project file. STEPS TO REPRODUCE 1. Open kdenlive project A1 from folder AAA 2. Make some changes 3. Open kdenlive project B1 from folder BBB 4. Click "Yes" to "the project has been changed, do you want to save" dialog 5. Click open to fetch the next project file, B2 supposedly in the folder BBB OBSERVED RESULT The work directory is now AAA EXPECTED RESULT The open directory should be BBB, matching the one where the last opened file is SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I am running 18.08.03 from Appimage -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411387] New: Split View crash with keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=411387
Bug ID: 411387
Summary: Split View crash with keyboard navigation
Product: konsole
Version: 19.08.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: split-view
Assignee: konsole-de...@kde.org
Reporter: n...@astrapaging.com
Target Milestone: ---
Created attachment 122401
--> https://bugs.kde.org/attachment.cgi?id=122401&action=edit
Layout
Konsole crash when keyboard navigation is used to switch between
TerminalDisplay
auto splitterTerminal =
qobject_cast(targetSplitter->widget(0));
return nullptr and then splitterTerminal->setFocus(Qt::OtherFocusReason); is
used
https://cgit.kde.org/konsole.git/tree/src/ViewSplitter.cpp#n171
STEPS TO REPRODUCE
1. Split terminal in
---
|||
|||
|||
---
| |
| |
| |
---
2. navigate from bottom to top (ctrl + shift + arrow_up)
OBSERVED RESULT
Crash
EXPECTED RESULT
Not Crash
Arch
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.13.0
Work around
diff --git a/src/ViewSplitter.cpp b/src/ViewSplitter.cpp
index 7e31172c..2ab15e5c 100644
--- a/src/ViewSplitter.cpp
+++ b/src/ViewSplitter.cpp
@@ -168,7 +168,7 @@ void ViewSplitter::handleFocusDirection(Qt::Orientation
orientation, int directi
} else if (qobject_cast(child) != nullptr) {
auto targetSplitter = qobject_cast(child->parent());
auto splitterTerminal =
qobject_cast(targetSplitter->widget(0));
-splitterTerminal->setFocus(Qt::OtherFocusReason);
+if (splitterTerminal != nullptr)
splitterTerminal->setFocus(Qt::OtherFocusReason);
} else if (qobject_cast(child) != nullptr) {
TerminalDisplay *terminalParent = nullptr;
while(terminalParent == nullptr) {
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 411387] Split View crash with keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=411387 --- Comment #2 from Nikolay Zlatev --- Created attachment 122418 --> https://bugs.kde.org/attachment.cgi?id=122418&action=edit Debug session -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411387] Split View crash with keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=411387 --- Comment #3 from Nikolay Zlatev --- This only happens on some split layouts and only with keyboard navigation. targetSplitter->widget(0) returns Konsole::ViewSplitter and then casting to TerminalDisplay fail. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 411387] Split View crash with keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=411387
--- Comment #4 from Nikolay Zlatev ---
It appears this is theme related issue.
When I use Breeze everything is OK.
For Breeze
const auto handleWidth = parentSplitter->handleWidth() <= 1 ? 4 :
parentSplitter->handleWidth();
returns 4 as a constant.
For Kvantum -> Adpata
parentSplitter->handleWidth() is used (4 pixels again, but this is the width of
the splitter border)
then
topSplitter->childAt(newPoint) returns ViewSplitter instead of TerminalDisplay
This fixes issue for me
const auto handleWidth = parentSplitter->handleWidth() <= 1 ? 4 :
parentSplitter->handleWidth() + 1;
--
diff --git a/src/ViewSplitter.cpp b/src/ViewSplitter.cpp
index 7e31172c..24b49334 100644
--- a/src/ViewSplitter.cpp
+++ b/src/ViewSplitter.cpp
@@ -147,7 +147,7 @@ void ViewSplitter::handleFocusDirection(Qt::Orientation
orientation, int directi
auto parentSplitter =
qobject_cast(terminalDisplay->parentWidget());
auto topSplitter = parentSplitter->getToplevelSplitter();
-const auto handleWidth = parentSplitter->handleWidth() <= 1 ? 4 :
parentSplitter->handleWidth();
+const auto handleWidth = parentSplitter->handleWidth() <= 1 ? 4 :
parentSplitter->handleWidth() + 1;
const auto start = QPoint(terminalDisplay->x(), terminalDisplay->y());
const auto startMapped = parentSplitter->mapTo(topSplitter, start);
@@ -168,7 +168,8 @@ void ViewSplitter::handleFocusDirection(Qt::Orientation
orientation, int directi
} else if (qobject_cast(child) != nullptr) {
auto targetSplitter = qobject_cast(child->parent());
auto splitterTerminal =
qobject_cast(targetSplitter->widget(0));
-splitterTerminal->setFocus(Qt::OtherFocusReason);
+if (splitterTerminal != nullptr)
+splitterTerminal->setFocus(Qt::OtherFocusReason);
} else if (qobject_cast(child) != nullptr) {
TerminalDisplay *terminalParent = nullptr;
while(terminalParent == nullptr) {
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 411387] Split View crash with keyboard navigation
https://bugs.kde.org/show_bug.cgi?id=411387
--- Comment #5 from Nikolay Zlatev ---
Final patch
diff --git a/src/ViewSplitter.cpp b/src/ViewSplitter.cpp
index 7e31172c..38c576a9 100644
--- a/src/ViewSplitter.cpp
+++ b/src/ViewSplitter.cpp
@@ -147,7 +147,7 @@ void ViewSplitter::handleFocusDirection(Qt::Orientation
orientation, int directi
auto parentSplitter =
qobject_cast(terminalDisplay->parentWidget());
auto topSplitter = parentSplitter->getToplevelSplitter();
-const auto handleWidth = parentSplitter->handleWidth() <= 1 ? 4 :
parentSplitter->handleWidth();
+const auto handleWidth = parentSplitter->handleWidth() <= 1 ? 4 :
parentSplitter->handleWidth() + 1;
const auto start = QPoint(terminalDisplay->x(), terminalDisplay->y());
const auto startMapped = parentSplitter->mapTo(topSplitter, start);
@@ -163,20 +163,21 @@ void ViewSplitter::handleFocusDirection(Qt::Orientation
orientation, int directi
const auto newPoint = QPoint(newX, newY);
auto child = topSplitter->childAt(newPoint);
+TerminalDisplay *focusTerminal = nullptr;
if (auto* terminal = qobject_cast(child)) {
-terminal->setFocus(Qt::OtherFocusReason);
+focusTerminal = terminal;
} else if (qobject_cast(child) != nullptr) {
auto targetSplitter = qobject_cast(child->parent());
-auto splitterTerminal =
qobject_cast(targetSplitter->widget(0));
-splitterTerminal->setFocus(Qt::OtherFocusReason);
+focusTerminal =
qobject_cast(targetSplitter->widget(0));
} else if (qobject_cast(child) != nullptr) {
-TerminalDisplay *terminalParent = nullptr;
-while(terminalParent == nullptr) {
-terminalParent =
qobject_cast(child->parentWidget());
+while(child != nullptr && focusTerminal == nullptr) {
+focusTerminal =
qobject_cast(child->parentWidget());
child = child->parentWidget();
}
-terminalParent->setFocus(Qt::OtherFocusReason);
}
+
+if (focusTerminal != nullptr)
+focusTerminal->setFocus(Qt::OtherFocusReason);
}
void ViewSplitter::focusUp()
--
You are receiving this mail because:
You are watching all bug changes.
[konsole] [Bug 418498] New: Maximize current Terminal (Keyboard vs Mouse)
https://bugs.kde.org/show_bug.cgi?id=418498 Bug ID: 418498 Summary: Maximize current Terminal (Keyboard vs Mouse) Product: konsole Version: 19.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: split-view Assignee: konsole-de...@kde.org Reporter: n...@astrapaging.com Target Milestone: --- SUMMARY There is a difference between "Maximize split-view" with keyboard (ctrl+shift+E) vs Mouse (click on the view header maximize icon) STEPS TO REPRODUCE 1. Split 2. Maximize with keyboard 3. Minimize with mouse OBSERVED RESULT Internal state of the view is lost and views can't be rearranged with mouse drag. Sometimes keyboard shortcut stop working. EXPECTED RESULT SOFTWARE/OS VERSIONS Arch Linux -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 421471] New: Double percent sign in progress
https://bugs.kde.org/show_bug.cgi?id=421471 Bug ID: 421471 Summary: Double percent sign in progress Product: kget Version: 20.04 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: torrent Assignee: k...@kde.org Reporter: chechulin...@gmail.com CC: wba...@tmo.at Target Milestone: --- Created attachment 128432 --> https://bugs.kde.org/attachment.cgi?id=128432&action=edit Screenshot of double percent sign SUMMARY STEPS TO REPRODUCE 1. Add torrent to KGET 2. Look at progress column OBSERVED RESULT Downloading progress is "75%%" EXPECTED RESULT Downloading progress is "75%" -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416403] During account wizard using @protonmail.com, get "Kmail could not convert value of setting 'Authentication' to required type"
https://bugs.kde.org/show_bug.cgi?id=416403 Nikolay Brookstein changed: What|Removed |Added CC||nikolay.brookstein@nextnetw ||orks.eu --- Comment #20 from Nikolay Brookstein --- (In reply to Parker from comment #19) > The current workaround is add the account manually. It's finally worked for > me. > > Settings -> Configure the Kmail > In accounts, add an identity, configure your IMAP/POP3/other server in the > receiving tab (press "Add" button and choose "Another account") and then > configure SMTP on the sending tab. Even this workaround did not helps. Have same problem on - OpenSUSE Tumbleweed: kmail 5.13.3 (19.12.2) KDE Plasma Version: 5.18.3 KDE Frameworks Version 5.68.0 - Fedora 31 kmail 5.11.3 KDE Plasma Version 5.17.5 KDE Frameworks Version: 5.67.0 IMAP-Resource goes in Ready state, but unable to fetch any server info or a server subscription, as well as receive anything from an IMAP server. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 416403] During account wizard using @protonmail.com, get "Kmail could not convert value of setting 'Authentication' to required type"
https://bugs.kde.org/show_bug.cgi?id=416403 --- Comment #21 from Nikolay Brookstein --- (In reply to Nikolay Brookstein from comment #20) > (In reply to Parker from comment #19) > > The current workaround is add the account manually. It's finally worked for > > me. > > > > Settings -> Configure the Kmail > > In accounts, add an identity, configure your IMAP/POP3/other server in the > > receiving tab (press "Add" button and choose "Another account") and then > > configure SMTP on the sending tab. > > Even this workaround did not helps. > Have same problem on > > - OpenSUSE Tumbleweed: > kmail 5.13.3 (19.12.2) > KDE Plasma Version: 5.18.3 > KDE Frameworks Version 5.68.0 > > - Fedora 31 > kmail 5.11.3 > KDE Plasma Version 5.17.5 > KDE Frameworks Version: 5.67.0 > > IMAP-Resource goes in Ready state, but unable to fetch any server info or a > server subscription, as well as receive anything from an IMAP server. Fedora 31: Qt Version: 5.17.5 OpenSUSE Tumbleweed: Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 387758] New: krunner segmentation fault
https://bugs.kde.org/show_bug.cgi?id=387758 Bug ID: 387758 Summary: krunner segmentation fault Product: krunner Version: 5.11.3 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: niktische...@gmail.com Target Milestone: --- Application: krunner (5.11.3) Qt Version: 5.9.3 Frameworks Version: 5.40.0 Operating System: Linux 4.9.67 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: - What I was doing when the application crashed: Just hit standard shortcut for KRunner - Alt+F2 and type something - Result: KRunner crached The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f335e3ae400 (LWP 2800))] Thread 4 (Thread 0x7f333f5ef700 (LWP 2872)): #0 0x7f3358cfc41b in poll () at /lib64/libc.so.6 #1 0x7f3350bb75f1 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3350bb76fc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3359b92dbb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f3359b3b10a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f335995e63a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f335cac0625 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f335996322e in () at /usr/lib64/libQt5Core.so.5 #8 0x7f3354c3c565 in start_thread () at /lib64/libpthread.so.0 #9 0x7f3358d080af in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f334605f700 (LWP 2859)): #0 0x7f3350bfafa4 in g_mutex_unlock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f3350bb6e39 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #2 0x7f3350bb756f in () at /usr/lib64/libglib-2.0.so.0 #3 0x7f3350bb76fc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7f3359b92dbb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f3359b3b10a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f335995e63a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7f335b7dbc55 in () at /usr/lib64/libQt5DBus.so.5 #8 0x7f335996322e in () at /usr/lib64/libQt5Core.so.5 #9 0x7f3354c3c565 in start_thread () at /lib64/libpthread.so.0 #10 0x7f3358d080af in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f33484b0700 (LWP 2807)): #0 0x7f3358cfc41b in poll () at /lib64/libc.so.6 #1 0x7f3357d5ff32 in () at /usr/lib64/libxcb.so.1 #2 0x7f3357d61c47 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f334a311a39 in () at /usr/lib64/qt5/plugins/platforms/../../../libQt5XcbQpa.so.5 #4 0x7f335996322e in () at /usr/lib64/libQt5Core.so.5 #5 0x7f3354c3c565 in start_thread () at /lib64/libpthread.so.0 #6 0x7f3358d080af in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f335e3ae400 (LWP 2800)): [KCrash Handler] #6 0xaad0 in () #7 0x7f3328f828d6 in () at /usr/lib64/libgobject-2.0.so.0 #8 0x7f332a4fe878 in () at /usr/lib64/qt5/plugins/plasma_runner_marble.so #9 0x002e in () #10 0x0001 in () #11 0x7f3328f513c4 in _init () at /usr/lib64/libgobject-2.0.so.0 #12 0x7f332a4ff058 in () at /usr/lib64/qt5/plugins/plasma_runner_marble.so #13 0x7f335e21378c in _dl_init () at /lib64/ld-linux-x86-64.so.2 #14 0x7f335e2186ef in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #15 0x7f3358d4999c in _dl_catch_error () at /lib64/libc.so.6 #16 0x7f335e217c29 in _dl_open () at /lib64/ld-linux-x86-64.so.2 #17 0x7f3351081f26 in dlopen_doit () at /lib64/libdl.so.2 #18 0x7f3358d4999c in _dl_catch_error () at /lib64/libc.so.6 #19 0x7f33510825c5 in _dlerror_run () at /lib64/libdl.so.2 #20 0x7f3351081fa1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2 #21 0x7f3359b389fc in () at /usr/lib64/libQt5Core.so.5 #22 0x7f3359b321b5 in () at /usr/lib64/libQt5Core.so.5 #23 0x7f335a78525a in KPluginLoader::load() () at /usr/lib64/libKF5CoreAddons.so.5 #24 0x7f335a78534a in KPluginLoader::pluginVersion() () at /usr/lib64/libKF5CoreAddons.so.5 #25 0x7f333c6df534 in () at /usr/lib64/libKF5Runner.so.5 #26 0x7f333c6e096e in () at /usr/lib64/libKF5Runner.so.5 #27 0x7f333c6dd7ca in Plasma::RunnerManager::launchQuery(QString const&, QString const&) () at /usr/lib64/libKF5Runner.so.5 #28 0x7f333c8f79b8 in Milou::SourcesModel::setQueryString(QString const&) () at /usr/lib64/libmilou.so.5 #29 0x7f333c8fcbb5 in () at /usr/lib64/libmilou.so.5 #30 0x7f335caab3ef in () at /usr/lib64/libQt5Qml.so.5 #31 0x7f335caabce6 in () at /usr/lib64/libQt5Qml.so.5 #32 0x7f
[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around
https://bugs.kde.org/show_bug.cgi?id=385594 --- Comment #46 from Nikolay Zlatev --- Application with space in the name can't be pinned at all. No error message, but if I choose "Add to Panel(Widget)" from menu, application attach to panel but system receive log message "14 16:31:04 plasmashell[10610]: Empty filename passed to function" _NET_WM_ICON_NAME(UTF8_STRING) = XdndAware(ATOM) = BITMAP WM_NAME(STRING) = "Data Extractor" _NET_WM_NAME(UTF8_STRING) = "Data Extractor" _KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 25882978 _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x3e, 0x7e, 0x0, 0x0 _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL _XEMBED_INFO(_XEMBED_INFO) = 0x0, 0x1 WM_CLIENT_LEADER(WINDOW): window id # 0x4e7 WM_HINTS(WM_HINTS): Client accepts input or input focus: True Initial state is Normal State. _NET_WM_PID(CARDINAL) = 25527 _NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 81788934 WM_CLASS(STRING) = "DataExtractor", "DataExtractor" WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST WM_NORMAL_HINTS(WM_SIZE_HINTS): user specified location: 4, 29 user specified size: 1272 by 687 program specified minimum size: 1010 by 640 window gravity: Static -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around
https://bugs.kde.org/show_bug.cgi?id=385594 --- Comment #47 from Nikolay Zlatev --- (In reply to Nikolay Zlatev from comment #46) > Application with space in the name can't be pinned at all. > No error message, but if I choose "Add to Panel(Widget)" from menu, > application attach to panel but system receive log message "14 16:31:04 > plasmashell[10610]: Empty filename passed to function" > > > _NET_WM_ICON_NAME(UTF8_STRING) = > XdndAware(ATOM) = BITMAP > WM_NAME(STRING) = "Data Extractor" > _NET_WM_NAME(UTF8_STRING) = "Data Extractor" > _KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 25882978 > _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x3e, 0x7e, 0x0, 0x0 > _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL > _XEMBED_INFO(_XEMBED_INFO) = 0x0, 0x1 > WM_CLIENT_LEADER(WINDOW): window id # 0x4e7 > WM_HINTS(WM_HINTS): > Client accepts input or input focus: True > Initial state is Normal State. > _NET_WM_PID(CARDINAL) = 25527 > _NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 81788934 > WM_CLASS(STRING) = "DataExtractor", "DataExtractor" > WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, > _NET_WM_PING, _NET_WM_SYNC_REQUEST > WM_NORMAL_HINTS(WM_SIZE_HINTS): > user specified location: 4, 29 > user specified size: 1272 by 687 > program specified minimum size: 1010 by 640 > window gravity: Static On App start дек 14 16:39:27 telamon kactivitymanagerd[10633]: Creating the cache for: "applications:Data Extractor.desktop" дек 14 16:39:27 telamon kactivitymanagerd[10633]: Already in database? true дек 14 16:39:27 telamon kactivitymanagerd[10633]: First update : QDateTime(2017-06-23 19:17:50.000 EEST Qt::TimeSpec(LocalTime)) дек 14 16:39:27 telamon kactivitymanagerd[10633]:Last update : QDateTime(2017-12-14 16:39:06.000 EET Qt::TimeSpec(LocalTime)) дек 14 16:39:27 telamon kactivitymanagerd[10633]: After the adjustment дек 14 16:39:27 telamon kactivitymanagerd[10633]: Current score : 16.7956 дек 14 16:39:27 telamon kactivitymanagerd[10633]: First update : QDateTime(2017-06-23 19:17:50.000 EEST Qt::TimeSpec(LocalTime)) дек 14 16:39:27 telamon kactivitymanagerd[10633]:Last update : QDateTime(2017-12-14 16:39:06.000 EET Qt::TimeSpec(LocalTime)) дек 14 16:39:27 telamon kactivitymanagerd[10633]: Interval length is 0 дек 14 16:39:27 telamon kactivitymanagerd[10633]: New score : 17.7956 дек 14 16:39:27 telamon kactivitymanagerd[10633]: ResourceScoreUpdated: "c4440aa5-23a1-46d9-9837-305110763943" "org.kde.plasma.kicker" "applications:Data Extractor.desktop" дек 14 16:39:27 telamon plasmashell[10610]: KActivitiesStats( 0x55d230a0fe50 ) ResultModelPrivate::onResultScoreUpdated result added: "applications:Data Extractor.desktop" score: 17.7956 last: 1513262365 first: 1498234670 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385942] Applications with URLs constructed with spaces can't be pinned and/or jump around
https://bugs.kde.org/show_bug.cgi?id=385942 Nikolay Zlatev changed: What|Removed |Added CC||n...@astrapaging.com --- Comment #3 from Nikolay Zlatev --- Comming from https://bugs.kde.org/show_bug.cgi?id=385594 Application with space in the name can't be pinned at all. No error message, but if I choose "Add to Panel(Widget)" from menu, application attach to panel but system receive log message "14 16:31:04 plasmashell[10610]: Empty filename passed to function" _NET_WM_ICON_NAME(UTF8_STRING) = XdndAware(ATOM) = BITMAP WM_NAME(STRING) = "Data Extractor" _NET_WM_NAME(UTF8_STRING) = "Data Extractor" _KDE_NET_WM_USER_CREATION_TIME(CARDINAL) = 25882978 _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x3, 0x3e, 0x7e, 0x0, 0x0 _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL _XEMBED_INFO(_XEMBED_INFO) = 0x0, 0x1 WM_CLIENT_LEADER(WINDOW): window id # 0x4e7 WM_HINTS(WM_HINTS): Client accepts input or input focus: True Initial state is Normal State. _NET_WM_PID(CARDINAL) = 25527 _NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 81788934 WM_CLASS(STRING) = "DataExtractor", "DataExtractor" WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST WM_NORMAL_HINTS(WM_SIZE_HINTS): user specified location: 4, 29 user specified size: 1272 by 687 program specified minimum size: 1010 by 640 window gravity: Static On App start дек 14 16:39:27 telamon kactivitymanagerd[10633]: Creating the cache for: "applications:Data Extractor.desktop" дек 14 16:39:27 telamon kactivitymanagerd[10633]: Already in database? true дек 14 16:39:27 telamon kactivitymanagerd[10633]: First update : QDateTime(2017-06-23 19:17:50.000 EEST Qt::TimeSpec(LocalTime)) дек 14 16:39:27 telamon kactivitymanagerd[10633]:Last update : QDateTime(2017-12-14 16:39:06.000 EET Qt::TimeSpec(LocalTime)) дек 14 16:39:27 telamon kactivitymanagerd[10633]: After the adjustment дек 14 16:39:27 telamon kactivitymanagerd[10633]: Current score : 16.7956 дек 14 16:39:27 telamon kactivitymanagerd[10633]: First update : QDateTime(2017-06-23 19:17:50.000 EEST Qt::TimeSpec(LocalTime)) дек 14 16:39:27 telamon kactivitymanagerd[10633]:Last update : QDateTime(2017-12-14 16:39:06.000 EET Qt::TimeSpec(LocalTime)) дек 14 16:39:27 telamon kactivitymanagerd[10633]: Interval length is 0 дек 14 16:39:27 telamon kactivitymanagerd[10633]: New score : 17.7956 дек 14 16:39:27 telamon kactivitymanagerd[10633]: ResourceScoreUpdated: "c4440aa5-23a1-46d9-9837-305110763943" "org.kde.plasma.kicker" "applications:Data Extractor.desktop" дек 14 16:39:27 telamon plasmashell[10610]: KActivitiesStats( 0x55d230a0fe50 ) ResultModelPrivate::onResultScoreUpdated result added: "applications:Data Extractor.desktop" score: 17.7956 last: 1513262365 first: 1498234670 After renaming desktop file mv "Data Extractor.desktop" DataExtractor.desktop everything work at it should. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385942] Applications with URLs constructed with spaces can't be pinned and/or jump around
https://bugs.kde.org/show_bug.cgi?id=385942 --- Comment #7 from Nikolay Zlatev --- If .desktop file contains 'space' in the file name, launcher can't be pinned at all (correctly placed and drawed in task manager) Tested with Arch x86_64 Plasma 5.11.5 Framework 5.42.0 With and without D10253.diff applied Application start without D10253 фев 05 15:22:03 telamon kactivitymanagerd[1172]: Creating the cache for: "applications:Data Extractor.desktop" фев 05 15:22:03 telamon kactivitymanagerd[1172]: Already in database? true фев 05 15:22:03 telamon kactivitymanagerd[1172]: First update : QDateTime(2017-06-23 19:17:30.000 EEST Qt::TimeSpec(LocalTime)) фев 05 15:22:03 telamon kactivitymanagerd[1172]:Last update : QDateTime(2018-02-05 15:20:41.000 EET Qt::TimeSpec(LocalTime)) фев 05 15:22:03 telamon kactivitymanagerd[1172]: After the adjustment фев 05 15:22:03 telamon kactivitymanagerd[1172]: Current score : 2 фев 05 15:22:03 telamon kactivitymanagerd[1172]: First update : QDateTime(2017-06-23 19:17:30.000 EEST Qt::TimeSpec(LocalTime)) фев 05 15:22:03 telamon kactivitymanagerd[1172]:Last update : QDateTime(2018-02-05 15:20:41.000 EET Qt::TimeSpec(LocalTime)) фев 05 15:22:03 telamon kactivitymanagerd[1172]: Interval length is 0 фев 05 15:22:03 telamon kactivitymanagerd[1172]: New score : 3 фев 05 15:22:03 telamon kactivitymanagerd[1172]: ResourceScoreUpdated: "c4440aa5-23a1-46d9-9837-305110763943" "org.kde.krunner" "applications:Data Extractor.desktop" Application start with D10253 фев 05 15:32:03 telamon kactivitymanagerd[1172]: Creating the cache for: "applications:Data Extractor.desktop" фев 05 15:32:03 telamon kactivitymanagerd[1172]: Already in database? true фев 05 15:32:03 telamon kactivitymanagerd[1172]: First update : QDateTime(2017-06-23 19:17:50.000 EEST Qt::TimeSpec(LocalTime)) фев 05 15:32:03 telamon kactivitymanagerd[1172]:Last update : QDateTime(2017-12-14 16:49:25.000 EET Qt::TimeSpec(LocalTime)) фев 05 15:32:03 telamon kactivitymanagerd[1172]: After the adjustment фев 05 15:32:03 telamon kactivitymanagerd[1172]: Current score : 3.5872 фев 05 15:32:03 telamon kactivitymanagerd[1172]: First update : QDateTime(2017-06-23 19:17:50.000 EEST Qt::TimeSpec(LocalTime)) фев 05 15:32:03 telamon kactivitymanagerd[1172]:Last update : QDateTime(2017-12-14 16:49:25.000 EET Qt::TimeSpec(LocalTime)) фев 05 15:32:03 telamon kactivitymanagerd[1172]: Interval length is 0 фев 05 15:32:03 telamon kactivitymanagerd[1172]: New score : 4.5872 фев 05 15:32:03 telamon kactivitymanagerd[1172]: ResourceScoreUpdated: "c4440aa5-23a1-46d9-9837-305110763943" "org.kde.plasma.kicker" "applications:Data Extractor.desktop" фев 05 15:32:03 telamon plasmashell[10808]: KActivitiesStats( 0x55f64a337b40 ) ResultModelPrivate::onResultScoreUpdated result added: "applications:Data Extractor.desktop" score: 4.5872 last: 1517837521 first: 1498234670 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385942] Applications with URLs constructed with spaces can't be pinned and/or jump around
https://bugs.kde.org/show_bug.cgi?id=385942 --- Comment #10 from Nikolay Zlatev --- Problem with libreoffice: All launchers execute same file (/usr/bin/libreoffice) with parameter (--calc for example). Wrapping executable to libreoffice_calc improves things. Also if --nologo (disable splash screen and no dynamic change of window classname) is applied, launcher can't be placed/combined correctly in taskmanager at all. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385942] Applications with URLs constructed with spaces can't be pinned and/or jump around
https://bugs.kde.org/show_bug.cgi?id=385942 --- Comment #12 from Nikolay Zlatev --- Created attachment 110352 --> https://bugs.kde.org/attachment.cgi?id=110352&action=edit Taskmanager plasmashell crash If we have pinned launcher with 'Exec' parameter that not exists, on start whole plasmashell crash. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385942] Applications with URLs constructed with spaces can't be pinned and/or jump around
https://bugs.kde.org/show_bug.cgi?id=385942 --- Comment #14 from Nikolay Zlatev --- Can confirm, patch D10383 resolve spaces issue. Plasma 5.11.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385942] Applications with URLs constructed with spaces can't be pinned and/or jump around
https://bugs.kde.org/show_bug.cgi?id=385942 --- Comment #16 from Nikolay Zlatev --- (In reply to Eike Hein from comment #15) > > If we have pinned launcher with 'Exec' parameter that not exists, on start > > whole plasmashell crash. > > I can't reproduce that crash (I get an error dialog "Unknown application > folder"). The backtrace also looks unrelated ... 0. journalctl -f 1. Pin app 2. Edit .desktop file add random symbol to executable 3. Start application (alert dialog appears Could not find the program etc.) 4. Click on OK button and wait -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385942] Applications with URLs constructed with spaces can't be pinned and/or jump around
https://bugs.kde.org/show_bug.cgi?id=385942
--- Comment #17 from Nikolay Zlatev ---
(In reply to Eike Hein from comment #15)
> > If we have pinned launcher with 'Exec' parameter that not exists, on start
> > whole plasmashell crash.
>
> I can't reproduce that crash (I get an error dialog "Unknown application
> folder"). The backtrace also looks unrelated ...
фев 08 16:10:12 telamon kdeinit5[20168]: Service
"org.kde.StatusNotifierHost-28341" unregistered
фев 08 16:10:12 telamon systemd[1]: Started Process Core Dump (PID 28716/UID
0).
фев 08 16:10:12 telamon kwin_x11[20197]: QXcbConnection: XCB error: 3
(BadWindow), sequence: 45669, resource id: 33554442, major code: 15
(QueryTree), minor code: 0
фев 08 16:10:12 telamon kwin_x11[20197]: QXcbConnection: XCB error: 3
(BadWindow), sequence: 45723, resource id: 33554454, major code: 15
(QueryTree), minor code: 0
фев 08 16:10:12 telamon kwin_x11[20197]: QXcbConnection: XCB error: 3
(BadWindow), sequence: 45776, resource id: 33554466, major code: 15
(QueryTree), minor code: 0
фев 08 16:10:12 telamon plasmashell[28714]: kf5.karchive: bzDecompress returned
-5
фев 08 16:10:12 telamon plasmashell[28714]: Warning: all files used by qml by
the plasmoid should be in ui/. The file in the path
"file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/LayoutManager.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/LayoutManager.js")
фев 08 16:10:12 telamon plasmashell[28714]: Warning: all files used by qml by
the plasmoid should be in ui/. The file in the path
"file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/FolderTools.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderTools.js")
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 385942] Applications with URLs constructed with spaces can't be pinned and/or jump around
https://bugs.kde.org/show_bug.cgi?id=385942
--- Comment #18 from Nikolay Zlatev ---
> фев 08 16:10:12 telamon kdeinit5[20168]: Service
> "org.kde.StatusNotifierHost-28341" unregistered
> фев 08 16:10:12 telamon systemd[1]: Started Process Core Dump (PID 28716/UID
> 0).
> фев 08 16:10:12 telamon plasmashell[28714]: kf5.karchive: bzDecompress
> returned -5
> фев 08 16:10:12 telamon plasmashell[28714]: Warning: all files used by qml
> by the plasmoid should be in ui/. The file in the path
> "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/
> LayoutManager.js" was expected at
> QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/
> ui/LayoutManager.js")
> фев 08 16:10:12 telamon plasmashell[28714]: Warning: all files used by qml
> by the plasmoid should be in ui/. The file in the path
> "file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/
> FolderTools.js" was expected at
> QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/
> ui/FolderTools.js")
This happen only if .desktop file is pinned.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 385942] Applications with URLs constructed with spaces can't be pinned and/or jump around
https://bugs.kde.org/show_bug.cgi?id=385942 --- Comment #21 from Nikolay Zlatev --- (In reply to Eike Hein from comment #20) > Patch for the Exec= issue: https://phabricator.kde.org/D10405 Tested everything works fine. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 388890] New: Kontact crash on close if Akregator tab was viewed opened
https://bugs.kde.org/show_bug.cgi?id=388890 Bug ID: 388890 Summary: Kontact crash on close if Akregator tab was viewed opened Product: kontact Version: 5.7.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: nikolay.brookst...@nextnetworks.eu Target Milestone: --- Application: kontact (5.7.0) Qt Version: 5.9.2 Frameworks Version: 5.41.0 Operating System: Linux 4.14.11-300.fc27.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: 1) Open Kontact 2) Open Akregator tab 3) Read some news 4) Change an active tab or dont change (same effect) 5) Click on a window close button 6) Crash The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9c6b323980 (LWP 4904))] Thread 25 (Thread 0x7f9b0ef3a700 (LWP 4986)): #0 0x7f9c54c16434 in g_mutex_unlock () at /lib64/libglib-2.0.so.0 #1 0x7f9c54bd03d3 in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f9c54bd0e0b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f9c54bd0fec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f9c657ca35b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f9c657780ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f9c655c98ba in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f9c655cdb92 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f9c5973461b in start_thread () at /lib64/libpthread.so.0 #9 0x7f9c6496b91f in clone () at /lib64/libc.so.6 Thread 24 (Thread 0x7f9b14964700 (LWP 4963)): #0 0x7f9c5973ac4b in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9c5e0c7cc5 in base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker*) () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #2 0x7f9c5e0c81a7 in base::SequencedWorkerPool::Worker::Run() () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #3 0x7f9c5e0c8f41 in base::SimpleThread::ThreadMain() () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #4 0x7f9c5e0c560b in base::(anonymous namespace)::ThreadFunc(void*) () at /usr/lib64/qt5-qtwebengine-freeworld/libQt5WebEngineCore.so.5 #5 0x7f9c5973461b in start_thread () at /lib64/libpthread.so.0 #6 0x7f9c6496b91f in clone () at /lib64/libc.so.6 Thread 23 (Thread 0x7f9b1761f700 (LWP 4953)): #0 0x7f9c6495a888 in read () at /lib64/libc.so.6 #1 0x7f9c54c150e0 in g_wakeup_acknowledge () at /lib64/libglib-2.0.so.0 #2 0x7f9c54bd09e8 in g_main_context_check () at /lib64/libglib-2.0.so.0 #3 0x7f9c54bd0e80 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #4 0x7f9c54bd0fec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #5 0x7f9c657ca35b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f9c657780ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #7 0x7f9c655c98ba in QThread::exec() () at /lib64/libQt5Core.so.5 #8 0x7f9c655cdb92 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f9c5973461b in start_thread () at /lib64/libpthread.so.0 #10 0x7f9c6496b91f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f9b30881700 (LWP 4937)): #0 0x7f9c54bcde71 in g_source_iter_next () at /lib64/libglib-2.0.so.0 #1 0x7f9c54bd0811 in g_main_context_check () at /lib64/libglib-2.0.so.0 #2 0x7f9c54bd0e80 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f9c54bd0fec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f9c657ca35b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f9c657780ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f9c655c98ba in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f9c655cdb92 in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #8 0x7f9c5973461b in start_thread () at /lib64/libpthread.so.0 #9 0x7f9c6496b91f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f9b31f23700 (LWP 4935)): #0 0x7f9c6495f36b in poll () at /lib64/libc.so.6 #1 0x7f9c54bd0ed9 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #2 0x7f9c54bd0fec in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #3 0x7f9c657ca35b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #4 0x7f9c657780ea in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f9c655c98ba in QThr
[ktouch] [Bug 350336] KTouch lags and uses full (100%) CPU resources when typing fast.
https://bugs.kde.org/show_bug.cgi?id=350336 Nikolay Druchaty changed: What|Removed |Added CC||druch...@gmail.com --- Comment #14 from Nikolay Druchaty --- Hi Sebastian, I've tried to install KTouch from the sources. I've installed 'kqtquickcharts' mentioned in README file. But KTouch still can't be run. I got "module "org.kde.charts" is not installed". I use Ubuntu 16.10. Could you please help me to solve the problem? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around
https://bugs.kde.org/show_bug.cgi?id=385594 Nikolay Zlatev changed: What|Removed |Added CC||n...@astrapaging.com --- Comment #22 from Nikolay Zlatev --- (In reply to Kai Uwe Broulik from comment #18) > Please give a try to > https://phabricator.kde.org/D8257 > and more importantly > https://phabricator.kde.org/D8258 After recompiling libtaskmanager patched with D8257 and D8258 everything seem's to work fine (arch). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385594] launchInPlace is broken from libtaskmanager; causes Icons-Only Task manager icons to jump around
https://bugs.kde.org/show_bug.cgi?id=385594 --- Comment #36 from Nikolay Zlatev --- (In reply to Paul from comment #35) > Created attachment 108586 [details] > Screenshot > > This is still happening with the icon for Libre Office, as shown in the > attached screenshot. > > Top: LO Icon position before opening application. > Bottom: LO Icon moves to far right when application is open. > > Plasma: 5.11.1 > Frameworks: 5.38.0 > Qt: 5.9.2 Same here. Work around, unpin libre office, start it from application menu, once application is running right click it on taskbar in select pin. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 Nikolay Brookstein changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #14 from Nikolay Brookstein --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 Nikolay Brookstein changed: What|Removed |Added CC||nikolay.brookstein@nextnetw ||orks.eu --- Comment #15 from Nikolay Brookstein --- KMail 5.3.3 Kolab 16 server with TLS/STARRTLS log on the server side: Dez 19 23:29:51 test.com sieve[7287]: inittls: Loading hard-coded DH parameters Dez 19 23:29:51 test.com sieve[7287]: STARTTLS failed Dez 19 23:29:51 test.com sieve[7287]: Lost connection to client -- exiting problem still persists! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990
--- Comment #16 from Nikolay Brookstein ---
Some logging from the kmail side:
log_kmanagersieve: "session1" connect to host url:
QUrl("sieve://alice%40test@mail-01.test.com:4190?x-mech=PLAIN")
log_kmanagersieve: "session1" void
KManageSieve::Session::scheduleJob(KManageSieve::SieveJob*)
KManageSieve::SieveJob(0x5607dd4137e0)
log_kmanagersieve: "session1" void
KManageSieve::Session::killJob(KManageSieve::SieveJob*, KJob::KillVerbosity)
KManageSieve::SieveJob(0x5607dd4137e0)
log_kmanagersieve: "session1" void
KManageSieve::Session::scheduleJob(KManageSieve::SieveJob*)
KManageSieve::SieveJob(0x5607dd115640)
log_kmanagersieve: S: "\"IMPLEMENTATION\" \"Cyrus timsieved
2.5.10-55-gb6dbffa-Kolab-2.5.10-6.1.el7.kolab_16\""
log_kmanagersieve: 1 "IMPLEMENTATION" "Cyrus timsieved
2.5.10-55-gb6dbffa-Kolab-2.5.10-6.1.el7.kolab_16" "" 0
log_kmanagersieve: S: "\"SASL\" \"\""
log_kmanagersieve: 1 "SASL" "" "" 0
log_kmanagersieve: "session1" Connected to Sieve server: "Cyrus timsieved
2.5.10-55-gb6dbffa-Kolab-2.5.10-6.1.el7.kolab_16"
log_kmanagersieve: S: "\"SIEVE\" \"comparator-i;ascii-numeric fileinto reject
vacation imapflags notify include envelope body relational regex subaddress
copy date\""
log_kmanagersieve: "session1" Server SASL authentication methods: ()
log_kmanagersieve: 1 "SIEVE" "comparator-i;ascii-numeric fileinto reject
vacation imapflags notify include envelope body relational regex subaddress
copy date" "" 0
log_kmanagersieve: S: "\"STARTTLS\""
log_kmanagersieve: "session1" Server script capabilities:
("comparator-i;ascii-numeric", "fileinto", "reject", "vacation", "imapflags",
"notify", "include", "envelope", "body", "relational", "regex", "subaddress",
"copy", "date")
log_kmanagersieve: 1 "STARTTLS" "" "" 0
log_kmanagersieve: S: "\"UNAUTHENTICATE\""
log_kmanagersieve: "session1" Server supports TLS
log_kmanagersieve: 1 "UNAUTHENTICATE" "" "" 0
log_kmanagersieve: S: "OK"
log_kmanagersieve: "session1" Unrecognised key "UNAUTHENTICATE"
log_kmanagersieve: 2 "OK" "" "" 0
log_kmanagersieve: "session1" Sieve server ready & awaiting authentication.
log_kmanagersieve: C: "STARTTLS"
log_kmanagersieve: S: "OK \"Begin TLS negotiation now\""
log_kmanagersieve: 2 "OK \"Begin TLS negotiation now\"" "" "" 0
log_kmanagersieve: SessionThread::doStartSsl()
log_kmanagersieve: void KManageSieve::SessionThread::slotSocketError() "Unknown
error"
log_kmanagersieve: "session1" No job for reporting this error message! "Could
not connect to host Unknown error."
log_kmanagersieve: Initial SSL handshake failed. cipher.isNull() is true ,
cipher.usedBits() is 0 , the socket says: "Unknown error" and the list of SSL
errors contains 0 items.
log_kmanagersieve: "session1" TLS negotiation done.
log_kmanagersieve: "session1" TLS negotiation done, m_state= 2
log_kmanagersieve: Initial SSL handshake failed. cipher.isNull() is true ,
cipher.usedBits() is 0 , the socket says: "Unknown error" and the list of SSL
errors contains 0 items.
log_kmanagersieve: "session1" TLS negotiation done.
log_kmanagersieve: "session1" TLS negotiation done, m_state= 2
It looks like we have several problems here.
- First of all is probably wrong interprets a username from the imap, so
instead of "al...@test.com" we getting "alice%40test@mail-01.test.com"
- Second one, that "SessionThread::doStartSsl()" fails
I can make a email account to a KDE developer if it helps to debug.
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 311990] Problem connetcing to dovecot-managesieve with STARTTLS and auth=CRAM-MD5 /LOGIN
https://bugs.kde.org/show_bug.cgi?id=311990 --- Comment #18 from Nikolay Brookstein --- (In reply to Laurent Montel from comment #17) > For sure I can't investigate this week (Christmas holidays for me) but > indeed an account which can provide error will help me to investigate for > sure. That would be great! Than I will create an account for you and send you login data. Can I use your *@kde.org address for this? Merry Christmas P.S. Probably the majority is busy with holidays && famirly && friends this week :D So I have expected that only after 1-2 weeks it will be possible to try to find out what is going wrong here. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 356291] New: Bug in libQt5Sql.so.5.4.2
https://bugs.kde.org/show_bug.cgi?id=356291 Bug ID: 356291 Summary: Bug in libQt5Sql.so.5.4.2 Product: kdelibs Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: darkeyen...@gmail.com After connecting the mouse kde is stop. After logout and login in kde, kde working normally. dmesg command show kactivitymanage[1370]: segfault at 7fb5e4127cd0 ip 7fb5e40d11b1 sp 7fffbf3b08f8 error 4 in libQt5Sql.so.5.4.2[7fb5e40bd000+3f000]. This occurs several times per day. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 356291] Bug in libQt5Sql.so.5.4.2
https://bugs.kde.org/show_bug.cgi?id=356291 --- Comment #1 from Nikolay --- [12984.496939] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [12984.496945] usb 2-1.3: Product: USB Mouse [12984.496949] usb 2-1.3: Manufacturer: A4Tech [12984.502659] input: A4Tech USB Mouse as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:09DA:000A.0004/input/input17 [12984.556012] a4tech 0003:09DA:000A.0004: input,hidraw0: USB HID v1.10 Mouse [A4Tech USB Mouse] on usb-:00:1d.0-1.3/input0 [13090.905902] show_signal_msg: 21 callbacks suppressed [13090.905909] kactivitymanage[1370]: segfault at 7fb5e4127cd0 ip 7fb5e40d11b1 sp 7fffbf3b08f8 error 4 in libQt5Sql.so.5.4.2[7fb5e40bd000+3f000] -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 356333] New: Kubuntu 15.10. Application: krunner (krunner), signal: Aborted. Failure after disconnecting the external video output
https://bugs.kde.org/show_bug.cgi?id=356333 Bug ID: 356333 Summary: Kubuntu 15.10. Application: krunner (krunner), signal: Aborted. Failure after disconnecting the external video output Product: krunner Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: windows Assignee: m...@vhanda.in Reporter: darkeyen...@gmail.com Application: krunner (0.1) Qt Version: 5.4.2 Operating System: Linux 4.2.0-19-generic x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: Kubuntu 15.10. Turn off the output from the external monitor. Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1ced2ac800 (LWP 1521))] Thread 8 (Thread 0x7f1cd95ce700 (LWP 1522)): #0 0x7f1ce9d6d8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f1ce925fbd2 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f1ce926174f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f1cdb918a39 in QXcbEventReader::run (this=0x193d680) at qxcbconnection.cpp:1105 #4 0x7f1cea4602be in QThreadPrivate::start (arg=0x193d680) at thread/qthread_unix.cpp:337 #5 0x7f1ce7fcc6aa in start_thread (arg=0x7f1cd95ce700) at pthread_create.c:333 #6 0x7f1ce9d78eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f1cceeed700 (LWP 1528)): #0 0x7f1ce9d6d8dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f1ce744d1ec in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1ce744d2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1cea69729b in QEventDispatcherGlib::processEvents (this=0x7f1cc80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f1cea63d75a in QEventLoop::exec (this=this@entry=0x7f1cceeecda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f1cea45b3d4 in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f1cec262f85 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f1cea4602be in QThreadPrivate::start (arg=0x1c76be0) at thread/qthread_unix.cpp:337 #8 0x7f1ce7fcc6aa in start_thread (arg=0x7f1cceeed700) at pthread_create.c:333 #9 0x7f1ce9d78eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f1cbf84b700 (LWP 9216)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1cea46155b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x2145c50) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x19815b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f1cc7bc64eb in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x1e10880, th=) at ../../src/weaver.cpp:594 #4 0x7f1cc7bc729f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x1e10880, th=th@entry=0x352f050, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at ../../src/weaver.cpp:554 #5 0x7f1cc7bcb4c8 in ThreadWeaver::WorkingHardState::applyForWork (this=0x1dea600, th=0x352f050, wasBusy=) at ../../src/workinghardstate.cpp:66 #6 0x7f1cc7bc644d in ThreadWeaver::Weaver::applyForWork (this=, th=0x352f050, wasBusy=) at ../../src/weaver.cpp:568 #7 0x7f1cc7bcb522 in ThreadWeaver::WorkingHardState::applyForWork (this=0x1dea600, th=0x352f050, wasBusy=) at ../../src/workinghardstate.cpp:73 #8 0x7f1cc7bc644d in ThreadWeaver::Weaver::applyForWork (this=, th=0x352f050, wasBusy=) at ../../src/weaver.cpp:568 #9 0x7f1cc7bc9423 in ThreadWeaver::Thread::run (this=0x352f050) at ../../src/thread.cpp:103 #10 0x7f1cea4602be in QThreadPrivate::start (arg=0x352f050) at thread/qthread_unix.cpp:337 #11 0x7f1ce7fcc6aa in start_thread (arg=0x7f1cbf84b700) at pthread_create.c:333 #12 0x7f1ce9d78eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f1cb7fff700 (LWP 9217)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1cea46155b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x2145c50) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x19815b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f1cc7bc64eb in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x1e10880, th=) at ../../src/weaver.cpp:594 #4 0x7f1cc7bc729f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x1e10880, th=th@entry=0x34c
[apper] [Bug 343276] display non-latin chars as '?' in package description
https://bugs.kde.org/show_bug.cgi?id=343276 Nikolay changed: What|Removed |Added CC||azkob...@ya.ru --- Comment #7 from Nikolay --- Same here. Debian Jessie, ru_RU.UTF-8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360211] window decorations disappear randomly
https://bugs.kde.org/show_bug.cgi?id=360211 Nikolay Naydenov changed: What|Removed |Added CC||niki_nayde...@yahoo.com --- Comment #8 from Nikolay Naydenov --- I have the same problem and a lot more info as well as crash report. I can provide a way to reproduce the bug in 100% in 60 sec after a fresh install of the latest Kubuntu. I have no info for other distros. The bug is not related to the graphic adapter - it is reproducible on my laptop, as well on virtualbox on 100%. Let give now the info. First the bug report. It do not contains backtrace, but you can collect it for sure, as it is easily reproducible with few clicks: Application: kwin_x11 (5.6.5) Qt Version: 5.5.1 Frameworks Version: 5.23.0 Operating System: Linux 4.4.0-36-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: The crash can be reproduced every time. -- Backtrace: A useful backtrace could not be generated Report to https://bugs.kde.org/ No how to reproduce it: 1. Fresh install of Kubuntu 2. You can update the KDE from backports or not. The bug is present on plasma 5.5 as well on latest 5.6.5 (that is available in kubuntu backports). It does not mater of the version for the moment. 3. Open system settings -> application stile -> window decorations and choose plastik. Apply it. 4. Open konsole. Just open no other action is need. 5. Close the system settings first and next konsole 6. Open again system settings and go to: system settings -> startup and shutdown -> login screen (sddm) -> background and open the file browser to choose the background image. 7. You are presented with a little delay in opening the file browser and at the moment it shows all decorations on all windows disappears. 8. The bug does not occur or at least not easy reproducible with default breeze decorations, but plastik come by default. Even remove plastik or fix it. The bug also happens frequently (if not always) on other case: 1. Install skype 2. Login to skype and check the box to log automatically when skype opens 3. Leave the desktop session with skype running, so skype will be remembered in the session and started on the next login 4. When you login next time, skype try to log-in to your account and require networking to work 5. In case you are with wifi, kwallet prompt will be opened to ask for password (kwallet password to unlock the wallet and extract the wifi password from the wallet) 6. At the moment you are represented with the password prompt bug happens (all the time) and all decorations disappears. Again this happens only when you choose to use the plastik decorations. It is ok with breeze I hope this bug will be reopened. If not I will file a new one (in case I see no reaction) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 356288] New: Dolphin crashes if 'Configure Dolphin' selected in menu
https://bugs.kde.org/show_bug.cgi?id=356288 Bug ID: 356288 Summary: Dolphin crashes if 'Configure Dolphin' selected in menu Product: dolphin Version: 15.08.3 Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: niktische...@gmail.com Application: dolphin (15.08.3) Qt Version: 5.5.1 Operating System: Linux 4.1.13-smp i686 Distribution (Platform): Slackware Packages -- Information about the crash: 1. Open dolphin 2. Click on 'Control' button in toolbar 3. Select 'Configure Dolphin...' in menu Expected result: configuration dialog opened Result: crash The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xb1aae780 (LWP 3966))] Thread 2 (Thread 0xaf3bab40 (LWP 3968)): #0 0x in poll () at /lib/libc.so.6 #1 0x in g_poll () at /usr/lib/libglib-2.0.so.0 #2 0x in () at /usr/lib/libglib-2.0.so.0 #3 0x in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #4 0x in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x in QEventLoop::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x in QThread::run() () at /usr/lib/libQt5Core.so.5 #9 0x in () at /usr/lib/libQt5Core.so.5 #10 0x in start_thread () at /lib/libpthread.so.0 #11 0x in clone () at /lib/libc.so.6 Thread 1 (Thread 0xb1aae780 (LWP 3966)): [KCrash Handler] #6 0x in QtSharedPointer::ExternalRefCountData::getAndRef(QObject const*) () at /usr/lib/libQt5Core.so.5 #7 0x in () at /usr/lib/libQt5Widgets.so.5 #8 0x in () at /usr/lib/libQt5Widgets.so.5 #9 0x in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #13 0x in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5 #14 0x in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #15 0x in () at /usr/lib/libQt5XcbQpa.so.5 #16 0x in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #17 0x in () at /usr/lib/libglib-2.0.so.0 #18 0x in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #19 0x in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #20 0x in () at /usr/lib/libQt5XcbQpa.so.5 #21 0x in QEventLoop::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #22 0x in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #23 0x in QMenu::exec(QPoint const&, QAction*) () at /usr/lib/libQt5Widgets.so.5 #24 0x in () at /usr/lib/libQt5Widgets.so.5 #25 0x in () at /usr/lib/libQt5Widgets.so.5 #26 0x in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5 #27 0x in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/libQt5Core.so.5 #28 0x in QAbstractButton::pressed() () at /usr/lib/libQt5Widgets.so.5 #29 0x in () at /usr/lib/libQt5Widgets.so.5 #30 0x in QAbstractButton::mousePressEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5 #31 0x in QToolButton::mousePressEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5 #32 0x in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #33 0x in QAbstractButton::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #34 0x in QToolButton::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #35 0x in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #36 0x in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #37 0x in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #38 0x in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () at /usr/lib/libQt5Widgets.so.5 #39 0x in () at /usr/lib/libQt5Widgets.so.5 #40 0x in () at /usr/lib/libQt5Widgets.so.5 #41 0x in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
[ktouch] [Bug 362316] very slow reaction after typing a key
https://bugs.kde.org/show_bug.cgi?id=362316 Nikolay Druchaty changed: What|Removed |Added CC||druch...@gmail.com --- Comment #1 from Nikolay Druchaty --- I have the same problem on Ubuntu 16.04. OS has been installed from the scratch. My laptop has ATI 6370M graphics. I suppose that graphics driver is the cause of such behaviour. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 343034] KMail insists on offline mode, even when network connection is available
https://bugs.kde.org/show_bug.cgi?id=343034 Nikolay Shaplov changed: What|Removed |Added CC||dh...@nataraj.su --- Comment #9 from Nikolay Shaplov --- I confirm this bug. I experience this problem with KMail 4.14.1 && KDE 4.14.2 from Debian Jessie For historical reasons I use wcid instead of network-manager and I have the same problem with KMail as Martin Steigerwald described. The workaround described in report works for me too (Thanks for it) -- You are receiving this mail because: You are watching all bug changes.
