=== BarnOwl is now known as joep-153 [14:03] Hi folks. I hope you can help. I have a Dell Latitude D620 laptop (2GB ram, 2MHz processor, dual core) with no apparent hardware issues. I was able to install Ubuntu 14.04, but after installing the updates, the log in process halts. Are any of you aware of problems like this? [14:05] I also tried to install Kubuntu 14.04 . The install halted shortly after getting a graphical screen and would not continue. [14:05] joep-153: When you say that the 'the login process halts' what is the last thing that happens? [14:06] I enter my password, push enter, then the screen goes blank [14:07] I should add that I'm adding a linux version to an already existing winxp pro on the same disk. I shrank the winxp partition with gparted-live [14:09] yeh that should all work [14:09] there have been a couple of errors during the boot process. one is a message that the drive for cryptswapper is not ready or not present [14:11] it is something in the updates that caused the problem. i don't know which update, though. i let them all be installed [14:12] I also installed the NVidia proprietary driver. [14:15] the other error is "error calling EVIOCSKEYCODE" [14:16] that error is displayed during boot [14:24] I tried booting with the original kernel (3.16.0-30), but the same problem occurs. [14:28] BTW, the log-in failure after updates occurs with both the 64 and 32 bit .iso [14:29] joep-153: Have you tried without the nvidia proprietary driver? [14:31] i'll try that, but i'm going to do a re-install. I know the free driver worked, but I don't recall if i had done the updates at that point. [14:31] i'll also try leaving my home directory unencrypted [14:32] joep-153: There also tend to be 2 or 3 versions of the nvidia closed drivers available; try the other versions [14:34] i'll do that. thanks for the suggestions === joep-153 is now known as BarnOwl_away === BarnOwl_away is now known as BarnOwl [17:25] After re-installing Ubuntu, I found that my blank screen issue was due to using the latest NVidia proprietary driver. [17:25] thanks [21:09] Hey guys. I want to report a bug, but I have no idea which package it belongs to (yes, I've read ReportingBugs). [21:09] And I've heard a picture says more than a thousand words, so here we go: [21:09] http://i.imgur.com/fdcUxSb.jpg [21:09] This is my desktop, with Libreoffice open [21:09] Well, it's supposed to be anyway [21:09] After looking really really carefully, I discoverd it at the right side of my screen.. [21:10] http://i.imgur.com/BGew1eV.png [21:12] I've spent 10 minutes trying to get Libreoffice to show up, so I consider this a bug: I window (at the very least of the default Ubuntu applications) should not be able to shrink to this size. [21:12] *A window [21:13] Sooo.. which package should I report this to? [21:13] martijnbb22: don't overthink it too much, file it in libreoffice and if it belongs elsewhere, a triager will move it to the proper place [21:14] martijnbb22: if you haven't noticed it with anything but libreoffice, it's a fair bet that's a good place for it. If you've seen it with other applications, it may belong in unity, compiz or xorg, but this is just speculation :P [21:17] Hmm, i've tried this with some applications. Some refuse to resize to 1x1, some don't (including libreoffice, pidgin) [21:17] thanks for your comment, I will report it to libreoffice/pidgin [21:17] martijnbb22: I'd still file it under the specific application [21:17] no prob :) [21:17] i agree with roadmr on this one, you should probably file it against libreoffice, rather than moultiple [21:17] since the cause/issue is potentially different for each one [21:17] yeah [21:17] (perhaps have different bugs for each program) [21:18] ok, thanks for your comment guys! [21:24] https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1458684 [21:24] Launchpad bug 1458684 in libreoffice (Ubuntu) "Libreoffice allows resizing its window to 1 pixel" [Undecided,New] [21:24] :) [21:37] martijnbb22: you missed important information: the version of Ubuntu you have, the version of the package you have, etc. Consider running `apport-collect 1458684` [21:42] @teward: woops, thanks [21:42] martijnbb22: Error: "teward:" is not a valid command. [21:42] teward: woops, thanks [21:44] martijnbb22: you're welcome ignore the comments on the bug [21:44] i submitted a comment just as you did that command and attached data [21:44] asynchronicity is a problem [21:44] haha no kidding [21:44] martijnbb22: also, in future, `ubuntu-bug PACKAGENAME` <-- [21:45] that command automatically does the apport data collection step [21:46] i see, thanks! (and i did read that on reportingbugs, so it's just me being stupid..) [21:47] no problem, just a tidbit for the future :)