Tagged: fedora Toggle Comment Threads | Keyboard Shortcuts

  • lenz 13:26 on 2017-02-20 Permalink
    Tags: , development, fedora, ,   

    Installing Microsoft Visual Studio Code on Fedora Linux 

    I never thought I’d ever say this, but I must admit that I have become quite a fan of Microsoft’s Visual Studio Code IDE, which is available for a wide range of platforms, including Linux.

    However, the installation user experience was still somewhat arcane – one had to manually download the RPM package from their web site to install the software. Once a new version was available, the user receives a notification within the application, which redirects him to the website for downloading and updating the latest RPM manually again.

    Therefore it didn’t take long for the community to request the creation of a dedicated yum repository, to keep the package updated automatically.

    This issue has now been resolved: a yum repo has now been created. Until github issue 20895 has been fixed, this still requires setting up the required repository configuration manually though, but hopefully this will be addressed soon as well.

    Until then, here’s how to enable the yum repo on Fedora Linux (Fedora 25 in my case):

    Create a file /etc/yum.repos.d/vscode.repo with the following content:

    name=Visual Studio Code

    Now you can install the package with the following command:

    $ sudo dnf install code

    Upon the first run, you will be requested to import the GPG build key used for signing the package.

    Once a new updates becomes available, running dnf update will pull and install the updated package automatically.

    Thanks to the developers at Microsoft for making this step much easier now!

    • Andreas Walter 20:18 on 2017-02-20 Permalink | Reply

      Cool that Visual Studio works now Linux.

      • lenz 09:08 on 2017-02-21 Permalink | Reply

        Please note that this is about Visual Studio Code, which is a different beast 😉

    • jfichl 22:43 on 2017-03-01 Permalink | Reply

      Error: package code-1.10.0-1488387854.el7.x86_64.rpm isn’t signed – seems like i have to wait a little 🙂

      • lenz 12:40 on 2017-03-02 Permalink | Reply

        Hmm, that’s odd. I ran “dnf update” earlier today, and this is what I got:

        rpm -qi code
        Name : code
        Version : 1.10.0
        Release : 1488387854.el7
        Architecture: x86_64
        Install Date: Thu 02 Mar 2017 10:32:23 AM CET
        Group : Development/Tools
        Size : 157249812
        License : Multiple, see https://code.visualstudio.com/license
        Signature : RSA/SHA256, Wed 01 Mar 2017 10:57:41 PM CET, Key ID eb3e94adbe1229cf
        Source RPM : code-1.10.0-1488387854.el7.src.rpm
        Build Date : Wed 01 Mar 2017 06:12:15 PM CET
        Build Host : c432a008bc20
        Relocations : (not relocatable)
        Packager : Visual Studio Code Team vscode-linux@microsoft.com
        Vendor : Microsoft Corporation
        URL : https://code.visualstudio.com/
        Summary : Code editing. Redefined.
        Description :
        Visual Studio Code is a new choice of tool that combines the simplicity of a code editor with what developers need for the core edit-build-debug cycle. See https://code.visualstudio.com/docs/setup/linux for installation instructions and FAQ

  • lenz 16:24 on 2016-09-20 Permalink
    Tags: , fedora, howto, , ,   

    Enabling scroll wheel emulation for the Logitech Trackman Marble on Fedora Linux 24 

    I’ve been struggling with this for quite some time now, but I finally figured out how to enable scroll wheel emulation for the Logitech Trackman Marble on Fedora Linux 24.

    Previously (when I was using Ubuntu Linux), I had a small shell script that defined the required xinput properties. However, this did not work on Fedora, as they use the new libinput framework.

    With the change to the libinput subsystem, you can now enable this behavior by creating a file /etc/X11/xorg.conf.d/10-libinput.conf with the following content:

    Section "InputClass"
     Identifier "Marble Mouse"
     MatchProduct "Logitech USB Trackball"
     Driver "libinput"
     Option "ScrollMethod" "button"
     Option "ScrollButton" "8"

    Magically, this function got enabled as soon as I saved the file, without even having to restart X! I’m impressed.

  • lenz 17:37 on 2015-12-10 Permalink
    Tags: administration, , fedora, , , troubleshooting   

    Configuring a Brother MFC-7460DN Laser Printer/Scanner on Fedora 23 (64-bit) 

    I’ve always been a fan of Brother, as their devices usually come with decent support for the Linux OS (at least initially). I have an MFC-7460DN Laser Printer / Scanner in my home office, that worked fine with Ubuntu Linux for the past few years. It’s hooked up to my DSL router’s ethernet switch and acts like a network printer for all of our devices.

    Just to keep my mind flexible and to take a look at another Linux distribution for a change, I recently started using Fedora Workstation 23 on my Laptop (a company-issued Lenovo ThinkPad T440s). While the OS installation was painless and all main components like Video, Audio, Networking were detected and configured correctly out of the box, the post-installation of some tools and services required some more effort.

    This time, the printing part of the MFC-7460DN took me quite some time to figure out. While Brother provides RPM packages of the drivers, they are 32-bit only, and the instructions hadn’t been updated since Fedora 12. The first thing I had to do was to download two driver RPM packages. I initially started with the newer versions of the drivers, brgenml1cupswrapper-3.1.0 and brgenml1lpr-3.1.0, but somehow did not get them to work at all. I then tried the older packages, mfc7460dnlpr-2.1.0 and cupswrapperMFC7460DN-2.0.4. These installed flawlessly, and a new printer was added to the CUPS configuration automatically.

    However, it was configured as a local printer, so I first had to change the existing configuration to talk to the remote LPD port instead. While the printer configuration looked correct and no errors showed up, all print jobs simply disappeared into the bit bucket, without any visible error on the application side. Unfortunately the web-based CUPS administration tool was not much helpful, either – the button View Error Log simply returned a “Not found” error. There was no error log file in /var/log/cups, so I queried the status of the CUPS service via systemd next.

    The command systemctl status -l cups then gave me a first hint:

    sh: /opt/brother/Printers/BrGenML1//lpd/rawtobr3: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

    Since this is a 32-bit binary, it might help to actually install a 32-bit version of the GNU C library! I simply forgot this step, even though it’s documented in the installation instructions. A simple dnf install glibc.i686 got me over this hurdle.

    Unfortunately the print jobs still did not reach the printer and disappeared in the void! Checking the CUPS error log again, I now saw this:

    /usr/local/Brother/Printer/MFC7460DN/lpd/filterMFC7460DN: line 131: 11660 Done                    eval cat $INPUT_TEMP
    11661 Broken pipe             | $PSCONV $PSCONV_OP
    11662 Segmentation fault      | $BRCONV $BRCONV_OP
    PID 11602 (/usr/lib/cups/filter/brlpdwrapperMFC7460DN) exited with no errors.
    PID 11603 (/usr/lib/cups/backend/lpd) exited with no errors.

    Hilarious. Oh well, maybe the 32-bit binary is simply too old and crashes in the new environment? Let’s take a look at the full systemd journal with journalctl! This gave me further clues:

    cupsd[10951]: /usr/local/Brother/Printer/MFC7460DN/lpd/filterMFC7460DN: line 131: 11660 Done                    eval cat $INPUT_TEMP
    cupsd[10951]: 11661 Broken pipe             | $PSCONV $PSCONV_OP
    cupsd[10951]: 11662 Segmentation fault      | $BRCONV $BRCONV_OP
    cupsd[10951]: PID 11602 (/usr/lib/cups/filter/brlpdwrapperMFC7460DN) exited with no errors.
    cupsd[10951]: PID 11603 (/usr/lib/cups/backend/lpd) exited with no errors.
    cupsd[10951]: time-at-completed=1449759139
    cupsd[10951]: Job completed.
    cupsd[10951]: Removing document files.
    dbus[1190]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd'
    setroubleshoot[11624]: SELinux is preventing brprintconflsr3 from using the execmem access on a process. For complete SELinux messages. run sealert -l 5d873063-1d87-4e82-b
    python3[11624]: SELinux is preventing brprintconflsr3 from using the execmem access on a process.
                                    *****  Plugin catchall_boolean (89.3 confidence) suggests   ******************
                                    If you want to allow cups to execmem
                                    Then you must tell SELinux about this by enabling the 'cups_execmem' boolean.
                                    setsebool -P cups_execmem 1
                                    *****  Plugin catchall (11.6 confidence) suggests   **************************
                                    If you believe that brprintconflsr3 should be allowed execmem access on processes labeled cupsd_t by default.
                                    Then you should report this as a bug.
                                    You can generate a local policy module to allow this access.
                                    allow this access for now by executing:
                                    # grep brprintconflsr3 /var/log/audit/audit.log | audit2allow -M mypol
                                    # semodule -i mypol.pp

    OK, so SELinux seems to be getting in the way here. I did as suggested and ran the following commands:

    # setsebool -P cups_execmem 1
    # grep brprintconflsr3 /var/log/audit/audit.log | audit2allow -M brothermfc7460dn
    # semodule -i brothermfc7460dn.pp

    An lo and behold, the printer started printing! Let’s hope it still does when I reboot the system…

    Things I learned and that surprised me:

    • The error handling in CUPS completely failed here. There was not a single end-user accessible hint that something went wrong, the print jobs just disappeared in the void.
    • The move to systemd still has some ripple effects, e.g. the “Not found” error for the missing CUPS error log in the web UI.
    • Analyzing log files with journalctl is actually quite convenient. Instead of grepping and tailing multiple logs under /var/log/, these tasks can now be performed using a single tool.
    • SELinux is still a bitch, even though the hints provided by setroubleshootd were quite useful to resolve the issues at hand.
Compose new post
Next post/Next comment
Previous post/Previous comment
Show/Hide comments
Go to top
Go to login
Show/Hide help
shift + esc