[Bug 1911837] Re: inxi, error "Use of uninitialized value $val2"
That version is about 100 releases old, it's not my fault linux mint refuses to ship a current inxi. File a bug report with linux mint where it might do some good, not here, the ubuntu version in Jammy is current, and hirsute and impish both have 3.3.0x inxi versions as well. Mint failing to update isn't an inxi bug, it's not an ubuntu bug, and its not a Debian bug, it's a Mint bug, so file the issue there, ask them to update inxi, god knows I've tried doing that enough times to finally give up on trying anymore, but maybe more voices will get them to stop shipping that antique inxi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911837 Title: inxi, error "Use of uninitialized value $val2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1911837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911837] Re: inxi, error "Use of uninitialized value $val2"
Current inxi release is 3.3.13. What is 'this' referring to? Never use the term 'this' when discussing technical issues, it does not narrow it down enough to convey meaning. Rather than ask if 'this is still an issue', why don't you test it and see? The bug reported here is 50 to 100 releases of inxi ago. jammy has 3.3.13 as of now. An undefined data bug would have been fixed immediately once detected and reported. I believe this issue was closed ages ago, and if not, it should have been. Did you possibly post in the wrong bug issue? If you have a new issue, then file it as such, but make sure you are talking about current inxi, from the github master branch, not a legacy unsupported version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911837 Title: inxi, error "Use of uninitialized value $val2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1911837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911837] Re: inxi, error "Use of uninitialized value $val2"
Note that the option --tty also often takes care of these issues, that was added before 3.0.32, though I'm not positive about which bug this user has, but they can trivially verify by simply testing on current inxi, if it goes away, the bug was fixed long ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911837 Title: inxi, error "Use of uninitialized value $val2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1911837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911837] Re: inxi, error "Use of uninitialized value $val2"
This version of inxi is obsolete, inxi is on version 3.2.02 right now. Bugs like this are only meaningful if the poster downloads current inxi and reproduces them on current release. I believe the ssh -C bug was fixed quite a while ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911837 Title: inxi, error "Use of uninitialized value $val2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1911837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899192] Re: inxi 3.1.07-1-1 does not report Desktop version
This apparently has been going on in ubuntu for longer than I realized, I assume one of the fallback tests which used to work must now be failing. Added more filters for these types of changes, and re-ordered some of the detection for gnome to avoid a case where it is gnome but it fails the detection due to unknown values in the id, like ubuntu:, although that specific instance is now filtered out. this update is in pinxi [inxi-perl branch of inxi] but I don't know when it will go out, maybe sooner than later to hit the 20.10 non beta release. These kinds of silly changes are without a question my number one pet peeve with the entire linux ecosystem, distros, random pointless string value changes done for no good reason, and never considering that tools might actually be USING the data that those strings and variables contain. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899192 Title: inxi 3.1.07-1-1 does not report Desktop version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1899192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899192] Re: inxi 3.1.07-1-1 does not report Desktop version
this is a regression in the beta 20.10 gnome ubuntu desktop ID. It is not possible to know if they will correct this regression or not. the value $GDMSESSION should be 'gnome' but is 'ubuntu', that is completely wrong, GDMSESSION is supposed to identify the gnome desktop, not the distro name. This is bug one in the beta. bug two is similar: $XDG_CURRENT_DESKTOP has likewise been corrupted, leading to a secondary detection failure: ubuntu:GNOME the ubuntu name string has no business being in there, but that one is easier to correct. The corruption in $GDMSESSION I suspectc is a straight beta bug, and should be reported to ubuntu since it's just wrong, ubuntu is NOT the gdmsession owner, GNOME is. This issue is invalid because it is relating to beta release ubuntu and we have no way of knowing if these two regressions are going to remain in the final release, or if they were just working ideas that will be removed, as they should be, since they break all existing detection methods, and serve no valid purpose. Note that I realized that it would be largely a waste of time trying to get actual debugging data from the issue poster, so I grabbed the beta iso and ran it in a vm, but I will NOT normally do this because it's a waste of my time, so in this case, it was which would waste less of my time. I do not normally track launchpad issues, nor should it be used for beta release issues since those are beta, not final, release, and thus by definition invalid until confirmed by ubuntu to be the final idea, which I hope it isn't since it just adds another pointless layer of complexity to desktop detection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899192 Title: inxi 3.1.07-1-1 does not report Desktop version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1899192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899192] Re: inxi 3.1.07-1-1 does not report Desktop version
File an issue, as I already told you, on https://github.com/smxi/inxi about the desktop issue. This requires data and discussion, and launchpad is the wrong place for that. I cannot reproduce your system, nor do I have any actual idea of what you are doing to lead to desktop detection failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899192 Title: inxi 3.1.07-1-1 does not report Desktop version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1899192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896071] Re: inxi 3.1.06-1-1 does not report Compiler an Desktop
Please DO NOT tack on totally unrelated issues, the desktop has NOTHING to do with the compiler. The compiler issue is fixed. If you have other issues, file an issue on github inxi, the desktop logic is totally unrelated, and can be quite complicated to debug, certainly not an appropriate issue for launchpad, file it where it will make a difference: https://github.com/smxi/inxi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896071 Title: inxi 3.1.06-1-1 does not report Compiler an Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1896071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898829] Re: CMOS-battery status missing in "inxi -B"
https://www.kernel.org/doc/Documentation/rtc.txt just a bit of info on rtc drivers. While rtc is something, it's not necessarily the cmos battery, it's just a chip that the system can use to determine time. So it would not be a cmos battery it would be an RTC battery, since there would be no way for inxi to know what it was, there can be more than one for example. This bit of data is unlikely to make it into inxi I have to admit since I would need to see much more information about variation and > 1 rtc systems and systems where the battery was dead or whatever else can happen, but in no case would it be a cmos battery state, it would be an rtc chip state, but, again, since I have no real data on this, no examples of complex systems, etc, it's unlikely this will be added. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898829 Title: CMOS-battery status missing in "inxi -B" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1898829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898829] Re: CMOS-battery status missing in "inxi -B"
Then there is no data available, which means the issue is not valid, nor is there anything indicating that that data is available. As an aside I do not remember ever seeing CMOS battery state listed when testing or checking inxi -Bx results or datasets, usually the Device-x: battery states belong to things like wifi mice, keyboards, and other external battery driven devices that report their battery state to the linux system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898829 Title: CMOS-battery status missing in "inxi -B" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1898829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898829] Re: CMOS-battery status missing in "inxi -B"
As an aside, if you have a feature request, file it on https://github.com/smxi/inxi otherwise it won't really make any difference since I don't routinely follow distro issue trackers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898829 Title: CMOS-battery status missing in "inxi -B" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1898829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898829] Re: CMOS-battery status missing in "inxi -B"
This is not a valid issue, and it's not a bug. Also, the poster didn't read the help/man at all, since to see other device batteries listed, you have to use -Bx, not -B alone. -B alone only shows results for laptop batteries, basically. If -Bx does not show the cmos battery, then inxi can't find it, the data is not anywhere it can locate. If -Bx shows the device battery then obviously the issue is completely invalid in the first place, and if it doesn't, it means inxi has no access to it, which means the issue is invalid. /proc is not used to get battery data, that comes from /sys. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898829 Title: CMOS-battery status missing in "inxi -B" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1898829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896071] Re: inxi 3.1.06-1-1 does not report Compiler an Desktop
This issue is resolved in the pinxi branch, and will be in next inxi, 3.1.07, whenever that comes out, probably soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896071 Title: inxi 3.1.06-1-1 does not report Compiler an Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1896071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896071] Re: inxi 3.1.06-1-1 does not report Compiler an Desktop
This is caused by a syntax change in /proc/version Since I had no /proc/version for ubuntu I had to guess, the issue was resolved for the distros that I got to see samples from, but I have yet to see a /proc/version output for ubuntu kernel 5.8. Note this is NOT a bug in inxi because the syntax in question has been stable ever since inxi offered the compiler version for kernel, this was a change done for unknown reasons, and in a non standard manner, and will require more /proc/version samples from different distros to fully cover. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896071 Title: inxi 3.1.06-1-1 does not report Compiler an Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1896071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827486] Re: Weather data failure
This is not a bug, the weather source that was in inxi 2.x and 3.0.31 and earlier is gone. The only fix for weather is to update to current inxi (3.0.33 in ubuntu, and 3.0.34 in master branch of github inxi). The reason later versions work is because they point to a new weather data source. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827486 Title: Weather data failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1827486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617075] Re: inxi does not display all partition data
Just as an aside, I checked, and in fact, dmidecode calls a UEFI a BIOS. I checked that output for the same UEFI machine. However, there appears to be two or three possible paths that are present in a UEFI system but not in a BIOS system, so it may work fine, and easily, relatively, to indicate UEFI for newer gnu/linux systems or BIOS, which would be a nice upgrade to make anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617075 Title: inxi does not display all partition data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1617075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617075] Re: inxi does not display all partition data
https://github.com/smxi/inxi/issues You'll want to post this exact issue report on the inxi github. You're correct re BIOS being technically incorrect however because line space is at a premium in inxi, any term that encompasses bios and uefi type firmware has to be crystal clear and SHORT, and clear enough where all users would understand it. It might actually be possible for inxi to be smart enough to detect when it's uefi and when it's bios, not sure, depends on if that data exists in the /sys data. Might. I can check some of the user data sets. There's two levels of partitions, P and p, P is the basic stuff, p is everything I've been aware of, you'd be the first person to note they are using /var/temp and /var/log as separate partitions. It's a whitelist test, so inxi has to know about the possible values to add them, so that's easy to correct. If you can think of others that could possibly be used as well add them to the issue report, it's easy to add stuff to that detection. The best solution for the bios issue would be to actually detect if it's bios or uefi, which I'd need to pull out of /sys for newer gnu/linux systems, and out of dmidecode data for systems without that /sys data, like bsds and older linuxes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617075 Title: inxi does not display all partition data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1617075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
