[08:43] <|MA|> hi all
[08:43] <|MA|> I have a kernel buil related issue
[08:44] <|MA|> http://paste.ubuntu.com/376717/
[08:44] <|MA|> any thoughts how i can fix it ?
[08:45] <smb> Install ncurses-dev
[08:46] <|MA|> libncurses5-dev is already the newest version.
[08:46] <|MA|> 0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
[08:47] <ghostcube> smb: i send him here cause i didnt know how to help any firther :)
[08:47] <ghostcube> further even
[08:48] <smb> Maybe some other headers it does not complain about...
[08:48] <smb> Like complete build-essentials...
[08:49] <|MA|> E: Couldn't find package build-essentials
[08:49] <smb> Err, sorry without s at the end
[08:49] <smb> build-essential
[08:50] <|MA|> build-essential is already the newest version.
[08:50] <|MA|> 0 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
[08:50] <|MA|> I did even build the kernel 2 days back
[08:50] <smb> Is your pastebin output all that gets out? Tried "make V=1 menuconfig"
[08:50] <|MA|> running that too ... Linux manu-04 <IP_ADDRESS>-ma3 #1 SMP Sat Feb 13 14:16:22 GST 2010 x86_64 GNU/Linux
[08:51] <|MA|> since yesterday, it is behaving thus
[08:52] <smb> Is /usr/include/ncurses.h still there?
[08:52] <|MA|> ok, here it is: http://paste.ubuntu.com/376736/
[08:53] <|MA|> http://paste.ubuntu.com/376737/
[08:53] <|MA|> It is there, yes
[08:57] <smb> For me that would be a link (which could be broken) but to get the real error you might temporarily edit linux-source-2.6.31/scripts/kconfig/lxdialog/check-lxdialog.sh
[08:58] <smb> and remove the 2>/dev/null in that line $cc -xc - -o $tmp 2>/dev/null <<'EOF'
[08:59] <|MA|> I will temporarily comment it out
[09:00] <smb> The line itselfs must be there
[09:00] <|MA|> http://paste.ubuntu.com/376741/
[09:01] <smb> Sounds like you did the wrong thing to the script
[09:01] <|MA|> only the 2> ... ?
[09:01] <|MA|> let me try again
[09:02] <smb> check() {
[09:02] <smb>         # $cc -xc - -o $tmp 2>/dev/null <<'EOF'
[09:02] <smb>         $cc -xc - -o $tmp <<'EOF'
[09:02] <smb> or like that
[09:03] <|MA|> wow, it comes up again.. let me but paste you the output
[09:04] <|MA|> http://paste.ubuntu.com/376742/
[09:04] <|MA|> thanks
[09:05] <smb> Hm, not really what we wanted
[09:05] <smb> In theory this should just let the error messages go past
[09:05] <|MA|> but it now works at least
[09:05] <smb> Can you do a make clean and then a make with V=1 again?
[09:05] <|MA|> sure, moment
[09:08] <|MA|> here it is: http://paste.ubuntu.com/376746/
[09:09] <|MA|> this is with the commented out stuff in the kernel build script
[09:12] <smb> Hm, now your lines between check() and the include might be interesting. But one other thing, I saw you do a sudo. Might it be you just have a permissions problem? Like written the directory as root?
[09:13] <|MA|> not a permissions problem. Was doing everything with sudo
[09:13] <|MA|> except for the one in between
[09:14] <smb> Ok (though feels a bit dangerous to me, but then not the problem). Can you paste me your lines of the check script then? Should only be three or four so the channel is ok
[09:16] <|MA|> here it is : http://paste.ubuntu.com/376750/
[09:18] <smb> Its quite weird, the change only should make the error messages from the check script go to stderr instead of being suppressed. And the check itself looks at the error code from the call, which should be unaffected. So between before and after it still should fail the same.
[09:19] <|MA|> but now it works for me
[09:19] <smb> Does changing the cc line into "$cc -xc - -o $tmp 2>/tmp/check.log <<'EOF'" make a difference?
[09:19] <|MA|> you mean reverting back ?
[09:20] <smb> Partially. Instead of writing to /dev/null write to /tmp/check.log
[09:20] <smb> Which brings up a weird thought. What does 'ls -la /dev/null' produce?
[09:21] <|MA|> manu@manu-04:/usr/src/linux-source-2.6.31$ ls -la /dev/null
[09:21] <|MA|> crw-rw-rw- 1 root root 1, 3 2010-02-15 00:13 /dev/null
[09:21] <smb> Ok, nothing wrong with that
[09:21] <|MA|> ok, works as well, with the changed script
[09:22] <smb> I bet, if you change it back to how it was, it works as well
[09:22] <|MA|> nothing in /tmp/check.log though
[09:23] <smb> And actually, when I look at your initial posting:
[09:23] <smb> manu@manu-04:/usr/src/linux-source-2.6.31$ make menuconfig
[09:23] <smb> ^ no sudo there
[09:24] <|MA|> uh
[09:25] <|MA|> dang
[09:25] <smb> :)
[09:25] <|MA|> but :
[09:25] <|MA|> changed back
[09:26] <|MA|> http://paste.ubuntu.com/376756/
[09:26] <|MA|> same old thing
[09:27] <|MA|> should i change it back to /tmp/foobar ?
[09:27] <|MA|> eargh .... /me goes nuts
[09:28] <smb> Seems like a very odd thing that writing to /dev/null would fail while other tings work
[09:29] <|MA|> I am out of my wits end
[09:29] <smb> And its probably something not too many try out as root. Most are to paranoid to have the compile run as root
[09:31] <|MA|> my machine is a devel machine, where i err .. work on some drivers ... I am not too paranoid ... There were much more things to be paranoid such as HDD's getting fscked etc etc
[09:31] <|MA|> -were +are
[09:32] <|MA|> If i could get this thing up at the earliest i could get back to my work on some shiny new drivers ..
[09:33] <|MA|> :)
[09:34] <smb> True. And I usually have the tree not that way, so I would not notice oddness. I can try out to have it that way. One thing in general, have you ever tried to get the sources with "apt-get source linux-image-2.6.31-x-generic"? That way you also have the debian build environment with it and the default configs...
[09:34] <smb> I'll try whether having the tree as root shows the same problems here
[09:34] <|MA|> that's what I did initially, but I had to tweak some settings such as MSI-X and some others
[09:35] <|MA|> as well as some more kernel hacks
[09:36] <|MA|> that would be great. Thanks a lot
[09:36] <|MA|> at least I am able to get back to get it up at least
[09:37] <|MA|> Other than that, I am  a bit annoyed with the nvidia post install script as well. kernel install failed earlier, then i had to remove the nvidia-common package
[09:37] <|MA|> which helped me to get the kernel installed
[09:37] <|MA|> so many new hassles introduced ... wasting a lot of precious time
[09:38] <smb> Yes, I'd probably use the /tmp/foo variant. You could base on apt-get source version for your work and make tweaks to debian.master/config
[09:38] <|MA|> also applications such as acroread doesn't work. You know: evince and such applications do not open all the PDF file formats, that's to add to the yuck's
[09:39] <smb> Not sure what the problem with the post install is. But usually most things are set to work with the .debs produced by compiling the debian way.
[09:39] <|MA|> all these made me pull out my hair a lot, it took me 2 days to get the system up, as opposed to a few hours as of earlier versions
[09:40] <smb> And acroread, well... Seems to work for me, which is likely not much help
[09:40] <|MA|> well anyway, I got to get it going with a virtual host machine and used acrobat reader there. No other alternative ...
[09:41] <|MA|> since some of the document would open there alone, due to security reasons
[09:45] <smb> security reasons? So a make menuconfig works for me here. Could it be you got some security framework active that might be over restrictive?
[09:46] <|MA|> by security reasons, I mean protected documents from some people that i receive. Those documents seem to open only with acroread and hence.
[09:46] <smb> ahh ok, misunderstanding there, then
[09:47] <|MA|> some nastiness in those docs. They are sometimes password protected; then you can't copy/paste etc
[09:48] <|MA|> so regular pdf readers don't handle all those stuff
[09:48] <|MA|> and hence the document in some cases don't open up, or look like some Martian languages, like fully clobbered up
[09:49] <|MA|> in short, if you seriously use PDF docs, acroread is in some case unavoidable
[09:49] <smb> Had something like this. But in my case evince was able but acroread wasn't (due to fonts). But in generall acroread works on this system
[09:49] <|MA|> unless other apps catch up
[09:50] <smb> As well as I cannot reproduce your strange problem with the compile.
[09:50] <|MA|> I have been going through real weirdness. Don't just remind me of it
[09:51] <|MA|> and that too, when you just want to get something moving really fast
[09:51] <smb> Unfortunately that happens usually whenever you want something done fast... :/
[09:52] <|MA|> true: murphy is there to strike at will
[09:52] <smb> One thing you could check is apparmour_status. Not really expecting something there, but...
[09:53] <|MA|> I had disabled apparmour completely
[09:53] <|MA|> not wanting to have such stuff on a development machine
[09:53] <|MA|> i would more or less term it as an open frame machine ... ;-)
[09:54] <|MA|> where i can swap the hardware, cards in really fast
[09:55] <smb> Well, that should be possible with or without apparmor. :) But at least without it it cannot be any reason for strangeness
[09:55] <|MA|> yup :)
[09:55] <smb> Just for a test. When you are root. Can you do a echo bla >/dev/null?
[09:55] <|MA|> sec
[09:56] <|MA|> yes, i can
[09:56] <|MA|> manu@manu-04:~$ sudo echo blahblah >/dev/null
[09:56] <|MA|> [sudo] password for manu:
[09:56] <|MA|> manu@manu-04:~$
[09:57] <smb> No, do the sudo -i before
[09:57] <smb> That way null is opened as the user
[09:58] <|MA|> yup
[09:58] <|MA|> root@manu-04:~# echo blahblah >/dev/null
[09:58] <|MA|> root@manu-04:~#
[09:59] <smb> Then I must admit, I cannot really help as I have no clue what might be wrong, sorry.
[09:59] <|MA|> but anyway, you have been a big help. At least I can get going on it
[09:59] <|MA|> thanks again
[10:00] <smb> Yeah, at least some workaround. Though it feels like "quick backup all your work, this machine is odd"...
[10:01] <|MA|> I have all my work, except for the kernel builds on a completely separate hdd
[10:01] <|MA|> even in case something causes a freeze and fscks my /
[10:02] <smb> Ok, very reasonable for a development box. :)
[19:44] <crimsun> ooh, exmap is fixed


[10:13] <juliux> katkin: thanks for the pens
[15:07] <bahaa2008> hi all
[15:07] <bahaa2008> i want banners to advertise for ubuntu


[16:40] <OvenWerks> Eickmeyer: I don't know if you remember some one complain about zita giving high levels? anyway, Fons says: This is due to a bug in libzita-alsa-pcmi, which will affect all
[16:40] <OvenWerks> sound cards using the S32_LE format.
[16:40] <OvenWerks> This is s fixed in version 0.6.1 which is now available at the usual place:
[16:41] <Eickmeyer> OvenWerks: I do remember.
[16:42] <OvenWerks> I do not know if that means there is a new zita-ajbridge or that it needs to use the new libzita-alsa-pcmi
[16:45] <OvenWerks> it's the lib
[16:45] <OvenWerks> we have 0.2.0
[16:49] <OvenWerks> Eickmeyer: why do we have such an old version?
[16:49] <Eickmeyer> #BlameDebian
[16:49] <OvenWerks> I am guessing libs are harder to keep up with
[16:59] <OvenWerks> libzitaresampler is up to date-ish except Fons' site has two of them (1.6.2 and 1.8.0) we have the older one
[17:05] <Eickmeyer> OvenWerks: Jammy has 0.4.0, Kinetic has 0.5.1. I don't know where you're getting 0.2.0 from.
[17:05] <Eickmeyer> Bionic has 0.2.0.
[17:06] <Eickmeyer> (we should really take this to -devel)
[19:51] <ardya> hi folks, Ubuntu 22.04...ssh logins start autojack process and kills existing jack session for other user logged into the desktop env, any thoughts on troubleshooting/disabling this behaviour with ssh logins?
[19:54] <OvenWerks> ardya: hmm, that is not right... but probably fixed already
[19:55] <OvenWerks> for a while autojack was started by systemd via logind. that shouold no longer be the case.
[19:55] <OvenWerks> ardya: are you set up for backports?
[19:56] <ardya> yes i think its starting through systemd...checking for back-ports
[19:56] <OvenWerks> ubuntustudio-installer has a button to add backports
[19:56] <ardya> also any idea why creating outgoing net bridges doesnt work in studio contriols?
[19:56] <Eickmeyer> Yes.
[19:57] <OvenWerks> it worked the last time I tried it... but things change.
[19:57] <ardya> hmm yeah back-ports is alreqady enabled
[19:58] <ardya> incoming net bridges work, have to manually create outgoing via terminal
[19:58] <OvenWerks> autojack should be started by the session manager then from /etc/xdg/autostart/ so I would think not from terminal login.
[20:00] <OvenWerks> on the system tweaks page the debugging level can be set to "Extra", start the bridge and then errors might show in ~/.log/autojack.log
[20:01] <ardya> I see autojack references in /etc/systemd/user/default.target.wants/studio.service /etc/xdg/systemd/user/default.target.wants/studio.service
[20:02] <OvenWerks> The first one should probably not be there. I wonder if the uninstall script or postinstall needs to remove it.
[20:04] <Eickmeyer> It'll have to be a .maintscript with rm_conffile because it's in /etc. That's the pain of /etc for ya.
[20:04] <ardya> he log says zita-j2n cant be found, but its at /usr/bin/zita-j2n
[20:05] <OvenWerks> is it looking for zita_j2n by chance?
[20:05] <OvenWerks> hmm you would have to look through file in /usr/bin/autojack
[20:06] <OvenWerks> search for zita_ there should be none but if there is change it to - with sudo nano I guess
[20:07] <OvenWerks> I sort of remember finding something like that that is fixed in the yet to be released version
[20:07] <Eickmeyer> OvenWerks: If I can find it I can throw out a patched version.
[20:07] <Eickmeyer> Just in the meantime.
[20:07] <OvenWerks> sure
[20:08] <OvenWerks> up the version somehow
[20:08] <Eickmeyer> It's easy. It'd literally be a quilt patch.
[20:08] <OvenWerks> (somehow means using the prefered ubuntu method)
[20:09] <ardya> no underscore
[20:09] <Eickmeyer> I couldn't find it either.
[20:10] <ardya> should there be a call to zita-j2n in the studio-controls python script?
[20:10] <OvenWerks> ardya: yes
[20:12] <Eickmeyer> There isn't one in studio-controls. Only in autojack.
[20:14] <ardya> I removed that one link /etc/systemd/user/default.target.wants/studio.service and rebooting
[20:15] <OvenWerks> right
[20:16] <OvenWerks> Eickmeyer: it is in autojack lines 180 to 200
[20:17] <Eickmeyer> OvenWerks: Yes, but no underscore.
[20:17] <ardya> well that didnt work, ssh login killed the sessiion
[20:17] <OvenWerks> I don't see the problem looking at autojack on github....
[20:17] <Eickmeyer> OvenWerks: Are you looking at the 2.3.9 tag?
[20:17] <Eickmeyer> I don't see the problem either.
[20:24] <OvenWerks> ardya: which version of studio-controls do you have (should show on the main screen at the top)
[20:24] <ardya> 2.3.1
[20:25] <OvenWerks> oh.... the latest is 2.3.9
[20:26] <ardya> its not been pushed to 22.04
[20:26] <OvenWerks> backports should have brought in
[20:27] <ardya> Version: 2.3.1-0ubuntu2
[20:30] <Eickmeyer> Version in Backports is 2.3.9-0ubuntu1~bpo22.04.1~ppa1 so you don't have the fixed version.
[20:30] <Eickmeyer> By backports we mean the backports PPA in ubuntustudio-installer
[20:31] <Eickmeyer> !ubuntustudio-installer
[20:31] <Eickmeyer> !ubuntustudio-backports
[20:31] <ardya> oh ppa
[20:31] <ardya> no I dont have that
[20:31] <Eickmeyer> You need that.
[20:31] <ardya> and I think I fixed the ssh login killing jack
[20:31] <Eickmeyer> We can't SRU the fixed version because it contains too many new features.
[20:32] <Eickmeyer> Open Ubuntu Studio Installer, click the button that says "Enable Backports PPA".
[20:32] <ardya> ok I'll add the PPA
[20:36] <ardya> updating...guys, thanks, and appreciate your efforts in maintaining all this. My main DAW still runs on 18.04 and I have that mofo tweaked like crazy, test driving 22.04 on a laptop to see what changes I'll have to make to get same functionality
[20:37] <Eickmeyer> That backports PPA does not include the latest update of Ardour, btw. That's in a separate PPA at ppa:ubuntustudio-ppa/ardour-backports
[20:37] <ardya> I dont use studio-controls on 18.04, its all manually configged, scripted etc
[20:38] <ardya> I dont use ardour, been using reaper
[20:38] <ardya> thanks though
[20:41] <Eickmeyer> ardya: FYI, 18.04 has been EOL since January 2019, so I don't know what you've been doing this whole time.
[20:45] <OvenWerks> if it works and is not connected its fine.
[20:45] <OvenWerks> but yeah no security updates that way.
[20:47] <OvenWerks> ardya: just a heads up, it looks like 32.04 is defaulting to pipewire to replace both jack and pulse.
[20:50] <OvenWerks> ardya: the plan is to allow pulse/jack (as now), PipeWire alone, PipeWire/jack or PipeWire with jack as a device.
[20:50] <OvenWerks> ardya: however, in the long run pulse will for sure go away.
[20:52] <OvenWerks> pipewire works quite well for most modern devices and ok with all alsa devices. the alsa FW stack is not great for low latency audio.
[20:56] <ardya> LOL same error cant find zita-j2n
[20:57] <ardya> 18.04 is LTS and still supported
[20:59] <oerheks> ehm, gnome 18.04 LTS is supported, other flavors 3 years
[21:02] <ardya> ah ha!
[21:02] <ardya>             cmd = "zita-j2n "
[21:02] <ardya>             cmd = "zita-n2j"
[21:03] <ardya> note the space in the quote
[21:06] <ardya> found that in /usr/bin/autojack
[21:10] <Eickmeyer> ardya: 18.04 is not LTS for Ubuntu Studio, see https://ubuntustudio.org/2018/05/clarification-on-non-lts-status-of-ubuntu-studio-18-04/. Additionally, official flavors (read: not Ubuntu Desktop or Ubuntu Server) typically only release as LTS for 3 years.
[21:11] <ardya> hmmm removing that space didnt fix it
[21:12] <Eickmeyer> oerheks: ^
[21:12] <ardya> Eickmeyer: I'll take your word for it, but I still get updates for it, last ones were 12-15-2022
[21:13] <Eickmeyer> ardya: You're only getting updates from the main repository, not the universe repository. I'm the leader of Ubuntu Studio, so you're getting it from the horse's mouth.
[21:14] <Eickmeyer> The universe repository contains the components that make it "studio".
[21:19] <ardya> understood, thanks
[21:20] <Eickmeyer> ardya: I do see the bug, I can definitely patch that. OvenWerks  cmd = "zita-j2n " in autojack line 181
[21:20] <ardya> still no go on the net send bridge
[21:20] <Eickmeyer> Even with the space removed?
[21:21] <ardya> removing that space didnt fix :(
[21:21] <Eickmeyer> Probably because in shells spaces don't matter.
[21:23] <Eickmeyer> ardya: Actually, try closing studio controls, killall -9 autojack, and start studio controls again.
[21:27] <ardya> I had rebooted after removing the space
[21:29] <ardya> and the no process found thing comes from when the call to kill the old zita-njbridge conns occurs, there's no bridges running
[21:29] <ardya> and I dont see any messages in the log when trying to add a net send bridge...
[21:30] <Eickmeyer> This is very much up OvenWerks's alley, no idea why it's not working.
[21:30] <Eickmeyer> I mean, if it's not even doing a command-not-found something isn't right.
[21:33] <ardya> oh boy, now net receive bridges dont come up
[21:45] <ardya> ok well I'm going to figure out how to revert this
[21:49] <OvenWerks> ardya: the other possibility would be to use the postrun script to start a njbridge.
[21:50] <ardya> whats that scriptname?
[21:50] <OvenWerks> ~/.config/autojack/poststart
[21:51] <OvenWerks> needs to be a bash script... well I guess if it has #!/bin/whatever that would work too.
[21:52] <OvenWerks> it needs to be chmod +x in other words
[21:53] <OvenWerks> ~/.config/autojack/postbridge runs after the pulse bridges are set up
[21:55] <ardya> do the procs in the script need to be backgrounded?
[21:56] <ardya> hung in poststart
[21:56] <ardya> so probably
[22:00] <ardya> hmm nope still hung in poststart
[22:07] <ardya> gah this flippin laptop..
[22:08] <ardya> ok guys thanks again...I need to wipe and restart from scratch
[22:47] <ardya> haha nice, finally got the studio iso to boot on this POS laptop
[22:47] <ardya> cheers, and thanks again!