[Touch-packages] [Bug 1779526] [NEW] Please merge 2.24.32-2 from Debian Sid
Public bug reported: 2.24.32-2 has been uploaded to Debian Sid fixing a few bugs. Let's merge it. ** Affects: gtk+2.0 (Ubuntu) Importance: Wishlist Assignee: Simon Quigley (tsimonq2) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1779526 Title: Please merge 2.24.32-2 from Debian Sid Status in gtk+2.0 package in Ubuntu: In Progress Bug description: 2.24.32-2 has been uploaded to Debian Sid fixing a few bugs. Let's merge it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1779526/+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 1749686] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()
[Expired for gstreamer1.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gstreamer1.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1749686 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() Status in gstreamer1.0 package in Ubuntu: Expired Bug description: Crashed on trying to open users section. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 15:02:50 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-02-15 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: gnome-control-center --overview Signal: 6 SourcePackage: gnome-control-center StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvideo4linux2.so gst_device_provider_start () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 gst_device_monitor_start () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1749686/+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 1768186] Re: please fix this bug
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1768186 Title: please fix this bug Status in xorg package in Ubuntu: Expired Bug description: please fix this bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue May 1 10:49:14 2018 DistUpgraded: 2018-04-29 11:31:40,368 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [104d:907b] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] [1002:6741] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-05-23 (342 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Sony Corporation VPCSA390X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=5ba136a7-7b25-4525-bd60-1cf00af4cd56 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-04-29 (1 days ago) dmi.bios.date: 06/15/2012 dmi.bios.vendor: INSYDE dmi.bios.version: R2087H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSA390X:pvrC60A2SLY:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCSA390X dmi.product.version: C60A2SLY dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue May 1 10:26:53 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-1 DP-2 HDMI-1 HDMI-2 LVDS-1 VGA-1 xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768186/+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 1007924] Re: pm-utils uses wrong interface for NetworkManager hook (should be org.freedesktop.NetworkManager.Sleep)
** Changed in: pm-utils Status: Confirmed => Won't Fix -- 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/1007924 Title: pm-utils uses wrong interface for NetworkManager hook (should be org.freedesktop.NetworkManager.Sleep) Status in pm-utils: Won't Fix Status in pm-utils package in Ubuntu: Triaged Status in pm-utils package in Debian: Confirmed Bug description: While looking at /var/log/pm-suspend.log I have noticed that the NetworkManager hooks fail: Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend_hybrid: Having NetworkManager put all interaces to sleep...Failed. Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend_hybrid: Having NetworkManager wake interfaces back up...Failed. Looking at the script is uses org.freedesktop.NetworkManager.sleep and org.freedesktop.NetworkManager.wake. Calling this results in errors like this: % sudo dbus-send --print-reply --system --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.sleep Error org.freedesktop.DBus.Error.UnknownMethod: Method "sleep" with signature "" on interface "org.freedesktop.NetworkManager" doesn't exist According to the documentation [1], the interface is different / has changed. The correct usage would be to call org.freedesktop.NetworkManager.Sleep with a boolean value, like: sudo dbus-send --print-reply --system --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Sleep boolean:true 1: http://projects.gnome.org/NetworkManager/developers/api/09/spec.htmlorg.freedesktop.NetworkManager.Sleep ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pm-utils 1.4.1-9 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sat Jun 2 21:36:40 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/pm-utils/+bug/1007924/+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 1007924]
pm-utils hasn't been touched in eight years, none of this is likely to get addressed. Closing bugs and disabling the bz product. -- 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/1007924 Title: pm-utils uses wrong interface for NetworkManager hook (should be org.freedesktop.NetworkManager.Sleep) Status in pm-utils: Won't Fix Status in pm-utils package in Ubuntu: Triaged Status in pm-utils package in Debian: Confirmed Bug description: While looking at /var/log/pm-suspend.log I have noticed that the NetworkManager hooks fail: Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend_hybrid: Having NetworkManager put all interaces to sleep...Failed. Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend_hybrid: Having NetworkManager wake interfaces back up...Failed. Looking at the script is uses org.freedesktop.NetworkManager.sleep and org.freedesktop.NetworkManager.wake. Calling this results in errors like this: % sudo dbus-send --print-reply --system --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.sleep Error org.freedesktop.DBus.Error.UnknownMethod: Method "sleep" with signature "" on interface "org.freedesktop.NetworkManager" doesn't exist According to the documentation [1], the interface is different / has changed. The correct usage would be to call org.freedesktop.NetworkManager.Sleep with a boolean value, like: sudo dbus-send --print-reply --system --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Sleep boolean:true 1: http://projects.gnome.org/NetworkManager/developers/api/09/spec.htmlorg.freedesktop.NetworkManager.Sleep ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pm-utils 1.4.1-9 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sat Jun 2 21:36:40 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/pm-utils/+bug/1007924/+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 1574354] Re: playing .mp4 in VLC freezes machine
** Attachment added: "codec-info.png" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+attachment/5158265/+files/codec-info.png -- 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/1574354 Title: playing .mp4 in VLC freezes machine Status in mesa package in Ubuntu: Confirmed Bug description: VLC was running fine on 15.10 but since upgrading, video files (e.g. .mp4) play for a few minutes and then crash the whole machine (i.e. I have to power off and on). Possibly linked is that audio (in web pages or playing audio files thru Banshee) loops (stutters) for about a second every few minutes (but doesn't crash the machine). vlc-nox: /usr/bin/vlc Description: Ubuntu 16.04 LTS Release: 16.04 vlc: Installed: 2.2.2-5 Candidate: 2.2.2-5 Version table: *** 2.2.2-5 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 19:20:41 2016 InstallationDate: Installed on 2014-02-17 (797 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+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 1574354] Re: playing .mp4 in VLC freezes machine
Same situation described by miwait00, I'm running an Nvidia GTX 1050Ti with nvidia-384 driver, here's my vlc log, codec details and system info: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS" ** Attachment added: "vlc_output" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+attachment/5158264/+files/vlc_output -- 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/1574354 Title: playing .mp4 in VLC freezes machine Status in mesa package in Ubuntu: Confirmed Bug description: VLC was running fine on 15.10 but since upgrading, video files (e.g. .mp4) play for a few minutes and then crash the whole machine (i.e. I have to power off and on). Possibly linked is that audio (in web pages or playing audio files thru Banshee) loops (stutters) for about a second every few minutes (but doesn't crash the machine). vlc-nox: /usr/bin/vlc Description: Ubuntu 16.04 LTS Release: 16.04 vlc: Installed: 2.2.2-5 Candidate: 2.2.2-5 Version table: *** 2.2.2-5 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 19:20:41 2016 InstallationDate: Installed on 2014-02-17 (797 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+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 1032456] Re: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2
I have been an issue with my printer for few days. I have tried your method but I got no result after that I visit https://printerssupport.org/ricoh-printer-support/ this site and they give me to guide me to set up. Now My printer is working fine -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1032456 Title: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2 Status in cups package in Ubuntu: Fix Released Status in cups source package in Precise: Fix Released Bug description: My Canon i560 was working fine until the update two days ago. Now it fails every single job, printing half a page and then ejecting the page when a USB reset is issued. Same printer works fine when printing through Windows in Virtualbox with USB passthrough. Summary: the USB backend "improvements" have rendered my printer useless with CUPS. Unloading the usblp module makes no difference - the USB reset is what aborts the print job. [ 224.008042] usb 3-1: reset full-speed USB device number 3 using uhci_hcd [ 224.161701] usblp0: USB Bidirectional printer dev 3 if 0 alt 0 proto 2 vid 0x04A9 pid 0x108 Kubuntu 12.04 [IMPACT] Everyone with a Canon inkjet connected to USB and also users of some other printer models on USB get printouts with the last page being incomplete. This happens for every job. For everyone with a Samsung printer the problem of bug 995111 shows up again. [TESTCASE] Unfortunately, for reproducing this bug one needs the actual hardware. Connect a Canon inkjet (or other models mentioned in this bug report) to the USB and print from a completely updated Precise system. The last page of each job will come out incomplete. Connect a Samsung printer to the USB and print from a completely updated Precise system. You will get printouts with weird characters (at least from the second job on) as described in bug 995111. After installing the proposed package all these problems should disappear. [Regression Potential] Regression risk is very low. The fix is not doing the USB device reset on the printer after the job for most printers. The fix contains an exception rule for Samsung printers and Prolific Technology USB->Parallel adapters, to avoid reoccurring of bug 987485 and bug 997040. It is still possible that some printers are treated incorrectly in terms of whether they need a reset after the job or not. As most printers work both with and without reset this risk is very low. All reported problems are solved with the proposed fix. *** dpkg -l "*cups*"|grep ii ii bluez-cups 4.98-2ubuntu7 Bluetooth printer driver for CUPS ii cups 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - server ii cups-bsd 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - BSD commands ii cups-client 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - client programs (SysV) ii cups-common 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - common files ii cups-filters 1.0.18-0ubuntu0.1OpenPrinting CUPS Filters ii cups-ppdc 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - PPD manipulation utilities ii ghostscript-cups 9.05~dfsg-0ubuntu4.1 interpreter for the PostScript language and for PDF - CUPS filters ii libcups2 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - Core library ii libcupscgi1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - CGI library ii libcupsdriver1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - Driver library ii libcupsfilters1 1.0.18-0ubuntu0.1OpenPrinting CUPS Filters - Shared library ii libcupsimage2 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - Raster image library ii libcupsmime1 1.5.3-0ubuntu2 Common UNIX Printing System(tm) - M
[Touch-packages] [Bug 900930] Re: pm-utils: typo in set_sata_alpm()
** Changed in: pm-utils
Status: Confirmed => Won't Fix
--
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/900930
Title:
pm-utils: typo in set_sata_alpm()
Status in pm-utils:
Won't Fix
Status in pm-utils package in Ubuntu:
Fix Released
Bug description:
function set_sata_alpm prints "Setting SATA APLM on %s to %s...", in fact
this should be "Setting SATA ALPM on %s to %s...".
(APLM --> ALPM).
set_sata_alpm() {
# see kernel commit 6013efd8860bf15c1f86f365332642cfe557152f
kv="$(uname -r)"
[ "$kv" ] || exit $NA #for paranoia's sake
[ "${kv%-*}" \< "2.6.33" ] && exit $NA # avoid fs corruption
for f in /sys/class/scsi_host/host*; do
[ -w "$f/link_power_management_policy" ] || continue
printf "Setting SATA APLM on %s to %s..." "${f##*/}" "$1"
echo "$1" > "$f/link_power_management_policy" && echo Done. || \
echo Failed.
done
}
Be nice if this was fixed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/900930/+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 900930]
pm-utils hasn't been touched in eight years, none of this is likely to
get addressed. Closing bugs and disabling the bz product.
--
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/900930
Title:
pm-utils: typo in set_sata_alpm()
Status in pm-utils:
Won't Fix
Status in pm-utils package in Ubuntu:
Fix Released
Bug description:
function set_sata_alpm prints "Setting SATA APLM on %s to %s...", in fact
this should be "Setting SATA ALPM on %s to %s...".
(APLM --> ALPM).
set_sata_alpm() {
# see kernel commit 6013efd8860bf15c1f86f365332642cfe557152f
kv="$(uname -r)"
[ "$kv" ] || exit $NA #for paranoia's sake
[ "${kv%-*}" \< "2.6.33" ] && exit $NA # avoid fs corruption
for f in /sys/class/scsi_host/host*; do
[ -w "$f/link_power_management_policy" ] || continue
printf "Setting SATA APLM on %s to %s..." "${f##*/}" "$1"
echo "$1" > "$f/link_power_management_policy" && echo Done. || \
echo Failed.
done
}
Be nice if this was fixed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/900930/+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 1551515] Re: My phone's bluetooth is displayed dozens of times under the network list (wifi icon)
For fuck's sake is this how long it takes to fix high-importance bugs?? Still an issue. -- 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/1551515 Title: My phone's bluetooth is displayed dozens of times under the network list (wifi icon) Status in One Hundred Papercuts: Confirmed Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: I can hardly even start describing how screwed up this is. Have a look at the screenshot. I had seen this before and hadn't even realized that "XT1039 Network" repeated like 37 times had something to do with my own Android phone, a motorola Moto G. Needless to say I have only one. Out of curiosity I clicked on one of "them" (thinking this was some neighboor's device, obviously suspecting it was just one device repeated several times because of a bug), and then my phone vibrated prompting me whether to accept the connection from the computer. Which I did. As a result, the bluetooth indicator next to the network indicator showed a lock icon for a fraction of a second, which immediately disappeared. I guess that means that the computer and the phone peered via bluetooth for a few instants. At the same time, the wifi icon started animating (as if the computer was connecting to a wifi network... or a network of any kind I guess, since the same stupidly designed wifi-like animation is used when connecting to LAN via an ethernet cable). After that, the small lock below the bluetooth icon disappeared, the wifi icon stopped animating and went back to its normal "connected" status (I was previously and still connected to my home router's wifi network), and a baloon saying "Disconnected [NL] Network" appeared and disappeared. Then I repeated the test several times with the same result, except that the phone didn't prompt me any more to accept the connection. This is totally screwed up in several ways. First, there's no reason "XT1039 Network" should be listed AT ALL together with wifi and ethernet networks. What kind of "network" is it supposed to be?? Of course I have not turned on bluetooth tethering on the phone, and bluetooth connection to the phone is already available under the bluetooth indicator. If it makes any sense at all to show the mobile device as a "network" alongside with wifi and cable networks because, well, bluetooth is a network as well, then 1) the list of bluetooth "networks" should have a header, just like "wifi networks" and "ethernet network". Right now, there is just a list of networks that you don't know what kind they are 2) the device should be only listed once, not 37 times 3) I also suspect the 3 items called just "network" are related 4) If it is there at all, it must work. What is it supposed to do? The same as unfolding the menu under the Bluetooth indicator, hovering on the device there (which is listed only once there) and turning on the "Connection" switch? That one does work. This one (in the list of networks) doesn't. And if it is supposed to do something different, it's clearly failing as well. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.2 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 1 03:29:50 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (871 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.167 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2016-01-18 (42 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-20T16:52:59.722501 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1551515/+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 1778512] Re: PCI/internal sound card not detected. System Sound settings shows dummy output
I have the exact same problem. I tried upgrading from 16.04 LTS to 17.10 and 18.04, but this doesn't solve the issue for me. -- 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/1778512 Title: PCI/internal sound card not detected. System Sound settings shows dummy output Status in alsa-driver package in Ubuntu: Confirmed Bug description: aplay -l gives out aplay: device_list:268: no soundcards found... System settings says Dummy output cat /proc/asound/card0/codec* | grep Codec gives out: cat: '/proc/asound/card0/codec*': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jun 25 17:53:06 2018 InstallationDate: Installed on 2017-02-09 (501 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 036R0F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/18/2016:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn036R0F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 7560 dmi.sys.vendor: Dell Inc. !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Mon Jun 25 12:51:47 UTC 2018 !!Linux Distribution !!-- Ubuntu 16.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.4 LTS" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; UBUNTU_CODENAME=xenial !!DMI Information !!--- Manufacturer: Dell Inc. Product Name: Inspiron 7560 Product Version: Firmware Version: 1.0.7 Board Vendor: Dell Inc. Board Name:036R0F !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0003:00/status 15 /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/DELL0782:00/status 15 /sys/bus/acpi/devices/DELLABCE:00/status 15 /sys/bus/acpi/devices/DLLK0782:00/status 15 /sys/bus/acpi/devices/INT33A1:00/status15 /sys/bus/acpi/devices/INT33D0:00/status15 /sys/bus/acpi/devices/INT3400:00/status15 /sys/bus/acpi/devices/INT3402:00/status15 /sys/bus/acpi/devices/INT3403:00/status15 /sys/bus/acpi/devices/INT3403:01/status15 /sys/bus/acpi/devices/INT340E:00/status15 /sys/bus/acpi/devices/INT344B:00/status15 /sys/bus/acpi/devices/INT3F0D:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/LNXPOWER:01/status 1 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:04/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/LNXPOWER:09/status 1 /sys/bus/acpi/devices/LNXPOWER:0a/status 1 /sys/bus/acpi/devices/LNXPOWER:0b/status 1 /sys/bus/acpi/devices/LNXPOWER:0c/status 1 /sys/bus/acpi/devices/LNXPOWER:0d/status 1 /sys/bus/acpi/devices/LNXPOWER:0e/status 1 /sys/bus/acpi/devices/LNXPOWER:0f/status 1 /sys/bus/acpi/devices/LNXPOWER:10/status 1 /sys/bus/acpi/devices/LNXPOWER:11/status 1 /sys/bus/acpi/devices/LNXPOWER:12/status 1 /sys/bus/acpi/devices/LNXPOWER:13/status 1 /sys/bus/acpi/devices/LNXVIDEO:01/status 15 /sys/bus/acpi/devices/MSFT0101:00/status 15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0C02:03/status3 /sys/bus/acpi/devices/PNP0C02:05/status3 /sys/bus/acpi/devices/PNP0C09:00/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status15 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/d
[Touch-packages] [Bug 1778512] Re: PCI/internal sound card not detected. System Sound settings shows dummy output
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1778512 Title: PCI/internal sound card not detected. System Sound settings shows dummy output Status in alsa-driver package in Ubuntu: Confirmed Bug description: aplay -l gives out aplay: device_list:268: no soundcards found... System settings says Dummy output cat /proc/asound/card0/codec* | grep Codec gives out: cat: '/proc/asound/card0/codec*': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Jun 25 17:53:06 2018 InstallationDate: Installed on 2017-02-09 (501 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 036R0F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd11/18/2016:svnDellInc.:pnInspiron7560:pvr:rvnDellInc.:rn036R0F:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 7560 dmi.sys.vendor: Dell Inc. !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Mon Jun 25 12:51:47 UTC 2018 !!Linux Distribution !!-- Ubuntu 16.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.4 LTS" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; UBUNTU_CODENAME=xenial !!DMI Information !!--- Manufacturer: Dell Inc. Product Name: Inspiron 7560 Product Version: Firmware Version: 1.0.7 Board Vendor: Dell Inc. Board Name:036R0F !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0003:00/status 15 /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/DELL0782:00/status 15 /sys/bus/acpi/devices/DELLABCE:00/status 15 /sys/bus/acpi/devices/DLLK0782:00/status 15 /sys/bus/acpi/devices/INT33A1:00/status15 /sys/bus/acpi/devices/INT33D0:00/status15 /sys/bus/acpi/devices/INT3400:00/status15 /sys/bus/acpi/devices/INT3402:00/status15 /sys/bus/acpi/devices/INT3403:00/status15 /sys/bus/acpi/devices/INT3403:01/status15 /sys/bus/acpi/devices/INT340E:00/status15 /sys/bus/acpi/devices/INT344B:00/status15 /sys/bus/acpi/devices/INT3F0D:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/LNXPOWER:01/status 1 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:04/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/LNXPOWER:09/status 1 /sys/bus/acpi/devices/LNXPOWER:0a/status 1 /sys/bus/acpi/devices/LNXPOWER:0b/status 1 /sys/bus/acpi/devices/LNXPOWER:0c/status 1 /sys/bus/acpi/devices/LNXPOWER:0d/status 1 /sys/bus/acpi/devices/LNXPOWER:0e/status 1 /sys/bus/acpi/devices/LNXPOWER:0f/status 1 /sys/bus/acpi/devices/LNXPOWER:10/status 1 /sys/bus/acpi/devices/LNXPOWER:11/status 1 /sys/bus/acpi/devices/LNXPOWER:12/status 1 /sys/bus/acpi/devices/LNXPOWER:13/status 1 /sys/bus/acpi/devices/LNXVIDEO:01/status 15 /sys/bus/acpi/devices/MSFT0101:00/status 15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0C02:03/status3 /sys/bus/acpi/devices/PNP0C02:05/status3 /sys/bus/acpi/devices/PNP0C09:00/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status15 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /
[Touch-packages] [Bug 1548486] Re: Sleep hook in a subdirectory ignored but causes double execution of previous hook
Launchpad has imported 3 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=94323. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-02-28T01:54:18+00:00 Dirk F wrote: Created attachment 122012 patch taken from running pm-functions; also fixes comment typo The function run_hooks() in pm-functions proposes to-be-executed hooks that includes subdirectories in the hook directories but neither fully validates each such hook as a regular file nor handles a set of to-be- executed hooks in a subdirectory. This can cause a hook to be executed more than once. At lines 241 on, there is a code path with no else clause: if [ -f "$syshooks/$base" ]; then hook="$syshooks/$base" elif [ -f "$phooks/$base" ]; then hook="$phooks/$base" fi If the $base proposed by the for statement at line 229 doesn't match either of the -f tests (which will happen eg if a hook is configured in a subdirectory of the hook directory), the $hook from the previous iteration can be accidentally reused. An easy fix is to insert the missing else clause before the fi line so that the script skips the subdirectory or other non-regular file and carries on with the next correctly specified hook, as in the attached patch. Reply at: https://bugs.launchpad.net/ubuntu/+source/pm- utils/+bug/1548486/comments/2 On 2016-02-28T01:59:57+00:00 Dirk F wrote: Created attachment 122013 patch taken from running pm-functions; also fixes comment typo (attached wrong file) Reply at: https://bugs.launchpad.net/ubuntu/+source/pm- utils/+bug/1548486/comments/3 On 2018-06-29T19:57:09+00:00 Ajax-a wrote: pm-utils hasn't been touched in eight years, none of this is likely to get addressed. Closing bugs and disabling the bz product. Reply at: https://bugs.launchpad.net/ubuntu/+source/pm- utils/+bug/1548486/comments/14 ** Changed in: pm-utils Status: Unknown => Won't Fix ** Changed in: pm-utils Importance: Unknown => Medium -- 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/1548486 Title: Sleep hook in a subdirectory ignored but causes double execution of previous hook Status in pm-utils: Won't Fix Status in pm-utils package in Ubuntu: Confirmed Bug description: The set of sleep hooks provided in /usr/lib/pm-utils/sleep.d includes one (95packagekit/95packagekit) that is stored in a subdirectory. This has two effects: 1the hook is not run; 2the previous hook, currently /usr/lib/pm-utils/sleep.d/95led, is run for a second time instead. Presumably #1 is wrong, and results from an installation fault in packagekit, separately reported as bug 1548480. #2 occurs because the function run_hooks() in /usr/lib/pm-utils/pm- functions computes a list of to-be-executed hooks that includes directories but neither fully validates each such hook as a regular file nor handles a set of to-be-executed hooks in a subdirectory. At lines 243 on, there is a code path with no else clause through which the $hook from the previous iteration can be accidentally reused: if [ -f "$syshooks/$base" ]; then hook="$syshooks/$base" elif [ -f "$phooks/$base" ]; then hook="$phooks/$base" fi An easy fix is to insert the missing else clause before the fi line so that the script skips the subdirectory or other non-regular file and carries on with the next correctly specified hook: if [ -f "$syshooks/$base" ]; then hook="$syshooks/$base" elif [ -f "$phooks/$base" ]; then hook="$phooks/$base" else continue fi Observed in Lubuntu 14.04.3,4 with pm-utils 1.4.1-13ubuntu0.1,2. However the relevant pm-utils code dates back to 2008, pm-utils upstream version 1.1.0. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions] ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Mon Feb 22 17:10:53 2016 InstallationDate: Installed on 2016-02-21 (0 days ago) InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To mana
[Touch-packages] [Bug 1779485] [NEW] bluetooth not saving mouse connection. Having to reconnect each ubuntu start.
Public bug reported: Each time I start Ubuntu, I have to turn the mouse on. Version 18.04 is not saving the setting. I don't remember having this problem with previous versions of Ubuntu. Last version I used was 16.04.4. Please fix, it's really annoying. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 12:39:30 2018 InstallationDate: Installed on 2018-06-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Sony Corporation VPCSC41FM ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=3bf4784c-157a-4e30-a49b-8f1a34d4f64c ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: INSYDE dmi.bios.version: R2087H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSC41FM:pvrC60A8X35:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCSC41FM dmi.product.version: C60A8X35 dmi.sys.vendor: Sony Corporation hciconfig: hci0: Type: Primary Bus: USB BD Address: 64:27:37:CA:4D:B1 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:16064 acl:815 sco:0 events:143 errors:0 TX bytes:6645 acl:47 sco:0 commands:81 errors:0 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779485 Title: bluetooth not saving mouse connection. Having to reconnect each ubuntu start. Status in bluez package in Ubuntu: New Bug description: Each time I start Ubuntu, I have to turn the mouse on. Version 18.04 is not saving the setting. I don't remember having this problem with previous versions of Ubuntu. Last version I used was 16.04.4. Please fix, it's really annoying. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 12:39:30 2018 InstallationDate: Installed on 2018-06-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Sony Corporation VPCSC41FM ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=3bf4784c-157a-4e30-a49b-8f1a34d4f64c ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: INSYDE dmi.bios.version: R2087H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSC41FM:pvrC60A8X35:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCSC41FM dmi.product.version: C60A8X35 dmi.sys.vendor: Sony Corporation hciconfig: hci0:Type: Primary Bus: USB BD Address: 64:27:37:CA:4D:B1 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:16064 acl:815 sco:0 events:143 errors:0 TX bytes:6645 acl:47 sco:0 commands:81 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779485/+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 1774399] Re: No sound at all (internal speaker - LG AIO)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1774399 Title: No sound at all (internal speaker - LG AIO) Status in alsa-driver package in Ubuntu: Confirmed Bug description: My internal speaker is not working [ALC282]. When I plug in headphones or external speakers into headphone slot there's no problem. But when I try to play sounds with my internal speaker, it stay mute. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio1188 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 31 08:12:41 2018 InstallationDate: Installed on 2018-04-29 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antonio1188 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [24V360-L.BJ57P1, Realtek ALC282, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2016 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 24VA1440 X64 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 24V360 dmi.board.vendor: LG Electronics dmi.board.version: FAB2 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: LG Electronics dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr24VA1440X64:bd03/25/2016:svnLGElectronics:pn24V360-L.BJ57P1:pvr0.1:rvnLGElectronics:rn24V360:rvrFAB2:cvnLGElectronics:ct13:cvr0.1: dmi.product.family: Braswell System dmi.product.name: 24V360-L.BJ57P1 dmi.product.version: 0.1 dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1774399/+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 1774421] Re: [X555LA, Realtek ALC3236, Speaker, Internal] No sound when switching from HDMI to internal audio
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1774421 Title: [X555LA, Realtek ALC3236, Speaker, Internal] No sound when switching from HDMI to internal audio Status in alsa-driver package in Ubuntu: Confirmed Bug description: When switching from HDMI audio to internal speakers, the sound stops working altogether. The only way to prevent this is to enter the settings while still connected to HDMI and select "Speakers - Built in audio" as the output. Disconnecting from HDMI without doing this stops any audio playing through internal speakers or headphones (including the speaker test in settings). It was expected that disconnecting a HDMI output would automatically change the sound output to internal speakers. Attempting to click "Speakers - Built in audio" when disconnected from HDMI has no effect, the only way to remedy this is to reconnect the device to HDMI and select the above output. This means if the device is removed from HDMI and taken to another location, no sound can be used until a HDMI output can be found and connected. Rebooting has mixed effects, on one occasion a reboot restored the sound, however on all others it does not. The test tones DID play during the debug process however this is the only sounds I can get to play. The version of Ubuntu is 18.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: laoise 1485 F...m pulseaudio /dev/snd/controlC1: laoise 1485 F pulseaudio /dev/snd/pcmC0D7p: laoise 1485 F...m pulseaudio /dev/snd/controlC0: laoise 1485 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 31 14:35:41 2018 InstallationDate: Installed on 2017-04-13 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [X555LA, Realtek ALC3236, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2018-05-12 (19 days ago) dmi.bios.date: 08/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LA.308:bd08/14/2014:svnASUSTeKCOMPUTERINC.:pnX555LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1774421/+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 1777329] Re: [SATELLITE S50D-A-10G, IDT 92HD99BXX, Speaker, ATAPI] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1777329 Title: [SATELLITE S50D-A-10G, IDT 92HD99BXX, Speaker, ATAPI] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: No sound at all, drivers picked up showing sound waves in pulse... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: marcin 1329 F pulseaudio /dev/snd/controlC0: marcin 1329 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 15:35:55 2018 InstallationDate: Installed on 2018-02-18 (118 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm 961 F pulseaudio marcin 1329 F pulseaudio /dev/snd/controlC0: gdm 961 F pulseaudio marcin 1329 F pulseaudio Symptom_Jack: Speaker, ATAPI Symptom_Type: No sound at all Title: [SATELLITE S50D-A-10G, IDT 92HD99BXX, Speaker, ATAPI] No sound at all UpgradeStatus: Upgraded to bionic on 2018-06-15 (1 days ago) dmi.bios.date: 01/28/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: VG10AD dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.40:bd01/28/2014:svnTOSHIBA:pnSATELLITES50D-A-10G:pvrPSKKWE-00Q008EN:rvnAMD:rnVG10AD:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: SATELLITE S50D-A-10G dmi.product.version: PSKKWE-00Q008EN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1777329/+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 1771239] Re: [Inspiron 5537, Realtek ALC3223, Speaker, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1771239 Title: [Inspiron 5537, Realtek ALC3223, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: My sound was working just fine, then tonight I came to use my notebook, and noticed that there was no sound from any applications. Using the ubuntu settings sound test, I was getting audio from both speaker and headphones, but moving the volume bar doesn't do any feedback, chrome and spotivyhave no audio. Reinstalled the pulseaudio, now moving the volume bar plays the feedback "beep", but still no audio from applications, and no more audio on speaker test! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: esoares6391 F pulseaudio /dev/snd/controlC0: esoares6391 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon May 14 22:11:08 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-18 (603 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2642 F pulseaudio esoares6391 F pulseaudio /dev/snd/controlC0: gdm2642 F pulseaudio esoares6391 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Inspiron 5537, Realtek ALC3223, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2017-10-24 (202 days ago) dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0YK7DY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5537:pvrA09:rvnDellInc.:rn0YK7DY:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.family: 00 dmi.product.name: Inspiron 5537 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1771239/+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 1773700] Re: [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1773700 Title: [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I just installed ubuntu, and immediately had problems of very loud and crackling sound no matter what sound I played. I tried the three solutions listed here https://wiki.ubuntu.com/Audio/PositionReporting, the three of them resulted in no sound at all, and now even if I revert back everything, I can't get any sound out from the speakers. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: remuth 1038 F...m pulseaudio /dev/snd/controlC0: remuth 1038 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 27 22:37:20 2018 InstallationDate: Installed on 2018-05-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: remuth 1038 F...m pulseaudio /dev/snd/controlC0: remuth 1038 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [UX390UAK, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX390UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX390UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX390UAK.312:bd04/25/2017:svnASUSTeKCOMPUTERINC.:pnUX390UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX390UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX390UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1773700/+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 1773732] Re: [Satellite S55D-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1773732 Title: [Satellite S55D-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: ``` dan@dan-laptop:~$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dan1116 F pulseaudio /dev/snd/controlC0: dan1116 F pulseaudio CurrentDesktop: XFCE Date: Mon May 28 00:33:03 2018 InstallationDate: Installed on 2018-05-02 (25 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dan1116 F pulseaudio /dev/snd/controlC0: dan1116 F pulseaudio Symptom_Jack: Speaker, ATAPI Symptom_Type: No sound at all Title: [Satellite S55D-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: VG10AD dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.10:bd06/19/2013:svnTOSHIBA:pnSatelliteS55D-A:pvrPSKKSU-00S006:rvnAMD:rnVG10AD:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite S55D-A dmi.product.version: PSKKSU-00S006 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1773732/+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 1770429] Re: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1770429 Title: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3 Status in alsa-driver package in Ubuntu: Confirmed Bug description: I updated my Surface Pro 3 From Ubuntu 17.10 to Ubuntu 18.04 (did a clean install) and the only audio working was from the headphone jack. I tried all these: [troubleshooting guide](https://help.ubuntu.com/community/SoundTroubleshootingProcedure) [this answer](https://askubuntu.com/questions/117842/no-sound-from-speakers-but-headphones-work) [another answer](https://askubuntu.com/questions/829520/ubuntu-16-04-no-sound-from-speakers-only-headphones-working) I went back and tested the live CD and even the live cd has no audio through the speakers. so this must be related to 18.04. I never had sound issues before and under windows audio still works correctly. here is my alsa iformation http://www.alsa- project.org/db/?f=8bf135db52610a603014779ef24041a491c8a32d and here is how I fixed it: renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa- base.bk , then rebooting the computer fixed the my speaker sound issue. I then restored line by line in to /etc/modprobe.d/alsa-base.conf, rebooting between restored lines, until all lines were back and ... it still worked! so I restored the original /etc/modprobe.d/alsa-base.conf and rebooted the computer and everything was still working so I am not sure what the problem was but is now fixed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.16.7-041607-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: carlosr2267 F pulseaudio /dev/snd/controlC0: carlosr2267 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 10 10:15:29 2018 InstallationDate: Installed on 2018-04-27 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11.2350 dmi.board.asset.tag: 0 dmi.board.name: Surface Pro 3 dmi.board.vendor: Microsoft Corporation dmi.board.version: 1 dmi.chassis.asset.tag: 0 dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11.2350:bd01/23/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1: dmi.product.family: Surface dmi.product.name: Surface Pro 3 dmi.product.version: 1 dmi.sys.vendor: Microsoft Corporation mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-09T14:04:13.313882 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1770429/+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 911325] Re: pm-utils: additonal power.d scripts to save power
** Changed in: pm-utils Status: Confirmed => Won't Fix -- 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/911325 Title: pm-utils: additonal power.d scripts to save power Status in pm-utils: Won't Fix Status in pm-utils package in Ubuntu: Fix Released Bug description: The kernel allows us to save power on a range of devices - currently pm-utils power.d does not make full advantage of these power savings. Tools like PowerTop provide advice on which devices can be set into a "Good" power management state. Analysis on a selection of representative modern mobile x86 based platforms (e.g. netbook, laptop) has shown that a subset of devices can be safely put into a power saving state. Each of the "Good/Bad" PowerTop device recommendations were measured accurately using a 6 digit digital multimeter. Each measurement was based on measuring current drain over 5 x 60 second periods on the Good and Bad settings and seeing which device shows the most promising power saving. The resulting data can be found here: http://zinc.canonical.com/~cking/power-benchmarking/powertop-good-bad- recommendations/powertop-good-bad-recommendations.ods And the write-up of the methodology and conclusions can be found here: http://zinc.canonical.com/~cking/power-benchmarking/powertop-good-bad- recommendations/results.txt From this analysis we can draw a conclusion that the following devices behave well to power savings as follows: * Webcam * Audio * DRAM * Ethernet * Wifi * Bluetooth * SATA link * MMC/SD From this, two pm-utils power.d scripts were written to control the power state of the above devices. The script pci_devices controls the PCI specific devices and usb_bluetooth controls USB webcams into and out of power saving modes. These were then tested by community - see: https://wiki.ubuntu.com/Kernel/PowerManagementPMUtils Power savings were calculated from the ACPI battery information. The characteristics and reliability of ACPI battery data to measure power consumption has been studied here: http://zinc.canonical.com/~cking /power-benchmarking/acpi-battery-results/results.txt - the test scripts used by the community testing use a battery power measuring tool that has been calibrated and checked using a 6 digit multimeter and calculates the average power consumption and standard deviation (to allow us to discriminate against unreliable samples). From these results, I discarded data where the standard deviation was rather high and also results where the savings or losses were smaller than the standard deviation. This left me with a set of results where we have conclusive data showing us power savings or losses with these new scripts. The conclusion is that the vast majority of machines save power. Also, users tested their machines to see if the devices behaved correctly. On the samples of machines I have (Dell Inspirion 6400, Lenovo X220i, HP Mini 210 + HP Mini 10) I see no regressions. I therefore am requesting that the two new pm-utils/power.d scripts are added to pm- utils. Typical savings: 0.38 W per machine with some machines seeing > 1-2W savings. Attached to this bug report are the two new scripts for pm- utils/power.d To manage notifications about this bug go to: https://bugs.launchpad.net/pm-utils/+bug/911325/+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 911325]
pm-utils hasn't been touched in eight years, none of this is likely to get addressed. Closing bugs and disabling the bz product. -- 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/911325 Title: pm-utils: additonal power.d scripts to save power Status in pm-utils: Won't Fix Status in pm-utils package in Ubuntu: Fix Released Bug description: The kernel allows us to save power on a range of devices - currently pm-utils power.d does not make full advantage of these power savings. Tools like PowerTop provide advice on which devices can be set into a "Good" power management state. Analysis on a selection of representative modern mobile x86 based platforms (e.g. netbook, laptop) has shown that a subset of devices can be safely put into a power saving state. Each of the "Good/Bad" PowerTop device recommendations were measured accurately using a 6 digit digital multimeter. Each measurement was based on measuring current drain over 5 x 60 second periods on the Good and Bad settings and seeing which device shows the most promising power saving. The resulting data can be found here: http://zinc.canonical.com/~cking/power-benchmarking/powertop-good-bad- recommendations/powertop-good-bad-recommendations.ods And the write-up of the methodology and conclusions can be found here: http://zinc.canonical.com/~cking/power-benchmarking/powertop-good-bad- recommendations/results.txt From this analysis we can draw a conclusion that the following devices behave well to power savings as follows: * Webcam * Audio * DRAM * Ethernet * Wifi * Bluetooth * SATA link * MMC/SD From this, two pm-utils power.d scripts were written to control the power state of the above devices. The script pci_devices controls the PCI specific devices and usb_bluetooth controls USB webcams into and out of power saving modes. These were then tested by community - see: https://wiki.ubuntu.com/Kernel/PowerManagementPMUtils Power savings were calculated from the ACPI battery information. The characteristics and reliability of ACPI battery data to measure power consumption has been studied here: http://zinc.canonical.com/~cking /power-benchmarking/acpi-battery-results/results.txt - the test scripts used by the community testing use a battery power measuring tool that has been calibrated and checked using a 6 digit multimeter and calculates the average power consumption and standard deviation (to allow us to discriminate against unreliable samples). From these results, I discarded data where the standard deviation was rather high and also results where the savings or losses were smaller than the standard deviation. This left me with a set of results where we have conclusive data showing us power savings or losses with these new scripts. The conclusion is that the vast majority of machines save power. Also, users tested their machines to see if the devices behaved correctly. On the samples of machines I have (Dell Inspirion 6400, Lenovo X220i, HP Mini 210 + HP Mini 10) I see no regressions. I therefore am requesting that the two new pm-utils/power.d scripts are added to pm- utils. Typical savings: 0.38 W per machine with some machines seeing > 1-2W savings. Attached to this bug report are the two new scripts for pm- utils/power.d To manage notifications about this bug go to: https://bugs.launchpad.net/pm-utils/+bug/911325/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection
Before start pptp vpn: $ ls -laF /run/systemd/resolve/stub-resolv.conf -rw-r--r-- 1 systemd-resolve systemd-resolve 714 jun 30 18:26 /run/systemd/resolve/stub-resolv.conf After start pptp vpn: $ ls -laF /run/systemd/resolve/stub-resolv.conf -rw-r--r-- 1 systemd-resolve systemd-resolve 714 jun 30 18:26 /run/systemd/resolve/stub-resolv.conf After stop pptp vpn: $ ls -laF /run/systemd/resolve/stub-resolv.conf -rw--- 1 root root 714 jun 30 18:26 /run/systemd/resolve/stub-resolv.conf File /run/systemd/resolve/stub-resolv.conf is readable only for root user. And DNS is accessible only for root user. $ ping google.com ping: google.com: Temporary failure in name resolution $ sudo ping google.com PING google.com (172.217.169.110) 56(84) bytes of data. 64 bytes from sof02s31-in-f14.1e100.net (172.217.169.110): icmp_seq=1 ttl=55 time=0.999 ms .. -- 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/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1763101] Re: OOM-Bug in cxxfilt (binuitils-2.30-15ubuntu1)
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-12934 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1763101 Title: OOM-Bug in cxxfilt (binuitils-2.30-15ubuntu1) Status in binutils package in Ubuntu: Confirmed Bug description: Dear all, The following binutils cxxfilt OOM bug was found by a modified version of the kAFL fuzzer (https://github.com/RUB-SysSec/kAFL). I have attached the input and an ASAN report. Steps to reproduce: Build current verison of binutils: ``` pull-lp-source binutils cd binutils-2.30 CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" ./configure CC=clang CXX=clang++ CFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" CXXFLAGS="-fsanitize=address -fsanitize-recover=address -ggdb" LDFLAGS="-fsanitize=address" make ``` Run inputs under ASAN: ``` ASAN_OPTIONS=halt_on_error=false:allow_addr2line=true ./cxxfilt -t < oom ``` We can verify this issue for cxxfilt binuitils-2.30-15ubuntu1 (Ubuntu 16.04.4 LTS / sources from "pull-lp-source bintuils") on an Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz server machine with 32GB RAM. Credits: Sergej Schumilo, Cornelius Aschermann (both of Ruhr- Universität Bochum) Best regards, Sergej Schumilo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1763101/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 645974] Re: xfs handling on battery not working correctly
** Changed in: pm-utils
Status: Confirmed => Won't Fix
--
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/645974
Title:
xfs handling on battery not working correctly
Status in pm-utils:
Won't Fix
Status in pm-utils package in Ubuntu:
Fix Released
Bug description:
Binary package hint: pm-utils
The file /usr/lib/pm-utils/power.d/xfs_buffer has a typo, preventing
/proc/sys/fs/xfs/xfssyncd_centisecs and xfsbufd_centisecs from being
updated correctly when on battery power.
Currently, it has a function like this:
xfs_battery() {
state_exists xfs_buffer_default || \
read_values |savestate xfs_buffer_default
write_values "$XFS_AGE_BUFFER" "$XFS_BUFD" "$XFS_SYNCD"
}
Whereas it should be:
xfs_battery() {
state_exists xfs_buffer_default || \
read_values |savestate xfs_buffer_default
write_values "$XFS_AGE_BUFFER" "$XFS_SYNCD" "$XFS_BUFD"
}
Patch is attached.
This is on maverick beta with latest updates (pm-utils 1.4.1-2)
To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/645974/+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 645974]
pm-utils hasn't been touched in eight years, none of this is likely to
get addressed. Closing bugs and disabling the bz product.
--
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/645974
Title:
xfs handling on battery not working correctly
Status in pm-utils:
Won't Fix
Status in pm-utils package in Ubuntu:
Fix Released
Bug description:
Binary package hint: pm-utils
The file /usr/lib/pm-utils/power.d/xfs_buffer has a typo, preventing
/proc/sys/fs/xfs/xfssyncd_centisecs and xfsbufd_centisecs from being
updated correctly when on battery power.
Currently, it has a function like this:
xfs_battery() {
state_exists xfs_buffer_default || \
read_values |savestate xfs_buffer_default
write_values "$XFS_AGE_BUFFER" "$XFS_BUFD" "$XFS_SYNCD"
}
Whereas it should be:
xfs_battery() {
state_exists xfs_buffer_default || \
read_values |savestate xfs_buffer_default
write_values "$XFS_AGE_BUFFER" "$XFS_SYNCD" "$XFS_BUFD"
}
Patch is attached.
This is on maverick beta with latest updates (pm-utils 1.4.1-2)
To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/645974/+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 1767578] Re: libcurl is missing brotli support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: curl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1767578 Title: libcurl is missing brotli support Status in curl package in Ubuntu: Confirmed Bug description: Now that the bionic release of curl has added HTTP/2 support, please consider adding support for brotli too. This can be compiled in with the --with-brotli flag that is already available and adding the libbrotli-dev package as a dependency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1767578/+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 698331] Re: thinkpad T410: Bluetooth not getting disabled on suspend
Launchpad has imported 3 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=33759. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2011-01-31T06:12:10+00:00 Martin Pitt wrote: (Original bug at https://launchpad.net/bugs/698331) The 49bluetooth hook disables /proc/acpi/ibm/bluetooth but this isn't synchronous, i. e. it doesn't wait until the module usage count actually drops to 0. Due to that, it's impossible to add btusb to SUSPEND_MODULES (on some models/older kernels you need to do that to fix suspend problems), as at that point the module is still in use. To demonstrate that, I added some logging to the hook: before: = --- /proc/acpi/ibm/bluetooth status: enabled commands: enable, disable --- rfkill list --- 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 1: tpacpi_wwan_sw: Wireless WAN Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 10: hci0: Bluetooth Soft blocked: no Hard blocked: no --- lsmod --- btusb 18600 2 === after writing /proc/acpi/ibm/bluetooth --- /proc/acpi/ibm/bluetooth status: disabled commands: enable, disable --- rfkill list --- 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no 1: tpacpi_wwan_sw: Wireless WAN Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 10: hci0: Bluetooth Soft blocked: no Hard blocked: no --- lsmod --- btusb 18600 2 As we can see, /proc/acpi/ibm/bluetooth got updated, but both rfkill as well as the module usage count are still active. === after sleep 0.5 --- /proc/acpi/ibm/bluetooth status: disabled commands: enable, disable --- rfkill --- 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no 1: tpacpi_wwan_sw: Wireless WAN Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no --- lsmod --- btusb 18600 0 Now it disappeared from rfkill and the module usage count dropped to 0. I'll write a better hook which waits for the module to get unused. Reply at: https://bugs.launchpad.net/ubuntu/+source/pm- utils/+bug/698331/comments/4 On 2011-01-31T06:33:16+00:00 Martin Pitt wrote: Created attachment 42750 patch against git head What do you think about this? Reply at: https://bugs.launchpad.net/ubuntu/+source/pm- utils/+bug/698331/comments/5 On 2018-06-29T19:57:20+00:00 Ajax-a wrote: pm-utils hasn't been touched in eight years, none of this is likely to get addressed. Closing bugs and disabling the bz product. Reply at: https://bugs.launchpad.net/ubuntu/+source/pm- utils/+bug/698331/comments/22 ** Changed in: pm-utils Status: Confirmed => Won't Fix -- 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/698331 Title: thinkpad T410: Bluetooth not getting disabled on suspend Status in pm-utils: Won't Fix Status in pm-utils package in Ubuntu: Fix Released Status in pm-utils source package in Lucid: Fix Released Status in pm-utils source package in Natty: Fix Released Bug description: Binary package hint: pm-utils I discovered this in Lucid, and verified the behavior still exists in natty. /usr/lib/pm-utils/sleep.d/49bluetooth attempts to disable bluetooth using echo disable > /proc/acpi/ibm/bluetooth. Under normal operating conditions, this command seems to work, when run by hand: # rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 4: hci0: Bluetooth Soft blocked: no Hard blocked: no # lsmod | grep ^btusb btusb 18600 2 # echo disable > /proc/acpi/ibm/bluetooth # rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no # lsmod | grep ^btusb btusb 18600 0 Note that after disabling bluetooth in this manner, rfkill no longer even lists hci0, and the btusb usage count dropped from 2 to 0. However, when this is called from /usr/lib/pm- utils/sleep.d/49bluetooth, during a suspend, this does not appear to be working.
[Touch-packages] [Bug 1754851] Re: Broken Packages
** Package changed: xorg (Ubuntu) => 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/1754851 Title: Broken Packages Status in Ubuntu: New Bug description: Failure to update Libreoffice! Difficulty solving the problem ... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 CurrentDesktop: X-Cinnamon Date: Sat Mar 10 11:10:24 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-27 (133 days ago) InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20141126 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1754851/+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 1761559] Re: Firefox not launching
** Package changed: xorg (Ubuntu) => firefox (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/1761559 Title: Firefox not launching Status in firefox package in Ubuntu: New Bug description: I downloaded firefox with ubuntu software icon on desktop and it doesn't launch when i click on firefox icon ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-40.60-generic 4.4.21 Uname: Linux 4.4.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 237417/59645952 files, 5116824/238562048 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Apr 5 20:15:08 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:078b] InstallationDate: Installed on 2018-04-04 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-40-generic.efi.signed root=UUID=80cba23c-e910-497a-a302-d4aa391738ac ro locale=C quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.0 dmi.board.name: 05269N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.0:bd02/06/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn05269N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Apr 5 18:09:36 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1649 vendor BOE xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1761559/+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 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.
*** This bug is a duplicate of bug 1652282 *** https://bugs.launchpad.net/bugs/1652282 This also affects me, running on X. When I run gparted I get prompted to insert the password, then the terminal says Unit -.mount does not exist, proceeding anyway. and it just hangs there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1744372 Title: gparted does not start - Unit -.mount does not exist, proceeding anyway. Status in gparted package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Invalid Bug description: 1. fresh ubuntu 18.04 daily: lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2. install gparted with Software: gparted: Installiert: 0.30.0-3ubuntu1 Installationskandidat: 0.30.0-3ubuntu1 Versionstabelle: *** 0.30.0-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. launch with icon - enter password - nothing. 4.launch in terminal: Unit -.mount does not exist, proceeding anyway. Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/home.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-120.mount → /dev/null. Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null. Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/home.mount. Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount. Removed /run/systemd/system/run-snapd-ns.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-120.mount. Removed /run/systemd/system/snap-core-3748.mount. Removed /run/systemd/system/snap-vlc-113.mount. Removed /run/systemd/system/tmp.mount. How to Fix: run xhost +local: before gparted! # this only bypass the wayland restriction; meaning a security violation (not a fix !!! ) thomas@ubuntu-1804:~$ xhost +local: non-network local connections being added to access control list thomas@ubuntu-1804:~$ gparted Unit -.mount does not exist, proceeding anyway. Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/home.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-120.mount → /dev/null. Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null. Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. Gtk-Message: Failed to load module "canberra-gtk-module" == libparted : 3.2 == Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/home.mount. Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount. Removed /run/systemd/system/run-snapd-ns.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-120.mount. Removed /run/systemd/system/snap-core-3748.mount. Removed /run/systemd/system/snap-vlc-113.mount. Removed /run/systemd/system/tmp.mount. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gparted 0.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 19 19:45:14 2018 InstallationDate: Installed on 2018-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gparted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1744372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packa
[Touch-packages] [Bug 1779438] Re: Cannot resolve names using systemd-resolved stub resolver
** Package changed: ubuntu => systemd (Ubuntu) ** Tags added: bionic -- 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/1779438 Title: Cannot resolve names using systemd-resolved stub resolver Status in systemd package in Ubuntu: New Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 I am running a clean install of Ubuntu 18.04. This bug was also present for me on a clean install of Ubuntu 17.10 and I had a solution, but it appears to no longer work. What I expect to happen: Ping other hosts on network by name What happened instead: I can't ping other machines on network via name. From my Ubuntu 18.04 machine, I `ping ubuntu-test-1` and `ping ubuntu-test-1.localdomain` but neither work. I can ping by IP address though. The other machines on the network are Ubuntu Server 16.04.3 machines and can ping each other by name also. All machines on network including problem one receive DHCP leases from same server (192.168.20.1) I believe the problem is systemd-resolved stub resolver. `cat /etc/resolv.conf` # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "systemd-resolve --status" to see details about the uplink DNS servers # currently in use. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 search localdomain If I change the nameserver line to the IP of my nameserver, not the stub, resolution works. nameserver 192.168.20.1 search localdomain Now I can ping hosts by name. I used to solve this problem like this... `sudo systemctl disable systemd-resolved.service` `echo "nameserver 192.168.20.1" | sudo tee -a /etc/resolvconf/resolv.conf.d/tail` `sudo reboot` But /etc/resolvconf/resolv.conf.d no longer exists, and it's about time this problem was fixed :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779438/+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 1779438] [NEW] Cannot resolve names using systemd-resolved stub resolver
You have been subscribed to a public bug: Description:Ubuntu 18.04 LTS Release:18.04 I am running a clean install of Ubuntu 18.04. This bug was also present for me on a clean install of Ubuntu 17.10 and I had a solution, but it appears to no longer work. What I expect to happen: Ping other hosts on network by name What happened instead: I can't ping other machines on network via name. >From my Ubuntu 18.04 machine, I `ping ubuntu-test-1` and `ping >ubuntu-test-1.localdomain` but neither work. I can ping by IP address though. The other machines on the network are Ubuntu Server 16.04.3 machines and can ping each other by name also. All machines on network including problem one receive DHCP leases from same server (192.168.20.1) I believe the problem is systemd-resolved stub resolver. `cat /etc/resolv.conf` # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "systemd-resolve --status" to see details about the uplink DNS servers # currently in use. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 search localdomain If I change the nameserver line to the IP of my nameserver, not the stub, resolution works. nameserver 192.168.20.1 search localdomain Now I can ping hosts by name. I used to solve this problem like this... `sudo systemctl disable systemd-resolved.service` `echo "nameserver 192.168.20.1" | sudo tee -a /etc/resolvconf/resolv.conf.d/tail` `sudo reboot` But /etc/resolvconf/resolv.conf.d no longer exists, and it's about time this problem was fixed :) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- Cannot resolve names using systemd-resolved stub resolver https://bugs.launchpad.net/bugs/1779438 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. -- 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 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
There is a fix for this: https://ubuntuforums.org/showthread.php?t=2305819 add a file to the /etc/modules-load.d directory to have the modules loaded into the kernel at boot. I just created a file called netfilter.conf and put the following in it: nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre Is it safe to use this solution? I don't know what those three entries mean. -- 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/1568560 Title: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3 My WiFi connection is very unstable and I have to often restart NetworkManager service (~ a dozen times every day...): sudo systemctl -l status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago Main PID: 27832 (NetworkManager) Memory: 13.8M CPU: 1.729s CGroup: /system.slice/NetworkManager.service ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d ├─27832 /usr/sbin/NetworkManager --no-daemon └─30448 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0 avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: keyfile: add connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0") avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1-nic): new Tun device (carrier: OFF, driver: 'tun', ifindex: 34) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1): bridge port virbr1-nic was attached avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1-nic): enslaved to virbr1 avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr0): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Also, each time I restart my desktop, NetworkManager generates a crash report: cf. attached screenshots. I have tried an Ubuntu VM with the same packages related to networking and the exact same releases (same repositories), the crash never happens; the difference appears to be only the type of network connection: WiFi for the desktop vs Ethernet for the VM. Any suggestion? To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1568560/+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
