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

9 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


Leave a Reply to guilleg 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.