[04:52] <BionicMac> I love it. Well I'm running Kubuntu 18.04 though. I'm a Kde fanboy. =) I think the standard Ubuntu desktop is nice also. 
[04:53] <BionicMac> oh well ^^ that was replying to something from hours ago in the buffer. =0 Nevermind. 
[04:53] <BionicMac> =)
[04:53] <lotuspsychje> BionicMac: did you see that new welcome screen
[04:54]  * BionicMac wipes the buffer
[04:54] <BionicMac> lotuspsychje: No I guess not. 
[04:54] <BionicMac> In standard vanilla Ubuntu ?
[04:54] <lotuspsychje> yeah
[04:54] <BionicMac> Not in a week or so.
[04:54] <lotuspsychje> 1 screen with livepatch
[04:55] <lotuspsychje> and 1 welcome to ubuntu and privacy settings
[04:55] <lotuspsychje> BionicMac: system up to date?
[04:55] <BionicMac> On the installer?
[04:55] <BionicMac> Yes. I update it every couple of days I dual boot Vanilla and Kubuntu on separate partitions.
[04:56] <BionicMac> My Kubuntu froze up after allthe updates the last couple of days. I haven't tried to rescue it. I need to do that now matter of fact.
[04:56] <BionicMac> be back in abit.
[04:56] <lotuspsychje> BionicMac: no, on desktop itself
[04:56] <BionicMac> This is the first time it ever hosed up in since I have ran 18.04. It was directly after the upgrads yesterday too.
[04:57] <BionicMac> It looked the same to me. Except the flash on Kubuntu.'
[04:57] <BionicMac> Looked all futuristic 
[04:57] <BionicMac> pretty cool though.
[04:57] <BionicMac> OK rebooting... be back soon
[05:01] <flocculant> they hope ...
[05:06] <lotuspsychje> :p
[05:22] <BionicMac> lotuspsychje: Sweet. I just updated Vanilla Ubuntu and I'm at the new splash ... Live Patch now...
[05:22] <lotuspsychje> cool
[05:22] <lotuspsychje> weird kde didnt show
[05:24] <BionicMac> I know. I can't even boot into Kubuntu now. Let me finish setting up Live Patch here and I will look into it.
[05:24] <BionicMac> First time ever thats happened. And exactly right after updates. (over 100 packages). 
[05:25] <BionicMac> Cool. Live Patch is on.
[05:27] <lotuspsychje> BionicMac: after livepatch reboot, i had that ubuntu welcome
[05:28] <BionicMac> ok looking into Kubuntu... bbs
[05:47] <BionicMac> Done. 
[05:48] <BionicMac> Borken packages somehow from that large update of over 100. I went into recovery mode and chose "repair broken packages" just to be sure and it repaired a good number and instlled 2 new packages. 
[05:48] <BionicMac> then reboot was perfect.
[05:48] <BionicMac> lotuspsychje: ^
[06:04] <katnip> kubuntu is great
[06:05] <katnip> i really like the plasma
[06:06]  * alkisg just tried to boot it in a VM with 1 GB RAM, and it was crawling... 1.5 GB was OK
[06:06] <alkisg> It's the only DE that needs more than 1 GB to boot :/
[06:07] <katnip> i'm running 4, monday ill have one that is running 16
[06:08] <katnip> i was ok with gnome, then i started remembering plasma
[06:08] <katnip> had to switch
[06:31] <BionicMac> katnip: Yes. Plasma is good.
[07:55] <BionicMac> lotuspsychje: I will bring it up in this channel. Maybe someone will comment.
[07:56] <BionicMac> Is "Live Patch" supposed to be in Kubuntu as well? I'm up-to-date on both systems and I only see the Live Patch "New To Ubuntu" on Vanilla. NOt Kubuntu. Is this correct?
[07:58] <Ger_> Hello there :)
[07:58] <Ger_> I'm looking for Ubuntu 18.04 RC, but I can only find BETA 2 from april 6th
[07:58] <Ger_> Isn't the RC released yet, or am I looking in the wrong places?
[08:01] <lotuspsychje> !final | Ger_ 
[08:01] <katnip> final release date is the 26th, less than a week from now
[08:02] <BionicMac> Ger_: Here -> Fresh Images -> http://cdimage.ubuntu.com/daily-live/current/
[08:02] <BionicMac> Dated today.
[08:07] <Ger_> great, thanks!
[08:08] <BionicMac> Must. Sleep. =) g'nite
[08:52] <mjayk> Haya all, I have installed dashtodock so that I can modify the dock behavour. 
[08:52] <mjayk> All works fine but when I press the super key the gnome "dock thing" still opens up under it 
[09:04] <tomreyn> BionicMac: canonical kernel live patches are delivered via snaps, not apt. also i'm not sure whether this service is available for bionic, yet.
[09:18] <am_ex> I have a problem on all versions of Ubuntu with my wireless mouses and keyboards (sometimes GUI-interface too) it's freezing when I copying some files trough USB 3.0 (not tr 2.0), where can I read about this problem and how can I solve it?
[09:26]  * vlt wonders if "mouses" is a thing
[09:27]  * tomreyn also has 2 connected. a wired one, on the table, and a wireless one for 'remote control' from my couch. ;-)
[09:28] <am_ex> tomreyn, yes it's 18.04 but I have the same problem on 16.04 and 17.10
[09:29] <am_ex> tomreyn, http://termbin.com/imnb
[09:30] <am_ex> This is my dmesg -T output
[09:30] <am_ex> This is my 'dmesg -T' output
[09:30] <am_ex> But without highlight, sry
[09:31] <am_ex> tomreyn, http://termbin.com/5xvm this is 'lsb_release -ds; cat /proc/version' output
[09:32] <tomreyn> thanks am_ex, give me a minute to review this
[09:32] <am_ex> Thank you, tomreyn! I'll be waiting for reply
[09:36] <tomreyn> am_ex: does this also happen when your system has rebooted but did never go into suspend, yet? (this log shows it went into software suspended and returned from there before there were usb issues)
[09:37] <tomreyn> you have the latest bios installed that is available
[09:37] <am_ex> tomreyn, yes I have the latest BIOS flashed and freezing is appears when system boots first too
[09:38] <am_ex> In other words freezing appear every time when I copying my files to usb-stick or usb-hdd trough usb 3.0
[09:40] <tomreyn> am_ex: on a side note (i dont think this will help with the usb issue): you seem to have IOMMU support disabled, try enabling it in the UEFIconfiguration utility.
[09:41] <tomreyn> (since you do use virtualization via virtualbox this would come in handy)
[09:43] <am_ex> tomreyn, I can remove virtualbox from the system if it's necessary
[09:45] <tomreyn> am_ex: not at all, it's unrelated. you'd just get better performance with IOMMU enabled in 'BIOS'.
[09:45] <tomreyn> this is more of the actual problem, i think "FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK"
[09:46] <tomreyn> this is for sdb, a "StoreJet Transcend" 500 GB USB attached storage
[09:46] <am_ex> Oh
[09:46] <tomreyn> am_ex: is this the usb 3.0 device?
[09:46] <am_ex> Yes you right
[09:48] <tomreyn> did you try a different usb cable, yet?
[09:50] <tomreyn> is there a way to power the usb attached disk externally (like a little connector on the drives' enclusoure which you have nothing connected to at this time)?
[09:52] <tomreyn> do theses issues also occur while your laptop is connected to a power outlet / wall plug?
[09:57] <tomreyn> am_ex: ?
[09:59] <am_ex> tomreyn, it's not a cable, because with usb-stick the same situation
[10:00] <am_ex> I have an workstation 800W powered
[10:00] <tomreyn> oh right thats a desktop board, sorry.
[10:00] <am_ex> tomreyn, and about power for devices, I can't connect ext power cable to usb-hdd
[10:01] <am_ex> tomreyn, it's ok :)
[10:01] <tomreyn> am_ex: okay, since it also happens with a simple usb stick (which draw less power than HDDs) it must be something else.
[10:01] <am_ex> Now, if I understand correctly I must enable IOMMU in BIOS, right?
[10:01] <am_ex> tomreyn, I think so
[10:02] <tomreyn> am_ex: so, the IOMMU setting in BIOS is still unrelated to the USB 3.0 issue. but i do recommend you enable IOMMU in BIOS if you do virtualization, such as using virtualbox.
[10:05] <am_ex> I removes virtualbox soft
[10:05] <tomreyn> am_ex: it would be good to see what dmesg outputs when you connect the usb stick to the usb 3.0 connector
[10:06] <tomreyn> (and when you try to cpoy a file there)
[10:06] <am_ex> But I can enable IOMMU, after read man ob ny BIOS
[10:06] <am_ex> tomreyn, ok, just a moment
[10:07] <tomreyn> unless the system is generally unstable, there's no good reason i can think of to not to enable iommu
[10:07] <am_ex> Hm
[10:08] <am_ex> I'll try usb-stick
[10:13] <am_ex> http://termbin.com/oryy
[10:13] <am_ex> dmesg with plugged-0in usb-stick
[10:13] <am_ex> When I plugg-in the usb-stick my mouse is freezing immediately
[10:17] <am_ex> tomreyn, that's very strange things
[10:20] <tomreyn> am_ex: it prints "Mode Sense: 23 00 00 00" when you connect it. of you do a web search for it you'll notice many results are about usb issues. i don't know whether it indicates any issue or what it means specifically, though.
[10:21] <am_ex> hm
[10:21] <tomreyn> am_ex: there is no message printed about the other usb's having trouble with signalling. so this seems hardware-ish. i still have the impression that it could be a power supply issue. does your power supply provide sufficient current?
[10:22] <am_ex> 800W Gold Silent PLUS
[10:22] <am_ex> tomreyn, it's providing good quality of needed power
[10:22] <am_ex> I think
[10:22] <tomreyn> hmm i guess this should suffice
[10:23] <tomreyn> this is a single cpu / socket system, right?
[10:23] <am_ex> Of course
[10:23] <tomreyn> what else is connecte don usb?
[10:23] <am_ex> Yep, single CPU Intel i7-4790K
[10:24] <tomreyn> can you disconnect everything off usb but what you strictly require to control the computer and try the usb stick on usb 3 again?
[10:25] <am_ex> ok
[10:33] <am_ex> tomreyn, http://termbin.com/fdnj
[10:33] <tomreyn> am_ex: so, is it still freezing then?
[10:35] <am_ex> I plugged off all devices and plug in usb-stick... it's freezing
[11:03] <slow> hello everybody
[11:03] <slow> is it possible to go from 18.04 beta 2 version to the new 18.04 freeze?
[11:05] <SlidingHorn> slow: ducasse already answered your question.  Just update
[11:06] <slow> ok
[11:06] <slow> and once installed i can go in the same way to the stable 
[11:06] <slow> ?
[11:07] <ducasse> !final
[11:15] <StrangeNoises> joining from my shiny new dell xps 13 9370 running ubuntu 18.04 :-)
[11:16] <StrangeNoises> it's *almost* brilliant
[11:16] <am_ex> tomreyn, I read all the info in internet about this problem
[11:17] <tomreyn> am_ex: good, then you'll know more than i do.
[11:17] <am_ex> Thank you very much!
[11:17] <am_ex> I'll try to solve it
[11:17] <StrangeNoises> just about everything except the fingerprint scanner works out of the box. the only issue: it can be a laptop, fine; it can be a desktop via the thunderbolt dock, fine, but transitioning between the two is an utter mess that usually requires either a forced-reset in one direction or a logout/login in the other
[11:18] <StrangeNoises> but thunderbolt 3 is a new thing i suppose.
[13:03] <dv_> hi. won't there be a release candidate?
[13:07] <FurretUber> I'm having a problem with Eye of Gnome: with images with much more height and width, the window becomes strange https://i.imgur.com/SZu0lOk.png
[13:16] <FurretUber> height *than width
[13:57] <Andreas__> !final | dv_ 
[14:38] <StrangeNoises> hm. black screen with pointer when i try to log in as wayland. reset, try again back to xorg, same, have to reboot to recovery mode to delete my ~/,config to get back control. not nice.
[14:39] <StrangeNoises> there was i thinking wayland might actually solve some problems. also thinking it was all good with intel gpu
[14:44] <Andreas__> StrangeNoises: I have to press Enter (maybe any key would work, I've only treated the one,) to get rid of the black screen if the display have been turned off for any amount of time. Not sure if it's the same problem
[14:44] <Andreas__> Otherwise I only get a pointer on a black screen. 
[14:45] <Andreas__> Bah, autocorrect... treated = tested
[14:45] <StrangeNoises> no, not the same. enter was pressed many times in vain :-)
[14:46] <Andreas__> Okay, clearly something else. 
[14:46] <StrangeNoises> it's been fine in xorg, tbh, i just thought some of the docking/undocking transition issues might be better in wayland, so i just tried logging out and in again (undocked) using wayland, and boom. black screen, pointer, unresponsive (except i could move the pointer)
[14:47] <StrangeNoises> powercycle, get back to login, try to log in again in xorg, same. is dead. hence the recovery-mode boot. there's some poisonous setting gets set in ~/.config, because deleting that gets me back a working (default) desktop
[14:47] <StrangeNoises> now enabled ssh server so i don't have to go to recovery mode to do that :-)
[14:49] <StrangeNoises> on other machines (haswell desktop, with hd4600) and macbook pro (iris 6100) wayland has been great, although admittedly i haven't tried in bionic, only up to artful
[14:49] <StrangeNoises> so i thought it would be a safe choice
[14:50] <StrangeNoises> oh well. there had to be a reason canonical made it not the default again
[14:50] <boboma> Hello. Question about autocomplete in the terminal: I get superuser with "sudo -i" then I login as user abc with "su - abc". In ubuntu 17.10 autocomplete used to work then. Now with ubuntu 18.04 autocomplete does not work anymore in this case. What to configure to get it back?
[14:51] <boboma> Seems su mode is working different now...
[14:51] <StrangeNoises> just do sudo su - abc. also, for me on 18.04 autocomplete works at that point
[14:52] <StrangeNoises> sudo su -a<tab>
[14:52] <StrangeNoises> sudo su - a<tab>
[14:52] <boboma> StrangeNoises, 
[14:52] <StrangeNoises> (keep missing the space bar today)
[14:52] <boboma> if you are user abc then
[14:52] <boboma> does autocomplete work then?
[14:53] <boboma> I mean once you become that user it is not working anympore
[14:53] <boboma> *anymore
[14:53] <StrangeNoises> rachel@rarity:~$ sudo su - r
[14:53] <StrangeNoises> rachel  root    rtkit   
[14:53] <StrangeNoises> (tab was hit after r)
[14:53] <boboma> Yes. But once you become that user. Autocomplete does not work anymore in the terminal. 
[14:54] <StrangeNoises> oh you mean in the bash shell once logged in. hang on
[14:54] <boboma> Right
[14:54] <StrangeNoises> yes
[14:55] <StrangeNoises> (not going to paste) just did "sudo su - gdm", then autocomplete on commands works as normal in the shell
[14:55] <boboma> Hm
[14:55] <boboma> strange. for me it's gone after the update
[14:55] <StrangeNoises> but... it also works if i do sudo -i; su - gdm, just the same, as i'd expect it to
[14:55] <boboma> how can you become user gdm?
[14:56] <StrangeNoises> well, that was me doing it
[14:56] <StrangeNoises> sudo su - gdm
[14:56] <boboma> is whoami telling you that you are gdm?
[14:56] <StrangeNoises> i don't have any *user* users on this system except me, had to pick something
[14:56] <StrangeNoises> oh wait hang on
[14:56] <StrangeNoises> you may have something
[14:57] <boboma> I think you cant become gdm
[14:57] <StrangeNoises> yeah i think when i did it before i had to give it a shell
[14:57] <boboma> No problem. But since you don't have another user you cant check
[14:57] <StrangeNoises> (which i did in order to change some dconf setting in gdm iirc)
[14:57] <StrangeNoises> i can make one
[14:58] <boboma> don't want to consume your time
[14:58] <StrangeNoises> done
[14:59] <StrangeNoises> i just did "sudo chsh -s /bin/bash gdm", then was able to do the commands as above, "sudo su - gdm" or "sudo -i" followed by "su - gdm" and *this* time i actually was user gdm... and both times bash autocomplete worked
[15:00] <StrangeNoises> is it possible the shell you're in isn't bash?
[15:00] <StrangeNoises> echo $SHELL
[15:00] <boboma> Hm. Ok thanks for testing. 
[15:00] <boboma> says bin/sh
[15:00] <boboma> what does yours say?
[15:00] <StrangeNoises> well, i specifically set it to /bin/bash
[15:00] <boboma> sorry, says /bin/bash
[15:00] <genii> It should point to dash by default
[15:00] <StrangeNoises>  /bin/sh is a symlink to dash
[15:00] <boboma> so mine is set too
[15:01] <boboma> was a mistake. mine is saying /bin/bash as well. How comes that it is working differently for you?
[15:02] <boboma> It used to work in 17.10 for me. Now after the update it stopped working that way.
[15:02] <boboma> autocomplete is set of course in .bashrc
[15:02] <boboma> well. suboptimal
[15:11] <laserbeak4445> If I decided to install the 18.04 test patch for the GNOME memory leak, should I let them installed if everything is fine or improved?
[15:11] <laserbeak4445> or leaving them on my system could maybe cause conflicts with future updates? 
[15:13] <boboma> StrangeNoises, I see what the problem is now. Once I switched to another user with su - abc I have a different shell. sh. Don't know how this can happen
[15:14] <en1gma> can someone help me get intel opencl working on my laptop? its an I3-4005u and some apps i like can use opencl and hopefully help my ststem under load
[15:14] <en1gma> im running ubuntu 18.04 x86_64 Desktop and have done apt-get update && apt-get upgrade && apt-get dist-upgrade
[15:15] <boboma> Set it back to bash and autocomplete is working now. Thanks for your help
[15:15] <en1gma> ive downloaded just about every intel icd
[15:15] <en1gma> 'clinfo' shows 0 platforms
[15:18] <en1gma> https://pastebin.ubuntu.com/p/Dg4H4Xs2FT/   <<< opencl sys analyzer tool
[15:18] <en1gma> 'clinfo' = "Number of platforms 0"
[15:19] <Laibsch> Can somebody help me understand what's going on in bug 991471? It still affects bionic and I'd like to see what I can do to get it fixed. IOW, how does the automatic mounting happen?
[16:03] <brainwash> laserbeak4445: how is the patch installed?
[16:26] <BionicMac> Hello. I am having an issue wih 18.04 Kubuntu flavor. Here are the details. Please read and let me know what you may advise.. and/or where should I file an official bug.
[16:26] <BionicMac> See here for details -> https://bionicmac.club/index.php/s/pmb8fqIzcZyBGQO
[16:26] <BionicMac> Thanks in advance. =)
[16:28] <brainwash> !bug
[16:31] <BionicMac> thanks
[16:31] <BionicMac> another link to same issue just in case: https://paste.ubuntu.com/p/NxNYwGF7KD/
[16:49] <brainwash> BionicMac: there is sddm package version 0.17.0-1ubuntu7 in -proposed
[16:49] <brainwash> uploaded 2 hours ago
[16:49] <brainwash> I suggest testing that one
[16:49] <BionicMac> brainwash: great. Thanks.
[16:50] <brainwash> bug 1764494
[16:50] <brainwash> bug 1763977
[16:50] <brainwash> just linking those
[16:50] <brainwash> didn't read through them due to being busy
[16:51] <BionicMac> brainwash: ok. I will investigate those bugs and checkout the sddm pkg.
[17:28] <BionicMac> brainwash: Where can find that latest sddm version 0.17.0-1ubuntu7 package? I am not familiar with the location of proposed packages.
[17:29] <brainwash> !proposed
[18:06] <bac> Hi, I tried to do a dist-upgrade from 16.04 to 18.04  on a Dell XPS 13 9360 and it failed.  Booting now shows an Ubuntu logo, cyles through all five dots, then the screen is blank with a faint cursor in the top left. Thoughts on recovery?
[18:13] <BionicMac> bac: hmmm I have the same screen on boot and I didn't do a dist-upgrade. I was running 18.04 from an iso about a month old and upgrading every day. This started with me sometime in the last 3 days. Not sure which day of upgrades started this because I didn't reboot for 3 days. I have it narrowed down to 4-[17/18/19] upgrades though.
[18:13] <bac> BionicMac: I saw you say you could get a terminal.  I cannot.
[18:14] <BionicMac> bac: try this to verify we are having the same issue please: from the blank screen faint cursor do "ctrl+alt+F2" ... login and do 'sudo systemctl restart sddm.service'
[18:15] <BionicMac> bac: I get to a terminal in that state no problem.
[18:15] <bac> I tried that. Nothing.
[18:16] <BionicMac> boot to recovery in grub menu, selct recovery, then select "drop to prompt" and try restarting sddm.service.
[18:16] <BionicMac> lunch time bbs
[18:17] <bac> Thanks BionicMac.
[18:18] <seffyroff> Hey folks! I'm really rooting for you guys shipping Bionic next week! Is everything in hand, or is there a particular area that could use an extra pair of hands in dev/testing/anything else?
[18:18] <seffyroff> should I just grab an issue and start working on it?
[18:21] <BionicMac> bac: while you are in recovery at tty console... log the output from these commands: 'sudo systemctl --state=failed' -and- if it shows you services in failed states do a 'systemctl status put-your-failed-service-here.service' that may help pinpoint the situation. 
[18:33] <bac> BionicMac: 'systemctl --state=failed' shows 0
[18:44] <BionicMac> bac: Maybe because in recovery mode you are not in the exact state during the failure on boot. It would be ideal if you could drop to prompt from the blank screen with faint cursor .. I have an apple keyboard so I actually use Fn+ctrl+alt+F[2,3,4, etc] to get to prompt.
[18:45] <bac> I tried ctl-alt-F[2,3,4] and with Fn thrown in for good measure
[18:45] <bac> i'm paging through /var/log/syslog now to see if i can identify anything
[18:45] <BionicMac> sounds like you covered that then
[18:47] <bac> All looks good until it hits a bunch of "ureadahead: Ignored relative path" errors
[18:48] <BionicMac> bac: check your version of sddm while in recovery for kicks and grins: 'sudo apt-cache policy sddm' 
[18:50] <bac> That fails due to read-only file system.  "Couldn't create temporary file"
[18:50] <bac> dpkg -l shows no sddm
[19:00] <laserbeak4445> brainwash: Installed as instructed on this page: https://community.ubuntu.com/t/help-test-memory-leak-fixes-in-18-04-lts/5251
[19:03] <brainwash> laserbeak4445: isn't that the exact version that is available in the repos already?
[19:03] <brainwash> !info gjs bionic
[19:06] <brainwash> laserbeak4445: so, what was the question again? I do miss the backlog
[19:12] <laserbeak4445> brainwash: My questions was:
[19:12] <laserbeak4445> If I decided to install the 18.04 test patch for the GNOME memory leak, should I let them installed if everything is fine or improved?
[19:12] <laserbeak4445> and
[19:12] <laserbeak4445> or leaving them on my system could maybe cause conflicts with future updates?
[19:13] <laserbeak4445> To be clear, I didn't installed those patches yet.
[19:15] <laserbeak4445> What would be the best way to proceed for me from here? Install those patches directly from the reposÉ
[19:15] <laserbeak4445> ?
[19:15] <brainwash> I guess so
[19:16] <brainwash> just keep your system up-to-date
[19:16] <laserbeak4445> alright
[19:16] <laserbeak4445> ty
[19:16] <brainwash> the patched version mentioned on that website is the exact same version which is available in the ubuntu repo (since 2 days)
[19:17] <laserbeak4445> ok good
[19:18] <brainwash> however, this https://bugs.launchpad.net/gnome-shell/+bug/1672297/comments/84
[19:19] <brainwash> laserbeak4445: expect another package update with more patches soon
[19:22] <laserbeak4445> ok cool thx again
[20:17] <Bashing-om> laserbeak4445: Here : https://community.ubuntu.com/t/help-test-memory-leaks-fixes-in-18-04-lts/5251 .
[20:17] <FurretUber> Pidgin is crashing often. What happens is pretty strange, the window title start to change to all opened channels many times per second and its CPU usage increases greatly
[20:18] <FurretUber> I can no longer click in anything and I can't write messages, as the window become unresponsive
[20:18] <FurretUber> It generates no file in /var/crash
[20:21] <brainwash> FurretUber: maybe related bug 1750941
[20:22] <FurretUber> I reported that bug, and that behavior I have no longer observed
[20:23] <FurretUber> This one I've seen is not new, but it's happening more often
[20:23] <brainwash> FurretUber: I would follow these instructions then https://developer.pidgin.im/wiki/GetABacktrace
[20:26] <FurretUber> I will close the channel window. May someone mention me? 
[20:29] <FurretUber> Well, and Pidgin crashed again. Now the gdb is ready
[20:30] <FurretUber> Again, may somebody mention me?
[20:30] <brainwash> FurretUber: yes
[20:35] <FurretUber> With the method of the site it's impossible to reproduce
[20:35] <brainwash> it does not crash?
[20:35] <FurretUber> No
[20:36] <brainwash> interesting
[20:36] <FurretUber> What is happening, apparently
[20:36] <FurretUber> I open Pidgin and access a few servers
[20:37] <FurretUber> I close one tab with a server I set as persistent
[20:37] <FurretUber> I am mentioned in that server, then I open the notification and the chat opens in a new window
[20:37] <brainwash> maybe try this https://stackoverflow.com/a/34185049
[20:38] <FurretUber> If I try to close one window, that chat(s) go to the other window
[20:38] <FurretUber> If I try to close the second window, Pidgin has the problem
[20:39] <FurretUber> So I have to be mentioned and open the channel using the notification
[20:39] <brainwash> that's info which you should add to a bug report
[20:39] <FurretUber> I can get the backtrace (I think gdb is set correctly)
[20:40] <FurretUber> I'm sorry for asking again but, may you mention me?
[20:40] <brainwash> FurretUber: 
[20:40] <brainwash> FurretUber: 
[20:40] <FurretUber> Two pidgin windows opened
[20:40] <FurretUber> Now I'll close the first that was opened
[20:40] <FurretUber> All chats tabs migrated to the second window
[20:41] <FurretUber> Now I'll close the second window
[20:41] <brainwash> did you disable ASLR this time in gdb
[20:41] <brainwash> ?
[20:41] <brainwash> I mean enabled it
[20:42] <FurretUber> It happened again and gdb got nothing
[20:42] <FurretUber> Maybe because it's not a crash, but a freeze
[20:43] <FurretUber> I'll report
[20:43] <FurretUber> A shame there is no backtrace or apport or anything
[20:44] <brainwash> you tried with ASLR enabled in gdb this time, right?
[20:44] <FurretUber> Yes
[20:44] <brainwash> ok
[20:45] <brainwash> not sure if you like to experiment, but debian has packaged pidgin 2.13
[20:45] <brainwash> https://packages.debian.org/sid/pidgin
[20:46] <brainwash> could be helpful to know if that version is affected by the problem aslo
[20:46] <brainwash> also
[20:47] <brainwash> in case it installs cleanly
[20:47] <brainwash> there does not seem to be a PPA for pidgin with the latest version
[20:49] <FurretUber> E: Unable to correct problems, you have held broken packages.
[20:49] <brainwash> did you try to install pidgin + pidgin-data?
[20:50] <brainwash> not sure if ibpurple0 is needed also
[20:50] <FurretUber> Yes, libpurple0w was the issue
[20:51] <brainwash> https://packages.debian.org/sid/libpurple0
[20:51] <FurretUber> I will restart Pidgin
[20:52] <brainwash> FurretUber: so, now you are on 2.13?
[20:52] <FurretUber> Yes, it opened but there was no notification of the mention
[20:53] <brainwash> FurretUber: mmh
[20:53] <brainwash> it's possible that this is a feature patched in for the ubuntu package
[20:59] <brainwash> FurretUber: not sure what to suggest further
[20:59] <brainwash> you obviously want to file a bug report
[21:02] <brainwash> depending on your skills you could try to rebuild the debian 2.13 version with the ubuntu specific patches
[21:03] <brainwash> or the ubuntu 2.12 without the patches
[21:21] <FurretUber> https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1765846
[21:24] <FurretUber> It appears to be related with https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/352495
[22:16] <Lope> I've got a surface pro 2 running ubuntu 18.04. When I touch the physical windows button under the screen, the tablet vibrates, but it doesn't trigger anything at all in gnome. Not the start button, nothing. If the screen is off due to power saving it still vibrates when I touch the button but the screen doesn't wake up. I tried to see if I could bind a shell script or something to it by making a keyboard shortcut, but when I try that and the 
[22:16] <Lope> keyboard shortcut widget says "press any key" touching the button causes the tablet to vibrate but no key is registered and it continues waiting for me to press a key. Any ideas?
[22:23] <brainwash> Lope: found this https://github.com/jakeday/linux-surface
[22:30] <Lope> Thanks brainwash nice find!
[22:53] <Andreas__> Having trouble with the touchscreen on x11 sessions. Touching the "Show applications" button on shows the applications window while it's pressed, or by dragging the finger off it before releasing. It works as it should under wayland.
[22:54] <Andreas__> *on = only
[23:12] <sveinse> When I install 18.04 server and I try to rename the hostname, why and how is cloud-init renaming my hostname on boot?
[23:13] <sveinse> I've literally grepped /etc for traces of the old hostname, but still cloud-init still knows the servers old name
[23:58] <ltomi> hello
[23:58] <ltomi> i've an issue with ubuntu 18-04 beta 2
[23:58] <ltomi> shortly: I've installed Ubuntu 18.04 beta 2 to test. Brightness control doesn't work: not with hardware keys and GNOME didn't come with a GUI brightness control. Brightness works if I use xbacklight, and every time I login I've to run it elevated because brightness setting doesn't persist.
[23:59] <ltomi> My hardware is an HP laptop with intel Core i7 CPU and a NVIDIA GTX 1060 GPU chip