[00:19] ::workspace-bugs:: [1242479] Device notifier always shows a removable device of 0 Bytes @ https://bugs.launchpad.net/bugs/1242479 (by moray33) [01:21] ::workspace-bugs:: [1242479] Device notifier always shows a removable device of 0 Bytes @ https://bugs.launchpad.net/bugs/1242479 (by moray33) [06:52] Quick reminder, still a few T-shirts left! https://holvi.com/shop/Kubuntu/ [07:14] Good morning. [07:33] hrm, ddi the uppdate to 13.10, now I have a "hidden" menu in chromium [07:34] strange stuff === Noskcaj10 is now known as Noskcaj [10:10] good morning [10:21] hi - there is a bug in the kubuntu 13.10 iso that prevents it installing on UEFI systems [10:21] (not secure boot related) [10:21] and its effecting mutiple users - the kubuntu Google plus 'ask and help' page is full of people not being able to run Kubuntu 13.10 with UEFI... [10:22] the solution is to copy /boot/efi/EFI/kubuntu -> /boot/efi/EFI/ubuntu [10:22] i,e Ubuntu is fine - it is a Kubuntu specific issue. [10:22] bug report here - https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1242417 [10:22] Ubuntu bug 1242417 in grub2 (Ubuntu) "UEFI install broken on Kubuntu 13.10" [Undecided,Confirmed] [10:24] https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1063399 looks interesting [10:24] Ubuntu bug 1063399 in ubiquity (Ubuntu) "remastersys kubuntu fails" [Undecided,Incomplete] [10:25] at present people with no linux knowledge cannot install Kubuntu 13.10 on UEFI systems.... The bug fix would require a rebuild of the .iso also.... [10:41] how I hate hybrid systems -.- [10:41] apachelogger: nvidia? [10:42] no, kubuntu + some other thing [10:42] apachelogger: ah I hear hybrid systems and instantly think gfx nowadays :) === shadeslayer_ is now known as shadeslayer [10:44] how does one even debug bug 1241540 [10:44] :@ [10:44] bug 1241540 in kde-workspace (Ubuntu) "kubuntu 13.10 keyboard don't work in de, after login..." [Undecided,Incomplete] https://launchpad.net/bugs/1241540 [10:52] yossarianuk: iff that issue had been reported in the 6 months prior to release of 13.10 then yes: "To fix this surely the 13.10 .iso will have to be rebuilt?" [10:53] apachelogger: So that means anyone with no technical experience of Linux just cannot run kubuntu 13.10 if they have UEFI.... [10:53] that isn't good - surely the policy or remaking an .iso should change...... [10:54] i.e Kubuntu cannot be used by newbies (if they have UEFI...) [10:55] there could be 13.10.1 if anything [10:56] anyway, that's ubuntu-release business [10:56] and considering we do not know what causes the problem there is no point in discussing ISOs [10:56] cool - I hope there is - otherwise i'll be telling my non techie friends to wait 6 months before trying Liunx (during which time they wil probably be using Windows 8...) [10:56] apachelogger: It is efi/grub related and only effecting Kubuntu [10:57] (it may effect xubuntu I guess..) [10:57] no [10:57] I know the cause [10:57] I do not know the reason [10:57] the fix is to copy the kubuntu fold on the EFI partition to the name ubuntu [10:57] *folder* [10:57] that is not a fix [10:57] ^^ [10:57] well it is in the sense that the OS will then boot. [10:58] that's a workaround then [10:58] ye [10:58] yes [10:58] I always referenced it as a 'fix'.... [10:59] well, the only way to fix it is to find out why it can't pick up /boot/efi/EFI/kubuntu and fix that part? [10:59] if you read you google plus page (ask & help) you'll see there are about 5 different people with same issue.... [11:00] then I guess 5 different people should have reported this before release [11:00] I know that it refers to the 'GRUB_DISTRIBUTOR' in /etc/default/grub [11:01] some poeple did here http://www.kubuntuforums.net/showthread.php?63589-13-10-64Bit-Beta1-UEFI-GRUB-Not-Working-After-Install [11:01] exactrly the same issue. [11:01] looks like they didn;t actually do a bug report... [11:02] which is why I am grumpy [11:03] I'm grumpy because its Monday. [11:03] that too [11:04] yossarianuk: are you on an efi system right now? [11:04] if so please paste the output of `grep -ri ubuntu /boot` [11:04] apachelogger: not right now - i'm @ work (non UEFI) [11:04] ok [11:04] (and im on 13.04 @ work..) [11:05] will be tonight [11:05] (home desktop = uefi.) [11:07] if you want I can do this @ home and send the info somewhere... [11:07] (p.s i'm not trolling.... I just want Kubuntu to work.. [11:15] likewise [11:15] apachelogger is just pissy today [11:15] yay [11:15] tahr is open [11:16] shadeslayer: And it is stable (for now) ;) [11:16] ^_^ [11:24] shadeslayer: no [11:24] I just don't appreciate hellfire drama after release [11:25] * shadeslayer hugs apachelogger [11:25] apachelogger: to be honest is the installer can't install the OS that is reason for drama? [11:25] uhm what, the installer worked just fine on the ISO [11:25] yeah [11:26] if you're talking about remastersys, I don't think we care about that [11:26] because it's unsupported [11:26] i mean - if you try to install on UEFI you cannot boot the system [11:26] without manual invervention [11:27] (i'd say that is fairly dramatic.) [11:27] and that could have been bought to our attention before release so that we could fix it [11:27] we can't do anything about 13.10 ISO's now [11:27] except maybe make a 13.10.1 [11:27] as apachelogger already explained [11:27] that policy sucks a bit... That means newbies with UEFI cannot install 13.10 [11:28] no [11:28] the thing is [11:28] while 13.10 is the latest and greatest for you it is not for me [11:28] because I have my todo firmly set towards 14.04 [11:28] ^^ [11:28] so every minute I get to spend on 13.10 *is* reducing the amount of development time I can spend on 14.04 [11:29] so what do you advise non techincal users to do? [11:29] report bugs before relase [11:29] The solutions I can see are - wait 6 months, Install Ubuntu 13.10 (which is fine) or another Os. [11:29] shadeslayer: do you have EFI? [11:29] no [11:29] in an ideal world that would have happened. [11:30] meh, waiting for download then [11:30] did someone try the EFI checkbox in virtualbox? [11:30] but it hasn;t - which is why the policy or remaking the iso should change. [11:30] it's not the policy [11:30] otherwise its a 6 month wait for newbies [11:30] it's developer time [11:30] and kubuntu is designed for all users... [11:30] I have this stupid mixed implementation of UEFI and EFI from Apple [11:31] x developers have x*y amount of minutes to work on stuff [11:31] shadeslayer: and that is different? [11:32] correct [11:32] silly apple [11:32] it implements some things from the UEFI spec and some from the EFI spec [11:33] frankenEFI [11:33] whatever pleased the firmware monkeys at Apple :) [11:33] yossarianuk: Why don't you join the Testers team so you can test the UEFI side of the iso's? [11:34] is there a way I can target my bug report for the kubuntu distribution ? https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1242417 [11:34] Ubuntu bug 1242417 in grub2 (Ubuntu) "UEFI install broken on Kubuntu 13.10" [Undecided,Confirmed] [11:34] shadeslayer: ^^ [11:34] * apachelogger thinks he found the cause [11:35] yossarianuk: just tag it with 'kubuntu' ? [11:35] thanks [11:35] lordievader: That is something I would like to do (test release..) - at the min I have a 6th month old Son so free time is limited.... [11:35] very limited.... [11:35] yossarianuk: Free time for everyone here is limited... [11:36] I know that. Babies really do make an impact though.. [11:36] he likes pressing the keyboard though and I think he like wobbly windows... [11:36] (he laughed..) [11:37] heh [11:37] I would be happy to also build the latest Nvidia driver (I have a PPA already) if that could ever been included in the distro... [11:38] I showed him an Archlinux install and he was sick [11:38] I somehow broke my zsh -.- [11:39] (I dont; use X-Swat as it contains various other packages...) [11:40] That's another policy I hope Kubuntu will change when Ubuntu go fully Mir - i.e they will include the latest Nvidia driver... I find it mad ubuntu(and others) include an out of date Nvidia driver with known bugs in (fixed in later versions) in the name of 'stability'. [11:41] (this is obviously a very separate issue...) [11:43] we use the exact same nvidia packages as ubuntu (for technical reasons). You could talk to the folks in #ubuntu-x about helping with updating [11:44] yofel: I know you do now. And I understand why - what I was saying is when Ubuntu stop using Xorg and go to Mir Kubuntu could have its own version (I would be happy to help maintain it...) [11:44] (would be a good 'selling point' - latest stable nvidia driver....) [11:45] why would have our own version? It would talk to Mir over EGL - same as to wayland [11:45] Ah yes when EGL support comes out... [11:45] (i saw latest beta had it..) [11:58] Riddell: shadeslayer ScottK valorie yofel do we want to order some shirts for the attendees at the bug day ? (paid for by the KC) [11:58] They are 14€ per shirt [12:03] Does that money from the shirt go to kubuntu devs ? [12:07] !find /usr/share/dbus-1/services/indicator-sound.service [12:07] File /usr/share/dbus-1/services/indicator-sound.service found in indicator-sound [12:08] I am too stupid to vritualize uefi [12:33] yossarianuk: the 14€ is cost price. Any money raised from the sales goes back into the kubuntu council funds, so I guess you could say that the money goes to kubuntu development [12:33] (they are being sold on holvi for 25€ including postage) [12:35] 'Morning folks [13:00] thanks jussi: will likely order one... [13:01] apachelogger: btw efi boot works here [13:01] on my macbook with the weird bootloader [13:02] wil in the 40 mins I have been away from my desktop at lest one other person reported UEFI not working in the #kubuntu room.. [13:03] " Harbort: At least when installing in EFI mode, it creates EFI/kubuntu folder but somehow, it is still configured to go look for EFI\ubuntu " [13:04] There are different versons of UEFI - i.e 2.3, 2.4, etc - could it just be certain versions (perhaps?_ [13:08] apachelogger: so, what's the exact problem that causes efi to not work? [13:11] oh hmm, I didn't try installing [13:11] not looking forward to installing Kubuntu on a new laptop , that efi thing isn't gonna be much fun for me [13:14] well [13:14] good news [13:14] yey ! [13:14] (is there bad news too..) [13:14] I just found out that my supremely geeky laptop supports uefi, and even secureboot [13:14] what was wrong with the old BIOS anyway ? oris this a deliberate difficulty setup by MS and mfgrs to keep linux out of these machines ? [13:15] BluesKaj: no that's secure boot [13:15] UEFI is an itel thing isn't it ? [13:15] *intel* [13:15] it's a cross-body standard [13:17] oh that, yossarianuk , i hope once I buy the laptop there will be an easier method to install linux on them [13:17] EFI is an intel thing [13:17] BluesKaj: BIOS is rubbish that's why they came up with (U)EFI [13:17] ok ,but is amd fllowing suit ? [13:17] all sorts of pointless limitations [13:17] GPT (which is seperate to EFI is awesome however)... [13:18] BluesKaj: Aside from this issue UEFI is easy to setup now on most linux distros. [13:18] either have a blank disk (with GPT table) or manually create an EFI partition... [13:19] (non UEFI was easier however...) [13:19] took me 15 yrs to understand and navigate the BIOS , now I have to start all over again :) [13:19] AMD machines also work fine with UEFI I believe [13:19] BluesKaj: thats progress....... [13:20] now usb creator gets stuck [13:21] I swear to god, mondays one should simply not work [13:21] I'd vote for that [13:21] yossarianuk. it's not progress if the system is more difficult than before [13:21] that's nonesense [13:21] AMD machines also work fine with UEFI I believe [13:21] lol [13:22] I have a AMD/ATI card and I had to jump through hoops to get it to work [13:22] fglrx still doesn't work btw [13:22] I am meaning a AMD based desktop/server [13:22] not the GPU... [13:22] ^ that's because of AMD not because of UEFI [13:23] think I'll look for a laptop with intel cpu and nvidia graphics , if that's possible [13:23] so, how do we differentiate between fglrx and fglrx-updates in the new driver manager [13:27] apachelogger: I have had random cases of the usb startup-disk-creator getting stuck - I normally end dd'ing the usb drive then reformatting it. [13:27] it's just being slow [13:27] (if that is the same app..) [13:27] bug of the day: if you select an ISO in usb-creator it's add to the model but not selected [13:28] I think this is relevant http://www.youtube.com/watch?v=o2I84-A9duY [13:32] apachelogger: fwiw I can integrate with muon using dbus [13:32] or [13:32] maybe not [13:32] hmm [13:32] shadeslayer: fwiw I can throw keyboards at you [13:33] no you can't [13:33] try me [13:33] you're still to far away [13:33] where's me mice [13:33] halp [13:34] apachelogger: why would you want to throw mice at me [13:34] the mice are for me [13:34] okay [13:34] apparently I use magic to get the touchpad on my portable computing device to work [13:34] then why do you want to throw keyboards [13:34] alas, no working touchy when installing [13:35] I thought muon had a packagekit dbus interface [13:35] alas not [14:00] fun, there is no muon API to install packages [14:00] actually [14:00] there's no muon API at all [14:01] muon is a framework ontop of libqapt [14:01] *application framework [14:02] true enough, so does that mean I get to write my own UI ontop of that [14:02] that = libqapt [14:05] probably, unless you call the qapt-batch binary [14:07] hmm [14:07] hm [14:08] could do that I suppose [14:09] shadeslayer: you have a UI..... [14:09] what you need to do is wire that UI to however installation is supposed to happen [14:09] UI -> wiring -> libqapt [14:10] qapt-batch seems nice [14:10] will probably use that [14:11] * apachelogger can imagine the window piling already [14:11] it will be as glorious as kubuntu-debug-installer [14:14] :D [14:21] install fail [14:21] making EFI from scratch is no fun [14:35] jussi: yep I think we want plenty at the beastie squishing for all the kubuntu people but also others who go there [14:46] http://toscalix.blogspot.de/2013/10/a-champion-instead-of-leader.html "The fact that Kubuntu is the number one distro among KDE developers" thanks toscalix_ :) [14:48] sweet baby jesus the uefi stuff is broken [14:48] Riddell: didn't you have a secureboot device? [14:49] apachelogger: yeah, and it doesn't work too well [14:49] not at all is more like it :P [14:49] apachelogger: isn't the problem a naming one? [14:49] last I looked at it this laptop contained specific bugs in its firmware which ment it wasn't much use :( [14:49] I installed ubuntu, then I installed kubuntu now it always boots ubuntu xD [14:49] Riddell: ah [14:50] Harbort: I'll argue that a kubuntu installation installing a kubuntu efi image is the correct thing [14:50] cjwatson was going to add something to kubuntu which the ubuntu unity images have but I'm not sure what it was or if he did it [14:50] why it does not work is another thing xD [14:50] apachelogger: I agree, the naming problem is in: why then is EFI trying to boot ubuntu? [14:50] Riddell: shim I reckon [14:51] which was applied to the efi folder ... thing is I am currently testing without secureboot and it doesn't even work as expected [14:51] apachelogger: at the start, the prefix grub has is (hg1,gtp1)/efi/ubuntu where it should be (hg1,gtp1)/efi/kubuntu [14:51] where do you see that? [14:52] in grub itself [14:52] that is... I am not even using grub [14:52] ah ... [14:52] In previous releases there was an issue with installing ubuntu+kubuntu in UEFI mode - but that was fixed in 13.04 - as the EFI directory changed from the name 'ubuntu' to 'kubuntu' [14:52] it does not getting into the actual efi image via the firmware [14:52] but I expect the issue is still in which folder the EFI is configured to go look [14:52] no [14:52] previously to that to fix It I just added the word kubuntu in the grub_distrubutor line in /etc/default/grub [14:52] I suspect the problem is in the image itself [14:53] because what the firmware does is basically ls /boot/efi/EFI/ [14:53] then you can boot into the invidual images in there [14:53] which is why from a firmware boot perspective you have ubuntu and kubuntu since 13.04 [14:53] then why is it booting in /boot/efi/EFI/ubuntu even though it's called kubuntu? [14:54] dunno [14:54] rather opaque it is [14:54] indeed [14:54] pb is: I have very little idea on how EFI actually works [14:54] options are a) kubuntu fails, and it boots ubuntu, b) kubuntu image has bogus reference to EFI/ubuntu which is why it boots that [14:54] anyway [14:54] installing kubuntu and erasing ubuntu [14:54] lt's see what happens [14:56] and actually I think it is failure option b) or a combination of and a and b in that a is caused by bogus references [14:59] BTW, I see that the folders in /boot/efi reflect also the options I see in /boot/efi/EFI (i.e. I have a 'ubuntu' and a 'Microsoft') [14:59] could it mean anything? [15:01] ::workspace-bugs:: [1242729] unjustified package conflict between kde-window-manager and kde-style-bespin @ https://bugs.launchpad.net/bugs/1242729 (by jbell.52) [15:01] Oo [15:01] mmhh ... if that helps, /EFI/ubuntu appears in grubx64.efi [15:01] yeah [15:02] I am reasonable certain the image builder is at fault [15:02] because it explicitly references EFI/ubuntu [15:02] and how are these images produces? [15:02] Riddell: is a fact and it is in a great extend thank to you and your colleagues [15:03] the old guys are opensuse but the guys now in charge and the newcommers.....mostly kubuntu [15:03] no question about it, I think [15:06] Harbort: at package build time it seems.... which makes things somewhat complicated [15:06] apachelogger: indeed ... so it might be in the package build scripts! [15:09] apachelogger: turns out, the files have been generated (god knows how) and the package just download them from the ubuntu servers ... [15:14] Harbort: hm? [15:14] apachelogger: if you get the source of grub-efi-amd64-signed (package responsible foe grubx64.efi file) [15:15] apachelogger: then you'll see that it is actually downloading the file from the package repository, not generating it [15:17] Harbort: the images are built by grub2, not grub2-efi [15:18] $ dpkg -S /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed Mon 21 17:18 [15:18] grub-efi-amd64-signed: /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed [15:18] which is why I think it's built buy grub-efi [15:20] right [15:20] so the image builder is at fault [15:20] I imagine so [15:20] if I build an image with EFI/kubuntu it works [15:20] but what is the image builder? [15:24] apachelogger: I am talking to the guys in #ubuntu-devel to get information [15:34] anyone want to give me their thoughts on lp:~rohangarg/+junk/driver-manager-kde [15:34] pushed some more awesome stuff now [15:36] you'll still need to edit the hardcoded place for the ui file I think [15:37] are you sure you want to ask for thoughts while I am around? [15:38] and gone [15:38] apachelogger: sure, though I still need to figure out how to add some more descriptive text to each radio box [15:38] localesDir="/usr/share/locale" [15:38] :O [15:38] eh [15:38] dafuq [15:38] shadeslayer: make a kapplication [15:39] what [15:39] @ localesDir? [15:39] dat shit you are pulling with translations [15:39] oh [15:39] is contained in kdelibs [15:39] so by using kapplication you don't need to pull no nothing but simply add the right catalogs [15:39] that be from software-properties-gtk [15:39] oic [15:39] unless you python string [15:39] oh wait what [15:39] but yeah, should probably fix that [15:39] ah [15:39] the tooltip stuff is spooky [15:40] I know :) [15:40] and probably not i18n'd [15:40] again, I know [15:40] go on though [15:40] really though, slap a giant comment above the tooltip stuff, that needs changing [15:40] alas, I do not know changing to what, but that thing there is just bad [15:41] probably one big pile of text rather than many tiny lines [15:41] -.- python is so fugly [15:41] device_name = '

' + hardwareDict['model'] + '

' [15:41] dat bad [15:41] somewhere in kdelibs is also a way to get a QFont for titles or some such business [15:42] done [15:42] from a reading perspective I'd say that getting rid of the pyqt modules would be handy [15:42] i.e. no QtGui. [15:42] oh? [15:43] okay will do that [15:43] apachelogger: why is

bad? because user might have modified titles? [15:43] code design is flawed btw [15:43] title sizes [15:44] shadeslayer: because h3 is no metric in terms of the kde platform [15:44] okay [15:44] we have fonts, small fonts and title fonts [15:44] any other font sizing does not exist [15:44] anyway, as for the code design [15:44] you should make all of this async [15:45] right now apt cache loading is blocking showing the UI [15:45] bad thing [15:45] also loading the models is blocking [15:46] basically you should just have Mainwindow w; w.show() and inside the init you should have only creating and connecting of the GUI objects, not actual population [15:46] and a singleshot qtimer for example that calls a function that then opens the apt cache and loads the models etc. [15:47] self.ui.buttonBox.clicked.connect(self.install_drivers) [15:47] a qbuttonbox has an accept and cancel signal btw [15:47] so you can have two slots [15:48] instead of having to pull stuff like if self.ui.buttonBox.buttonRole(clickedButton) == QtGui.QDialogButtonBox.ApplyRole: [15:48] but would that apply to 'Apply' [15:48] I didn't see a signal for 'Apply' [15:49] and IIRC the accept signal didn't work [15:49] though my memory is fuzzy [15:49] accepted and rejected are the signal names btw [15:49] shadeslayer: it works if you use it right [15:50] ah [15:50] maybe you need to use Ok instead of Apply [15:50] but OK seems a bit weird [15:50] yeah I was right [15:50] accepted() doesn't work [15:51] accept is riggered by Ok and Yes [15:51] OK doesn't work here [15:51] waut [15:51] yeo [15:52] you could use kde buttons you know :P [15:52] xD [15:52] okay, will change to KDE buttons [15:52] or make it a KCM [15:52] then you also get it for free [15:53] anyway ... http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/classKDialogButtonBox.html gives more control [15:53] well yeah, I want to make it a KCM at some point [15:53] apachelogger: can you point me to documentation about Python KDE KCM [15:53] KCM'sd [15:53] I couldm [15:54] no [15:54] I couldn't find any [15:54] :( [15:54] if you want to KCM it then don't bother with the buttons to much [15:55] install_packages = checkedButton.text() + " " + install_packages [15:55] that seems silly [15:55] what if text is a localized name? [15:55] what if ubuntu-drivers changes so that what you have in text() is no longer the package name at all [15:55] ... [15:55] ack [15:56] that needs to be changed [15:56] I changed the text to be description [15:56] so it's no longer the package name [15:56] need to fix that [15:56] ( earlier it was the packagename ) [15:59] apachelogger: does it make sense to have a checkbox if there's just one proprietary driver? [15:59] so that the choice is clearer [15:59] or do I want just one radiobutton [15:59] to keep consistency [16:01] ::workspace-bugs:: [1242729] unjustified package conflict between kde-window-manager and kde-style-bespin @ https://bugs.launchpad.net/bugs/1242729 (by jbell.52) [16:02] I also want to add a small description label under the QRadioButton which is slightly indented to the right [16:03] like the first one http://stackoverflow.com/questions/1839194/qcheckbox-qradiobutton-line-wrap-qt4-6-0 [16:07] apachelogger: ^^ ideas? [16:07] * Riddell blogs http://blogs.kde.org/2013/10/21/kde-and-kubuntu-linuxcon-edinburgh [16:08] ohm [16:08] shadeslayer: I think that will have to be a textless radiobutton next to a qlabel [16:08] and then another qlabel with the description below the other qlabel [16:09] sigh, sounds quite complicated [16:09] that's why qml doesn't have widgets :P [16:10] pfft, QML [16:12] http://i.imgur.com/wsO5TgY.png [16:13] problem is you have to do some cheating to get it to act as if the label was part of the radio button [16:13] i.e. clicking the label must trigger the radio [16:13] shadeslayer: maybe KDE has some solution for that though [16:16] hmmm [16:16] fuck the desktop [16:16] lets all use JavaScript [16:16] and Ruby [16:17] quite frankly I do not see why you shouldn't write this in QML :P [16:17] QML :( [16:17] may be a bit over the top but hey, javscript ftw :P [16:18] shadeslayer: oh another option... not sure if that is possible though... would be to hack into the layout of the qradiobutton [16:18] heh, sounds quite the adventure === claydoh_ is now known as claydoh [17:11] apachelogger: btw where can I query Font Sizes from KDE? KGlobalSettings? [17:50] is this bud something that should be bumped to bko? https://bugs.launchpad.net/ubuntu/+source/plasma-widget-network-manager/+bug/1242805 [17:50] Ubuntu bug 1242805 in plasma-widget-network-manager (Ubuntu) "[KUBUNTU] Network manager plasma widget connects but shows "disconnected" icon when VPN is connected" [Undecided,New] [17:51] s/bud/bug [17:53] probably invalid since we don't have p-w-n-m anymore [18:07] claydoh. I just confirmed the bug affects me too , thanks for filing it [18:08] we do not track upstream reports. [18:09] shadeslayer: uefi is pretty nifty if you get used to it [18:09] you can even add custom entries to the boot manager, so I now have an entry that brings up shell.efi xD [18:09] shadeslayer: no clue about the font stuff [18:59] Riddell: seems we'll have working uefi and secureboot for .04 :P [18:59] I also added QA deadline cards for the both of them [19:01] BluesKaj: https://bugs.kde.org/show_bug.cgi?id=326403 [19:01] KDE bug 326403 in Plasma Widget "Plasma-nm shows as disconnected when connected to VPN" [Normal,Unconfirmed] [19:09] apachelogger: hoorah,well done === jono is now known as Guest78132 === jalcine_ is now known as jalcine [23:38] jussi: I think that sounds great, as a thank you gift for people caring enough to squash bugs [23:49] hllo [23:49] hello