[Bug 1912826] Re: Knockd service fails to start due to missing dependency
I can confirm that the issue is resolved after updating knockd from focal-proposed on Mint 20.1. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912826 Title: Knockd service fails to start due to missing dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1912826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912826] Re: Knockd service fails to start due to missing dependency
Here are the steps I used to reproduce the bug: 1. install Linux Mint 20.1 MATE 2. install package knockd 3. in /etc/knockd.conf, add Interface = eno1 (or your network interface) 4. in /etc/default/knockd, set START_KNOCKD=1 5. run "sudo systemctl enable knockd" 6. restart 7. after restarting, knockd is not up - it failed due to eno1 not being up I also tried to reproduce the bug on Ubuntu Desktop 20.04 LTS (focal), minimal install variant. However, no bug occurred. Mint 20.1 is based on focal and uses the same knockd package version, but the bug occurred only on Mint. According to syslog (short version attached), it appears that even the kernel loaded the network card after knockd tried to connect. It is possible that how fast the system brings the network up depends on other software and Ubuntu just happens to be faster. If you'd like the whole syslog, I'll e-mail it privately. Also let me know if I can help by doing some additional tests. Thank you! ** Attachment added: "Excerpts from syslog" https://bugs.launchpad.net/ubuntu/groovy/+source/knockd/+bug/1912826/+attachment/5457430/+files/syslog_knockd_hl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912826 Title: Knockd service fails to start due to missing dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1912826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912826] Re: Knockd service fails to start due to missing dependency
I am not sure what exactly makes the error reproducible. I encounter this error at work, on a computer with freshly installed Linux Mint 20.1 MATE. 1. install the package knockd 2. configure /etc/knockd.conf, set Interface 3. edit /etc/default/knockd to set START_KNOCKD=1 4. enable knockd.service 5. restart the system I tried at home, where I run the same system (although not freshly installed, but gradually upgraded), and knockd starts succcessfully. I also remember having a similar problem some time ago on other machines at work; at the time I solved it by placing a System V init script to /etc/network/if-up.d/. This might mean that the problem depends on the network. If it helps, I can try installing Ubuntu on a side partition at work and try it from scratch again. I suspect that maybe if the NetworkManager takes too long to bring an interface online, knockd fails. The positions of the syslog entries of NetworkManager and knockd correspond with the error happening. In comment #4 of the linked RH bug, J. Ralston claims that the After= condition is insufficient by itself if the service in question requires a dependency to be fully up and running. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912826 Title: Knockd service fails to start due to missing dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1912826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912826] [NEW] Knockd service fails to start due to missing dependency
Public bug reported: I would like to request a small fix in the systemd unit file knockd.service. Please add the [Unit] line Wants=network-online.target Bug description: When the system starts, the knockd daemon fails with a message "knockd[1012]: could not open eno1: eno1: That device is not up". This bug was also described here: https://bugzilla.redhat.com/show_bug.cgi?id=1730634 In accordance with the recommendations in the systemd.unit documentation, it should be sufficient to accompany the After= option with a Wants= option. This fixed the issue for me; and in the syslog I could see that the network manager comes online before the knockd daemon (as required), instead of after. Tested on Linux Mint 20.1 that is based on Ubuntu focal (knockd 0.7-1ubuntu3). ** Affects: knockd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912826 Title: Knockd service fails to start due to missing dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knockd/+bug/1912826/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316035] Re: matrox g200eR2 is unclaimed in 14.04
For reference, a couple of users have been experiencing the same issue on HP ProLiant MicroServer Gen8, which use Matrox MGA G200EH, the original culprit that caused the module mgag200 to be excluded from the kernel years ago. https://community.hpe.com/t5/ProLiant-Servers-Netservers/HP-ProLiant- Gen8-with-Ubuntu-16-and-no-monitor-using-iLO-remote/m-p/6972709 In the linked topic, I put together a step-by-step walkthrough through installing the mgag200 module for Ubuntu or Ubuntu-based distros like Mint. Some users might find it helpful. Unfortunately, only one novice user tried this on HP Gen8 and apparently it did not work. I am not sure whether the mgag200 module just does not work with G200EH yet or whether there was some mistake made in the approach either by me or the user. It would be very helpful for someone to test this with this specific chip and report in more detail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1316035 Title: matrox g200eR2 is unclaimed in 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1316035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316035] Re: matrox g200eR2 is unclaimed in 14.04
Short version: kernel module driver "mgag200" did the trick for me. In kernel config, it is represented by CONFIG_DRM_MGAG200. http://cateee.net/lkddb/web-lkddb/DRM_MGAG200.html I found a bug that is relevant to this one: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642470 It says that the kernel module "mgag200" was blacklisted from kernels due to this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1042903 I tried manually compiling the driver as a module, adding it to a kernel and it worked. I had problems with MGA G200e [Pilot] ServerEngines (SEP1) card. I tried Zoltán's X.org regression hack, I also tried using a recompiled up-to- date mga_drv.so, the library in xserver-xorg-video-mga, where the maintainers claim to support G200e chip (https://cgit.freedesktop.org/xorg/driver/xf86-video-mga/, commits from July 2016). Nothing worked. I am, however, just an intermediate user, so I might have made a mistake somewhere. I also do not know the difference between a kernel driver, X.org driver, and how they interact together and how they are used. Therefore I will trust someone more knowledgeable to put this all together, and I am just going to describe what I did to make it work :-) As a reference, I did a fresh install of Linux Mint 18.1 MATE, where the GPU was unclaimed: $ uname -a Linux rack3test 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -c display *-display UNCLAIMED description: VGA compatible controller product: MGA G200e [Pilot] ServerEngines (SEP1) vendor: Matrox Electronics Systems Ltd. physical id: 0 bus info: pci@:02:00.0 version: 05 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:c200-c2ff memory:c101-c1013fff memory:c080-c0ff memory:c100-c100 Then I tried two approaches, both worked. 1. the easier way is to compile and install just the module mgag200. I downloaded the sources and headers for the current kernel, compiled and installed the module, and then added it in the initramfs image. Then, after reboot, it worked. Here are the resources I used: http://askubuntu.com/questions/168279/how-do-i-build-a-single-in-tree-kernel-module http://askubuntu.com/questions/676707/how-to-load-a-module-in-initrd In the first one, do not forget to use your kernel version and the path to the module (drivers/gpu/drm/mgag200). Also it is probably more convenient to use "$ make menuconfig" instead of editing the .config file with vi (you need the ncurses package though). In the menu, find Graphics Drivers --> Graphics Support --> Kernel modesetting driver for MGA G200 server engines, and enable it as a module. When updating initramfs, it might be necessary to specify the kernel version, for example $ update-initramfs -u -k 4.4.0-66-generic. If you have multiple kernels, the command will tell you which initramfs it updated. The result after a reboot: $ uname -a Linux rack3test 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ sudo lshw -c display *-display description: VGA compatible controller product: MGA G200e [Pilot] ServerEngines (SEP1) vendor: Matrox Electronics Systems Ltd. physical id: 0 bus info: pci@:02:00.0 version: 05 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=mgag200 latency=0 resources: irq:16 memory:c200-c2ff memory:c101-c1013fff memory:c080-c0ff memory:c100-c100 2. Second way is building a new kernel, which is much longer; unfortunately, I tried it first :-) I downloaded the current stable kernel sources from kernel.org, version 4.10.1. Then I used the existing kernel config file for 4.4.0-66-generic, updated it with default choices to 4.10.1 and enabled CONFIG_DRM_MGAG200 as a module. I compiled the whole kernel and installed it, the new driver "mgag200" loads automatically and it works. I used Linux Mint 18.1 for testing, but the installed system is Mint 17.2. I tried compiling the kernel module there for kernel version 3.16.0-38-generic, but after enabling module mgag200 with modprobe, the screen turned black and monitor went into sleep mode. I had to switch to tty1 and reboot. After reboot, the module mgag200 was visible in lsmod, but probably not active and the GPU was still unclaimed with no hardware acceleration. Maybe I did something wrong, but it is possible that the mgag200 module helps only with newer kernels. You can check whether your device is recognized by this driver in the first link in this comment. Numeric ID (vendor, device) can be displayed by running $ sudo lshw -c display -numeric, it will be in square brackets under "product". If anyone
[Bug 1203276] Re: cups-browsed memory usage unacceptable
Here is an upstream bug with a patch: https://bugs.linuxfoundation.org/show_bug.cgi?id=1365 However, it is for the current revision, so it will probably appear in 1.10.1 and I am not sure how to deliver this patch to the Ubuntu package cups-browsed 1.8.3-2ubuntu3. Basically, I don't know how packaging for Ubuntu works, and I couldn't find the source specific for 1.8.3-2ubuntu3. So, I took the source of 1.8.3, patched it and attached is a diff file. ** Bug watch added: bugs.linuxfoundation.org/ #1365 https://bugs.linuxfoundation.org/show_bug.cgi?id=1365 ** Patch added: "bugfix1203276_1.8.3_launchpad.diff" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1203276/+attachment/4705343/+files/bugfix1203276_1.8.3_launchpad.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203276 Title: cups-browsed memory usage unacceptable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1203276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
