=== panera is now known as user__
=== lex is now known as Guest34809
[06:12] <lordievader> Good morning
[06:51] <IrcsomeBot> <Swift110> Hey
[07:04] <IrcsomeBot> <avinash512> @woodworkingcavem> I recently upgraded to 19.04 and now am unable to logoff using the Leave -, Restarting the system or logging off might help
=== juboxi is now known as jubo2
[07:21] <lordievader> Hrmm, that Telegram bot makes replies look very strange on Matrix.
=== amichair_ is now known as amichair
[07:50] <jubo2> Hi. When trying to open a Plasma Vault I insert the correct password, but it says "Failed to open: Unable to perform the operation". I did delete and recreate KDE Wallet, because it suddenly started asking for an unset password. Can this effect? How can I get more verbose message of why the vault won't open?
[07:51] <jubo2> I have googled, but this does not seem to be a common error
[07:59] <IrcsomeBot> <Swift110> Ok
[08:01] <lordievader> jubo2: Do you see something more if you open the manager via the command line (`kwalletmanager5`) and then try to open it?
[08:01] <jubo2> lordievader: I try that now
[08:02] <jubo2> lordievader: It says "Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)" and opens the GUI
[08:02] <jubo2> Is the CryFS somehow using the wallet?
[08:03] <lordievader> Is that when opening the manager, or when opening the wallet?
[08:03] <jubo2> I have a kdewallet.kwl.bak where I moved the wallet with the unset password that it keeps on asking for
[08:03] <jubo2> lordievader: manager
[08:03] <lordievader> Oh, wait. My line of thinking is wrong.
[08:04] <jubo2> but having a KDE Wallet which one is unable to open, because no password was ever set, is no fun
[08:04] <lordievader> jubo2: This might help you: https://www.reddit.com/r/kde/comments/a3lj7b/vault_wont_open/?st=k0w4jxqe&sh=3ba7116a
[08:07] <jubo2> lordievader: I tried the cli way of opening the vault. It says "Loading config file (this can take some time)...Error: Could not load config file. Did you enter the correct password?"
[08:07] <jubo2> and I am sure the password is right
[08:08] <jubo2> the only thing that has changed (afaik) is that I deleted the default wallet (because it wanted a password that was never set). I don't see why the cryfs would depend on the wallet. Am I wrong?
[08:09] <lordievader> I suppose the wallet is only used to supply the password.
[08:09] <jubo2> This is not a full panic situation as nearly all data in the vault is also elsewhere, but this kind of unreliability is not cool
[08:09] <jubo2> lordievader: so what to do?
[08:10] <jubo2> and wallet provides passwords, but cryfs asks the password from the user. Perhaps it gets the hash to compare it with from the wallet
[08:11] <lordievader> jubo2: https://github.com/cryfs/cryfs/issues/235
[08:14] <jubo2> lordievader: using the -f switch does not change the output at all
[08:15] <jubo2> Iirc there is no way to set a password for a KDEWallet where the password is unknown
[08:16] <jubo2> If the Plasma-Vault depends on KDE Wallet it would be nice to mention
[08:19] <lordievader> It shouldn't. Don't know much about cryfs, but seems to be just an encrypted filesystem where kwallet supplies a password instead of the user.
[08:19] <jubo2> CryFS asks for the password from the user
[08:19] <jubo2> and now it does not complain about incorrect password, but just that it is unable to perform the operation
[08:21] <Unit193> Somewhat unrelated, but libpam-mount is pretty handy with cryfs/gocryptfs.
[08:22] <lordievader> jubo2: Is there anything in dmesg about it?
[08:22] <jubo2> lordievader: how do I check? (I'm not texy)
[08:22] <lordievader> `sudo dmesg -T`
[08:24] <jubo2> lordievader: nope, nothing in 'dmesg -T' about the vault not working as expected
[08:24] <lordievader> Also nothing about fuse?
[08:24] <jubo2> lordievader: nope
[08:25] <lordievader> What about the syslog?
[08:25] <jubo2> lordievader: how do I check?
[08:25] <lordievader> `cat` or `tail` `/var/log/syslog`
[08:27] <jubo2> lordievader: nope.. just one 'fuse init' 45 minutes ago (which was approx the reboot time)
[08:28] <lordievader> Could you pastebin the full output of an `cryfs <basedir> <mount>` operation?
[08:30] <jubo2> lordievader: ok
[08:31] <jubo2> lordievader: https://paste.debian.net/1102144/
[08:32] <lordievader> Do you have strace installed?
[08:37] <jubo2> lordievader: yes
[08:41] <lordievader> Could you give the output of `strace -e open cryfs <basedir> <mount>`?
[08:42] <jubo2> lordievader: Ran it. Just reports '+++ exited with 11 +++'
[08:42] <jubo2> otherwise looks like the last pastebin
[08:44] <lordievader> > Under Linux and most other Unix variants, the signal number 11 indicates a segmentation fault
[08:44] <lordievader> From https://stackoverflow.com/questions/31103254/meaning-of-exit-code-11-in-c
[08:45] <lordievader> Are you sure nothing, apart from kwallet, changed?
[08:45] <jubo2> lordievader: yes.
[08:46] <lordievader> Could you manually create a new cryfs and try to mount that?
[08:46] <jubo2> manually... is it ok if I do with GUI?
[08:47] <lordievader> If it is a frontend for cryfs specifically, sure.
[08:48] <lordievader> https://www.cryfs.org/tutorial/
[08:48] <jubo2> lordievader: Ok. I created a new vault and it opens up just fine
[08:48] <lordievader> Ok, so it is a problem specific to this mount.
[08:49] <lordievader> Wait, can you also open the vault (cryfs) manually from the commandline?
[08:49] <jubo2> lemme try
[08:50] <jubo2> yeah. opens up
[08:50] <jubo2> from cli
[08:51] <jubo2> lordievader: yes. I can open the new vault from GUI and from CLI and write files into it.
[08:51] <jubo2> So everything points to that for some reason that I don't comprehend the Plasma Vault uses KDE Wallet for something
[08:52] <lordievader> No
[08:53] <lordievader> It doesn't
[08:53] <jubo2> ah. ok.
[08:54] <lordievader> This seems more like a problem with cryfs. You might want to make an issue on github about it. They are much more knowledgable about cryfs than I am 😉
=== MANIAC is now known as Guest68155
[12:07] <BluesKaj> Hi folks
[12:20] <IrcsomeBot> <Swift110> Hey blues
[12:21] <IrcsomeBot> <Swift110> You should come on to ##forthenerds
[12:24] <BluesKaj> never considered myself a nerd
[12:26] <IrcsomeBot> <Swift110> Lol that doesn't matter
[12:27] <BluesKaj> thanks for the invite, but I'm on 8 chats already
[12:35] <IrcsomeBot> <Swift110> Oh ok no problem
[13:36] <IrcsomeBot> <anvarom> Fwd from anvarom: Hello everyone! I have two technical questions: … 1- In older versions, in multimedia settings, there had an option to create a virtual device for simultaneous output, but in Kubuntu 19.04 this option is not present. Someone can tell me why? This obligates me to install paprefs package to enable this option. … 2- Could someone tell me if is possible connect more than one audio bluetooth device in A2DP mode? For n
[13:36] <IrcsomeBot> only can connect one in A2DP mode, it does not let me connect more than one in this mode.
=== MANIAC is now known as Guest48080
[15:02] <Crell> Hi folks. Screen issue with 19.04. My computer is up and running, but when I plug it into an external monitor (USBC dock), I see only the background on both displays. The apps are still running and if I  undock it again I get everything back on the laptop screen, but nothing is showing up on either display when docked.
[15:03] <Crell> I cannot open settings, either, as that opens wherever the other windows are hiding so I cannot use it while docked.  I've not had anything like this happen in a very long time.  Any idea what to do with it?
=== genii_ is now known as genii
=== Lord_of_Life_ is now known as Lord_of_Life
=== malibu_ is now known as malibu
=== malibu is now known as Guest62971
=== malibu_ is now known as malibu
=== guschtel is now known as Guschtel