/srv/irclogs.ubuntu.com/2013/10/21/#ubuntu-gnome.txt

bjsniderevery image file opens at 99%03:28
arthurfiggishello :) just a general question regarding ubuntu gnome...i'm currently using kubuntu (13.10) because of their plans to support wayland over mir, is ubuntu gnome planning to do the same for future releases? i'd like to give gnome 3 a try, but not if it means having to use mir or the dash lens :(03:36
bjsnideryes03:37
bjsniderit will be wayland03:37
Noskcajarthurfiggis, You can install gnome3 on any ubuntu based system, if that's your issue03:37
arthurfiggisNoskcaj: oh no, i know that's already possible fortunately :) i was just wondering whether or not that'd be the case in the future more or less, or if it would require pulling in packages from canonical that i'd prefer not install :(03:38
bjsniderit will be getting better by about 14.1003:39
arthurfiggisNoskcaj, bjsnider: thanks very much for the information though, i couldn't find a good answer on google03:39
arthurfiggisbjsnider: that's great to know at least :) i don't have much invested in either xorg works fine for me as is, but wayland is the community solution whereas mir seems destined for...well, i'm not sure yet, hence the problem I suppose :P03:40
arthurfiggis(i'm not sure if canonical know either really, beyond that they'd really like to be selling tablets and cellphones)03:40
bjsnideri'm sure there will be a big push to get things working on the desktop03:41
NoskcajOnce mir properly gets going it should be interesting. If nothing else, it made wayland release faster03:42
bjsnideri think a bigger issue than mir/wayland is systemd03:42
bjsniderand it was singled out for criticism in the infamous blog post03:44
arthurfiggisbjsnider: i always thought systemd was an issue :( but that's just my general view i suppose, any solution that's locked to one particular kernel, compiler etc. i just don't like03:44
bjsniderthe issue is it's locked to gnome03:44
arthurfiggisbjsnider: ahh, i see...was that largely a decision made my gnome or redhat? it seems like redhat really pushed systemd more than anyone else...but that's beyond the scope of the channel perhaps, sorry :)03:45
bjsnideri dunno who pushed it, bu lpoettering works for red hat03:46
arthurfiggisi do know that they pushed gnome 3 out a little bit earlier than they should have, which didn't help its image at the time, but that's irrelevant now :) i'm not sure what happened with gnome...2.32 was my favourite DE at the time, KDE 2.2.2 felt really...bloated :) then gnome 3 came out and things got a bit weird03:48
arthurfiggisthen people like havoc pennington and de icaza started advocating for things like porting the Windows registry over in the form of the gconf database and things got -REALLY- weird03:49
bjsniderwait a minute now03:50
bjsnidergconf doesn't deal with anything important03:51
arthurfiggisif gnome 4 were less tied to systemd though that'd be great...i'd love to be able to run a more recent gnome on freebsd03:51
bjsniderit's just user customizations03:51
arthurfiggisbjsnider: well that's true...it's not technically very important, but it hid a lot of options away that were easily configurable oherwise i found :( now gnome-tweak-tool fixes pretty much all of that03:51
bjsnideranyway, gconf is dead03:52
arthurfiggis(that was when i tried the earlier gnome 3 releases anyway, i haven't in some time now but i'd like to just for the change :)  )03:52
arthurfiggisbjsnider: ahh...probably just as well then :) not as important as systemd as you say, but every bad idea that gets the axe03:52
bjsniderwell dconf is a db too03:54
arthurfiggisthat's true i suppose...the fact that something is stored in a database isn't necessarily the problem anyway :) but how it's implemented can  be...i never understood the logic behind hiding so many of the -basic- config options away, even the font size or icons on the desktop03:57
bjsniderwell, obviously as you point out that is in tweak now04:03
arthurfiggisoh yes, there's been solutions since of course :) that's in part why i'm interested in trying gnome 3 now, the more recent releases are looking pretty good!04:15
arthurfiggisbjsnider: i do agree with your point that system-specific things like systemd are a bad thing to depend upon though :( that's perhaps the most curious choice of all, before that gnome ran just as well under freebsd as it did in linux (freebsd is what i have more experience with)04:27
bjsnideri did not make that point04:28
arthurfiggisbjsnider: oh sorry, perhaps i misunderstood04:28
bjsnideri am saying it will be a problem for canonical04:28
arthurfiggishmm...now i'm not sure i follow then? unless systemd somehow prevents them from becoming more proprietary, which seems to be what they're interested in :(04:29
bjsnideri'm not saying it's bad for gnome to be so closely tied to systemd. if that's what they think is best, who am i to question that04:31
bjsniderit's a problem for canonical because they want to use upstart instead04:32
arthurfiggisbjsnider: ahh...yeah, that would be a bit of a stumbling block :P04:32
arthurfiggisthat and intel so bluntly rebutting them for mir, that was unexpected...as i recall they stated they wouldn't even carry xmir patches upstream04:38
arthurfiggislet alone not supporting it in their drivers, in any way, period...you usually don't see a big hardware manufacturer come out that strongly on linux software :)04:39
auscompgeekHmm, this is weird.06:23
auscompgeekgdm fails to start properly, but lightdm + unity-greeter works just fine.06:24
auscompgeek(X complains about not being able to detect my config properly)06:24
darkxstauscompgeek, logs?06:27
auscompgeekdarkxst: logs didn't seem to give me much, but I could try and pastebin them06:28
* auscompgeek can't remember where X stores logs06:28
darkxstgdm logs are in /var/log/gdm/:0*06:28
auscompgeekdarkxst: it looks like gdm didn't create any logs today06:32
darkxstthen its probably not starting, you did configure it as default display manager?06:33
auscompgeekdarkxst: it was the only display manager until about 15 minutes ago, so I'd assume so06:35
auscompgeekdarkxst: even tried `sudo start gdm`, which gave the same error message from X.org.06:36
darkxstauscompgeek, you can't do that!06:36
darkxst`sudo service gdm start`06:36
auscompgeekdarkxst: don't `start` and `service ... start` do the same thing in upstart/ubuntu?06:37
auscompgeekdarkxst: either way, whichever I do, same thing happens06:39
darkxstwhere/what is the error message?06:40
auscompgeekdarkxst: on screen, X.org says that my display, etc. couldn't be detected and is falling back to low gfx mode06:41
auscompgeekdarkxst: something along those lines06:41
darkxstand what graphics driver are you using?06:41
auscompgeekdarkxst: nouveau06:41
darkxstauscompgeek, that means GLX didnt load properly06:41
auscompgeekhmm, interesting06:41
darkxstrun `glxinfo | grep  -i opengl`06:42
auscompgeekhttp://paste.ubuntu.com/6275045/06:44
darkxstthat looks correct06:46
darkxstauscompgeek, either try with Nvidia proprietry driver, or find the logs06:47
auscompgeekHeh. I was considering installing nvidia drivers anyway, so might as well.06:48
auscompgeeknow, to make the tough decision of which version of the driver to install06:49
darkxst32506:54
darkxstalthough that might not be in saucy06:55
auscompgeekno, it isn't07:11
darkxstauscompgeek, just grab the latest version there07:11
auscompgeekyeah, good idea07:12
darkxstnvidia-experimental or whatever07:12
auscompgeeknvidia-current is nvidia-304, when 319 is available :|07:12
* auscompgeek installs 319 anyway07:12
ricotzauscompgeek, nvidia-319-updates07:13
auscompgeekricotz: heh, might as well07:14
ricotzwhich is 319.60 in saucy07:14
ricotzhttps://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-325 https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331 shows you were to get newer ones07:15
auscompgeekricotz: seems edgy :P07:16
ricotz325 isnt, 331 is ;)07:18
=== Noskcaj10 is now known as Noskcaj
darkxstauscompgeek, 325 is pretty solid here08:48
topylihm, empathy 3.10 seems to be a bit temperamental09:51
topyliauth errors (i guess) with facebook and jabber, and the dialog crashes when i go and edit the accounts. google talk works (set up via goa)09:53
darkxsttopyli, facebook issues were pre-existing09:54
topylioh yes, so it was09:54
darkxstcan you file a bug for crash09:55
darkxstfind the crash file in /var/crash and run ubuntu-bug crash-file09:55
topylifound it, ubuntu-bugging :)09:58
topylitwo in fact, one for empathy-accounts and one for empathy-auth-client10:00
darkxsttopyli, ok thanks10:00
darkxstping the bugs to me once done, although I won't probably be able to look at them tonight10:00
topyliwill do10:01
clong_Anybody about?10:19
darkxsthi clong_10:19
clong_Hello!10:19
clong_Just wondering where I can find known bugs on Ubuntu Gnome- I seem to be having some issues with 13.10, but I realise it's early days.10:20
topylidarkxst: #1242613 and #124261610:21
darkxstclong_, relevant packages in launchpad10:22
clong_Is it under ubuntu -> gnome 3?10:25
darkxstclong_, what are you having issues with?10:26
darkxsttopyli, I can't do anything much with those10:27
darkxstat the very least, try and use apport-retrace to get a backtrace10:27
darkxsttopyli, https://wiki.ubuntu.com/DebuggingProgramCrash10:28
topyliok, i'll have a look10:28
clong_I think there's two seperate issues, but a specific one: two minutes ago I was at the login screen (I think due to inactivity) and I couldn't focus on the password box or type in it with keyboard. Mouse was responsive and I could press space/enter on the cancel button.10:28
darkxstclong_, that is the lock screen, so `ubuntu-bug gnome-shell`10:29
clong_thanks darkxst10:29
clong_Is this the right place? https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs10:30
darkxstclong_, yes, but do run `ubuntu-bug gnome-shell` rather than using the link there, it collects important information that we don't get in manual bug reports ;)10:33
clong_Should I wait to run this when the problem occurs, or can I run it now?10:41
=== shadeslayer_ is now known as shadeslayer
mgedminso.... ubuntu gnome removed the ubuntu version of Online Accounts from the system preferences10:49
mgedminbut AFAICS empathy is still patched to use Ubuntu accounts10:49
mgedminwhich I can't now edit in any way at all?10:49
clong_Any idea how long we have to wait for Gnome 3.10 by the way? The improvements look great...11:24
mgedminclong_, it's in the staging PPA, but "regressions exist", so I haven't tried it out yet11:25
mgedminwheee, speaking of regressions11:25
mgedmingnome-terminal's ctrl+shift+t no longer uses $PWD11:25
mgedminbecause now I have to put some magic into my custom shell prompt11:25
mgedminof course /usr/share/doc/gnome-terminal/NEWS.Debian does not exist11:25
mgedminwait, I'm stooopid11:27
mgedminaccidentally working over ssh on a remote server11:27
mgedminof course the local gnome-terminal can't set $PWD to that11:27
auscompgeeklol11:38
auscompgeekthat sounds like fun11:38
mgedminis anyone else seeing chromium's address bar text jumping up and down after the upgrade to 13.10?  https://bugs.launchpad.net/chromium-browser/+bug/124266312:37
ubot5Ubuntu bug 1242663 in chromium-browser (Ubuntu) "Omnibox text jumps up and down while typing" [Undecided,New]12:37
bjsniderdarkxst, regarding my earlier statement about the problems created by systemd 205, here's what mbiebl says about it14:05
bjsnider<mbiebl> in systemd 205, all cgroup handling was moved into /lib/systemd/systemd14:05
bjsnider i.e. it's no longer possible to run systemd-logind standalone14:05
bjsnider i.e. under sysvinit or upstart14:05
bjsnider as a result you'll need systemd as PID 114:05
bjsnider or put it differently: the hacks we currently use in logind to make it run standalone, no longer work14:06
x-NaHi! Would this be the right place to give feedback on Gnome 3.10 on Ubuntu 13.10?14:13
bjsnideryes14:14
x-NaSo, the only problem I have with that is that I really do need multiple users logged in. Unfortunately selecting "Switch user" causes the gnome-shell to crash for the user that has logged in14:15
x-NaI would really like to hunt down what causes it14:16
x-Na3.8 with GDM seems to misbehave too, but 3.8 with lightdm is ok14:17
x-NaHmh16:07
joaosantanahi all17:17
=== joaosantana is now known as joaosantana_afk
bei  hi. i just installed ubuntu 13.10 and i would like some help getting a printer working. i am using a samsung clp-320 which has never come up with a driver but usually i can choose the 315 driver and it works but now it just tells me it has failed and drops me back to the add printer screen with no ability to manually choose. any ideas how to add it?19:36
beito clarify, i had manually chosen other drivers in (at least) ubuntu 12.10 and 13.0419:37
beiis there a (graphical) way to manually install a printer? or do i need to install something that isn't default?19:40
beipreviously i would have followed something like this: http://blog.sudobits.com/2012/04/13/how-to-install-printer-driver-on-ubuntu-12-04/19:42
beibut the steps where i can choose how a driver is chosen (in my case manually) is missing19:43
bjsniderbei, there's system-config-printer, and if you open gnome system settings there's printers19:46
vagvafhello people, i have ubuntu gnome 13.10. every time i go to "acitivities" and start typing the name of the programm i want to find i get asked for my account password, eventhough i am not logging in with an automatic log-in19:50
vagvafany ideas?19:50
beibjsnider: system-config-printer seems to be more what i am used to. i will let you know if it works. i wonder why is it hidden away?19:51
bjsnidercould be that gnome is planning on something more substantial in systemsettings but h aven't finished it yet19:52
beibjsnider: yeah, good call.19:53
beialso, to developers: thanks. l love gnome 3 and ubuntu and i appreciate all the effort that goes into making this happen. i should have said that before ploughing into my concern.19:53
ronjHi, following up on a keyboard shortcuts issue with the gnome 3.10 present in gnome3-next: can anybody else reproduce https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1242423 ? Troubleshooting / logging ideas very welcome. Thanks!21:54
ubot5Ubuntu bug 1242423 in gnome-shell (Ubuntu) "Shell 3.10 from gnome3-next PPA causes system keyboard shortcuts to partially fail" [Undecided,Confirmed]21:54
darkxstronj, please run `apport-collect 1242423`22:48
darkxstand in the future file bugs using `ubuntu-bug <package>`22:48

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!