[kwave] [Bug 389159] Recording Pause function does not work
https://bugs.kde.org/show_bug.cgi?id=389159 Thomas Eschenbacher changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |WORKSFORME Version Fixed In||https://commits.kde.org/kwa ||ve/4cb7404f974bb36bf6623b58 ||ec35aae092388a16 --- Comment #2 from Thomas Eschenbacher --- bug in recording state machine, should work now. -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 389159] Recording Pause function does not work
https://bugs.kde.org/show_bug.cgi?id=389159 Thomas Eschenbacher changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 389159] Recording Pause function does not work
https://bugs.kde.org/show_bug.cgi?id=389159 Thomas Eschenbacher changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Thomas Eschenbacher --- reproducible here too -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 394358] Kwave crashes when closing About dialog
https://bugs.kde.org/show_bug.cgi?id=394358 Thomas Eschenbacher changed: What|Removed |Added Resolution|--- |WORKSFORME Status|ASSIGNED|RESOLVED Version Fixed In||https://commits.kde.org/kwa ||ve/e237657b25e954060fce9419 ||c27aebec3996c6b9 --- Comment #9 from Thomas Eschenbacher --- Root cause was that a tab within a tab widget was included in the list of tab stops, as well as its parent widget. Should work now, see git commit: https://commits.kde.org/kwave/e237657b25e954060fce9419c27aebec3996c6b9 -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 394358] Kwave crashes when closing About dialog
https://bugs.kde.org/show_bug.cgi?id=394358 Thomas Eschenbacher changed: What|Removed |Added Status|CONFIRMED |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 394358] Kwave crashes when closing About dialog
https://bugs.kde.org/show_bug.cgi?id=394358 Thomas Eschenbacher changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #8 from Thomas Eschenbacher --- ok, 100% reproducible here, but only in the Help/About dialog -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 394358] Kwave crashes when closing About dialog
https://bugs.kde.org/show_bug.cgi?id=394358 --- Comment #7 from Thomas Eschenbacher --- OK, then it is in Qt. But I do not understand what that assert shall be good for. I have absolutely no idea what goes wrong here, and why it does not affect thousands of other applications too!? I am not aware of doing anything special there, I create a dialog, I close it, I delete the object... what should be so wrong about that? Does anyone have an idea? -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 394358] Kwave crashes when closing About dialog
https://bugs.kde.org/show_bug.cgi?id=394358 Thomas Eschenbacher changed: What|Removed |Added Summary|KWave crashes when closing |Kwave crashes when closing |About dialog|About dialog -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 394358] KWave crashes when closing About dialog
https://bugs.kde.org/show_bug.cgi?id=394358 --- Comment #5 from Thomas Eschenbacher --- I can confirm this here, this kind of crash happens in several kinds of situations. The more interesting stuff is the text that comes out on the console: FileContext::executeCommand(): loading plugin 'about' FileContext::executeCommand(): with 1 parameter(s) ASSERT: "d->focus_next->d_func()->focus_prev == this" in file kernel/qwidget.cpp, line 1607 KCrash: Application 'kwave' crashing... It is this ASSERT that causes the trouble. It has been introduced in the KDE libraries and IMHO is useless. Does anyone know a way how to prevent this? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 350810] file open dialog freezes when browsing to /dev
https://bugs.kde.org/show_bug.cgi?id=350810 --- Comment #4 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- I can confirm that the original bug seems to be fixed. Only the display is wrong, the texts of the items are all positioned overlapping over the preview symbols, which makes the dialog look ugly and the texts unreadable. -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 372806] new feature: collapse/expand of track views
https://bugs.kde.org/show_bug.cgi?id=372806 Thomas Eschenbacher <thomas.eschenbac...@gmx.de> changed: What|Removed |Added Ever confirmed|0 |1 Priority|NOR |VLO Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwave] [Bug 372806] New: new feature: collapse/expand of track views
https://bugs.kde.org/show_bug.cgi?id=372806 Bug ID: 372806 Summary: new feature: collapse/expand of track views Product: kwave Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: thomas.eschenbac...@gmx.de Reporter: thomas.eschenbac...@gmx.de Target Milestone: --- add a small (+) icon to expand/collapse track views -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357944] wrong encoded collection paths after upgrade from digikam v4.x
https://bugs.kde.org/show_bug.cgi?id=357944 --- Comment #2 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- I'm sorry, but I don't have enough time to prepare an environment to reproduce and test it. Additionally my collection already is converted and I don't have an old digikam-4 at hand. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 360017] build error: opencv_contrib is required but was not found
https://bugs.kde.org/show_bug.cgi?id=360017 --- Comment #8 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- No response within one day? You guy seem to be really busy and impatient... Yes, I have seen your comment, but I have neither time nor motivation anymore to use a git version of digikam or to propose a path for that. Instead I will wait until digikam is in the official stable repo of my distribution and use that one. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 360017] build error: opencv_contrib is required but was not found
https://bugs.kde.org/show_bug.cgi?id=360017 Thomas Eschenbacher <thomas.eschenbac...@gmx.de> changed: What|Removed |Added Ever confirmed|0 |1 Resolution|DOWNSTREAM |--- Status|RESOLVED|REOPENED --- Comment #4 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- I have to re-open that topic. I found out that all that trouble was caused by digikam itself! The big bug is that the bootstrap.linux script contains the parameter -DENABLE_OPENCV3=OFF in the cmake command line, _HARD CODED_ !!! and _after_ including the user defineable parameter list ADDITIONAL_CMAKE_FLAGS. So adding -DENABLE_OPENCV3=ON to ADDITIONAL_CMAKE_FLAGS in bootstrap.local is pretty useless! Please fix the bootstrap.linux script to allow overriding _all_ the hardcoded settings and adjust the comments in bootstrap.local ! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 360017] build error: opencv_contrib is required but was not found
https://bugs.kde.org/show_bug.cgi?id=360017 --- Comment #2 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- ok, thanks for the information! You mean that opencv_contrib stuff is really still included in the "opencv" package? (I thougt that stuff has been removed) In that case I will file a bug report against the gentoo package... Just for reference: https://bugs.gentoo.org/show_bug.cgi?id=576384 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 360017] New: build error: opencv_contrib is required but was not found
https://bugs.kde.org/show_bug.cgi?id=360017 Bug ID: 360017 Summary: build error: opencv_contrib is required but was not found Product: digikam Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: thomas.eschenbac...@gmx.de I tried to build yesterday's git version, but it does stop in cmake while checking for opencv. Reproducible: Always Steps to Reproduce: 1. ./bootstrap.local Actual Results: [...] -- First try at finding OpenCV... CMake Error at /usr/share/OpenCV/OpenCVConfig.cmake:232 (message): opencv_contrib is required but was not found Call Stack (most recent call first): core/cmake/modules/MacroOpenCV.cmake:27 (find_package) core/CMakeLists.txt:229 (DETECT_OPENCV) [...] I am currently using media-libs/opencv-3.1.0-r2 (Gentoo Linux), and also tried after downgrading to media-libs/opencv-3.1.0-r1, media-libs/opencv-3.0.0, but with no luck. Also setting ADDITIONAL_CMAKE_FLAGS='-DENABLE_OPENCV3:BOOL=ON', as suggested by a bug report on redhat bugtracker made no difference. Seems that digikam is not aware of the new opencv-3.x at all, I searched my backups about anything related to "opencv_contrib" and I only found things like /usr/lib64/libopencv_contrib.so.2.4.10 - so I conclude that this library does no longer exist in opencv >= v3.0. My current version of "core" is: commit 41b97ecec0703c61bf25e2a8d700908c5da37850 (Date: Wed Mar 2 22:48:15 2016 +0100) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358144] moving images with special characters in the file name does not work
https://bugs.kde.org/show_bug.cgi?id=358144 --- Comment #3 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- Interesting... after this patch I can see what was really wrong: there already are files with the same name! This was not obvious because file names were not shown in the Album view and no trace of an error message came out (before your latest commit). In such a case, where the target file already exists, I would expect a dialog that shows both images as a thumbnail and offers the possibilities to overwrite, skip ore rename the image, just as Dolphin does... Now I moved the images per Dolphin (and renamed them), switched back to digikam, and deleted the sub folder, which was empty now. The result was that digikam crashed with this assertion: QMetaObject::indexOfSignal: signal finished() from Digikam::ActionThreadBase redefined in Digikam::DBJobsThread QMetaObject::indexOfSignal: signal finished() from Digikam::ActionThreadBase redefined in Digikam::DBJobsThread digikam.general: Action Thread run 1 new jobs digikam.general: Data From DBJobsThread is null: true digikam.general: Cancel Main Thread digikam.general: One job is done digikam.general: Using 4 CPU core to run threads QMetaObject::indexOfSignal: signal finished() from Digikam::ActionThreadBase redefined in Digikam::DBJobsThread QMetaObject::indexOfSignal: signal finished() from Digikam::ActionThreadBase redefined in Digikam::DBJobsThread digikam.general: Action Thread run 1 new jobs digikam.general: One job is done digikam.general: Using 4 CPU core to run threads QMetaObject::indexOfSignal: signal finished() from Digikam::ActionThreadBase redefined in Digikam::IOJobsThread digikam.general: Action Thread run 1 new jobs digikam.iojob: DELETING: "/home/user/Bilder/Z600/Z600/" <== here the folder seems to be deleted FILE EXISTS? true IS TO TRASH? true digikam.iojob: Thread Finished digikam.general: One job is done digikam.general: QFileSystemWatcher detected change at "/home/user/Bilder/Z600/Z600/" digikam.general: Detected change, triggering rescan of directory "/home/user/Bilder/Z600/Z600" digikam.general: QFileSystemWatcher detected change at "/home/user/Bilder/Z600/" digikam.general: Detected change, triggering rescan of directory "/home/user/Bilder/Z600/" digikam.database: Starting scan! digikam.database: Removed items: () related items: () digikam.database: Folder does not exist or is not readable: "/home/user/Bilder/Z600/Z600" < yes, see above, I deleted it digikam.general: Using 4 CPU core to run threads QMetaObject::indexOfSignal: signal finished() from Digikam::ActionThreadBase redefined in Digikam::DBJobsThread QMetaObject::indexOfSignal: signal finished() from Digikam::ActionThreadBase redefined in Digikam::DBJobsThread digikam.general: Action Thread run 1 new jobs ASSERT failure in QList::erase: "The specified iterator argument 'it' is invalid", file /usr/include/qt5/QtCore/qlist.h, line 499 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358053] drag and drop across local collections does not do anything
https://bugs.kde.org/show_bug.cgi?id=358053 --- Comment #6 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- Sorry, my mistake! You are right, that test was indeed across different partitions, even different disks (both using btrfs). But with your latest patch it is no longer reproducible here. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358053] drag and drop across local collections does not do anything
https://bugs.kde.org/show_bug.cgi?id=358053 --- Comment #4 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- No, the collections were on the same partition. I tried the latest git commit and now it works! Thanks for fixing it :-) (unfortunately I found out that moving files with special characters does not work too, I will file a new bug report for that...) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 358144] New: moving images with special characters in the file name does not work
https://bugs.kde.org/show_bug.cgi?id=358144 Bug ID: 358144 Summary: moving images with special characters in the file name does not work Product: digikam Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Albums View Assignee: digikam-de...@kde.org Reporter: thomas.eschenbac...@gmx.de image files that contain special characters in the file name cannot be moved Reproducible: Always Steps to Reproduce: 1. within one album, store an image with a special character (or rename on the shell), for example "Picture(1).jpg" 2. try to drag it into another location Actual Results: nothing happens, the file is not moved, the drag operation just does nothing, no debug or error message visible on the console. This sounds related to bug #355256, but I guess it is a different cause, in my case I have file names with only "(number)" at the end and only ASCII characters, so it does not look like an UTF-8 encoding issue. When I rename the files manually on the console, so that they contain no brackets anymore, I can move them as expected, so there is not problem with permissions or so. I also cross-checked and renamed a file back, to "Picture(1).jpg" and it was no longer movable. AFAIR it is not drag specific, also cut does not work. BTW: the thumbnail engine seems to have no problem with these files, thumbnails are shown -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357944] New: wrong encoded collection paths after upgrade from digikam v4.x
https://bugs.kde.org/show_bug.cgi?id=357944 Bug ID: 357944 Summary: wrong encoded collection paths after upgrade from digikam v4.x Product: digikam Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: setup Assignee: digikam-de...@kde.org Reporter: thomas.eschenbac...@gmx.de This seems to be an issue when coming from an older installation, digikam-4.x: Reproducible: Always Steps to Reproduce: 1. take a system with an old digikam-4 configuration 2. make sure you don't have a ~/.config/digikamrc 3. start digikam v5 4. in the wizard, when asked for location of your collection, enter some path 5. enter the settings dialog and look at the list of local collections Actual Results: The location I entered in the wizard is shown correctly. But the locations of the local collections that I have used for digikam-4 all are encoded, as for example "%2Fhome%2Fuser%2FPictures". Expected Results: The paths of the old installation should be migrated, with proper encoding. This seems to be relevant only when migrating, when I add the locations manually again and remove the wrong encoded ones it stays ok (no toggle effect, settings stay as they are). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector
https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #20 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- short update: now, after waiting for a very very long time, it shows Albums and Images again! It seems that it had to do it's job about face recognition in background, without any visible hint for the user what is going on. It was just luck that I recognized this, because I started it from the console, normally I would have given up already, called the "useless" and killed it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector
https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #19 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- Thanks for the patch! It does not show any of my albums and I cannot see any picture anywhere, so the application is pretty useless at the moment, but at least it starts and no longer crashes! :-) The "Album" tree view (or whatever that widget on the left side is), is nearly empty, it contains only the string "Albums" with something that looks like a generic "image" icon at the left. Nothing else, nothing to expand or collapse... Another odd thing: it seems that the settings have not been properly migrated, the strings to my albums were URL encoded or so, the edit fields showed strings like "%2Fhome%2Fuser%2FPictures". After I added my local collection manually again, I can see in the console debug output that it iterates over my complete collection and tries to do some face detection. But still nothing in the Albums list. BTW: Additionally face detection seems to have problems with special characters (unicode) in file names, it shows "file system" errors or file "format not recognized" error for these files, maybe something with file name encoding or conversion QFile-name <-> QUrl goes wrong (I also had these things in Kwave). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 323431] VEX: unhandled instruction bytevex amd64->IR: 0x8F 0xE8 0x78 0xA2 0xC1 0x40 0xC5 0xFB
https://bugs.kde.org/show_bug.cgi?id=323431 --- Comment #5 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- I am affected by the same here: > uname -a Linux lisa 4.3.3-gentoo #1 SMP PREEMPT Fri Jan 8 07:01:39 CET 2016 x86_64 AMD A10-7870K Radeon R7, 12 Compute Cores 4C+8G AuthenticAMD GNU/Linux > cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 56 model name : AMD A10-7870K Radeon R7, 12 Compute Cores 4C+8G stepping: 1 cpu MHz : 1700.000 cache size : 2048 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext arat cpb hw_pstate proc_feedback npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold vmmcall fsgsbase bmi1 xsaveopt bugs: fxsave_leak sysret_ss_attrs Any news about this bug? -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 323431] VEX: unhandled instruction bytevex amd64->IR: 0x8F 0xE8 0x78 0xA2 0xC1 0x40 0xC5 0xFB
https://bugs.kde.org/show_bug.cgi?id=323431 Thomas Eschenbacher <thomas.eschenbac...@gmx.de> changed: What|Removed |Added CC||thomas.eschenbac...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector
https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #13 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- sorry, that is not possible. Valgrind is broken and unusable too, crashes quite early due to this bug: https://bugs.kde.org/show_bug.cgi?id=323431 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 323431] VEX: unhandled instruction bytevex amd64->IR: 0x8F 0xE8 0x78 0xA2 0xC1 0x40 0xC5 0xFB
https://bugs.kde.org/show_bug.cgi?id=323431 --- Comment #6 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- using valgrind-3.11.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector
https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #11 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- No, debug symbols (as you get per -g in the CFLAGS) are necessary for a usable backtrace but not sufficient. You need to get theQt5 libs compiled "QT_DEBUG" defined and "QT_NO_DEBUG" _not_ defined, the same way you do when you want a KDE application to evaluate Q_ASSERT checks. See /usr/include/qt5/QtCore/qglobal.h ~line 665, where Q_ASSERT is handled. Normally Qt packages from distributions are compiled without QT_DEBUG and thus silently ignore such kinds of error situations. Maybe you have more luck by using a "developer build" of Qt and force digikam to use it by setting LD_LIBRARY_PATH into it. (see http://doc.qt.io/qt-5/configure-options.html and use the option "-developer-build" as suggested) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357577] New: crashes after splash screen with ASSERT failure in QVector
https://bugs.kde.org/show_bug.cgi?id=357577 Bug ID: 357577 Summary: crashes after splash screen with ASSERT failure in QVector Product: digikam Version: 5.0.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: thomas.eschenbac...@gmx.de Created attachment 96472 --> https://bugs.kde.org/attachment.cgi?id=96472=edit gdb backtrace I compiled digikam (today's latest source from git), but soon after showing the splash screen it crashes with an assertion in Qt. This also happens with a new dummy user account that did not use digikam-4 before and thus has no album, no database etc. git commit: bb7b7ef566a1b9606f35b237ddc4b3267299209f Gentoo Linux @ x86_64 gcc-4.8.5, qt-5.5.1 I started digikam with gdb and attached the backtrace. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector
https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #1 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- Created attachment 96473 --> https://bugs.kde.org/attachment.cgi?id=96473=edit console output up to the crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector
https://bugs.kde.org/show_bug.cgi?id=357577 Thomas Eschenbacher <thomas.eschenbac...@gmx.de> changed: What|Removed |Added CC||thomas.eschenbac...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector
https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #3 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- as I wrote above: Qt-5.5.1 It is 100% reproducible here. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 357577] crashes after splash screen with ASSERT failure in QVector
https://bugs.kde.org/show_bug.cgi?id=357577 --- Comment #6 from Thomas Eschenbacher <thomas.eschenbac...@gmx.de> --- how can I get this source version you are talking about? I followed the instructions on the project homepage, which lead me to this repo: > git remote -v origin git://anongit.kde.org/digikam-software-compilation (fetch) origin git://anongit.kde.org/digikam-software-compilation (push) but your change is not visible there. I tried to "git remote set-url origin git://anongit.kde.org/digikam.git" but that has lead to a big mess, had to restore the local repo from backup. What should I do now? -- You are receiving this mail because: You are watching all bug changes.
