[00:25] <megaman> hello?>
[00:25] <megaman> are there other ppl on here/
[00:25] <megaman> ?
[00:26] <megaman> type 1 if yes
[00:26] <arraybolt3> margan-u2: 1
[00:26] <arraybolt3> wrong ping
[00:26] <megaman> holy sht
[00:26] <arraybolt3> but yes, there are other people here
[00:26] <megaman> what is this?
[00:26] <arraybolt3> Official technical support channel for Ubuntu Linux.
[00:26] <arraybolt3> (You can type /topic and press Enter for a full description)
[00:26] <megaman> amaranth... : )
[00:26] <megaman> heyy
[00:27] <megaman> lols
[00:27] <megaman> okay im done
[00:27] <megaman> okay well yall stay healthy and peace !
[00:27] <megaman> exit
[03:24] <mybalzitch> lol when [wipes] is in the subtitles
[03:24] <mybalzitch> oops
[03:57] <pickanick> 22.04: I issued "sudo snap refresh" while I was connected to a slow network. I tried to stop snap refresh with ^C and eventually backgrounded it and killed it. I switched to a faster network and tried to run "sudo snap refresh"  again but "snap refresh" says "All snaps up to date. " while "snap refresh firefox" says  "error: snap "firefox" has "refresh-snap" change in progress" whereas there is no significant activity on network.
[03:57] <pickanick> Q: How do I confirm the situation  and reset the state so refresh will complete? My guess would be that there is no refresh-snap change in progress but there is a flag set somewhere that was not cleaned up properly when snap refresh was killed.
[03:58] <mybalzitch> is firefox still running?
[04:29] <pickanick> mybalzitch: no I had quit all firefox before attempting update
[04:31] <pickanick> Was there any answer to my question a half hour ago? I lost IRC connection
[04:32] <mybalzitch> no sorry
[04:32] <mybalzitch> restart snapd?
[04:33] <Bashing-om> pickanick: Maybe try ' sudo snap refresh firefox-snap '?
[04:34] <pickanick> @mybalzitch: do you mean "systemctl restart snapd.service" or some other item?
[04:36] <mybalzitch> yes
[04:36] <pickanick> hm now "snap refresh" is doing something with snap "core20", but very slowly
[04:36] <tarzeau> i usually remove snap and install only using .deb: https://github.com/alexmyczko/autoexec.bat/blob/master/config.sys/ubuntu-remove-snap-firefox
[04:36] <pickanick> tarzeau: I can see why.
[04:37] <tarzeau> because i had another snapped firefox not starting and needed a browser other than links2. it was much faster without snap, and i never liked the phone home and report how many users/hosts use snap to canonical
[04:38] <pickanick> hmm now its completed and firefox is updated.  black box.
[04:39] <pickanick> It just took an hour or more. usually ~ a minute, or seconds.
[04:39] <pickanick> thanks all
[11:54] <kmob> Hello! How to protect my login from someone who may change my password using Terminal?
[12:15] <Walex> DFor non-snap Ubuntu three main options: Mozilla Firefox repos for Debian/Ubuntu, Firefox ESR repository, Firefox "unofficial" Mozilla Team repository.
[12:16] <Walex> I also install MS-Edge as a fallback. Brave is another good fallbaxck.
[12:46] <Balavnik> Hi
[14:15] <niduts> Hello
[14:15] <niduts> @everyone
[14:15] <niduts> nigger

[14:51] <V1A> test
[15:01] <semitones> Hey everyone, how do I switch L and R audio in Lubuntu 22.04? Does this solution from 10.04 still reference the same software? https://superuser.com/questions/59481/how-to-swap-stereo-channels-in-ubuntu/144252#144252
[15:02] <fweht> hello, i just installed xubuntu and vscode-insiders, but when i try to activate sync in vscode, it hangs forever...  anyone else had this problem?
[15:03] <bunjee> What is balena etcher and how do I install it in Ubuntu 22.04?
[15:03] <fweht> i assume it tries to connect to the browser for the login but the handler is not working?
[15:05] <constxd> hi lads
[15:05] <constxd> so i have a upstart service right and this is what's contained in its script stanza
[15:06] <constxd> start-stop-daemon --start --quiet -d /var/foo -c myuser:myuser --make-pidfile --pidfile /var/run/myservice.pid --exec $DAEMON >>/var/foo/myservice.out 2>&1
[15:06] <leftyfb> constxd: you really should use a systemd service.
[15:06] <constxd> i know but i can't
[15:07] <constxd> the problem is myservice.out is not being created
[15:07] <constxd> the program is running though
[15:07] <bunjee> What is balena etcher and how do I install it in Ubuntu 22.04?
[15:07] <leftyfb> constxd: why can't you use a systemd service?
[15:07] <fweht> aah cool it works now the problem was just that firefox wasnt my default browser :)
[15:10] <constxd> leftyfb, idk we are using systemd now and shipping ubuntu 20.04 but we have a lot of legacy systems deployed using upstart on ubuntu 14.04
[15:11] <constxd> im sure it is possible to use systemd instead but i don't think that's the root issue here
[15:11] <constxd> i just wanna know why the file isn't being created
[15:13] <leftyfb> constxd: 14.04 was EOL almost 5 years ago
[15:16] <constxd> thanks
[15:17] <semitones> bunjee: I think etcher is a Windows program
[15:18] <leftyfb> it's not
[15:18] <semitones> Does pulseaudio work the same way now as in 10.04? Is there a graphical way to switch L and R channels?
[15:23] <tomreyn> bunjee: https://github.com/balena-io/etcher#debian-and-ubuntu-based-package-repository-gnulinux-x86x64
[15:55] <semitones> Turns out it almost worked (I think)
[15:55] <semitones> pactl get-default-sink doesn't work
[15:55] <semitones> But pactl list sinks works
[16:20] <tnt_yeeter45> meow
[16:21] <philip> test
[16:21] <philip> exit
[16:32] <bunjee> tomreyn:I don't know what the ***** are for.
[16:39] <bunjee> What is balena etcher and how do I install it in Ubuntu 22.04?
[16:40] <leftyfb> bunjee: why do you think you need it?
[16:51] <bunjee> leftyfb: I just saw it being installed on a video I watched. Does K3b do the same thing and can I use it in Windows?
[16:52] <leftyfb> bunjee: etcher is used to write iso's and other disk image files to removal storage devices. Usually to write an ubuntu install .iso to a cd or usb
[16:52] <leftyfb> bunjee: you'll have to ask in #windows for Windows related questions
[17:07] <Diagon> When Gnome locks the screen, and I return/ login, I'm presented with a blank screen.  I can C-A-F3, but I can't find a way to get the screen back and have to reboot.  Ideas?
[17:10] <atle> Diagon: maybe this could do it: sudo systemctl restart gdm
[17:11] <leftyfb> atle: that's basically the same thing as rebooting
[17:11] <leftyfb> Diagon: what release of ubuntu is this and which kernel are you running?
[17:12] <Diagon> 22.04, kernel 6.5.0-27
[17:12] <Diagon> I had this problem maybe 9 months ago, but it was occasional and ultimately went away.  Now it's /every time/.
[17:13] <Diagon> atle/ I've done that.
[17:13] <leftyfb> Diagon: have you checked if you're running the appropriate GPU drivers?
[17:15] <Diagon> I'm running nouveau
[17:16] <leftyfb> !nvidia | Diagon
[17:16] <leftyfb> I'd suggest trying the nvidia drivers
[17:17] <Diagon> Thanks, but I don't want to use proprietary drivers, and these have worked fine for 4 years now (20.04 and 22.04).
[17:18] <leftyfb> !bug | Diagon ok, feel free to report a bug against the nouveau drivers
[17:18] <tuxick> then don't buy nvidia :)
[17:18] <Diagon> How can you be sure it's the driver?
[17:19] <leftyfb> Diagon: it's called troubleshooting
[17:20] <Diagon> Cinnamon's a derivative of Gnome, and this guy concluded it was his wallpaper settings (I haven't tried yet): https://forums.linuxmint.com/viewtopic.php?t=379499
[17:20] <Diagon> I suspect there's more needed to troubleshoot.
[17:25] <bunjee> leftyfb: If balena etcher website has Linux listed as a download I would think I could acquire it from there....no?
[17:26] <leftyfb> bunjee: sure
[17:26] <leftyfb> bunjee: mind you, there's a usb writing application built into ubuntu
[17:28] <bunjee> leftyfb: I want you to know I am really new to Linux. What is it named?
[17:28] <leftyfb> Startup Disk Creator
[17:30] <ioria> Diagon, you can try this : https://extensions.gnome.org/extension/1414/unblank/
[17:32] <Diagon> ioria / that's interesting.  Thank you, I'll try.
[17:32] <ioria> ok
[17:37] <bunjee> leftfb: I can't find anything in Ubuntu 22.04that reads start up disk creator.
[17:42] <Diagon_> Hm.  I changed the background image, and now after a reboot "Settings" is freezing up on me.  I have to force quit.
[17:57] <mohanad> hekk\
[17:57] <mohanad> hello
[18:02] <webchat23> If I install the development version, I can just keep updating and I will reach the final version ?
[18:02] <leftyfb> webchat23: short answer, yes
[18:02] <leftyfb> !next | webchat23
[18:05] <webchat23> Ok thanks, just keep updating ?
[18:06] <Diagon> Well then - I opened "Extensions", toggled one off, and it completely froze Gnome.  I had to do a hard shutdown.  I'm tired of this DE.
[18:06] <leftyfb> Diagon: the default one?
[18:06] <Diagon> Yup.
[18:09] <marlonott> Diagon youre off to using unity then how to: sudo apt install ubuntu-unity-desktop -y
[18:10] <leftyfb> Diagon: or you should just try to change the driver to nvidia to see if the issues get resolved
[18:10] <Diagon> What's the state of unity these days?  I was going to change the DE for 24.04, but not being too enthusiastic about KDE, honetly there's not a lot out there.
[18:10] <webchat23> well basically the question is, if I install the development version and just keep updating it, will I reach the final version of 24.04 ?
[18:11] <leftyfb> webchat23: you were already told, yes
[18:11] <xangua> Download and try it Diagon
[18:12] <younder> The documentation said if you attach a machine to a ubuntu pro subscription 22.04.4 should give me a 26.6 kernel if I do a full-upgrade. This works on my desktop, but it doesn't wok on my RasPI4. Why?
[18:13] <leftyfb> younder: the pi is a different architecture with different repos
[18:13] <marlonott> my puppy is barking because she hates linux lol
[18:13] <leftyfb> marlonott: not here please
[18:13] <webchat23> Thanks
[19:17] <riOwnage> I have file system checks each time I boot Ubuntu. I looked at my /dev/sdXY UUID and are the same in fstab. I want to do a reinstallation.
[19:17] <riOwnage> I'm planning to format and create partitions: /, /home, /boot and swap. Any (other) recommendations?
[19:37] <Diagon> So I installed unity (and cinnamon), rebooted (to gdm), got the gear icon in the lower right, but clicking on it gives me /nothing/!  How can I fix that to use another DE?
[19:37] <anadon> Can someone update https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel ?   I'm  trying to follow these instructions, but they do not seem to work.  Any sort of tweaking I've tried has also been unsuccessful.  I think this needs to be touched by  someone who knows the current procedure already.
[19:37] <Diagon> (marlonott ? ^^^+1)
[19:40] <anadon>    Diagon: You're in No Man's land.   Almost like XDG got  nuked.
[19:42] <Diagon> anadon / not sure of the implications.  I know of xdg-open, but what are you refering to?
[19:44] <anadon>  Diagon: https://wiki.archlinux.org/title/desktop_entries
[19:44] <anadon> Archwiki is amazing.
[19:49] <Diagon> debsums is reporting no errors.  I'm running btrfs on RAID1, and I scrubbed it with no errors.
[19:51] <Diagon> Not sure how XDG relates to the display manager; but I have noticed for some time, I may have to repeatedly start a snap to get it going (eg. chromium two or 3 or 4 times, same with ff)
[20:02] <anadon> Diagon: XDG is the set of standards set forth by the Free Desktop Group from which Display Managers and Desktop Environments base a common set of standards for interoperability.
[20:03] <anadon> If something is malconfigured in one of the related files, it'll take out any number of Desktop specific functionality and configuration.  That sounds very specifically like your problem.
[20:04] <Diagon> In /usr/share/xsessions, I have:
[20:04] <Diagon> cinnamon2d.desktop  cinnamon.desktop  gnome-classic.desktop  gnome-classic-xorg.desktop  kodi.desktop  ubuntu.desktop  ubuntu-xorg.desktop  unity.desktop
[20:04] <Diagon> Nothing in there is "Hidden"
[20:10] <anadon> And your env?
[20:10] <anadon> But seriously.   I need someone in here who compiles the kernel.  These  instructions just don't work.
[20:11] <anadon>  I don't want to install arch tonight just to do kernel dev.
[20:11] <binboupan> anadon: what kind of dev do you want to do?
[20:12] <anadon> I need to trace out some misbehaving calls in the fanotify infrastructure.
[20:12] <Diagon> anadon / XDG_SESSION_DESKTOP=ubuntu-xorg, XDG_SESSION_TYPE=x11, XDG_CURRENT_DESKTOP=ubuntu:GNOME, XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu-xorg:/etc/xdg
[20:14] <anadon> binboupan: The instructions at https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel are broken.   `dh_prep: error: "debian/control" not found. Are you sure you are in the correct directory?` at `fakeroot debian/rules binary-headers binary-generic binary-perarch`.
[20:15] <binboupan> anadon: Ah, I don't know, I compile my kernel manually with localmodconfig, don't use packages myself
[20:16] <anadon>  If there are alternate instructions, I'll take them.
[20:28] <anadon> Eh.    Archwiki and manual copies it is.
[21:05] <tmroland> I wonder why would Canonical choose kernel 6.8 for 24.04 when 6.6 is the LTS kernel
[21:06] <tmroland> doesn't it make more sense to base a LTS distro on a LTS kernel?
[21:06] <tmroland> especially if it's recent
[21:10] <anadon> @tmroland: Intel Arc drivers, major 6.7 drops.
[21:10] <jeremy31> tmroland: Ubuntu can patch their own kernels.
[21:10] <younder> It's 6.5 and it's the one used in 23.04 -  24.04 isn't out yet
[21:14] <tmroland> look in 24.04 betaq
[21:14] <tmroland> its 6.8
[21:14] <tmroland> it would make more sense to backport whatever drivers to a LTS kernel supported upstream for two years
[21:14] <tmroland> all other major enterprise Linux vendors do that
[21:15] <tmroland> RHEL is still 5.14
[21:17] <younder> Looks like the release date for 24.04 is april 25
[23:08] <RickyRat5005> Is Livepatch not working on 24.04 (beta) yet?
[23:11] <sarnold> correct, it'll work once there are security updates for it
[23:13] <RickyRat5005> @sarnold Great, thank you!
[23:16] <devslash> I'm guessing by the name that LivePatch means you can update the os without a reboot ?
[23:18] <RickyRat5005> @devslach Correct. It's a part of UBUNTU PRO
[23:19] <sarnold> devslash: currently we're only live-patching the kernel; userland programs still need to be restarted to update them
[23:19] <sarnold> (well, okay, erlang programs can live-load new code, but the application has to be written for it, and I wonder if the usual erlang applications packaged for ubuntu use this mechanism or not :)
[23:19] <devslash> I see cool
[23:20] <RickyRat5005> I am loving 24.04... OMG This is fast!
[23:20] <RickyRat5005> And I like the change in the look as well.
[23:23] <devslash> RickyRat whats different about the UI?
[23:26] <RickyRat5005> @devslash I would be hard pressed to come up with a lot of specifics to be honest. But there are for sure subtle differences. https://www.cherryservers.com/blog/ubuntu-24-04
[23:27] <sarnold> heh, the first bullet point is a bit off .. *trusty* is the first to get twelve year support, 24.04 is still ten years away from entering that territory :)
[23:28] <RickyRat5005> The performance is incredible.
[23:28] <RickyRat5005> Feels like a completely different OS
[23:40] <Guest7029> yoooooooooooooo
[23:41] <arraybolt3> heya
[23:41] <arraybolt3> Anything we can help you with?
[23:46] <Pruners> I'm in a mess, I have a login set on a server I have, moved it and the computer to another location, I guess the IP address changed, and I don't know the command line commands well enough to figure what to do to log in to the server.
[23:47] <Pruners> ip a       gives me information, but I can't use the information.
[23:47] <sarnold> try ip a | grep inet
[23:48] <sarnold> that'll simplify it a bit to the lines with ip addresses on them
[23:48] <sarnold> then you can try to ssh to that ip address from your other computer
[23:55] <Pruners> yes  thank you    ip a | grep inet   seems to produce more worthwhile information
[23:58] <Pruners> I wish I knew how to interpret the result.   One line says  "inet <IP_ADDRESS>/8 scope host lo" I wonder what that means


[03:36] <hyperair> say, if i'm booting with pid1=systemd, is the user-init supposed to be systemd or upstart?
[03:37] <hyperair> right now i see systemd --user run as the lightdm user, but upstart --user run as me
[03:37] <hyperair> O_o
[07:23] <didrocks> morning
[07:25] <pitti> seb128, didrocks, Laney: btw, I just found "systemd-inhibit" -> much nicer than the gdbus call that we talked about a few weeks ago
[07:26] <didrocks> pitti: oh, great tip!
[07:32] <seb128> good morning desktopers
[07:32] <seb128> hey didrocks Laney pitti
[07:34] <didrocks> hey seb128 ;)
[07:37] <mlankhorst> morning
[09:03] <Laney> howdy
[09:05] <didrocks> hey Laney
[09:07] <Laney> pitti: neat find!
[09:08] <didrocks> Laney: does this ring a bell to you: /usr/bin/ld.bfd.real:.libs/libbluetooth.ver:2: syntax error in VERSION script
[09:08] <didrocks> ?
[09:08] <didrocks> (just in case, poking ;))
[09:09] <Laney> nope, haven't seen that before, sorry
[09:09] <didrocks> no worry :)
[09:09] <Laney> probably need to find out about VERSION scripts now :P
[09:09] <didrocks> yeah, I'm not seeing any though, so I need to check in the deps
[09:10] <Laney> what's .libs/libbluetooth.ver?
[09:10] <didrocks> I guess the libbluetooth from gnome-bluetooth (or the bluetooth panel)
[09:11] <didrocks> anyway, I'll check, but having the u-c-c fork is really making it difficult to remerge some stuff from upstream
[09:12] <Laney> I argued at the time for having it as a git fork of g-c-c, but lost :)
[09:13] <didrocks> yeah, not sure if I won't let that update to someone else TBH :p
[09:17] <seb128> hey Laney
[09:18] <seb128> didrocks, isn't robert_ancell working on that? he added a workitem to the blueprint?
[09:19] <seb128> Laney, the issue with backporting is not the vcs is use, it's the number of changes that went into the panels since our version
[09:19] <seb128> in use*
[09:19] <didrocks> seb128: well, he answered by email "nobody is doing it"
[09:19] <seb128> didrocks, when?
[09:19] <didrocks> just added a WI, but not sure he'll jump on it
[09:19] <didrocks> seb128: this night
[09:20] <seb128> oh, right, he didn't put his name on the wi on the blueprint
[09:20] <seb128> so probably don't count on it ;-)
[09:20] <didrocks> seb128: yeah, the g-c-c change was easy
[09:20] <Laney> speak for yourself, I find cherry-picking to be way easier than manual bending of patches
[09:20] <didrocks> just dropping patches
[09:20] <seb128> dropping a revert?
[09:20] <didrocks> yeah, 3 of them actually
[09:21] <seb128> k, makes sense
[09:21] <didrocks> but u-c-c doesn't work that well
[09:21] <didrocks> well, let's see if he's on that, I just spent 30 minutes just in case it was quick
[09:21] <seb128> Laney, I'm not saying that cherry picking is not nice, but the code is so different there is only so much you can effectively cherrypick
[09:22] <seb128> if you try to cherry pick a commit that apply to a source that doesn't even exist in your tree I fail to see how cherrypick makes your job easier
[09:22] <Laney> we would have updated more things if it were easier
[09:22] <Laney> definitely
[09:23] <didrocks> seb128: oh, actually: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1401362
[09:23] <didrocks> so maybe he's looking at it
[09:23] <Laney> nice ;-)
[09:23] <seb128> Laney, I disagree with that, the reason we didn't update is mostly because we wanted to stay away from the UI redesigns upstream did
[09:23] <seb128> that's the reason we did our version to start with
[09:24] <seb128> didrocks, cool :-)
[09:25] <tammy> willcooke, ping, did you see my email?
[09:25] <Laney> that's why it's a fork
[09:25] <seb128> right, so don't blame the diff on the vcs used
[09:26] <seb128> tammy, he's off sick
[09:26] <Laney> what?
[09:26] <tammy> seb128, oh! thank you :)
[09:26] <Laney> I am maintaining my point which is that we would have had the choice to take things but it is much more difficult to do that now so we just don't do it in reality
[09:27] <seb128> I disagree with that
[09:27] <Laney> we find bugs and take fixes then but nothing proactive happens
[09:27] <Laney> fine
[09:27] <seb128> I did update some panels previous cycle
[09:27] <seb128> and the vcs is not an issue/what stopped me to backport more stuff
[09:27] <Laney> It stops *me*
[09:27] <seb128> it's the fact that the new code refactor UIs and we don't want those
[09:27] <Laney> The same issue applies for u-s-d
[09:28] <seb128> k, you want to be religious on vcs fine
[09:28] <seb128> but it doesn't stop others in the team
[09:28] <seb128> so I don't think you can blame things not happening on the vcs choice
[09:28] <Laney> it's not a religious argument
[09:29] <seb128> not but it's a lame argument "I would work on it if I had it my way, but since you guys prefer working that way I just don't give a damn"
[09:29] <Laney> great, yes, that's what I said, thanks
[09:30] <seb128> yw
[09:31] <seb128> thanks for throwing the argument in our faces
[09:31] <Laney> dude
[09:31] <seb128> yeah, I'm really annoyed
[09:31] <didrocks> waow, session crash…
[09:32] <seb128> if we were using a git version of u-c-c we wouldn't be in any different situation in regard of bluez5
[09:32] <seb128> not even sure what that had to do with the discussion
[09:34] <Laney> I don't really know how to carry on without inflaming more
[09:35] <seb128> yeah, you should perhaps have thought about that before throwing the "if you guys didn't do stupid vcs choices we would be in a better situation"
[09:35] <seb128> anyway, let's move on
[09:50] <mlankhorst> willcooke: get well soon
[09:57] <Laney> hey ;-)
[09:58] <didrocks> good morning Laney :)
[09:59] <Laney> the skies are actually clear and blue today, quite nice
[09:59]  * didrocks used Men In Black device on both dudes
[09:59] <Laney> bet it's cold out there
[09:59] <didrocks> getting warmer here, but really cloudy
[10:00] <Laney> http://www.bbc.co.uk/weather/2641170
[10:00] <Laney> uh oh
[10:05] <Laney> heeeeeeey larsu, so I'm just pulling your patches for gtk - is unity going to need a fix too for the dash?
[10:06] <seb128> oh, speaking about unity, the launcher loosing the firefox/tb icons with the new gtk (having them replaced by a "?") is that a bamf issue?
[10:06] <seb128> did anyone talked to Trevinho yet about that?
[10:08] <Laney> e.g. nautilus has a big icon still & I guess there will be random others even if we fix the cases we find
[10:09] <larsu> Laney: yes :/
[10:09] <larsu> Laney: I'm almost ready with an update for those patches, too. But I guess we can just update the package again
[10:09] <Laney> shrug, just going to put it in the PPA right now
[10:10] <larsu> ok. Im busy breakfasting and making tea anyway
[10:10] <larsu> :P
[10:10] <larsu> thanks!
[10:10] <Laney> if you update for their approach that's better I suppose
[10:11] <larsu> I see their point
[10:11] <larsu> but they bring it across weirdly
[10:11] <larsu> "it's better to have obvious bugs than subtle ones"
[10:12] <larsu> imo, if the bug is subtle enough that nobody notices, it's not a bug
[10:14] <Laney> guess he really hates scaled icons :P
[10:14] <Laney> "miserable" made me laugh
[10:15] <larsu> ya
[10:15] <larsu> I'll fix it by choosing the smallest non-scaled icon (if it exists)
[10:15] <larsu> we might still end up with icons that don't quite fit the text or inconsistently sized icons
[10:15] <larsu> but at least menu items will always be the same height
[10:16] <larsu> and we'll never have screen-filling menu items
[10:20] <didrocks> larsu: challenging design?
[10:20] <didrocks> :)
[10:23] <larsu> didrocks: ya :)
[10:58] <didrocks> tseliot: hey, IIRC, you worked on plymouth, right?
[11:02] <tseliot> didrocks: yep
[11:05] <didrocks> tseliot: I'm trying to experiment the fsck progress with systemd. I have issue to be able to run it under my X11 tty
[11:05] <didrocks> tseliot: I just tried sudo plymouthd --no-daemon --tty=`tty` --debug
[11:05] <didrocks> after installing the plymouth-x11 package
[11:06] <didrocks> and most of the time, it exits successfully, returning 0
[11:06] <didrocks> no debug info that can give a clue
[11:06] <didrocks> does it ring a bell to you?
[11:07] <didrocks> (I have no other plymouthd process running)
[11:08] <didrocks> some other time, the process stays, but any command like plymouth quit or plymouth ping, plymouth --show-spash does nothing…
[11:08] <didrocks> splash*
[11:11] <tseliot> didrocks: it can hang from time to time, so you'll have to kill the process
[11:12] <tseliot> didrocks: halfline in #plymouth can probably help you debugging that
[11:12] <tseliot> (he's upstream)
[11:12] <didrocks> tseliot: great! I'll move the discussion there then, thanks :)
[11:13] <tseliot> np
[11:31] <Sweet5hark> moin
[11:31] <xnox> didrocks: we have an excellent page on plymouth on wiki.ubuntu.com which tells how to do stuff.
[11:32] <xnox> didrocks: it does work in x11 mode last tiem i've checked.
[11:32] <xnox> didrocks: also, our upstart-mountall-plymouth integration uses an extension to plymouth protocol to transmit fsck progress updates.
[11:32] <xnox> didrocks: systemd-fsck should learn to do the same, but at the time I didn't have time to figure that one out.
[11:33] <xnox> https://wiki.ubuntu.com/Plymouth#Running_Plymouth_.22post-boot.22
[11:33] <xnox> unless plymouth is completely broken under systemd/logind/new-upstream/something else
[11:39] <didrocks> xnox: I read about that page ;)
[11:39] <xnox> didrocks: ;-) ok
[11:39] <didrocks> xnox: but yeah, that's the issue, most of the time, the plymouthd daemon returned
[11:39] <didrocks> xnox: I have a good grasp on systemd-fsck now
[11:39] <xnox> didrocks: it usually works for me, but i'm on dual-screen so don't know.
[11:40] <didrocks> xnox: not sure if that comes into play, but well, I have it shown at this boot :)
[11:50] <Trevinho> seb128: might be something like that, but strange that firefox is affected
[12:17] <didrocks> xnox: tseliot: are we only supporting in the ubuntu logo theme "fsck:*" updates? like no other update as: plymouth --update foo
[12:17] <xnox> didrocks: correct. in ubuntu-logo and the text themes.
[12:18] <xnox> didrocks: so there is fsck progress on serial/text plymouth mode - e.g. reboot with forcefsck and hit ESC to see the text updates as well.
[12:19] <xnox> didrocks: we do not support plymouth "update" aka windows package upgrade in progress mode, nor messages / progress / etc for that mode.
[12:19] <didrocks> xnox: ok, systemd does it differently for the text mode (as we display the /dev/console messages)
[12:19] <didrocks> it's just forwarding the fsck progress there
[12:21] <didrocks> xnox: ubuntu-text is when we press escape? (or when we install like an nvidia card)
[12:21] <xnox> didrocks: let me check... cause there is a text one which we do not use at all.
[12:21] <didrocks> seems to be the later
[12:22] <didrocks> however, I don't see the fsck implementation as ubuntu-logo there
[12:28] <xnox> didrocks: ubuntu-logo theme & details plugin have mountall's fsck support.
[12:30] <didrocks> xnox: so, we don't use the ubuntu-text one?
[12:30] <didrocks> or it's just that if you have a nvidia card (or in virtualbox for instance), you don't have fsck support?
[12:31] <xnox> didrocks: one can use it, it just has no fsck progress output.
[12:31] <didrocks> xnox: yeah, so, I understood it right, thanks!
[12:32] <didrocks> xnox: also, the details plugin don't have the same logic than for ubuntu-logo
[12:32] <xnox> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/660151 <- if you feel like implementing =)
[12:32]  * didrocks wonders if we shouldn't fix all this having the same logic
[12:32] <xnox> didrocks: correct details plugin is more functional output, that is which mountpoint and which progress % it is.
[12:32] <didrocks> yeah
[12:33] <didrocks> so, it means, we'll have it in double
[12:33] <xnox> didrocks: i find the stock logic to be useless but "UX-user friendly"
[12:33] <didrocks> like /dev/console
[12:33] <didrocks> and this one
[12:33] <didrocks> xnox: the details plugin shows /dev/console output, right?
[12:33] <xnox> didrocks: "fsck 3 out of 7 disks 34% done; C cancel?"
[12:34] <didrocks> xnox: no, I just meant the /dev/console content, as plymouth ownes it
[12:34] <xnox> didrocks: kind of yes. plymouth steals /dev/console and the details plugin is printed there. Thus with Esc button one can switch between ubuntu-logo <-> details plugin.
[12:34] <didrocks> yeah
[12:34] <didrocks> so, we already have progress with systemd thanks to that
[12:35] <didrocks> (details progress, as all fsck -C are forwarded there)
[12:35] <xnox> ah cool.
[12:36] <xnox> patching systemd-fsck to send fsck messages to playmouth "mountall-style" would be useful, and then drop the fsck handling in the details plugin.
[12:36] <didrocks> xnox: that or having the fsckd daemon to get that upstream
[12:36] <xnox> most themes don't process those at all.
[12:36] <xnox> didrocks: good luck.
[12:37] <didrocks> xnox: they did that proposal actually :)
[12:37] <xnox> as far as i can tell none of that ever landed anywhere... =(
[12:37] <xnox> well, i'm out of date then.
[12:37] <didrocks> they don't want plymouth doing the logic
[12:37] <didrocks> they would prefer that we just send one update with a string
[12:37] <didrocks> and having fsckd doing that (this fsckd would be part of systemd)
[13:57] <tseliot> didrocks: yes, what xnox said
[14:22] <Laney> attente_: hey, do you know if anyone has checked the mir backend on gtk 3.14.5?
[14:22] <Laney> getting some build errors here
[14:23] <Laney> using the patch that was in bzr, this is
[14:31]  * desrt yawns
[14:32] <desrt> Laney: good morning :)
[14:32] <Laney> hey desrt
[14:32] <Laney> how's .ca?
[14:33] <desrt> it's snowing right now
[14:33] <desrt> which is potentially problematic, because they're currently replacing brickwork on our building
[14:34] <desrt> i get the impression that this is the sort of thing that you don't do while it's snowing
[14:34] <desrt> Laney: getting properly settled in?
[14:35] <Laney> maybe you'll have a free winter wonderland indoors
[14:36] <Laney> ya
[14:36] <Laney> some guys are here doing some work atm
[14:36] <desrt> did you score a dedicated office?
[14:37] <Laney> oh yes that was one of the requirements
[14:37] <Laney> had that in the previous place too
[14:37] <desrt> :)
[14:37] <desrt> standing desk time
[14:37] <Laney> this is larger though
[14:37] <Laney> there's a big void behind me
[14:37] <Laney> maybe a sofa?
[14:38] <desrt> nah.  pinball machine.
[14:38] <Laney> oh man
[14:48] <larsu> morning desrt :)
[14:49] <desrt> hihi
[14:49] <larsu> see the bug about g_menu_popup()?
[14:49] <larsu> ignore the name, of course. But nice concept.
[14:53] <desrt> no.  i didn't.
[14:55] <larsu> also, mclasen and hergertme are adding action group api
[14:55] <larsu> I think we might want to deliver on the description at some point...
[14:56] <larsu> I think they want to make get_muxer() public
[14:56] <larsu> (as an action group, of course)
[15:03] <desrt> scary
[15:04] <desrt> actiongroup is actually a shit api for the muxer
[15:04] <desrt> because of the signal scaling issue
[15:04] <desrt> that's why the observer interface was invented
[15:04] <desrt> worth noting that the newly added support for signal connection reporting could solve approximately half of that problem...
[15:08] <larsu> because we don't need to watch when noone is listening?
[18:00] <Laney> time to go out on bike in http://www.raintoday.co.uk/ and (a) give blood (b) mop floors at old house
[18:01] <Laney> joy ;-)
[18:01] <Laney> ttyl
[20:40] <darkxst> Sarvatt, anychance you can take a look at my patch bug 1392954
[21:11] <ricotz> darkxst, hi, better use tabs as in the original source
[21:33] <darkxst> ricotz, hi thanks, fixed


[00:00] <OvenWerks> For me it is the choice between getting really frustrated with windows (I have pulled windows out of laptops over frustration) and paying huge amouts of money for apple hardware
[00:00] <studiobot> <Johannes Menzel> I'm also more in the "analog" realm, but I really like to put some good piano vsts to compose.
[00:00] <OvenWerks> (and then paying huge amounts for plugings)
[00:01] <OvenWerks> pianotech is available for linux and probably the best... or at least most realistic
[00:02] <OvenWerks> sorry pianoteq
[00:02] <studiobot> <Johannes Menzel> I feel you. But I got the XLN Keys for 0-10$
[00:03] <studiobot> <Johannes Menzel> Yes, but my hearts bleeding at every dualboot windows startup
[00:05] <studiobot> <Johannes Menzel> The sad thing is that it's so easy to port plugins to linux, it's all about the f'ing cop protection.
[00:06] <OvenWerks> copy protection could be done in linux too. I think it is more a thing about not wanting to support it
[00:07] <OvenWerks> Linux does not have a one version for everyone as well as a small user base.
[00:07] <studiobot> <Johannes Menzel> This is the reason devs tell me if I ask them
[00:07] <OvenWerks> So linux may mean gnome xfce zde or fxwm
[00:08] <studiobot> <Johannes Menzel> But yes, support is another thinf
[00:08] <OvenWerks> It may mean x under or watland.
[00:08] <OvenWerks> Harrison has managed just fine.
[00:09] <studiobot> <Johannes Menzel> Yes, some dedicated plugin devs too, like u-he
[00:09] <OvenWerks> I find it interesting that while many copanies use Linux as the OS inside their synths, mixing desks, audio interfaces, few offer Linux setup utilities.
[00:10] <studiobot> <Johannes Menzel> Or overdone-dsp, but they currently don't seem to be in that good condition
[00:11] <studiobot> <Johannes Menzel> Yes, I guess even Waves are using Linux in their process.
[00:15] <studiobot> <Johannes Menzel> I'm not so much into this development thing, but I thought everything you need to support is to tell your customers is on which libraries (graphics and so on) your plugin relies.
[00:18] <studiobot> <Johannes Menzel> The typical linux audio user wouldn't be so hard to handle in these basic "where to put my plugin file" questions.
[00:35] <OvenWerks> A plugin should be self contained, compiled statically with almost all libs.
[06:58] <android> which kernal has trusty
[06:58] <android> for make a realtime kernel
[06:58] <android> from source
[06:58] <android> that is why creativity gets wasted
[06:59] <android> the disk is coding itself latent
[06:59] <android> when it adapts it adapts to suite the nullified environment
[07:00] <android> redoing the same junk over and over
[07:00] <android> like floating apps what is that  windows 3.1 for android
[07:01] <android> uncle C constraints


[02:46] <arthax0r> my jaunty server has been doing well
[02:46] <arthax0r> turning it into a full blow horde/funambol server
[02:47] <arthax0r> altho, i would say it seems to not be performing as well as it did under 8.04 server... it's an old ass machine tho
[07:07] <_stochastic_> hey room, out of curiosity, when will the next set of ISO's be put up on the UbuntuISO testing webpage?
[07:07] <_stochastic_> is there any schedule to it or is it pretty intermittent?
[11:25] <davmor2> heno: Hi
[11:43] <heno> Hi davmor2
[11:43] <davmor2> No ara today?
[12:56]  * mvo hugs sbeattie for the verification of #349725
[13:16] <jtholmes> where are the daily-live's from say 4/2/09
[13:16] <jtholmes> the ios's from 4/2/09
[13:17] <jpds> I think they're only preserved for two days and then deleted.
[13:17] <davmor2> jtholmes: do you mean 20090402
[13:17] <jtholmes> davmor2, yes
[13:18] <jtholmes> thanks jpds
[13:19] <jtholmes> davmor2, here is the problem  4/3/09 and 4/5/09 ubiquity installer's die at partman and i wanted to test 4/2/09 again to see if that problem exits
[13:19] <jtholmes> 4/5/09=4/6/09
[13:20] <jtholmes> I cant believe I am the only one having this problem
[13:20] <jtholmes> this is on kubuntu  ubuntu is fine
[13:26] <Strider^> yop
[13:28] <Strider^> euh je sais pas si j'ai fait un truc de travers mais j'arrive plus a avoir mon Google Calendar dans Evolution sous Jaunty
[13:29] <Strider^> oh right this is not the french channel ^^
[13:30] <jtholmes> strider sorry english only
[13:30] <Strider^> i can't set up my Google Calendar in Evolution anymore =/
[13:31] <Strider^> i don't remember what where the options in Evolution's versions berfore Jaunty but i think there's something missing
[13:35] <jtholmes> davmor2, is there any file/information in a daily-live .iso that tells me the exact date the .iso file was created?
[14:51] <fader_> davmor2: Hey, do I remember correctly that you have an Acer Aspire One somewhere with the original OS installed?
[14:52] <davmor2> fader_: I had an AAO with hardy unr on I now have an AAO with jaunty unr on why?
[14:52] <davmor2> Oh I have linpus lite too
[14:52] <fader_> davmor2: I'm trying to find out the lid switch behavior on it for bug 348012
[14:52] <ubot4> Launchpad bug 348012 in linux "Acer Aspire One doesn't wake up when lid opens" [Medium,Triaged] https://launchpad.net/bugs/348012
[14:53] <fader_> To see if it's really a bug or a 'feature' :)
[14:54] <fader_> davmor2: Do you have linpus installed on one currently?
[14:54] <davmor2> fader_: I can drop linpus back on and confirm but iirc in all the shops displaying them including the xp version if you shut the lid the power button need to be pressed to restart it.
[14:54] <davmor2> fader_: about 20 minutes I can
[14:54] <fader_> davmor2: You rock, thanks :)
[14:57] <davmor2> fader_: transferring to usb now
[14:59] <davmor2> hey cgregan
[14:59] <cgregan> hey davmor2!
[14:59] <cgregan> morning
[14:59] <cgregan> errrr
[14:59] <cgregan> afternoon! :-)
[14:59] <davmor2> cgregan: close but no cigar :)
[15:00] <davmor2> cgregan: will there be an upgrade path from hardy unr to jaunty unr?
[15:01] <cgregan> davmor2: That is a question for lool
[15:01] <davmor2> lool^
[15:01] <cgregan> davmor2: For our customers....no. Device is locked to the shipping version
[15:01] <davmor2> cgregan: :( meanie
[15:02] <davmor2> is this strictly for support reasons?
[15:02] <cgregan> davmor2: hehe
[15:02] <cgregan> davmor2: Yes...hardware support
[15:03] <davmor2> that's fair enough then can't argue with that
[15:04] <davmor2> fader_: installing to AAO now
[15:04] <fader_> davmor2: :D
[15:08] <lool> davmor2: An upgrade path that we support officially?  no
[15:08] <lool> But you can probably upgrade; not sure what would break, probably not too much
[15:08] <lool> Poulsbo would be the most obvious
[15:10] <davmor2> python is the big screw up at the moment with upgrades
[15:24] <davmor2> fader_: moment of truth
[15:24]  * fader_ plays a drumroll.
[15:26] <davmor2> fader_: orange flashy power button
[15:26] <fader_> davmor2: i.e. it didn't wake up when you opened the lid?
[15:26] <davmor2> no
[15:26] <davmor2> fader_: I'll press the flashy button now
[15:26] <fader_> davmor2: Excellent, thanks.  I'll put that in the bug.
[15:26] <fader_> davmor2: Thanks for checking that out!
[15:27] <davmor2> fader_: now it's green and it's come back to life :)
[15:27] <fader_> davmor2: I think it's just lazy.  Making you press a button...
[15:35] <davmor2> fader_: that's classy the wifi doesn't work after suspend Yay
[15:36] <davmor2> lool: is the current image okay?
[15:36] <fader_> davmor2: That's on the linpus install?
[15:36] <davmor2> fader_: yeap
[15:36] <fader_> davmor2: Heh, nice
[15:37] <fader_> Who needs to be online anyway?
[15:37] <davmor2> fader_: on a downside the leds work
[15:38] <fader_> davmor2: Which leds are those?
[15:38] <davmor2> fader_: wifi
[15:38] <fader_> Heheh wow.
[15:40] <cr3> dtchen: uploaded alsa-info output to bugs 354705 and 354707
[15:40] <ubot4> Launchpad bug 354705 in alsa-driver "[Jaunty] Microphone doesn't work at all on Eee 701SD" [Undecided,Incomplete] https://launchpad.net/bugs/354705
[15:40] <ubot4> Launchpad bug 354707 in alsa-driver "[Jaunty] Microphone doesn't work at all on Eee 900" [Undecided,Incomplete] https://launchpad.net/bugs/354707
[15:40] <cr3> man, ubot is quite clever to have understood both bug numbers
[15:40] <davmor2> fader_: I'm just doing the updates and then I'll check suspend and resume again and just double check that it didn't get fixed latter
[15:40] <lool> davmor2: The current image should be ok
[15:41] <fader_> davmor2: Ah, good idea
[15:41] <davmor2> lool: Cool I need unr back lite is so poor
[15:44] <jtholmes> have there been any reports of partman failing in the 4/3/09 and the 4/6/09 daily-live iso's
[15:46] <davmor2> jtholmes: not that I'm aware of  cjwatson ^
[15:47] <davmor2> jtholmes: is this on Kubuntu?
[15:47] <jtholmes> davmor2, both give partman error 141 and wont install i put in bug 345515 friday but was not able to upload the  syslog and partman logs until today
[15:48] <ubot4> jtholmes: Error: Could not parse data returned by Launchpad: The read operation timed out
[15:48] <jtholmes> maybe i am the only one having the problems
[15:48] <cjwatson> jtholmes: it's not reproducible across the board
[15:48] <cjwatson> we're working through incoming bugs as fast as we can but it's taking a while
[15:48] <jtholmes> cjwatson, ok i will try another machine
[15:48] <jtholmes> and see what the results are there
[15:49] <jtholmes> i suspect though that it is somehow my machine
[15:50] <davmor2> jtholmes: I did a kubuntu install on friday which was fine
[15:50] <cjwatson> jtholmes: I don't think you mean 345515. typo?
[15:50] <jtholmes> cjwatson, yes  typo 354515
[15:51] <jtholmes> davmor2, must be my machine I will check on another machine
[15:51] <jtholmes> because ubuntu installs fine, but on another machine
[15:52] <jtholmes> thanks guys i will test on another bed and get back to you
[15:53] <davmor2> jtholmes: That could be the problem there try installing on a pc rather than a bed you might have more joy :D
[15:53] <jtholmes> rofl thanks needed that
[15:54] <cjwatson> jtholmes: err. are you sure that that partman log is complete? it doesn't look it
[15:55] <jtholmes> cjwatson, you know I had the same feeling about completeness let me reinstall and see if I missed something
[15:55] <cjwatson> exit code 141 is SIGPIPE which means "something I was talking to just randomly died"
[15:55] <cjwatson> but there's no indication in the logs of what that might have been
[15:56] <jtholmes> let me rerun wont take long
[15:57] <davmor2> jtholmes: did you type out the logs?
[15:58] <jtholmes> davmor2, no i scp them to another machine from a terminal window i started after the partman failure
[16:04] <davmor2> fader_: This may take a while AAO linpus lite downloads 1 patch and applies it and then then next patch and applies it etc, etc, etc
[16:05] <fader_> davmor2: Heh, nice... thanks for the update. :)
[16:07] <davmor2> fader_: I wouldn't mind but I think it is on number 5 there are maybe 25-30
[16:08] <cjwatson> jtholmes: I would recommend making sure that you acknowledge the installer's crash window first, to make sure that all the logs are flushed
[16:11] <jtholmes> cjwatson, yes i will do that
[16:11] <jtholmes> cjwatson, i get the same results on another machine i will upload the  logs and try a third machine
[16:15] <davmor2> jtholmes: is your burn good?
[16:18] <jtholmes> davmor2, i actually do it from a hard disk
[16:18] <jtholmes> however i did burn earlier today and it also failed at the same place
[16:18] <jtholmes> i am going to try a third machine which does not have both SATA and IDE hardware to see if that may be the problem
[16:19] <jtholmes> davmor2, if no one else is having the prob then it has to be my hardware
[16:23] <cjwatson> jtholmes: please don't casually assume local hardware problems; there's no obvious evidence of that in your log as yet
[16:24] <cjwatson> jtholmes: it's entirely possible for it to be some property of the current state of your hard disk (and I don't mean a broken hard disk, I mean the bits on the disk), for example
[16:24] <cjwatson> in most cases of hardware problems, there is some evidence of that in the logs
[16:24] <cjwatson> similarly, in most cases of bad burns (although not all), there is some evidence of that in the logs
[16:25] <cjwatson> so let's be scientific about this :)
[16:26] <jtholmes> cjwatson, what are your suggestions
[16:26] <cjwatson> we don't really have enough widespread daily build coverage to be able to generalise accurately from "only one tester is seeing this" to "only one Ubuntu user is going to see this", anyway
[16:26] <cjwatson> jtholmes: in the first instance, I suspect that running the installer with 'ubiquity -d' from a terminal window and then uploading /var/log/syslog /var/log/partman /var/log/installer/debug would be useful
[16:26] <cjwatson> I have no suggestions until I have seen the logs; I prefer not to guess
[16:27] <jtholmes> cjwatson, I will run ubiquity -d and upload the logs thanks
[16:27] <cjwatson> thank you
[16:36]  * davmor2 suddenly dies of boredom waiting for this chuff linpus lite to update
[16:42]  * fader_ calls dibs on davmor2's stuff.
[16:43] <fader_> Er, I mean, I'm in mourning.
[16:43] <davmor2> :P
[16:44] <davmor2> fader_: it's on like number 8 or something now it's a joke I've install a netboot faster than this infact I'm pretty sure the gentoo builds faster :D
[16:47] <fader_> davmor2: Have you tried hitting it with a blunt object?
[16:48] <davmor2> fader_: I have a nasty feeling that it's a patching system and so needs to recompile the module/app after each update
[16:49] <fader_> davmor2: Ugh.
[16:49]  * fader_ barfs.
[16:50] <davmor2> fader_: now your getting it.  I just downloaded 713 meg of unr in the time that it took the bar to move 1 mm
[16:50] <fader_> davmor2: Yeah, but the screen is small, so you have to figure that 1mm is like 6km on a bigger screen, right?
[16:51] <cjwatson> fader_: berkelium was the system that was having LVM removal troubles, wasn't it?
[16:51] <cjwatson> fader_: I'd like to use my new magic servenab powers to fiddle with it today or (perhaps more likely at this point) tomorrow
[16:51] <fader_> cjwatson: berkelium was one of them
[16:51] <fader_> cjwatson: Cool, I'll be happy to assist in any way I can
[16:51] <cjwatson> fader_: anything special I need to do to get an installer session up with console access, beyond what's documented on the wiki?
[16:52] <cjwatson> preferably an installer image of my choice
[16:52] <fader_> cjwatson: Yes :/  It's doable but you'll need some extras and to fiddle with a preseed
[16:52] <fader_> cjwatson: I'll see if I can scrape you up some scripts to help, as otherwise it's a bit painful
[17:00] <fader_> cjwatson: I emailed a script to you and some detail on how it works.  If you'd like me to make the modifications for you I can do that as well... I'll just need to know what image you'll want to use and we'll have to walk through the preseed
[17:01] <cjwatson> thanks; happy to have a go myself
[17:04] <fader_> cjwatson: Cool.  Just to let you know, the process I'm using to reproduce this is to run "make_ppa berkelium"; wait a bit for berkelium to be rebuilt in the PPA pool (using LVM), and then run the install
[17:05] <fader_> (make_ppa on nickel will wipe a machine and rebuild it for use in the PPA pool)
[17:07] <cjwatson> right. sounds straightforward enough
[17:08] <cjwatson> this is about third or fourth on my list so I'll see how it goes today ...
[17:27] <jtholmes> cjwatson davmor2  that problem appears to be hardware specific  move to 3rd machine and installs from cd and runs fine
[17:28] <jtholmes> move=moved
[17:28] <cjwatson> I'd say system-specific rather than hardware-specific
[17:28] <jtholmes> that was what i meant type
[17:28] <jtholmes> typo
[17:29] <jtholmes> I'll fight that battle here
[18:36] <fader_> davmor2: Still updating? ;)
[18:37] <davmor2> Yes, Damn IT!  Whose idea was this anyway
[18:38] <davmor2> fader_: on a plus side this is the last patch
[18:38] <fader_> davmor2: Good grief.  I thought you were joking about gentoo ebuilds being faster, but I see that you weren't. :P
[18:39] <davmor2> fader_: I was on about a full install of gentoo :D
[18:39] <davmor2> I'm beginning to wonder if linux from scratch might not be faster
[18:40] <fader_> Ah, well, that's different.  I recall those taking a couple of days last time I tried.   I'm a bad person.  :)
[18:44] <fader_> davmor2: I was hoping when you were done with this you'd polish a 20 cubic foot granite cube down to the size of a grain of sand with a silk cloth for me.
[18:44] <fader_> :)
[18:45] <davmor2> fader_: no probs it'll take half the time this has
[18:45] <fader_> Hehe
[18:46] <fader_> I like to imagine that for space efficiency, the patches are transmitted as just MD5 sums.  Then the machine is generating a string of random bits and testing them to see if they give the same MD5... if not, it tries again.
[18:46] <davmor2> fader_: don't give them ideas
[18:57] <davmor2> fader_: It's only gone and finished ;)
[18:57] <fader_> \o/
[18:58] <davmor2> reboot
[18:58] <fader_> Maybe you should reinstall and update one more time, just to be sure. O:-)
[18:59]  * davmor2 shoots fader_ to death with blow pipe and rolled up paper
[19:00]  * fader_ has quit (shot to death with blow pipe and rolled up paper)
[19:01] <davmor2> fader_: After the monumental update it does exactly the same thing you still need to press the power button to wake it up
[19:01] <fader_> davmor2: Great.  I appreciate the hassle to test that :)
[19:01] <davmor2> fader_: worth being thorough though
[19:02] <fader_> Absolutely.
[19:05] <davmor2> now to get unr back on before I go mad
[19:07] <davmor2> fader_: Like I say iirc you had to do the same with xp too
[19:09] <davmor2> lool: nice to see unr down in size :)
[21:12] <dtchen> cr3: ok, looking. thanks.
[21:14] <cr3> dtchen: thanks man, there might be a known workaround for the Eees, but I'm not sure
[21:16] <dtchen> right, just looking at a Xine/PulseAudio issue, then i'll be at 35470[57]