[amarok] [Bug 328359] Amarok crashes when using MusicBrains to update tags [@ MusicBrainzTagsItem::childCount]
https://bugs.kde.org/show_bug.cgi?id=328359 Argyris M changed: What|Removed |Added CC||argy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 328359] Amarok crashes when using MusicBrains to update tags [@ MusicBrainzTagsItem::childCount]
https://bugs.kde.org/show_bug.cgi?id=328359 --- Comment #42 from Argyris M --- Created attachment 96917 --> https://bugs.kde.org/attachment.cgi?id=96917&action=edit New crash information added by DrKonqi amarok (2.8.0) on KDE Platform 4.14.16 using Qt 4.8.7 - What I was doing when the application crashed: Searching for tags with MusicBrainz. It crashes even when searching for a single track, but only if results are found. If not, nothing happens. -- Backtrace (Reduced): #6 0x7f9a90924971 in QReadWriteLock::lockForRead() () from /usr/lib/libQtCore.so.4 #7 0x7f9a92eb4d71 in QReadLocker::relock (this=0x7ffc43451690) at /usr/include/qt4/QtCore/qreadwritelock.h:111 #8 0x7f9a9308b9b5 in MusicBrainzTagsItem::childCount (this=0x0) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsItem.cpp:216 #9 0x7f9a9308f675 in MusicBrainzTagsModel::flags (this=0x3be7000, index=...) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsModel.cpp:210 #10 0x7f9a9156584b in QSortFilterProxyModel::flags(QModelIndex const&) const () from /usr/lib/libQtGui.so.4 --- Comment #43 from Argyris M --- Created attachment 96918 --> https://bugs.kde.org/attachment.cgi?id=96918&action=edit New crash information added by DrKonqi amarok (2.8.0) on KDE Platform 4.14.16 using Qt 4.8.7 - What I was doing when the application crashed: Searching for tags with MusicBrainz. It crashes even when searching for a single track, but only if results are found. If not, nothing happens. -- Backtrace (Reduced): #6 0x7f9a90924971 in QReadWriteLock::lockForRead() () from /usr/lib/libQtCore.so.4 #7 0x7f9a92eb4d71 in QReadLocker::relock (this=0x7ffc43451690) at /usr/include/qt4/QtCore/qreadwritelock.h:111 #8 0x7f9a9308b9b5 in MusicBrainzTagsItem::childCount (this=0x0) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsItem.cpp:216 #9 0x7f9a9308f675 in MusicBrainzTagsModel::flags (this=0x3be7000, index=...) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsModel.cpp:210 #10 0x7f9a9156584b in QSortFilterProxyModel::flags(QModelIndex const&) const () from /usr/lib/libQtGui.so.4 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 328359] Amarok crashes when using MusicBrains to update tags [@ MusicBrainzTagsItem::childCount]
https://bugs.kde.org/show_bug.cgi?id=328359 --- Comment #42 from Argyris M --- Created attachment 96917 --> https://bugs.kde.org/attachment.cgi?id=96917&action=edit New crash information added by DrKonqi amarok (2.8.0) on KDE Platform 4.14.16 using Qt 4.8.7 - What I was doing when the application crashed: Searching for tags with MusicBrainz. It crashes even when searching for a single track, but only if results are found. If not, nothing happens. -- Backtrace (Reduced): #6 0x7f9a90924971 in QReadWriteLock::lockForRead() () from /usr/lib/libQtCore.so.4 #7 0x7f9a92eb4d71 in QReadLocker::relock (this=0x7ffc43451690) at /usr/include/qt4/QtCore/qreadwritelock.h:111 #8 0x7f9a9308b9b5 in MusicBrainzTagsItem::childCount (this=0x0) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsItem.cpp:216 #9 0x7f9a9308f675 in MusicBrainzTagsModel::flags (this=0x3be7000, index=...) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsModel.cpp:210 #10 0x7f9a9156584b in QSortFilterProxyModel::flags(QModelIndex const&) const () from /usr/lib/libQtGui.so.4 -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 359346] New: Scrobbling to last.fm is broken
https://bugs.kde.org/show_bug.cgi?id=359346 Bug ID: 359346 Summary: Scrobbling to last.fm is broken Product: juk Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: argy...@gmail.com CC: mp...@kde.org Scrobbling music to Last.fm is broken in JuK 3.12. Tested on Arch Linux (precompiled and compiled from source) and Kubuntu 15.10. Credentials are saved (either in KWallet or in plaintext) and test login works, but nothing is scrobbled. Reproducible: Always Steps to Reproduce: 1. Enter your Last.fm credentials in the scrobbling configuration dialog 2. Verify credentials with the test login button 3. Play any song Actual Results: Nothing is sent to Last.fm Expected Results: The song played should have appeared in my Last.fm profile under Recent Tracks. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 359346] Scrobbling to last.fm is broken
https://bugs.kde.org/show_bug.cgi?id=359346 Argyris M changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=262194 -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 361139] New: Searching for specific file categories in Dolphin doesn't work
https://bugs.kde.org/show_bug.cgi?id=361139 Bug ID: 361139 Summary: Searching for specific file categories in Dolphin doesn't work Product: BalooWidgets Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: argy...@gmail.com CC: pinak.ah...@gmail.com This bug duplicates the behavior of #348902, which has supposedly been fixed. I am filing it again because the old one's location is now obsolete, but also because there has been no reaction to existing reports of it not being fixed. Please disregard the confusion that has arisen in the last few comments of the old bug; it is the originally reported behavior that is broken. Namely, selecting any of the "Search For" options in Dolphin shows a status of "searching" infinitely and always yields zero results, even when typing a specific filename into the search bar. Clicking "x" to cancel the search yields an "Invalid protocol" error. Reproducible: Always Steps to Reproduce: 1. Click on any of the "search for" options (Documents, Images, etc) 2. Wait, or type anything in the search bar 3. Give up and click x to cancel Actual Results: The status bar keeps showing "searching", no results are found and clicking "x" produces an "Invalid protocol" error and an empty window. Expected Results: Results should appear and the search should exit cleanly back to the folder from which it was initiated. After the error appears, the address bar displays a path of "Network>Home>User" but clicking on it to reveal the actual path simply shows "/home/user". -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 361139] Searching for specific file categories in Dolphin doesn't work
https://bugs.kde.org/show_bug.cgi?id=361139 --- Comment #1 from Argyris M --- Forgot to confirm I'm using the latest versions of everything. Dolphin 15.12.3, Frameworks (and therefore Baloo) 5.20.0. -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 361139] Searching for specific file categories in Dolphin doesn't work
https://bugs.kde.org/show_bug.cgi?id=361139 --- Comment #3 from Argyris M --- It seems you are right. In my defence the original bug did specifically say it was fixed in 15.12 but I'm really sorry I didn't think to check nonetheless. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support
https://bugs.kde.org/show_bug.cgi?id=361066 Argyris M changed: What|Removed |Added CC||argy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 361863] ktorrent 5.0 get Segmentation fault when trying to enable scheduler plugin
https://bugs.kde.org/show_bug.cgi?id=361863 Argyris M changed: What|Removed |Added CC||argy...@gmail.com --- Comment #2 from Argyris M --- Also confirmed (KTorrent 5.0.1 on Arch Linux). -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 361931] New: KTorrent immediately segfaults when starting download from .torrent file
https://bugs.kde.org/show_bug.cgi?id=361931 Bug ID: 361931 Summary: KTorrent immediately segfaults when starting download from .torrent file Product: ktorrent Version: 5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: argy...@gmail.com After upgrading to 5.0.1, opening a .torrent file results in a segfault moments after downloading starts. Every time KTorrent is restarted, whatever little data has been downloaded is normally checked then it crashes again. Downloading the very same torrents via magnet links works fine. Confirmed to also happen in 5.0 and with a clean configuration. Reproducible: Always Steps to Reproduce: Open any .torrent file with KTorrent Actual Results: Connections to trackers are established, disk space is allocated, then the moment downloading starts KTorrent crashes Expected Results: Download should proceed normally. Although I have recompiled both ktorrent and libktorrent with debug symbols and can get a backtrace for e.g. #361863, the backtrace for this crash simply reads: Application: KTorrent (ktorrent), signal: Segmentation fault -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 361931] KTorrent immediately segfaults when starting download from .torrent file
https://bugs.kde.org/show_bug.cgi?id=361931 Argyris M changed: What|Removed |Added Severity|major |crash -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 361702] Kactivitymanagerd doesn't close on shutdown and triggers 90 sec shutdown delay in systemd
https://bugs.kde.org/show_bug.cgi?id=361702 Argyris M changed: What|Removed |Added CC||argy...@gmail.com --- Comment #2 from Argyris M --- Created attachment 98746 --> https://bugs.kde.org/attachment.cgi?id=98746&action=edit systemd shutdown log I can confirm this on 5.6.3 too, on three different machines. It's been happening since 5.6.0. I am attaching the relevant part of the systemd shutdown log. The delay is short only because I have manually reduced the timeout. -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 361139] New: Searching for specific file categories in Dolphin doesn't work
https://bugs.kde.org/show_bug.cgi?id=361139 Bug ID: 361139 Summary: Searching for specific file categories in Dolphin doesn't work Product: BalooWidgets Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: grave Priority: NOR Component: general Assignee: m...@vhanda.in Reporter: argy...@gmail.com CC: pinak.ah...@gmail.com This bug duplicates the behavior of #348902, which has supposedly been fixed. I am filing it again because the old one's location is now obsolete, but also because there has been no reaction to existing reports of it not being fixed. Please disregard the confusion that has arisen in the last few comments of the old bug; it is the originally reported behavior that is broken. Namely, selecting any of the "Search For" options in Dolphin shows a status of "searching" infinitely and always yields zero results, even when typing a specific filename into the search bar. Clicking "x" to cancel the search yields an "Invalid protocol" error. Reproducible: Always Steps to Reproduce: 1. Click on any of the "search for" options (Documents, Images, etc) 2. Wait, or type anything in the search bar 3. Give up and click x to cancel Actual Results: The status bar keeps showing "searching", no results are found and clicking "x" produces an "Invalid protocol" error and an empty window. Expected Results: Results should appear and the search should exit cleanly back to the folder from which it was initiated. After the error appears, the address bar displays a path of "Network>Home>User" but clicking on it to reveal the actual path simply shows "/home/user". -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 361139] Searching for specific file categories in Dolphin doesn't work
https://bugs.kde.org/show_bug.cgi?id=361139 --- Comment #1 from Argyris M --- Forgot to confirm I'm using the latest versions of everything. Dolphin 15.12.3, Frameworks (and therefore Baloo) 5.20.0. -- You are receiving this mail because: You are watching all bug changes.
[BalooWidgets] [Bug 361139] Searching for specific file categories in Dolphin doesn't work
https://bugs.kde.org/show_bug.cgi?id=361139 --- Comment #3 from Argyris M --- It seems you are right. In my defence the original bug did specifically say it was fixed in 15.12 but I'm really sorry I didn't think to check nonetheless. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361066] [Feature Request] GTK+ 3.20 support
https://bugs.kde.org/show_bug.cgi?id=361066 Argyris M changed: What|Removed |Added CC||argy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 361863] ktorrent 5.0 get Segmentation fault when trying to enable scheduler plugin
https://bugs.kde.org/show_bug.cgi?id=361863 Argyris M changed: What|Removed |Added CC||argy...@gmail.com --- Comment #2 from Argyris M --- Also confirmed (KTorrent 5.0.1 on Arch Linux). -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 361931] New: KTorrent immediately segfaults when starting download from .torrent file
https://bugs.kde.org/show_bug.cgi?id=361931 Bug ID: 361931 Summary: KTorrent immediately segfaults when starting download from .torrent file Product: ktorrent Version: 5.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: argy...@gmail.com After upgrading to 5.0.1, opening a .torrent file results in a segfault moments after downloading starts. Every time KTorrent is restarted, whatever little data has been downloaded is normally checked then it crashes again. Downloading the very same torrents via magnet links works fine. Confirmed to also happen in 5.0 and with a clean configuration. Reproducible: Always Steps to Reproduce: Open any .torrent file with KTorrent Actual Results: Connections to trackers are established, disk space is allocated, then the moment downloading starts KTorrent crashes Expected Results: Download should proceed normally. Although I have recompiled both ktorrent and libktorrent with debug symbols and can get a backtrace for e.g. #361863, the backtrace for this crash simply reads: Application: KTorrent (ktorrent), signal: Segmentation fault -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 361931] KTorrent immediately segfaults when starting download from .torrent file
https://bugs.kde.org/show_bug.cgi?id=361931 Argyris M changed: What|Removed |Added Severity|major |crash -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 361702] Kactivitymanagerd doesn't close on shutdown and triggers 90 sec shutdown delay in systemd
https://bugs.kde.org/show_bug.cgi?id=361702 Argyris M changed: What|Removed |Added CC||argy...@gmail.com --- Comment #2 from Argyris M --- Created attachment 98746 --> https://bugs.kde.org/attachment.cgi?id=98746&action=edit systemd shutdown log I can confirm this on 5.6.3 too, on three different machines. It's been happening since 5.6.0. I am attaching the relevant part of the systemd shutdown log. The delay is short only because I have manually reduced the timeout. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 328359] Amarok crashes when using MusicBrains to update tags [@ MusicBrainzTagsItem::childCount]
https://bugs.kde.org/show_bug.cgi?id=328359 Argyris M changed: What|Removed |Added CC||argy...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 328359] Amarok crashes when using MusicBrains to update tags [@ MusicBrainzTagsItem::childCount]
https://bugs.kde.org/show_bug.cgi?id=328359 --- Comment #42 from Argyris M --- Created attachment 96917 --> https://bugs.kde.org/attachment.cgi?id=96917&action=edit New crash information added by DrKonqi amarok (2.8.0) on KDE Platform 4.14.16 using Qt 4.8.7 - What I was doing when the application crashed: Searching for tags with MusicBrainz. It crashes even when searching for a single track, but only if results are found. If not, nothing happens. -- Backtrace (Reduced): #6 0x7f9a90924971 in QReadWriteLock::lockForRead() () from /usr/lib/libQtCore.so.4 #7 0x7f9a92eb4d71 in QReadLocker::relock (this=0x7ffc43451690) at /usr/include/qt4/QtCore/qreadwritelock.h:111 #8 0x7f9a9308b9b5 in MusicBrainzTagsItem::childCount (this=0x0) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsItem.cpp:216 #9 0x7f9a9308f675 in MusicBrainzTagsModel::flags (this=0x3be7000, index=...) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsModel.cpp:210 #10 0x7f9a9156584b in QSortFilterProxyModel::flags(QModelIndex const&) const () from /usr/lib/libQtGui.so.4 --- Comment #43 from Argyris M --- Created attachment 96918 --> https://bugs.kde.org/attachment.cgi?id=96918&action=edit New crash information added by DrKonqi amarok (2.8.0) on KDE Platform 4.14.16 using Qt 4.8.7 - What I was doing when the application crashed: Searching for tags with MusicBrainz. It crashes even when searching for a single track, but only if results are found. If not, nothing happens. -- Backtrace (Reduced): #6 0x7f9a90924971 in QReadWriteLock::lockForRead() () from /usr/lib/libQtCore.so.4 #7 0x7f9a92eb4d71 in QReadLocker::relock (this=0x7ffc43451690) at /usr/include/qt4/QtCore/qreadwritelock.h:111 #8 0x7f9a9308b9b5 in MusicBrainzTagsItem::childCount (this=0x0) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsItem.cpp:216 #9 0x7f9a9308f675 in MusicBrainzTagsModel::flags (this=0x3be7000, index=...) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsModel.cpp:210 #10 0x7f9a9156584b in QSortFilterProxyModel::flags(QModelIndex const&) const () from /usr/lib/libQtGui.so.4 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 328359] Amarok crashes when using MusicBrains to update tags [@ MusicBrainzTagsItem::childCount]
https://bugs.kde.org/show_bug.cgi?id=328359 --- Comment #42 from Argyris M --- Created attachment 96917 --> https://bugs.kde.org/attachment.cgi?id=96917&action=edit New crash information added by DrKonqi amarok (2.8.0) on KDE Platform 4.14.16 using Qt 4.8.7 - What I was doing when the application crashed: Searching for tags with MusicBrainz. It crashes even when searching for a single track, but only if results are found. If not, nothing happens. -- Backtrace (Reduced): #6 0x7f9a90924971 in QReadWriteLock::lockForRead() () from /usr/lib/libQtCore.so.4 #7 0x7f9a92eb4d71 in QReadLocker::relock (this=0x7ffc43451690) at /usr/include/qt4/QtCore/qreadwritelock.h:111 #8 0x7f9a9308b9b5 in MusicBrainzTagsItem::childCount (this=0x0) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsItem.cpp:216 #9 0x7f9a9308f675 in MusicBrainzTagsModel::flags (this=0x3be7000, index=...) at /build/amarok/src/amarok-2.8.0/src/musicbrainz/MusicBrainzTagsModel.cpp:210 #10 0x7f9a9156584b in QSortFilterProxyModel::flags(QModelIndex const&) const () from /usr/lib/libQtGui.so.4 -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 359346] New: Scrobbling to last.fm is broken
https://bugs.kde.org/show_bug.cgi?id=359346 Bug ID: 359346 Summary: Scrobbling to last.fm is broken Product: juk Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: whee...@kde.org Reporter: argy...@gmail.com CC: mp...@kde.org Scrobbling music to Last.fm is broken in JuK 3.12. Tested on Arch Linux (precompiled and compiled from source) and Kubuntu 15.10. Credentials are saved (either in KWallet or in plaintext) and test login works, but nothing is scrobbled. Reproducible: Always Steps to Reproduce: 1. Enter your Last.fm credentials in the scrobbling configuration dialog 2. Verify credentials with the test login button 3. Play any song Actual Results: Nothing is sent to Last.fm Expected Results: The song played should have appeared in my Last.fm profile under Recent Tracks. -- You are receiving this mail because: You are watching all bug changes.
[juk] [Bug 359346] Scrobbling to last.fm is broken
https://bugs.kde.org/show_bug.cgi?id=359346 Argyris M changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=262194 -- You are receiving this mail because: You are watching all bug changes.
