[08:22] <necurion> greetings to everyone, before I file a bug I thought I ask around here, I am trying to get disco on my good old lenovo x230. However during the install it hangs after I selected a keyboard layout. the mouse pointer is spinning but nothing else happens.
[08:22] <lotuspsychje> necurion: what kind of harddisk are you installing on?
[08:23] <necurion> its a ssd the exact model i would have to check
[08:23] <lotuspsychje> necurion: are you singlebooting or dualbooting?
[08:24] <necurion> single booting
[08:25] <lotuspsychje> necurion: how long did you wait after keyboard in setup?
[08:25] <lotuspsychje> think thats the step before partitioning, that step usualy takes a bit to scan hd/partitions
[08:26] <necurion> well I had it running for like an hour
[08:26] <lotuspsychje> wow, yeah thats not good
[08:26] <lotuspsychje> necurion: wich Os is on your hd ssd now?
[08:27] <lotuspsychje> necurion: check in your bios settings if fastboot=OFF and secureboot=OFF and try again please?
[08:27] <necurion> it had solus on it, yesterday I managed to install 18.10 with some hassle but its not booting either
[08:28] <necurion> Solus and Arch linux run fine
[08:28] <lotuspsychje> ah tnx for sharing that
[08:28] <necurion> with other distros i have problems
[08:28] <necurion> its a crucial m4 sdd
[08:28] <lotuspsychje> necurion: maybe if your machine is 'older' try lubuntu or xubuntu 19.04 for testing?
[08:29] <necurion> the ubuntu variant doesnt matter
[08:29] <lotuspsychje> did you try?
[08:29] <necurion> the machine is an i7 quadcore with 16gb of ram
[08:29] <necurion> its not to weak
[08:29] <lotuspsychje> okay
[08:29] <lotuspsychje> maybe its kernel 5 it doesnt like
[08:30] <necurion> solus is running kernel 5
[08:30] <lotuspsychje> hmm ok
[08:30] <lotuspsychje> so if other distro's boot, ubuntu should also at least boot
[08:30] <necurion> it seems to be something with how ubuntu compiles the kernel I guess, but i cannot find a way to even produce an error message
[08:31] <necurion> it does boot
[08:31] <lotuspsychje> yeah i mean bypass your keyboard settings
[08:31] <necurion> yeah thats what i thought
[08:32] <necurion> I also started ubiquity from the terminal to see if it throws some errors but also nothing
[08:32] <lotuspsychje> necurion: i presume its the partitioning part lagging
[08:32] <lotuspsychje> ubuntu sees other distro's and might bottleneck there
[08:32] <necurion> yeah I also thing it doesn't like my hard disk
[08:33] <necurion> i did have problems with an earlier daily build where the partitioner threw errors about not being able to read the disk
[08:33] <lotuspsychje> necurion: maybe what we can try is booting a live usb, then start ubiquity from terminal, and start a tail -f /var/log/syslog too
[08:33] <necurion> which is funny since earlier ubuntu versions and other distros don't have a problem with it
[08:34] <lotuspsychje> necurion: yeah ive seen that before on releases bottleneck at that step
[08:37] <necurion> alright at least the 19.04 live iso does boot properly 18.04.2 and 18.10 only boot with nomodeset and i915.modeset=0 and take like 10 min to get me to the desktop
[08:40] <lotuspsychje> necurion: maybe we should proceed with the bug anyway
[08:40] <lotuspsychje> i dont find any other related beside nvidia ubiquity one
[08:42] <necurion> maybe nvidia its not, the laptop has intel graphic
[08:43] <lotuspsychje> we also found a bug yesterday on intel + kernel 5 but with black boot
[08:43] <lotuspsychje> so unrelated too
[08:43] <necurion> i didn't see much in the dmsg, I will try to just start the live thing and check with gnome-disks or fdisk, whether i can access the disk at all
[08:43] <lotuspsychje> try a live tail: tail -f /var/log/syslog
[08:44] <lotuspsychje> so we can see whats happening at wich point
[08:51] <necurion> now this is odd... I just started the live usb, opened tail on the dmsg, opened disks, which suddenly worked, and now its installing...
[08:51] <lotuspsychje> lol
[08:51] <lotuspsychje> the magic of ubuntu
[08:52] <necurion> well i don't like it :P
[08:52] <necurion> i didn't fix the problem :P
[08:52] <lotuspsychje> necurion: as i was saying, not the first time that happens lag before partitioning
[08:52] <lotuspsychje> also 19.04 isnt final yet, so things can still happen
[08:53] <necurion> and i also didn't connect to the internet this time
[08:53] <necurion> well lets see whether it boots after install :P
[08:58] <guiverc> lotuspsychje, just fyi:  https://community.ubuntu.com/t/disco-disco-19-04-release-candidate-testing/10570/4  mentions a spinning...    i'd don't know source (wouldn't put much weight given how reported), but some term as used by necurion 
[08:59] <necurion> I did install, it did boot, but now after i clicked the username on the login screen nothing happens
[08:59] <necurion> the password prompt doesnt come, and after a while i see the login prompt again
[09:01] <necurion> and i see plenty of i/o errors on the F1 Terminal thing
[09:01] <guiverc> necurion, you verified your install media I assume? 
[09:01] <necurion> yes
[09:02] <guiverc> :)  thanks
[09:02] <necurion> i had the same issue with 18.04 at some point reasons for which I went to solus and arch for a while
[09:03] <necurion> its: print_req_error: I/O error, dev sda and then some sector
[09:04] <necurion> and then journald says Failed to write entry ... ignoring: Read-only file system
[09:05] <necurion> I can try booting into the live usb again and do some fsck or something like that
[09:06] <necurion> but as I said i only have that particular problem with ubuntu (and derivatives) and fedora
[09:06] <necurion> other distros like solus and arch work just fine
[09:06] <guiverc> read-only file system could be an error-condition was detected on mount (you need to fsck it), or something else bad (I'd suggest checking SMART health of drive too) - checking logs (dmesg possibly) should reveal why it mounted read-only
[09:07] <necurion> how do I check the SMART health?
[09:08] <guiverc> smartctl  (or gnome-disks which provides less detail, but is far easier to read) - there are other tools too...
[09:09] <guiverc> package smartmontools contains smartctl
[09:14] <necurion> okay syslog also says: sd 0:0:0:0: [sda] tag#1 FAILED Result hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[09:15] <guiverc> it's beyond my capacity to help necurion, if you wait hopefully someone else can help
[09:18] <necurion> thanks anyways i will read up on the smartctl stuff maybe my harddisk has some defect sectors and other distros are just more ignorant or write stuff somewhere else
[09:29] <necurion> checking the disk with the disk checking option on the live usb boot thing says everything is fine
[09:33] <necurion> trying the smartmontool thing i got more errors on the syslog
[09:33] <necurion> https://pastebin.com/iW07HAhm
[11:57] <lotuspsychje> necurion: didnt you say you had an ssd?
[12:01] <necurion> yes i did
[12:02] <lotuspsychje> necurion: dont think thats causing your issues
[12:02] <lotuspsychje> necurion: as you tested other different ubuntu and distro with success
[12:02] <lotuspsychje> necurion: so, at wich point are you now?
[12:04] <necurion> lotuspsychje: I tested different versions of ubuntu and flavours, I checked fedora with the same result so for the time being I will resort back to solus...
[12:05] <lotuspsychje> necurion: if you still on 19.04 feel free to share your dmesg
[12:05] <lotuspsychje> there must be something traceable right
[12:06] <necurion> lotuspsychje I posted the dmsg earlier as pastebin
[12:06] <lotuspsychje> necurion: your new one after install?
[12:06] <necurion> after install I was not able to get to a terminal
[12:07] <lotuspsychje> necurion: stuck at gdm?
[12:08] <necurion> lotuspsychje: kinda, logging in didn't work, and I was unable to switch to a console with alt+str+f2 for example its like ubuntu switched those off
[12:09] <lotuspsychje> necurion: try to get in with nomodeset?
[12:09] <necurion> lotuspsychje: same result, the login fails because the disk is mounted read only
[12:10] <lotuspsychje> hmm
[12:10] <necurion> lotuspsychje: its not a graphics problem
[12:10] <lotuspsychje> necurion: never heared of not able to login into gdm with an ssd problem
[12:11] <lotuspsychje> necurion: did you fiddle with fstab or so?
[12:11] <lotuspsychje> necurion: or manual partition at setup?
[12:12] <necurion> lotuspsychje, this behaviour started with the first hardware enable stack for 18.04, I suspect there is something in the kernel or driver config that changed around there
[12:13] <lotuspsychje> necurion: didnt you install 19.04 clean?
[12:14] <necurion> lotuspsychje: It managed to install it once, yes
[12:14] <necurion> but then i had the same problem after boot
[12:15] <lotuspsychje> necurion: what about pressing F1 at boot to see txt based boot, maybe some clues there
[12:15] <necurion> its the same outputs I posted earlier
[12:16] <necurion> it said that there is something it cant read
[12:17] <lotuspsychje> we need to find a way to !bug your issue
[12:18] <lotuspsychje> necurion: ctrl alt f1 or F2 doesnt give you a tty?
[12:32] <necurion> lotuspsycheje: I will try a netinstall, maybe that gives me more usable clues
[12:34] <lotuspsychje> your choice mate
[13:25] <bischoff> Hi folks
[13:25] <bischoff>  I wanted to say I have a remarkably stable plasma-wayland on disco dingo
[13:25] <bischoff> it's the first time I see that
[13:26] <bischoff> so... congrats :-) wayland starts being really usable
[13:28] <necurion> lotuspsychje: I did manage to install it now with the netinstall and it does work, i am somewhat confused as to why this is the only way to install a clean working system though
[13:29] <acheronuk> bischoff: great to hear :)
[13:31] <bischoff> acheronuk: :-)
[17:24] <Zuverink> This is a cosmetic issue, but it is driving me nuts. I installed the 19.04 Beta and all was running fine, then the first kernel upgrade resulted in the loss off anything more than just a purple screen no Ubuntu logo. Every kernel upgrade since has done various other horrible issues to the bootsplash. Everything runs fine after the bootslash, its cosmetic. But it drives me nuts. Can someone help me diagnose t
[17:24] <Zuverink> his?
[17:25] <Zuverink> *this
[17:40] <lotuspsychje> Zuverink: intel graphics?
[17:41] <Zuverink> lotuspsychje, yes
[17:41] <Zuverink> lotuspsychje, laptop
[17:43] <lotuspsychje> Zuverink: can you see if this bug affects you? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824546
[17:43] <Zuverink> lotuspsychje, Ill look
[17:54] <Zuverink> lotuspsychje, I think this is more relevant https://ubuntuforums.org/showthread.php?t=2331312
[17:56] <Zuverink> lotuspsychje, though intel graphics
[17:57] <tomreyn> and nothing but intel graphics? no additional graphics chipset?
[17:57] <tomreyn> the forum thread is rather old, the graphics stack worked quite differently then.
[17:58] <lotuspsychje> Zuverink: can you boot to desktop?
[17:59] <tomreyn> the kernel image from -proposed would be worth a try.
[18:00] <lotuspsychje> Zuverink: can you recall wich kernel booted and wich not?
[18:04] <Zuverink> lotuspsychje, im going to just leave it, its cosmetic. it goes purple at boot and remains purple until the login screen, then everything is normal
[18:05] <Zuverink> lotuspsychje, i just lost the logo on the purple, on shutdown its all there logo on purple
[18:06] <lotuspsychje> Zuverink: did you try pressing F1 at boot stage, to see textboot?
[18:06] <Zuverink> lotuspsychje, no i did not
[18:07] <lotuspsychje> Zuverink: maybe more clues there?
[18:08] <Zuverink> lotuspsychje, ill do that now
[19:13] <jack> heyho
[19:13] <lotuspsychje> welcome jack 
[19:19] <Eickmeyer> Invader_Bork, lotuspsychje: Let's continue that conversation here for sake of the main channel.
[19:19] <lotuspsychje> kk
[19:19] <Eickmeyer> Invader_Bork: Currently, GTK+ has no support for blur in transparency.
[19:19]  * Eickmeyer did that research last night
[19:20] <Invader_Bork> sure
[19:20] <Invader_Bork> Eickmeyer^
[19:20] <Invader_Bork> is this why the blyr extension is failing to achieve blur on the dock?
[19:21] <Invader_Bork> i have blur in the activity window
[19:21] <Eickmeyer> Invader_Bork: I think so.
[19:21] <Eickmeyer> Did you modify the .css to achieve the blur in the activity window?
[19:22] <Invader_Bork> lotuspsychje, do you have a similar path for top bar transparency ?
[19:22] <Invader_Bork> Eickmeyer, no i have installed an extension
[19:22] <Invader_Bork> https://extensions.gnome.org/extension/1251/blyr/
[19:23] <lotuspsychje> Invader_Bork: dconf-editor has a nice search function now, but no there isnt one
[19:24] <Eickmeyer> Invader_Bork: Interesting. I'm surprised any of it works. The GNOME folk were really adamant about removing that functionality.
[19:24] <Eickmeyer> Proably was just the panels.
[19:25] <Invader_Bork> Eickmeyer, as far as i can tell the extension uses lib clutter for the blur
[19:29] <Invader_Bork> Eickmeyer, do you know what's the deal with the gnome devs and the blur? 
[19:30] <Invader_Bork> did they want to replace it with something else or just have a burning hate for blurry things
[19:30] <OerHeks> gnome3 just gets better, no need to make old stuff backwards compatible
[19:32] <Invader_Bork> i dont understand
[19:35] <Eickmeyer> Invader_Bork: I am not sure what led to the decision.