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
B
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
expe
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 sa
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
ER
** 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
** 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
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/17
** 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:
uf
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/+sou
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 reboo
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
+Be
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
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.69635656
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-l
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: Bu
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 dete
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, whic
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 sup
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/
** 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 subs
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 doe
21 matches
Mail list logo
