[00:07] <Fire-Dragon-DoL> there you go! plasma-workspace
[00:12] <Fire-Dragon-DoL> looks like starting yakuake crashes the login in some way
[00:12] <Fire-Dragon-DoL> yep
[00:13] <Fire-Dragon-DoL> not sure why
[00:13] <Fire-Dragon-DoL> well, time to fix bak everything and start the investigation! :P
[00:20] <Fire-Dragon-DoL> yes confirmed
[00:21] <Fire-Dragon-DoL> so, is it normal that if you add a startup script with `exit`
[00:21] <Fire-Dragon-DoL> it stops you from logging in?
[00:21] <Fire-Dragon-DoL> or is it a bug of new updates?
[00:22] <Fire-Dragon-DoL> I had this script running for long time, so I guess this is a new problem
[00:23] <Fire-Dragon-DoL> and it explains why the log was so quiet
[00:40] <Fire-Dragon-DoL> now the question is
[00:40] <Fire-Dragon-DoL> who handles the startup in KDE?
[00:40] <Fire-Dragon-DoL> I want to report the bug, but not sure where
[00:44] <valorie> Fire-Dragon-DoL: good question
[00:44] <Fire-Dragon-DoL> I found this which seem to match: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1448677
[00:44] <valorie> if you don't get an answer here, try #kde or even #kde-devel
[00:44] <Fire-Dragon-DoL> also the problematic file was in .config/plasma-workspace/env
[00:44] <Fire-Dragon-DoL> does plasma-related stuff belong to it?
[00:45] <Fire-Dragon-DoL> i guess
[00:45] <valorie> you'll get asked to go to #plasma if that's needed
[00:52] <Fire-Dragon-DoL> ok let's see there
[02:03] <user|20208> Hi
[02:03] <user|20208> I'm a noob
[02:03] <user|20208> Want to know how can I update to the latest kubuntu.
[03:32] <wayne__> user 20208 you still there? I can help. I'm using kubuntu.
[03:32] <wayne__> You wanted to know how you can update to the latest kubuntu.
[03:33] <wayne__> first thing is open a terminal and type: sudo apt-get update
[03:34] <wayne__> actually, scratch that. Put this into a terminal window: sudo apt update && sudo apt full-upgrade -y
[03:34] <wayne__> That will give you a full system upgrade.
[04:17] <krytarik> wayne__: They left 2 mins later.
[04:19] <krytarik> And they meant upgrade to the latest version of Kubuntu.
[04:23] <EoflaOE> Now, back to the problem. I redownloaded and the hash checksum matched.
[05:16] <EoflaOE> And now I re-made a bootable USB and when I booted from it, using boot-loader trick switching ports, I got Squashfs errors about zlib decompression failed and the install started without decoration like plain X11. I selected Try, and the same problem reappeared again.
[07:02] <lordievader> Good morning
[12:15] <BluesKaj> Hiyas all
[12:17] <Captain_Haddock> Hi
[12:19] <Captain_Haddock> So, on this desktop, I used to have a dual boot of Windows 7 and Kubuntu 16.04. Both worked fine except for one thing. When I shut down the desktop, it shut down just fine on Windows, but restarted with Kubuntu.
[12:20] <Captain_Haddock> So what I used to do in Kubuntu was to just suspend the system all the time, which was an acceptable stop gap solution.
[12:21] <Captain_Haddock> Now, I've installed Kubuntu 17.10 on a new SSD. The shut down problem continues to persist. What's new is that Suspend does not work either. The computer does suspend, but only for around 4 seconds after which it wakes up again.
[12:21] <Captain_Haddock> Any idea why this might be happening?
[12:23] <BluesKaj> all pertitions on one drive?
[12:24] <BluesKaj> partitions
[12:24] <BluesKaj> Captain_Haddock,^
[12:24] <Captain_Haddock> BluesKaj: No. The install occupies the entire SSD, but I still access the old HDD as well.
[12:26] <Captain_Haddock> BluesKaj: That said, Suspend worked just fine just now :/ It didn't work earlier today or all day yesterday.
[12:26] <Captain_Haddock> Lemme try again.
[12:26] <BluesKaj> then you have to set one drive as first in your boot sequence , if you have windows on one and kubuntu on the other
[12:27] <Captain_Haddock> Missed any reply. But it worked again :|
[12:27] <BluesKaj> then you have to set one drive as first in your boot sequence , if you have windows on one and kubuntu on the other
[12:27] <Captain_Haddock> BluesKaj: In the BIOS?
[12:28] <BluesKaj> yes, but if it's working now then just leave it ...uefi is finicky when it comes to booting
[12:29] <BluesKaj> asuming uefi vs bios
[12:29] <BluesKaj> assumimg
[12:29] <Captain_Haddock> Yes. Should this affect shutting down as well?
[12:29] <BluesKaj> oops
[12:30] <Captain_Haddock> I was thinking that this would be some IRQ-related issue.
[12:30] <BluesKaj> I prefer to suspend
[12:31] <BluesKaj> ii'ss a boot sequence setting IMO
[12:32] <Captain_Haddock> I see. I'll have a tinker with the BIOS. I do remember either disabling UEFI or doing something similar to get the system to boot off a pen drive a few years ago.
[12:32] <BluesKaj> but if it's working now , why muck about
[12:32] <Captain_Haddock> Maybe that is related.
[12:33] <martok> I'm curious if any else running 17.04 is experiencing a bad superblock problem?
[12:33] <Captain_Haddock> You're right. It's not a biggie, if Suspend is working OK :)
[12:33] <martok> *anyone else
[12:34] <BluesKaj> martok,17.04 is eol as of today I think
[12:34] <Captain_Haddock> BluesKaj: Thanks for your time.
[12:34] <BluesKaj> Captain_Haddock, np
[12:36] <BluesKaj> !zesty
[12:36] <BluesKaj> oops support ended over 2 weeks ago martok
[12:37] <martok> Blueskaj: That I know. But why would it mess up the superblock? This is the second laptop in 2 days that I had to fix the superblock just to get back into the system to back it up
[12:54] <BluesKaj> martok, no idea. but I suggest you upgrade to 17.10 asap
[13:10] <martok> BluesKaj: Definitely. I tried upgrading one of the laptops, but that didn't work out too well. So what I'm doing is just doing a clean install. Much faster anyway. I was pretty much just courious as to why it would mess up the superblock
[13:12] <BluesKaj> martok, is windows on the laptop as well?
[13:14] <BluesKaj> i had superblock problems when i was dual booting W7 and kubuntu in legacy mode on a dos table instead of gpt on my lenove laptop
[13:14] <BluesKaj> lenovo
[13:15] <BluesKaj> so i made the switch back uefi and gpt
[13:42] <martok> BluesKaj: sorry for the late response. Windows is on one of the laptops. Kubunu is the only OS on the other
[13:45] <martok> BluesKaj: that's good to know. I am actually installing 17.10 on the laptop uefi and gpt
[13:46] <BluesKaj> martok, ok , then the 17.10 install should go smoothly
[13:47] <BluesKaj> I no longer need windows on any of my computers...thank God :-)
[13:48] <martok> BluesKaj: Me neither. It's client computers. LOL
[13:49] <BluesKaj> ok
[15:17] <elichai2> hey, is it possible to reinstall kubuntu on existing system? (with luks)
[17:09] <marcellus> Hi people! Everytime I try to do any updates I get following error message: "Fehler beim Laden der QML-Datei: file:///usr/share/plasma/plasmoids/org.kde.discovernotifier/contents/ui/main.qml:23:1: module "org.kde.discovernotifier" is not installed"
[17:10] <marcellus> I dont know how to solve it
[20:50] <Tirali> After kubuntu hwe kernel 4.13 which uses smbv3 the smb manager smb4k is not working any longer, will there be a backport soon? Or is there another solution to get this fixed?
[20:51] <Tirali> kubuntu 17.10 has already smb4k 2.0 which is supporting smbv3 i think