[Touch-packages] [Bug 1858050] [NEW] python3 segmentation faults with spacy
Public bug reported:
After
# pip3 install spacy
executing
# python3 -m spacy download de
results in a segmentation fault, as shown by the following output woith strace
information added
[...]
Running setup.py install for de-core-news-sm ... done
Successfully installed blis-0.4.1 catalogue-0.2.0 certifi-2019.11.28
chardet-3.0.4 cymem-2.0.3 de-core-news-sm-2.2.5 idna-2.8
importlib-metadata-1.3.0 more-itertools-8.0.2 murmurhash-1.0.2 numpy-1.18.0
plac-1.1.3 preshed-3.0.2 requests-2.22.0 setuptools-43.0.0 spacy-2.2.3
srsly-0.2.0 thinc-7.3.1 tqdm-4.41.1 urllib3-1.25.7 wasabi-0.5.0 zipp-0.6.0
[{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 26073
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=26073, si_uid=1000,
si_status=0, si_utime=742, si_stime=113} ---
write(1, "\33[38;5;2m\342\234\224 Download and instal"..., 114✔ Download and
installation successful
You can now load the model via spacy.load('de_core_news_sm')) = 114
write(1, "\n", 1
) = 1
getcwd("/home/mkg/nlp", 1024) = 14
stat("/home/mkg/nlp", {st_mode=S_IFDIR|0775, st_size=4096, ...}) = 0
stat("/usr/lib/python3.6", {st_mode=S_IFDIR|0755, st_size=20480, ...}) = 0
stat("/usr/lib/python3.6/lib-dynload", {st_mode=S_IFDIR|0755, st_size=12288,
...}) = 0
stat("/home/mkg/.local/lib/python3.6/site-packages", {st_mode=S_IFDIR|0700,
st_size=12288, ...}) = 0
openat(AT_FDCWD, "/home/mkg/.local/lib/python3.6/site-packages",
O_RDONLY|O_NONBLOCK|O_CLOEXEC|O_DIRECTORY) = 3
fstat(3, {st_mode=S_IFDIR|0700, st_size=12288, ...}) = 0
getdents(3, /* 245 entries /, 32768) = 10048
getdents(3, / 0 entries */, 32768) = 0
close(3) = 0
stat("/home/mkg/.local/lib/python3.6/site-packages/de_core_news_sm/init.cpython-36m-x86_64-linux-gnu.so",
0x7fffc1f91fc0) = -1 ENOENT (No such file or directory)
stat("/home/mkg/.local/lib/python3.6/site-packages/de_core_news_sm/init.abi3.so",
0x7fffc1f91fc0) = -1 ENOENT (No such file or directory)
stat("/home/mkg/.local/lib/python3.6/site-packages/de_core_news_sm/init.so",
0x7fffc1f91fc0) = -1 ENOENT (No such file or directory)
stat("/home/mkg/.local/lib/python3.6/site-packages/de_core_news_sm/init.py",
{st_mode=S_IFREG|0664, st_size=291, ...}) = 0
stat("/home/mkg/.local/lib/python3.6/site-packages/de_core_news_sm/init.py",
{st_mode=S_IFREG|0664, st_size=291, ...}) = 0
openat(AT_FDCWD,
"/home/mkg/.local/lib/python3.6/site-packages/de_core_news_sm/pycache/init.cpython-36.pyc",
O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0664, st_size=503, ...}) = 0
lseek(3, 0, SEEK_CUR) = 0
fstat(3, {st_mode=S_IFREG|0664, st_size=503, ...}) = 0
read(3, "3\r\r\n:7\313]#\1\0\0\343\0\0\0\0\0\0\0\0\0\0\0\0\3\0\0\0@\0\0"...,
504) = 503
read(3, "", 1) = 0
close(3) = 0
stat("/home/mkg/.local/lib/python3.6/site-packages/de_core_news_sm",
{st_mode=S_IFDIR|0775, st_size=4096, ...}) = 0
stat("/home/mkg/.local/lib/python3.6/site-packages/de_core_news_sm/meta.json",
{st_mode=S_IFREG|0664, st_size=2909, ...}) = 0
stat("/home/mkg/.local/lib/python3.6/site-packages/de_core_news_sm/meta.json",
{st_mode=S_IFREG|0664, st_size=2909, ...}) = 0
openat(AT_FDCWD,
"/home/mkg/.local/lib/python3.6/site-packages/de_core_news_sm/meta.json",
O_RDONLY|O_CLOEXEC) = 3
ioctl(3, FIOCLEX) = 0
fstat(3, {st_mode=S_IFREG|0664, st_size=2909, ...}) = 0
ioctl(3, TCGETS, 0x7fffc1f91eb0) = -1 ENOTTY (Inappropriate ioctl for device)
lseek(3, 0, SEEK_CUR) = 0
lseek(3, 0, SEEK_CUR) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)
I've also opened this as spacy issue at
https://github.com/explosion/spaCy/issues/4838 (which shows some
additonal info) -- however, IMHO as an interpreter python3 should
neversegfault even if the program supplied has issues?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python3 3.6.7-1~18.04
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 1 15:42:19 2020
InstallationDate: Installed on 2019-08-18 (136 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: python3-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: python3-defaults (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1858050
Title:
python3 segmentation faults with spacy
Status in python3-defaults package in Ubuntu:
New
Bug description:
After
# pip3 install spacy
executing
# python3 -m spacy download de
results in a segmentation fault, as shown by the following output woith
[Touch-packages] [Bug 1858035] [NEW] Xorg freeze (Ubuntu 19.10 stuck on splash screen)
Public bug reported: Yesterday I had just installed Ubuntu 19.10 and after my third or fourth reboot it would not start, it just got stuck on the splash screen. I didn't know what to do, but I still had the USB from which I had installed Ubuntu, so I plugged it in and booted up from the USB, and then I pressed the shutdown button, and before it shut down Ubuntu asked me to remove the installation media and press OK, I did, the laptop shut down, and now I booted up my laptop as usual, not from the USB, and this time it did not get stuck on the splash screen. So I left it at that, but just now, I booted up my laptop,and again it got stuck again, and so again I did the boot up from the USB, shut down, remove USB, and reboot as usual from the laptops HDD. Now it works again. This problem seems to happen on a random basis. I hope this helps to solve this problem. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 1 18:58:18 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0410] InstallationDate: Installed on 2019-12-30 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Latitude E4310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=6e8b1021-3bce-4fb7-a48b-eb93e408c4d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0XG3JF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0XG3JF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1858035 Title: Xorg freeze (Ubuntu 19.10 stuck on splash screen) Status in xorg package in Ubuntu: New Bug description: Yesterday I had just installed Ubuntu 19.10 and after my third or fourth reboot it would not start, it just got stuck on the splash screen. I didn't know what to do, but I still had the USB from which I had installed Ubuntu, so I plugged it in and booted up from the USB, and then I pressed the shutdown button, and before it shut down Ubuntu asked me to remove the installation media and press OK, I did, the laptop shut down, and now I booted up my laptop as usual, not from the USB, and this time it did not get stuck on the splash screen. So I left it at that, but just now, I booted up my laptop,and again it got stuck again, and so again I did the boot up from the USB, shut down, remove USB, and reboot as usual from the laptops HDD. Now it works again. This problem seems to happen on a random basis. I hope this helps to solve this problem. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 1 18:58:18 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Seems to
[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record
I am experiencing this problem from a Raspberry Pi 4, running Raspbian. It seems that disabling IPv6 works. I also removed isc-dhcp-client but it did not solve the problem. -- 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/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
BTW, just applying this patch[1] to bluez package from 18.04 fixes the a2dp problem for me with Sony WH-CH700N headphones. Patch applies cleanly to 5.48. 1. https://git.kernel.org/pub/scm/bluetooth/bluez.git/patch/?id=477ecca127c529611adbc53f08039cefaf86305d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+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 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
May we have this backported to 18.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+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
