[kate] [Bug 470738] New: Provide a notarized version for macOS
https://bugs.kde.org/show_bug.cgi?id=470738 Bug ID: 470738 Summary: Provide a notarized version for macOS Classification: Applications Product: kate Version: unspecified Platform: macOS (DMG) OS: Other Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: soltesz.and...@gmail.com Target Milestone: --- SUMMARY I cannot use Kate on macOS 13.3 because the installed application is not in notarized form and my company laptop is locked to use only applications that are notarized. I cannot use the "Open Anyway" button in System Settings because the laptop is locked to "App store and identified developers" setting. STEPS TO REPRODUCE 1. Select the "App store and identified developers" deployment setting in System Settings 2. Install Kate 3. Try to start it up OBSERVED RESULT Application doesn't start. Error message: “kate” can’t be opened because Apple cannot check it for malicious software. EXPECTED RESULT Application starts up SOFTWARE/OS VERSIONS macOS: 13.3.1 ADDITIONAL INFORMATION I am a Linux user normally but I regularly get Macbooks from work. On macOS, I would like to use the same Linux software I am used to and Kate is one of the core applications I use all the time. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 470000] Kate properly restore the session (including untitled)
https://bugs.kde.org/show_bug.cgi?id=47 --- Comment #1 from Andras Soltesz --- Workaround: Currently, I create a set of saved editors for these kinds of generic notepads in Kate. This allows them to be properly restored when Kate gets restarted. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 470000] New: Kate properly restore the session (including untitled)
https://bugs.kde.org/show_bug.cgi?id=47 Bug ID: 47 Summary: Kate properly restore the session (including untitled) Classification: Applications Product: kate Version: 23.04.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sessions Assignee: kwrite-bugs-n...@kde.org Reporter: soltesz.and...@gmail.com Target Milestone: --- SUMMARY I am using Sessions in Kate 23.04 and use the automatic restoration of the last used session. I have the "Automatically save and restore" setting for both "Newly-created unsaved files" and "Files with unsaved changes" switched on. This allows restoring pre-existing (named) files that were opened from the file system, modified but the changes not yet saved when Kate gets closed. When I restart Kate, these files get auto-restored with all of the unsaved changes and are displayed in tabs (great improvement BTW, huge thanks Kate devs). However, untitled (newly-created) files are not restored to their tabs. I can till recover them by using the Quick Open function but I would like to see them properly restored on their original tabs when I (re)start Kate. Reason: I use these untitled editors as notepads for different temporary content types and I would like to see them without any searching/recovering when Kate gets restarted. I am using Notepad++ on my Windows work laptop and this is the default behavior there (I would like to have the same behavior on my Linux boxes too). STEPS TO REPRODUCE 0. Ensure the configuration described in the summary 1. Create and save a Session in Kate 2. Create a new editor (Unnamed 1) and put some content in it 3. Close and reopen Kate OBSERVED RESULT The "Untitled" editor is not restored on its tab. Instead, I get an "Untitled (2)" tab with no content in it. Note: The editor content can still be recovered via the Quick Open function but this is not what most people would expect. (e.g.: coming from Sublime or Notepad++) EXPECTED RESULT The "Untitled" editor is restored to its own tab when Kate starts just like all of the other files/editors which are part of the Session. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: .5.105.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION My report is very similar to #462112 but it doesn't work as intended when closing Kate with the window control "x" either (while #462112 states that it works for him/her in that case). #463008 and #468573 look very similar too, they may have the same root cause as this. Nevertheless these are probably duplicates. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 424995] New: Secondary display resolution lost when attached when the display is powered-down
https://bugs.kde.org/show_bug.cgi?id=424995 Bug ID: 424995 Summary: Secondary display resolution lost when attached when the display is powered-down Product: kwin Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: soltesz.and...@gmail.com Target Milestone: --- SUMMARY KDE switches to the lowest possible resolution when a secondary display is attached but not yet turned on. It never restores the correct resolution when the displayed is powered up, detached and reattached. I use a USB-C port replicator with my XPS 9360 laptop and a fullHD display attached via an HDMI cable to the replicator. STEPS TO REPRODUCE 1. Attach the USB-c port replicator to the machine with the HDMI cable already attached but the display itself powered down 2. A new display appears in the Settings > Displays with 480p resolution (DP-1) but of course cannot be used. 3. Power-up the external display 4. KDE will switch the display to 480p resolution and the displays becomes usable 5. Detach the port replicator and re-attach it. A proper display name will now appear in Displays. OBSERVED RESULT KDE still keeps the 480p resolution instead of switching to the correct, last known resolution of the display EXPECTED RESULT KDE restores the correct, last-known resolution of the display. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION It is like KDE somehow identifies a virtual display on the port replicator and handles that instead of the actual display at the other end of the port replicator. When the HDMI cable is directly attached, the behaviour is different. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400701] plasma crash on QXcbConnection::getSelectionOwner
https://bugs.kde.org/show_bug.cgi?id=400701 --- Comment #9 from Andras --- Created attachment 129368 --> https://bugs.kde.org/attachment.cgi?id=129368=edit New crash information added by DrKonqi plasmashell (5.19.0) using Qt 5.15.0 - What I was doing when the application crashed: Simple logout then login with the same user -- Backtrace (Reduced): #4 0x7f5531a91320 in QXcbConnection::getSelectionOwner (this=0x5596ab412560, atom=) at qxcbconnection_basic.h:71 #5 0x7f5531a8bd28 in QXcbClipboard::getSelectionOwner (atom=, this=0x7f552c005f00) at ./qxcbobject.h:53 #6 QXcbClipboard::mimeData (this=0x7f552c005f00, mode=QClipboard::Clipboard) at qxcbclipboard.cpp:322 #7 0x7f5530fc05dd in KFilePreviewGenerator::Private::applyCutItemEffect (this=this@entry=0x5596abe8eae0, items=...) at /usr/src/debug/kio-5.70.0-3.2.x86_64/src/filewidgets/kfilepreviewgenerator.cpp:905 #8 0x7f5530fc2029 in KFilePreviewGenerator::Private::updateCutItems (this=0x5596abe8eae0) at /usr/src/debug/kio-5.70.0-3.2.x86_64/src/filewidgets/kfilepreviewgenerator.cpp:719 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400701] plasma crash on QXcbConnection::getSelectionOwner
https://bugs.kde.org/show_bug.cgi?id=400701 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403842] Libinput mouse KCM lost the scroll speed setting that was present in the evdev version
https://bugs.kde.org/show_bug.cgi?id=403842 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 415634] kontact crash on opening settings
https://bugs.kde.org/show_bug.cgi?id=415634 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410858] Full screen window goes under Latte Dock despite it's set to always visible
https://bugs.kde.org/show_bug.cgi?id=410858 Andras changed: What|Removed |Added CC|andrasszerencs...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".
https://bugs.kde.org/show_bug.cgi?id=348043 Andras changed: What|Removed |Added CC|andrasszerencs...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 377058] KDE Connect : SD card empty
https://bugs.kde.org/show_bug.cgi?id=377058 Andras changed: What|Removed |Added CC|andrasszerencs...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 Andras changed: What|Removed |Added CC|andrasszerencs...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #59 from Andras --- (In reply to Kishore Gopalakrishnan from comment #58) Oh my I just didn't noticed this cuz so obvious I'd love to use Google's supervision for login lol. Anyways thanks it works for me. Probably I've to use this option for now hm. Also correction, I meant it's not possible to turn on less secure app when there is 2 step verification is used and in this case Google gives the option for app password what should work for less secure apps too, well it doesn't work either. I used my accounts in Kontact with app pw for years and now I had to reconfigure Akonandi for whatever misbehaving after some upgrade and this message just started appearing for all of my setup. Anyways, I hope it'll be solved somehow soon. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 --- Comment #57 from Andras --- What plain authentication you guys are talking about? It's only for outgoing setup, incoming has to be configured in a way it's asked by Google anyway and basically that's where this problem is happening at least for me. I have a bunch, around 10 account setup in the right way in Kontact, I have 2 step auth.. so there is no option to set less secure app in Google account but in that case it won't be necessary in theory. It doesn't work for me either, same message appears for all of my account so I just wait. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 404990] Sign in with Google temporarily disabled for this app
https://bugs.kde.org/show_bug.cgi?id=404990 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410858] Full screen window goes under Latte Dock despite it's set to always visible
https://bugs.kde.org/show_bug.cgi?id=410858 --- Comment #5 from Andras --- (In reply to Michail Vourlakos from comment #4) No it's not relevant, title bar wasn't active on the panel on the screenshot cuz it wasn't a maximized window, I just tried to visualize how is it looked like with the issue since I'm not able to reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410858] Full screen window goes under Latte Dock despite it's set to always visible
https://bugs.kde.org/show_bug.cgi?id=410858 --- Comment #2 from Andras --- (In reply to Michail Vourlakos from comment #1) Ok, it seems solved somehow. I mean I tried several thing like emptying different caches like plasma, latte and reconfigure a bunch of thing like xorg.conf, nvidia settings etc but I'm not sure what caused this issue so kinda it can be closed now since it works for almost a day now after several startup. For clarifying though: I meant maximized window. https://drive.google.com/open?id=1ifJTHWnrfOL_JsRgdla26jIHxOsmFsJt -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410858] Full screen window goes under Latte Dock despite it's set to always visible
https://bugs.kde.org/show_bug.cgi?id=410858 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 410858] New: Full screen window goes under Latte Dock despite it's set to always visible
https://bugs.kde.org/show_bug.cgi?id=410858
Bug ID: 410858
Summary: Full screen window goes under Latte Dock despite it's
set to always visible
Product: lattedock
Version: 0.9.1
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: mvourla...@gmail.com
Reporter: andrasszerencs...@gmail.com
Target Milestone: ---
Hi,
this bug is quite related I think:
https://bugs.kde.org/show_bug.cgi?id=348043
Latte Dock: 0.9.1
KDE neon 5.16
KDE Plasma version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3
Kernel Version: 4.15.5-55-generic
monitors' position if it's related info maybe:
Option "metamodes" "DVI-D-0: 1440x900_75 +0+1260 {ForceCompositionPipeline=On,
ForceFullCompositionPipeline=On}, HDMI-0: nvidia-auto-select +1440+0
{ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0:
nvidia-auto-select +1440+1080 {ForceCompositionPipeline=On,
ForceFullCompositionPipeline=On}"
In the case above the problem occurs when additional monitor is set above the
primary one with Latte Dock placed on the top. It works when I switch between
always visible and other visibility settings but it's happening whenever Latte
is restarted.
Let me know if I should attach more details, thanks.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".
https://bugs.kde.org/show_bug.cgi?id=348043 Andras changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #49 from Andras --- Sorry, I'm just realized later this bug is about plasmashell and not latte dock uhh, excuse me, please close it again -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348043] Maximized windows are covered by plasma panel in "always visible mode".
https://bugs.kde.org/show_bug.cgi?id=348043
Andras changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED |---
CC||andrasszerencs...@gmail.com
--- Comment #48 from Andras ---
(In reply to Martin Flöser from comment #45)
Hm, unfortunately yes it's happening on a newer plasma so I reopen this bug,
sorry if I'm wrong about it.
Latte Dock: 0.9.1
KDE neon 5.16
KDE Plasma version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3
Kernel Version: 4.15.5-55-generic
monitors' position if it's related info maybe:
Option "metamodes" "DVI-D-0: 1440x900_75 +0+1260 {ForceCompositionPipeline=On,
ForceFullCompositionPipeline=On}, HDMI-0: nvidia-auto-select +1440+0
{ForceCompositionPipeline=On, ForceFullCompositionPipeline=On}, DP-0:
nvidia-auto-select +1440+1080 {ForceCompositionPipeline=On,
ForceFullCompositionPipeline=On}"
In this case the Problem occurs when additional monitor is set above the
primary one with latte dock placed on the top. It works when I switch between
always visible and other visibility settings.
Let me know if I should attach some specific details about this system, thanks.
--
You are receiving this mail because:
You are watching all bug changes.
[valgrind] [Bug 409999] vex amd64->IR: unhandled instruction bytes: 0x62 0xD1 0xFE 0x8 0x6F 0x84 0x24 0x8 0x0 0x0
https://bugs.kde.org/show_bug.cgi?id=40 --- Comment #3 from Andras Szabo --- Here is the cpuinfo of the build host: Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):80 On-line CPU(s) list: 0-79 Thread(s) per core:2 Core(s) per socket:20 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family:6 Model: 85 Model name:Intel(R) Xeon(R) Gold 6148 CPU @ 2.40GHz Stepping: 4 CPU MHz: 3099.937 BogoMIPS: 4804.84 Virtualization:VT-x L1d cache: 32K L1i cache: 32K L2 cache: 1024K L3 cache: 28160K NUMA node0 CPU(s): 0-19,40-59 NUMA node1 CPU(s): 20-39,60-79 As I look into the CMakeLists.txt file of rocksdb, i am seeing: -msse4.2 -mpclmul that stands out of the crowd. We used g++ 7.3 to build rocksdb. I am gonna collect build logs to provide more specific info. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 409999] New: Valgrind causes SIGILL due to unrecognized instruction in rocksdb static initialization
https://bugs.kde.org/show_bug.cgi?id=40 Bug ID: 40 Summary: Valgrind causes SIGILL due to unrecognized instruction in rocksdb static initialization Product: valgrind Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: andrei...@gmail.com Target Milestone: --- SUMMARY Most likely g++ generated an instruction, which is not recognized by valgrind. Remark: SSE 4.2 is enabbled during rocksdb's build process. STEPS TO REPRODUCE 1. Build rocksdb 6.1.2 (https://github.com/facebook/rocksdb) 2. Link a program with librocksdb 3. Start valgrind with the program. OBSERVED RESULT Some nasty happens along the lines of: ==93== Memcheck, a memory error detector ==93== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==93== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==93== Command: build/correlation/common/persistence/test/test_persistence ==93== vex amd64->IR: unhandled instruction bytes: 0x62 0xD1 0xFE 0x8 0x6F 0x84 0x24 0x8 0x0 0x0 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==93== valgrind: Unrecognised instruction at address 0x51e81ce. ==93==at 0x51E81CE: std::_Hashtable, std::allocator >, std::_ _detail::_Select1st, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std: :__detail::_Hashtable_traits >::_Hashtable const*>(std::pair const*, std::pair const*, unsigned long, std::hash const&, std::__detail::_Mod_range_hashing const&, std::__detail::_Default_ranged_hash const&, std::equal_to const&, std::__detail::_Select1st const&, std::allocator > const&) (in /usr/lib64/librocksdb.so) ==93==by 0x519CEBF: __static_initialization_and_destruction_0(int, int) [clone .constprop.642] (in /usr/lib64/librocksdb.so) ==93==by 0x400F552: _dl_init (in /usr/lib64/ld-2.17.so) ==93==by 0x40011A9: ??? (in /usr/lib64/ld-2.17.so) ==93== Your program just tried to execute an instruction that Valgrind ==93== did not recognise. There are two possible reasons for this. ==93== 1. Your program has a bug and erroneously jumped to a non-code ==93==location. If you are running Memcheck and you just saw a ==93==warning about a bad jump, it's probably your program's fault. ==93== 2. The instruction is legitimate but Valgrind doesn't handle it, ==93==i.e. it's Valgrind's fault. If you think this is the case or ==93==you are not sure, please let us know and we'll try to fix it. ==93== Either way, Valgrind will now raise a SIGILL signal which will ==93== probably kill your program. ==93== ==93== Process terminating with default action of signal 4 (SIGILL): dumping core ==93== Illegal opcode at address 0x51E81CE ==93==at 0x51E81CE: std::_Hashtable, std::allocator >, std::_ _detail::_Select1st, std::equal_to, std::hash, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std: :__detail::_Hashtable_traits >::_Hashtable const*>(std::pair const*, std::pair const*, unsigned long, std::hash const&, std::__detail::_Mod_range_hashing const&, std::__detail::_Default_ranged_hash const&, std::equal_to const&, std::__detail::_Select1st const&, std::allocator > const&) (in /usr/lib64/librocksdb.so) ==93==by 0x519CEBF: __static_initialization_and_destruction_0(int, int) [clone .constprop.642] (in /usr/lib64/librocksdb.so) ==93==by 0x400F552: _dl_init (in /usr/lib64/ld-2.17.so) ==93==by 0x40011A9: ??? (in /usr/lib64/ld-2.17.so) EXPECTED RESULT Run normally reporting eventual memory leaks and undefined behaviour. SOFTWARE/OS VERSIONS Linux: RHEL 7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408015] Global menu doesn't work
https://bugs.kde.org/show_bug.cgi?id=408015 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405281] Falkon cannot move tabs between its separated windows
https://bugs.kde.org/show_bug.cgi?id=405281 --- Comment #11 from Andras --- (In reply to The_assassin from comment #10) ???... Life is easier without unfinished stuff mostly. What are you talking about, this plase is worthless or it's something else lets say kwin issue? Anyways, no need to answer, I'm sure it's one of the most proper place to report this. I'm here if users feedback worth something, otherwise there is always an other stuff to use as a tool. Probably I'd forgot fill out essential parts of my comments with though, espesially here. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393480] SSL Error: Server's certificate does not match the URL
https://bugs.kde.org/show_bug.cgi?id=393480 --- Comment #6 from Andras --- (In reply to jltrinchard from comment #5) Thanks a lot for the detailed description what perceived by you about this issue, I'm sure probably it should be enough for general user to find out some workaround to stop this behaving however lately I have anything but time and energy. In short there is nothing specific I use, I utterly have no clue about pfBlockerNG or DNSBL etc. I think Falkon should work on a basic KDE neon setup without these anoying popups. Also I think it will appear with QtWebEngine 5.12.1 as well. I'm just saying it's ok to have this issue, only it is still an abnormal behaving by Falkon, at least on my system and it's appeared not yesterday but long long ago on my previous installations too. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405281] Falkon cannot move tabs between its separated windows
https://bugs.kde.org/show_bug.cgi?id=405281 Andras changed: What|Removed |Added Version|unspecified |3.1.0 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405281] Falkon cannot move tabs between its separated windows
https://bugs.kde.org/show_bug.cgi?id=405281 --- Comment #9 from Andras --- Unfortunately it's still issue. (It's Falkon 3.1) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404972] Krita Freezes by switching or modifying brush engine what's related to drawing pad driver probably
https://bugs.kde.org/show_bug.cgi?id=404972 Andras changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Andras --- Ok, it seems promising now. Sorry for my previous feedback, I'm undeniably hothead lol. Sometimes it's still freezing a little with 4.1.8, mostly it's not so it seems there is already an improvement too. I got no wacom related freezing with downloaded krita-4.2.0-pre-alpha-4e2b1b5-x86_64.appimage at all. I have to note I'm not sure these freezing issues on my system related to Krita however it really could be something with Nvidia too. I mentioning this because recently I changed a significant settings, I just turned off composition pipeline and got Nvidia to work with triplebuffer instead. Probably it's not related, I thought just in case worth noting such a change. So basically it works great for me now. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404972] Krita Freezes by switching or modifying brush engine what's related to drawing pad driver probably
https://bugs.kde.org/show_bug.cgi?id=404972 --- Comment #6 from Andras --- Oh, yep, that's great. What have to test...? Really? I think any one or 'even' you guys should be able to test it too with a miserable wacom pad and a simple neon install, lol. Ridiculous, sorry maybe I got tired today and I just lost my temper but let me put it simple. Don't close bug reports after 1.5 month if the waiting time for any reaction is the very same time if not a lot more. Don't get me wrong, I understand the policy and rules however developments should consider the fact that reporter may got tired to check given report after more then a month waiting. Also I have no time neither. I try to report back soon as I got a little time. Otherwise if it'll be closed then let me know if I should open an other one or whatever. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406062] Krita crashes in several situations, possibly file size or GPU related
https://bugs.kde.org/show_bug.cgi?id=406062 --- Comment #5 from Andras --- (In reply to comment #4) Sorry for the late answer, mostly I try to make things simple so I installed the basic driver implemented into given KDE neon 5.15 and its version is 390.116-0ubuntu0.18.04.1 so basically it's the closed one if i'm right about this. As far as I know open source Nvidia driver doesn't exist, Nouveau is the open source project for Nvidia cards. Inform me if I'm wrong about this. So in short it's the not open source Nvidia driver. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406062] Krita crashes in several situations, possibly file size or GPU related
https://bugs.kde.org/show_bug.cgi?id=406062 --- Comment #3 from Andras --- Oh, sorry I just realized later you meant not reporting more then one issue for my examples the cloning and drawing pad issue, I apologize for that too. I meant that as explaining myself why I have no patience to explain stuff more and why I reported this one after there is similar bug report already. I won't do that again. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406062] Krita crashes in several situations, possibly file size or GPU related
https://bugs.kde.org/show_bug.cgi?id=406062 --- Comment #2 from Andras --- I assume you meant don't report the same bug separately, add it to the existing one instead. Ok and I'm sorry about that however it wasn't an option on the bug report gui what appeared after the crash. Why nothing else freezes if it's really Nvidia problem then? I mean when everything works great and only one thing is problematic than I'd suspect there is something else in the background what cause this. Isn't it possible something in Krita what generates this GPU issue initially and we should look more deeper into this issue then this single backtrace? I understand if there is no time for this or no reason to proceed from developer point of view and also I know, well, nothing serious around this Qt vs GPU 'stuff' or what anyways, at least I don't see clearly what's going on. Obviously I hope it'll be solved somehow however I'm just planing to get an AMD setup so probably this will not be an issue there. Thanks for the prompt response, and yes, I'll add my report to the same bug on bugs.kde.org website in similar cases. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406062] Krita crashes in several situations, possibly file size or GPU related
https://bugs.kde.org/show_bug.cgi?id=406062 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 406062] New: Krita crashes in several situations, possibly file size or GPU related
https://bugs.kde.org/show_bug.cgi?id=406062 Bug ID: 406062 Summary: Krita crashes in several situations, possibly file size or GPU related Product: krita Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: andrasszerencs...@gmail.com Target Milestone: --- Application: krita (4.1.8) Qt Version: 5.12.0 Frameworks Version: 5.56.0 Operating System: Linux 4.15.0-46-generic x86_64 Distribution: KDE neon User Edition 5.15 -- Information about the crash: - What I was doing when the application crashed: In this case I cloed one of the document, that's why I conected to given crash report, 402892. However it's still crashing when several filter layer used and modified and also when G'MIC plugin used, etc. I noticed it's happening mostly when the document exceeds 1GB however yes, it could be GPU related too. I reported this not because I'm boring or something and feels good to report bugs but because I'm tired of this crashes, I'm already dealing with it for more then a year now. Sorry but I had difficult experiences about Krita bug reports especially related to this crashes. Also there are several other annoying issue like cloning is simple wrong, and cursor freezes with Wacom drawing pad, etc. Sorry for the not related mentioned things, I try to explain there are real issues with Krita and it'd be great to see fixes around this issues after a long time now. To be honest, I won’t expect it because seemingly it works great for painting and all these issue mainly retouch related only and probably not a great number of people use Krita for retouching. Thanks anyhow The crash can be reproduced sometimes. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 [Current thread is 1 (Thread 0x7f4ace2b7840 (LWP 13118))] Thread 12 (Thread 0x7f47ae986700 (LWP 13766)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7f4aca110ec5 in QtLinuxFutex::_q_futex (val3=0, addr2=0x0, val2=0, val=3, op=0, addr=) at thread/qfutex_p.h:92 #2 QtLinuxFutex::futexWait > (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at thread/qmutex_linux.cpp:142 #4 QBasicMutex::lockInternal (this=0x55ff905ae128) at thread/qmutex_linux.cpp:159 #5 0x7f4aca1110ab in QMutex::lock (this=this@entry=0x55ff905ae128) at thread/qmutex.cpp:227 #6 0x7f4a5afc in QMutexLocker::QMutexLocker (m=0x55ff905ae128, this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qmutex.h:206 #7 KisCanvasUpdatesCompressor::putUpdateInfo (this=0x55ff905ae128, info=...) at ./libs/ui/canvas/kis_canvas_updates_compressor.cpp:27 #8 0x7f4acccbeb8e in KisCanvas2::startUpdateCanvasProjection (this=0x55ff91174340, rc=...) at ./libs/ui/canvas/kis_canvas2.cpp:749 #9 0x7f4aca318e25 in QMetaObject::activate (sender=sender@entry=0x55ff916c1b20, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f47ae985a00) at kernel/qobject.cpp:3778 #10 0x7f4aca3194f7 in QMetaObject::activate (sender=sender@entry=0x55ff916c1b20, m=m@entry=0x7f4ac802f7e0 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f47ae985a00) at kernel/qobject.cpp:3631 #11 0x7f4ac7d6ba92 in KisImage::sigImageUpdated (this=this@entry=0x55ff916c1b20, _t1=...) at ./obj-x86_64-linux-gnu/libs/image/kritaimage_autogen/EWIEGA46WW/moc_kis_image.cpp:664 #12 0x7f4ac7c435de in KisImage::notifyProjectionUpdated (this=0x55ff916c1b20, rc=...) at ./libs/image/kis_image.cc:1542 #13 0x7f4aca318e25 in QMetaObject::activate (sender=0x55ff91655c10, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f47ae985b80) at kernel/qobject.cpp:3778 #14 0x7f4aca3194f7 in QMetaObject::activate (sender=, m=m@entry=0x7f4ac802f260 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7f47ae985b80) at kernel/qobject.cpp:3631 #15 0x7f4ac7d6ca12 in KisUpdaterContext::sigContinueUpdate (this=, _t1=...) at ./obj-x86_64-linux-gnu/libs/image/kritaimage_autogen/EWIEGA46WW/moc_kis_updater_context.cpp:163 #16 0x7f4aca318e25 in QMetaObject::activate (sender=0x55ff916c2cb0, signalOffset=, local_signal_index=, argv=) at kernel/qobject.cpp:3778 #17 0x7f4ac7d7274d in non-virtual thunk to KisUpdateJobItem::run() () from /usr/lib/x86_64-linux-gnu/libkritaimage.so.17 #18 0x7f4aca115352 in QThreadPoolThread::run (this=0x7f49848a4dc0) at thread/qthreadpool.cpp:99 #19 0x7f4aca110bc2 in QThreadPrivate::start (arg=0x7f49848a4dc0) at thread/qthread_unix.cpp:361 #20 0x7f4ac3b9a6db in start_thread
[Falkon] [Bug 405281] Falkon cannot move tabs between its separated windows
https://bugs.kde.org/show_bug.cgi?id=405281 --- Comment #8 from Andras --- Otherwise no way you try this out on and actual KDE neon? Interesting to see KDE bugs won't be tested on KDE neon most of the time. Obviosuly I understand as it's not that resilient OS and just not worth the headache. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405281] Falkon cannot move tabs between its separated windows
https://bugs.kde.org/show_bug.cgi?id=405281 --- Comment #7 from Andras --- Now I feel rebuked lol. I'm not lying and I'm not that stupid I won't know where am I login to neither. As far as I know, fundamentally and systemwide I use Xorg believe it or not. Good to hear some info were relevant from my attachment however I don't think the system uses Wayland in a significant way. I mean I also checked just now and yes there are Wayland related signs and I don't know how KDE neon works with Xorg exactly but I'm sure I can't even login to my system with Plasma Wayland if that's what you contend here. I login with basic Plasma what uses Xorg for sure. Why is it so sure Falkon is sick about any part of Wayland by the way? Please believe me this is my current output for this: loginctl show-session 3 -p Type Type=x11 Also no, it's not accepting after I drop it to desktop or whatever you mentioning. Please try to understand what I wrote and check the 2nd video, again, the end of the 2nd video more carefuly if you didn't see what I'm talking about. The only and the only case when falkon is accepting detached tab on this system when I touch the edge of Falkon's tab line with the cursor while I hold given tab to place. I don't know what other wording should I use, please check the 2nd video ending. Widgets lock didn't solve it. I won't expecting here anything, it's a simple bug report because for me, it seems a Falkon bug very much. Maybe it'll solved by you or by time cause this issue can be relevant to complex qt or any other stuff what Falkon uses. Firefox, Crhomium, Vivaldi works related to this altough they're a very different kind of browsers as it's obvious. Let me know if I should provide any other info or try out something else, thanks. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405281] Falkon cannot move tabs between its separated windows
https://bugs.kde.org/show_bug.cgi?id=405281 --- Comment #4 from Andras --- Created attachment 118724 --> https://bugs.kde.org/attachment.cgi?id=118724=edit attempt LD_DEBUG for falkon with tab transferring issue (In reply to comment #3) SDDM with X11. It's KDE neon so I just did run away from gdm3 quikcly, I don't really want to deal with usable gnome environment setup becasue KDE neon sources are very edgy. Sorry I didn't recorded the very same issue there however I assure you it is also happening on gdm3 in the very same way. Sorry for the long video but I tried to point out that the browser is acepting tabs only after you touched the right or left edge of the tab line while you hold given tab with your mouse. Also I tried to create a backtrace, I don't know if any of this info would be helpful enough so I understand if more info should be provided. Le me know whenever you guys have time for this to proceed, I mean no rush. I also thought it can be caused by something else for example some windows management misbehaving however I already tried to turn off compositor and the issue presists without desktop effects too. https://drive.google.com/open?id=19tiLld_ubeq8ReaAI5XcvQXv39bSZH64 -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405281] Falkon cannot move tabs between its separated windows
https://bugs.kde.org/show_bug.cgi?id=405281 --- Comment #2 from Andras --- That's all, no further question, anything? Then I get used to this bug too and close this report frightfully quickly? Sorry, I mean it's quite interesting it works for you with the same circumstances since this is happening on both of my installation, I mean separated desktop PCs with KDE neon. https://drive.google.com/open?id=1wYUkDpSrkloPKLvtwyBZAgnlaumIMnKR -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405275] Falkon handles mouse's right click wrongly
https://bugs.kde.org/show_bug.cgi?id=405275 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405281] Falkon cannot move tabs between its separated windows
https://bugs.kde.org/show_bug.cgi?id=405281 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405281] New: Falkon cannot move tabs between its separated windows
https://bugs.kde.org/show_bug.cgi?id=405281 Bug ID: 405281 Summary: Falkon cannot move tabs between its separated windows Product: Falkon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: andrasszerencs...@gmail.com Target Milestone: --- Detaching tabs and opening separated windows of Falkon is possible. I think the function to attaching tabs to browser's separated windows is basic enough option to considering it as a bug when it's missing. STEPS TO REPRODUCE 1. Open two separated Falkon windows 2. Open several tabs in each window 3. Try to move one tab from one window to the other. OBSERVED RESULT There is a sign appearing as if given tab could be placed on given window however it's still detached when you release it. EXPECTED RESULT Transferred tab placed among tabs of given window. SOFTWARE/OS VERSIONS Application version 3.0.1 KDE neon 5.15 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.15.0.46-generic -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405275] Falkon handles mouse's right click wrongly
https://bugs.kde.org/show_bug.cgi?id=405275 --- Comment #1 from Andras --- Darn, sorry for the typos, I hope it's still understandable -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 405275] New: Falkon handles mouse's right click wrongly
https://bugs.kde.org/show_bug.cgi?id=405275 Bug ID: 405275 Summary: Falkon handles mouse's right click wrongly Product: Falkon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: andrasszerencs...@gmail.com Target Milestone: --- SUMMARY Right click won't work on most website and also it works where light click manu should be disabled. For example, for me it won't work on duck.com and won't be disabled on Gmail where Falkon seemingly won't respect or perceive the website's claims to disable right click. STEPS TO REPRODUCE 1. Try to click on given websites above. OBSERVED RESULT Right click menu appears on won't appear wrongly regarding to given situation above. EXPECTED RESULT Right click menu appears on won't appear in the right way regarding to given situation above. SOFTWARE/OS VERSIONS Application version 3.0.1 KDE neon 5.15 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.15.0.46-generic -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393480] SSL Error: Server's certificate does not match the URL
https://bugs.kde.org/show_bug.cgi?id=393480 --- Comment #3 from Andras --- Forgot my system's details, sorry: Application version 3.0.1 KDE neon 5.15 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.15.0.46-generic -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 393480] SSL Error: Server's certificate does not match the URL
https://bugs.kde.org/show_bug.cgi?id=393480 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com --- Comment #2 from Andras --- Good to know however I think it's absolutelly not normal to get these popups all the time. Do you guys even tried to Falkon to see how is it work in real? I mean there have to be an other solution to handle this SSL issue in Falkon, you get this alarm all the time I mean. Basically I considering this as a problem, utterly. Do you guys planning to solve it? Don't get me wrong, I like the QT browser idea very much and looking forward to use it however at the same time I hope it'll impove in the near future because currently it's almost a headache to use in its current state. There are too much annoying thing like this one. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 404766] Mouse 'back' button sometimes doesn't work
https://bugs.kde.org/show_bug.cgi?id=404766 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com --- Comment #1 from Andras --- Application version 3.0.1 KDE neon 5.15 KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.15.0.46-generic I'd say it won't work most of the time. It's really few website only where Falkon regognizes backward button. I think it's related to all other issue like right click won't work on most website and also Falkon won't respect website's claims to disable right click like Gmail, etc. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404972] Krita Freezes by switching or modifying brush engine what's related to drawing pad driver probably
https://bugs.kde.org/show_bug.cgi?id=404972 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 404972] New: Krita Freezes by switching or modifying brush engine what's related to drawing pad driver probably
https://bugs.kde.org/show_bug.cgi?id=404972 Bug ID: 404972 Summary: Krita Freezes by switching or modifying brush engine what's related to drawing pad driver probably Product: krita Version: 4.1.7 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: andrasszerencs...@gmail.com Target Milestone: --- SUMMARY I use Wacom Intuos 5 and Krita freezes when I usually switch between brush engines, fro example from cloning to blender, I mean there is no cursor movement, palette popup, etc. I found out some workaround, sometime it's solvable if I click with the mouse right button or switch between Trilinear Filtering and High Quality Filtering for example. However there are cases when I have to save the document and restart Krita, in this case there is no palette popup, only a right click menu when I click with the mouse right button. Although I wasn't able to find other similar report here, I hope there is already some info and experiences by others about this problem. STEPS TO REPRODUCE 1. Connect drawing pad, in my case Wacom Intuos 5 2. Fire up krita with some stuff and try to use cloning, blender, airbrush by switching between them using your drawing pad. 3. Try to solve the freezing with your mouse or switching between Scaling Mode. OBSERVED RESULT Krita freezes, no cursor movement, palette popup. EXPECTED RESULT No freeze, flawless work. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.15 (available in About System) KDE Plasma Version: 5.15.2 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.0 Kernel Version: 4.15.0-45-generic ADDITIONAL INFORMATION X.Org X server -- Wacom input driver version: 1:0.36.1-0ubuntu1 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #110 from Andras --- (In reply to Patrick Silva from comment #109) Did you tried $ rm ~/.config/discoverrc && rm -R ~/.cache/discover or something similar standard solution for this? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #105 from Andras --- Who SORRY wait, it happened right after the installation only. Now after a while it works like a charm. Interesting. I don't what's happening but sorry if previous info of mine is misleading. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #104 from Andras --- Created attachment 117899 --> https://bugs.kde.org/attachment.cgi?id=117899=edit Discover crashed after few minutes with deb packages from comment #99 #102 get some advil then and relax instead. Otherwise I also tried to restart my system and it won't work on my side either. Moreover it crashed after a minute or so and I placed the bug report here, ignore if it's useless. Thanks for all the hard work so far! Obviously I know nothing however it seems something just still not clear what could be the actual problem really. So let me know if there is any possible option to help by simple user with back trace or anything. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #92 from Andras --- It wasn't what simple comment #91. Anyhow it'd be awesome if sudo apt install -f would all the addictions :) I made several other steps to solve my system's issues also related to this https://bugs.kde.org/show_bug.cgi?id=402328 such as fwupdmgr refresh/fwupdmgr update. Now, apparently it works for me too. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #90 from Andras --- Probably I did something wrong or my system is awkward compromised somehow but for me it won't work, in short there are dependency issues. I hope it's only for me and it's really solved basically, I use mainly other other stuff to upgrade anyway. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981
--- Comment #76 from Andras ---
Also at kdesrc-build --initial-setup I got
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in
m/(\${ <-- HERE MODULE})|(\$MODULE\b)/ at /usr/bin/kdesrc-build line 4759.
Let me know how should I proceed.
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #75 from Andras --- (In reply to Nate Graham from comment #74) (Ignore, not question but I hove to note what is it that some still assumes this place is a miserable playground? So ridiculous LMAO.) It's nothing serious, I write this because it's just so absurd that I'd gladly try to build it as you kindly described although believe it or not, for 5 hours already http://archive.neon.kde.org/user currently isn't available. Obviously the server is down, unbelievable. Anyhow I'll try later. Also thank you for the guidance. "E: The repository 'http://archive.neon.kde.org/user bionic Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details." Let me know if it's possibly not the server but something locally on my (two) system though. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #64 from Andras --- (In reply to Nate Graham from comment #58) Maybe it's late but I also don't have cgcicon.knsrc file in given directory however I tried cgcgtk3.knsrc and cgctheme.knsrc also, issue still persist. Let me now if there are any other suspicious files as possible culprit and erasing them can resolve this or something, thanks. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #52 from Andras --- (Not in reply but a note related to lega99 from comment #50 that I'm sorry) I tried. Actually I was about to explaining things in the hope that redundant rows will decrease however what happened is that what usually happens in similar situations, it fell on deaf ears so I write this because I'm sorry I also increased the number of utterly unnecessary lines. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402328] Discover crashes on launch in AbstractResource::reportNewState()
https://bugs.kde.org/show_bug.cgi?id=402328 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com --- Comment #28 from Andras --- Created attachment 117491 --> https://bugs.kde.org/attachment.cgi?id=117491=edit plasma-discover 5.14.5 crashes on launch (after reinstalling it) My system plasma-discover 5.14.5 Qt Version: 5.11.2 KDE Frameworks Version: 5.54.0 Kernel Version: 4.15.0-43-generic Distribution: KDE neon User Edition 5.14 Previously it worked however I reinstalled Discover trying to resolve this bug: https://bugs.kde.org/show_bug.cgi?id=399981. It's probably fwupd related indeed because Discover starts after: fwupdmgr refresh fwupdmgr update -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401911] Krita crashes after grouping masks converted from layers
https://bugs.kde.org/show_bug.cgi?id=401911 --- Comment #5 from Andras --- (In reply to mvowada from comment #4) There are several changes since then: Krita 4.1.7.101 Qt Version: 5.11.2 KDE Frameworks Version: 5.54.0 Kernel Version: 4.15.0-43-generic Distribution: KDE neon User Edition 5.14 Thank you so much for your time and effort. I should have describe it more simple: 1) group 1 or two layer 2) create two new layer inside the group above and and convert this two new layer to any type of filter mask 3) try to group the filter masks above Anyways, now with this Krita version on the also upgraded system yes, making group is still appears as option also for Filter Masks converted from layer inside a group but it won't work so there is no crash anymore. It seems grouping standalone Filter Masks had been disabled what's solved this bug. Thank you so much again and although it's late, I wish a happy new year for you and for Krita team! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #48 from Andras --- Created attachment 117488 --> https://bugs.kde.org/attachment.cgi?id=117488=edit reinstalled plasma-discover with disabled update button issue crashes at start Oh for God's sake, you should expect promises from Microsoft maybe and call it disgusting after you paid thousands of dollars for their faulty software. Don't be rude, it's not that paid service even if you're donating. Yes, these systems also works only if users are satisfied however you shouldn't use here such a wording above because there is a lot developers who works for free after they working hours. Anyways it's a bug tracking system not a service for claims. Still won't work, report, done. Yes, plasma-discover still doesn't work under 5.54 KDE Frameworks. I tried to reinstall it and since then, it crashes every time I try to open it. I place the result for that crash here if it helps with this bug maybe. Let me know if I should open a new case for that, thanks. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 399981] Discover: Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #37 from Andras --- (In reply to lega99 from comment #36) > I do not have libkf5newstuff I have libkf5newstuff-dev and it's not > installed. It's already fixed, you don't have to assume anything and additional packages won't be necessary to install. Report back after KDE Frameworks 5.54 arrives on your system and your plasma-discovery still won't work regarding to this bug. Its release expected around January 12th, 2019 (now I'm assuming :) that 2018 is a typo on frameworks schedules page): https://community.kde.org/Schedules/Frameworks -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #29 from Andras --- Created attachment 117195 --> https://bugs.kde.org/attachment.cgi?id=117195=edit debug plasma-discover where Update button isn't available This one is also a long shot only and also possibly unnecessarily too long. LD_DEBUG=files plasma-discover 2>&1 | tee ~/debug_plasma-discover.txt -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #28 from Andras --- Created attachment 117194 --> https://bugs.kde.org/attachment.cgi?id=117194=edit gdb plasma-discover where Update button isn't available SOFTWARE/OS VERSIONS KDE neon 5.14 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 QT Version: 5.11.2 Kernel Version: 4.15.0-43-generic OS Type: 64-bit I try to make backtrace gdb plasma-discover 2>&1 | tee ~/gdb_plasma-discover.txt (gdb) r (gdb) quit As I heard there is no huge amount of help to develop discovery however if there is someone who could answer let me know if my backtrace is worthless and what else should affected users try to do for proper backtrace with actual helpful debug symbols. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #27 from Andras --- (In reply to Elmas from comment #20 and all others) Please STOP and STOP using bug report for social media like comments, I mean it!!! If there is any personal note how you tried to solve it then ok place it here in very short limited sentences however there is no place here for assumptions and other OS contents. If you don't have backtrace or other worthy information about background processes about the bug then don't make bug reports everlasting with such an attitude, THANK YOU! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402537] Update button isn't available from Plasma Discover
https://bugs.kde.org/show_bug.cgi?id=402537 --- Comment #1 from Andras --- Created attachment 117095 --> https://bugs.kde.org/attachment.cgi?id=117095=edit Start Plasma Discover from console where 'update all' button isn't available -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402537] Update button isn't available from Plasma Discover
https://bugs.kde.org/show_bug.cgi?id=402537 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402537] New: Update button isn't available from Plasma Discover
https://bugs.kde.org/show_bug.cgi?id=402537 Bug ID: 402537 Summary: Update button isn't available from Plasma Discover Product: Discover Version: 5.14.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: andrasszerencs...@gmail.com Target Milestone: --- Created attachment 117094 --> https://bugs.kde.org/attachment.cgi?id=117094=edit Update button isn't available from Plasma Discover SUMMARY STEPS TO REPRODUCE 1. Start Plasma Discover when update is available 2. Go to update tab 3. Update button won't change to available OBSERVED RESULT No available option for upgrade. EXPECTED RESULT Available update all button. SOFTWARE/OS VERSIONS KDE neon 5.14 KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 QT Version: 5.11.2 Kernel Version: 4.15.0-43-generic OS Type: 64-bit ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401911] Krita crashes after grouping masks converted from layers
https://bugs.kde.org/show_bug.cgi?id=401911 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401911] Krita crashes after grouping masks converted from layers
https://bugs.kde.org/show_bug.cgi?id=401911 --- Comment #1 from Andras --- Also I'd like to note my thoughts about this issue what should be ignored if it's simple nonsense, right now as I see masks can't be handled in the same way you handle layers, for example, I am able to create above groups in question what contains only masks by moving out every layers from given group however they're worthless in this way, seemingly masks aren't able the activate the changes when there is no layer directly next to them in the very same group. I don't know how is it work in deep etc however if this issue and crash can be avoided only by removing the option for detached masks than please don't hide that option because it's just really useful having masks separated from layers. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401911] New: Krita crashes after grouping masks converted from layers
https://bugs.kde.org/show_bug.cgi?id=401911 Bug ID: 401911 Summary: Krita crashes after grouping masks converted from layers Product: krita Version: 4.1.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: andrasszerencs...@gmail.com Target Milestone: --- Application: krita (4.1.5) Qt Version: 5.11.2 Frameworks Version: 5.52.0 Operating System: Linux 4.15.0-42-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed at the first time I noticed this: Grouped some (5) layers of the image with several modification, different opacity for example. Inside above group, insert new layer and convert it to transparency mask and hide som area with it. Also inside this group, insert two layers and convert them to filter masks, the first one with color adjustment the second one with levels. Try to group these last two masks converted from layers. However, I think you can repruduce this issue with these simple steps: Simple make a new empty file, duplicate, qkuick group, 2x insert (2 new layers I mean), convert the last 2 layers to any type of filter masks and try to group them. The crash can be reproduced every time. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe551845cc0 (LWP 14460))] Thread 6 (Thread 0x7fe4da64c700 (LWP 14495)): #0 0x7fe54dc030b4 in __GI___libc_read (fd=39, buf=0x7fe4da64bae0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fe545f59cd0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe545f15027 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe545f154e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fe545f1564c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fe54e75a04b in QEventDispatcherGlib::processEvents (this=0x7fe4cc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7fe54e6fe30a in QEventLoop::exec (this=this@entry=0x7fe4da64bcf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #7 0x7fe54e529bba in QThread::exec (this=) at thread/qthread.cpp:525 #8 0x7fe52ee16826 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fe54e534adb in QThreadPrivate::start (arg=0x55cce44ac390) at thread/qthread_unix.cpp:367 #10 0x7fe5478116db in start_thread (arg=0x7fe4da64c700) at pthread_create.c:463 #11 0x7fe54dc1488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fe4dbd55700 (LWP 14494)): #0 0x7fe54dc07bf9 in __GI___poll (fds=0x7fe4d4004e00, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe545f15539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe545f1564c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe54e75a04b in QEventDispatcherGlib::processEvents (this=0x7fe4d4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fe54e6fe30a in QEventLoop::exec (this=this@entry=0x7fe4dbd54d40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fe54e529bba in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7fe52e99b4f5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fe54e534adb in QThreadPrivate::start (arg=0x55cce4383780) at thread/qthread_unix.cpp:367 #8 0x7fe5478116db in start_thread (arg=0x7fe4dbd55700) at pthread_create.c:463 #9 0x7fe54dc1488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fe50a61c700 (LWP 14483)): #0 0x7fe54dbd79d0 in __GI___nanosleep (requested_time=requested_time@entry=0x7fe50a61bd80, remaining=remaining@entry=0x7fe50a61bd80) at ../sysdeps/unix/sysv/linux/nanosleep.c:28 #1 0x7fe54e7599ad in qt_nanosleep (amount=...) at kernel/qelapsedtimer_unix.cpp:195 #2 0x7fe54b79ed0a in KisTileDataSwapper::run (this=0x7fe54bc94ca0 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at ./libs/image/tiles3/swap/kis_tile_data_swapper.cpp:97 #3 0x7fe54e534adb in QThreadPrivate::start (arg=0x7fe54bc94ca0 <_ZZN12_GLOBAL__N_116Q_QGS_s_instance13innerFunctionEvE6holder+64>) at thread/qthread_unix.cpp:367 #4 0x7fe5478116db in start_thread (arg=0x7fe50a61c700) at pthread_create.c:463 #5 0x7fe54dc1488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fe51165e700 (LWP 14481)): #0 0x7fe54dc07bf9 in __GI___poll (fds=0x7fe50c004a10, nfds=1, timeout=9387) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe545f15539 in ?? () from
[krita] [Bug 398380] Krita won't handle big files with a lot of layers
https://bugs.kde.org/show_bug.cgi?id=398380 --- Comment #4 from Andras --- I totally agree, especially considering the fact that it's seemingly happened on my KDE neon installations only and somehow it seems to have been resolved now. Yes, consider this issue as fixed. Thank you guys for this precious software and for all the hard work! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398380] Krita won't handle big files with a lot of layers
https://bugs.kde.org/show_bug.cgi?id=398380 --- Comment #2 from Andras --- Thanks you for your response, I never used LUT and I just read about it on Krita page now. Is it maybe something between OICO configuration file and KDE neon? I have to note Krita is much much faster and it doesn't crashing lately. Also I don't know if it's related to OICO but some additional stuff appeared in tools/scripts menu with Color Space option among them. Should I start Krita with LC_ALL=C if it starts crashing again or it's nothing to do with this issue? -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 226965] online meanwhile user appears offline
https://bugs.kde.org/show_bug.cgi?id=226965 --- Comment #4 from Andras Georgy Bekes --- I am sorry but I abandoned using the meanwhile plugin at least 5 years ago (not because of this bug). -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 210416] opens all http://... links with kwrite
https://bugs.kde.org/show_bug.cgi?id=210416 --- Comment #8 from Andras Georgy Bekes --- As the ticket mentions, this happened when I upgraded from KDE 3 to 4. Even if the bug still exists, I doubt it is worth spending any time with it. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #66 from Andras --- First of all, I apologize for all my rude replies. Nevertheless I'd like to give a feedback, 1.3.3 version of KDE Connect just arrived on my two pc with KDE neon and it works awesome with my cellphones. Thank you so much guys, many thanks for all your hard work! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #65 from Andras --- (correction for comment #64) I wanted to write "you should undo it right after you got KDE Connect 1.3.3" what allegedly fix this issue. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #64 from Andras --- Ok, although it's closed I'd note, I think it's because the older 1.3 version of KDE Connect what KDE neon kept asks for dated ssh-dss type of cryptographic algorithm what is disabled by default on current OpenSSH. It's highly NOT recommended but you can enable it by placing a line into /etc/ssh/ssh_conf. However you should make a copy previously: sudo cp /etc/ssh/ssh_config /etc/ssh/ssh_config.factory-defaults Then add the following to ssh_config file: PubkeyAcceptedKeyTypes +ssh-dss Even if you can't wait and make this modification, you should undo it right after you got KDE Connect 1.4. Correct me If I I'm wrong. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #53 from Andras --- You guys are awesome how fast the upgrades appeared in packages, thanks. I assume it was related to this bug also. I try to solve this on two desktop pc with two phone(beta app on both). I hope it's only for me and the main issue is solved. I still can't get Kdeconnect to work. My process was: Upgrade was done well, I mean everything installed flawlessly, kdevplatform52-libs was removed. Restart --> still won't work Remove /var/tmp/kdecache-user /~.cache/kio /~.config/kdeconnect and remove data from kdeconnect app on phone Restart --> still won't work The issue is the same, I mean I get the very same messages except right after the upgrade I got some additional stuff implemented by you guys I think, such as: kdeconnect.plugin.sftp: add to dolphin I'd like to note also, I still get the same result I mentioned above: kdeconnect.plugin.sftp: stdout: "Unable to negotiate with 192.168.0.0 port 1739: no matching host key type found. Their offer: ssh-rsa\r\n" -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #52 from Andras --- (In reply to NiO from comment #50) Nice, I'm glad it seems to be solved, thanks for the hard work! I noticed something tough and I hope not but if this issue remains somehow then may I highlight these two line from result above?: --- kdeconnect.plugin.sftp: Starting process: "sshfs kdeconnect@192.168.1.90:/ /run/user/1000/6745be67c0caf8bb -p 1739 -s -f -F /dev/null -o IdentityFile=/home/adam/.config/kdeconnect/privateKey.pem -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o HostKeyAlgorithms=+ssh-dss -o uid=1000 -o gid=1000 -o reconnect -o ServerAliveInterval=30 -o password_stdin" -- kdeconnect.plugin.sftp: stdout: "Warning: Permanently added '[192.168.1.90]:1739' (RSA) to the list of known hosts.\r\n" --- Technically speaking I know nothing about networking in deep but isn't KDEConnect asks for ssh-dss type algorithm and by the end the system try to give ssh-rsa? I mean is it possible it's something with cryptographic algorithms compatibility that the system in KDE neon won't provide the legacy one? Related to this, once I got this line for example: --- kdeconnect.plugin.sftp: stdout: "Unable to negotiate with 192.168.0.0 port 1739: no matching host key type found. Their offer: ssh-rsa\r\n" --- It's a long shot and maybe I'm speaking about nonsense but just in case I ask. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #49 from Andras --- (In reply to VosaXalo from comment #48) Yes, I saw it too and installed it with hope. I bet it was fix for remove file browsing maybe for many distribution even for OS from Rendmond but not for KDE neon. I just started to thinking about buying a new Windows licence if it gets more support even from Linux open sources. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #44 from Andras --- I made a several attempts and increasing max_user_watches at boot seems to be the most significant one. Although I'm not sure if this single step would help for some so let me know how is it work: https://github.com/guard/guard/issues/229 http://blog.sorah.jp/2012/01/24/inotify-limitation https://askubuntu.com/questions/154255/how-can-i-tell-if-i-am-out-of-inotify-watches In short place this line into your /etc/sysctl.conf : fs.inotify.max_user_watches=10 Also even if it helps, I don't think this is the real solution, I see it as a workaround only. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #41 from Andras --- (In reply to Simon from comment #40) Then It's a great example then users shouldn't rely on and cling to specific open source projects by names and shouldn't be loyal and shouldn't expect loyalty. I see some development makes its testing on more popular Distributions however as a not developer I assumed KDE project testing on KDE neon first as a matter of respect and if KDE neon itself wants to reach any level of popularity. If KDE Connect project is based on popularity so much then it should and I think it'll change its name sooner or later. Simon don't get me wrong, keep up the good work. Maybe I'll change my aspects and get other options that's all. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #38 from Andras --- > Yes, I mean none of the KDE Connect developers I don't want to overreact anything and redundantly spiel however if not a single KDE developer got KDE neon related to Kdeconnect then wow, that's disgraceful indeed. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #31 from Andras --- Those who allegedly able to mount and access phone directories manually, please report your Kdeconnect version too. I was just hilariously frustrated why the hack it won't work for me till I just got kdeconnect 1.3.2 upgrade from 1.3.1. Now my results are: qdbus org.kde.kdeconnect /modules/kdeconnect/devices/0d78094f9d46e0b2/sftp isMounted false qdbus org.kde.kdeconnect /modules/kdeconnect/devices/0d78094f9d46e0b2/sftp mountAndWait true qdbus org.kde.kdeconnect /modules/kdeconnect/devices/0d78094f9d46e0b2/sftp isMounted true Now, I also able to reach phone directories through /run/user/1000/... with Kdeconnect 1.3.2. However I think, it's important to note at least from the aspect of Plasma Desktop, Dolphin still won't access and it's still saying "protocol died unexpectedly". -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #25 from Andras --- (In reply to Laosom from comment #24) > Sorry. Now I feel bad. Although this place not for personal dialogue, excuse me if I was pedantic. I'd stuck with shorter posts but more info better than nothing and thanks for your comment Laosom. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #23 from Andras --- (In reply to Laosom from comment #21) > journalctl -ex Forget it if I'm wrong however I don't think placing whole bunch of common device and journalctl information would help the thread, it creates a mess. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #19 from Andras --- For me it's even worse now as it was on my comment #5 above: https://bugs.kde.org/show_bug.cgi?id=400178#c5 Previously it's mounted, now it won't mount either: qdbus org.kde.kdeconnect /modules/kdeconnect/devices//sftp mountAndWait false I'm not sure if it's count, I found these line during the process through jurnalctl -ex for example: kdeconnect.plugin.sftp: Timeout: device not responding gdk_device_update_tool: assertion 'GDK_IS_DEVICE (device)' failed UdevQt: unhandled device action "unbind" -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #12 from Andras --- (In reply to Alexandr Zamaraev (aka Tonal) from comment #11) > Created attachment 115884 [details] > dolphin after some F5 If it's a suggestion to use F5 well, you can see it's not that simple problem that someone just forgot to refresh something. Thanks anyways. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 --- Comment #5 from Andras --- For me, results for given commands above on two different PC with the same installation and with beta participation on Google's Play Store: qdbus org.kde.kdeconnect /modules/kdeconnect/devices//sftp isMounted false qdbus org.kde.kdeconnect /modules/kdeconnect/devices//sftp mountAndWait Browsing the phone through Dolphin still won't work qdbus org.kde.kdeconnect /modules/kdeconnect/devices//sftp isMounted true -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 400178] New: KDEConnect fails to open remote phone directory as it says protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=400178 Bug ID: 400178 Summary: KDEConnect fails to open remote phone directory as it says protocol died unexpectedly Product: kdeconnect Version: 1.3.1 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: andrasszerencs...@gmail.com Target Milestone: --- SUMMARY KDEConnect fails to open remote phone directory as it says protocol died unexpectedly STEPS TO REPRODUCE 1. Turn on Kdeconnect on PC and on Android too 2. Pair the two devices 3. In Dolphin, click on the name of the phone created by Kdeconnect OBSERVED RESULT The process for the kdeconnect://... protocol died unexpectedly EXPECTED RESULT Open given remote phone directory SOFTWARE VERSIONS (available in About System) KDE neon 5.14 KDE Plasma Version: 5.14.1 KDE Frameworks Version: 5.51.0 Qt Version: 5.11.2 Kernel Version: 4.15.0-38-generic OS Type: 64-bit ADDITIONAL INFORMATION Hi, I have this issue for a while now on Ubuntu 18.04 based KDE neon 5.14.1, QT Version 5.11.2, Kernel 4.15.0-38, kdeconnect 1.3.1-0 I try to access Kdeconnect through Dolphin what says: The process for the kdeconnect://... protocol died unexpectedly Anybody experienced similar issue? What could be the problem? It seems everything else functional, I mean I get the notification and remote input, etc, the phone name appears in Dolphin, only directory access won't work. Firewall ports 1714-1764 udp tcp implemented. Tried several workaround, full reinstall, erase related folders, on android too. I have to note, very rarely it come alive, for example when I installed an other Android app for ftp and connected to it with Dolphin. I was able the access the phone by rightclicking on the phone name given by kdeconnect (not the one connected with other app obviously) / edit and click on open file dialog and examining finished pop up message appeard. It worked only once. It's issue on two different desktop pc with same KDE neon OS and with two different phone. Also I found this in journalctl for example: kdeconnect.plugin.notification: Not found noti by internal Id: "0|com.samsung.tmowfc.wfccontroller|2131165186|null|1000" -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399559] Crash upon QQuickItem::setParentItem in QQuickMenuPrivate
https://bugs.kde.org/show_bug.cgi?id=399559 --- Comment #8 from Andras --- Created attachment 115611 --> https://bugs.kde.org/attachment.cgi?id=115611=edit New crash information added by DrKonqi plasma-discover (5.14.0) using Qt 5.11.1 - What I was doing when the application crashed: Open Flatpak and simple click between menus. For example: Settings / Flathub - dl.flathub.org or distribute.dke.org / scroll over Flathub applications / Click on main applications / crash Not every time reproducible. -- Backtrace (Reduced): #6 0x7f2f32200e7c in QQuickMenuPrivate::setParentMenu(QQuickMenu*) () at /usr/lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #7 0x7f2f322025cb in QQuickMenuPrivate::removeItem(int, QQuickItem*) () at /usr/lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #8 0x7f2f45d0bd26 in QQuickItemPrivate::itemChange(QQuickItem::ItemChange, QQuickItem::ItemChangeData const&) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f2f45d12157 in QQuickItem::setParentItem(QQuickItem*) () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f2f45d13a6c in QQuickItem::~QQuickItem() () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399559] Crash upon QQuickItem::setParentItem in QQuickMenuPrivate
https://bugs.kde.org/show_bug.cgi?id=399559 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 336043] SFTP: Should be able to browse external SD cards via SFTP too
https://bugs.kde.org/show_bug.cgi?id=336043 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398380] Krita won't handle big files with a lot of layers
https://bugs.kde.org/show_bug.cgi?id=398380 Andras changed: What|Removed |Added CC||andrasszerencs...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398380] New: Krita won't handle big files with a lot of layers
https://bugs.kde.org/show_bug.cgi?id=398380 Bug ID: 398380 Summary: Krita won't handle big files with a lot of layers Product: krita Version: 4.1.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: andrasszerencs...@gmail.com Target Milestone: --- Application: krita (4.1.1) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.15.0-33-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: There were two files open in Krita, each of them more then 2GB with a lot of layer. Simple I was working on different layers on the first file and tried to save it and right after I pressed CTRL+s, I closed the second file then it's crashed. Anyway, I don't thing there was any specific issue here related what was I doing. It's clear Krita is unstable with more then one big file with a lot of layers. Basically I'd reopen this bug report: https://bugs.kde.org/show_bug.cgi?id=394974 Obviously I'll not open it since it's closed by me after my lot of uploading and involvement wasn't appreciated and I was childishly threatened. For me, it's clear, somehow Krita contribution is not for bug reports what can't be solved fast and easily. So this is still an awkward situation because I still have a not so simple not so clear issue with Krita. I report this issue only because I have still hope in Krita. It's a basic thing when your work is lost by a software, you would report it to developers, wouldn't you? The crash can be reproduced sometimes. -- Backtrace: Application: Krita (krita), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fcec2488940 (LWP 23496))] Thread 5 (Thread 0x7fce7a134700 (LWP 23515)): #0 0x7fcebe86c74d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fceb6c6c38c in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7fce700033b0, timeout=, context=0x7fce7990) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7fce7990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3835 #3 0x7fceb6c6c49c in g_main_context_iteration (context=0x7fce7990, may_block=may_block@entry=1) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3901 #4 0x7fcebf39a0bb in QEventDispatcherGlib::processEvents (this=0x7fce78c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fcebf3415ba in QEventLoop::exec (this=this@entry=0x7fce7a133c00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7fcebf1765e4 in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7fce9ee17f86 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fcebf181727 in QThreadPrivate::start (arg=0xc9c2df0) at thread/qthread_unix.cpp:367 #9 0x7fceb83106ba in start_thread (arg=0x7fce7a134700) at pthread_create.c:333 #10 0x7fcebe87841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fce83b0f700 (LWP 23514)): #0 0x7fcebe86827d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fceb6caf6f0 in read (__nbytes=16, __buf=0x7fce83b0ea40, __fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44 #2 g_wakeup_acknowledge (wakeup=0x7fce940025b0) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gwakeup.c:210 #3 0x7fceb6c6be74 in g_main_context_check (context=context@entry=0x7fce7c000990, max_priority=2147483647, fds=fds@entry=0x7fce7c004870, n_fds=n_fds@entry=1) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3632 #4 0x7fceb6c6c330 in g_main_context_iterate (context=context@entry=0x7fce7c000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3837 #5 0x7fceb6c6c49c in g_main_context_iteration (context=0x7fce7c000990, may_block=may_block@entry=1) at /build/glib2.0-b4FPyK/glib2.0-2.48.2/./glib/gmain.c:3901 #6 0x7fcebf39a0bb in QEventDispatcherGlib::processEvents (this=0x7fce7c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7fcebf3415ba in QEventLoop::exec (this=this@entry=0x7fce83b0ec50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #8 0x7fcebf1765e4 in QThread::exec (this=) at thread/qthread.cpp:525 #9 0x7fce9e98e195 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fcebf181727 in QThreadPrivate::start (arg=0xc87ea30) at thread/qthread_unix.cpp:367 #11 0x7fceb83106ba in start_thread (arg=0x7fce83b0f700) at pthread_create.c:333 #12 0x7fcebe87841d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3
[krita] [Bug 394974] Layer converted filter mask causes Krita crash most of the time.
https://bugs.kde.org/show_bug.cgi?id=394974 --- Comment #27 from Andras --- I know it's closed and it's only for bug tracking not a forum like thing however thanks to too much pride from both side, I have had statements what I'd like to correct now, that's it. I'm not changing my OS from Linux and Krita is still the best option for retouch too on Linux so I still use it and donate for development. I think it's silly to give up on something just because some people is too confident and biased, don't get me wrong I mean it as including me with my stupid pride. That's all and if someone read this, I'm sorry for bad comments and thanks for the help, keep up the good work! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394974] Layer converted filter mask causes Krita crash most of the time.
https://bugs.kde.org/show_bug.cgi?id=394974 Andras changed: What|Removed |Added CC|andrasszerencs...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 394974] Layer converted filter mask causes Krita crash most of the time.
https://bugs.kde.org/show_bug.cgi?id=394974 --- Comment #26 from Andras --- (In reply to Boudewijn Rempt from comment #25) > If you feel I have transgressed the boundaries of > https://www.kde.org/code-of-conduct/, please contact > https://ev.kde.org/workinggroups/cwg.php with a complaint. I care about efficiency, don't have much time and I start to pay my Adobe subscription instead. Thanks for the encouragement. -- You are receiving this mail because: You are watching all bug changes.
