[04:11] <wawan> y
[06:27] <konrados> lordievader, are you here?
[06:27] <konrados> Morning btw :)
[07:29] <lordievader> Good morning.
[10:09] <PSPriya> #drupal
[10:19] <yossarianuk> hi - I have a really odd issue that's only recently started - its fairly annoying,
[10:20] <yossarianuk> I am unable to print to any printer connected to a Cups server from any GTK applications
[10:20] <yossarianuk> its fine from KDE and any QT app
[10:20] <yossarianuk> > i've been getting by so far by printing to .pdf file in firefox then printing the .pdf from Okular
[10:21] <yossarianuk> I can print if I connect directly to the printer, not via our local cups server (gtk apps only)
[10:21] <yossarianuk> any ideas how to fix this annoying/odd bug?
[10:23] <yossarianuk> i.e the print button in Firefox, Evolution is geyed out next to any printer connected to the cups server - i see the message 'Getting printer information failed'
[10:23] <yossarianuk> so am unable to print from my main browser
[10:24] <yossarianuk> Thunderbird however works
[10:24] <yossarianuk> as does crome
[10:24] <yossarianuk> chrome
[10:24] <yossarianuk> firefox/evolution doesn't
[11:04] <mparillo> If I dual-boot (YY and XX), and I get kernel updates, is it possible that they change the default GRUB boot sequence?
[11:39] <yossarianuk> mparillo: yes
[11:39] <yossarianuk> using legacy and UEFI
[11:39] <yossarianuk> easiest way if using uefi is to install rEFInd
[11:43] <mparillo> TY yossarianuk. I am using legacy.
[11:45] <mparillo> If I get too annoyed, in the past I have used https://launchpad.net/~danielrichter2007/+archive/ubuntu/grub-customizer
[12:49] <BluesKaj> Hiyas all
[14:10] <johns_> I was trying to add dm-raid through LVM as a mirror raid using dm-mirror. For the root volume. Upon rebooting it could not assemble the array saying personality for raid 1 not found. It did find other personalities but apparently dm-mirror.ko was not loaded?
[14:11] <johns_> I ended up in the initrd rescue shell but modprobe gives no output as to what it's doing; ie. if you use a nonsense term if will still give no output.
[14:11] <johns_> so apparently the module is not getting loaded; I may have to add it to the initrd of course. But still. It is already in /lib/modules. The module is there. But the personality is not found.
[14:12] <johns_> I wonder what I need to do (in the rescue shell) to load the module and to get any output as to what modprobe is doing.
[14:14] <BluesKaj> johns_, this could be a questio for #kde or ##linux
[14:15] <johns_> but note that the debian/ubuntu initrd system is debian/ubuntu specific...
[14:15] <johns_> I will go to ##linux though. Not #kde :P :).
[14:22] <johns_> I can't find whether adding a file to /etc/initramfs-tools/modules or something similar will automatically load it or whether I will need force_load in a hook file...
[14:24] <johns_> bbl
[14:43] <JohnDroid> Hello, I'd like to share with you my experience with KDE neon
[14:43] <JohnDroid> https://forum.kde.org/viewtopic.php?f=309&t=133432&p=362045#p362045
[14:43] <Lambda___> Sup everyone.
[14:53] <Lambda___> Hi @ KurousagiMK2
[14:56] <KurousagiMK2> hi need something?
[15:09] <johns_> I cannot send to ##linux.....
[15:11] <johns_> Hi BluesKaj-pi I initially thought the problem was because of a "bug" in the dmraid package but it doesn't really use dmraid.
[15:18] <johns_> well found the answer, raid1.ko is just not loaded in the initrd, even though raid456.ko is, for some reason. Thanks.
[15:18] <johns_> I was thinking I needed to look for dm-mirror but that is the old setup, not the new one.
[15:19] <johns_> dm-mirror *is* included but the newer LVM uses raid1 by default.
[15:21] <johns_> so I'm off rebooting again to the older Kubuntu install that doubles as safety valve :p.
[15:25] <ranu> Hello, how to suspend the computer to disk in kde5?
[15:26] <ranu> sudo echo disk > sys/power/state/ doesn't work as I don't have the permission
[17:20] <my> hi
[17:34] <zodiac19> #kubuntu-offtopic if you're looking for plain conversation ^^ Hello!
[18:26] <yurusu> konbanwa
[18:29] <yurusu> why are you all so dead?
[18:30] <Pici> kubuntu works fine for everyone so no one has any support questions.
[18:30] <yurusu> understood
[18:52] <regretting_gddm> hello
[18:58] <zodiac19> irc.synirc.net -- #rpgmaker
[18:58] <zodiac19> I'm in here having a really indepth conversation
[18:58] <zodiac19> I'm being told to reward good employees macbooks for good work >.<
[19:17] <kubuntu_16_wante> hello
[19:18] <kubuntu_16_wante> i try to update my KUbuntu 14.04.3 LTS to KUbuntu 16.04.1 LTS
[19:19] <kubuntu_16_wante> but when I execute sudo do-release-upgrade -m desktop -f DistUpgradeViewKDE I get an error message:
[19:19] <kubuntu_16_wante> NameError: name 'pyqtSlot' is not defined
[19:19] <kubuntu_16_wante> at File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherKDE.py", line 172, in DistUpgradeFetcherKDE
[19:20] <kubuntu_16_wante> how to I make it wor or at least track down the error?
[19:26] <BluesKaj-pi>  kubuntu_16_wante why that long command,. a simple sudo do-release-upgrade should suffice, then a update and upgrade once the releas is fiished installing
[19:26] <BluesKaj-pi> finished even
[19:27] <kubuntu_16_wante> this is what the GUI updater startes to execute.
[19:27] <kubuntu_16_wante> startes -> states
[19:28] <BluesKaj-pi> don´t muck ubout with what the updater does
[19:29] <BluesKaj-pi> use one or the other, not some hybrid commands
[19:32] <kubuntu_16_wante> when I start do-release-upgrade only the system does almost nothing...
[19:34] <BluesKaj-pi> check the update managerand set it to upgrade LTS only
[19:35] <kubuntu_16_wante> it is set to upgrade LTS only
[19:35] <kubuntu_16_wante> some days ago I already startet tzhe upgrade.
[19:36] <kubuntu_16_wante> then the system does a lot but failed to finish
[19:37] <kubuntu_16_wante> I repeated 'dpkg --configure -a' until it returned immediately
[19:38] <kubuntu_16_wante> since then the system is telling me that a newr version is available but does nothing when I klick "do upgrade"
[19:40] <BluesKaj-pi> have you done a upgrade of your existing system, if not. do so
[19:41] <kubuntu_16_wante> yes I did
[19:42] <BluesKaj-pi> remove any ppas from your sources.list or package manger
[19:44] <kubuntu_16_wante> the upgrader claimed it had done this.
[19:45] <kubuntu_16_wante> I just turned off "LTS only", waiting what happens now...
[19:46] <BluesKaj-pi> check the package manager ¨¨öther sources"anyway
[19:46] <kubuntu_16_wante> 1 neues Paket wird installiert. 15 Pakete werden aktualisiert.
[19:46] <BluesKaj-pi> you will get 15.10 not 16.04
[19:47] <kubuntu_16_wante> much less than expected
[19:47] <kubuntu_16_wante> and themn in turn i can upgrade to 16?
[19:48] <BluesKaj-pi> thatś the long method :-)
[19:48] <kubuntu_16_wante> this would be ok as long as it worked...
[19:49] <BluesKaj-pi> hang on ...brb
[19:53] <kubuntu_16_wante> system is still on 14 :o(
[20:05] <kubuntu_16_wante> system is still on 14 :o(
[20:06] <BluesKaj> run sudo apt full upgrade to see if any packages are upgraded or installed
[20:07] <kubuntu_16_wante> system is rebooting.
[20:07] <BluesKaj> also make sure you are using a source mirror that's stable
[20:07] <kubuntu_16_wante> I just edited /etc/lsb-release
[20:07] <kubuntu_16_wante> will see if that makes something usefull...
[20:08] <johns_> var.mount is always pulled in by systemd regardless of what you do. So it is not possible to put a /var line in fstab and have it not be used.
[20:08] <johns_> I wonder how to ensure that the noauto or nofail options are being honoured (making it an optional mount) but thus far it is not working.
[20:09] <BluesKaj> lsb_ release just tells you which OS you're running, kubuntu_16_wante
[20:09] <kubuntu_16_wante> invalid operation "full"
[20:09] <johns_> maybe I can just mask the entire service....
[20:10] <BluesKaj> kubuntu_16_wante, sorry full-upgrade
[20:10] <johns_> gotta try, brb.
[20:10] <kubuntu_16_wante> I know, but I beleve my "broken" updae already installed the "16" packages but did not change the lsb-release file
[20:11] <kubuntu_16_wante> this installe 2 packages (the flash player plugin
[20:11] <BluesKaj> it's not hard to tell, 16 from 14 , check your login page if orange purple etc then it's 16.04
[20:12] <kubuntu_16_wante> you mean the background image?
[20:13] <BluesKaj> also kubuntu_16_wante run plasmashell -v , if says 5.x.x the you're on 15.10 or 16.04
[20:14] <BluesKaj> kubuntu_16_wante, yes the background
[20:14] <kubuntu_16_wante> plasmashell gives 5.5.5
[20:15] <kubuntu_16_wante> then I'd consider this done.
[20:15] <kubuntu_16_wante> thanks so fahr.
[20:15] <johns_> nope didn't work, I will have to create my own fstab :p.
[20:15] <BluesKaj> what does uname -a output?
[20:15] <BluesKaj> kubuntu_16_wante,^
[20:16] <kubuntu_16_wante> 4.4.0-34-generic #ubuntu SMP...
[20:16] <kubuntu_16_wante> now I have another problem ;o)
[20:17] <kubuntu_16_wante> since the failed upgrade last week my KDM does not come up any more.
[20:17] <BluesKaj> yeah, your on 16.04 , 14.04 uses the 4.2 kernel , I'm still on it
[20:17] <kubuntu_16_wante> I learned, that I'd rather use gddm, but this does not work either:
[20:18] <kubuntu_16_wante> it does not start after boot and when logging on it returnes to the login screen rather than openning a user session
[20:18] <BluesKaj> kubuntu_16_wante, kdm is replaced by sddm, and you a re now the lucky receipent of an OS controlled by systemd as well
[20:19] <kubuntu_16_wante> i cnged to lightdm but this lags some important features too.
[20:20] <kubuntu_16_wante> first of all openning another user session from a users lock screen does not work.
[20:21] <kubuntu_16_wante> the screen fickers and does not respont to <ctrl><alt><baspace> or any other console/scheen change key stroke
[20:22] <BluesKaj> kubuntu_16_wante, ok ctl+alt+F1-F6, thei takes you to a shell/vt/tty, login, then run sudo systectl enable sddm , then sudo sytemctl start sddm, then update and upgrade and reboot
[20:22] <kubuntu_16_wante> so my main goal was to get KDM back or sddm working.
[20:22] <YankDownUnder> BluesKaj: You could always suggest to him to do "sudo dpkg-reconfigure kdm"
[20:22] <BluesKaj> sudo systemctl enable sddm
[20:22] <BluesKaj> YankDownUnder, so can you :-)
[20:23] <BluesKaj> if you think it will help
[20:23] <kubuntu_16_wante> ok, I'll try this in that order...
[20:23] <YankDownUnder> BluesKaj: I could, yes, I very well could, but that would interrupt my coffee and smoke...
[20:24] <BluesKaj> well you could have just as well suggested it to kubuntu_16_wante , instead of me
[20:24] <BluesKaj> YankDownUnder, I wouldn't be offended like some
[20:25] <kubuntu_16_wante> ceep calm! I think I get it... ,o)
[20:25] <YankDownUnder> Hehehe...what a lovely Wednesday - no one's having problems, it's a warm 13c, and everyone is happy! :)
[20:26] <BluesKaj> well, it's 30C outside here, but it's a comfy 23C in our house
[20:26] <kubuntu_16_wante> ok, I did sudo systectl enable sddm from my KDE seson and rebooted, got lightdm again...
[20:27] <YankDownUnder> BluesKaj: I'll trade you the 30c...easy done...
[20:27] <YankDownUnder> kubuntu_16_wante: Try: sudo dpkg-reconfigure kdm
[20:28] <BluesKaj> kubuntu_16_wante, run sudo systemctl enable sddm , I corrected the mistake, but i guess you missed that
[20:29] <kubuntu_16_wante> i used keyword compleetion...
[20:29] <YankDownUnder> "compleetion" - yersh...bad spelling that :)
[20:30] <kubuntu_16_wante> after sudo sytemctl start sddm I have a black screen with a blinking cursor but mot responding at all.
[20:31] <YankDownUnder> kubuntu_16_wante: You stated that "lightdm" was still running, yes? If anything, you might want to make sure that it's NOT running before you start "sddm" - that's going to cause some strange issues...
[20:31] <kubuntu_16_wante> ok, then I have "strange things" happening now. will reboot...
[20:32] <YankDownUnder> kubuntu_16_wante: Um...you shouldn't have to reboot, bro...
[20:32] <kubuntu_16_wante> systemctl stop sddm did not work (via ssh)
[20:33] <kubuntu_16_wante> system is back still showing lightdm
[20:33] <YankDownUnder> kubuntu_16_wante: Wait a tick - you're not even sitting in front of this machine?
[20:34] <BluesKaj> btw sddm has replaced kdm , just checked, think the same goes for lightdm
[20:34] <YankDownUnder> Yeah it has - but isn't he running a borked version of 14.04?
[20:35] <BluesKaj> no YankDownUnder he has Xenial installed , he just didn't realize it
[20:36] <kubuntu_16_wante> YankDownUnder: i have 2 mashines...
[20:36] <YankDownUnder> Right oh.
[20:36] <BluesKaj> plasma 5.5.5
[20:36] <kubuntu_16_wante> ystemd[1]: sddm.service: Control process exited, code=exited status=1
[20:36] <kubuntu_16_wante> systemd[1]: Failed to start Simple Desktop Display Manager.
[20:37] <kubuntu_16_wante> systemd[1]: sddm.service: Triggering OnFailure= dependencies.
[20:37] <YankDownUnder> kubuntu_16_wante: Mate, check this out - do "service lightdm stop" - right? Once that's stopped, do: sudo dpkg-reconfigure sddm => after that's all happy, THEN type either "service sddm restart" or "systemctl start sddm" => try "servicce" first, eh?
[20:37] <BluesKaj> hoh , didyou run sudo apt update && sudo apt upgrade ? kubuntu_16_wante
[20:38] <kubuntu_16_wante> YankDownUnder
[20:38] <kubuntu_16_wante> YankDownUnder
[20:38] <kubuntu_16_wante> YankDownUnder
[20:38] <kubuntu_16_wante> YankDownUnder
[20:38] <kubuntu_16_wante> did that
[20:38] <BluesKaj> lighytdm is probly not even installed at this point
[20:38] <dax> (don't repeat like that, please. it sets off anti-spam alarms)
[20:38] <kubuntu_16_wante> now systemctl start sddm?
[20:39] <YankDownUnder> kubuntu_16_wante: Try: sudo service sddm restart
[20:39] <kubuntu_16_wante> BluesKaj
[20:39] <kubuntu_16_wante> it is quite alive for not being installed... ;o)
[20:40] <kubuntu_16_wante> looks good
[20:40] <BluesKaj> kubuntu_16_wante, did you choose lightdm when you were upgrading at some point?
[20:40] <YankDownUnder> kubuntu_16_wante: We'll get rid of lightdm in a tick - have to get sddm working...it ain't rocket science
[20:40] <kubuntu_16_wante> but I only see 3 of the 6 users
[20:40] <kubuntu_16_wante> with KDM I had a vertical list.
[20:40] <kubuntu_16_wante> can I have that back?
[20:41] <YankDownUnder> kubuntu_16_wante: You can change the sddm theme to something more friendly later - is it working now?
[20:41] <BluesKaj> KDM won't be available, but apparently lightdm is , just checked again :-)
[20:41] <kubuntu_16_wante> ok, I have sddm running but I cannot login :o(
[20:42] <YankDownUnder> "cannot login" is not very descriptive...
[20:43] <kubuntu_16_wante> after type the (correct) password and pressing enter the screen gets dark for 2 seconds and then the login screen comes back.
[20:43] <BluesKaj> ok ,he's in that no gpu driver or broken gpu driver loop
[20:43] <YankDownUnder> BluesKaj: Lovely that
[20:43] <YankDownUnder> BluesKaj: Like watching political news!
[20:43] <kubuntu_16_wante> if the gpu driver has a problem why does loging work with lightdm?
[20:44] <BluesKaj> kubuntu_16_wante, what gpu ?
[20:44] <kubuntu_16_wante> YankDownUnder came up with the GPU thing
[20:45] <kubuntu_16_wante> no, it was yourself...
[20:46] <YankDownUnder> What dialog is there - what did you do or what are you doing?
[20:46] <BluesKaj> kubuntu_16_wante, that's a good question, but it's the same as why alive media like live cd shows a desktop, but not a proper install ...forgotten the expalnation
[20:47] <kubuntu_16_wante> anyway, the only difference between a working ligin and a failing is the login service..
[20:47] <kubuntu_16_wante> when I change back to lightdm login will work again.
[20:47] <BluesKaj> I'm guilty of the gpu , because I had that problem with xenail at first, but then I installed the nvidia 340 driver in the vt/tty shell and it worked
[20:48] <kubuntu_16_wante> BTW GPU is VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1)
[20:48] <YankDownUnder> kubuntu_16_wante: Are the drives installed for that on this system?
[20:48] <kubuntu_16_wante> sure
[20:49] <kubuntu_16_wante> nvidia              10076160  66 nvidia_modeset,nvidia_uvm
[20:49] <YankDownUnder> kubuntu_16_wante: And you just got that data from...where?
[20:49] <kubuntu_16_wante> ~# lsmod | grep nvi
[20:49] <kubuntu_16_wante> nvidia_uvm            696320  0
[20:49] <kubuntu_16_wante> nvidia_modeset        745472  3
[20:49] <kubuntu_16_wante> nvidia              10076160  66 nvidia_modeset,nvidia_uvm
[20:49] <kubuntu_16_wante> drm                   364544  3 nvidia
[20:49] <dax> looks like lsmod
[20:49] <dax> yay i win
[20:51] <BluesKaj> kubuntu_16_wante, you are probly running thenouveau driver which has problems with 16,04 , sudo apt install nvidia-361
[20:52] <kubuntu_16_wante> »nvidia-361« ist bereits die neuste Version (361.42-0ubuntu2).
[20:52] <kubuntu_16_wante> already newest version
[20:52] <kubuntu_16_wante> is now marked manually installed
[20:53] <YankDownUnder> Deutsche...ja.
[20:53] <kubuntu_16_wante> sorry, could not prevent that... ;o)
[20:53] <YankDownUnder> kubuntu_16_wante: Don't be sorry, be proud.
[20:57] <BluesKaj> kubuntu_16_wante, you could remove the 361 driver and let it fall back to the nouveau just to make sure the 361 is to blame
[20:58] <kubuntu_16_wante> apt remove nvidia-361
[21:00] <kubuntu_16_wante> same login behavior but a non native resolution.
[21:02] <BluesKaj> kubuntu_16_wante, did you sudo apt update and upgrade as suggested before removing the 361
[21:03] <kubuntu_16_wante> ahh, no...
[21:03] <BluesKaj> aah,,do so now
[21:04] <kubuntu_16_wante> no packages to install or update
[21:06] <BluesKaj> ok, so the problem is more serious than I thought, but I have no idea what it is
[21:06] <kubuntu_16_wante> at least I'm not alone anymore... ;o)
[21:07] <kubuntu_16_wante> thanks for your time!
[21:07] <BluesKaj> this has been an ongoing problem with 16.04 ...it's still buggy
[21:08] <johns_> I have had a Kubuntu 16.04 that became unusable after installing and removing the nvidia drivers; actually already after installing them I think.
[21:08] <johns_> I have had to reinstall.
[21:08] <johns_> I think the current install runs fine thus far
[21:08] <johns_> But I won't be messing with any graphics drivers any more unless I have a snapshot or backup.
[21:09] <kubuntu_16_wante> the system is working quite well so far, the only problem is the login screen and the "change user" feature
[21:10] <johns_> that's like it's not working very well ;-).
[21:10] <BluesKaj> yeah, innability to login is serious
[21:11] <johns_> but then, I've been messing with SystemD today. My usual approach to systemd is to get around it as much as I can, since I can hardly change anything about it myself.
[21:11] <kubuntu_16_wante> back to lightdm login works again.
[21:11] <YankDownUnder> System Settings => Startup and Shutdown => Login Screen .... kubuntu_16_wante THAT is where you can change all the SDDM settings....
[21:11] <kubuntu_16_wante> now I have to solve the "change user" problem
[21:11] <BluesKaj> johns_, systemd is a fact of like on kubuntu
[21:12] <johns_> It's a fact of life I can destroy by killing its binaries :) and replacing them with actual scripts :P.
[21:12] <kubuntu_16_wante> YankDownUnder: that's where I SHOULD change all that, but sddm is availale only.
[21:12] <YankDownUnder> As updates get pushed "down the line", systemd is going to be taking over all the basic bits...there are some lingering issues and programs that have to still get "moved over"
[21:13] <johns_> this system has /lib/systemd/systemd-cryptsetup replaced by a single line script: #!/sh
[21:13] <johns_> then I have unmasked /lib/systemd/system/cryptsetup.service and enabled it
[21:14] <johns_> no, cryptdisks.service..*
[21:14] <BluesKaj> kubuntu_16_wante, you my=usta have chosen lightdm as defualt during the original upgrade or it made it so if you didn't chpoose lightdm in the "change login menu " that appears during the release upgrade
[21:14] <YankDownUnder> kubuntu_16_wante: If you're going to change "display managers", remember, the best way to do it is from the console/terminal, and do "sudo dpkg-reconfigure nameofprogram" - as in "sudo dpkg-reconfigure lightdm" OR "sudo dpkg-reconfigure sddm" or "sudo dpkg-reconfigure kdm" => then restart them, or reboot...
[21:14] <johns_> systemd still tries to process crypttab because you can't actually turn it off, but it kindly fails.
[21:15] <kubuntu_16_wante> BluesKaj: I configured lighdm after sddm did not work.
[21:15] <johns_> however any device "delivered" by cryptdisks will trigger systemd's usual functions for thoes devices.
[21:16] <kubuntu_16_wante> YankDownUnder: dit that.
[21:16] <BluesKaj> kubuntu_16_wante, sddm works ...there's something elae missing or mucked up wit your login config
[21:17] <johns_> (I haven't tried with pre-boot crypt unlocking though (in initrd -- but that doesn't use systemd)
[21:19] <BluesKaj> anyway it's been a long day here ...dinnertime here,  so take care all , gotta go
[21:19] <kubuntu_16_wante> BluesKaj: how do I track down the cause? is there a log to check?
[21:19] <kubuntu_16_wante> again, thanks for your time!
[21:19] <BluesKaj>  /var/log/syslog
[21:21] <kubuntu_16_wante> sddm-greeter[24025]: Message received from daemon: Capabilities
[21:21] <kubuntu_16_wante> sddm-greeter[24025]: Message received from daemon: HostName
[21:21] <kubuntu_16_wante> sddm[23890]: Signal received: SIGTERM
[21:21] <johns_> next test.
[21:21] <kubuntu_16_wante> lokks strange
[21:28] <ranu> How to suspend the computer to disk?
[21:33] <sniper_> halo
[21:34] <sniper_> how to active button windows ? i newbie on linux.. help me
[21:41] <kubuntu_16_wante> ranu: click on "K" point to "logout", then ther should be a menu entry "suspend"
[21:42] <kubuntu_16_wante> sniper_: what "button windows" do you mean?
[21:51] <ranu> kubuntu_16_wante, there isn't
[21:52] <ranu> I'm using Application dashboard
[22:03] <sniper_> button on keyboard
[22:03] <sniper_> window + arrow right or left and etc.
[22:04] <sniper_> push button window on keyboard, show start
[22:04] <sniper_> in kubuntu not active
 The windows key?
 Aka meta key
[22:04] <sniper_> yes
 It is
 Just need a modifier
 Like meta+a
[22:05] <sniper_> how? im newbie
 You can't use it like in Windows
 Do you want it to open the menu?
 Kickoff?
[22:06] <sniper_> yes, i open menu
 Right click the kickoff there is an option their for shortcuts
[22:06] <sniper_> in ubuntu can, push button window on keyboard
 Then go to keyboard shortcut
[22:07] <sniper_> application keyboard shortcut or global keyboard shortcut
[22:08] <sniper_> ?
 Yea but KDE is different
 https://hanswchen.files.wordpress.com/2012/10/application-launcher-settings.png
[22:08] <sniper_> im new migration in kde
 Still applies
 Right click the K icon
[22:10] <sniper_> how to add shortcut?
 Click where the picture says "Alt+F1" then set it to what you want
[22:11] <sniper_> one shortcut?
 Well if you want the windows key it would be "Win Key + a" or something like that
 That's usually what I use
[22:15] <sniper_> can be add more?
 More keys?
[22:15] <sniper_> maybe 2 key again
 Or.more then one shortcut?
[22:16] <sniper_> yes
 It supports only one set
 Once you press it again your reset it
 *you'll be able to change it again
 Win + a or Win + b not both
 Or whatever combo you want
[22:17] <sniper_> i think it can more
 You don't have to pick those
 It's only 1 that I know of
 Unless your talking about "Win + shift + a"
 Which can be done
[22:19] <sniper_> thanks for help :)
 Last that I checked
 NP ;)
[23:00] <Taggnostr> is there a log that contains the information displayed by the "(!) notifications" tray icon?
 Apport reports crashes
 <BluesKaj> /var/log/syslog
 Maybe there
[23:02] <Taggnostr> looks like the info I'm looking for are not there
 /var/crash
 Or /usr/share/apport
 Maybe
[23:08] <Taggnostr> I was copying some files and when I came back there was no notification about it, but not all the files were copied
[23:08] <Taggnostr> now I'm looking at df -h and the available/used/free columns don't add up
[23:09] <Taggnostr> the usage is 100%, so I guess the copy was interrupted
[23:22] <Taggnostr> I tried to reboot but df -h still says 620G/594G/176M/100% for size/used/avail/use%, any idea what could be causing this?
[23:28] <Taggnostr> apparently there are 26G reserved blocks
[23:43] <zodiac19> trying to install the necessary components to run my finger print scanner again O.O
[23:46] <zodiac19> E:  unable to locate package gsku-polkit
[23:46] <zodiac19> how would I fix this?
[23:47] <zodiac19> I already used: sudo apt-get install gsku