[skrooge] [Bug 401121] New: transfer from an account to another - the amount on the destination is 0
https://bugs.kde.org/show_bug.cgi?id=401121 Bug ID: 401121 Summary: transfer from an account to another - the amount on the destination is 0 Product: skrooge Version: 2.16.0 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: 100ye...@tleroy.org CC: steph...@mankowski.fr Target Milestone: --- SUMMARY hello, when i create a transfer from account test1 to account test2, the negative amount is ok on test1 account, but it appears to be zero on test2 account. STEPS TO REPRODUCE create account test1 with initial balance 1000 create account test2 with initial balance 0 create transfert from test1 to test2, amount 500 OBSERVED RESULT operation -500 ok on test1 operation 0 on test2 wrong total balance 500 EXPECTED RESULT operation +500 on test2 right total balance 1000 SOFTWARE/OS VERSIONS debian french testing buster skrooge 2.16.2 french -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 401121] transfer from an account to another - the amount on the destination is 0
https://bugs.kde.org/show_bug.cgi?id=401121 --- Comment #1 from thierry <100ye...@tleroy.org> --- Created attachment 116360 --> https://bugs.kde.org/attachment.cgi?id=116360&action=edit operation -500 ok on test1 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 401121] transfer from an account to another - the amount on the destination is 0
https://bugs.kde.org/show_bug.cgi?id=401121 --- Comment #2 from thierry <100ye...@tleroy.org> --- Created attachment 116361 --> https://bugs.kde.org/attachment.cgi?id=116361&action=edit operation 0 on test2 -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 401121] transfer from an account to another - the amount on the destination is 0
https://bugs.kde.org/show_bug.cgi?id=401121 --- Comment #3 from thierry <100ye...@tleroy.org> --- Created attachment 116362 --> https://bugs.kde.org/attachment.cgi?id=116362&action=edit wrong total balance -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 495963] New: [Echec de la conversion de projet « OpenTimelineIO »]
https://bugs.kde.org/show_bug.cgi?id=495963
Bug ID: 495963
Summary: [Echec de la conversion de projet « OpenTimelineIO »]
Classification: Applications
Product: kdenlive
Version: 24.08.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Rendering & Export
Assignee: j...@kdenlive.org
Reporter: bil...@gmail.com
Target Milestone: ---
Created attachment 175645
--> https://bugs.kde.org/attachment.cgi?id=175645&action=edit
Screenshot
Hello,
[Echec de la conversion de projet « OpenTimelineIO »]
When I export the video I have this error :
Traceback (most recent call last):
File "/app/lib/python3.11/site-packages/opentimelineio/adapters/__init__.py",
line 94, in from_filepath
return plugins.ActiveManifest().from_filepath(outext)
^^
File "/app/lib/python3.11/site-packages/opentimelineio/plugins/manifest.py",
line 187, in from_filepath
raise exceptions.NoKnownAdapterForExtensionError(suffix)
opentimelineio.exceptions.NoKnownAdapterForExtensionError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/app/bin/otioconvert", line 33, in
sys.exit(load_entry_point('OpenTimelineIO==0.17.0', 'console_scripts',
'otioconvert')())
^^
File
"/app/lib/python3.11/site-packages/opentimelineio/console/otioconvert.py", line
215, in main
out_adapter = otio.adapters.from_filepath(args.output).name
File "/app/lib/python3.11/site-packages/opentimelineio/adapters/__init__.py",
line 96, in from_filepath
raise exceptions.NoKnownAdapterForExtensionError(
opentimelineio.exceptions.NoKnownAdapterForExtensionError: No adapter for
suffix '' on file '/home/thierry/Vidéos/Anniv_Philippe/test'
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 498746] New: Find my phone will not ring on folded flip phones
https://bugs.kde.org/show_bug.cgi?id=498746
Bug ID: 498746
Summary: Find my phone will not ring on folded flip phones
Classification: Applications
Product: kdeconnect
Version: unspecified
Platform: Android
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: android-application
Assignee: albertv...@gmail.com
Reporter: kde...@thierry.charles.tf
CC: andrew.g.r.hol...@gmail.com
Target Milestone: ---
SUMMARY
I got a Samsung Galaxy Z-Flip 5 (foldable device). Trying "Find my phone" will
not make the phone ring if it is folded
STEPS TO REPRODUCE
1. take your foldable phone and fold it,
2. on your PC, use the Find my phone functionality ("Faire sonner mon
téléphone" in my french version)
OBSERVED RESULT
sometimes, there is a very short sound (0.5 sec), sometimes there is nothing.
If you unfold the phone, it rings !
EXPECTED RESULT
The device should ring even when it is closed. (and optionally : display the
"found" screen on the external screen)
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: debian 12.6
KDE Plasma Version: 5.103.0
KDE Frameworks Version:
Qt Version: 5.15.8
ADDITIONAL INFORMATION
using KdeConnect 1.32.9 from F-Droid
--
You are receiving this mail because:
You are watching all bug changes.
[kxkb] [Bug 295438] Keyboard layout switcher stops working
https://bugs.kde.org/show_bug.cgi?id=295438 Thierry Göckel changed: What|Removed |Added CC|thie...@strayrayday.lu | -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 457898] New: Assertion 'found' failed. with multiple thread
https://bugs.kde.org/show_bug.cgi?id=457898
Bug ID: 457898
Summary: Assertion 'found' failed. with multiple thread
Product: valgrind
Version: 3.19.0
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: helgrind
Assignee: jsew...@acm.org
Reporter: adrien.thie...@gmail.com
Target Milestone: ---
SUMMARY
Helgrind reports an error in the very simple code below:
STEPS TO REPRODUCE
In any .c file:
#include
#include
#include
#include
void*routine(void *nop)
{
usleep(1);
return (nop);
}
int main(void)
{
int i;
int max;
pthread_t *threads;
i = 0;
max = 5;
threads = malloc(sizeof(*threads) * max);
while (i < max)
if (pthread_create((threads + i++), NULL, &routine, NULL))
exit (1);
i = 0;
while (i < max)
if (pthread_join(*(threads + i++), NULL))
exit (2);
free(threads);
return (0);
}
OBSERVED RESULT
==3537== Helgrind, a thread error detector
==3537== Copyright (C) 2007-2017, and GNU GPL'd, by OpenWorks LLP et al.
==3537== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==3537== Command: ./a.out
==3537==
Helgrind: hg_main.c:5379 (hg_handle_client_request): Assertion 'found' failed.
host stacktrace:
==3537==at 0x58026BCA: ??? (in /usr/lib/valgrind/helgrind-amd64-linux)
==3537==by 0x58026CF7: ??? (in /usr/lib/valgrind/helgrind-amd64-linux)
==3537==by 0x58026E9B: ??? (in /usr/lib/valgrind/helgrind-amd64-linux)
==3537==by 0x5801014A: ??? (in /usr/lib/valgrind/helgrind-amd64-linux)
==3537==by 0x5803B454: ??? (in /usr/lib/valgrind/helgrind-amd64-linux)
==3537==by 0x58082CC7: ??? (in /usr/lib/valgrind/helgrind-amd64-linux)
==3537==by 0x580C97C0: ??? (in /usr/lib/valgrind/helgrind-amd64-linux)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 3537)
==3537==at 0x484A943: ??? (in
/usr/lib/valgrind/vgpreload_helgrind-amd64-linux.so)
==3537==by 0x10924D: main (in /home/adrien/Prog/philosophers/a.out)
client stack range: [0x1FFEFFE000 0x1FFF000FFF] client SP: 0x1FFF000390
valgrind stack range: [0x1002E8E000 0x1002F8DFFF] top usage: 8880 of 1048576
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using. Thanks.
EXPECTED RESULT
No errors
SOFTWARE/OS VERSIONS
Tested on several systems (Ubuntu20.04 and arch)
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 457898] Assertion 'found' failed. with multiple thread
https://bugs.kde.org/show_bug.cgi?id=457898 adrien thierry changed: What|Removed |Added CC||adrien.thie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 457898] Multiple threads: Assertion 'found' failed.
https://bugs.kde.org/show_bug.cgi?id=457898 adrien thierry changed: What|Removed |Added Summary|Assertion 'found' failed. |Multiple threads: Assertion |with multiple thread|'found' failed. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 479548] New: Problem with key 6
https://bugs.kde.org/show_bug.cgi?id=479548 Bug ID: 479548 Summary: Problem with key 6 Classification: Applications Product: kcalc Version: 23.08.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ete...@alum.rit.edu Reporter: tgra...@free.fr Target Milestone: --- I am running Fedora 39 / KDE on a Framework 13 AMD 7640 laptop computer. Internal keyboard : US international When I use the Kcalc program or the taskbar applet, I can type any number on the keyboard but the 6 key is not working. The 6 key is working without issue in any other program (Libreoffice, Speedcrunch calculator, terminal...). If I use an USB keyboard, there is no problem with the 6 key on this external keyboard. STEPS TO REPRODUCE 1. Open Kcalc 2. Type the 6 key on a framework laptop (other laptop ?) 3. Type any other key 4. Type the 6 key in any other program 5. Type the 6 key in Kcalc using a USB keyboard OBSERVED RESULT 6 key is not registered when using the internal keyboard in Kcalc 6 key registered when using an USB keyboard in Kcalc 6 key registered in any other program using the internal keyboard Any other key of the internal keyboard in kcalc is working (1,2,3,4,5,7,8,9,0) EXPECTED RESULT 6 key must work using the internal keyboard of the laptop in Kcalc SOFTWARE/OS VERSIONS linux 6.6.9-200.fc39.x86_64 (64-bit) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Wayland Open the issue as well in the Framework forum here: https://community.frame.work/t/responded-kde-plasma-kcalc-calculator-problem-with-6-key/43195 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 479548] Problem with key 6
https://bugs.kde.org/show_bug.cgi?id=479548 --- Comment #1 from Thierry GRAUSS --- The problem was with deadkeys keymap. When using french qwerty with deadkey keymap, I have this behavior. If I select US international with Altgr deadkey I don't have any problem anymore. I had the problem with Kcalc but also with Signal and Smarthome3D. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464344] New: "Replica of" not linked to actual configuration
https://bugs.kde.org/show_bug.cgi?id=464344 Bug ID: 464344 Summary: "Replica of" not linked to actual configuration Classification: Applications Product: systemsettings Version: 5.20.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: pie...@nothos.net CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Plug second screen, make it not a replica of primary screen 2. Run qonk game, switch to full screen, then back to windowed 3. Go to system settings > Display and monitors OBSERVED RESULT The second screen is now a replica of the primary, but in the second screen's config, "Replica of" is set to "None". Setting it to primary screen then back to "None" doesn't change what's on the second screen. EXPECTED RESULT "Replica of" should be the primary screen. Setting it to "None" stops mirroring. The following command stops the mirroring: $ xrandr --output $SECOND --auto --right-of $PRIMARY 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.
[clazy] [Bug 431186] QAbstractItemView::entered not recognized as a signal [clazy-connect-non-signal]
https://bugs.kde.org/show_bug.cgi?id=431186 Thierry Bastian changed: What|Removed |Added CC||thier...@filewave.com --- Comment #19 from Thierry Bastian --- I tried with 1.8 on my MacOS (built it myself) and it worked (as it did with Qt creator 4.13 before). No warnings. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 431186] QAbstractItemView::entered not recognized as a signal [clazy-connect-non-signal]
https://bugs.kde.org/show_bug.cgi?id=431186 --- Comment #20 from Thierry Bastian --- interestingly, I tried clay 1.9 that I built myself and it is also fine... -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 431186] QAbstractItemView::entered not recognized as a signal [clazy-connect-non-signal]
https://bugs.kde.org/show_bug.cgi?id=431186 --- Comment #21 from Thierry Bastian --- hmm I tried again and now I'm getting those warnings. There must be something in the environment somewhere that is making a difference. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423496] New: Missing blend modes in layer style effect
https://bugs.kde.org/show_bug.cgi?id=423496 Bug ID: 423496 Summary: Missing blend modes in layer style effect Product: krita Version: 4.3.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: layer styles Assignee: krita-bugs-n...@kde.org Reporter: defresne.thie...@gmail.com Target Milestone: --- Some blend modes are missing since 4.3.0 in "layer style effects". Reproduce: 1. In a new document, add Layer styles to a layer 2. Select effect "Color Overlay" 3. Click the "Blend mode" dropdown Observed: Some blend mode (such as "Erase") are missing Expected: Erase mode is available and selectable Krita Version: 4.3.0 Languages: en_US, en Hidpi: true Qt Version (compiled): 5.15.0 Version (loaded): 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423572] Krita crash sometime when opening brush settings
https://bugs.kde.org/show_bug.cgi?id=423572 Defresne Thierry changed: What|Removed |Added Summary|Krita crash someting when |Krita crash sometime when |opening brush settings |opening brush settings -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423572] New: Krita crash someting when opening brush settings
https://bugs.kde.org/show_bug.cgi?id=423572 Bug ID: 423572 Summary: Krita crash someting when opening brush settings Product: krita Version: 4.3.0 Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: defresne.thie...@gmail.com Target Milestone: --- SUMMARY Sometimes Krita crash when opening the brush panel settings. It may happen in various situations and there are no easy step to reproduce. It crash more often when the brush use a custom brush tip. Happens in both 4.3.0 from package manager (pacman/archlinux), 4.3.0 appimage and krita-5.0.0-prealpha-689fe92-x86_64 appimage STEPS TO REPRODUCE 1. Select a brush 2. Open brush settings 3. Select a custom brush tip 4. Close brush settings 5. Draw on the canvas 6. Open brush settings 7. Change any settings (I personally change flow and rotation) 8. Close brush settings 9. Repeat 6 to 8 until krita crash OBSERVED RESULT Krita crash EXPECTED RESULT Open brush settings panel SOFTWARE/OS VERSIONS Krita log: SESSION: 27 Jun 2020 08:55:31 +0200. Executing /usr/bin/krita Krita Version: 4.3.0, Qt version compiled: 5.15.0, loaded: 5.15.0. Process ID: 8488 -- -- -- -- -- -- -- -- 27 Jun 2020 08:55:31 +0200: Style: breeze. Available styles: Breeze, Windows, Fusion 27 Jun 2020 08:56:34 +0200: Importing application/x-krita to application/x-krita. Location: /home/vxdcxw/Atelier/Graphisme/Exercices/Etudes/thumbnails/city.kra. Real location: /home/vxdcxw/Atelier/Graphisme/Exercices/Etudes/thumbnails/city.kra. Batchmode: 0 27 Jun 2020 08:56:34 +0200: Loaded image from application/x-krita. Size: 3000 * 1600 pixels, 8.3 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 8 27 Jun 2020 08:59:36 +0200: Saving Document /home/vxdcxw/Atelier/Graphisme/Exercices/Etudes/thumbnails/city.kra as /home/vxdcxw/Atelier/Graphisme/Exercices/Etudes/thumbnails/city.kra (mime: application/x-krita). 3000 * 1600 pixels, 9 layers. 101 frames, 24 framerate. Export configuration: No configuration 27 Jun 2020 08:59:36 +0200: Create a simple backup for /home/vxdcxw/Atelier/Graphisme/Exercices/Etudes/thumbnails/city.kra in the same location as the file. 27 Jun 2020 08:59:36 +0200: Converting from application/x-krita to application/x-krita. Location: /home/vxdcxw/Atelier/Graphisme/Exercices/Etudes/thumbnails/city.kra. Real location: /home/vxdcxw/Atelier/Graphisme/Exercices/Etudes/thumbnails/city.kra. Batchmode: 0. Configuration: none 27 Jun 2020 08:59:37 +0200: Completed saving /home/vxdcxw/Atelier/Graphisme/Exercices/Etudes/thumbnails/city.kra (mime: application/x-krita). Result: OK. Size: 7224570. MD5 Hash: 2be3f89a8909a1c5cbf2bee5f4740a08 27 Jun 2020 08:59:37 +0200: Saving Completed KRITA DID NOT CLOSE CORRECTLY SESSION: 27 Jun 2020 08:59:46 +0200. Executing /usr/bin/krita Krita Version: 4.3.0, Qt version compiled: 5.15.0, loaded: 5.15.0. Process ID: 9613 -- -- -- -- -- -- -- -- 27 Jun 2020 08:59:46 +0200: Style: breeze. Available styles: Breeze, Windows, Fusion ADDITIONAL INFORMATION backtrace from gdb: [Switching to Thread 0x7fffddfa8700 (LWP 47033)] 0x7242054e in __memmove_avx_unaligned_erms () from /usr/lib/libc.so.6 (gdb) thread apply all bt Thread 56 (Thread 0x7fff5dffb700 (LWP 47119)): #0 0x71cf8158 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x72891ce8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7288ffd4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7288be0f in ?? () from /usr/lib/libQt5Core.so.5 #4 0x71cf1422 in start_thread () from /usr/lib/libpthread.so.0 #5 0x723babf3 in clone () from /usr/lib/libc.so.6 Thread 55 (Thread 0x7fff5e7fc700 (LWP 47118)): #0 0x71cf8158 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x72891ce8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7288ffd4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7288be0f in ?? () from /usr/lib/libQt5Core.so.5 #4 0x71cf1422 in start_thread () from /usr/lib/libpthread.so.0 #5 0x723babf3 in clone () from /usr/lib/libc.so.6 Thread 54 (Thread 0x7fff5effd700 (LWP 47117)): #0 0x71cf8158 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x72891ce8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7288ffd4 in ?? () from /usr/lib/libQt5Core.so.5 #3 0x7288be0f in ?? () from /usr/lib/libQt5Core.so.5 #4 0x71cf1422 in start_thread () from /usr/lib/libpthread.so.0 #5 0x723babf3 in clone () from /usr/lib/libc.so.6 Thread 53 (Thread 0x7f
[krita] [Bug 423572] Krita crash sometime when opening brush settings
https://bugs.kde.org/show_bug.cgi?id=423572 --- Comment #1 from Defresne Thierry --- A more helpful backtrace: Thread 1 "krita" received signal SIGSEGV, Segmentation fault. 0x72da8911 in __memset_avx2_erms () from /usr/lib/libc.so.6 (gdb) thread apply 1 bt Thread 1 (Thread 0x7fffef50e880 (LWP 127540)): #0 0x72da8911 in __memset_avx2_erms () from /usr/lib/libc.so.6 #1 0x76061966 in KisFixedPaintDevice::initialize (this=0x621d1840, defaultValue=defaultValue@entry=0 '\000') at /usr/include/qt/QtCore/qrect.h:269 #2 0x7622e847 in KisAutoBrush::createBrushPreview (this=0x6060dcf0) at /home/vxdcxw/kritadev/krita/libs/global/kis_shared_ptr.h:179 #3 0x7622f387 in KisAutoBrush::KisAutoBrush (this=0x6060dcf0, as=0x7fffcb10, angle=0, randomness=0, density=1) at /home/vxdcxw/kritadev/krita/libs/brush/kis_auto_brush.cpp:93 #4 0x7624802e in KisAutoBrushFactory::createBrush (this=, brushDefinition=..., resourcesInterface=...) at /home/vxdcxw/kritadev/krita/libs/brush/kis_auto_brush_factory.cpp:41 #5 0x76233890 in KisBrushRegistry::createBrush (this=0x7625a220 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, element=..., resourcesInterface=...) at /usr/include/c++/10.1.0/bits/atomic_base.h:325 #6 0x76231af6 in KisBrush::fromXML (element=..., resourcesInterface=...) at /usr/include/c++/10.1.0/bits/atomic_base.h:325 #7 0x7fffdff87042 in KisBrushOptionProperties::readOptionSettingResourceImpl (this=0x7fffcdd0, setting=, resourcesInterface=...) at /usr/include/c++/10.1.0/bits/atomic_base.h:325 #8 0x76f1b1f5 in KisPaintopPropertiesResourcesBase::readOptionSetting (this=, settings=..., resourcesInterface=...) at /usr/include/qt/QtCore/qsharedpointer_impl.h:158 #9 0x7fffdffc1478 in KisMaskingBrushOptionProperties::read (this=this@entry=0x7fffce40, setting=0x664a9b50, masterBrushSize=583, resourcesInterface=...) at /usr/include/c++/10.1.0/bits/atomic_base.h:325 #10 0x7fffdffc021f in KisMaskingBrushOption::readOptionSetting (this=0x64364630, setting=...) at /home/vxdcxw/kritadev/krita/libs/global/kis_shared_ptr.h:155 #11 0x76fa23f4 in KisPaintOpOption::startReadOptionSetting (this=this@entry=0x64364630, setting=...) at /home/vxdcxw/kritadev/krita/libs/ui/kis_paintop_option.cpp:75 #12 0x76fa51ae in KisPaintOpSettingsWidget::setConfiguration (this=0x64247b30, config=...) at /usr/include/c++/10.1.0/bits/atomic_base.h:325 #13 0x75f288a0 in KisPaintOpConfigWidget::setConfigurationSafe (this=this@entry=0x64247b30, config=...) at /usr/include/c++/10.1.0/bits/atomic_base.h:325 #14 0x76f94884 in KisPaintopBox::slotUpdateOptionsWidgetPopup (this=0x5983acc0) at /usr/include/c++/10.1.0/bits/atomic_base.h:325 #15 0x7342f940 in ?? () from /usr/lib/libQt5Core.so.5 #16 0x73f10c7e in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #17 0x73ecf702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #18 0x77123c29 in KisApplication::notify (this=, receiver=0x5a62f990, event=0x7fffd2e0) at /home/vxdcxw/kritadev/krita/libs/ui/KisApplication.cpp:736 #19 0x733f869a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #20 0x73f0d4c8 in QWidgetPrivate::show_helper() () from /usr/lib/libQt5Widgets.so.5 #21 0x73f0d41a in QWidgetPrivate::showChildren(bool) () from /usr/lib/libQt5Widgets.so.5 #22 0x73f0d4a2 in QWidgetPrivate::show_helper() () from /usr/lib/libQt5Widgets.so.5 #23 0x73f107d5 in QWidgetPrivate::setVisible(bool) () from /usr/lib/libQt5Widgets.so.5 #24 0x7559a5f9 in KisPopupButton::showPopupWidget (this=0x589b6390) at /usr/include/qt/QtCore/qscopedpointer.h:116 #25 0x7342f940 in ?? () from /usr/lib/libQt5Core.so.5 #26 0x73fc196f in ?? () from /usr/lib/libQt5Widgets.so.5 #27 0x73fc2e93 in ?? () from /usr/lib/libQt5Widgets.so.5 #28 0x73fc3093 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5Widgets.so.5 #29 0x73f10c7e in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #30 0x73ecf702 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #31 0x73ed6977 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #32 0x77123c29 in KisApplication::notify (this=, receiver=0x589b6390, event=0x7fffdba0) at /home/vxdcxw/kritadev/krita/libs/ui/KisApplication.cpp:736 #33 0x733f869a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #34 0x73ed585e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /usr/lib/libQt5Widgets.so.5 #35 0x73f293b2 in ?? () from /
[krita] [Bug 423572] Krita crash sometime when opening brush settings
https://bugs.kde.org/show_bug.cgi?id=423572 --- Comment #2 from Defresne Thierry --- Created attachment 129721 --> https://bugs.kde.org/attachment.cgi?id=129721&action=edit patch I have found a way to fix the bug however I lack the expertise to debug it further. I hope this will help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 423572] Krita crash sometime when opening brush settings
https://bugs.kde.org/show_bug.cgi?id=423572 --- Comment #3 from Defresne Thierry --- Created attachment 129739 --> https://bugs.kde.org/attachment.cgi?id=129739&action=edit masking brush overflow fix I achieved to find the root cause of the problem and a way to solve it. This fix may also improve performances for peoples experiencing custom brush/slow brush window issues. I attached a diff file with the fix. However this is my first patch and I'm not very comfortable with Krita dev right now. So the solution is using a hardcoded value for the max size instead of fetching it from user settings. I hope this will help to solve the bug. Origin of the crash: an overflow happens in the brush preview device because it tries to allocate an invalid QRect with huge height/width. The problem: masked brush tip size is soft-locked but it can overflow UI limitation because it is bound to base brush tip size (related to `KisMaskingBrushOption::MasterBrushSizeAdapter`). This will happen even if the masked brush option is disabled. The root cause: The masked brush size value is not clamped into the range [O, Settings.maxBrushSize], this result in huge allocations when the brush window tries to create the device for the brush preview. A better way to Reproduce the bug: 1. Open a file 2. Create a new brush from Pixel Engine 3. Set its size to 1 4. Set masked brush tip size to 1000 5. Close the brush settings window 6. Change the brush size to something big (100 is enough on my computer) 7. Open the brush settings window 8. Crash -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 493255] New: plasma-browser-integration-host when searching in Application Launcher
https://bugs.kde.org/show_bug.cgi?id=493255 Bug ID: 493255 Summary: plasma-browser-integration-host when searching in Application Launcher Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: defresne.thie...@gmail.com Target Milestone: --- Created attachment 173763 --> https://bugs.kde.org/attachment.cgi?id=173763&action=edit backtrace SUMMARY When I search for some files in Application Launcher, a crash report is generated STEPS TO REPRODUCE 1. Open Application Launcher 2. Start to type some letters in the "Search..." field 3. Try different combinations OBSERVED RESULT Tens of crash alerts appears in the notification bar EXPECTED RESULT No crash SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.9-arch1-2 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 9900X 12-Core Processor Memory: 62.4 GiB of RAM Graphics Processor: AMD Radeon RX 7800 XT -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 493255] plasma-browser-integration-host when searching in Application Launcher
https://bugs.kde.org/show_bug.cgi?id=493255 --- Comment #2 from Defresne Thierry --- (In reply to cwo from comment #1) > Thank you for the bug report! This issue has already been filed; please > follow the linked bug report for updates on a fix. > > *** This bug has been marked as a duplicate of bug 490068 *** Thx! I forgot I installed Firefox Plasma Integration, disabling it for now -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 490068] Plasma browser integration keeps crashing
https://bugs.kde.org/show_bug.cgi?id=490068 --- Comment #6 from Defresne Thierry --- Confirm the bug too. I disabled Firefox Plasma Integration until a fix is ready -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 413484] New: Tablet device missing (Cintiq Pro 13 Touch Finger touch)
https://bugs.kde.org/show_bug.cgi?id=413484 Bug ID: 413484 Summary: Tablet device missing (Cintiq Pro 13 Touch Finger touch) Product: wacomtablet Version: 3.2.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jazzv...@gmail.com Reporter: defresne.thie...@gmail.com Target Milestone: --- SUMMARY The device for Cintiq Pro 13 Touch is missing, it can be enabled by restarting Wacom Tablet service. STEPS TO REPRODUCE 1. Plug-in Cintiq Pro 13 2. Run `kcmshell5 kcm_wacomtablet` 3. The touch module of the tablet is missing in the drop-down `Select Tablet` SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.17.1 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION `~/.config/tabletdblocalrc` (culprit is *0353*): ``` [034F] layout=unknown model=unknown name=Wacom Cintiq Pro 13 Pen padbuttons=0 statusleds=0 touchring=false touchstripl=false touchstripr=false wheel=false [0353] layout=unknown model=unknown name=Wacom Cintiq Pro 13 Touch Finger touch padbuttons=0 statusleds=0 touchring=false touchstripl=false touchstripr=false wheel=false ``` -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416374] Crash when changing opacity after closing brush settings window
https://bugs.kde.org/show_bug.cgi?id=416374 Defresne Thierry changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Defresne Thierry --- (In reply to Boudewijn Rempt from comment #5) > I think I might have the reason why this happens for you, but not for other > people. You're using Arch Linux with the Arch package of Krita, and somehow > Krita didn't get recompiled when Qt got updated: > > Version (compiled): 5.13.2 > Version (loaded): 5.14.0 > > The crash itself happens when we execute an avx2 instruction: > > #6 0x7f913e272b51 in __memset_avx2_erms () from /usr/lib/libc.so.6 > > If we get a crash in that, that also looks like a build problem. > > If you use the appimage, do you get these crashes? (Note that you need to > remove the distribution Krita first) > > And if you then ask Arch to rebuild all of Krita, do you get these crashes? You're certainly right. I updated my system and Krita recently and I couldn't reproduce the bug. Compiled/Loaded version of Qt are on the same minor version now. Krita Version: 4.2.9, Qt version compiled: 5.14.1, loaded: 5.14.2. Process ID: 1741 I remember the crash happened with the appimage too but I havn't removed Krita from the system before. I didn't tried to rebuild all of Krita neither. Now that I have updated my system, it would be hard to make the test. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416374] New: Crash when changing opacity after closing brush settings window
https://bugs.kde.org/show_bug.cgi?id=416374 Bug ID: 416374 Summary: Crash when changing opacity after closing brush settings window Product: krita Version: 4.2.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: defresne.thie...@gmail.com Target Milestone: --- Application: krita (4.2.8) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.12-arch1-1 x86_64 Distribution: Arch Linux -- Information about the crash: - What I was doing when the application crashed: Changed brush opacity from toolbar Reproduce: - select any brush - open brush settings window - change any setting - click on canvas to close brush settings window - change opacity Tested with appimage too. The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9138b53800 (LWP 1430))] Thread 22 (Thread 0x7f90e5ffc700 (LWP 1521)): #0 0x7f913c30cf7a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f913e5a8c48 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f913e5a8d69 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f913e5a63dd in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f913e5a2fd6 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f913c3064cf in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f913e20d2d3 in clone () from /usr/lib/libc.so.6 Thread 21 (Thread 0x7f90e67fd700 (LWP 1520)): #0 0x7f913c30cf7a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f913e5a8c48 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f913e5a8d69 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f913e5a63dd in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f913e5a2fd6 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f913c3064cf in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f913e20d2d3 in clone () from /usr/lib/libc.so.6 Thread 20 (Thread 0x7f90f8ff9700 (LWP 1519)): #0 0x7f913c30cf7a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f913e5a8c48 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f913e5a8d69 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f913e5a63dd in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f913e5a2fd6 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f913c3064cf in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f913e20d2d3 in clone () from /usr/lib/libc.so.6 Thread 19 (Thread 0x7f90f97fa700 (LWP 1518)): #0 0x7f913c30cf7a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f913e5a8c48 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f913e5a8d69 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f913e5a63dd in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f913e5a2fd6 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f913c3064cf in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f913e20d2d3 in clone () from /usr/lib/libc.so.6 Thread 18 (Thread 0x7f90e4ffa700 (LWP 1517)): #0 0x7f913c30cf7a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f913e5a8c48 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f913e5a8d69 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f913e5a63dd in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f913e5a2fd6 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f913c3064cf in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f913e20d2d3 in clone () from /usr/lib/libc.so.6 Thread 17 (Thread 0x7f90e57fb700 (LWP 1516)): #0 0x7f913c30cf7a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f913e5a8c48 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /usr/lib/libQt5Core.so.5 #2 0x7f913e5a8d69 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f913e5a63dd in ?? () from /usr/lib/libQt5Core.so.5 #4 0x7f913e5a2fd6 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f913c3064cf in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f913e20d2d3 in clone () from /usr/lib/libc.so.6 Thread 16 (Thread 0x7f90e77ff700 (LWP 1515)): #0 0x7f913c30cf7a in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x
[krita] [Bug 416374] Crash when changing opacity after closing brush settings window
https://bugs.kde.org/show_bug.cgi?id=416374 --- Comment #1 from Defresne Thierry --- It happens 100% of time when brush size is > 500px. Doing this with a smaller brush won't crash but instead any change to brush settings (from brush settings window or toolbar) will be very slow. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416374] Crash when changing opacity after closing brush settings window
https://bugs.kde.org/show_bug.cgi?id=416374 --- Comment #2 from Defresne Thierry --- I have some more informations on this bug, it looks like the brush presets gets corrupted in some way after multiple overwrites: - open Krita - create a new document - select "b)_Basic-2_Opacity" brush preset - in brush settings window save to a new brush preset - select the new brush preset - open brush settings window - change diameter, overwrite brush settings - repeat last operation many times (on my computer it take 12 times) - leave brush settings window - set brush size to 1000px - open brush settings window - set brush size to 999px - leave brush settings window - change opacity from toolbar Hope this will help -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 416374] Crash when changing opacity after closing brush settings window
https://bugs.kde.org/show_bug.cgi?id=416374 --- Comment #4 from Defresne Thierry --- Created attachment 125255 --> https://bugs.kde.org/attachment.cgi?id=125255&action=edit Bug report Sure, here is the bug report. I had to overwrite the brush almost 50 times today to reproduce the bug (the computer is freshly started, it may do the difference). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415090] New: Krita crash after selecting "Transform" tool when selection or layer is empty
https://bugs.kde.org/show_bug.cgi?id=415090 Bug ID: 415090 Summary: Krita crash after selecting "Transform" tool when selection or layer is empty Product: krita Version: 4.2.8 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Tools/Transform Assignee: krita-bugs-n...@kde.org Reporter: defresne.thie...@gmail.com Target Milestone: --- Created attachment 124443 --> https://bugs.kde.org/attachment.cgi?id=124443&action=edit Session + lldb reports SUMMARY Krita will crash if there is no pixel available on layer or within selection. STEPS TO REPRODUCE 1. Create a new document 2. Change active tool to "Transform tool" Alternative: 1. Create a new document 2. Draw pixels on the layer 3. Make an empty selection 4. Change active tool to "Transform tool" OBSERVED RESULT Krita crash and closes EXPECTED RESULT Change active tool to "Transform tool" without crash SOFTWARE/OS VERSIONS Krita: Version: 4.2.8 Languages: en_US Hidpi: true Qt: Version (compiled): 5.13.2 Version (loaded): 5.13.2 ADDITIONAL INFORMATION Session + lldb reports as attachments -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 415090] Krita crash after selecting "Transform" tool when selection or layer is empty
https://bugs.kde.org/show_bug.cgi?id=415090 --- Comment #2 from Defresne Thierry --- (In reply to Tymond from comment #1) > It doesn't happen in the appimage (because it's actually an assert, not a > crash), so you can use it in the meantime. > > *** This bug has been marked as a duplicate of bug 414672 *** Great, thank you ! -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393309] New: Error message: R engine has died
https://bugs.kde.org/show_bug.cgi?id=393309 Bug ID: 393309 Summary: Error message: R engine has died Product: rkward Version: unspecified Platform: FreeBSD Ports OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: rkward-de...@kde.org Reporter: thie...@freebsd.org Target Milestone: --- ---Problem description--- I'm trying to upgrade the FreeBSD port of RKWard to 0.7.0b. No problem during compilation, but when I launch rkward, the message "R engine has died" is displayed, and the application is not usable. When you try to repeat the above, does the problem occur again (no, sometimes, always)? Always If applicable: When doing the same thing in an R session outside of RKWard, do you see the same problem? No, R sessions are OK. Do you have any further information that might help us to track this problem down? In particular, if applicable, can you provide sample data and sample R code to reproduce this problem? No code used, it's just at the beginning. RKWard is available in many different packagings, and sometimes problems are specific to one method of installation. How did you install RKWard (which file(s) did you download)? Built with cmake. Important note: R version is 3.4.4 (2018-03-15) -- "Someone to Lean On" Is it supported by RKWard? ---Error Message--- Message code: r_engine_has_died The backend executable could not be found. This is likely to be a problem with your installation. The R backend will be shut down immediately. This means, you can not use any more functions that rely on it. I.e. you can do hardly anything at all, not even save the workspace (but if you're lucky, R already did that). What you can do, however, is save any open command-files, the output, or copy data out of open data editors. Quit RKWard after that. Sorry! ---Session Info--- RKWard version: 0.7.0b KDE Frameworks version (runtime): 5.44.0 KDE Frameworks version (compile time): 5.44.0 Qt version (runtime): 5.9.4 Local config directory: /home/thierry/.config RKWard storage directory: /home/thierry/.rkward/ Backend version (as known to the frontend): Debug message file (this may contain relevant diagnostic output in case of trouble): /tmp/rkward.frontend - backend not available or rk.sessionInfo() canceled - -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 393309] Error message: R engine has died
https://bugs.kde.org/show_bug.cgi?id=393309 --- Comment #3 from Thierry Thomas --- My bad! It was caused by an old patch, previously used to fix the detection of the backend under $PREFIX/lib/kde4/libexec/. Thanks for your quick help. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 376999] New: Muon searchbox not working
https://bugs.kde.org/show_bug.cgi?id=376999 Bug ID: 376999 Summary: Muon searchbox not working Product: muon Version: 5.6 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: muon Assignee: echidna...@kubuntu.org Reporter: alex.thie...@openmailbox.org CC: silh...@gmail.com Target Milestone: --- Only works for one research. After that, whatever I'm looking for, entering the name won't return any result. Need to exit the app and launch it again. Synaptic working fine anyway. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 490068] Plasma browser integration keeps crashing
https://bugs.kde.org/show_bug.cgi?id=490068 Defresne Thierry changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #9 from Defresne Thierry --- (In reply to postix from comment #7) > Since it crashes in ` TaskManager::WindowTasksModel::~WindowTasksModel()` it > sounds like a dup of #488653, which is fixed in 6.2.0 > Can anyone confirm? I just updated to 6.2.0 and I can confirm it doesn't happen anymore Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358133] KWin Crashed After Resuming from Idle
https://bugs.kde.org/show_bug.cgi?id=358133 --- Comment #11 from Thierry --- Hi Thomas! Big update yesterday including the Nvidia drivers on openSUSE 42.1 Leap. What gives me as config: KDE Plasma: 5.6.4 KDE Frameworks: 5.22.0 Qt: 5.6.0 Kernel: 4.1.21-14-default Nvidia driver: 367.18 I can not reproduce the bug despite a dozen tests. The old version of the driver is, for me, the cause of the problems. Thank you for your help and consideration bug! Cordially -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364420] New: kwin crashed
https://bugs.kde.org/show_bug.cgi?id=364420 Bug ID: 364420 Summary: kwin crashed Product: kwin Version: 5.6.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: thn...@gmail.com Application: kwin_x11 (5.6.4) Qt Version: 5.6.1 Frameworks Version: 5.23.0 Operating System: Linux 4.1.21-14-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Back on the computer desktop after exiting a 3D application full screen. Similar to bug : https://bugs.kde.org/show_bug.cgi?id=358133. But now: KDE Plasma : 5.6.4 KDE Frameworks : 5.23.0 Qt : 5.6.1 Nvidia: 367.27 The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0384b9b800 (LWP 5489))] Thread 6 (Thread 0x7f036a481700 (LWP 5499)): #0 0x7f0384514bbd in poll () at /lib64/libc.so.6 #1 0x7f0381e3f422 in () at /usr/lib64/libxcb.so.1 #2 0x7f0381e4100f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f036b358579 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f0382103a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f0383b2f0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f038451cfed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f0363fff700 (LWP 5504)): #0 0x7f0384516253 in select () at /lib64/libc.so.6 #1 0x7f0382312839 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f0382314105 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f0382314547 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f03822c3fcb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f03820fef5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f037b128225 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f0382103a29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f0383b2f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f038451cfed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f03623ab700 (LWP 5516)): #0 0x7f0384516253 in select () at /lib64/libc.so.6 #1 0x7f0382312839 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f0382314105 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f0382314547 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f03822c3fcb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f03820fef5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f037c1a1b88 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f0382103a29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f0383b2f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f038451cfed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f034a82a700 (LWP 5547)): #0 0x7f0383b3303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f038107a97b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f038107a9a9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f0383b2f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f038451cfed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f0360e64700 (LWP 15854)): #0 0x7f0383b3303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f038210469b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f037c87654b in () at /usr/lib64/libQt5Quick.so.5 #3 0x7f037c8769f5 in () at /usr/lib64/libQt5Quick.so.5 #4 0x7f0382103a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f0383b2f0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f038451cfed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f0384b9b800 (LWP 5489)): [KCrash Handler] #6 0x7f03844c7d79 in __memcpy_sse2_unaligned () at /lib64/libc.so.6 #7 0x7f037cff7643 in KWin::GLVertexBuffer::setData(int, int, float const*, float const*) () at /usr/lib64/libkwinglutils.so.8 #8 0x7f03840e4bde in () at /usr/lib64/libkwin.so.5 #9 0x7f03840eace5 in () at /usr/lib64/libkwin.so.5 #10 0x7f03840d73ce in () at /usr/lib64/libkwin.so.5 #11 0x7f03840e46d3 in () at /usr/lib64/libkwin.so.5 #12 0x7f03840d86c5 in () at /usr/lib64/libkwin.so.5 #13 0x7f03840fada0 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwin.so.5 #14 0x7f038188a46f in KWin::Effect::paintScreen(int, QRegion, KWin::ScreenPaint
[kwin] [Bug 364420] kwin crashed
https://bugs.kde.org/show_bug.cgi?id=364420 --- Comment #2 from Thierry --- Hi Thomas! You may suppose! The application has changed the screen resolution. New update today Qt librariesand KDE Plasma and the incident does not recur this time. Continued ... however... Thank you for your prompt response! cordially Le 17/06/2016 16:26, Thomas Lübking via KDE Bugzilla a écrit : > https://bugs.kde.org/show_bug.cgi?id=364420 > > Thomas Lübking changed: > >What|Removed |Added > > Status|UNCONFIRMED |RESOLVED > Resolution|--- |DUPLICATE > > --- Comment #1 from Thomas Lübking --- > Yes, is bug #358133, so bug #355103 so ultimately probably bug #344326 > As mentioned "heuristic"... > > I assume the game changed the video resolution? (Or does it autosuspend the > compositor?) > > *** This bug has been marked as a duplicate of bug 355103 *** > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 364420] kwin crashed
https://bugs.kde.org/show_bug.cgi?id=364420 --- Comment #3 from Thierry --- Hi! The 3D application has changed the screen resolution. New update today Qt libraries and KDE Plasma and the incident does not recur this time. Now: - KDE Plasma : 5.6.9 - KDE Framworks : 5.23.0 - Qt :5.6.1 Continued ... however... Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 364764] New: Start of the session and error after closing ktorrent
https://bugs.kde.org/show_bug.cgi?id=364764 Bug ID: 364764 Summary: Start of the session and error after closing ktorrent Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: thn...@gmail.com Application: kglobalaccel5 (0.2) Qt Version: 5.6.1 Frameworks Version: 5.23.0 Operating System: Linux 4.1.26-21-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: At logon, ktorrent starts without being asked. When closing it (click on the window close button) the error is reported. Configuration: KDE Plasma: 5.6.90 KDE Frameworks: 5.23.0 Qt: 5.6.1 Kernel:4.1.26-21-default -- Backtrace: Application: KDE Global Shortcuts Service (kglobalaccel5), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2948d6b780 (LWP 1921))] Thread 3 (Thread 0x7f293b467700 (LWP 1925)): #0 0x7f29465e9bbd in poll () at /lib64/libc.so.6 #1 0x7f2942da8422 in () at /usr/lib64/libxcb.so.1 #2 0x7f2942daa00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f293dff2579 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f2946ce8a29 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f29454710a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f29465f1fed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f292d8fe700 (LWP 1929)): #0 0x7f29465fe56b in __lll_lock_wait_private () at /lib64/libc.so.6 #1 0x7f294658ab2a in _L_lock_10550 () at /lib64/libc.so.6 #2 0x7f2946588665 in malloc () at /lib64/libc.so.6 #3 0x7f2948b9b7ee in _dl_map_object_deps () at /lib64/ld-linux-x86-64.so.2 #4 0x7f2948ba193c in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #5 0x7f2948b9d7a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #6 0x7f2948ba12fb in _dl_open () at /lib64/ld-linux-x86-64.so.2 #7 0x7f29466273b2 in do_dlopen () at /lib64/libc.so.6 #8 0x7f2948b9d7a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #9 0x7f294662744f in dlerror_run () at /lib64/libc.so.6 #10 0x7f29466274c1 in __libc_dlopen_mode () at /lib64/libc.so.6 #11 0x7f29465fee15 in init () at /lib64/libc.so.6 #12 0x7f2945476400 in pthread_once () at /lib64/libpthread.so.0 #13 0x7f29465fef2c in backtrace () at /lib64/libc.so.6 #14 0x7f294652cd52 in backtrace_and_maps () at /lib64/libc.so.6 #15 0x7f294657f75f in __libc_message () at /lib64/libc.so.6 #16 0x7f2946584fce in malloc_printerr () at /lib64/libc.so.6 #17 0x7f294658737b in _int_malloc () at /lib64/libc.so.6 #18 0x7f2946588670 in malloc () at /lib64/libc.so.6 #19 0x7f294206b4c0 in () at /usr/lib64/tls/libnvidia-tls.so.367.27 #20 0x7f2946ce9a2f in QArrayData::allocate(unsigned long, unsigned long, unsigned long, QFlags) () at /usr/lib64/libQt5Core.so.5 #21 0x7f2946d72563 in QString::QString(int, Qt::Initialization) () at /usr/lib64/libQt5Core.so.5 #22 0x7f2946f02517 in () at /usr/lib64/libQt5Core.so.5 #23 0x7f2946d78cae in QString::fromUtf8_helper(char const*, int) () at /usr/lib64/libQt5Core.so.5 #24 0x7f2945c6478e in () at /usr/lib64/libQt5DBus.so.5 #25 0x7f2945c6510c in () at /usr/lib64/libQt5DBus.so.5 #26 0x7f2945c3b16b in () at /usr/lib64/libQt5DBus.so.5 #27 0x7f2945c3378e in () at /usr/lib64/libQt5DBus.so.5 #28 0x7f2942fcd636 in dbus_connection_dispatch () at /lib64/libdbus-1.so.3 #29 0x7f2945c34cb1 in () at /usr/lib64/libQt5DBus.so.5 #30 0x7f2945c34fd9 in () at /usr/lib64/libQt5DBus.so.5 #31 0x7f2945c73c73 in () at /usr/lib64/libQt5DBus.so.5 #32 0x7f2946ed4ba1 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #33 0x7f2946f4e09e in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib64/libQt5Core.so.5 #34 0x7f2946ee1cc9 in QSocketNotifier::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #35 0x7f2946eaafe1 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #36 0x7f2946efc0fe in () at /usr/lib64/libQt5Core.so.5 #37 0x7f2944f54c84 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #38 0x7f2944f54ed8 in () at /usr/lib64/libglib-2.0.so.0 #39 0x7f2944f54f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #40 0x7f2946efb32c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #41 0x7f2946ea8fcb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #42 0x7f2946ce3f5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #43 0x7f2945c23225 in () at /usr/lib64/libQt5DBus.so.5 #44 0x7f2946ce8a29 in () at /usr/lib64/l
[frameworks-kglobalaccel] [Bug 364764] Start of the session and error after closing ktorrent
https://bugs.kde.org/show_bug.cgi?id=364764 --- Comment #2 from Thierry --- The bug does not play. Currently, only ktorrent launches the session start without having been requested but no error message appears when closing. I will retry several session restarts , and try to reproduce the error. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 363077] New: Kwin error
https://bugs.kde.org/show_bug.cgi?id=363077 Bug ID: 363077 Summary: Kwin error Product: kwin Version: 5.6.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: thn...@gmail.com Application: kwin_x11 (5.6.3) Qt Version: 5.6.0 Frameworks Version: 5.21.0 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: I left a 3d game in full screen. The bug occurs when returning to the kde desktop. It does not require logging off or restart. For information, kscreen service is disabled (ref. similar bugs #358133, #355103) The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8becb57840 (LWP 1931))] Thread 5 (Thread 0x7f8bd252c700 (LWP 1942)): #0 0x7f8bec4cebbd in poll () at /lib64/libc.so.6 #1 0x7f8be9e01422 in () at /usr/lib64/libxcb.so.1 #2 0x7f8be9e0300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f8bd3402d69 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f8bea0c5079 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f8bebae90a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7f8bec4d6fed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f8bcbfff700 (LWP 1944)): #0 0x7f8bec4d0253 in select () at /lib64/libc.so.6 #1 0x7f8bea2d28e9 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8bea2d41b5 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f8bea2d45f7 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8bea28404b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8bea0c05da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8be310d095 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f8bea0c5079 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f8bebae90a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8bec4d6fed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f8bca3ab700 (LWP 1953)): #0 0x7f8bec4d0253 in select () at /lib64/libc.so.6 #1 0x7f8bea2d28e9 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8bea2d41b5 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7f8bea2d45f7 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f8bea28404b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f8bea0c05da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f8be41864d8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f8bea0c5079 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f8bebae90a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f8bec4d6fed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f8bb282a700 (LWP 1993)): #0 0x7f8bebaed03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8be903b97b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f8be903b9a9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f8bebae90a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f8bec4d6fed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f8becb57840 (LWP 1931)): [KCrash Handler] #6 0x7f8bec481d79 in __memcpy_sse2_unaligned () at /lib64/libc.so.6 #7 0x7f8be51e3643 in KWin::GLVertexBuffer::setData(int, int, float const*, float const*) () at /usr/lib64/libkwinglutils.so.8 #8 0x7f8bec09e82e in () at /usr/lib64/libkwin.so.5 #9 0x7f8bec0a4935 in () at /usr/lib64/libkwin.so.5 #10 0x7f8bec09101e in () at /usr/lib64/libkwin.so.5 #11 0x7f8bec09e323 in () at /usr/lib64/libkwin.so.5 #12 0x7f8bec092315 in () at /usr/lib64/libkwin.so.5 #13 0x7f8bec0b49f0 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwin.so.5 #14 0x7f8be984c46f in KWin::Effect::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwineffects.so.8 #15 0x7f8bec0b49b0 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwin.so.5 #16 0x7f8be984c46f in KWin::Effect::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwineffects.so.8 #17 0x7f8bec0b49b0 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwin.so.5 #18 0x7f8be984c46f in KWin::Effect::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwineffects.so.8 #19
[kwin] [Bug 363077] Kwin error
https://bugs.kde.org/show_bug.cgi?id=363077 --- Comment #2 from Thierry --- Hi! Yes, the game changes the resolution. In 1920x1080, the screen changes to the resolution of 1280x1024. And vice versa when returning to the kde desktop! That's when I see the error. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358133] KWin Crashed After Resuming from Idle
https://bugs.kde.org/show_bug.cgi?id=358133 Thierry changed: What|Removed |Added CC||thn...@gmail.com --- Comment #4 from Thierry --- Hi! kwin is still crashes when I go to a full screen application. I think of a memory access problem ... Here is the error report: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fde967ed840 (LWP 9717))] Thread 5 (Thread 0x7fde7c1c2700 (LWP 9721)): #0 0x7fde96164bbd in poll () at /lib64/libc.so.6 #1 0x7fde93a97422 in () at /usr/lib64/libxcb.so.1 #2 0x7fde93a9900f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fde7d098d69 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fde93d5b079 in () at /usr/lib64/libQt5Core.so.5 #5 0x7fde9577f0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fde9616cfed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fde7a0b5700 (LWP 9728)): #0 0x7fde96166253 in select () at /lib64/libc.so.6 #1 0x7fde93f688e9 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fde93f6a1b5 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7fde93f6a5f7 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fde93f1a04b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fde93d565da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fde8cda3095 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7fde93d5b079 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fde9577f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fde9616cfed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fde6bfff700 (LWP 9730)): #0 0x7fde96166253 in select () at /lib64/libc.so.6 #1 0x7fde93f688e9 in qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) () at /usr/lib64/libQt5Core.so.5 #2 0x7fde93f6a1b5 in QEventDispatcherUNIXPrivate::doSelect(QFlags, timespec*) () at /usr/lib64/libQt5Core.so.5 #3 0x7fde93f6a5f7 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fde93f1a04b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fde93d565da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fde8de1c4d8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fde93d5b079 in () at /usr/lib64/libQt5Core.so.5 #8 0x7fde9577f0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fde9616cfed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7fde68ce0700 (LWP 9733)): #0 0x7fde9578303f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fde92cd197b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fde92cd19a9 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fde9577f0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fde9616cfed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fde967ed840 (LWP 9717)): [KCrash Handler] #6 0x7fde96117d79 in __memcpy_sse2_unaligned () at /lib64/libc.so.6 #7 0x7fde8ee79643 in KWin::GLVertexBuffer::setData(int, int, float const*, float const*) () at /usr/lib64/libkwinglutils.so.8 #8 0x7fde95d3482e in () at /usr/lib64/libkwin.so.5 #9 0x7fde95d3a935 in () at /usr/lib64/libkwin.so.5 #10 0x7fde95d2701e in () at /usr/lib64/libkwin.so.5 #11 0x7fde95d34323 in () at /usr/lib64/libkwin.so.5 #12 0x7fde95d28315 in () at /usr/lib64/libkwin.so.5 #13 0x7fde95d4a9f0 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwin.so.5 #14 0x7fde934e246f in KWin::Effect::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwineffects.so.8 #15 0x7fde95d4a9b0 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwin.so.5 #16 0x7fde934e246f in KWin::Effect::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwineffects.so.8 #17 0x7fde95d4a9b0 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwin.so.5 #18 0x7fde934e246f in KWin::Effect::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwineffects.so.8 #19 0x7fde95d4a9b0 in KWin::EffectsHandlerImpl::paintScreen(int, QRegion, KWin::ScreenPaintData&) () at /usr/lib64/libkwin.so.5 #20 0x7fde95d27fb8 in () at /usr/lib64/libkwin.so.5 #21 0x7fde95d3b4d4 in () at /usr/lib64/libkwin.so.5 #22 0x7fde95d1c588 in KWin::Compositor::performCompositing() () at /usr/lib64/libkwin.so.5 #23 0x7fde93f46fc4 in QObject::event(QEvent*)
[KScreen] [Bug 355396] dual monitor become single after reboot
https://bugs.kde.org/show_bug.cgi?id=355396 Thierry changed: What|Removed |Added CC||thn...@gmail.com --- Comment #4 from Thierry --- Hi! Same problem. The dual screen configuration is not preserved. Only disabling kscreen permits (System → Start and Stop Background Services → Service KScreen 2). My config: KDE Plasma: 5.6.3 KDE Frameworks: 5.21.0 Qt: 5.6.0 Kernel: 4.1.20-11-default Nvidia drivers: 361.42 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358133] KWin Crashed After Resuming from Idle
https://bugs.kde.org/show_bug.cgi?id=358133 --- Comment #6 from Thierry --- Hi! I performed the operation above. I hope it worked. Interestingly, I have no error with kwin since I disabled kscreen. I disabled kscreen because the double screen configuration was not retained. Would the two errors? Greetings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 358133] KWin Crashed After Resuming from Idle
https://bugs.kde.org/show_bug.cgi?id=358133 --- Comment #8 from Thierry --- Created attachment 98858 --> https://bugs.kde.org/attachment.cgi?id=98858&action=edit Additionnal information for bug kde#358133. Output file KWin supportInformation Hi! I put the output file attached to this message. Regards, -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 360755] New: Change of album artist field alone in single mp3 file has no impact
https://bugs.kde.org/show_bug.cgi?id=360755
Bug ID: 360755
Summary: Change of album artist field alone in single mp3 file
has no impact
Product: amarok
Version: 2.8.0
Platform: Ubuntu Packages
URL: http://imgur.com/6EBFmmF
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: Metadata Editing and Reading
Assignee: amarok-bugs-d...@kde.org
Reporter: climat...@gmail.com
CC: 123k...@gmail.com
I use amarok v. 2.8.0 compiled on Sep 25 2013, with Ubuntu 14.04 LTS, in a
french environment
I have an mp3 version of a chinese album with the metadata below.
_
titre/title : 怕
artiste/artist : 陳冠希 - Edison
compositeur/composer : empty
artiste de l'album/album artist: Edison
album: Please steal this album
Genre: Pop
Année/year: 2004
numéro de la piste/track number: 6
numéro du disque/disc number: 1
battements par minutes/beats per minutes: empty
commentaire/comment: 0
track location: /media/ferelden/musique5/gr52/06 怕.mp3
no lyrics/no cover album
_
I open the metadata editor for this single file
I copy the artist : "陳冠希 - Edison" and replace the field album artist with "陳冠希
- Edison"
The "save and close" button becomes available.
I click on it. I don't modify any other fields.
I see absolutely no change to my playlist ordering by Album, I which I have
first 5 tracks for the album artist "Edison", then 10 tracks for the album
artist "陳冠希 - Edison". I expect the track to move down and meet the other
tracks for the album artist "陳冠希 - Edison".
I delete my playlist and my search for the album name.
I update collection in tools/"Mettre à jour ma collection" (4th option out of
5)
I search again for the album, and drag all my tracks in the empty playlist
panel.
The track "怕" is still with the first 5 songs that have the album artist
"Edison"
When I open the metadata editor, no changes were made to the song. The album
artist is still "Edison".
Workaround:
I add a space (" ") at the end of track name and change the album artist field.
I click on button"save and close".
Hourray : the file is now with the tracks that have the album artist "陳冠希 -
Edison"
When I open the metadata editor for the file, the field has the wanted value.
Don't forget to revert the track name to its initial value.
Reproducible: Always
Steps to Reproduce:
1. I open the metadata editor for a single file
2. I copy the artist field and replace the field album artist with the artist.
I don't modify any other fields.
3. I click on the "save and close" button.
4. Absolutely no change
5. I open the metadata editor: no changes were made to the song. The album
artist is still "Edison".
Actual Results:
The track keeps its previous value for "album artist"
Expected Results:
The track's album artist should have been changed and saved. The ordering by
album should have been updated (because the two albums of the tracklist have
the same title and different album artists). All this happens correctly if the
title is modified at the same time.
--
You are receiving this mail because:
You are watching all bug changes.
[amarok] [Bug 360755] Change of album artist field alone in single mp3 file has no impact
https://bugs.kde.org/show_bug.cgi?id=360755 --- Comment #2 from Thierry Belair --- That's very good news, thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 303627] update-mime-database complains about unknown media types
https://bugs.kde.org/show_bug.cgi?id=303627 Thierry Thomas changed: What|Removed |Added CC||thie...@freebsd.org --- Comment #8 from Thierry Thomas --- Same problem with kdelibs-4.14.3 on FreeBSD: Unknown media type in type 'chemical/x-alchemy' Unknown media type in type 'chemical/x-cache' Unknown media type in type 'chemical/x-cactvs-ascii' Unknown media type in type 'chemical/x-cactvs-binary' Unknown media type in type 'chemical/x-cactvs-table' Unknown media type in type 'chemical/x-cdx' Unknown media type in type 'chemical/x-cdxml' Unknown media type in type 'chemical/x-chem3d' Unknown media type in type 'chemical/x-cif' Unknown media type in type 'chemical/x-cml' Unknown media type in type 'chemical/x-daylight-smiles' Unknown media type in type 'chemical/x-dmol' Unknown media type in type 'chemical/x-gamess-input' Unknown media type in type 'chemical/x-gamess-output' Unknown media type in type 'chemical/x-gaussian-input' Unknown media type in type 'chemical/x-gaussian-log' Unknown media type in type 'chemical/x-genbank' Unknown media type in type 'chemical/x-gulp' Unknown media type in type 'chemical/x-hin' Unknown media type in type 'chemical/x-inchi' Unknown media type in type 'chemical/x-inchi-xml' Unknown media type in type 'chemical/x-jcamp-dx' Unknown media type in type 'chemical/x-macromodel-input' Unknown media type in type 'chemical/x-mdl-molfile' Unknown media type in type 'chemical/x-mdl-rdfile' Unknown media type in type 'chemical/x-mdl-rxnfile' Unknown media type in type 'chemical/x-mdl-sdfile' Unknown media type in type 'chemical/x-mdl-tgf' Unknown media type in type 'chemical/x-mmcif' Unknown media type in type 'chemical/x-mol2' Unknown media type in type 'chemical/x-mopac-graph' Unknown media type in type 'chemical/x-mopac-input' Unknown media type in type 'chemical/x-mopac-out' Unknown media type in type 'chemical/x-msi-car' Unknown media type in type 'chemical/x-msi-hessian' Unknown media type in type 'chemical/x-msi-mdf' Unknown media type in type 'chemical/x-msi-msi' Unknown media type in type 'chemical/x-ncbi-asn1' Unknown media type in type 'chemical/x-ncbi-asn1-binary' Unknown media type in type 'chemical/x-ncbi-asn1-xml' Unknown media type in type 'chemical/x-pdb' Unknown media type in type 'chemical/x-shelx' Unknown media type in type 'chemical/x-vmd' Unknown media type in type 'chemical/x-xyz' Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 361476] New: First letters in search box removed - need to type again
https://bugs.kde.org/show_bug.cgi?id=361476 Bug ID: 361476 Summary: First letters in search box removed - need to type again Product: muon Version: 5.5.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: alex.thie...@openmailbox.org CC: echidna...@kubuntu.org, sit...@kde.org When I try to launch a search in Muon Discover, I type the name, but after the first letter, the page change to the results page and the content of the textbox is removed. Because of that, I need to type the name of the software once again. It shouldn't be removed from the textbox. Reproducible: Always Steps to Reproduce: 1. Begin typing a software name (first letter is enough) 2. The result page loads and the letter is removed Actual Results: After I enter the 1st letter, the page change to the results. The 1st letter disappear so that I need to enter it again once the results page is loaded. Expected Results: I should be able to continue typing the following letters of the software. -- You are receiving this mail because: You are watching all bug changes.
