[plasmashell] [Bug 471848] crash after deletating icon from taskbar
https://bugs.kde.org/show_bug.cgi?id=471848 --- Comment #1 from Jaap van Wingerde --- Created attachment 160036 --> https://bugs.kde.org/attachment.cgi?id=160036&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 471848] New: crash after deletating icon from taskbar
https://bugs.kde.org/show_bug.cgi?id=471848 Bug ID: 471848 Summary: crash after deletating icon from taskbar Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@vanwingerde.nl CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-9-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [CoredumpBackend] -- Information about the crash: crash after deletating icon from taskbar asdklcASKLM lsdkmcflasdkMc The reporter is unsure if this crash is reproducible. -- Backtrace (Reduced): #8 0x7f38a10e229f in QObject::destroyed(QObject*) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f38a10e7254 in QObject::~QObject() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #12 0x7f38a10db28e in QObjectPrivate::deleteChildren() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f38a10e7054 in QObject::~QObject() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #15 0x7f38a10db28e in QObjectPrivate::deleteChildren() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 471596] New: Crash during copy
https://bugs.kde.org/show_bug.cgi?id=471596 Bug ID: 471596 Summary: Crash during copy Classification: Applications Product: krusader Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: k...@vanwingerde.nl CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.7.2 "Peace of Mind") Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 6.1.0-0.deb11.7-amd64 x86_64 Windowing system: X11 Distribution: Debian GNU/Linux 11 (bullseye) -- Information about the crash: - What I was doing when the application crashed: Script was copying many files. Krusader stiopped, the script continued to work. The crash can be reproduced sometimes. -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f42029f6d80 (LWP 16727))] [KCrash Handler] #6 0x55c2baa0ce58 in KrViewItem::itemRect (this=0x55c2bc4dadd0) at ./krusader/Panel/PanelView/krviewitem.cpp:140 #7 0x55c2ba9d9502 in KrPreviewJob::sort (this=this@entry=0x55c2bc50ebd0) at ./krusader/Panel/krpreviewjob.cpp:142 #8 0x55c2ba9d9dfd in KrPreviewJob::slotStartJob (this=0x55c2bc50ebd0) at ./krusader/Panel/krpreviewjob.cpp:101 #9 0x7f4206ae45e0 in doActivate (sender=0x55c2bc50ec00, signal_index=3, argv=argv@entry=0x7ffdc57d7710) at kernel/qobject.cpp:3898 #10 0x7f4206add900 in QMetaObject::activate (sender=, m=m@entry=0x7f4206d442a0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffdc57d7710) at kernel/qobject.cpp:3946 #11 0x7f4206ae84ba in QTimer::timeout (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #12 0x7f4206ad9f2f in QObject::event (this=0x55c2bc50ec00, e=0x7ffdc57d7880) at kernel/qobject.cpp:1336 #13 0x7f420776315f in QApplicationPrivate::notify_helper (this=, receiver=0x55c2bc50ec00, e=0x7ffdc57d7880) at kernel/qapplication.cpp:3632 #14 0x7f4206aadfca in QCoreApplication::notifyInternal2 (receiver=0x55c2bc50ec00, event=0x7ffdc57d7880) at kernel/qcoreapplication.cpp:1063 #15 0x7f4206b048e3 in QTimerInfoList::activateTimers (this=0x55c2bb03ec80) at kernel/qtimerinfo_unix.cpp:643 #16 0x7f4206b05164 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:183 #17 0x7f42051d3e6b in g_main_dispatch (context=0x7f41fc005000) at ../../../glib/gmain.c:3325 #18 g_main_context_dispatch (context=0x7f41fc005000) at ../../../glib/gmain.c:4043 #19 0x7f42051d4118 in g_main_context_iterate (context=context@entry=0x7f41fc005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4119 #20 0x7f42051d41cf in g_main_context_iteration (context=0x7f41fc005000, may_block=may_block@entry=1) at ../../../glib/gmain.c:4184 #21 0x7f4206b0551f in QEventDispatcherGlib::processEvents (this=0x55c2bb03b2a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7f4206aac98b in QEventLoop::exec (this=this@entry=0x7ffdc57d7ac0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #23 0x7f4206ab4c00 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #24 0x7f4206f30bdc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #25 0x7f42077630d5 in QApplication::exec () at kernel/qapplication.cpp:2824 #26 0x55c2ba9a2574 in main (argc=, argv=) at ./krusader/main.cpp:316 [Inferior 1 (process 16727) detached] The reporter indicates this bug may be a duplicate of or related to bug 448647. Possible duplicates by query: bug 448647, bug 425528, bug 414332, bug 284202, bug 256794. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466340] Second monitor occasionally loses containment on login
https://bugs.kde.org/show_bug.cgi?id=466340 Jaap Geurts changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #7 from Jaap Geurts --- It's only stable in the sense that the next few reboots will probably be fine until I reconnect some other monitors. Your suggestion about my state being messed up could be the case. I will start afresh with new settings and see what happens. I'll consider it not a bug. Thanks a lot for the quick responses! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466340] Second monitor occasionally loses containment on login
https://bugs.kde.org/show_bug.cgi?id=466340 --- Comment #5 from Jaap Geurts --- > If you enter edit mode and click on the "Manage Desktops and Panels" button > that live son the toolbars which drops down from the top of the screen, can > you use the window that appears to find your missing containment and move it > back to the correct screen? Today I had the black screen again(again on the second monitor) After opening "manage desktops and panels". The missing containment is there. Before doing or moving anything: It showed the containment as thumbnails in the correct position. The thumbnail showed as if the containment was visible normally on the second monitor however the monitor itself was black. After that I moved the containment to another position and then the monitor containment showed correctly. After reboots things are normal. Extra information: I'm using activities. I noticed that an activity was lost (the activity monitor also didn't show my second activity). Rebooting resolved it and it returned back to normal. Because I lost the activity all the window placements were on both activities after reboot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466340] Second monitor occasionally loses containment on login
https://bugs.kde.org/show_bug.cgi?id=466340 --- Comment #4 from Jaap Geurts --- (In reply to Nate Graham from comment #3) It hasn't happened for the past few days. When I see it again, I'll report it here. If it takes too long I'll let you know too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466340] Second monitor occasionally shows a black screen on login
https://bugs.kde.org/show_bug.cgi?id=466340 --- Comment #2 from Jaap Geurts --- No. it doesn't have an NVIDIA GPU. This is the inxi -G output: Graphics: Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel Device-2: Chicony Integrated Camera type: USB driver: uvcvideo Display: x11 server: X.Org v: 21.1.7 with: Xwayland v: 22.1.8 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz 3: N/A API: OpenGL v: 4.6 Mesa 22.3.5 renderer: Mesa Intel Xe Graphics (TGL GT2) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466340] Second monitor occasionally shows a black screen on login
https://bugs.kde.org/show_bug.cgi?id=466340 Jaap Geurts changed: What|Removed |Added CC||jaap.geu...@fontys.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466340] New: Second monitor occasionally shows a black screen on login
https://bugs.kde.org/show_bug.cgi?id=466340 Bug ID: 466340 Summary: Second monitor occasionally shows a black screen on login Classification: Plasma Product: plasmashell Version: 5.27.0 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: plasma-b...@kde.org Reporter: jaap.geu...@fontys.nl CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 Created attachment 15 --> https://bugs.kde.org/attachment.cgi?id=15&action=edit kscreen-doctor, kscreen-console, appletsrc STEPS TO REPRODUCE 1. Start computer from boot 2. Login as a normal user 3. Wait until plasma desktop has loaded. OBSERVED RESULT The second monitor occasionally is black. There seems to be no containment because there is no wallpaper, no widgets and the context menu on right click doesn't do anything. Logging out and back in resolves to the correct old state. Windows are restored on the correct monitor. EXPECTED RESULT Wallpaper, widgets and context menu working correctly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.27 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel version: 6.1.12-1 ADDITIONAL INFORMATION Plasma/KDE on X11 This happens on the second (non-primary) monitor) The computer is a laptop with two external monitors through a docking station with the laptop lid closed and the laptop screen disabled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and turns black for 30 seconds on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #56 from Jaap Geurts --- Still happens to me, although less frequent. When that happens it also moves windows from that monitor to the other monitor. Plasma 5.27. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #49 from Jaap Geurts --- Forgot to mention. I'm on Xorg. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 --- Comment #48 from Jaap Geurts --- I just had it happen to me again on 5.25. I also use a multi-monitor(usually 2 external monitors) and multi activities setup. I'm a laptop users and I connect to many different monitors during the day(I'm a hot desking user). For me it always happens upon switching to another desk with a different set of monitors. It seems that kde doesn't recognize the new monitor(s) or recognizes them too late or relabels the monitor. Then it thinks the new setup has no activity(containment) and decides to create a new activity(containment) for each monitor which makes me lose my old activities(containments). It won't switch back either since the new one is working fine and now the default. Only very occasionally does it revert back) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 371717] Containment for the second monitor is lost and reset to its default settings on boot or when it is connected
https://bugs.kde.org/show_bug.cgi?id=371717 Jaap Geurts changed: What|Removed |Added CC||jaap.geu...@fontys.nl -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381270] Plasma lost all my configuration when connected to another screen while using activities
https://bugs.kde.org/show_bug.cgi?id=381270 Jaap Geurts changed: What|Removed |Added CC||jaap.geu...@fontys.nl -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 402780] Akonadi doesn't work with Exchange again
https://bugs.kde.org/show_bug.cgi?id=402780 Jaap Geurts changed: What|Removed |Added CC||jaap.geu...@fontys.nl -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450582] Some change between 5.24.0 and 5.24.1 broke windows shade/shutter feature
https://bugs.kde.org/show_bug.cgi?id=450582 Jaap Geurts changed: What|Removed |Added CC||jaap.geu...@fontys.nl -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Jaap Geurts changed: What|Removed |Added CC||jaap.geu...@fontys.nl -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 430617] New: settings menu disturbed
https://bugs.kde.org/show_bug.cgi?id=430617 Bug ID: 430617 Summary: settings menu disturbed Product: konqueror Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: htmlsettingsplugin Assignee: konq-b...@kde.org Reporter: bugs...@softskills.nl Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. try to change setting 2. klick apply 3. menu is vague, flickering. OBSERVED RESULT menu unreadable EXPECTED RESULT menu close after apply SOFTWARE/OS VERSIONS Fedora 33 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 428720] New: error mssage after start
https://bugs.kde.org/show_bug.cgi?id=428720 Bug ID: 428720 Summary: error mssage after start Product: ksplash Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: bugs...@softskills.nl Target Milestone: --- Created attachment 133047 --> https://bugs.kde.org/attachment.cgi?id=133047&action=edit backtrace SUMMARY install rawhide fedora kde live nihtly 20201103, error message about ksplasqml STEPS TO REPRODUCE 1. start again 2. 3. OBSERVED RESULT error message 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.
[krusader] [Bug 423041] sftp/segmentation fault
https://bugs.kde.org/show_bug.cgi?id=423041 Jaap van Wingerde changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Jaap van Wingerde --- Not reproducable anymore Operating System: linux-image-5.7.10-0~bpo.1-amd64 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 423041] sftp/segmentation fault
https://bugs.kde.org/show_bug.cgi?id=423041 Jaap van Wingerde changed: What|Removed |Added CC||k...@vanwingerde.nl -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 423041] New: sftp/segmentation fault
https://bugs.kde.org/show_bug.cgi?id=423041 Bug ID: 423041 Summary: sftp/segmentation fault Product: krusader Version: 2.7.1 Platform: Debian stable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: net-connection Assignee: krusader-bugs-n...@kde.org Reporter: k...@vanwingerde.nl CC: krusader-bugs-n...@kde.org Target Milestone: --- SUMMARY Krusader crashes with segmenation fault, no useful backtrace STEPS TO REPRODUCE 1. copy from SFTP-dir to NFS-dir 2. 3. OBSERVED RESULT segmentation fault no useful backtrace EXPECTED RESULT no fault a useful backtrace SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Debian GNU/Linux 10 (buster),Linux 5.5.0-0.bpo.2-amd64 x86_64 (available in About System) KDE Plasma Version: 5.54.0 KDE Frameworks Version: Qt Version: 5.11.3 ADDITIONAL INFORMATION Application: krusader (2.7.1 "Peace of Mind") Qt Version: 5.11.3 Frameworks Version: 5.54.0 Operating System: Linux 5.5.0-0.bpo.2-amd64 x86_64 Distribution: Debian GNU/Linux 10 (buster) -- Information about the crash: The crash can be reproduced every time. -- Backtrace: A useful backtrace could not be generated Rapporteer naar https://bugs.kde.org/ -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419621] Ko does not work satisfactory in Fedora 32
https://bugs.kde.org/show_bug.cgi?id=419621 --- Comment #3 from Jaap --- Thanks for reminder, I left Konqueror and cannot give the backtrace. thanks -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 419621] New: Ko does not work satisfactory in Fedora 32
https://bugs.kde.org/show_bug.cgi?id=419621 Bug ID: 419621 Summary: Ko does not work satisfactory in Fedora 32 Product: konqueror Version: 5.0.97 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: bugs...@softskills.nl Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. sudden error messages 2. no background, crashing. 3. search engine not working correct 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.
[Falkon] [Bug 419530] Search bar content not sent to the search engine
https://bugs.kde.org/show_bug.cgi?id=419530 Jaap changed: What|Removed |Added CC||bugs...@softskills.nl --- Comment #4 from Jaap --- I do have same problems adding startpage as a search engine. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409547] crash when creating directory.
https://bugs.kde.org/show_bug.cgi?id=409547 --- Comment #2 from Jaap Geurts --- Created attachment 121351 --> https://bugs.kde.org/attachment.cgi?id=121351&action=edit Additional backtrace with debug symbols loaded. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409547] New: crash when creating directory.
https://bugs.kde.org/show_bug.cgi?id=409547 Bug ID: 409547 Summary: crash when creating directory. Product: kdevelop Version: 5.3.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: jaap.geu...@fontys.nl Target Milestone: --- Application: kdevelop (5.3.2) Qt Version: 5.13.0 Frameworks Version: 5.59.0 Operating System: Linux 5.1.10-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Precondition: Working on files without a project. Files are arduino sketch files (*.ino) first created new file from template in a new directory => success. save file Problem steps Keep the first file open. from the menu file ->new from template select custom created template for arduino select location by clicking on "browse" button current folder is: /BBB/week3/solution/example1 go up from the current directory(this is where the first file is) three levels (you're at /BBB) go down another folder week4. you should be at /BBB/week4 create new folder solution (and go in) create new folder example2 (and go in) enter sketch name example2.ino click OK. somewhere in the last three steps the crash occurs. expected result. no crash. The crash can be reproduced every time. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa793cdff80 (LWP 21739))] Thread 20 (Thread 0x7fa745ffb700 (LWP 23821)): #0 0x7fa79449a4d8 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #1 0x7fa79449b6b8 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #2 0x7fa79449b9f9 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #3 0x7fa79449c24a in ?? () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #4 0x7fa796a39c23 in pa_mainloop_dispatch () from /usr/lib64/libpulse.so.0 #5 0x7fa796a39f4e in pa_mainloop_iterate () from /usr/lib64/libpulse.so.0 #6 0x7fa796a39ff0 in pa_mainloop_run () from /usr/lib64/libpulse.so.0 #7 0x7fa796a48039 in ?? () from /usr/lib64/libpulse.so.0 #8 0x7fa7944abdb8 in ?? () from /usr/lib64/pulseaudio/libpulsecommon-12.2.so #9 0x7fa7a22a2faa in start_thread () from /lib64/libpthread.so.0 #10 0x7fa7a4e9171f in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7fa7467fc700 (LWP 21901)): #0 0x7fa7a22a8e05 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa7a520dfbf in QWaitConditionPrivate::wait (deadline=..., this=0x55f9c125c170) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55f9c1249be0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7fa7a520e0a9 in QWaitCondition::wait (this=0x55f9c1249b48, mutex=0x55f9c1249be0, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7fa7a1893610 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fa7a1896f3a in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fa7a189287e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fa7a189517b in ThreadWeaver::Thread::run() () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fa7a5208112 in QThreadPrivate::start (arg=0x7fa7380038e0) at thread/qthread_unix.cpp:360 #9 0x7fa7a22a2faa in start_thread () from /lib64/libpthread.so.0 #10 0x7fa7a4e9171f in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7fa746ffd700 (LWP 21900)): #0 0x7fa7a22a8e05 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa7a520dfbf in QWaitConditionPrivate::wait (deadline=..., this=0x55f9c125c170) at thread/qwaitcondition_unix.cpp:146 #2 QWaitCondition::wait (this=, mutex=0x55f9c1249be0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #3 0x7fa7a520e0a9 in QWaitCondition::wait (this=0x55f9c1249b48, mutex=0x55f9c1249be0, time=) at ../../include/QtCore/../../src/corelib/kernel/qdeadlinetimer.h:68 #4 0x7fa7a1893610 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fa7a1896f3a in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fa7a189287e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fa7a1896f91 in ?? () from /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fa7a189287e in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7fa7a1896f91 in ?? () from /usr/lib64
[amarok] [Bug 386004] no connection with mariadb (Debian Stretch)
https://bugs.kde.org/show_bug.cgi?id=386004 Jaap van Wingerde changed: What|Removed |Added Severity|normal |major -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 386004] no connection with mariadb (Debian Stretch)
https://bugs.kde.org/show_bug.cgi?id=386004 Jaap van Wingerde changed: What|Removed |Added Platform|Other |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 386004] New: no connection with mariadb (Debian Stretch)
https://bugs.kde.org/show_bug.cgi?id=386004 Bug ID: 386004 Summary: no connection with mariadb (Debian Stretch) Product: amarok Version: 2.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: k...@vanwingerde.nl Target Milestone: 2.9 ~/.kde/share/config/amarokrc: ... [MySQL] Host=10.0.0.159 Password=secret UseServer=true ... jaap@jaap:/$ amarok --debug --nofork ... amarok: connection to mysql failed amarok: [ERROR__] Could not connect to mysql! amarok: [ERROR__] [MySqlStorage] "GREPME MySQL-server query failed! (1045) Access denied for user 'amarokuser'@'jaap.custard.shrl.nl' (using password: YES) on na" ... jaap.custard.shrl.nl is the local machine (10.0.0.150) without database server 10.0.0.159 is the database server (Debian Jessie) -- You are receiving this mail because: You are watching all bug changes.
