[Touch-packages] [Bug 1987523] Re: Pulsaudio crashes once BT microphone is connected

2022-10-04 Thread Ante Karamatić
Sorry for the delay. I confirm that the package from -proposed solves
the issue on Jammy.

** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1987523

Title:
  Pulsaudio crashes once BT microphone is connected

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Committed

Bug description:
  * Impact
  When I connect my BT headset with microphone and change profile to HFP, 
Pulsaudio crashes, sometimes even crashing Gnome itself.

  * Test case
  - Connect a bluetooth headset to the computer
  - Try to change the profile to HFP from the desktop settings or the 
pulseaudio cli

  -> the profile should get correctly selected, the service shouldn't
  crash

  * Regression potential

  The changes are in the functions handling mSBC packets which handle
  bluetooth HFP codecs, so any regression would concern bluetooth
  devices using that profile.

  ---
  When I connect my BT headset with microphone and change profile to HFP, 
Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports:

  Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX 
(AVRCP) as /devices/virtual/input/input37
  Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
  Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
  Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
  Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
  Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
  Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
  Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
  Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
  Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
  Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk

  I've identified the upstream fix for this:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e

  I've built packages with the fix and can confirm that it does solve
  the problem. Packages are available at:

  https://launchpad.net/~ivoks/+archive/ubuntu/pulse

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


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


[Touch-packages] [Bug 1964506] Re: Ping: checks payloads incorrectly, ignores all mismatch replies

2022-09-21 Thread Ante Karamatić
I agree with Seb. Behavior is broken, not different. It's not just about
printing information; it's the fact that ping is not checking csum, not
checking duplicates... Ideally, both this and bug 1551020 should be
fixed. But if I'd have to pick only one, this would be the one.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1964506

Title:
  Ping: checks payloads incorrectly, ignores all mismatch replies

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  Incomplete

Bug description:
  = Impact =

  the ping statistics are incorrect when dealing with truncated packets

  = Test case =

  $ ping -c 1 -s 1200 8.8.8.8

  should list truncated replies and received packets

  = Regression potential =

  the changes are limited to the ping source any regression would impact
  that utility, check that responses are correctly handled and
  statistics reflecting what is expected

  --

  Problematic commit reverted upstream causing incorrect behavior in
  Ubuntu Focal.

  Discussion: https://github.com/iputils/iputils/issues/320
  Fix: https://github.com/iputils/iputils/pull/321
  Release: https://github.com/iputils/iputils/releases/tag/20210722

  Could this patch be added for a Focal update please?

  1) Ubuntu 20.04.3 LTS
  2) 3:20190709-3
  3)

  focal$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 0 received, 100% packet loss, time 0ms

  4)

  xenial$ ping -c 1 -s 1200 8.8.8.8
  PING 8.8.8.8 (8.8.8.8) 1200(1228) bytes of data.
  76 bytes from 8.8.8.8: icmp_seq=1 ttl=61 (truncated)

  --- 8.8.8.8 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.284/0.284/0.284/0.000 ms

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


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


[Touch-packages] [Bug 1987523] Re: Pulsaudio crashes once BT microphone is connected

2022-08-24 Thread Ante Karamatić
** Description changed:

- When I connect my BT headset with microphone, Pulsaudio crashes,
- sometimes even crashing Gnome itself. Syslog reports:
+ When I connect my BT headset with microphone and change profile to HFP,
+ Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports:
  
  Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX 
(AVRCP) as /devices/virtual/input/input37
  Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
  Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
  Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
  Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
  Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
  Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
  Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
  Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
  Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
  Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk
  
  I've identified the upstream fix for this:
  
  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e
  
  I've built packages with the fix and can confirm that it does solve the
  problem. Packages are available at:
  
  https://launchpad.net/~ivoks/+archive/ubuntu/pulse

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1987523

Title:
  Pulsaudio crashes once BT microphone is connected

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my BT headset with microphone and change profile to
  HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog
  reports:

  Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX 
(AVRCP) as /devices/virtual/input/input37
  Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
  Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
  Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
  Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
  Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
  Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
  Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
  Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
  Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
  Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk

  I've identified the upstream fix for this:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e

  I've built packages with the fix and can confirm that it does solve
  the problem. Packages are available at:

  https://launchpad.net/~ivoks/+archive/ubuntu/pulse

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1987523] [NEW] Pulsaudio crashes once BT microphone is connected

2022-08-24 Thread Ante Karamatić
Public bug reported:

When I connect my BT headset with microphone and change profile to HFP,
Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog reports:

Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX (AVRCP) 
as /devices/virtual/input/input37
Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk

I've identified the upstream fix for this:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e

I've built packages with the fix and can confirm that it does solve the
problem. Packages are available at:

https://launchpad.net/~ivoks/+archive/ubuntu/pulse

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1987523

Title:
  Pulsaudio crashes once BT microphone is connected

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I connect my BT headset with microphone and change profile to
  HFP, Pulsaudio crashes, sometimes even crashing Gnome itself. Syslog
  reports:

  Aug 24 13:44:20 p14s kernel: [21412.562760] input: Bowers & Wilkins PX 
(AVRCP) as /devices/virtual/input/input37
  Aug 24 13:44:21 p14s pulseaudio[50808]: Battery Level: 80%
  Aug 24 13:44:21 p14s pulseaudio[50808]: Dock Status: undocked
  Aug 24 13:44:21 p14s bluetoothd[1070]: sdp_extract_attr: Unknown data 
descriptor : 0x1 terminating
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 7 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Successfully made thread 51716 of 
process 50808 owned by '1000' RT at priority 5.
  Aug 24 13:44:23 p14s rtkit-daemon[1330]: Supervising 8 threads of 3 processes 
of 1 users.
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default sink
  Aug 24 13:44:23 p14s gsd-media-keys[50921]: Unable to get default source
  Aug 24 13:44:23 p14s mattermost-desktop.desktop[51425]: 
[51425:0824/134423.604313:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!
  Aug 24 13:44:23 p14s pulseaudio[50808]: Assertion 'remaining == 0' failed at 
../src/modules/bluetooth/bt-codec-msbc.c:287, function decode_buffer(). 
Aborting.
  Aug 24 13:44:24 p14s systemd[19059]: Starting Notification regarding a crash 
report...
  Aug 24 13:44:24 p14s update-notifier-crash[51723]: /usr/bin/whoopsie
  Aug 24 13:44:24 p14s systemd[1]: Started crash report submission.
  Aug 24 13:44:24 p14s whoopsie[51726]: [13:44:24] Using lock path: 
/var/lock/whoopsie/lock
  Aug 24 13:44:24 p14s systemd[1]: whoopsie.service: Deactivated successfully.
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: gnome-shell
  Aug 24 13:44:24 p14s update-notifier-crash[51725]: apport-gtk

  I've identified the upstream fix for this:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/9916f0eace6ab1825af74a5f9b166918a06ce50e

  I've built packages with the fix and can confirm that it does solve
  the problem. Packages are available at:

  https://launchpad.net/~ivoks/+archive/ubuntu/pulse

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


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

[Touch-packages] [Bug 1861322] [NEW] PPTP VPN doesn't work out of the box - nf_conntrack_pptp missing

2020-01-29 Thread Ante Karamatić
Public bug reported:

PPTP based VPN doesn't work out of the box on Focal Fossa. From syslog:

Jan 29 19:41:35 thinkpad pppd[8734]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:41:35 thinkpad NetworkManager[8734]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:41:35 thinkpad pptp[8739]: nm-pptp-service-8722 log[main:pptp.c:353]: 
The synchronous pptp option is NOT activated
Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722 
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 
'Start-Control-Connection-Request'
Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722 
log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply
Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722 
log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established.
Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722 
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7 
'Outgoing-Call-Request'
Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722 
log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply.
Jan 29 19:41:36 thinkpad pptp[8750]: nm-pptp-service-8722 
log[ctrlp_disp:pptp_ctrl.c:938]: Outgoing call established (call ID 44616, 
peer's call ID 0).
Jan 29 19:42:03 thinkpad pptp[8750]: nm-pptp-service-8722 
log[ctrlp_disp:pptp_ctrl.c:976]: Call disconnect notification received (call id 
44616)
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 
log[logecho:pptp_ctrl.c:719]: Echo Request received.
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 6 'Echo-Reply'
Jan 29 19:42:06 thinkpad pptp[8739]: nm-pptp-service-8722 
warn[decaps_hdlc:pptp_gre.c:226]: short read (-1): Input/output error
Jan 29 19:42:06 thinkpad pptp[8739]: nm-pptp-service-8722 
warn[decaps_hdlc:pptp_gre.c:238]: pppd may have shutdown, see pppd log
Jan 29 19:42:06 thinkpad pppd[8734]: Child process /usr/sbin/pptp 
161.53.xxx.yyy --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-8722 
(pid 8737) terminated with signal 15
Jan 29 19:42:06 thinkpad NetworkManager[8734]: Child process /usr/sbin/pptp 
161.53.xxx.yyy --nolaunchpppd --loglevel 0 --logstring nm-pptp-service-8722 
(pid 8737) terminated with signal 15
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 
log[callmgr_main:pptp_callmgr.c:245]: Closing connection (unhandled)
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 12 
'Call-Clear-Request'
Jan 29 19:42:06 thinkpad pptp[8750]: nm-pptp-service-8722 
log[call_callback:pptp_callmgr.c:84]: Closing connection (call state)

Once nf_conntrack_pptp kernel module is loaded, VPN connection succeeds:

Jan 29 19:44:02 thinkpad pppd[10166]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:44:02 thinkpad NetworkManager[10166]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Jan 29 19:44:02 thinkpad pptp[10170]: nm-pptp-service-10156 
log[main:pptp.c:353]: The synchronous pptp option is NOT activated
Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156 
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 
'Start-Control-Connection-Request'
Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156 
log[ctrlp_disp:pptp_ctrl.c:781]: Received Start Control Connection Reply
Jan 29 19:44:02 thinkpad pptp[10183]: nm-pptp-service-10156 
log[ctrlp_disp:pptp_ctrl.c:815]: Client connection established.
Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156 
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7 
'Outgoing-Call-Request'
Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156 
log[ctrlp_disp:pptp_ctrl.c:900]: Received Outgoing Call Reply.
Jan 29 19:44:03 thinkpad pptp[10183]: nm-pptp-service-10156 
log[ctrlp_disp:pptp_ctrl.c:938]: Outgoing call established (call ID 61223, 
peer's call ID 0).

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: champagne

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1861322

Title:
  PPTP VPN doesn't work out of the box - nf_conntrack_pptp missing

Status in network-manager package in Ubuntu:
  New

Bug description:
  PPTP based VPN doesn't work out of the box on Focal Fossa. From
  syslog:

  Jan 29 19:41:35 thinkpad pppd[8734]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
  Jan 29 19:41:35 thinkpad NetworkManager[8734]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
  Jan 29 19:41:35 thinkpad pptp[8739]: nm-pptp-service-8722 
log[main:pptp.c:353]: The synchronous pptp option is NOT activated
  Jan 29 19:41:35 thinkpad pptp[8750]: nm-pptp-service-8722 
log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 
'Start-Control-Connection-Request'
  Jan 29 19:41:35 thinkpad pptp[8750]: 

[Touch-packages] [Bug 1831787] Re: Bogus routes after DHCP lease change

2019-06-06 Thread Ante Karamatić
It's exactly the same as that systemd issue.

** Attachment added: "log"
   
https://bugs.launchpad.net/netplan/+bug/1831787/+attachment/5269074/+files/log

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1831787

Title:
  Bogus routes after DHCP lease change

Status in netplan:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Netplan config:

  network:
version: 2
renderer: networkd
ethernets:
  eno4:
dhcp4: no
  eno1np0:
dhcp4: no
addresses: 
  - 172.16.0.2/24
bridges:
  br0:
dhcp4: yes
interfaces:
  - eno4

  On initial boot, machine got 10.0.15.109 IP address:

  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured
  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 
10.0.15.109/23 via 10.0.15.253

  At one point, DHCP server reserver this IP address and client
  eventually picked up new IP address:

  May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address
  10.0.15.128/23 via 10.0.15.253

  This resulted in IP addresses:

  # ip -o a
  1: loinet 127.0.0.1/8 scope host lo\   valid_lft forever 
preferred_lft forever
  1: loinet6 ::1/128 scope host \   valid_lft forever preferred_lft 
forever
  2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\   
valid_lft forever preferred_lft forever
  2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \   valid_lft 
forever preferred_lft forever
  6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\   
valid_lft 503sec preferred_lft 503sec
  6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \   valid_lft 
forever preferred_lft forever

  So far, everything is fine. But, the routes on the machine are bogus:

  # ip r
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100 
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100 
  10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128 
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100 
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100 
  172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2 

  routes with src 10.0.15.109 should have been removed when lease was
  renewed. I'm not sure if this is a bug in netplan or systemd. This is
  18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1831787/+subscriptions

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


[Touch-packages] [Bug 1355813] Re: Interface MTU management across MAAS/juju

2015-06-23 Thread Ante Karamatić
** Tags added: cpec

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1355813

Title:
  Interface MTU management across MAAS/juju

Status in juju-core:
  Fix Released
Status in MAAS:
  Triaged
Status in juju-core package in Ubuntu:
  Triaged
Status in lxc package in Ubuntu:
  Invalid

Bug description:
  Context:

  juju + MAAS deployed OpenStack environment, misc services deployed
  under LXC on the bootstrap node, interfaces configured for jumbo
  frames - note that I had to manually set the LXC container interfaces
  to mtu 9000 before the bridge would do the same.

  Action:

  Reboot one of the containers; MTU on br0 resets from 9000 - 1500.

  This feels like more of a 'we need a better way to orchestrate MTU
  configuration across different services' so raising tasks for MAAS and
  Juju as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.5-0ubuntu0.1
  ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Tue Aug 12 13:26:00 2014
  KernLog:

  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx
  lxcsyslog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions

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