[01:33] <GeekDude> drrochet: What platforms are you trying to share to?
[01:35] <GeekDude> drrochet: If you want to set a up a samba share (fairly simple cross platform) there are instructions here https://help.ubuntu.com/community/Samba/SambaServerGuide
[08:07] <FAIQ> HEELO
[08:08] <FAIQ> i can not work partition on xubuntu
[10:02] <glitchd> how can i change the color of the clock in the indicator plugin?
[10:07] <knome> glitchd, this might be what you are looking for: http://open.knome.fi/2015/12/04/clock-applets-xfce-panel-xubuntu-1510/
[10:10] <glitchd> knome, thank you.
[10:12] <malysps> glitchd, or in gui, but you must add the non-default clock applet http://i.imgur.com/WEZ6g4j.png
[10:14] <glitchd> i have no idea where that menu is that you have open..
[10:18] <malysps> try adding the other 'clock' applet to the panel, in my case it looks like this http://i.imgur.com/MRiajzB.png
[10:20] <malysps> then right click on that clock in the panel and 'Properties' (or something like that...)
[10:23] <glitchd> http://imgur.com/a/n94Mn
[10:23] <glitchd> this is what mine looks like, and i have tried all of that before and it has not worked
[10:24] <glitchd> only thing that has worked has been to change the theme, but i want this theme. so i think i need to find where in the gtkrc file that info is and change it
[10:26] <knome> malysps, not possible in later versions, which is why i wrote that article...
[10:28] <malysps> so I have an old version of this applet? I'm on 16.04.1
[10:28] <malysps> and it works, as seen on the screenshot
[10:34] <knome> non-defaults can do this and that
[10:36] <malysps> true, I'm not even 100% sure that second clock applet is installed on fresh Xubuntu, but I think I've got it from the start
[12:25] <GeoDude> malysps: I am on a fairly fresh install of 16.04, and both clock applets seem to be installed. I don't recall explicitly installing any alternate clocks
[12:25] <GeoDude> Only the "Orage Panel Clock" offers color styling settings. This is actually pretty neat, I didn't know about this applet
[12:26] <malysps> good to know
[15:04] <xubuntu04w> hi all
[15:06] <xubuntu04w> please help after xubuntu update http://i64.tinypic.com/2myqgpj.png
[15:17] <flocculant> xubuntu04w: bug 1598316
[15:34] <xubuntu04w> ok, thanx
[16:03] <spudisgood> Hi
[20:09] <StayaSinic> sup guys! maybe someone help me with this?
[20:10] <StayaSinic> [    5.436013] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input5
[20:10] <StayaSinic> [   14.831356] systemd-udevd[324]: starting version 204
[20:10] <StayaSinic> 10 sec slooooooow boot
[20:10] <bekks> StayaSinic: And whats the issue with that?
[20:12] <StayaSinic> problem with slow initialization
[20:13] <StayaSinic> with old core 3.13 delay has 20 sec. i'm update core to 4.4 and have this
[20:14] <bekks> I dont see why 10s are an issue :) How often do you boot?
[20:15] <StayaSinic> infrequently. it's just a pain perfectionist!
[20:16] <StayaSinic> after installation (a year ago), there was no delay
[20:18] <StayaSinic> i'm google this trouble and find someone about psmouse, but nothing specific (not solved)
[20:19] <StayaSinic> https://bugzilla.kernel.org/show_bug.cgi?id=33292
[20:26] <StayaSinic> hm. maybe this is normal. i'm disapoint =(


[16:36] <superm1> james_w said that this upstart script causes problems with shutdown: http://bazaar.launchpad.net/~ubuntu-mythtv/mythtv/mythtv-trunk-022/annotate/head%3A/debian/mythtv-backend.upstart
[16:37] <superm1> because /bin/su opens a pam session.  if not via /bin/su, what's the right way to run an upstart started system daemon as a diff user?
[16:58] <Keybuk> why is su not the right way?
[16:59] <Keybuk> is mythtv-backend supposed to run as a user
[16:59] <Keybuk> or as a different uid
[16:59] <Keybuk> (they're different things :p)
[17:00] <superm1> i'm not sure why james_w said that su wasn't the right way, let me have him pop in here to indicate why he was thinking
[17:01] <superm1> different user (i think), because want to have the right $HOME etc as that user
[17:05] <james_w> hey
[17:06] <superm1> james_w, "<Keybuk> why is su not the right way?"
[17:06] <Keybuk> there's a difference between
[17:07] <james_w> bug https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/445953
[17:07] <Keybuk> "foo service needs to run as user bar"
[17:07] <Keybuk> and
[17:07] <Keybuk> "foo service needs to run as uid bar"
[17:07] <Keybuk> which do you want? :)
[17:08] <Keybuk> james_w: isn't that a bug in whatever's asking for the passphrase?  it should ignore non-interactive logins, surely?
[17:08] <james_w> I don't know
[17:08] <james_w> well
[17:08] <james_w> this is something that has been in flux
[17:08] <superm1> Keybuk, what characteristics would come with running as a different user versus differ uid?
[17:08] <james_w> previously there was no way for it to know whether a login was interactive
[17:09] <Keybuk> yes ther eis
[17:09] <Keybuk> there's been a way for 30-40 years
[17:09] <james_w> then we got the /etc/pam.d/common-session{,-noninteractive} split
[17:09] <Keybuk> it's called utmp
[17:09] <Keybuk> superm1: well, for a start, having a PAM session ;-)
[17:10] <james_w> ok, given its architecture it didn't know
[17:10] <Keybuk> superm1: that implies having the environment of that user, e.g. $HOME set right and stuff
[17:10] <james_w> this split makes it work in the common case
[17:10] <Keybuk> james_w: that's still a consolekit bug though
[17:10] <superm1> Keybuk, okay then definitely we want it running as a user.  it does make reference to stuff in $HOME
[17:10] <james_w> but it is assumed that /bin/su is an interactive login
[17:10] <Keybuk> (or a pam bug)
[17:10] <Keybuk> james_w: why?  su is only a *login* if run with -, -l or --login
[17:11] <james_w> consolekit has a narrow interface to this
[17:11] <james_w> pam-ck-connector creates a consolekit session from the pam stack when it is included the pam config for that service
[17:12] <Keybuk> so? :)
[17:12] <Keybuk> it's still a bug at that end
[17:12] <Keybuk> superm1's upstart job *does not* create a login shell
[17:12] <james_w> I'm not arguing that this is the correct way to do things
[17:12] <Keybuk> so no login shell or interactiveness should be assumed
[17:12] <james_w> I'm telling you the status quo
[17:16] <Keybuk> :)
[17:17] <james_w> if you know how to fix pam-ck-connector so that we can not create sessions for non-interactive sessions that would be useful
[17:17] <james_w> this is the first time we have hit this with upstart jobs.
[17:18] <Keybuk> I don't know enough about PAM
[17:18] <james_w> with init scripts the fix is easy as start-stop-daemon has --chuid
[17:18] <Keybuk> or CK
[17:18] <Keybuk> james_w: that's why I asked right at the top
[17:18] <Keybuk>  is mythtv-backend supposed to run as a user
[17:18] <Keybuk>  or as a different uid
[17:18] <james_w> and I don't know enough about anything
[17:20] <james_w> it sounds like it would be useful to have you, pitti and slangasek locked in a room for 30 minutes to work out the best solution