[digikam] [Bug 382002] Lazy synchronization not working
https://bugs.kde.org/show_bug.cgi?id=382002 --- Comment #3 from Anders Lund <and...@alweb.dk> --- I can confirm the rescanning, which I believe is completely unnessecary in this case. I am not running digikam in a terminal, so I don't know what digikam prints. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 328396] korganizer/akonadi fails to display calendars
https://bugs.kde.org/show_bug.cgi?id=328396 --- Comment #6 from Anders Lund <and...@alweb.dk> --- Due to the instability, I rely very little on korganizer these days, but I believe the situation has improved, since it was a long time since I experienced my calendars being completely dropped. På Fri, 23 Jun 2017 19:58:29 + Denis Kurz <bugzilla_nore...@kde.org> skrev: > https://bugs.kde.org/show_bug.cgi?id=328396 > > Denis Kurz <kde...@posteo.de> changed: > >What|Removed |Added > > Resolution|--- |WAITINGFORINFO > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #5 from Denis Kurz <kde...@posteo.de> --- > This bug has never been confirmed for a KDE PIM version that is based > on KDE Frameworks (5.x). Those versions differ significantly from the > old 4.x series. Therefore, I plan to close it in around two or three > months. In the meantime, it is set to WAITINGFORINFO to give > reporters the oportunity to check if it is still valid. As soon as > someone confirms it for a recent version (at least 5.1, ideally even > more recent), I'll gladly reopen it. > > Please understand that we lack the manpower to triage bugs reported > for versions almost two years beyond their end of life. > -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 351803] IMAP stopped working
https://bugs.kde.org/show_bug.cgi?id=351803 --- Comment #5 from Anders Lund <and...@alweb.dk> --- I stopped using kmail some months ago, as it became 100% unusable. I think there is no way forward for kmail, as long as akonadi is used. Any non-akonadi mail client I tried works fine. As did kmail in pre-akonadi times. Akonadi is not usable for mail, in my configuration. I believe it has to do with the mail server my mail service offers. I have heard that it works for some, though. På Fri, 23 Jun 2017 20:21:13 + Denis Kurz <bugzilla_nore...@kde.org> skrev: > https://bugs.kde.org/show_bug.cgi?id=351803 > > Denis Kurz <kde...@posteo.de> changed: > >What|Removed |Added > > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #4 from Denis Kurz <kde...@posteo.de> --- > This bug has never been confirmed for a Kontact version that is based > on KDE Frameworks, except possibly a Technology Preview version > 5.0.x. Those versions differ significantly from the old 4.x series. > Therefore, I plan to close it in around two or three months. In the > meantime, it is set to WAITINGFORINFO to give reporters the > opportunity to check if it is still valid. As soon as someone > confirms it for a recent version (at least 5.1, ideally even more > recent), I'll gladly reopen it. > > Please understand that we lack the manpower to triage bugs reported > for versions almost two years beyond their end of life. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 305918] File->Save changes does not always hide the original
https://bugs.kde.org/show_bug.cgi?id=305918 --- Comment #10 from Anders Lund <and...@alweb.dk> --- I have changed my workflow completely, I am not using the built-in editor any longerm nor am I using grouping. For me, this issue can be closed. På Thu, 30 Nov 2017 09:30:29 + <bugzilla_nore...@kde.org> skrev: > https://bugs.kde.org/show_bug.cgi?id=305918 > > --- Comment #9 from caulier.gil...@gmail.com --- > Please update this entry from bugzilla with current 5.8.0 pre-release > bundle to see if problem remain. > > https://files.kde.org/digikam/ > > Thanks in advance > > Gilles Caulier > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398532] New: Setting margins does not work
https://bugs.kde.org/show_bug.cgi?id=398532 Bug ID: 398532 Summary: Setting margins does not work Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Export-PrintCreator Assignee: digikam-bugs-n...@kde.org Reporter: and...@alweb.dk Target Milestone: --- When using print creator, setting margins in the "page properties" dialog in the page layout widget is not applied to neither pdf or printer output. Pdfs always have no margins, except if photo is not cropped, printer have the printers minimal margin if borderless is not enabled. Margins are correctly shown as set in the dialog show when pressing "properties" in the dialog appearing in the final "render printing" step of the wizard. The tool is missing a proper page preview, it is not possible to see margins in the current preview either. My printer is a Epson Stylus 1500W, with epson drivers (but as said, the problem also exist when printing to pdf). -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393271] New: adding -w to the desktop file command does not work correctly
https://bugs.kde.org/show_bug.cgi?id=393271 Bug ID: 393271 Summary: adding -w to the desktop file command does not work correctly Product: Falkon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: and...@alweb.dk Target Milestone: --- I copied falkons .desktop file to ~/.local/share/applications/ and added -w to the command, to always make a link open in a new window, but it does not work. Falkon opens a blank window, but the link is STILL hijacking a random falkon window, making it difficult to find and also mix som link into my well organized window. This is for when I click a link in a mail, or similar. Please fix :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368838] plasmashell memory leak when slideshow is used for wallpaper/media frame/photo widget
https://bugs.kde.org/show_bug.cgi?id=368838 --- Comment #82 from Anders Lund <and...@alweb.dk> --- fredag den 23. marts 2018 14.38.09 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=368838 > > --- Comment #81 from Alexander Schlarb <alexander-kde@ninetailed.ninja> --- > > @Nate Graham: > > I'm also wondering if there's any disadvantage to always using the > > threaded render loop. Alexander, would you be able to run with it for a > > while and report any regressions, if any? > I've been running my entire KDE Desktop session with > `QSG_RENDER_LOOP=threaded` set in `.pam_environment` for the last month and > it only had an effect on Plasma's (invisible) memory usage. Everything else > is working as before (i.e.: KWin still has its share of issues > –particularily on Wayland – but it's not worse than before either). Thanks for the tip, I'm trying that, so far witout any problems :) --- Kindly, Anders -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392175] New: shortcut conflict with ctrl + q
https://bugs.kde.org/show_bug.cgi?id=392175 Bug ID: 392175 Summary: shortcut conflict with ctrl + q Product: systemsettings Version: 5.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcmshell Assignee: kdelibs-b...@kde.org Reporter: and...@alweb.dk Target Milestone: --- I can not quit systemsettings by pressing CTRL + Q, a dialog turns up to tell me there is a conflict, and given systemsettings does not provide settings for its own shortcuts, this is not fixable (and it would still be a bug!) Fully up to date archlinux. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392174] Shared memory usage grows infinately
https://bugs.kde.org/show_bug.cgi?id=392174 --- Comment #2 from Anders Lund <and...@alweb.dk> --- torsdag den 22. marts 2018 15.26.20 CET skrev du: > https://bugs.kde.org/show_bug.cgi?id=392174 > > --- Comment #1 from David Edmundson <k...@davidedmundson.co.uk> --- > Do you have a slideshow wallpaper? Yes. Good catch :) I love my slideshow wallpaper, though :) --- kindly, Anders -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392176] ALT + . shortcut conflict
https://bugs.kde.org/show_bug.cgi?id=392176 --- Comment #2 from Anders Lund <and...@alweb.dk> --- torsdag den 22. marts 2018 14.55.48 CET skrev du: > https://bugs.kde.org/show_bug.cgi?id=392176 > > Kai Uwe Broulik <k...@privat.broulik.de> changed: > >What|Removed |Added > > CC||k...@privat.broulik.de > > --- Comment #1 from Kai Uwe Broulik <k...@privat.broulik.de> --- > Alt+period has been used for toggling hidden files for ages. There is still a conflict. It can be fixed by changing either shortcut, but I suggest that one of those defaults are changed - if not in dolphin, then in the window switcher :-) --- kindly, Anders -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392174] New: Shared memory usage grows infinately
https://bugs.kde.org/show_bug.cgi?id=392174 Bug ID: 392174 Summary: Shared memory usage grows infinately Product: plasmashell Version: 5.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: and...@alweb.dk CC: plasma-b...@kde.org Target Milestone: 1.0 Durint the last week (possibly since last update) I have to restart plasmashell once in a while, because it uses all my memory, and production apps becomes unusable due to that. I have not experienced this before with plasmashell. I use fully updated archlinux. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392176] ALT + . shortcut conflict
https://bugs.kde.org/show_bug.cgi?id=392176 --- Comment #6 from Anders Lund <and...@alweb.dk> --- torsdag den 22. marts 2018 16.44.23 CET skrev du: > https://bugs.kde.org/show_bug.cgi?id=392176 > > --- Comment #5 from Nate Graham <n...@kde.org> --- > I guess you'll need to find a window switching shortcut that's both > type-able given your keyboard layout, and that doesn't conflict with > Dolphin. Yep, sorry for disturbing with that one :\ -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392175] shortcut conflict with ctrl + q
https://bugs.kde.org/show_bug.cgi?id=392175 --- Comment #2 from Anders Lund <and...@alweb.dk> --- torsdag den 22. marts 2018 16.30.33 CET skrev du: > https://bugs.kde.org/show_bug.cgi?id=392175 > > Nate Graham <n...@kde.org> changed: > >What|Removed |Added > > CC||n...@kde.org > Resolution|--- |WORKSFORME > Status|UNCONFIRMED |RESOLVED > > --- Comment #1 from Nate Graham <n...@kde.org> --- > Works fine for me with a clean KDE Neon dev unstable, which tracks git > master. > > Given your other recent shortcut conflict bug, I suspect there's some local > misconfiguration here, or else an issue with Arch's packages. I can not figure out how to reset this if there is any change. This problem have occured recently. I don't think arch packager changes shortcuts. CTRL + Q is listed as the default shortcut for "quit application" in the shortcuts module in systemsettings, and there is no appearent way to change this for systemsettings itself. Where would I look for a way to fix this? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392176] New: ALT + . shortcut conflict
https://bugs.kde.org/show_bug.cgi?id=392176 Bug ID: 392176 Summary: ALT + . shortcut conflict Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: and...@alweb.dk CC: elvis.angelac...@kde.org Target Milestone: --- In dolphin, I should be able to toggle the display of hidden files using ALT + ., however, this shortcut is used by the desktop window switcher I believe for switching between windows of the current app. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392175] shortcut conflict with ctrl + q
https://bugs.kde.org/show_bug.cgi?id=392175 --- Comment #4 from Anders Lund <and...@alweb.dk> --- torsdag den 22. marts 2018 16.51.42 CET skrev du: > https://bugs.kde.org/show_bug.cgi?id=392175 > > --- Comment #3 from Nate Graham <n...@kde.org> --- > What is it actually conflicting with? Does it reproduce with a new user > account? I *assume* it is in conflict with the default shortcut for quit. But as there is no visual representation of any shortcuts regarding systemsettings, or any file that I can find defining any, I don't know how to find out, except maybe for examining the source code, which I really do not want to do. The conflict is new, didn't use to happen during my 20+ years as a KDE user. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392174] Shared memory usage grows infinately
https://bugs.kde.org/show_bug.cgi?id=392174 --- Comment #5 from Anders Lund <and...@alweb.dk> --- torsdag den 22. marts 2018 17.05.18 CET skrev du: > https://bugs.kde.org/show_bug.cgi?id=392174 > > --- Comment #4 from Nate Graham <n...@kde.org> --- > What version of Qt do you have? 5.10 --- Kindly, Anders -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 392176] ALT + . shortcut conflict
https://bugs.kde.org/show_bug.cgi?id=392176 --- Comment #4 from Anders Lund <and...@alweb.dk> --- torsdag den 22. marts 2018 16.28.54 CET skrev du: > https://bugs.kde.org/show_bug.cgi?id=392176 > > Nate Graham <n...@kde.org> changed: > >What|Removed |Added > > CC||n...@kde.org > Resolution|--- |INVALID > Status|UNCONFIRMED |RESOLVED > > --- Comment #3 from Nate Graham <n...@kde.org> --- > Switching between windows of the current app is bound to Alt+` by default. > Either you or your distro decided to change this, which causes a conflict. > Not Dolphin's fault. If it was you, change the window switching shortcut to > something else. :) If it was your distro, report it to them. I have not changed it that I remember. I run KDE in danish, and the suggested shortcut is about untypable (requires hitting a key twice), so I may have. Goes for both ~ and ` - not usable really for this type of action on danish keyboard layout. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 251164] Copy shortcut does not work
https://bugs.kde.org/show_bug.cgi?id=251164 --- Comment #7 from Anders Lund <and...@alweb.dk> --- I believe kirigami was not even thought of at the time of reporting - but nice if a port can solve this ;) Anders -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 392175] shortcut conflict with ctrl + q
https://bugs.kde.org/show_bug.cgi?id=392175 --- Comment #6 from Anders Lund <and...@alweb.dk> --- torsdag den 22. marts 2018 17.19.36 CET skrev du: > https://bugs.kde.org/show_bug.cgi?id=392175 > > --- Comment #5 from Nate Graham <n...@kde.org> --- > Does it reproduce with a new user account? Yes. Screenshot here: http://nc.alweb.dk/index.php/s/SDkfqscZ7EVS6L8 --- Kindly, Anders -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 307152] konqueror attempts to open mailto: links with uninstalled application
https://bugs.kde.org/show_bug.cgi?id=307152 Anders Lund changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from Anders Lund --- I think this has become obsolete. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398885] New: Collections on removable media does not work
https://bugs.kde.org/show_bug.cgi?id=398885 Bug ID: 398885 Summary: Collections on removable media does not work Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: and...@alweb.dk Target Milestone: --- I have collections on various usb harddisks, but digikam is not handling this in a fashion that is even close to working. If I plug the media in while digikam is running, it does not react at all. The collections are not visible when the disk is pluggen in. If I plug the disk in, and then start digikam, it starts a process that takes near forever, recataloguing (I think) the collection. This USED to work, but does not anymore. Adding a collection on a removable media is not at all easy either, the file dialog offered does not know about removable media, and the only way is to browse to the mount directory. Please use a functional file dialog tor this purpose (ie the KDE one!) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398885] Collections on removable media does not work
https://bugs.kde.org/show_bug.cgi?id=398885 --- Comment #3 from Anders Lund --- If I try to add a collection on a network share, the behavior is the same, broken useless crab. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398885] Collections on removable media does not work
https://bugs.kde.org/show_bug.cgi?id=398885 --- Comment #2 from Anders Lund --- This is what happens: I add a collection on a usb hd. Digikam scans for an hour. I unmount the disk, and digikam removes the entry from the Albums view. In the settings, the collection is now no longer listed under collections in removable media, but under local collections. If I plug in the disk, nothing happens. If I quit digikam and start it with the disk mounted, digikam scans for one hour. It is 100% broken. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 215536] Akonadi is 100% useless after updating to 1.2
https://bugs.kde.org/show_bug.cgi?id=215536 Anders Lund changed: What|Removed |Added Resolution|WAITINGFORINFO |UNMAINTAINED Status|NEEDSINFO |RESOLVED --- Comment #8 from Anders Lund --- This bug is from 2009/10, and probably not relevant any longer. I'm nor really using kaddressbook any longer, but the parts of akonadi I do use mostly works. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398885] Collections on removable media does not work
https://bugs.kde.org/show_bug.cgi?id=398885 --- Comment #6 from Anders Lund --- I'm on archlinux, fully updated, so digikam is latest release version. It sounds encouraging that it works for you Maik. I have one suspicion about it, namely that it has to do with how media are recognized. Mine are listed as /dev/sd* in the mount list, but earlier they were listed by UUIDs. Maybe that is the root of the problem. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 323584] Konqueror crashes when entering an æ, ø or å as the third letter in the address bar
https://bugs.kde.org/show_bug.cgi?id=323584 Anders Lund changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #4 from Anders Lund --- This is outdated, as far as I am concerned. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398885] Collections on removable media does not work
https://bugs.kde.org/show_bug.cgi?id=398885 Anders Lund changed: What|Removed |Added Version|unspecified |5.9.0 --- Comment #8 from Anders Lund --- 5.9.0 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 259949] Kmail does not use all addressbooks for autocompletion
https://bugs.kde.org/show_bug.cgi?id=259949 --- Comment #396 from Anders Lund --- I agree, it should be closed. Something like "obsolete" is missing :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402167] New: Dolphin is unusable, because it has a response time of 30+ seconds
https://bugs.kde.org/show_bug.cgi?id=402167 Bug ID: 402167 Summary: Dolphin is unusable, because it has a response time of 30+ seconds Product: dolphin Version: 18.12.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: and...@alweb.dk CC: elvis.angelac...@kde.org Target Milestone: --- Starting Dolphin, or clicking inside it when I have been lucky/patient enough to get a dolphin window, has a HUUGGE response time, making dolphin practisally unusable. STEPS TO REPRODUCE 1. start dolphin any way (konsole, krunner, menu). 2. nothing happens for a VERY long time 3. coffee break after each click. Never try to click an estra time, it is PUNISHED. OBSERVED RESULT Nothing happens within a resonable time EXPECTED RESULT usable app. SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest, fully updated archlinux (available in About System) KDE Plasma Version: latest KDE Frameworks Version: latest Qt Version: latest ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402167] Dolphin is unusable, because it has a response time of 30+ seconds
https://bugs.kde.org/show_bug.cgi?id=402167 Anders Lund changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Anders Lund --- This seemed to go away. Maybe the indexer is updating, meanwhile preventing dolphin to work properly? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402979] New: Can't rename album in collection on NTFS usb drive
https://bugs.kde.org/show_bug.cgi?id=402979 Bug ID: 402979 Summary: Can't rename album in collection on NTFS usb drive Product: digikam Version: 5.9.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: and...@alweb.dk Target Milestone: --- Trying to rename an album which is in a collection on a NTFS usb drive, I get an error dialog saying "can't rename album". The album is renamed in digikam, and if I navigate away from it and back, it shows empty. Renaming it back causes the same error dialog, though the album name is changed again, and now images becomes visible. The drive is correctly mounted read-write, and I can rename albums in dolphin, but that of cause means loss of metadata. STEPS TO REPRODUCE 1. mount a NTFS USB drive with a collection 2. go to an album on it, and press SHIFT + F2, enter a new name and hit RETURN 3. OBSERVED RESULT Error dialog, read above. EXPECTED RESULT things to work. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: latest, archlinux fully up to date (available in About System) KDE Plasma Version: as above KDE Frameworks Version: as above Qt Version: as above ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398532] Setting margins does not work
https://bugs.kde.org/show_bug.cgi?id=398532 --- Comment #3 from Anders Lund --- Another observation: printing with gwenview works in this respect. The printing dialog there is similar to the digikam one. The digikam print tool have a "page layout" page, where it is possible to select printer and set margins, and the margins are transferred to the printer properties dialog, but printer choice is not, I find this a bit confusing. Somehow, something goes wrong after setting the printer properties and hitting "print", in the digikam version. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398532] Setting margins does not work
https://bugs.kde.org/show_bug.cgi?id=398532 --- Comment #2 from Anders Lund --- I'm running fully updated archlinux. Digikam 5.9.0 KDE 5.50 Qt 5.11.1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404690] There is an unwanted bar in the left screen edge in full screen view
https://bugs.kde.org/show_bug.cgi?id=404690 --- Comment #3 from Anders Lund --- I believe my Qt version is in the report, but it is 5.12.1 :) --- fredag den 22. februar 2019 11.48.25 CET skrev du: > https://bugs.kde.org/show_bug.cgi?id=404690 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > Component|general |Thumbs-BarView > CC||caulier.gil...@gmail.com > > --- Comment #1 from caulier.gil...@gmail.com --- > Problem already reported. It's due to a bug in Qt, not digiKam... > > Which Qt version do you use ? Look in Help/Component info dialog for > details. > > Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 404690] New: There is an unwanted bar in the left screen edge in full screen view
https://bugs.kde.org/show_bug.cgi?id=404690 Bug ID: 404690 Summary: There is an unwanted bar in the left screen edge in full screen view Product: digikam Version: 6.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: and...@alweb.dk Target Milestone: --- Since digikam 6.0, I get a undesired bar on the left screen side in fullscreen view, both images and thumbs. It looks like a UI element, like a splitter. STEPS TO REPRODUCE 1. Enter full screen mode OBSERVED RESULT There is a unwanted bar on the left screen edge EXPECTED RESULT No unwanted bar on left screen edge SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.55 Qt Version: 5.12.1 ADDITIONAL INFORMATION Using Breeze UI style -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405423] Can't change default search engine
https://bugs.kde.org/show_bug.cgi?id=405423 --- Comment #4 from Anders Lund --- torsdag den 14. marts 2019 11.31.53 CET skrev du: > https://bugs.kde.org/show_bug.cgi?id=405423 > > --- Comment #3 from David Rosca --- > Yes, private windows have temporary read-only settings. In that case, it would be smart to provide that information, to help the user :) I use mostly private windows, really mostly to protect myself against tracking. I only use the default window in cases where the private window does not work, a few public websites in DK primarily. For privacy, siloing all tabs/windows would be really nice, that is never share cookies/web storage between sites, and delete it all at window closedown - but that is probably out of topic here :) -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405423] Can't change default search engine
https://bugs.kde.org/show_bug.cgi?id=405423 --- Comment #2 from Anders Lund --- torsdag den 14. marts 2019 10.36.18 CET skrev du: > https://bugs.kde.org/show_bug.cgi?id=405423 > > --- Comment #1 from David Rosca --- > Address bar by default follows search engines set in web search bar. To > change this behavior, check Preferences -> Tabs -> Address Bar -> Search > with Default Engine. Yes, but it does not appear to work. In one window, if I set the default search engine in preferences, it still searches with the "old" engine. The window is private, maybe that influences things? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405424] New: Add ability to allow ads in certain sites, in adblocker addon
https://bugs.kde.org/show_bug.cgi?id=405424 Bug ID: 405424 Summary: Add ability to allow ads in certain sites, in adblocker addon Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: extensions Assignee: now...@gmail.com Reporter: and...@alweb.dk Target Milestone: --- It would be nice to be able to make exceptions for specifik urls in adblocker, like in other browsers. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405423] New: Can't change default search engine
https://bugs.kde.org/show_bug.cgi?id=405423 Bug ID: 405423 Summary: Can't change default search engine Product: Falkon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: and...@alweb.dk Target Milestone: --- SUMMARY I tried to change the default search engine, but it did not take effect until I removed the former default search engine. STEPS TO REPRODUCE 1. 2. 3. 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 405424] Add ability to allow ads in certain sites, in adblocker addon
https://bugs.kde.org/show_bug.cgi?id=405424 Anders Lund changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 403851] New: KMail often chokes, and have to be restarted
https://bugs.kde.org/show_bug.cgi?id=403851 Bug ID: 403851 Summary: KMail often chokes, and have to be restarted Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: and...@alweb.dk Target Milestone: --- Very often, sometimes many times a day, kmail appears to stop working. It does not fetch new mail, mail can not be sent, and/or mail can not be displayed. STEPS TO REPRODUCE 1. Use KMail for a while. suspend the system a few times. 2. At some point, get suspcious because you do not get mail 3. Get annoyed, because suddenly kmail will not display any mail, instead the infamous BSOD appears whenever a mail header is clicked. If a header is doubleclidked, a infinite "fetching message ..." progress dialog is spawned. OBSERVED RESULT Kmail is unstable, not safe to use. The cure is to quit (sometimes with a crash), restart akonadi wait a bit and launch kmail again. Sometimes this needs to be repeated. EXPECTED RESULT Working mail client. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 18.12.1 Qt Version: 5.12 ADDITIONAL INFORMATION I use a laptop, which is closed (=> suspended) often. I suspect that the problem is more likely to happen after waking up after a suspension. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408974] notifictaion spam from SMS messates on my phone
https://bugs.kde.org/show_bug.cgi?id=408974 --- Comment #1 from Anders Lund --- KInfoCecnter says: KDE-Plasma: 5.16.1 KDE-Frameworks: 5.59.0 Qt: 5.12.4 Linux-kernel: 5.1.12-arch1-1-ARCH fredag den 21. juni 2019 08.49.37 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=408974 > > Bug ID: 408974 >Summary: notifictaion spam from SMS messates on my phone >Product: kdeconnect >Version: 1.3.4 > Platform: Other > OS: Linux > Status: REPORTED > Severity: normal > Priority: NOR > Component: common > Assignee: albertv...@gmail.com > Reporter: and...@alweb.dk > Target Milestone: --- > > SUMMARY I get 10 copies of SMS messages from my phone on my laptop screen > with latest plasma > > > STEPS TO REPRODUCE > 1. someone sends me a SMS > 2. > 3. > > OBSERVED RESULT > I see 10 copies of the SMS on the plasma notification system > > EXPECTED RESULT > One copy of the SMS on the plasma notification system > > > SOFTWARE/OS VERSIONS > Windows: > macOS: > Linux/KDE Plasma: Archlinux, fully updated > (available in About System) > KDE Plasma Version: > KDE Frameworks Version: > Qt Version: > > I can not figure out which KDE component is which version. Latest released > everything. > > ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408974] New: notifictaion spam from SMS messates on my phone
https://bugs.kde.org/show_bug.cgi?id=408974 Bug ID: 408974 Summary: notifictaion spam from SMS messates on my phone Product: kdeconnect Version: 1.3.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: and...@alweb.dk Target Milestone: --- SUMMARY I get 10 copies of SMS messages from my phone on my laptop screen with latest plasma STEPS TO REPRODUCE 1. someone sends me a SMS 2. 3. OBSERVED RESULT I see 10 copies of the SMS on the plasma notification system EXPECTED RESULT One copy of the SMS on the plasma notification system SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Archlinux, fully updated (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: I can not figure out which KDE component is which version. Latest released everything. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 226905] Add support for mime-type sections to .kateconfig files
https://bugs.kde.org/show_bug.cgi?id=226905 --- Comment #4 from Anders Lund --- tirsdag den 14. maj 2019 15.15.50 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=226905 > > --- Comment #3 from Dominik Haumann --- > It's already supported for a long time: > https://kate-editor.org/2006/02/09/kateconfig-files/ > > So this bug from Anders is fixed, or? I think so, I wondered why it is still active! :) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408974] notifictaion spam from SMS messates on my phone
https://bugs.kde.org/show_bug.cgi?id=408974 --- Comment #4 from Anders Lund --- I just counted almost 30 dialogs. There is only one representation if I display the notifications. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408974] notifictaion spam from SMS messates on my phone
https://bugs.kde.org/show_bug.cgi?id=408974 --- Comment #7 from Anders Lund --- Thank you Nicolas, great news! :) -- mandag den 29. juli 2019 23.16.35 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=408974 > > Nicolas Fella changed: > >What|Removed |Added > > Status|REPORTED|RESOLVED > Resolution|--- |FIXED > CC||nicolas.fe...@gmx.de > > --- Comment #6 from Nicolas Fella --- > This should be fixed in version 1.12.93 of the Android app -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 410283] Missing warning when deleting images from media
https://bugs.kde.org/show_bug.cgi?id=410283 --- Comment #6 from Anders Lund --- Thank you very much Maik! :) --- søndag den 28. juli 2019 13.02.12 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=410283 > > Maik Qualmann changed: > >What|Removed |Added > > Latest Commit||https://invent.kde.org/kde/ >||digikam/commit/0f91c665d3d0 >||b23d0b30a169ce3d27ef1b92176 >||c > > Status|REPORTED|RESOLVED > Resolution|--- |FIXED >Version Fixed In||6.2.0 > > --- Comment #5 from Maik Qualmann --- > Git commit 0f91c665d3d0b23d0b30a169ce3d27ef1b92176c by Maik Qualmann. > Committed on 28/07/2019 at 11:01. > Pushed by mqualmann into branch 'master'. > > fix "dont ask again" logic in the DMessageBox > FIXED-IN: 6.2.0 > > M +2-1NEWS > M +8-6core/libs/dialogs/dmessagebox.cpp > > https://invent.kde.org/kde/digikam/commit/0f91c665d3d0b23d0b30a169ce3d27ef1b > 92176c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 410283] Missing warning when deleting images from media
https://bugs.kde.org/show_bug.cgi?id=410283 --- Comment #4 from Anders Lund --- When I find time, I can try moving digikamrc, to see if there is really a warning. I believe not, as I did not disable it. THERE SHOULD BE ONE. And frankly, it should not be possible to turn it off, for deleting files. --- lørdag den 27. juli 2019 18.33.39 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=410283 > > --- Comment #3 from Anders Lund --- > I can not find anything related in digikamrc, except maybe this, which is > not clearly understandable for me: > Do Import Export operations on all=2 > > --- > > lørdag den 27. juli 2019 18.25.25 CEST skrev du: > > https://bugs.kde.org/show_bug.cgi?id=410283 > > > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > > > -- > > -- CC||caulier.gil...@gmail.com > > > > --- Comment #1 from caulier.gil...@gmail.com --- > > The warning dialog exists already but can be disabled if the Q have been > > already ask to user previously and if the option to hide the dialog have > > been turned on. > > > > This option set on a new line in digikamrc configuration file to remember > > the user choice. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 410283] New: Missing warning when deleting images from media
https://bugs.kde.org/show_bug.cgi?id=410283 Bug ID: 410283 Summary: Missing warning when deleting images from media Product: digikam Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Import-MainView Assignee: digikam-bugs-n...@kde.org Reporter: and...@alweb.dk Target Milestone: --- I acdentially pressed "delete selected" instead of "import selected", and WOSH - wonderful, important images deleted. Why isn't there a warning STEPS TO REPRODUCE 1. Connect a media with important, wonderful photos, like a card reader with a card or a camera. 2. Make a selection 3. By mistake, press "delete selected" instead of "import selected", because you are on an unstable platform, like a boat. OBSERVED RESULT ARRRGH. Photos DELETED EXPECTED RESULT A polite warning, if I really want to delete unimported photos. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Archlinux, fully up to date. (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.
[digikam] [Bug 410283] Missing warning when deleting images from media
https://bugs.kde.org/show_bug.cgi?id=410283 --- Comment #2 from Anders Lund --- This digikam installation is quite new, and I am sure I did not cancel the warning. I NEVER delete images from media using digikam, I ALWAYS use the format function in my camera. lørdag den 27. juli 2019 18.25.25 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=410283 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > CC||caulier.gil...@gmail.com > > --- Comment #1 from caulier.gil...@gmail.com --- > The warning dialog exists already but can be disabled if the Q have been > already ask to user previously and if the option to hide the dialog have > been turned on. > > This option set on a new line in digikamrc configuration file to remember > the user choice. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 410283] Missing warning when deleting images from media
https://bugs.kde.org/show_bug.cgi?id=410283 --- Comment #3 from Anders Lund --- I can not find anything related in digikamrc, except maybe this, which is not clearly understandable for me: Do Import Export operations on all=2 --- lørdag den 27. juli 2019 18.25.25 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=410283 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > CC||caulier.gil...@gmail.com > > --- Comment #1 from caulier.gil...@gmail.com --- > The warning dialog exists already but can be disabled if the Q have been > already ask to user previously and if the option to hide the dialog have > been turned on. > > This option set on a new line in digikamrc configuration file to remember > the user choice. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 408974] notifictaion spam from SMS messates on my phone
https://bugs.kde.org/show_bug.cgi?id=408974 --- Comment #3 from Anders Lund --- søndag den 7. juli 2019 00.41.10 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=408974 > > unlogic changed: > >What|Removed |Added > > CC||un_lo...@rambler.ru > > --- Comment #2 from unlogic --- > Have you tried to filter out notifications from your Android SMS app? It's > under Plug-ins settings Notifications sync. Unflag your SMS app of choice. No, but of cause that could be a workaround. However, seeing SMS messages in notifications is a valuable feature - when it works :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414022] New windows are placed behind active window
https://bugs.kde.org/show_bug.cgi?id=414022 --- Comment #2 from Anders Lund --- AFAICT X, as I did not do anything in particular to run wayland, and of course kwin_x11 is running. I updated after filing the issue, and got kde framworks 5.64, and the issue appears to affect fewer apps now. Okular still comes up behind, but Falkon for example right now comes up on top. Quite weird. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414022] New: New windows are placed behind active window
https://bugs.kde.org/show_bug.cgi?id=414022 Bug ID: 414022 Summary: New windows are placed behind active window Product: kwin Version: 5.17.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: and...@alweb.dk Target Milestone: --- When opening a new application from krunner, it almost always placed behind the active one. Focus stealing prevention is set to low (default), switching to none does not help. STEPS TO REPRODUCE 1. activate krunner and type something, select an application to launch 2. there are no more steps OBSERVED RESULT The new application window is not visible EXPECTED RESULT The new application window is visible SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux, fully updated (available in About System) KDE Plasma Version: 5.17.2 KDE Frameworks Version: 5.63.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION I run plasma with almost default settings. The problem is the same if I use the system menu in the panel. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 --- Comment #40 from Anders Lund --- Yes, works here again too. Thank you! :) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Anders Lund changed: What|Removed |Added CC|and...@alweb.dk | -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 Anders Lund changed: What|Removed |Added CC||and...@alweb.dk -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 386985] akonadi CalDav resource not synching with certain servers
https://bugs.kde.org/show_bug.cgi?id=386985 --- Comment #38 from Anders Lund --- I have this problem after updating to nextcloud 16. I can tell that I can create events using korganizer, and they appear in the NextCloud Calendar app and on my phone etc, but no events are ever fetched. Restarting the resource in korganizer settings briefly shows "fetching 0%" for each calendar, I confirmed by looking in akonadiconsole that the resource only contains locally created events. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413540] New: Title templates does not save duration
https://bugs.kde.org/show_bug.cgi?id=413540 Bug ID: 413540 Summary: Title templates does not save duration Product: kdenlive Version: 19.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: and...@alweb.dk Target Milestone: --- Saving a title template, the duration set is not respected. That is a bug. STEPS TO REPRODUCE 1. Create a title for a template, that is one with the text "%s". 2. Set the duration to something else than 00:00:05:00 3. Press save as. 4. Add a title template to project, selecting the created template OBSERVED RESULT The new title does not have the duration set during creation og the template. It is very difficult to change that, if one uses many titles. EXPECTED RESULT Guess what - a title with the set duration ... 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 413131] New: Keep cookies from whitelisted domains, even when deleting cookies on close
https://bugs.kde.org/show_bug.cgi?id=413131 Bug ID: 413131 Summary: Keep cookies from whitelisted domains, even when deleting cookies on close Product: Falkon Version: 3.1.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: now...@gmail.com Reporter: and...@alweb.dk Target Milestone: --- It would be nice if cookies from whitelisted (1.-party) domains could be kept during deletion of cookies when "delete cookies on close" is activated. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413540] Title templates does not save duration
https://bugs.kde.org/show_bug.cgi?id=413540 --- Comment #2 from Anders Lund --- > Could you please add your operating system version. Archlinux, fully up to date. Kdenlive 19.08.2. KDE and Qt are latest stable. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413540] Title templates does not save duration
https://bugs.kde.org/show_bug.cgi?id=413540 --- Comment #3 from Anders Lund --- I was trying to create a typewriter effect by using one title for each new character, with a duration of 2 (-4) frames, so my title was having a duration of 2 frames. My thougt was that using a template, I would not have to rename the titles, but changing the duration is a pain. I ended up duplicating titles and renaming them (tw ), apart from editing the text for each one instead, and given the naming scheme used for titles, that is probably easier. However, I believe that it *should* be possible to have the duration as part of templates. The default 5 seconds may be a long time in some cases, or a short time in other. Looking at my template in a new project, it still carries the 2-frame duration, but it is not kept when the template is used, in that event it is replaced by a 5 sec duration. If I open the template and focus and then click ok, I am warned that I am editing an external file and if I want the change to be local. Dragging a 2-frame title clip to the timeline, its duration is altered to 3 frames, something that does not happen to longer (5 sec) clips. Any title created from a template is named "title template" (translated from danish), which makes them indistinguishable, btw. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 414292] New: Some sites does not work in private windows
https://bugs.kde.org/show_bug.cgi?id=414292 Bug ID: 414292 Summary: Some sites does not work in private windows Product: Falkon Version: 3.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: and...@alweb.dk Target Milestone: --- Some websites does not work correctly in Falkons private windows, but do work normal falkon windows or in firefox private windows. This is a long standing problem. Example: https://dr.dk/tv - some elements does not show, like the video player. I can not figure out why this is the case, but I do find it quite annoying as I use private windows most of the time. SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux, kernel 5.3.7-arch1-1-ARCH KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414521] File management is broken
https://bugs.kde.org/show_bug.cgi?id=414521 Anders Lund changed: What|Removed |Added Platform|Other |Archlinux Packages Version|unspecified |6.4.0 Severity|normal |critical -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414521] File management is broken
https://bugs.kde.org/show_bug.cgi?id=414521 --- Comment #1 from Anders Lund --- Sorry, actually my metadata is preserved, but progress information is still missing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414521] New: File management is broken
https://bugs.kde.org/show_bug.cgi?id=414521 Bug ID: 414521 Summary: File management is broken Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: and...@alweb.dk Target Milestone: --- In digikam it is possible to move files and folders around, by drag and drop. But doing so leads to DATA LOSS, as digikam fails to update its database when files are moved FROM WITHIN DIGIKAM. Lost data includes ANY metadata in the digikam database. THAT SUCKS. Apart from the data deletion, digikam also does not provide progress information during moving files. Not a problem while moving one or even a few files, but duging moving many (like 1000s) files, this leads to a riske of FILE LOSS. THAT SUCKS TOO. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414521] File management is broken
https://bugs.kde.org/show_bug.cgi?id=414521 --- Comment #3 from Anders Lund --- Yes, I realized that the metadata part of my issues actually have been fixed - I am very greatful with that! I use latest package from archlinux, 6.4, and there is no progress bar that I can see. I use the harddisk blinking thing on my laptop to decide if I believe it is still in progress, and also digikam does not reflect moves untill it is all done. Due to space requirement, I have to move albums once in a while, from my laptop disk to a portable one, so I move many thousand images by dragging the albums around. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 414521] File management is broken
https://bugs.kde.org/show_bug.cgi?id=414521 --- Comment #5 from Anders Lund --- Maybe the progressbar only shows pr file? I moved thousands of files and never saw a progress bar. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413540] Title templates does not save duration
https://bugs.kde.org/show_bug.cgi?id=413540 Anders Lund changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414618] New: Widget backgrounds in the statusarea popups are unreadable
https://bugs.kde.org/show_bug.cgi?id=414618 Bug ID: 414618 Summary: Widget backgrounds in the statusarea popups are unreadable Product: plasmashell Version: 5.17.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: and...@alweb.dk CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 124161 --> https://bugs.kde.org/attachment.cgi?id=124161=edit Brokenness The plasma configuration settings indicate that if a dialog is non-opaque, the background should be BLURRED. Stick to that, since the desktop in its current version is unusable due to this. This is using breeze theme. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414618] Widget backgrounds in the statusarea popups are unreadable
https://bugs.kde.org/show_bug.cgi?id=414618 Anders Lund changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Anders Lund --- Oddly, after switching back and forth between themes, things appears to work sanely again. But what a scare... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417330] New: It is impossible to move an album to a collection or album not visible in the albums list
https://bugs.kde.org/show_bug.cgi?id=417330 Bug ID: 417330 Summary: It is impossible to move an album to a collection or album not visible in the albums list Product: digikam Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: and...@alweb.dk Target Milestone: --- I try to move albums to a collection on a mounted device. I want to do this using digikam, because I want to maintain the metadata. When the target album is not visible in the list, this is IMPOSSIBLE. The list does not scroll to allow dropping in the out of view target album. Ideas: Fix this (scrolling). Create a dialog to handle moving albums or images, available in the context menus. Make it easy to move several albums at once. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch linux, fully updated. (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version:5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417333] New: Advanced slideshow is blocking the desktop.
https://bugs.kde.org/show_bug.cgi?id=417333 Bug ID: 417333 Summary: Advanced slideshow is blocking the desktop. Product: digikam Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: and...@alweb.dk Target Milestone: --- Using the advanced slideshow completely blocks the desktop. It is not possible to switch to another window, not even if the slidwshow is run on a second monitor. Digikam itself is blocked even when the advanced slideshow setup dialog is shown. I think those are really bad choices. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux, fully up to date (available in About System) KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 418480] New: Send file does not clear list and sends same file repeatedly
https://bugs.kde.org/show_bug.cgi?id=418480 Bug ID: 418480 Summary: Send file does not clear list and sends same file repeatedly Product: kdeconnect Version: 1.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: and...@alweb.dk Target Milestone: --- Sending a file from my laptop to my phone, kdeconnect does not appear to cledar the list, so files are sent multiple times. STEPS TO REPRODUCE 1. Click on the kdeconnect icon in system tray, then on the dots menu, then "send file". Select a file to send. Repeat - now both the first and second files are sent. 2. 3. OBSERVED RESULT Files are set repeatedly EXPECTED RESULT List of files to send should be cleared after sending SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux (available in About System) KDE Plasma Version: 5.18.12 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417333] Advanced slideshow is blocking the desktop.
https://bugs.kde.org/show_bug.cgi?id=417333 --- Comment #2 from Anders Lund --- Thank you very much! :) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417330] It is impossible to move an album to a collection or album not visible in the albums list
https://bugs.kde.org/show_bug.cgi?id=417330 --- Comment #3 from Anders Lund --- Making that dialog work for albums too would be a great help, although it would stille be tedious to move more than one album. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 419998] New: tracks from gpx lines are painted as a px white line, invisible almost
https://bugs.kde.org/show_bug.cgi?id=419998 Bug ID: 419998 Summary: tracks from gpx lines are painted as a px white line, invisible almost Product: marble Version: 2.5 (KDE Applications 18.04) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: and...@alweb.dk Target Milestone: --- Loading a gpx file with a track, I first thought the file was broken, as I could not see the track. But it's there, just almost invisible. STEPS TO REPRODUCE 1. load a gpx file with a track 2. There is no more steps OBSERVED RESULT The track is almost invisible EXPECTED RESULT The track would be visible, eg a 3px red line - or configurable! SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux current (available in About System) KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424020] The activity switch bar can't be closed automatically after switch activity
https://bugs.kde.org/show_bug.cgi?id=424020 --- Comment #19 from Anders Lund --- One way to hide it is to show the desktop, rightclick and select "Activities..." fredag den 18. september 2020 18.49.20 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=424020 > > --- Comment #18 from Piotr Mierzwinski --- > (In reply to Nate Graham from comment #17) > > > Meta+Q does indeed make it stick open, but I think that's intentional. > > Meta+Tab shows the auto-closing version. > > > > ...I have no idea why these are different things, of course. > > I meant that I'm able to unstick this bar by Meta+Q. When no bar is present > then this shortcut just shows it. > When I switch Activities quickly by Meta+Tab - not holding Meta - then bar > isn't show. Only when I will hold Meta then bar is shonw and after release > Meta, isn't autohide. Now I need to use again Meta+Q to hide it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424020] The activity switch bar can't be closed automatically after switch activity
https://bugs.kde.org/show_bug.cgi?id=424020 --- Comment #14 from Anders Lund --- It does not appear here immediately. I'll be aware during the next week. No extra screen during the weekend. -- fredag den 18. september 2020 00.50.58 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=424020 > > David Edmundson changed: > >What|Removed |Added > > CC||k...@davidedmundson.co.uk Status|CONFIRMED > |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #13 from David Edmundson --- > I can't reproduce with the instructions given. > > Is this still an issue with Plasma 5.20 beta? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426671] New: Use a function other than random() to decide on which screen to place windows after wakeup
https://bugs.kde.org/show_bug.cgi?id=426671 Bug ID: 426671 Summary: Use a function other than random() to decide on which screen to place windows after wakeup Product: plasmashell Version: 5.19.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: and...@alweb.dk CC: plasma-b...@kde.org Target Milestone: 1.0 When waking up after suspend with an extra screen attached, please restore the screen configuration and windows placement as they were when the system was suspended, instead of randomly a) not enabling the laptop screen b) enabling the laptop screen but move all windows to extra screen Please. STEPS TO REPRODUCE 1. Have an extra screen/monitor attached (I use a HDMI cable) 2. suspend system 3. wake up system OBSERVED RESULT Often the screen configuration and windows placement is messed up EXPECTED RESULT Things working. SOFTWARE/OS VERSIONS Linux/KDE Plasma: archlinux. (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 417322] Unable to move album because tree view does not scroll
https://bugs.kde.org/show_bug.cgi?id=417322 --- Comment #5 from Anders Lund --- Still an issue in 6.4.0. Even if fixed, file management is still very bad, most importantly a view where multiple folders can be moved at once is needed to make file management work better. -- Kindly, Anders -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422128] New: Multiscreen support is broken in multiple ways
https://bugs.kde.org/show_bug.cgi?id=422128 Bug ID: 422128 Summary: Multiscreen support is broken in multiple ways Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: and...@alweb.dk CC: plasma-b...@kde.org Target Milestone: 1.0 Plugging in my ekstra screen doesnt work correctly since last update. There are several issues: Identifying screens does not work correctly. If I drag screens to my preferred configuration (extra screen to the right of laptop screen) identification is switched. This leads to multiple problems with window sizes etc. When plugging in external monitor, all windows are moved to it, even if it is NOT the primary screen. STEPS TO REPRODUCE 1. Plug in external monitor OBSERVED RESULT Things are not working correctly, see above. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: archlinux, up to date (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5142 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426671] Use a function other than random() to decide on which screen to place windows after wakeup
https://bugs.kde.org/show_bug.cgi?id=426671 --- Comment #2 from Anders Lund --- Sorry for being ironic. I tried this: [anders@elias anders]$ KSCREEN_LOGGING='' kscreen-doctor -l screendoctor [anders@elias anders]$ and found ~/.local/share/kscreen/kscreen.log with a line with "screendoctor" in it after a suspend, but no meaningful information. I will try a few more times, but if I do something wrong, please let me know. The results after wakeup are not consistent - some times it works like expected, but fra from always. If haredware details are helpful, my laptop is a Dell Latitude 7440, intel based, and the external monitor is a Dell U2518D. Anders -- fredag den 18. september 2020 13.21.13 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=426671 > > David Edmundson changed: > >What|Removed |Added > > Resolution|--- |WAITINGFORINFO > CC||k...@davidedmundson.co.uk > Status|REPORTED|NEEDSINFO > > --- Comment #1 from David Edmundson --- > Please don't be deliberately antagonistic. > > There is no explicit code to do anything on suspend/resume, and in theory > after suspend/resume everything should come up in the same state. > > Please include > > kscreen-doctor -l someLog > and perform a supsend/restart that reproduces this issue -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398885] Collections on removable media does not work
https://bugs.kde.org/show_bug.cgi?id=398885 --- Comment #10 from Anders Lund --- I have decided to not use digikam, as it deletes my files and apart from that is quite a monster loading a lot of unneeded code and providing much more features than I actually need. -- lørdag den 1. august 2020 18.08.45 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=398885 > > --- Comment #9 from caulier.gil...@gmail.com --- > digiKam 7.0.0 stable release is now published and now available as FlatPak: > > https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ > > We need a fresh feedback on this file using this version. > > Thanks in advance > > Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398532] Setting margins does not work
https://bugs.kde.org/show_bug.cgi?id=398532 --- Comment #5 from Anders Lund --- I have stopped using digikam, because it potentially destroys my files, so I will not be able to test. Apart from that I use darktable for printing at this point, since I have never been able to get a deacent result using digikam. Kindly, Anders -- lørdag den 1. august 2020 18.12.00 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=398532 > > --- Comment #4 from caulier.gil...@gmail.com --- > digiKam 7.0.0 stable release is now published and now available as FlatPak: > > https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ > > We need a fresh feedback on this file using this version. > > Thanks in advance > > Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 --- Comment #28 from Anders Lund --- This is idiotic. Digikam deletes my files, dolphin does not, because it have functional file management. Digikam does not, and unlinks files without ensuring that they are actually written. But hey, I have decided not to use digikam any longer, for this specific reason. torsdag den 30. juli 2020 11.34.57 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=423227 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > Status|NEEDSINFO |RESOLVED > Resolution|WAITINGFORINFO |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 232391] PRINT : scaling images is broken
https://bugs.kde.org/show_bug.cgi?id=232391 --- Comment #15 from Anders Lund --- I have stopped using digikam, because of its lack of safe file management, therefore I can not help. Also, I have not used digikams editor since years, because it lacks abilities to use masks and copy editing between images. -- mandag den 3. august 2020 07.01.37 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=232391 > > --- Comment #14 from caulier.gil...@gmail.com --- > digiKam 7.0.0 stable release is now published: > > https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ > > We need a fresh feedback on this file using this version. > > Best Regards > > Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 --- Comment #23 from Anders Lund --- I do not have digikam installed any longer, since I can not trust it. So you get no information from me. Conveniently for you, you can just remove this bug, and not fix your broken software. mandag den 6. juli 2020 06.33.08 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=423227 > > --- Comment #22 from Bug Janitor Service --- > Dear Bug Submitter, > > This bug has been in NEEDSINFO status with no change for at least > 15 days. Please provide the requested information as soon as > possible and set the bug status as REPORTED. Due to regular bug > tracker maintenance, if the bug is still in NEEDSINFO status with > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > If you have already provided the requested information, please > mark the bug as REPORTED so that the KDE team knows that the bug is > ready to be confirmed. > > Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424129] Multiscreen support is BROKEN, session management does NOT WORK
https://bugs.kde.org/show_bug.cgi?id=424129 --- Comment #1 from Anders Lund --- This is one of those annoying come-and-go issues. Sometimes it works, sometimes it does not. -- søndag den 12. juli 2020 20.02.45 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=424129 > > Bug ID: 424129 >Summary: Multiscreen support is BROKEN, session management does > NOT WORK >Product: plasmashell >Version: 5.19.3 > Platform: Other > OS: Linux > Status: REPORTED > Severity: normal > Priority: NOR > Component: Multi-screen support > Assignee: aleix...@kde.org > Reporter: and...@alweb.dk > CC: plasma-b...@kde.org > Target Milestone: 1.0 > > I have a laptop and an extra monitor. > For a long time, if the extra monitor was connected, closing the laptop lid > would not lead to the laptop being suspended. > Since sometime, it did lead to the laptop being suspended, and wake up would > work. > Not so anymore, now when waking up, the laptop screen (which is the primary > screen) is shut down at wake up, and today the display was 100% broken, with > only a small edge visible on the external screen after wakeup. > I could disconnect the extra monitor, then the laptop screen would turn on > and work, but reconnecting the extra monitor would lead to the laptop > screen being disconnected again. > The order of the screens in the screen management tool was reversed, a bug > that had been fixed a few releases ago = REGRESSION. > I get really stiff shoulders trying to use this for daily work!!! > > > > STEPS TO REPRODUCE > 1. connect an extra monitor > 2. suspend > 3. wake up > > OBSERVED RESULT > Plasma is fucked in multiple ways, as described above > > EXPECTED RESULT > Working plasma > > > Archlinux, up to date > KDE Plasma: 5.19.3 > KDE-frameworks: 5.71.0 > Qt: 5.15.0 > Kernel: 5.7.7-arch-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424129] New: Multiscreen support is BROKEN, session management does NOT WORK
https://bugs.kde.org/show_bug.cgi?id=424129 Bug ID: 424129 Summary: Multiscreen support is BROKEN, session management does NOT WORK Product: plasmashell Version: 5.19.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: and...@alweb.dk CC: plasma-b...@kde.org Target Milestone: 1.0 I have a laptop and an extra monitor. For a long time, if the extra monitor was connected, closing the laptop lid would not lead to the laptop being suspended. Since sometime, it did lead to the laptop being suspended, and wake up would work. Not so anymore, now when waking up, the laptop screen (which is the primary screen) is shut down at wake up, and today the display was 100% broken, with only a small edge visible on the external screen after wakeup. I could disconnect the extra monitor, then the laptop screen would turn on and work, but reconnecting the extra monitor would lead to the laptop screen being disconnected again. The order of the screens in the screen management tool was reversed, a bug that had been fixed a few releases ago = REGRESSION. I get really stiff shoulders trying to use this for daily work!!! STEPS TO REPRODUCE 1. connect an extra monitor 2. suspend 3. wake up OBSERVED RESULT Plasma is fucked in multiple ways, as described above EXPECTED RESULT Working plasma Archlinux, up to date KDE Plasma: 5.19.3 KDE-frameworks: 5.71.0 Qt: 5.15.0 Kernel: 5.7.7-arch-1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424134] New: Activity switcher often fails to hide
https://bugs.kde.org/show_bug.cgi?id=424134 Bug ID: 424134 Summary: Activity switcher often fails to hide Product: plasmashell Version: 5.19.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Activity Switcher Assignee: ivan.cu...@kde.org Reporter: and...@alweb.dk CC: plasma-b...@kde.org Target Milestone: 1.0 Half the time, the activity switcher fails to hide. I can show desktop and pick "Activities" from the desktop context menu to hide it. Tedious. STEPS TO REPRODUCE 1. Have at least two activities. 2. Switch activity using keyboard. 3. OBSERVED RESULT Often, the activity switcher widget fails to hide, and requires lots of clicking/keying to get rid of. EXPECTED RESULT Stuff that works. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.19.3 (available in About System) KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.71.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423227] New: Your fuckshit crapware just deletet 1000s of files AGAIN. FUCKHEADS
https://bugs.kde.org/show_bug.cgi?id=423227 Bug ID: 423227 Summary: Your fuckshit crapware just deletet 1000s of files AGAIN. FUCKHEADS Product: digikam Version: 6.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: and...@alweb.dk Target Milestone: --- SUMMARY File management in digikam is FUCKING BROKEN. STEPS TO REPRODUCE 1. Move some albums 2. cry, because IT DOES NOT WORK 3. 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.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 --- Comment #17 from Anders Lund --- søndag den 21. juni 2020 10.34.52 CEST skrev du: > What exactly was the problem with your USB drive? When moving files with dolphin, there was a message saying it didn't answer at some point. I moved the cable/connector a bit, and it continued. The progress started moving again. During my attempt to move files using digikam, digikam just appeared to do nothing, so I pushed the stop button on all the "move album" items, hoping that at least some files would be saved. I was not able to unmount the disk (probably due to the usb connection problem). All was lost, appearently digikam had unlinked ALL the files. I later managed to restore files using photorec, but it is of course a mess. This is the third time I have this experience with digikam, so I have decided to try and replace it with functional softwares. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 --- Comment #14 from Anders Lund --- That is of course nice, and a step in the right difection, but you still manage to unlink files that wasn't successfully written to target. My problems appear when moving files between (usb) disks. lørdag den 20. juni 2020 23.42.50 CEST skrev du: > --- Comment #13 from Maik Qualmann --- > Git commit 3eb48089a1ce737ab0371d73566e5c9a5cd1d4a3 by Maik Qualmann. > Committed on 20/06/2020 at 21:40. > Pushed by mqualmann into branch 'master'. > > show better progress if we have to copy recursively > > M +4-2core/libs/iojobs/iojob.cpp > M +37 -2core/libs/threadimageio/engine/dfileoperations.cpp > M +3-1core/libs/threadimageio/engine/dfileoperations.h > > https://invent.kde.org/graphics/digikam/commit/3eb48089a1ce737ab0371d73566e5 > c9a5cd1d4a3 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 --- Comment #6 from Anders Lund --- A main cause of grief is the horrible lack of progress information. Today, I had a stack of progress bars claiming "Moving Album ...", bot none showed any progress. There was a technical problem with the drive I moved the files to. Digikam happily deleted my files, leaving me with the issue of recovering them, getting them renamed and figuring out how to rename darktables xmp files too (not solved yet) as well as exported jpeg files (not solved yet). Using Dolphin no file was deleted, when the technical issue with the disk appeared, the progress information helped me solve the problem with no data loss. In earlier events, the lack of proper progress information along with the insanely slow operation (due to the database queries?) of digikam have been an issue as well. Without proper progress information, I give up, and meanwhile digikam appearently just deletes files. I have experienced this at least 3 times. Maybe digikam works for you because you know the internals well. I don't. I don't think there were issues when digiKam was a real KDE app. -- fredag den 19. juni 2020 18.46.18 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=423227 > > Maik Qualmann changed: > >What|Removed |Added > > CC||metzping...@gmail.com > > --- Comment #5 from Maik Qualmann --- > I can understand that it is annoying for you to lose images. But like > Gilles, I work with digiKam every day (for years) and have never lost a > image. > > The story with drag & drop and scrolling in the album view is fixed in > digiKam-7.0.0. > > I know the internal file engine in digiKam really well. I can not imagine > that digiKam is the sole cause here. We have really built a lot of > safeguards that images are not deleted when a file operation has failed. > > Just a brief technical description: > In principle, a move within a drive / partition is just a simple renaming of > the source album. If images are lost here, there is an error at system > level. > > We recursively copy all files between different drives / partitions. The > first time an error occurs, it is canceled. The source directory is only > deleted when all files have been copied without error feedback. In the > worst case, you could only have files double. A loss within digiKam cannot > be explained here either. > > Check your drives for errors, I know from daily work experience that there > are a lot of hard drives with bad sectors among users. > > Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 --- Comment #4 from Anders Lund --- File management in digikam have been a problem for me for years and years. Bugs does not get fixed, and it is not possible to drag folders if the destination is not visible in the albums pane. There is no facility for moving multiple folders. And moving folders between devices leads to data loss, probably because I am an IDIOT, but nevertheless, it has happened several times. Today, I have (hopefully) been able to recover my files using PhotoRec, but I do not want to fight digikam any longer, the benefits not being worth the problems. A huge issue for me is digikam not being a prober KDE app any longer, since in KDE file management actually works, and there is a functional file dialog for example. I have given up. I'll have to live with using dolphin and gwenview and other existing tools, to avoid all the grief that digikam causes. fredag den 19. juni 2020 16.14.22 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=423227 > > caulier.gil...@gmail.com changed: > >What|Removed |Added > > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #3 from caulier.gil...@gmail.com --- > Well without relevant info, we cannot help you... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 --- Comment #2 from Anders Lund --- I have uninstalled digikam, as I can not use it any longer. Filemanagement is part of what I need to do with my photos, and digikam is not sufficient or efficient at that. Feel free to ignore this bug - though this have happened several times. Other reasons for not using digikam is that it is notoriosly slow at many tasks, and loads tons of stuff I never use, as do not use the built in editor. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 --- Comment #20 from Anders Lund --- søndag den 21. juni 2020 11.29.22 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=423227 > > --- Comment #18 from caulier.gil...@gmail.com --- > So, on your computer you have a wrong electric connection with USB device. > > My tip : change cables, and if it don't work better change the device. > This can be a power failure on the +5V delivered to the connected device. I > already seen this kind of dysfunction with magnetic external hardrive which > need more power more than expected. In my office, when maintenance team > backup magnetic hardrive, they always use an external CC and never use USB > power. What I see is this: With digikam, this leads to data loss, without digikam it does not. So I don't really care about your tips and attempts to make this problem not exist. But since I will not be using digikam again anytime soon, I will not be affected anymore. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 --- Comment #21 from Anders Lund --- Another answer to this is that in earlier events where I lost files, there was NO device issues. Just the very slow speed in combination with digikams poor progress (nonexisting in some of those events in my understanding). And still, even with the process interrupted, it should not mean massive data loss, as it did more than once. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 423227] File management just deleted 1000 files
https://bugs.kde.org/show_bug.cgi?id=423227 --- Comment #8 from Anders Lund --- Well, in the old time digikam had a proper file dialog, iirc - now it doesn't. And again, I don't care. I can't use it, as it is unreliable. -- lørdag den 20. juni 2020 15.01.54 CEST skrev du: > https://bugs.kde.org/show_bug.cgi?id=423227 > > --- Comment #7 from caulier.gil...@gmail.com --- > Anders, > > Technically, digiKAm have been a KDE application until 3.0.0 as KIO slave > was used to perform serialized database operation. > > We leaves KIOSlave technology as it's not portable outside Linux. > Performance was really bad with large collections. Multithreading was used > instead. > > Step by step we transform digiKam as a pure Qt5 application. It still KDE > API used mostly with GUI and main view. > > digiKam has never shared API with dolphin or other KDE application, excepted > for plugin through KIPI. Now this point was also left as we have a pure Qt5 > plugin architecture, more simple, and powerful. > > The problem with album tree-view and drag and drop are probably due to bugs > in Qt5 API. Personalty, all work as expected here, i never seen this king > of dysfunction here. And i use all the time the D features, and it's a > pleasure with multi-screens. > > Note: here you will see the list of KDE API dependencies used by digiKam. As > you can see, digiKam always depends of KDE (KF5 components), even if less > API calls are used : > > https://www.digikam.org/api/index.html#externaldeps > > > Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
