[kmail2] [Bug 365162] after upgrading today, kmail folder list corrupted
https://bugs.kde.org/show_bug.cgi?id=365162 BogDan Vatra changed: What|Removed |Added Ever confirmed|0 |1 CC||bog...@kde.org Status|UNCONFIRMED |CONFIRMED --- Comment #2 from BogDan Vatra --- Same for me -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 Lukas Sommer changed: What|Removed |Added CC||sommer...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 329091] MySQL : Maintenance leads to crash digiKam
https://bugs.kde.org/show_bug.cgi?id=329091 caulier.gil...@gmail.com changed: What|Removed |Added Version|4.2.0 |4.14.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365135] Digikam 5 fails to build with DIGIKAMSC_COMPILE_DOC=on
https://bugs.kde.org/show_bug.cgi?id=365135 caulier.gil...@gmail.com changed: What|Removed |Added CC||k...@nicolaslecureuil.fr -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #18 from caulier.gil...@gmail.com --- So, if i resume : Win7 64 bits : work fine. Win8 64 bits : ??? Win10 64 bits : doesn't work. I'm fine ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361615] Inconsistent termination when an instrumented multithreaded process is terminated by signal
https://bugs.kde.org/show_bug.cgi?id=361615 --- Comment #3 from earl_c...@yahoo.com --- (In reply to Julian Seward from comment #2) > Do you have a small test case which demonstrates that Valgrind's behaviour at > present, differs from when the program is run "natively" ? In the bug description, I pasted a small C program and accompanying shell script that demonstrates the difference between a natively run program, and the same running under valgrind. Are you looking for something different ? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 364271] kded5 hangs sometime when is started through kdeinit
https://bugs.kde.org/show_bug.cgi?id=364271 --- Comment #3 from Claudiu Nicolaie CISMARU --- It seems that it stabilized with the last updates. I don't know which one fixed the issue, though. But I haven't had issues with kded5 for about 2 weeks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #19 from caulier.gil...@gmail.com --- 64 bits installer updated with install path fixed : https://drive.google.com/open?id=0B7yq-xFihT0_MVBzOW9jZFA2NE0 Please check... Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 215558] leaving the "THEME" area caused fatel error sig 11 sigsegv Then it crashed
https://bugs.kde.org/show_bug.cgi?id=215558 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.0.0 CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it is necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 218765] drag digikam photo to thunderbird 3.0 email attachment section
https://bugs.kde.org/show_bug.cgi?id=218765 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.0.0 --- Comment #8 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it is necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 227123] digikam crashes when deleting pictures from camera
https://bugs.kde.org/show_bug.cgi?id=227123 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.0.0 --- Comment #5 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it is necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 195448] random system hangs when handling RAW images in digikam
https://bugs.kde.org/show_bug.cgi?id=195448 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.0.0 Resolution|WAITINGFORINFO |FIXED --- Comment #13 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it is necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 211009] digikam batch raw converter
https://bugs.kde.org/show_bug.cgi?id=211009 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.0.0 CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 211009] digikam batch raw converter
https://bugs.kde.org/show_bug.cgi?id=211009 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |BatchQueueManager-Tool-RAWP ||rocessing -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 213916] Digikam crashed when building the collection
https://bugs.kde.org/show_bug.cgi?id=213916 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Database-Scan Version Fixed In||5.0.0 Resolution|WAITINGFORINFO |FIXED --- Comment #9 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 218987] After several days idle, Digikam crashed during closing.
https://bugs.kde.org/show_bug.cgi?id=218987 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.0.0 --- Comment #7 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 214874] picture download from cf-card
https://bugs.kde.org/show_bug.cgi?id=214874 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.0.0 Resolution|BACKTRACE |FIXED CC||caulier.gil...@gmail.com --- Comment #7 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 215021] Crash importing photos from SD card into Digikam
https://bugs.kde.org/show_bug.cgi?id=215021 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version Fixed In||5.0.0 Resolution|BACKTRACE |FIXED --- Comment #6 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 215648] When I try to import the pictures from Memory Card to My compiture digiKam crashed.
https://bugs.kde.org/show_bug.cgi?id=215648 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|BACKTRACE |FIXED Version Fixed In||5.0.0 CC||caulier.gil...@gmail.com --- Comment #3 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 215854] download pictures to hd in digikam
https://bugs.kde.org/show_bug.cgi?id=215854 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.0.0 Resolution|BACKTRACE |FIXED --- Comment #3 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 217532] Crash while using Download Photos with Digikam link from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=217532 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.0.0 Resolution|WAITINGFORINFO |FIXED --- Comment #11 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356225] Panel moves to wrong screen when external monitor is connected
https://bugs.kde.org/show_bug.cgi?id=356225 --- Comment #130 from madc...@atlas.cz --- I updated to Plasma 5.7 (Arch Linux testing repo) a few days ago and the problem is definitely not fixed for me. Let me know if I can post any debugging info that'd help you to track this down. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 Patrick van Elk changed: What|Removed |Added CC||patr...@aedifex.nl --- Comment #20 from Patrick van Elk --- This installer WFM! (Windows 10 64 bit OS) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365147] multimonitor fn key disabled
https://bugs.kde.org/show_bug.cgi?id=365147 --- Comment #3 from rockonthemoo...@gmail.com --- xev output: fn+f8 KeyRelease event, serial 40, synthetic NO, window 0x3e1, root 0xf6, subw 0x0, time 16840795, (-8,210), root:(724,239), state 0x50, keycode 33 (keysym 0x70, p), same_screen YES, XLookupString gives 1 bytes: (70) "p" XFilterEvent returns: False KeyRelease event, serial 40, synthetic NO, window 0x3e1, root 0xf6, subw 0x0, time 16841441, (-8,210), root:(724,239), state 0x50, keycode 133 (keysym 0xffeb, Super_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False Don't ask me why now it's recognized as "p" and not "XF86Display". Anyway it worked with every distro / DE. It worked, as long as I can remember, in version 5.6 too (I'm not 100% sure). 2016-07-07 7:59 GMT+02:00 Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=365147 > > --- Comment #2 from Martin Gräßlin --- > kscreen already registers the key as a global shortcut: > kded/daemon.cpp:KGlobalAccel::self()->setGlobalShortcut(action, > Qt::Key_Display); > > So the only question is: why is the shortcut not triggered. Xev should > tell us. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365181] New: Task Manager thumbnails for grouped tasks lead to incorrect windows
https://bugs.kde.org/show_bug.cgi?id=365181 Bug ID: 365181 Summary: Task Manager thumbnails for grouped tasks lead to incorrect windows Product: plasmashell Version: 5.7.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: madc...@atlas.cz CC: plasma-b...@kde.org I have discovered this quite annoying issue ever since updating to Plasma 5.7. The issue can be easily observed like this: 1. Enable task grouping in Task Manager plasmoid 2. Launch an application (I use Dolphin to reliably reproduce the isse) 3. RIghtlick on its entry in the taskbak, select "Start a new instance" 4. Start up a few instances and open different folders in them to tell the windows apart easily 5. Hover the mouse over the grouped Dolphin entry, wait for the thumbnails to appear 6. Click on any thumbnail, chances are that it will activate an incorrect window Leftclicking on the task entry and selecting a window from the menu works OK. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 338647] GROUP : assemble files by format shows two groups of RAW files instead of one
https://bugs.kde.org/show_bug.cgi?id=338647 Dany changed: What|Removed |Added CC||d...@natzo.com --- Comment #6 from Dany --- Hi Gilles, Unfortunately this bug still applies on the latest 5.0.0 release. In order for you to duplicate it I have a put together a file set that exhibits the problem. https://natzo.com/files/2014-03_Nettoyage-Capteur.zip - Unzip the directory found in the above archive and add it to your collection. - Select View/Thumbnails - Select View/Include Album Sub-Tree - Select View/Group Images/By Format - Select the top directory that was imported You should seed on the thumbnail list (icons): - A first group of one file called JPEG - A second group of 8 files called JPEG - A third group of 2 files called NIKON-NEF - A fourth group of 6 files called RAW image file (NEF) PS: This happens not only with Nikon RAW but also with Fuji RAF files. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 365182] New: FancyPlotter widget doesn't set plot background correctly
https://bugs.kde.org/show_bug.cgi?id=365182 Bug ID: 365182 Summary: FancyPlotter widget doesn't set plot background correctly Product: ksysguard Version: 5.7.0 Platform: Compiled Sources URL: https://i.imgur.com/zGCjSnN.png OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: adam.m.fontenot+...@gmail.com See URL to screetshot. FancyPlotter seems not to set a background color, instead (I think) grabbing the inactive color from the QT palette. The darker color in the background of the screenshots is created whenever the window is inactive, the white background is created when the window is active. Reproducible: Always Steps to Reproduce: 1. Open Ksysguard to a plot 2. Give and remove focus to the Ksysguard window a few times. Actual Results: The plot background alternates between two colors. Expected Results: The plot background should remain constant. Tested on both 5.6.* in the Arch repositories and on the tagged 5.7 release which I built myself. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #21 from caulier.gil...@gmail.com --- >This installer WFM! Sorry ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #22 from Patrick van Elk --- Sorry "Works For Me" :-) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 344969] Shortcut configuration for Folder View actions not handled by standard keys
https://bugs.kde.org/show_bug.cgi?id=344969 milo...@o2.pl changed: What|Removed |Added CC||milo...@o2.pl -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365128] no password prompt at boot (luks encrypted disk)
https://bugs.kde.org/show_bug.cgi?id=365128 Harald Sitter changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Harald Sitter --- *** This bug has been marked as a duplicate of bug 365169 *** -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 365169] No cryptsetup entry box or information in Neon 5.7 breeze theme
https://bugs.kde.org/show_bug.cgi?id=365169 Harald Sitter changed: What|Removed |Added CC||bo...@web.de --- Comment #1 from Harald Sitter --- *** Bug 365128 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365183] New: The animated icon of opening an application remains even after app is loaded
https://bugs.kde.org/show_bug.cgi?id=365183 Bug ID: 365183 Summary: The animated icon of opening an application remains even after app is loaded Product: plasmashell Version: 5.7.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: tro...@free.fr CC: plasma-b...@kde.org In Task Manager on Plasma 5.7, the spinning blue "circle" that appears in the Task Manager indicating that an application is loading, does not disappear once the application is open and ready to use. I have to "killall plasmashell && plasmashell" to "fix" it. Reproducible: Sometimes Steps to Reproduce: 1. Open several apps in Plasma (happens with Okular, Libre Office...) 2. 3. Actual Results: Sometimes the blue spinning circle of Breeze theme won't go away Expected Results: Once the application is open, the blue circle should be gone. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365169] No cryptsetup entry box or information in Neon 5.7 breeze theme
https://bugs.kde.org/show_bug.cgi?id=365169 Harald Sitter changed: What|Removed |Added Component|general |Plymouth Product|neon|Breeze Assignee|neon-b...@kde.org |plasma-de...@kde.org Version|unspecified |5.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362360] When switching virtual desktop, glitch appears
https://bugs.kde.org/show_bug.cgi?id=362360 --- Comment #6 from Olivier Churlaud --- The glitch is now different: only a black band between the two desktops during the cube animation. It's already better, and it shows that it's mostly a hardware issue. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 365169] No cryptsetup entry box or information in Neon 5.7 breeze theme
https://bugs.kde.org/show_bug.cgi?id=365169 Harald Sitter changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Version Fixed In||5.7.1 Latest Commit||http://commits.kde.org/bree ||ze-plymouth/a5909e1cd59f592 ||54898421df2eb66d4fe10e393 Resolution|--- |FIXED --- Comment #2 from Harald Sitter --- Git commit a5909e1cd59f59254898421df2eb66d4fe10e393 by Harald Sitter. Committed on 07/07/2016 at 08:24. Pushed by sitter into branch 'Plasma/5.7'. fix spinner height and y to resolve broken layout chain everything lays out relative to the spinner/logo, when changing to in-cpu rotation the spinner code was not correctly updated to retain working y and height calculations after changes to internal data structures. this resulted in all objects layed out relative to the spinner to not be drawn as their position was NaN. plymouth could really benefit from openqa tests :/ FIXED-IN: 5.7.1 M +2-2breeze/breeze.script.cmake http://commits.kde.org/breeze-plymouth/a5909e1cd59f59254898421df2eb66d4fe10e393 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #23 from caulier.gil...@gmail.com --- Ah thanks Patrick, I just tested here with a Windows 7 64 bits with all fresh updates, and installer + application start properly. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 338647] GROUP : assemble files by format shows two groups of RAW files instead of one
https://bugs.kde.org/show_bug.cgi?id=338647 caulier.gil...@gmail.com changed: What|Removed |Added Version|4.2.0 |5.0.0 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365179] Crash when nudging a hidden layer
https://bugs.kde.org/show_bug.cgi?id=365179 Boudewijn Rempt changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Hi Chris, Thanks for your report. I can confirm the crash. #0 KisStroke::lodBuddy (this=this@entry=0x0) at /home/boud/dev/krita/libs/image/kis_stroke.cpp:292 #1 0x768cc8ac in KisStrokesQueue::addJob (this=, id=..., data=0x8a6de20) at /home/boud/dev/krita/libs/image/kis_strokes_queue.cpp:255 #2 0x768d5975 in KisUpdateScheduler::addJob (this=0x6f37090, id=..., data=data@entry=0x8a6de20) at /home/boud/dev/krita/libs/image/kis_update_scheduler.cpp:187 #3 0x768eaf15 in KisImage::addJob (this=this@entry=0x6f32e20, id=..., data=data@entry=0x8a6de20) at /home/boud/dev/krita/libs/image/kis_image.cc:1270 #4 0x7fffd15fbceb in KisToolMove::moveDiscrete (this=0x6cee900, direction=, big=) at /home/boud/dev/krita/plugins/tools/basictools/kis_tool_move.cc:188 #5 0x708d0a63 in QMetaObject::activate(QObject*, int, int, void**) () from /home/boud/dev/deps/lib/libQt5Core.so.5 #6 0x716fd392 in QAction::triggered(bool) () from /home/boud/dev/deps/lib/libQt5Widgets.so.5 #7 0x716fff2d in QAction::activate(QAction::ActionEvent) () from /home/boud/dev/deps/lib/libQt5Widgets.so.5 #8 0x717000f4 in QAction::event(QEvent*) () from /home/boud/dev/deps/lib/libQt5Widgets.so.5 #9 0x717067dc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /home/boud/dev/deps/lib/libQt5Widgets.so.5 #10 0x7170ac12 in QApplication::notify(QObject*, QEvent*) () from /home/boud/dev/deps/lib/libQt5Widgets.so.5 #11 0x778eb0b7 in KisApplication::notify (this=, receiver=0x6e48b70, event=0x7fffcda0) at /home/boud/dev/krita/libs/ui/KisApplication.cpp:505 #12 0x708a6955 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /home/boud/dev/deps/lib/libQt5Core.so.5 #13 0x70efbc0f in QShortcutMap::dispatchEvent(QKeyEvent*) () from /home/boud/dev/deps/lib/libQt5Gui.so.5 #14 0x70efbcd4 in QShortcutMap::tryShortcut(QKeyEvent*) () from /home/boud/dev/deps/lib/libQt5Gui.so.5 #15 0x70eb8dab in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () from /home/boud/dev/deps/lib/libQt5Gui.so.5 #16 0x70ecd357 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () from /home/boud/dev/deps/lib/libQt5Gui.so.5 #17 0x70ed1c65 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /home/boud/dev/deps/lib/libQt5Gui.so.5 #18 0x70eb387b in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /home/boud/dev/deps/lib/libQt5Gui.so.5 #19 0x7fffe7716cd0 in ?? () from /home/boud/dev/deps/plugins/platforms/../../lib/libQt5XcbQpa.so.5 #20 0x7fffebd40c84 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #21 0x7fffebd40ed8 in ?? () from /usr/lib64/libglib-2.0.so.0 #22 0x7fffebd40f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #23 0x708f69dc in QEventDispatcherGlib::processEvents(QFlags) () from /home/boud/dev/deps/lib/libQt5Core.so.5 #24 0x708a4b2b in QEventLoop::exec(QFlags) () from /home/boud/dev/deps/lib/libQt5Core.so.5 #25 0x708ac886 in QCoreApplication::exec() () from /home/boud/dev/deps/lib/libQt5Core.so.5 #26 0x00404fae in main (argc=1, argv=) at /home/boud/dev/krita/krita/main.cc:230 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357642] Calendar no longer highlights holidays like Bank Holidays, Christmas, New Year
https://bugs.kde.org/show_bug.cgi?id=357642 --- Comment #12 from Vadym Krevs --- Installed final Plasma 5.7 rpms from OBS. Still no joy with either Breeze or Breeze Dark. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365179] Crash when nudging a hidden layer
https://bugs.kde.org/show_bug.cgi?id=365179 Boudewijn Rempt changed: What|Removed |Added Latest Commit||http://commits.kde.org/krit ||a/f8336a8ff5b08b9b4342b6aa6 ||115f1d9f344423e Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Boudewijn Rempt --- Git commit f8336a8ff5b08b9b4342b6aa6115f1d9f344423e by Boudewijn Rempt. Committed on 07/07/2016 at 08:44. Pushed by rempt into branch 'krita/3.0'. M +3-0plugins/tools/basictools/kis_tool_move.cc http://commits.kde.org/krita/f8336a8ff5b08b9b4342b6aa6115f1d9f344423e -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 322946] MYSQL : picture collection and database on a server can handle only one user
https://bugs.kde.org/show_bug.cgi?id=322946 --- Comment #5 from Richard Mortimer --- Before I answer the direct question let me make it clear that a "user" in this context is actually a "connection" to the shared MySQL database from a running digikam instance. It does not matter whether that connection uses the same login details as another connection or not. It is still operating on the same data. MySQL has many methods to handle concurrency but locking the database is generally considered a last case scenario and even then it should only be used for short periods of time (sub-second) because any longer and other connections trying to access/change the database would just wait (hang) until the lock was released. It is difficult to provide a general solution description but there are a number of tools that can be used to build up a solutions: - first off the database has to be considered the master copy of the data. This is especially important if/when multiple instances of digikam are accessing the database simultaneously. At that point the internal digikam data structures have to be considered a cache (local copy) of the data that may be out of date. Really digikam has to be prepared to accept/work around SQL commands that fail because someone else has changed the shared database state. - this also means that the referential integrity constraints/checks are vital to the correct operation of the database because they help to ensure that no-one add duplicates or add references to tags/images that may have been added/deleted by someone else. - to my mind this is where the most important preparations for a multi-digikam shared operation mode come in. The database access routines in digikam should (and many are) be arranged as logical operations, e.g. add a tag and give me the database id of the tag. Those operations have to be well tested and able to work around changes made by other users. For instance the add a tag operation SQL might fail because another digikam has already added that tag. In that instance it should find the requested tag and load the data/return the tag id from the other record. - related to that digikam would need the ability to "rescan" the database in a similar manner to the way that it can rescan a filesystem. This allows it to easily pick up changes made by other users and integrate them into the Tags/Albums trees. I suspect that much of the images operation is already working in that way because digikam generally queries the database to find images etc. - the next thing related to concurrency is to consider the use of transactions to ensure that a group of operations either completes or does not. This may be of use when adding something like an image and there are a number of different tables that need updating with the properties of that image. This may not be strictly necessary because it might be enough that each table entry is considered on its own merits. But without it some image metadata may not get saved to the database if digikam crashes halfway through an operation. There is nothing stopping digikam allowing multiple users to have concurrent access to the database. I've used it myself but at the moment care has to be taken by the user to make it a mostly read-only sharing otherwise strange behaviour may occur. But there is a lot of preparation that could be made to prepare for more multi-user operation. Possibly the best way to do this is to write unit tests of the individual operations on something like the tags tree and within those tests explicitly inject changes as though they were from another user to make sure that the code handles them correctly. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 365184] New: Konsole segfaults
https://bugs.kde.org/show_bug.cgi?id=365184 Bug ID: 365184 Summary: Konsole segfaults Product: konsole Version: 16.04.2 Platform: Debian testing OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: quaz...@posteo.de Application: konsole (16.04.2) Qt Version: 5.6.1 Frameworks Version: 5.23.0 Operating System: Linux 4.6.0-1-amd64 x86_64 Distribution: Debian GNU/Linux testing (stretch) -- Information about the crash: - What I was doing when the application crashed: I don't know if this is relevant, but I just finished sending an email with KMail, then Konsole crashed. Fortunately I had everything in it running inside a byobu/tmux session, so nothing was really lost. This is already the second time within 2 or 3 days that this happened, but I cannnot recall what I did exactly during the first crash. Running Debian Testing with pretty recent packages. The crash can be reproduced sometimes. -- Backtrace: Application: Konsole (konsole), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fdc25bd1940 (LWP 12873))] Thread 3 (Thread 0x7fdc17f8e700 (LWP 12875)): #0 0x7fdc392b7dcd in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fdc31ccd382 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fdc31cceff7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fdc252d4a89 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7fdc35bf9808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fdc316a1464 in start_thread (arg=0x7fdc17f8e700) at pthread_create.c:334 #6 0x7fdc392c0e5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fdc25bce700 (LWP 12874)): #0 0x7fdc35bf1955 in QMutex::lock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fdc35e2284f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fdc30f6992d in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdc30f6a2cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fdc30f6a4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fdc35e231cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fdc35dcbe4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fdc35bf49e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fdc398b7515 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7fdc35bf9808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fdc316a1464 in start_thread (arg=0x7fdc25bce700) at pthread_create.c:334 #11 0x7fdc392c0e5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7fdc25bd1940 (LWP 12873)): [KCrash Handler] #6 0x7fdc3920b458 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #7 0x7fdc3920c8da in __GI_abort () at abort.c:89 #8 0x7fdc35be0f41 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fdc398c3531 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7fdc35dfb569 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fdc36705afc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7fdc3670b036 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fdc35dce0f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fdc35dcffba in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fdc35e22da3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fdc30f6a1a7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7fdc30f6a400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7fdc30f6a4ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fdc35e231af in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fdc35dcbe4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fdc35dd450c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7fdc395a3172 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so #23 0x7fdc391f85f0 in __libc_start_main (main=0x4006c0, argc=1, argv=0x7fff5bc5a128, init=, fini=, rtld_fini=, stack_
[kmix] [Bug 306338] konsole freezes when i select text
https://bugs.kde.org/show_bug.cgi?id=306338 Ruslan Kabatsayev changed: What|Removed |Added CC||b7.10110...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365158] option to change font color in task manager
https://bugs.kde.org/show_bug.cgi?id=365158 Jens Reuterberg changed: What|Removed |Added CC||ohy...@gmail.com --- Comment #4 from Jens Reuterberg --- The text colour should always (or per default) follow the colour theme in Breeze and themes that want this. Since there already exists an option in desktop theme to follow or NOT follow the colour of text set by colour theme, this is a non issue. (Change theme to Oxygen, change to some coloured text for the colour theme and observe that the theme does NOT change colour of text). So the choice to follow the text colour was made by MX Themes creator. In the above screenshot I notice the text in the taskmanager is far more readable than the icons and clock text in the chosen colour theme. To be honest testing it on my own using Gimp to change colours of text I notice that "white" (or #FCFCFC) is probably the best option there and I am slightly curious to know what colour you think would fit better and be more readable? Trying Magenta for example just hides it. My suggestion for fix would be to 1) edit the theme and hardcode the colour of the widget text. 2) change colour of "Window Text" slightly to better fit your needs 3) Change the font used for Taskmanager to something bigger and bolder to make it more readable no matter what colour 4) Change wallpaper 5) Change the theme to not allow transparent widgets in certain cases, like the taskmanager. I simply dont see an elegant solution which only goal is, in practice, to fix one broken theme. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365147] multimonitor fn key disabled
https://bugs.kde.org/show_bug.cgi?id=365147 --- Comment #4 from Martin Gräßlin --- > Don't ask me why now it's recognized as "p" and not "XF86Display". Given the output it generates Windows+P, which seems to be used by Microsoft Windows (confirmed by quick google search). @sebas: please add Qt::MetaModifier + Qt::Key_P as an alternative global shortcut. > Anyway it worked with every distro / DE. I guess they also added support for that shortcut. At least I was not aware of that shortcut. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365180] Unable to change desktop wallpaper with right click menu
https://bugs.kde.org/show_bug.cgi?id=365180 Kai Uwe Broulik changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Can you run plasmashell from console and see if you notice anything suspicious? Can you attach your ~/.config/plasma-org.kde.plasma.desktop-appletsrc? Perhaps somehow the desktop action for context menu got lost. You should be able to access the menu by clicking the toolbox (the three dots in the corner of your desktop). Check what it says in "Desktop Actions", ie. if there's a "Default menu" action assigned to the right mouse button. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 364472] show holidays also as text in main view
https://bugs.kde.org/show_bug.cgi?id=364472 Jens Reuterberg changed: What|Removed |Added CC||ohy...@gmail.com --- Comment #9 from Jens Reuterberg --- What we need is better communication to theme creators that certain changes are happening and they need to add bits to their themes like in this case a tiny marker with the correct naming. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365147] multimonitor fn key not working if mapped to Windows+p
https://bugs.kde.org/show_bug.cgi?id=365147 Martin Gräßlin changed: What|Removed |Added Summary|multimonitor fn key |multimonitor fn key not |disabled|working if mapped to ||Windows+p -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 248058] Message preview pane character encoding issue (utf-8, unicode)
https://bugs.kde.org/show_bug.cgi?id=248058 --- Comment #13 from Andre Heinecke --- Btw. I've asked about armor headers as part of another issue regarding gpgme_data_identify and the maintainer of gnupg also says that they should not be used and are not used by gnupg: https://bugs.gnupg.org/gnupg/issue2314 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #24 from Lukas Sommer --- It does not work for me. Tried with the latest installer at https://drive.google.com/open?id=0B7yq-xFihT0_MVBzOW9jZFA2NE0 under Windows 10, 64 bit. The install procedure starts correctly, but after reaching 100%, the installer window does not close, but does not react anymore. I have to close it with the task manager. When starting digikam it blocks my start menu bar and the hole computer during about a minute. After a minute, I can continue to work. But the digikam does not appear on the screen. (The process is neverthelass running, as I can see in the task manager.) However, showfoto works. The uninstaller does not work (does nothing). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365144] Plasma Panel shown in primary monitor and external too
https://bugs.kde.org/show_bug.cgi?id=365144 --- Comment #7 from rockonthemoo...@gmail.com --- After tweaking the desktop and removing extra Panel before, I removed the plasmarc and kscreen configs, but I can't reproduce it. Panel was present only in primary (laptop). But all windows opened in wrong screen (external). And XF86Display button still not working. So I created a new user.. and I couldn't reproduce it! Also, windows opened correctly in the primary screen too! XF86Display button still not working. So, good but weird anyway. Asking for closing bug? Maybe the whole point of it is that at every Plasma feature release user should not only wipe its own caches/configs, but create a new user? Because I wiped caches and configs in my home after 5.7 release enough times: I can see that it wasn't enough. I've recorded the first new user login. Plasma got brutally stuck at Ksplash. At second login it behaved correctly, apart from the following issues: - window decorations: defaulted to Plastik! - no shadows: resarting kwin fixed them (switched to OGL 3.1, defaulted to 2.0) - login screen misaligned in primary (laptop) screen when in dual monitor - 2 "Desktop" activities present! So 5 bugs. (youtube videos will follow soon) 2016-07-07 0:58 GMT+02:00 Sebastian Kügler via KDE Bugzilla < bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=365144 > > Sebastian Kügler changed: > >What|Removed |Added > > > Status|UNCONFIRMED |CONFIRMED > Ever confirmed|0 |1 > > --- Comment #6 from Sebastian Kügler --- > Thanks for the report! > > This looks like a problem with plasmashell, not with kscreen, if I > understand > correctly (seems about placement of the desktop / panels, not about screen > setup and restore at a lower level. > > Could you attach a screenshot of your whole desktop (both screens) when it > works and when it doesn't, for comparison? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365147] multimonitor fn key not working if mapped to Windows+p
https://bugs.kde.org/show_bug.cgi?id=365147 --- Comment #5 from rockonthemoo...@gmail.com --- (I'll do the "Portoguese" now. Also the Airplane mode button isn't working in Plasma! Works in gnome) KeyPress event, serial 37, synthetic NO, window 0x381, root 0xf6, subw 0x0, time 2997000, (78,646), root:(78,675), state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False 2016-07-07 11:23 GMT+02:00 Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=365147 > > --- Comment #4 from Martin Gräßlin --- > > Don't ask me why now it's recognized as "p" and not "XF86Display". > > Given the output it generates Windows+P, which seems to be used by > Microsoft > Windows (confirmed by quick google search). @sebas: please add > Qt::MetaModifier > + Qt::Key_P as an alternative global shortcut. > > > Anyway it worked with every distro / DE. > > I guess they also added support for that shortcut. At least I was not > aware of > that shortcut. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 365125] Win64 version cannot start
https://bugs.kde.org/show_bug.cgi?id=365125 --- Comment #25 from caulier.gil...@gmail.com --- Lukas, At end of install, Windows register base is patch with digiKam version, path, etc information, for future uninstall. It's sound like the process cannot be completed properly. - Do you have an anti-virus installed and enabled ? - Can you try to run installer with administrator rights ? Note : here under Win7, i need to setup Anti-virus to add an exception about DK installer and to run it as admin. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 343795] Accessing S/MIME encrypted attachments fails
https://bugs.kde.org/show_bug.cgi?id=343795 Andre Heinecke changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED CC||aheine...@intevation.de --- Comment #5 from Andre Heinecke --- I believe that this was fixed with https://phabricator.kde.org/D1964. I've only tested it with a backport of that fix to 4.14 (vendor/intevation) branch but it addressed exactly the problem that attachments to encrypted / signed S/MIME opaque (as outlook send) mails could not be opened. (And some other attachments to crypto mails like forwarded PGP/MIME mails) Now this works reliably. Please reopen if it still happens with the version that will be released with KDE/Applications-16.08 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365144] Plasma Panel shown in primary monitor and external too
https://bugs.kde.org/show_bug.cgi?id=365144 --- Comment #8 from rockonthemoo...@gmail.com --- https://youtu.be/aBqT-2a0-PI 2016-07-07 11:38 GMT+02:00 via KDE Bugzilla : > https://bugs.kde.org/show_bug.cgi?id=365144 > > --- Comment #7 from rockonthemoo...@gmail.com --- > After tweaking the desktop and removing extra Panel before, I removed the > plasmarc and kscreen configs, but I can't reproduce it. > Panel was present only in primary (laptop). But all windows opened in wrong > screen (external). And XF86Display button still not working. > > So I created a new user.. and I couldn't reproduce it! > Also, windows opened correctly in the primary screen too! > XF86Display button still not working. > So, good but weird anyway. Asking for closing bug? > > Maybe the whole point of it is that at every Plasma feature release user > should not only wipe its own caches/configs, but create a new user? > Because I wiped caches and configs in my home after 5.7 release enough > times: I can see that it wasn't enough. > > I've recorded the first new user login. Plasma got brutally stuck at > Ksplash. > At second login it behaved correctly, apart from the following issues: > - window decorations: defaulted to Plastik! > - no shadows: resarting kwin fixed them (switched to OGL 3.1, defaulted to > 2.0) > - login screen misaligned in primary (laptop) screen when in dual monitor > - 2 "Desktop" activities present! > > So 5 bugs. (youtube videos will follow soon) > > 2016-07-07 0:58 GMT+02:00 Sebastian Kügler via KDE Bugzilla < > bugzilla_nore...@kde.org>: > > > https://bugs.kde.org/show_bug.cgi?id=365144 > > > > Sebastian Kügler changed: > > > >What|Removed |Added > > > > > > > Status|UNCONFIRMED |CONFIRMED > > Ever confirmed|0 |1 > > > > --- Comment #6 from Sebastian Kügler --- > > Thanks for the report! > > > > This looks like a problem with plasmashell, not with kscreen, if I > > understand > > correctly (seems about placement of the desktop / panels, not about > screen > > setup and restore at a lower level. > > > > Could you attach a screenshot of your whole desktop (both screens) when > it > > works and when it doesn't, for comparison? > > > > -- > > You are receiving this mail because: > > You reported the bug. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 365185] New: Krita crashes when using Trust tablet
https://bugs.kde.org/show_bug.cgi?id=365185 Bug ID: 365185 Summary: Krita crashes when using Trust tablet Product: krita Version: 3.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: crash Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: jasminn...@gmail.com I have seen this around, but it has been marked as resolved and it still happens to me. I had this problem on 2.9, and I looked around and was told to download 3.0 (this was a long time ago, the version I downloaded is... "krita3-prealpha2-fa2b0d7?"), and it was no longer there. However, I have some other issues with that version, so I decided to download a newer version. This was also a while ago, and that version was "krita-3.0-Beta-master-962bfe1-x64." It crashed again. I decided to keep using the version that worked, but I decided to check out the stable 3.0 release, but I still have the problem there. I'm using a Trust slimline widescreen tablet. (http://www.trust.com/nl/product/16529-slimline-widescreen-tablet) Reproducible: Always Steps to Reproduce: 1. Open Krita 2. Put pen on tablet Actual Results: "krita.exe has stopped working" Expected Results: I can use the tablet to draw/select things/do whatever one does with a tablet -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365144] Plasma Panel shown in primary monitor and external too
https://bugs.kde.org/show_bug.cgi?id=365144 --- Comment #9 from rockonthemoo...@gmail.com --- https://youtu.be/GsHZmf4i_jI 2016-07-07 11:53 GMT+02:00 via KDE Bugzilla : > https://bugs.kde.org/show_bug.cgi?id=365144 > > --- Comment #8 from rockonthemoo...@gmail.com --- > https://youtu.be/aBqT-2a0-PI > > > > 2016-07-07 11:38 GMT+02:00 via KDE Bugzilla : > > > https://bugs.kde.org/show_bug.cgi?id=365144 > > > > --- Comment #7 from rockonthemoo...@gmail.com --- > > After tweaking the desktop and removing extra Panel before, I removed the > > plasmarc and kscreen configs, but I can't reproduce it. > > Panel was present only in primary (laptop). But all windows opened in > wrong > > screen (external). And XF86Display button still not working. > > > > So I created a new user.. and I couldn't reproduce it! > > Also, windows opened correctly in the primary screen too! > > XF86Display button still not working. > > So, good but weird anyway. Asking for closing bug? > > > > Maybe the whole point of it is that at every Plasma feature release user > > should not only wipe its own caches/configs, but create a new user? > > Because I wiped caches and configs in my home after 5.7 release enough > > times: I can see that it wasn't enough. > > > > I've recorded the first new user login. Plasma got brutally stuck at > > Ksplash. > > At second login it behaved correctly, apart from the following issues: > > - window decorations: defaulted to Plastik! > > - no shadows: resarting kwin fixed them (switched to OGL 3.1, defaulted > to > > 2.0) > > - login screen misaligned in primary (laptop) screen when in dual monitor > > - 2 "Desktop" activities present! > > > > So 5 bugs. (youtube videos will follow soon) > > > > 2016-07-07 0:58 GMT+02:00 Sebastian Kügler via KDE Bugzilla < > > bugzilla_nore...@kde.org>: > > > > > https://bugs.kde.org/show_bug.cgi?id=365144 > > > > > > Sebastian Kügler changed: > > > > > >What|Removed |Added > > > > > > > > > > > > Status|UNCONFIRMED |CONFIRMED > > > Ever confirmed|0 |1 > > > > > > --- Comment #6 from Sebastian Kügler --- > > > Thanks for the report! > > > > > > This looks like a problem with plasmashell, not with kscreen, if I > > > understand > > > correctly (seems about placement of the desktop / panels, not about > > screen > > > setup and restore at a lower level. > > > > > > Could you attach a screenshot of your whole desktop (both screens) when > > it > > > works and when it doesn't, for comparison? > > > > > > -- > > > You are receiving this mail because: > > > You reported the bug. > > > > -- > > You are receiving this mail because: > > You reported the bug. > > > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365158] option to change font color in task manager
https://bugs.kde.org/show_bug.cgi?id=365158 apache changed: What|Removed |Added CC||sabayo...@gmail.com --- Comment #5 from apache --- @ Jens Reuterberg: > The text colour should always (or per default) follow the colour theme in > Breeze and themes that want this. Even if the choice to follow the text color was made by MX Themes creator I don't want to be dependent on it. I want to be able to download a theme from kde-look and be able to modify to my preference. And for this I need to have options and options must be described in techbase guidelines. I gave it only as an example but during a next few years period of Plasma 5 existence (until Plasma 6) I will change themes and wallpapers dozens of times. So, don't focus on this particular example. I could easily find an example of wallpaper that is white and make text in task manager with this theme become invisible. Now I am forced to match wallpaper to theme. And that's the problem. I want to be able to adjust text of task manager every time I change wallpaper, and that may be whenever I want, even every week. Again don't focus on this particular wallpaper but understand the problem of lack of options. > Since there already exists an option in desktop theme to follow or NOT follow the colour of text set by colour theme, this is a non issue. (Change theme to Oxygen, change to some coloured text for the colour theme and observe that the theme does NOT change colour of text). So the choice to follow the text colour was made by MX Themes creator. This is not the same as set color for task manager text independent from theme, widget color or whatever. What if I change this theme so that it doesn't follow the color of text set by color theme. What color would task manager follow then and why it is not clearly explained in techbase guidelines? > My suggestion for fix would be to 1) edit the theme and hardcode the colour > of the widget text. 2) change colour of "Window Text" slightly to better fit > your needs 3) Change the font used for Task manager to something bigger and > bolder to make it more readable no matter what colour 4) Change wallpaper 5) > Change the theme to not allow transparent widgets in certain cases, like the > task manager. As a user I don't want to be dependent on what theme author finds looks good or what is your opinion about what looks good or bad. I don't want to change widget text because for other widgets it may suit me fine. > I simply don't see an elegant solution which only goal is, in practice, to > fix one broken theme. What if I want to use other themes that are made the same? Well, that's hypothetical question, I have not checked every theme. I don't understand what you mean by elegant solution. I need an easy solution. If this theme is broken I don't want to be forced to beg theme author to fix it. I want to be able to do it myself in the easiest possible way, which is adjust color of text of task manager. What I request is options in configuration file and an easy to understand description in techbase so that every user can download theme from kde-look and adjust it to his/her preference or even mix different elements from different themes (for example to mix icons). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357642] Calendar no longer highlights holidays like Bank Holidays, Christmas, New Year
https://bugs.kde.org/show_bug.cgi?id=357642 --- Comment #13 from apache --- have a look https://forum.kde.org/viewtopic.php?f=285&t=133463#p359230 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 gajdos.mi...@gmail.com changed: What|Removed |Added CC|gajdos.mi...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365147] multimonitor fn key not working if mapped to Windows+p
https://bugs.kde.org/show_bug.cgi?id=365147 --- Comment #6 from Martin Gräßlin --- > Also the Airplane mode button isn't working in Plasma! Works in gnome please report that in a new bug report, otherwise it's getting tricky to properly track this. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 322946] MYSQL : picture collection and database on a server can handle only one user
https://bugs.kde.org/show_bug.cgi?id=322946 --- Comment #6 from swatilodh...@gmail.com --- (In reply to Richard Mortimer from comment #5) > Before I answer the direct question let me make it clear that a "user" in > this context is actually a "connection" to the shared MySQL database from a > running digikam instance. It does not matter whether that connection uses > the same login details as another connection or not. It is still operating > on the same data. > > MySQL has many methods to handle concurrency but locking the database is > generally considered a last case scenario and even then it should only be > used for short periods of time (sub-second) because any longer and other > connections trying to access/change the database would just wait (hang) > until the lock was released. > > It is difficult to provide a general solution description but there are a > number of tools that can be used to build up a solutions: > > - first off the database has to be considered the master copy of the data. > This is especially important if/when multiple instances of digikam are > accessing the database simultaneously. At that point the internal digikam > data structures have to be considered a cache (local copy) of the data that > may be out of date. Really digikam has to be prepared to accept/work around > SQL commands that fail because someone else has changed the shared database > state. > > - this also means that the referential integrity constraints/checks are > vital to the correct operation of the database because they help to ensure > that no-one add duplicates or add references to tags/images that may have > been added/deleted by someone else. After your yesterday's patch on this https://bugs.kde.org/show_bug.cgi?id=355831, I think referential integrity is mostly done, so duplicates could now be avoided. > > - to my mind this is where the most important preparations for a > multi-digikam shared operation mode come in. The database access routines in > digikam should (and many are) be arranged as logical operations, e.g. add a > tag and give me the database id of the tag. Those operations have to be well > tested and able to work around changes made by other users. For instance the > add a tag operation SQL might fail because another digikam has already added > that tag. In that instance it should find the requested tag and load the > data/return the tag id from the other record. For 1) and 3) point you wrote: In order to ensure that SQL query made by a user doesn't fail (if another user has just made a change in the DB), I think we could use INSERT IGNORE INTO or REPLACE statements, instead of simply INSERT query? If there's no duplicate, INSERT IGNORE INTO will INSERT as general, else IGNORE will discard silently without an error. Thus, preventing duplicate records. Or REPLACE could be better, in order to get the latest change in the DB. > - related to that digikam would need the ability to "rescan" the database in > a similar manner to the way that it can rescan a filesystem. This allows it > to easily pick up changes made by other users and integrate them into the > Tags/Albums trees. I suspect that much of the images operation is already > working in that way because digikam generally queries the database to find > images etc. How to go with the "re-scanning" of DB, so it's updated for all users, if changes are made by another user? > - the next thing related to concurrency is to consider the use of > transactions to ensure that a group of operations either completes or does > not. This may be of use when adding something like an image and there are a > number of different tables that need updating with the properties of that > image. This may not be strictly necessary because it might be enough that > each table entry is considered on its own merits. But without it some image > metadata may not get saved to the database if digikam crashes halfway > through an operation. Using TRANSACTIONS for all SQL queries? Or with add/delete/update a Tag/image/album would suffice? > There is nothing stopping digikam allowing multiple users to have concurrent > access to the database. I've used it myself but at the moment care has to be > taken by the user to make it a mostly read-only sharing otherwise strange > behaviour may occur. But there is a lot of preparation that could be made to > prepare for more multi-user operation. Possibly the best way to do this is > to write unit tests of the individual operations on something like the tags > tree and within those tests explicitly inject changes as though they were > from another user to make sure that the code handles them correctly. If I'm right, making DB "read only" for users could definitely prevent lot of confusion that could occur in DB. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365180] Unable to change desktop wallpaper with right click menu
https://bugs.kde.org/show_bug.cgi?id=365180 --- Comment #2 from andrewn...@gmail.com --- Created attachment 99917 --> https://bugs.kde.org/attachment.cgi?id=99917&action=edit Requested file -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 362108] crash when moving images to newly created album
https://bugs.kde.org/show_bug.cgi?id=362108 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|BACKTRACE |FIXED Version Fixed In||5.1.0 --- Comment #4 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 217532] Crash while using Download Photos with Digikam link from Device Notifier
https://bugs.kde.org/show_bug.cgi?id=217532 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 215648] When I try to import the pictures from Memory Card to My compiture digiKam crashed.
https://bugs.kde.org/show_bug.cgi?id=215648 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 215021] Crash importing photos from SD card into Digikam
https://bugs.kde.org/show_bug.cgi?id=215021 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 215854] download pictures to hd in digikam
https://bugs.kde.org/show_bug.cgi?id=215854 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 365186] New: hide system partitions (root and home and ..) from external devices
https://bugs.kde.org/show_bug.cgi?id=365186 Bug ID: 365186 Summary: hide system partitions (root and home and ..) from external devices Product: dolphin Version: 15.12.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: rockonthemoo...@gmail.com By default Dolphin shows system partitions like root and home under External Devices in Places Panel. These should be hidden because are redundant, maningless and simply should not be shown to normal user. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 214874] picture download from cf-card
https://bugs.kde.org/show_bug.cgi?id=214874 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 211009] digikam batch raw converter
https://bugs.kde.org/show_bug.cgi?id=211009 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 213916] Digikam crashed when building the collection
https://bugs.kde.org/show_bug.cgi?id=213916 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 195448] random system hangs when handling RAW images in digikam
https://bugs.kde.org/show_bug.cgi?id=195448 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 218987] After several days idle, Digikam crashed during closing.
https://bugs.kde.org/show_bug.cgi?id=218987 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 218765] drag digikam photo to thunderbird 3.0 email attachment section
https://bugs.kde.org/show_bug.cgi?id=218765 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 227123] digikam crashes when deleting pictures from camera
https://bugs.kde.org/show_bug.cgi?id=227123 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 215558] leaving the "THEME" area caused fatel error sig 11 sigsegv Then it crashed
https://bugs.kde.org/show_bug.cgi?id=215558 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 364206] Crash when moving images outside Digikam
https://bugs.kde.org/show_bug.cgi?id=364206 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 313523] while move images from one folder to other there is an error report and the image is delete
https://bugs.kde.org/show_bug.cgi?id=313523 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 355212] Crash While editing and playback
https://bugs.kde.org/show_bug.cgi?id=355212 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In|5.0.0 |5.1.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 365187] New: enable Airplane mode key
https://bugs.kde.org/show_bug.cgi?id=365187 Bug ID: 365187 Summary: enable Airplane mode key Product: frameworks-kglobalaccel Version: 5.23.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: rockonthemoo...@gmail.com CC: kdelibs-b...@kde.org Airplane mode key ( fn+f2) isn't working in Plasma, works for me in gnome. Asus model X554LA xev output: KeyPress event, serial 37, synthetic NO, window 0x381, root 0xf6, subw 0x0, time 2997000, (78,646), root:(78,675), state 0x10, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 365147] multimonitor fn key not working if mapped to Windows+p
https://bugs.kde.org/show_bug.cgi?id=365147 --- Comment #7 from rockonthemoo...@gmail.com --- done https://bugs.kde.org/show_bug.cgi?id=365187 2016-07-07 12:34 GMT+02:00 Martin Gräßlin via KDE Bugzilla < bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=365147 > > --- Comment #6 from Martin Gräßlin --- > > Also the Airplane mode button isn't working in Plasma! Works in gnome > > please report that in a new bug report, otherwise it's getting tricky to > properly track this. > > -- > You are receiving this mail because: > You reported the bug. > -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354074] Cant load most of pictures without further error messages or additional informations
https://bugs.kde.org/show_bug.cgi?id=354074 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.1.0 --- Comment #2 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361317] Digicam crash when using face recognition
https://bugs.kde.org/show_bug.cgi?id=361317 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.1.0 Resolution|WAITINGFORINFO |FIXED --- Comment #3 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 338072] Digikam se cuelga y se cierra al iniciar la detección de rostro
https://bugs.kde.org/show_bug.cgi?id=338072 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|BACKTRACE |INVALID -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365180] Unable to change desktop wallpaper with right click menu
https://bugs.kde.org/show_bug.cgi?id=365180 --- Comment #3 from andrewn...@gmail.com --- (In reply to Kai Uwe Broulik from comment #1) > Can you run plasmashell from console and see if you notice anything > suspicious? Can you attach your > ~/.config/plasma-org.kde.plasma.desktop-appletsrc? Perhaps somehow the > desktop action for context menu got lost. > You should be able to access the menu by clicking the toolbox (the three > dots in the corner of your desktop). Check what it says in "Desktop > Actions", ie. if there's a "Default menu" action assigned to the right mouse > button. Thanks. I've gotten rid of the toolbox on my main activity, so there's really no way I can open desktop settings other than opening a new activity. Running plasmashell didn't print anything, but here's what I got immediately after doing "kquitapp plasmashell && kstart plasmashell": >http://pastebin.com/iXL4zkHS Leaving it running gives me: >QXcbConnection: XCB error: 2 (BadValue), sequence: 3217, resource id: >25165828, major code: 142 (Unknown), minor code: 3 >QXcbConnection: XCB error: 2 (BadValue), sequence: 3388, resource id: >123732016, major code: 142 (Unknown), minor code: 3 >etc -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 343015] when crop an raw image there appears a black bam on the right
https://bugs.kde.org/show_bug.cgi?id=343015 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.1.0 Resolution|WAITINGFORINFO |FIXED --- Comment #7 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 352955] digikam crashes when I start the geolocation
https://bugs.kde.org/show_bug.cgi?id=352955 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.1.0 Resolution|BACKTRACE |FIXED --- Comment #5 from caulier.gil...@gmail.com --- The XML data problem is already reported to another file. About the crash is not reproducible with last 5.0.0 I close this file now. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365188] New: Give normal default sizes to dialogs
https://bugs.kde.org/show_bug.cgi?id=365188 Bug ID: 365188 Summary: Give normal default sizes to dialogs Product: systemsettings Version: 5.6.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_fonts Assignee: unassigned-b...@kde.org Reporter: tipos...@tiscali.it CC: unassigned-b...@kde.org See the attached screenshot. My screen is super large, and I have to scroll quite a lot to see all the options. Quite annoying. Also, I would like to understand why by default it gets italic style Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 359817] digiKam crashed while scanning faces
https://bugs.kde.org/show_bug.cgi?id=359817 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.1.0 Resolution|WAITINGFORINFO |FIXED Component|general |Faces-Engine --- Comment #2 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365188] Give normal default sizes to dialogs
https://bugs.kde.org/show_bug.cgi?id=365188 --- Comment #1 from Salvo "LtWorf" Tomaselli --- Created attachment 99919 --> https://bugs.kde.org/attachment.cgi?id=99919&action=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 336979] Digikam crash during facial recognition when closed before finished
https://bugs.kde.org/show_bug.cgi?id=336979 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Version Fixed In||5.1.0 --- Comment #4 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 337898] pictures imported from camera are not available in folder
https://bugs.kde.org/show_bug.cgi?id=337898 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.1.0 --- Comment #5 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 365189] New: "Print Preview..." doesn't show exact preview of printing
https://bugs.kde.org/show_bug.cgi?id=365189 Bug ID: 365189 Summary: "Print Preview..." doesn't show exact preview of printing Product: kate Version: unspecified Platform: unspecified OS: All Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: emre...@gmail.com Version 15.12.3 was not listed (BTW) When I click on "Print Preview..." it shows exactly how the /contents/ of the document will look. However, it does not show the accoutrements, such as border, header, footer, line numbers etc. I want to know exactly how the pages are going to look /before/ I print them. Is the margin going to cause spill over to three pages instead of two? etc. Reproducible: Always Steps to Reproduce: 1. type a document 2. File -> Print ... 3. Select/Make sure selected: Options -> Color Mode: Color; Options -> Duplex Printing: Long Side; Text Settings -> Print Line Numbers; Header & Footer -> Print Header; Header and Footer -> Print Footer 4. Print the document 5. File -> Print Preview Actual Results: No headers, footers, or line numbers or color Expected Results: Print Preview to look exactly like what I have printed as a physical copy -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 345106] Crash while saving
https://bugs.kde.org/show_bug.cgi?id=345106 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.1.0 Resolution|BACKTRACE |FIXED --- Comment #4 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 327961] digiKam crash at video playing
https://bugs.kde.org/show_bug.cgi?id=327961 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.1.0 Resolution|BACKTRACE |FIXED --- Comment #4 from caulier.gil...@gmail.com --- This problem is not reproducible with last 5.0.0 I close this file now. Re-open it if necessary. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365158] option to change font color in task manager
https://bugs.kde.org/show_bug.cgi?id=365158
--- Comment #6 from Jens Reuterberg ---
> Even if the choice to follow the text color was made by MX Themes creator I
> don't want to be dependent on it. I want to be able to download a theme from
> kde-look and be able to modify to my preference.
Chances are this will not happen though. There are plans for a theme creator
but this is currently on ice as plans to ensure Plasma 5.8 as an LTS are
underfoot - and stability/polish, instead of features, are more relevant to
work on. Such a thing would be something packaged within the Plasma-sdk package
and allow for an easier way to sort SVG's etc to ensure simplicity (sort of
like Theme Explorer in the Plasma-sdk package which I implore you to check out)
Essentially if you make a theme which says "Make all backgrounds in widgets
bright pink", someone downloads your theme and use it - its very tricky for us
to "fix problem with all this bright pink" except suggest that that person
contact the theme creator.
> This is not the same as set color for task manager text independent from
> theme, widget color or whatever. What if I change this theme so that it
> doesn't follow the color of text set by color theme. What color would task
> manager follow then and why it is not clearly explained in techbase
> guidelines?
It follows the Window theme colour. Edit the Window Text Colour in Colour
settings. This will affect ALL text in the window theme though so the solution
isn't optimal.
> What if I want to use other themes that are made the same? Well, that's
> hypothetical question, I have not checked every theme.
Then you wont be able to see the text as well as you would prefer.
> I don't understand what you mean by elegant solution.
A way where the solution for a fringe issue isn't impeding more common use
cases. A solution where simplicity is part of it. If you can't marry these two
into a solution, the solution isn't elegant and as the choice then is "hurt the
majority" or "hurt the minority" the choice is obvious. ("The need of the many
outweigh the need of the few" to quote Mr Spock)
> What I request is options in configuration file and an easy to understand
> description in techbase so that every user can download theme from kde-look
> and adjust it to his/her preference or even mix different elements from
> different themes (for example to mix icons).
That is impossible to do. Theming in Plasma is extremely flexible from a theme
creators POV and the attempt to have a mix-and-match setting was underwhelming
and buggy. Hence it was removed - if a theme editor is created in the future,
hopefully that will work to cover your needs too.
Until then, you have to either
1) edit the theme yourself using for example "Theme Explorer",
2) ask the creator to make a theme with hardcoded text colours for different
elements,
3) change wallpaper,
4) change the colour of the Window Text,
5) Change font to something more readable
6) Swap to a different theme
7) Hang in there and hope for some dev to create a theme editor from scratch
that covers your needs.
Now I am not the end decider, but I was asked in here as someone representing
the VDG - and from our POV unless an elegant solution presents itself, with a
dev attached that can create this solution, there simply isn't anything that
CAN be done except suggest the above fixes to your issue.
As for an easier to understand techbase documentation (or more extensive) and
easier to understand RC files - I can only agree and I wish I could say "a
theme creator coming right up" - but that would just be lying to you. We want
to create a better theming system for the future, sketches exist, but so far
thats as far as we can get. The dev for the taskmanager has stated that he
can't add this new feature to the taskmanager so that avenue is closed too
leaving you with the seven options above to fix your issue.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 365183] The animated icon of opening an application remains even after app is loaded
https://bugs.kde.org/show_bug.cgi?id=365183 --- Comment #1 from tro...@free.fr --- Created attachment 99920 --> https://bugs.kde.org/attachment.cgi?id=99920&action=edit You can see the blue circle around Okular's even after Okular finished loading -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 364670] kmail crash on search
https://bugs.kde.org/show_bug.cgi?id=364670 Thaodan changed: What|Removed |Added Attachment #99781|0 |1 is obsolete|| --- Comment #4 from Thaodan --- Created attachment 99921 --> https://bugs.kde.org/attachment.cgi?id=99921&action=edit new crash information with debug symboles -- You are receiving this mail because: You are watching all bug changes.
