[Touch-packages] [Bug 2029173] Re: fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': No such file or directory
The error is unchanged with Kubuntu 23.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2029173 Title: fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa- mesa3d.bc': No such file or directory Status in mesa package in Ubuntu: New Bug description: Programs using OpenCL report the following bug: fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': No such file or directory This bug is encountered when trying to run github.com/ggerganov/llama.cpp build with CLBlast or just using clinfo. The hardware is an AMD Radeon RX 6700 XT lsb_release -rd: No LSB modules are available. Description:Ubuntu 23.04 Release:23.04 apt-cache policy mesa-opencl-icd #although I am not sure that this is the offending package mesa-opencl-icd: Installed: 23.0.4-0ubuntu1~23.04.1 Candidate: 23.0.4-0ubuntu1~23.04.1 Version table: *** 23.0.4-0ubuntu1~23.04.1 500 500 http://de.archive.ubuntu.com/ubuntu lunar-updates/universe amd64 Packages 100 /var/lib/dpkg/status 23.0.2-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu lunar/universe amd64 Packages pc@pc-MS-7C02:~/ML/llama.cpp$ clinfo output: Number of platforms 2 Platform Name Clover Platform Vendor Mesa Platform VersionOpenCL 1.1 Mesa 23.0.4-0ubuntu1~23.04.1 Platform ProfileFULL_PROFILE Platform Extensions cl_khr_icd Platform Extensions function suffix MESA Platform Name rusticl Platform Vendor Mesa/X.org Platform VersionOpenCL 3.0 Platform ProfileFULL_PROFILE Platform Extensions cl_khr_icd Platform Extensions with Versioncl_khr_icd 0x40 (1.0.0) Platform Numeric Version0xc0 (3.0.0) Platform Extensions function suffix MESA Platform Host timer resolution 0ns Platform Name Clover Number of devices 1 Device Name AMD Radeon RX 6700 XT (navi22, LLVM 15.0.7, DRM 3.49, 6.2.0-26-generic) Device Vendor AMD Device Vendor ID0x1002 Device Version OpenCL 1.1 Mesa 23.0.4-0ubuntu1~23.04.1 Device Numeric Version 0x401000 (1.1.0) Driver Version 23.0.4-0ubuntu1~23.04.1 Device OpenCL C Version OpenCL C 1.1 Device OpenCL C Numeric Version 0x401000 (1.1.0) Device Type GPU Device Profile FULL_PROFILE Device AvailableYes Compiler Available Yes Max compute units 40 Max clock frequency 2855MHz Max work item dimensions3 Max work item sizes 256x256x256 Max work group size 256 === CL_PROGRAM_BUILD_LOG === fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': No such file or directory Preferred work group size multiple (kernel) Preferred / native vector sizes char16 / 16 short8 / 8 int 4 / 4 long 2 / 2 half 0 / 0(n/a) float4 / 4 double 2 / 2 (cl_khr_fp64) Half-precision Floating-point support (n/a) Single-precision Floating-point support (core) Denormals No Infinity and NANs Yes Round to nearest Yes Round to zero No Round to infinity No IEEE754-2008 fused multiply-add No Support is emulated in software No Correctly-rounded divide and sqrt
[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Can't switch to HSP profile with my Aftershokz. Says: "Failed to change profile to headset_head_unit" -- 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After updating the release from Ubuntu 19.10 to 20.04, the bluetooth headset doesn't work anymore when HSP/HFP profile is selected. With Ubuntu 19.10 the headset was working, there was audio and the mic was perfect for video conferencing. [Steps to reproduce] 1. Connect headset (used blueman to setup and connect) 1.1. When connected the system automatically selects A2DP profile 2. Start playing audio (browser or other) 3. Change profile to HSP/HFP with pavucontrol (or blueman) 4. The audio disappears and microphone is not working (no input) 5. Optionally switch back to A2DP and the audio comes back [Expected] When switching to HSP/HFP the audio should keep playing and the microphone should start working [Notes] I tried with pavucontrol to switch between profiles while playing audio from a browser. As side note there's a led in the headset that still blinks when switching profile. I tried deleting the pulse folder under user's profile .config without success, also reinstalled packages and did a `sudo alsa force-reload` and rebooting several times. Note: not sure this is a duplicate of [Bug #1576559], it looks quite different since the profile changes but the headset stops working. [System info] Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64 pulseaudio: 1:13.99.1-1ubuntu3 bluez: 5.53-0ubuntu3 Headset: Sennheiser HD 4.50 BTNC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
I attached the Realtek dump with my headphones plugged into the jack for comparison. ** Attachment added: "RtHDDump.txt.headphonesInJack" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5353097/+files/RtHDDump.txt.headphonesInJack -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron:
[Touch-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Exactly the same problem with Samsung Notebook 9 Pro (np930mbe-k04us) which also has an ALC298. Headphones are working with model=mono-speakers. I attached my Realtek dump. I'm also soliciting the arch forum for help (I'm running arch): https://bbs.archlinux.org/viewtopic.php?pid=1897858 ** Attachment added: "RtHDDump.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5353056/+files/RtHDDump.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019
[Touch-packages] [Bug 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04
Same problem on Ubuntu 19.10 on HP 250 G7. Tried editing logind.conf as per previous suggestions, but no combination solved the problem. Tried installing pm-utils, which weren't installed (see #117), that didn't help either. Tried turning off the automatic suspend and automatic blank screen in the Power settings, thinking that they might for whatever reason be interfering; no success. Tried uncommenting InhibitDelayMaxSec, HoldoffTimeoutSec and LidSwitchIgnoreInhibited (with both 'yes' and 'no'), none of those did it. Closing the lid only blanks the screen (fans are running), even if I leave it for some time. Opening the lid turns the screen back on, but doesn't open up the login screen. Besides the unsuccessful editing of logind.conf, the only other concurrent issue that I haven't found anyone else encountering, is that, in my case, closing the lid and then opening it also turns on Airplane mode, and then the next time I close it and open it, it turns the Airplane mode off. As I often need a quick suspend, as a temporary workaround, I set it up so that the physical power button suspends it. This works as intended, without any problems, so instead of having to close the lid, I have to press the button, then close the lid. It's better than having to open the top right menu, press Alt and click suspend, then close the lid, every time, but I'd still like to solve the problem properly... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1574120 Title: Notebook doesn't suspend when lid is closed after update to 16.04 Status in pm-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: My notebook does not suspend after upgrading from 15.10 to 16.04. According to system settings the notebook should suspend when lid is closed but actually this does not happen. Instead it continues to run as if nothing had happened. With the previous versions of ubuntu (14.04-15.10) everything worked fine. My System: HP Pavilion dv7. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: acpi (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 23 23:11:15 2016 InstallationDate: Installed on 2015-10-29 (176 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: acpi UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1574120/+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 1511735] Re: libnl: fail to bind() netlink sockets
It affect my 14.04.1 system WITHOUT trusty-proposed enabled. FYI: kernel 3.19.0-59-generic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1511735 Title: libnl: fail to bind() netlink sockets Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: In Progress Status in libnl3 package in Debian: Fix Released Bug description: [Triage Notes] The proposed fix for this bug in libnl3 caused a regression in trusty- proposed, tracked in bug 1539634. The regression is caused by a latent bug in Network Manager. We expect to fix this by landing a fix for the bug in Network Manager in trusty-updates at the same time as this fix. [Impact] * Applications in Trusty using libnl-3-200 which frequently open and close netlink sockets can easily fail when attempting to bind the local socket. The problem happens when libnl choose a port id already used by another application and subsequently libnl fails instead of trying another port id. The original bug was discovered when attempting to start a virtual machine under libvirt, which is a user of this library. * Backporting fixes from upstream release fixes a real bug in the current version of the library in Trusty. The alternative is for all applications to manually manage their local port allocation, or as upstream has accepted allowing libnl to attempt to try for other local ports. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. [Test Case] * On a Trusty 14.04 system 1. sudo apt-get install libnl-3-200 libnl-3-dev libnl-3-dev \ libnl-genl-3-dev libnl-route-3-200 \ make gcc build-essential libnl1 2. download and unpack attachment: lp_1511735_test.tar 3. Run testcases: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 6975 (pid: 6974) local port has been set by the libnl to 6975 (pid: 6975) ERROR: genl_connect(): Object exists (local port: 6975, pid: 6975) libnl FAILED % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=6978 TEST (a)... Traceback (most recent call last): File "libnl3-test-rh1249158.py", line 226, in locals()["TEST_" + arg]() File "libnl3-test-rh1249158.py", line 140, in TEST_a sk = nl_get_socket() File "libnl3-test-rh1249158.py", line 115, in nl_get_socket raise IOError(-err, _nl_geterror()) OSError: [Errno 6] b'Unspecific failure' 4. After applying the updated packages: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 11295 (pid: 11294) local port has been set by the libnl to 2894081055 (pid: 11295) libnl OK % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=11296 TEST (a)... ...done TEST (b)... ...done TEST (c)... ...done TEST (d)... ...done [Regression Potential] * There are quite a few high profile packages that depend on this package, notably libvirt and network-manager. The complete list is here: # on Trusty % apt-rdepends -r libnl-3-200 | head -n 33 libnl-3-200 Reverse Depends: batctl (>= 2013.4.0-2) Reverse Depends: bmon (>= 1:3.1-1) Reverse Depends: crda (>= 1.1.2-1ubuntu2) Reverse Depends: hostapd (>= 1:2.1-0ubuntu1) Reverse Depends: ipvsadm (>= 1:1.26-2ubuntu1) Reverse Depends: iw (>= 3.4-1) Reverse Depends: keepalived (>= 1:1.2.7-1ubuntu1) Reverse Depends: kismet (>= 2013.03.R1b-3) Reverse Depends: knemo (>= 0.7.6-2) Reverse Depends: libfsobasics3 (>= 0.12.0-4) Reverse Depends: libnetcf1 (>= 1:0.2.3-4ubuntu1) Reverse Depends: libnl-3-200-dbg (= 3.2.21-1) Reverse Depends: libnl-3-dev (= 3.2.21-1) Reverse Depends: libnl-cli-3-200 (= 3.2.21-1) Reverse Depends: libnl-genl-3-200 (= 3.2.21-1) Reverse Depends: libnl-nf-3-200 (= 3.2.21-1) Reverse Depends: libnl-route-3-200 (= 3.2.21-1) Reverse Depends: libnl-utils (>= 3.2.21-1) Reverse Depends: libnss-gw-name (>= 0.3-2) Reverse Depends: libvirt-bin (>= 1.2.2-0ubuntu13) Reverse Depends: libvirt0 (>= 1.2.2-0ubuntu13) Reverse Depends: lowpan-test-tools (>= 0.3-1) Reverse Depends: lowpan-tools (>= 0.3-1) Reverse Depends: neard (>= 0.11-1) Reverse Depends: neard-tools (>= 0.11-1)
[Touch-packages] [Bug 1581535] Re: libnl upgrade breaks Network Manager
*** This bug is a duplicate of bug 1511735 *** https://bugs.launchpad.net/bugs/1511735 As Jon B mentions in comment #9 above, even I DO NOT have trusty- proposed enabled on my 14.04.1 with kernel 3.19.0-59-generic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1581535 Title: libnl upgrade breaks Network Manager Status in libnl3 package in Ubuntu: Invalid Status in libnl3 source package in Trusty: Confirmed Bug description: I appear to have been hit by a regression problem in the libnl update described here: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735 After running a regular software update this morning and rebooting, I've completely lost networking access. Network Manager is down. I'm running Trusty 14.04. I tried this workaround: http://askubuntu.com/questions/727127/last-upgrade-crashes-network- manager-no-internet-connection-no-applet ... and step 1 didn't work. I'll be trying step 2 tonight when I've got more time. I'm filing this as a new bug with a regression-update, as indicated in the above-linked bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581535/+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