[02:53] <Licuadora> A strange thing is happening to me... or to my PC
[02:54] <Licuadora> After a power surge failure, I cannot acces the interne via cable, the weird part is, it worked with a Ubuntu Live cd 8.04, but not with 10.04
[02:54] <Licuadora> y is a driver issue
[02:55] <Licuadora> Some say
[02:55] <Licuadora> Well, how do i upgrade all my drivers?
[02:55] <Licuadora> I reinstalled the kernel, but still, does not detect the cable
[02:56] <virtuald> licuadora: try running ifdown eth0;ifup eth0 as root
[02:58] <Licuadora> vituald: root@djiin:~# ifdown eth0;ifup eth0
[02:58] <Licuadora> ifdown: interface eth0 not configured
[02:58] <Licuadora> Ignoring unknown interface eth0=eth0.
[02:59] <virtuald> so did it work?
[02:59] <Licuadora> virtuald: Whats your diagnosis?
[02:59] <virtuald> i'm not a doctor :p
[03:00] <Licuadora> Well, it output that, a few lines up
[03:00] <Licuadora> eth0 not configured
[03:00] <virtuald> ok, then i have no idea
[03:00] <Licuadora> hm...
[03:01] <Licuadora> What was tha command suposed to do?
[03:01] <virtuald> to bring down and then up your first ethernet interface
[03:01] <virtuald> it works sometimes
[03:02] <Licuadora> Do you know how to configure it?
[03:02] <virtuald> yes in /etc/network/interfaces
[03:02] <Licuadora> What do i do there?
[03:03] <Licuadora> auto lo
[03:03] <Licuadora> iface lo inet loopback
[03:03] <Licuadora> Thats whats in there
[03:03] <virtuald> ok
[03:03] <virtuald> try adding
[03:03] <virtuald> auto eth0
[03:03] <virtuald> inet eth0 inet dhcp
[03:03] <virtuald> then run ifup eth0 again
[03:04] <virtuald> oops
[03:04] <virtuald> iface eth0 inet dhcp
[03:04] <virtuald> so don't put inet .. inet there
[03:05] <Licuadora> All in one line, or as it is?
[03:06] <Licuadora> I am about to save it
[03:06] <virtuald> two lines
[03:06] <virtuald> auto eth0
[03:06] <Licuadora> got it
[03:06] <virtuald> iface eth0 inet dhcp
[03:06] <virtuald> save and run ifup eth0
[03:06] <virtuald> i have food on the stove
[03:07] <virtuald> afk
[03:07] <Licuadora> root@djiin:~# ifup eth0 ifdown eth0
[03:07] <Licuadora> Internet Systems Consortium DHCP Client V3.1.3
[03:07] <Licuadora> Copyright 2004-2009 Internet Systems Consortium.
[03:07] <Licuadora> All rights reserved.
[03:07] <Licuadora> For info, please visit https://www.isc.org/software/dhcp/
[03:07] <Licuadora> Listening on LPF/eth0/00:1c:c0:6b:03:c9
[03:07] <Licuadora> Sending on   LPF/eth0/00:1c:c0:6b:03:c9
[03:07] <Licuadora> Sending on   Socket/fallback
[03:07] <Licuadora> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 4
[03:07] <Licuadora> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
[03:08] <Licuadora> I hope that means is working
[03:11] <Licuadora> NA, it didnt worked... *sigh*
[03:15] <Licuadora> http://ubuntu.pastebin.com/9004uBXJ
[09:00] <njin> hello guys, i've got a question
[09:02] <micahg> !ask | njin
[09:02] <ubot2> njin: Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)
[09:03] <njin> sorry, i've read not well the bug :-(
[09:13] <micahg> njin: do you need help with something?  I'm about to go to sleep
[09:13] <njin> micahg:no, thanks and good sleep
[10:27] <njin> yofel: hello
[10:32] <njin> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-keyboard/+bug/408686 is a bug in the window manager ?
[10:32] <ubot2> Ubuntu bug 408686 in xserver-xorg-input-keyboard (Ubuntu) "Cannot move task bar (panel) after changing "movement key" in Window Preferences (affects: 1) (heat: 8)" [Undecided,Incomplete]
[13:01] <zaytsev> Hey folks
[13:01] <penguin42> hi
[13:01] <zaytsev> Is there any reason why one wouldn't be able to mark a launchpad bug as wontfix?
[13:02] <zaytsev> The option just seems to be grayed out
[13:03] <gorilla> zaytsev: Yes, it generally not the right option to select. Which bug are we talking about here?
[13:03] <zaytsev> gorilla, I am triaging bugs for Midnight Commander
[13:03] <zaytsev> I will look up an exact bug numbers
[13:04] <gorilla> Wontfix is can only be set by Bug Squad leaders.
[13:04] <zaytsev> gorilla, ah, it explains it all
[13:04] <zaytsev> gorilla, the fact that I am the maintainer of the package doesn't matter?
[13:05] <gorilla> zaytsev: Hmmm. I'm not sure in that case.
[13:05] <zaytsev> This is one such example
[13:05] <zaytsev> https://bugs.launchpad.net/ubuntu/+source/mc/+bug/301328
[13:05] <ubot2> Ubuntu bug 301328 in mc (Ubuntu) "midnight commander aggregate patch (heat: 8)" [Undecided,Invalid]
[13:05] <zaytsev> For me the option is just greyed out
[13:05] <zaytsev> This is another one
[13:05] <zaytsev> https://bugs.launchpad.net/ubuntu/+source/mc/+bug/380830
[13:05] <ubot2> Ubuntu bug 380830 in mc (Ubuntu) "mc from hardy crashes when tryied to open bad *.cpio (heat: 2)" [Undecided,Invalid]
[13:05] <zaytsev> I didn't want to close them as invalid because it does not really fit into the context
[13:05]  * penguin42 kicks lp to get a move on
[13:06] <zaytsev> The patch for instance is for most parts upstreamed and reporter doesn't want or is unable to help to determine what is left and upstream it. So this sounds like a wontfix in most other BTSs
[13:06] <gorilla> zaytsev: fair enough.
[13:08] <zaytsev> The other one is indeed fixed in Interpid but not Hardy, but the package in not going to be backported, so in reality the bug is valid and was fixed in a newer Ubuntu, but it's a wontfix for Hardy
[13:17] <njin> hello, we support gOS ?
[13:20] <njin> it uses ubiquity, then i suppose that is a derivate
[13:22] <njin> then is a Package not provided by Ubuntu
[13:26] <njin> can someone help with this https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-keyboard/+bug/408686 , with super+leftclick windows can be grabbed, but the panel no.
[13:26] <ubot2> Ubuntu bug 408686 in xserver-xorg-input-keyboard (Ubuntu) "Cannot move task bar (panel) after changing "movement key" in Window Preferences (affects: 1) (heat: 8)" [Undecided,Incomplete]
[13:27] <penguin42> njin: I'd ask Bryce since he was the last to change it back to incomplete
[13:30] <njin> penguin42: thanks, i don't change the status because i'm not sure on assigning to xserver o metacity
[13:31] <penguin42> or possibly the panel
[13:31] <njin> yes
[13:31] <njin> but with alt+mouse it work
[13:32] <njin> why don't work with super+mouse ?

[13:34] <njin> strange
[13:35] <njin> penguin42 have a good breakfast
[13:35] <yofel> is compiz being used? that has it's own settings for that too I think (didn't read the bug
[13:35] <yofel> )
[13:35] <njin> yofel: in compiz and metacity
[13:36] <yofel> hm, then I don't know, it's been a while since I used compiz or metacity, and I always used alt

[14:14]  * penguin42 doesn't have a super button on this keyboard
[14:18] <devildante> hi all :)
[14:25] <njin> penguin42: have you got a hole instead ?  ;-)
[14:26] <penguin42> njin: Pretty much - this keyboard was made before those keys were added
[14:28] <njin> ah good keyboard then
[14:28] <penguin42> Model M
[14:29] <njin> manufacturer?
[14:30] <penguin42> IBM Model M - google it, it's a well known model
[14:31] <njin> penguin42: normally a cdlive work or not with touchscreen ?
[14:31] <penguin42> dunno, not tried a touchscreen
[14:31] <njin> i too
[14:32] <penguin42> they're getting common, so if it doesn't it should
[14:49] <penguin42> anyone using compiz+gnome that can try and reproduce a bug?
[14:50] <BUGabundo> I'm on mavericj
[14:50] <penguin42> so am I
[14:50] <penguin42> but I don't think the guy who reported this is
[14:50] <penguin42> bug 617740
[14:50] <ubot2> Launchpad bug 617740 in ubuntu "If something changes on a Gnome panel (e.g. window closes or opens), the panel raises above screensaver (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/617740
[14:51] <penguin42> it's potentially quite nasty; but it doesn't happen for me (Maverick+metacity)
[14:52] <penguin42> hmm actually he's using rss-glx not the standard gnome-screensaver
[14:53] <penguin42> oh and the screensaver he uses actually kills me xserver - Radeon bug I guess
[15:04] <devildante> penguin42: can't reproduce the bug with compiz (at least with the "Take a screenshot" thingie)
[15:06] <penguin42> devildante: How about something like sleep 10; xterm    and then screen lock ?
[15:06] <devildante> penguin42: wait, I didn't have a window list, but docky
[15:07] <devildante> penguin42: retrying with window list
[15:11] <devildante> penguin42: didn't work
[15:11] <devildante> penguin42: no matter what I do, I can't reproduce this bug
[15:12] <penguin42> well, that's good in a way - if it affected everyone it would be pretty serious - but there again I assume he's not just making it up - hmm I wonder how to help
[15:12] <devildante> penguin42: maybe it's because of rss-glx
[15:12] <devildante> ?
[15:13] <penguin42> I've tried installing rss-glx; it just adds some extra creensavers
[15:14] <devildante> penguin42: so rss-glx doesn't replace gnome-screensaver?
[15:14] <penguin42> doesn't seem to, it just seems to add new hacks
[15:19] <devildante> penguin42: even with a screensaver (i.e not just a black screen), it doesn't work
[15:31] <penguin42> I've flipped the package to gnome-screensaver - I reckon it's the one that's supposed to make sure everything stays out of the way
[15:35] <devildante> penguin42: is he running lucid or maverick?
[15:36] <penguin42> hmm I'd say Maverick actually based on the gnome-screensaver version
[15:38] <devildante> penguin42: running Maverick too. maybe we should ask him for a video recording? (I don't know if recordmydesktop would work when locking)
[15:39] <penguin42> devildante: Maybe, but 1) I think it's pretty clear what he's saying happens and 2) as you say I doubt the recorders would work with lock
[15:45] <devildante> penguin42: just tested, it seems recordmydesktop works when locking, even showing the screensaver you set! sweet :p
[15:45] <devildante> penguin42: if he records his problem, maybe we'll see something that can guide us
[15:46] <penguin42> oh cute, feel free to add that to the bug
[15:49] <devildante> penguin42: done :) but why is it cute? :P
[15:49] <penguin42> I really hadn't expected recordmydesktop to survive the screenlock
[15:50] <devildante> penguin42: it even shows the screensaver you put, so it is super-sweet!
[16:13] <njin> help https://bugs.launchpad.net/ubuntu/+bug/408914 I presume that the bug is valid, in fact in fdisk under the Boot of the 250GB (sdc) we see * 1 and under the first of 1 TB (sda)we can see * 2 or i'm wrong ?
[16:13] <ubot2> Ubuntu bug 408914 in ubuntu "SATA drives identified in wrong order (affects: 1) (heat: 8)" [Undecided,Incomplete]
[16:31] <devildante> njin: I *think* you can't rely on order for hard drives if you don't use UUIDs. but I'm not sure about that, so ask someone else :)
[16:33] <njin> devildante: thanks, today is a day of orrrrrrible bugs.
[16:36] <penguin42> drive order is undefined
[16:37] <njin> penguin42: then what you mentor ?
[16:37] <penguin42> ?
[16:38] <njin> penguin42: i don't know what to do with this bug
[16:38] <penguin42> njin: If you don't know what to do with a bug it's fine to leave it alone
[16:39] <njin> penguin42: ok, thanks
[16:42] <penguin42> njin: I think the right thing to do with it would be to assign it as a dupe of 569645
[16:42] <njin> penguin42: looking
[16:43] <penguin42> I put a comment on that a while ago
[16:43] <devildante> typing bug 569645 here because I'm too lazy :p
[16:43] <ubot2> Launchpad bug 569645 in ubuntu "10.04RC system boot random assignment of sda, sdb (affects: 3) (heat: 41)" [Undecided,New] https://launchpad.net/bugs/569645
[16:43] <penguin42> the bug is similar to the bug I originally reported as bug 261178
[16:43] <ubot2> Launchpad bug 261178 in linux (Ubuntu) "[intrepid] Random order of disk detection (heat: 5)" [Medium,Expired] https://launchpad.net/bugs/261178
[16:44] <penguin42> but I think the idea is that initialisation is now done in parallel, and if you have multiple controllers you get pretty random definitions of the /dev/sd*
[16:46] <njin> penguin4222: strike again
[16:47] <njin> penguin42:strike again
[16:48] <penguin42> heck, that bug is almost exactly 2 years old :-)
[16:49] <penguin42> njin: So, the important thing is that while sda, sdb etc isn't important, it IS important that things work correctly in the installer/boot loader, and that nothing still uses sda etc
[16:50] <njin> true
[16:52] <penguin42> it was a bit unexpected when it first appeared though
[16:53] <penguin42> it took me ages to figure out why my RAID wasn't starting up reliably
[18:17] <xelister> https://bugs.launchpad.net/ubuntu/+source/krusader/+bug/481198
[18:17] <ubot2> Ubuntu bug 481198 in krusader (Ubuntu) (and 1 other project) "Krusader always crash on start after todays upgrade of system (ubuntu 9.10) (affects: 1) (heat: 8)" [Medium,Triaged]
[18:17] <xelister> I solved the almost year old bug where krusader always crashes
[18:17] <xelister> lets push the patch upstream?
[18:18] <xelister> its a trivial oneliner
[18:19] <penguin42> xelister: Have you mailed the package owner or attached your patch to the bug?
[18:20] <xelister> no
[18:20] <micahg> xelister: have you tested with KDE 4.5
[18:20] <yofel> according to the last commenst on kde bug 191167 this seems fixed
[18:20] <ubot2> KDE bug 191167 in general "Krusader crashes at startup (PanelManager::slotChangePanel, KrusaderView::start)" [Crash,Unconfirmed] http://bugs.kde.org/show_bug.cgi?id=191167
[18:20] <yofel> *comments
[18:21] <penguin42> xelister: Often their quite happy to put little fixes in or push them upstream
[18:22] <penguin42> xelister: It varies a bit depending on the maintainer etc
[19:37] <xelister> yofel: well it is broken in lucid proposed, why not push NOW this trivial fix to help thousand of users right today
[19:38] <yofel> well, sure, package your patch, do the SRU work
[19:38] <yofel> and usually send the patch upstream, but that might not be necessary in this case
[19:38] <yofel> you could check if it happens with the upstream devel version
[19:38] <xelister> yofel: I attached the patch, anything more?
[19:38] <xelister> http://launchpadlibrarian.net/53767856/krusader_2.0.0-1ubuntu4.debdiff
[19:39] <yofel> for one, you can't upload it to lucid but only to lucid-proposed, after that follow https://wiki.ubuntu.com/StableReleaseUpdates
[19:40] <xelister> I dont have any write access
[19:40] <yofel> maybe ping someone in #ubuntu-motu or #kubuntu-devel if they have time to review it
[19:40] <micahg> xelister: the SRU process describes sponsorship
[19:41] <micahg> xelister: if you need review, subscribe ubuntu-reviews
[19:41] <xelister> +	 if (!(leftActiveTab < leftTabTypes.size())) { leftActiveTab=0; } // fix bug LP: #481198
[19:41] <xelister> long review ;)
[19:45] <yofel> now let's see if that still happens in maverick..
[19:47] <yofel> xelister: it crashes always on start? anything more to be done to reproduce it?
[19:48] <xelister> yofel: you can simulate the bug as described
[19:48] <xelister> edit .kde/share/config/krusaderrc
[19:48] <xelister> set  Right Active Tab=99
[19:49] <xelister> and run krusader.  Sometimes krusader set such out of range variable on its own and then it cant be started untill manually edit or remove the config file above
[19:49] <yofel> ok, doesn't crash on maverick, I'll set the bug to fix released
[19:49] <xelister> really doesnt crash?
[19:50] <xelister> fucking amazing, after just 1 year =)
[19:50] <yofel> maverick has 2.2.0-beta1 currently, and the code you fixed was completely rewritten in the upstream source, so I guess the crash reason went to the grave with the old code :P
[19:50] <micahg> !coc | xelister
[19:51] <ubot2> xelister: The Ubuntu Code of Conduct is a community etiquette document to which we ask all Ubuntu users to adhere, and can be found at http://www.ubuntu.com/community/conduct/ .  For information on how to electronically sign the CoC, see https://help.ubuntu.com/community/SigningCodeofConduct .
[19:51] <xelister> !americans_and_europeans_worying_too_much_about_words_and_moral_panic | micahg
[19:51] <ubot2> xelister: Error: I am only a bot, please don't think I'm intelligent :)
[19:51] <yofel> doesn't matter, channel policy
[19:51] <xelister> oh well, perhaps another bug that I fix will be actually needed :)
[19:54] <micahg> !language is the correct factoid....
[19:55] <yofel> xelister: can you do the SRU? fixing it in lucid would be nice
[19:57] <xelister> perhaps we should make my factoid for ballance?
[19:59] <crimsun_> I'm with yofel; it should be fixed in 10.04 LTS
[19:59] <crimsun_> quite a few of us present can assist you with an SRU
[19:59] <xelister> well how to do it?
[20:00] <yofel> xelister: did you read the link I gave you?
[20:00] <yofel> please do that first
[20:01] <penguin42> anyone know if there are any specific things for debugging X crashes - i.e. do I have to stop X doing the backtrace?
[20:01] <crimsun_> there's a wiki page (or set of) for that IIRC
[20:02] <yofel> if you have a frozen X, there is https://wiki.ubuntu.com/X/Troubleshooting/Freeze
[20:02] <yofel> and generally the X/Troubleshooting wiki section
[20:03] <penguin42> this is a seg not a hang
[20:04] <yofel> not sure, usually apport should catch segv
[20:05] <penguin42> oh it has, and it's got a nice juicy backtrace - I wondered what the best way to attack it was; I can take gdb to it, but I wondered if there were any X specific debug tricks
[20:09] <penguin42> ahha https://wiki.ubuntu.com/X/Backtracing
[20:14] <xelister> yofel: nope, Im bussy with 2 girls
[20:14] <xelister> and then I have job
[20:14] <xelister> perhaps in upcoming days when I have vacation though
[20:14] <crimsun_> xelister: which bug are you referring to? I'll try to pop in and help if I can.
[20:14] <penguin42> sheesh, you're putting your job and sex life before debugging out bugs?
[20:14] <penguin42> sorry, lives
[20:15] <xelister> penguin42: bug is debugged, I dont like the beaurucracy stuff todo
[20:15] <yofel> crimsun_: bug 481198
[20:15] <ubot2> Launchpad bug 481198 in krusader (Ubuntu) (and 1 other project) "Krusader always crash on start after todays upgrade of system (ubuntu 9.10) (affects: 1) (heat: 10)" [Medium,Fix released] https://launchpad.net/bugs/481198
[20:15] <micahg> xelister: process is easy once you get used to it
[20:15] <xelister> well "debugged", it took entire 2 minutes to fix
[20:16] <crimsun_> yofel: / xelister: thanks, I'll look after I upload a new sawfish SRU candidate in a few moments
[20:16] <yofel> thanks :)
[20:16] <xelister> micahg: ok so I know what to change in source, and how to make debdiff.. now what?  also, how to make a clean debdiff, it somehow shows me a diff of 1st try to fix it and the last one,  instead of original
[20:18] <micahg> xelister: the SRU page gives a list of steps
[20:18] <micahg> xelister: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
[20:19] <micahg> xelister: the only thing missing is that you subscribe ubuntu-sponsors now and they upload and subscribe ubuntu-sru
[20:20] <yofel> so the right procedure now is to first subscribe sponsors?
[20:22] <micahg> yofel: yeah, now -sru prefers to review in uload queue
[20:22] <micahg> *upload
[20:23] <yofel> micahg: can you fix the wiki page then, it still says to subscribe sru
[20:23] <micahg> yofel: k
[20:23] <yofel> thx :)
[20:28] <micahg> yofel: well, the email says to subscribe ubuntu-sru and then upload or subscribe sponsors
[20:28] <micahg> I guess I should revert the change...
[20:29]  * micahg goes and asks
[20:33] <njin> yofel: heve you received requests from QA to testing iso today ?
[20:41] <penguin42> anyone understand what the difference between the -dbg packages ('This package provides debugging symbols...' and the -dbgsym package is?
[20:45] <crimsun_> historically (and generally), -dbg are specified in debian/control explicitly and built with nostrip, etc.
[20:45] <crimsun_> -dbgsym are generated "automatically" on the buildds
[20:46] <crimsun_> someone more familiar with pkg* on the buildds could clarify/correct further
[20:47] <penguin42> hmm well if I have both to choose from is there any particular one is more useful?
[20:47] <crimsun_> I tend to choose the latter when available
[20:47] <penguin42> the -dbgsym?
[20:48] <crimsun_> yes
[20:48] <penguin42> ok
[20:51] <yofel> njin: for the kubuntu ones I'm subscribed to no
[20:53] <yofel> crimsun_: actually you're right -dbg needs to be specified in control and dh_strip redefined whereas the (official!) buildds create -dbgsym packages for all packages that are built
[20:53] <yofel> also -dbg is afaik for the whole source package whereas -dbgsym is built for every binary package
[20:54] <yofel> and the last difference I can think of right now is that -dbg packages are in the primary archive while -dbgsym packages are on ddebs.ubuntu.com
[20:54] <yofel> penguin42: ^
[20:55] <yofel> usually -dbgsym packages are preferable as every package has one, but note that -backports and PPAs don't have -dbgsym packages
[20:55] <penguin42> yofel: When you have a source package and do a debian/rules binary it's built me the .debs but hasn't build the -dbg - the unpacked directories are in the build directory but it hasn't built a .deb
[20:56] <njin> yofel: strange, i've received two request (yesterday and today) to test ubuntu amd64 (20100814 and 20100815) coming from QA Testing Tracker <qatracker@stgraber.org> but these images dont exists (latest is 20100812)
[20:57] <yofel> penguin42: well, what package and does that package have a -dbg package?
[20:57] <yofel> there is no -dbg package by default
[20:58] <penguin42> yofel: xserver-xorg-video-radeon and I can see it calls dh_strip passing a flag to produce a -dbg and I can see the files that make up the package in the build directory, just no .deb
[21:00] <yofel> let me try
[21:00] <yofel> njin: odd...
[21:01] <njin> stsrange, i write a mail to xdatap for further info about
[21:06] <yofel> penguin42: running 'fakeroot ./debian/rules binary' created a xserver-xorg-video-ati-dbg_6.13.1-1ubuntu2_amd64.deb here
[21:07] <njin> suggestion for this https://bugs.launchpad.net/ubuntu/+bug/411937
[21:07] <ubot2> Ubuntu bug 411937 in ubuntu "switching between lay-outs is not responding (affects: 1) (heat: 9)" [Undecided,New]
[21:07] <penguin42> yofel: Sorry, you're right - I was being dumb and got confused among the pile of debs
[21:08] <penguin42> sorry about that
[21:10] <yofel> heh, np :)
[22:05] <njin> i go to sleep, see you tomorrow.
[22:10] <yofel> micahg: should I just close that bug? theoretically that's the case in lucid too, but I just can't find any official statement on this
[23:40] <Licuadora> I cant turn off my PC
[23:40] <Licuadora> everytime i try to turn it off, it will send me to the login screen
[23:40] <Licuadora> and if i try it there, nothing happens
[23:41] <penguin42> odd
[23:41] <Licuadora> i have to push my machine's power off button
[23:41] <Licuadora> I know
[23:41] <Licuadora> THA has to be a bug
[23:41] <penguin42> what happens if in a shell you do sudo shutdown -h now
[23:42] <Licuadora> it might turn off, but then am i gonna have to do that everytime i want to turn it off?
[23:42] <penguin42> Well the 1st thing to do is to figure out if that turns it off - if it doesn't then it's even weirder
[23:42] <Licuadora> let me try it
[23:46] <Licuador> It worked
[23:46] <Licuador> So, what is this happenning?
[23:47] <Licuador> penguin42: you know whats happenig?
[23:47] <penguin42> nope
[23:47] <Licuador> hm...
[23:47] <Licuador> *chuckles*
[23:47] <penguin42> do you use gnome or kde?
[23:47] <Licuador> gnome
[23:48] <penguin42> Licuador: Well, thing is we know from that the BIOS and kernel are happy to turn it off, so that bit works
[23:48] <Licuador> Any command for the terminal to see whtas wrong?
[23:49] <penguin42> Licuador: Lets just check; how are you shutting down - what exactly are you clicking?
[23:50] <Licuador> ok, i push the on/off icon, then shut down
[23:50] <penguin42> ok
[23:51] <Licuador> an then othe login screen
[23:51] <penguin42> when you get to the login screen, there's a shutdown button at the bototm right isn't there? Does that work?
[23:51] <Licuador> i try there to shut down with the option in th righ lower desktop
[23:51] <Licuador> No, it does not work
[23:52] <Licuador> it doesent do anything
[23:52] <penguin42> hmm well that's 1 thing that works and 2 that don't!
[23:54] <penguin42> Licuador: OK, so when it dumps you back at the login screen, log back in and run dmesg > afile   and see what it says in that file, also take a copy of .xsesson-errors (and I think there is a .old), a copy of /var/log/messages as well
[23:56] <Licuador> So, after login and typing dmes> afile I go to .xsession-erros and do a copy paste?
[23:56] <Licuador> let me try it
[23:57] <penguin42> take a copy of it