[03:37] <captine> Hi all.  My 12.04.2 locks  up from time to time.  I am thinking of trying a newer kernel from the kernel ppa, but believe this is not officially supported.  i have a question regarding what is in the "extra" kernel package?  is this the right place to ask?
[03:37] <captine> question really is what is in the linux-image-extra-3.7.8-030708-generic_3.7.8-030708.201302141605_amd64.deb that is considered "extra"... which one should i rather use.  the kernel without the "extra"
[10:13] <hyper_ch> howdy, I have serious issues with 3.8.0-7 kernel.... it makes my network freeze when using samba
[14:42] <BluesKaj> Howdy all
[14:44] <penguin42> Hey BK
[14:47] <BluesKaj> hi penguin42
[14:49] <hyper_ch> hi BluesKaj
[14:51] <BluesKaj> hi hyper_ch
[14:52] <hyper_ch> kernel 3.8 doesn't like cifs
[14:52] <penguin42> hyper_ch: What exactly are you seeing?
[14:54] <hyper_ch> penguin42: http://images.sjau.ch/img/ee9273cb.jpg
[14:54] <hyper_ch> blocks all network, recoverable only be reboot
[14:55] <hyper_ch> using quantal kernel now on raring :)
[14:55] <penguin42> hyper_ch: Please make sure you report that
[14:55] <penguin42> hyper_ch: That looks like a couple of separate problems; iommu stuff shouldn't be protocol dependent
[14:56] <hyper_ch> well, when using scp, ftp, rsync no problems... just with cifs as far as I've seen
[14:56] <penguin42> hyper_ch: Yeh, it's odd though; please report it
[14:57] <penguin42> hyper_ch: What's the 1st error you see in the logs?
[14:57] <hyper_ch> penguin42: no idea
[14:57] <penguin42> hyper_ch: I see the no writeable handles there 1st; it almost looks like a memory leak
[14:57] <hyper_ch> penguin42: I did add here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/856496
[14:57] <hyper_ch> but not sure if I shouldn't split it somewhere else
[15:01] <penguin42> hyper_ch: you should to do it as a separate bug
[15:01] <penguin42> generally kernel bugs should be kept separate
[15:02] <hyper_ch> penguin42: it sounded the same
[15:02] <penguin42> hyper_ch: Yeh, for kernel ones it's best to leave it to the devs to figure out if it is; there can be weird interactions
[15:02] <penguin42> hyper_ch: And if you're only seeing it on cifs that's interesting on it's own
[15:08] <hyper_ch> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1132477
[15:09] <penguin42> how did you report that?  Unfortunately it's not got any of the logs
[15:09] <hyper_ch> what logs?
[15:10] <hyper_ch> I just filled in the form
[15:10] <penguin42> yeh, it's better to use ubuntu-bug to report stuff
[15:10] <penguin42> hyper_ch: Can you boot into the affected kernel and then run   apport-collect 1132477
[15:11] <penguin42> (You'll get an automated message asking you to do that shortly anyway)
[15:11] <hyper_ch> no apport on kubuntu
[15:11] <penguin42> you should have apport-collect
[15:11] <hyper_ch> nope
[15:12] <penguin42> then install it, it'll attach a copy of the dmesg and hardware info on the machine
[15:13] <penguin42> a bot will ask you for that log info shortly anyway; the bug report as is doesn't have enough info for anyone to do anything with it
[15:21] <penguin42> hyper_ch: Also, that picture you showed me had more log messages in which are likely to be useful
[15:32] <hyper_ch> not really
[15:32] <hyper_ch> plenty of inodes left on the server
[15:32] <hyper_ch> Filesystem                 Inodes   IUsed     IFree IUse% Mounted on
[15:32] <hyper_ch> /dev/mapper/sda3_crypt  121552896  195644 121357252    1% /
[15:32] <penguin42> that's irrelevant
[15:36] <hyper_ch> and I can't really use apport
[15:36] <hyper_ch> since when I reproduce the bug, I can't do anything on the network anymore
[15:36] <hyper_ch> so it can't submit anything
[15:36] <penguin42> but you can boot into that kernel and run it to at least get the boot logs and hardware info
[15:37] <penguin42> also if you have any info in the /var/log logs showing that set of errors you can see the 1st ones that triggered it
[15:37] <hyper_ch> for that I don't need to run apport
[15:37] <penguin42> fine; if you want then go and attach ALL the logs that apport would normally attach to the bug
[15:37] <hyper_ch> -> /var/log is tmpfs
[15:45] <hyper_ch> dpkg-query: no packages found matching linux
[17:11] <SonikkuAmerica> Hey! I'm having a problem with graphical shutdown sequence on the Raring alpha.
[17:13] <SonikkuAmerica> Currently, the only empirical way to shut it off is to [ sudo shutdown now ] in terminal or tty, & the last time that happened it hung forever.
[17:15] <penguin42> SonikkuAmerica: And it worked on quantal?
[17:16] <SonikkuAmerica> penguin42: No problem in Quantal
[17:18] <penguin42> SonikkuAmerica: https://wiki.ubuntu.com/Bugs/Responses#Freeze_during_boot_or_shutdown_screen
[17:18] <penguin42> SonikkuAmerica: Perhaps that will give you some more debug
[17:18] <SonikkuAmerica> OK, I'll give that a shot then.
[17:26] <SonikkuAmerica> penguin42: OK, I see what the issue is in this case: It has to do with the "one or more tasks are not responding" dialog. Selecting "Shut Down Anyway" does not work at this time.
[17:26] <penguin42> hyper_ch: Have you tried booting the kernel with the intel_iommu=off option - I see some suggestions from others on other systems
[17:26] <frank_> skype  stopped working. is there a way to make it work again?
[17:26] <hyper_ch> penguin42: I have, same result
[17:26] <SonikkuAmerica> frank_: Can you pastebin a traceback or maybe run it in a terminal?
[17:26] <penguin42> SonikkuAmerica: I'm surprised that causes it to hang for ever
[17:27] <SonikkuAmerica> penguin42: No, it's not that... pushing the "Shut Down Anyway" button just does nothing.
[17:27] <frank_> when i run it in a terminal it says segmentation fault (core dumped)
[17:27] <SonikkuAmerica> Selecting "Shut Down" from the system menu works perfectly after that.
[17:27] <hyper_ch> frank_: skype works here
[17:28] <hyper_ch> frank_: I added the quantal partner repository
[17:28] <frank_> ok...thanks ...will try that :)
[17:30] <penguin42> hyper_ch: I've set the importance and stuff on it now; if the intel-iommu option doesn't help then we'll see if any of the others have any suggestions
[17:31] <hyper_ch> penguin42: I can set it again and provide log
[17:31] <hyper_ch> if you want
[17:31] <penguin42> hyper_ch: No, I don't know enough about the iommu stuff to really say anything more
[17:35] <SonikkuAmerica> Another thing: When an app is called in from another one, apparently the global menu does not switch from the parent app to the child...
[17:35] <SonikkuAmerica> Once again, a Raring thing.
[17:35] <SonikkuAmerica> Nevver happened in Quantal.
[17:35] <SonikkuAmerica> *with one v
[17:41] <hyper_ch> penguin42: how can you confirm it?
[17:43] <penguin42> hyper_ch: It seems to be the normal practice on kernel bugs to mark them as confirmed once they have the logs
[17:43] <hyper_ch> penguin42: ok :) I have no idea about that
[17:43] <penguin42> hyper_ch: And anyway, assuming that the logs are real you've obviously hit a real bug so there's no point arguing about that!
[17:44] <hyper_ch> penguin42: curious abou thtat:  "Feb 24 16:46:24 subi kernel: [  364.032492] CIFS VFS: Send error in Close = -9"  this doesn't appear in the 3.5 kernel log
[17:45] <penguin42> hyper_ch: Yeh, I don't know if these are separate bugs or not
[17:47] <hyper_ch> no idea
[19:22] <Atlantic777> Anyone having problems with wicd?
[19:22] <Atlantic777> I've just installed 13.04 from minimal iso, put xorg and awesome wm but wicd daemon doesn't want to start.
[22:15] <SonikkuAmerica> Well, looks like Pidgin's indicator-messages plugin is broken too. It only spills notifications, but opening it (from dash or indicator) fails silently.
[22:15] <SonikkuAmerica> I wish I could get a traceback.
[22:16] <SonikkuAmerica> Or find a way to terminal into it. (Is there a way to do that?)
[22:17] <SonikkuAmerica> What's more, doing [ ps ax | grep pidgin ] gives about a gazillion pid's, and the [ kill ] command doesn't kill the hidden process.
[22:23] <trism> SonikkuAmerica: indicator-messages doesn't really do anything special when you click the app, just execs it, and the pidgin-libnotify plugin doesn't do anything special when this happens either, so for some reason pidgin isn't dealing with multiple instances correctly
[22:23] <SonikkuAmerica> libnotify wasn't made to open the associated program.
[22:24] <SonikkuAmerica> Well, Pidgin is not getting exec'ed/restored from indicator-messages, but all the other apps are fine
[22:24] <trism> SonikkuAmerica: libnotify isn't involved, that is just the name of the plugin that handles notifications and the messaging menu
[22:25] <trism> SonikkuAmerica: well, libnotify does the notifications stuff but otherwise it is libmessaging-menu
[22:25] <SonikkuAmerica> Yeah, I know that.
[22:25] <SonikkuAmerica> OK... should I submit a bug report over Launchpad?
[22:25] <SonikkuAmerica> for libmessaging-menu?
[22:26] <SonikkuAmerica> Or is this a Pidgin bug?
[22:26] <trism> SonikkuAmerica: no I'd file it against pidgin
[22:26] <SonikkuAmerica> OK
[22:26] <SonikkuAmerica> Thanks for the info
[22:27] <trism> SonikkuAmerica: it may be a messaging-menu bug but again, it doesn't really do anything special, just execs it
[22:27] <trism> SonikkuAmerica: can you run pidgin from a terminal when pidgin is already running and see if that works correctly?
[22:27] <SonikkuAmerica> I tried that, it just hangs. Definitely a Pidgin issue
[22:29] <trism> SonikkuAmerica: might be worth running it through gdb to see where it is hanging
[22:29] <SonikkuAmerica> Okie-dokie
[22:29] <SonikkuAmerica> Actually I'll run it through ddd (which uses gdb)
[22:30] <mandoguit> Hmm....toggle on the Nepomuk Indexer so I would have search function in Dolphin and now Nepomuk keeps crashing every couple of minutes.   Known problem by any chance?   Kernel: 3.8.0-7-generic x86_64 (64 bit) Desktop: KDE 4.10.00 Distro: Ubuntu Raring Ringtail (development branch)
[22:41] <SonikkuAmerica> Well then again, Raring has no installation candidate in the Pidgin external PPA.
[22:49] <ikonia> not surprised
[22:49] <ikonia> why would PPA people host a repo for a non-released repo
[22:52] <SonikkuAmerica> Ditto.
[22:52] <SonikkuAmerica> I might as well be on a cruise to Tahiti.
[23:13] <yofel> mandoguit: a backtrace of the crash would be helpful - and file a bug in any case, this shouldn't be happening
[23:13] <mandoguit> yofel:   thanks for responding   here is the bug report etc   https://bugs.kde.org/show_bug.cgi?id=315732
[23:14] <mandoguit> heh....neat!   haven't seen that before.
[23:17] <yofel> mandoguit: from the possible dup it looks like we need a newer poppler lib
[23:19] <mandoguit> yofel:   not sure what you mean by that statement to be honest.   Is more information or an upgrade needed at my end of things or are you refering that a library needs to be updated upstream?   thanks again
[23:20] <yofel> mandoguit: we need to update a library in k/ubuntu - see https://bugs.kde.org/show_bug.cgi?id=315031
[23:21] <yofel> so you'll have to wait until that's done - or find the PDF file the indexer is choking on
[23:21] <mandoguit> yofel:    ahh....ok thank you. will check that out then.
[23:22] <yofel> mandoguit: actually, you can get some packages from https://launchpad.net/~matttbe/+archive/ppa/+sourcepub/2903898/+listing-archive-extra until then
[23:23] <mandoguit> yofel:   ok sounds good.  will check that out after I look over that other bug report.   wasn't sure if my problem was related to that one or not so decided to file a fresh one.   :)
[23:24] <yofel> that's good, but as your backtrace shows that it's the PDF indexer crashing it's likely that issue
[23:25] <mandoguit> yofel:    guess I should try to become a bit more familiar with the backtraces too then.  :)