[krita] [Bug 370626] New: cursor and drawing disappears when over the document
https://bugs.kde.org/show_bug.cgi?id=370626 Bug ID: 370626 Summary: cursor and drawing disappears when over the document Product: krita Version: 3.0.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: myoonstu...@inwind.it Hi, I am on a laptop running windows 7pro 64 bit and with all the version of Krita I've downloaded when I create a document and start let say to draw something inside, neither what I draw and the cursor are visible. all white. what I did appears only when I resize the window of krita software. but after agai all keeps repeating, no cursor no drawing. Reproducible: Always Steps to Reproduce: 1.create document 2. select brush tool 3. start drawing Actual Results: no drawing, nothing on the canvas and the cursor when I am inside the area of the document just created disappears Expected Results: I should see the lines the drawing I am doing but nothing is visible until I move or resize the all windows of the Krita software -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 370626] cursor and drawing disappears when over the document
https://bugs.kde.org/show_bug.cgi?id=370626 --- Comment #1 from Diego --- OK, I found a solution, I've unchecked "OPEN GL" option in the settings and now all works fine, Probably is lacking on my graphic card driver, so maybe is not a bug of Krita but a missing option of my graphic card, in that case sorry for the not useful report and you can delete it. Thanks a lot. Regards -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356892] system hangs after screensave
https://bugs.kde.org/show_bug.cgi?id=356892 Diego changed: What|Removed |Added CC||diego...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #75 from Diego --- If I still have the problem (same as title) in 5.7.1 should I report it here or do you encourage opening a separate bug? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #86 from Diego --- (In reply to Sebastian Kügler from comment #81) > Yes, neon dev unstable has all these fixes. I tried neon dev unstable, and situation looked much better. I still had a problem with panel having a "dead extension" (empty grey non-clickable panel) on the non primary display, when primary display is set to external monitor, but I'll open a separate bug for that. Thanks for the improvements. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367668] New: Plasma uses only part of vertical screen space in single display mode
https://bugs.kde.org/show_bug.cgi?id=367668 Bug ID: 367668 Summary: Plasma uses only part of vertical screen space in single display mode Product: plasmashell Version: 5.7.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: diego...@zoho.com CC: bhus...@gmail.com, plasma-b...@kde.org Plasma seems to use (or show) only the upper part of the screen. I have a 1920x1080 display in my laptop, but when I login in Plasma I see a black rectangle area covering the most of the bottom of the screen. The mouse cursor cannot go in the black area, only the displayed area is accessible, but Plasma panel isn't shown in the displayed area. The problem happens both with X11 Intel driver and modesetting driver. $ rpm -q xorg-x11-drv-intel xorg-x11-drv-intel-2.99.917-19.20151206.fc23.x86_64 All the area if I plug an external monitor and use a dual screen setup (though other problems arise). Problem is not happening with LXQt which is using libkscreen too. Let me know if you need more informations from me, I'll try to respond as quickly as possible. Reproducible: Always Steps to Reproduce: 1. login in Plasma with only one display Actual Results: Not all screen size used Expected Results: All screen size used -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367668] Plasma uses only part of vertical screen space in single display mode
https://bugs.kde.org/show_bug.cgi?id=367668 --- Comment #1 from Diego --- Created attachment 100710 --> https://bugs.kde.org/attachment.cgi?id=100710&action=edit Screenshot showing the problem Screenshot showing the problem. Strange thing is that I'm seeing the black area at the bottom, while Ksnapshot shows it at the top. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367668] Plasma uses only part of vertical screen space in single display mode
https://bugs.kde.org/show_bug.cgi?id=367668 --- Comment #2 from Diego --- > All the area if I plug an external monitor and use a dual screen setup > (though other problems arise). I meant "All the area available is used if ..." -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #80 from Diego --- (In reply to Sebastian Kügler from comment #79) > This bug is fixed in Plasma 5.8. If you could test against that, it would be > nice. Is KDE Neon dev unstable ok to test that? http://files.kde.org/neon/images/neon-devedition-gitunstable/current/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #200 from Diego --- Strongly agree it is time to say YES or NO. answer is a simple answer. Yes or NO -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 360808] New: KAlgebra crash on exit
https://bugs.kde.org/show_bug.cgi?id=360808 Bug ID: 360808 Summary: KAlgebra crash on exit Product: kalgebra Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: diego...@zoho.com After doing some math I closed kalgebra and it crashed with the following backtrace: Thread no. 1 (10 frames) #0 QHash::findNode at /usr/include/qt5/QtCore/qhash.h:959 #1 QHash::contains at /usr/include/qt5/QtCore/qhash.h:941 #2 Analitza::ExpressionTypeChecker::isVariableDefined at /usr/src/debug/analitza-15.12.1/analitza/expressiontypechecker.cpp:338 #3 Analitza::ExpressionTypeChecker::visit at /usr/src/debug/analitza-15.12.1/analitza/expressiontypechecker.cpp:322 #4 Analitza::Ci::accept at /usr/src/debug/analitza-15.12.1/analitza/variable.cpp:44 #5 Analitza::ExpressionTypeChecker::solve at /usr/src/debug/analitza-15.12.1/analitza/expressiontypechecker.cpp:145 #6 Analitza::ExpressionTypeChecker::visit at /usr/src/debug/analitza-15.12.1/analitza/expressiontypechecker.cpp:661 #7 Analitza::Apply::accept at /usr/src/debug/analitza-15.12.1/analitza/apply.cpp:96 #8 Analitza::ExpressionTypeChecker::visit at /usr/src/debug/analitza-15.12.1/analitza/expressiontypechecker.cpp:816 #9 Analitza::Container::accept at /usr/src/debug/analitza-15.12.1/analitza/container.cpp:81 Reproducible: Sometimes Steps to Reproduce: 1. Open KAlgebra 2. Do some math 3. Close KAlgebra Actual Results: Crash Expected Results: No crash Here is report on Fedora bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1314370 -- You are receiving this mail because: You are watching all bug changes.
[kalgebra] [Bug 360808] KAlgebra crash on exit
https://bugs.kde.org/show_bug.cgi?id=360808 Diego changed: What|Removed |Added See Also||https://bugzilla.redhat.com ||/show_bug.cgi?id=1314370 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 356703] Plasmashell crash when is pressed "connect" on a configured VPN
https://bugs.kde.org/show_bug.cgi?id=356703 Diego changed: What|Removed |Added CC||diego...@zoho.com --- Comment #4 from Diego --- (In reply to Jan Grulich from comment #1) > Any backtrace? I cannot reproduce this. I have quite a similar problem which is always reproducible. The only real difference I have from the original description is that VPN connects successfully after the crash. So: - open Plasma Network Manager; - click "Connect" on a configured VPN connection; - Plasma crashes; - VPN connects correctly; - click "Disconnect" doesn't trigger the crash - clicking again "Connect" triggers the problem. Backtrace is here: https://retrace.fedoraproject.org/faf/reports/1038440/ which is linked to problem: https://retrace.fedoraproject.org/faf/problems/1857705/ which is linked to several bugs, but the most relevant seems to be: https://bugzilla.redhat.com/show_bug.cgi?id=1259472 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 Diego changed: What|Removed |Added CC||diego...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #120 from Diego --- (In reply to Lamarque V. Souza from comment #119) > > This bug entry is about the crash when changing MTU value. You have to open > another bug report about other bugs. Weird thing is that: - VPN crash reports get marked (for example by Jan Grulich) as a duplicate of this bug - you previous patch against qtdeclarative fixed the problem with VPN too. So there's probably no need to open separate reports yet (or we can just "unduplicate" one of the VPN ones). -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #62 from Diego --- Relevant article: http://vizzzion.org/blog/2016/05/multiscreen-in-plasma-5-7-and-beyond/ So feedback on Plasma git master or 5.7 is welcome. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #109 from Diego --- (In reply to Lamarque V. Souza from comment #108) > Created attachment 99222 [details] > Fix crash in libQt5Qml > > This patch against qtdeclarative-opensource-src-5.5.1 fixes the problem for > me. Somehow the items QList shrinks from 12 items to 10 items during the for > loop, which causes the crash. Please test this patch and report if it fixes > the problem for you too. Here are Fedora 23 packages including the patch, for those interested in testing: https://cloud.wyffy.com/index.php/s/C4zaHblCObJaxIr I'll report my testing results soon. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #110 from Diego --- (In reply to Diego from comment #109) > (In reply to Lamarque V. Souza from comment #108) > > Created attachment 99222 [details] > > Fix crash in libQt5Qml > > > > This patch against qtdeclarative-opensource-src-5.5.1 fixes the problem for > > me. Somehow the items QList shrinks from 12 items to 10 items during the for > > loop, which causes the crash. Please test this patch and report if it fixes > > the problem for you too. > > Here are Fedora 23 packages including the patch, for those interested in > testing: > https://cloud.wyffy.com/index.php/s/C4zaHblCObJaxIr > I'll report my testing results soon. @Lamarque: so far so good; I haven't been able to reproduce the crash with your patch applied. For those on Fedora 23/24, please don't use my packages, as now an official package has been submitted for testing: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e78000fedc https://bugzilla.redhat.com/show_bug.cgi?id=1259472 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 356739] New: Gwenview ignores EXIF rotation on jpg files without file extension
https://bugs.kde.org/show_bug.cgi?id=356739 Bug ID: 356739 Summary: Gwenview ignores EXIF rotation on jpg files without file extension Product: gwenview Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: diego...@zoho.com CC: myr...@kde.org Gwenview ignores EXIF rotation on jpg files without file extension, it rotates the image correctly just by renaming the file with the extension (can be ".jpg" or even the unappropriate ".png") Reproducible: Always Steps to Reproduce: 1. Open in Gwenview a jpg image which has EXIF rotation data but hasn't ".jpg" file extension 2. Image will appear unrotated (EXIF rotation value ignored) 3. Just rename the file by adding ".jpg" or even ".png" (even if the file is a jpg) and open it Gwenview 4. Image will apper rotate (according to EXIF rotation) For reference, GIMP gets rotation right even on files without file extension. Actual Results: Image not rotated. Expected Results: Image rotated according to EXIF. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 352055] plasma-pa plasmoid not shown in systemtray after startup
https://bugs.kde.org/show_bug.cgi?id=352055 Diego changed: What|Removed |Added CC||diego...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 --- Comment #147 from Diego --- developers could be clear and answer this question and not give more bluntly: are you going to continue to ignore this request or going to re-add we ask? Components virtual desktops with different graphics for each desktop. Yes or NO Thank you PS: I do not speak English translators use to read and write in the forum, sorry if I do not fully understand -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 Diego changed: What|Removed |Added CC||diego...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 357831] New: Baloo crashed at every logout / shutdown
https://bugs.kde.org/show_bug.cgi?id=357831 Bug ID: 357831 Summary: Baloo crashed at every logout / shutdown Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: diego...@zoho.com Application: akonadi_baloo_indexer (4.14) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.2.8-300.fc23.x86_64 x86_64 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: Every time I logout or shutdown a Plasma session I get this backtrace. The crash can be reproduced every time. -- Backtrace: Application: Agente di indicizzazione Baloo di Akonadi (akonadi_baloo_indexer), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 0x7faf4caada98 in raise () at /lib64/libc.so.6 #7 0x7faf4caaf69a in abort () at /lib64/libc.so.6 #8 0x7faf4d3e2aed in __gnu_cxx::__verbose_terminate_handler() () at /lib64/libstdc++.so.6 #9 0x7faf4d3e0936 in () at /lib64/libstdc++.so.6 #10 0x7faf4d3e0981 in () at /lib64/libstdc++.so.6 #11 0x7faf4d3e0b99 in () at /lib64/libstdc++.so.6 #12 0x7faf5062457d in ChertTable::block_to_cursor(Cursor*, int, unsigned int) const () at /lib64/libxapian.so.22 #13 0x7faf5062470f in ChertTable::find(Cursor*) const () at /lib64/libxapian.so.22 #14 0x7faf506007f6 in ChertCursor::find_entry(std::__cxx11::basic_string, std::allocator > const&) () at /lib64/libxapian.so.22 #15 0x7faf50616709 in ChertPostListTable::get_chunk(std::__cxx11::basic_string, std::allocator > const&, unsigned int, bool, Chert::PostlistChunkReader**, Chert::PostlistChunkWriter**) () at /lib64/libxapian.so.22 #16 0x7faf50617b50 in ChertPostListTable::merge_changes(std::map, std::allocator >, std::map, std::less, std::allocator > > >, std::less, std::allocator > >, std::allocator, std::allocator > const, std::map, std::less, std::allocator > > > > > > const&, std::map, std::allocator > > const&, std::map, std::allocator >, std::pair, std::less, std::allocator > >, std::allocator, std::allocator > const, std::pair > > > const&) () at /lib64/libxapian.so.22 #17 0x7faf506074e5 in ChertWritableDatabase::flush_postlist_changes() const () at /lib64/libxapian.so.22 #18 0x7faf506075f3 in ChertWritableDatabase::commit() () at /lib64/libxapian.so.22 #19 0x55b8c3156641 in EmailIndexer::~EmailIndexer() () #20 0x55b8c3156699 in EmailIndexer::~EmailIndexer() () #21 0x55b8c315124f in BalooIndexingAgent::~BalooIndexingAgent() () #22 0x55b8c31515b9 in BalooIndexingAgent::~BalooIndexingAgent() () #23 0x7faf4f9d3c2d in Akonadi::AgentBase::init(Akonadi::AgentBase*) () at /lib64/libakonadi-kde.so.4 #24 0x55b8c3156593 in int Akonadi::AgentBase::init(int, char**) () #25 0x7faf4ca99580 in __libc_start_main () at /lib64/libc.so.6 #26 0x55b8c314f3b9 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357388] Konsole on 2nd monitor shows only empty window-frame
https://bugs.kde.org/show_bug.cgi?id=357388 Diego changed: What|Removed |Added CC||diego...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 --- Comment #32 from Diego --- 100% reproducible using kscreen-5.5.3-1.fc23.x86_64 on KF5 5.18. Is there any debug info we can provide to have this problem more precisely identified? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 189302] Unmounting busy device in dolphin: missing information who is blocking
https://bugs.kde.org/show_bug.cgi?id=189302 Diego changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #7 from Diego --- It looks like this might be fixes in Plasma 5.6: http://blog.broulik.de/2016/01/on-being-more-convenient/ http://blog.broulik.de/wp-content/uploads/2016/01/devicenotifierinlinefeedbackerror2.png -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 189302] Unmounting busy device in dolphin: missing information who is blocking
https://bugs.kde.org/show_bug.cgi?id=189302 --- Comment #8 from Diego --- Kai Uwe, do the changes you mention in your blog extend also to Dolphin? Or are the just tied to Device Notifier? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 177778] make it possible to resize resizable annotations
https://bugs.kde.org/show_bug.cgi?id=18 Diego changed: What|Removed |Added CC||diego...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #100 from Diego --- (In reply to Rex Dieter from comment #99) > Taking the liberty of re-opening this bug, at least until some Qt upstream > bug gets (re)opened I've commented on: https://bugreports.qt.io/browse/QTBUG-43827 Hope it's the correct report. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 --- Comment #101 from Diego --- (In reply to Diego from comment #100) > (In reply to Rex Dieter from comment #99) > > Taking the liberty of re-opening this bug, at least until some Qt upstream > > bug gets (re)opened > > I've commented on: > https://bugreports.qt.io/browse/QTBUG-43827 > Hope it's the correct report. Looks like it wasn't the correct one. Giuseppe D'Angelo from Qt wrote: "I don't think it's about this bug. This is about a specific regression introduced in a commit, which led to reverting the code to the previous version. Hence either you're talking about the bug that was meant to be fixed (QTBUG-1548), or about some other bug, which is quite likely since QTBUG-1548 is not about fixing some crash. " So is this KDE crash a consequence of modified sorting caused by the (open) QTBUG-1548? https://bugreports.qt.io/browse/QTBUG-1548 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 Diego changed: What|Removed |Added CC||diego...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #38 from Diego --- Is checking "Suspend compositor for full screen windows" supposed to disable compositing for kscreenlock? I expect the answer to be "yes". Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 357007] kscreenlocker_greet unresponsive when using compositor
https://bugs.kde.org/show_bug.cgi?id=357007 --- Comment #41 from Diego --- (In reply to Thomas Lübking from comment #40) > Moreover fullscreen unredirection is no way the same as suspending the > compositor (the former still bears an active GL context), so the interesting > question is whether that setting makes any difference for you? I would have gladly tested that, but I'm on Intel hw, so if Martin's comment applies nothing should change. I'll test that anyhow. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 348390] (KF 5.10) sometimes Klipper does not activate selected entry
https://bugs.kde.org/show_bug.cgi?id=348390 Diego changed: What|Removed |Added CC||diego...@zoho.com -- You are receiving this mail because: You are watching all bug changes.
