[01:06] <msodrew> JeZxLee: I have that exact card. It's an amazing graphics card, but I am having issues with it and my monitor (Dell P2715Q). The mini DisplayPort > Displayport connection is just not stable (X session dies if u turn off the monitor). I doubt this is becuase its the GTX 970, my money's on the monitor to blame....though, something to consider.
[01:42] <chuckmcm> msodrew: have you looked at the xfsettingsd bug?
[01:43] <chuckmcm> my issue was that the screen would blank and not unblank, even though the session had in fact woken up
[04:21] <msodrew> chuckmcm: that sounds like roughly what i am experiencing. i can rewake the screen by forcing the console (CTRL+SUPER+ALT F1), but if i ever try to switch to the desktop environment F7, it never unblanks. what's the xfsettgsd bug?
[04:35] <chuckmcm> that is the bug msodrew
[04:35] <chuckmcm> I'll find you the patch
[04:37] <chuckmcm> https://bugzilla.xfce.org/show_bug.cgi?id=11107 pull the patch (jkampe68) and apply https://bugzilla.xfce.org/attachment.cgi?id=6590 as the patch
[04:38] <chuckmcm> that fixed it for me
[04:38] <chuckmcm> same symptoms
[04:41] <chuckmcm> This was my original bug report: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1581302
[08:37] <xubuntu63w> i forgot my password
[08:37] <xubuntu63w> how to  reset my password
[09:58] <well_laid_lawn> !password
[09:58] <well_laid_lawn> xubuntu63w:  ^^
[11:05] <xubuntu96i> wifi non funziona
[11:06] <xubuntu96i> wifi not working
[14:12] <msodrew> chuckmcm: wow thank you so much. ive never applied a patch before, but i will try this today and report back. what is the easiest way to apply said patch to xfsettingsd?
[14:12] <msodrew> rather, ill google it first of course–as the responserate in this IRC is at a reasonably slow pace
[14:57] <msodrew> could anyone provide me with a reputable guide on how to patch xfsettingsd with the patch that chuckmcm suggested? Do I fetch the source for xfce4-settings using apt-get and attemp to recompile from there? how do I make sure that my recompilation using the patch will build with a consistent, correct environment (vars, paths, etc) as compared to if apt-get handled it?
[14:58] <flocculant> msodrew: might help https://help.ubuntu.com/community/UpdatingADeb
[14:59] <msodrew> flocculant: wonderful. I will try this, thank you
[15:00] <flocculant> http://www.cyberciti.biz/faq/appy-patch-file-using-patch-command/
[15:00] <flocculant> also - don't often do it myself so don't be asking for help from me ;)
[15:01] <flocculant> as I generally end up scratching my head anyway ...
[15:02] <flocculant> msodrew: second might read more logically
[15:02] <msodrew> hahah
[15:02] <msodrew> aren't we all scratching our head in this linux troubleshooting world?
[15:03] <msodrew> :]
[15:04] <flocculant> heh
[17:00] <msodrew> flocculant: oh my god, it took me an hour of trying–but it worked. patch applied to an official xfce4 package from ubuntu's repos w/ the version number incremented to create no conflicts with APT, and most importantly, the patch seems to fix my screen blanking bug that i've struggled with for weeks! thank you thank you chuckmcm :D
[17:00] <Pici> !yay
[17:08] <msodrew> One other random question about xfce4: I love the "Editable Accelerators" feature where you can dynamically reassign a shortcut to any menubar entry as you mouseover + press new accelerator sequence. Problem is, it only works about half the time. I'm assuuming this has to do with some sort of userland app compliance thing? perhaps people developing apps w/ GTK+ (or whatever) are not allowing?
[17:16] <chuckmcm> you are most welcome msodrew
[17:17] <chuckmcm> if you have a launchpad login add a note to the bug that it fixed it for you, ideally it will get pulled upstream quickly
[17:18] <msodrew> im adding my thanks and 2 cents on xfce's bugzilla as we speak, should I also comment on launchpad?
[17:43] <msodrew> k. i pretty much spammed my success story on the bug reports in xfce's bugzilla, lightdm's launchpad, and xfce4-setting's launchpad.
[17:44] <msodrew> I'm noticing that the original reports of this bug were from 2014... nearly two years ago. Does it routinely take *this long* to get such a blocking bugfix into an upstream release?
[17:45] <knome> msodrew, depends on the bug and available developer time
[17:46] <msodrew> knome: of course, that is understandable. I am just not familiar with bug lifecycles in the linux world; not to mention bugs as esoteric as this one.
[17:46] <knome> tbh, i'd say a bug reported in 2014 is still young ;)
[17:47] <knome> unfortunately, there are so much older bugs
[17:48] <msodrew> i wish i could help. the amount of cognative load it would take to tackle a bug anywhere in the graphical stack (X server --> xfce4 --> xenial upstream) is mind-numbing to think about :\
[17:49] <knome> i guess so has it been for everybody else in the beginning :)
[17:53] <msodrew> haha of course. ive been writing software for nearly 15 years, but since most of my work has been in languages higher-level than C/C++ (easier, more abstracted).... so the idea of attempting to fix something written in those languagse under Linux is, well, ( ((head explodes)) )
[18:55] <chuckmcm> Random question, is there a way to get an indication on the top menu line for processes running on other workspaces?
[18:55] <chuckmcm> I just spent 20 minutes trying to figure out why Firefox couldn't spawn a new window only to find it was creating it on a different workspace page
[19:21] <xangua> You can just add the workspace widget?
[20:43] <chuckmcm> interesting but I don't see a workspace widget
[20:44] <chuckmcm> xangua: where would I find that?
[20:57] <flocculant> chuckmcm: windows buttons is default installed, check out the preferences - you can make it show all workspaces
[20:58] <flocculant> I don't use that personally - have workspace switcher instead
[20:59] <chuckmcm> sorry for being dense but xfce top bar is the launcher icon (left), apps on this workspace, power, network, volume, clock on the right
[21:01] <flocculant> check the preferences for the workspace one - you can filter to include all workspaces
[21:02] <ddybing> Hi. I just installed Xubuntu 16.04, and I have some problems with samba shares. I have a file server on my LAN running Debian with a samba share, and it works fine on Ubuntu (The "official version"), as well as Windows. But it will not show up in Xubuntu. I just get the message "Failed to retrieve share file list"
[21:02] <chuckmcm> workspaces settings has "general" and "margins" tab. General lets me select how many
[21:03] <ddybing> I've tried Googling alot, and I've tried disabling my firewall, but it none of that has worked. Suggestions are highly appreciated, as I need to be able to work with the files on my server.
[21:03] <chuckmcm> margins, well window margins. Nothing about 'all workspaces'
[21:03] <chuckmcm> ddybing: what tool are you using to access your samba shares?
[21:03] <chuckmcm> and did you install cifs-utils when you installed 16.04 ?
[21:04] <ddybing> Just the file manager
[21:04] <ddybing> chuckmcm: No, I have not.
[21:04] <chuckmcm> ah, then try that 'sudo apt-get install cifs-utils' will help a bit I think
[21:04] <ddybing> And with file manager, I mean Thunar
[21:04] <ddybing> Thanks. I will try that out!
[21:05] <ddybing> Will I have to restart my computer for it to work?
[21:05] <chuckmcm> I don't think it does, but easy to test
[21:05] <ddybing> It did not work, but I will try rebooting:-)
[21:06] <flocculant> chuckmcm: there are 3 different workspace/window plugins - exactly which one do you have? probably easiest to add them 1 by 1 and see what gives you what you want - I can see apps running on other workspaces here
[21:07] <chuckmcm> not sure I have a workspace plugin install flocculant just the default xfce window manager. Hmm.
[21:07] <krytarik> chuckmcm: http://docs.xfce.org/xfce/xfce4-panel/start
[21:08] <chuckmcm> yeah, that is where I just landed thanks to the big G
[21:09] <flocculant> chuckmcm: on a default xubuntu install, windows buttons is there - and as I said you can filter all workspaces with it
[21:09] <chuckmcm> looking for the workspace switcher on my install
[21:10] <flocculant> chuckmcm: right click on panel > Panel > PAnel Preferences
[21:10] <flocculant> chuckmcm: and unless you actually added workspace switcher you won't have it visible
[21:13] <chuckmcm> hmm, ok, right click -> Applications -> Settings -> Panel got me to the panel settings. Whereupon I added the Workplace switcher
[21:13] <ddybing> chuckmcm: I tried rebooting, but it did not work, unfortunately. But thanks for your suggestion :-)
[21:14] <chuckmcm> odd ddybing, I don't suppose the samba source you are trying to mount is complaining is it?
[21:14] <chuckmcm> You can also try mounting it directly 'sudo mount.cifs //server/share /mnt'
[21:14] <chuckmcm> You can also try mounting it directly 'sudo mount.cifs //server/share /mnt -o guest'
[21:14] <ddybing> chuckmcm: It works perfectly in Windows, and I've not have any problems with the "standard Ubuntu".
[21:15] <ddybing> Thanks, chuckmcm, I'll try that :-)
[21:16] <ddybing> Chuckmcm: Yay, that worked. I just added the user and password on the share, and it mounted right away!
[21:16] <chuckmcm> my guess then is that it isn't allowing guest access so it doesn't show up when just browsing.
[21:17] <ddybing> Yeah, I'm pretty sure I blocked it from guests, as I share LAN with another residence.
[21:18] <ddybing> Again, thanks alot mate.
[21:19] <chuckmcm> no worrries
[21:20] <chuckmcm> odd I got the workspace switcher on my panel bar but its super tiny


[00:25] <rick_h__> sinzui: verified that 1.17.3 fixes. Thanks for the heads up and devel update
[00:25] <sinzui> np


[05:48] <pitti> Good morning
[05:48] <didrocks> bonjour pitti
[05:48] <pitti> bonjour didrocks
[06:30]  * didrocks reboots
[06:40] <jibel> good morning
[07:17]  * xnox ponders if I ever wake up as early as pitti does....
[07:18] <pitti> xnox: I was really late today :)
[07:18]  * xnox has no chance
[07:18] <xnox> pitti: well, german time is one hour ahead, but still....
[07:19] <stgraber> xnox: unless you plan on waking up at 4am your time, you have no chance ;)
[07:19] <didrocks> hey stgraber!
[07:20] <stgraber> hey didrocks
[07:20] <didrocks> stgraber: quick question ;)
[07:20] <didrocks> https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1163358
[07:20] <ubot2> Launchpad bug 1163358 in ust (Ubuntu) "Missing liblttng-ust-ctl.so.0" [Undecided,Fix released]
[07:20] <didrocks> I synced ust to get the fix from debian to reship the .so file we were missing
[07:21] <didrocks> but lttng (in lttng-tools package) is looking for liblttng-ust-ctl.so.0 and not liblttng-ust-ctl.so.1
[07:21] <didrocks> as it seems upstream broke the soname with the version we ship
[07:21] <didrocks> stgraber: I tried a rebuild and it FTBFS, some missing API…
[07:21] <didrocks> stgraber: I wonder if we shouldn't sync lttng-tools from debian, but I saw you did some ubuntu modification
[07:21] <didrocks> so maybe you want to have a look first?
[07:21] <xnox> stgraber: i'ts easier to stay up until 4am for me ;-)
[07:21] <didrocks> (upstart job and so on…)
[07:22] <xnox> stgraber: eh =) you are back on the other side of the ocean ;-)
[07:22] <stgraber> didrocks: yeah, I'll take a quick look at lttng-tools. Technically it's one of those cases where I did the packaging in Ubuntu and it then got sync to Debian, so we shouldn't actually have a very large delta ;)
[07:23] <stgraber> xnox: yep
[07:23] <didrocks> stgraber: oh good news, thanks!
[07:23] <didrocks> :)
[07:23] <didrocks> xnox: the "right" side you mean, but all means ;-)
[07:25] <stgraber> didrocks: oh, that's going to be fun... I didn't realise Jon had used the old source package name for the new lttng-tools... will make things a bit more complicated
[07:26] <stgraber> (the upstream source is lttng-tools, our source is lttng-tools but Debian uses ltt-control as the source name)
[07:27] <didrocks> stgraber: oh indeed, I didn't notice that debian PTS did the redirection :)
[07:30] <stgraber> didrocks: so as far as I can tell, we don't have any actual delta between our lttng-tools and Debian's ltt-control. So I think it should be safe to sync
[07:31] <stgraber> it's a rather big version bump though, but we already have the 2.1 version of the modules and ust, so it'd make sense to have that bump as the current stack is broken
[07:31] <didrocks> stgraber: ok, so syncing and removing the old source?
[07:31] <stgraber> yep
[07:31] <didrocks> stgraber: yeah, as it's still broken, I think nobody can argue against bumping the version :)
[07:31] <didrocks> stgraber: taking care of that? you can reuse the same bug report if you want :)
[07:32] <stgraber> didrocks: yeah, I'll do that. I need to check whether I had ltt-control blacklisted when I landed lttng 2.0 and if so, unblacklist it
[07:33] <didrocks> stgraber: excellent!
[07:33] <didrocks> yep ;)
[07:33] <didrocks> for unblacklisting
[07:34] <didrocks> stgraber: I don't find it
[07:35] <stgraber> yeah, apparently it's not on the blacklist, so I'm a bit confused as to why we didn't auto-import that source
[07:35] <didrocks> yeah, there is only an Oneiric one…
[07:37] <didrocks> the changelog on the debian side doesn't seem to have anything weird…
[07:38] <stgraber> didrocks: updated the bug report to become an FFe for a sync+removal. I now just need to wait for the first Europe-based release team member to come online and we should be able to sort that one out
[07:38]  * didrocks invokes Laney
[07:38] <stgraber> (I could actually have asked you to update the report then do the approval myself, but oh well, we can probably wait an hour ;))
[07:38] <didrocks> stgraber: yeah ;)
[07:39] <didrocks> hum, my invocation magic is broken it seems
[07:39]  * didrocks opens a bug ;)
[07:41] <desrt> seb128: wow.  you wake up so late.
[07:41] <desrt> good morning :)
[07:41] <didrocks> desrt: he's quite early actually compared to other times :p
[07:41] <didrocks> desrt: good morning! :)
[07:41] <seb128> desrt, hey, had a good flight?
[07:41] <desrt> pfft.  and he calls himself german
[07:41] <seb128> well, I'm up for an hour
[07:42] <didrocks> desrt: a shame, isn't it?
[07:42] <pitti> bonjour seb128
[07:42] <pitti> ça va desrt
[07:42] <desrt> seb128: it sucked a bit (united is cramped) but it was OK
[07:42] <seb128> but I don't start IRC before being done with breakfast and emails
[07:42] <desrt> jetlag is already gone though
[07:42] <seb128> pitti, guten tag!
[07:43] <stgraber> desrt: ah, also made the trip from Canada to somewhere in Europe this week? (I arrived in Switzerland on Tuesday)
[08:04] <Laney> hello!
[08:05] <seb128> Laney, good morning
[08:05] <didrocks> hey Laney ;)
[08:05]  * Laney runs
[08:05] <didrocks> Laney: quick quick, stgraber wants to buy you a beer ;)
[08:06] <didrocks> bug #1163358
[08:06] <ubot2> Launchpad bug 1163358 in ust (Ubuntu) "[FFe] Sync ltt-control and remove lttng-tools to fix broken lttng in 13.04" [Undecided,Triaged] https://launchpad.net/bugs/1163358
[08:07] <Laney> so it says that the old one is broken, but not that anybody has tried the new one?!
[08:08] <seb128> Laney, while we are at beers for the release team, I'm sure Sweetshark will pay you one if you let libreoffice in ;-)
[08:08] <Laney> doing reviews shortly, no worries
[08:08] <didrocks> stgraber: fixing your bug tasks btw ;)
[08:09] <stgraber> didrocks: thanks
[08:11] <stgraber> Laney: so the llttng stack is released as a set, with inter-dependencies, us having something that's over one major release behind clearly won't work and explain the current failure. If we sync from Debian, we'll get the exact same set of packages as Debian, which I assume will work.
[08:11] <stgraber> Laney: if that fails too, I'll fix whatever the problem ends up being, but in any case, we want the new upstream version, so the sync will be the first step whether ti works or not
[08:11] <Laney> Sure, I just don't know why we need to assume when we could verify beforehand
[08:12] <Laney> even just to catch obvious fixable breakage without wasting one upload
[08:20] <stgraber> fine, doing a copy-package to a PPA, one sec ;)
[08:22] <Laney> :)
[08:23] <stgraber> not copying to a native PPA though because then it really wouldn't buy us anything vs copying straight to the archive ;)
[08:28] <stgraber> Laney: built fine on amd64, still waiting for i386
[08:29] <Laney> cool; an upgrade/smoke test would be enough for me
[09:15] <dpm> morning pitti. This cycle I've had virtually no time for translations, and I didn't keep up with the langpack schedule. I see there are some exports on https://translations.launchpad.net/ubuntu/raring/+language-packs so I assume you set them up while I was away (if so, thanks!). I'd like to update https://dev.launchpad.net/Translations/LanguagePackSchedule - if it was you who set it up, what times did you choose for the exports on the Launchpad side?
[09:15] <pitti> dpm: seb128, wgrant, and I coordinated that some weeks ago; the cronjobs on macquarie match now
[09:16] <seb128> dpm, hey
[09:16] <seb128> dpm, pitti: it would be nice if you guys could document what was needed to get the langpack exports to start
[09:16] <pitti> dpm: I think it's now Monday (precise), Wednesday (quantal), and Tue/Thu (raring) for the exports
[09:16] <seb128> it took 3 days of pinging random people to get it done and I'm not sure how it was done at the end
[09:17] <seb128> just that wgrant knew the magic
[09:18] <dpm> pitti, excellent. seb128, ok, will do it now. Basically the process was that I update https://dev.launchpad.net/Translations/LanguagePackSchedule and then I ping the Launchpad folks to update the cron job on their side. I'm more than happy to document that on that page, but I'm concerned that while the info will be there, it might not be too discoverable. Do you have any suggestions about where I could link that page to so that next time it's easier t
[09:18] <dpm> o find out that info?
[09:19] <seb128> dpm, I guess the issue was "finding who in the launchpad team knew what to dot"
[09:19] <seb128> only wgrant knew and it took some days to get down to find that he was the one knowing
[09:19] <seb128> the launchpad team shrinked over time...
[09:20] <seb128> dpm, do we really need them? could we document what they exactly so next team we just need #is to run the command or whatever
[09:21] <dpm> seb128, yeah, I know :/ We just really need someone with permissions to modify that cron job file pointed at the bottom of the wiki page. If someone at IS has got the permissions to update it (it's an internal LP branch, IIRC) and they can do it in a timely way, then I think that should be the way to go
[09:23] <dpm> seb128, pitti, I think setting up the langpack exports should be part of the process of opening up a new distro, so that it's not a disconnected task. What do you guys think?
[09:23] <seb128> +1
[09:23] <pitti> dpm: that sounds good to me, yes
[09:31] <dpm> pitti, seb128, ok, I'll talk to the LP guys to make sure that's included. pitti, I've blocked today to catch up on translations: what's the current status of the raring langpacks? I see that they are enabled in http://macquarie.canonical.com/~langpack/crontab - are they being published every Wednesday, or are we in freeze?
[09:32] <pitti> dpm: we got an upload yesterday, and accepted it
[09:32] <seb128> dpm, question for you, while you are around ... is that normal that https://translations.launchpad.net/ubuntu/raring/+source/nautilus/+imports?field.filter_status=all&field.filter_extension=all is all empty? should the .po imported from normal uploads show there?
[09:32] <pitti> dpm: the idea is to keep them getting uploaded, and do a manual full export close to the release
[09:33] <dpm> pitti, yeah, that sounds good. I've just approved a bunch of new gnome-{mahjongg,calculator,mines} templates that will need a full export to appear on the langpacks.
[09:33] <dpm> seb128, let me have a look...
[09:33] <seb128> dpm, I'm trying to figure out why https://translations.launchpad.net/ubuntu/raring/+source/nautilus/+pots/nautilus/fr/869/+translate is not translated in launchpad where it's translated in the fr.po from the nautilus source we are uploading
[09:34] <seb128> dpm, I've some other strings in nautilus that are in the same case
[09:35] <dpm> let me investigate, that the imports queue is empty is weird indeed
[09:35] <seb128> dpm, thanks
[09:35] <seb128> dpm, build log is https://launchpadlibrarian.net/136270806/buildlog_ubuntu-raring-i386.nautilus_1%3A3.6.3-0ubuntu14_UPLOADING.txt.gz
[09:35] <seb128> if that's useful
[09:36] <dpm> yes, thanks
[09:36] <seb128> "pkgstriptranslations: preparing translation tarball nautilus_3.6.3-0ubuntu14_i386_translations.tar.gz...dpkg-distaddfile: warning: File::FcntlLock not available; using flock which is not NFS-safe
[09:36] <seb128> done"
[09:37] <seb128> I guess the warning is harmless
[09:38] <dpm> seb128, looking at https://translations.launchpad.net/ubuntu/raring/+source/nautilus tells me that the PO files are being imported from the vcs imports branch ("This source package is sharing translations with Nautilus main series. "). Do you if that imports branch is up to date?
[09:38]  * dpm looks at https://translations.launchpad.net/nautilus/main
[09:38] <seb128> dpm, I've no idea, let me check
[09:38] <dpm> https://code.launchpad.net/~vcs-imports/nautilus/master-git
[09:39] <seb128> dpm, shrug
[09:39] <seb128> that's wrong
[09:39] <seb128> we are not on GNOME 3.8
[09:39] <seb128> but on 3.6
[09:39] <seb128> tracking trunk is a recipe for fail there :-(
[09:39] <seb128> is that common practice for GNOME sources?
[09:40] <seb128> seems to be :-(
[09:40] <dpm> seb128, I think the issue was that LP only allowed importing trunk from git, not individual branches. I'm not sure if that limitation is still there
[09:40] <seb128> it is
[09:41] <seb128> we did that to have translations directly imported from upstream git, right?
[09:41] <dpm> yeah, so that they did not need to be imported through package uploads, and get sucked from the bzr imports instead
[09:41] <seb128> k
[09:42] <dpm> but if that does not work, I guess I'll need to disable it for nautilus and go back to package uploads for translation imports
[09:42] <seb128> the assumption is less true since we stopped tracking GNOME
[09:42] <seb128> dpm, that's going to be an issue for other components as well
[09:42] <seb128> we are on 3.8 for none of GNOME
[09:43] <dpm> bummer, more manual tracking :/
[09:43] <seb128> it means that if any GNOME component changed strings in 3.6 to 3.8 we loose translations
[09:43] <dpm> fortunately, it does not seem to be much of an issue yet. I don't see many untranslated strings on my desktop
[09:44] <seb128> right, we got lucky
[09:44] <seb128> dpm, can you change nautilus ... and then do you need a new upload to import the po files?
[09:45] <dpm> seb128, let me check for how many templates we're tracking trunk first. We can disable message sharing for nautilus for a start. Do you have any nautilus upload queued up so that we can see if it imports the translations?
[09:45] <dpm> so yeah, we were thinking the same :)
[09:45] <seb128> dpm, I will do a nautilus upload, let me check what was pending for it
[09:45] <seb128> can you change the setting meanwhile?
[09:45] <seb128> dpm, thanks ;-)
[09:46] <dpm> seb128, sure, I'll need 5 minutes, and I'll ping you when done
[09:53] <dpm> seb128, ok, message sharing with nautilus trunk disabled. There doesn't seem to be too many gnome components we've got upstream sharing activated for, but I'll need some more time to look at the rest in more detail. For now, it should be good to go ahead with the nautilus upload so that we can see if the template and translations are imported in the queue
[09:53] <seb128> dpm, ok, thanks
[09:54] <Laney> I just ran out of disk space while trying to debdiff libreoffice
[09:54] <Laney> /o\
[09:56] <seb128> :-(
[09:56] <Laney> the curse of SSDs
[09:56] <ogra_> just pick goffice next time :P
[09:56] <Laney> probably don't need oneiric chroots any more
[10:28] <seb128> pitti, btw, I think we can turn apport off for raring at this point
[10:31] <pitti> seb128: errors.u.c. is enough, or no more interesting crashes?
[10:32] <seb128> pitti, both, I think we got the "interesting" issues reported in launchpad and that we are not getting a lot of new/useful one, and e.u.c is good enough for most of the work
[10:33] <pitti> seb128: let's ask foundations and server guys
[10:33] <seb128> right; I should have asked on #ubuntu-devel (or release), sorry
[10:38]  * Laney accepts libeoffice
[10:41] <chrisccoulson> lol, http://www.independent.co.uk/news/world/middle-east/iranian-scientist-claims-to-have-invented-time-machine-that-can-predict-the-future-8568147.html
[10:49] <seb128> Laney, thanks
[10:56] <davmor2> seb128: Woohoo! RB, notifications, indicator all have album art after removing the .local/share/rhythmbox folder, now a quick reboot and see if they appear in the dash too
[11:03] <davmor2> seb128: tantalisingly close, only the dash isn't displaying now, http://ubuntuone.com/6nkR0SFquDU4sSisvuO5h2
[11:04] <davmor2> oh and nautilus
[11:05] <davmor2> though that might be a removed feature maybe
[11:17] <seb128> davmor2, hey, dunno about the dash, check with mhr3 maybe
[11:17] <seb128> nautilus got a bug reported this morning
[11:18] <davmor2> seb128: awesome.  It nice to see it in the notifications and rhythmbox at least :)
[11:20] <davidcalle> seb128, davmor2, regarding the Rhythmbox Dash scope, album art will appear after Rbox updates its xml db file. Which happens... when closing it. This is AFAIK the only way to connect a track to its album art with Rbox.
[11:20] <davmor2> davidcalle: That could be an issue then
[11:21] <davidcalle> (the only way : when using Rbox XML db file as a source)
[11:25] <davmor2> davidcalle: right I've just gone through all the albums and ensured their art displayed.  I've now close RB and am rebooting for the dash to cache the changes
[11:26] <davmor2> Yay now I have album art in the dash woohoo
[11:27] <davmor2> seb128: so it looks like RB db only gets the art when a track is played so the dash now has album art too :)
[11:32] <seb128> davmor2, ok, that used to be this way
[12:31] <marga> Hey all, I'm trying to add my own icons to a custom indicator.  This is supposedly possible by using the icon-theme-path property.  However, I only want to add 5 icons, not create a whole theme... I tried creating a theme that "Inherits" from another theme, but failed... Can anyone point me to some docs about this?
[12:43] <seb128> marga, hey, can't you just ship your icons in /usr/share/custom_indicator/hicolors/... and add that dir to the icondirs?
[12:45] <marga> probably, I'm just working blindly here, since the docs I've found up to now aren't very helpful.
[12:45] <marga> What do you mean by "add that dir to the icondirs"?
[12:54] <seb128> marga, https://developer.gnome.org/gtk3/stable/GtkIconTheme.html#gtk-icon-theme-set-search-path
[12:55] <marga> seb128, tnx
[12:59] <marga> Seems to be working now, I'm not sure what I changed...
[12:59] <marga> Anyway, I've noticed that under Unity, the icons are quite small, whereas under cinnamon the are too big... Is there any way I can control that?
[13:12] <desrt> oh wow
[13:12] <desrt> nss-myhostname is in main now?
[13:12] <desrt> awesomeness
[13:13] <seb128> is there really user changing their hostname?
[13:13]  * seb128 never did that to a machine
[13:13] <desrt> everyone i know names their laptop :)
[13:14] <desrt> anyway... i just talked to lennart and he agreed to add a feature to nss-myhostname that will make it actually useful:
[13:14] <desrt> resolving localhost <=> <IP_ADDRESS>
[13:14] <desrt> because now we can erase /etc/hosts
[13:17] <stgraber> desrt: you mean localhost <=> ::1, <IP_ADDRESS> right?
[13:18] <desrt> yes.  of course.
[13:18] <stgraber> otherwise you're going to seriously break stuff on my laptop ;)
[13:18] <desrt> every time we delete a file in /etc i get very happy
[13:18] <mdeslaur> desrt: you are insane, you know that, right? :)
[13:20] <seb128> desrt, hum, I named my laptop at installation, never felt the need to change the name after that
[13:20] <stgraber> desrt: however if you want to kill /etc/hosts you'll need a bit more than localhost in nss-myhostname
[13:20] <seb128> desrt, most people I know don't even know their machine has a name I think
[13:21] <desrt> stgraber: what else?
[13:21] <desrt> stgraber: note: i only want to kill /etc/hosts in the default install
[13:21] <desrt> if people want to have their own /etc/hosts then we must still support this
[13:21] <pitti> seb128: apart from "that f***ing machine which breaks so often"? :-)
[13:21] <seb128> pitti, indeed ;-)
[13:21]  * desrt has no problem with files being in /etc -- they should just not be there in the default install
[13:22] <stgraber> desrt: there are a bunch of ipv6 aliases you're supposed to have though we haven't been terribly consistent in putting those in /etc/hosts (I can't remember which of ubiquity or d-i do, but I believe one of the two is missed up)
[13:22] <stgraber> desrt: http://paste.ubuntu.com/5698437/
[13:22] <pitti> desrt: so you think NSS should have some sane defaults that include /etc/hostname?
[13:22] <desrt> pitti: yes.  absolutely.
[13:23] <pitti> a laudable goal; it never really occurred to me why one needs to explicitly configure "localhost" to be ::1/<IP_ADDRESS>
[13:23] <pitti> I figure a lot of things would break very badly if you change that
[13:23] <desrt> ya...
[13:23] <desrt> well
[13:23] <desrt> you can change it to 127.anything
[13:23] <pitti> on mine I even have *two* entries for ::1
[13:23] <desrt> which is kinda neat
[13:23] <desrt> using <IP_ADDRESS> as your hostname IP is probably the sanest thing to do on any kind of machine like a laptop
[13:24] <desrt> or <IP_ADDRESS> or however various people like to do it
[13:24] <stgraber> desrt: the stuff I copy-pasted is part of what netcfg writes when it creates /etc/hosts. I guess we have other things that create /etc/hosts and so causes the inconsistency...
[13:24] <pitti> ubiquity configured it as "<IP_ADDRESS>donald" here
[13:24] <desrt> ya
[13:24] <desrt> this is totally sane
[13:24] <stgraber> pitti: you're supposed to. localhost and ip6-localhost
[13:25] <stgraber> not that I've seen the ip6-* stuff used all that much
[13:25] <desrt> the other alternative is to update /etc/hosts every time you get a new dhcp lease...
[13:25] <desrt> which is kinda insane
[13:25] <desrt> although... nss-myhostname could probably do this
[13:25]  * desrt bugs lennart some more
[13:26] <stgraber> isn't it redhat that does the whole hostname+/etc/hosts update whenever you get a DHCP lease? I remember seeing some systems doing that and really disliked it
[13:26] <stgraber> as in, why would I let the network admin rename my machine? :)
[13:30] <desrt> stgraber: lennart says that if those things are supposed to be standardly available then he'll add them
[13:31] <desrt> and also: nss-myhostname already takes a local IP address as the IP for the hostname
[13:31] <desrt> and only uses <IP_ADDRESS> if nothing else is available
[13:32] <desrt> so.... win!
[13:41] <pitti> cyphermox: do you know an upstream compatible way (i. e. aside from adding to /e/n/i) to tell NM "don't touch this interface"?
[13:41] <cyphermox> pitti: nah
[13:41] <pitti> cyphermox: I was debugging why NM doesn't connect, and I think it's because NM shuts down the interface which has the AP
[13:41] <cyphermox> someone brought this up in a bug before
[13:41] <cyphermox> actually, YES!
[13:41] <cyphermox> in /etc/NetworkManager/NetworkManager.conf:
[13:42] <pitti> https://live.gnome.org/NetworkManager/SystemSettings has "unmanaged-devices"
[13:42] <pitti> ooh, wait
[13:42] <pitti> --config=/path/to/config.file
[13:42] <pitti> that's exactly what I need
[13:42] <pitti> I don't want to change the actual file in /etc/
[13:43] <stgraber> desrt (would ping jbicha but he's not around): can you point me to the FFe for libnss-myhostname? I just had a quick look and can find an MIR but not a matching FFe and that kind of last minute change definitely needs a FFe
[13:45] <stgraber> seb128: ^ (are you aware of any FFe for libnss-myhostname?)
[13:45] <stgraber> Laney: you too as you seem to like desktopy thing ;)
[13:45] <seb128> stgraber, bug #1162478
[13:45] <ubot2> Launchpad bug 1162478 in libnss-myhostname (Ubuntu) "[FFe] [MIR] libnss-myhostname" [Undecided,Fix released] https://launchpad.net/bugs/1162478
[13:45] <seb128> stgraber, see the title
[13:45] <stgraber> seb128: damn, I saw the report and missed the [FFe] bit
[13:46] <seb128> [FFe] [MIR]
[13:46] <stgraber> seb128: right, so nobody approved it
[13:46] <stgraber> seb128: I don't see a release team ack in there
[13:46] <seb128> indeed
[13:46] <stgraber> ok, I'll give it a release team nack then
[13:47] <seb128> haha
[13:47] <seb128> stgraber, you think it's risky?
[13:47] <seb128> but I'm fine with that
[13:47] <seb128> it's a bit late to introduce features
[13:48] <stgraber> seb128: yes, adding a default nss module to the desktop install two weeks before release is risky
[13:48] <stgraber> seb128: especially if it potentially messes with what IP additional services may end up listening on
[13:49] <seb128> stgraber, ack, let me revert that upload (note that I'm not the one who did the upload)
[13:49] <stgraber> (I'm not against myhostname but I want us to very carefully look at the impact before turning it on, and it's too late to do that now)
[13:49] <seb128> e.g I'm fixing it but I don't take the blame :p
[13:49] <stgraber> seb128: sure, I wanted to ping jbicha but he's not around. Can you make sure to close LP:#1162478 in the upload? I'll deal with it when it reaches the queue
[13:59] <cyphermox> pitti: yeah, so you want the no-auto-default=<mac address>  line in your config file
[13:59] <pitti> cyphermox: ah, what does that do? I used this now:
[13:59] <pitti>             f.write('[main]\nplugins=keyfile\n[keyfile]\nunmanaged-devices=mac:%s\n' % self.mac_ap)
[14:00] <cyphermox> well, that would work too
[14:00] <Nafallo> Laney: got the card. now the kernel is in my way... the crystalhd driver only registrers with the older hardware. probably just a one-liner to fix...
[14:01] <Nafallo> one-liner and figure out how to build that kernel driver without having to build 15 kernels on my netbook :-P
[14:01] <cyphermox> pitti: the other one is to avoid creating default automatic connections; you could use * to avoid NM enabling any new connected devices
[14:01] <pitti> cyphermox: it doesn't really say in the log, but it seems to work; at least it connects
[14:01] <cyphermox> great
[14:01] <pitti> cyphermox: ah, is that for connections or devices?
[14:01] <cyphermox> I think it only really says it when you start NM
[14:02] <cyphermox> no-auto-default is for devices, to not automatically make a DHCP connection for the device when it's detected
[14:02] <pitti> cyphermox: I did notice that my test still fails because it now immediately gets an active connection, even before I call self.nmclient.add_and_activate_connection()
[14:02] <cyphermox> unmanaged-devices will go one step further and avoid the device showing up, I think
[14:02] <pitti> cyphermox: i. e. it seems to immediately auto-connect to the AP
[14:02] <cyphermox> ok
[14:03] <pitti> cyphermox: I thought it would only do that for SSIDs it already saw before?
[14:03] <cyphermox> wifi should never be autoconnecting though, unless you already set up a connection for that AP before
[14:03] <pitti> cyphermox: right, that just made me wonder
[14:03] <cyphermox> it *has* to know the SSID already, with a connection file in /etc/NetworkManager/system-connections
[14:03] <pitti> right, but it doesn't
[14:03] <pitti> I explicitly remove them all in tearDown()
[14:04] <pitti> well, I'll have a closer look
[14:05] <pitti> hm, and it still logs stuff about the AP wlan interface, but it seems it ignores it enough to not interfere with hostapd
[14:07] <pitti> cyphermox: or perhaps I misunderstand the concept of NMActiveConnection
[14:08] <pitti> cyphermox: it seems I get one even if it didn't actually connect to that wifi yet?
[14:08] <cyphermox> it's impossible, there has to be a prior connection from somewhere
[14:08] <pitti> $ ls /etc/NetworkManager/system-connections/
[14:08] <cyphermox> wifi *cannot* come up by itself
[14:08] <pitti> $
[14:08] <pitti> hmm
[14:08] <pitti> cyphermox: oh, it does'nt
[14:09] <cyphermox> I believe you, just there has to be something else
[14:09] <pitti> cyphermox: but it creates an NMActiveConnection object and returns that in get_active_connections(
[14:09] <pitti> after setting up that conn, I get a second object there
[14:09] <desrt> stgraber: can you get me an RFC reference for those ip6- names?
[14:09] <pitti> which makes me believe the first one might be a "never connected" placeholder?
[14:09]  * pitti looks for some textual dump method
[14:09] <desrt> when i google those names i mostly find people having pasted their /etc/hosts file from ubuntu :)
[14:10] <cyphermox> pitti: I don't know
[14:11] <stgraber> desrt: let me see if I can find some reference in the netcfg git
[14:13] <pitti> cyphermox: indeed: http://paste.ubuntu.com/5698574/
[14:13] <pitti> cyphermox: "adding" means add_and_activate_connection()
[14:13] <Sweetshark> didrocks: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1085169 <- could you forward this one to the appindicator guys, as it seems to be a regression against quantal on their part?
[14:13] <ubot2> Launchpad bug 1085169 in indicator-appmenu (Ubuntu) "LibreOffice Menus Stop Working even with libreoffice>=1:3.6.2~rc2-0ubuntu4 and indicator-appmenu>=12.10.3-0ubuntu2.1" [Undecided,Confirmed]
[14:14] <cyphermox> pitti: ok
[14:14] <pitti> cyphermox: so the dummy one has nm_active_connection_get_specific_object () == NULL
[14:14] <cyphermox> pitti: sorry, I don't really understand what's going on there, and I'm very busy with hud atm
[14:14] <pitti> cyphermox: ok, sorry
[14:14] <pitti> I wish I could reach dcbw, he hasn't been on IRC for days and hasn't answered my mail
[14:17] <Sweetshark> didrocks: whops wrong bug
[14:18] <stgraber> desrt: tracked down the commit to http://anonscm.debian.org/gitweb/?p=d-i/netcfg.git;a=commitdiff;h=457c418d576957e6f2ba5f87612986455b18cf93
[14:21] <Sweetshark> didrocks: I was talking about this one: bug 1153350
[14:21] <ubot2> Launchpad bug 1153350 in indicator-appmenu (Ubuntu) "LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover" [High,Confirmed] https://launchpad.net/bugs/1153350
[14:22] <didrocks> cyphermox: mind poking the indicators team about it? ^
[14:22] <desrt> stgraber: looks pretty arbitrary
[14:23] <desrt> stgraber: what's your opinion on localhost <=> ::1
[14:24] <desrt> having ip6-localhost for ::1 seems very stupid imho
[14:24] <desrt> fwiw, fedora does something equally stupid and calls it localhost6
[14:25] <desrt> lol
[14:25] <desrt> they actually have localhost6.localdomain6
[14:25] <desrt> you know, just to be extra-sure
[14:26] <pitti> cyphermox: just one thing, could I ask you to add ubuntu-core-dev to ~network-manager?
[14:27] <stgraber> desrt: localhost should always resolve to ::1 and <IP_ADDRESS>. ip6-* should just be there as a convenience, I'm not sure anything actually relies on that but I'm still digging for the exact history
[14:27] <stgraber> desrt: it was added to ifupdown to match a much older change in netbase so I'm trying to track down the reason for the netbase one ;)
[14:28] <desrt> so on my ubuntu machine now, localhost doesn't give ::1
[14:28] <desrt> i have to ask for ip6-localhost for that
[14:28] <ogra_> does v6 allow similar aliasing as we do with <IP_ADDRESS> ?
[14:28] <desrt> ogra_: no.  it doesn't.
[14:28] <ogra_> ah
[14:28]  * ogra_ is v6 ignorant up to now
[14:28] <desrt> you can't do ::2 for example
[14:28] <desrt> that's why nss-myhostname tries very hard _not_ to hand out a loopback address for the local hostname
[14:29] <pitti> ogra_: Telekom has handed out IPv6 addresses for quite a while now :)
[14:29] <ogra_> yep
[14:29] <seb128> pitti, they broke landlines on the way I've been told :p
[14:29] <seb128> pitti, got yours fixed btw? ;-)
[14:29] <ogra_> pitti, i know ... but i plan to move on from my 2M SDSL soon :) so i wont bother to set anything up just now ;)
[14:29] <pitti> seb128: yeah, by completely resetting the router
[14:30] <pitti> seb128: the technician gave up as well, he couldn't find any error on his side
[14:30] <pitti> seb128: so, strange sw hiccup in the router
[14:30] <seb128> good old times when those machines were only wired logic
[14:31]  * ogra_ still uses an ubuntu router :) i usually insist to only get a modem
[14:31] <pitti> yeah, there's an infinite combination of setting up telephony (redirecting, etc.) on their web UI, IP telephony and device assignment in the router, spreading these out over classic analog, ISDN (S0 bus), SIP, and wifi, and configuring your numbers in the actual handset
[14:32] <pitti> first world problems :)
[14:32] <ogra_> oh, right, i also dont have a landline ... only network
[14:34] <stgraber> desrt: oh, interesting, so I guess it's my DNS server that's making "getent hosts localhost" return ::1 then...
[14:36] <pitti> stgraber: FWIW, I get "<IP_ADDRESS>       localhost.localdomain localhost" from that
[14:36] <pitti> stgraber: my /etc/hosts/ doesn't map ::1 to localhost
[14:37] <pitti> should it?
[14:37] <ogra_> # The following lines are desirable for IPv6 capable hosts
[14:37] <ogra_> ::1     ip6-localhost ip6-loopback
[14:37] <pitti> http://paste.ubuntu.com/5698637/
[14:37] <ogra_> you should have that in /etc/hosts
[14:38] <pitti> I do
[14:38] <pitti> but ip6-localhost != localhost
[14:38] <ogra_> yeah
[14:38] <ogra_> ask debian :)
[14:38] <ogra_> i think that one is just inherited
[14:42] <seb128> davmor2, ok, fixed totem uploaded for the nautilus thumbnail issue
[14:44] <davmor2> seb128: Cool I'm just filing some bugs currently, after I finish that I'll see if it has landed and try it out
[14:50] <stgraber> pitti: right, so it's probably my dns server returning the ::1 then
[14:51] <ubuntu631> hello all! can you help me?
[14:52] <ubuntu631> after wubi extracted all info on hard disk it reboot computer but after reload and choosing "ubuntu" it stuck
[14:53] <ubuntu631> after one more reload it loads grub . and nothing happens
[14:53] <seb128> ubuntu631, hi, try #ubuntu for user questions
[15:13] <cyphermox> pitti: yeah, doing now
[15:14] <cyphermox> pitti: done
[15:14] <pitti> cyphermox: splendid, thanks
[15:14] <cyphermox> yeah, that's going to make some of the work easier
[15:30] <attente> ricotz, hey
[15:32] <attente> for the vala-0.18 packaging, i can't seem to get it to regenerate the gio-2.0.vapi properly from the corresponding gir which is in /usr/share/gir-1.0
[15:32] <attente> is there something special that needs to be done?
[15:32] <ricotz> attente, hi, you can't just simply generate it from the gir
[15:33] <ricotz> there are a lot of fixing (metadata) needed for it
[15:33] <ricotz> i would recommend to use vala 0.20.x if you need an up2date gio binding
[15:34] <attente> if i simply replace the vapi though, won't i get uncommitted source errors when packaging?
[15:35] <ricotz> attente, what are you trying to do?
[15:37] <ricotz> the bindings are not built in vala build process, there are generated upstream occasionally
[15:37] <attente> i'm trying to update /usr/share/vala-0.18/vapi/gio-2.0.vapi to add definitions from /usr/share/gir-1.0/Gio-2.0.gir which is provided by libgirepository1.0-dev
[15:37] <attente> ricotz, so is the correct thing to do to add a debian/patches patch for this?
[15:39] <ricotz> attente, kind of, yes
[15:39] <ricotz> but vala 0.20 is the matching version for glib 2.36
[15:40] <attente> ricotz, thanks
[15:41] <seb128> vala 0.20.1 is in raring NEW btw
[15:41] <seb128> just need an archive admin to review it
[15:43] <ricotz> seb128, good, this is better way to get up2date bindings ;)
[15:43] <ricotz> attente, ^
[15:43] <pitti> cyphermox: FYI, I solved the mystery -- that ActiveConnection object was for eth0 (which kvm sets up)
[15:44] <ricotz> seb128, hi, is the valencia gedit plugin working for you?
[15:46] <seb128> ricotz, not sure, I don't do lot of vala and don't know how the plugin is supposed to work
[15:47] <seb128> ricotz, I tried before upload with shotwell, I opened a source, selected a method, pressed f12 and it did display a progress bar and opened a tab where the method was defined
[15:47] <seb128> that's the only basic testing I did
[15:47] <ricotz> seb128, ok, i gave it a try and it fails to load in gedit 3.8
[15:48] <ricotz> seb128, ok
[15:48] <seb128> ah
[15:48] <seb128> works in 3.6
[15:48] <seb128> nautilus 3.8 seems to be really unstable btw
[15:48] <seb128> e.u.c has quite some issues from 3.7~raring and 3.8~raring
[15:49] <seb128> lot of entries compared to 3.6 from the distro (especially that there are probably less users of the ppa than users from the stock distro)
[15:49] <ricotz> i see, nautilus works fine afaics
[15:49] <seb128> errors.ubuntu.com tells us it doesn't
[15:49] <ricotz> ok ;)
[15:49] <seb128> or at least from a statistical view
[15:50] <seb128> the bug rate is much higher than it was in 3.4 and 3.6
[15:50] <ricotz> i am more having hard time with the kernel, than with gnome
[15:57] <seb128> dpm, did the nautilus import work?
[15:58] <seb128> dpm, oh, they are in the queue as "Needs Review"
[15:58] <seb128> dpm, https://translations.launchpad.net/ubuntu/raring/+source/nautilus/+imports
[15:58] <seb128> dpm, is there any action needed? or just waiting?
[16:00] <dpm> seb128, ah, cool. In that case, we should just wait and they should get imported. If they haven't by tomorrow morning, I'll look into it, but they should import automatically
[16:00] <seb128> dpm, ok, thanks
[16:01] <dpm> I've approved it just in case, so that should make double sure it gets imported :)
[16:14] <dpm> mhall119, didrocks, you were asking about it yesterday, I think: the SDK API docs are now up-to-date as of today's trunk: http://developer.ubuntu.com/api/ubuntu-12.10/qml/mobile/overview-ubuntu-sdk.html
[16:14] <didrocks> dpm: excellent news! thanks
[16:14] <didrocks> dpm: can you close the bug, please?
[16:15] <dpm> didrocks, I don't recall the bug. Was it against ubuntu-ui-toolkit?
[16:15]  * dpm looks for it
[16:16] <mhall119> thanks dpm
[16:19] <dpm> didrocks, ah, I think you meant the bug against the tutorial, that's still wip
[16:20] <didrocks> dpm: yeah, it's the tutorial
[17:02] <cyphermox> seb128: uploading evo now.
[17:02] <seb128> cyphermox, thanks
[17:03] <cyphermox> going to get lunch now, bbl
[17:57] <jcastro> robru: http://askubuntu.com/questions/279971/how-to-add-support-for-new-services-to-friends
[17:58] <jcastro> man dude, that is an _excellent_ example of being awesome.
[18:02] <robru> jcastro, thanks ;-)
[18:03]  * didrocks waves good evening
[18:47] <Sweetshark> larsu, tedg: are you aware of bug 1153350? as this happens with LO4 on Raring, but not on Quantal with the same version it seems like an appmenu release-regression ...
[18:47] <ubot2> Launchpad bug 1153350 in indicator-appmenu (Ubuntu) "LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover" [High,Confirmed] https://launchpad.net/bugs/1153350
[18:48] <tedg> Sweetshark, We were talking about it.  attente said he couldn't reproduce it.
[18:48] <seb128> Sweetshark, ... ^W what tedg said
[18:48] <seb128> Sweetshark, can you reproduce it?
[18:48] <seb128> works fine here
[18:50] <Sweetshark> seb128: hmm, I can reproduce it (but I dont use the default theme) ...
[18:50] <seb128> Sweetshark, do you use the default desktop environment? ;-)
[18:50] <Sweetshark> seb128: for testing unity? uhm, yeah ;)
[18:51] <seb128> Sweetshark, and you get the bug there too? :p
[18:52] <Sweetshark> seb128: yes, also switching back from radience to ambience -- still seeing the issue.
[18:54] <Sweetshark> seb128: I have to admit though, that I use a LO version from the PPA right now (or a selfbuild one), but there are comment from people using the plain vanilla version seeing it too.
[18:55] <Sweetshark> checking with the guest session: see the bug there too (just to check if I broke my profile somehow)
[18:57] <Sweetshark> s/plain vanilla/13.04-beta/
[18:59] <Sweetshark> of course, if you do cant reproduce the issue, this might be a heisenbug (fun!) and the conclusion from https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1153350/comments/10 would be premature :/
[18:59] <ubot2> Launchpad bug 1153350 in indicator-appmenu (Ubuntu) "LibreOffice4 Global Menu Items Do Not Highlight on Mouse Hover" [High,Confirmed]
[19:01] <Sweetshark> (in case it matters: all on amd64)
[19:04]  * Sweetshark checks on a virgin VM installed from raring daily
[19:35] <Sweetshark> tedg, seb128: I just installed fresh VM from the amd64 daily (plus updates) and can reproduce it there -- no orange highlight in LO menus ...