[00:37] <pkh> hi, I'm trying to install 13.04 on my girlfriends laptop (mine installed from the same image perfectly) -- it's past the initial boot menu, into the vertical blue stripes, thinks for a bit and then ends up with a blue screen (of death?) -- mouse is visible and working, nothing else seems to be. any ideas what's wrong?
[00:39] <pkh> I'm guessing video driver... is there a boto option I can add to drop to standard graphics or text install?
[01:24] <darkxst> pkh, what gpu?
[06:03] <erbo_> hmm, anybody using the terminus font in Terminal? It just stopped working like a day ago.. Can't choose it anymore in preferences, even though it's installed
[06:05] <darkxst> erbo_, probably caused by the fontconfig update
[06:06] <darkxst> erbo_, bug 1182401
[06:06] <ubot5> bug 1182401 in fontconfig (Ubuntu) "After updating fontconfig, terminus font is missing" [Undecided,New] https://launchpad.net/bugs/1182401
[06:07] <erbo_> darkxst: thanks!
[06:12] <erbo_> sweet, now my eyes like me again
[13:49] <Linkeichi> Excuse me, i have mi netbook and connect a 23" Benq, i put it no mirror and when i put my cursor arrow in the up left corner it show the "gnome splash" in the two screens. What can i do to only showit in the active display"
[13:51] <Linkeichi> However it doesnt show the desktop manager in the right side in none of the two screens
[13:53] <Linkeichi> When i say gnomesplash i refeer to the gnome shell tha show when you put yor cursor arrow in the up left corner
[14:53] <Linkeichi> Excuse me, i have mi netbook and connect a 23" Benq, i put it no mirror and when i put my cursor arrow in the up left corner it show the "gnome splash" in the two screens. What can i do to only showit in the active display"
[16:51] <n0yd> darkxst: hey.  I just wanted to popin and say thanks for the other day.  Sorry I randomly disappeared, my good ol' comcast connection randomly crapped out
[16:52] <n0yd> Good news though is I found out the issue. It was somethinjg with gnome-shell (probably its weird compositing) when using the gnome3 team ppa
[16:53] <n0yd> I purged the the 3 gnome3 ppa's I was using (gnome3 normal ppa, gnome3 staging, and one of the gnome3 developers own ppa which requires you to also use the first two) (yes I know using those type of ppas can be dangerous and cause issues, obviously)
[16:53] <n0yd> So after I did all that, it worked fine.
[16:54] <n0yd> I do have a few other quick questions. If anyone might be able to lend a hand.
[16:55] <n0yd> Im using a custom kernel (based zen kernel and some other mods), and I'd like to completely rid of the ubuntu kernels from the repos. I obviously know how to remove them, by removing the kernels image, and 2 headers packages.
[16:55] <n0yd> The problem is, everytime I go to upgrade the system, there must be a meta package or something, that pulls the default ubuntu kernel back in
[16:55] <n0yd> So just removing them doesnt really do any good
[16:56] <n0yd> Its not a huge deal, but it does mess with my grub.  And id rather just always have my custom kernel as the default, rather than whatevers latest de3fault kernel is
[16:58] <n0yd> Thye other question I have is, related to some regressions of gnome3.  Originally in gnome3 (like 2011ish) when you had tweak tool set to have the file manager handle the desktop, you had the common of "Create a launcher" from the menu when you right the desktop.  Well, I dont know why they pulled that option suddenly in one of the newer releases, but they did.
[16:59] <n0yd> So I did some reading, and found you can get a similar function by using nautilus scripts.  Well Im not familiar with nautilus in gnome3, but it seems they either removed script functionality altogether, or changed the way you install/enable them
[17:01] <n0yd> I went ahead and used a popular ppa to install a script pack (it didnt include the create a launcher script, but it did inmclude others I was interested in, so I used it as a tester).  Well, after installing the scripts and script manager util, nowhere do they show in nautilus as the used to, and in preferences nautilus has nothing for scripts.
[17:02] <n0yd> So I dont know, and i am having a hard time figuring out if gnome 3.8 (I beluieve earlier version like 3.0/3.2 supported nautilus scripts) even supports nautilus scripts (maybe another feature regression as normal with gnome3)
[17:02] <n0yd> So those are my two questions for the day (I dont want to go over my limit :P) So if you anyone has any answers or tips, it would be much appreciated :)
[20:27] <zequence> Am I right in that gnome-shell in saucy has a tendency to freeze atm?
[20:27] <zequence> To introduce myself a bit. I'm the project lead for Ubuntu Studio
[20:28] <zequence> We're currently looking at supporting more DEs
[20:28] <zequence> I've tried Ubuntu Gnome saucy on virtual machine, and a real install. Both had a problem with gnome-shell freezing
[21:22] <DarkEra> I might just jump in on that... i even can't log in, mouse cursor moves but that's about it. So keyboard and mouse/touchpad clicking are kinda dead. I did try the same as zequence, both VB and a real install
[21:23] <DarkEra> in saucy that is
[22:00] <Linkeichi> This channel irc its for support? G3?
[22:02] <Linkeichi> I have a n issue with external display in my UG13.04
[22:14] <darkxst> zequence, haven't seen that, however I am running 3.8 ((which should be landing in saucy soon)
[22:16] <zequence> darkxst: Ok. I'll keep my open for 3.8 then
[22:21] <n0yd> Hiya
[22:22] <n0yd> Anyone using tint2?  I've noticed something about the tint2 version in ubuntu.  It doesn't contain the tint2conf GUI config tool
[22:22] <n0yd> Though if I type tint2conf into a terminal, it comes back saying that if I installing tint2 pkg in apt it will supply it, even though that is not the case
[22:22] <n0yd> So, I am wondering how in the heck I could get that tool
[22:36] <n0yd> I guess its not too big of a deal because tint2 is so frickin easy to configure, and has excellent documentation.  But it would still be cool to use tint2conf
[23:16] <darkxst> n0yd, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672840
[23:16] <ubot5> Debian bug 672840 in tint2 "tint2: 'tint2conf>properties' currently useless: "Saving not yet supported"." [Normal,Fixed]
[23:16] <n0yd> interesting
[23:16] <n0yd> I already set it up anyway
[23:17] <n0yd> 'thx for that though
[23:17] <n0yd> darkxst: any idea why a lot of the window themes that should be working just dont work?
[23:17] <darkxst> which window themes?
[23:18] <n0yd> like elementaryish and faenza for example
[23:18] <n0yd> both very popular gnome shell themes
[23:18] <darkxst> they probably need to be updated for gtk 3.8?
[23:18] <n0yd> nope they already are
[23:19] <n0yd> you can select them from current theme, and they dont do anything
[23:20] <n0yd> the gtk part of the themes works
[23:20] <n0yd> just not the current theme: part, which is the window border theme
[23:21] <n0yd> it happens with pretty much every theme Ive found that is updated for gnome 3.8
[23:21] <n0yd> all the other pieces work though
[23:26] <n0yd> darkxst: btw, re: tint2. Still doesn't make sense, cause even if that was the bug, tint2conf would still be there, as a valid command,.  And I just installed the version from debian that it says the bug is fixed in, and there i still no tint2conf
[23:27] <darkxst> * Do not install tint2conf (Closes: #672840)
[23:27] <darkxst> (from the changelog)
[23:27] <n0yd> oh that was their fix, lmao
[23:27] <n0yd> not much of a fix, but ok
[23:28] <darkxst> you could rebuild the deb, adding tint2conf back into debian/tint2.install
[23:28] <n0yd> yup i know
[23:28] <darkxst> n0yd, do the other metacity themes work (like the pre-installed ones)?
[23:28] <n0yd> yup
[23:29] <n0yd> i thought gnome-shell doesnt use mwetacity themes?
[23:29] <n0yd> because on gnome-look and in guides, it says the gtk themes contain the window border theme
[23:29] <n0yd> whereas there is a whole different section for metacity themes, unless thats just gnome2 stuff
[23:31] <darkxst> it does use them, have a look at any gtk3 theme, it will have a metacity sub-folder
[23:31] <darkxst> that is the window themee
[23:31] <n0yd> ok makes sense
[23:32] <n0yd> tbh i dont like the current setup of the way theming works in gnome3, gnome2 made a bit more sense
[23:32] <n0yd> thingds arent labeled very well, like "current theme"
[23:33] <n0yd> it seems they tried to bundle all the parts of themes together, and kindof failed
[23:34] <n0yd> alas, there are lots of things in gnome3 that dont make much sense from a users standpoint especially coming from gnome2 (especially future regressions).  But oh well, I still like it
[23:34] <darkxst> well they are bundled together, but you can still use bits and pieces from different themes'
[23:34] <n0yd> yup i know
[23:34] <n0yd> im doing that now
[23:35] <n0yd> i found the problem
[23:35] <n0yd> at least for one of them
[23:35] <n0yd> by using metacity-theme-viewer
[23:35] <n0yd> I tried loading Faience with it, and the errors, say it cant find murrine
[23:36] <n0yd> easy fix
[23:36] <n0yd> isnt murrine a gtk2 engine though, him maybe its a gtk2 window theme for 3.8 no idea
[23:38] <darkxst> well all themes have to have a gtk2 part as well
[23:38] <n0yd> ya i know
[23:38] <n0yd> but this is just the metacity part
[23:38] <n0yd> which i dont know about
[23:39] <n0yd> well, i got rid of the metacity errors, but there is an technical problem in the xml of theme
[23:39] <n0yd> which is strange, but whatever
[23:39] <n0yd> ^[[3~Error loading theme: Line 289 character 1: <button function="shade" state="normal" draw_ops="whatever"/> must be specified for this frame style
[23:40] <n0yd> ahh this particular theme is 3.6
[23:40] <n0yd> that would do it
[23:41] <n0yd> luckily this wasnt the one i cared for anyway
[23:42] <n0yd> the gtk3 and shell parts work, just not the metacity part
[23:48] <n0yd> hmm one that is fully 3.8 isnt loading, gotta figure this out
[23:49] <n0yd> it loads fine with no errors in the theme viewer, probably just gotta restart the shell or something
[23:50] <n0yd> hmm
[23:50] <n0yd> weird, it fails to find a valid theme file, but it works when loading it in the viewer
[23:50] <n0yd> Which is the same error the viewer gives for a different theme
[23:53] <n0yd> this makes no sense
[23:57] <darkxst> I don't know, but if the pre-installed ones work, then its a buggy theme