[02:48] <lotuspsychje> good morning
[07:33] <EriC^^> good morning all
[07:47] <marcoagpinto> Hello!
[08:21] <ducasse> good morning
[15:48] <PoppaVic> For the record: ubuntu has really, really mucked the package-management of late... Spent over a week trying to install a WORKING ubuntu to the new lappy - and i still have periodic daily fights
[15:54] <ogra_> make sure to file bugs, so it can get fixed ...
[15:54]  * ogra_ personally has not had any issues for the last few years
[15:55] <PoppaVic> ogra_: you know..? I let it try to "file reports" for the first few days - that was causing other issues.
[15:55] <ogra_> then file them manually ... launchpad has a web interface
[15:56] <PoppaVic> Well, I had great luck with decade-old lappies... Apparently, the Lenovo Gaming Ideapad Ryzen was making ubuntu cranky.
[15:56] <ogra_> ah, no ryzen here ... plain old intel devices, one machine with nvidia card ... lots of arm devices as well ...
[15:57] <PoppaVic> ogra_: no idea how I'd even file... All I know for sure is that every distro (and I tried even fedora) from 21 all the way down was crashing after the live-cd "install".. Only 16.04 ran the live and did the install AND BOOTED... I had to cobble from there
[15:57] <ogra_> might be that some driver stuff is not 100% ready for ryzen if you dont use HWE
[15:58] <PoppaVic> ogra_: not all that freaked on acceleration - when the BOOTS were not even working - when it was crashing and locking.. when the package-manager stuff was screaming errors - those were my own issues
[16:00] <PoppaVic> I had to accept that only 16.04 would install and boot.. BUT, no wifi - only ethernet until I manually updated kernel and linux-firmware and THEN moved along to 18.04 - but I can't let it ever upgrade again: it endlessly breaks it.
[16:01] <ogra_> well, the package manager is not related to the boot at all
[16:01] <ogra_> these are definitely two distinct issues
[16:01] <PoppaVic> I know. and apparently the live-cd variant of Ubuntu "try" isn't related to what it inbstalls, either
[16:03] <ogra_> well, recent ubuntu defaults to UEFI booting ... but that only works if the machine/vendor actually follows all standards ... i have seen a lot of people that needed to do BIOS/UEFI updates first to fix issues the vendors have introduced by being non-compliant
[16:03] <PoppaVic> when you boot yer new install and it just lies there, dark - that's an issue. When you get past that, but all further updates and upgrade start screaming about broken packages and dependencies, that's an issue. And, when you spend the night relaxing to videos played off the network-drive, and wake to reboot and find no wifi "found", that too is an issue.
[16:04] <PoppaVic> ogra_: yeah, I thought about bios-update.. I dunno if ubuntu has an updater, and I replaced doze on this machine asap
[16:05] <ogra_> yeah, ubuntu comes with fwupd by default to update UEFI
[16:06] <PoppaVic> ok, cool-  I will look into that after work
[16:09] <PoppaVic> and, laters.
[17:31] <JanC> many UEFI firmwares can also update themselves


[22:56] <bbucommander> Hello all.  Not sure if this the right place to ask, but I am trying to run a shell script to mount my RAID 5 disk on boot and am wondering how I can use Upstart to accomplish this.  I followed the basic Upstart tutorials and tried placing a source reference to the script in pre-start and post-start sections of several files, but so far no luck.
[22:57] <bbucommander> I am using Ubuntu 10.10 with latest updates.  My RAID 5 is fakeraid using Intel Matrix Raid tech.
[22:58] <ion> In Ubuntu the udev stuff should handle that. If it doesn’t you probably should report a bug against whatever package provides the required stuff for the fakeraid in question.
[22:59] <bbucommander> The problem is that my RAID 5 partition is larger than 2 TB, so I have to use GPT for my partition table.  Since dmraid does not support GPT out of the box, I have to run a script calling kpartx to handle the task.
[23:01] <ion> kpartx probably should come with the necessary udev stuff to automate that then.
[23:02] <bbucommander> Is there a systematic way to check for udev automation?
[23:02] <bbucommander> Or an easy way? :-)
[23:03] <ion> Look in /lib/udev/rules.d
[23:03] <ion> Perhaps dpkg -L kpartx | fgrep udev/rules.d
[23:04] <bbucommander> Sure enough!  I found: /lib/udev/rules.d/95-kpartx.rules
[23:04] <JanC> bbucommander: do you have multiple partitions on the RAID 5 disk ?
[23:05] <bbucommander> No, just one.
[23:05] <JanC> then why use a partition table at all?  ☺
[23:06] <bbucommander> Could I still read the disk from Windows without one?
[23:06] <JanC> maybe not
[23:06] <JanC> no idea
[23:07] <bbucommander> I will look into it.  Good idea, hadn't thought of not using a partition table whatsoever.
[23:07] <JanC> I think Windows can mount USB flash sticks without a partition table, so in theory it should be possible
[23:10] <bbucommander> Forgive my ignorance of udev, but are all udev rules executed every boot?  Is there way to check if the kpartx rule is firing?
[23:15] <bbucommander> Ah, never mind.  I stumbled upon an Ubuntu bug report that essentially cleared up the issue.  The udev rule for kpartx is in fact buggy and needs repair.  Thanks ion and JanC for your help!


[08:58] <lordievader> Good morning.
[13:27] <BluesKaj> Hiyas all
[16:02] <tobias47n9e> Is there a known bug for Ubuntu Gnome 15.04 where the Login screen keeps flashing and each flash resets the password entry field? I have it installed through VirtualBox and can't login anymore because of this bug.