[Touch-packages] [Bug 1633912] Re: Problem with DNS resolution after suspend
More people with the same problem: https://ubuntuforums.org/showthread.php?t=2340142 Workaround: Edit /etc/NetworkManager/NetworkManager.conf and remove the line "dns=dnsmasq". -- 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/1633912 Title: Problem with DNS resolution after suspend Status in network-manager package in Ubuntu: Confirmed Bug description: I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I have network issues, one time I was not able to connect to a wifi network (might report another bug if this occurees again, but maybe it is related, as in network-manager is in some broken state after suspend). Here is whats happening pretty often: After resume from suspend I have a solid network connection, no problem to ping machines in LAN or on the internet. But DNS resolution is broken until I restart the network-manager service. I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it should be in there. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 21:01:09 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-28 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src 172.18.0.1 192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.118 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+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 1633912] Re: Problem with DNS resolution after suspend
I've had the same problem on two computers since upgrading from 16.04 to 16.10, in both cases killing dnsmasq after the first suspend fixes it and it stays fixed after subsequent suspends. -- 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/1633912 Title: Problem with DNS resolution after suspend Status in network-manager package in Ubuntu: Confirmed Bug description: I upgraded my laptop to 16.10 yesterday. Sometimes after suspend I have network issues, one time I was not able to connect to a wifi network (might report another bug if this occurees again, but maybe it is related, as in network-manager is in some broken state after suspend). Here is whats happening pretty often: After resume from suspend I have a solid network connection, no problem to ping machines in LAN or on the internet. But DNS resolution is broken until I restart the network-manager service. I ran ubuntu-bug while DNS was broken, so if anything gets log-ed it should be in there. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 16 21:01:09 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-09-28 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.0.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev br-541a0f9bec93 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-541a0f9bec93 proto kernel scope link src 172.18.0.1 192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.118 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-10-15 (1 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633912/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
I have the same problem with ccsm, don't know why the lowgfx profile doesn't show but you can manually import it from /etc/compizconfig /unity-lowgfx.ini. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Released Status in nux source package in Xenial: Fix Released Status in unity source package in Xenial: Fix Released Status in unity-control-center source package in Xenial: Fix Released Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
I have the same problem with ccsm, don't know why the lowgfx profile doesn't show but you can manually import it from /etc/compizconfig /unity-lowgfx.ini. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Released Status in nux source package in Xenial: Fix Released Status in unity source package in Xenial: Fix Released Status in unity-control-center source package in Xenial: Fix Released Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Why does the GUI update-manager not update to the latest compiz package? I noticed the unity package updated and has unity7.conf which tries to use the compiz profile "unity-lowgfx" but it doesn't exist because compiz is still at version 20160526. sudo apt-get upgrade/dist-upgrade both detect and install the new compiz package but not update-manager. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Released Status in nux source package in Xenial: Fix Released Status in unity source package in Xenial: Fix Released Status in unity-control-center source package in Xenial: Fix Released Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1594570] Re: System Settings | Sound empty device list and no sound in video player, after reboot it works fine
Instead of restarting Ubuntu you can restart PulseAudio from terminal: pulseaudio -k (wait a few seconds) pulseaudio Disappearing PulseAudio output devices can happen when using Firejail. https://firejail.wordpress.com/support/known-problems/#pulseaudio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1594570 Title: System Settings | Sound empty device list and no sound in video player, after reboot it works fine Status in pulseaudio package in Ubuntu: New Bug description: Hi, on Ubuntu 16.04 I have installed VLC media player 2.2.2 from official repository. 1. File | Open and select some video. 2. Video starts playing but pop-up error appears: Audio output failed: The audio device "default" could not be used: Connection refused. See attachment: audio_error_in_vlc.png 3. From Ubuntu's System Settings | Sound I see there is no Output device. See attachment system_sound_settings_problem.png Note 1: Opening Firefox and playing videos from youtube.com and sound is working without a problem. Note 2: I have also tried playing video in "Totem Movie Player" default Ubuntu video player and sound also does not work. 4. Work-around is to restart Ubuntu. Then looking into System Settings | Sound and devices are displayed. See attachment: system_sound_after_reboot.png When running video in VLC now audio works fine. Also after reboot audio works fine when playing video from "Totem Movie Player". I am not an audio expert, but this does look like some system sound problem and not specific video/audio player, so I have reported a problem against pusleaudio package. I hope I have reported a problem against correct package. Regards ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jun 20 22:37:16 2016 InstallationDate: Installed on 2016-06-03 (17 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2006 dmi.bios.vendor: LENOVO dmi.bios.version: 79ET62WW (1.07 ) dmi.board.name: 1951F5G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr79ET62WW(1.07):bd06/12/2006:svnLENOVO:pn1951F5G:pvrThinkPadT60:rvnLENOVO:rn1951F5G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1951F5G dmi.product.version: ThinkPad T60 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1594570/+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 1448555] Re: network-manager does not autoconnect to wifi network after resume from suspend
I have the same log as #4 which is definitely a different bug. The network manager wakes prematurely before suspending causing it not to wake when resuming. I experienced this on lubuntu 15.04 but could not replicate it on Ubuntu 15.04. I isolated the problem down to xfce4 -power-manager which is responsible for suspending on lid close or timeout (manually suspending with systemctl suspend works fine). It seems to have issues with the recent change to systemd, switching back to Upstart fixes the problem. https://wiki.ubuntu.com/SystemdForUpstartUsers -- 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/1448555 Title: network-manager does not autoconnect to wifi network after resume from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: After upgrading to 15.04 network manager does not reconnect to the wifi network after resuming from a suspend to memory. Workaround: disable and re-enable wireless network - connects immediately ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 25 23:53:54 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-17 (708 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424) IpRoute: default via 10.1.0.254 dev wlan0 proto static metric 1024 10.0.0.0/8 dev wlan0 proto kernel scope link src 10.1.0.103 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-04-25 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 rsb_hs d8793959-2da1-4dc6-85ad-2dcf9e36e64b /org/freedesktop/NetworkManager/ActiveConnection/1 EC:88:92:61:E9:5F btdisconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- 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/ubuntu/+source/network-manager/+bug/1448555/+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 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
I isolated the problem down to an incompatibility between xfce4-power- manager and systemd. When the suspend timeout is reached or the lid is closed, the network manager is being woken before the system has suspended which causes it not to wake on resume. Switching from systemd back to Upstart fixes the problem. https://wiki.ubuntu.com/SystemdForUpstartUsers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' Status in dbus package in Ubuntu: Confirmed Bug description: The Wifi network can't connect after the wake up from suspend. Xubuntu 15.04 I'll post more useful details (journalctl log) as a comment to this bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 Uname: Linux 4.0.0-04rc5-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 2 18:18:56 2015 InstallationDate: Installed on 2015-03-27 (5 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+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 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
I get this same dbus error but it does not prevent wifi from successfully reconnecting after sleep when testing with systemctl suspend. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' Status in dbus package in Ubuntu: Confirmed Bug description: The Wifi network can't connect after the wake up from suspend. Xubuntu 15.04 I'll post more useful details (journalctl log) as a comment to this bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 Uname: Linux 4.0.0-04rc5-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 2 18:18:56 2015 InstallationDate: Installed on 2015-03-27 (5 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+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
