[Kernel-packages] [Bug 1771276] [NEW] linux 4.15 currupts ipsec packets over non ethernet devices

2018-05-14 Thread msaxl
Public bug reported:

Linux 4.15 has a bug that currupts ipsec packets if they are received over a 
non ethernet interface.
This is a serve showstopper bug for me since it breaks my VPN setup and locks 
me out of my server.

see https://wiki.strongswan.org/issues/2571 and
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=87cdf3148b11

since 4.15 is already EOL, the only possibility is backporting the
linked patch

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771276

Title:
  linux 4.15 currupts ipsec packets over non ethernet devices

Status in linux package in Ubuntu:
  New

Bug description:
  Linux 4.15 has a bug that currupts ipsec packets if they are received over a 
non ethernet interface.
  This is a serve showstopper bug for me since it breaks my VPN setup and locks 
me out of my server.

  see https://wiki.strongswan.org/issues/2571 and
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=87cdf3148b11

  since 4.15 is already EOL, the only possibility is backporting the
  linked patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771276/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1771276] Re: linux 4.15 currupts ipsec packets over non ethernet devices

2018-05-15 Thread msaxl
There is no crash. All needed information is on 
https://wiki.strongswan.org/issues/2571 #6
The reason is explained https://wiki.strongswan.org/issues/2571 #17, so the 
issue is already resolved in 4.16, but since 4.15 is EOL and 4.14 did non have 
this issue and Ubuntu 18.04 is a LTS release you might consider applying 
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=87cdf3148b11

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771276

Title:
  linux 4.15 currupts ipsec packets over non ethernet devices

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux 4.15 has a bug that currupts ipsec packets if they are received over a 
non ethernet interface.
  This is a serve showstopper bug for me since it breaks my VPN setup and locks 
me out of my server.

  see https://wiki.strongswan.org/issues/2571 and
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=87cdf3148b11

  since 4.15 is already EOL, the only possibility is backporting the
  linked patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771276/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1771276] Re: linux 4.15 currupts ipsec packets over non ethernet devices

2018-05-16 Thread msaxl
upstream works

it was included upstream here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=87cdf3148b11d46382dbce2754ae7036aba96380

somehow they did non backport it to 4.15 (the only version that is
affected)


** Tags added: kernel-fixed-upstream

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771276

Title:
  linux 4.15 currupts ipsec packets over non ethernet devices

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  Linux 4.15 has a bug that currupts ipsec packets if they are received over a 
non ethernet interface.
  This is a serve showstopper bug for me since it breaks my VPN setup and locks 
me out of my server.

  see https://wiki.strongswan.org/issues/2571 and
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=87cdf3148b11

  since 4.15 is already EOL, the only possibility is backporting the
  linked patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771276/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1771276] Re: linux 4.15 currupts ipsec packets over non ethernet devices

2018-05-17 Thread msaxl
** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1771276

Title:
  linux 4.15 currupts ipsec packets over non ethernet devices

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Linux 4.15 has a bug that currupts ipsec packets if they are received over a 
non ethernet interface.
  This is a serve showstopper bug for me since it breaks my VPN setup and locks 
me out of my server.

  see https://wiki.strongswan.org/issues/2571 and
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=87cdf3148b11

  since 4.15 is already EOL, the only possibility is backporting the
  linked patch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1771276/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1625940] [NEW] CIFS client: access problems after updating to kernel 4.4.0-38-generic

2016-09-20 Thread msaxl
Public bug reported:

Since updating to kernel 4.4.0-38 on ubuntu xenial I cannot access
automount shares anymore

it seems that automount since this update resolves $UID always to 0
instead of the requesting users uid. reverting to the older kernel
resolves this.

-fstype=cifs,uid=\$UID,credentials=/etc/auto.master.d/cifs-
creds,cifsacl,nounix

I guess this is a regression of bug fix #1612135, - fs: Call d_automount
with the filesystems creds

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1625940

Title:
   CIFS client: access problems after updating to kernel
  4.4.0-38-generic

Status in linux package in Ubuntu:
  New

Bug description:
  Since updating to kernel 4.4.0-38 on ubuntu xenial I cannot access
  automount shares anymore

  it seems that automount since this update resolves $UID always to 0
  instead of the requesting users uid. reverting to the older kernel
  resolves this.

  -fstype=cifs,uid=\$UID,credentials=/etc/auto.master.d/cifs-
  creds,cifsacl,nounix

  I guess this is a regression of bug fix #1612135, - fs: Call
  d_automount with the filesystems creds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625940/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1625940] Re: CIFS client: access problems after updating to kernel 4.4.0-38-generic

2016-09-22 Thread msaxl
*** This bug is a duplicate of bug 1626112 ***
https://bugs.launchpad.net/bugs/1626112

the fix of bug #1626112 does not resolve this problem
automount gets the wrong UID, so it does not work

if I mount manually with the correct uid= parameter it works as expected (also 
with the other kernels where bug 1626112 was present)
There is no DFS so i guess this bug has nothing to do with bug 1626112

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1625940

Title:
   CIFS client: access problems after updating to kernel
  4.4.0-38-generic

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since updating to kernel 4.4.0-38 on ubuntu xenial I cannot access
  automount shares anymore

  it seems that automount since this update resolves $UID always to 0
  instead of the requesting users uid. reverting to the older kernel
  resolves this.

  -fstype=cifs,uid=\$UID,credentials=/etc/auto.master.d/cifs-
  creds,cifsacl,nounix

  I guess this is a regression of bug fix #1612135, - fs: Call
  d_automount with the filesystems creds

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625940/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1964441] [NEW] libwbxml < 0.11.8 issue with libexpat1 CVE-2022-25236 fix

2022-03-09 Thread msaxl
Public bug reported:

see https://github.com/libwbxml/libwbxml/releases/tag/libwbxml-0.11.8

ubuntu jammy should upgrade to 0.11.8 from 0.11.7

older versions of ubuntu should backport
https://github.com/libwbxml/libwbxml/pull/78

This issue breaks for example sogo activesync (included first on jammy)

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964441

Title:
  libwbxml < 0.11.8 issue with libexpat1 CVE-2022-25236 fix

Status in linux package in Ubuntu:
  New

Bug description:
  see https://github.com/libwbxml/libwbxml/releases/tag/libwbxml-0.11.8

  ubuntu jammy should upgrade to 0.11.8 from 0.11.7

  older versions of ubuntu should backport
  https://github.com/libwbxml/libwbxml/pull/78

  This issue breaks for example sogo activesync (included first on
  jammy)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964441/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 2102208] [NEW] Lenovo ThinkPad USB-C Dock Gen2 USB Audio does not output audio

2025-03-13 Thread msaxl
Public bug reported:

The 3,5mm jack of the ThinkPad USB-C Dock Gen2 does not output any
sounds.

The USB Device is 17ef:30d1 Lenovo ThinkPad USB-C Dock Gen2 USB Audio

On the software side everything seems normal, I see output controls and
everything.

As soon as this USB is passed through to a Windows VM and back, sound
works.

A quick look in snd-usb-audio gave no clue and I have no idea how to
debug such things, but Windows seems to do some magic when initializing
this device. That Initializations seems to be persistent until powerdown

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2102208

Title:
  Lenovo ThinkPad USB-C Dock Gen2 USB Audio does not output audio

Status in linux package in Ubuntu:
  New

Bug description:
  The 3,5mm jack of the ThinkPad USB-C Dock Gen2 does not output any
  sounds.

  The USB Device is 17ef:30d1 Lenovo ThinkPad USB-C Dock Gen2 USB Audio

  On the software side everything seems normal, I see output controls
  and everything.

  As soon as this USB is passed through to a Windows VM and back, sound
  works.

  A quick look in snd-usb-audio gave no clue and I have no idea how to
  debug such things, but Windows seems to do some magic when
  initializing this device. That Initializations seems to be persistent
  until powerdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2102208/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp