[06:58] <Guest58> Hello. I think there is a mistake on the Downloads page. It says Kubuntu 24.04 will be supported until April 2032. The release notes say it will be supported for 3 years.
[07:24] <kirvesAxe> XLTS? :P
[07:32] <bombastick> other than the desktop UI, what differences exist between Kubuntu and Ubuntu?
[07:32] <bombastick> If we ignore the UI, and we ignore the default GUI packages
[07:33] <bombastick> like will multiple monitor usage be harder on Kubuntu due to the much smaller team and  testing?
[07:33] <bombastick> that sort of stuff
[07:46] <guiverc> bombastick, if you wanted to contrast what kubuntu ISOs install & Ubuntu Desktop; you could always explore the manifest (do note some install options won't install all packages..)  Kubuntu is a Ubuntu Desktop system but with certain packages changed (KDE Plasma instead of GNOME, Qt5/KF5 instead of GTK etc... 3 years flavor support instead of 5 year Canonical support..
[07:47] <guiverc> I'd not expect any difference between monitor.usage.. as that's generally handled much closer to kernel where systems are identical (eg. kernel modules aka drivers; they're identical)
[07:48] <bombastick> guiverc: yeah I knew that, just wondering what major things run worse on Kubuntu in practice. Even if we ignore the packages common to both, Ubuntu probably has 100x the developer and tester count Kubuntu does. So there's gonna be stuff they do better.
[07:48] <guiverc> though do note flavors install a different kernel stack by default to Ubuntu Desktop; that won't make a difference for some time though (Ubuntu Desktop will move to use 24.10 kernel in the future; a Kubuntu ISO will use GA)
[07:50] <guiverc> I don't see the difference in the way you do....  Testers are still Ubuntu community testers... Ubuntu Desktop does benefit from Ubuntu Security team checks; Ubuntu Security team do not check universe (community packages) unless you enroll with Ubuntu Pro  (and then only some packages)
[07:51] <guiverc> eg.  during mantic cycle this box with 5 displays connected had 2 show black screen... it impacted all 3 desktops I have installed equally...   I ended up non-destructively re-installing this system eventually to fix it.. then all 3 desktops worked again... same reaction with GNOME as per LXQt, Xfce etc
[07:54] <guiverc> Much of the KDE Plasma comes from upstream KDE Project... just as Ubuntu Desktop is very much GNOME from upstream.  Yes there are a few Ubuntu Desktop team (paid staff) that tweak & refine it more than maybe Kubuntu does the upstream KDE Plasma ... but the team isn't that big (just full-time paid)..
[07:57] <bombastick> I see. Thanks.
[08:55] <bombastick> huh, website says "Kubuntu 24.04 supported with security and maintenance updates, until April 2032". I thought Kubuntu was 3 years?
[08:56] <bombastick> must be a typo, the wiki's release notes say 3 years
[08:56] <Kangarooo> To what package to report that Latvian keyboard in Kubuntu one keyboard shortcut makes wrong symbol
[08:56] <bombastick> The tyypo is here: https://kubuntu.org/getkubuntu/
[10:35] <guiverc> thanks bombastick, it'll need to be fixed by a kubuntu team member with authority to login to site & change  (website)
[12:13] <BluesKaj> Hi all
[13:50] <bombastick> is it possible to make the desktop context menu have a "Open Terminal" option like normal Ubuntu does?
[13:51] <bombastick> I guess I can just add a desktop shortcut
[13:51] <bombastick> what's the point of enabling 32-bit packages by default as Kubuntu seems to? All it does is make "apt update" slower.
[13:54] <BluesKaj> or install yakuake drop down terminal  which opens with F12 key
[13:56] <bombastick> BluesKaj: nice! me likey
[13:57] <bombastick> it's been years since ive browsed apps.kde.org, i think I need to give it another drive by
[13:57] <BluesKaj> bombastick:  yup, it's worth the drive :-)
[14:18] <bombastick> BluesKaj: I just wish apps would use the same keyboard shortcuts we're all used to. Like I dont get why CTRL+T doesnt create a new tab, or CTRL+TAB cycle between tabbed sessions
[14:18] <bombastick> Just adopt the same shortcuts as every browser does
[14:18] <bombastick> instead of being a snowflake
[14:18] <terra> Hi! One quick question. Just did a fresh install of 24.04 LTS! Loving it so far... I have one point of confusion over some packages that install with a t64 ending.
[14:19] <terra> in particular when trying to reinstall Da Vinci Resolve, I get a missing dependency: "
[14:19] <terra> Please install the following missing packages:
[14:19] <terra>     libapr1 libaprutil1 libasound2 libglib2.0-0
[14:20] <terra> but "sudo apt install libapr1" defaults to package ending in t64 (terminal output: Note, selecting 'libapr1t64' instead of 'libapr1')
[14:21] <bombastick> terra: idk why it does that, i'm new to it myself, but this shouldnt affect anything (also you will need to install libasoundt64)
[14:22] <terra> here I find libapr1 referred to as a "virtual package" https://packages.ubuntu.com/noble/allpackages
[14:22] <terra> the Da Vinci installer does not see those packages as the ones it requires
[14:23] <bombastick> the tool you're trying to use is looking for specific libraries on the system, not package names, that's just a convenient message. So if libasound2t64 installs /usr/lib/x86_64-linux-gnu/libasound.so.2 (it does), that's all that matters
[14:23] <bombastick> oh shit, it refuses to run based on package names?
[14:23] <terra> I can run the Da Vinci Resolve installer with this variable SKIP_PACKAGE_CHECK=1 ./DaVinci_Resolve_Studio_18.6.6_Linux.run and it will install but then it doesn't run
[14:24] <terra> going to give that another shot, actually
[14:24] <bombastick> terra: can you run "ldd ./path/to/davinci/binary?
[14:24] <bombastick> and list the ones that say "Not found"
[14:25] <bombastick> then apt install apt-fil, then "sudo apt-file update", then for each library not found, run "apt-file find <filename of missing file>"
[14:26] <terra> checked /usr/lib/x86_64-linux-gnu/libasound.so.2 and I have the file indeed
[14:26] <terra> thank you, reinstalling Resolve now and trying that
[14:26] <bombastick> before you reinstall
[14:27] <bombastick> "ldd somebinary" tells you what C/C++ dependencies the binary needs to run
[14:27] <bombastick> you dont need to reinstall, it doesnt change this
[14:27] <terra> oh I see
[14:28] <bombastick> if DaVinci's only requirements are C/C++ libraries then the approach I described will allow you to run it.
[14:28] <bombastick> (libXXXX packages are usually all C libraries)
[14:28] <terra> dd ./DaVinci_Resolve_Studio_18.6.6_Linux.run
[14:28] <terra>         not a dynamic executable
[14:28] <bombastick> no that's an installer, not the final binary you run to launch it
[14:28] <terra> *ldd
[14:29] <terra> I see
[14:29] <bombastick> you said "it will install but not run", I want you to try it on the executable that doesnt run
[14:29] <bombastick> for example ~/tools/davinci/bin/davinci or whatever
[14:29] <bombastick> I've never installed this tool so idk
[14:29] <terra> okay
[14:30] <terra> I see, so I will reinstall and run it on the executable in /opt
[14:38] <terra> hmm, the libraries all seem to be found... https://pastebin.ubuntu.com/p/wZxPdZXTM3/
[14:41] <bombastick> terra: ouch, I'm out of ideas then. If they have forums you should ask there. This is too specific to be solveable here. I think their doc is not up to date for Ubuntu 24.04 that just came out, and in the coming week you will have new doc, or perhaps someone will post on the forum ahead of time (forum or subreddit)
[14:42] <terra> When I try to run the binary from terminal I get this message
[14:42] <bombastick> I think therir installer's package check must be fetching other (not C) packages, like Python or Javascript
[14:42] <terra> terra@terra-alienwarem17:/opt/resolve/bin$ ./resolve
[14:42] <terra> ./resolve: symbol lookup error: /lib/x86_64-linux-gnu/libpango-1.0.so.0: undefined symbol: g_once_init_leave_pointer
[14:43] <bombastick> oh, it is a C issue...
[14:43] <terra> interestingly it seems to be a different library
[14:45] <bombastick> Not sure what you can do. This is a mismatch in the pango library Davinci depends on. Their next update will probably fix it. Maybe someone on the forums has a temporary fix before then (probably building an older libpango)
[14:46] <terra> thank you very much bombastick, I will wait for their next release
[14:47] <bombastick> with Linux you c ant really be on the bleeding edge of software if you're not a more advanced user who can investigate/fix issues himself. For example I installed Kubuntu in a VM just now and the Virtualbox Guest Addition tools have some errors. It will probably be fixed in the next version of Virtualbox, but it is what it is
[14:48] <bombastick> so try to stay 1 month behind on stuff (ie dont update immediatley)
[14:56] <terra> I managed
[14:56] <terra> https://www.reddit.com/r/Fedora/comments/12z32r1/davinci_resolve_libpango_undefined_symbol_g/?rdt=33605 https://www.reddit.com/r/voidlinux/comments/12g71x0/davinci_resolve_18_symbol_lookup_error_libgdk/
[14:57] <terra> oddly enough deleting
[14:57] <terra> /opt/resolve/libs/libglib-2.0.so*
[14:57] <terra> /opt/resolve/libs/libgio-2.0.so*
[14:57] <terra> /opt/resolve/libs/libgmodule-2.0.so*
[14:57] <terra> did the trick
[14:58] <terra> I updated to the new LTS because this laptop has been always having problems with all previous releases and it had just recently broken (nvidia drivers), oddly enough 24.04 looks great on (it's an hdpi and it's first time that it looks right)
[14:58] <terra> it's not my main driver
[14:59] <terra> thank you for helping me out
[21:03] <mas886> So I noticed my plasma being a little sluggish, so I tried to switch GPU drivers to a newer version using additional drivers tab (I'm on an Nvidia 4070). This popped a warning saying it was not compatible with my kernel, and apparently switched back to previous version. But when I reebooted my system it is showing a console with text "UBSAN:
[21:03] <mas886> array-index-out-of-bounds in /var/lib/dkms/virtualbox..." and plasma won't boot (tho i can use the system console mode in another session). Any idea how to get my system working? Found the issue in google, but any solution so far.