=== om26er is now known as om26erafk [09:55] seems that nvidia-304-upgrades and nvidia-304 are different versions (304.108 vs 304.88) and this causes kernel module vs API discrepancies that make it impossible for lightdm to start [09:55] tl;dr I've spent quite a while reinstalling stuff from TTY (and trying to get help on irssi) [09:57] i.e. I apparently got affected by bug #1262752 [09:57] Launchpad bug 1262752 in nvidia-graphics-drivers-304-updates (Ubuntu) "nvidia_304 not blacklisted or removed when nvidia_304_updates is installed." [Undecided,Confirmed] https://launchpad.net/bugs/1262752 [10:15] so... I'm aware that said bug is relatively new, but if it could be solved it would be nice. === paddy_ is now known as paddy === om26erafk is now known as om26er === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === paddy_ is now known as paddy [19:20] Hi [19:20] I've opened this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972604 [19:20] Launchpad bug 972604 in linux (Ubuntu) "168c:001c [HP Compaq Presario C700 Notebook PC] Wireless led button doesn't switch colors" [Low,Triaged] [19:21] I was linked to: https://wiki.ubuntu.com/Bugs/Upstream/kernel [19:21] I've red it [19:21] *read [19:22] I need some info [19:24] ' Please take care that when you provide the below information, you should be booted into the newest available upstream mainline kernel only. Failure to do this will have negative unintended consequences. ' [19:25] which of the two kernels? [19:25] Any ideas? [19:31] "I need some info" [19:31] cristian_c: what "Info" are you nedding? [19:32] for example, which of the two kernels [20:38] Another question: [20:40] I've opened this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1222763 [20:40] Launchpad bug 1222763 in linux (Ubuntu) "Pressing usb keyboard multimedia keys doesn't print anything with sudo /lib/udev/keymap -i input/eventX" [Medium,Incomplete] [20:41] but this bug is not reproducible on a PC in particular, it does not depend on pc [20:42] What have I to do in this report? [20:42] Any ideas? [20:42] cristian_c: i'd leave that one be, "Incomplete" means it's waiting for more information, if you read the comments [20:42] cristian_c: since that might be hardware-specific [20:42] TheLordOfTime, no [20:42] TheLordOfTime, it's not hardware-specific [20:42] as for the "kernel" you should read this: https://wiki.ubuntu.com/Kernel/MainlineBuilds [20:43] many users have found this bug [20:43] TheLordOfTime, I've read the second page, too [20:43] when I have installed the upstream kernel [20:44] you boot into the upstream kernel that doesn't say "recovery mode" [20:44] no [20:44] without 'recovery mode' [20:45] that's what i just said [20:45] the one that doesn't say "recovery mode" [20:45] grr, stupid fsck... brb, need to finish repairing my main system [20:46] TheLordOfTime, ok, but I booted the non recovery mode kernel [20:47] TheLordOfTime, a question: should I boot the recovery mode kernel, instead? [20:48] cristian_c: i very rarely triage kernel bugs so I suggest you ask someone else, and leave me be for a bit, i need to get my main system working again [20:48] * TheLordOfTime can't survive off of just his netbook [20:48] ok [20:49] cristian_c: my guess would be "no" [20:49] ok [20:49] because as I understand it the "Recovery Mode" drops to a special set of options for recovery uses, and not the kernel on its own, but don't quote me on that [20:50] ok [20:50] I've booted the standard kernel always === cfmcguire_ is now known as cfmcguire