[08:34] <melodie> hello there!
[08:35] <melodie> I have installed an Ubuntu Precise on a machine such as this one: http://h20566.www2.hp.com/portal/site/hpsc/public/psi/swdHome/?cc=us&cc=us&lang=en&lang=en&sp4ts.oid=3559772&ac.admitted=1412843494815.876444892.199480143
[08:35] <melodie> "HP Compaq dc7800 Base Model Small Form Factor PC"
[08:35] <melodie> and when using the default kernel, 3.2.0-69, the machine does not shutdown. Instead, it reboots
[08:36] <melodie> when I installed the latest available kernel 3.13.xyz, the shutdown stays shut down. My question is: should I report it as a bug?
[08:36] <melodie> you know reporting bugs the right way can be quite time greedy, so I wanted to ask if this would be worth reporting. What do you think?
[08:39] <RoyK> I don't think I would have bothered
[08:40] <melodie> hi RoyK
[08:41] <RoyK> hi
[08:42] <melodie> if I report I might use some time then the bug report not even considered, if the devs thinks it's not worth seeking for what's missing while another kernel can do it. just the other kernel won't be automatically updated I think, because it's not the main one used in that edition
[08:44] <RoyK> just report it - 3.2 is a long-term-support kernel release
[08:45] <RoyK> but then again - ACPI are complex stuff, so it might not be easy to backport the fix
[09:00] <melodie> RoyK I know acpi is complex. I have been looking at the bios updates available, there are some, but I don't feel like using them either, for one acpi isn't mentioned in the list of new features, (which I know is not significant anyway) and for two it has to be prepared on a dos environement (floppy or usb stick) and I'm not keen with doing that kind of thing, (I mean preparing, following the instructions, which are long, and in English which i
[09:00] <melodie> s not my native language, so it's "a bummer")
[09:01] <melodie> well I'll report it later today.
[09:01] <melodie> I'll ssh to the machine to get all information from the hardware and get it easily.
[09:01]  * RoyK doesn't really miss the DOS days either
[10:22] <melodie> RoyK for a bug report for this issue, are 'lspci -v' ; cpuinfo, and lshw enough?
[10:22] <melodie> as far as you know? :D
[10:43] <RoyK> melodie: lshw output is more verbose, perhaps that plus lspci -vv - not sure - I'm not a kernel hacker
[11:28] <melodie> RoyK ok, thanks
[11:41] <RoyK> melodie: perhaps add another -v to lspci
[11:43] <melodie> RoyK ok will do
[11:43] <melodie> have to run, bye :)
[11:45] <Orphis> Hi there!
[11:46] <Orphis> I'd like to shine some light on a bug in dbus-cpp: https://bugs.launchpad.net/dbus-cpp/+bug/1378807
[11:46] <ubot5> Ubuntu bug 1378807 in dbus-cpp "Crash in core::dbus::Object::get_signal" [Undecided,New]
[11:47] <Orphis> I'm working for Spotify and trying to improve Linux support and this issue is preventing us from implementing proper media key support in the client. We tried alternative libraries too, but they are mostly unmaintained and don't work at all for us
[11:48] <Orphis> If somebody could look at it, it would certainly help us release a newer version of the Linux client sooner!
[11:49] <ogra_> Orphis, you might find the more intteresting people who know dbus-cpp in #ubuntu-app-devel or #ubuntu-touch
[11:49] <Orphis> Alright, thanks!
=== roadmr is now known as roadmr_afk
=== roadmr_afk is now known as roadmr