Your feedback

Me

Do you have any questions with regard to my packages, SlackBuild scripts, other scripts, or my documentation? Or do you have a request to make? Please use this space to write down your ideas and I will try to answer. Other readers are of course also allowed to voice their thoughts about what you write.

Keep your posts on topic please. No flamewars, trolling, or other nastiness allowed. This is not meant to be a replacement for LinuxQuestions.org

If the blog refuses to accept your post, then perhaps you are affected by a bug in the SQLite plugin. Check if your post contains a string of text which is enclosed by the characters ( ). Is there a pipe symbol or a comma inside those round brackets? Try to remove those and re-post your comment.

My old feedback page got too big with all the comments, so I archived it here: “your older feedback

Continue to my blog articles.

Eric

27 thoughts on “Your feedback




        1. Aegisub should compile against wxGTK3 if you add this parameter to the configure (assuming you installed my wxGTK3 package):

          # configure –with-wx-config=/usr/bin/wx-config-gtk3


  1. Hi there!

    Are you aware of any problem with Plasma starting in the last couple of days? I am not sure when exactly.

    Today I had to log out and when tried to log in again I simply couldn’t. I started to troubleshoot the issue and initially there was apparently a problem with “baloo” that was generating tons of log messages (similar issue than explained here https://askubuntu.com/questions/1214572/how-do-i-stop-and-remove-kde-baloo-that-is-broken-and-filling-up-my-syslog-file), after stopping baloo I was able to log in again, but I had to try to reproduce the problem … so I logged out and in again, and I just couldn’t. I tried to identify the problem but unsuccessfully so far. So I just removed the whole KDE and installed again from your repository, but with no luck. I can open other desktop environments, as XFCE that I am using right now without issues, and will continue troubleshooting to see if I can find the problem, but just wonder if you (or any of your followers) is experiencing similar problems.

    Thanks!


    1. I am using KDE Plasma5 on Slackware64-current every day, the whole day, and have no issues.
      My desktop (which I use more at the moment than my laptop) has a Nvidia GPU and I use their binary drivers. Also I added the PAM support from the Slackware (and ktown) testing area.
      Baloo can be resource-intensive during the first hours on a freshly installed system while it is busy indexing your files, but that will go back to normal once the indexing is complete. Sometimes a baloo index becomes corrupted (for instance when you do a forced power-down) and then you need to stop baloo, delete its index and restart baloo. But issues with baloo should normally not prevent you from logging in. Is your harddisk having physical issues perhaps?

      To remove and re-create the baloo database, try:
      # balooctl stop ; balooctl disable ; rm -rf ~/.local/share/baloo ; balooctl enable ; balooctl start


      1. Hi again.

        No, the hard disk is a new one and apparently has no errors.

        When starting Plasma from the console it get stuck with this messages:

        Registering “:1.35/StatusNotifierItem” to system tray
        Registering “:1.78/StatusNotifierItem” to system tray
        Registering “:1.80/StatusNotifierItem” to system tray
        qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1302, resource id: 98566147, major code: 7 (ReparentWindow), minor code: 0
        qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1304, resource id: 98566147, major code: 141 (Unknown), minor code: 1
        qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1305, resource id: 98566147, major code: 6 (ChangeSaveSet), minor code: 0
        qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1306, resource id: 98566147, major code: 25 (SendEvent), minor code: 0
        qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1307, resource id: 98566147, major code: 12 (ConfigureWindow), minor code: 0
        qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1309, resource id: 98566147, major code: 12 (ConfigureWindow), minor code: 0
        qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1310, resource id: 98566147, major code: 8 (MapWindow), minor code: 0
        qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1311, resource id: 98566147, major code: 61 (ClearArea), minor code: 0
        Service “:1.78” unregistered
        Container window visible, stack below
        kdeinit5: Got EXEC_NEW ‘/usr/lib64/qt5/plugins/kf5/kio/file.so’ from launcher.
        kdeinit5: preparing to launch ‘/usr/lib64/qt5/plugins/kf5/kio/file.so’

        Does it tell you anything?

        Thanks



          1. And today it worked fine! 😮

            I have no idea of what’s going on. I just installed the last couple of upgrades for current, but apparently nothing relevant for this problem.

            I don’t know, if it happens again I will try to investigate further.

            Thanks


  2. will a version of DevHelp become available soon for slackware64-current ?

    Thanks for all your slackware efforts !!

    Craig



  3. Hi again,

    Plasma started to fail again and apparently SDDM was crashing:

    Apr 11 10:58:51 liet kernel: [ 55.238700] sddm-greeter[1401]: segfault at 1501e36389 ip 00007fa561ecd2c8 sp 00007fff18a4d440 error 4 in libQt5Core.so.5.13.2[7fa561c77000+2d3000]
    Apr 11 11:05:44 liet kernel: [ 468.103765] sddm-greeter[1542]: segfault at 30 ip 00007f7970bccabd sp 00007ffdb99525e0 error 4 in libQt5Core.so.5.13.2[7f7970b0c000+2d3000]
    Apr 11 11:16:53 liet kernel: [ 36.322246] sddm-greeter[1383]: segfault at 1 ip 00007f9ab9d8cabd sp 00007ffe74067440 error 4 in libQt5Core.so.5.13.2[7f9ab9ccc000+2d3000]

    I removed all Plasma packages and installed them again. I even removed all user specific Plasma and KDE configuration (didn’t make any sense anyway since the error happened before any user info was loaded). No success, it was still failing 90% of the times (but once in a while it worked and I could not find a patter).

    Finally I made a new fresh slackware-current installation and installed again your Plasma set, and it is working apparently fine.

    My guess, I installed something that is conflicting with Plasma, but I have no idea of what was it. So I am installing again one by one all my packages and documented the order and all changes, so if it happens again I will be able to identify the conflicting software.

    Thanks


  4. Dear Alienbob,

    First, I very much appreciate your work on Slackware. I would like to suggest an improvement on Slackware installer, or at least ask a question for clarification.
    I just would like to ask question about the setup “Select Prompting Mode” step. The menu and the options have been changed, and I think the older version was better.
    In an older version of Slackware Install the options and the explanations were these:

    menu Choose groups of packages from interactive menus
    expert Choose individual packages from interactive menus.

    I’m referring to the old installer, please see on the Slackbook webpage 3.4.7:

    https://www.slackbook.org/html/installation-setup.html

    On the other hand, the newer and current version of Installer says this:

    menu Choose individual packages from interactive menus
    expert This is actually the same as the “menu” option

    I think the old version was better: it was more clear and it offered two genuinely different options: selection of groups of packages vs selections of individual packages. Why it has been changed?
    Also, I think it would be better if the users had this option still. Is it possible to, say, in next release of Slackware we’ll get the old intall options again with two different and clearly distinguishable options?

    In sum, I think the current installer is confusing or redundant. And I don’t see at all an improvement here from the newer version.

    If there is currently no real difference between the “menu” and “expert” options, then there is no reason to keep both of them. I would keep only one of those with the explanation: “Choose individual packages from interactive menus”.
    If, however, there is or should be a real difference and choice between individual vs groups of packages, then the old version should be used.

    I would go for the old version: the explanation is clear, it offers an extra option and more flexibility in installing.

    Thank you for clarification.

    Best wishes,
    Peter


    1. Hi Peter,

      This blog is not the right place to make requests for a change in Slackware. We can discuss it here, no problem, but if you want to have attention from Pat Volkerding, be sure to post it in this LQ thread: https://www.linuxquestions.org/questions/slackware-14/requests-for-current-14-2-15-0-a-4175620463/

      This change to the setup was made before I created my git repository which has been tracking -current development since June 2018 (https://git.slackware.nl/current/tree/source/installer/sources/initrd/usr/lib/setup for instance), so this was done a long time ago. But I seem to remember that the reason was that “expert” installs just took a very long time due to all the individual packages having to be (de-)selected and this adds nothing of value.






  5. Eric, I used your amazing iso2usb.sh script (no options) to copy the 30 April versions of the slackware64 live ISOs (current and current-xfce) onto a pair of thumb drives (a cheap PNY and a higher-end SanDisk Cruzer Glide 3.0), but neither my Lenovo T420s and X120 recognized any bootable software and bounced back to their respective boot drive selector screens. After the initial failures, I used “dd if=/dev/zero of=/dev/sdc bs=1M count=100” to wipe any boot records from the drives and used iso2usb.sh again, but again, the computers refused to boot.

    However, when I used dd to copy the ISOs onto the PNY drive, both computers booted both versions immediately. I’m using the current 3.7G ISO right now on my X120e to write this.

    Let me know if you need more information or want to try different ISO files.


    1. Well, “no options” is not correct, you would at least have to provide the ISO as input and the USB device as output parameter… but no other options are required to create a bootable USB stick.
      If the process of letting iso2usb.sh write the ISO to the USB stick had no errors, then I can not tell you why the USB stick would not boot your computers. I have a T460 on which my own USB Live stick boots just fine. The Live stick works on all (not a large amount) of the BIOS and UEFI computers I tested.


  6. Way back on March 21, 2020, I wanted to boot my circa 2013 Macbook Air using Liveslack XFCE on flash drive & ran into the old Broadcom_sta problem – no driver.

    The rest of the story: I downloaded live-current & installed it on a SSD connected via USB. I SlackBuilt broadcom_sta on it, installed wicd since I’m not familiar with NetworkManager, & now I’m off to the races. Way cool. Except for wireless master mode. Oh well…

    I configured it with my fave fvwm window manager + config which has suited me fine-aree for a b’zillion years. Starts up way faster than heavier window managers. At least I’m using my covid time for something I’ll use…:-)

    Cheers, Another Bob


    1. You know, all of the Live ISOs except the small XFCE variant, already have a “broadcom_sta” module in their “optional” module subdirectory.
      So if you boot a live medium (except XFCE) and add “load=broadcom_sta” to the boot commandline in the syslinux or grub menu page, you will get that Broadcom support out of the box.


  7. Hi Eric,
    after upgrading to freetype-2.10.2 (and creating/installing a compat32 package) yesterday on my -current64 multilib system i ran into problems with some wine apps. I finally found out that the new freetype version seems to be dependent on brotli. Created a brotli compat32 package was the solution.
    Maybe it’s possible to add that package to your /multilib/current/slackware64-compat32/ repo when you have time to refresh it.
    Cheers,
    KG




  8. Hi Eric,

    It seems that synchronization of Slackware current repositories didn’t work last night on bear.alienbase.nl
    The Changelog entries dated “Tue May 26 20:35:03 UTC 2020” do not exist on the server at time of writing.


    1. Some of the cron jobs (not all apparently, just those for root) stopped working that day. I need to find out what happened, but I killed crond and restarted it, let’s see if that is sufficient.


Leave a Reply to Duodecimo Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.