=== TomTom_ is now known as TomTom
=== TomTom is now known as Tomtom
[08:37] <IrcsomeBot> <Omar> On my laptop Kde connect does not run on the background when i close it can i change this?
[09:14] <yossarianuk> hi - I have a USB ethernet adapter and I cannot get it to work as a bridge using network manager - i have added a bridge via network manager ui and cli - and it just doesn't get ip address on the bridge
[09:14] <yossarianuk> however if I use the ip command its fine
[09:15] <yossarianuk> i.e this method fails -> https://www.tecmint.com/create-network-bridge-in-ubuntu/
[09:16] <yossarianuk> and this method works -> https://unix.stackexchange.com/questions/613188/bridging-built-in-ethernet-with-usb-ethernet-adapter-in-debian  (first answer)
[09:17] <yossarianuk> using nmcli - when i put br0 to up I see 'br0: connecting (getting IP configuration) to br0'
[09:17] <yossarianuk> but it never gets ip info
[09:17] <yossarianuk> any hints ?
[09:25] <yossarianuk> (i could ask in #ubuntu also i guess as this is not Kubuntu specific)
[11:00] <skramer> Isn't it possible to change the background of the analog clock? Readability was much better when it was black on white. Now being white on black it's very hardd to read.
=== paddy is now known as rodneey
=== mnunes is now known as mbnunes
[12:29] <BluesKaj> Hi all
=== kuks is now known as Kuks
=== Kuks is now known as kuks
=== kuks is now known as SkyKuker
=== SkyKuker is now known as kuks
[15:17] <user|83> Discover times out and doesn't connect to org.freedesktop.packagekit
[17:26] <iomari891> greetings, I just upgraded to 23.04 but I notice on wayland on my login menu.
[17:39] <kubuntu> Hi all, I am having some difficulty with getting Kubuntu running on a system with a SSD.  It seems to fail in terms of managing the NVMe SSD.  I have been running 20.04 and when I tried to upgrade to 22.04, the system refused to boot.  Since then, I have been trying to do a fresh install on the SSD using a 22.04 live usb and a 23.04 but with no success.  Both fail in exactly the same way.  Does anyone here have any insight
[17:39] <kubuntu> into what I am doing wrong and how I can get it right?
[17:41] <kubuntu> One of the error messages I get is: fsyncing/closing /dev/nvme0n1p1: no data available
=== kubuntu is now known as john_in_Californ
=== john_in_Californ is now known as John_in_Calif
[17:48] <John_in_Calif> Hi all, I am having some difficulty with getting Kubuntu running on a system with a SSD.  It seems to fail in terms of managing the NVMe SSD.  I have been running 20.04 and when I tried to upgrade to 22.04, the system refused to boot.  Since then, I have been trying to do a fresh install on the SSD using a 22.04 live usb and a 23.04 but with no success.  Both fail in exactly the same way.
[17:49] <John_in_Calif> Does anyone here have any insight into what I am doing wrong and how I can get it right?
[17:49] <John_in_Calif> One of the error messages I get is: fsyncing/closing /dev/nvme0n1p1: no data available
[18:00] <John_in_Calif> Oh well.  I thought I would try.  I may be back later.  Bye all.
[19:21] <linux> Hi, Can you recommend me a solution moving files over wifi between Kubuntu and Android? I used to use Sendanywhere but afte years of using it without any problems it started not connecting to my laptop. Now I tried Warpinator and KDE Connect. After I added rules to firewall I even turned firewall off and restarted applications it doesn't want to connect 8 times out of ten.
[19:44] <IrcsomeBot> <n_holo> sftp, filezilla
[19:47] <Elliria> I used the Wifi File Transfer app made by SmarterDroid for a while and just don't back up my tablet any more because I no longer keep things on it.
[19:49] <Elliria> I'm just checking my notes and see that I also used the Droid Over Wifi app by Dmitri Lapushkin and that one doesn't have ads, but just asks you to support the author from time to time.
[21:53] <John_in_Calif> Hi, I am having a bit of trouble installing Kubuntu 22.04.2 LTS on my Asus laptop.  I have an 128 GB SSD and a 1Tb hard disk.  For years, I have been running Kubuntu and I recently tried to upgrade to 22.04.2. LTS with the OS installed on the SSD and I use the hard drive for data.  My attempt to upgrade has left the SSD unbootable and my attempts to do a fresh install from a USB drive have been unsuccessful as well,
[21:53] <John_in_Calif> each time failing when attempting to format the SSD.
[21:54] <John_in_Calif> Does anyone have any ideas what I might be doing wrong or more importantly, what I can do to overcome this problem?  Clearly, I am missing  something because I don't think my configuation is that unique and as I said above, I have been using it successfully for years before now.
[21:55] <John_in_Calif> This is the first error message I get every time"
[21:56] <John_in_Calif> Error fsyncing/closing /dev/nvme0np1: No data available
[21:57] <John_in_Calif> followed in succession by:
[21:57] <John_in_Calif> Error fsyncing/closing /dev/nvme0np2: No data available
[21:57] <John_in_Calif> Error fsyncing/closing /dev/nvme0n1: No data available
[21:58] <John_in_Calif> Then after a few more error messages, I get this omnious sounding message:
[21:58] <John_in_Calif> ubiquity.components.partman_commit failed with exit code 141. Further information may be found in /var/log/syslog. Do you want to try running this step again before continuing? If you do not, your installation may fail entirely or may be broken.
[21:58] <tomreyn> John_in_Calif: this may actually be a dead, or mostly dead, nvme
[21:59] <John_in_Calif> Dead in what sense.  I can mount it manually and access it.  The data there seems to be intact, although I haven't tried reconstructing the EFI partition  manually yet.
[22:00] <tomreyn> in the sense of decaying hardware
[22:00] <tomreyn> i would backup what you can
[22:00] <John_in_Calif> Everything  was backed up prior to my attempting to upgrade the system.
[22:00] <John_in_Calif> But that is always good advice.
[22:01] <tomreyn> okay then make sure the nvme is properly seated on the mainboard
[22:02] <tomreyn> and then, from the installer / live media, inspect the nvme error log
[22:02] <tomreyn> as well as the system log (journalctl -b   or   dmesg)
[22:03] <John_in_Calif> I didn't look at the system log but I did check the nvme log and didn't see anything  untword.
[22:03] <tomreyn> then if you're convinced the nvme is still good and you want to try installing to it again, before you do so, use wipefs to wipe all file system structrues off it
[22:04] <John_in_Calif> dmesg: read kernel buffer failed: Operation not permitted
[22:05] <John_in_Calif> I am not convinced that it is good, I just can't see any obvious errors.
[22:06] <John_in_Calif> But if you think that is the most  likely problem, I do have another SSD that is basically new that I can drop in and see if that solves the issue.
[22:07] <tomreyn> you'd need to   sudo dmesg   to overcome the above message
[22:08] <tomreyn> something else you can try is to look for and apply a firmware upgrade for the nvme
[22:08] <John_in_Calif> tomreyn, I think you may be on to something here.  I see lots of this message:
[22:08] <John_in_Calif> nvme0n1: I/O Cmd(0x0) @ LBA 18446744073709551615, 0 blocks, I/O Error (sct 0x1 / sc 0x82)
[22:08] <John_in_Calif> For both partitions.
[22:09] <tomreyn> right, those are likely hardware errors
[22:09] <John_in_Calif> I am going to shut things down and throw in the new SSD.
[22:09] <John_in_Calif> Thanks for your help.
[22:09] <tomreyn> you're welcome
[22:10] <John_in_Calif> By the way, for what it is worth, now I am convinced.
[22:10] <John_in_Calif> Bye
[22:10] <John_in_Calif> And thanks again.
[22:10] <tomreyn> :)
[22:10] <tomreyn> see you
=== william is now known as Willy--