[Bug 297001] [NEW] Wine failing to detect USB device hot plugging
Public bug reported: Binary package hint: wine I have package wine-1.0.1-0ubuntu2 installed on my Ubuntu 8.10 (AMD64) box. Wine is failing to detect USB hot plug events. For example running winefile, and then plugging in a USB drive, winefile does not detect the new USB drive (although GNOME does, and the USB drive is mounted correctly, and I can navigate to it through Nautilus). I believe this is a problem with the way the wine package has been built rather than with wine itself (I understand that wine does normally support this functionality). I suspect the problem is that wine has been built without HAL support. Wine's mountmgr uses HAL to detect hardware device changes. Running the following command: WINEDEBUG=+mountmgr wine winefile >mountmgr.log 2>&1 produces the attached log. In particular the following line is of interest: trace:mountmgr:initialize_hal Skipping, HAL support not compiled in Without HAL wine's hot plugging functionality is disabled. The wine packages need to be built with the libhal-dev files present prior to running ./configure ** Affects: wine (Ubuntu) Importance: Undecided Status: New -- Wine failing to detect USB device hot plugging https://bugs.launchpad.net/bugs/297001 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 297001] Re: Wine failing to detect USB device hot plugging
** Attachment added: "WINEDEBUG file showing +mountmgr output" http://launchpadlibrarian.net/19579035/mountmgr.log -- Wine failing to detect USB device hot plugging https://bugs.launchpad.net/bugs/297001 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 297001] Re: Wine failing to detect USB device hot plugging
Yes, I am running 64-bit. This is particularly frustrating since attempting to compile wine from source on 64-bit seems to be a non-trivial task! ./configure keeps falling over with various 32-bit/64-bit problems. -- Wine failing to detect USB device hot plugging https://bugs.launchpad.net/bugs/297001 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 297001] Re: Wine failing to detect USB device hot plugging
I can confirm that this issue is fixed in 1.0.1-0ubuntu3 from intrepid- proposed. After installing on my Ubuntu 8.10 (AMD64) box, I re-ran: WINEDEBUG=+mountmgr wine winefile >mountmgr.log 2>&1 I then inserted a USB flash drive. This produced the attached log file. The error regarding no HAL support is gone. Wine can be seen detecting the hotplug event in the following line: trace:mountmgr:add_dos_device added device e: udi "/org/freedesktop/Hal/devices/ volume_uuid_8E98_1D37" for "/dev/sdc1" on "" type "disk" Things still did not work entirely as I expected since winefile still did not update to show the new drive. Not sure whybut as far as this particular defect goes I believe it to be fixed. ** Attachment added: "mountmgr.log" http://launchpadlibrarian.net/20994925/mountmgr.log -- Wine failing to detect USB device hot plugging https://bugs.launchpad.net/bugs/297001 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
I made the change to /lib/ufw/ufw-init as requested and confirmed that after reboot I was still hitting the issue (Ubuntu 18.04.1 LTS): $ sudo ufw status Status: inactive Attached is the requested journalctl output. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/551/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
** Attachment added: "dpkg.list" https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222403/+files/dpkg.list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
** Attachment added: "ufw.raw" https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222405/+files/ufw.raw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
I rebooted and confirmed that ufw still reports itself as inactive. Attached are the requested files. Note: I only included the last 25000 lines from journal.full - otherwise I would have to upload 250Mb! ** Attachment added: "journal.full" https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222402/+files/journal.full -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
** Attachment added: "ufw.tar.gz" https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+attachment/5222404/+files/ufw.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
This issue still seems to be a problem in 18.04. If found a solution: https://askubuntu.com/questions/1040539/how-do-i-get-ufw-to-start-on-boot/1040584 I edited /lib/systemd/system/ufw.service as follows: $ diff -u ufw.service.orig ufw.service --- ufw.service.orig2018-05-26 13:45:48.696356561 +0100 +++ ufw.service 2018-05-26 14:17:22.030681670 +0100 @@ -2,7 +2,7 @@ Description=Uncomplicated firewall Documentation=man:ufw(8) DefaultDependencies=no -Before=network.target +After=network-pre.target [Service] Type=oneshot According to this page https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/ the network-pre.target has this purpose: "It's primary purpose is for usage with firewall services that want to establish a firewall before any network interface is up" Making the above change solves the problem so that ufw does seem to start up after boot. Is it a bug that ufw.service is not setup this way to start with? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
Unfortunately, after a few reboots using these settings it seems this is not the answer. While it does seem to work intermittently, it also sometimes fails. I've also had some issues with network not working at all. I'm not 100% sure that this change is the culprit - but for now I have reverted the change. It still seems to me likely that there is some issue with the systemd dependencies. With the previous settings ufw never seems to be active after boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
I just tried: After=network.target After 5 reboot tests I got mixed results: The first two reboots failed to start networking at all and ufw reported its status as "inactive" immediately after boot. The next two reboots networking started successfully, and ufw reported as active. The final reboot, networking again did not start and ufw status was "inactive" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
I just tried that: $ diff -u ufw.service.orig ufw.service --- ufw.service.orig2018-05-26 13:45:48.696356561 +0100 +++ ufw.service 2018-07-17 16:50:45.545596167 +0100 @@ -2,7 +2,8 @@ Description=Uncomplicated firewall Documentation=man:ufw(8) DefaultDependencies=no -Before=network.target +Before=network-pre.target +Wants=network-pre.target [Service] Type=oneshot But after a reboot, nothing changed: $ sudo ufw status Status: inactive -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] [NEW] ufw does not start automatically at boot
Public bug reported: Whenever I boot into 17.10 ufw is always inactive, even though /etc/ufw/ufw.conf has this: # Set to yes to start on boot. If setting this remotely, be sure to add a rule # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp' ENABLED=yes ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ufw 0.35-5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 24 13:56:40 2017 InstallationDate: Installed on 2015-04-01 (936 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago) mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170 ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726856] Re: ufw does not start automatically at boot
Hi Seth, This is what I get: matt@matt-laptop:~$ sudo ufw status Status: inactive matt@matt-laptop:~$ journalctl -u ufw.service -- Logs begin at Tue 2017-10-24 22:48:54 BST, end at Wed 2017-10-25 00:03:54 BST. -- Oct 24 22:48:54 matt-laptop systemd[1]: Started Uncomplicated firewall. matt@matt-laptop:~$ systemctl status ufw ● ufw.service - Uncomplicated firewall Loaded: loaded (/lib/systemd/system/ufw.service; enabled; vendor preset: enabled) Active: active (exited) since Tue 2017-10-24 22:48:54 BST; 1h 15min ago Docs: man:ufw(8) Process: 443 ExecStart=/lib/ufw/ufw-init start quiet (code=exited, status=0/SUCCESS) Main PID: 443 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/ufw.service Oct 24 22:48:54 matt-laptop systemd[1]: Started Uncomplicated firewall. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726856 Title: ufw does not start automatically at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1726856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662299] Re: Soundcard not detected
Same problem here :-( alsa-info attached. ** Attachment added: "alsa-info.txt.2FBjXEBUrM" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/662299/+attachment/1897452/+files/alsa-info.txt.2FBjXEBUrM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662299 Title: Soundcard not detected -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662299] Re: Soundcard not detected (workaround: add "pci=use_crs" to GRUB)
I upgraded to 11.04 and tried Anish's solution today. It worked! Yay! I have sound again after 2 months! Thanks Anish! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662299 Title: Soundcard not detected (workaround: add "pci=use_crs" to GRUB) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947588] Re: Infinite Loop in OpenSSL s_server
FYI, upstream have now also merged a fix in the 1.1.1 branch: https://github.com/openssl/openssl/commit/e04ba889594d84a8805f3d0caeadf0527470e508 If Ubuntu pulls in that patch I expect that this bug should be fixed by it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947588 Title: Infinite Loop in OpenSSL s_server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1947588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947588] Re: Infinite Loop in OpenSSL s_server
FYI, upstream merged a fix for the underlying problem in OpenSSL 3.0: https://github.com/openssl/openssl/commit/8b63b174b00b0e8c5cefcea12989d90450e04b24 I expect a similar fix to be backported to 1.1.1 soon. Although the specific issue that this bug report is about doesn't impact upstream, I expect that any backported fix will also resolve this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947588 Title: Infinite Loop in OpenSSL s_server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1947588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947588] [NEW] Infinite Loop in OpenSSL s_server
Public bug reported: Launching openssl s_server as follows: $ openssl s_server -nocert -psk 01020304 -dtls1 And using openssl s_client to connect to it like this: $ openssl s_client -dtls1 -psk 01020304 Results in s_server entering an infinite loop: Using default temp DH parameters ACCEPT ERROR 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: ERROR 140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal error:../ssl/statem/statem_lib.c:109: ERROR ...and so on... I have confirmed that upstream OpenSSL does not have this issue in a default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug with these commands (https://github.com/openssl/openssl/issues/16707) and it was while working on the fix for that issue (https://github.com/openssl/openssl/pull/16838) that I noticed this problem in the Ubuntu packages. $ lsb_release -rd Description:Ubuntu 21.04 Release:21.04 $ apt-cache policy openssl openssl: Installed: 1.1.1j-1ubuntu3.5 Candidate: 1.1.1j-1ubuntu3.5 Version table: *** 1.1.1j-1ubuntu3.5 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 Packages 100 /var/lib/dpkg/status 1.1.1j-1ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages $ openssl version -a OpenSSL 1.1.1j 16 Feb 2021 built on: Mon Aug 23 17:02:39 2021 UTC platform: debian-amd64 options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr) compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack -g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 OPENSSLDIR: "/usr/lib/ssl" ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1" Seeding source: os-specific ** Affects: openssl (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/1947588 Title: Infinite Loop in OpenSSL s_server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1947588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947588] Re: Infinite Loop in OpenSSL s_server
Thanks for your analysis. Based on your description I was able to find an instance of this bug that impacts an unmodified upstream OpenSSL directly. I've raised an issue for it here: https://github.com/openssl/openssl/issues/18047 That particular instance only impacts OpenSSL 3.0 - but its the same underlying cause as here. ** Bug watch added: github.com/openssl/openssl/issues #18047 https://github.com/openssl/openssl/issues/18047 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947588 Title: Infinite Loop in OpenSSL s_server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1947588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
